Home » Applications » Oracle Fusion Apps & E-Business Suite » Error occured when trying to update address using API
Error occured when trying to update address using API [message #271264] Mon, 01 October 2007 01:33 Go to next message
satya.das2007
Messages: 33
Registered: February 2007
Location: India
Member
Hi,

I am getting following error while executing hr_person_address_api.update_person_address API to update an address.

The following error has occurred:

ORA-20001: HR_xxxx_INVALID_EVENT_TYPE:
ORA-06512: at "APPS.PERADDRESSES_56U_DYT", line 171
ORA-04088: error during execution of trigger 'APPS.PERADDRESSES_56U_DYT'
ORA-06512: at "APPS.HR_PERSON_ADDRESS_API", line 3577
ORA-06512: at line 4

Code used is
declare
p_object_version_number number := 1;
begin
hr_person_address_api.update_person_address
    (p_validate                     => FALSE
    ,p_effective_date               => sysdate
    ,p_address_id                   => 41832
    ,p_object_version_number        => p_object_version_number
    ,p_date_from                    => sysdate
    ,p_date_to                      => NULL
    ,p_address_type                 => 'MAIL'
    ,p_comments                     => NULL
    ,p_address_line1                => '52 Pochester Drive'
    ,p_address_line2                => NULL
    ,p_address_line3                => NULL
    ,p_town_or_city                 => 'Mindarie'
    ,p_region_1                     => 'WA'
    ,p_postal_code                  => '6030'
    ,p_country                      => 'AU'
    ,p_telephone_number_1           => NULL
    ,p_telephone_number_2           => NULL
    ,p_telephone_number_3           => NULL
    ,p_addr_attribute_category      => NULL
    ,p_addr_attribute1              => NULL
    ,p_addr_attribute2              => NULL
    ,p_addr_attribute3              => NULL
    ,p_addr_attribute4              => NULL
    ,p_addr_attribute5              => NULL
    ,p_addr_attribute6              => NULL
    ,p_addr_attribute7              => NULL
    ,p_addr_attribute8              => NULL
    ,p_addr_attribute9              => NULL
    ,p_addr_attribute10             => NULL
    ,p_addr_attribute11             => NULL
    ,p_addr_attribute12             => NULL
    ,p_addr_attribute13             => NULL
    ,p_addr_attribute14             => NULL
    ,p_addr_attribute15             => NULL
    ,p_addr_attribute16             => NULL
    ,p_addr_attribute17             => NULL
    ,p_addr_attribute18             => NULL
    ,p_addr_attribute19             => NULL
    ,p_addr_attribute20             => NULL
    ,p_add_information13            => NULL
    ,p_add_information14            => NULL
    ,p_add_information15            => NULL
    ,p_add_information16            => NULL
    ,p_add_information17            => NULL
    ,p_add_information18            => NULL
    ,p_add_information19            => NULL
    ,p_add_information20            => NULL
    );

	end;

Re: Error occured when trying to update address using API [message #272182 is a reply to message #271264] Thu, 04 October 2007 03:29 Go to previous messageGo to next message
vamsi kasina
Messages: 2107
Registered: October 2003
Location: Riyadh, Saudi Arabia
Senior Member
Is PERADDRESSES_56U_DYT custom trigger?
Cross check the code.

By
Vamsi
Re: Error occured when trying to update address using API [message #272331 is a reply to message #272182] Thu, 04 October 2007 10:44 Go to previous messageGo to next message
satya.das2007
Messages: 33
Registered: February 2007
Location: India
Member
Its not a custom trigger, rather a seeded Oracle Trigger.

Still not able to find any solution for the same.

Can anyone try ?
Re: Error occured when trying to update address using API [message #272520 is a reply to message #272331] Fri, 05 October 2007 06:49 Go to previous messageGo to next message
vamsi kasina
Messages: 2107
Registered: October 2003
Location: Riyadh, Saudi Arabia
Senior Member
Quote:
Its not a custom trigger, rather a seeded Oracle Trigger.
In 11i or in R12?
Are you sure it is a seeded trigger? I didn't find that in etrm.
Please provide the 4 digit version.

By
Vamsi
Re: Error occured when trying to update address using API [message #272836 is a reply to message #272520] Mon, 08 October 2007 00:07 Go to previous messageGo to next message
satya.das2007
Messages: 33
Registered: February 2007
Location: India
Member
RDBMS : 9.2.0.7.0
Oracle Application version is : 11.5.10.2.

Its a seeded trigger, I believe.
Re: Error occured when trying to update address using API [message #272883 is a reply to message #272836] Mon, 08 October 2007 02:13 Go to previous messageGo to next message
vamsi kasina
Messages: 2107
Registered: October 2003
Location: Riyadh, Saudi Arabia
Senior Member
Quote:

Its a seeded trigger, I believe
I believe, it is not.
Anyway it is not a matter of belief.

On which table it is?
Have you checked the code of the trigger?
Have you checked etrm?

By
Vamsi
Re: Error occured when trying to update address using API [message #273201 is a reply to message #271264] Tue, 09 October 2007 08:18 Go to previous messageGo to next message
satya.das2007
Messages: 33
Registered: February 2007
Location: India
Member
PERADDRESSES_56U_DYT trigger is on PER_ADDRESSES Table and trigger code is

CREATE OR REPLACE TRIGGER PERADDRESSES_56U_DYT AFTER UPDATE ON PER_ADDRESSES FOR EACH ROW 
DECLARE 
  /* Local variable declarations */
  l_business_group_id            NUMBER;
  l_legislation_code             VARCHAR2(10);
  l_mode  varchar2(80);

--
BEGIN
/*
  ================================================
  This is a dynamically generated database trigger
  ================================================
            ** DO NOT CHANGE MANUALLY **          
  ------------------------------------------------
    Table:  PER_ADDRESSES
    Action: Update
    Date:   15/12/2006 22:03
    Name:   PER_ADDRESSES_ARU
    Info.:  Continuous Calculation trigger on update of Address
  ================================================
*/
--
  l_mode := pay_dyn_triggers.g_dyt_mode;
  pay_dyn_triggers.g_dyt_mode := pay_dyn_triggers.g_dbms_dyt;
IF NOT (hr_general.g_data_migrator_mode <> 'Y') THEN
  RETURN;
END IF;
  /* Initialising local variables */
  l_business_group_id := pay_core_utils.get_business_group(
    p_statement                    => 'select '||nvl(to_char(:new.business_group_id), 'null')||' from sys.dual'
  ); 
  --
  l_legislation_code := pay_core_utils.get_legislation_code(
    p_bg_id                        => l_business_group_id
  ); 
  --
  /* Is the trigger in an enabled functional area */
  IF paywsfgt_pkg.trigger_is_not_enabled(
    p_event_id          => 56,
    p_legislation_code  => l_legislation_code,
    p_business_group_id => l_business_group_id,
    p_payroll_id        => NULL
  ) THEN
    RETURN;
  END IF;
  --
  /* Global component calls */
  pay_continuous_calc.PER_ADDRESSES_aru(
    p_business_group_id            => l_business_group_id,
    p_effective_date               => :new.date_from,
    p_legislation_code             => l_legislation_code,
    p_new_ADDRESS_ID               => :new.ADDRESS_ID,
    p_new_ADDRESS_LINE1            => :new.ADDRESS_LINE1,
    p_new_ADDRESS_LINE2            => :new.ADDRESS_LINE2,
    p_new_ADDRESS_LINE3            => :new.ADDRESS_LINE3,
    p_new_ADDRESS_TYPE             => :new.ADDRESS_TYPE,
    p_new_ADDR_ATTRIBUTE1          => :new.ADDR_ATTRIBUTE1,
    p_new_ADDR_ATTRIBUTE10         => :new.ADDR_ATTRIBUTE10,
    p_new_ADDR_ATTRIBUTE11         => :new.ADDR_ATTRIBUTE11,
    p_new_ADDR_ATTRIBUTE12         => :new.ADDR_ATTRIBUTE12,
    p_new_ADDR_ATTRIBUTE13         => :new.ADDR_ATTRIBUTE13,
    p_new_ADDR_ATTRIBUTE14         => :new.ADDR_ATTRIBUTE14,
    p_new_ADDR_ATTRIBUTE15         => :new.ADDR_ATTRIBUTE15,
    p_new_ADDR_ATTRIBUTE16         => :new.ADDR_ATTRIBUTE16,
    p_new_ADDR_ATTRIBUTE17         => :new.ADDR_ATTRIBUTE17,
    p_new_ADDR_ATTRIBUTE18         => :new.ADDR_ATTRIBUTE18,
    p_new_ADDR_ATTRIBUTE19         => :new.ADDR_ATTRIBUTE19,
    p_new_ADDR_ATTRIBUTE2          => :new.ADDR_ATTRIBUTE2,
    p_new_ADDR_ATTRIBUTE20         => :new.ADDR_ATTRIBUTE20,
    p_new_ADDR_ATTRIBUTE3          => :new.ADDR_ATTRIBUTE3,
    p_new_ADDR_ATTRIBUTE4          => :new.ADDR_ATTRIBUTE4,
    p_new_ADDR_ATTRIBUTE5          => :new.ADDR_ATTRIBUTE5,
    p_new_ADDR_ATTRIBUTE6          => :new.ADDR_ATTRIBUTE6,
    p_new_ADDR_ATTRIBUTE7          => :new.ADDR_ATTRIBUTE7,
    p_new_ADDR_ATTRIBUTE8          => :new.ADDR_ATTRIBUTE8,
    p_new_ADDR_ATTRIBUTE9          => :new.ADDR_ATTRIBUTE9,
    p_new_ADDR_ATTRIBUTE_CATEGORY  => :new.ADDR_ATTRIBUTE_CATEGORY,
    p_new_ADD_INFORMATION13        => :new.ADD_INFORMATION13,
    p_new_ADD_INFORMATION14        => :new.ADD_INFORMATION14,
    p_new_ADD_INFORMATION15        => :new.ADD_INFORMATION15,
    p_new_ADD_INFORMATION16        => :new.ADD_INFORMATION16,
    p_new_ADD_INFORMATION17        => :new.ADD_INFORMATION17,
    p_new_ADD_INFORMATION18        => :new.ADD_INFORMATION18,
    p_new_ADD_INFORMATION19        => :new.ADD_INFORMATION19,
    p_new_ADD_INFORMATION20        => :new.ADD_INFORMATION20,
    p_new_BUSINESS_GROUP_ID        => :new.BUSINESS_GROUP_ID,
    p_new_COUNTRY                  => :new.COUNTRY,
    p_new_DATE_FROM                => :new.DATE_FROM,
    p_new_DATE_TO                  => :new.DATE_TO,
    p_new_PERSON_ID                => :new.PERSON_ID,
    p_new_POSTAL_CODE              => :new.POSTAL_CODE,
    p_new_PRIMARY_FLAG             => :new.PRIMARY_FLAG,
    p_new_PROGRAM_APPLICATION_ID   => :new.PROGRAM_APPLICATION_ID,
    p_new_PROGRAM_ID               => :new.PROGRAM_ID,
    p_new_PROGRAM_UPDATE_DATE      => :new.PROGRAM_UPDATE_DATE,
    p_new_REGION_1                 => :new.REGION_1,
    p_new_REGION_2                 => :new.REGION_2,
    p_new_REGION_3                 => :new.REGION_3,
    p_new_REQUEST_ID               => :new.REQUEST_ID,
    p_new_STYLE                    => :new.STYLE,
    p_new_TELEPHONE_NUMBER_1       => :new.TELEPHONE_NUMBER_1,
    p_new_TELEPHONE_NUMBER_2       => :new.TELEPHONE_NUMBER_2,
    p_new_TELEPHONE_NUMBER_3       => :new.TELEPHONE_NUMBER_3,
    p_new_TOWN_OR_CITY             => :new.TOWN_OR_CITY,
    p_old_ADDRESS_ID               => :old.ADDRESS_ID,
    p_old_ADDRESS_LINE1            => :old.ADDRESS_LINE1,
    p_old_ADDRESS_LINE2            => :old.ADDRESS_LINE2,
    p_old_ADDRESS_LINE3            => :old.ADDRESS_LINE3,
    p_old_ADDRESS_TYPE             => :old.ADDRESS_TYPE,
    p_old_ADDR_ATTRIBUTE1          => :old.ADDR_ATTRIBUTE1,
    p_old_ADDR_ATTRIBUTE10         => :old.ADDR_ATTRIBUTE10,
    p_old_ADDR_ATTRIBUTE11         => :old.ADDR_ATTRIBUTE11,
    p_old_ADDR_ATTRIBUTE12         => :old.ADDR_ATTRIBUTE12,
    p_old_ADDR_ATTRIBUTE13         => :old.ADDR_ATTRIBUTE13,
    p_old_ADDR_ATTRIBUTE14         => :old.ADDR_ATTRIBUTE14,
    p_old_ADDR_ATTRIBUTE15         => :old.ADDR_ATTRIBUTE15,
    p_old_ADDR_ATTRIBUTE16         => :old.ADDR_ATTRIBUTE16,
    p_old_ADDR_ATTRIBUTE17         => :old.ADDR_ATTRIBUTE17,
    p_old_ADDR_ATTRIBUTE18         => :old.ADDR_ATTRIBUTE18,
    p_old_ADDR_ATTRIBUTE19         => :old.ADDR_ATTRIBUTE19,
    p_old_ADDR_ATTRIBUTE2          => :old.ADDR_ATTRIBUTE2,
    p_old_ADDR_ATTRIBUTE20         => :old.ADDR_ATTRIBUTE20,
    p_old_ADDR_ATTRIBUTE3          => :old.ADDR_ATTRIBUTE3,
    p_old_ADDR_ATTRIBUTE4          => :old.ADDR_ATTRIBUTE4,
    p_old_ADDR_ATTRIBUTE5          => :old.ADDR_ATTRIBUTE5,
    p_old_ADDR_ATTRIBUTE6          => :old.ADDR_ATTRIBUTE6,
    p_old_ADDR_ATTRIBUTE7          => :old.ADDR_ATTRIBUTE7,
    p_old_ADDR_ATTRIBUTE8          => :old.ADDR_ATTRIBUTE8,
    p_old_ADDR_ATTRIBUTE9          => :old.ADDR_ATTRIBUTE9,
    p_old_ADDR_ATTRIBUTE_CATEGORY  => :old.ADDR_ATTRIBUTE_CATEGORY,
    p_old_ADD_INFORMATION13        => :old.ADD_INFORMATION13,
    p_old_ADD_INFORMATION14        => :old.ADD_INFORMATION14,
    p_old_ADD_INFORMATION15        => :old.ADD_INFORMATION15,
    p_old_ADD_INFORMATION16        => :old.ADD_INFORMATION16,
    p_old_ADD_INFORMATION17        => :old.ADD_INFORMATION17,
    p_old_ADD_INFORMATION18        => :old.ADD_INFORMATION18,
    p_old_ADD_INFORMATION19        => :old.ADD_INFORMATION19,
    p_old_ADD_INFORMATION20        => :old.ADD_INFORMATION20,
    p_old_BUSINESS_GROUP_ID        => :old.BUSINESS_GROUP_ID,
    p_old_COUNTRY                  => :old.COUNTRY,
    p_old_DATE_FROM                => :old.DATE_FROM,
    p_old_DATE_TO                  => :old.DATE_TO,
    p_old_PERSON_ID                => :old.PERSON_ID,
    p_old_POSTAL_CODE              => :old.POSTAL_CODE,
    p_old_PRIMARY_FLAG             => :old.PRIMARY_FLAG,
    p_old_PROGRAM_APPLICATION_ID   => :old.PROGRAM_APPLICATION_ID,
    p_old_PROGRAM_ID               => :old.PROGRAM_ID,
    p_old_PROGRAM_UPDATE_DATE      => :old.PROGRAM_UPDATE_DATE,
    p_old_REGION_1                 => :old.REGION_1,
    p_old_REGION_2                 => :old.REGION_2,
    p_old_REGION_3                 => :old.REGION_3,
    p_old_REQUEST_ID               => :old.REQUEST_ID,
    p_old_STYLE                    => :old.STYLE,
    p_old_TELEPHONE_NUMBER_1       => :old.TELEPHONE_NUMBER_1,
    p_old_TELEPHONE_NUMBER_2       => :old.TELEPHONE_NUMBER_2,
    p_old_TELEPHONE_NUMBER_3       => :old.TELEPHONE_NUMBER_3,
    p_old_TOWN_OR_CITY             => :old.TOWN_OR_CITY
  );
  --
  /* Legislation specific component calls */
  --
  /* Business group specific component calls */
  --
  /* Payroll specific component calls */
  --
  pay_dyn_triggers.g_dyt_mode := l_mode;
EXCEPTION
  WHEN OTHERS THEN
    hr_utility.set_location('PERADDRESSES_56U_DYT',ABS(SQLCODE));
    pay_dyn_triggers.g_dyt_mode := l_mode;
    RAISE;
  --
END;
Re: Error occured when trying to update address using API [message #273453 is a reply to message #273201] Wed, 10 October 2007 09:26 Go to previous messageGo to next message
vamsi kasina
Messages: 2107
Registered: October 2003
Location: Riyadh, Saudi Arabia
Senior Member
As it says, it is a dynamically generated trigger.
I 'm not having much idea on that. But you can check the following sql's whether they are returning data or not.
select * 
  from pay_trigger_events
 where event_id = 56;
 
select * 
  from hr_lookups
 where lookup_type in ('EVENT_TYPE','PROCESS_EVENT_TYPE')
   and lookup_code = '56';
By
Vamsi
Re: Error occured when trying to update address using API [message #273454 is a reply to message #271264] Wed, 10 October 2007 09:31 Go to previous messageGo to next message
satya.das2007
Messages: 33
Registered: February 2007
Location: India
Member
first query is returning single row but the second query is not retuning any value.

What is the use of these two queries?
Re: Error occured when trying to update address using API [message #273457 is a reply to message #273454] Wed, 10 October 2007 09:36 Go to previous messageGo to next message
vamsi kasina
Messages: 2107
Registered: October 2003
Location: Riyadh, Saudi Arabia
Senior Member
I found some code (involves the above sql's),which gives the error "HR_xxxx_INVALID_EVENT_TYPE".
You may track the code of the trigger and the package, which is being called in that.

By
Vamsi
Re: Error occured when trying to update address using API [message #273459 is a reply to message #271264] Wed, 10 October 2007 09:39 Go to previous messageGo to next message
satya.das2007
Messages: 33
Registered: February 2007
Location: India
Member
Thanks Vamsi,

I have raised an TAR / SR to Oracle for solution. Lets C.

Nice talking to you.

Regards
Satya
Re: Error occured when trying to update address using API [message #273461 is a reply to message #273459] Wed, 10 October 2007 09:53 Go to previous messageGo to next message
vamsi kasina
Messages: 2107
Registered: October 2003
Location: Riyadh, Saudi Arabia
Senior Member
If it got resolved, please post the TAR/SR number, so that it will help others.

By
Vamsi
Re: Error occured when trying to update address using API [message #273466 is a reply to message #271264] Wed, 10 October 2007 10:09 Go to previous messageGo to next message
satya.das2007
Messages: 33
Registered: February 2007
Location: India
Member
Sure but it seems to be a bug.

SR No is : 6526458.993
Re: Error occured when trying to update address using API [message #273468 is a reply to message #273466] Wed, 10 October 2007 10:18 Go to previous message
vamsi kasina
Messages: 2107
Registered: October 2003
Location: Riyadh, Saudi Arabia
Senior Member
Thanks for sharing the SR Number.

Wow! It got addressed already.
I feel it is better to provide the information (output of the sql's), which you have. That might be useful for them.

By
Vamsi
Previous Topic: Who Handles creating responsibilities in your organization?
Next Topic: Is it necessary for to define historical rates for translation
Goto Forum:
  


Current Time: Fri Dec 02 18:28:15 CST 2016

Total time taken to generate the page: 0.47306 seconds