Access Receiver Determination value in mapping

Hi Everyone,
We have a need to access the receiver determination value from our mapping. Is this information stored in a global variable that we can access from a UDF in our mapping?
Cheers.

Joe,
Could you plz brief your reqmt?
raj.

Similar Messages

Multi Mapping using condition & Dynamic Receiver determination – Used XSLT Mapping

Dear Experts,
 I am struggling to identify an error on the Technical Routing. Firstly according to my scenario, I receive an XML file with multiple PO's and I have to split the file to 2 different target messages. and also according to the source payload I have to send the file to 2 different receivers. first receiver is ABAP Proxy to the back end system and the 2nd one is to a file location. I have used XSLT to split the message into 2 target message type and I have used a XSLT mapping for receiver determination. Does any one have any idea of what I am doing wrong.
Note: some time I will only be able to fill in on target message.
I have attached my XSLT message split mapping with this post, please let me know if you have further question.
Your help is more appreciated.
Advance Thanks,
Pradeep
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/sapxsl" version="1.0">
<xsl:variable name="vFlag"/>
<xsl:variable name="vPONUM" select="POTRACKING/Lines[1]/PONumber"/>
<xsl:template match="/">
 <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
 <ns0:Message1>
 <ns1:MT_Tracking xmlns:ns1="http://www.findel-education.co.uk/axapta">
 <xsl:for-each select="POTRACKING/Lines">
 <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
 <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
 <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
 </sap:call-external>
 <xsl:if test="$vFlag = 0">
 <Lines>
 <DDate>
 <xsl:value-of select="DespatchDate"/>
 </DDate>
 <PONumber>
 <xsl:value-of select="PONumber"/>
 </PONumber>
 <POLine>
 <xsl:value-of select="POLine"/>
 </POLine>
 <QTY>
 <xsl:value-of select="Quantity"/>
 </QTY>
 <VendorMaterial>
 <xsl:value-of select="VendorMaterialNumber"/>
 </VendorMaterial>
 <AccountRef>
 <xsl:value-of select="AccountReference"/>
 </AccountRef>
 <ConsignNumber>
 <xsl:value-of select="ConsignmentNumber"/>
 </ConsignNumber>
 <CarrierURL>
 <xsl:value-of select="CarrierURL"/>
 </CarrierURL>
 <ConsignURL>
 <xsl:value-of select="ConsignmentURL"/>
 </ConsignURL>
 </Lines>
 </xsl:if>
 </xsl:for-each>
 </ns1:MT_Tracking>
 </ns0:Message1>
 <ns0:Message2>
 <ns2:MT_Tracking xmlns:ns2="http://www.findel-education.co.uk/ecc/ax/po/ftp">
 <xsl:for-each select="POTRACKING/Lines">
 <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
 <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
 <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
 </sap:call-external>
 <xsl:if test="$vFlag = 1">
 <Lines>
 <DDate>
 <xsl:value-of select="DespatchDate"/>
 </DDate>
 <PONumber>
 <xsl:value-of select="PONumber"/>
 </PONumber>
 <POLine>
 <xsl:value-of select="POLine"/>
 </POLine>
 <QTY>
 <xsl:value-of select="Quantity"/>
 </QTY>
 <VendorMaterial>
 <xsl:value-of select="VendorMaterialNumber"/>
 </VendorMaterial>
 <AccountRef>
 <xsl:value-of select="AccountReference"/>
 </AccountRef>
 <ConsignNumber>
 <xsl:value-of select="ConsignmentNumber"/>
 </ConsignNumber>
 <CarrierURL>
 <xsl:value-of select="CarrierURL"/>
 </CarrierURL>
 <ConsignURL>
 <xsl:value-of select="ConsignmentURL"/>
 </ConsignURL>
 </Lines>
 </xsl:if>
 </xsl:for-each>
 </ns2:MT_Tracking>
 </ns0:Message2>
 </ns0:Messages>
</xsl:template>
</xsl:stylesheet>

Hi Hareesh,
Please find my determination in the XSLT below, I am using enhanced receiver determination.
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/sapxsl" xmlns:p1="http://sap.com/xi/XI/System" xmlns:ns="urn:sap-com:document:sap:idoc:messages" version="1.0">
<xsl:variable name="vFlag"/>
<xsl:variable name="vAX" select="0"/>
<xsl:variable name="vSAP" select="0"/>
<xsl:variable name="vBoth" select="0"/>

