RFC to XI: Empty payload xml

Hello everyone,
We have a very simple scenarion RFC -> XI -> JDBC.
When the rfc is executed in the backend R/3 i can see the xml in sxmb_moni
BUT the payload is empty.
The remote function uses TABLE instead of IMPORT / EXPORT parameters.
Any ideas?
Thanks in advance
Dimitris

Hi,
RFC is sending the table name , check.What are all the Return values in terms of structure and also check the struture of the return /response message,
http://help.sap.com/saphelp_erp2005vp/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm
Problem passing a table parameter in rfc call using the function control
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
Regrads
Chilla
reward points if it is helpful..

Similar Messages

Enhanced Interface Determination gives Empty Payload

Hi,
I am using Enhanced Interface Determination in my scenario.
1:3 Message Types(Interfaces).
The thing is that split occurs, but after Message Mapping I get empty Payloads..
I am using External Definitions instead of Message types.
Another question: Can there be multiple dynamic confgiurations during splits. i.e one Dynamic Configuration for each message split.
Note: testing the Interface mapping from IR with payload from MONI gives proper output.
Regards,
Sundar.

Hi All,
I copied the entire XML which i used for testing in Interface Mapping which i should not have....
I gave as
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
 <ns0:Message1>
 <ns1:SAP_HR_MT xmlns:ns1="http://com.cognizant/sapr3/all">
 <Participant>....
 </Participant>
 <Dependent>
 .... </Dependent>
 <Coverage>
 .... </Coverage>
 </ns1:SAP_HR_MT>
 </ns0:Message1>
</ns0:Messages>
But the input should have been
<?xml version="1.0" encoding="UTF-8"?>
 <ns1:SAP_HR_MT xmlns:ns1="http://com.cognizant/sapr3/all">
 <Participant>....
 </Participant>
 <Dependent>
 .... </Dependent>
 <Coverage>
 .... </Coverage>
 </ns1:SAP_HR_MT>
now the output is perfectly coming....:-)
Regards,
Sundar )

Ignore empty Payload

Hello All,
I have a Proxy-PI-SOAP scenario. There are situations when proxy generates messages with no payload. In that situation, it throws an error in PI (RWB -> Message Monitoring -> AE) as there is no node getting generated.
I can apply the rule in Proxy code not to send the message to PI in case there is no payload, but business won't allow that.
So, I have to handle this in PI.
I can't use the dummy receiver, as it will again throw an error in case it is unable to find the receiver (I can't create a dummy receiver on the Prod box as per my Client).
I would like to know what other option I am left with? I don't want to encounter any errors in the MONI or elsewhere. How I can "stop" the processing of those messages which are having empty payload?
Just to add - I am using XSLT mapping.
Any suggestions will be highly appreciated. Thanks for your time.
--Abhi
Edited by: Abhi_1516 on Jan 4, 2010 7:34 PM

Hi Abhi,
You can use the "Ignore" option in the Receiver Determination. Put a condition for the root node existence, if found send the message to the desired target else use the option "If no receiver is found" and check the radio button "Ignore".
Just to let you know that with Ignore option, the messages will still show successful in RWB.
Hope this helps.
Regards,
Neetesh

After Transporting the request RFC Destination is empty in SWCV and BEA

Hi All,
we are using SAP NW Mobile 7.1 SP08
After transporting the SWCV & Backend adapter, in the transported system the RFC Destination is empty
Please help me to fix this issue.
Thanks and Regards,
Joseph Beevin.

Hi,
When an SWCV is trnasported to a another system,the backend destination will be empty in the target system.,We need to configure the bakcned destination in the target sytem through the DOE Adimin.
DOE_ADmin Portal -->Configuration --->Backend Configuration.
In the backend configuration,select the SWCV for which the destination needs to be configured.Select the parameter "RFC DESTINATION FOR BACKEND"
When the SWCV is selected all the active Data Objects will be listed in the table below
Insert the above parameter to the parameter list(the table below)
Give the name of the availlable backemnd destination name in the "text value" column of the table for each data object and save it.
Now the backend destination is configured correctly in the target system.Please try this..
Regards,
Muralikrishna T.

Payload XML

Hi All,
Payload XML in BPM Process should contain element with '*response' or not???
When I added a service task activity in the BPM process i can see some .xsd got generated in the SOA project under xsd. Can I consider this as my payload?? But, it doen't have any <*repsonse*> element in it
Thanks,

