IDoc included in IDoc packet containing an error: transfer it separately

Hi Gurus,
I'm having this problem in our ECC side. I already did what Michal said in his blog:
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
I have bundled the multiple IDOCs into 1 MATMAS.
But I'm still having the error IDoc included in IDoc packet containing an error: transfer it separately.
I've searched in the forums and none of them worked for me.
Thanks in advance!

Disable packaging or change the Partner Profile on WE02 transaction to "process immediately" the IDOCS.
When you process the IDOCS in background mode, it will create packages (it is enabled by default), and in case any of them fail you won't be able to see the root cause, but will have to go to BD97 transaction to process them again. Therefore, please use the "process immediately" or disable packaging and then you will be able to either see the error or process it because it won't fail because of another IDOC.

Similar Messages

Getting error 51 saying 'IDoc included in IDoc packet containing an error'

When I am processing idoc in LSMW, getting error saying 'IDoc included in IDoc packet containing an error'.
Can any one tell me how to resolve this.

Hi,
Change the packet size to 1 then process again.

Getting error saying 'IDoc included in IDoc packet containing an error'.

hi experts
When I am processing idoc in LSMW, getting error saying 'IDoc included in IDoc packet containing an error'.I changed the packet size also but it was not resolved.
Can any one tell me how to resolve this.

Hi,
Check below link......
Getting error 51 saying 'IDoc included in IDoc packet containing an error'
even this link is not solving problem then check the aplication log to get exact error text.
Thanks,
Asit Purbey.

SM58 - IDoc adapter inbound: IDoc data record table contains no entries

Trying to send Idocs from SAP ECC6.0 via PI 7.0 up until 2 days ago there was no problem.
Since yesterday, only one specific type of Idoc does not make it into XI (PI). In the Idoc monitor (WE02) the idocs that were created gives status 3 which is good. But all Idocs of that specific type (ZRESCR01) does not go to XI. I can only find them bakc in SM58 where it gives the following message:
IDoc adapter inbound: IDoc data record table contains no entries
I have checked SAP notes 1157385 and also 940313, none of them gives me any more insight into this error. I have also checked all the configuration in WE20, SM59, and in XI (repository and directory) and in XI IDX1, IDX2 but could not find anything that would cause this. I can also not think of anything that changed since 2 days ago.
Please point me in the right direction.

hi,
i think in sm 58 u can find entries only when there is some failure in login credential .
if there is change in IDoc structure than you have to reimport the idoc metadata defination at IDX2.otherwise not requird.
please check the logical system name pointing to the your requird target system....
please also verify thet your port should not be blocked.
pls find the link it may help
Monitoring the IDOC Adapter in XI/PI using IDX5
regards,
navneet

PO item 00010 included in IDoc twice

Hi:
I work in SRM 5.0 ,MM-SUS scenario .
The vendor does confirmation in SUS .I can find the IDOC from XI .But there is an error about the IDOC .It dispalys "PO item 00010 included in IDoc twice", What is the reason?
PS: I create IDOC Distribute model in the ECC system ,and the Sender is SUSClient ,Receiver is ECC Client,the message type is :ORDRSP.Is there something wrong ?Or I must Create the Distribute model in SUS Client?
I create partner profile in ECC system ,and define the message Type -ORDRSP.
BestRegards.
Alex

I have resolved it .Because of the inbound partner.

Web Service to IDoc scenario: No receiver could be determined error

Hi. I am working on a web service to IDoc scenario. I am receiving 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>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I've taken the XML message being sent to me and tested the mapping and I've completed the test configuration in the IB. Both work fine. Any ideas? I've been looking into this for a couple of days, so I've been through all the previous posts I could find.
Thank you.
Nicole

hi,
This is not related to receiverdetermination ,whether you creaeted or not.
It is somthing related to receiver systemwhich was configured in Receier determination.
check the target BS is correct or not or the inbound interface.
Did you configured the proper receiver technical system..
OR
Check the Receiver Determination is configured correctly. i.e R/3
Verify all the configurations like SM59, Partner Profile/Logical systems. etc. Also check in SM58 of R/3 system.Make sure that All the objects are activated in the Directory.Refresh the cache.Verify is the business system is pointing to correct R/3 system . Go to Business system/Service->Menu->Adapter specific identifiers in the directory
You can test your configuration with sample
payload.
In ID goto to TOOLS -
> Test Configuration for testing.
Hope in this way you can still find at which point the interface goes wrong.

