SAP EXIT_SAPMC29C_004 Function Module for Engineering Change Management: Check When Setting a System Status









EXIT_SAPMC29C_004 is a standard exit sapmc29c 004 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Engineering Change Management: Check When Setting a System Status 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 exit sapmc29c 004 FM, simply by entering the name EXIT_SAPMC29C_004 into the relevant SAP transaction such as SE37 or SE38.

Function Group: XCCA
Program Name: SAPLXCCA
Main Program:
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function EXIT_SAPMC29C_004 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 'EXIT_SAPMC29C_004'"Engineering Change Management: Check When Setting a System Status
EXPORTING
BUS_TRAN = "Business Transaction
ECM_DATA = "Change Master
OMR_CURRENT = "Current object management record
ECM_MNT_VALUE = "Maintenance Variant
ECM_OBJ_TYPE = "Table: Object Types
ECM_OBJMNGREC = "Table: Object mgmt records
ECM_ALT_DATE = "Table: Alternative Dates
ECM_EFFECTIVITY = "Table: Parameter Effectivity
ECM_HIERARCHY = "Table: Change Hierarchy

EXCEPTIONS
NOT_OK = 1
.



IMPORTING Parameters details for EXIT_SAPMC29C_004

BUS_TRAN - Business Transaction

Data type: TJ05-VRGNG
Optional: No
Call by Reference: No ( called with pass by value option)

ECM_DATA - Change Master

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

OMR_CURRENT - Current object management record

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

ECM_MNT_VALUE - Maintenance Variant

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

ECM_OBJ_TYPE - Table: Object Types

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

ECM_OBJMNGREC - Table: Object mgmt records

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

ECM_ALT_DATE - Table: Alternative Dates

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

ECM_EFFECTIVITY - Table: Parameter Effectivity

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

ECM_HIERARCHY - Table: Change Hierarchy

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

EXCEPTIONS details

NOT_OK - No system status change

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

Copy and paste ABAP code example for EXIT_SAPMC29C_004 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_not_ok  TYPE STRING, "   
lv_bus_tran  TYPE TJ05-VRGNG, "   
lv_ecm_data  TYPE AENRB, "   
lv_omr_current  TYPE CC_J_OBJNR, "   
lv_ecm_mnt_value  TYPE AEPFB, "   
lv_ecm_obj_type  TYPE CC00_T_OBJ_TYPE, "   
lv_ecm_objmngrec  TYPE CC00_T_OBJMNGREC, "   
lv_ecm_alt_date  TYPE CC00_T_ALT_DATE, "   
lv_ecm_effectivity  TYPE CC00_T_EFFECTIV, "   
lv_ecm_hierarchy  TYPE CC00_T_HIERARCHY. "   

  CALL FUNCTION 'EXIT_SAPMC29C_004'  "Engineering Change Management: Check When Setting a System Status
    EXPORTING
         BUS_TRAN = lv_bus_tran
         ECM_DATA = lv_ecm_data
         OMR_CURRENT = lv_omr_current
         ECM_MNT_VALUE = lv_ecm_mnt_value
         ECM_OBJ_TYPE = lv_ecm_obj_type
         ECM_OBJMNGREC = lv_ecm_objmngrec
         ECM_ALT_DATE = lv_ecm_alt_date
         ECM_EFFECTIVITY = lv_ecm_effectivity
         ECM_HIERARCHY = lv_ecm_hierarchy
    EXCEPTIONS
        NOT_OK = 1
. " EXIT_SAPMC29C_004




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPMC29C_004

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 VRGNG FROM TJ05 INTO @DATA(ld_bus_tran).
 
 
 
 
 
 
 
 
 


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!