Issues Transporting Infoobject - No Compounding or Attributes Mapping
I created a custom compounded infoobject with Master Data. I also added some attributes to it. All attributes are Active in DEV and QA. When I transport the infoobject, the Infoobject gets transported "successfully", but none of the attributes and compounding elements mappings get transported. So I end up with a InfoObject with no attributes and no compounding Infoobjects. Any ideas?
I am suspecting this is a Basis issue because this should be a pretty simple transport. Any help would be appreciated.
INFOOBJECT DETAILS:
GENERAL -
CHAR: 10
MASTER DATA -
Application Component: N/A
Infoarea: ZIA_MASTER
ATTRIBUTES -
0SALES_GRP, 0SALES_OFF, 0SALES_DIST, 0ROUTE, 0CUST_HIE01, 0CUST_HIE02
COMPOUNDING -
0DIVISION, 0DISTR_CHAN, 0SALESORG
Yes. Al InfoObjects are present and active in QA already.
I should probably add that the QA system was recently refreshed from PRD. I am mentioning this because I had some issues transporting a datasource until I fixed the System Mappings through RSA1 >TOOLS.
The Basis guy says that I should just collect all InfoObjects into a transport and move them, but DEV and QA are not necessarily in synch and even though I could double check the InfoObjects involved, I wouldn't want this to be the norm. The attributes and compounding objects exist in QA and I shouldn't have to include anything else in the transport but my newly created InfoObject. Am I correct?
Is there a Basis set up that would prevent the Attribute SID table from being generated?
Similar Messages
-
Document attribute ticked on InfoObject which is nav attribute
Hi SDN Community,
We have recently enhanced a query, by removing a natural characteristic Cost Centre Category ZCOBCAT that exists in an infocube, and replaced this with a characteristic which is a navigational attribute - CC Func Code ZCCFUNCCD.
eg. characteristic value with was CC11 is now 11 with this change
On both these characteristics, in the infoObject properties, the "Document attribute" checkbox is ticked.
However, we find that when storing commentary functionality, the comments are applicable against the whole infoObject ZCCFUNCCD. Eg. If the variable input parameters are 11, the comments, are retrieved against 11, and every other value against the ZCCFUNCCD characteristic.
Is it such that navigable attributes enabled against multiproviders will not allow the "Document attribute" against the infoobject to work?
Or is it such i have to enable some other parameter against the Multiprovider or infocube that i have overlooked.
Thank you for your help in advance.
SimonHi Karthik, Gattu,
Thank you both for your answers.
As you have indicated, i have verified this:
1) the "Attribute Only" in the Miscallaneous area in the General tab of the infoObject is unticked
2) the "Characteristic is a document attribu" in the Miscallaneous area in the General tab of the infoObject is TICKED as this is what allows storing of documents against the infoObject, and is ticked in the original InfoObject. Are we saying here this should be unticked?
3) ZCCFUNCCD is flagged as a Navigational Attribute in all InfoProviders
4) I have also verified that the Multiprovider has all the assignment correctly ticked for the ZCCFUNCCD is ticked for all the InfoProviders.
What i do find different, is that if i look at 0COSTCENTER, then the attribute ZCCFUNCCD, has a check in the column "Texts of Char." But this should not be causing any issue as this is only using the same description for the Navigational Attribute Display in the queries.
Any other suggestions would be most helpful thanks.
Simon -
Hi,
I think it is the later case, that is, the current object is being altered
by SetValue. Maybe you can trace the action by creating a DomainClass from
TextNullable and run it in debug.
Regards,
Peter Sham.
-----Original Message-----
From: Dimitar Gospodinov [SMTP:[email protected]]
Sent: Tuesday, March 23, 1999 3:01 PM
To: Forte Users Mail List
Subject: Attributes mapping
Does anyone know what mechanism Forte uses when performs an
attribute
mapping in the window classes.
For example if we have a DataField widget named MyDataField that
maps to
TextData. Let assume also that you have created an instance of the
TextData class that is referenced by the MyDataField variable.
Then the question is what will happen when you change the value in
the
DataField?
A new object will be created or the current object will be altered
by
invoking the method SetValue?
Regards,
Dimitar Gospodinov
Dimitar Gospodinov
Consultant
International Business Corporation
e-mail: [email protected] << File: Card for Dimitar Gospodinov >>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>Try to use rework warehouse as a location for rework and if you want it recorded in a specific/certain GL, you must define it in COA firsts. using good issue and good receipts and do not forget to record PO no. in the remarks (comments field). So, when rework happens, receipt it in the rework warehouse using good receipts and issuing it from production warehouse and vice versa.
BTw, what type of company you are currently facing ? Is it assembly type ? steel manufacturing or what ? You must also provide info whether you use backflush or manual.
Rgds, -
UIXInclude getAttribute Illegal access of the include attribute map out
Using JDeveloper 11.1.1.6.0
I've been digging into the reason why I've been getting this in my logs. At first, I thought it was because of a declarative component, but after further digging, it was actually the region which I'm using inside a declarative region's facet.
<UIXInclude> <getAttribute> Illegal access of the include attribute map outside of the include context
Searching google only gets me to this link:
[ Oracle® Fusion Middleware Error Messages Reference|http://docs.oracle.com/cd/E16162_01/core.1112/e22506/chapter_adf_faces_messages.htm]
Has anyone encountered this same log? If you have, can you share what is causing it?
Thanks.
-MarvinFound the issue.
Too bad I had to realize it the hard way. When the declarative component is trying to point to an attribute that doesn't exist, then you get this message in your log. Feel bad for the af:region for getting blamed... (but hey the documentation said contact support so that didn't help as well).
Killed the unneeded and anonymous attribute element and everything is back to normal.
-Marvin -
TopLink : attribute-mapping direct-xml-type-mapping
hi
Using TopLink Workbench 10g Release 3 (10.1.3.0.0) Build 060118 it is possible to configure a "Direct to XML Type" mapping.
see http://www.oracle.com/technology/products/ias/toplink/doc/1013/main/_html/relmapun004.htm#CHDFIFEF
In the TopLink map this results in a
<opm:attribute-mapping xsi:type="toplink:direct-xml-type-mapping">Is there a way to configure this kind of attribute mapping using JDeveloper?
thanks
Jan VerveckenHi Paul,
The problem you're going to hit trying to do this with a TransformationMapping in 904 (as in my other post) is that during the UnitOfWork commit, when TopLink is checking for changes a .equals will end up being called on an XMLType instance which will throw a NullPointerException (in oracle.sql.Datum I think).
One way to work around this (depending on the requirements for your app) is to set the isMutable flag on the TransformationMapping to false. This flag indicates that the value in the object's attribute isn't going to be changed, so we don't bother trying to check to see if it's changed. This will allow you to do reads, inserts and deletes with no problems.
The downside is that if you need to be able to change the XML content in your objects model and do an update of the row, TopLink will never detect a change and never issue an update of the XMLType field.
Incidentilly, if you happen to hit the same issue you had with the DirectToXMLTypeMapping where you were getting back an instance of java.sql.Opaque instead of the expected oracle.xdb.XMLType from JDBC, you should be able to handle that case in your AttributeTransformer by doing
XMLType myXML = XMLType.createXML(myOpaque)
Document = myXML.getDocument();
Hope this helps
Matt MacIvor -
Hi,
We need to have some values in AP_INVOICES_ALL in some DFF ( For example Attribute10 ) for invoices we import via expense express. When we update attribute10 of ap_expense_report_headers_all after import i dont see it in the ap_invoices_all table.
What is the mapping of the ap_invoices_all attributes to the ap_expense_report_headers_all attributes.
Please help.
thanks
RamakrishnaHi,
The Attribute Mapping must be exactly matching between AP & Iexp.
For example, if you are having a DFF in iExpense called DFF1 (Attribute12-Expense Headers), then you need to create a Attribute in AP Invoice Headers with the same Attribute Number 12.
If you are creating in Expenses Report Lines, the create in AP Invoice Lines category. Pls remember that Attribute No. must be same. If it is done, then data will move exactly from iExpense to AP when Expense Report Export program is run.
The DFF Names need not be same.
Regards,
guru -
I've encountered an attribute mapping problem when using the Java OracleXMLQuery class in XSU (Oracle XML Developer's Kit for PL/SQL on Windows NT - 9i 9.2.0.1.0). As an example, take a look at the following object type containing one field whose name is prefaced with "@". This should cause XSU to map the field as an attribute rather than an element:
create or replace type testtype_t as object
"@test_attribute" varchar2(20),
test_element varchar2(30)
Here's the query passed to OracleXMLQuery:
select testtype_t('abc', 'def') "TEST1", testtype_t('ghi', 'jkl') "TEST2" from dual
Here's the output of the getXMLString method:
<?xml version = '1.0'?>
<ROWSET>
<ROW num="1">
<TEST1 test_attribute="abc">
<TEST_ELEMENT>def</TEST_ELEMENT>
</TEST1>
<TEST2>
<test_attribute>ghi</test_attribute>
<TEST_ELEMENT>jkl</TEST_ELEMENT>
</TEST2>
</ROW>
</ROWSET>
Notice that the output is correct for the "TEST1" element - it contains a "test_attribute" attribute. The "TEST2" element, however, does not contain a "test_attribute" attribute. Instead, the field was output as a child element of "TEST2" called "test_attribute". To get around this, I had to create another object type as follows:
create or replace type testtype2_t as object
"@test_attribute" varchar2(20),
test_element varchar2(30)
It's format is identical to the "testtype_t" object type described above. Here's the new query passed to OracleXMLQuery:
select testtype_t('abc', 'def') "TEST1", testtype2_t('ghi', 'jkl') "TEST2" from dual
Here's the resulting output of the getXMLString method:
<?xml version = '1.0'?>
<ROWSET>
<ROW num="1">
<TEST1 test_attribute="abc">
<TEST_ELEMENT>def</TEST_ELEMENT>
</TEST1>
<TEST2 test_attribute="ghi">
<TEST_ELEMENT>jkl</TEST_ELEMENT>
</TEST2>
</ROW>
</ROWSET>
Now, the "TEST2" element contains an attribute as it should.
It seems that the only time attributes are mapped correctly for a particular object type is when it is first encountered in the query. The mapping fails for each subsequent occurrence. Creating additional object type definitions is a solution, but this can result in the creation of many redundant object type definitions. Is there another solution available? Thanks . . .Hi,
Please tell me when you are getting this error and please explain a bit more what exactly you want to do..
Thanks
--Anil -
Attribute mapping not working with complex searches
Hi all,
We are using "attribute mapping" for some attributes and that works fine as far as we don't make a complex search. We are doing the attribute mapping at the Directory proxy 6.3 so we map businessSector to businessUnit. Everything work fine if we just put businessSector in the search, but if we add something else to the search filter, it will not work.
So, if we use filter businessSector=XXXXXXX, it will work and make all the mapping, but if we use something like "(&(pocketSizeOffice=Yes)(businessSector=XXXXXXX))", it will not work.
We have look at the logs and we see the mapping happening in the first case, but not in the second one.
Have somebody seem this before or is facing this problem?
Thanks,
FedericoHi Federico,
I was not able to reproduce the problem with DPS 6.3 in my labs... so the conditions to reproduce it may be more tricky than described. Anyway, this is not a known problem.
Feel free to contact Sun support to have a fix delivered to you.
Thanks
-Sylvain -
Issue in Develop mode for embedding google map
Hello,
I am facing an interesting issue in Develop mode for embedding google map html code (screenshot is attached)
The map rectangle showing almost same size box underneath filled in black, while in preview mode, it is working properly. I could not find the reason, where I am doing something wrong.
Many thanks .Hi Muzeone,
Its a default behavior with every WYSIWYG HTML Designer or editor,
Reason :The black box which is appearing in the design view is because you might have tried increasing the size of the iframe thumbnail.
If you are using Iframe and using Insert HTML feature in MUSE, make sure when you paste the iframe code in MUSE, it creates a thumbnail in design view do not resize it in design view.
Size does not change the height and width of Iframe in MUSE as its being controlled by the codes that you are inserting.
The design view will only show you iframe height which is defined in the codes below that it will show a black box.
Enjoy working with MUSE !!
Thanks
Prabhakar Kumar -
UME attribute mapping for lastpasswordchange to AD
We are on EP 7.0 and are using Microsoft Active Directory 2003 as our user repository.
I am using a writeable datasource configuration file to update passwords in AD from portal (SSL configured)
For users who had password reset done through the portal, portal has the information for "Date of Last Password Change".
However, for users who do password resets with other mechanisms (outside of SAP portal), portal does not have this information.
I am trying to map the UME logical attribute "lastpasswordchange" to the corresponding physical attribute on Active Directory - which I believe is "pwdLastSet".
My XML configuration looks like the following
<dataSource id="CORP_LDAP"
<responsibleFor>
<principal type="account">
<nameSpace name="com.sap.security.core.usermanagement">
<attribute name="j_user"/>
<attribute name="logonalias"/>
<attribute name="j_password"/>
<attribute name="userid"/>
<attribute name="lastpasswordchange"/>
</nameSpace>
<nameSpace name="com.sap.security.core.authentication">
<attribute name="principal"/>
<attribute name="realm"/>
<attribute name="domain"/>
</nameSpace>
</principal>
<principal type="user">
</principal>
<principal type="group">
</principal>
</responsibleFor>
<attributeMapping>
<principal type="account">
<nameSpace name="com.sap.security.core.usermanagement">
<attribute name="j_user">
<physicalAttribute name="samaccountname"/>
</attribute>
<attribute name="logonalias">
<physicalAttribute name="samaccountname"/>
</attribute>
<attribute name="j_password">
<physicalAttribute name="unicodepwd"/>
</attribute>
<attribute name="userid">
<physicalAttribute name="*null*"/>
</attribute>
<attribute name="lastpasswordchange">
<physicalAttribute name="pwdLastSet"/>
</attribute>
</nameSpace>
</principal>
<principal type="user">
<nameSpace name="com.sap.security.core.usermanagement">
<attribute name="firstname">
<physicalAttribute name="givenname"/>
</attribute>
</principal>
</attributeMapping>
<privateSection>
</privateSection>
</dataSource>
However the above configuration doesn't work. I am not able to read the attribute "pwdLastSet" from AD using attribute mapping.
Can some one please suggest what I am missing ?
Thank You,You may google "pwdLastSet convert" a try to find out some scripts to convert pwdLastSet to another timestamp.
As I got from some Google's [links|http://anothersysadmin.wordpress.com/2010/10/22/convert-pwdlastset-to-a-human-readable-date/] pwdLastSet it counts time in nanoseconds.
Consult you MS Active Diractory team for help to create the converting script of create another attribute in AD with the format that match the portal's timestamp. Then you'll map the new AD attribute to the "lastpasswordchange" attribute of the portal.
Regards, Mikhail. -
Attribute mapping in replication
Hi,
We have around 10 servers running DS5.2P4.
Now we are building DS6.3 servers for an acquired enterprise and would like to store the new directory information in one of the old 5.2 servers for data recovery.
The problem is that the schema in 6.3 is different compared to the old 5.2P4.
So is attribute mapping possible in replication between 6.3 and 5.2 Directory servers.
ThanksHi,
Please tell me when you are getting this error and please explain a bit more what exactly you want to do..
Thanks
--Anil -
Lifecycle issue with table binding + read-only attributes: ADF BUG
Hello all,
I have found what I believe to be an easily reproducible bug in ADF that reproduces in 10.1.3.x, but not in 11g (at least not in drop 6). The best way to describe the bug would be to walk through a simple set of steps to reproduce the bug:
1). Create a new application (ADF BC + ADF Faces).
2). In the model project, create a new Entity Object from the Employee table in the default HR schema. Allow JDev to create an updatable view object and an AM as well.
3). Put a validation rule on the first name attribute of the EO (can be anything, really - I made mine so that the first name cannot be "foo").
4). Test everything using the BC tester if you like.
5). In the UI project, create a new JSPX page.
6). Drag the updatable VO on to your page as an updatable af:table.
7). Put an af:commandButton on the page. Bind its Action or ActionListener to a method in a new backing bean. Put some simple code (I used System.out.println) in the backing bean method.
8). Run the jspx page.
9). Put some invalid data in (e.g. "foo" in the first name field) and click the af:commandButton. Verify that you get an error message and that the Action/ActionListener method DOES NOT fire. So far, so good.
10). Now, to demonstrate the problem. First, look at the page definition for the jspx file. Identify the first attribute that is mentioned (in my case, it was the employee id).
11). Go to the updatable view object and make the attribute from #10 read-only or updatable when new only.
12. Now, repeat step 9 - you should see the error message AND also see that the Action/ActionListener method was executed. You will also see in the messages window that ADF attempted to set the value of the read-only attribute, and thus got a ReadOnlyAttrException.
This issue only happens if the first attribute mentioned in the table binding is read-only. A workaround would simply be to re-order the attributes in the table binding of the pagedef so that the first attribute isn't read-only.
Don't ask how I figured this out ;)
Best,
JohnHi Frank,
Yes, I simply scripted it out this way to contrast the behaviour if the first attribute was read-only vs not read-only. I found the issue on a page in our app that was simply drag-and-drop the VO from the data control on the page.
It's quite annoying, because our particular use case that hit this error is a "save" button on the page. If the commit operation doesn't return any errors (and it doesn't in this use case!), we add a JSF message saying "save successful" - then the attribute errors are further added later in the page lifecycle, so we get 3 messages: "Save successful" and "Fix this error" and "Tried to set read-only attribute" - quite confusing to the end-user when the only message they should see is "fix this error."
At any rate, the fix is to simply re-order the attributes in the page definition - that doesn't affect the UI at all, other than to fix this issue.
John -
Advanced Pricing: A Custom Attribute is mapped to Std. Volume's ITEM_QUANTITY field, to be able to capture a user-defined volume onto the Standard Quantity field via. Attribute Mapping. However the expected behavior is not achieving. Still the PTE prices if off the OM/ASO's Quantity field, and not based on the number that goes into the attribute field.
PTE= 'Order Fulfillment', Context Type = 'Pricing Context', Context = 'VOLUME', Code = 'ITEM_QUANTITY'.
Attribute Mapping Method = ATTRIBUTE MAPPING.
Click on Attribute Mapping button
Application Name=Advanced Pricing
Line Level User Source Type=PL/SQL API
User Value String= OE_ORDER_PUB.G_LINE_REC.ATTRIBUTE10
When I create the Sales Order in OM, at the line level after entering the item, I entered a number in attribute10, then
also a value in the standard quantity field, and Save. The item had price
breaks defined in the pricelist. But the price returned was based on the value
in the standard Quantity field, not the value in attribute10. Even when I
reprice the line (Actions-->Price Line), there is no change.
Expected behavior is to get the Price off the Attribute that mapped to the 'ITEM_QUANTITY' field (which is a standard/seeded attribute).
Does anyone made such expected behavior to work (without being used with a Customer Price API)?can someone pls reply?
Thanks! -
Export Custom Attribute Mapping
Hello Gurus!
I'm migrating a xMII 11.5 project to MII 12.1 and the migration tool was fine on creating the Custom Attributes and Custom Attribute Mapping. However, what I need now is to export Custom Attribute and Custom Attribute Mapping from MII 12.1 DEV to QAS and PRD.
My question is: When exporting Custom Attributes from Configurations menu, it will export Custom Attribute Mapping too? How can I export and import Custom Attribute Mapping from DEV to QAS and PRD?
ThanksManoel,
have you tried the following:
- open System Management / Configurations
- unmark the "Select All" and only mark the "Custom Attributes"
- click export and save the zip file
The exported zip file should include all the settings. In your follow up systems QAS and PRD you can import the zip file.
See also SAP Help on [MII 12.1 Configuration|http://help.sap.com/saphelp_mii121/helpdata/en/43/e80b59ad40719ae10000000a1553f6/frameset.htm]
Michael -
HCM / VDS / IDM Attribute Mapping
Hi folks!
So we have a bunch of attributes in SAP that start with SYHR, and we have a couple of questions about them.
1. How are these fields mapped to IDM? We've found some information in Identity Management for SAP System Landscapes: Configuration Guide, but we are looking for something more. It seems attributes mapped in the PNP database (or tables?) is not shown that clearly. Our Business Analysts want more information.
2. It seems most of these fields are calculated somehow. As a bonus, we'd like to know how these fields are calculated in the first place.
Thanks for any help you can provide,
MattI am not sure how well the document reflects the attribute mapping in the transfer event task in the Staging Id Store. I guess that you need to both look at the document and the event task in Staging Id Store that moves the data to Productive Id Store to see all the attribute mappings.
The real question is how would you need to map them between HCM and IdM. It's pretty normal requirement analysis work to figure out what to export. You should only export relevant attributes.
I am not sure about "calculated attributes" and I am not an ABAP'per, but if you have HCM-consultants on site have them analyze the query definition shipped with HCM. Any transformation that takes place should be in the query and it's data mappings.
I wrote this while ago, won't give you any technical tips etc but more of what I've faced in HCM-integration: Considerations in connecting SAP IdM with Leading Identity System(s)
regards, Tero
Maybe you are looking for
-
Will someone outside of the United States check to see if a song is available in your country?
I am looking for someone located in Canada, Spain or South America who can check to see if a certain song is available on their country's itunes. If you are willing to take a couple of minutes to check for me that would be great and highly appreciate
-
I cannot access my previous computer (as the School Technicians reformatted it before deactivating Adobe Acrobat XI Pro). What's the procedure to contact someone to help when chat is closed?
-
Hi, We just upgraded to oracle patch set 9.2.0.8.0 Now We are not able to start database. OS Win2k3 Logs: trc file: "dev_w0", trc level: 1, release: "640" ACTIVE TRACE LEVEL 1 ACTIVE TRACE COMPONENTS all, M B B Mon Nov 10 22:02:15 200
-
We are running Portal 3.0.9.8.0. I am wondering if anyone has come across away to disable the ability of users to create database links.
-
Currently, we are using a security table, which has, username, department columns. All the base tables have department column. We use views on top of base tables and use a where clause to link security table. For example: select name, address from ta