MDG-C initial upload via IDOC XML

Hello All,
I am uploding Customer master data initial load using IDOC xml, where i am getting below error.
"ID of the local system cannot be determined".
I have Logical system configured with inbound parameters message type DEBMAS. Any thing else i am missing? Please help.

Uploading via idoc xml .. if there is another connected SAP system .. I wouldnt prefer it as you could directly transfer it via the idocs.
However, this is a simple config as per the config guide available under the MDG help for 6.1. Please check if you have followed all the settings.
Data Export from Source System
http://help.sap.com/erp_mdg_addon61/helpdata/en/68/edb50f21e74fd486009959ce2d72cd/content.htm?frameset=/en/77/29ad50e6542f3ce10000000a44538d/frameset.htm

Similar Messages

IDOC testing: how to upload sample IDOC xml file while outbound IDOCtesting

Hi experts,
can any one tell me , how to upload a sample XML idoc xml(data) file while Outbound IDOC testing;
in WE19 tcode ( insted of manually entering the sample data, i have to import the sample XML/text file into the idoc fields). say IDOC is MATMAS.
Thanks in advance;
Kumar

Hi Asit Purbey,
can you clearly explain, how to upload the file and how can i genetare the IDOC no?
i have seen that function module IDOC_XML_FROM_FILE, in that it is required a port no, what exactly it is, and what type of port is it?
suppose i am having a XML/TEXT file with IDOC data, how can i upload it into the server and how can convert it into the IDOC and how can i generate the IDOC no for outbound testing?
Thanks,
Anil

SAP MDG - Customer IDOC XML

Hello All,
We are trying to upload Customer - IDOC XML for initial upload via Data Import Framework. But my XML file is being ignored when i see the log. My first concern is to check the File format.
Can any one has the IDOC - DEBMAS xml sample file format? If so, can you please share it with me.

Thanks Aleksandr for your response.
I was using the same FM to generate the IDOC xml from IDOC number. This XML file is being ignored after import and there is no proper error message why its been ignored in logs(SLG1). Thats the reason i requested for sample Customer - IDOC xml.
I have done extensive seach on SDN but i couldnt find the sample file. Can any one help me on this please?

Splitting multiple IDoc XML files into single IDoc messages for R/3

Hi all. I have a problem splitting IDoc XML files coming in to XI. I currently have an interface that takes in single store sale IDoc transactions (type WPUBON01) in an IDoc XML file. I then have some complex graphical mapping on the IDoc before sending to R/3 via the IDoc adapter. This works fine. However, we now wish to include multiple sales in one file i.e. many WPUBON01 IDocs. I could use message splitting to do this BUT the mapping is so complex, I do not wish to have to change it to enable the processing of many IDocs in one file instead of just one.
What I want to do: have one mapping splitting a multiple IDoc XML file into single IDoc messages and then another taking these single messages as before and performing the mapping. I cannot find a way to do this in one interface; the main problem I'm having is getting XI to split the multiple IDocs into many single IDoc messages within XI itself. I'd be very grateful for any advice on the best way to do this.
Thankyou.
Stuart Richards (Halfords, UK)

Bhavesh,
Thanks again for a clear explanation... I'm moving forwards but still struggling. I've been on this all afternoon today (after a break on other things) and just cannot get my message to split properly (though the SOAP adapter problem I had earlier is now fixed!). If my initial IDoc XML file contains this format:
<WPUBON01><IDOC>....</IDOC>
<IDOC>....</IDOC>
<IDOC>....</IDOC></WPUBON01>
.. I'm not sure what the cardinaility on the first message mapping and interface mapping should be. I'd have thought the source interface would be 1 and the target would be 0..unbounded but this isn't working. I'm trying different things but I get different errors each time. Currently, I have the above cardinality in my first interface and I'm passing in the following data:
<WPUBON01><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832292</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160633</VORGZEIT><BONNUMMER>1001</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1001</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832293</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1002</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1002</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832294</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1003</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1003</ZUONR></E1WPB06></E1WPB01></IDOC></WPUBON01>
In the message monitor, I get a chequered flag. Great. However, I get the dreaded error 500 in the SOAP receiver comm channel:
SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Exception caught by adapter framework: SOAP Error
Delivery of the message to the application using connection AFW failed, due to: SOAP Error.
Any ideas as to what this might be?! I'm getting there.... if I get a solution out of this, I promise to write the blog myself!
Cheers
Stuart

Best method for initial upload data into CRM

