Interface in Receivables

Hi,
Could anyone tell me what the interfaces available in the Receivables.
Srikanth

Interfaces are documented in the module user guides available at http://www.oracle.com/technology/documentation/applications.html
HTH
Srini

Similar Messages

PI 7.1 Sender Interface and Receiver Interface gets interchanged

Hi All,
I m facing a strange problem in PI 7.1
For many of my scenarios, the Sender Interface, sender namespace and receiver Interface, receiver namespace information gets interchanged and displayed incorrectly.
But sometimes its working fine.
When we analysed the Log messages, found that, after xml validation step, the sender and reciever interface gets interchanged.
Any idea why this happens?
How to rectify this error?

Aarthi,
Please check your message interfaces once again. Sender is outbound and Receiver is inbound.
Also please check your receiver determination.
Regards,
---Satish

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.

API/Interface for receiving an RMA return line

Hello,
Is there API or an interface available in 11.5.10 that will allow a return line/RMA to be received? The documentation for the receiving interface says that returns or receiving against RMAs is not supported.
Thanks,
Gary

Could you please provide more information, on how exactly you were to do this.
I mean the interface tables you used and the name of the interface program that was run.
Regards,
Shashi
Edited by: user1163046 on Feb 1, 2011 4:51 AM

Not getting Service interface in receiver side

Hi,
I am working on a newly configured PI server.
Here, I am working on a synchronous SOAP to RFC scenario from third party to ISU.
From the Display WSDL option of ID I have created a wsdl file and testing the scenario by importing wsdl file into SOAP UI. When I am sending some request from SOAP UI , I am getting proper response message ; that's mean interface is working fine and properly hitting the RFC in ISU.
I can see the message in SXMB_MONI of my PI server . But I am not getting the message in SXMB_MONI of ISU server . Even in SXMB_MONI of ISU I am not getting the inbound service interface also .
What can be the possible reason . As I am working on a totally new server should I do any configuration in the server to get the SI in receiver side.
Please help.
Thanks in advance.

Hi,
Please check if Sync logging is enable in ISU. refer the below blog
XI: I cannot see some of my messages in the SXMB_MONI
regareds,
Harish

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*

Interface - Payment received from 3rd party

Good day,
Can you please assist? Is there a standard IDOC that I can use to post payments to IS-U. We will receive the payments in a flat file format from the 3rd party.

Hi,
If you go into IS-U report program RFKKZE00 (Payment Lot transfer, IS-U Transaction code FPB3), read the documentation on what file format is expected by the program. Here is an extract of the first few paragraphs of the documentation:
Payment Lot Transfer
Description
This report transfers payment data and creates one or more lots for payments, checks, payment orders, or credit card payments.
To do this, it executes the following steps:
1. Read the specified application server file and check the data contained therein
2. Create one or more lots as long as the data records are correct
3. Close and post the created lots as long as the relevant indicator is set
Data records that contain errors are saved separately, and can be transferred after they have been corrected.
Output
The report outputs the following information in a log:
The number of data records (payment items) containing errors, their numbers and their lines in the application server file
A list of the lots created and their status
You can select an extended log.
Requirements
The report transfers the payment data from the application server file. Note the following for this file:
All fields must have character format.
Every line can only contain one structure.
The report expects the following for each file (take note of the sequence):
One file header record (BFKKZGR00 structure) per file
One payment lot header (BFKKZK structure)
Any number of items (structure BFKKZP)
Several lines with additional selections (structure BFKKZS) and enhancements to the note to payee (structure BFKKZV) can follow each item.
You can include data for any number of lots in a file. However, you have to ensure that you always specify the lot header first and then the related line items.
If you transfer a check lot, the BFKKZK-XSCHS field must be filled with X.
If you transfer a payment order lot, the BFKKZK-XZAUS field must be filled with X.
If you transfer a credit card lot, the BFKKZK-XCRDS field must be filled with X.
You can generate a test file using report RFKKZEDG.
You can display or change transfer files using report RFKKZEDA.
I hope this helps.
Ivor Martin

Receiver Determination and Interface Determination Condition conflict in ICO

