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.

Similar Messages

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.

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.

I was trying to installed new ios update and suddenly my WIFI connection got desconnect. now I am trying to restore my Ipad2 but getting error saying "the Ipad could not restored, An unknown error accured (3194).

I was trying to installed new ios update and suddenly my WIFI connection got desconnect. now I am trying to restore my Ipad2 but getting error saying "the Ipad could not restored, An unknown error accured (3194)". so please help me out to resolve the same.

When I restart my iPad the connect to iTunes comes up and stays on until it shuts down again, I have read a report from Apple support suggesting I reinstall iTunes so I might try that again and also your suggestion which i shall also try, but thanks again - rg1547

SAP Web Service error text : The database returned a value containing an error , type CX_SY_OPEN_SQL_DB

Hello Guru's,
we are creating sales order in SAP from a quote created in .NET, through Web Service created in SAP, and consumed in .NET.
When ever a order is created in SAP for a given quote, SAP returns the sales order number to .NET.
Orders are getting created as expected, but once in a while we are getting the following error from webservice :
Web service processing error; more details in the web service error log on provider side (UTC timestamp 20140609173429; Transaction ID 4DFCEFE33301F1EBB5CE00155D0B4530)
But the problem is order is getting created in SAP for the perticular quote for which we are getting the above error and this order number is not getting returned to .NET.
Upon analysis in TCODE SRT_UTIL for the above transaction ID, has the following details , which are hardly help full to resolve the error.
----TYPE                                  CX_SY_OPEN_SQL_DB
----ERROR_TEXT                   The database returned a value containing an error
----CX_SY_NO_HANDLER
-----CLASSNAME                     CX_SY_OPEN_SQL_DB
This Exception raised by Web Service application
Could you please help in resolving this issue or alteast provide an approach for the same.
Thank you,
Suresh.

