Flat Idoc and receiver determination

Hi Folks,
I have a scenario in which the Idoc is sent to XI in a flat format (Flat Idoc) using tunneling mechanism. The receiver determination configured is conditional based (Verifies the values in the specified fields of the Idoc).
Now my question is as we know flat Idoc doesn't contain any fields like XML in the input payload, how the receiver can be identified?
Reminder: (Receiver determination is conditional based and verifies some field values in the Idoc structure)
Thanks,
SPMD

Hi Shabbirmdpasha,
You can use file adapter channel to get idoc flatfile and convert to xml idoc in the module of the file adapter (available in PI 7.1). You only need to make a relation with the type of idoc with the name of the file: for example, DESADV_xxxxxx.txt for all files with DESADV flatfile idoc's.
With this method, you know the interface of the outbound interface, and in the receiver determination you can check in the header of the idoc (dc40) to determine the target system.
PD: Sorry for me english...
Edited by: Oscar Navas on Dec 1, 2010 4:11 PM

Similar Messages

Interface determination and Receiver Determination

Any one can give the clear idea about Interface determination and Receiver Determination????????

HI Gabriel
Interface Determination
An InterfaceDetermination specifies which interface is to be used for the inbound process of a message.
Interface Determination is to specify which inbound interface of a receiver a message is to be forwarded to. We also specify which interface mapping from the Integration Repository is to be used for processing the message. Here it will know which kind of mapping you are using etc.
 ReceiverDeterminatioin.
A ReceiverDetermintaion defines on or more receivers for a sender and an outbound interface.
Receiver Determination is to specify which receivers a message is to be sent to.
Cheers...
Vasu
** REward Points if found useful **

IDoc to IDoc - conditional receiver determination issue

Hello All,
We are using XI 3.0 and this is my scenario:
Sender: IDOC from SAP system
Receivers: There are 2 receivers (one SAP and one non sap system).
I want conditional receiver determination based on the idoc field RCVPRN.
Integration Repository: I imported standard SAP IDOC FIDCC2 into IR and it is in "urn:sap-com:document:sap:idoc:messages" namespace of my SWCV. I am not creating data types, message types or message interfaces as I want to use the IDOC type directly as the interface name in Integration directory.
Integration directory: When I am creating receiver determination, I am getting a warning 'Message interface does not exist in any software components installed on this business system'. When I got to condition editor and want to choose the idoc field RCVPRN using XPATH, it is not showing the idoc structure.
In SLD, the correct product is installed on my sender ABAP technical system, and correct SWCV (into which i imported the IDOC) is installed on my business system. I refreshed cache and cleared SLD cache in ID. Still i get the same warning 'Message interface does not exist in any software components installed on this business system'.
How can i solve this issue? Any help is highly appreciated.
Thanks,
Chandra

Hi Chandra,
Can you check whether you have assigned or linked the SWCV with the Business system in SLD.
Just go to SLD and open the SWCV and check if it is linked with the BS od the sender system.
Since the sender is ABAP, you must have created the TS and BS using rz70, then see that that the SWCV is attached to the BS correctly. Under TS add the Product and then the corresponding SWCV.
Also check one thing: are u selecting the correct Communication component, under which the Interface is present.
Lastly if these doesnot work: In Integration Directory, Go to Environment-> Clear SLD Data Cache. Then try once again.
Cheers,
Souvik
Edited by: Souvik Chatterjee on May 16, 2011 3:39 PM

Some PI questions regarding RFC and receiver determination

If we import the design objects in one customer system from another customer system , and in the original system there is an imported RFC ,
This RFC has been created in the new SAP customer system.
My question is do we have to import the RFC again , as it is already in the imported design objecs.
My second question is , di we need to create a receiver determination for the answe in a synchronous send step of the BPM ,
Thanks

My question is do we have to import the RFC again , as it is already in the imported design objecs
Yes....the RFC/ IDOC should be imported from the system to/ from which you will send/ receive the data.
If the RFC was in system1 earlier and now in system2.....then you have to delete the RFC imported from system1 (if it is not used) and then import it from system2
My second question is , di we need to create a receiver determination for the answe in a synchronous send step of the
BPM ,
Irrespective of sync/ async send step.....you should create Receiver Determination....which will have BPM as sender and the TO_SYSTEM as receiver.....not separately for response....just once
Regards,
Abhishek.

Interface and Receiver determination steps

