Always false
This activity code is an "Always false" activity code (always inactive).
Functions concerned
The following functions are impacted by the activity code :
Development > Script dictionary > Scripts > Eclipse editor
Usage > Users > User change
Financials > Reporting > Offset extraction > Offset extraction
Financials > Interfaces > Balance export Portugal statement
Manufacturing > Detailed scheduling > Scheduling (inquiry)
Manufacturing > Detailed scheduling > Detailed scheduling
Manufacturing > Detailed scheduling > Optimization
Common data > Manufacturing tables > Teams
Setup > Users > BI user profile
Financials > Reporting > Offset extraction > Extraction result
Declarations > Audit > Portugal > Setup > Connection parameters
Declarations > Audit > Portugal > Setup > Key management
Human Resources administration > Payroll > Legal declarations > Legal obligations setup
Setup > Usage > Sage Sales Tax connection
Usage > Trade connectors > ENERGY > ENERGY setup
Setup > Stock > Requirements parameters
Common data > Manufacturing tables > Teams
Usage > Trade connectors > APS Forecast > DYNASYS > SCM n.skep setup
Usage > Calculation engine
Usage > Trade connectors > ENERGY > ENERGY interface launch
Manufacturing > Detailed scheduling > Unlock selected WOs
Usage > Trade connectors > APS Forecast > DYNASYS > SCM n.skep interface start
Linked activity codes
The following technical activity codes are linked to the code FAL.These codes are never entered in folder management, because their value is calculated.
GLMID (Global leave managment).
Remarks
The activity codes FAL and TRU are the standard activity codes that are used for marking the elements in the dictionary that must always be active or always inactive for technical reasons.
To date, these activity codes are essentially of interest within the framework of bespoke developments, when they are used in dependency formulas.
The automated documentation function available in version 150 benefits from the FAL activity code. When this code is present in a documentation paragraph, the paragraph involved is never included in the documentation. This makes it possible to prevent paragraphs that are automatically generated from the dictionary, but are of no use in a specific case, from being taken into account in the final documentation.