Thank you Bhaskar,
How can we clarify whether the error is from SAP or Web part.
I have checked ST22, but there is not entry for the perticular exception transaction ID
My exception time stamp is
-------------------START-------------6/9/2014 1:34:33 PM
Error :Web service processing error; more details in the web service error log on provider side (UTC timestamp 20140609173429; Transaction ID 4DFCEFE33301F1EBB5CE00155D0B4530)
-------------------END-------------6/9/2014 1:34:33 PM
In al11, i found the following for the perticular exception time stamp
**** Trace file opened at 20140609 133431 Eastern Daylight Time, by disp+work
**** Versions SAP-REL 720,0,500 RFC-VER U 3 1442251 MT-SL
XRFC> Begin of user trace
XRFC> ---------------------------------------------------------------------
XRFC>                                                                     <
XRFC> TRACE SOAP RUNTIME - header                                         <
XRFC>                                                                     <
XRFC> ------------------------------------------------------------------ <
XRFC> REQ_SIZE   : 2685                                                   <
XRFC> RESP_SIZE : 0                                                      <
XRFC> PARENT_ID : ROOT_CALL_ID                                           <
XRFC> TRC_KEY    : 40FCEFE3BD6EF184B5CE00155D0B4530                       <
XRFC> REQ_BASED :                                                        <
XRFC> SESSION_ID : 0003925540FCEFE3BD6EF17DB5CE00155D0B4530               <
XRFC> TS_CALL    : 20140609173408.2880000                                 <
XRFC> SY_UNAME   :                                            <
XRFC> HOSTNAME   :                                              <
XRFC> SY_SID     : PRD                                                    <
XRFC> SY_MANDT   : 300                                                    <
XRFC> SYS_NR     : 19                                                     <
XRFC> APPLSERVER :                                      <
XRFC> ISPRESCHED : X                                                      <
XRFC> DURATION   : 21810                                                  <
XRFC> NETHDRTIME : 21810                                                  <
XRFC> CALL_STATE : 2                                                      <
XRFC> ERRORTYPE : APPLFAIL                                               <
XRFC> ERRORAREA : APPL                                                   <
XRFC> CTXDP_TYPE : SOAP_RUNTIME                                           <
XRFC> SYNC_ASYNC : S                                                      <
XRFC> LOCATION   : P                                                      <
XRFC> DIRECTION : I                                                      <
XRFC> REQ_ID     : 91C57815916E421CA9F3D652FFACE9C7                       <
XRFC> RESP_ID    : 00155D0B45301EE3BBFF89A0267EB5CE                       <
XRFC> MSG_STATE : 114                                                    <
XRFC> IF_NAME_I : ZSD_CS_CREATE_SALESORDER_SERVI                         <
XRFC> IF_NS_E    : urn:sap-com:document:sap:soap:functions:mc-style       <
XRFC> IF_NAME_E : ZSD_CS_CREATE_SALESORDER_SERVI                         <
XRFC> ISSHORTCUT :                                                        <
XRFC> TRC_PATT   : WSTEST                                                 <
XRFC> TRC_SSID   : PRD_19                                                 <
XRFC> TRC_USER   :                                           <
XRFC> TRC_TS     : 20140609173409                                         <
XRFC> TRC_COUNT : 99                                                     <
XRFC> TRC_EXT    :                                                        <
XRFC> COMPLETE   : OK                                                     <
XRFC> CALLEDPROG : ZSD_CS_CREATE_SALESORDER_SERVI                         <
XRFC> SOAP_APPLI : urn:sap-com:soap:runtime:application:rfc:710           <
XRFC> CONF_ID    : 00155D0B45301EE3AEFDAD78756555CE                       <
XRFC> BIND_ID    : 00155D0B45301EE3AEFDAD787565B5CE                       <
XRFC> OP_NAME    : ZsdCsCreateSalesorder                                  <
XRFC> COMM_PATRN : Method:ZsdCsCreateSalesorder                           <
XRFC> OP_NS      : urn:sap-com:document:sap:soap:functions:mc-style       <
XRFC> REMADDRESS : 172.16.11.43                                           <
XRFC> DT_OBJ     : ZSD_CS_CREATE_SALESORDER_SERVI                         <
XRFC> MEMCONSUMP : 296291                                                 <
XRFC> WSHOST     :                                                        <
XRFC> WSPORT     :                                                        <
XRFC> WSPROT     :                                                        <
XRFC> WSCLIENT   :                                                        <
XRFC> WSPATH     :                                                        <
XRFC> PXYHOST    :                                                        <
XRFC> PXYPORT    :                                                        <
XRFC> USEDRFCDES :                                                        <
XRFC> BONAME     :                                                        <
XRFC> PROCCOMP   :                                                        <
XRFC> DEPLOYUNIT :                                                        <
XRFC> ------------------------------------------------------------------ <
XRFC>                                                                     <
XRFC> TRACE SOAP RUNTIME - trace records                                  <
XRFC>                                                                     <
XRFC> ------------------------------------------------------------------ <
XRFC> E SOAP_RUNTIME 20140609173429.7400000 : CL_SOAP_RUNTIME_SERVER      <
XRFC> ->EXECUTE_PROCESSING Exception handling for IF "ZSD_CS_CREATE       <
XRFC> _SALESORDER_SERVI" OP name "ZsdCsCreateSalesorder" MSG ID           <
XRFC> "91C57815916E421CA9F3D652FFACE9C7" user "STULZWEBSERV"              <
XRFC>                                                                     <
XRFC>                                                                     <
XRFC> E SOAP_RUNTIME 20140609173429.7240000 : CL_SOAP_RUNTIME_SERVER      <
XRFC> ->EXECUTE_PROCESSING CX_SOAP_ROOT : An exception has occurred. |    <
XRFC> program: CL_SOAP_RUNTIME_ROOT==========CP include: CL_SOAP          <
XRFC> _RUNTIME_ROOT==========CM004 line: 120                              <
XRFC>                                                                     <
XRFC>                                                                     <
XRFC> E SOAP_RUNTIME 20140609173429.7400000 : CL_SOAP_RUNTIME_SERVER      <
XRFC> ->EXECUTE_PROCESSING CX_SY_NO_HANDLER : An exception with the type <
XRFC> CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor    <
XRFC> declared in a RAISING clause | program: SAPLSTXD include: LSTXDFDB <
XRFC> line: 200                                                           <
XRFC>                                                                     <
XRFC>                                                                     <
XRFC> E SOAP_RUNTIME 20140609173429.7400000 : CL_SOAP_RUNTIME_SERVER      <
XRFC> ->EXECUTE_PROCESSING CX_SY_OPEN_SQL_DB : The database returned a    <
XRFC> value containing an error | program: SAPLSTXD include: LSTXDFDB     <
XRFC> line: 227                                                           <
XRFC>                                                                     <
XRFC> ---------------------------------------------------------------------
XRFC> End of user trace

The expression in field u0093Company_Codeu0094 contains an error: Syntax error

Hi all,
I have added an extra variable to my query. Then in VC I refreshed my queries and added an extra field to the input form I used. I also updated the submit actions. Now when I deploy it says
The expression in field Company_Code contains an error: Syntax error
How to solve this?
Thanks in advance,
Ralph