Hi,
I found a strange issue today while configuring two receivers using the Receiver and Interface Determination conditions.
Sender - Proxy Service
Receiver1 - ReceiverA
Receiver2 - ReceiverB
Receiver Determination Condition : When Field1 = 100, message should flow to ReceiverA and ReceiverB
Interface Determination Condition (ReceiverA) : When Field1=100 and Field2=50 message should flow to a specific interface in ReceiverA
There is no Interface Determination condition for ReceiverB, for all messages having Field1=100, it should go to ReceiverB.
Test Scenarios:
1) Field1=100, Field2=50 : Message flows successfully to ReceiverA and ReceiverB
2) Field1=100, Field2=89 : Message fails to process from ECC itself throwing Interface Determination not found error. Ideally this is a positive scenario for ReceiverB and it should send the message to ReceiverB without any errors. But, this did not happen in this case
I tried the same by configuring the conditions completely in Receiver Determination itself without using the Interface Determination, it worked perfectly fine. But, just wanted to understand that if this is an expected behavior.

Hi Sherin,
As there are two receivers Receiver A and Receiver B.You need to create two bussiness components and two communcication channels for two receivers and one Reciver Determination, two Interface Determination,two Receiver Agreement.In Receiver Determination you need to keep the below and condition.
In the above screenshot the two receiver are Receiver B and Receiver C and Field 1 is Key_Value and Field2 is Emp_ID.
If the Key_Value=100 and Emp_ID =22 then the message should go to both the receivers B & C by keeping the following AND condition
If the Key_Value=100 and Emp_ID is not equal to 22 then the message should go only to Receiver B by keeping the following condition
You need not keep any condition in Interface Determination just create 2 Interface determination for two receivers.
Hope this helps you.
Thanks,
Durga.

Multiple Receiver Interface in integrated config(AAE)

Hello Experts,
We have a SOAP to RFC synchronous interface.There is a requirement where we have a Single Sender interface(Single Sender System) and based on the value in Payload we have to select either of two different Receiver RFC interface(Single receiver System). I am not sure whether we can select either of two different RFC interface for the same Receiver system in an Integrated Configuration(AAE).
Appreciate your help!!!
Thanks.

Hi,
Alternatively, you can opt to use multi-mapping, with the occurrences of each message set to 0..1. The interface is triggered via conditions. In ID, you would be declaring an Enhanced Interface Determination.
Hope this helps,

Interface Determination causing issue in Receiver Determination

Hi
I am having an issue with interface and receiver determination as follows:
- Inbound message may be sent to two receivers.
- Message gets sent to first receiver, fails during interface determination. There are multiple inbound interfaces found based on a set of XPATH conditions. This creates an error 'Inbound interface found more than once for outbound interface '. That is itself is not the issue.
- Issue is that the message is stopped from going to the other receiver even if there are no issues in the interface determination for that receiver.
Is there a way to resolve this? Appreciate any help. Thx, Duncan

Again, thanks for the replies.
MONI for RD
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="3" type="T">...create rule engine</Trace>
<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE COSTCENTRE or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTERPLANT or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTERPLANT_ONESTEP or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTRAPLANT or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTRAPLANT_ONESTEP or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice")% EX or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:inventoryActivityOrInventoryStatus")% EX</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:despatchAdvice</Trace>
<Trace level="2" type="T">......extracting values found: 0</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="2" type="T">...valid Receiver with Condition: - GLR430</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 2</Trace>
<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE COSTCENTRE and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTERPLANT and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTERPLANT_ONESTEP and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTRAPLANT and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTRAPLANT_ONESTEP</Trace>
<Trace level="2" type="T">...invalid Receiver: P_3PL_XML_ME_ODTH - despatchAdviceToE1EDT20</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 3</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: P_3PL_XML_ME_ODTH - S_HTTP</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:2</Trace>
</Trace>
</Trace>
</Trace>
Here, you see that both receivers are found.
MONI for ID
<Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION" />
- 
<Trace level="1" type="Timestamp">2007-02-26T20:06:49Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...create rule engine</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p1:inventoryActivityOrInventoryStatus/inventoryDocumentType")% CE INVENTORY_STATUS</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:inventoryActivityOrInventoryStatus/inventoryDocumentType</Trace>
<Trace level="2" type="T">......extracting values found: 0</Trace>
<Trace level="2" type="T">...invalid InbIf: WMMBXY.WMMBID01</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p1:inventoryActivityOrInventoryStatus/inventoryDocumentType")% CE INVENTORY_ACTIVITY</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:inventoryActivityOrInventoryStatus/inventoryDocumentType</Trace>
<Trace level="2" type="T">......extracting values found: 0</Trace>
<Trace level="2" type="T">...invalid InbIf: WMMBXY.WMMBID01</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice/receivingAdviceItemContainmentLineItem/purchaseOrder/documentReference/uniqueCreatorIdentification")% EX</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice/receivingAdviceItemContainmentLineItem/purchaseOrder/documentReference/uniqueCreatorIdentification</Trace>
<Trace level="2" type="T">......extracting values found: 2</Trace>
<Trace level="2" type="T">...valid InbIf with Condition: WMMBXY.WMMBID01</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice/carrier/additionalPartyIdentification/additionalPartyIdentificationValue")% CE SHUTTLE</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice/carrier/additionalPartyIdentification/additionalPartyIdentificationValue</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="2" type="T">...valid InbIf with Condition: WMMBXY.WMMBID01</Trace>
</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Here, you see that the ID runs for the first receiver. It hits an error because two conditions on the ID for the first receiver are satisfied. However, it then stops rather than allow the processing for the other receiver to continue.
Any ideas? Thx, Duncan

