SAP BAPI_PROCORDCONF_CREATE_HDR Function Module for Enter Confirmations for Process Order Header









BAPI_PROCORDCONF_CREATE_HDR is a standard bapi procordconf create hdr SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Enter Confirmations for Process Order Header 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 procordconf create hdr FM, simply by entering the name BAPI_PROCORDCONF_CREATE_HDR into the relevant SAP transaction such as SE37 or SE38.

Function Group: 2016
Program Name: SAPL2016
Main Program: SAPL2016
Appliation area:
Release date: 04-Feb-2004
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_PROCORDCONF_CREATE_HDR 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_PROCORDCONF_CREATE_HDR'"Enter Confirmations for Process Order Header
EXPORTING
* POST_WRONG_ENTRIES = '0' "Key: Insert Incorrect Confirmations
* TESTRUN = "Switch to Simulation Mode for Write BAPIs

IMPORTING
RETURN = "Return Parameter(s)

TABLES
ATHDRLEVELS = "Process Order Confirmation: Header Confirmation
* GOODSMOVEMENTS = "BAPI Communication Structure: Create Material Document Item
* LINK_CONF_GOODSMOV = "Link: Confirmation with Goods Movements
* CHARACTERISTICS_BATCH = "Batch Characteristics
* LINK_GM_CHAR_BATCH = "Link: Batch Characteristics with Goods Movement Item
* DETAIL_RETURN = "Return Information for APIs
.



IMPORTING Parameters details for BAPI_PROCORDCONF_CREATE_HDR

POST_WRONG_ENTRIES - Key: Insert Incorrect Confirmations

Data type: BAPI_CORU_PARAM-INS_ERR
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TESTRUN - Switch to Simulation Mode for Write BAPIs

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

EXPORTING Parameters details for BAPI_PROCORDCONF_CREATE_HDR

RETURN - Return Parameter(s)

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

TABLES Parameters details for BAPI_PROCORDCONF_CREATE_HDR

ATHDRLEVELS - Process Order Confirmation: Header Confirmation

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

GOODSMOVEMENTS - BAPI Communication Structure: Create Material Document Item

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

LINK_CONF_GOODSMOV - Link: Confirmation with Goods Movements

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

CHARACTERISTICS_BATCH - Batch Characteristics

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

LINK_GM_CHAR_BATCH - Link: Batch Characteristics with Goods Movement Item

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

DETAIL_RETURN - Return Information for APIs

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

Copy and paste ABAP code example for BAPI_PROCORDCONF_CREATE_HDR 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_return  TYPE BAPIRET1, "   
lt_athdrlevels  TYPE STANDARD TABLE OF BAPI_PI_HDRLEVEL, "   
lv_post_wrong_entries  TYPE BAPI_CORU_PARAM-INS_ERR, "   '0'
lv_testrun  TYPE BAPI_CORU_PARAM-TESTRUN, "   
lt_goodsmovements  TYPE STANDARD TABLE OF BAPI2017_GM_ITEM_CREATE, "   
lt_link_conf_goodsmov  TYPE STANDARD TABLE OF BAPI_LINK_CONF_GOODSMOV, "   
lt_characteristics_batch  TYPE STANDARD TABLE OF BAPI_CHAR_BATCH, "   
lt_link_gm_char_batch  TYPE STANDARD TABLE OF BAPI_LINK_GM_CHAR_BATCH, "   
lt_detail_return  TYPE STANDARD TABLE OF BAPI_CORU_RETURN. "   

  CALL FUNCTION 'BAPI_PROCORDCONF_CREATE_HDR'  "Enter Confirmations for Process Order Header
    EXPORTING
         POST_WRONG_ENTRIES = lv_post_wrong_entries
         TESTRUN = lv_testrun
    IMPORTING
         RETURN = lv_return
    TABLES
         ATHDRLEVELS = lt_athdrlevels
         GOODSMOVEMENTS = lt_goodsmovements
         LINK_CONF_GOODSMOV = lt_link_conf_goodsmov
         CHARACTERISTICS_BATCH = lt_characteristics_batch
         LINK_GM_CHAR_BATCH = lt_link_gm_char_batch
         DETAIL_RETURN = lt_detail_return
. " BAPI_PROCORDCONF_CREATE_HDR




ABAP code using 7.40 inline data declarations to call FM BAPI_PROCORDCONF_CREATE_HDR

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 INS_ERR FROM BAPI_CORU_PARAM INTO @DATA(ld_post_wrong_entries).
DATA(ld_post_wrong_entries) = '0'.
 
"SELECT single TESTRUN FROM BAPI_CORU_PARAM INTO @DATA(ld_testrun).
 
 
 
 
 
 


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!