SAP EXIT_SAPLE70E_001 Function Module for IS-U: Enhance communication structure MCVU_ESTA
EXIT_SAPLE70E_001 is a standard exit saple70e 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-U: Enhance communication structure MCVU_ESTA 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 exit saple70e 001 FM, simply by entering the name EXIT_SAPLE70E_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XE70E
Program Name: SAPLXE70E
Main Program: SAPLXE70E
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPLE70E_001 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 'EXIT_SAPLE70E_001'"IS-U: Enhance communication structure MCVU_ESTA.
EXPORTING
X_BILL = "Data for Changing Budget Billing Cycle
TABLES
XMCVU_ESTA = "Communication Structure
T_EVER = "Contract Data
T_EANL = "Installation Data
EXCEPTIONS
INPUT_ERROR = 1
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.ISU_SALES_STATS_CREATE_MCESTA INTERNAL: Supply Communication Structure MCESTA from Bill Document
IMPORTING Parameters details for EXIT_SAPLE70E_001
X_BILL - Data for Changing Budget Billing Cycle
Data type: ISU2A_BILL_DOCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPLE70E_001
XMCVU_ESTA - Communication Structure
Data type: MCVU_ESTAOptional: No
Call by Reference: No ( called with pass by value option)
T_EVER - Contract Data
Data type: EVEROptional: No
Call by Reference: No ( called with pass by value option)
T_EANL - Installation Data
Data type: V_EANLOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INPUT_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLE70E_001 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_x_bill | TYPE ISU2A_BILL_DOC, " | |||
lt_xmcvu_esta | TYPE STANDARD TABLE OF MCVU_ESTA, " | |||
lv_input_error | TYPE MCVU_ESTA, " | |||
lt_t_ever | TYPE STANDARD TABLE OF EVER, " | |||
lt_t_eanl | TYPE STANDARD TABLE OF V_EANL. " |
  CALL FUNCTION 'EXIT_SAPLE70E_001' "IS-U: Enhance communication structure MCVU_ESTA |
EXPORTING | ||
X_BILL | = lv_x_bill | |
TABLES | ||
XMCVU_ESTA | = lt_xmcvu_esta | |
T_EVER | = lt_t_ever | |
T_EANL | = lt_t_eanl | |
EXCEPTIONS | ||
INPUT_ERROR = 1 | ||
. " EXIT_SAPLE70E_001 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLE70E_001
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