HTTP to RFC Interface Determination problem

Hi experts,
I am doing HTTP <-> RFC scenario mentioned in blog
/people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit
almost everthing is done; but while configuring the interface determination, i am not able to see the inbound interface.
your valuable help would be appreciated
Regards
Sumit Bhutani

Hi Bhavesh,
Thanks for your quick response; this problem has been resolved, but while testing my scenario using RWB i am getting this 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="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to read payload from the message object</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Please suggest on this
Thanks
Sumit

Similar Messages

Interface determination problem

Hi experts,
I hae a scenario in which i need to split a given message to multiple message(1:n) multimapping.
I am doing without BPM,and my scenario is working fine and good when i test in message mapping giving various inputs.
when i test in configuration or runtime it throws an error saying that interface determaination not found
The funniest part is if i give some payload it will work fine,and determines the interface....
but for some conditions it shows interface determaination not found....
Can anyone throw light on this problem please..
Thnks,
Babu

The funniest part is if i give some payload it will work fine,and determines the interface....
but for some conditions it shows interface determaination not found....
This would mean that for some payload the condition is not met. Verify that the payloads for whom you are receiving the error are having the fields/ values that are required to satisfy the condition.
Regards,
Abhishek.

EOIO Problem in the Interface Determination

Hi All,
I have two different source systems (BUSSYS111 , BUSSYS222) and one target system BUSSYS999 (SAP System). I have two different mappings in each interface
Interface 1:
BUSSYS111 -> BUSSYS999 (file1 -> RFC, file1 -> JDBC, without BPM, split mapping)
Interface mappings:
Flow1 : BUSSYS111_File_To_BUSSYS999 (FILE -> RFC)
Flow2 : BUSSYS111_FILE_TO_BUSSYS111 (File -> JDBC)
Flow2 should execute only if the Flow1 is successful (RFC call is successful).
Interface Determination for Interface 1
Sender: BUSSYS111
Interface: Source Interface1
Receiver : BUSSYS999
Maintain Order at runtime Checked.
Receiver Interfaces
BUSSYS111_File_To_BUSSYS999 (Result of Flow1 & Flow2)
BUSSYS111_FILE_TO_BUSSYS111
The queue that is getting generated is *XISERIALIZE0011_BUSSYS999*_ (EOIO)
Interface 2:
BUSSYS222 -> BUSSYS999 (file1 -> RFC, file1 -> JDBC, without BPM, split mapping)
Interface mappings:
Flow1 : BUSSYS222_File_To_BUSSYS999 (FILE -> RFC)
Flow2 : BUSSYS222_FILE_TO_BUSSYS111 (File -> JDBC)
Flow2 should execute only if the Flow1 is successful (RFC call is successful).
Interface Determination for Interface 1
Sender: BUSSYS222
Interface: Source Interface1
Receiver : BUSSYS999
Maintain Order at runtime Checked.
Receiver Interfaces
BUSSYS222_File_To_BUSSYS999 (Result of Flow1 & Flow2)
BUSSYS222_FILE_TO_BUSSYS222
The problem here is in both the cases above, the interfaces seems to be independant. But sometimes for some messages the same queue *XISERIALIZE0011_BUSSYS999*_ is used and for some, a different queue is generated.and if the same queue is used in both the cases, the first interface fails, then the second one is going into holding state.
Can any one help to resolve this issue without going for the BPM (as it would be a design change) and it is already in production.
Thanks in Advance
Anil

Hi,
in the documentation
Interface Determination - Enabling Application-to-Application Processes - SAP Library
its mentioned as
You specify manually to which inbound interface at the receiver the message is to be forwarded. You can also specify the mapping that is to be executed. If you specify more than one inbound interface, you can specify conditions for forwarding the message to the inbound interfaces. These conditions are evaluated at runtime.
so better to raised it to SAP.
Reg,
avinash M

Problem in Interface determination for multiple MM

