SAP CONTRACT_OM_TRIGGER Function Module for Trigger Output Management









CONTRACT_OM_TRIGGER is a standard contract om trigger SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Trigger Output Management processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for contract om trigger FM, simply by entering the name CONTRACT_OM_TRIGGER into the relevant SAP transaction such as SE37 or SE38.

Function Group: DR_CTR
Program Name: SAPLDR_CTR
Main Program: SAPLDR_CTR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 2



Function CONTRACT_OM_TRIGGER pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'CONTRACT_OM_TRIGGER'"Trigger Output Management
EXPORTING
IV_EBELN = "Purchasing Document Number
* IV_BSTYP = "Document Type
.



IMPORTING Parameters details for CONTRACT_OM_TRIGGER

IV_EBELN - Purchasing Document Number

Data type: EBELN
Optional: No
Call by Reference: No ( called with pass by value option)

IV_BSTYP - Document Type

Data type: BSTYP
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CONTRACT_OM_TRIGGER Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lv_iv_ebeln  TYPE EBELN, "   
lv_iv_bstyp  TYPE BSTYP. "   

  CALL FUNCTION 'CONTRACT_OM_TRIGGER'  "Trigger Output Management
    EXPORTING
         IV_EBELN = lv_iv_ebeln
         IV_BSTYP = lv_iv_bstyp
. " CONTRACT_OM_TRIGGER




ABAP code using 7.40 inline data declarations to call FM CONTRACT_OM_TRIGGER

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!