SAP ABAP: IDoc Status Codes

The following table describes outbound IDOC status codes

Outbound IDOCs
Code	Error	Event Severity	SAP Meaning
2	Yes	Error	Error passing data to port
3	No	Error if transaction SM58 indicates an RFC transmission error	Data pass to port OK
4	Yes	Error	Control information of EDI subsystem
5	Yes	Error	Translation
6	No	Harmless	Translation
7	Yes	Error	Syntax check
8	No	Harmless	Syntax check
9	Yes	Error	Interchange handling
10	No	Harmless	Interchange handling
11	Yes	Error	Dispatch
12, 13, 14	No	Harmless	OK
15	Yes	Warning	Interchange acknowledgement negative
16	No	Harmless	Functional acknowledgement
17	Yes	Warning	Functional acknowledgement negative
18	No	Harmless	Triggering EDI subsystem
20	Yes	Error	Triggering EDI subsystem
22	No	Harmless	Dispatch OK, acknowledgement still due
23	Yes	Error	Retransmission
24	No	Harmless	Control information of EDI subsystem
25	Yes	Warning	Processing despite syntax error
26	Yes	Error	Syntax check
27	Yes	Error	ALE error
29	Yes	Error	Error in ALE services
30	No	Harmless	Ready for dispatch (ALE)
31	No	Harmless	IDOC is marked for deletion
33	No	Harmless	Original of an IDOC which was edited
34	Yes	Error	Error in control record of IDOC
36	Yes	Error	Timeout error; electronic signature not performed
37	Yes	Error	IDOC added incorrectly
38	No	Harmless	IDOC archived
39	No	Harmless	Receive confirmed
40	Yes	Error	Application document not created in target system
41	No	Harmless	Application document created in target document

The following table describes the inbound IDOC status codes :

<><><>  <><><>  <><><> 

Inbound IDOCs
Code	Error	Event Severity	SAP Meaning
51, 52	Yes	Error	Posting error
53	No	Harmless	Posting successful
54	Yes	Error	Error during formal application check
55	No	Harmless	Formal application check
56	Yes	Error	IDOC with error added
60	Yes	Error	Syntax error
61	Yes	Warning	Processing despite syntax error
62	No	Harmless	IDOC passed to application
63	Yes	Error	Error passing IDOC to application
64	No	Harmless	IDOC ready to be passed to application
65	Yes	Error	ALE error
68	No	Harmless	IDOC is marked for deletion
70	No	Harmless	Original of an IDOC which was edited
73	No	Harmless	IDOC archived

source: www. publib .boulder .ibm .com

How to email output from Background Jobs

Introduction

One of my Customers has a regularly scheduled job with spool (SP01) output.  They have asked if it could be be emailed to a group email address.  The address management is nice and easy in this case; they manage the mail group, adding and deleting email addresses as people move in and out of the group.  But how do we send the spool output as email ?

Go into transaction SM37 (Job Overview) and search for the job that creates the output you wish to mail.  You need to make sure you find a scheduled, released or ready version of the job as you can't do this with an existing spool output.

Click here for full story

Author: Martin

Source: snd.sap.com

Manipulating MS Office documents from ABAP (OLE2)

Introduction

The idea to start using the OLE2 interface came from the repetitive steps that needed to be done to fill out a technical design (TD) template. For instance for a new ABAP program a lot of information for the TD can be directly passed from the SAP system, such as program name, description, author, date, version number, etc. When you have to make changes to this program you could also use the OLE2 interface to open the existing TD and automatically add a new line to the version history as well as inserting a new paragraph which describes the changes for this version. The developer then only needs to enter the actual text describing the changes.

Click here for full story

Author: Roel van den Berge

Source: sdn.sap.com