OCI mapping 2 Qualified tables

Is it possible that 2 qualified tables can be OCI mapped to the same set of fields on requistions page?
We are storing Material Master information in one Qualified table and Calalog information in another Qualified table. The end user can EITHER select Material Master information OR Catalog information, add it to the shopping cart. But, when the items from shopping cart are brought back to the Requistion page, it populates the same fields.
Can it be achieved. Any Ideas.
Thank you guys.
Shai

Hi Priti,
For multivalued field you need to check for Qualified Update option. For this you can refer page 257 of Import manager 7.1 reference guide. Try this option, it should solve your problem.
Thanks & Regards
Dilmit Kaur Chadha

Similar Messages

Issue in Mapping Qualified Table in Import Manager

Hi Experts
I have extracted Customer data from R/3 ECC, I could successfully loaded reference data, but when trying to load Main table data (Using DEBMDM06 MAP) I am getting mapping issues with Qualified table (Sales Data and Bank Details).
Error Messages
Map 'Sales Data' field to import qualifier(s)
Map 'Bank Detals' field to import qualifier(s)
I have checked and found that all the field and value mapping is in place, If i remove mapping for the qualified table fields then the data is ready to import.
What is the issue, and how do I import Qualified Table data.
Appreciate your inputs
Gaurav.

Hi vickey ,
Kindly go through the below link it will help you understand better the mapping the workinga nd importing of Qualified tables:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00a15239-684e-2b10-b8ae-b936b7d1c1fe
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c03240fa-cc3e-2b10-aa9a-a5798e319a6e(Qualified importing with main table)
Hope It Helped
Thanks & Regards
Simona Pinto

OCI Mapping field/table

Hi Gurus,
This is regarding an issue that I am facing with some materials in punchout catalog used with SRM5.0
For some particular items, I get an error "Incomplete items in catalog, only complete items were transferred" on transferring the data from catalog to shopping cart. I checked the slg1 log and found that the error message shows "00001 E BBPWS Unit of measure D97 is not an ISO code. Item will not be transferred D97".
For this item, the catalog shows the unit of measure as Pallets. In the CUNI transaction, the SRM system has D97 and PF having the same descirption 'Pallet'. In the 'Unit of measure' tab, the Pallet unit is maintained as 'PAL' with ISO code as 'PF'. But, I am unable to understand how the D97 UoM is picked by the SRM system while transferring data from the catalog.
Can someone tell me where to look for the mapping fields? I mean where is the data mapping between catalogs and SC saved?
I referred SAP note 395312 which says that "check the mapping of the catalog attributes on the OCI fields in the SAP CartEditor (Logon to the ECManager: Administration --> Configuration -> Shopping Cart)." Can someone guide me as to where to look for this link? What does ECManager logon mean? I am unable to find this link in the web login of SRM. Please help me to find a solution to this.
Thanks n Regards,
Ancy

Hi Masa,
Thanks for the inputs. I checked the slg1 log for catalog interface log and it helped us reach into the program saplbbp_ws_api.
My ABAP consultant tells me that this program is in-turn calling some function modules to read the data. But, he can only conclude that D97 is coming from function module BBP_WS_MAP_OCI_TO_SC and the comment on this call is 'Map from OCI or XML to the SC structure'.
But, then again I am back to my original question: How do I see the mapping rules from OCI?
Thanks n Regards,
Ancy

Import issue with Auto-id in Qualifier table

Hi,
I am trying to load Customer_contact table in MDM5.5 sp4 from R3.
Since SAP-Id is generated in R3, initially portal will send all data to R3 w/o SAP-id but with the MDM-Auto-id.
In return from R3,MDM receives the SAP-id and Contact-id against this MDM-id for update.
In conversion,I am getting "Error in Look uptable" "Internal Error" message to load this file in Main table.
Is there any workaround to map qualifier table with a auto-id in Main table?
This auto-id needs to be non-qual for portal to create the initial record in MDM.But since this is a non-qual fld and we are not able to map it in main table giving "Internal error" . It is my guess.
Appreciate your idea and help
-reo

The issue was fixed after dropping the calculated fld as Non-qual one which was giving problem since required to be mapped in Main table.

