ATTRIBUTE_IDOC_METADATA : Sender not in payload

Hi all
when i am doing this:
file-> XI -> IDOC
I got 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="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Use sender from payload: Sender not in payload</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Use sender from payload: Sender not in payload</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Sombody helps me
Thanks in advance

Hi Leo,
A few suggestions from my end are:
Go to IDX2 in XI system and import the Idoc. If it exists,delete it and Reload.
Also make sure that,IDX1 entry is correct.
If you are in PI 7.0 then you can try this-
http://help.sap.com/saphelp_nw04/helpdata/en/44/11982eb8da648fe10000000a1553f7/frameset.htm
Before doing this I would ask you to ensure that all the segments are released.
Also you can check the IDOC via we30 by F9 (check).
Regards,
Abhy

Similar Messages

Use sender from payload: Sender not in payload

Hi,
I am currently facing problems with a IDoc -> XI -> Proxy(XI) sceanrio.
The Idoc is received by XI without any problems. No message mapping is required for this scenario. However, the message keeps getting stuck in the Inbound queue (SMQ2). The status text says "Use sender from payload: Sender not in payload".
Can anyone help me out on this?
Thanks,
Krishneel

Check this related problem:
ATTRIBUTE_IDOC_METADATA : Sender not in payload
Regards,
Abhishek.

Error: Sender Not in Payload

Dear All,
I m doing FILE_XI_IDOC(CREMAS03) scenario. I am getting the following error in SXMB_MONI:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Copy sender from payload: Sender not in payload</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Copy sender from payload: Sender not in payload</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have seen some already posted queries (ATTRIBUTE_IDOC_METADATA : Sender not in payload) regarding this and they suggest to Populate SNDPRN with the valud Sender Partner Name in the mapping and then process the IDOC.
But I am not able to get where we have to update this value. Please guide me regarding this.
Warm Regards,
N.Jain

hi,
1. you can put the sender field in your mapping
open EDI_dc40 semgne of your IDOC (cremas)
and find SNDPRN field
2. you can also have a look at my blog:
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
3. for IDOC-XI scenario you can also
have a look at my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
you can also make disable the edidc40 segment in mapping
and uncheck - use sender from the payload
in idoc receiver adapter and it will be filled with defaults
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Error: Copy sender from payload: Sender not in payload

Hi all.
I generated a new WSDL with XI. when i posted it with XML Spy in SXI_MONITOR got this error:
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Copy sender from payload: Sender not in payload</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Copy sender from payload: Sender not in payload</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
WSDL could be wrong?
Rgds
RP

Hi,
it's not a WSLD error it's IDOC
have a look at my answer here:
Re: Error: Sender Not in Payload
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Use sender in Payload: Sender not in Payload.

Hi,
When R3 sends ORDRSP to XI , the BPM in XI sends a Status ( SYSTAT01 IDoc ) back to R3 without any problem. Whereas when R3 sends DELVRY03 to XI, the BPM in XI is not able to send the Status back to R3 and gets stuck in XI Queue. The reason: Use sender in Payload: Sender not in Payload.
Both ORDRSP and DELVRY03 are using the same IDOC Receiver Channel with Take Sender from Payload checked.
Any idea what is causing the message to get stuck in the queue.
Thanks,
Sreekanth

The reason: Use sender in Payload: Sender not in Payload.
Check below link:
Error: Sender Not in Payload
also there are other threads...but ultimately it is Michal's reply which everyone is refering to.
Regards,
Abhishek

NetStream.send not working in Flash Player 11.2 Beta with Cirrus, Please confirm if it is a bug

