[SAP XI] EDI orders posting job to SAP R/3

[Former Member]

Hi everyone!

I would like to know if SAP XI has the capability to directly post EDI orders in SAP R/3 wherein IDocs are placed. If yes, how? (Please describe the process in detail)

In normal EDI implementation (AI, 3rd party translator used), batchjobs are created to be able to post EDI orders. The AI/3rd party translator are sending the IDocs after conversion from customer format order file to the specified UNIX directory in SAP and batchjobs will post these as EDI orders that can be viewed in WE02/WE05.

In SAP XI direct connection case, all IDocs received are automatically posted in SAP R/3 without having a batchjob executing this. However, orders are not successfully posted as there is an authorization issue** (user/system/technology posting EDI orders are not allowed to create an EDI order) so we need to determine which user/system/technology are executing the job (posting of IDocs to an EDI order).

Please advise. Thank you very much!

Fred

[Former Member]

Here's what you need to do:

1. Get the Logical System name for your R/3. Usually, this will be <SID>CLNT<NNN>.

2. Go to SM59 in XI, and open the above destination.

3. Go to 2nd tab, identify the user ID used there.

4. Give this user ID to your securty tem, and ask them to assign authorizations for creating POs etc.

-Feroz

[Former Member]

Hi,

U can do the send EDI data into SAP using third party tool or adapter(Seeburger) or by using the conversion agant.

U need to have the XSD for the EDI structure and EDI data should be flat file.

Check some links on Conversionagant and Seeburger.

/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact

http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf

http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf

http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf

http://www.seeburger.com

http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf

http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf

http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf

http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf

http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf

http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt

http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integratio...

http://www.seeburger.com

http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf

http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf

http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf

http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt

http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf

http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf

http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf

http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf

http://help.sap.com/saphelp_nw04/helpdata/en/43/6d95e0ac846fcbe10000000a1553f6/CMGetStart.pdf

http://help.sap.com/saphelp_nw04/helpdata/en/43/4c38c4cf105f85e10000000a1553f6/content.htm

/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield

/people/alexander.bundschuh/blog/2006/03/14/integrate-sap-conversion-agent-by-itemfield-with-sap-xi

/people/paul.medaille/blog/2005/11/18/conversion-agent-a-free-lunch

/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield

Regards,

Phani

Reward points if Helpful

[Former Member]

Hi everyone!

The scenario is this.

3rd party will send EDI to XI, then XI will translate it to IDOC.

Then it will send to SAP R/3 (A5A).

XI have successfully translated the EDI to IDOC and sent to SAP.

However, on SAP side, it was not successful posting the Idocs.

Idoc adapter is the one sending the IDocs to SAP A5A (R/3), right?

Is there an authorization issue on XI side?

or is there a compatibility issue between XI and SAP A5A?

Does the SAP release number got to do with this? [e.g. SAP 4.5B(A5A)]

because the posting of Idocs on SAP side were not successful.

[prateek]

The EDI orders can only be posted directly through XI in case u receive the EDI document as a flat file and u have the structure (xsd) corresponding to that incoming file. However in a usual generic scenario there is a possibility of many types of incoming files. So direct usage of XI is not possible.

The possible ways are:

1. Use of third party EDI adapters ( e.g.Seeburger)

2. Custom developed adapter module/ adapter

3. Use of Conversion agent

Regards,

Prateek

[prabhu_s2]

by mapping the edi data to the bapi/rfc (by importing in xi) we can post the data directly to r3.