Mapping issue with Qualifier table

Hi,
1. I have an issue after mapping all 3 non-qual flds of a qualifier table in main table getting the compound fld enabled but selecting it , not mapping automatically to the appropiate compound field in the destination side, but giving an error message
"unable to retrieve source record".
2. The second issue is that after mapping some of the fields and qualified table and loading the maintable data, saving the map but subsequently when trying to open the saved map , it is coming out with the usual main error window
SAP MDM Import Manager
SAP Import manager has encountered a problem and needs to close.
We are sorry for the inconvenience.
Debug Close
Appreciate your help/suggestion on this issues.
regards
-reo

Answer for Qn2:
First you have to map all the display fields to individual Source Fields..
Once you have mapped all the dispaly fields of the Qualified Table, you have to do value mapping for the Fields that require Value Mapping.
Ex: Source Field A -> Destination Display Field 1
Source Field B -> Destination Display Field 2
Source Field C -> Destination Display Field 3
Now Value Mapping where required should be done.
Once the value mapping is done, then you can create a Compound Field.
If you have done the previous steps correclty, then the compound field name is enabled for you to create Compound Field.
Now map the newly created Compound Field to the Qualified Lookup field of the main table.
Now you have to click on the Automap for value mapping.
Hope this helps.
Please reward if you find this helpful

Import Server - Multiple Qualified Table - Map Crash

Hello,
Requirement: I need to update multiple qualified table using single source file.
Preparation: I have created a map where mapping to multiple qualified table fields maually.
Have created a Inbound Port using the above map.
Problem: Import server throws an exception; while opening the Import Manager using the Port Option and corresponding Exception; Lot of fields were un-mapped. Looks like Import map crashed.
Please feel free to throw some light reg the same!
Thanks
Alexander

Hi Alexander,
If you are performing multiple qualifier table mapping and importing then you will hav eto create differnt map for each table importing.In that case you will rrquire multiple inbound ports and in each ports deatils you will give the map name pertaining to which qualified lookup table you wish to import.
Actually using automatic importing for lookups is not desirable as the lookups always need to be prepopulated before your main table importing.
The exception taht you are receiving could be due to the reason that the map you are saving is using only one table mapping and so most of the fields are left unmapped.
try not to use automatic importing for Lookup qualifier tables and use manual importing and see if the the exception still comes.
Hope it helps
Kindly reaward points if found useful
Thanks
Simona

MDM 2.0 - OCI mapping of field "Price Information"

