SAP B2B Add on - EDI Inbound

[Former Member]

Hi All,

I have doubt in case of EDI inbound using EDISeparator (SAP B2B Add on). I gone through the document and as per my understanding, in inbound EDI there will be two interface

Interface 1) EDI (AS2 or File adapter) to EDI separator adapter (Receiver)

Interface 2) EDI separator adapter (Sender) to IDoc/ file/etc receiver (It may be something else also)

Q1. In case of interface (1) what should be the Outbound interface and Inbound interface. Since Interface (1) is used to separate mass EDI into individual EDI, so I am not sure about the interface use for mass EDI.

Q2. I believe there will be only single interface of type (1) for each EDI format (ANSI, EDIFACT, etc..) and there will be many interfaces of type (2) based on Partners and EDI transaction.

Please correct me if I am wrong in my understanding and provide your inputs to clear my queries.

- RM

[Former Member]

Hi all,

is it obligatory transfer EDI message via EDI SEPARATOR - can i transfer it directly in case single EDI message ?

When i try via EDI SEPARATOR - i am getting internal adapter error:

Error during processing local bean: localejbs/EDIFACTConverterModule

is it works at all for EDIFACT ?

Regards,

Ivan.

[piyush_gakhar]

Hello Ivan,

Closing this loop as it is answered at other location as well

Name of the module need to be exactly mentioned as "localejbs/EdifactConverterModule"

Regards,

Piyush

[Former Member]

Hello Rahul -

I am also panning to explore more on this, Can you tell is this inbuild with 7.3 version or you separately licensed RDS (B2B- Add-one) .  Please advise me.

Regards

Naveen

[Former Member]

Hi Naveen,

B2B Add-on required separate license. You can find many useful blogs and help guides in the new B2B integration space. SAP has provided very useful documentation on installation and configuration of the interface with new solution.

- RM

[Former Member]

Thank you for your prompt response. As you said correct,  gone thru entire document but only thing i am not having system with licensed . We are using 7.1 version which is not accessible. I am very much interested to explore on it. Until unless if you wont experienced in system then you wont be much gain knowledge. Let me know id there any alternate way....

[Former Member]

Hi All,

I have done some progress and configured dummy interface in case (1) interface above. I was able to split the EDI message (ANSI) and generate the output.

Q.)  Scenario I have configured is for ANSI EDI messages from Sender A. Consider in case Sender A also send the EDIFACT messages, then I have to configure one EDISeparator receiver channel of Message Protocol 'EDIFACT'.

How do I add the condition in Receiver determination to route it to the different receiver , based on format (EDIFACT,ANSI). Since inbound payload is EDI not EDI XML.

[Former Member]

Hi Rahul,

As far as the queries in your first post is concerned, you could just use a dummy Inbound and Outbound interface as there is no need for any xml processing or mapping for a simple EDI Separator scenario to run. As i see you already seemed to have achieved the desired result.

Coming to your query in the 2nd post, you say you are using the same sender A to send EDIFACT messages too. You are right that another receiver channel with Message Protocol 'EDIFACT' has to be used. additionally, EDI Separator sender channels should also be configured to receive the split EDIFACT messages(one for each split message).

Hence, you could only send either a bulk EDIFACT message or ANSI ASC X12 message (or ODETTE and VDA too) at a time to one EDI Separator receiver channel. The receiver determination is taken care of at runtime based on the type of the message and you do not have to do anything additional during configuration.

What you need to ensure is that you have separate scenarios(including the Sender, EDI Separator reciever and the EDI Separator senders) configured for very different type of bulk message u want to send(ANSI X12 or EDIFSCT or ODETTE or VDA).

Also, i would like to mention that, development is in progress to allow one EDI Separator receiver channel to receive any bulk message (of course, ANSI X12, EDIFACT, ODETTE and VDA only)  irrespective of the message protocol. The receiver channel shall then take care of splitting the bulk message and dispatching it to the sender channels based on the configuration(if available).

After this feature is available, you would not need separate scenarios for separate message protocols as opposed to the point mentioned by me in the previous paragraph.

Hope this answers your question.

[Former Member]

Hi Amulya,

Thanks for your input and update regarding ongoing development.

I tried your suggestion and configured separate configuration objects for EDIFACT message and ANSI messages. I kept the same sender communication channel, sender agreement and no condition in receiver agreement for routing.

Once scenario runs it runs for both ANSI as well as for EDIFACT and obvious one got failed. It is not taking care of receiver determination in runtime.

My Configuration is

ANSI

EDISenderA(CC_File_Sender)---->EDISeprator(CC_EDISeparator_ANSI_Recv)

EDISeprator(CC_EDISeparator_Sender_ANSI_Ord)--->FileRecv (CC_file_recv_ord)

EDIFACT

EDISenderA(CC_File_Sender)---->EDISeprator(CC_EDISeparator_EDIFACT_Recv)

EDISeprator(CC_EDISeparator_Sender_EDI_Inv)--->FileRecv (CC_file_recv_inv).

am I correct on my understanding of your reply?

Regards

RM

[piyush_gakhar]

Hello Rahul,

Are you trying to execute a  POC or is it specific to customer requirement?

You have currently three options:

1) Use different communication channels on sender side. They may point to same input folder where you can provide different file names for EDIFACT and ANSI bulk messages respectively

2) Wait for new support package for B2B  where we are planning to provide this enhancement.

3) Workaround for your current requirement:

a) Write a custom adapter module( to be used on sender side) which can read incoming message and create an XML message with root tag describing the message type(say EDIFACT or something) based on received bulk message . You need to add these XML tags after reading the headers of the incloming EDI messages. Add this custom module to your sender channel.

b) Add two different receivers to the same scenario.and provide condition based on value of XMl Tags you have added during your module development.

c)Now your message is routed in the right manner to the respective EDI Seperator receiver channel. Write another module (or enhance the same adapter module) which can remove these XML tags and convert the payload  back to plain EDI bulk message (which you received initially) and use this module in EDI Sperator receiver channels.

But would be great if you can help us understand the use case of your scenario. Is it real time customer requirement?

Regards,

Piyush

[Former Member]

Hi Piyush,

Thanks for your reply.

I am executing the scenario for POC purpose. We could demonstrate the new B2B solution to our existing and prospective customers. I have following points regarding the three options you provided.

1)  Use different communication channels on sender side. They may point to same input folder where you can provide different file names for EDIFACT and ANSI bulk messages respectively

I can use this solution temporarily for my POC. But in case of real time customer requirement where we have to use AS2 sender adapter or some other technical adapter, we need some different solution to handle this situation.

2) Wait for new support package for B2B  where we are planning to provide this enhancement.

Any expected date for the release of new support package.

3) Workaround one: I will try this.

As Amulya updated in his last post that new support package will not required Message format in case of sender EDISeprator. so this issue will not appear in future.

Any plan of Contrl (EDIFACT) acknowledgement support from the new support package?

- Rahul Malani

[piyush_gakhar]

Hello Rahul,

Yes, CONTROL is also planned. Tentative date would be early December,2012.

Let us know in case you have some more feedback.

You can use this B2B integration space which has been specially created for these new AddOn solutions. You will find latest info, help guides and some important Blogs in the "CONTENT" section.

Regards,

Piyush