SAP ALE_JBD_LMB_GET_DET_MULT Function Module for BAPI -> IDoc: ALE_JBD_LMB_GET_DET_MULT

Search SAP Function Modules

ALE_JBD_LMB_GET_DET_MULT is a standard ale jbd lmb get det mult SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI -> IDoc: ALE_JBD_LMB_GET_DET_MULT 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 ale jbd lmb get det mult FM, simply by entering the name ALE_JBD_LMB_GET_DET_MULT into the relevant SAP transaction such as SE37 or SE38.

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

Function ALE_JBD_LMB_GET_DET_MULT 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 'ALE_JBD_LMB_GET_DET_MULT'"BAPI -> IDoc: ALE_JBD_LMB_GET_DET_MULT
  EXPORTING
*  PROCESSEXTENSION =  "Flag
*  OBJ_TYPE = 'BUSJBDLM' "
*  SERIAL_ID = '0' "

TABLES
   LIMITLIST =  "
*  APPLICATION_OBJECTS =  "
   ILIMITLIST =  "
*  LIMITDATAHEADER =  "
*  ATTRIBUTESCHAR =  "
*  ATTRIBUTESLIMHEAD =  "
*  ATTRIBUTESLIMPOS =  "
*  EXTENSIONIN =  "Bezugsstruktur für BAPI-Parameter ExtensionIn / ExtensionOut
   RECEIVERS =  "
*  COMMUNICATION_DOCUMENTS =  "

EXCEPTIONS
   ERROR_CREATING_IDOCS = 1 

.

IMPORTING Parameters details for ALE_JBD_LMB_GET_DET_MULT

PROCESSEXTENSION - Flag

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

OBJ_TYPE -

Data type: SERIAL-OBJ_TYPE
Default: 'BUSJBDLM'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SERIAL_ID -

Data type: SERIAL-CHNUM
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ALE_JBD_LMB_GET_DET_MULT

LIMITLIST -

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

APPLICATION_OBJECTS -

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

ILIMITLIST -

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

LIMITDATAHEADER -

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

ATTRIBUTESCHAR -

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

ATTRIBUTESLIMHEAD -

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

ATTRIBUTESLIMPOS -

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

EXTENSIONIN - Bezugsstruktur für BAPI-Parameter ExtensionIn / ExtensionOut

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

RECEIVERS -

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

COMMUNICATION_DOCUMENTS -

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

EXCEPTIONS details

ERROR_CREATING_IDOCS -

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

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

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