Hi Ravi,
Thanks for your response. Could you please let me know how the payload xml may look like for the following scenario. Also, please provide some sample payload xml, my main doubt is does the pay load should contain the 'response' tag or not??
Scenario 1
Consider a process diagram with start event, human task, service task, end event. (consider the case of hello world project without the reviewer).
My Queries ::
1) If I am talking about payload will it exist for each element of the process diagram(like start event, human task, service task, end event) or the payload exists for the whole process diagram??
2) If payload exists for each element or the whole process is it automatically generated by the system in the above scneario? if so under which location I can find that??
Scenario 2
I created a start event and defined an interface. It means that interface is exposed as webservice for that process right?? IF so, how can I get the url for that webservice??
Thanks,

Empty payload for idoc adapter

Hello,
I have a file to idoc scenario with an xslt mapping. Normaly after the mapping the idoc looks like:
<wpwuw>-
<idoc>...</idoc>
<idoc>...</idoc>
</wpwuw>
Because of the business requirements in some cases the mapping should not generate an idoc. That means I have to create an empty payload.
The problem is that the idoc adapter creates an error for all kinds of empty messages.
a) empty payload
b) empty trading segment ( <wpwuw></wpwuw> )
c) empty idoc segment ( <wpwuw>-<idoc/>-</wpwuw> )
Any idea what I can do not to get an error from the idoc adapter ?
Regards Bernd

HI
instead of creating empty paylaod. Use conditional(enhanced for mapping & standard for condition on Xpath) receiver determination for this and dont generate IDOC for the specified conditions.
Thanks
Gaurav

SOLVED: SPA2102, WRP400, SPA8000, SRP521 and SRP521-U FAX NSE fails with empty Payload c0000000

Hi Experts.
In my SIP network there is a Cisco PGW 9.6(1) used as PSTN gateway. PGW call agent controls many Cisco AS5400 via MGCP. We use Linksys SPA2102 to connect fax and modem devices.
Both PGW and AS5400 are configured to support FAX passthrough upspeeding via NSE event. Also SPA2102 devices are configured to support FAX passthrough NSE.
After many tests and debugs I see that SPA2102 doesn't recognize NSE event sent from AS5400.
From debug and wireshark traces you can see that AS5400 sends NSE 192 event correctly (see attachments).
So I've try to compare this scenario with a working one. The only difference is in the Payload content of NSE messages.
With AS5400 the Payload is c0000000. I think tath this is an empty payload while with different gateway or ATA the payload is c096c4e. In this last case SPA detects correctly NSE message.
Is this a BUG of SPA2102?
Thanks.

Hi experts, I updated this post after several months because we need information about the status of this issue.
Now we are using the firmware 2.00.21 for WRP400 (a beta) and the firmware 5.2.10 for SPA2102 devices.
No news about next release of WRP400 and the last software for SPA 5.2.12 doesn't fix this issue.
Now we must take a decision for buying thousand CPE for current year. If this issue will not fixed during this month we will be forced to change products and vendor !!!
I hope in a your positive response.
Regards.

PI 7.0 connecting to WebSphere MQ - Empty payload by reciever channel

I have PI 7.0 connecting to WMQ 6.0 using JMS adapter.
The scenario in technical terms is a IDoc to JMS scenario. For one of the message flows, PI delivered an empty message to the MQ queue.
Having checked the audit logs and the MessagingSystem etc, there were no clues why this happened.
In the Message monitoring, on the content tab , in the drop down, i could only see the SOAP envelope. The message content wasnt available in the drop down at all.
Any clues why this may have happened?
There is no content conversion and we are delivering XML to the queues.

