
Scaling SAP ABAP with RESTful Programming Model (RAP)
UdemyMark your own learning status. Opening a course link does not establish enrollment.
Loading saved status…
This intermediate Udemy session focuses on SAP WM warehouse operations and the function modules that drive them. It shows how to find and test a function module in transaction SE37, then walks through creating, cancelling and confirming transfer orders by calling the relevant modules.
The material suits developers and functional consultants who already know their way around SAP and want to see how warehouse transactions can be driven through code. Because its scope is narrow, it works best as a targeted refresher.
The update module section, which covers primary and secondary updates and how a commit triggers them, is the part most worth revisiting.
In this Training, I provided details of below topics
- Usage of Transaction Code SE37
- How to test the Function Modules by using SE37 Transaction Code
- Training on Transfer Order Creation with FM
- Training on Transfer Order Cancellation with FM
- Training on Transfer Order Cancellation by Storage Unit with FM
- Training on Transfer Order Confirmation with FM
Types of Function Modules
Function Modules can be categorized based on their processing type, which determines how they are executed.
1. Regular Function Module
This is the standard and most common type of Function Module. It is executed synchronously in the same work process as the calling program. The program waits until the Function Module has finished its execution before continuing.
2. Remote-Enabled Function Module (RFC)
These Function Modules can be called from other SAP systems or even non-SAP systems. They are the backbone of communication and integration between different systems. To make a Function Module remote-enabled, the "Remote-Enabled Module" processing type must be selected in its attributes. This is the foundation for BAPIs (Business Application Programming Interfaces).
3. Update Function Module
Update Function Modules are designed to perform database updates in a separate update work process. They are not executed immediately when called. Instead, they are registered for execution and are triggered by a COMMIT WORK statement. This ensures that database changes are bundled into a single Logical Unit of Work (LUW), maintaining data consistency. There are two types of update modules:
V1 (Primary) Update: These are critical updates that are processed first.
V2 (Secondary) Update: These are less critical updates that are processed after all V1 modules have been successfully completed
Advertisement
No Korshub reviews yet.