SAP CKBA_GET_LOTSIZE_FROM_PROCESS Function Module for









CKBA_GET_LOTSIZE_FROM_PROCESS is a standard ckba get lotsize from process SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ckba get lotsize from process FM, simply by entering the name CKBA_GET_LOTSIZE_FROM_PROCESS into the relevant SAP transaction such as SE37 or SE38.

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



Function CKBA_GET_LOTSIZE_FROM_PROCESS 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 'CKBA_GET_LOTSIZE_FROM_PROCESS'"
EXPORTING
I_PROCESS = "Process Material
I_VERID = "Production Version
I_STLAL = "Alternative BOM
I_STLAN = "BOM Application
I_MATNR = "Co-Product
I_WERKS = "Plant
I_QUANTITY = "Beschaffungsmenge
I_MEINS = "Unit of Measure

IMPORTING
O_LOSGR = "Lot Size
O_MEINS = "Unit of Measure

EXCEPTIONS
NOT_POSSIBLE = 1
.



IMPORTING Parameters details for CKBA_GET_LOTSIZE_FROM_PROCESS

I_PROCESS - Process Material

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

I_VERID - Production Version

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

I_STLAL - Alternative BOM

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

I_STLAN - BOM Application

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

I_MATNR - Co-Product

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

I_WERKS - Plant

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

I_QUANTITY - Beschaffungsmenge

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

I_MEINS - Unit of Measure

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

EXPORTING Parameters details for CKBA_GET_LOTSIZE_FROM_PROCESS

O_LOSGR - Lot Size

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

O_MEINS - Unit of Measure

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

EXCEPTIONS details

NOT_POSSIBLE - Ermittlung der Losgröße nicht möglich

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

Copy and paste ABAP code example for CKBA_GET_LOTSIZE_FROM_PROCESS 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_o_losgr  TYPE CKMLMV001-LOSGR_PC, "   
lv_i_process  TYPE CKMLMV001-MATNR, "   
lv_not_possible  TYPE CKMLMV001, "   
lv_i_verid  TYPE CKMLMV001-VERID_ND, "   
lv_o_meins  TYPE CKMLMV001-MEINS_PC, "   
lv_i_stlal  TYPE CKMLMV001-STLAL_ND, "   
lv_i_stlan  TYPE CKMLMV001-STLAN_ND, "   
lv_i_matnr  TYPE CKMLMV001-MATNR, "   
lv_i_werks  TYPE CKMLMV001-WERKS, "   
lv_i_quantity  TYPE CKMLMV001-LOSGR_PC, "   
lv_i_meins  TYPE CKMLMV001-MEINS_PC. "   

  CALL FUNCTION 'CKBA_GET_LOTSIZE_FROM_PROCESS'  "
    EXPORTING
         I_PROCESS = lv_i_process
         I_VERID = lv_i_verid
         I_STLAL = lv_i_stlal
         I_STLAN = lv_i_stlan
         I_MATNR = lv_i_matnr
         I_WERKS = lv_i_werks
         I_QUANTITY = lv_i_quantity
         I_MEINS = lv_i_meins
    IMPORTING
         O_LOSGR = lv_o_losgr
         O_MEINS = lv_o_meins
    EXCEPTIONS
        NOT_POSSIBLE = 1
. " CKBA_GET_LOTSIZE_FROM_PROCESS




ABAP code using 7.40 inline data declarations to call FM CKBA_GET_LOTSIZE_FROM_PROCESS

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 LOSGR_PC FROM CKMLMV001 INTO @DATA(ld_o_losgr).
 
"SELECT single MATNR FROM CKMLMV001 INTO @DATA(ld_i_process).
 
 
"SELECT single VERID_ND FROM CKMLMV001 INTO @DATA(ld_i_verid).
 
"SELECT single MEINS_PC FROM CKMLMV001 INTO @DATA(ld_o_meins).
 
"SELECT single STLAL_ND FROM CKMLMV001 INTO @DATA(ld_i_stlal).
 
"SELECT single STLAN_ND FROM CKMLMV001 INTO @DATA(ld_i_stlan).
 
"SELECT single MATNR FROM CKMLMV001 INTO @DATA(ld_i_matnr).
 
"SELECT single WERKS FROM CKMLMV001 INTO @DATA(ld_i_werks).
 
"SELECT single LOSGR_PC FROM CKMLMV001 INTO @DATA(ld_i_quantity).
 
"SELECT single MEINS_PC FROM CKMLMV001 INTO @DATA(ld_i_meins).
 


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!