SAP /1FE/CSAP_BIT2_UPDATE Function Module for Change Billable Items for Class CSAP
/1FE/CSAP_BIT2_UPDATE is a standard /1fe/csap bit2 update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change Billable Items for Class CSAP 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 /1fe/csap bit2 update FM, simply by entering the name /1FE/CSAP_BIT2_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: /1FE/CSAP
Program Name: /1FE/SAPLCSAP
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function /1FE/CSAP_BIT2_UPDATE 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 '/1FE/CSAP_BIT2_UPDATE'"Change Billable Items for Class CSAP.
EXPORTING
* IT_BIT2_IT = "
* IT_BIT2_PY = "
* IT_BIT2_TX = "
* IT_BIT2_TT = "
IMPORTING Parameters details for /1FE/CSAP_BIT2_UPDATE
IT_BIT2_IT -
Data type: FKKBIXBIT2_IT_ALL_TABOptional: Yes
Call by Reference: Yes
IT_BIT2_PY -
Data type: FKKBIXBIT2_PY_ALL_TABOptional: Yes
Call by Reference: Yes
IT_BIT2_TX -
Data type: FKKBIXBIT2_TX_ALL_TABOptional: Yes
Call by Reference: Yes
IT_BIT2_TT -
Data type: FKKBIXBIT2_TT_ALL_TABOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for /1FE/CSAP_BIT2_UPDATE 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_it_bit2_it | TYPE FKKBIXBIT2_IT_ALL_TAB, " | |||
lv_it_bit2_py | TYPE FKKBIXBIT2_PY_ALL_TAB, " | |||
lv_it_bit2_tx | TYPE FKKBIXBIT2_TX_ALL_TAB, " | |||
lv_it_bit2_tt | TYPE FKKBIXBIT2_TT_ALL_TAB. " |
  CALL FUNCTION '/1FE/CSAP_BIT2_UPDATE' "Change Billable Items for Class CSAP |
EXPORTING | ||
IT_BIT2_IT | = lv_it_bit2_it | |
IT_BIT2_PY | = lv_it_bit2_py | |
IT_BIT2_TX | = lv_it_bit2_tx | |
IT_BIT2_TT | = lv_it_bit2_tt | |
. " /1FE/CSAP_BIT2_UPDATE |
ABAP code using 7.40 inline data declarations to call FM /1FE/CSAP_BIT2_UPDATE
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