Hi experts,
i designed an IDOC to Jdbc scenario.
The particular thing is that I have TWO message mappings to apply for the same source and same target.
Hence, I have in my directory two scenarios with :
- same Reveicer Determination
- same Interface Determination
- differents Receiver agreements (i have two Communication Channels)
In my interface determination, I have configured a standard Interface determination with my two interface mappings to apply.
My problem is when I send an idoc, the result should be for my two interfaces differents payloads to inject to the database, but I get the same payload for both interfaces with the same namespace...it looks like it only use one Interface mapping instead of both...
It is driving me crazy...
Any help would be greatly appreciated
Kind regards,
Jamal

Hi,
i have the same receiver.
I do have two interface mappings in my interface determination. The problem is that it uses the same for both interface.
If I use enhanced ID, i can only specify one Interface mapping.
What I want :
- sender A - Message mapping 1 - receiver A
- and also sender A - Message mapping 2 - receiver A
when the idoc is sent.
what I have right now (though my configuration seems to be right) :
- sender A - Message mapping 1 - receiver A
- and also sender A - Message mapping 1- receiver A
Thanks a lots,
Jamal

RFC to WebService Receiver Determination Problem

Hi,
I am doing RFC to WebService with the help of this weblog
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2 In Interface Determination - when picking Inbound interface is coming as No objects found.
How to resolve it?
regards,
Ansar.

Ansar,
In RFC to Web service the inbound interface should be the WSDL.
Did you import WSDL under 'External Definations'.
After importing you need to create a inbound message interface of the Message within the WSDL that you need to use.
Regards,
Ashish
Message was edited by:
Ashish Goyal

Problem in Interface Determination

Hi All,
While trying to do webservices using webdynpro i was able to do the repository part without any errors but while trying to do configuration i'm facing a problem in interface determination.
I'm unable to find my interface mapping in the interface determination.
While trying to search for the interface mapping its showing me as "no objects found".
Could anyone help me out in this regard.
Thanks in Advance
Madhu

Hi,
As said by Moorthy, you should able to see interface mapping.You just Copy the interface mapping name from IR and insert at Interface Mapping in interface determination.To insert Interface mapping , right click choose Insert option from context.Save & activate Interface determination.If it is activated successfully every thing is ok.Otherwise once you should check as said by Moorthy and check Namespace of Interface too.Hope this will solve your problem.
Cheers
Tiger Woods
Note:Give the points for helpful answers

Condition in Interface Determination giving problem - URGENT!

Hello experts,
In my scenario I have one idoc posted from the SAP R/3 and I need to write max of 3 files in the same receiver file system based on some condition i.e. based on the value of some field in the incoming idoc.
What I have done is in my interface determination, I have given that condition for all the 3 inbound interface. that is in the condition field in interface determination, for each inbound interface I chose that perticular field in idoc and gave the condition for which that interface should run.
Now when I am pusing an idoc, if that idoc contains only one condition than my interface is working fine by creating only that file. I have checked this for all 3 files by sending 3 different conditions in 3 idocs. It creates 3 different files for 3 idocs.
But if I send all 3 conditions in one idoc (since idocs can have multiple segments - in few segments i am giving one condition and in few others the 2nd conditon and in the rest the 3rd condition), I expect all 3 files to be created in my file system with data fulfilluing only that perticular condition. but this is not happening. In interface determination only one of the 3 is getting executed. Rest 2 is ignored and i cannot trace it anywhere (RWB, SXI_MONITOR etc)
I have tried all possible combinations but this is not working if i send in 1 single idoc?
Please help me in solveing this as this is a production issue and they cannot send 3 diffent idoc for 3 conditions. Where am i going wrong?
Waiting for your responses.
Thanks,
Yash

Hi Jakub,
My scenario is one idoc say IDOC 1 and 3 files says FILE1, FILE2 and FILE3. Now the target message type for these three files are MT_FILE1, MT_FILE2 and MT_FILE3 (3 different message types).
The only catch point here is i have 2 different interface for creating FILE3 (same message type but different mapping, interface etc). Each interface is based on a condition.
Now when I send one doc which includes condition for only FILE1 and FILE2, it creates 2 file.
If I have condition of only FILE3 (one condition of FILE 3 as FILE3 has 2 conditions) and FILE2, it creates both files.
If I have both condition for FILE3 and FILE2, it creates FILE3 with only one condition and FILE2.
If i have condition for FILE1, FILE2 and both conditions for FILE3, it creates FILE1 and FILE2 both no FILE3 at all.
I guess the problem might be that I have same message type for both conditions for FILE3 but I m not sure. Let me try by creating seperate message type for both and see. But is there any other problem?
Yash

