SAP BAPI_PROCORD_COSTING Function Module for BAPI: Carry Out Costing for Process Orders

Search SAP Function Modules

BAPI_PROCORD_COSTING is a standard bapi procord costing SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI: Carry Out Costing for Process Orders 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 bapi procord costing FM, simply by entering the name BAPI_PROCORD_COSTING into the relevant SAP transaction such as SE37 or SE38.

Function Group: 0001_BAPI
Program Name: SAPL0001_BAPI
Main Program: SAPL0001_BAPI
Appliation area:
Release date: 25-Feb-2004
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_PROCORD_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 'BAPI_PROCORD_COSTING'"BAPI: Carry Out Costing for Process Orders
  EXPORTING
*  WORK_PROCESS_GROUP = 'COWORK_BAPI' "Logon/Server Group Name
*  WORK_PROCESS_MAX = 99 "Maximum number of work processes that can be used

 IMPORTING
   RETURN =  "Return Parameters

TABLES
   ORDERS =  "Order Numbers
*  DETAIL_RETURN =  "Return Structure for Order BAPIs
*  APPLICATION_LOG =  "ApplicationLog Handle

.

IMPORTING Parameters details for BAPI_PROCORD_COSTING

WORK_PROCESS_GROUP - Logon/Server Group Name

Data type: BAPI_ORDER_CNTRL_PARAM-WORK_PROC_GROUP
Default: 'COWORK_BAPI'
Optional: Yes
Call by Reference: No ( called with pass by value option)

WORK_PROCESS_MAX - Maximum number of work processes that can be used

Data type: BAPI_ORDER_CNTRL_PARAM-WORK_PROC_MAX
Default: 99
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_PROCORD_COSTING

RETURN - Return Parameters

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

TABLES Parameters details for BAPI_PROCORD_COSTING

ORDERS - Order Numbers

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

DETAIL_RETURN - Return Structure for Order BAPIs

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

APPLICATION_LOG - ApplicationLog Handle

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

Copy and paste ABAP code example for BAPI_PROCORD_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.

ABAP code using 7.40 inline data declarations to call FM BAPI_PROCORD_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