SAP BCA_DIM_BILLDOC_CHANGE Function Module for Abrechnungsbelege erzeugen
BCA_DIM_BILLDOC_CHANGE is a standard bca dim billdoc change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Abrechnungsbelege erzeugen 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 bca dim billdoc change FM, simply by entering the name BCA_DIM_BILLDOC_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BCA_DIM_LOANS_RFC
Program Name: SAPLBCA_DIM_LOANS_RFC
Main Program: SAPLBCA_DIM_LOANS_RFC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BCA_DIM_BILLDOC_CHANGE 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 'BCA_DIM_BILLDOC_CHANGE'"Abrechnungsbelege erzeugen.
EXPORTING
ADJUSTED_DOC = "External Billing Document to be Adjusted
HEADER = "Header structure for wrapper RFC
* TESTRUN = ' ' "Switch to Simulation Session for Write BAPIs
TABLES
* ITEMS = "Items for Wrapper RFC
* TAXITEMS = "Tax items in External Billing System
* ADDITEMS = "
* EXTENSIONIN = "
* EXTENSIONOUT = "
* BAPI_BILLDOCNUMBER = "
RETURN = "
EXCEPTIONS
BP_UPDATE_FAILED = 1 FAILED = 2
IMPORTING Parameters details for BCA_DIM_BILLDOC_CHANGE
ADJUSTED_DOC - External Billing Document to be Adjusted
Data type: BAPI_EXT_ADJUSTED_DOCOptional: No
Call by Reference: No ( called with pass by value option)
HEADER - Header structure for wrapper RFC
Data type: BCA_STR_DIM_BAPI_EXTDOC_HOptional: No
Call by Reference: No ( called with pass by value option)
TESTRUN - Switch to Simulation Session for Write BAPIs
Data type: BAPI_AUX_INV-TESTRUNDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BCA_DIM_BILLDOC_CHANGE
ITEMS - Items for Wrapper RFC
Data type: BCA_STR_DIM_BAPI_IST_EXTDOC_IOptional: Yes
Call by Reference: No ( called with pass by value option)
TAXITEMS - Tax items in External Billing System
Data type: BAPI_EXTDOC_TOptional: Yes
Call by Reference: No ( called with pass by value option)
ADDITEMS -
Data type: BAPI_EXTDOC_AOptional: Yes
Call by Reference: No ( called with pass by value option)
EXTENSIONIN -
Data type: BAPIPAREXOptional: Yes
Call by Reference: No ( called with pass by value option)
EXTENSIONOUT -
Data type: BAPIPAREXOptional: Yes
Call by Reference: No ( called with pass by value option)
BAPI_BILLDOCNUMBER -
Data type: BAPI_FKKINV_BILLDOCNUMBEROptional: Yes
Call by Reference: No ( called with pass by value option)
RETURN -
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
BP_UPDATE_FAILED - Business Partner Update Failed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FAILED - Billing Document Creation Failed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BCA_DIM_BILLDOC_CHANGE 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_items | TYPE STANDARD TABLE OF BCA_STR_DIM_BAPI_IST_EXTDOC_I, " | |||
| lv_adjusted_doc | TYPE BAPI_EXT_ADJUSTED_DOC, " | |||
| lv_bp_update_failed | TYPE BAPI_EXT_ADJUSTED_DOC, " | |||
| lv_failed | TYPE BAPI_EXT_ADJUSTED_DOC, " | |||
| lv_header | TYPE BCA_STR_DIM_BAPI_EXTDOC_H, " | |||
| lt_taxitems | TYPE STANDARD TABLE OF BAPI_EXTDOC_T, " | |||
| lv_testrun | TYPE BAPI_AUX_INV-TESTRUN, " SPACE | |||
| lt_additems | TYPE STANDARD TABLE OF BAPI_EXTDOC_A, " | |||
| lt_extensionin | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_extensionout | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_bapi_billdocnumber | TYPE STANDARD TABLE OF BAPI_FKKINV_BILLDOCNUMBER, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2. " |
| CALL FUNCTION 'BCA_DIM_BILLDOC_CHANGE' "Abrechnungsbelege erzeugen |
| EXPORTING | ||
| ADJUSTED_DOC | = lv_adjusted_doc | |
| HEADER | = lv_header | |
| TESTRUN | = lv_testrun | |
| TABLES | ||
| ITEMS | = lt_items | |
| TAXITEMS | = lt_taxitems | |
| ADDITEMS | = lt_additems | |
| EXTENSIONIN | = lt_extensionin | |
| EXTENSIONOUT | = lt_extensionout | |
| BAPI_BILLDOCNUMBER | = lt_bapi_billdocnumber | |
| RETURN | = lt_return | |
| EXCEPTIONS | ||
| BP_UPDATE_FAILED = 1 | ||
| FAILED = 2 | ||
| . " BCA_DIM_BILLDOC_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM BCA_DIM_BILLDOC_CHANGE
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 TESTRUN FROM BAPI_AUX_INV INTO @DATA(ld_testrun). | ||||
| DATA(ld_testrun) | = ' '. | |||
Search for further information about these or an SAP related objects