IT Partners

18 Feb: Debugging ABAP for Functional Teams – Part 1

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.

19 Jan: What are BTE and BDT Enhancements – Part 2

To begin, we must keep in mind every SAP implementation is different. That is because every business is different in the details related to their individual business processes and/or master data. Even with in the same company or entity, there can be slight or major differences in a business process or master data based on an enterprise slice. Some parts of the organization perform business one way, while another performs business another. While this is a challenge during implementations, SAP has delivered many different enhancement options. These may be leveraged by the design and development teams to meet the needs of the organization. Enhancement options are always preferable to core modifications when possible.

09 Dec: What are BTE and BDT Enhancements – Part 1

To begin, we must keep in mind every SAP implementation is different. That is because every business is different in the details related to their individual business processes and/or master data. Even with in the same company or entity, there can be slight or major differences in a business process or master data based on an enterprise slice. Some parts of the organization perform business one way, while another performs business another. While this is a challenge during implementations, SAP has delivered many different enhancement options. These may be leveraged by the design and development teams to meet the needs of the organization. Enhancement options are always preferable to core modifications when possible.

New-Me

14 Aug: IDocs: A Guide for New Developers – Part 2

An IDoc is the run−time instance of an IDoc type. An IDoc consists of a control record, several data records,and a list of status records. The control record defines control information such as sender and receiver information. The data records contain the application data that is to be transferred via IDocs. The status records contain status information (success or failure) recorded at each point in the process.

New-Me

16 Jul: IDocs: A Guide for New Developers – Part 1

A large enterprise’s networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc (for intermediate document) encapsulates data so that it can be exchanged between different systems without conversion from one format to another. IDocs are used for 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.