cancel
Showing results for 
Search instead for 
Did you mean: 

XI and EDI: Mapping Strategy

Former Member
0 Kudos
237

I need to get some opinions on mapping approaches in XI. We're doing EDI with XI 3.0 and the Seeburger Adapter.

We're making design decisions now and the question came up whether we should build one map per IDoc-Partner-X12 transaction or one map per X12-Idoc pair and build in logic to take care of partner specific requirements.

I'm wondering how other folk have dealt with the same design decision? Any pros or cons on either side? I'm wondering about development effort and ongoing maintenance, particularly in production. Any insights would be greatly appreciated. Thanx!

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Thanx for the input everybody. We're also in the earliest stages of our implementation. We've settled on Seeburger and are this week installing XI. The team has had a week of training on XI but it wasn't EDI specific. We have been looking at auto map generators like Contivo but in the end it will need to prove real immediate ROI before we take on another tool.

As for mapping, I understand about the one map. The concern here about the one-map approach is related to regression testing: if you have only one map per transaction for all partners, and a new partner is added, or an old partner needs to change something, then do we need to do regression testing for all partners because of the change in the one map?

As a developer, I know that we can isolate partner-specific logic within the code of the one map so that it doesn't affect other partners, but the business folk paying the bills don't have the same level of comfort in the logic. The folk at Contivo also recommend doing one big base map capturing everything. They didn't answer the regression testing question very well, however.

Another approach I'm considering is to build one base transaction map that will be used by all partners and will capture the 90 or 95% of the standard that all partners use. Then where there are partner specific requirements that can't be accomodated in the standard, write separate mapping logic to handle exceptions after the base map executes.

It's still too soon for us to make a final decision on mapping approach. At my last project, we did one map per transaction per partner. But we were using a legacy EDI translator through a legacy EAI hub that was being coded by inexperienced developers offshore and was separate from our application system (SAP) development team. We exported or imported the IDocs, and took care of all SAP dev, they did everything else within the EDI architecture outside of SAP.

Thanx to all!

Former Member
0 Kudos

Emmanuel,

Your question is probably the most widely asked question in the EDI world and is valid for not only XI<->EDI butEDI in general.

I have dealt both types in my previous implementations.

In one situation, for EDIFACT, we had single map (in Gentran) to cater to all D96A messages. Customer specific logic were built inside this single map. I found this advantageous, especially when we had to make a global change in the mapping for all customers.

In another situation, for X12, we had individual mapping program for individual customers. This gave more flexibility to customize unique customer's requirements and a change for one customer didn't impact others.

However, I personally prefer one single mapping program because, EDI anyway, is supposed to be following a pre-defined standard. Moreover, its much easier to maintain.

Thanks

KK

Message was edited by: KK

Former Member
0 Kudos

Hi

I would like to know more abt your IDoc and X12 implementation. I am in the beginning stage of IDoc - X12 implementation using XI. We don't have the adapter yet. Which adpater is good Seeburger or some thing else. I would like to know deatils abt imlementing in seburger.

Former Member
0 Kudos

Ram,

At this point of time, Seeburger is the only EDI adapter, I know of, for XI.

SAP has a re-seller agreement with Seeburger. Hence, you can buy this adapter from SAP.

Seeburger also offer training in their adapters and you can find more information by calling them.

Thanks

KK

Former Member
0 Kudos

Hi

I have the same situation, we are thinking of having one IDoc and map to various outbound X12s like 511R 511M 870S 869C etc. Also various inbound X12s mapp to one IDoc. We are in the very intial stage.