Dear Experts,
I have list of queries which I am facing issue in ID. I am working on SOAP<->SAP-PI<->PROXY scenario.
1. Created 2 Service Interface i.e. SI_SOAP_OB and SI_PROXY_IB in ESR.
My question is that in the sender and receiver tab what should be the entries in Business System of SOAP and PROXY systems ( i.e. BS system created under the node Communication Component without party). I created this Business System ABAP from the entries of SLD.
2. What is the sequence of steps in the ID i.e. Cc,ID,RD,SA,RA.
3. In the Receiver Determination, I can see in the "Configuration Overview" tab
that the PROXY business system has red entries. I think that this system should show SI_PROXY_IB
but it shows SI_SOAP_OB.
4. When trying to create Interface Determination, I receive "JAVA.lang stack overflow error"
and INTERNAL ERROR.I made sure that there is no inactivated objects under my user.
5. I am sure that the step till creating SI in ESR and sender agreement in ID is correct. Can I create proxy as well as WSDL with end point at this stage.
I need urgent suggestions from experts , kindly help.
Regards
Alice Rebecca

1. Created 2 Service Interface i.e. SI_SOAP_OB and SI_PROXY_IB in ESR.
My question is that in the sender and receiver tab what should be the entries in Business System of SOAP and PROXY systems ( i.e. BS system created under the node Communication Component without party). I created this Business System ABAP from the entries of SLD.
ANS -
For SOAP, anything like Legacy_filer can be created & used.
For PROXY, use the business system of R/3 system maintained in SLD.
2. What is the sequence of steps in the ID i.e. Cc,ID,RD,SA,RA.
ANS-
Sender CC
Sender Agreement
Rec Determination
Int Determination
Rec CC
Rec Agreement.
Create the steps in COnfiguration Scenario directly.
3. In the Receiver Determination, I can see in the "Configuration Overview" tab
that the PROXY business system has red entries. I think that this system should show SI_PROXY_IB
but it shows SI_SOAP_OB.
4. When trying to create Interface Determination, I receive "JAVA.lang stack overflow error"
and INTERNAL ERROR.I made sure that there is no inactivated objects under my user.
ANS
its cache error. Go for full cache refresh in IB>AdministrationData cahce--cache refresh.
5. I am sure that the step till creating SI in ESR and sender agreement in ID is correct. Can I create proxy as well as WSDL with end point at this stage.
ANS
Nope. create the structure in ESR & generate proxy for the same in ECC system. that's it. No need of WSDL here.
-santosh.

INTERFACE DETERMINATION AND RECEIVER DETERMINATION DOUBTS???

Hi Team
I am having doubts regarding the Interafce Determination and the receiver determination. In pur landscape in our objects, some times i am seeing a Condition is being defined in the Interafce Determination and sometimes am seeing a Condition is being defined in the receiver determination . could you please let me know the differences between the above two.
thanx in advance.

Hi Nabhinav,
Condtions in receiver determination - These conditions are evaluated and executed to determine the receivers for this incoming message.
Condtions in Interface determination - These conditions are evaluated and ececuted to determine the Interface mapping to be called in order to map the source message to the target message.
Please take a loot at these links for more details:
http://help.sap.com/saphelp_srm50/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/content.htm
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce2a8e3a8e5430e10000000a42189b/content.htm
Also, search the SDN before posting you query.
Regards, Gaurav.

Context Object for IDOC in Receiver Determination

hi,
I am trying to filter the receivers based on the vendor values in IDOC ORDERS using Context Object.
I don't see the vendor field where i could filter the value.
Any ideas would be greatful.
Thanks,
Tirumal

hi,
Conditional Receiver determaintion is possible only on the Source Message. the reason being that the integration engine will first execute receiver determiantion--> interface determiantion --> message mapping.
If you are getting the IDOC as a source, then you can use the XPATH to do conditional receiver determination.
Regards,
Bhavesh

XPATH and Receiver Determination

In Reference to forum thread : Conditions in Xpath (Receiver determination)
Suppose I have MT as
MT_Pickfile
 |_Header
 |_Body
 |_Trailer
And i need to check;
(field3 = "100" or field3 = "200" or field3 = "300" ) and(field5 = "AA" or field5 = "BB" or field5 = "CC")
field3 is in Header and field5 is in Body
I tried giving
/p1:MT_Pickfile/Header[(field3 = "100" or field3 = "200" or field3 = "300" )] and /p1:MT_Pickfile/Body[(field5 = "AA" or field5 = "BB" or field5 = "CC")] EX
It doesnt work. But then if both field3 and field5 are in Header then it works (as had been the case in the above mentioned thread which Stefan Grube replied to) i.e. to say
/p1:MT_Pickfile/Header[(field3 = "100" or field3 = "200" or field3 = "300" )] and [(field5 = "AA" or field5 = "BB" or field5 = "CC")] EX
Can anybody put in their suggestions ?
Thanx in Advance,
ShaBZ

