Posting Vendor data from MDM to R3

Hi,
We are trying to post vendor data from MDM to ECC via XI using CREMDM -> CREMAS + ADRMAS and using the standard mapping SAP has provided. I have serialized CREMAS + ADRMAS such that ADRMAS posts before CREMAS. ADRMAS works fine but CREMAS fails with error "Fill all required fields SAPMF02K 0111 ADDR1_DATA-NAME1". Standard mapping is mapping the no-data value "/" in CREMAS NAME1 field too as recommended.Still it throws this error.
If anyone has worked on similar scenario...Please help.
Thanks,

Hi Swapna,
we had faced the same error.
You will need to enter a value in the name1 field if you want your idoc to post successfully.
even though in the vendor creation transaction name1 is not a mandatory field but for the idoc posting, the name1 field is required.
We solved the error by entering a value in the name 1 field.
Hope this helps.
Jyotika
Pls reward for helpful answers

Similar Messages

Error while extracting Vendor Data from R/3 system

Hi all,
I am trying to extract vendor data from R/3(ECC6.0) system to XI using Tcode MDM_CLNT_EXTR.
already I have maintained partner profile for the same.
I have given the necessary details like Creditor_extract,Target System and Distribution Mode as initial load.asusaully extraction process started and I found error in log file like"Table MASTER_IDOC_DATA is empty". Please help me if anyboday have idea about this.
Thanks in Advance,
Ravi.

Hi Ravi,
you've got to set up the message type MDMRECEIPT for the Idoc distribution from R/3 to XI. Check chapter 5.2 in the IT configuration guide available on <a href="http://service.sap.com/installmdm">MDM Documentation Center</a>. It describes the necessary steps.
BR Michael

Problem: Unable to retrieve workflow data from MDM repository

This is a new MDM installations scenario for version 5.5 SP05 (5.5.40.83).
After installing MS Visio, finding problems connecting it with the MDM Data Manager. After doing MDM workflow installations, able to initiate the MS Visio Workflow from MDM Data Manager and can see the Pane-MS Visio Workflow Stencil but not the able to see the Pane-MS Visio Workflow Stencil Details that appears below the Pane-MS Visio Workflow Stencil. Secondly geting a pop-up with the error message as - 'Unable to retrieve workflow data from MDM repository.'
I have added a parameter Mail Server=MailServerIPAddess (the existing IP addr), but it hasn't helped.
Can any one please help me in this !

Hi
As Felix mentioned, it might be a version compatibility problem.
You have also mentioned that mail server is not working for that do this
Mailserver = SMTP server.company.com ( ex. Mail.company(xxxxx).com)
MDM workflow notify task is working after rebooting the Machine. So the rule is after making changes to MDS.ini file reboot the machine ,to observe the consequence of configurable changes.
If u need anything this let me know.
Regards
Hari

Error while retrieving bulk data from mdm in staging server

I am getting an error while retrieving bulk data from MDM. The error goes like this "NiRawReadError: An error occured when reading data from socket.".
Could anyone please suggest me about the possible cause of this error. Please reply soon.
Moderator message: network error, relation to ABAP development unclear, please search for available answers, check with system administrators, consult SAP service marketplace.
Edited by: Thomas Zloch on Nov 22, 2010 5:16 PM

Can you elaborate the thing... I don't think /*+ APPEND */ this is working for me ,still I am getting same error.
If you have any other suggestion,I would like to hear.
Should i not put commit after some 500 records inserted ? As i am putting commit once after whole data gets inserted.

Transfer the data from MDM to SAP R/3