Hey guys,
could someone tell me what is the best and fastest method to upload a mass of data (11 mio. BPs) to CRM? Now i am not sure. I thought you have to do that through the CRM middleware. Now i read you can do this also via IDOC. Which method should i use to do this? What about LSMW?
regards,
Ming

Hello Ming,
Could you tell us where is the Mass Data of BP located?
Are you trying to upload the data from R/3 to CRM? or from legacy systems?
If its from legacy or non-R/3 systems then LSMW is the best approach.
But if its from R/3 to CRM, then better approach would be via MW since once initial load is performed using txn:R3AS,
subsequent delta changes would flow down automatically to CRM.
Hope this helps!
Best Regards,
Shanthala Kudva.

Send/Receive IDOCs (XML) from/to SAP R/3 with XI-SOAP without XI!

Dear SAP specialists,
(BACKGROUND) We are using the Microsoft BizTalk Adapter for SAP 1.0, developed on top of the SAP DCOM Connector (we are using the version 6.20 Patch Nr. 177), with Microsoft BizTalk Server 2002 SP1 in order to send and receive IDOC via the tRFC transport protocol. We are using the Microsoft BizTalk Adapter for SAP 1.0 since February 2002, and today we are exchanging more than 25,000 IDOC/day with this architecture.
When we migrate our SAP R/3 system to the version 4.7 with WAS 6.20, I was very enthusiastic about the possibility of sending the IDOC in XML via the standard HTTP transport protocol, because it would considerably simplify my architecture, i.e. no need of any (expensive) adapter any more! But, I had to realise that the quality of service exactly once will not be there anymore with HTTP as it exists with tRFC. Then, we carry on using the tRFC transport protocol with the adapter.
(QUESTION) But recently, I followed the SAP Course TBIT40 XI Foundations and I learn that:
1. On one hand, the XI-SOAP protocol supports the quality of service exactly once by the usage of a message GUID within the XI-SOAP envelope;
2. On the other hand, all mySAP solutions using WAS 6.20 (or higher) carry a small Integration Engine (with XI-SOAP as the native transport protocol).
Then, my question is: << Is it possible to exchange IDOC (XML) directly with an SAP R/3 4.7 (WAS 6.20) via the XI-SOAP transport protocol using the small Integration Engine embedded into it, with the quality of service exactly once? >>
Many thanks in advance and best regards,
Patrice Krakow

Hello Patrice
We have same issue. Is it possible to use IDoc (XML) directly with SAP 5.0 with SOAP (HTTP) without XI?
Since your que is three years old, I'm sure you must have found some method for this.
We'll highly appreciate your help.
Regards: Gaurave

Convert IDOC XML structure to flat file - and now?

Hi,
we are working with input message ORDERS05 and want to convert it to flat file.
So we used the implementation description from "how to convert an IDOC-XML structure to a flat file....".
Looks like this is a standard procedure described here fitting for all IDOCs.
We followed the guide, making XI ready for Abap-Mapping, implemented the Abap class like described, added an interface mapping with source ORDERS05 to a mess.type dummy destination, added with type Abap-class the class implemented from the guide and completed the Int.Dir. implementation.
For comparism purpose we have two systems as receiver, one with a standard flat file with regular graph.mapping in XI, one with the Abap mapping.
Result:
Error description in SXMB_MONI:
Didn´t expect something like that! The IDOC was delivered successfully to the other simple flat file receiver.
Any idea what we made wrong (we are on SP17) or if there is a standard mistake you can do when following the guide?
Best regards
Dirk

Hi,
I've got the same problem. He the solution in my case:
The problem is:
My IDOC has no element <STDMES>, but the method IF_MAPPING~EXECUTE from the 'HOW-TO Guide' does not check this situation:
el_element = idocument->find_from_name('STDMES').
ls_edidc-stdmes = el_element->get_value().
thows the exception.
Solution:
make shure that the field STDMESis set or change the method to:
el_element = idocument->find_from_name('STDMES').
if not el_element is initial.
ls_edidc-stdmes = el_element->get_value().
endif.
Best regards
Dieter

Integration strategies - Questions about using IDOC XML?

Hello. First time poster here. I am looking for some information for a project for a client and I am hoping someone can give me a pointer to where to start.
I need to connect my clients SAP system to an XML based software package. I have heard about IDOC XML and I hope I can use this technology to do the following:
1. Extract PO's from SAP
2. Insert PO changes to SAP (Price, Delivery, Quantity, etc.)
3. Extract RFQ information from SAP
4. Insert vendor quotations for those RFQ's
Are there existing IDOC XML document types for these transactions?
Does SAP have a tool that generates the IDOC XML and makes the data available as a disk file?
Does SAP have a tool that can read an IDOC XML from a disk file and submit it for insertion into SAP?
Would I need to do any programming on the SAP side to accept the data into SAP or are there, for instance, specific IDOC XML documents for uploading changes to existing PO's?
Is there documentation avaialble that will answer these kinds of questions?
Thank you in advance
David Kuehner

