SAP EXIT_SAPLLOI1_001 Function Module for User exit for planned orders
EXIT_SAPLLOI1_001 is a standard exit saplloi1 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 User exit for planned orders 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 saplloi1 001 FM, simply by entering the name EXIT_SAPLLOI1_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XLOI
Program Name: SAPLXLOI
Main Program: SAPLXLOI
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLLOI1_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_SAPLLOI1_001'"User exit for planned orders.
EXPORTING
MESSAGE_TYPE = "
SEGMENT_NAME = "
* F_PLAF = "
* F_PLOP = "
* F_KBED = "
* F_PLUV = "
* F_KBEU = "
* F_RESB = "
* IS_PLAF = "Planned Order
IMPORTING
IDOC_CIMTYPE = "
DELETION_INDICATOR = "Checkbox field
CHANGING
* CAPREQ_ONLY_FOR_DET_PLANNING = 'X' "Checkbox
TABLES
IDOC_DATA = "
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.CLOI_DOWNLOAD_TRIGGER_MDAT Master data: trigger different IDoc creating reports
CLOI_DOWNLOAD_TRIGGER_TRANS Transactional data: trigger different IDoc creating reports
CLOI_KBED_READ Read KBED for planned orders
CLOI_LOIPGR_READ Select product groups and send their IDocs
CLOI_MASTERIDOC_CREATE_LOIBOM Create BOM IDOCs
CLOI_MASTERIDOC_CREATE_LOICAL Create masteridoc for messagetype LOICAL
CLOI_MASTERIDOC_CREATE_LOINUM Create masteridoc for messagetype LOINUM
CLOI_MASTERIDOC_CREATE_LOIPLO Create master IDOC for message type LOIPLO
CLOI_MASTERIDOC_CREATE_LOIPRO Create master IDOC for message type LOIPRO
CLOI_MASTERIDOC_CREATE_LOIRNH Create master IDoc for message type LOIRNH
CLOI_MASTERIDOC_CREATE_LOIROU Create master IDOC for message type LOIROU
CLOI_MASTERIDOC_CREATE_LOIRSH Create master IDOC for message type LOIRSH
CLOI_MASTERIDOC_CREATE_LOISTD Create master IDOC for message type LOISTD
CLOI_MASTERIDOC_CREATE_LOIWCS Create master IDOC for message type LOIWCS
CLOI_MASTERIDOC_CREATE_MATMAS Create IDoc for material
CLOI_MATERIALS_COPRODUCTS_ADD Kopfmaterial an gegebe Material/Werksliste anfügen
CLOI_MATERIAL_READ Read Material for given Ranges-Tables
CLOI_MATERIAL_SEND Vorbereitung zum Versenden von MasterIDoc MATMAS
CLOI_PARALLEL_SEL_BOMS Parallelisierung von RCCLBOM zur Selektion und Versendung von Stücklisten
CLOI_PLANNED_ORDER_READ Read Planned order for Select-options
CLOI_QUEUE_CHECK Check IDoc relevant queues
CLOI_RESB_READ Read RESB for planned orders
CLOI_ROUTING_FOR_ARBID_READ Select routings for given arbid(s)
CLOI_ROUTING_READ Read routings for given ranges tables
CLOI_ROUTING_SEND select routings to a material+werks key, create IDocs and send them
CLOI_STEUS_GET get control keys for the log. system
CLOI_TRANSMATRIX_SEND Preparation for sending MasterIDoc LOITMX
CLOI_WC_CAPACITY_READ Retrieve the available capacity of a work center
CLOI_WORKCENTER_SEND select work center to a ARBID key, create IDocs and send them
IMPORTING Parameters details for EXIT_SAPLLOI1_001
MESSAGE_TYPE -
Data type: EDMSG-MSGTYPOptional: No
Call by Reference: No ( called with pass by value option)
SEGMENT_NAME -
Data type: EDIDD-SEGNAMOptional: No
Call by Reference: No ( called with pass by value option)
F_PLAF -
Data type: E3PLAFLOptional: Yes
Call by Reference: No ( called with pass by value option)
F_PLOP -
Data type: E3PLOPLOptional: Yes
Call by Reference: No ( called with pass by value option)
F_KBED -
Data type: E3KBEDLOptional: Yes
Call by Reference: No ( called with pass by value option)
F_PLUV -
Data type: E3PLUVLOptional: Yes
Call by Reference: No ( called with pass by value option)
F_KBEU -
Data type: E3KBEULOptional: Yes
Call by Reference: No ( called with pass by value option)
F_RESB -
Data type: E3RESBLOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_PLAF - Planned Order
Data type: PLAFOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EXIT_SAPLLOI1_001
IDOC_CIMTYPE -
Data type: EDIDC-CIMTYPOptional: No
Call by Reference: No ( called with pass by value option)
DELETION_INDICATOR - Checkbox field
Data type: CLOI_PARA-XFLAGOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for EXIT_SAPLLOI1_001
CAPREQ_ONLY_FOR_DET_PLANNING - Checkbox
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPLLOI1_001
IDOC_DATA -
Data type: EDIDDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLLOI1_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: | ||||
| lt_idoc_data | TYPE STANDARD TABLE OF EDIDD, " | |||
| lv_idoc_cimtype | TYPE EDIDC-CIMTYP, " | |||
| lv_message_type | TYPE EDMSG-MSGTYP, " | |||
| lv_capreq_only_for_det_planning | TYPE XFELD, " 'X' | |||
| lv_segment_name | TYPE EDIDD-SEGNAM, " | |||
| lv_deletion_indicator | TYPE CLOI_PARA-XFLAG, " | |||
| lv_f_plaf | TYPE E3PLAFL, " | |||
| lv_f_plop | TYPE E3PLOPL, " | |||
| lv_f_kbed | TYPE E3KBEDL, " | |||
| lv_f_pluv | TYPE E3PLUVL, " | |||
| lv_f_kbeu | TYPE E3KBEUL, " | |||
| lv_f_resb | TYPE E3RESBL, " | |||
| lv_is_plaf | TYPE PLAF. " |
|   CALL FUNCTION 'EXIT_SAPLLOI1_001' "User exit for planned orders |
| EXPORTING | ||
| MESSAGE_TYPE | = lv_message_type | |
| SEGMENT_NAME | = lv_segment_name | |
| F_PLAF | = lv_f_plaf | |
| F_PLOP | = lv_f_plop | |
| F_KBED | = lv_f_kbed | |
| F_PLUV | = lv_f_pluv | |
| F_KBEU | = lv_f_kbeu | |
| F_RESB | = lv_f_resb | |
| IS_PLAF | = lv_is_plaf | |
| IMPORTING | ||
| IDOC_CIMTYPE | = lv_idoc_cimtype | |
| DELETION_INDICATOR | = lv_deletion_indicator | |
| CHANGING | ||
| CAPREQ_ONLY_FOR_DET_PLANNING | = lv_capreq_only_for_det_planning | |
| TABLES | ||
| IDOC_DATA | = lt_idoc_data | |
| . " EXIT_SAPLLOI1_001 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLLOI1_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.| "SELECT single CIMTYP FROM EDIDC INTO @DATA(ld_idoc_cimtype). | ||||
| "SELECT single MSGTYP FROM EDMSG INTO @DATA(ld_message_type). | ||||
| DATA(ld_capreq_only_for_det_planning) | = 'X'. | |||
| "SELECT single SEGNAM FROM EDIDD INTO @DATA(ld_segment_name). | ||||
| "SELECT single XFLAG FROM CLOI_PARA INTO @DATA(ld_deletion_indicator). | ||||
Search for further information about these or an SAP related objects