Mysterious routing problem / interface determination

Hi,
I have a very very strange routing problem with XI.
A message is sent from R/3 to XI and then send via adapter to an external party. The routing is configured well. But sometimes I have the following problem:
A message is received by XI (from R/3). The receiver is determinated. Although an interface determination and receiver agreement is configured, the trace shows "no interface determination fpr party xyz and service abc found". The very strange thing is that finally the receiver interface DELINS.DELFOR01 with namespace urn:sap-com:document:sap:idoc:messages is set!!
Finally, the error message is "no receiver agreement found for "... DELINS.DELFOR01, urn:sap-com:document:sap:idoc:messages", which is reasonable because this receiver interface has never ever been configured!
Any idea why the interface determination cannot be found and nevertheless a completely wrong receiver interface is set?
This error occurs just sometimes for certain partners, but not always with all messages for these partners!
Help appreciated!
Christopher

Hi,
all routing objects are 100% correct. Particularly the receiver service has definitely no DELINS.DELFOR01 interface, but nevertheless the Integration Runtime tries to send the message to this interface. Another strange thing is that in the trace there is the warning "no interface determination for party xxx and service xxx found".
By the way: The Receiver Determination was configured to terminate message processing when no receiver can be found.
CHRIS

HTTP with RFC destination problem

Hi,
We're doing an SAP R/3 --> XI --> External System scenario. We've had no problems making the SAP R/3 to XI work. For XI to External System, we're using the Plain HTTP adapter with an RFC destination. The Server, Intermediate and Root CA of the External System have been already installed on the ABAP layer of XI using the transaction STRUST/STRUSTSSO2 . The Server Certificate and Root CA of XI have also been installed on the External System Server. The problem is that everytime we test the RFC destination, we are still getting an ICM_HTTP_SSL_ERROR
Additional Parameters:
SSL has been enabled on the RFC destination
All three certificates can be found in STRUST
Regards

HI
is the certificate same for both of you have installed external system certificate and external system have PI certificate
Check SAP note 510007
Check similar threads
ICM_HTTP_SSL_ERROR
ICM_HTTP_SSL_ERROR for plain HTTPS with RFC Destination type G
Thanks
Gaurav

HTTP to RFC (Calling BAPI)

Hi,
I am working on creating a Purchase Order in SAP system by calling BAPI's from XI using RFC adapter.
I defined the following in IR:
1. Created data types for mapping with BAPI request and response.
2. Created messsage types and assigned corresponding data types to the message types.
3. Created one Message Interface (Outbound/Synchronous), Output message - request message type, Input message - response message type.
4. Create request and response message mapping and one Inteface mapping (with request tab and response tab) properly assigned.
Defined the following in ID:
1. Created HTTP business system (no communication channel)
2. Created communication channel for receiving system (SAP).
3. Created receiving determination and interface determination, receiver agreement, no sender agreement.
I sent XML message (required data to create purchase order) from HTTP client but I am getting the response as <b>Unable to determine name of mapping program</b>, my Interface Determination has proper Inbound Interface (ZBAPI_PO_CREATE) and Mapping program (PO_I_MAP). But Why am I getting the reposnse as I said above in my HTTP client?
Appreciate your help,
Thanks and Regards,
Jagadish.

