Updating attributes in PPOMA

Hello people,
we are using SRM 5.5 and we would like to create a program to update some attributes in PPOMA_BBP.
To do this, we think to use bbp_update_attributes funtion module.
I made some tests running this function in SE37 but I could not change some attributes (WRK, for instance).
I saw this attribute is marked as SIMULATED in t77omattus table.
What it means? Anyone has the same problem? Do you know where can I find documentation about this function?
Thanks a lot!

yes. in old version we called this attribute WRK as a plant.
for eg. we dont have BP for LAG storage loation but for plant we have BP with plant.
so it could be little tricky part.
did you try to update plant for user wise or organisation wise.
br
muthu

Similar Messages

EPMA Automation - Update Attribute

I am presently using EPMA 11.1.1.3 and wanted to elicit views on the below :
Is there an automated way through which the dimension attributes can be updated during the run time. Or can the task of updating Attributes be performed only
by EPMA Administrator ?
Thanks in advance !
navpreet

I would say it is the task of an administrator to maintain the metadata.
Cheers
John
http://john-goodwin.blogspot.com/

Updating attribute columns

Hi,
we are on oracle applications 11i.
We have a requirement to create a descriptive flexfield in the items form and suppliers form to accept ids generated in another system. update would be from database end.
what is the impact of updating attribute columns in two tables: MTL_SYSTEM_ITEMS_B and po_vendors with a simple procedure, i.e without using existing Oracle APIs?
Regards

Hi,
here is why i think i need to insert a row the value set table : fnd_flex_values .
after i update the record of the table and alter attribute field with value XXX for value set segment GLOBAL_ID, I go to the application and query the record. It gives me error:
Value XXX for the flexfield segment Global ID does not exist in the value set XX_GLOBAL_ID.
this error only goes away when i insert the value XXX to the descriptive flexfield segment values list.
I defined the value set as independent. If you have another mean where i can accomplish this, I will like to know about it.
From ittoolbox forum i had the name of the package, which is fnd_flex_values_pkg. I need more details on the tables that i need to update or insert rows into and about the package; if possible.
thanks

Launch workflow in user form after updating attributes

Hello,
When I launch a workflow in my activeSync user form, attributes are not updated if there are changes for the account.
I launch the worfklow as described below:
                <Field name='viewOptions.Process'>
                    <Comments> Workflow</Comments>
                    <Expansion>
                        <s>DeleteAccounts</s>
                    </Expansion>
                </Field>Is it possible in a first time to update attributes and then to launch the workflow ?
Thanks,
Nicolas

