SAP CON_ACC_BADI_ORDER_COSTING Function Module for









CON_ACC_BADI_ORDER_COSTING is a standard con acc badi order costing 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 con acc badi order costing FM, simply by entering the name CON_ACC_BADI_ORDER_COSTING into the relevant SAP transaction such as SE37 or SE38.

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



Function CON_ACC_BADI_ORDER_COSTING 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 'CON_ACC_BADI_ORDER_COSTING'"
  EXPORTING
   IR_CON_FIN_COPROD_DISTR =  "
   ID_STLPROCID =  "
*  ID_KEYDATE =  "
   IT_STLRULES_D =  "
   IR_BASISDATA =  "
*  ID_STRUCNAME_BASIS =  "
   IT_RECEIVER =  "
   ID_STLFUNCTION =  "

 IMPORTING
   ER_RESULT =  "
   ED_STRUCNAME_RESULT =  "
   ED_ERROR_OCCURRED =  "
   ET_BAPIRET =  "
   ED_DISTRIBUTION_DONE =  "
.



IMPORTING Parameters details for CON_ACC_BADI_ORDER_COSTING

IR_CON_FIN_COPROD_DISTR -

Data type: OBJECT
Optional: No
Call by Reference: Yes

ID_STLPROCID -

Data type: FIN_STLPROCID
Optional: No
Call by Reference: Yes

ID_KEYDATE -

Data type: DATUM
Optional: Yes
Call by Reference: Yes

IT_STLRULES_D -

Data type: UAINV_T_STLRULES_D
Optional: No
Call by Reference: Yes

IR_BASISDATA -

Data type: DATA
Optional: No
Call by Reference: Yes

ID_STRUCNAME_BASIS -

Data type: FIELDNAME
Optional: Yes
Call by Reference: Yes

IT_RECEIVER -

Data type: UAINV_T_ENHANCED_RECEIVER
Optional: No
Call by Reference: Yes

ID_STLFUNCTION -

Data type: FIN_STLFUNCTION
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for CON_ACC_BADI_ORDER_COSTING

ER_RESULT -

Data type: DATA
Optional: No
Call by Reference: Yes

ED_STRUCNAME_RESULT -

Data type: FIELDNAME
Optional: No
Call by Reference: Yes

ED_ERROR_OCCURRED -

Data type: BOOLE_D
Optional: No
Call by Reference: Yes

ET_BAPIRET -

Data type: BAPIRETTAB
Optional: No
Call by Reference: Yes

ED_DISTRIBUTION_DONE -

Data type: BOOLE_D
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CON_ACC_BADI_ORDER_COSTING 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_er_result  TYPE DATA, "   
lv_ir_con_fin_coprod_distr  TYPE OBJECT, "   
lv_id_stlprocid  TYPE FIN_STLPROCID, "   
lv_ed_strucname_result  TYPE FIELDNAME, "   
lv_id_keydate  TYPE DATUM, "   
lv_ed_error_occurred  TYPE BOOLE_D, "   
lv_et_bapiret  TYPE BAPIRETTAB, "   
lv_it_stlrules_d  TYPE UAINV_T_STLRULES_D, "   
lv_ir_basisdata  TYPE DATA, "   
lv_ed_distribution_done  TYPE BOOLE_D, "   
lv_id_strucname_basis  TYPE FIELDNAME, "   
lv_it_receiver  TYPE UAINV_T_ENHANCED_RECEIVER, "   
lv_id_stlfunction  TYPE FIN_STLFUNCTION. "   

  CALL FUNCTION 'CON_ACC_BADI_ORDER_COSTING'  "
    EXPORTING
         IR_CON_FIN_COPROD_DISTR = lv_ir_con_fin_coprod_distr
         ID_STLPROCID = lv_id_stlprocid
         ID_KEYDATE = lv_id_keydate
         IT_STLRULES_D = lv_it_stlrules_d
         IR_BASISDATA = lv_ir_basisdata
         ID_STRUCNAME_BASIS = lv_id_strucname_basis
         IT_RECEIVER = lv_it_receiver
         ID_STLFUNCTION = lv_id_stlfunction
    IMPORTING
         ER_RESULT = lv_er_result
         ED_STRUCNAME_RESULT = lv_ed_strucname_result
         ED_ERROR_OCCURRED = lv_ed_error_occurred
         ET_BAPIRET = lv_et_bapiret
         ED_DISTRIBUTION_DONE = lv_ed_distribution_done
. " CON_ACC_BADI_ORDER_COSTING




ABAP code using 7.40 inline data declarations to call FM CON_ACC_BADI_ORDER_COSTING

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



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!