Hi Jagadish,
The error lies in Message Mapping .So please check it once again .You have mentioned your steps it seem there is problem in Message mapping..
Please look at the following Steps..
IR:
1.Import Corresponding RFC(BAPI). No need to create Interface Objects( Data type, Message type,Message Interface ) for SAP( RFC ) system..
2.Create Interface Objects For HTTP System.As you told it is synchronous.
3.Perform Two Message Mappings
(A).HTTP Request <--> RFC Req
(B).RFC Response<-->HTTP Res
4.Perform one Interface Mapping which includes Request and Response Mappings ..
5.Activate all objects..
ID : what you have done is ok..
URL: http://<hostname:port>/<path>?<query-string> Make sure your URL is correct or not for( sender HTTP )..
I think it will hepl you , if it is solved please assign points . If you have any doubt you can call me...
Thanks
N.Prasad Babu
iGATE Global Solutions Hyderabad : 98490 65377

XPATH to determine node name in condition of Interface determination

Hi,
does anybody out there know whether one can use a condition such as "name(/p1:Envelop/p1:Body/*)" to retrieve the name of the first element underneath the Body structure which is usually the payload. In the example below. I'd like to retrieve "ns0:BAPI_USER_GET_DETAIL" or just "BAPI_USER_GET_DETAIL" which I would like to than compare in my "=" condition.
<?xml version="1.0" encoding="iso-8859-1"?>
<sap:Envelope xmlns:sap="urn:sap-com:document:sap" version="1.0">
<sap:Header xmlns:rfcprop="urn:sap-com:document:sap:rfc:properties">
    <saptr:From xmlns:saptr="urn:sap-com:document:sap:transport">BC1</saptr:From>
    <saptr:To xmlns:saptr="urn:sap-com:document:sap:transport">BC2</saptr:To>
</sap:Header>
<sap:Body>
     <ns0:BAPI_USER_GET_DETAIL xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
      <CACHE_RESULTS/>
      <USERNAME>bauerd</USERNAME>
     </ns0:BAPI_USER_GET_DETAIL>
</sap:Body>
</sap:Envelope>
I have a client that once to migrate his SAP BC interfaces to PI without having to change the sending application which is a CICS mainframe application. The mainframe application invokes various BAPI's by just passing in a different payload into the above envelope. The payload is always the request structure for the BAPI. The message is send synchronously to SAP BC which than calls the BAPI and returns the response to the caller, again in form of the above envelope and as payload the BAPI response structure.
To convert this to PI I have to be able to initiate different interface mappings depending on what BAPI is requested. This is pretty straight forward as there are no special mapping transformation taking place in SAP BC for both the BAPI request and response. However I need to determine what interface mapping to call depending on BAPI requested by the CICS application.
As said the customer does not want to change the sending application. The only part we are allowed to change is the URL which changes from SAP BC to the SAP PI Plain HTTP sender adapter. The post will always use the same outbound message interface. Therefore I can't use SAP PI's standard receiver determination. Using this adapter I will also be able to get access to the whole message envelope as outlined above.
I already got all of this working nicely with the exception that I can't determine what BAPI is requested and therefore what interface mapping I have to trigger in my interface determination.
Has anybody used a condition as above and if so how should it look like in the condition editor. The one outlined above does not seem to work. However it is also not failing in PI.
Also I don't want to change my approach for doing this. However if it is not possible to retrieve the node name using the xpath statement (as outlined above) in the condtion editor than I will have to look for a different approach to resolve this problem. Any suggestions would than be more than welcome.
Many thanks in advance.
Dieter

If the structure is not too big, you can use:
//ns0:BAPI_USER_GET_DETAIL EX
otherwise take the full path:
/p1:Envelop/p1:Body/ns0:BAPI_USER_GET_DETAIL EX
The namespaces have to be declared.
Regards
Stefan

HTTP to RFC synchronous scenario Issue