You can double click on the error and then you get more information and the issue is selected by the Visual Composer. Maybe there is an error in your formula or the value, which you have assinged has a wrong data type.
Best Regards,
marcel

Error while activating DTP : database returned a value containing an error

Hi ,
I am getting an error as "The database returned a value containing an error"
while activating the DTP. Can neone suggest any solution for this error .
The system is also not allowing to delete the DTP and giving the same error as above one .

Are you receiving a similar error as below from the log:
Creation of PSA /BIC/B0001995 failed
Error during creation of DDIC sources of Data Transfer Process DTP_4DGGKC0NCCP394FEOOSQC68Y3
If yes then look into SAP Note 1145673 - Extracting from InfoProviders with navigation attributes. Application of this note should resolve the issue.

Sender Port Error in SAP ECC for IDoc

Hi,
I am creating scenario IDOC -> XI -> JDBC with Customer Master IDoc.
After sending it with we19 he said "IDoc sent to SAP system or external program".
In we02 and we05 the IDOC it says "Data passed to port OK".
But in SM58, the IDoc ends in error saying
Transaction IDX1: Port SAPIDST100, client 600, RFC destination contains error.
What I identified that the port SAPIDST100 is the sender port in the IDoc being send. However, for PI we do not need to maintain sender port.
Business Systems:
Sender : SAP ECC
Receiver: SAPPID
Kindly provide your inputs.
Thanks
Rahul

Hi Rahul,
thanks for the information that your scenario is working fine.
But i want to clarify some points:
   - If you send out an IDoc from an ECC system, the senderport is filled with SAP+<system-id> by the SAP IDOC API,
     i.e. if your system id is "ABC", the senderport is "SAPABC"
      => your senderport SAPIDST does not match this template, so i assume you entered the value for the senderport
     manually in the idoc test utility WE19
   - if you send out an idoc, only the receiver port must be created in transaction WE21, it is not necessary to create
     the senderport in WE21, this is not necessary and did not solve your problem
