Regarding EDI

[Former Member]

Hi All,

I went through some documents and understand about EDI. But I would like to learn more about it so any one can please send me as screen short with following manner.

1. From EDI to EDI-XML with screen short

2. EDI-XML to IDOC with screen short

[Former Member]

Hi ! raja

for EDI to EDI-XML

To convert EDI Message into EDI-XML,U have to use standard mappings name inside the BIC modules which will convert the EDIFACT message into desired format.Standard Mapping Name depends upon ur source nd target interface.As u needs to convert EDI TO XML,So the standard mapping name will be See_E2X_(___________) .It will be started with this format and term inside the bracket depends upon ur interfaces used.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e2aeb02c-0601-0010-d680-c9be61ff...

Regds

Abhishek

[Former Member]

follow the below steps:

1) First deploye the Std seeburger mapping provided by see burger on XI

2) If you are using the AS2 adapter then you have to install the AS2 server on XI server.

3) Once you install the std seeburger on SAP XI server you will see the AS2,X400,OFTPS,VAN adapter on XI ID.

5) You need to call the std mapping in the adapter module which does the conversion from EDI to XML and XML to EDI.

steps in IR and ID.

In IR:

You need to use the Standard XSD provided by Seeburger for different mesages like EDFACT ORDERS D96A etc in IR and other steps are similar which we do for the normal scenarios.

In ID:

This is the scenario for AS2

Seeburger has provided std mapping which need to be deployed on Xi server and will be used in XI adapter module tab for EDI-XML and XML-EDi conversion.

Example of mapping:

See_E2X_INVOIC_UN_D96A

See_E2X_INVOIC_UN_D99A

See_E2X_ORDERS_UN_D96A

See_E2X_OSTRPT_EAN_D96A.

1) After deploying mapping program.

We need to give the AS2ID in the party identifier tab,AS2ID that is entered here will be used for identifying the sender and receiver of the document.

1)The value of the Agency field must be Seeburger.

2)The value of the Schema field must be AS2ID.

Every partner is assigned the WAN no which is provided by the WAN service provider. That WAn no we need to configure in the party identifier tab

Configuration in adapter:

Under the party identifiere tab

Agency will be seeburger

Scheme=AS2ID

Name = WAN network no of the partner who is sending the file

Sender AS2 adapter configuration:

Few changes in the module parameter tab.

localejbs/CallBicXIRaBean bic

CallSapAdapter 0

Module configuration:

bic= destSourceMsg = MainDocument

bic= destTargetMsg = MainDocument

bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A which does the conversion of EDI-XML.

Receiver AS2 adapter configuration:

When the adapter is used in a receiver channel, it obtains a message from the Integration Engine and sends it to a business partner. In this case, the following steps are required:

1. Define the channel as a Receiver channel on the Parameters tab

2. The last step ensures the module sequence is complete:

Make sure the module ModuleProcessorExitBean does exist in the module sequence:

Module Name=localejbs/ModuleProcessorExitBean

Type=L

Module Key=Exit

• with the following module parameter:

Module Key=Exit

Parameter Name=JNDIName

Parameter Value=deployedAdapters/SeeXIAS2/shareable/SeeXIAS2

You can refer my thread reply:

flow of the data from EDi to SAp r/3 using seeburger:

1) Data will be coming thorugh WAN or mailbox.

2) If its coming through WAN then every WAN provider will give the partner which is sending the data a partner number for indentification.

3) In your AS2 channel you need to configure the party and for that party you need to give the WAN number which is proivded for that partner. So it will run that configuration whenever that partner send the data.

4) In the adapter you have to give the mapping program name which does the conversion of EDI-XML and XML-EDI.

5) Once you XML is generated then it will be used in MM

6) At the receiver if its IDOC adapter then IDOC adapter will post the IDOC to R3 system.

Thnx

Chirag

[Former Member]

Thanks you so much guys

[Former Member]

Hi Raja,

always rewqard points once u got the required solutions.

Thnx

Chirag

[Former Member]

Hi All,

I am very new to Seeburger Adapter. In my project we are planning to use Seeburger. By reading the above thread I knew that there are some BIC pdfs are there. Any one can please send those pdf to my mail id cheedella_koti@yahoo.com.

Thanks,

Rao.

[Former Member]

Hi,

Can you please raise separate thread for the same.

Chirag

[prateek]

There are many possibilities of handling the EDI documents:

1. Using Seeburger Adapter

2. Creating ur own adapter module

3. Use of conversion agent for specific cases

Based on ur choice, the procedure for configuration will change. So I would suggest to make first ur option clear.

Regards,

Prateek

[Former Member]

Hi,

Basically EDI messages are in different formats namely ANSI X12, EDIFACT, TRADCOMS etc. And for converting this EDI messages to XML messages, you will use a Seeburger adapter along with Seeburger BIC module(Mapping program). So that EDI messages are converted to xml for XI to process it or xml messages are converted in to EDI message.

Refer these blogs for more help:

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

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

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

Regards,

Nithiyanandam