SAP CUSL_BIC_BATCH_VALUES_GET Function Module for NOTRANSL: Bewertung für Chargen im BIC lesen
CUSL_BIC_BATCH_VALUES_GET is a standard cusl bic batch values get 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: Bewertung für Chargen im BIC lesen 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 cusl bic batch values get FM, simply by entering the name CUSL_BIC_BATCH_VALUES_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: CUSL
Program Name: SAPLCUSL
Main Program: SAPLCUSL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CUSL_BIC_BATCH_VALUES_GET 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 'CUSL_BIC_BATCH_VALUES_GET'"NOTRANSL: Bewertung für Chargen im BIC lesen.
EXPORTING
IV_MATERIAL = "Material Number
* IV_PLANT = "Plant
IV_BATCH = "Batch Number
IV_BATCH_CUOBJ = "Configuration (Internal Object Number)
IV_CLASSTYPE = "Class Type
IV_CLASS = "Class Number
* IV_LANGUAGE = SY-LANGU "Language Key of Current Text Environment
IMPORTING
ET_VALUES_EXT = "Table Type for CONF_OUT
ET_VALUES_INT = "Table Type for AUSP
EXCEPTIONS
ERROR_IN_CLASSIFICATION = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLCUSL_001 Control of Selection Criteria for Batch Determination
IMPORTING Parameters details for CUSL_BIC_BATCH_VALUES_GET
IV_MATERIAL - Material Number
Data type: MATNROptional: No
Call by Reference: Yes
IV_PLANT - Plant
Data type: WERKS_DOptional: Yes
Call by Reference: Yes
IV_BATCH - Batch Number
Data type: CHARG_DOptional: No
Call by Reference: Yes
IV_BATCH_CUOBJ - Configuration (Internal Object Number)
Data type: CUOBJOptional: No
Call by Reference: Yes
IV_CLASSTYPE - Class Type
Data type: KLASSENARTOptional: No
Call by Reference: Yes
IV_CLASS - Class Number
Data type: KLASSE_DOptional: No
Call by Reference: Yes
IV_LANGUAGE - Language Key of Current Text Environment
Data type: SYLANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CUSL_BIC_BATCH_VALUES_GET
ET_VALUES_EXT - Table Type for CONF_OUT
Data type: CONF_OUT_TTOptional: No
Call by Reference: Yes
ET_VALUES_INT - Table Type for AUSP
Data type: TT_AUSPOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_IN_CLASSIFICATION -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CUSL_BIC_BATCH_VALUES_GET 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_iv_material | TYPE MATNR, " | |||
| lv_et_values_ext | TYPE CONF_OUT_TT, " | |||
| lv_error_in_classification | TYPE CONF_OUT_TT, " | |||
| lv_iv_plant | TYPE WERKS_D, " | |||
| lv_et_values_int | TYPE TT_AUSP, " | |||
| lv_iv_batch | TYPE CHARG_D, " | |||
| lv_iv_batch_cuobj | TYPE CUOBJ, " | |||
| lv_iv_classtype | TYPE KLASSENART, " | |||
| lv_iv_class | TYPE KLASSE_D, " | |||
| lv_iv_language | TYPE SYLANGU. " SY-LANGU |
|   CALL FUNCTION 'CUSL_BIC_BATCH_VALUES_GET' "NOTRANSL: Bewertung für Chargen im BIC lesen |
| EXPORTING | ||
| IV_MATERIAL | = lv_iv_material | |
| IV_PLANT | = lv_iv_plant | |
| IV_BATCH | = lv_iv_batch | |
| IV_BATCH_CUOBJ | = lv_iv_batch_cuobj | |
| IV_CLASSTYPE | = lv_iv_classtype | |
| IV_CLASS | = lv_iv_class | |
| IV_LANGUAGE | = lv_iv_language | |
| IMPORTING | ||
| ET_VALUES_EXT | = lv_et_values_ext | |
| ET_VALUES_INT | = lv_et_values_int | |
| EXCEPTIONS | ||
| ERROR_IN_CLASSIFICATION = 1 | ||
| . " CUSL_BIC_BATCH_VALUES_GET | ||
ABAP code using 7.40 inline data declarations to call FM CUSL_BIC_BATCH_VALUES_GET
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.| DATA(ld_iv_language) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects