message types

16 Mar: Debugging ABAP for Functional Teams – Part 2

Debugging is the way to find the root cause of certain SAP transactional behavior (e.g., finding a reason why a certain value in a field was updated or determining why users receive an error, warning, or abnormal termination message during the processing of a transaction). Debugging is necessary if the root cause cannot be determined from functional methods such as checking customizing or master data.

Since ABAP is the backbone of SAP, at one point or another, every member of a functional team must have had to deal with SAP development technicalities behind the business functionality. This need for technical details can occur during various phases, such as writing functional specifications or analyzing a production environment issues.

#

09 Nov: IDocs: A Guide for New Developers – Part 5

If you recall from last month’s blog, the Function Module we are using follows a naming convention “IDOC__NAME OF MESSAGE TYPE”. For our example the delivered Message Type for an Invoice is INVOIC and this is an Outbound scenario, so the function module will be “IDOC_OUTPUT_INVOIC”. The User Exit for the transaction can be found using the transaction SMOD. Here we need to give the package to find the exact enhancement and the respective function module which will serve our purpose. The steps are as follows…

#

21 Oct: IDocs: A Guide for New Developers – Part 4

The message type determines the technical structure of the message, along with the data contained. Through configuration, it will also determine the process flow involved in a “Distributed environment”. The Message Type controls Process Code, which in turn drives a Function Module to derive the content of the message in an OUTBOUND scenario or execute the desired SAP process in an INBOUND scenario. Finally, it also controls how the IDocs will be processed (batch, immediately etc).

#

18 Sep: IDocs: A Guide for New Developers – Part 3

Standard SAP sends out or receives in data through IDocs using standard delivered Segments, Message Types and fields. But sometimes, these fields are not sufficient for a specific end-to-end business scenario as far as data transfer is concerned. So in such scenarios, we can add new segments with completely new structures to the standard IDoc as an extension. We create a brand new structure and insert it into existing delivered IDoc structure creating a whole new IDoc satisfying the requirement. This new IDoc is called an Extended IDoc