SAP EXIT_SAPLLOI1_007 Function Module for User exit for work centers









EXIT_SAPLLOI1_007 is a standard exit saplloi1 007 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 work centers 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 007 FM, simply by entering the name EXIT_SAPLLOI1_007 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_007 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_007'"User exit for work centers
  EXPORTING
   MESSAGE_TYPE =  "
*  F_KAPA =  "
*  F_CRCO =  "
*  F_KAKOI =  "
   SEGMENT_NAME =  "
*  F_CRHD =  "
*  F_CRTX =  "
*  F_CRCA =  "
*  F_KAKO =  "
*  F_KARE =  "
*  F_KAZY =  "
*  F_KAPE =  "

 IMPORTING
   IDOC_CIMTYPE =  "

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_007

MESSAGE_TYPE -

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

F_KAPA -

Data type: E3KAPAL
Optional: Yes
Call by Reference: No ( called with pass by value option)

F_CRCO -

Data type: E3CRCOL
Optional: Yes
Call by Reference: No ( called with pass by value option)

F_KAKOI -

Data type: E3KAKOIL
Optional: Yes
Call by Reference: No ( called with pass by value option)

SEGMENT_NAME -

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

F_CRHD -

Data type: E3CRHDL
Optional: Yes
Call by Reference: No ( called with pass by value option)

F_CRTX -

Data type: E3CRTXL
Optional: Yes
Call by Reference: No ( called with pass by value option)

F_CRCA -

Data type: E3CRCAL
Optional: Yes
Call by Reference: No ( called with pass by value option)

F_KAKO -

Data type: E3KAKOL
Optional: Yes
Call by Reference: No ( called with pass by value option)

F_KARE -

Data type: E3KAREL
Optional: Yes
Call by Reference: No ( called with pass by value option)

F_KAZY -

Data type: E3KAZYL
Optional: Yes
Call by Reference: No ( called with pass by value option)

F_KAPE -

Data type: E3KAPEL
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for EXIT_SAPLLOI1_007

IDOC_CIMTYPE -

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

TABLES Parameters details for EXIT_SAPLLOI1_007

IDOC_DATA -

Data type: EDIDD
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for EXIT_SAPLLOI1_007 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_f_kapa  TYPE E3KAPAL, "   
lv_f_crco  TYPE E3CRCOL, "   
lv_f_kakoi  TYPE E3KAKOIL, "   
lv_segment_name  TYPE EDIDD-SEGNAM, "   
lv_f_crhd  TYPE E3CRHDL, "   
lv_f_crtx  TYPE E3CRTXL, "   
lv_f_crca  TYPE E3CRCAL, "   
lv_f_kako  TYPE E3KAKOL, "   
lv_f_kare  TYPE E3KAREL, "   
lv_f_kazy  TYPE E3KAZYL, "   
lv_f_kape  TYPE E3KAPEL. "   

  CALL FUNCTION 'EXIT_SAPLLOI1_007'  "User exit for work centers
    EXPORTING
         MESSAGE_TYPE = lv_message_type
         F_KAPA = lv_f_kapa
         F_CRCO = lv_f_crco
         F_KAKOI = lv_f_kakoi
         SEGMENT_NAME = lv_segment_name
         F_CRHD = lv_f_crhd
         F_CRTX = lv_f_crtx
         F_CRCA = lv_f_crca
         F_KAKO = lv_f_kako
         F_KARE = lv_f_kare
         F_KAZY = lv_f_kazy
         F_KAPE = lv_f_kape
    IMPORTING
         IDOC_CIMTYPE = lv_idoc_cimtype
    TABLES
         IDOC_DATA = lt_idoc_data
. " EXIT_SAPLLOI1_007




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLLOI1_007

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).
 
 
 
 
"SELECT single SEGNAM FROM EDIDD INTO @DATA(ld_segment_name).
 
 
 
 
 
 
 
 


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!