Hi SDN,
we are on SRM 5.0.
we are setting up MDM 2.0. We do a new installation, although we were already on MDM 1.0. Anyway, we want to keep the repository from MDM 1.0.
Right now we have problems transferring the price of shopping cart positions from the MDM Web Search UI to EBP.
what we did so far:
1. set up j2ee server and oracle
2. set up MDM 2.0 Server
3. Deploy MDM 2.0 SP 2.0 Java API and UI stuff to j2ee
4. set MDM 1.0 Repository in the appropriate place in the file system of MDM Server and unarchived it in the MDM console
5. run repository upgrade using link from upgrade guide (http://<j2eeserver>:50000/webdynpro/dispatcher/sap.com/tcmdmsrmcat~uiutil/Utilities)
6. upgrade configuration (same link as before, but step 2)
still, in the OCI Mapping for price, I still have "price - amount" mapped on NEW_ITEM-PRICE
and still, the price, which I can see in the search UI, is not being transferred to EBP...
I am not sure, if I have to have "Price Information - amount" available as OCI mapping field. Right now, this is NOT the case. In MDM 1.0 it used to work fine with "Price - amount"
In my repository in table cataloge items I have the field "Price Information" which is a qualified lookup table, based on look up table "Price". "Price" contains the field amount, which carries the price value.
any clues welcome - regards, Matthias
Edited by: Matthias Kasig on Dec 20, 2007 4:25 PM

Hi Masa,
just another brief status Q:
Now I am able to receive the price in EBP.
But this is a workaround. Just for a test I did a new OCI mapping like this:
I leave the OCI field NEW_ITEM-PRICE blank and use instead
NEW_ITEM-CUST_FIELD4 --> mapped on --> Price Information - Amount.
Thus I am able to get the value of the price field in my BADI bbp_catalog_transfer.
There seems to be a mismatch of field types. In the MDM Console the amount field is of type 'currency' - I assume this is decimal in fact.
In my incoming structure in the BADI I have tabletype catalog_content which is based on structure BBP_WS_OCI_ITEM_S which carries field price of type DEC... seems reasonable to me - but in the debugger I can't see the incoming price value. Instead now I use BBP_WS_OCI_ITEM_S-CUST_FIELD4 which is of type CHAR20. This works! I regard this as a workaround and I am still researching to get the price field mapped correctly to the proper price field in my BADI.
Masi: Concerning your weblog and SLG1 and Errorlog BTC1...
I set up in SPRO the MDM Catalog and also checked "use error log" for the catalog - still
I wonder how I can access this log and esp the OCI fields -- can you guide me there?
I was clicking through the entries of SLG1 but don't get to see the OCI fields of the transfer, though an entry which is because of the data transfer from mdm towards EBP.
kind regards, matthias
btw: SDN was down, hence the delayed response

Not able to Populate Qualified Table in Import Manager

Hi,
I am performing following steps for populating Bank Detail Qualified table in MDM from R3 but not able to populate the data.
1.Populating all lookup tables like Account_no,Bank-Key.......
2.Mapping all fields in Bank detail table except the 'Collect Auth'
field which is Qualifier
3.In Customer table(Main) mapping Collect auth to Bank Detail field and
customer_no to its corresponding ID.
It is not populating the Bank detail data which are available in lookup tables
Appreciate your suggestion
-regards,
reo

Reo
Matching will be based on the Display field (at least one) of the Main table. This is for example the Customer Number.
You also need to map all the display fields of the qualified lookup table. Then you can set the Qualified Update Action by right clicking on the field in the main that is linked to the qualified lookup.(the Collection_Authorization I think). Set the option that well update/append/replace the qualified data fields of the looked table.
There is two how_to_guides that will help. You can download from SAP Service Market Place. (Otherwise I can email to you)
How To Troubleshoot MDM Import Manager
HowTo_LoadQualifiedFields
Rgs
Con

Using Import Man to load Data into Multi Value Fileds in a Qualified Table

Hi there,
When using the Import Manager, i can not use the "append" option to load data into my multi value field which is contained within my qualified table.
Manually it works fine on Data manager, so the field has been set up correctly. Only problem is appending the data during Import Manager Load.
Any reason why I do not have this option available during Field mapping in Import Manager. The selection options are shown but in gray.
Would appreciate any sugestions.
Chris Huggett

Thanks Sowseel
Its a good document but doesn't address my problem, maybe My problem isn't clear.
The structure(part of) that I have currently is as follows.
Main Table - Material
                       QFTable- MNF PN
                           LUField - MNF Name(Qualifier Single Value)
                           LUField - BU ID (Non Qualifier Multi Value)
                           TField   - P/N- (Non Qualifier)
I know how to load data to the main and qualified tables, but what I can not do, using Import Manger, is updating the "LUField - BU ID (Non Qualifier Multi Value)" using the append functionality.
Thanks
Chris Huggett

Qualified Table getting a blank row in MDM 7.1

Hi All,
We are implementing MDM 7.1 and have created custom repository with multiple main table. We have also few qualified tables.
There is only one non-qualifier in all the qualified tables. The values are u201CAu201D (Active) or u201CIu201D (Inactive).
For example:
We have a qualified table called company group, where we store the groups to which a company belongs.
The import is through import sever and xml file is the input.
When there are no values for the group at the source system, we will not receive the XML tags for the group and we will receive xml tags for other data. The non-qualifier value u201CAu201D will also be part of the company group values from source.
The expected functionality is import server should ignore the company group table in total while importing through import server, as there is no xml tags for group.
We are getting a qualified row with only non-qualifier value u201CAu201D and rest of the values as blank.
Kindly provide suggestion to resolve this.
Regards,
Arul Manickavel

Hi Arul
Try using "Update" or "Replace" in the Import Map for the Qualified field mapping's "Set Qualified Update" option.
Regards
Varun

Source file structure when importing a qualified table

Hello MDM:ers
I need to import a qualified table into the following repository
(it is simplified to illustrate the problem):
Main table: Products
Fields: ID (int), Name (Text), Part number (Qualified)
Qualified Table: Part Numbers
Fields: Manufacturer (Lookup), Part Number (Text)
Lookup table: Manufacturers
Fields: Name (Text)
The source file is a very large text file that has the following structure:
Part ID          Name     Part no. Manuf 1     Part no. Manuf2
123          Nut     ABC               XYZ
456          Bolt     DEF               QWV
The result Im looking for Is to map a file structured a above so that two main table records are created (Nut and Bolt) which both have two qualified table records for each manufacturer. I have not been able to create such a map. I have tried to partitioning and combining fields without success.
I have no problem creating the map if I manually restructure the file to look like:
Part ID          Name     Manufacturer           Part Number
123          Nut     Manufacturer 1          ABC
123          Nut     Manufacturer 2          XYZ
456          Bolt     Manufacturer 1          DEF
456          Bolt     Manufacturer 2          QWV
It where a way to import the file directly in MDM without restructuring it?

Hi Alexander,
MDIS will not work fine if you have multiple tables as the mapping is saved only for 1 table. If you have multiple tables then after performing the process of Pivoting/Reverse pivoting, you will have to use joins.
Join the other tables as Lookup in the Main Table
Save all your configuration in a map. And then configure the map in the port.
It should then work with the MDIS also.
hope it helps.
Thanks and Regards
Niitn Jain

How to map qualifiers?

Hello,
I am new in MDM and have (hopefully) a basic question:
I have issues in the import manager.
My target table is the table Products (source is an Excel file). I am facing issues to import the price data. The sub table price is a qualified look up table that looks like this (its just an example):
Lower Bound (integer Non Qualifier - DF)
Price (integer Qualifier - DF)
Year (text50 Non Qualifier DF)
UOM (text50 Qualifier )
As soon as I map a Qualifier field (either Price or UOM) the import manager tells me:
Map 'Price' field to import qualifier(s).
I think he wants me to map the target field Price <Year; Lower Bound>
What I tried is to create a Partition of the source fields year and Lower Bound and map it to the target field Price <Year; Lower Bound>.
During the value mapping I can not choose the option Add it is grayed out. There is only Map and Auto Map available. But what I like is that these values will be created if they not yet exist..So the only option I have is to map it to the existing <Null> value
Can anyone help me? I am sure it is just a problem of understanding.
How does the process look like to map qualifiers?

Hi ,
What about mapping i ncase of e-mail ,phone and fax fields in the standard business content. In this case the main table is the customer table and it has the e-mail/phone/fax field as a multi-valued qualified lookup.
The lookup table has the country field as a display -non qualifier and other fields like e-mail, address type ,home flag as the qualifiers.
The issue is that with only country as the non qual display field, the mapping is not possible. None of the other fields can act as non-qualifiers, as they are mainly flags.
Ideally, the e-mail address has to appear in the main table as a display field. If this field is created as a DF and qualifier, the compound field does not get created.
If it is created as a DF ,non qualifier, it is wrong, as each customer would have a different e-mai land we cannot upload lookup values for it.
What is the best way to tackle this issue ?
Thanks for all your suggestions.
Regards,
Anita

Lookup Flat Table and Lookup Qualifier Table

Hi,
Can any body confirm that if I will change the type of lookup-flat type field to lookup-qualifier type field. But the structure of Lookup Flat table and Lookup Qualifier table will be the same then the Java code written to populate the lookup-flat type field will work without any changes with its new type (lookup-qualifier).
Right now when I run the code after the above said changes, no error comes but no values is assigned to that field.
Another way to ask this question, can a simple Qualifier Lookup table(without having any qualifier type field) be used as like Lookup flat table.
I would appreciate if any body can help me in this regard ASAP.
Regards
Shahid Nadeem

Hi Alok,
I think this Qualifier importing after main table import is quite trickier that you estimate.
1)Map all the fields of qualified table with source fields whther they are qualifiers or non-qulaifiers.
- we will only be able to view the Non Qualifier field in the qualified table.
2)Now the main step is when you finish all field and value mapping there will be also a Target field name on your qualified table with values of display field. this field must be mapped to a source field to import qualified table. do value mapping also.
- This target field is the linkup field you are talking abot i feel, and it is viewed only in the main table and, as i have only on one non- qualifier this will not be a combination of any display fields.
3)I am not abl eto see the Non -Qualifier in my main table
So how do i proceed.
Kindly guide
Thanks
Simona

