SAP FILA_ITEM_PROCESSING_PERFORM Function Module for NOTRANSL: Verarbeitung eines Geschäftsvorfalles zu einer Vertragsposition









FILA_ITEM_PROCESSING_PERFORM is a standard fila item processing perform 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: Verarbeitung eines Geschäftsvorfalles zu einer Vertragsposition 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 item processing perform FM, simply by entering the name FILA_ITEM_PROCESSING_PERFORM into the relevant SAP transaction such as SE37 or SE38.

Function Group: FILADM
Program Name: SAPLFILADM
Main Program: SAPLFILADM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FILA_ITEM_PROCESSING_PERFORM 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_ITEM_PROCESSING_PERFORM'"NOTRANSL: Verarbeitung eines Geschäftsvorfalles zu einer Vertragsposition
EXPORTING
* IS_ITEMS = "LAE: Contract Items
* IS_ITEMDATA = "Object Data
* ID_COMPONENT = 'FILA' "Application Component
* IF_TESTRUN = "
* IF_DIALOGCALL = "Screens, display user entry
* IF_TRACE = "
* IF_COMMIT = 'X' "Execute Commit Work

IMPORTING
ETY_ITEM = "
ET_RETURN = "
ES_ITEMS = "Status of Processing

EXCEPTIONS
ERROR_OCCURRED = 1
.



IMPORTING Parameters details for FILA_ITEM_PROCESSING_PERFORM

IS_ITEMS - LAE: Contract Items

Data type: LAE_CRM_ITEMS
Optional: Yes
Call by Reference: Yes

IS_ITEMDATA - Object Data

Data type: FILA_GF_ITEMDATA
Optional: Yes
Call by Reference: Yes

ID_COMPONENT - Application Component

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

IF_TESTRUN -

Data type: SY-DATAR
Optional: Yes
Call by Reference: Yes

IF_DIALOGCALL - Screens, display user entry

Data type: SY-DATAR
Optional: Yes
Call by Reference: Yes

IF_TRACE -

Data type: SY-DATAR
Optional: Yes
Call by Reference: Yes

IF_COMMIT - Execute Commit Work

Data type: SY-DATAR
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FILA_ITEM_PROCESSING_PERFORM

ETY_ITEM -

Data type: FILAE_CT_ITEM
Optional: No
Call by Reference: Yes

ET_RETURN -

Data type: FILAE_TB_RETURN
Optional: No
Call by Reference: Yes

ES_ITEMS - Status of Processing

Data type: LAE_CRM_ITEMS
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR_OCCURRED - Error Occurred During Processing

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FILA_ITEM_PROCESSING_PERFORM 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_ety_item  TYPE FILAE_CT_ITEM, "   
lv_is_items  TYPE LAE_CRM_ITEMS, "   
lv_error_occurred  TYPE LAE_CRM_ITEMS, "   
lv_et_return  TYPE FILAE_TB_RETURN, "   
lv_is_itemdata  TYPE FILA_GF_ITEMDATA, "   
lv_es_items  TYPE LAE_CRM_ITEMS, "   
lv_id_component  TYPE FILA_COMPONENT, "   'FILA'
lv_if_testrun  TYPE SY-DATAR, "   
lv_if_dialogcall  TYPE SY-DATAR, "   
lv_if_trace  TYPE SY-DATAR, "   
lv_if_commit  TYPE SY-DATAR. "   'X'

  CALL FUNCTION 'FILA_ITEM_PROCESSING_PERFORM'  "NOTRANSL: Verarbeitung eines Geschäftsvorfalles zu einer Vertragsposition
    EXPORTING
         IS_ITEMS = lv_is_items
         IS_ITEMDATA = lv_is_itemdata
         ID_COMPONENT = lv_id_component
         IF_TESTRUN = lv_if_testrun
         IF_DIALOGCALL = lv_if_dialogcall
         IF_TRACE = lv_if_trace
         IF_COMMIT = lv_if_commit
    IMPORTING
         ETY_ITEM = lv_ety_item
         ET_RETURN = lv_et_return
         ES_ITEMS = lv_es_items
    EXCEPTIONS
        ERROR_OCCURRED = 1
. " FILA_ITEM_PROCESSING_PERFORM




ABAP code using 7.40 inline data declarations to call FM FILA_ITEM_PROCESSING_PERFORM

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_testrun).
 
"SELECT single DATAR FROM SY INTO @DATA(ld_if_dialogcall).
 
"SELECT single DATAR FROM SY INTO @DATA(ld_if_trace).
 
"SELECT single DATAR FROM SY INTO @DATA(ld_if_commit).
DATA(ld_if_commit) = 'X'.
 


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!