Sender RFC Scenario Error:Payload Is Missing
I am facing an issue in 'RFC2JDBC' scenario which is mentioned below:
here our scenario is 'RFC2JDBC'.here our 'RFC' is having 2 fields in tables parameter
i.e. empno & empname.
the results of the 'RFC' is coming as:
Personnel Number Employee Name
00000100 Rasmiraj
00000200 Tanmay
00000300 Kanhu
00000400 Debabrata
00000500 shantanu
i am triggering the 'rtfc' through a program.
when i am triggering the 'RFC',in monitor of PI it's coming as sucessful.however in the payload one of the field value is missing i.e. employee name.(same also updating in the legacy database)
in the payload it's appearing as:
[ <?xml version="1.0" encoding="UTF-8" ?>
- <rfc:ZSAM_SEND_RFC_PI xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
- <EMP_DTLS>
- <item>
<EMPNO>00000100</EMPNO>
<EMPNAME />
</item>
- <item>
<EMPNO>00000200</EMPNO>
<EMPNAME />
</item>
- <item>
<EMPNO>00000300</EMPNO>
<EMPNAME />
</item>
- <item>
<EMPNO>00000400</EMPNO>
<EMPNAME>a</EMPNAME>
</item>
- <item>
<EMPNO>00000500</EMPNO>
<EMPNAME />
</item>
</EMP_DTLS>
</rfc:ZSAM_SEND_RFC_PI> ]
please,suggest.(here,we are using sender 'RFC' communication channel & an 'RFC'destination of type 'T'(with parameter registered server program,gateway host,gateway service)
Hi rasmiraj tripathy,
I am also facing the same problem (Sender or Payload is missing) while integrating R3 to B1 using IDOC. When I resend IDOC, it capture by B1iSN but doesn't work, it gives me error. When I look into xml document, it is found that there is no receiver payload.
My R3 system is non-unicode and it is difficult to change it to unicode as it requires updation.
Can you please confirm that this error is coming due to Non-Unicode, and can be resolved by setting it to Unicode.
Note: There is no double definition of any object.
Similar Messages
-
SOAP to RFC Scenario - Error at Sender Communication channel !!
Hi Experts ,
I am trying to execute a SOAP to RFC scenario . At SOAP sender channel level I am getting the error in RWB .
My findings :-
1. Error at RWB 9/24/09 4:24:10 PM error occured
9/24/09 4:24:06 PM request received
2. At SOAP UI client tool :
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>ADAPTER.JAVA_EXCEPTION</code>
<text>com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:UPDATE:HTTP status code401 Unauthorized
at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:917)
at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:207)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</text>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
3. At SOAP UI level - "requires authentication with the realm 'XISOAPApps'"
1. I don't see any issue in authorization as i am having SAP_ALL .
2. URL string seems to be O.K :
http://ABC:50000//XISOAPAdapter/MessageServlet?channel=:BSer_SOAP:CC_SOAP_Sender&version=3.0&Sender.Service=BSer_SOAP&Interface=urn:ABC.com:%5EMI_CustomerInfo
Kindly advice !!!
Regards ,1. Check PI id and password is working fine.
Check if the user you are using has SAP_XI_APPL_SERV_USER role.
Another way is to pass id and pwd in URL
Try to pass the User ID and Password in the URL( the URL which is given to the webservice).
Example: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel &sap-user=xxxx&sap-password=xxxx
2.Provide SOAP URL like -
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel -
Hi PI Experts,
For the first time i was doing soap to rfc scenario. I have created all the objects in the ID and in the IR and also created a web service from ID an then i have saved the wsdl in my system. I have uploaded the wsdl in altova xml spy and tested it but i got an error like 'no channel specified'. and also got an error 'unable to post the file'.
so kindly please help me to solve this scenario.
Thanks & Regards,
B.Srinivas Prasad.I have uploaded the wsdl in altova xml spy and tested it but i got an error like 'no channel specified'. and also got an error 'unable to post the file'.
Make sure that its in the below format :
From SAP help :
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel
and check Sender Soap Channel Status is it activated/not and check Cache Status -
Sender RFC adapter Error- request was null while trying to extract it.
Hi All,
I have a scenario running in Production(PI 7.0 system) where SAP ECC sends RFC request through sender RFC adapter. The scenario was working fine but now I am getting the below error in default trace and I couldn't see any error in communication channel monitoring.
java.lang.Exception: RfcServer[BAS_ECC_RFC_Snd]1[AFSenderD] request was <null> while trying to extract it.
I have gone through the below thread and performed a full cache refresh but it didn't help :
[NULL]
I have gone through SAP note:730870 and I couldn't get any help on this error. Can you please suggest your ideas to solve this issue.
Thanks & Regards,
LaawanyaHi Lawanya,
Check you RFC and input data , whether the RFC call is able to get the data from ECC or not.
you can test the same RFC in ECC with input data and you can check whether the RFC in ECC is return the value or not.
I gues in your case the RFC in ECC is not return any data to PI. -
SYSTEM_FAILURE error after executing RFC for Sender RFC Scenario
Hi ,
I have configured a scenario where my sender is R3 System , data is sent via executing the RFC (BAPI) ........
I have configured the TCP type RFC destination and also maintained a unique program ID ...... i am able to see the program ID as registered service in SMGW.....
while executing the RFC i specify the RFC destination configured as the RFC target Sys...but when i execute ..i get a "<b>SYSTEM_FAILURE</b>" exception....
Please suggest some solution.
Thanks ,
SushilHi,
Execute your RFC in bakground mode. Create dummy report and polpulate your parameter of RFC in this report and execute RFC in background with following syntax.
CALL FUNCTION <yourfunction>
IN BACKGROUND TASK
DESTINATION <yourRFCDest>
<Export/Table/Exception etc Paramters>
COMMIT WORK.
You can found similar issues in forum.
Regards,
Gourav
null -
Sender RFC scenario not working
Hi All,
I'm trying to configure a scenario where the sender is an RFC. I have done the following configuration steps:
1. Created an RFC destination in the R/3 system.
Program ID: SAPSLDAPI_X3A
Gateway Host: hostname of the XI system
Gateway Service: Gateway service of the XI system
2. In the RFC Sender channel
App Server Gateway: R/3 system's hostname
App Server Service: of the R/3 system
Program ID: SAPSLDAPI_X3A
3. In the RFC Metadata Repository Parameter, the details of the R/3 system is provided.
4. The RFC is triggered by calling a report program specifying the RFC destination.
But no messages are coming to the message monitor. Is anything wrong here or is something missing? Is there any way to see what happened in the R/3 system?
Could you please help?
Thanks,
PriyaHi,
<i>1. Created an RFC destination in the R/3 system.
Program ID: SAPSLDAPI_X3A
Gateway Host: hostname of the XI system
Gateway Service: Gateway service of the XI system</i>
This is fine.. I would recommend you to use different name coz SAPSLDAPI is a RFC destination name for SLD communication purpose. Its better to avoid using some system names. But this is not a problem.
<i>2. In the RFC Sender channel
App Server Gateway: R/3 system's hostname
App Server Service: of the R/3 system
Program ID: SAPSLDAPI_X3A</i>
The App Server Gateway, App Server Service & Program ID should match with what you have given in the RFC destination of R/3 system.
After this try doing a test connection from the RFC destination sm59. Your test should be succesful.
<i>3. In the RFC Metadata Repository Parameter, the details of the R/3 system is provided.</i>
This is fine
<i>4. The RFC is triggered by calling a report program specifying the RFC destination.</i>
This is also fine.
Also in order to see any messages in SXMB_MONI you need to enable Logging. Trace level = 3 will not capture the Sync message. RFC is by default Sync. If your sender is not expecting any response then you will get an error in the response message, in this case you need Async.
For Async you need to add this addition while doing the call function "IN BACKGROUND TASK". Also make sure you re mentioning the <b>destination</b> while doing the call function.
Check you have mentioned
DESTINATION <rfc destname>.
Thanks,
Prakash -
Dear XI Expert,
I have completed configuration part of Sender RFC scenario. In this scenario, when I execute RFC in Source SAP system, message gets routed through XI and then it is converted to file. This file is placed on a file system.
The inbound message interface is asynchronous mode.
The problem is 'After placing the file on File system, it is travelling in the reverse direction and expected mapping program between inbound message type and outbound message type.
In message monitoring it showing error with ID 'NO MAPPING_PROGRAM_FOUND' with Type to be 'Synchronous'.
1. sender service --> xi -->receiver service
2. receiver service --> xi --> sender service.
I don't want the 2nd step and want to configure 'Asynchronous' Sender RFC.
Can anybody help me in configuring 'Asynchronous' Sender RFC?
Regards,
Suraj Kumar> Dear XI Expert,
>
> I have completed configuration part of Sender RFC
> scenario. In this scenario, when I execute RFC in
> Source SAP system, message gets routed through XI and
> then it is converted to file. This file is placed on
> a file system.
Hi suraj,
i am not able to configure Sender RFC in XI which would take RFC calls from my R/3 SAP system.
The Technical System & business system that i have created for my R/3 are of type Web As ABAP ( Is this the right option ?)
I basically get error saying Program Id not registered, what might be the reason -
sender RFC scenario without BPM
every thing is fine but the value which i gv is comming as out put but i shuld get the details from SAP...
and in MONI only one msg is comming that is showing Success...
Can anyone Explain me Plz.
THX
john...Hi,
File-RFC-File is asysnch to sysnch scenario this scenario can be handled in two ways
1) Using BPM:
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
2) The weblog which is provided to u in this case u need to do the same configuration which is mentioned in the weblog.
If u have not done the configuration then do it and then try.
Chirag -
Missed data JDBD Sender- RFC Receiver Scenario
Hello,
I simulated a JDBC synchronous scenario by developed a JDBC Sender-RFC Receiver Scenario to retrieve data from an Oracle Database and inside the RFC , ECC executed a Proxy-JDBC scenario to mark the retrieved items in the Oracle Database.
Sometimes, in my productive system, some of the items retreived from de JDBC sender seems to be missed. In TA sxmb_moni i saw the message from the JDBC sender channel but the ECC don´t send the message from de proxy request inside the RFC, wich means that RFC doesn´t execute. And a time after without any kind of action, the complete scenario work fine.
We found this trace log in the NWA stack :
"Catching com.sap.aii.af.service.cpa.CPAException: Couldn't retrieve outbound binding for the given P/S/A values: "
Thanks in advance.Hi Mariluz,
Make a full CPACache refresh using the following url:
http://XIhost:port/CPACache/refresh?mode=delta
http://XIhost:port/CPACache/refresh?mode=full
note: use PIDIRUSER for refreshing CPA CACHE for the above uri's
Also Check the note #1057990 for more details
there might be other reason that below services might abruptly stop check this also:
- XPI Adapter: File
- XPI Adapter: JDBC
Regards,
Naveen -
Displaced content from sender RFC in payload - PI 7.0
Hello,
we have a strange behaviour here.
After implementing a scenario with HTTP->PI->RFC
which works fine transporting a structure to an R/3, we wanted implement another scenario RFC->PI->HTTP (RFC is async).
Problem when testing it:
The RFC hands over a structure which contains in the first field a order number (so leading zeros are cut).
The cutting of the zeros results in a displacing of the rest of all fields. So filling the payload PI is in some trouble and adds an error code #... in some fields.
This is why we identified the problem, because the error codes run into error during mapping.
We reimported the RFC more than once, changing the structure to be sure that we can se a successful update of the RFC structure in the repository. Everything fine, but the error is still the same.
Now we convert on the R/3 side the order no. field:
Instead of leading zeros we replaced them with '9' ´s.
Then we correct this in mapping.
But this is not a solution!
Is there anybody who had the same effect on his XI/PI using sender RFC?
If you can offer a solution for that..... would be great!
Best regards
DirkHello,
this is another idea but would do the same as our '9'-solution. It would solve the specific issue but will not remove the problem itself.
We had a hint from somebody in our company internal forum:
"If you had used a custom RFC pls make use of conversion routines for the order no field. in a std rfc this would have been handeled implicitly."
Will discuss this with the developer and come back.
We got the answer:
On R/3 side there is a customer table which provides the data. There is conversion routine ALPHA already added to several fields. But only field "orderno" is resulting in trouble. We do now a move to a workarea based on a new defined structure instead of moving the select result based on the table structure to the RFC. In the structure we defined order no. as a simple CHAR field w/o any conversion behind.
So now it is working!
regards
Dirk
Edited by: Dirk Meinhard on Feb 20, 2008 6:28 PM -
NO_RECEIVER_CASE_BE error in a SOAP - XI - RFC scenario
Hi gurus:
I'm configuring a SOAP -> XI -> RFC scenario and I'm getting a "NO_RECEIVER_CASE_BE" error when I send a test message using the SOAP adapter.
I have another interfaces using the SOAP adapter of the same XI server and no problems with it. So I think my problem is not into the SOAP adapter.
Thanks to all in advance,
Alejandro Gomez.
Edited by: Alejandro Gómez on May 27, 2008 10:24 AMHi:
The entire XML result from MONI is next:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Inbound Message --> <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30"><SOAP:Header><SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7"><SAP:MessageClass>ApplicationMessage</SAP:MessageClass><SAP:ProcessingMode>synchronous</SAP:ProcessingMode><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:TimeSent>2008-05-27T09:10:24Z</SAP:TimeSent><SAP:Sender><SAP:Service>Openlab_Desarrollo</SAP:Service><SAP:Interface namespace="http://www.huc.es/xmlns/openlab">ServicioObtencionDatosPaciente</SAP:Interface></SAP:Sender><SAP:Interface namespace="http://www.huc.es/xmlns/openlab">ServicioObtencionDatosPaciente</SAP:Interface></SAP:Main><SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:QualityOfService>BestEffort</SAP:QualityOfService></SAP:ReliableMessaging><SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Hop timeStamp="2008-05-27T09:10:24Z" wasRead="false"><SAP:Engine type="AE">af.xi2.xidserver</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:Info/></SAP:Hop><SAP:Hop timeStamp="2008-05-27T09:10:24Z" wasRead="false"><SAP:Engine type="IS">is.00.xidserver</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:Info>3.0</SAP:Info></SAP:Hop></SAP:HopList><SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SAP:Date>20080527</SAP:Date><SAP:Time>101024</SAP:Time><SAP:Host>xidserver</SAP:Host><SAP:SystemId>XI2</SAP:SystemId><SAP:SystemNr>00</SAP:SystemNr><SAP:OS>Windows NT</SAP:OS><SAP:DB>ORACLE</SAP:DB><SAP:Language/><SAP:ProcStatus>023</SAP:ProcStatus><SAP:AdapterStatus>000</SAP:AdapterStatus><SAP:User>XIAFUSER</SAP:User><SAP:TraceLevel>3</SAP:TraceLevel><SAP:Logging>1</SAP:Logging><SAP:LogSeqNbr>001</SAP:LogSeqNbr><SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr><SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal><SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal><SAP:PipelineElementId>5BC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId><SAP:PipelineService>PLSRV_RECEIVER_DETERMINATION</SAP:PipelineService><SAP:QIdInternal/><SAP:CommitActor>X</SAP:CommitActor><SAP:SplitNumber>0</SAP:SplitNumber><SAP:NumberOfRetries>0</SAP:NumberOfRetries><SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries><SAP:TypeOfEngine client="100">CENTRAL</SAP:TypeOfEngine><SAP:PlsrvExceptionCode/><SAP:EOReferenceRuntime type="TID"/><SAP:EOReferenceInbound type="TID"/><SAP:EOReferenceOutbound type="TID"/><SAP:MessageSizePayload>508</SAP:MessageSizePayload><SAP:MessageSizeTotal>2985</SAP:MessageSizeTotal><SAP:PayloadSizeRequest>508</SAP:PayloadSizeRequest><SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap><SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse><SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap><SAP:Reorganization>INI</SAP:Reorganization><SAP:AdapterInbound>AENGINE</SAP:AdapterInbound><SAP:InterfaceAction>INIT</SAP:InterfaceAction><SAP:RandomNumber>00</SAP:RandomNumber><SAP:AckStatus>000</SAP:AckStatus><SAP:SkipReceiverDetermination/></SAP:RunTime><SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30"><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="end" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="end" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.616</SAP:Timestamp></SAP:RunTimeItem></SAP:PerformanceHeader><SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:TraceLevel>Fatal</SAP:TraceLevel><SAP:Logging>Off</SAP:Logging></SAP:Diagnostic><SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">Party normalization: sender </Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace><!-- ************************************ -->
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = xidserver:8000</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 10.137.73.104</Trace>
<Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace><!-- ************************************ -->
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace><!-- ************************************ -->
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB... </Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
</Trace>
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found </Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK. </Trace>
</Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">XMB entry processing </Trace>
<Trace level="3" type="T">system-ID = XI2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = S</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE"></Trace><!-- ************************************ -->
<Trace level="1" type="T">Message-GUID = BD9B57A12BCC11DDC738001B7899027A</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace><!-- ************************************ -->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline attributes </Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline elements </Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="2" type="T">Persisting original message </Trace>
<Trace level="3" type="T">Message-Version = 000</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION"></Trace><!-- ************************************ -->
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_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_RD_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>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace><!-- ************************************ -->
<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="1" type="T">No Relation found - accept given Receivers. </Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules. </Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0 </Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
<Trace level="3" type="T">Persisting message Status = 023</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace></SOAP:Header><SOAP:Body><SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7"><SAP:Payload xlink:href="cid:payload-bd9b57a22bcc11dd95bc001b7899027a#sap.com"><SAP:Name>MainDocument</SAP:Name><SAP:Description>Main XML document</SAP:Description><SAP:Type>Application</SAP:Type></SAP:Payload></SAP:Manifest></SOAP:Body></SOAP:Envelope>
Thanks,
Alejandro Gomez. -
HTTP to RFC scenario, RWB error
Hi
I am following this scenario
/people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit
I tried in RWB-->component Monitoring->Integration Engine and gave Header Information sender, interface, Namespace,
user, Password(XI user ID and Password), and Quality of Service Payload information also given from the message mapping If I click on send message Following error is displayed
Error Code: ICF-LE-http-c:000-l:-T:1-C:6-U:5-P:5-L:6
HTTP 401 - Unauthorized
Your SAP Internet Communication Framework Team
what is this error about ? How to solve this ?
Thanks, dushanthDear Dushanth ,
It is very simple ..
Go to SU01 , Select user XIRWBUSER and assign role SAP_XI_RWB_SERV_USER.
Just for your update :
XIREPUSER->User for the Integration Repository->SAP_XI_IR_SERV_USER
XIDIRUSER->User for the Integration Directory->SAP_XI_ID_SERV_USER
XIAPPLUSER->User for sender applications->SAP_XI_APPL_SERV_USER
XILDUSER->User for the System Landscape Directory->SAP_BC_AI_LANDSCAPE_DB_RFC
XIRWBUSER->User for the Runtime Workbench->SAP_XI_RWB_SERV_USER
XIISUSER->User for the Integration Server->SAP_XI_IS_SERV_USER
XIAFUSER->User for the Adapter Engine (communication between SLD, Integration Server, and Adapter Framework)
->SAP_XI_AF_SERV_USER_MAIN.
Regards,
Santosh Karadkar -
XI to RFC Scenario: Runtime error during RFC Call
Hi,
I am testing a XI-to-RFC scenario involving BPM. The RFC works perfectly from SE37; but I get 'ICM_HTTP_TIMEOUT, Error code 402' when I invoke it from XI. On digging through the problem, it appeared that the calling program produced a short dump at the ABAP end. The code is as follows:
<b>module %_rfcdia_start output.
"Do not display screen !
call 'DY_INVISIBLE_SCREEN'.
perform remote_function_diastart.
endmodule.
module %_rfcdia_call output.
"Do not display screen !
call 'DY_INVISIBLE_SCREEN'.
perform remote_function_diacall.
endmodule.
module %_cpic_start.
if sy-xprog(4) = '%RFC'.
perform remote_function_call using rfctype_external_cpic.
else.
call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.
perform cpic_call using convid.
endif.
endmodule.
form cpic_call using convid type c.
communication send id convid buffer header.
if sy-subrc eq 0.
perform (sy-xform) in program (sy-xprog).
else.
message a800.
endif.
endform.
form remote_function_call using value(type).
data rc type i value 0.
do.
********This is the line where error occurs************
<i>call 'RfcImport' id 'Type' field type.</i>
if sy-xprog = 'JAVA'.
system-call plugin
id 'JAVA' value 'FORW_JAVA'
id 'RC' value rc.
if there is no rollout on the JAVA side which
rolls both, JAVA and ABAP, we return to the
C-Stack and reach this point
in case there was an rollout, the ABAP-C stack is lost
and we jump direkt to this point
here we trigger the rollout on this Abap side with
the following statement
system-call plugin
id 'JAVA' value 'ROLL_OUT'
id 'RC' value rc.
else.
perform (sy-xform) in program (sy-xprog).
rsyn >scont sysc 00011111 0.
endif.</b>
Anybody has any idea why it is happening? Is it a network issue? The dump in ST22 says that 'The program "SAPMSYS1" was terminated manually'. How it is possible to manually abort an automatic call?
Awaiting reply.
Regards.Hi,
Probably because of timeout, it is unable to execute the request ..so it is aborted.
btw, is it a synchronous call ? what is the message size ? the given data to RFC is correct and valid structure ? check the mapping .for this use the data from SXMB_MONI and test it
Check this blog for timeout errors-
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
Regards,
moorthy -
Mapping error in file(FCC) to rfc scenario
Hi,
i am trying to implement mapping in file (fcc) to rfc scenario. the source file is getting picked up, but the problem is arising during mapping. i am unable to generate the target structure. i am attaching mapping structure as follows
Source Structure Target Structure: RFC
storesales -POSDW-CREATE_TRANSACTIONS_EXT
recordset it_transaction
gmd_site_101 item
gmd_site_102
gmd_site_103
gmd_site_104
here the recorset is mapped to item, and fields of subnode gmd_site_101 is mapped to fields of subnode item. similarly, for the other subnodes. but when testing with xml file, the target field is not getting generated. in FCC parameters, ignorerecordset name is set to "true".
any help would be very helpful..thanks in advance.
warm regards,
kartzhi
You can test the data using payload from SXMB_MONI in message mapping test tool so as you can get to know the reason of failure.
It would be better if you paste the error you are getting over there.
Check if you have maintained the namespace in CC or not. it should be same maintained if you have kept namespace in message type.
Also check in FCC parameters you must have used ignoreRecordsetName = true
Regards
Raj -
Error in 'WEBSERVICE TO RFC' SCENARIO
Hi experts,
i am facing a problem in 'WEB SERVICE-RFC' scenario,here we are using soap sender communication cheannel & rfc receiver communication channel.while processing the message from 'portal'(through web service in 'SXI_MONI' we are gettin 1 request & 2 response(error) message.
(in sxi_moni)
1st error message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="RFC_ADAPTER">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="urn:sap-com:document:sap:rfc:functions">ZBAPI_QUOTATION.Exception</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
[note: here we are using 'ZBAPI_QUOTATION' IN sap r/3)
2nd response:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping
-->
- <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">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID 08490A2EBE1A301E9D13373FF379B9BE Software Component 9776FD71CBAE11DF8942F5910A010C19</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Interface mapping Object ID 08490A2EBE1A301E9D13373FF379B9BE Software Component 9776FD71CBAE11DF8942F5910A010C19 does not exist in runtime cache</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
please help me to solve this issue.For the mapping error >>> Please check whether you have created a response mapping and properly referenced it in your operation mapping
For the RFC exception error >> Please check if you have any new fields added in RFC , re Import the RFC definition in PI
refresh the cache SXI_Cache
Please check below similar threads
file rfc file
RFC_ADAPTER "APPLICATION_ERROR"
Re: Webservice to RFC testing
Hope this helps
Regards
Ninad
Maybe you are looking for
-
Reading Values from a Datatable to a backing bean
I have a Datatable which has 3 columns. First Column is a Account Number and the Second Column gives the address of the Account Number. The Inputs 1 to 5 Account Number on the Previous Page. Depending on number of Accounts Input by the user - the dat
-
Clear query when i enter on the request page
I have a page with some query field and a button ('execute query'). When i return on the page the was dispaly the old query, it is possibile to enter in the page and finf it clear ?? Thank's'.
-
How do i turn off the service searching?plz read
Ok so I was stationed to Iwankuni Japan and of course my awesome iphone doesn't work out here :'-( how can i turn off the phone part so that i can still have my wifi on and it isn't searching for service? pretty much i want to make it an ipod touch.
-
Mass change of valuation class
Hi Folks, We need to change Valution class for almost 150 materials. I'm referring SAP note:-160970 for this. So,please guide me from where should I start? I think I need to first check any open POs or stocks are there or not...right?Anything else? B
-
SP3 and Fix Pack 3.1 errors.
Hello, I am using Xcelsius 2008 and I am having 2 problems here. 1st problem, I have tried to install the Service Pack 3. After I install it, whenever I add a new Data Connection, the right screen (where it was supposed to be the data connection seet