Movement integration
This function is one phase of the movement integration mechanisms, such integration relating both to taking into account modifications and/or movements, and to triggering the corresponding actions, transfers or issues, for instance.
The integration of the movements is carried out through the two following stages:
1/ Import of movements
This import consists in loading the home table (FXDMVT / FXDMVTD) from a file.
It is carried out by the standardImportfunction, through an import template (standard FXDSTD template or any other customized template). The import stage is optional to the extent that loading the home table can be carried out by any other source, particularly SQL.
The movements taken into account as well as the fields that can be transacted are indicated below.
Assets
Movements | Fields that can be used |
Issue / issue cancellation | Screen fields: FASISSP of Mass issue function (FASISSM) |
Transfer / transfer cancellation | Screen fields: FASTRFP of Mass transfer function (FASTRFM) |
Accounting allocation modification | Screen fields: FASTRFC of the function Change the accounting allocation (FASTRFCM) |
Modifications | They are specified in the 637 miscellaneous table. |
Split | of the screens: FASSPL1 of function Split an asset accessible from the Asset management function. |
Expenses
Movements | Fields that can be used |
Modifications | They are specified in the 636 miscellaneous table. |
Physical elements
Movements | Fields that can be used |
Issue / issue cancellation | Screen fields: PHYISSP of Mass issue function (PHYISSM) |
Transfer | Screen fields: PHYTRFM of Mass geographical transfer function (PHYTRFM) |
Modifications | They are specified in the 638 miscellaneous table. |
The Exhaustive list of the fields that can be used in the movements is provided by an attached document. These fields are classified by object type and movement type.
2/ The integration of the movements included in the home table.
The integration is associated with a triggering of business actions corresponding to the movement type.
This processing can be carried out in interactive mode using the Movement integration function, or using a batch processing executed by recurring task.
When the integration of some movements fails, it is necessary to go to the function: Movements to integrate indicated in the following stage, so as to modify the incorrect values.
Optional stage: inquiring and, if necessary, modifying and/or deleting information included in the home table.
This stage is carried out through function Movements to integrate.
It is only mandatory where an object is rejected in the course of the movement integration stage, because of an incorrect information. It can be used to modify the incorrect variable(s) before processing again the rejected movement.
To trigger several movements by reference, it is necessary to save as many requests, i.e. as many lines in the import file as requested movements. For instance, to transfer the geographic location and the cost sector of a fixed asset, it is necessary to save 2 lines in the import file for said fixed asset.
This function corresponds to the second stage of the movement integration mechanism.
It makes it possible to process all the movements whose status has the following value: To be processed or Rejected. The integration is carried out by triggering, if necessary, the different actions linked to the movement.
Some movements can be subject to rejection during the processing. The cause for the rejection can be linked to:
- An incorrect information. It is necessary, in this case, to either proceed to a new import after modifying the incorrect values, or modify the values directly concerned at the level of the home table through the function Movements to integrate, then to re-launch the integration.
- One or several setup requirements. In this case, it is necessary to remove the lock by intervening on the setup, before re-launching the integration processing.
Prerequisites
Refer to documentation Implementation
Screen management
Entry screen
Presentation
Mainly, this screen is used to:
- specify if the processing is carried out as a Simulation and, when it is actually carried out, whether or not the movements processed have to be archived. When they are archived, they remain visible - they cannot be modified - at function level Movements to integrate, otherwise they are deleted.
- select movements to process.
Close
Fields
The following fields are present on this tab :
Options
|
This box is checked by default. It specifies that the processing is carried out in simulation mode. In this case, the controls and the process are carried out but no modification of the database is recorded. |
|
When this indicator is selected, the movements processed without rejection will be kept and archived. They can be consulted through function Movements to integrate. Otherwise, these movements will be deleted. |
|
The log is more or less detailed according to this indicator. |
Object type
|
By default, the processing takes into account all the movements linked to all the types of objects. |
|
|
|
|
|
|
Criteria
|
By default, the processing takes into account all the movements linked to the companies. |
|
This field can only be accessed when the All companies flag is deactivated. |
|
By default, the processing takes into account all the movements linked to the company or companies as selected. |
|
This field can only be accessed if the check box "All sites" is not selected. |
|
By default, the processing takes into account all movement types. |
|
|
|
|
|
|
|
|
|
|
Range
|
These fields are used to indicate a record reference or the range of record references to process. The entry of ranges is only significant if one object type only is selected. |
Close