SAP SEPM_GWS_SO_GET_DETAIL Function Module for EPM: Retrieval of Sales Order Data ( triggered by an EPM GW-Service )
SEPM_GWS_SO_GET_DETAIL is a standard sepm gws so 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 EPM: Retrieval of Sales Order Data ( triggered by an EPM GW-Service ) 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 sepm gws so get detail FM, simply by entering the name SEPM_GWS_SO_GET_DETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: SEPM_GATEWAY_SERVICES
Program Name: SAPLSEPM_GATEWAY_SERVICES
Main Program: SAPLSEPM_GATEWAY_SERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SEPM_GWS_SO_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 'SEPM_GWS_SO_GET_DETAIL'"EPM: Retrieval of Sales Order Data ( triggered by an EPM GW-Service ).
EXPORTING
IV_SO_ID = "EPM: Sales Order ID
* IT_BEHAVIOR_CONTROL = "EPM: Behavior control for Gateway Service RFCs
IMPORTING
ES_SO_HEADER = "EPM: SO Header data for Gateway Services
ET_SO_ITEMS = "EPM: Sales Order item list for GW Services
ET_RETURN = "Return parameter table
IMPORTING Parameters details for SEPM_GWS_SO_GET_DETAIL
IV_SO_ID - EPM: Sales Order ID
Data type: SNWD_SO_IDOptional: No
Call by Reference: No ( called with pass by value option)
IT_BEHAVIOR_CONTROL - EPM: Behavior control for Gateway Service RFCs
Data type: SEPM_GWS_BEHAVIOR_CONTROL_TOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SEPM_GWS_SO_GET_DETAIL
ES_SO_HEADER - EPM: SO Header data for Gateway Services
Data type: SEPM_GWS_SO_HEADEROptional: No
Call by Reference: No ( called with pass by value option)
ET_SO_ITEMS - EPM: Sales Order item list for GW Services
Data type: SEPM_GWS_SO_ITEM_TOptional: No
Call by Reference: No ( called with pass by value option)
ET_RETURN - Return parameter table
Data type: BAPIRET2_TOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SEPM_GWS_SO_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: | ||||
| lv_iv_so_id | TYPE SNWD_SO_ID, " | |||
| lv_es_so_header | TYPE SEPM_GWS_SO_HEADER, " | |||
| lv_et_so_items | TYPE SEPM_GWS_SO_ITEM_T, " | |||
| lv_it_behavior_control | TYPE SEPM_GWS_BEHAVIOR_CONTROL_T, " | |||
| lv_et_return | TYPE BAPIRET2_T. " |
|   CALL FUNCTION 'SEPM_GWS_SO_GET_DETAIL' "EPM: Retrieval of Sales Order Data ( triggered by an EPM GW-Service ) |
| EXPORTING | ||
| IV_SO_ID | = lv_iv_so_id | |
| IT_BEHAVIOR_CONTROL | = lv_it_behavior_control | |
| IMPORTING | ||
| ES_SO_HEADER | = lv_es_so_header | |
| ET_SO_ITEMS | = lv_et_so_items | |
| ET_RETURN | = lv_et_return | |
| . " SEPM_GWS_SO_GET_DETAIL | ||
ABAP code using 7.40 inline data declarations to call FM SEPM_GWS_SO_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.Search for further information about these or an SAP related objects