SAP FILA_ITEMS_PROCESS Function Module for NOTRANSL: Triggert Verarbeitung der zur Verarbeitung anstehenden Geschäfts









FILA_ITEMS_PROCESS is a standard fila items process SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Triggert Verarbeitung der zur Verarbeitung anstehenden Geschäfts 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 fila items process FM, simply by entering the name FILA_ITEMS_PROCESS into the relevant SAP transaction such as SE37 or SE38.

Function Group: FILA
Program Name: SAPLFILA
Main Program: SAPLFILA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function FILA_ITEMS_PROCESS 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 'FILA_ITEMS_PROCESS'"NOTRANSL: Triggert Verarbeitung der zur Verarbeitung anstehenden Geschäfts
EXPORTING
* ID_COMPONENT = 'FILA' "Application Component
* IF_TRACE = "
* ID_BUKRS = "Company Code
* ID_OBJID = "Object Number
* ID_SUBID = "Subobject Number
* ID_EVENT = "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
* ID_TMSTAMP = "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
* ID_STATUS = 1 "
* IF_TESTRUN = "
* IF_DIALOGCALL = "
.



IMPORTING Parameters details for FILA_ITEMS_PROCESS

ID_COMPONENT - Application Component

Data type: FILA_COMPONENT
Default: 'FILA'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IF_TRACE -

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

ID_BUKRS - Company Code

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

ID_OBJID - Object Number

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

ID_SUBID - Subobject Number

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

ID_EVENT - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)

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

ID_TMSTAMP - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)

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

ID_STATUS -

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

IF_TESTRUN -

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

IF_DIALOGCALL -

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

Copy and paste ABAP code example for FILA_ITEMS_PROCESS 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_id_component  TYPE FILA_COMPONENT, "   'FILA'
lv_if_trace  TYPE SY-DATAR, "   
lv_id_bukrs  TYPE BUKRS, "   
lv_id_objid  TYPE FILA_OBJID, "   
lv_id_subid  TYPE FILA_SUBID, "   
lv_id_event  TYPE FILA_EVENT, "   
lv_id_tmstamp  TYPE TIMESTAMP, "   
lv_id_status  TYPE FILA_STATUS, "   1
lv_if_testrun  TYPE SY-DATAR, "   
lv_if_dialogcall  TYPE SY-DATAR. "   

  CALL FUNCTION 'FILA_ITEMS_PROCESS'  "NOTRANSL: Triggert Verarbeitung der zur Verarbeitung anstehenden Geschäfts
    EXPORTING
         ID_COMPONENT = lv_id_component
         IF_TRACE = lv_if_trace
         ID_BUKRS = lv_id_bukrs
         ID_OBJID = lv_id_objid
         ID_SUBID = lv_id_subid
         ID_EVENT = lv_id_event
         ID_TMSTAMP = lv_id_tmstamp
         ID_STATUS = lv_id_status
         IF_TESTRUN = lv_if_testrun
         IF_DIALOGCALL = lv_if_dialogcall
. " FILA_ITEMS_PROCESS




ABAP code using 7.40 inline data declarations to call FM FILA_ITEMS_PROCESS

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.

DATA(ld_id_component) = 'FILA'.
 
"SELECT single DATAR FROM SY INTO @DATA(ld_if_trace).
 
 
 
 
 
 
DATA(ld_id_status) = 1.
 
"SELECT single DATAR FROM SY INTO @DATA(ld_if_testrun).
 
"SELECT single DATAR FROM SY INTO @DATA(ld_if_dialogcall).
 


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!