Transfer of IDOC from R/3 to XI - SM58 error

Hi
i am working on scenario where the output of the delivery created in R/3 is a idoc to be sent to XI.
When i create a delivery of type LO(without reference to Sales order) the IDOC gets passed on to XI successfully
But when i create a delivery of type LF (with reference to Sales order) the IDOC gets stuck in SM 58 in R/3.
I dont know why this is happening.
when i check the sm58 it shows the following in Status text:
EDISDEF: Port SAPEC1 segment defn E2EDL43 in IDoc type DELVRY05 CIM type where SAPEC1 is the port which i have defined in XI for R/3 DELVRY05 is IDOC type.
please help me understand this error
Thanks and regards,
Amit Deshpande

Hi,
I tried doing as per your suggestions
I deleted the DELVRY05 in IDX2 and tried to execute the process as suggested by Renjith but same error continues.
I checked as per Sreeram's view this segment E2EDL43 which is not there. but when i checked the we60 in R/3 this segment is of type E1EDL43 which is there in DELVRY05.
Do u have any further observations?
thanks and regards,
Amit Deshpande

Standard program for creating outbound IDoc including wbs + cost planning

Hello,
a)
Before we start developing our own ABAP, I would like to ask the forum if somebody knows if there is already a standard ABAP program for generating outbound IDocs including wbs-element data (CJ20N; wbs ID, description) plus annual data from the cost planning (CJ41; such as fiscal year and costing items from unit costing; quantity, unit, price per unit, total price, description of item) ?
b) we are planning to use the logical message /ISDFPS/PS, basic type /ISDFPS/PS01 and enhance this IDoc with segments for the costing items from the cost planning.
Question: Do you know if there is a standard IDoc which has segments for both wbs-element data and costing items?
Kind regards
Viveka Schwartz