- the idoc was send from ECC (application system with application IDoc metadata) to an XI/PI system (basis system
    without application idoc metadata
   The IDoc adapter on the pi system must analyze the IDoc segments and must know the idoc application metadata,
   but this is not known. So the idoc adapter on PI side looks at the senderport to identify the sender.
   In transaction IDX1 an rfc-destination can be configured to point to the sendersystem with that senderport
   With this rfc-destination the IDoc adapter tries to read the idoc aplication metadata from the ECC system and stores it on PI side.
   If there is no rfc-destination configured in transaction IDX1 on PI side you get the error mentioned in your request.
   I assume that in transaction IDX1 somebody configured the correct RFC-Destination.
I hope this clarification helps you to understand the error and the solution.
Kind regards,
Andreas Dahl

Error when testing the standard idoc number of type PORDCH

while i was testing the idoc message type PORDCH in we02,i have got an error message type saying as
the following below are the steps which i have done in testing the idoc
WE02
Enter Idoc 705556 and execute
Opened status record.
Looked at the error under status 51. it says
An error has occurred assigning data (E1BPMEPOITEM )
Message no. B1527
Diagnosis
To call a BAPI the IDoc data must first be assigned to the relevant BAPI interface parameters.
An error has occurred when carrying out this operation, possibly due to an incorrect data type or data format in the segment E1BPMEPOITEM.
Procedure
Check that the data types in the IDoc data record matches the data types in the BAPI parameter.
You can reproduce the same error with BD87
Enter Idoc number and execute.
Drill down to the error (debug) and click process.
sap has shown the following error message in one of the status record when i tested using transactions bd87 and we02.
so wat must i do ,can i implement the SAP Note 731418 - ALE interfaces for PORDCR1 and PORDCH
are not up-to-date or is there any alternate way
will be waiting for quick and good response
bye.
Regards.
Varma Mandapati

Hi Seeta Ram,
try to reprocess the idoc using the Program
Program RBDMANI2 for status 51 ..
Read the below document for the Possible error
Processing in the Application Layer
The posting function module either calls a standard
SAP transaction, using the call transaction command
for posting the document, or invokes a direct input function module.
The results of the execution are passed back via the function
module's output parameters. If posting is successful, an application
document is created. The IDoc gets a status code of 53 (Application document posted).
If errors occur, the IDoc gets a status code of 51 (Application document not posted).
Regrads,
Prabhudas
Edited by: Prabhu Das on Apr 17, 2009 11:22 PM
Edited by: Prabhu Das on Apr 17, 2009 11:23 PM

Unknown Error - new to CRM - Contracts IDOC

hi guru's ,
my object is to load contract details to CRM .. so i have used LSMW with IDOC's...
I have Finished with LSMW ....
I tried to Load 6 documents... through the LSMW..... all the IDOC are in Status 53... and it say that its executed Successfully....
but when i see the Transaction. only the last document is seen..
I have checked SMW01 ( no error's )
I have check SM13( no update termination error's)
when I am loading a OPEN contract i should get.... a message saying that ( THE CONTRACT WILL BE REGISTERED... NOW I AM NOT GETTING the message)
Please do help me
Regards,
vj

Thanks for the feedback. With MobileMe being discontinued next June 30th and with it all websites this might be a good time to find another web host and new blog. There is an application out that can convert an iWeb blog into a WordPress blog. You can get more information about it from this tutorial:
No. 23 - Life After MobileMe
OT

Error in creation of PurOrd IDoc

Hi All,
I have set up the output type for PO and created patner profiles and also add the message types ORDER and ORDCHG but when I save the PO and check the messages, I get an error: " No recipient found for message type ORDERS in the ALE Model ".
What could be the possible problem?
Highly appreciate any kind of help.
Thanks in advance,
Shweta
PS: <b><REMOVED BY MODERATOR></b>
Message was edited by:
Alvaro Tejada Galindo

Hi
Check the Partner Profile in WE20 correctly
also see the steps for it as per the doc
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Regards
Anji

Error while creating an outbound idoc using idoc type delvry02

hi,
i getting the following error while creating an outbound idoc(outbound shipping notification) using message type " DESADV" and IDOC TYPE " DELVRY02"
ERROR:
" SPECIFY EITHER ADDRESS NO OR ADDRESS HANDLE"
MESSAGE NO: AM053
Help would be appreciated.
regards
leo

The message is kind of self-explanatory. It seems that some address (delivery address ?) is required but is missing from the IDoc. If it's a syntax error, then the segment with error will appear in red in WE05 transaction.
It is also possible that you have filled some field that you should have left blank and now SAP is trying to find an address based on that field.
Check your IDoc contents. It's really hard to tell from the distance since the requirements and configuration could be very different in different systems. Sometimes the OSS note search by message ID and number is also helpful.

Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML

Hello Rescue Team,
I am facing the following error :\
16.06.2014 23:22:42.164
Error
Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.166
Error
MP: exception caught with cause com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Exception caught by adapter framework: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Transmitting the message to endpoint <local> using connection EDISeparator_http://sap.com/xi/XI/EDISeparator failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
and the payload transferred is as attached in the attachment below.
I have refered various blogs, however I am still not able to understand how to get the exact location of the error location..According to me, the value that is giving trouble is OTH in <BSARK> however I have checked the permitted values for BSARK on ECC and OTH is maintained.
Can you please help how I can resolve this error.
Thanks
Saurabh

Hi Guys,
This is solved..I corrected the date format of the ZZTIME segment from 1157 to 115700.
Thanks
Saurabh

Lock table overflow 1 & Error 7 when sending an IDoc

dear all,
we r getting error in purchasing cube for itm datasource
2lis_o2_itm for delta...
1.Lock table overflow 1
2.Error 7 when sending an IDoc
3.Errors in source system
when i check in details it is showing :
Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
its daily delta..plz give me solution its urgent....
at request in manage...we got some records...wat shud the process..
Thanks in adv
pinky reddy
Edited by: pinky reddy on Apr 8, 2008 7:42 AM

solved

RFC error "No authorization to send IDOCs with message type ..."

Hi all,
I have now tried just about everything I could think of, applied all the notes mentioned on this forum but still no luck. Can anyone please help ...
I have got a file to idoc scenario, the status in the sxmb_moni is successful, but the outbound processing logs an error. When I go to transaction SM58 I get an error for the user XIAFUSER with the message "No authorization to send IDOCs with message type WPUUMS".
I have tried giving this user SA_ALL access and still got the same error thus concluding that this is not an authorisation error.
Any suggestions?
Regards,
Liesel

Hi Liesel,
The RFC destination that you have put in IDoc communication channel must be present in your SAP XI system, transaction SM59 also.
Please check if the user id/Password that you have given has all the authorization.
Also check the User ID and passwrord in SM59 in R3 and see if a Remote Login is possible.
There is also some configuration by which the clients are allowed / blocked from receiving Idocs from XI. Basis guys can do it for you. Please approach your basis consultant. Hopefully that helps..
Regards,
Abhy Thomas

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

Similar Messages

Maybe you are looking for