Hi,
I have to transfer the material master data from MDM to R/3.I have syndicated the data and put the file in the .xsd format in the ready folder of the repository.Now I have to transfer this file to R/3 , one way is through XI(XI will pick the file from the current location and an IDOC from there will pass this data to R/3. The other way I was thinking a UNIX script can do it. The UNIX script will run and pick the data from ready folder and pass it to R/3.If somebody of you has done similar thing kindly reply.
Regards,
Ashutosh

The best method of integrating MDM with R/3 is to use XI (PI). There are a couple of reasons for this, but most importantly you can use the IDoc adapter to turn your XML message into an IDoc and send it to R/3. This has a lot of advantages because IDocs are very easy to monitor, troubleshoot, and reprocess in the event of an error. IDocs are definitely the preferred method of integration with R/3, therefore using PI is a very good idea. A few years back I wrote a blog about how to configure XI for an interface between MDM and R/3, perhaps it will help you:
/people/harrison.holland5/blog/2006/12/20/xi-configuration-for-mdm-integration--sample-scenario
While it is possible to use a batch script, it's not recommended. You would still have to write a load program (LSMW or some other type of load program) on the R/3 side. Monitoring and troubleshooting is going to be more cumbersome, because you also have to monitor the message flow on the UNIX system. If PI is serving as the middleware it does the end-to-end monitoring for you.

Read data from MDM For Lookup and Flat table using MDM ABAP API

Hi,
I have requriment to read data from MDM from FLAT and Lookup table using MDM ABAP API. My design is like this ,
I have one ITEMS (Main table in MDM) and inside that i have one Lookup flat table ITEM_TYPE , my requriment is to read Item number and its related Item type.
From ABAP.
Please help if any body has any idea.
Regards,
Shyam

HI Guys,
I found my solution by myself. Below is the solution , hope this will help others:-
Retrieve data from MDM using MDM ABAP API.
Step- 1. Create structure in SAP with the same name as that of MDM field code for MDM Main table.
Step-2. Create another structure in SAP having all lookup fields of MDM , fieldname in ECC must be same as that of MDM field
code.
Step-3.Create structure in SAP for individual lookup field(Single Field only)   with the same name as MDM Field code.
Step-4.
DATA: IT_QUERY            TYPE STANDARD TABLE OF MDM_QUERY, "MDM_QUERY_TABLE,
      WA_QUERY            TYPE MDM_QUERY,
      WA_CDT_TEXT         TYPE MDM_CDT_TEXT,
      IT_RESULT_SET_KEY   TYPE MDM_SEARCH_RESULT_TABLE,
      WA_RESULT_SET_KEY   TYPE MDM_SEARCH_RESULT,
      WA_STRING           TYPE STRING.
DATA:<Internal table> TYPE STANDARD TABLE OF <SAP Str Having all LOOKup Fields>
DATA: :<Internal table>TYPE STANDARD TABLE OF <SAP Str one LOOKup field>,
     <Workarea> LIKE LINE OF :<Internal table>.
*PASS LOGICAL OBJECT NAME.
V_LOG_OBJECT_NAME = 'Logical object name defined in Customization'.
Define logon language, country & region for server
WA_LANGUAGE-LANGUAGE = 'eng'.
WA_LANGUAGE-COUNTRY = 'US'.
WA_LANGUAGE-REGION = 'USA'.
TRY.
    CREATE OBJECT LR_API
      EXPORTING
        IV_LOG_OBJECT_NAME = V_LOG_OBJECT_NAME.
ENDTRY.
CONNECT to repository. Apply particular logon language info
CALL METHOD LR_API->MO_ACCESSOR->CONNECT
EXPORTING
    IS_REPOSITORY_LANGUAGE = WA_LANGUAGE.
*NOW PASS ITEM NO AND GET KEY FROM MDM.
CLEAR WA_QUERY.
WA_QUERY-PARAMETER_CODE = <MDM FIELD CODE>. "Field code
WA_QUERY-OPERATOR        = 'EQ'. "Contains
WA_QUERY-DIMENSION_TYPE = 1. "Field search
WA_QUERY-CONSTRAINT_TYPE = 8. "Text search
WA_STRING                = <Field Value>.
GET REFERENCE OF WA_STRING INTO WA_QUERY-VALUE_LOW.
APPEND WA_QUERY TO IT_QUERY.
CLEAR WA_QUERY.
*PASS ITEM NUMBER AND GET RELATED KEY FROM MDM.
TRY.
    CALL METHOD LR_API->MO_CORE_SERVICE->QUERY
      EXPORTING
        IV_OBJECT_TYPE_CODE = <MDM Main Table>
        IT_QUERY            = IT_QUERY
      IMPORTING
        ET_RESULT_SET       = IT_RESULT_SET_KEY.
CATCH CX_MDM_COMMUNICATION_FAILURE .
CATCH CX_MDM_KERNEL .
CATCH CX_MDM_NOT_SUPPORTED .
CATCH CX_MDM_USAGE_ERROR .
CATCH CX_MDM_PROVIDER .
CATCH CX_MDM_SERVER_RC_CODE .
ENDTRY.
Pass record id into keys.
LOOP AT IT_RESULT_SET_KEY INTO WA_RESULT_SET_KEY.
WA_KEYS = WA_RESULT_SET_KEY-RECORD_IDS.
ENDLOOP.
WA_RESULT_SET_DEFINITION-FIELD_NAME = <Look field name>.
APPEND WA_RESULT_SET_DEFINITION TO IT_RESULT_SET_DEFINITION.
CALL METHOD LR_API->MO_CORE_SERVICE->RETRIEVE
EXPORTING
    IV_OBJECT_TYPE_CODE      = <MDM Main Table>
    IT_RESULT_SET_DEFINITION = IT_RESULT_SET_DEFINITION
    IT_KEYS                  = WA_KEYS
IMPORTING
    ET_RESULT_SET            = IT_RESULT_SET.
LOOP AT IT_RESULT_SET INTO
        WA_RESULT_SET.
*PASS KEYS INTO MAIN TABLE TO GET Structure for FALT or Look up Table
TRY.
      CALL METHOD LR_API->MO_CORE_SERVICE->RETRIEVE_SIMPLE
        EXPORTING
          IV_OBJECT_TYPE_CODE = <MDM Main Table>
          IT_KEYS             = WA_KEYS
        IMPORTING
          ET_DDIC_STRUCTURE =<SAP Strct having all Look up fileds of MDM>
ENDTRY.
LOOP AT <SAP Strct having all Look up fileds of MDM> INTO <Work area>.
    CLEAR WA_KEYS.
    APPEND <Work area>-field name TO WA_KEYS.
    CALL METHOD LR_API->MO_CORE_SERVICE->RETRIEVE_SIMPLE
      EXPORTING
        IV_OBJECT_TYPE_CODE = <MDM Lookup table name>
        IT_KEYS             = WA_KEYS
      IMPORTING
        ET_DDIC_STRUCTURE   = <Single Structure in SAP For Lookup field>.
    READ TABLE <Single Structure in SAP For Lookup field>. INTO <Work Area> INDEX 1.
Here you can get the value of realted lookup fields associated with main table data.
ENDLOOP.
ENDLOOP.
LR_API->MO_ACCESSOR->DISCONNECT( ).
Edited by: Shyam Babu Sah on Nov 24, 2009 4:52 AM

How to retrive data from MDM Tuple?

Hi,
How to retrive MDM Tuple data into a java Application? Here I have to fetch the data from MDM Tuple and populate it in a list. can anybody please help me in doing this.
Thanks.

Hi Sree,
Any one of the below mentioned APIs can perform the record retrival from a Tuple.
- Record.getFieldValue(tupleFieldId)
If the tuple record is part of the original table record that can be obtained using one of the Retrieve commands responsible for retrieving records.
- TupleValue.getFieldValue(tupleFieldId)
If the tuple record is part of another tuple record (nested tuple structure)
Hope this helps.
Also a good read related to this - http://help.sap.com/saphelp_nwmdm71/helpdata/en/49/03144f3fad3697e10000000a42189b/content.htm
Regards,
Vinay M.S

How to retrieve data from MDM using java API

hi experts
Please explain me the step by step procedure
how to retrieve data from MDM using java API
and please tell me what are the
important classes and packages in MDM Java API
thanks
ramu

Hi Ramchandra,
You can refer to following links
MDM Java API-pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2d18d355-0601-0010-fdbb-d8b143420f49
webinr of java API
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/89243c32-0601-0010-559d-80d5b0884d67
Following Fourm Threads will also help.
Java API
Java API
Re: usage of java API ,
Matching Record
Need Java API for Matching Record
Thanks and Regards,
Shruti.
Edited by: Shruti Shah on Jul 16, 2008 12:35 PM

Error in Posting the data from SAP ABAP Progra,

Hi,
I am sending sap data from ABAP Program,
I called RFC in the Function Module and given the RFC Destination,
While I am Executing it is going to short Dump.
Data is not posting.
Points will be awarded.
Regards,
Jayasimha.

Dear jaya,
execute FM once without RFC destination.
now collect the data in intermediate variable.
now execute FM with RFC destaination passing collected data as input.
second RFC is genrally treated as dummy which is used only for sending data to XI,it doesnt do any "function" as such.
this should solve your problem gurnteed.
if you still find short dump please paste your abap code,ll get back to you.
reason for short dump:
record set is high and executing module at remote system at a stretch doesn't work sometimes.
Thanks & Regards,
Rama Krishna

Conversion of Vendor data from legacy to SAP

Hi Gurus,
In our conversion process, we have converted our legacy system vendors to SAP. After our conversion, during our validation, we have pulled data from LFA1 (pulled Vendor and Account Group), LFB1 (Pulled Vendor and Previous Account Number - ALTKN) and LFM1 (Pulled Vendor and Currency Code)
We have observed that the number of vendor records in the three tables are different. Here are the results
1) LFA1 - Number of records - 51,158
2) LFB1 - Number of records - 51,164
3) LFM1 - Number of records - 51,147
Can anybody guess why the number of vendor records are different in different tables?
Thanks

