About SEEBURGER-SPLIT 997 adapter

former_member1275317 · ‎08-18-2008

Hi

Can anybody please brief about me SEEBURGER-SPLIT adapter.

In which cases Split adapter comes to picture.?

In our project i will have to implement this adapter, for incoming Purchase order 850 I need to use this split adapter before posting it into R/3.

As i'm new to this seeburger, i'm completely in confuse...

can anyboby give me sugguestions on this ?

pls dont point out me to links....

Regards,

Sandeep

Former Member · ‎08-18-2008

Hi,

By default we get the Order(850) with some acknowledgement(997), so we can split this and send 850 to R/3 and acknowledgement to the sender if they required.

For splitting this we use the split 997 adapter.

S0003485845 · ‎08-18-2008

Hello,

usually you combine the following 3 modules in your Channel:

1. Classifier

2. BIC-Module

3. MessageSplitter

1.)

The Classifier is able to determine if you receive an EDIFACT or ANSIX12 or Flatfile....and depending on this, the BIC-Module executes the appropriate format-conversion

=> like if the files are received from a VAN, you might receive different files in the same channels and this Module-Chain helps you to be able to process all of them in the correct way.

2.) The BIC then translates the EDI-FIle ( ANSI-X12 or EDIFACT...or whatever) into the XML-ANSI-FIle that can be processed by XI.

In your case the 850 is translated into an XML version of the 850.

=> Also if there would be different messages (different ST-Loops, e.g. 850 together with 860 and 997) within one file (ISA-Loop), the BIC then is able to translate each of these ST-Loops into the appropriate XML-Format

3. The MessageSplitter then takes care to send each translated XML-piece in a seperate Channel to the XI, so that you can configure the XML of the 850 to be processed differently to the 860-XML within XI...

The above described scenario then also allows for creating of a 997 message as response to your partner

(using the result of the BIC-Conversion => that means if your translation goes well and your 850 files had correct syntax you can get a positive 997 out of it, to send back to the partner).

Greetings

Stefan

Former Member · ‎08-18-2008

Hi,

Example of splitter

1) Suppose u have a orders file which has multiple orders and u have a requirement where u need to create the n no of IDOC based on the orders which is coming in the file.

So splitter will split the file into n orders n generate n idocs.

Chirag

former_member182455 · ‎08-18-2008

Hi sandeep,

Please go through the following links

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

regards

srinivas

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

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

regards

srinivas

former_member238007 · ‎08-18-2008

Hi,

Check with this basics..

Seeburger EDI Adapter leverages SAP XI's Adapter Framework. This Adapter is used to perform conversion between EDI and XML format. It also provides some canned EDI layouts and the ability to build your own. It is used to transfer the EDI message via HTTP or AS2 protocols.

The most direct way of using the Seeburger adapters is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to do the following:

1. define or import the inbound message metadefinition in various formats ( edifact, xml,...)

2. using a mapping create an xml variant as the output metadefinition or edifact in the other direction.

3. create a one to one mapping between input en output.

4. export the metadata in xsd or sda format for import in XI