>
dkuehner wrote:
> Hello. First time poster here. I am looking for some information for a project for a client and I am hoping someone can give me a pointer to where to start.
>
> I need to connect my clients SAP system to an XML based software package. I have heard about IDOC XML and I hope I can use this technology to do the following:
>
> 1. Extract PO's from SAP
> 2. Insert PO changes to SAP (Price, Delivery, Quantity, etc.)
> 3. Extract RFQ information from SAP
> 4. Insert vendor quotations for those RFQ's
>
> Are there existing IDOC XML document types for these transactions?
> Does SAP have a tool that generates the IDOC XML and makes the data available as a disk file?
> Does SAP have a tool that can read an IDOC XML from a disk file and submit it for insertion into SAP?
> Would I need to do any programming on the SAP side to accept the data into SAP or are there, for instance, specific IDOC XML documents for uploading changes to existing PO's?
>
> Is there documentation avaialble that will answer these kinds of questions?
>
> Thank you in advance
>
> David Kuehner
You can use XML port for IDOC xml output to file disk or XML-HTTP port to send and receive message through HTTP protocol.
Search for SAP Help ALE

Idoc-xml to Idoc

Hi,
Sender is a 'party' which generates an Idoc. Some of the fields from this idoc has to be fetched by XI and passed to the receiver R/3 system.
Requirement :
Party -
> Idoc-xml -
>XI--> Idoc--
> R/3
(XI - Adapter Sender) ( IDOC Recevier Adapter)
1) what are the initial setting to be done in Xi & R/3 systems?
2) Any authentication details of the party is needed? ( as the XI sender adapter doesn't have many parameters to eneter in comm channel)
Also, here party is an 'R/3 system', who sends the data as an Idoc.
3) How should i convert the idoc to Idoc-xml? In other words how would i create my source DT,MT and MI ?
Appreciate Ur comments,
Thanks,
Raggy

Hi,
Here are the answers pointwise.
1) what are the initial setting to be done in Xi & R/3 systems?
Initial settings are Port and partner configuration in both XI and R/3 systems. You have to configure the RFC destication also.
2) Any authentication details of the party is needed? ( as the XI sender adapter doesn't have many parameters to eneter in comm channel)
Also, here party is an 'R/3 system', who sends the data as an Idoc.
Why are you using XI - adapter???any specific reason?
If party is an R/3 system then you can use IDOC adapter and if not then you can use FILE adapter to pick up the IDOC-XML file.
3) How should i convert the idoc to Idoc-xml? In other words how would i create my source DT,MT and MI ?
You do not need to convert the idoc to idoc-xml. IDOC adapter will do it automatically.
IDOC will act as a MT and also as a MI.
Hope it clarifies your doubts.
Br,
Madan Agrawal

Query about IDOC XML Port

Hi,
I'm trying out the blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/4443. [original link is broken] [original link is broken] [original link is broken] But, I don't see any advantage of using this as it's like appending the file (because each IDoc xml will have it's own start and end tag). Please clarify.
Thanks in advance.
Regards,
Joe.

Hi Joe,
In that case, the root node's occurances should be changes from 1:1 to 1: unbounded.
In general, the idoc's minimum and maximum occurances will be 1.
You have to download the XSD of the standard IDOC and edit the root node occurances to:
xsd:element name="IDOC" type="ORDERS.ORDERS05" minOccurs="1" maxOccurs="unbounded"
then upload the new XSD as external definition.
Then use this external definition as the source structure in the mapping.
Regards,
Ravi

How to transfer data from ECC to CRM via IDocs (Clfmas01),

Hi all,
how to transfer data from ECC to CRM via IDocs (Clfmas01), that to material master data from ECC to Production master data in CRM.
Need Information regarding, how to upload file to CRM from ECC, through, IDocs......Plz help me...
Edited by: khaja fareed on Jan 11, 2010 12:44 PM

First of all push ECC data in to GTS server through T.code:/N/SAPSLL/MENU_LEGALR3. First click on Master data tab there enter customer/vendor number then execute.
2-Go to document tab there enter Sales order no/PO number then execute it.
Then go to GTS server in compliance management module you can get all the information.
Regards
Sitanshu Panigrahi

