SAP BAM1_SAVE_MOD_OBJ_ANALYSIS Function Module for
BAM1_SAVE_MOD_OBJ_ANALYSIS is a standard bam1 save mod obj analysis SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bam1 save mod obj analysis FM, simply by entering the name BAM1_SAVE_MOD_OBJ_ANALYSIS into the relevant SAP transaction such as SE37 or SE38.
Function Group: BAM1
Program Name: SAPLBAM1
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BAM1_SAVE_MOD_OBJ_ANALYSIS 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 'BAM1_SAVE_MOD_OBJ_ANALYSIS'".
EXPORTING
SEQNO = "
DATE = "
TABLES
MODIFIED_OBJECTS = "
IMPORTING Parameters details for BAM1_SAVE_MOD_OBJ_ANALYSIS
SEQNO -
Data type: BAMANDIR-SEQNOOptional: No
Call by Reference: No ( called with pass by value option)
DATE -
Data type: BAMANDIR-DATEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAM1_SAVE_MOD_OBJ_ANALYSIS
MODIFIED_OBJECTS -
Data type: BAMSSMODOBOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAM1_SAVE_MOD_OBJ_ANALYSIS 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_seqno | TYPE BAMANDIR-SEQNO, " | |||
| lt_modified_objects | TYPE STANDARD TABLE OF BAMSSMODOB, " | |||
| lv_date | TYPE BAMANDIR-DATE. " |
|   CALL FUNCTION 'BAM1_SAVE_MOD_OBJ_ANALYSIS' " |
| EXPORTING | ||
| SEQNO | = lv_seqno | |
| DATE | = lv_date | |
| TABLES | ||
| MODIFIED_OBJECTS | = lt_modified_objects | |
| . " BAM1_SAVE_MOD_OBJ_ANALYSIS | ||
ABAP code using 7.40 inline data declarations to call FM BAM1_SAVE_MOD_OBJ_ANALYSIS
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.| "SELECT single SEQNO FROM BAMANDIR INTO @DATA(ld_seqno). | ||||
| "SELECT single DATE FROM BAMANDIR INTO @DATA(ld_date). | ||||
Search for further information about these or an SAP related objects