Are the attributes changing because of changes through role assignments? I think those changes happen during check-in. (Maybe in a reprovision, too: I haven't tried.)
My instructor said he has seen times after activeSync is run that, if you edit the user, additional attribute changes finally go through. He didn't elaborate on when it happens. I've seen it, but for reasons that aren't relevant in this discussions, I haven't had to deal with it yet.
Anyway, he recommended setting viewOptions.Process to something that does an extra check-out/in (or in/out?) to handle that situation. You might want to add a check-in/out to your workflow before you do your other processing...

Updating attributes for InfoObject

I am getting below error while trying to load the master data "0MAT_PLANT" using DTP.
" There are duplicates of the data record 1 & with the key ' &' for
characteristic 0MAT_PLANT &. "
Tetted following.
1.vealidated the data in PSA, thers is no duplicate entries.
2.In the DTP monitor, I can see..
   1.Extraction DataSource 0MAT_PLANT_ATTR : Green
   2.Filter Out New Records with the Same Key : Green
   3.RSDS 0MAT_PLANT_ATTR -> IOBJ 0MAT_PLANT : Green
   4.Updating attributes for InfoObject 0MAT_PLANT : Red (falied)
I was performin the data load with only one record eventhough I m agetting this error measge Duplicates entries" , your help on this greatly appericiated..
Thanks,
Raman

Hi,
Check if it is full upload from PSA, and check how many PSA request are coming when you pull the data.
Might be in other request in PSA have duplicate entries.
When you pull the data from DTP as Full it will select all the request from PSA..
Check this..
Regards
Gopal

Update Attributes in UME

Hi
Is it possible to update attributes e.g Language in UME via security.api ?.
Thanks
Damien

Damien,
Lokesh has given good input but user.setLocale("EN"); may not work as such because method setLocale
public boolean setLocale(java.util.Locale locale).
does not accept String parameter.
I tried it following way and it worked for me.
IUserMaint user = UMFactory.getUserFactory().getMutableUser(UMFactory.getUserFactory().getUserByLogonID("userid").getUniqueID());
Locale deLocale = new Locale("de", "DE");
user.setLocale(deLocale);
user.commit();
Obviously, "userid" needs to be replaced with a real User ID.
After this, refresh the browser and all navigation for user mapped to userid will be in German. You can get more information about Locale [here|http://java.sun.com/developer/technicalArticles/J2SE/locale/].
Hope it helps,
Vishwas.

Simple question, updating attributes

Hello,
I have simple question. When I update attributes using ActiveSync. I have to submit created events in poll method (resp. processUpdates method). How does the update works, do I have to specify all the attributes or just those which are beeing updated?????
Thank you a lot for answering or leading me where to find answer.
Martin

In documenation there is:
Updating the Identity Manager Repository
When an update is received, the adapter uses the IAPI classes, notably IAPIFactory to:
* Collect the changed attributes
* Map the changes to a unique Identity Manager object.
* Update that object with the changed information
Mapping the Changes to the Identity Manager Object
Using the Active Sync event parameter configurator for the resource, IAPIFactory.getIAPI constructs an IAPI object, either IAPIUser or IAPIProcess from a map of changed attributes. If an exclusion rule (iapi_create, iapi_delete, or iapi_update) is configured for the resource, IAPIFactory checks if the account is excluded. If a non-null object is created and returned by the Factory, the adapter can modify the IAPI object (for example, by adding a logger), then submits it.
When the object is submitted, the form associated with the resource is expanded with the object view before the view is checked in. For details on forms and views, see the chapters titled Identity Manager Forms and Identity Manager Views.
In SkeletonActiveSyncResourceAdapter, this process is handled in the buildEvent and processUpdates methods.
... which looks like not all attributes have to be specified but is there any example how object userMap which is passes to event creator looks like?????
Martin

How to update attributes from OIM to AD in case of LDAPSync

Hi All,
In our scenario, we have LDAPSync configured for OIM AD Integration. OIM version is OIM 11gR2 PS1 (11.1.2.1.0.0)
It is working fine and On user creation in OIM ,RealTime user creation under specified container in AD is happening.It is SSL enabled,so password is also getting updated from OIM to AD.
But we have following conflicting scenario --
- As per our requirement we have to generate random password for User in OIM. For that we have PostProcess event handler implemented in OIM.
- We have tested LDAPSync by creating user manually through OIM console. While creating user manually, we have provided value for password attribute along with other attributes.
So, password attribute in AD will get updated for User along with all other attributes values mapped for AD from OIM.
- But, in our scenario random password is generated for User through OIM post process event handler and it will be updated again in user profile of user created manually in OIM. This password is sent to User through mail.
As this password event handler will get triggered after LDAPSnyc only, this password will not be update in AD for manually created user in OIM. So he can log into OIM with this new password but not to AD system.
He will be able to login to AD system with same User ID but with password which was set at time of manual User Creation in OIM and not with the password updated in OIM user profile by PostProcess event handler.
Is it possible to set password for user through PreProcess even handler implementation for Random Password generation. In this case also , the default OIM post process
password generator will override the PreProcess event handler.How to resolve this issue.
Also,when AD connector is in place in OIM environment we would be having change/update tasks for any attribute update to be send from OIM to AD.
How this update scenario will be implemented from OIM to AD in case of LDAPSync ?
Please provide any helpful pointer on this.
Thanks,
RPB

Password :
Increase order of calling for custom password event handler than OOTB handler.
Update:
you wanted to update custom fields?
Did you check default update tasks comes with connector?

Is it possible to update attributes in all tables in a multi entity view

Hi I have a view based on 4 entities, all of which are a 3 of which are 1 to many relationship with the 4th. The 3 additional entities have 2 or 3 attributes, Id, name, and one entity has a foreign key relating to a different table which I do not care about. The IDs are all updatable in the entity, and none of them are generated from a sequence but are inserted manually, except for the 4th (Master?) which is generated from a sequence.
I create the view and all the entities are updatable, but in the view when I go to attributes from the other tables, it says updatable never and is grayed out so I cannot change it, even though in the entities tab, it is updatable always.
So I was wondering if this was possible to do???

I do not understand really, if it is 2 different tables, it is 2 different primary keys. Why would this even happen? What does it matter if EmployeeID and DepartmentID is both 1??? It just seems that there has to be a simpler way to do this but ok.
So I go to the AppModule, Java tab and go generate Java class. The original code was
public ViewObjectImpl getObjektiCRUDView1()
return (ViewObjectImpl)findViewObject("ObjektiCRUDView1");
I then copy your code to the best of my limited knowledge and get this
public ViewObjectImpl getObjektiCRUDView1()
this.getObjektiCRUDView1().executeEmptyRowSet();
{Row yourRow = this.getObjektiCRUDView1().createRow();
this.getObjektiCRUDView1().insertRow(yourRow );
return (ViewObjectImpl)findViewObject("ObjektiCRUDView1");
On the first row the getObjektiCRUDView1() is underlined and it says missing method body or declare as abstract.
I know I did something wrong here but I have no idea what as I am not very good with Java
Also it is not a jsf page, I create a single jspx page and divided it using the panel splitter so on one side we have an adf table for updating the Objekti database table, and on the other side I have an adf form for updating the Positions table (and later on other tables, I hope to have many forms there)
Edited by: Dino2dy on Jun 10, 2010 12:02 AM

LDAP weird error on updating attributes, no error on reading

I have to modify the email addresses of only some users in the LDAP database, hence I am doing a search for all objects with the specified email address and updating it using the modifyAttribute function......
When I just read the properties the code works fine, but when I try to modify the attribute it throws me the following error
javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; remaining name 'strsdistrid=3+strsdistruserid=isdfv01,ou=autodistributionobjects'
javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; remaining name 'strsdistrid=3+strsdistruserid=isdfv01,ou=autodistributionobjects'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3013)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2934)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2740)
at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1440)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDirContext.java:255)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:172)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:161)
at javax.naming.directory.InitialDirContext.modifyAttributes(InitialDirContext.java:146)
at fullname.main(fullname.java:77)
here is the code.....
while (answer.hasMore()) {
SearchResult sr = (SearchResult)answer.next();
sr.setRelative(false);
System.out.println(">>>" + sr.getName());
String dn = sr.getName();
Attributes attrs = sr.getAttributes();
String givenName = " ";
String surName = " ";
try {
givenName = attrs.get("mail").toString();
} catch (Exception err) {
givenName = " ";
System.out.println(">>> [Email addresses] " + givenName);
try {
surName = attrs.get("document").toString();
} catch (Exception e2) {
surName = " ";
System.out.println(">>> [Object name] " + surName);
ModificationItem mods[] = new ModificationItem[1];
// Put in mail
Attribute mod0 = new BasicAttribute( "strsdistremailaddress","[email protected]");
mods[0] = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, mod0);
System.out.println("Modifications set");
ctx.modifyAttributes(sr.getName(),mods);
All help is appreciated.

Hi Timbuk,
Iam also having a similar problem as yours.
I have added groups into Active Directory, when i try to add users to groups, Iam getting the same exception.
javax.naming.NameNotFoundException: [LDAP: error code 32 - 00000525: NameErr: DSID-031A0F80, problem 2001 (NO_OBJECT), data 0, best match of:
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3057)
     at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2978)
     at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2785)
     at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1468)
     at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDirContext.java:273)
     at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:190)
     at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:179)
     at javax.naming.directory.InitialDirContext.modifyAttributes(InitialDirContext.java:165)
        at com.loadtesting.main(AddingUser.java:414)