Qualified Table (Bank Details) Import Question

I am using MDM 5.5 SP6
I am using the Standard SAP delivered Vendor Master Repository and trying to load the Qualified Bank Details table. Bank Details qualified table we have 9 non-qualified fields and 6 qualified fields.
Do we need to load the non-qualified fields in the bank detail table first?
Anyone help me with details about how to load this table including linking this to the main table?. If anyone has any document explain the steps in detail then could you send it?
Thanks in Advance
Steve

First thanks to all who contributed.
I am able to load the qualified table but these non- qualified fields (Street, City, Swift Code, Bank Group, Bank number and Bank branch), I am not able to map it so after loading it was blank.
Out of the 9 non-qualified fields in the Bank Details Qualified table, Country, Bank Key and Bank name are DISPLAY fields and I am able to map and load these fields.
Other non-qualified fields such as Street, City, Swift Code, Bank Group, Bank number and Bank branch are NOT DISPLAY fields. While using the import manager and doing field mapping, for these 6 fields there is NO destination fields displayed. So I couldnu2019t map it.
When I made the above 6 non-qualified fields as DISPLAY fields, then try to map it, I am able to see these fields in the destination side and did the mapping. After import still those 6 fields are blank.
What I am missing here?. Is there any limit that only 3 non-qualified fields we can map it?
Steve.

