Files vs. Registration Binding
In this register, the user can relate a Movement File to the basic records used in processing. These registers are automatically exported with the Movement File.
More than one Basic Record can be related per Movement File.
Procedures
Adding a Binding Movement File vs. Register:
| 1. | In Files Maintenance vs. Records window, click Add. |
The screen for addition is displayed.
| 2. | Fill in data according to the following instructions: |
| • | File Acronym |
Acronym of the main file.
Example:
SE2
| • | Description |
File name, automatically updated by the system.
| • | File Registered |
Acronym of the record auxiliary file.
Example:
SA2
| • | Description Registered |
Description of the record auxiliary file.
| • | Validation |
Through this field, you can specify a validation to filter the records to be exported.
Its content may be an \"IF\" or an ExecBlock, and must return a logic variable (.T. or .F.).
Example:
IF E2_USUR == \"S\", ...
| • | Key |
Key that relates the main file to the record file. Entering the branch field in the key is not necessary.
Example:
E2_FORNECE+E2_LOJA
| • | Edit Branch |
When a file is exported, information about the source branch in sent records is saved.
If this field is set as S (Yes), code of the origin branch is changed to the code of the destination branch in the text file generated.
This feature must be used for exclusive files.
Example:
File SE2 generated by branch 01 has the content 01 saved in field \"E2_FILIAL.\" When exported to branch 02, the destination file will have the content 02 saved in field \"E2_FILIAL.\"
| • | Import Type |
This field indicates if the import/export is to be performed through the field MSIDENT or through the index key (SINDEX).
The MSIDENT field has a single key and is saved sequentially by Microsiga Protheus®, regardless of the file; thus, two records with the same number cannot exist.
Verification of existing record (if the record already exists, it overwrites the existing information; if it does not exist, a new record is generated).
When importing, the existence of the record is checked through fields MSFIL + MSIDENT.
| • | Key Number |
If the import is performed through the index key, you must enter the index number to be used.
| • | Key Description |
Displays the index key description only after saving the inclusion.
| • | Responsible Changing |
This field defines whether the responsible for the record must be changed or not.