SAP FILA_ADJUSTMENT_CHECK_NEW Function Module for NOTRANSL: Prüft, ob Änderung der Daten zulässig
FILA_ADJUSTMENT_CHECK_NEW is a standard fila adjustment check new 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: Prüft, ob Änderung der Daten zulässig 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 adjustment check new FM, simply by entering the name FILA_ADJUSTMENT_CHECK_NEW 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_ADJUSTMENT_CHECK_NEW 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_ADJUSTMENT_CHECK_NEW'"NOTRANSL: Prüft, ob Änderung der Daten zulässig.
EXPORTING
* ID_COMPONENT = 'FILA' "Application Component
ID_EVENTADJ = "
ID_REASON = "Reason for Change
* ID_BUKRS = "Company Code
* ID_OBJID = "Object Number
* ID_SUBID = "Subobject Number
IMPORTING
ES_ITEMCHAH = "Object Data: Value ID Change Header Information
ES_ITEMS = "LAE: Contract Items
EXCEPTIONS
ERROR_OCCURRED = 1
IMPORTING Parameters details for FILA_ADJUSTMENT_CHECK_NEW
ID_COMPONENT - Application Component
Data type: FILA_COMPONENTDefault: 'FILA'
Optional: Yes
Call by Reference: Yes
ID_EVENTADJ -
Data type: FILA_EVENTADJOptional: No
Call by Reference: Yes
ID_REASON - Reason for Change
Data type: FILA_ADJREASONOptional: No
Call by Reference: Yes
ID_BUKRS - Company Code
Data type: BUKRSOptional: Yes
Call by Reference: Yes
ID_OBJID - Object Number
Data type: FILA_OBJIDOptional: Yes
Call by Reference: Yes
ID_SUBID - Subobject Number
Data type: FILA_SUBIDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FILA_ADJUSTMENT_CHECK_NEW
ES_ITEMCHAH - Object Data: Value ID Change Header Information
Data type: FILA_GF_ITEMCHAHOptional: No
Call by Reference: No ( called with pass by value option)
ES_ITEMS - LAE: Contract Items
Data type: LAE_CRM_ITEMSOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_OCCURRED - Error during processing
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FILA_ADJUSTMENT_CHECK_NEW 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_es_itemchah | TYPE FILA_GF_ITEMCHAH, " | |||
lv_id_component | TYPE FILA_COMPONENT, " 'FILA' | |||
lv_error_occurred | TYPE FILA_COMPONENT, " | |||
lv_es_items | TYPE LAE_CRM_ITEMS, " | |||
lv_id_eventadj | TYPE FILA_EVENTADJ, " | |||
lv_id_reason | TYPE FILA_ADJREASON, " | |||
lv_id_bukrs | TYPE BUKRS, " | |||
lv_id_objid | TYPE FILA_OBJID, " | |||
lv_id_subid | TYPE FILA_SUBID. " |
  CALL FUNCTION 'FILA_ADJUSTMENT_CHECK_NEW' "NOTRANSL: Prüft, ob Änderung der Daten zulässig |
EXPORTING | ||
ID_COMPONENT | = lv_id_component | |
ID_EVENTADJ | = lv_id_eventadj | |
ID_REASON | = lv_id_reason | |
ID_BUKRS | = lv_id_bukrs | |
ID_OBJID | = lv_id_objid | |
ID_SUBID | = lv_id_subid | |
IMPORTING | ||
ES_ITEMCHAH | = lv_es_itemchah | |
ES_ITEMS | = lv_es_items | |
EXCEPTIONS | ||
ERROR_OCCURRED = 1 | ||
. " FILA_ADJUSTMENT_CHECK_NEW |
ABAP code using 7.40 inline data declarations to call FM FILA_ADJUSTMENT_CHECK_NEW
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'. | |||
Search for further information about these or an SAP related objects