SAP CUSL_BATCHES_HAS_VALUES Function Module for NOTRANSL: Selektionskriterien für Chargenfindung

Search SAP Function Modules

CUSL_BATCHES_HAS_VALUES is a standard cusl batches has values 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: Selektionskriterien für Chargenfindung 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 batches has values FM, simply by entering the name CUSL_BATCHES_HAS_VALUES 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_BATCHES_HAS_VALUES 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_BATCHES_HAS_VALUES'"NOTRANSL: Selektionskriterien für Chargenfindung
  EXPORTING
   MATERIAL =  "Material Number
*  PLANT =  "Plant
   BATCH =  "Batch Number
*  BATCH_CUOBJ =  "Configuration (internal object number)
*  VALUES_BY_SORT = ' ' "
*  LANGUAGE = SY-LANGU "ABAP System Field: Language Key of Text Environment

TABLES
   OBJECTS =  "Transfer Object to Value Assignment for Object Characts
   CLASSIFICATION =  "Configuration Output

EXCEPTIONS
   NO_CLASSIFICATION_DATA = 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_BATCHES_HAS_VALUES

MATERIAL - Material Number

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

PLANT - Plant

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

BATCH - Batch Number

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

BATCH_CUOBJ - Configuration (internal object number)

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

VALUES_BY_SORT -

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

LANGUAGE - ABAP System Field: Language Key of Text Environment

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for CUSL_BATCHES_HAS_VALUES

OBJECTS - Transfer Object to Value Assignment for Object Characts

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

CLASSIFICATION - Configuration Output

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

EXCEPTIONS details

NO_CLASSIFICATION_DATA -

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

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

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