Hi,
I think the explanation is not so difficult:
LFA1 key fields: MANDT (client), LIFNR (vendorID)
LFB1 key fields: MANDT, LIFNR, BURKS (company code)
LFM1 key fields: MANDT, LIFNR, EKORG (purchasing organisation)
Relations:
LFA1 - LFB1 > 1 : N
LFA1 - LFM1 > 1 : N
You always have to have a record for a vendorIDin LFA1, but you not always have to have a record for this vendorID in LFB1 and LFM1 if the vendor is not extended for any company code or any purchasing organisation.
If the vendor is extended for a company a company code or purchasing organisation, it means you have a relevant record for the vendorID in LFB1 and LFM1.
You have more records (51 164) in LFB1 than in LFA1 (51 158) because one vendorID (only one record in LFA1) may be extended for several (more than one) company codes. Each extension of this vendorID for company code has a separate record in LFB1. (LFA1 > vendorA; LFB1 > vendorA-company code1 + vendorA-company code2)
Less record in LFM1 means that you have such vendorIDs (records) in LFA1 that are not extended for any purchasing organisation.
BR
Csaba
Edited by: Csaba Szommer on Jul 27, 2008 2:02 PM

Want to pull data from MDM into SAP and send it to portal.

Hi,
I have a requirement where-in i want to get some data from master data management application(a third party application) into sap and send that data to portal. Kindly suggest me on how to go about doing the same. Awaiting your kind responses guys.
Regards
Shailendra.k