How to add Two Interface Mappings to One Receiver(BPM) Help needed urgently

I have a requirement where i get a flat file and split into multiple files and send to BPM.
For each split file I created Interface Mapping using Java Mapping Program.
In the Configuration how to add more Interface Mappings?
Thanks for your help in advance.
Regards
Sudha

You can use Enhanced Interface Determination to split one message to Multiple hence to multiple Interfaces.
You have to change the Occurance of Messages in Message Mapping and their Corresponding Interfaces in Interface Mapping. That would create Multiple Files with Multiple Interfaces to Receiver (BPM)
1) You need not to use Multilpe Interface Mapping
2) You will use Extended Interface Determination for this.
regards.
Jeet.

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 **

Receiver Determination and Interface Determination

Hi,
Please, can anyone explain what is the concept of 'Receiver determination' and 'Interface Determination'?
Thanks,
Harikumar. S

Hi,
>>>>Receiver determination
its about finding the receiver system for particular source system and outbound interface.
Suppose,you want to send data from file->XI->SAP and CRM based on some condition
in this scenario you need to determine whether to send file data to SAP or CRM system,this decision you will do in Receiver determination
in Receiver determination screen you need to provide the following details
1.Source system(ex: File system)
2.Outbound Interface(File Message Interface)
3.condition and receiving system(ex:if some x field value in source payload is 1 go to SAP elseif '0' go to CRM system)
>>>>>>Interface Determination
suppose in above scenario you determined the receiver i.e SAP,you will have number of IDOCs (Inbound Interfaces)in SAP.
so to which IDOC you will send file data?This decision you will make in Interface determination(we can it as Inbound Interface determination).if you find the IDOC is CREMAS then how will transfer file structure data to IDOC structure? answer is Message Mapping
From all the above decisions you need to provide following details in Interface determination screen
1.Source System
2.Outbound Interface
3.Receiver System
4.Inbound Interface(IDOC type)
5.Message Mapping(i.e file to IDOC)
Even in Interface determination you can specify the condition to select Inbound Interfaces(ex.IDOCs)
if you have any doubts please lets know.
Cheers,
Jag

Receiver Business System Connot find Inbound Interface - IDoc to File

Hi Everyone,
I am doing IDoc to File Scenario.....Idoc got triggered from SAP system and successfully posted to SAP PI.
Now when I check in T-Code IDX5 in PI, I got one message. When I double click that I am getting following error:
<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:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also When I am selecting Receiving Inbound interface for Receiver system, I am not getting any interface by default.
Please help me out.
Thanks & Regards,
Sudheer

Hi everyone,
Thanks for your quick responses.
Actually I am doing IDoc to File Scenario from blog which consists of Conditional Receiver Determination
"SNDPFC"
Here is the Explanation given in that blog:
In most instances, a new Receiver Determination would be created. However, given that in this scenario the combination of the sender service (i.e. u201CGL1u201D) and interface (i.e. u201CMATMAS.MATMAS04u201D) will be used by every student, each student will instead be adding their receiver service to an existing Receiver Determination
11. In the Condition column on that same line, left click on the question mark help icon
12. In the following Condition Editor pop-up window, left click on the help icon in the u201CLeft Operandu201D field
13. In the following Expression Editor pop-up window, select the u201CContext Objectu201D radio button
14. Use the drop drown to locate and select the u201CSNDPFCu201D field and u201COKu201D
15. Back in the Expression Editor, leave the u201C=u201D Operand as is
16. Enter your group number in the u201CRight Operandu201D and u201COKu201D
17. u201CSaveu201D and validate your u201CConfigured Receiversu201D as seen below:
I did not understood this Conditional RD.
Apart from this all configuration are correct.
Thanks,
Sudheer

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

Interface in Receivables

Similar Messages

Maybe you are looking for