Hi Shabarish,
It is not possible to have and or or outside the brackets [].
Try following:
/p1:MT_Pickfile[(Header/field3 = "100" or Header/field3 = "200" or Header/field3 = "300" ) and Body/field5 = "AA" or Body/field5 = "BB" or Body/field5 = "CC")]
Another idea:
Write two lines in receiver determination (use insert expression):
1. line:
/p1:MT_Pickfile/Header[(field3 = "100" or field3 = "200" or field3 = "300" )]
2. line
/p1:MT_Pickfile/Body[(field5 = "AA" or field5 = "BB" or field5 = "CC")]
Hope that helps
Stefan

IDOC error "receiver determination" while sending from R3 to XI

Hi all,
I'm trying to send an IDOC from R3 to BW thro' XI.
I created 2 business system for R3 & BW.
I created communication channel for receiving BW with IDOC adapter.
I created the receiver determination, interface determination & receiver agreement.
I also used IDX1,IDX2 to configure the port to load to IDOC.
When I send IDOC from R/3, It gets received in XI with the error message
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
It didn't select the receiver.
Am I missing anything? Can anyone help me with this.
The same problem exists even I tried to get IDOC into a file in XI.
I appreciate all your help.
thanks
felix.

Hello Ujjwal,
Receiver is already defined in "Receiver Determination".
Even I refreshed CPA Chache many times but getting same error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks.
RP

ENHANCED INTERFACE AND RECEIVER DETERMINATION

1)what is the use of enhanced interface determination and enhanced receiver determination and in scenarios we will use them and in what conditions ,and what differentiates it from standard interface/reciever determination?

1. Standard receiver determination to specify the receivers of the message (and optionally routing conditions) manually.You can specify receiver parties and receiver services. To specify the receiver in more detail, you have the following options:
● Select the receiver from the Integration Directory
● Specify a constant value for the receiver
1.2You also have the option of specifying the conditions to be applied when forwarding a message to the receiver(s) in a receiver determination.
Generally, a condition relates to the contents of a message; if a specified condition is fulfilled for a particular payload element (the corresponding element has a certain value, for example), then the message is forwarded to the specified receiver(s).
Enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtimeInstead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
A typical usage case is if you do not yet know the names of the receivers at configuration time. In this case, you can define a mapping program, for example, which reads a list of receivers from a table or from the payload of the message at runtime.
2.Standard Interface Determination :You can specify to which inbound interface at the receiver the message is to be sent at runtime. You also have the option of specifying a mapping and (when multiple inbound interfaces are defined) a condition for each inbound interface.
2.1 n an enhanced interface determination, you do not enter the inbound interfaces manually, but first select a multi-mapping. You get the inbound interfaces from the target interfaces of the multi-mapping. The inbound interfaces are determined at runtime during the mapping step.
You typically use an enhanced interface determination if the source message has an element with occurrence 0 ... unbounded (for multiple items of a data record) and you want multiple messages (for the individual items) to be generated at runtime.
for receiver determination try this link also
http://help.sap.com/saphelp_nw70/helpdata/en/43/a5f2066340332de10000000a11466f/frameset.htm
Regards,
Mandeep Virk
*Reward if Helpful*

Automatic Payment Process through IDOC and Receive Message Acknowledgement and BANST file format

Hi Experts,
We are implementing payment process to our client through Idoc.
Normally the process will go like below. Once Payment Initiated --> IDoc will generate --> This Idoc process through PI system and send to Bank.--> Once payment data received bank --> it will generate acknowledgement receipt and Bansta file and send it PI system --> This PI system system again send it --> SAP system. Here I want to know the required configuration from PI system to SAP system while receiving acknowledgement and Bansta file. And let me know if u guys have steps...
Thanks,
Raviram

Hi,
>is possible using the fileadapter to read this file and with pass it throug PI to IDOC receiver adapter without any mapping?
yes
>In that case what should the Message Type we are using in the file-sender adapter look like?
If you have no mapping it doesnt matter, the message type will not be validated during runtime. You can take the IDoc type imported from the SAP system
Regards,
Udo

Sender IDOC and Receiver Soap

Hi,
I dont Know how to do the Scenario.
I never used Sender IDOC in XI.
I am Using Now.
Cany Any one of u Explain in Detail about Sender IDOC How to configure..
I Dont Know How to define Logical system and where to define and when to use.
I need compl,ete Information/
Ponts willbe awarded.
Regards,
Jayasimha
[email protected]

