SAP EXIT_SAPMOIFA_040 Function Module for Validation of customer SD partner functions









EXIT_SAPMOIFA_040 is a standard exit sapmoifa 040 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Validation of customer SD partner functions 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 sapmoifa 040 FM, simply by entering the name EXIT_SAPMOIFA_040 into the relevant SAP transaction such as SE37 or SE38.

Function Group: XOIF
Program Name: SAPLXOIF
Main Program: SAPLXOIF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function EXIT_SAPMOIFA_040 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_SAPMOIFA_040'"Validation of customer SD partner functions
IMPORTING
E_STATUS = "

TABLES
T_OIRBBP1PF = "Location partner role SD partner functions (IS-Oil SSR)
.



EXPORTING Parameters details for EXIT_SAPMOIFA_040

E_STATUS -

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

TABLES Parameters details for EXIT_SAPMOIFA_040

T_OIRBBP1PF - Location partner role SD partner functions (IS-Oil SSR)

Data type: ROIRBBP1PF
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for EXIT_SAPMOIFA_040 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_e_status  TYPE ROIFXICSTA-OBSTAT, "   
lt_t_oirbbp1pf  TYPE STANDARD TABLE OF ROIRBBP1PF. "   

  CALL FUNCTION 'EXIT_SAPMOIFA_040'  "Validation of customer SD partner functions
    IMPORTING
         E_STATUS = lv_e_status
    TABLES
         T_OIRBBP1PF = lt_t_oirbbp1pf
. " EXIT_SAPMOIFA_040




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPMOIFA_040

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 OBSTAT FROM ROIFXICSTA INTO @DATA(ld_e_status).
 
 


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!