Please let me know if you got solution for your problem. So that you can help me. Urgent
Thanks in advance.
Deebika

Update Attribute values of AR transaction.

Hi All,
We have a requirement to update the attribute of the AR transaction and have written the following code:
DECLARE
   l_msg_count               NUMBER;
   l_msg_data                VARCHAR2 (2000);
   l_return_status           VARCHAR2 (10);
   v_batch_rec               ra_batches_all%ROWTYPE;
   v_header_rec              ra_customer_trx%ROWTYPE;
   v_errors                  arp_trx_validate.message_tbl_type;
   v_lines_tbl               ar_transaction_pub.line_tbl_type;
   v_tax_lines_tbl           ar_transaction_pub.line_tbl_type;
   v_freight_lines_tbl       ar_transaction_pub.line_tbl_type;
   v_salescredit_lines_tbl   ar_transaction_pub.salescredit_tbl_type;
   v_dist_tbl                ar_transaction_pub.dist_tbl_type;
   v_commitment_rec          arp_process_commitment.commitment_rec_type;
   v_date                    DATE;
   out_message               VARCHAR2 (4000);
   l_msg_index_out           INTEGER;
   cursor c_trx is
   select * from ra_customer_trx_all
   where customer_trx_id = 272499;--234915;
BEGIN
   fnd_msg_pub.initialize;
   fnd_client_info.set_org_context ('328');
   fnd_global.apps_initialize (37850,50261,222, 0);
   v_date := SYSDATE - 30;--This must be a date in the open gl period
   for i in c_trx
   loop
    v_header_rec.interface_header_attribute8:= i.interface_header_attribute8;
    v_header_rec.interface_header_context:= i.interface_header_context;
    v_header_rec.default_ussgl_trx_code_context:= i.default_ussgl_trx_code_context;
    v_header_rec.interface_header_attribute10:= i.interface_header_attribute10;
    v_header_rec.interface_header_attribute11:= i.interface_header_attribute11;
    v_header_rec.interface_header_attribute12:= i.interface_header_attribute12;
    v_header_rec.interface_header_attribute13:= i.interface_header_attribute13;
    v_header_rec.interface_header_attribute14:= i.interface_header_attribute14;
    v_header_rec.interface_header_attribute15:= i.interface_header_attribute15;
    v_header_rec.interface_header_attribute9:= i.interface_header_attribute9;
    v_header_rec.default_ussgl_transaction_code:= i.default_ussgl_transaction_code;
    v_header_rec.recurred_from_trx_number:= i.recurred_from_trx_number;
    v_header_rec.attribute11:= i.attribute11;
    v_header_rec.attribute12:= i.attribute12;
    v_header_rec.attribute13:= i.attribute13;
    v_header_rec.attribute14:= i.attribute14;
    v_header_rec.attribute15:= i.attribute15;
    v_header_rec.interface_header_attribute1:= i.interface_header_attribute1;
    v_header_rec.interface_header_attribute2:= i.interface_header_attribute2;
    v_header_rec.interface_header_attribute3:= i.interface_header_attribute3;
    v_header_rec.interface_header_attribute4:= i.interface_header_attribute4;
    v_header_rec.interface_header_attribute5:= i.interface_header_attribute5;
    v_header_rec.interface_header_attribute6:= i.interface_header_attribute6;
    v_header_rec.attribute_category:= i.attribute_category;
    v_header_rec.attribute1:= i.attribute1;
    v_header_rec.attribute2:= 'NEW';
    v_header_rec.attribute3:= i.attribute3;
    v_header_rec.attribute4:= i.attribute4;
    v_header_rec.attribute5:= i.attribute5;
    v_header_rec.attribute6:= i.attribute6;
    v_header_rec.attribute7:= i.attribute7;
    v_header_rec.attribute8:= i.attribute8;
    v_header_rec.attribute9:= i.attribute9;
    v_header_rec.attribute10:= i.attribute10;
    v_header_rec.customer_trx_id:= i.customer_trx_id;
    v_header_rec.trx_number:= i.trx_number;
    v_header_rec.paying_site_use_id:= i.paying_site_use_id;
    v_header_rec.bill_to_customer_id:= i.bill_to_customer_id;
    v_header_rec.cust_trx_type_id:= i.cust_trx_type_id;
    v_header_rec.reversed_cash_receipt_id:= i.reversed_cash_receipt_id;
    v_header_rec.agreement_id:= i.agreement_id;
    v_header_rec.batch_id:= i.batch_id;
    v_header_rec.status_trx:= i.status_trx;
    v_header_rec.doc_sequence_id:= i.doc_sequence_id;
    v_header_rec.doc_sequence_value:= i.doc_sequence_value;
    v_header_rec.paying_customer_id:= i.paying_customer_id;
    v_header_rec.related_batch_source_id:= i.related_batch_source_id;
    v_header_rec.default_tax_exempt_flag:= i.default_tax_exempt_flag;
    v_header_rec.created_from:= i.created_from;
    v_header_rec.org_id:= i.org_id;
    v_header_rec.request_id:= i.request_id;
    v_header_rec.program_application_id:= i.program_application_id;
    v_header_rec.program_id:= i.program_id;
    v_header_rec.program_update_date:= i.program_update_date;
    v_header_rec.finance_charges:= i.finance_charges;
    v_header_rec.complete_flag:= i.complete_flag;
    v_header_rec.posting_control_id:= i.posting_control_id;
    v_header_rec.bill_to_address_id:= i.bill_to_address_id;
    v_header_rec.ra_post_loop_number:= i.ra_post_loop_number;
    v_header_rec.ship_to_address_id:= i.ship_to_address_id;
    v_header_rec.credit_method_for_rules:= i.credit_method_for_rules;
    v_header_rec.credit_method_for_installments:= i.credit_method_for_installments;
    v_header_rec.receipt_method_id:= i.receipt_method_id;
    v_header_rec.related_customer_trx_id:= i.related_customer_trx_id;
    v_header_rec.invoicing_rule_id:= i.invoicing_rule_id;
    v_header_rec.ship_via:= i.ship_via;
    v_header_rec.ship_date_actual:= i.ship_date_actual;
    v_header_rec.waybill_number:= i.waybill_number;
    v_header_rec.fob_point:= i.fob_point;
    v_header_rec.customer_bank_account_id:= i.customer_bank_account_id;
