SAP PM_ORDER_EXTERN_CHECK Function Module for NOTRANSL: Check Interface CS-SDL aktiv









PM_ORDER_EXTERN_CHECK is a standard pm order extern check 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: Check Interface CS-SDL aktiv 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 pm order extern check FM, simply by entering the name PM_ORDER_EXTERN_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function PM_ORDER_EXTERN_CHECK 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 'PM_ORDER_EXTERN_CHECK'"NOTRANSL: Check Interface CS-SDL aktiv
EXPORTING
AUART = "Order Type

IMPORTING
EXTERN_SCHEDULE_ACTIVE = "Single-Character Indicator
.



IMPORTING Parameters details for PM_ORDER_EXTERN_CHECK

AUART - Order Type

Data type: AUFART
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for PM_ORDER_EXTERN_CHECK

EXTERN_SCHEDULE_ACTIVE - Single-Character Indicator

Data type: CHAR1
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PM_ORDER_EXTERN_CHECK 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_auart  TYPE AUFART, "   
lv_extern_schedule_active  TYPE CHAR1. "   

  CALL FUNCTION 'PM_ORDER_EXTERN_CHECK'  "NOTRANSL: Check Interface CS-SDL aktiv
    EXPORTING
         AUART = lv_auart
    IMPORTING
         EXTERN_SCHEDULE_ACTIVE = lv_extern_schedule_active
. " PM_ORDER_EXTERN_CHECK




ABAP code using 7.40 inline data declarations to call FM PM_ORDER_EXTERN_CHECK

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!