<xsl:template match="/">
 <xsl:for-each select="POTRACKING/Lines">
 <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
 <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
 <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
 </sap:call-external>
 <xsl:choose>
 <xsl:when test="$vFlag = 0">
 
 <xsl:variable name="vAX" select="$vAX + 1"/>
 </xsl:when>
 <xsl:when test="$vFlag = 1">
 
 <xsl:variable name="vSAP" select="$vSAP + 1"/>
 </xsl:when>
 </xsl:choose>
 </xsl:for-each>
 <xsl:if test="$vSAP > 0">
 <xsl:if test="$vAX > 0">
 <xsl:variable name="vBoth" select="$vBoth + 1"/>
 <xsl:variable name="vSAP" select="0"/>
 <xsl:variable name="vAX" select="0"/>
 </xsl:if>
 </xsl:if>
 <xsl:if test="$vBoth > 0">
 <p1:Receivers>
 <Receiver>
 <Service>
 <xsl:text>BS_AXAPTA_TST</xsl:text>
 </Service>
 </Receiver>
 <Receiver>
 <Service>
 <xsl:text>BS_ECQCLNT300</xsl:text>
 </Service>
 </Receiver>
 </p1:Receivers>
 </xsl:if>
 <xsl:if test="$vAX > 0">
 <p1:Receivers>
 <Receiver>
 <Service>
 <xsl:text>BS_AXAPTA_TST</xsl:text>
 </Service>
 </Receiver>
 </p1:Receivers>
 </xsl:if>
 <xsl:if test="$vSAP > 0">
 <p1:Receivers>
 <Receiver>
 <Service>
 <xsl:text>BS_ECQCLNT300</xsl:text>
 </Service>
 </Receiver>
 </p1:Receivers>
 </xsl:if>
</xsl:template>
</xsl:transform>

Receiver Determination in multi mapping

Dear Folks,
I am facing a difficulty in implementing conditional receiver determination in my scenario. This is an IDOC to FILE scenario and requirement is IDOC needs to be split in multiple messages and specific messages to be delivered to different warehouses using FTP.
I have implemented multimapping 1:N and able to split the IDOC as per the requirement. But when I execute conditional receiver determination, all the splitted files are sent to all the warehouses.
The input is
<IDOC>
 <Segment>
 <warehouse_no>1</warehouse_no>
 </Segment>
 <Segment>
 <warehouse_no>2</warehouse_no>
 </Segment>
 <Segment>
 <warehouse_no>3</warehouse_no>
 </Segment>
</IDOC>
and output I want as
File No 1
<MT_WarehouseDetails>
 <warehouse_no>1</warehouse_no>
</MT_WarehouseDetails>
sent to warehouse 1
File No 2
<MT_WarehouseDetails>
 <warehouse_no>2</warehouse_no>
</MT_WarehouseDetails>
sent to warehouse 2
File No 3
<MT_WarehouseDetails>
 <warehouse_no>3</warehouse_no>
</MT_WarehouseDetails>
sent to warehouse 3
currently I am getting all the files in all the folders.
Your help will be appreciated.
- Shri

