Adapter about PI EDI scenario

[former_member308636]

Hi expert,

We are now using the EDI scenario.

And we can send EDIFACT format profiles through PI by HTTP_AAE adapter.

But now in the inbound scenario, I do the same configuration in the module chain compare with the outbound scenarios.

It can not work well like the outbound scenario.

So I want to ask for your help, below are my screenshots about this, please check.

Looking forward to your help .

Thank you in advance.

Best Regards,

Leo

[S0003485845]

Hi Leo,

when sending out EDIFACT-data, you can clearly select the required X2E-mapping that needs to be used in the channel.

However, when you are receiving data, it is a little more complex, as in this case

- there might be multiple different EDIFACT-messages in one file.

- you might receice data from different partner via the same channel

- you might need to determine dynamically such information (type, partner...).

Therefor Harish has mentioned a module chain that includes additional components

- Classifier

- BIS

- Splitter

You can refer to the attached Blogs for taking a look at the procesing of EDI data with the Seeburger Adapter. They have been prepared some years ago but the steps are still the same.

Also in these examples, I am referring to ANSI X12 data and not EDIFACT data, but the concept is the same...

Previous Configuration (without ICO) :

Quick Overview - B2B Scenario (End2End) with Se... | SCN

Configuration with ICO:

Quick Overview - B2B Scenario with Seeburger ED... | SCN

Good Luck

KR

Stefan

[Harish]

Hi Leo,

you can use the same CallBICXIRawbean in the sender adapter as adapter module. The mapping name will change from X2E*** to E2X***.

AS2 Sender Configuration

1     localejbs/SeeClassifier     Local Enterprise Bean     classifier

2     localejbs/CallBicXIRaBean     Local Enterprise Bean     bic

3     localejbs/Seeburger/MessageSplitter     Local Enterprise Bean     splitter

4     localejbs/CallSapAdapter     Local Enterprise Bean     exit

classifier     attID     classifierAtt

classifier     classifierMappingID     XXX

classifier     destSourceMsg     MainDocument

classifier     showAuditLog     true

bic     classifierAttID     classifierAtt

bic     destEncoding     UTF8

bic     destSourceMsg     MainDocument

bic     destTargetMsg     MainDocument

bic     mappingName     AUTO

bic     split     true

bic     srcEncoding     UTF8

reference - http://scn.sap.com/thread/768355

regards,

Harish

[former_member308636]

Hi Harish,

It is so kind of you. Thank you.

Now the adapter I used is HTTP_AAE, can I configure the module like this?

Also, I have other question, after convert the EDI to XML(or XML to EDI) in the module, where can I check the EDI profile?

Looking forward to you further help.

Thank you in advance.

Best Regards,

Leo

[Harish]

Hi Leo,

from EDI profile, do you mean the EDI flat file? If yes then you need to archive/log the flat file before conversion. There are couple of ways to log/archive the file

1. Filestore module - to store the file in seeburger message tracking

2. BIC module parameter - Create file

Please refer the Stephen Hip response in below thread

File Archiving in AS2 sender adapter | SCN

regards,

Harish