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.

Similar Messages

Qualifier table option in import manager.

Hi Sdners,
I want ot know what is usability of "Set Qualified Update" option in menu bar of import manager.
How to use above mentioned option because when im trying to use it, its greyed out.
Iam using MDM 5.5 SP04.
Explain with below mentioned example.
Main table:
1)Material_number -
> Integer
2)Material_description -
> Text
3)Region -
> LookUpQualified(multivalued).
Qualified Table.
1)Region -
> Nonqualifier.
2)Tax -
> Nonqualifier.
3)Price -
> Qualifier.
Points will be rewarded for genuine answere.
Thanks in Advance.
Regards,
Neethu Joy.

Neethu,
Here's the scenario where you would use this option.
Suppose you are importing the main table data and qualified table data. The initial load will go fine and you will see correct data in the main table and in the qualified table. However, if you are loading the same data again (somebody made some changes and now the client wants you to re-import the data) then you should be very careful with the qualified data. By default a qualified link is set to 'Append' which means every time you import data (even the same data), import manager will create a new link in the qualified tables. To avoid this, you choose the option 'Update' instead of append. This option will allow you to update the existing links and create new ones ONLY if there is new data for them.
Now about why the option is grayed out. To enable this option you have to right click the field that links the qualified table to the main table. For example, in your example below, the field 'Region' is the link between the qualified table and the main table. Right click on this field to set the import option.
Regards,
T

Import Bank Details qualifier table not getting mapped in vendor scenario

Hi All,
I am using MDM5.5 SP5.
Trying to import the IDoc CREMDM04 from ECC 5.0 to MDM.
Using the note 830864 i have copied all the reference data to MDM using the xml that was generated by the program referred in the note..
But Bank details is missing in this reference data. If i try to use the map 99 for bank details i get the error msg "The map cannot be loaded because the table "Bank details" is not a source".
How do I get the bank reference data into MDM .
If I skip this step and i try to import the xml file of CREMDM04 (generated through XI). And then if i use the map 99 i get the same error.
If i use the map CREMDM04 I get the error "The map cannot be loaded because the table "E1LFA1M" is not a source".
Please help!
Thanks a lot!
Jyotika

HI Jyotika,
This usually happens when you have a lookup table which has more than one display field. You get this error because you have to create an Compound field, which might not be set in the map. In order to create a Compound filed just check wether all the individual fields in the destinations field BankDetails<X,Y,Z>(X,Y,Z are individually mapped) then just right click in any portion on the source fields and select compound filed's, it creates a Bank details field and automatically maps it to the destination fields. Some times it also maps the values; if not you got to manually map it.
I you have any problem please let me know.
Regards,
CHARAN

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

How to add record in Qualified table using MDM Java API

Hi experts,
I am trying to add a record into a Table.
but I am facing the problem in setFieldValue method.
//Getting Field-ID to pass in setFieldValue() method.
FieldId[] fields = new FieldId[6];
          fields[0] = repSchema.getFieldId("GTINs", "Description");
          fields[1] = repSchema.getFieldId("GTINs", "Unit_Descriptor");
          fields[2] = repSchema.getFieldId("GTINs", "GTIN");
          fields[3] = repSchema.getFieldId("GTINs", "Alternate_Item_Classifications");
          fields[4] = repSchema.getFieldId("GTINs", "Country_Of_Origin");
          fields[5] = repSchema.getFieldId("GTINs", "Bar_Coded");
