SAP GET_PLAF_WITH_PLNUM Function Module for NOTRANSL: Einsatzplanung: Planauftrag zu PLNUM lesen (aus Puffer PLAFX)

Search SAP Function Modules

GET_PLAF_WITH_PLNUM is a standard get plaf with plnum 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: Einsatzplanung: Planauftrag zu PLNUM lesen (aus Puffer PLAFX) 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 get plaf with plnum FM, simply by entering the name GET_PLAF_WITH_PLNUM into the relevant SAP transaction such as SE37 or SE38.

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

Function GET_PLAF_WITH_PLNUM 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 'GET_PLAF_WITH_PLNUM'"NOTRANSL: Einsatzplanung: Planauftrag zu PLNUM lesen (aus Puffer PLAFX)
  EXPORTING
   PLNUM =  "ID of desired planned order

 IMPORTING
   OPLAF =  "selected planned order
   PINDX =  "Index of planned order in PLAFX
   STATU =  "
   EPLST =  "

EXCEPTIONS
   NO_PLNUM_SPECIFIED = 1    OBJECT_NOT_FOUND = 2    PLAF_LOGICALLY_DELETED = 3 

.

IMPORTING Parameters details for GET_PLAF_WITH_PLNUM

PLNUM - ID of desired planned order

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

EXPORTING Parameters details for GET_PLAF_WITH_PLNUM

OPLAF - selected planned order

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

PINDX - Index of planned order in PLAFX

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

STATU -

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

EPLST -

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

EXCEPTIONS details

NO_PLNUM_SPECIFIED - no input available

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

OBJECT_NOT_FOUND - No planned order for ID PLNUM, available

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

PLAF_LOGICALLY_DELETED -

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

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

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