Hi Shailendra,
Your requirement is a huge activity with multiple tasks which can be done in multiple ways.
Some basic points:
1. You can read data from your Third party application using
a. Native SQL or
b. a middleware as PI or
c. using connectors based on the platform of the Third party application (VB, .NET, etc.)
2. Data can be sent to portal using
a. Middleware as PI or
b. Creating RFC's
c. BAPI's.
For any specific details, you can check SDN as detailed posts on each of the above is available or can post further.
Regards,
Pranav.

Posting modified data from adf table.

Hi,
I'm still novice in JDeveloper and ADF.
I need to exchange data between two records and store changes in the database.
If I'm using the code below
public void exchangeData(String iterator) {
BindingContainer bindings = getBindings();
DCIteratorBinding it = (DCIteratorBinding)bindings.get(iterator);
RowSetIterator rit = it.getRowSetIterator();
Row curRow = rit.getCurrentRow();
Row prevRow = null;
if (curRow != null && rit.hasPrevious()) {
prevRow = rit.previous();
String value = (String)prevRow.getAttribute("Comments");
prevRow.setAttribute("Comments", curRow.getAttribute("Comments"));
curRow.setAttribute("Comments", value);
} else { //TODO there is no current Record}
rit.setCurrentRow(prevRow);
the data is exchanged with previous record properly, but corresponding "Commit/Save" button is not going to be activated.
What should be done to post or submit data and then commit it?
Thanks in advance!

alexander,
Generally when working with business logic, the work is done in the model layer. You can more easily manipulate the data in a View Ojbect java class than on the form.
1. Look up how to retrieve/iterate data in a View Object or application module class.
2 Expose thoese methods on the view object/application module so that they will be accessable from the data control.
3. Then create a button that will initiate that method from the JSF form.
Stuart

How to retrieve the data from MDM hierarchy table using MDM Java API

Hi,
I had a hierarchy table in MDM. This table had some column say x. I want to retrieve the values of this x column and need to show them in a drop down using MDM Java API.
Can anyone help me to solve this?
Regards
Vallabhaneni

Hi,
Here is your code...
TableId Hier_TId = repository_schema.getTableId(<hierarchy table id>);
java.util.List list = new ArrayList();
ResultDefinition Supporting_result_dfn = null;
FieldProperties[] Hier_Field_props =rep_schema.getTableSchema(Hier_TId).getFields();
LookupFieldProperties lookup_field = null;
TableSchema lookupTableSchema = null;
FieldId[] lookupFieldIDs = null;
for (int i = 0, j = Hier_Field_props.length; i < j; i++) {
if (Hier_Field_props<i>.isLookup()) {
                              lookup_field = (LookupFieldProperties) Hier_Field_props<i>;
     lookupTableSchema =repository_schema.getTableSchema(lookup_field.getLookupTableId());
                              lookupFieldIDs = lookupTableSchema.getFieldIds();
     Supporting_result_dfn = new ResultDefinition(lookup_field.getLookupTableId());
     Supporting_result_dfn.setSelectFields(lookupFieldIDs);
     list.add(Supporting_result_dfn);
com.sap.mdm.search.Search hier_search =new com.sap.mdm.search.Search(Hier_TId);
ResultDefinition Hier_Resultdfn =     new ResultDefinition(Hier_TId);
Hier_Resultdfn.setSelectFields(rep_schema.getTableSchema(Hier_TId).getDisplayFieldIds());
ResultDefinition[] supportingResultDefinitions =
(ResultDefinition[])list.toArray(new ResultDefinition [ list.size() ]);
RetrieveLimitedHierTreeCommand retrieve_Hier_tree_cmd =
new RetrieveLimitedHierTreeCommand(conn_acc);
retrieve_Hier_tree_cmd.setResultDefinition(Hier_Resultdfn);
retrieve_Hier_tree_cmd.setSession(Auth_User_session_cmd.getSession());
retrieve_Hier_tree_cmd.setSearch(hier_search);
retrieve_Hier_tree_cmd.setSupportingResultDefinitions(supportingResultDefinitions);
try {
     retrieve_Hier_tree_cmd.execute();
} catch (CommandException e5) {
          // TODO Auto-generated catch block
          e5.printStackTrace();
HierNode Hier_Node = retrieve_Hier_tree_cmd.getTree();
print(Hier_Node,1);
//method print()
static private void print(HierNode node, int level) {
if (!node.isRoot()) {
     for (int i = 0, j = level; i < j; i++) {
          System.out.print("\t");
     System.out.println(node.getDisplayValue());
HierNode[] children = node.getChildren();
if (children != null) {
          level++;
for (int i = 0, j = children.length; i < j; i++) {
print(children<i>, level);
//end method print()
Best regards,
Arun prabhu S
Edited by: Arun Prabhu Sivakumar on Jul 7, 2008 12:19 PM

Problem posting Vendor Master Data

Hi,
We are posting Vendor Master data from MDM to ECC. We have serialized ADRMAS and CREMAS so that ADRMAS is always posted first and then CREMAS. ADRMAS is always posted correctly but for some reason the link between ADRMAS and its following CREMAS is not getting established. Because of that CREMAS is failing.
We have explored all possible workarounds but nothing is working. Please note that in ECC, the number ranges are set to external numbers. The number ranges in ECC start with leading zeros. We are sending vendor numbers in the same format with leading zeros. However, I have this gut feeling that these leading zeros are causing the problem but I am not sure.
Another thing is that if we create a vendor in ECC and then send data from MDM to update it, we can successfully do that. It's just the new vendor creation that is causing problem.
Please also note that we are using '005' as message function. I have also tried '009' but it's not working either.
Any suggestion, solution, workaround will be highly appreciated.
Thanks,
TS

Hi Michael,
Yes, that's always the case. The <ADRMASxx>-<E1ADRMAS>-<OBJ_ID> and <CREMASxx>-<E1LFA1M>-<LIFNR> both are mapped to our vendor number.
We are using ECC 6.0. I have tried distributing vendors with and without leading zeros but in either case it didn't work.
Here's the error message that we get while posting CREMAS
"Fill all required fields SAPMF02K 0111 ADDR1_DATA-DEFLT_COMM"
Message no. F2282
However, when we check the ADRMAS, we can see a value 'LET' against 'COMM_TYPE' field. It is not empty.
Any help will be greatly appreciated.
TS

Problems with posting iDocs from MDM in SAP R3

Hi,
I am an MDM consultant, with limited knowledge about SAP R3.
We send material master data from MDM, via PI to R3 using iDocs.
We are having problems with posting MATMAS, and it seems the problems are with updating already existing materials.
In BD87 we get the following warnings:
The field MARA-ERVOE is not ready for input and was therefore not initialized
The field MARA-ERVOL is not ready for input and was therefore not initialized
The field MARA-FERTH is not ready for input and was therefore not initialized
The field MARA-KZGVH is not ready for input and was therefore not initialized
The field MARA-XCHPF is not ready for input and was therefore not initialized
With the last message being:
No changes made
I have checked the MDM syndicator, and none of these idoc-fields are linked to the MDM repository.
So they are syndicated blank.
If we try to resend the material, it is again stopped and in BD87 I see the same messages.
Please help me understanding how to solve these issues.
Thanks,
Thomas

Hi,
Please refer the below threads which talks about the similar problem
http://scn.sap.com/thread/3180116
http://scn.sap.com/thread/1374222
Generally the basic view of the material to be created first. Then the sales, purchasing and other views to be created.
There are few fields in the other views which gets values from the basic data view.
Regards,
Antony

Posting Vendor data from MDM to R3

Similar Messages

Maybe you are looking for