Send PO via rfc XML with BC 4.7

Hi Gurus,
I have to send the Purchase Order to vendor via rfc XML with business connector 4.7. The vendor should receive the order via ebp XML. We are not using XI we use xCBL. SRM Server 5.5 Standalone.
i use zbbp_PO_send_xml badi for this purpose. We are able to send the data as rfc XML. But the smartform attachment is not working.
Can any one specify me the exact steps involved in this.
Please reply asap as there is an urgency in the task.
Points assured to helpful answers.
Cheers,
Lokesh

We are getting a similar error -
Any ideas on what parameters we need to pass or configure?
JCO.ServerThread-1 [13:15:27:437]: [JNI-LAYER] RFC.incomingRequestHandler() before dispatchRequest("IDOC_INBOUND_ASYNCHRONOUS")
JCO.ServerThread-1 [13:15:27:515]: [JNI-LAYER] RFC.nativeConnect() enter, [SUCCESS]
JCO.ServerThread-1 [13:15:27:515]: [JNI-LAYER] RFC.nativeConnect() before RfcOpenEx("CLIENT="110" USER="ALEWM1" PASSWD=********** LANG="EN" SYSNR="00" ASHOST="atlun02.celanese.com" R3NAME="atlun02.celanese.com" TRACE="1" TOUPPER="0"")
JCO.ServerThread-1 [13:15:27:515]: [JNI-LAYER] RFC.nativeConnect() after RfcOpenEx("CLIENT="110" USER="ALEWM1" PASSWD=********** LANG="EN" SYSNR="00" ASHOST="atlun02.celanese.com" R3NAME="atlun02.celanese.com" TRACE="1" TOUPPER="0"") = 0
with error: RFC_ERROR_PROGRAM No entry for 'atlun02.celanese.com' found in 'C:\WINDOWS\sapmsg.ini'
JCO.ServerThread-1 [13:15:27:515]: [JAV-LAYER] JCO.PoolManager.releaseClient: Cannot release client equals null
JCO.ServerThread-1 [13:15:27:515]: [JNI-LAYER] RFC.incomingRequestHandler() caught the following exception: com.sap.mw.idoc.IDoc$Exception: (2) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "LOIPRO01" is unavailable.
JCO.ServerThread-1 [13:15:27:515]: [JNI-LAYER] RFC.incomingRequestHandler() Exception.message = "The meta data for the IDoc type "LOIPRO01" is unavailable."
JCO.ServerThread-1 [13:15:27:515]: [JNI-LAYER] RFC.abort() enter, [SUCCESS]
JCO.ServerThread-1 [13:15:27:515]: [JNI-LAYER] RFC.abort() before RfcAbort(1,"The meta data for the IDoc type "LOIPRO01" is unavailable.")

Pricing Condition Records initial upload - COND_A

Hi,
I have configured outbound COND_A pricing condition Idocs for Change documents. Whenever the pricing condition is changed IDoc will be generated.
Now my requirement is how can I do the initial upload of existing Pricing Condition records to legacy system? I mean how can I generate Outbound IDocs for existing pricing condition records to do initial upload.
Thanks in advance for your help.
Rgds,
AK

HI,
way1:
if you are using Sretail (ARTMAS) then you can use BD10 tcode with the flag "send all data".
In that case the COND_A for every ARTMAS is send.
way2:
1. if you want to send a all condition, then go to MEK3 choose your conditiont ype and push "condition Info".
2. Make your selection and go ahead with F8
3. Push "Send condition"

Uploading data from xml format

Hi Experts,
                   i am working under ' ZTOOLREV ' transaction which is plant maintainence. i maintain one rfc in se37.
import parameters are mandatory fields entering in this application ,   export parameters are for the errors -
    it is of error structutre name.
further i am creating one web service using transaction ' WSCONFIG ' . so it will be coverted in xml data.
now my client will enter data in xml it has to come to sap and store in sap. and show if any errors.
my requirement is the data is coming from xml format. i have to upload data from xml.
what is the function module should be used to upload the data anad also what function module should used to handle errors?
here in this case i am using gui_download. but i want to put in export parameters.
which i maintained previously.
please guide me experts.
i can get a solution for this query because there are so many experts are there in sdn.sap.