Hi ,
Go thru this Blog for posting the IDoc from R/3 to XI.
<a href="/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi Steps for Posting IDOC's</a> by Ravikumar Allampalam
<a href="/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi Configuration for Pushing IDOC's from SAP to XI</a> by Swaroopa Vishwanath
This Blog explains the RFC to WEBSERVICE scenario.
Configure your scenario like this except making the changes to the sender as IDoc instead of RFC.
<a href="/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1 -> XI -> WebService - A Complete Walkthrough (Part 1)</a> by Shabarish Vijayakumar
<a href="/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2 -> XI -> WebService - A Complete Walkthrough (Part 2)</a> by Shabarish Vijayakumar
Regards
Santhosh
Remember to set the thread to solved when you have received a solution
[url=Use a Good Subject Line, One Question Per Posting - Award Points; Use a Good Subject Line, One Question Per Posting - Award Points[/url]

Multi Mapping with out BPM and Receiver Determination Condition

Hi Masters,
My Requirement Was:
Proxy will send the data to XI system, Based Customer group number[1000,2000,3000,4000], I need to split the message into 4 messages, and sent to 4 Different location, based on Customer Group condition.
For message split, I fallowed below weblog.
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
Problem is file split correctly, but data goes to all customer groups..
EX
If they send the customer group 1000, I need to send the customer group 1000 file to BS1[Business Server1],
If they send the customer group 2000, I need to send the customer group 2000 file to BS2[Business Server1],
Please guide me,
Thanks,
ANU-

Hi,
Develope it like follow.
Source Structure- Same for everything.
Create 4 different structures for all targets, create 4 different msg types, 4 inbound message interface ( i think you are creating single Message type now, that is the mistake)
In message maaping, add 4 target message types in same MM.. i hope i am clear.. ( same like in blog /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible he has created 2 message types USER_1 and Employee)
keep occurence of all of them 0 to unbunded (not necessary)
Now create mapping for each message type (same like USER_1 and Employee, imagine them like different message types virtually).
Map message type with the source field and mention the condition which you want test using graphical functions. i will say if x e equla to 1 creatif --> target.
I hope i m clear till now...
thanks.

Receiver determination doesn't work for same IDoc type but in differentSWCV

hi guys,
we have an emergency now. Receiver determination doesn't work for same IDoc type but in different SWCV.Please check below for detail.
1. The process flow is : R/3 IDoc -> XI -> Third party system
2. In previous release R13, IDoc ORDERS05 was imported and used in XI and software component version is R13. And receiver determination was created.
3. Now, in new release R17, IDoc ORDERS05 was imported from R/3 to XI again and software component version is R17. And in R17, the receiver determination created in R13 was used for both old interface(R13) and new interface in R17.
Then we encountered the problem, both interfaces doesn't work now, even we deleted the receiver condition(In R13, IDoc ORDERS05 was sent to system A, and in R17 IDoc ORDERS05 was sent to system B, RCVPRN was used as an condition).
Does anyone encounter this problem? really need and appreciate your help.
-Eddie

information from monitor:
Status Sender Service Sender Namespace Sender Interface
reschedul XXXCLNT100 urn:sap-com:document:sap:idoc:messages ORDRSP.ORDERS05
columns for "Receiver Service","Receiver Namespace", "Receiver Interface" are blank
And then double click records in monitor, go into detail information...
Normally there's lots of setps existed, such as
Inbound Message ( CENTRAL )
Receiver Identification
Interface Determination
Receiver Grouping
Message Branch According to Receiver List
Technical Routing
Call Adapter
But now there's only one setp -
"Inbound Message ( CENTRAL )" existed, no any another setp..., and payload in inbound message looks good.
And in SMQ2, I checked the queue information, found there's an error - "An exception occurred that was not caught." No any other detail information for this error.

Receiver Determination Condition and XPATH

Hi Everyone,
I have a receiver determination with conditions and can not figure out why one thing is working, and the other isn't.
As suggested in the following forum post, XPATH and RECEIVER DETERMINATION, I had to do the following to my XPATH expression to make it work. The full xpath expression is this:
(/p1:RenExtract_MT/Detail/CompanyCode = 9740)
where
p1 = http://company.com/xi/fin/
but whenever I put in a condition it could not find a receiver.
Hoewver, when I did this:
//CompanyCode
it worked.
I did everything through the condition editor, many times, and didn't type anything in myself. Is there a length limitation or something (I removed some data in here, the expression is really longer!).
Any ideas?
Peter

Hi Peter,
I do not have an explanation for this wired behaviour.
But I can assure your, that your working solution, the //something expression is a good one and not inferior to a solution using an explicit, absolute path.
Why is that: I can remember some benchmarks, where the //something expression always outperformed the other one.
Regards
Gregor

Flat Idoc and receiver determination

Similar Messages

Maybe you are looking for