SAP Function Modules

comments icon Comments

BAPI_PROCORDCONF_GETDETAIL SAP Function module - Detail Data for Process Order Confirmation







BAPI_PROCORDCONF_GETDETAIL is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name BAPI_PROCORDCONF_GETDETAIL into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: 2016
Released Date: 04.02.2004
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM BAPI_PROCORDCONF_GETDETAIL - BAPI PROCORDCONF GETDETAIL 





CALL FUNCTION 'BAPI_PROCORDCONF_GETDETAIL' "Detail Data for Process Order Confirmation
  EXPORTING
    confirmation =              " bapi_pi_conf_key-conf_no  Completion confirmation number for the operation
    confirmationcounter =       " bapi_pi_conf_key-conf_cnt  Confirmation counter
  IMPORTING
    return =                    " bapiret1      Return Parameters
    conf_detail =               " bapi_pi_confirm  Process Order Confirmation
* TABLES
*   goodsmovements =            " bapi2017_gm_item_show  BAPI Communication Structure: Display Mat. Document Item
*   failedgmoves =              " bapi_coru_fgm  Incorrect and intended goods movements for confirmation
    .  "  BAPI_PROCORDCONF_GETDETAIL

ABAP code example for Function Module BAPI_PROCORDCONF_GETDETAIL





The ABAP code below is a full code listing to execute function module BAPI_PROCORDCONF_GETDETAIL including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_return    TYPE BAPIRET1
,
ld_conf_detail    TYPE BAPI_PI_CONFIRM
,
it_goodsmovements    TYPE STANDARD TABLE OF BAPI2017_GM_ITEM_SHOW,"TABLES PARAM
wa_goodsmovements  LIKE LINE OF it_goodsmovements
,
it_failedgmoves    TYPE STANDARD TABLE OF BAPI_CORU_FGM,"TABLES PARAM
wa_failedgmoves  LIKE LINE OF it_failedgmoves
.





DATA(ld_confirmation) = Check type of data required


DATA(ld_confirmationcounter) = Check type of data required
 

"populate fields of struture and append to itab
append wa_goodsmovements to it_goodsmovements.
 

"populate fields of struture and append to itab
append wa_failedgmoves to it_failedgmoves.
.

CALL FUNCTION 'BAPI_PROCORDCONF_GETDETAIL'
  EXPORTING
    confirmation =               ld_confirmation
    confirmationcounter =        ld_confirmationcounter
  IMPORTING
    return =                     ld_return
    conf_detail =                ld_conf_detail
* TABLES
*   goodsmovements =             it_goodsmovements
*   failedgmoves =               it_failedgmoves
    .  "  BAPI_PROCORDCONF_GETDETAIL

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_return  TYPE BAPIRET1 ,
ld_confirmation  TYPE BAPI_PI_CONF_KEY-CONF_NO ,
it_goodsmovements  TYPE STANDARD TABLE OF BAPI2017_GM_ITEM_SHOW ,
wa_goodsmovements  LIKE LINE OF it_goodsmovements,
ld_conf_detail  TYPE BAPI_PI_CONFIRM ,
ld_confirmationcounter  TYPE BAPI_PI_CONF_KEY-CONF_CNT ,
it_failedgmoves  TYPE STANDARD TABLE OF BAPI_CORU_FGM ,
wa_failedgmoves  LIKE LINE OF it_failedgmoves.





ld_confirmation = Check type of data required 

"populate fields of struture and append to itab
append wa_goodsmovements to it_goodsmovements.

ld_confirmationcounter = Check type of data required 

"populate fields of struture and append to itab
append wa_failedgmoves to it_failedgmoves.

SAP Documentation for FM BAPI_PROCORDCONF_GETDETAIL


You can use this method to make the data of a confirmation for a process order available in the ConfDetail. ...See here for full SAP fm documentation

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name BAPI_PROCORDCONF_GETDETAIL or its description.


   
 

BAPI_PROCORDCONF_GETDETAIL - Detail Data for Process Order Confirmation
BAPI_PROCORDCONF_EXIST_CHK - Existence Check for Confirmation of Process Order
BAPI_PROCORDCONF_CREATE_TT - Enter Confirmation Time Ticket for Process Order
BAPI_PROCORDCONF_CREATE_TE - Enter Confirmation Time Event for Process Order
BAPI_PROCORDCONF_CREATE_HDR - Enter Confirmations for Process Order Header
BAPI_PROCORDCONF_CREATE_ACT - Enter Activity Confirmations for Process Orders