Why do we need to run the provisional flows generation?

5 minute read time.

You may have experienced some of the fixed asset records don’t show up in certain queries and reports. For example, list of fixed assets inquiry in Fixed assets, Inquiries, Germany & Austria (FASLISTDEP), when running this inquiry by selecting the company, depreciation plan, period type, start and end date nothing shows up. Or the FAS1PAGE report in Reports, Reports, prints a blank page.

When we face with this situation and we know that the report or query parameters entered are correct we can conclude that the issue is not a user error but a system issue.

Main cause of the issue is that FXDLIFL flow table is not populated for those assets.

Thanks to the Provisional flows generation function in Fixed assets, Processing, Depreciations (FASFLXM) we can launch this function for one or several contexts of a company, in order to load the FXDLIFL flow table whose records are used to produce the preparatory reports for the 2054 (FAS2054) and 2055 (FAS2055) fiscal statements ( French fiscal forms), the control reports such as the Fixed assets by account report (FLUIMMOCPT) or the Depreciation flows by account report (FLUAMTCPT), and potential other flow reports specifically developed.

Note, no flow is generated for the cancelled assets or for the in template holding type.

Now we look at how or when does the records get created in flow tables:

        1. To activate the flow management, in depreciation context select the Funds account check box for each plan. An initial flow for the fiscal year is generated for each asset and each plan. As these flows contain initial information, their statuses are set to Not generated (FLGSTATXS = 1)

        2. When generating an asset if the CALCAUTVAL – Automatic calculation on validation parameter in AAS, CLC group is set to ‘Yes’, it specifies a calculation of the FY depreciations and a flow generation.

        3. During the unit calculation of an asset.

        4. When closing a period and fiscal year flows are created or updated for the closed period or fiscal year with the Definitive status, which indicates that these flows can no longer be modified. When closing a FY, the flows are also initialized for the next FY for each plan concerned and for each asset of the company. Their status is set to not generated.

        5. During the generation process of the provisional flows. This process is used to generate the flows of all assets of the selected companies after a new fiscal year opens. This processing can be leveled over the whole first period; it is particularly useful as the processing time of the first closing is no longer jeopardized. Flows are created or updated with the provisional status (FLGSTATXS = 2), which means that the recorded information is relevant but not definitive as the closing is not completed yet.

This processing can be restarted at any time. In order to optimize processing times, it only applies to the new assets and to those that were subjected to a business action impacting flows (since last generation).

Next, lets look at the indicator of flow to generate: FLGCNXFLX

This indicator is included in financial assets table FXDASSETS. This is a 11-character alphanumerical field; the character of n rank specifies whether flow of context n is to be generated:

  • Value “1”: Flows are not to be generated
  • Value “2”: Flows are to be generated
  • Value “3”: Flows are not managed on context

There elements are included in local menu 3189.

When rank n of FLGCNXFLX is set to 1 – Generated flows:

  • For the provisional flow generation of context n.
  • For the periodic closing of context n.

When rank n of FLGCNXFLX is set to 2 – Flows to generate:

  • If context n is calculated (for any business action, when as asset is recalculated, its flows must be updated).
  • If the account posting of the asset has been changed.
  • If the asset has been subject to a financial organization transfer.
  • If the context has been subject to a FY closing.
  • If a flow management has been added.
  • If a context is redefined or if the management of its plans flows has been modified.

When rank n of FLGCNXFLX is set to 3 – Not managed flows:

  • If a context does not manage flows any longer.

Note, when a business action requires a new calculation, the indicator is not modified by the action, but it will be by the calculation program. If the asset is not recalculated, flows still correspond to depreciations. Flow generation is only required when the asset has been recalculated.

1. Create an asset and check the FXDLIFL and the FXDASSETS table to see what the status of the indicator is.

  • There will be 13 records in FXDLIFL table, for the fiscal year for each asset and each plan with provisional status and 1 entry with initial information with FLGSTATXS set to 1.
  • In FXDASSETS table FLGCNXFLX flag will be set to 13333333333 (flows are not to be generated).

  - Suppose if the depreciation context is updated, you need to rerun the depreciation calculation to rebuild the table, since the initial entry will be erased.

  - In FXDASSETS table the FLGCNXCLC = 2 (context to calculate is set to yes).

  - Run the depreciation calculation (FASCALC) to set the FLGCNXFLX = 23333333333 (Flows are to be generated).

2. Finally, run the Provisional flows generation to populate the FXDIFL table.

  • Uncheck the simulation check box after running it in simulation mode to make sure there are no errors
  • Select the company, company sites and the depreciation context will be selected automatically.
  • Force flow generation check box, this flag must only be activated to force the full generation of the flows. This forcing is used to ignore the optimization mechanism used for an asset, to not generate the flows of an asset as soon as no modification impacting the flows has been recorded for this asset for the last generation.

 

    - FXDLIFL table is populated and the FLGCNXFLX value is set to 13333333333 (flows are not to be generated).

   - Check the List of FA inquiry.

I hope this article was helpful and now you know why or when we need to run this process.