SAP PIC10_REQUIRE_ALLOCATION_LPART Function Module for NOTRANSL: Calls REQUIREMENTS_ALLOCATION for Leading Part

Search SAP Function Modules

PIC10_REQUIRE_ALLOCATION_LPART is a standard pic10 require allocation lpart 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: Calls REQUIREMENTS_ALLOCATION for Leading Part 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 pic10 require allocation lpart FM, simply by entering the name PIC10_REQUIRE_ALLOCATION_LPART into the relevant SAP transaction such as SE37 or SE38.

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

Function PIC10_REQUIRE_ALLOCATION_LPART 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 'PIC10_REQUIRE_ALLOCATION_LPART'"NOTRANSL: Calls REQUIREMENTS_ALLOCATION for Leading Part
  EXPORTING
   IV_GPBPT =  "Table of ind. requirements item data

 IMPORTING
   EV_PICID =  "Indicator : Leading part
   EV_CM60X =  "Interface structure for allocating independent reqmts

TABLES
   IT_KDPBOX =  "Open allocations from customer reqmt/reservation/dep.reqmt
   IT_KDPBX =  "Allocation index ind. reqmts to sales order
   IT_PBKDSX =  "Totals record allocation index: customer reqmts to ind.reqmt
   IT_PBKDX =  "Allocation index: customer reqmts to ind. requirements

EXCEPTIONS
   NON_LEADING_PART = 1 

.

IMPORTING Parameters details for PIC10_REQUIRE_ALLOCATION_LPART

IV_GPBPT - Table of ind. requirements item data

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

EXPORTING Parameters details for PIC10_REQUIRE_ALLOCATION_LPART

EV_PICID - Indicator : Leading part

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

EV_CM60X - Interface structure for allocating independent reqmts

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

TABLES Parameters details for PIC10_REQUIRE_ALLOCATION_LPART

IT_KDPBOX - Open allocations from customer reqmt/reservation/dep.reqmt

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

IT_KDPBX - Allocation index ind. reqmts to sales order

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

IT_PBKDSX - Totals record allocation index: customer reqmts to ind.reqmt

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

IT_PBKDX - Allocation index: customer reqmts to ind. requirements

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

EXCEPTIONS details

NON_LEADING_PART -

Data type:
Optional: No
Call by Reference: Yes

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

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