Hi Frank,
Did u check this Link on the PP confirmaitos[LINK|http://help.sap.com/saphelp_47x200/helpdata/en/12/3bbc1c504811d182c20000e829fbfe/frameset.htm]
Reg
Dsk
Edited by: DSk on Sep 14, 2010 3:44 PM

Difference between Master Idoc and Communication Idoc.

Can anyone list out the difference between Master Idoc and Communication Idoc?

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
Form and content: IDoc terminology
As is often the case with proprietary technologies, SAP assigns specific, object-oriented meanings to familiar terms. When referring to IDocs, the term document refers to a set of data comprising a functional group of records with a business identity. (For example, all the data in a purchase order, or all the profile information of a supplier in a supplier master record.)
A message refers to the contents of a specific implementation of an IDoc; its a logical reference. This differs from a reference to the IDoc itself, which specifies the messages physical representation. Think of it this way: If youre watching a parade pass by, the mayor waving to the crowd from his limousine is the message, and the mayors limousine (which is specific to the mayor) is the IDoc. Youre building a logical object, and the IDoc is both its container and the vehicle that moves it.
The IDoc control record
Each IDoc has a single control record, always the first record in the set. The structure of this record describes the content of the data records that will follow and provides administrative information, such as the IDocs functional category (Message Type/IDoc Type), as well as its origin (Sender) and destination (Receiver) as in conventional EDI
Layout of an IDoc control record
This cover slip format informs the receiving system of the IDocs purpose, and the receiving system uses it to determine the correct processing algorithm for handling the arriving IDoc.
Data records
The data records following the control record are structured alike, including two sections: a segment information section and a data section.
In the first part of a data record, the segment information section describes the structure of the data that follows, for the benefit of the IDoc processor. There is a segment name (like an EDI segment identifier) that corresponds to a data dictionary structure to which the IDoc processor has access. The remaining information is useful for foreign systems, such as a partner companys Oracle system, which has no such data dictionary.
The second part of the record is the data itself, a storage area of 1,000 characters.
Status records
If youve ever ordered a package from a faraway location and tracked its progress using the Internet-based tracking utilities now provided by most major parcel carriers, youre familiar with the list of stops and transfer points through which a package passes on its way to you.
This collection of records is exactly what youll see in an IDoc that has begun its work. Following the data records in an IDoc, status records accumulate as an IDoc makes its way from one point in a process to another.
Typically, an IDoc will acquire several of these records as its does its job. They are simple records, consisting of a status code (there are more than 70 codes, covering a broad range of conditions and errors), a date/time stamp, and some additional status information fields for system audit purposes. In addition, as errors occur in the processing of an IDoc, status records are used to record these errors and the date/time of their occurrence.
IDoc Base
IDocs, as data formatting tools, enable the easy sharing of data between databases and applications within a company as well as being an efficient data courier between companies. Typically in SAP, a database of IDoc definitions exists, to which any application may have access.
This IDoc Base gives all the applications and processes in your company domain the capacity to send, receive, and process a document in a contextually appropriate way, without doing anything to the data. For example, a purchase order IDoc can filter through every process it touches, passing from system to system, accumulating status records to track its progress.
Every department using the data can use it appropriately without any cumbersome intermediate processes, because each department draws its key to interpreting the IDoc from the same source.
Multiple messages
One cumbersome feature of conventional EDI is the embedding of more than one functional record type in a document. The unwieldy X-12 888 Item Maintenance transaction set is an example: It purports to handle so many different configurations of product master data that it is horrifically difficult to integrate into an existing system.
IDocs, on the other hand, handle multiple messages with ease. Given the centralized IDoc interpretation that SAP provides to all its parts, its no problem to define an IDoc that will contain more than one message, that is, more than one data record type.
A customer master IDoc, for example, may contain customer profile information records for a customer with many locations. But it may also contain location-specific pricing information records for that customer in the same document. This is an incredibly efficient way of bundling related records, particularly when passing large amounts of complex information from system to system Records in a multiple-message IDoc

Response message contains an error

Hi Experts,
i have a idoc to soap scenario. i am able to send idoc to soap adapter. but at receiver communication channel am getting following error : response message contains an error XIServer/UNKNOWN/ADAPTER/_JAVA_EXCEPTION. Parsing ERROR.ORG.XML.SAXParselException. Premature end of file.
Pls suggest

Hi Raja- It seems to be a data quality issue.
Check for the value @ 1447 position in the xml message that you are trying to send to web service..
may be a date filed/decimal value which is not in expected format.

XML IDOC to Native IDOC Conversion

Hi,
We have a scenario, where we need to convert XML idoc into native idoc and write to a file. I am doing this based on
How To Convert an IDoc-XML structure to a flat file and vice versa in XI 3.0.
When I first executed the scenario, I was getting the following error
Z_ABAP_MAPPING_IDOC_TO_FLAT (type SAP-ABAP, kernel error ID UNCAUGHT_EXCEPTION) An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause Dereferencing of the NULL reference.
After including the try-catch block, now i am just getting a blank file without any conversion.
Can anyone help me on this?
Regards,
Ravi

Hi,
It looks to be error in ABAP mapping
To test ABAP mapping in XI use the transaction SXI_MAPPING_TEST after creating a little scenario in the directory.
Or even you could do this with below sample code
Lets create one ABAP mapping class with the method IF_MAPPING~EXECUTE
data: obj type ref to zcl_abap_mapping_test.
data: source type xstring,
result type xstring.
data: param type ref to IF_MAPPING_PARAM,
trace type ref to IF_MAPPING_trace.
create object obj.
try.
CALL METHOD obj->IF_MAPPING~EXECUTE
EXPORTING
SOURCE = source
PARAM = param
TRACE = trace
IMPORTING
RESULT = result.
CATCH CX_MAPPING_FAULT .
ENDTRY.
This is a link very useful for ABAP Mapping :
http://help.sap.com/saphelp_nw04/helpdata/en/86/8280ba12d511d5991b00508b6b8b11/frameset.htm
Or may be think this exception you need to catch it in the ABAP..
This may help u- http://help.sap.com/saphelp_47x200/helpdata/en/55/bff20efe8c11d4b54a006094b9456f/content.htm
just cross verify with this guide-
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3ead790-0201-0010-64bb-9e4d67a466b4
Thanks
swarup

Acknowledgement contains system errors

Hi,
We have a IDOC to File scenario. When we check the status in SXMB_MONI, we are getting processed successfully flag, but getting ICON "acknowledgement contains system errors". And also file is not reaching destination folder. When I check the errors in acknowledgement, I can see the error message "OUTBOUND _ BINDING_NOT_FOUND " and below that some message saying,
"No receiver agreement found for sender BS_Receiver and receiver BS_sender. But my sender is BS_sender and Receiver is BS_Receiver and I have a receiver agreement with that combination. I checked entire configuration scenario and everything is fine.
I don't know why it's taking sender as receiver and receiver as sender and that too in case of receiver agreement only. In all other places sender is shown as BS_Sender and Receiver is shown as BS_Receiver. Anybody experienced this kind of error?

hi,
Just check this guide on how to handle acknowledgements,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
also,if you want you can turn off idoc acknowledgements then you use the report: IDX_NOALE .You can just add the entries in table IDXNOALE from SE16.
IDX_NOALE should run on your R/3.
Just check following SAP Note : 777175
Regards,
Bhavesh

Acknowledge Contains System Errors

Dear Friends,
I am sending the MATMAS idoc from ECC6.0 to LocalSystem using XI.
I got the error in SXI_MONITOR i.e
Acknowledge contains system errors.
R/3 side :
1.created RFC destination for XI
2.PORT For XI
3.Partnerprofile For XI
4.Distribution model view For XI
XI side:
1.created RFC destination For R/3
2.PORT For R/3
In I.D i created Business service for Local System and Business System for R/3 system.
I did this , I am Facing this problem(Acknowledgement contains system errors).
Next What Should I do.
How to resolve this issue.
Friends suggest me please.
Regards,
Shalini Shah.

Hi
Check it out IDX2 - IDoc Meta Data and IDX5 - Idoc Messages received in XI.
I guess Your message have been processed successfully(Black & White Flag).But acknowledge ment contains the system errors.
Go through the below link
http://help.sap.com/saphelp_nw04/helpdata/en/44/932e8896b610bbe10000000a422035/frameset.htm -- Configuring Acknowledgment Requests and follow the steps under Procedure.
You will able to solve u r problem.
Cheers
Veera

Workflow notification delegated to the originator contains an error message in notification content

Hi All,
We are using a workflow for managing User Access Request(to get new responsibilities) where approval hierarchy is set via AME rules.
Facing an issue, when approver has set a vacation rule and to whom the notification delegated happens to be the requester itself.
Notification contains an error message which says like: "Automatic route to <use name> failed. encountered during execution of Generate function 'WF_XML.Generate' for event 'oracle.apps.wf.notification.reassign"
However notification correctly displays its content and also the validation logic that we have put in post notification function while responding to notification is working correctly .
Also If the vacation rule is set to some user other than requester, issue does not appear.
Please guide if faced similar issue or any idea to overcome this.
Thanks in advance!!
Indu

I r-clicked on the error message of the details "Request IDoc : Application document not posted" and selected "Idoc maint in OLTP" and then I saw the error message in the log.
I see that my systems are off a couple minutes.
Should I just reboot these sys's?
DataSource 0TCTIOBJNM_TEXT has to be replicated (time stamp, see long text)
Message no. R3016
Diagnosis
DataSource 0TCTIOBJNM_TEXT does not have the same status as the source system in the Business Information Warehouse.
The time stamp in the source system is 10/31/2007 11:54:29.
The time stamp in the BW system is 10/31/2007 11:52:10.
System Response
The load process has been terminated.
Procedure
Copy the DataSource again and then activate the transfer rules that belong to it. You have to activate the transfer rules in every case, even if they are still active after the DataSource has been copied.

Save style sheet failed : Transformation contains syntax error.

Hello experts,
We are facing a problem, your valuable suggestion can help us to solved the problem.
Brief on system ladsacpe. We are using XI between R/3 and SRM.
Basically we are sending PO IDoc (ORDERS02) to SRM via XI. It also successfuly passed to SRM via XI. In XI SXMB_MONI i can see the checkred flag. Now in SRM SXMB_MONI the flag becomes Red and it shows Below error when i clcik on flag.
" Save Stylesheet failed /1SAI/TXSD5BFE2D6C24B57C0071F:
Transformation /1SAI/TXSD5BFE2D6C24B57C0071F contains syntax error " *
After this error when i check XI SXMB_MONI again, the flag is chekred but Acknowledgement status has error. and the Same error i can see in XI SXMB_MONI.
I think this error is coming when acknowleding back to XI to R/3.
But dont know how to solved?
Can you guys please help.
Thanks in Advance.
Aakash.

Hi Aakash
Try have a look at SAP Note Number: [1157004|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_dwb/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d31313537303034%7d]
Best regards,
Chris

IDoc included in IDoc packet containing an error: transfer it separately

Similar Messages

Maybe you are looking for