Hi Folks,
Currently I'm working on a HTTP to RFC synchronous scenario. Everything went well till i triggered the message. While triggering the message i'M GETTING IS AS BELOW
Result:
http-Status: 500 Internal Server Error
Payload:
<SAP:Error>
<SAP:Category>Application</SAP:Category>
<SAP:Code>MAPPING.EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_Comcode_</SAP:P1>
<SAP:P2>java.lang.NullPointerException</SAP:P2>
<SAP:Stack>java.lang.NullPointerException thrown during application mapping com/sap/xi/tf/_MM_Comcode_: </SAP:Stack>
</SAP:Error>
I also tried executting the message testing tool to see the trace and the below result I got
<?xml version="1.0" encoding="iso-8859-1" ?>
- <Top>
<First>BeginTrace</First>
<Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping is determined</Trace>
<Trace level="1" type="T">Interface Mapping http://www.http-rfc.com IM_Comdet</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping CA9DBC0BCB27311FBAA3C4CE387CEC3B</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping 226C2EB123A711DFC0F4FAEBC0A80020</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_Comcode_</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
<Trace level="2" type="T">Mode 3</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_Comcode_.</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_Comcode_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_Comcode_ completed. (executeStep() of com.sap.xi.tf._MM_Comcode_</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
<Trace level="1" type="E">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>
</Top>
But still I'm not able resolve this issue kindly help.
Regards,
Santosh

Looks like there is some mapping problems ,may be the RFC connection is not properly configured .Here is the link to configure the connection between ECC and PI :
http://wiki.sdn.sap.com/wiki/display/XI/ConnectionSettingsbetweenECCandPIsystem
May be there is no value retrieved from the ECC system so it is saying null value.
For proper configuration check you can refer the following blog:
/people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit
I am a beginner so not the full answer is there but may be this would help you.
Regards
Ravi Anand

Cannot create HTTP client Exception in Http -- XI -- RFC scenario

Hi,
We are testing Http --> XI --> RFC scenario
While testing this scenario from RWB we are getting following error message in the SXMB_MONI logs:
<?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="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_CREATE_FAILED</SAP:Code>
<SAP:P1>1</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Cannot create HTTP client (exception 1)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Following is the info from the Trace:
<Trace level="1" type="System_Error">cl_http_client exc = argument_not_found</Trace>
We have tried following things:
1. In SICF we made sure the /default_host/sap/xi/adapter_plain is active
2. Applied SAP Note: 716739
Any response will be greatly appreciated.
Thanks,
Paresh

Hi UDO,
Thanks for your reply. The error was gone when I tested again this morning. I am guessing it must be the SAP Note 716739 that we applied and might not have refreshed the cache.
I am still intereseted in confirming what exacly fixed this issue.
As per your suggestion, I looked at the left Nav bar and the error was at the "Call Adapter" step. Even in the log message it says the same. The reciever/interface determination and mapping were successfull. I could successfully test the scenario in the integration directory.
Here is what the 716739 Note said:
Symptom
If you call the Integration Server from a sending Integration Engine (proxy), the following error message occurs:
Category = XIServer
Area = INTERNAL
Id = CLIENT_CREATE_FAILED.
In transaction SXMB_ADM, you used the Configure Integration Engine function to enter a URL of the type http://<host>:<port>/sap/xi/engine?type=entry instead of a URL of the type dest://<name>.
Other terms
SICF, SXMB_MONI, SXMB_ADM, XI
Reason and Prerequisites
You have configured the communication route from the sending proxy (Integration Engine) to the Integration Server using the URL of the type
http://<host>:<port>/sap/xi/engine?type=entry and have saved the logon data on the Integration Server in the Service
/sap/xi/engine (transaction SICF).
A program error has occurred: the communication log is not correctly set when the HTTP client is set up.
Solution
The problem is eliminated with SAP_BASIS Support Package 2. To eliminate the problem, you can use an URL of the type dest://<name>, where <name> refers to the name of a HTTP destination that you have maintained with transaction SM59.
Now, I was not using the proxies but Http post to XI. Do you guys also think this might have fixed my issue?
Thanks,
Paresh

When we will go for Ectended Interface Determination

extended interface determination example give me any one...
Regards,
Vinay

Enhanced (Mapping-Based) Interface Determination
Use
In 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 example, you want to split an overall booking for a trip comprising connecting flights into individual booking orders (for each leg of the trip).
You cannot realize this usage case with a standard interface determination (without using an integration process). A standard interface determination does allow you to specify multiple (N) inbound interfaces (with different mapping). In this case, N messages with the same payload and different receiver interfaces are generated from the source message before the mapping step; these are then transformed differently depending on the receiver interface. Therefore it is conceivable to write the mappings in such a way that the first mapping from the source message generates a message that only contains the first item, the second mapping generates a messages that only contains the second item, and so on. However, this no longer works if the number of items can vary with each new source message.
You can use an enhanced interface determination to configure a mapping-based message split for this usage case. You assign the interface determination a multi-mapping that has a target interface with an element with occurrence 0...unbounded. At runtime, the individual messages (for the individual items) are calculated in the mapping step. First, the individual messages are grouped into a bulk message. Then, the bulk message is transferred to the Adapter Engine. The Adapter Engine then splits the bulk message up into the individual messages (see figure).
Procedure at Runtime During Message Split
Note that both the bulk message and all individual messages each have a message header with a receiver interface (see figure).
Receiver Interfaces of Bulk Messages and Individual Messages
The header of the individual messages contains the relevant receiver interface. It is based on the definition of the multi-mapping. Note that the receiver interfaces of the individual messages may be different. The receiver interface of the bulk message is always InterfaceCollection (namespace http://sap.com/xi/XI/System).
If the message split only results in one message, the original message structure remains the same. In this case, a bulk message containing just one individual message is not created.
You can also assign a multi-mapping with multiple different target interfaces to an enhanced interface determination (1:n transformation). Each target interface can contain elements with occurrence 0 ... unbounded.
Messages cannot be sent by using different Adapter Engines in a mapping-based message split. This affects configuration thus: All receiver agreements that have a receiver interface from the mapping entered in the key must only be assigned communication channels with the following adapter types:
-          RFC adapter
-          SAP Business Connector adapter
-          File/FTP adapter
-          JDBC adapter
-          JMS adapter
-          SOAP adapter
-          Marketplace adapter
-          Mail adapter
-          RNIF adapter
-          CIDX adapter
The adapters also have to all run on the same Adapter Engine.
Adapters developed by partners also support a mapping-based message split if they run on the same Adapter Engine.
Attachments from the original message are not appended to the messages resulting from the message split.
Activities
To execute a mapping-based message split, perform the following steps:
       1.      Integration Repository: Define the multi-mapping (see Developing Multi-Mappings for Message Splits).
       2.      Integration Directory: Define the interface determination.
Note the following:
○     The outbound interface of the multi-mapping must be entered as the sender interface in the key of the interface determination.
○     The interface determination type must be set to Enhanced.
○     Select the multi-mapping you defined previously from the Integration Repository.
To select the interface mapping, use the input help ( ).
The target interfaces of the interface mapping are displayed in the Inbound Interfaces frame.
The number of messages (for an inbound interface) created in the mapping step is displayed in the Occurrence column.
regards,
Raj

Error in HTTP to RFC senario?

Hi experts,
iam working on PI7 sandbox,i done a senario HTTP is the sender and RFC is the Receiver.....where i will send material nunber and i need responce from SAP system unit and weight details.
iam using HTTP client tool 2 post the payload into xi,iam geting this error
Result:
http-Status: 500 Internal Server Error
Payload:
<SAP:Error><SAP:Category>XIServer</SAP:Category><SAP:Code>MAPPING.NO_MAPPINGPROGRAM_FOUND</SAP:Code><SAP:P1>http://HTTP.com IM_Material</SAP:P1><SAP:Stack>Interface mapping http://HTTP.com IM_Material does not exist in runtime cache</SAP:Stack></SAP:Error>
i activated all objects in IR and ID i have done TEST CONFIGURATION in ID it was working fine......i checked the message mapping and Interface mapping ......still iam geting error.
iam using BAPI_Material_Get_detailsv this bapi...
Pleace help me in this issue
Regards,
Phani

Hi,
1. Just go the Interface Mapping and see whether u have specified same Msg Mpping prog in that.
2.Also go to the Interface determination and chk if u have specified the correct inbound Interface and Interaace Mapping corresponding to it.
Regards,
Ashwin M
Reward if helfpul

HTTP to RFC Interface Determination problem

Similar Messages

Maybe you are looking for