SAP BAPI_PROCORD_GET_DETAIL Function Module for BAPI: Output Details of a Process Order









BAPI_PROCORD_GET_DETAIL is a standard bapi procord get detail 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: Output Details of a Process Order 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 get detail FM, simply by entering the name BAPI_PROCORD_GET_DETAIL 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: 02-Mar-2004
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_PROCORD_GET_DETAIL 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_GET_DETAIL'"BAPI: Output Details of a Process Order
  EXPORTING
   NUMBER =  "Process Order Number
*  COLLECTIVE_ORDER =  "Display complete collective order
   ORDER_OBJECTS =  "Selection Structure for Process Order Objects

 IMPORTING
   RETURN =  "Return Parameters

TABLES
*  HEADER =  "Order header data
*  POSITION =  "Order Item Data
*  SEQUENCE =  "Order Sequence Data
*  PHASE =  "Phase Data
*  TRIGGER_POINT =  "Trigger Point Data
*  COMPONENT =  "Component Data
*  PROD_REL_TOOL =  "Production resources and tools data
.



IMPORTING Parameters details for BAPI_PROCORD_GET_DETAIL

NUMBER - Process Order Number

Data type: BAPI_ORDER_KEY-ORDER_NUMBER
Optional: No
Call by Reference: No ( called with pass by value option)

COLLECTIVE_ORDER - Display complete collective order

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

ORDER_OBJECTS - Selection Structure for Process Order Objects

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

EXPORTING Parameters details for BAPI_PROCORD_GET_DETAIL

RETURN - Return Parameters

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

TABLES Parameters details for BAPI_PROCORD_GET_DETAIL

HEADER - Order header data

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

POSITION - Order Item Data

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

SEQUENCE - Order Sequence Data

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

PHASE - Phase Data

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

TRIGGER_POINT - Trigger Point Data

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

COMPONENT - Component Data

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

PROD_REL_TOOL - Production resources and tools data

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

Copy and paste ABAP code example for BAPI_PROCORD_GET_DETAIL 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_header  TYPE STANDARD TABLE OF BAPI_ORDER_HEADER1, "   
lv_number  TYPE BAPI_ORDER_KEY-ORDER_NUMBER, "   
lv_return  TYPE BAPIRET2, "   
lt_position  TYPE STANDARD TABLE OF BAPI_ORDER_ITEM, "   
lv_collective_order  TYPE BAPI_ORDER_FUNC_CNTRL-COLLECTIVE_ORDER, "   
lt_sequence  TYPE STANDARD TABLE OF BAPI_ORDER_SEQUENCE, "   
lv_order_objects  TYPE BAPI_PI_ORDER_OBJECTS, "   
lt_phase  TYPE STANDARD TABLE OF BAPI_ORDER_PHASE, "   
lt_trigger_point  TYPE STANDARD TABLE OF BAPI_ORDER_TRIGGER_POINT, "   
lt_component  TYPE STANDARD TABLE OF BAPI_ORDER_COMPONENT, "   
lt_prod_rel_tool  TYPE STANDARD TABLE OF BAPI_ORDER_PROD_REL_TOOLS. "   

  CALL FUNCTION 'BAPI_PROCORD_GET_DETAIL'  "BAPI: Output Details of a Process Order
    EXPORTING
         NUMBER = lv_number
         COLLECTIVE_ORDER = lv_collective_order
         ORDER_OBJECTS = lv_order_objects
    IMPORTING
         RETURN = lv_return
    TABLES
         HEADER = lt_header
         POSITION = lt_position
         SEQUENCE = lt_sequence
         PHASE = lt_phase
         TRIGGER_POINT = lt_trigger_point
         COMPONENT = lt_component
         PROD_REL_TOOL = lt_prod_rel_tool
. " BAPI_PROCORD_GET_DETAIL




ABAP code using 7.40 inline data declarations to call FM BAPI_PROCORD_GET_DETAIL

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 ORDER_NUMBER FROM BAPI_ORDER_KEY INTO @DATA(ld_number).
 
 
 
"SELECT single COLLECTIVE_ORDER FROM BAPI_ORDER_FUNC_CNTRL INTO @DATA(ld_collective_order).
 
 
 
 
 
 
 


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!