Quantcast
Channel: SCN : Unanswered Discussions - B2B Integration with SAP Process Orchestration
Viewing all articles
Browse latest Browse all 499

Accessing sender party using getSenderParytAgency

$
0
0

Hi guys,

 

High level summary of my case:

  • I need to have a single map from Interface X to interface Y between 2 party.
  • The map will be used with multiple parties (for the sender and receiver)
  • The sender and receiver parties will have different Identifiers of different agencies. (DUNS,Phone etc..)
  • I want to use value mapping in a way that the Sender Party Identifiers values will be changes to the target target Party identifier value without referring to the partner in an if-else rule. Value mapping is relevant (although only one schema can defined for the target (and naturally I have more then one Party receiving the same map results).

 

 

Detailed level :

My requirements from the PI scenarios are as followed:

  1. I have an outbound IDoc to X12 scenario.
  2. I want to access in a dynamic way the sender and receiver Party Agency values during mapping.
  3. My map is a reusable map across different partners.
  4. I have maintained various Identifiers representing my sender Partner (DUNS,Phone number,ZZ for mutual defines and more..)

 

How can I get the sender party Agency values in a dynamic way during mapping?

 

For example in a scenario where my 3rd party expects my DUNS In the map I will access it using getSenderPartyAgency (getting back the Qualifier)

and then accessing the value relevant for DUNS.

And in the same map if my 3rd party expects my Phone number a a qualifier I will accedes it the same way sending him back my Phone number as maintained in my Party object.

 

All in the same map. No Partner specific conditions.

 

Is it possible?

Basically a standard scenario like Invoice IDoc mapped to x12 810 might take place with different  partners with different qualifiers but the payload logic will be remained for all..it will be just the ISA qualifiers that will get changed.

 

I believe that for the inbound (x12 to IDoc) it is more simple as the 3rd party usually will have only 2 identifiers - its own (DUNS for example)  and its SAP internal representative number (ALE#KU). But on the outbound scenario my own party might have different identifiers maintain to cover all the different partners doing bruises with it.

 

Appreciate your insights.


Viewing all articles
Browse latest Browse all 499

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>