hi,
it is indeed a nice solution here is what I propose:
define a new communication component called XI_BUS, define a sender comm soap channel SND_SOAP_IDOCTYPE and a receiver soap comm channel RCV_SOAP_IDoctype that points to the sender one. (you will need a service username and password in the pi system). check this link on how to configure your RCV comm channel to point back to your PI system [http://help.sap.com/saphelp_nw04/helpdata/en/2b/d5653fd1d3b81ae10000000a114084/frameset.htm]
source system -> XI (in this flow you do the multi mapping)-> XI_BUS (using RCV_SOAP_IDOCTYPE) (basically re-routing it back to XI)
XI_BUS(using SND_SOAP_IDOCTYPE) -> XI ( here you use your extended receiver determination) -> RCV_1
 -> RCV_2
 -> RCV_n
I hope this helps

Receiver determination for ALEAUD??

Hi,
I have configured my ALEAUD for a (B2B partner) R3 -> PI (B2b) - > PI (local) - > R3 (local) scenario... I have requested the partner PI system to map their systems to my business systems in their Receiver determination step - header mapping.... But the reverse step of sending back AleAUD is falling in our partners system because of the changed business system names...
I am not able map the ALEAUD back to the original Business sytems used by the partners....Although I have created a receiver aggrement the std Aleaud does not pick it up.
I would like to avoid using the ALEAUD as a seperate message approach.
Regards,
Arvind R

Hi Arvind,
Refer this links. Hope it will help you.
Custom processing for ALEAUD01 messages ??
Re: XML Incoming Invoices - Send response to Vendor for Failed Messages in XI
Thanks.

Enhanced receiver determination and value mapping

I want to use enhanced receiver determination functionality in my scenario.
I couldn't see any message interface or data type under http://sap.com/xi/XI/System.
we are on Sp08 nw04s and SAP BASIS 7.0 software component in IR.
I don't want to hard code my business service name in mapping.How can I achieve this?
Thanks,
Rekha.
Message was edited by:
Rekha Lather

Hi,
> couldn't see any message interface or data type under http://sap.com/xi/XI/System.
we are on Sp08 nw04s and SAP BASIS 7.0 software component in IR.
After upgradation to SP08 on NW04s , did you reimport the SAP BASIS Component into your IR? Ask your basis admin team to reimport the SAP basis Component into the IR.
>I don't want to hard code my business service name in mapping.How can I achieve this?
Similar discussion available in the comments section of this blog,
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
Would suggest you use value Mapping.
Regards
Bhavesh

How to Take source value remove zero and use it In receiver Determination

Hi
I am working On IDOc to Soap channel.
In idoc Fields ,I am using EMPST field from IDOC and accordingly I am putting Condition in Receiver Determination.
IF EMPST 111 Then Revceive1
IF EMPST 222 Then Revceive2
IF EMPST 333 Then Revceive3
But sometimes values also Come as 000111 or 00111 or 0111 same for Others.
I have used follwong condition in Receiver Determination.
IDOC/E1EDK01/EMPST u2248 *111
But it working fime for leading zero.
But if values come as 8111 or 78111 it is also routing message to Revceive1.
same for others.
Can you plz suggest solution?

you can use enhanced receiver determination ,, where you can specify your logic in the mapping
http://wiki.sdn.sap.com/wiki/display/XI/EnhancedReceiverDeterminationinSAP+XI
http://wiki.sdn.sap.com/wiki/display/SI/StepbyStepguidetoExplainEnhancedReceiver+Determination
in the UDF you can write the logic to remove leading zeros if required:
Re: removing leading zeros

Alert to Error in Receiver determination mapping

Hi everyboy.
Im using a mapping to decide the receiver determination (ReceiverDetermination - http://sap.com/xi/XI/System).
I can´t configure an alert when the mapping fails.
How could I do that????
Thanks a lot

Hi Christian,
As per my understanding you are using extended receiver determination by creating an interface mapping in between your outbound interface and standard receiver interface of SAP BASIS.Do you mean to say that if source data doesnot fulfill the condition to determine any receiver.If so, then I believe in SXMB_MONI we can find the error as unable to determine receiver.Since it belongs to mapping so it will be executed in Integration engine.
create an alert category in ALRTCATDEF
Define Alert Rule in RWB -> Alert Configuration
Select the our own Alert Category
Click to Add Rule and activate the corresponding rule
Regards,
Nutan

Accessing receiver communication channel parameters in mapping

Hi,
I have an XI sender to HTTP receiver scenario with mapping to set the value of the target URL, which is set as an Adapter Specific Message Attribute (TargetURL).
The mapping is responsible for adding hashed authentication credentials to the end of the URL string.
Ideally I'd like to be able to read the values of the host, port and path from the receiver communication channel configuration than hardcode these in the mapping class.
Does anyone know whether it is possible to read receiver communication channel values within mapping?
I could store the full URL string in the communication channel but this would not be secure hence the preference for doing this in mapping.
Thanks,
Alan

try using Dynamic confiuration
please check HTTP rec doc: http://help.sap.com/saphelp_nw2004s/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm
○ URL: TargetURL
○ HTTP Destination: HTTPDest

INTERFACE MAPPING wa not Displaying in Receiver Determination (Extended)

Hi friends,
I'm doing Enhanced Receiver determination.. but in this if i select Extended radio button in the receiver determination .. I'm not gettting any search help for selecting my Interface mappings..
what misteqe i did.. for getting those interface mappings in Receiver Determination does we need to do..any special things .
i followed the bellow blog.. but like that i'm not getting... and how many interface mappings do we need to create for this..
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
plz suggest me..
thanks
BABU

how many interface mappings do we need to create for this..
One
Make sure u have activated ur Interface Mapping. Also recheck the sender interface and the interface u r selecting in Interface Determination step.
Regards,
Prateek

Receiver Determination, condition to select receiver doesn't extract values

Dear all!
I have SAP PI 7.1
I am facing problem in Receiver Determination while using Condition to select receiver based on the values in the payload.
I need, if Identificador = 1 then receiver BC_1 and if Identificador = 2 then the receiver BC_2
My payload has the value:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:p1="http://pruebas.endesa.es/AME4S_2">
<soap:Body>
 <p1:MT_WS_SENDER_Q>
 <IDENTIFICADOR>1</IDENTIFICADOR>
 <OBJECT_ID>7600000009</OBJECT_ID>
 </p1:MT_WS_SENDER_Q>
</soap:Body>
</soap:Envelope>
But, the trace shows following:
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:MT_WS_SENDER_Q/IDENTIFICADOR </Trace>
<Trace level="2" type="T">......extracting values found: 0 </Trace>
I tried with double quotes, simple quotes, without quotes...
I tried too with a Receiver Rule (with context) and local rule with xpath....
Can someone please advise?
Thanks in advanced!!

Hello,
/p1:MT_WS_SENDER_Q/IDENTIFICADOR = 1
Can you try //p1:MT_WS_SENDER_Q/IDENTIFICADOR = 1 ? I'm sure I read it somewhere here in SDN regarding the xPath difference for stateless and stateless XI 3.0 compatible version is an additional /. It's worth to try
Hope this helps,
Mark

Interface mapping is not visible in receiver determination

Hi,
I could not see interface mapping in my receiver determination in ID.
I can see the message interface and receiver agreement in receiver determination
my scenario is idoc to soap (SAP R3 to webservice)
Thanks
Ruban

hi,
could you plz check as Sheshagiri and Phani have said.
Also wanted to know,are u using the configuration wizard for creating ur business scenario and not finding ur interface mapping?
if so is the case then try creating manually ur reciever determination and add ur interface mapping(if u have already done as said by phani and seshagiri) by inserting it.
let us know how it went.
thanks,
ahmed

Add Interface mapping to Receiver Determination is not possible

Hello,
I create some scenarios from R\3 to BW and R\3 to File.
When I want to add Interface mapping to Receiver Determination is not possible.
Not to choose from list and not with copy and paste.
Any ideas?
Regards
Elad

Hi Elad,
Just check whether ur interface mapping that u defined in IR is activated properly or not.It will be present in the hit list as soon as u click the help button of the interface mapping of the interface determination in the ID.
Regards,
Prasanthi.

Condition check (based on sender file name) at receiver determination step

Hi,
My scenario is File to AS2 (Sender side file adapter and receiver side AS2 adapter)
We have 5 customers, but the source location is same to pick the files, Here we are not using any ESR objects.
Based on the source file name PI need to determine to whoom this file need to send at receiver determination step
Craeted objects
1 Sender CC,
1 Sender agreement,
1 Receiver determination
5 Interface determinations
5 Receiver agreements
5 Receiver CCs.
Could you please provide me your valuable inputs.
Thanks
Ramesh

Hi Venkataramesh,
I understand your scenario as, picking files (different file naming standard for different target customer) from one source folder. Based on file name, that payload should be sent to corresponding target customer. You have mentioned u201CHere we are not using any ESR objectsu201D. I can see two reasons for this decision
1. PI is used to route the messages, i.e., no need to transform the payload. OR
2. Files can binary files like PDF, ZIP, JPG, GIFu2026
Now I can see two possible solutions
1. Simple solution, as proposed by u201CPrabhu Rajesh Janardananu201D, make it into 5 different scenarios (5 sender channels).
2. Bit complex solution, only one sender channel, using extended receiver determination
Step 1:- In Sender File channel check u201CAdapter u2013 Specific Message Adapteru201D in Advanced tab. File Name should be checked.
Step 2:- In Receiver Determination, Select Type of Receiver Determination as u201CExtendedu201D. http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce2a423a8e5430e10000000a42189b/frameset.htm
Step 3:- Do a Graphical Mapping (use it Operation Mapping in Receiver Determination).
Step 4:-
Source and target of graphical mapping will be same (below), because you donu2019t want to access input payload (it can be XML, flat file, JGP, GIF and you donu2019t have its structure).
<Receivers>
 <Receiver>
 <Party agency="" scheme=""></Party>
 <Service></Service>
 </Receiver>
</Receivers>
Step 5:- Write a UDF in Graphical mapping as below. http://help.sap.com/saphelp_nwpi71/helpdata/EN/43/03612cdecc6e76e10000000a422035/frameset.htm Pay attention to method declaration
public String Determine_Receiver( Container container) throws StreamTransformationException
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create(u201Chttp://sap.com/xi/XI/System/Fileu201D,u201CFileNameu201D);
String valueOld = conf.get(key);
//Put your logic here
if (valueOld.equal(u201Cuser1u201D)) {
return u201Cuser1u201D;}
if (valueOld.equal(u201Cuser2u201D)) {
return u201Cuser2u201D;}
if (valueOld.equal(u201Cuser3u201D)) {
return u201Cuser3u201D;}
Step 6: Now use this UDF to map to u201CReceiveru201D and u201C Serviceu201D.
This solution need more fine tuning.
Regards,
Raghu_Vamsee
Edited by: Raghu Vamsee on Jan 8, 2011 5:56 PM

Receiver determination step - Send context

Hi Experts,
I have understood from SAP library and others threads that send context in the receiver determination step is used to send value for the conditions we have added in ther receiver determination and fetch only receivers those satisfy the cretiria.
Please validate whether my understand is right or not?
If its correct, then my question is can we populate this value dyanmically, say field value from another message.
Please clarify.
Thanks,
Kar

Check if the below link is of any interest to you:
http://help.sap.com/saphelp_nwpi71/helpdata/en/46/8015de950e6be3e10000000a155369/frameset.htm
From the link:
Condition: when the AirlineID field in the message payload has the value LH, then the message is
forwarded to the receiver business system BUS_100. A context object of the same name from the ES
Repository is used to access the AirlineID field in the message.
It talks about normal receiver determination as against the receiver determination step (of BPM) which you want....

Receiver determintation using Abap Mapping

Hi,
I configured a scenario in which I'm using extended receiver determination to determine the receiver of an incoming message. (The reason for this is that there is only one XI system and two ECC systems - DEV and QAS. By means of the setting in a customizing table it can be determined whether the message is sent to DEV or QAS. The message can't be sent to both systems because it is a synchronous interface). The receiver determination calls an Interface Mapping which has target interface Receiver Determination. I made an Abap Mapping program in which the customize table is read and the output message is formed as follows (according to the structure of the Receivers message):
      lrf_output_document = lrf_ixml_factory->create_document( ).
      lrf_receivers = lrf_output_document->create_simple_element( name = 'Receivers'
                                                                  parent = lrf_output_document ).
      lrf_receiver = lrf_output_document->create_simple_element( name = 'Receiver'
                                                                  parent = lrf_receivers ).
      lrf_element   = lrf_output_document->create_simple_element( name = 'Party'
                                                                  value = ' '
                                                                  parent = lrf_receiver ).
      lrf_element->set_attribute( name = 'agency'
                                             value = ' ' ).
      lrf_element->set_attribute( name = 'scheme'
                                            value = ' ' ).
      lrf_element   = lrf_output_document->create_simple_element( name = 'Service'
                                                    value = 'DEV'
                                                    parent = lrf_receiver ).
To fill the RESULT field a stream factory is instantiated and a XSTRING is created. When I send a message to the system, the receiver determination dumps: Error when parsing receiver listLength of XML document 129 Error when parsing receiver listLength of XML Document 129 System expected the element 'Receivers'
Looks like the XSTRING has not got the right structure and can not be parsed into the Receivers message. However, when I create a CSTRING, the message looks OK. I also changed the encoding (Codepage 4103).
When I replace the Abap mapping with a message mapping, the receiver determination works OK. However, in that case it is not possible to read the customizing table. I really need the Abap mapping.
Has anyone ever filled the Receivers massage by means of Abap mapping. Any feedback will be appreciated!

Hi,
there is a easier way - totally based on my blogs
create an abap mapping that will feed the dynamicconfiguration in ABAP (with z "Z" namespace) - similar thing shown in my blog
/people/michal.krawczyk2/blog/2007/04/26/xipi-throwing-generic-exceptions-from-any-type-of-mapping
and you don't need to create the XML in ABAP mapping just parse it, fill DC and send the same source to the target
(so you don't change the XML)
then add a message mapping to your interface mapping in which you will only use dynamicconfig value
to populate the receiver segment
nice and clean way
Regards,
Michal Krawczyk

Access Receiver Determination value in mapping

Similar Messages

Maybe you are looking for