SAP BAPI_EPM_SO_CHANGE Function Module for EPM: BAPI 'Change Sales Order data by an Itelo Employee'
BAPI_EPM_SO_CHANGE is a standard bapi epm so change 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: BAPI 'Change Sales Order data by an Itelo Employee' 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 epm so change FM, simply by entering the name BAPI_EPM_SO_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SEPM_SALES_ORDER_BAPI
Program Name: SAPLSEPM_SALES_ORDER_BAPI
Main Program: SAPLSEPM_SALES_ORDER_BAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_EPM_SO_CHANGE 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_EPM_SO_CHANGE'"EPM: BAPI 'Change Sales Order data by an Itelo Employee'.
EXPORTING
SO_ID = "EPM: Sales Order ID to be used in BAPIs
* SOHEADERDATA = "EPM: Sales Order header data of BOR object 'EpmSalesOrder'
* SOHEADERDATAX = "EPM: SO header modif. info for BOR object EpmSalesOrder
* PERSIST_TO_DB = ABAP_TRUE "EPM: Boolean flag to be used as BAPI parameter
TABLES
* SOITEMDATA = "EPM: Sales Order Item data of BOR object 'EpmSalesOrder'
* SOITEMDATAX = "EPM: SO item. info for BOR object EpmSalesOrder
* RETURN = "Return Parameter
IMPORTING Parameters details for BAPI_EPM_SO_CHANGE
SO_ID - EPM: Sales Order ID to be used in BAPIs
Data type: BAPI_EPM_SO_IDOptional: No
Call by Reference: No ( called with pass by value option)
SOHEADERDATA - EPM: Sales Order header data of BOR object 'EpmSalesOrder'
Data type: BAPI_EPM_SO_HEADEROptional: Yes
Call by Reference: No ( called with pass by value option)
SOHEADERDATAX - EPM: SO header modif. info for BOR object EpmSalesOrder
Data type: BAPI_EPM_SO_HEADERXOptional: Yes
Call by Reference: No ( called with pass by value option)
PERSIST_TO_DB - EPM: Boolean flag to be used as BAPI parameter
Data type: BAPI_EPM_BOOLEANDefault: ABAP_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_EPM_SO_CHANGE
SOITEMDATA - EPM: Sales Order Item data of BOR object 'EpmSalesOrder'
Data type: BAPI_EPM_SO_ITEMOptional: Yes
Call by Reference: Yes
SOITEMDATAX - EPM: SO item. info for BOR object EpmSalesOrder
Data type: BAPI_EPM_SO_ITEMXOptional: Yes
Call by Reference: Yes
RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_EPM_SO_CHANGE 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_so_id | TYPE BAPI_EPM_SO_ID, " | |||
| lt_soitemdata | TYPE STANDARD TABLE OF BAPI_EPM_SO_ITEM, " | |||
| lt_soitemdatax | TYPE STANDARD TABLE OF BAPI_EPM_SO_ITEMX, " | |||
| lv_soheaderdata | TYPE BAPI_EPM_SO_HEADER, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_soheaderdatax | TYPE BAPI_EPM_SO_HEADERX, " | |||
| lv_persist_to_db | TYPE BAPI_EPM_BOOLEAN. " ABAP_TRUE |
|   CALL FUNCTION 'BAPI_EPM_SO_CHANGE' "EPM: BAPI 'Change Sales Order data by an Itelo Employee' |
| EXPORTING | ||
| SO_ID | = lv_so_id | |
| SOHEADERDATA | = lv_soheaderdata | |
| SOHEADERDATAX | = lv_soheaderdatax | |
| PERSIST_TO_DB | = lv_persist_to_db | |
| TABLES | ||
| SOITEMDATA | = lt_soitemdata | |
| SOITEMDATAX | = lt_soitemdatax | |
| RETURN | = lt_return | |
| . " BAPI_EPM_SO_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_EPM_SO_CHANGE
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.| DATA(ld_persist_to_db) | = ABAP_TRUE. | |||
Search for further information about these or an SAP related objects