--    v_header_rec.printing_option:= i.printing_option;
    v_header_rec.printing_count:= i.printing_count;
    v_header_rec.printing_pending:= i.printing_pending;
    v_header_rec.purchase_order:= i.purchase_order;
    v_header_rec.purchase_order_revision:= i.purchase_order_revision;
    v_header_rec.purchase_order_date:= i.purchase_order_date;
    v_header_rec.customer_reference:= i.customer_reference;
    v_header_rec.customer_reference_date:= i.customer_reference_date;
    v_header_rec.comments:= i.comments;
    v_header_rec.internal_notes:= i.internal_notes;
    v_header_rec.exchange_rate_type:= i.exchange_rate_type;
    v_header_rec.exchange_date:= i.exchange_date;
    v_header_rec.exchange_rate:= i.exchange_rate;
    v_header_rec.territory_id:= i.territory_id;
    v_header_rec.invoice_currency_code:= i.invoice_currency_code;
    v_header_rec.initial_customer_trx_id:= i.initial_customer_trx_id;
    v_header_rec.end_date_commitment:= i.end_date_commitment;
    v_header_rec.start_date_commitment:= i.start_date_commitment;
    v_header_rec.last_printed_sequence_num:= i.last_printed_sequence_num;
    v_header_rec.orig_system_batch_name:= i.orig_system_batch_name;
    v_header_rec.post_request_id:= i.post_request_id;
    v_header_rec.last_update_date:= i.last_update_date;
    v_header_rec.last_updated_by:= i.last_updated_by;
    v_header_rec.creation_date:= i.creation_date;
    v_header_rec.created_by:= i.created_by;
    v_header_rec.last_update_login:= i.last_update_login;
    v_header_rec.trx_date:= i.trx_date;
    v_header_rec.set_of_books_id:= i.set_of_books_id;
    v_header_rec.bill_to_contact_id:= i.bill_to_contact_id;
    v_header_rec.batch_source_id:= i.batch_source_id;
    v_header_rec.reason_code:= i.reason_code;
    v_header_rec.sold_to_customer_id:= i.sold_to_customer_id;
    v_header_rec.sold_to_contact_id:= i.sold_to_contact_id;
    v_header_rec.sold_to_site_use_id:= i.sold_to_site_use_id;
    v_header_rec.bill_to_site_use_id:= i.bill_to_site_use_id;
    v_header_rec.ship_to_customer_id:= i.ship_to_customer_id;
    v_header_rec.ship_to_contact_id:= i.ship_to_contact_id;
    v_header_rec.ship_to_site_use_id:= i.ship_to_site_use_id;
    v_header_rec.shipment_id:= i.shipment_id;
    v_header_rec.remit_to_address_id:= i.remit_to_address_id;
    v_header_rec.term_id:= i.term_id;
    v_header_rec.term_due_date:= i.term_due_date;
    v_header_rec.previous_customer_trx_id:= i.previous_customer_trx_id;
    v_header_rec.primary_salesrep_id:= i.primary_salesrep_id;
    v_header_rec.printing_original_date:= i.printing_original_date;
    v_header_rec.printing_last_printed:= i.printing_last_printed;
    v_header_rec.global_attribute1:= i.global_attribute1;
    v_header_rec.global_attribute2:= i.global_attribute2;
    v_header_rec.global_attribute3:= i.global_attribute3;
    v_header_rec.global_attribute4:= i.global_attribute4;
    v_header_rec.global_attribute5:= i.global_attribute5;
    v_header_rec.global_attribute6:= i.global_attribute6;
    v_header_rec.global_attribute7:= i.global_attribute7;
    v_header_rec.global_attribute8:= i.global_attribute8;
    v_header_rec.global_attribute9:= i.global_attribute9;
    v_header_rec.global_attribute10:= i.global_attribute10;
    v_header_rec.global_attribute11:= i.global_attribute11;
    v_header_rec.global_attribute12:= i.global_attribute12;
    v_header_rec.global_attribute13:= i.global_attribute13;
    v_header_rec.global_attribute14:= i.global_attribute14;
    v_header_rec.global_attribute15:= i.global_attribute15;
    v_header_rec.global_attribute16:= i.global_attribute16;
    v_header_rec.global_attribute17:= i.global_attribute17;
    v_header_rec.global_attribute18:= i.global_attribute18;
    v_header_rec.global_attribute19:= i.global_attribute19;
    v_header_rec.global_attribute20:= i.global_attribute20;
    v_header_rec.global_attribute_category:= i.global_attribute_category;
    v_header_rec.wh_update_date:= i.wh_update_date;
    v_header_rec.edi_processed_flag:= i.edi_processed_flag;
    v_header_rec.edi_processed_status:= i.edi_processed_status;
    v_header_rec.global_attribute21:= i.global_attribute21;
    v_header_rec.global_attribute22:= i.global_attribute22;
    v_header_rec.global_attribute23:= i.global_attribute23;
    v_header_rec.global_attribute24:= i.global_attribute24;
    v_header_rec.global_attribute25:= i.global_attribute25;
    v_header_rec.global_attribute26:= i.global_attribute26;
    v_header_rec.global_attribute27:= i.global_attribute27;
    v_header_rec.global_attribute28:= i.global_attribute28;
    v_header_rec.global_attribute29:= i.global_attribute29;
    v_header_rec.global_attribute30:= i.global_attribute30;
    v_header_rec.payment_server_order_num:= i.payment_server_order_num;
    v_header_rec.approval_code:= i.approval_code;
    v_header_rec.address_verification_code:= i.address_verification_code;
    v_header_rec.old_trx_number:= i.old_trx_number;
    v_header_rec.br_amount:= i.br_amount;
    v_header_rec.br_unpaid_flag:= i.br_unpaid_flag;
    v_header_rec.br_on_hold_flag:= i.br_on_hold_flag;
    v_header_rec.drawee_id:= i.drawee_id;
    v_header_rec.drawee_contact_id:= i.drawee_contact_id;
    v_header_rec.drawee_site_use_id:= i.drawee_site_use_id;
    v_header_rec.drawee_bank_account_id:= i.drawee_bank_account_id;
    v_header_rec.remittance_bank_account_id:= i.remittance_bank_account_id;
    v_header_rec.override_remit_account_flag:= i.override_remit_account_flag;
    v_header_rec.special_instructions:= i.special_instructions;
    v_header_rec.remittance_batch_id:= i.remittance_batch_id;
    v_header_rec.prepayment_flag:= i.prepayment_flag;
    v_header_rec.ct_reference:= i.ct_reference;
    v_header_rec.contract_id:= i.contract_id;
    v_header_rec.bill_template_id:= i.bill_template_id;
    v_header_rec.cc_error_flag:= i.cc_error_flag;
    v_header_rec.cc_error_code:= i.cc_error_code;
    v_header_rec.cc_error_text:= i.cc_error_text;
   dbms_output.put_line(v_header_rec.term_id);
   end loop;
   ar_transaction_pub.update_transaction
                         (p_api_name                   => 'AR_TRANSACTION_PUB',
                          p_api_version                => 1.0,
                          p_init_msg_list              => fnd_api.g_true,
                          p_commit                     => fnd_api.g_true,
                          p_validation_level           => fnd_api.g_valid_level_full,
                          p_batch_rec                  => v_batch_rec,
                          p_header_rec                 => v_header_rec,
                          p_receivable_gl_date         => v_date,
                          p_commitment_rec             => v_commitment_rec,
                          p_lines_tbl                  => v_lines_tbl,
                          p_tax_lines_tbl              => v_tax_lines_tbl,
                          p_freight_lines_tbl          => v_freight_lines_tbl,
                          p_salescredit_lines_tbl      => v_salescredit_lines_tbl,
                          p_dist_tbl                   => v_dist_tbl,
                          p_return_status              => l_return_status,
                          p_msg_count                  => l_msg_count,
                          p_msg_data                   => l_msg_data,
                          p_errors                     => v_errors,
                          p_recalc_tax_flag            => fnd_api.g_true,
                          p_rerun_autoacc_flag         => fnd_api.g_true,
                          p_backout_sc_flag            => fnd_api.g_true,
                          p_backout_dist_flag          => fnd_api.g_true
   IF (fnd_msg_pub.count_msg > 0)
   THEN
      FOR i IN 1 .. fnd_msg_pub.count_msg
      LOOP
         fnd_msg_pub.get (p_msg_index          => i,
                          p_encoded            => 'F',
                          p_data               => out_message,
                          p_msg_index_out      => l_msg_index_out
         DBMS_OUTPUT.put_line ('l_msg_data :' || out_message);
      END LOOP;
   END IF;
END;However getting the below error:
l_msg_data :Invalid payment terms id. (TERM_ID: &INVALID_VALUE)
l_msg_data :Invalid Transaction Status &INVALID_VALUE .
l_msg_data :Validation error(s) occurred. Rolling back and setting status to ERROR
This was working fine sometimes back. Can anyone point the right direction. I am able to update the attribute value fron the front end.
Thanks,
Subhasish

Hi All,
Any thoughts on this ??
Regards,
Subhasish

Updated attribute not showing up in the Front End

Hi,
I have to update an attribute column based on some conditions.
Even though I have updated, the updated value is not showing up in the front end
Moreover if I go to Diagnostics-> Examine and then query the attribute value I can see the updated Result
What can be the reason...
Please Advise
Rahul

Sounds like the Statement is not committed. Maybe you should add a
COMMIT;
at the end of your query.

API pa_project_pub.UPDATE_TASK is not updating attributes

Hi All,
I am facing a strange problem in calling API pa_project_pub.UPDATE_TASK. It updates fields like task name, description etc, but it doesn;t updates attribute8, or any attribute fields. The DFF which is on this table pa_tasks, is context basis, and we are updating it for 'Shipping' context, and I am giving this value means 'Shipping' in attribute_category fields, becasue in table pa_tasks, it stores this value in attribute_category only.
Below is the code, i m using... Please let me know if I am missing any parameter, becasue this API is giving SUCCESS, so I dont know why the values are not getting updated.
pa_project_pub.UPDATE_TASK(p_api_version_number => 1.0,
p_commit => FND_API.G_TRUE,
p_init_msg_list => FND_API.G_TRUE,
p_msg_count => l_msg_count,
p_msg_data => l_msg_data,
p_return_status => l_return_status,
p_pm_product_code => 'SERVICE REQUEST',
p_pa_project_id => '18090',
p_pm_task_reference => '90000',
p_pa_task_id => p_task_id,
p_service_type_code => 'NORDIC_EMLP_PROJECT',
p_attribute_category => 'Shipping',
p_attribute8 => 'test1',
p_out_pa_task_id => p_out_pa_task_id,
p_out_pm_task_reference => p_out_pm_task_reference,
p_update_task_structure => 'Y');
Thanks and Regards,
Nidhi

Are you using a vision instance? Which release are you in?
If the issue is yet to be resolved after checking and compiing the invalid objects, as suggested by Hussein, then you can do the following:
- Check the responsibility ID of "Projects, Vision Operations (USA)", the one you are using. In vision instances the responsibility ID 20420 (as provided in apps_initialize) is little odd. In 11.5.10.x and R12 vision instances the responsibility ID is normally 56486. Though it can be different in your instance.
- If the responsiblity ID is correct OR you are using a different responsibility then check whether responsibility Menu is having "Open Integration Toolkit Funtions Menu" submenu (without any prompt) assigned and active (grants checkbox). Please also check within this submenu whether "Activity Management Gateway:Add Task" function is assigned and active (grants checkbox)
- For seeded Project responsibilities the submenu & underlying function is seeded, but if you using a non project responsibility for creating project/ task etc then that responsibility should have "Open Integration Toolkit Funtions Menu" submenu (without any prompt) assigned and active.
Thanks
Supro

Update attribute value in xml db in Oracle 10g

I have a table with XML blob data
The root element is invoice with an element billInfo and attribute type0
I'm trying to update the attribute value using the following sql but it is not working.
the sql goes to sucess but the value is not updated.
Looking for a solution and I appreciate your help
update sc.table_name
set xml_cb= updateXML(xml_cb,'/invoice/billInfo/@type0','A')
where id = 1 succeeded.
select id,
extractValue(xml_cb,'/invoice/billInfo/@type0') type_val
from sc.table_name
where id =1;
ID TYPE_VAL
1 K

What database version are you using?
could you show us the outcome of:
SQL> select dbms_metadata.get_ddl('TABLE','TABLE_NAME','SC') from dual;
and/or a
SQL> describe SC.TABLE_NAME

API for Updating Attribute in CZ

Hi All,
Could you please suggest me any Standard API to update the Attribute Value in cz_config_ext_attributes.
Thank you,
Aush

Could you please suggest me any Standard API to update the Attribute Value in cz_config_ext_attributes.I do not see any reference on MOS that shows what API can be used to update this table.
Have you reviewed the documentation? -- http://www.oracle.com/technetwork/documentation/applications-167706.html
You may also review iREP and eTRM websites.
http://irep.oracle.com/index.html
http://etrm.oracle.com/
Thanks,
Hussein

Updating attributes in PPOMA

Similar Messages

Maybe you are looking for