Hi Chaitanya,
You may use the following program to upload your xml data into internal table
REPORT z_read_xml_file.
PARAMETERS: p_filnam TYPE localfile OBLIGATORY
DEFAULT 'C:\Documents and Settings\ssaha\Desktop\test.xml'.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_filnam.
DATA: l_v_fieldname TYPE dynfnam.
l_v_fieldname = p_filnam.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
program_name = syst-cprog
dynpro_number = syst-dynnr
field_name = l_v_fieldname
IMPORTING
file_name = p_filnam.
START-OF-SELECTION.
TYPES:
BEGIN OF ty_tab,
name TYPE string,
value TYPE string,
END OF ty_tab.
DATA:
lcl_xml_doc TYPE REF TO cl_xml_document,
v_subrc TYPE sysubrc,
v_node TYPE REF TO if_ixml_node,
v_child_node TYPE REF TO if_ixml_node,
v_root TYPE REF TO if_ixml_node,
v_iterator TYPE REF TO if_ixml_node_iterator,
v_nodemap TYPE REF TO if_ixml_named_node_map,
v_count TYPE i,
v_index TYPE i,
v_attr TYPE REF TO if_ixml_node,
v_name TYPE string,
v_prefix TYPE string,
v_value TYPE string,
v_char TYPE char2.
DATA:
itab TYPE STANDARD TABLE OF ty_tab,
wa TYPE ty_tab.
CREATE OBJECT lcl_xml_doc.
CALL METHOD lcl_xml_doc->import_from_file
EXPORTING
filename = p_filnam
RECEIVING
retcode = v_subrc.
CHECK v_subrc = 0.
v_node = lcl_xml_doc->m_document.
CHECK NOT v_node IS INITIAL.
v_iterator = v_node->create_iterator( ).
v_node = v_iterator->get_next( ).
WHILE NOT v_node IS INITIAL.
CASE v_node->get_type( ).
WHEN if_ixml_node=>co_node_element.
v_name = v_node->get_name( ).
v_nodemap = v_node->get_attributes( ).
IF NOT v_nodemap IS INITIAL
attributes
v_count = v_nodemap->get_length( ).
DO v_count TIMES.
v_index = sy-index - 1.
v_attr = v_nodemap->get_item( v_index ).
v_name = v_attr->get_name( ).
v_prefix = v_attr->get_namespace_prefix( ).
v_value = v_attr->get_value( ).
ENDDO.
ENDIF.
WHEN if_ixml_node=>co_node_text OR
if_ixml_node=>co_node_cdata_section.
text node
v_value = v_node->get_value( ).
MOVE v_value TO v_char.
IF v_char <> cl_abap_char_utilities=>cr_lf.
wa-name = v_name.
wa-value = v_value.
APPEND wa TO itab.
CLEAR wa.
ENDIF.
ENDCASE.
advance to next node
v_node = v_iterator->get_next( ).
ENDWHILE.
LOOP AT itab INTO wa.
ENDLOOP.

Asset Initial Upload & reporting for uploaded value

Hi SAP Gurus,
I have uploaded the asset data using AS91 and also updated the GL values in OASV.
The initial upload seems to be all correct in this manner since TB is tallying.
However when i view the FA reports for the date of upload i am finding discrepancies in the Accumulated Depreciation values as shown in the report & the values uplaoded in AS91.
Let me explain further, say for eg. the Cost of the asset was Rs. 10,000/- and Accumulated Depreciation as per legacy (as on date of upload) is Rs. 1858/-. However the actual Accumulated Depreciation should have been Rs. 1863 --- the diffference in legacy data was due to runding offs in previous months.
Now when i uploaded the intial data i used the legacy figures i.e. Rs. 10,000 & Rs. 1858 since trial balance had to be tallied.
However when i run reports in FA for the initial upload date, i find that the reports are showing the Acc. Depn (plan values) as Rs. 1863 & not the value that i have uploaded.
What possibly is the reason for this ?
Can anyone tell me any report to view only the uploaded information ?
Points will be awarded for useful answers.
Thanks & Regards
Piyush Kothari

Hi,
There is an error appearing as below:
"Report date 31.08.2007 is invalid for this report.
Reports of this kind can only be run for the last day of the period in which the last depreciation posting run took place (or in a subsequent period) in the relevant fiscal year.
It is not possible to run a report on posted depreciation in a fiscal year in which no depreciation posting run has yet taken place."
My legacy upload date was 31.08.2007.
When i run for 31.12.2007 (last period in the fiscal year for which dep. run has taken place) then the results are ok.
But still i would like to assign some points to you since this would have helped indeed.
Thanks
Piyush Kothari

MDG-C initial upload via IDOC XML

Similar Messages

Maybe you are looking for