Hi all,
we have the following situation. We are sending ORDERS.ORDERS05 IDocs from ERP to PI 7.4 AEX and from there to multiple receivers. Some go to SNC, other do "direct communication" with the respective supplier
1. ERP (IDoc) --> PI --> SNC (ABAP Proxy)
2. ERP (IDoc) --> PI --> Supplier 1 (HTTP_AAE)
3. ERP (IDoc) --> PI --> Supplier 2 (HTTP_AAE)
...
The control records of the IDocs that are sent from ERP look like this:
1. To SCN
MESFCT = SNC
SNDPOR = ERPSYS
SNDPRN = LOGERP
SNDPRT = LS
SNDPFC = <empty>
RCVPOR = PISYS
RCVPRN = 1234 (Party number of one supplier that is handled by SNC)
RCVPRT = LI
RCVPFC = LF
2. To Supplier 1
MESFCT = EDI
SNDPOR = ERPSYS
SNDPRN = LOGERP
SNDPRT = LS
SNDPFC = <empty>
RCVPOR = PISYS
RCVPRN = 4321(Party number of the supplier 1 that does direct communication)
RCVPRT = LI
RCVPFC = LF
The first scenario to SNC already existed and was built using an iFlow and standard XI Content provided by SAP (SNC inbound interface is ReplenishmentOrderNotification_In). Let's assume the name is "iFlow_SNC"
Now if i want to add the second scenario with direct communication to supplier to a new iFlow (say "iFlow_EDI_1") NWDS doesn't let me do this because the sender service and sender interface are already in use by "iFlow_SNC". I know I can just add interfaces to that iFlow_SNC and use receiver split with XPath to route to the correct receiver but I hesitate to do so because when looking into future we may have say 100 suppliers and the iFlow will get hard to maintain by then.
Questions:
1. Are there any best practice to deal with such situations (Same IDoc sender system / service to multiple receiver)
2. I fiddled around with parties (assigning the business system of ERP to a party and then creating a new iFlow based on that) but as you might expect, still iFlow_SNC gets chosen and routing fails because there is no rule for supplier 1 there. Is Party setup the right way here? If so, what did I do wrong?
Many thanks and kind regards
Jens
.
