SAP MSAM_MO_WARRANTY_ASSIGN_COMMIT Function Module for Warranty Commit









MSAM_MO_WARRANTY_ASSIGN_COMMIT is a standard msam mo warranty assign commit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Warranty Commit 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 msam mo warranty assign commit FM, simply by entering the name MSAM_MO_WARRANTY_ASSIGN_COMMIT into the relevant SAP transaction such as SE37 or SE38.

Function Group: MSAM_MO_WARRANTY
Program Name: SAPLMSAM_MO_WARRANTY
Main Program: SAPLMSAM_MO_WARRANTY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1



Function MSAM_MO_WARRANTY_ASSIGN_COMMIT 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 'MSAM_MO_WARRANTY_ASSIGN_COMMIT'"Warranty Commit
EXPORTING
* CHANGE_ALLOWED = 'X' "General Flag

TABLES
BGMKOBJ_INSERT = "Master Warranty - Object Assignment
BGMKOBJ_UPDATE = "Master Warranty - Object Assignment
BGMKOBJ_DELETE = "Master Warranty - Object Assignment
.



IMPORTING Parameters details for MSAM_MO_WARRANTY_ASSIGN_COMMIT

CHANGE_ALLOWED - General Flag

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for MSAM_MO_WARRANTY_ASSIGN_COMMIT

BGMKOBJ_INSERT - Master Warranty - Object Assignment

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

BGMKOBJ_UPDATE - Master Warranty - Object Assignment

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

BGMKOBJ_DELETE - Master Warranty - Object Assignment

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

Copy and paste ABAP code example for MSAM_MO_WARRANTY_ASSIGN_COMMIT 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:
lt_bgmkobj_insert  TYPE STANDARD TABLE OF BGMKOBJ, "   
lv_change_allowed  TYPE FLAG, "   'X'
lt_bgmkobj_update  TYPE STANDARD TABLE OF BGMKOBJ, "   
lt_bgmkobj_delete  TYPE STANDARD TABLE OF BGMKOBJ. "   

  CALL FUNCTION 'MSAM_MO_WARRANTY_ASSIGN_COMMIT'  "Warranty Commit
    EXPORTING
         CHANGE_ALLOWED = lv_change_allowed
    TABLES
         BGMKOBJ_INSERT = lt_bgmkobj_insert
         BGMKOBJ_UPDATE = lt_bgmkobj_update
         BGMKOBJ_DELETE = lt_bgmkobj_delete
. " MSAM_MO_WARRANTY_ASSIGN_COMMIT




ABAP code using 7.40 inline data declarations to call FM MSAM_MO_WARRANTY_ASSIGN_COMMIT

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.

 
DATA(ld_change_allowed) = 'X'.
 
 
 


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!