Hi Konrad,
Appreciate your response in this “desert of B2B implementation knowledge”.
- I am running a SAP PO 7.4 Dual stack with Seeburger AG.
- I have a single BackEnd ECC representing more then 5 sub ordinary companies of my organization.
- Each sub ordinary company has its own unique identifiers D-U-N-S ,GLN that will be used in the EDI Interchanges (x12 or EDIFACT).
- Each sub ordinary company might have business with different external EDI partners.
- Each sub ordinary company might have business with the same external EDI partners.
I integrate mainly using AS2 HTTPS ,so the usage of Parties is mandatory.
My aim is :
- To set the foundation for all outbound EDI messages in the organization. Inbound is already set.
- Maximum PI mapping objects reusability (based on message type-message version)
- Currently translation of interchange values for the 3rd parties and my sub ordinary companies is done using value mapping. SenderParty#ALE#LI or ReceiverParty#ALE#KU\ ReceiverParty#ALE#RE. (this works perfectly for both inbound and outbound EDI scenarios)
- To allow minimal setup time per new customer. (currently it’s a 1 hour setup when the map is reusable. IB+ID)
- In order to fulfill item 3 concept the usage of non-LS system is needed.
Regarding your answer: based on what I wrote you can understand there is no need for custom development on the ECC .PI provide all translations services using Value mapping.
Especially as no EDI properties are maintain on the ECC (like partner numbers translations).
According to SAP : non LS to non LS solution is valid.
See note: 2178769 - IDoc_AAE: Enhanced XI sender party resolution when IDoc sender partner is non LS
See document : How to Sample IDoc Scenarios within Exchange Infrastructure 3.0 (NW2004) chapter 4.
I will update this thread with SAP's reccomentations as I am in contact with them.