SAP EXIT_SAPLOIDA_002 Function Module for manipulate the checks to be done on external detail screen
EXIT_SAPLOIDA_002 is a standard exit saploida 002 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for manipulate the checks to be done on external detail screen 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 saploida 002 FM, simply by entering the name EXIT_SAPLOIDA_002 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XOID
Program Name: SAPLXOID
Main Program: SAPLXOID
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPLOIDA_002 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_SAPLOIDA_002'"manipulate the checks to be done on external detail screen.
EXPORTING
DOCUMENT_LEVEL = "
DISPLAY_ONLY = "
CHANGING
VALIDATION_A = "
VALIDATION_B = "
VALIDATION_C = "
C_OIC_PIPE = "
C_OID_EX = "
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.OIDA_DNITEM_DETERMINE_GIDOC determine goods issue doc. no. of the delivery note item
OIDA_EXTDET_SET External Details control for LORD
OIDA_GET_EXTERNAL_DETAILS Get the external details
OIDA_GET_ORIGIN_DESTINATION Get the orgin and destination field values from plant and ship-to
OIDA_POITEM_DETERMINE_DNITEM determine delivery note item for a MM purchase order item (stock transfer)
OIDA_POPUP_EXTERNAL_DETAILS Function Module for External Details Dialog Box
OIDA_SET_EXTERNAL_DETAILS Fill external details
IMPORTING Parameters details for EXIT_SAPLOIDA_002
DOCUMENT_LEVEL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DISPLAY_ONLY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for EXIT_SAPLOIDA_002
VALIDATION_A -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
VALIDATION_B -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
VALIDATION_C -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
C_OIC_PIPE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
C_OID_EX -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLOIDA_002 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_validation_a | TYPE STRING, " | |||
lv_document_level | TYPE STRING, " | |||
lv_display_only | TYPE STRING, " | |||
lv_validation_b | TYPE STRING, " | |||
lv_validation_c | TYPE STRING, " | |||
lv_c_oic_pipe | TYPE STRING, " | |||
lv_c_oid_ex | TYPE STRING. " |
  CALL FUNCTION 'EXIT_SAPLOIDA_002' "manipulate the checks to be done on external detail screen |
EXPORTING | ||
DOCUMENT_LEVEL | = lv_document_level | |
DISPLAY_ONLY | = lv_display_only | |
CHANGING | ||
VALIDATION_A | = lv_validation_a | |
VALIDATION_B | = lv_validation_b | |
VALIDATION_C | = lv_validation_c | |
C_OIC_PIPE | = lv_c_oic_pipe | |
C_OID_EX | = lv_c_oid_ex | |
. " EXIT_SAPLOIDA_002 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLOIDA_002
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