hi,
In the Message monitoring, on the content tab , in the drop down, i could only see the SOAP envelope. The message content wasnt available in the drop down at all.
Ok, but here you see the message received by your JMS, so the interest is limited. You need to compare your source message (idoc) to your target message (JMS). here's how to check.
Go to SXMB_MONI, select your message and then "detail" button.
In the left tree, open the FIRST level called "Inbound Message (CENTRAL)". And under this level check your Payload (should be your Idoc sent by ECC).
Then, in the same left tree, go to a level before "Call adapter", for instance in "XML validation Outbound Channel Request". Under this level, check your Payload (that should the XML sent to your JMS). Note: do not go in "response" level, because there is certainly no payload.
What do you have ? does your target payload is empty ? (certainly yes)
if yes, that's mean it's your mapping that something is wrong. Certainly a bad context management, due to a missing "SpliByValue" or something like that. And you certainly have one target message with the content of two idoc segment, whereas this one is empty.
To know which mapping link is bad, in SXMB_MONI, download the source message (so under level "Inbound Message (CENTRAL)", and test it i your Message Mapping.
regards.
mickael

RFC to JDBC Empty tables parameters in response

Hello,
I've got a problem with an XI query (RFC to JDBC, UPDATE_INSERT) which contains a "tables" parameter. When I get the RFC's response in se37 (in the calling system of course), the "tables" parameter is empty. I need the values for further processing. What can I do to get back the values?
Thanks in advance for your answers.
Pierre Lejeune

Hi Sarvesh.
Thanks for your answer. The XML response in SXI_MONITOR tells me table is empty.
My scenario is very simple. I got Receiver Determination, Interface Determination, Sender Agreement and Receiver Agreement, a sender CC to R/3 system and a receiver one to JDBC.
Maybe it's a mapping problem. In the response mapping, I don't know what to link to the "tables" parameter.

Multiple records of table from RFC to XI in single XML file

Hi
My Scenario is as following -->
RFC ---> Sender RFC Adapter ---> XI -
> Rec SOAP adapter ---> Web Service
Now we need multiple records from RFC which can be put in single XML file & XI can transport the whole XML file to Web Service. All the configuration in XI, Web Service is complete & I tested my mapping which is able to accept multiple records.
But when ABAPer is sending the records I am not getting it in XI, I checked that in message payload from RFC.
He put the table name in TABLE tab of RFC. But not under Import Tab, as whatever he is providing under Import parameter & exporting it through report I am getting in message payload but not the table data.
Did anyone try such scenario, can you tell me how can we achieve this.
Pls. provide me your mail ID in case you need an attachment of the current RFC & report code & my mapping snapshot.
Regards
- lalit -

Hi
We have created the BAPI in which we are just describing the structure of the payload & which I am importing in Integration Repository.
And we are calling this BAPI from another program using " Call function ... " command & also provinding the data in that program.
Actually ethically ABAPers are against the idea of provinding the data into program they would like to provide it in BAPI but that won't work, you have to provide data in program which in turn populate the fields of BAPI.
Let me know with your mail ID in case you need snapshot of function & programs.
Regards
- Lalit -

File-Adapter: Variable substitution form payload XML-attribute

Hi experts,
is possible to use XML-attribute-content for variable substitution in file-Adapter?
extract from XML:
<?xml version="1.0" encoding="utf-8" ?>
- <all>
- <transaction file="filename">
- <table name="BPAADDRESS" options="insertIfUpdateFails">
- <record id="1">
<hkeycol name="BPAMAINHKEY">0010500345</hkeycol>
<hkeycol name="USAGE">Invoice</hkeycol>
</transaction>
I want to get the value "filename" = attribute file of transaction.
Is this possible?
Thanks a lot,
Florian

I have done this taking a field from the XML.
You have to map the location of the field within the XML...
Taken from:
http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/frameset.htm
Variable Substitution (Target Directory/File Name Scheme)
If you set the Enable indicator, you can enter variables for the Target Directory and File Name Scheme. Enter the names of the variables and references in the table.
● Enter each variable that you reference in the Target Directory and File Name Scheme fields without the surrounding percentage sign under Name of Variables in the table.
The variables can refer to attributes of the message header or elements of the message payload.
○ If the variables are to refer to an attribute of the message header, add the prefix message: to the name of the variable under Reference. You can specify the following attributes of the message header:
sender_party, sender_service, receiver_party, receiver_service, interface_name, interface_namespace,
message_id (message ID with hyphens, for example 9fbe1ff1-9a0d-11d9-8665-cbf10a126331)
message_id_hex (message ID in hexadecimal format, for example 9fbe1ff19a0d11d98665cbf10a126331)
For example, if you want to specify the interface name from the message header in the target directory or in the file name scheme, enter message:interface_name as the reference.
If one of the message attributes contains characters that are not permitted in a file name, for example \, /, :, *, ?, ", <, >, |, then these characters are replaced by an underscore ("_").
○ If the variable refers to an element in XML schema, add the prefix payload: to the information under Reference. The reference then comprises a pseudo path description in the form of a comma-separated list with the schema namea,na,nameb,nb,....
namea,nameb,... corresponds to the element name and na,nb,... corresponds to the occurrence of the element name at the respective level in the document.
The description begins at the root of the document and ends at the respective element.
To reference the element that is in bold in the example, the following expression is used: payload:root,1,e1,1,e2,2
The parser searches for the first occurrence of the root element at the first level. It then searches for the first occurrence of e1 at the second level and for the second occurrence of e2 at the third level. The content of the last element (Example Value) is set as the value for a specified variable.
<?xml version="1.0" encoding="UTF-8" ?>
<root>
<dummy>
 <e1>
 <e2>Data_1</e2>
 <f/>
 <g attr="abc">text</g>
 <e2>Data_2</e2>
 </e1>
</dummy>
<e1>
 <e2>illegal/value</e2>
 <f/>
 <g attr="abc">text</g>
 <e2 attr="fghij">Example Value</e2>
</e1>
</root>
● To disable the check the adapter performs for the element data, set the Disable Security Checks indicator.
Otherwise, the adapter checks whether the element data contains characters that could lead to security risks in the file system environment. The check includes the characters /, \, and ...

RFC to PI Junk Payload

We are having typical issue in RFC-PI integration.
SAP sending data to PI via RFC. For which we have imported the BAPI. When the data is send by SAP, it is coming to PI as truncated one. For eg First field SAP is of 8 char length internal table but it has value of only 5, than next 3 char are filed by second field and all all other fields become junk. like 5 from first + 3 from second..
We tried to recreate the mapping, re import BAPI, created all ID objects again, Stopped/deactivate the RFC channel ..etc... etc.. but nothing seems to be working and we are getting truncated/concatenated data in Payload in PI
Pls let me know if you have solution for this issue
Thanks

Is your sender system unicode? If no, could you try to change the RFC destination in R/3 conecting to PI to unicode and try again.
Regards,
Prateek

Payload XML DOM Object Update using Java Embedding

Hi,
I have a Java Embedding activity which updates the payload after making
a call to a local EJB. The EJB sends back updated information. In my Java
Embedding activity i try to update the payload nodes with the new information.
It get's really cumbersome to do this sort of thing in BPEL. Basically i am trying
to remove an existing node in the payload and replace it with a new node.
I did so may things that i really don't remember what are they. Finally i managed to
update the payload with the following code.
org.w3c.dom.Element payload = (org.w3c.dom.Element)getVariableData("inputVariable","payload","/MSG");
org.w3c.dom.Element oldNode = (org.w3c.dom.Element)getVariableData("inputVariable","payload","/MSG/TSLData");
org.collaxa.thirdparty.dom4j.Element tslElem = com.collaxa.cube.xml.dom.DOMFactory.convertToCollaxaElement(oldNode);
oldNode = (org.w3c.dom.Element)getVariableData("inputVariable","payload","/MSG/REC");
payload.removeChild(oldNode);
msgElem = com.collaxa.cube.xml.dom.DOMFactory.convertToCollaxaElement(payload);
msgElem.add(recElem);
I feel that there no proper interface to update the data in the payload values with
nodes, string etc. It would be nice if we don't have to work with
com.collaxa.cube.xml.dom.DOMFactory
org.collaxa.thirdparty.dom4j.Element
the collaxa classes.
We need to have more than setVariableData, bascally good payload manipulation API's.
Let me know if there are any alternatives to do this.
Thanks,
Senthil L

I have been having the same difficulties. Were you able to find any documentation or javadocs for the Collaxa libraries? If so, I would greatly appreciate locating them.

Payload xml messages

Hi Friends,
Outbound proxy SAP to MQ.
while sending the data from SAP, in xml payload, complete data structure is not comming.
If the data available only, that field can be seen in xml payload ??
If data is not there, can we that particular fild in xml payload or not ??
Thanks.
vasu

>
> If data is not there, can we that particular fild in xml payload or not ??
>
above statement not clear.
if you want all the fileds to be present in Payload, then you have to maintain the data in ECC,
what exactly are you looking for??
Regards,
Raj

Seeburger Adapter Payload & XML Structure for AS2

Does anyone have a sample AS2 message with payload that I can use to test the Seeburger AS2 adapter for a customer in the UK?
Thanks in advance

Hi Frederic
we will be receiving Tradacoms over AS2. I understand that the Seeburger adatper uses the modules from BIC to convert to XI-SOAP ( XML ), but we need to have the schema created for us to construct the data types or to import external definitions into IR. I would like an actual AS2 message without header and signature if possible or a schema version of the tradacoms messsage format for EPOS data. Or if applicable the mapping program that the BIC module will call from the Seeburger adapter. I have the config guide for the BIC, so I know where to configure, but I need the mappping program which will create the XML prior to sending to XI.
Thanks.
I can send you a sample EDI message ( which will be the attachment ) if you give me your email address.
Cheers,
Mark

RFC to XI: Empty payload xml

Similar Messages

Maybe you are looking for