Record rec = RecordFactory.createEmptyRecord(mainTableId);
rec.setFieldValue(fields, );
but I am not getting how to assign the value to these fields using MDMvalue Interface.
Can anyone provide me the code sample or Code flow so that I can do this.
Plz help me it'll be great help for me.
Thanks
Tarun
Edited by: Tarun Sharma on Feb 4, 2008 11:39 AM
==========================================================================================
Hi Gurus
I found the way to add the MDMValue in setFieldValue Method.
we can set like this:
setFieldValue(<fieldId object like fieldId[], <MdmValue like this> new StringValue("ABC"));
Now I am facing problem in adding value to lookup flat table.
According to the setFieldValue method we can assign the loookup like this:
setFieldValue(<fieldId[0]>, new LookpValue(<here we have to pass the recordID of lookup table>);
so I want to know how I can pass the recordId of lookup table here.
Please suggest.
Thanks
Tarun Sharma
Edited by: Tarun Sharma on Feb 4, 2008 3:15 PM
Edited by: Tarun Sharma on Feb 4, 2008 3:25 PM
Edited by: Tarun Sharma on Feb 8, 2008 6:58 PM

Hi Andrea,
I tried your suggestion but now i am getting Type Mismatch Error.
Please suggest me what I can do?
//TableId for Lookup[Flat].
TableId lookupTableId = repSchema.getTableId("Return_Goods_Policies");
FieldId[] ReturnGoodsPolicyTableIdFields = new FieldId[1];
ReturnGoodsPolicyTableIdFields[0] = repSchema.getFieldId("Return_Goods_Policies", "Name");
Record recLookup = RecordFactory.createEmptyRecord(lookupTableId);
try{
recLookup.setFieldValue(ReturnGoodsPolicyTableIdFields[0], new StringValue("New_Brand"));
}catch(Exception ex){
System.out.println(ex);
//Creating Record in Qualified Table - Request Details
CreateRecordCommand createLookupcommand = new CreateRecordCommand(simpleConnection);
createLookupcommand.setSession(session);
createLookupcommand.setRecord(recLookup);
createLookupcommand.execute();
//Getting the recordId of Lookup record.
RecordId lookupRecordId = createLookupcommand.getRecord().getId();
//Table Id for Qualified table.
TableId qualifiedTableId = repSchema.getTableId("Ext_Hardlines");
FieldId[] ExtHardlinesFields = new FieldId[3];
ExtHardlinesFields[0] = repSchema.getFieldId("Ext_Hardlines", "Name");//Text
ExtHardlinesFields[1] = repSchema.getFieldId("Ext_Hardlines", "Pieces_Per_Trade_item");//Integer
ExtHardlinesFields[2] = repSchema.getFieldId("Ext_Hardlines","Return_Goods_Policy");
Record recQualified = RecordFactory.createEmptyRecord(qualifiedTableId);
try{
recQualified.setFieldValue(ExtHardlinesFields[0], new StringValue("Qualified Value"));
recQualified.setFieldValue(ExtHardlinesFields[1], new StringValue("Qualified Description"));
recQualified.setFieldValue(ExtHardlinesFields[2], new LookupValue(lookupRecordId));
}catch(Exception ex){
System.out.println(ex);
//Creating Record in Qualified Table - Request Details
CreateRecordCommand createQualifiedCommand = new CreateRecordCommand(simpleConnection);
createQualifiedCommand.setSession(session);
createQualifiedCommand.setRecord(recQualified);
createQualifiedCommand.execute(); I am getting this Type match here, but i m not getting what mistake i did.
RecordId qualifiedRecordId = createQualifiedCommand.getRecord().getId();
//Adding to Main Table
TableId mainTableId = repSchema.getTableId("GTINs");
FieldId[] gtinsFields = new FieldId[1];
gtinsFields[0] = repSchema.getFieldId("GTINs","Ext_Hardlines");
Record recMain = RecordFactory.createEmptyRecord(mainTableId);
//Adding the new record to Qualifed Lookup value and setting the Yes Qualifiers
QualifiedLookupValue qualifiedLookupValue = new QualifiedLookupValue();
qualifiedLookupValue.createQualifiedLink(qualifiedRecordId);
try{
recMain.setFieldValue(gtinsFields[0], new QualifiedLookupValue(qualifiedLookupValue));
}catch(Exception ex){
System.out.println(ex);
CreateRecordCommand createCmd = new CreateRecordCommand(simpleConnection);
createCmd.setSession(session);
createCmd.setRecord(recMain);
createCmd.execute();
Could you help me out?
Thanks
Tarun

Bank details in REGUH

Hi,
I am not able to see the bank details that we maintained on vendor master data in REGUH table when payment run is done. Is there some config or update i need to do or does it not update the REGUH table?

Hi,
In REGUH table, bank details of the bank account that is considered for payment will be available.
In case you want to see all the bank accounts that are maintained in the vendor master, use table LFBK. This will give the details like bank key and bank account number
In case bank details of the particular bank key are required, refer to table BNKA.

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

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

Issue with DTW import of BP bank details

Dear Experts,
While trying to update IBAN & Swift Code for existing bank details in BP Master using DTW, below error appears :-
Enter Valid Code (OCRB.BankCode) [?????173-36] Application defined or object defined error65171
I have checked the Bank code & it is correct.
Another question is if there are more than 1 entry in OCRB template, & a particular entry is to be update, linenum is required but there is no field named linenum available in OCRB table to determine which line in table is to be updated. But in DTW sample template for OCRB, linenum field is shown. Please advise from where to get this value or how to determine which line to be updated.
Another issue is that even if there is a single line in DTW template it takes 10-15 min for DTW to show the results. DTW hangs for this period.
I have tried to update the entry manually in BP master data to validate the IBAN number & it happened successfully.
I checked the import in a test environment & there as well I faced the same issue. Tested the issue on 8.82 PL12 & 14 with same results.
Please advise.
Thanks & regards,
Nitin

Hi,
Please refer SAP note:
865191
- DTW Troubleshooting Guide
Thanks & Regards,
Nagarajan

Creates new record in the Qualifier Table while importing.

Hi Guys,
When sending new bank details to MDM, then MDM creates a new record in the Bank Detail qualified lookup table. This is OK. But when sending exactly same bank details again to MDM, then MDM creates again a new record in the Bank Detail qualified lookup table. I would expect that it
first performs the Automap and only if it cannot find a value, it will add a new record!
Can you guys help me out from this?
Best Regards
Devaraj PK

Hi Devaraj,
Please check these configuration options of Import Manager
1. Default Qualified Update - The default setting for whether incoming source subrecords either are appended to, completely replace,or update the set of existing qualified links of a qualified lookup field when updating existing records.
2. Default Matching Qualifiers - The default setting for which qualifiers to use as matching qualifiers when matching existing qualified links when updating existing records.
Any operation on the qualified tables will depend on the above two options.
Reward if found useful
Regards,
Jitesh Talreja

Import Qualified Tables

Hi All,
When im tryin to import a QT im performing following steps:
1. Import Non Qualifiers with QT(Bank Details) on destination side.
2. Map other fields along with Qualifiers with Main table on destination side.
3. To map teh Qualified main table field i need to create a compound field on source side. When im doing a right click on LHS it gives a option to create compound field, but beyond that Bank details QT comes as a read only field.
Please let me know where im missing out on this.
Thanks
Manish

Hi Manish,
For creating compound field, you should have more than one display fied.
In your case if you have only one non-qualifier then simply map that with the qualified field and if you have more than one then map them will the fields marked as D on the destination side then select both the mapped source fields, right click and select create Compound Field -> Bank Details.
Regards,
Jitesh Talreja

How to import data into taxonomy tables and qualified tables

Hi ALL,
Can anybody suggest to import data into taxonomy tables and qualified tables, when is value mapping neccessary and what is partitioning? and what is the use of that partioning?

Hello rehman
even i am facing same issue regading import of data in taxonomy table
. can we do it through import manager.
please provide me some details i will be very very thankful to u
my email - [email protected]
Thanks & regards
Himanshu

Bank Statement Import interface tables

Hi all,
I'm using OEBS R 12.1.3. Can anybody tells me/some links or info / about the Bank Statement Import Program which interface tables uses as i cannot found or i'm just a bad researcher...? I have to insert data there in order this program to create bank statements.
Thanks in advance,
Bahchevanov.

See http://docs.oracle.com/cd/A60725_05/html/comnls/us/ce/intert01.htm
and How To Create New Bank Statement Mapping Template To Requirement, Latest Patch [ID 563476.1]
Sandeep Gandhi

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

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

Qualified Table (Bank Details) Import Question

Similar Messages

Maybe you are looking for