SAP CS_BT_POSITION_CHECK Function Module for NOTRANSL: Logisch selektierte und änderbare Positionen im Beleg kennzeichn









CS_BT_POSITION_CHECK is a standard cs bt position check 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: Logisch selektierte und änderbare Positionen im Beleg kennzeichn 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 cs bt position check FM, simply by entering the name CS_BT_POSITION_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function CS_BT_POSITION_CHECK 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 'CS_BT_POSITION_CHECK'"NOTRANSL: Logisch selektierte und änderbare Positionen im Beleg kennzeichn
EXPORTING
* EDATUB = 00000000 "
* EDATUV = 00000000 "
* ESTLAL = ' ' "
ETRTYP = "
* FLG_NFGRP = ' ' "
* FLG_NO_CHANGE = ' ' "

IMPORTING
FLG_BEZWI = "
FLG_CLSZU = "

TABLES
* NFTAB = "

EXCEPTIONS
POS_INVALID = 1 POS_NO_AENKZ = 2
.




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_SAPLCSBT_001 Order BOM (Knowledge Based): Set Status at Fix

IMPORTING Parameters details for CS_BT_POSITION_CHECK

EDATUB -

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

EDATUV -

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

ESTLAL -

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

ETRTYP -

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

FLG_NFGRP -

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

FLG_NO_CHANGE -

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

EXPORTING Parameters details for CS_BT_POSITION_CHECK

FLG_BEZWI -

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

FLG_CLSZU -

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

TABLES Parameters details for CS_BT_POSITION_CHECK

NFTAB -

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

EXCEPTIONS details

POS_INVALID - No valid item

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

POS_NO_AENKZ - No changeable item

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

Copy and paste ABAP code example for CS_BT_POSITION_CHECK 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_nftab  TYPE STANDARD TABLE OF CSNFTAB, "   
lv_edatub  TYPE SY-DATUM, "   00000000
lv_flg_bezwi  TYPE CSDATA-XFELD, "   
lv_pos_invalid  TYPE CSDATA, "   
lv_edatuv  TYPE SY-DATUM, "   00000000
lv_flg_clszu  TYPE CSDATA-XFELD, "   
lv_pos_no_aenkz  TYPE CSDATA, "   
lv_estlal  TYPE STAS-STLAL, "   SPACE
lv_etrtyp  TYPE TCS05-TRTYP, "   
lv_flg_nfgrp  TYPE CSDATA-XFELD, "   SPACE
lv_flg_no_change  TYPE CSDATA-XFELD. "   SPACE

  CALL FUNCTION 'CS_BT_POSITION_CHECK'  "NOTRANSL: Logisch selektierte und änderbare Positionen im Beleg kennzeichn
    EXPORTING
         EDATUB = lv_edatub
         EDATUV = lv_edatuv
         ESTLAL = lv_estlal
         ETRTYP = lv_etrtyp
         FLG_NFGRP = lv_flg_nfgrp
         FLG_NO_CHANGE = lv_flg_no_change
    IMPORTING
         FLG_BEZWI = lv_flg_bezwi
         FLG_CLSZU = lv_flg_clszu
    TABLES
         NFTAB = lt_nftab
    EXCEPTIONS
        POS_INVALID = 1
        POS_NO_AENKZ = 2
. " CS_BT_POSITION_CHECK




ABAP code using 7.40 inline data declarations to call FM CS_BT_POSITION_CHECK

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 DATUM FROM SY INTO @DATA(ld_edatub).
DATA(ld_edatub) = 00000000.
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_flg_bezwi).
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_edatuv).
DATA(ld_edatuv) = 00000000.
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_flg_clszu).
 
 
"SELECT single STLAL FROM STAS INTO @DATA(ld_estlal).
DATA(ld_estlal) = ' '.
 
"SELECT single TRTYP FROM TCS05 INTO @DATA(ld_etrtyp).
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_flg_nfgrp).
DATA(ld_flg_nfgrp) = ' '.
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_flg_no_change).
DATA(ld_flg_no_change) = ' '.
 


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!