Updating attribute associations
I have an standard ragged sparse dimension associated with and attribute ragged dimension. They are already built.I have a text file with two columns, the first for the member of the standard dimension and the second for the attribute. The association is made at level 0 of the standard dimension.When I try to load the associations file I get this message:Dimension build failed. There are many possible causes (for example, problem allocating memory). Check the server log file to locate the error that caused the failure.The server has plenty of RAM. The standard dimension has more than 20000 members and I made the load on the server.Can anybody help me? I'm in a hurry
.. And did you check the log? It usually gives a pretty good idea on what the problem is.
Similar Messages
-
Getting this error from DirSync
Unable to update this object because the following attributes associated with this object have values that may already be associated with another object in your local directory services: [UserPrincipalName
[email protected];]. Correct or remove the duplicate values in your local directory. Please refer to
http://support.microsoft.com/kb/2647098 for more information on identifying objects with duplicate attribute values.
Quick eyeball and couldn't see the cause in the user account so used the script here:
http://gallery.technet.microsoft.com/office/Fix-Duplicate-User-d92215ef
And got these outputs:
PS C:\Windows\System32\WindowsPowerShell\v1.0> Export-OSCADUserPrincipalName -UserPrincipalName "[email protected]" -Path .\outputs.csv
WARNING: Cannot find objects with specified duplicate user principal name
[email protected]
Found 0 user(s) with duplicate user principal name.
Where to from here?
Richard PHi,
Did you talk about the Microsoft Azure Active Directory Sync tool ?
If yes, this issue occurs if one or more of the following conditions are true:
An object in the on-premises Active Directory has an SMTP address that's the same as the SMTP address of the object that's reporting the problem.
An object in the on-premises Active Directory has a mail attribute that's identical to the object that's reporting the problem.
An object already exists in your organizational account and has the same SMTP address or mail attribute as the object in the on-premises Active Directory
More detail information, please refer to:
http://support.microsoft.com/kb/2520976/en-us
[Troubleshooting] Unable to update this object because the following attributes associated with this object
http://blogs.technet.com/b/aadsyncsupport/archive/2014/05/20/troubleshooting-unable-to-update-this-object-because-the-following-attributes-associated-with-this-object.aspx
Regards.
Vivian Wang -
ASO update of attribute associations causes Data to be "converted"?
Has anyone seen the issue in 11.1.2.3(.506) where associating attributes with a dimension causes Essbase to reorganize the data (it is referred to as convert)?
e.g.
import database app.db dimensions connect as user identified by password using server rules_file 'DimFuel' on error write to '/essapp/subject/sos/logs/sosp04_dims.build_dim_sosp04_sosp04_dimopen.20150429011053.err':
OK/INFO - 1270086 - Restructuring converted [5.72103e+08] input cells and removed [0] input cells.
OK/INFO - 1270087 - Restructuring converted [32] and removed [0] aggregate views.
OK/INFO - 1007067 - Total Restructure Elapsed Time : [1944.88] seconds.
Previoiusly this process ran in 3 seconds in 11.1.2.2(.100)I agree with everything that Tim has said. Let me elaborate some more that might be helpful:
The fact that agg views are not based on query tracking makes no difference in the analysis. Query tracking only affects WHICH views are selected. Once views are selected by whatever means they are handled in the same way. Is there a reason you think otherwise?
Let's divide the question into two parts:
1. What is a restructure and Why is a restructure needed?
2. Why must the agg views be converted
But first realize there are two possibilities concerning WHICH agg views actually exist:
a. All views might be on the primary hierarchy only. (You told Essbase to consider alternate hierarchies when creating aggregates) - let's call that the Agg_Primary option
b. Views might be based on both primary and alternate (which includes attribute) hierarchies - let's call that the Agg_Any option
All of this is is discussed in my Chapter "How ASO Works and How to Design for Performance" in the book "Developing Essbase Applications" edited by Cameron Lackpour. You will also find a discussion of the bitmap in the section of the DBAG entitled "An aggregate storage database outline cannot exceed 64 bits per dimension" (Essbase Administrators Guide Release 11.1.2.1 Chapter 62 page 934). and in a presentation I made at Kscope 20120 which you can find on ODTUG.com
1. Why a restructure? As Tim says the outline has changed and anytime the number of levels per hierarchy or the width of the hierarchy changes then the coding system used for the data changes. OK what do i mean by this? The binary system by which each piece of data in your cube is described is called the "BitMap". In actuality, this bitmap only reflects the data's position in the primary hierarchy for each dimension. The primary hierarchy for a specific dimension is not necessarily the first hierarchy seen in your outline. It is the "widest" hierarchy - the one requiring the greatest number of bits to represent all Level 0 (L0) members found in that hierarchy and each L0's full ancestry within that hierarchy.
If you read the references above you will see that the number of bits used to determine the "widest" hierarchy is a function of the number of levels and the size of the largest "family" in a hierarchy. A hierarchy of 5 levels where the largest family has 17 members will require 3 bits more than a hierarchy of 5 levels with 4 members in the family (17 requires 5 bits and 4 requires 2 bits). So you can see that any time you add more members you could be causing the size of the largest family to exceed a power of 2 boundary.
Additionally, if the primary hierarchy is NOT all inclusive - i.e. it contains all L0 members for that dimension then you have to add a sufficient number of bits to enumerate the hierarchies.
So, in summary changes to the width or the height (number of levels) will require a restructure forcing the the identifying bits on every piece of data to be updated.
In the case the OP mentions where the ONLY changes are to add attribute associations you normally would NOT expect to see a change in the bitmap due to the number of bits required. This is because attribute dimensions can never have new unique L0 members (you can not associate to something that does not exist). If you go thru the math (and realize that the bitmap for an attribute dimension does NOT have consider size of the L0 families of the primary hierarchy - or whichever Level the association is based on) you will find that there is no possible attribute dimension that can require more bits than the primary hierarchy. UNLESS you have been sloppy and you have a primary dimension with x L0 members and a very large secondary hierarchy with x-n members UNIQUE L0 members (i.e. L0 members not appearing in the primary hierarchy).
So the answer is to inspect the statistics tab before and after your addition of member associations.
Note - (and this does NOT pertain in the OP's Case) a similar situation exists if all secondary hierarchies contain ONLY members that already exist within the primary hierarchy. However, remember that the FIRST hierarchy in your outline is not necessarily the primary hierarchy. Most people however consider the first hierarchy as the de-facto primary. If one is in a hurry and adds the member to that first hierarchy but does not add it to ALL of the alternate hierarchies (one of which is the true primary), then bits will have to be added to each piece of data to enumerate the hierarchies - thus triggering a restructure.
Finally, I am relying on the OP's description of the conditions where it was stated that ONLY associations were added and that no upper level attribute members created. If upper level attribute members are added it is possible that the number of levels for the attribute dimension is changed. In this case a mini restructure would be required - one that would not change the bitmap on every data item but a change to the mapping table that relates alternate hierarchies to the primary hierarchy. Note the existence of this table and its exact structure is not acknowledged by Oracle - I (Dan Pressman) have postulated it as one possible implementation of the observed functionality.
2. Aggregate View Conversion: Each data item is tagged not only with a bitmap indicating its position within each primary hierarchy but with a "View ID". This is the number that is seen in the ASO version of the .CSC file created whenever the view definition is saved. The input data is always identified by a View ID of 0. The view ID of other views is a function of the number of levels and the bits required therefore of ALL hierarchies of ALL dimensions. Therefore any restructure will require that the View IDs of all aggregate views be translated (or converted) from the old scheme to the new scheme. Note that this is purely a translation and no aggregation is required.
Please excuse me if I post this now and add some more later on this second question - actually let me know if anyone has actually read this far and is interested.
Please note in the above whenever i have said "Each data item" I am referring to the situation where no dimension has been tagged as the "compression" dimension. If a compression dimension has been used then replace the phrase "Each data item" with the phrase "each data bundle". I will leave it to the reader to find the section of the DBAG that describes compression and data bundles. -
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.
MartinIn 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 -
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 !
navpreetI would say it is the task of an administrator to maintain the metadata.
Cheers
John
http://john-goodwin.blogspot.com/ -
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?
RegardsHi,
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,
NicolasAre 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 in LDAP during a disable
I am having trouble with a disable workflow for an LDAP resource. I need to modify an attribute in LDAP when performing the disable.
So, I have a modified disable user form that adds a "reason" from a textbox and also sets the date of the disble.
The account is being disabled in LDAP, but the attributes "reason" and "date" are not being pushed.
I am looking for the specific order in which I should call workflow to accomplish this task.
Should I:
checkout a userview
modifiy attributes
checkin userview
checkout disable view
checkin disable view
reprovision???
notification
Thanks for your help in advance.
C.The reason they aren't being pushed is because they are not attributes associated with the Disable View.
You can extend the view to include these attributes and then the disable form can include reference these as fields as
resourceAccounts.currentResourceAccounts[ResourceTypeName].attribute.
The view can be extended globally for all all resources of a specified type (e.g. LDAP 1, LDAP2) or for a specific resource.
The Deployment Guide has a chapter on Views and how to extend them. Refer there first, and if you have any followup questions post them here. -
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,
RamanHi,
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 -
Hi
Is it possible to update attributes e.g Language in UME via security.api ?.
Thanks
DamienDamien,
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. -
App creation wizard fails to recognize Attribute association
Hi friends,
The application creation wizard is broken as it does not recognize the attribute association with the base dimension.
Getting a message - Attribute dimension is associated with 0 base dimensions.It should be associated with one and only one base dimension.
Please advise.
EPMA 11.1
SQL 2005 SP2
Windows 2003 ServerHi,
Is the message :- Error : Attribute dimension "..." is associated with 0 base dimensions or has 0 associations to the same base dimension. It should be associated exactly once with only one base dimension.
If it is you have not created an association between the attribute dimension and the dimension you want to apply it to.
Right click over your dimension, select "Create Association", select "New Property" and give it a property name.
Now in your member properties you should be able to able to select the different attribute members, it should also validate.
Cheers
John
http://john-goodwin.blogspot.com/ -
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,
RPBPassword :
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,
SubhasishHi All,
Any thoughts on this ??
Regards,
Subhasish
Maybe you are looking for
-
How do I remove the computer I don't own anymore from iTunes Match?
-
Cannot connect to AirPort Express after setting it up in AirPort Utility
I have two PCs: one has a Linksys WMP54G wireless card to connect to my AirPort Express which is connected to a wired Linksys ethernet router; the other has an ethernet card which is also connected to the Linksys router. My cable modem is plugged int
-
How to pass byte array / binary data to a webservice as parameter in osb
i have a webservice that has a byte array input parameter. i tried to use this WS in a message flow via service-callout. the problem i encountered is the following: since webservice call by using service-callout requires you to use an xml input as pa
-
Process Order detail scheduling picking the std values from Phase.
I'm working on an Implementation scenario, where the Master Recipe contains only one Operation and one phase. After the Process order is created the basic start and End dates remain same. I did check the formula in the resource(on testing its working
-
Enhancement Request: Actions for JAVA Sources (compile to CLASS)
Hi All, I would like to change my JAVA Source in the DATABASE and compile it again. At the moment I can see only the code but have no actions to compile and generate it to classes. Is this planned for a future release? AS a LAYOUT idea ... if classes