<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: IDOC statuses... in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-statuses/m-p/2706518#M627115</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;lt;b&amp;gt; IDOC status codes&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This appendix describes the IDOC status codes and the corresponding event severities. For more detailed information about IDOC status codes, refer to the appropriate SAP documentation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note:&lt;/P&gt;&lt;P&gt;    Harmless events are generated only if the specific IDOC was in an error state in the previous polling cycle. Otherwise, no events are generated. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following table describes outbound IDOC status codes that generate Tivoli Enterprise Console events:&lt;/P&gt;&lt;P&gt;Outbound IDOCs&lt;/P&gt;&lt;P&gt;Code 	Error 	Event Severity 	SAP Meaning&lt;/P&gt;&lt;P&gt;02 	Yes 	Error 	Error passing data to port&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;03 	No 	Error if transaction SM58 indicates an RFC transmission error 	Data pass to port OK &amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;04 	Yes 	Error 	Control information of EDI subsystem&lt;/P&gt;&lt;P&gt;05 	Yes 	Error 	Translation&lt;/P&gt;&lt;P&gt;06 	No 	Harmless 	Translation&lt;/P&gt;&lt;P&gt;07 	Yes 	Error 	Syntax check&lt;/P&gt;&lt;P&gt;08 	No 	Harmless 	Syntax check&lt;/P&gt;&lt;P&gt;09 	Yes 	Error 	Interchange handling&lt;/P&gt;&lt;P&gt;10 	No 	Harmless 	Interchange handling&lt;/P&gt;&lt;P&gt;11 	Yes 	Error 	Dispatch&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;12, 13, 14 	No 	Harmless 	OK&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;15 	Yes 	Warning 	Interchange acknowledgement negative&lt;/P&gt;&lt;P&gt;16 	No 	Harmless 	Functional acknowledgement&lt;/P&gt;&lt;P&gt;17 	Yes 	Warning 	Functional acknowledgement negative&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;18 	No 	Harmless 	Triggering EDI subsystem&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;20 	Yes 	Error 	Triggering EDI subsystem&lt;/P&gt;&lt;P&gt;22 	No 	Harmless 	Dispatch OK, acknowledgement still due&lt;/P&gt;&lt;P&gt;23 	Yes 	Error 	Retransmission&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;24 	No 	Harmless 	Control information of EDI subsystem&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;25 	Yes 	Warning 	Processing despite syntax error&lt;/P&gt;&lt;P&gt;26 	Yes 	Error 	Syntax check&lt;/P&gt;&lt;P&gt;27 	Yes 	Error 	ALE error&lt;/P&gt;&lt;P&gt;29 	Yes 	Error 	Error in ALE services&lt;/P&gt;&lt;P&gt;30 	No 	Harmless 	Ready for dispatch (ALE)&lt;/P&gt;&lt;P&gt;31 	No 	Harmless 	IDOC is marked for deletion&lt;/P&gt;&lt;P&gt;33 	No 	Harmless 	Original of an IDOC which was edited&lt;/P&gt;&lt;P&gt;34 	Yes 	Error 	Error in control record of IDOC&lt;/P&gt;&lt;P&gt;36 	Yes 	Error 	Timeout error; electronic signature not performed&lt;/P&gt;&lt;P&gt;37 	Yes 	Error 	IDOC added incorrectly&lt;/P&gt;&lt;P&gt;38 	No 	Harmless 	IDOC archived&lt;/P&gt;&lt;P&gt;39 	No 	Harmless 	Receive confirmed&lt;/P&gt;&lt;P&gt;40 	Yes 	Error 	Application document not created in target system&lt;/P&gt;&lt;P&gt;41 	No 	Harmless 	Application document created in target document&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following table describes the inbound IDOC status codes that generate Tivoli Enterprise Console events:&lt;/P&gt;&lt;P&gt;Inbound IDOCs&lt;/P&gt;&lt;P&gt;Code 	Error 	Event Severity 	SAP Meaning&lt;/P&gt;&lt;P&gt;51, 52 	Yes 	Error 	Posting error&lt;/P&gt;&lt;P&gt;53 	No 	Harmless 	Posting successful&lt;/P&gt;&lt;P&gt;54 	Yes 	Error 	Error during formal application check&lt;/P&gt;&lt;P&gt;55 	No 	Harmless 	Formal application check&lt;/P&gt;&lt;P&gt;56 	Yes 	Error 	IDOC with error added&lt;/P&gt;&lt;P&gt;60 	Yes 	Error 	Syntax error&lt;/P&gt;&lt;P&gt;61 	Yes 	Warning 	Processing despite syntax error&lt;/P&gt;&lt;P&gt;62 	No 	Harmless 	IDOC passed to application&lt;/P&gt;&lt;P&gt;63 	Yes 	Error 	Error passing IDOC to application&lt;/P&gt;&lt;P&gt;64 	No 	Harmless 	IDOC ready to be passed to application&lt;/P&gt;&lt;P&gt;65 	Yes 	Error 	ALE error&lt;/P&gt;&lt;P&gt;68 	No 	Harmless 	IDOC is marked for deletion&lt;/P&gt;&lt;P&gt;70 	No 	Harmless 	Original of an IDOC which was edited&lt;/P&gt;&lt;P&gt;73 	No 	Harmless 	IDOC archived&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;a href="http://publib.boulder.ibm.com/tividd/td/ITMAN/SC23-4812-00/en_US/HTML/sa51mst256.htm"&amp;gt;refer this for statuses&amp;lt;/a&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;srinivas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;*&lt;STRONG&gt;reward for useful answers&lt;/STRONG&gt;*&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 22 Aug 2007 14:09:51 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-08-22T14:09:51Z</dc:date>
    <item>
      <title>IDOC statuses...</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-statuses/m-p/2706516#M627113</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;During a successfull Oubound IDOC creation and dispatch, what are the sequence of&lt;/P&gt;&lt;P&gt;status we should see i.e which status will follow other status for successful completion&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am concerned with Status 03, 18, 12 and 64.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rajesh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Aug 2007 13:54:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-statuses/m-p/2706516#M627113</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-22T13:54:32Z</dc:date>
    </item>
    <item>
      <title>Re: IDOC statuses...</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-statuses/m-p/2706517#M627114</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ALE/IDOC Status Codes/Messages----&lt;/P&gt;&lt;HR originaltext="-------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;01 Error --&amp;gt; Idoc Added&lt;/P&gt;&lt;P&gt;30 Error --&amp;gt; Idoc ready for dispatch(ALE Service)&lt;/P&gt;&lt;P&gt;then goto SE38 --&amp;gt; Execute the Program RBDMIDOC&lt;/P&gt;&lt;P&gt;29 Error --&amp;gt; ALE Service Layer &lt;/P&gt;&lt;P&gt;then goto SE38 --&amp;gt; Execute the Program RSEOUT00&lt;/P&gt;&lt;P&gt;03 Error --&amp;gt; Data Passed to Port ok&lt;/P&gt;&lt;P&gt;then goto SE38 --&amp;gt; Execute the Program RBDMOIND&lt;/P&gt;&lt;P&gt;12 Error --&amp;gt; Dispatch ok&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Inbound Status Codes&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;50 Error --&amp;gt; It will go for ALE Service Layer&lt;/P&gt;&lt;P&gt;56 Error --&amp;gt; Idoc with Errors added&lt;/P&gt;&lt;P&gt;51 Error --&amp;gt; Application Document not posted&lt;/P&gt;&lt;P&gt;65 Error --&amp;gt; Error in ALE Service Layer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Aug 2007 13:59:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-statuses/m-p/2706517#M627114</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-22T13:59:22Z</dc:date>
    </item>
    <item>
      <title>Re: IDOC statuses...</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-statuses/m-p/2706518#M627115</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;lt;b&amp;gt; IDOC status codes&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This appendix describes the IDOC status codes and the corresponding event severities. For more detailed information about IDOC status codes, refer to the appropriate SAP documentation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note:&lt;/P&gt;&lt;P&gt;    Harmless events are generated only if the specific IDOC was in an error state in the previous polling cycle. Otherwise, no events are generated. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following table describes outbound IDOC status codes that generate Tivoli Enterprise Console events:&lt;/P&gt;&lt;P&gt;Outbound IDOCs&lt;/P&gt;&lt;P&gt;Code 	Error 	Event Severity 	SAP Meaning&lt;/P&gt;&lt;P&gt;02 	Yes 	Error 	Error passing data to port&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;03 	No 	Error if transaction SM58 indicates an RFC transmission error 	Data pass to port OK &amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;04 	Yes 	Error 	Control information of EDI subsystem&lt;/P&gt;&lt;P&gt;05 	Yes 	Error 	Translation&lt;/P&gt;&lt;P&gt;06 	No 	Harmless 	Translation&lt;/P&gt;&lt;P&gt;07 	Yes 	Error 	Syntax check&lt;/P&gt;&lt;P&gt;08 	No 	Harmless 	Syntax check&lt;/P&gt;&lt;P&gt;09 	Yes 	Error 	Interchange handling&lt;/P&gt;&lt;P&gt;10 	No 	Harmless 	Interchange handling&lt;/P&gt;&lt;P&gt;11 	Yes 	Error 	Dispatch&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;12, 13, 14 	No 	Harmless 	OK&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;15 	Yes 	Warning 	Interchange acknowledgement negative&lt;/P&gt;&lt;P&gt;16 	No 	Harmless 	Functional acknowledgement&lt;/P&gt;&lt;P&gt;17 	Yes 	Warning 	Functional acknowledgement negative&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;18 	No 	Harmless 	Triggering EDI subsystem&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;20 	Yes 	Error 	Triggering EDI subsystem&lt;/P&gt;&lt;P&gt;22 	No 	Harmless 	Dispatch OK, acknowledgement still due&lt;/P&gt;&lt;P&gt;23 	Yes 	Error 	Retransmission&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;24 	No 	Harmless 	Control information of EDI subsystem&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;25 	Yes 	Warning 	Processing despite syntax error&lt;/P&gt;&lt;P&gt;26 	Yes 	Error 	Syntax check&lt;/P&gt;&lt;P&gt;27 	Yes 	Error 	ALE error&lt;/P&gt;&lt;P&gt;29 	Yes 	Error 	Error in ALE services&lt;/P&gt;&lt;P&gt;30 	No 	Harmless 	Ready for dispatch (ALE)&lt;/P&gt;&lt;P&gt;31 	No 	Harmless 	IDOC is marked for deletion&lt;/P&gt;&lt;P&gt;33 	No 	Harmless 	Original of an IDOC which was edited&lt;/P&gt;&lt;P&gt;34 	Yes 	Error 	Error in control record of IDOC&lt;/P&gt;&lt;P&gt;36 	Yes 	Error 	Timeout error; electronic signature not performed&lt;/P&gt;&lt;P&gt;37 	Yes 	Error 	IDOC added incorrectly&lt;/P&gt;&lt;P&gt;38 	No 	Harmless 	IDOC archived&lt;/P&gt;&lt;P&gt;39 	No 	Harmless 	Receive confirmed&lt;/P&gt;&lt;P&gt;40 	Yes 	Error 	Application document not created in target system&lt;/P&gt;&lt;P&gt;41 	No 	Harmless 	Application document created in target document&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following table describes the inbound IDOC status codes that generate Tivoli Enterprise Console events:&lt;/P&gt;&lt;P&gt;Inbound IDOCs&lt;/P&gt;&lt;P&gt;Code 	Error 	Event Severity 	SAP Meaning&lt;/P&gt;&lt;P&gt;51, 52 	Yes 	Error 	Posting error&lt;/P&gt;&lt;P&gt;53 	No 	Harmless 	Posting successful&lt;/P&gt;&lt;P&gt;54 	Yes 	Error 	Error during formal application check&lt;/P&gt;&lt;P&gt;55 	No 	Harmless 	Formal application check&lt;/P&gt;&lt;P&gt;56 	Yes 	Error 	IDOC with error added&lt;/P&gt;&lt;P&gt;60 	Yes 	Error 	Syntax error&lt;/P&gt;&lt;P&gt;61 	Yes 	Warning 	Processing despite syntax error&lt;/P&gt;&lt;P&gt;62 	No 	Harmless 	IDOC passed to application&lt;/P&gt;&lt;P&gt;63 	Yes 	Error 	Error passing IDOC to application&lt;/P&gt;&lt;P&gt;64 	No 	Harmless 	IDOC ready to be passed to application&lt;/P&gt;&lt;P&gt;65 	Yes 	Error 	ALE error&lt;/P&gt;&lt;P&gt;68 	No 	Harmless 	IDOC is marked for deletion&lt;/P&gt;&lt;P&gt;70 	No 	Harmless 	Original of an IDOC which was edited&lt;/P&gt;&lt;P&gt;73 	No 	Harmless 	IDOC archived&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;a href="http://publib.boulder.ibm.com/tividd/td/ITMAN/SC23-4812-00/en_US/HTML/sa51mst256.htm"&amp;gt;refer this for statuses&amp;lt;/a&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;srinivas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;*&lt;STRONG&gt;reward for useful answers&lt;/STRONG&gt;*&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Aug 2007 14:09:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-statuses/m-p/2706518#M627115</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-22T14:09:51Z</dc:date>
    </item>
  </channel>
</rss>

