How to set the SNDPRT+SNDPRN values on the ECC (outbound scenario)

[former_member187587]

I would like to recive in an IDoc  B2B scenario the control record representing my company with Party (as a sender).

How can that be achived?

default behaviour seems to be 'LS'

[konrad_thalheim3 · Accepted solution]

Hello Nimrod,

I think your requirement is not solvable within the SAP ECC standard as ALE always uses the logical system for routing.

However it could be possible to change the IDoc control record via an customer enhancement (user exit).

Please refer to this documentation: IDoc Interface/ALE - SAP Library

However if your EDI partners have different partner numbers for your company, you will face to maintain these numbers within transaction WE20 and ABAP programs, which is definitely not advisable.

It is always possible to create a Zsegment within your IDocs making them ZIDocs and fill via customer enhancement the desired values. E.g. ILN, GLN, shop codes, etc.

Depending on your process and IDocs, standard IDocs do contain already much information. Within SAP PO you can always use xpath expression for fields and values the deep IDoc structure to determine your receivers.

What kind of processes do you need to implement?

[former_member187587 · Accepted solution]

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 :

1. To set the foundation for all outbound EDI messages in the organization. Inbound is already set.
2. Maximum PI mapping objects reusability  (based on message type-message version)
3. Currently translation of interchange values for the 3^rd 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)
4. To allow minimal setup time per new customer. (currently it’s a 1 hour setup when the map is reusable. IB+ID)
5. 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.

[konrad_thalheim3 · Accepted solution]

Hi Nimrod,

for PI/PO to ECC communication (inbound to ERP) the receiver fields are optional. So the IDoc Adapters usually insert your PO system values in these fields if you do not override it. Inbound IDocs were just processed by the configured program in the partner profile entry for SNDPRN and type.

For outbound communication the ECC will execute the standard ALE behaviour, so you will always have your ECC system in the sender related EDI_DC40 fields.

In any case let us know what SAP support answers you.

[former_member187587 · Accepted solution]

According to SAP's official documentation a non-LS to non-LS B2B scenario is a valid one.

Currently as we assesed our requiremetns this is our scenario.

[former_member187587 · Accepted solution]

Hi Konard\PI guys,

SAP suggested consulting.

According to a colleague of mine there are user exits dedicated for the EDDIC control record per message type.
But, we are still looking for a standard customization though.

[Former Member · Accepted solution]

Nimrod,

Your requirement is very typical in the EDI world. You should leverage B2B - TPM Profiles and Templates to meet your requirement. The way huge organizations set up their trading partners sometimes unfortunately is not with EDI routing on mind. They just assume the message broker can handle anything.

The best way to route the EDI docs is always a combination of WE20 parameters, Payload values (WE/AG etc. segments), User Exit (least preferable), Value Maps (TPM is better) and TPM.

If you are lucky you will use just WE20 config and SHIP-TO, SOLD-TO segments. Next option is TPM Profiles and Templates with UDFTPMPool libraries to do the look up.

[former_member187587 · Accepted solution]

Thanks for the supportive post. 

Actually I am running a dual stack 7.4 PO here ,so the B2B add-on is not part of the solution.

The IT management was in favor of my solution (regarding SNDPRN,SNDPRT) and so forced it.

We are now also benefit from common X12 message mapping with maximum reusability and so our EDI implementations are super - fast.everyone is happy.
For this kind of implementations I have been practicing my whole professional life as a SAP PI architect...everything is falling into place. 

[Former Member · Accepted solution]

Hi Nimrod,

can You share how did You solve that issue? I am facing similar problem (but setup a little bit different):

SAP PO 7.40 single stack with B2B addon. There is no way to manipulate sndprn / sndprt to reflect your scenario.

Did You have to code on ECC side to make this happen or was it possible to go without coding?

best regards

Dawid

[former_member187587 · Accepted solution]

User exit on ECC.

Works like a charm.