SAP CLBA_CLASSIFICATION_BTCH_INPUT Function Module for









CLBA_CLASSIFICATION_BTCH_INPUT is a standard clba classification btch input 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 clba classification btch input FM, simply by entering the name CLBA_CLASSIFICATION_BTCH_INPUT into the relevant SAP transaction such as SE37 or SE38.

Function Group: CLBA
Program Name: SAPLCLBA
Main Program: SAPLCLBA
Appliation area: M
Release date: 30-Dec-1993
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CLBA_CLASSIFICATION_BTCH_INPUT 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 'CLBA_CLASSIFICATION_BTCH_INPUT'"
EXPORTING
* BDC_FLAG = ' ' "Batch input flag
GROUP_DATA = "BGR00 record
* TCODE_MODE = 'S' "for ODC mode: Processing mode (A,E,N)
* TCODE_UPDATE = 'S' "for ODC mode: Type of update (A is asynchronous, S is synch.)

IMPORTING
MSGID = "ID for messages
MSGNO = "Message number
MSGTY = "Message type
MSGV1 = "1st parameter of a message
MSGV2 = "2nd parameter of a message
MSGV3 = "3rd parameter of a message
MSGV4 = "4th parameter of a message

TABLES
IAUSP = "Valuation data
IKSSK = "Allocation dates
.



IMPORTING Parameters details for CLBA_CLASSIFICATION_BTCH_INPUT

BDC_FLAG - Batch input flag

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

GROUP_DATA - BGR00 record

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

TCODE_MODE - for ODC mode: Processing mode (A,E,N)

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

TCODE_UPDATE - for ODC mode: Type of update (A is asynchronous, S is synch.)

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

EXPORTING Parameters details for CLBA_CLASSIFICATION_BTCH_INPUT

MSGID - ID for messages

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

MSGNO - Message number

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

MSGTY - Message type

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

MSGV1 - 1st parameter of a message

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

MSGV2 - 2nd parameter of a message

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

MSGV3 - 3rd parameter of a message

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

MSGV4 - 4th parameter of a message

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

TABLES Parameters details for CLBA_CLASSIFICATION_BTCH_INPUT

IAUSP - Valuation data

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

IKSSK - Allocation dates

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

Copy and paste ABAP code example for CLBA_CLASSIFICATION_BTCH_INPUT 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:
lt_iausp  TYPE STANDARD TABLE OF BIAUSP, "   
lv_msgid  TYPE T100-ARBGB, "   
lv_bdc_flag  TYPE C, "   SPACE
lt_ikssk  TYPE STANDARD TABLE OF BIKSSK, "   
lv_msgno  TYPE SY-MSGNO, "   
lv_group_data  TYPE CLBGR00, "   
lv_msgty  TYPE SY-MSGTY, "   
lv_tcode_mode  TYPE SY, "   'S'
lv_msgv1  TYPE SY-MSGV1, "   
lv_tcode_update  TYPE SY, "   'S'
lv_msgv2  TYPE SY-MSGV2, "   
lv_msgv3  TYPE SY-MSGV3, "   
lv_msgv4  TYPE SY-MSGV4. "   

  CALL FUNCTION 'CLBA_CLASSIFICATION_BTCH_INPUT'  "
    EXPORTING
         BDC_FLAG = lv_bdc_flag
         GROUP_DATA = lv_group_data
         TCODE_MODE = lv_tcode_mode
         TCODE_UPDATE = lv_tcode_update
    IMPORTING
         MSGID = lv_msgid
         MSGNO = lv_msgno
         MSGTY = lv_msgty
         MSGV1 = lv_msgv1
         MSGV2 = lv_msgv2
         MSGV3 = lv_msgv3
         MSGV4 = lv_msgv4
    TABLES
         IAUSP = lt_iausp
         IKSSK = lt_ikssk
. " CLBA_CLASSIFICATION_BTCH_INPUT




ABAP code using 7.40 inline data declarations to call FM CLBA_CLASSIFICATION_BTCH_INPUT

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 ARBGB FROM T100 INTO @DATA(ld_msgid).
 
DATA(ld_bdc_flag) = ' '.
 
 
"SELECT single MSGNO FROM SY INTO @DATA(ld_msgno).
 
 
"SELECT single MSGTY FROM SY INTO @DATA(ld_msgty).
 
DATA(ld_tcode_mode) = 'S'.
 
"SELECT single MSGV1 FROM SY INTO @DATA(ld_msgv1).
 
DATA(ld_tcode_update) = 'S'.
 
"SELECT single MSGV2 FROM SY INTO @DATA(ld_msgv2).
 
"SELECT single MSGV3 FROM SY INTO @DATA(ld_msgv3).
 
"SELECT single MSGV4 FROM SY INTO @DATA(ld_msgv4).
 


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!