SAP EXIT_SAPLOIK7_130 Function Module for User exit LID determination
EXIT_SAPLOIK7_130 is a standard exit saploik7 130 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for User exit LID determination 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 saploik7 130 FM, simply by entering the name EXIT_SAPLOIK7_130 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XOIK
Program Name: SAPLXOIK
Main Program: SAPLXOIK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPLOIK7_130 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_SAPLOIK7_130'"User exit LID determination.
EXPORTING
I_ROIKLIDSCR = "Structure for LID control field maintenance
IMPORTING
O_ERROR = "
TABLES
* X_LIDTYPE_WA = "Workarea for LID-type Userexit
* X_ROIKLID_WA = "TAS LID Communication structure
* X_OIDMP_TAB = "Sales Document: Partner
* X_VBKD_TAB = "Sales Document: Business Data
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.OIK_LIDTYPE_GET Get Lidtype specific customizing settings
OIK_LID_DETERMINATION TAS Load ID Determination
OIK_LID_FUNCTIONS_GET TAS - get LID functions per function group
OIK_LID_OIKLIDR_CREATE_F4 TAS - get LID information (F4)
OIK_LID_REFERENCE_GET TAS - get information from reference table
OIK_MC_OIKL_T Matchcode-ID (OIKL-T) function for selecting LIDs from activ repository
OIK_MC_OIKU_A Matchcode-ID (OIKU-V) function for selecting Units of Maesure (volume)
OIK_MC_OIKU_B Matchcode-ID (OIKU-M) function for selecting Units of maesure (masses)
OIK_MC_VMVA_T Matchcode-ID (VMVA-T) - Selecting SD-DOCs from History Table (OIK01)
OIK_OIK01_ENTRY_CREATE TAS create entry in OIK01 as reference to parent document
OIK_READ_USERFIELDS TAS Read Userfields
OIK_RELEVANCE_DETERMINATION TAS Relevance determination Pickup
OIK_RELEVANCE_DETERMINATION_XX TAS Relevance determination Pickup (with static ranking)
OIK_RELEVANCE_DETERMINE_SHIPM TAS Relevance determination Shipment
OIK_RELEVANCE_DETERMINE_SHP_XX TAS Relevance determination Shipment (with static ranking)
OIK_SHIPMENT_SCHED_DATA_GET get scheduled shipment data
OIK_USERSCREEN_GET IS-OIL/TAS: get user-screen information
IMPORTING Parameters details for EXIT_SAPLOIK7_130
I_ROIKLIDSCR - Structure for LID control field maintenance
Data type: ROIKLIDSCROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EXIT_SAPLOIK7_130
O_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPLOIK7_130
X_LIDTYPE_WA - Workarea for LID-type Userexit
Data type: ROIKU130Optional: Yes
Call by Reference: Yes
X_ROIKLID_WA - TAS LID Communication structure
Data type: ROIKLIDWOptional: Yes
Call by Reference: Yes
X_OIDMP_TAB - Sales Document: Partner
Data type: VBPAOptional: Yes
Call by Reference: Yes
X_VBKD_TAB - Sales Document: Business Data
Data type: VBKDOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for EXIT_SAPLOIK7_130 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_o_error | TYPE STRING, " | |||
lv_i_roiklidscr | TYPE ROIKLIDSCR, " | |||
lt_x_lidtype_wa | TYPE STANDARD TABLE OF ROIKU130, " | |||
lt_x_roiklid_wa | TYPE STANDARD TABLE OF ROIKLIDW, " | |||
lt_x_oidmp_tab | TYPE STANDARD TABLE OF VBPA, " | |||
lt_x_vbkd_tab | TYPE STANDARD TABLE OF VBKD. " |
  CALL FUNCTION 'EXIT_SAPLOIK7_130' "User exit LID determination |
EXPORTING | ||
I_ROIKLIDSCR | = lv_i_roiklidscr | |
IMPORTING | ||
O_ERROR | = lv_o_error | |
TABLES | ||
X_LIDTYPE_WA | = lt_x_lidtype_wa | |
X_ROIKLID_WA | = lt_x_roiklid_wa | |
X_OIDMP_TAB | = lt_x_oidmp_tab | |
X_VBKD_TAB | = lt_x_vbkd_tab | |
. " EXIT_SAPLOIK7_130 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLOIK7_130
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