SEEBURGER Interface. - Invoice.

[Former Member]

Hi,

This is my first time . I am doing any interface which includes SeeBerger.

So I have Millions of Doubts.. Which may look Stupid to some one... But for mr it is first time . so i need guidence,

My Scenraio is EDI to IDOC

Invoice coming from vendor to ECC and then acknowledgement back to VENDOR.

This according to FD is two different Scenario.

1. Invoice coming from VENDOR to ECC

2. Acknowledgement ECC to VENDOR.

Now in ESR ,  I can see there are few objects available in predefined content related to SEEBURGER

SWCV : SeeBurger_Genric_EDI 2.1.3 of Seeberger

Namespace : Seeburger.com/B2bContent

Sample Mapping : A810_V4010_to_INVOICE02

External Def : A_810_V4010 - See_XML_810_V4010.xsd

External Def :  INVOIC.INVOICE02

Now Questions are :-

1. How to Start working on this scenario??

2. Do i have to copy mapping & External Def first in some other namespace .. Then i should start working on it ???

3. Rest Config would be same as below  ??? - please check ...

      3.1 Data Types : Copy external def from SeeBurger Namespace .
      3.2 Create Service interface for above external def
      3.3 Message Mapping : Copy message mapping from SeeBurger Namespace .
      3.4 Operation Mapping from above message mapping .

4. ID Config would also be same as normal ???

[zameerf · Accepted solution]

Hi Prabhat,

>>1. How to Start working on this scenario??

refer the below blog and document to have an overview of EDI message processing and step by step approach.

http://scn.sap.com/community/pi-and-soa-middleware/blog/2009/08/01/seeburger--part-1--the-basics

http://scn.sap.com/docs/DOC-30632

hope you find answers for the rest of your questions in above links 🙂

[Former Member]

Hi,

Now My Understanding is .. Interface would be like ... Please correct , If I am wrong ???

AS2 - 810 Sender [ Classifier, BIC , Split Module ]  sending data  to IDOC Receiver - Invoic02 .

Here Split Module will split 810 & functional acknowledgement.

Now  after Split Module -  Split 997 Adapter will come into picture and Pass actual data to IDOC Adapter whereas functional Acknowledgement to AS2 Receiver Adapter

Case I. ) actual data [ 810 ] to IDOC Receiver Adapter

Case II.) whereas functional Acknowledgement to AS2 Receiver Adapter.

More about Case II  - before transfering data to AS2 Receiver Adapter , mapping FunctionalAcknowledge_to_A_997_all will get execute and finally Data received at AS2 would be 997 EDI format.

So Summary : 4 Communicaion Channel.

1.       AS2 Sender – Send 810 EDI & Initiate the Process.

2.       SPLIT997 Sender – Pass actual data to IDOC Adapter whereas functional Acknowledgement to AS2 Receiver Adapter

3.       IDOC Receiver – Receives Invoic02 IDOC

4.       AS2 Receiver – Receives 997 EDI

[zameerf]

Your understanding looks to be okay, did you try to create your interface and test? hope you have the certificates and AS2 id's exchanged between you and your AS2 partner.

[former_member609026]

Hi Prabhath,

Do we need two more communication channels in your scenario?

1) File receiver communication channel to temporarily place the EDI 997 Ack files in PI App server.

2) File Sender to send EDI Ack from temp location of PI app server back to Sender As2 server.

Zameer Pls confirm.

Regards,

Pradeep A.

[Former Member]

Hi,

You are in the right path ..go ahead and build the interfaces..

check the below blog of mine..

http://scn.sap.com/community/icc/integration-scenario-pi/blog/2009/08/05/wanna-implement-seeburger-f...

all you need is to replace the file adapter with the AS2 adapters..

HTH

Rajesh