SAP BAPI_EXTORDER_CH_GETDETAIL Function Module for
BAPI_EXTORDER_CH_GETDETAIL is a standard bapi extorder ch getdetail 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 bapi extorder ch getdetail FM, simply by entering the name BAPI_EXTORDER_CH_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: 1312CH
Program Name: SAPL1312CH
Main Program: SAPL1312CH
Appliation area:
Release date: 13-May-2002
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_EXTORDER_CH_GETDETAIL 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_EXTORDER_CH_GETDETAIL'".
EXPORTING
EXTORDER_NO = "
IMPORTING
ORDER_HEADER = "
EXTORDER_HEADER = "
WORST_RETURNED_MSGTY = "
TABLES
* ORDER_POSITION = "
* EXTORDER_POSITION = "
* ORDER_BUSINESS_DATA = "
* ORDER_BUSINESS_PARTNER = "
* ORDER_ADDRESS_DATA = "
* ORDER_CONDITIONS = "
* ORDER_TEXTH = "
* ORDER_TEXTL = "
* RETURN = "
IMPORTING Parameters details for BAPI_EXTORDER_CH_GETDETAIL
EXTORDER_NO -
Data type: BAPIVBELN-VBELNOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_EXTORDER_CH_GETDETAIL
ORDER_HEADER -
Data type: BAPISDHDOptional: No
Call by Reference: No ( called with pass by value option)
EXTORDER_HEADER -
Data type: BAPI1312CHVBAKOptional: No
Call by Reference: No ( called with pass by value option)
WORST_RETURNED_MSGTY -
Data type: BAPINALL-WORSTRETMSGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_EXTORDER_CH_GETDETAIL
ORDER_POSITION -
Data type: BAPISDITOptional: Yes
Call by Reference: Yes
EXTORDER_POSITION -
Data type: BAPI1312CHVBAPOptional: Yes
Call by Reference: Yes
ORDER_BUSINESS_DATA -
Data type: BAPISDBUSIOptional: Yes
Call by Reference: Yes
ORDER_BUSINESS_PARTNER -
Data type: BAPISDPARTOptional: Yes
Call by Reference: Yes
ORDER_ADDRESS_DATA -
Data type: BAPISDCOADOptional: Yes
Call by Reference: Yes
ORDER_CONDITIONS -
Data type: BAPISDCONDOptional: Yes
Call by Reference: Yes
ORDER_TEXTH -
Data type: BAPISDTEHDOptional: Yes
Call by Reference: Yes
ORDER_TEXTL -
Data type: BAPITEXTLIOptional: Yes
Call by Reference: Yes
RETURN -
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_EXTORDER_CH_GETDETAIL 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_extorder_no | TYPE BAPIVBELN-VBELN, " | |||
| lv_order_header | TYPE BAPISDHD, " | |||
| lt_order_position | TYPE STANDARD TABLE OF BAPISDIT, " | |||
| lv_extorder_header | TYPE BAPI1312CHVBAK, " | |||
| lt_extorder_position | TYPE STANDARD TABLE OF BAPI1312CHVBAP, " | |||
| lt_order_business_data | TYPE STANDARD TABLE OF BAPISDBUSI, " | |||
| lv_worst_returned_msgty | TYPE BAPINALL-WORSTRETMSG, " | |||
| lt_order_business_partner | TYPE STANDARD TABLE OF BAPISDPART, " | |||
| lt_order_address_data | TYPE STANDARD TABLE OF BAPISDCOAD, " | |||
| lt_order_conditions | TYPE STANDARD TABLE OF BAPISDCOND, " | |||
| lt_order_texth | TYPE STANDARD TABLE OF BAPISDTEHD, " | |||
| lt_order_textl | TYPE STANDARD TABLE OF BAPITEXTLI, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2. " |
|   CALL FUNCTION 'BAPI_EXTORDER_CH_GETDETAIL' " |
| EXPORTING | ||
| EXTORDER_NO | = lv_extorder_no | |
| IMPORTING | ||
| ORDER_HEADER | = lv_order_header | |
| EXTORDER_HEADER | = lv_extorder_header | |
| WORST_RETURNED_MSGTY | = lv_worst_returned_msgty | |
| TABLES | ||
| ORDER_POSITION | = lt_order_position | |
| EXTORDER_POSITION | = lt_extorder_position | |
| ORDER_BUSINESS_DATA | = lt_order_business_data | |
| ORDER_BUSINESS_PARTNER | = lt_order_business_partner | |
| ORDER_ADDRESS_DATA | = lt_order_address_data | |
| ORDER_CONDITIONS | = lt_order_conditions | |
| ORDER_TEXTH | = lt_order_texth | |
| ORDER_TEXTL | = lt_order_textl | |
| RETURN | = lt_return | |
| . " BAPI_EXTORDER_CH_GETDETAIL | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_EXTORDER_CH_GETDETAIL
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 VBELN FROM BAPIVBELN INTO @DATA(ld_extorder_no). | ||||
| "SELECT single WORSTRETMSG FROM BAPINALL INTO @DATA(ld_worst_returned_msgty). | ||||
Search for further information about these or an SAP related objects