Title
NetStream.send not working in Flash Player 11.2 Beta with Cirrus, Please confirm if it is a bug or feature
Description
Problem Description:
NetStream.send can not send data to peerstreams when using with cirrus. Conflict with documents.
Sorry for tag the build as 11.0.1.3 while the bug is actually on 11.2 beta since the bug report system didn't have 11.2 beta yet.
If you are not responsible for 11.2 beta bug fix, please help a hand to handle this bug to 11.2 team.
This bug is "killing" to your application, so we really appreciate your help. Thanks.
==Publisher==
nc.connect("rtmfp://");
var ns:NetStream = new NetStream(nc, NetStream.DIRECT_CONNECTIONS);
ns.publish("sendtest");
...//after connection success.
ns.send("clientfunction", "ok"); // this line cannot reach subscribers. even if subscribers have client object correctly.
==Subscriber==
nc.connect("rtmfp://");
var ns:NetStream = new NetStream(nc, cirrusid);
var client:Object = new Object();
client.clientfunction = clientfunction; // target function
ns.client = client;
ns.play("sendtest");
Steps to Reproduce:
1. compile the code in the attachment to SendTestExample.swf (not be able to paste it here)
2. run it under flash player 11.2.202.19 beta
3. run it under flash player 11
Actual Result:
HeartBeat is:
Start HeartBeat:
send hello
send hello
send hello
which means NetStream.send was not able to call "clientfunction" as expected.
Expected Result:
Start HeartBeat:
send hello
in client function: hello
send hello
in client function: hello
send hello
in client function: hello
which can call into the clientfunction as flash player 11 did.
Any Workarounds:
I can not find it out since it's an api level bug. But this can be very important for lots of applications which rely on send to do rpc.
Test Configuration
IE8, Firefox under Windows 7
Also have problem under Windows XP (but not well tested on this platform)
App Language(s)
ALL
OS Language(s)
ALL
Platform(s)
Windows 7
Browser(s)
Internet Explorer 8.0
==Attachment==
package {
    import flash.display.Sprite;
    import flash.events.Event;
    import flash.events.NetStatusEvent;
    import flash.events.TimerEvent;
    import flash.media.Video;
    import flash.net.NetConnection;
    import flash.net.NetStream;
    import flash.text.TextField;
    import flash.utils.Timer;
    import flash.utils.setTimeout;
    public class SendTestExample extends Sprite
        public static var statusArea:TextField;
        var ncServer:NetConnection = new NetConnection();
        var nsServer:NetStream;
        var ncClient:NetConnection = new NetConnection();
        var nsClient:NetStream;
        var timer:Timer = new Timer(1000);
        public function SendTestExample() {
            ncServer.addEventListener("netStatus", onNCStatusServer);
            ncServer.connect("rtmfp://p2p.rtmfp.net","99f72ccbed0948d7589dc38a-3ce1b2616680");
            statusArea = new TextField();
            status("status");
            statusArea.x = 0;
            statusArea.y = 0;
            statusArea.border = true;
            statusArea.width = 200;
            statusArea.height = 350;
            addChild(statusArea);
        function onNCStatusServer(event:NetStatusEvent):void {
            status("Step 1:");
            status("server: " + event.info.code);
            status("id: " + ncServer.nearID);
            switch (event.info.code) {
                case "NetConnection.Connect.Success":
                    nsServer = new NetStream(ncServer, NetStream.DIRECT_CONNECTIONS);
                    nsServer.addEventListener(NetStatusEvent.NET_STATUS, onNSStatusServer);
                    nsServer.publish("sendtest");
                    ncServer.removeEventListener(NetStatusEvent.NET_STATUS, onNCStatusServer);
                    ncClient.connect("rtmfp://p2p.rtmfp.net","99f72ccbed0948d7589dc38a-3ce1b2616680");
                    ncClient.addEventListener("netStatus", onNCStatusClient);
                case "NetStream.Publish.BadName":
                    //status("Please check the name of the publishing stream" );
                    break;
        function onNCStatusClient(event:NetStatusEvent):void {
            status("Step 2:");
            status("client: " + event.info.code);
            status("id: " + ncClient.nearID);
            switch (event.info.code) {
                case "NetConnection.Connect.Success":
                    nsClient = new NetStream(ncClient, ncServer.nearID);
                    var c:Object = new Object();
                    c["clientfunction"] = clientfunction;
                    nsClient.client = c;
                    nsClient.play("sendtest");
                    ncClient.removeEventListener(NetStatusEvent.NET_STATUS, onNCStatusClient);
                    //setTimeout(sendHello, 5000);
                case "NetStream.Publish.BadName":
                    //status("Please check the name of the publishing stream" );
                    break;
        protected function onNSStatusServer(event:NetStatusEvent):void {
            status("nsserver: " + event.info.code);
            if (event.info.code == "NetStream.Play.Start") {
                status("Start HeartBeat:");
                this.timer.addEventListener(TimerEvent.TIMER, function (e:Event):void {
                    sendHello();
                this.timer.start();
        protected function sendHello():void {
            status("send hello");
            nsServer.send("clientfunction", "hello");
        protected function status(msg:String):void
            statusArea.appendText(msg + "\n");
            trace("ScriptDebug: " + msg);
        protected function clientfunction(event:Object):void {
            status("in client function: " + event);

Thanks for reporting. I can reproduce the bug in house. We will investigate.
Calise

Problem in sending Nota Fiscal XML as Email

Hi
We have activated B2B for our brazilianl client to send Nota fiscal xml as an email to the customer. This is triggered based upon the CNPJ code in table /xnfe/tb2b .This works fine.
Now, we have an additional requirement to send the XML to a general email address in the client company even for customers for whom B2B has not been activated in table /xnfe/tb2b.
For this wechanged the form check_b2b_sendin in program /XNFE/LAPPL_PROCESSESF02, to poulate the cnpj value even if it is not found in table /xnfe/tb2b.. however still the email is not triggered for such customers.
Thanks In advance!

I believe, you need to have partner profile(KU) created for your desired customer by using TCode WE20.
Then in customer master, your customer's contact email need to be maintain.
Regards
JP

Send note as a draft,works everytime

Re problem sending note via e mail.
Send note as a draft,works everytime

Hi bahama mama,
When you signed up for Adobe Send, which email address did you use? Did you use the new email address? This is the email address that Adobe Send will use when you send your files.
Sara

6288 message sending failed. Sending not allowed.

Hi,
I have a 6288, and just recently it has been coming up with the message 'Message sending failed. Sending not allowed' randomly when I try to send a txt. (A similar msg appears if I try to make a call as well). All other functions appear to work normally. The only way to get the phone to send/call is to switch off then on again. I can receive txt/calls when the phone is like this. This morning it also said that 'sim card registration failed'. Any help will be appreciated.

Have you tried updating your phone?
If not I would recommend you to do so.
Link here: http://europe.nokia.com/softwareupdate
Before the update be sure you meet the system requirements to perform the action and don't forget to backup your data first.

Setting dynamic file name in Receiver file adapter - not from payload

Guys I just remember reading a weblog but can't find it now that I need it, on how to set the file name in message mapping dynamically but not using any payload field.
Please let me know if you remember this.
Thanks a lot,
Viktor Varga

also u can check in
<a href="/people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii file name(XSLT Mapping with Java Enhancement) using XI 3.0 SP12 Part -II</a>
<a href="/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14: The same filename from a sender to a receiver file adapter - SP14</a>

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
Dirk

Hello,
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

Sender RFC Adapter , Sender File Adapter - Payload Compression

Sender RFC Adapter or the Sender File Adapter compress the payload of any spaces in between the tags or remove any spaces at the start and end of the payload.
We need to pass the spaces as is in the message payload to the receiving system?
Is there a way to do it in PI 7.1.

Hi Vikrant,
Preserving white spaces while reading a file from FTP
NameA.fieldContentFormatting
- Enter trim to remove all the leading and subsequent blanks for a value found. This is the default.
- Specify nothing to ensure that the value remains unaltered.
For RFC you need to check your payload to see whether spaces are coming from R/3 itself or not.
Regards
joel

Not getting payload in segments at SXMB_MONI

Hi,
I am doing scenario HTTP_XI_IDoc.i am sending the payload as thru component monitoring
<?xml version="1.0" encoding="UTF-8"?>
<p2:FICO_DT xmlns:p2="http://igate.com/peoplesoft/peoplesoft_ficoxrpm">
 <PROJID>PROJECT01</PROJID>
 <TASKID>TSK01</TASKID>
 <APPLICATION>SAPCO</APPLICATION>
 <LS>PSFT01</LS>
 <ORGTYPE>COA</ORGTYPE>
 <ORGID>0001</ORGID>
 <ORGCURR>USD</ORGCURR>
 <OBJLINK>100159</OBJLINK>
 <COBJTYPE>IO</COBJTYPE>
 <COBJID1>100159</COBJID1>
 <COBJID2>100159</COBJID2>
 <OBJCURR>USD</OBJCURR>
 <VALTYPE>41</VALTYPE>
 <VERSION>000</VERSION>
 <FISCYEAR>2005</FISCYEAR>
 <COSTCAT>0000415000</COSTCAT>
 <PERIODTYPE>Y</PERIODTYPE>
 <PERIODID>1</PERIODID>
 <PSTRTDATE>20030517</PSTRTDATE>
 <PENDDATE>20050817</PENDDATE>
 <AMTINORGCURR>140000</AMTINORGCURR>
 <AMTINOBJCURR>2580000</AMTINOBJCURR>
</p2:FICO_DT>.
In SXMB_MONI ia m able to see my outbound message as specified above.The thing here is i am not able to see my payload in the segments.it is showing like below.
<?xml version="1.0" encoding="UTF-8" ?>
- <RPMINTF1>
- <IDOC BEGIN="9999">
- <E1PRJTS SEGMENT="9999">
- <E1OBLKS SEGMENT="9999">
- <E1OBKFD SEGMENT="9999">
 <E1PDAMT SEGMENT="9999" />
 </E1OBKFD>
 </E1OBLKS>
</E1PRJTS>
</IDOC>
</RPMINTF1>.
I would like to see message like..
<IDOC BEGIN="9999">
- <E1PRJTS SEGMENT="9999">
 <PROJID>PROJECT01</PROJID>
 <TASKID>TSK01</TASKID>
 <APPLICATION>SAPCO</APPLICATION>
 <LS>PSFT01</LS>
 <ORGTYPE>COA</ORGTYPE>
 <ORGID>0001</ORGID>
 <ORGCURR>USD</ORGCURR>
- <E1OBLKS SEGMENT="9999">
 <OBJLINK>100159</OBJLINK>
 <COBJTYPE>IO</COBJTYPE>
 <COBJID1>100159</COBJID1>
 <COBJID2>100159</COBJID2>
 <OBJCURR>USD</OBJCURR>
- <E1OBKFD SEGMENT="9999">
 <VALTYPE>41</VALTYPE>
 <VERSION>000</VERSION>
 <FISCYEAR>2005</FISCYEAR>
 <COSTCAT>0000415000</COSTCAT>
 <E1PDAMT SEGMENT="9999" />
 <PERIODTYPE>Y</PERIODTYPE>
 <PERIODID>1</PERIODID>
 <PSTRTDATE>20030517</PSTRTDATE>
 <PENDDATE>20050817</PENDDATE>
 <AMTINORGCURR>140000</AMTINORGCURR>
 <AMTINOBJCURR>2580000</AMTINOBJCURR>
 </E1OBKFD>
 </E1OBLKS>
</E1PRJTS>
</IDOC>
Plz tell me where could be the problem.The XI is able to post the IDOC with 51 error in SAP.
The same thing which is specified above is working fine with HCM data.but not working with FI/CO.
Thanks in advance
Sridhar Raju Mahali

Hi Sridhar,
In the 2nd line of the payload check the entry.
You are giving
<?xml version="1.0" encoding="UTF-8"?>
<p2:FICO_DT xmlns:p2="http://igate.com/peoplesoft/peoplesoft_ficoxrpm">
make it
<?xml version="1.0" encoding="UTF-8"?>
<p2:FICO_MT xmlns:p2="http://igate.com/peoplesoft/peoplesoft_ficoxrpm">
Regards,
Vijay

Custom doc by email - sender not identified

Hi gurus,
My config is , remote is sending a custom xml document by email to host.
I have configured the document, partners and listening channels. I have configured xpath also.
In metrics/reports i find b2b reads the email but could not find who is the sender/remote TP.
The same file sent via ftp is successfully identified by b2b. I have configured the ftp folder name same as the remote tp name. Then it works fine.
Can you please help me what am i missing here?
Message:
Id     7F00000112AA71BA7A3000003E10F18E
Message Id     7F00000112AA71BA2C5000003E10F18A
Refer To Message     Refer To Message
Sender Type
Sender Value
Receiver Type     Generic Identifier
Receiver Value     [email protected]
Sender
Receiver     Host
Agreement Id
Agreement
Document Type     CustomPO
Document Protocol     Custom
Document Version
Message Type     REQ
Direction     INBOUND
Error Code     B2B-50547
Error Description     Machine Info: (localhost.localdomain) Description: Agreement not found for trading partners: FromTP null, ToTP Host with document type CustomPO-CustomPO-INBOUND.
Thanks
Ganesh

Hi Anuj,
Actually i have not configured any generic identifier.
Now that i have configured a generic identifier in remote TP (Generic identifier - [email protected]), i am getting the same result.
Sender Type
Sender Value
Receiver Type     Generic Identifier
Receiver Value     [email protected]
Sender
Receiver     Host
I am wondering how the mail id is coming up in receiver value & showing up the receiver as Host correctly?
I did see the logs, but could not get anything useful.
Msg :
Refer To Message     Refer To Message
Sender Type
Sender Value
Receiver Type     Generic Identifier
Receiver Value     [email protected]
Sender
Receiver     Host
Agreement Id
Agreement
Document Type     PURCHASEORDER
Document Protocol     Custom
Document Version
Message Type     REQ
Direction     INBOUND
State     MSG_ERROR
Acknowledgement Mode     NONE
Response Mode     ASYNC
Send Time Stamp     Friday, August 27, 2010 5:36:20 PM GMT+10:00
Receive Time Stamp     Friday, August 27, 2010 5:36:20 PM GMT+10:00
Document Retry Interval     0
Document Remaining Retry     0
Native Message Size     3554
Translated Message Size
Business Action Name
Business Transaction Name
Xpath Name1
Xpath Value1
Xpath Expression1
Xpath Name2
Xpath Value2
Xpath Expression2
Xpath Name3
Xpath Value3
Xpath Expression3
Correlation From XPath Name
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name
Correlation To XPath Value
Correlation To XPath Expression
Wire Message     Wire Message
Application Message     Application Message
Payload Storage     Payload Storage
Attachment     Attachment
Label
Collaboration Id     C0A8010D12AB279C9BE0000073EF1AFE
Collabration Name
Collabration Version
Business Action Name
Exchange Protocol Name     Generic Email
Exchange Protocol Version
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code     B2B-50547
Error Description     Machine Info: (ganesh-vm) Description: Agreement not found for trading partners: FromTP null, ToTP Host with document type PURCHASEORDER-FSX_1.50-INBOUND.
Error Level     ERROR_LEVEL_COLLABORATION
Error Severity     ERROR
Error Text     Agreement not found for trading partners: FromTP null, ToTP Host with document type PURCHASEORDER-FSX_1.50-INBOUND.
FTP msg : (success)
Id     C0A8010D12AB226745F0000073EF1A8C
Message Id     C0A8010D12AB226745D0000073EF1A8B-1
Refer To Message     Refer To Message
Sender Type     Name
Sender Value     Remote
Receiver Type     Name
Receiver Value     Host
Sender     Remote
Receiver     Host
Agreement Id     FSX__PO
Agreement     FSX__PO
Document Type     PURCHASEORDER
Document Protocol     Custom
Document Version     FSX_1.50
Message Type     REQ
Direction     INBOUND
State     MSG_COMPLETE
Acknowledgement Mode     NONE
Response Mode     ASYNC
Send Time Stamp     Friday, August 27, 2010 4:05:17 PM GMT+10:00
Receive Time Stamp     Friday, August 27, 2010 4:05:17 PM GMT+10:00
Document Retry Interval     0
Document Remaining Retry     0
Native Message Size     3459
Translated Message Size     3459
Business Action Name
Business Transaction Name
Xpath Name1     XPathName1
Xpath Value1
Xpath Expression1
Xpath Name2     XPathName2
Xpath Value2
Xpath Expression2
Xpath Name3     XPathName3
Xpath Value3
Xpath Expression3
Correlation From XPath Name     CorrelationFromXPathName
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name     CorrelationToXPathName
Correlation To XPath Value
Correlation To XPath Expression
Wire Message     Wire Message
Application Message     Application Message
Payload Storage     Payload Storage
Attachment     Attachment
Label     soa_b2b_ - Fri Aug 27 15:28:33 EST 2010
Collaboration Id     C0A8010D12AB226713C0000073EF1A8A
Collabration Name
Collabration Version
Business Action Name
Exchange Protocol Name     Generic FTP
Exchange Protocol Version     1.0
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code
Error Description
Error Level
Error Severity
Error Text
Thanks
Ganesh
Edited by: Ganesh on Aug 27, 2010 5:41 PM

B2B is not validating payloads against uploaded schemas

Hi Ramesh,
We setup our B2B to validate the payloads
but its really not happening.
We sent some invalid payloads, B2B sent them to TP successfully.
I set Is validation to True in Business action setup
Thanks
Praveen

Hi Sumit,
We are also planning to send Custom XML Document over HTTP. Could you please let us know the detailed steps on how we can configure the same in B2B.
I tried using Custom XML Document Over AS2 but the particluar schema is not coming up in B2B WSIL Browser in JDeveloper.
Appreciate your help and co-operation.
Thanks In Advance,
Dibya

ATTRIBUTE_IDOC_METADATA : Sender not in payload

Similar Messages

Maybe you are looking for