Qualified table issue

My excel sheet has 3 coloumns taxcategory taxclassification taxclassificationdesc
my main table come with fields countrycode classification and others
i need to model this in my repository
I have metioned taxclassification as my lookup qualified table with fileds
1 tax classification   qualifier    lookup         flat     taxtypes table
2 country code          noqualifier lookup      flat     countries table
taxtype table fields taxcategory taxclassification taxclassificationdesc
when i load the values and see    i find that this has been modelled incorrectly
because it should have the below relations ship
countrycode taxcategory taxclassification taxclassdesc
IN MWST 0 NO TAX
IN MWST 1 FULL TAX
IN GST 0 TAXABLE
IN GST 1 50 PERCENT TAX
IN GST 2 low TAX
US IST 0 NON TAXABLE
US IST 1 FULL TAXABLE
MX PGT 1 FULLTAX
MX CST 1 FULLTAX
etc
so under MWST should have look up values 0 no tax
                                                                        1 full tax
          gst       0 taxable
                    1 50
                    2 low tax
          IST      0
                   1
urg pls
regds
ve

Hi Veena,
follow the step
1. First import data for Tax Category table as it's lookup table
2. then import tuple data example as follow
Material Number->Country->Tax_Category--->Tax_Class>Tax_Class_Desc
000000000010001-> IN-----> MWST -
> 0 -
> No Tax
000000000010001-> IN-----> MWST -
> 1 -
> Full Tax
000000000010001-> IN-----> GST -
> 0 -
> Taxable
000000000010001-> IN-----> GST -
> 2 -
> Low Tax
000000000010001-> US-----> IST -
> 0 -
> NON Taxable
000000000010001-> US-----> IST -
> 1 -
> Full Taxable
000000000010002-> US-----> IST -
> 0 -
> NON Taxable
000000000010002-> US-----> IST -
> 1 -
> Full Taxable
in above example Material Number is field of main table and all other are tuple fields map one to one field at destination side and select Material Number as Matching field in Match Records tab and import the data
Note : tuple records data can not import directly it require atleast one main table field and it should be display field then select this main fileds as matching field in match records tab then only it will allow to import tuple data
Thanks,
Jignesh Patel

OCI mapping 2 Qualified tables

Similar Messages

Maybe you are looking for