SAP MC_PG_SPERREN Function Module for NOTRANSL: Sperren der Produktgruppen beim anlegen,ändern und bei SOP-Planu

Search SAP Function Modules

MC_PG_SPERREN is a standard mc pg sperren SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Sperren der Produktgruppen beim anlegen,ändern und bei SOP-Planu 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 mc pg sperren FM, simply by entering the name MC_PG_SPERREN into the relevant SAP transaction such as SE37 or SE38.

Function Group: MCP2
Program Name: SAPLMCP2
Main Program: SAPLMCP2
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MC_PG_SPERREN 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 'MC_PG_SPERREN'"NOTRANSL: Sperren der Produktgruppen beim anlegen,ändern und bei SOP-Planu
  EXPORTING
   I_AKTION =  "Action that initiates the blocking process
*  I_RMCP2S = ' ' "Dummy Table for Locking SOP

 IMPORTING
   COLLISION_UNAME =  "User name in lock entry
   ENQUEUE_SUBRC =  "ABAP System Field: Return Code of ABAP Statements

EXCEPTIONS
   FOREIGN_LOCK = 1    INVALID_ENQ_ACTION = 2    SYSTEM_FAILURE = 3 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLMCP2_008 User Exit: Processing Header Data in a Purchase Order from an IDoc
EXIT_SAPLMCP2_009 User Exit: Processing Item Data in a Purchase Order from an IDoc

IMPORTING Parameters details for MC_PG_SPERREN

I_AKTION - Action that initiates the blocking process

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

I_RMCP2S - Dummy Table for Locking SOP

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

EXPORTING Parameters details for MC_PG_SPERREN

COLLISION_UNAME - User name in lock entry

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

ENQUEUE_SUBRC - ABAP System Field: Return Code of ABAP Statements

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

EXCEPTIONS details

FOREIGN_LOCK -

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

INVALID_ENQ_ACTION -

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

SYSTEM_FAILURE -

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

Copy and paste ABAP code example for MC_PG_SPERREN 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.

ABAP code using 7.40 inline data declarations to call FM MC_PG_SPERREN

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