Copy Transactions
This utility allows the transfer from one folder to another of the definable transactions or screens in any of the software modules. Warning, only the transfer of the transaction is assured by this utility : It is necessary to revalidate the transactions in the target folder so that they can be used.
This utility can also transfer automatic journals.
The following transfers are authorized by this utility :
Module | Transferable elements |
Purchasing | RFQ, purchase request, order, contract order, invoice transactions |
Stocks | Stock and stock count transactions |
Sales | Quote, order, open order, delivery, return, invoice transactions |
Production | WO entry, production tracking, Enterprise planning, Production workbench, Grouping, Time tracking, Material tracking transactions, Production tracking transactions. |
Accounting | Entry screens and transactions Automatic journals |
AR and AP accounting | Entry transactions, item entry screens Automatic payment journals |
Prerequisites
Refer to documentation Implementation
Screen management
Entry screen
Presentation
In addition to the source and destination folders, entries with the detailed syntaxes in an annex document, for each type of document, the user specifies whether or not to carryout the transfer and if yes, the transfer can be contained within two transaction codes.
Validation of the box triggers the transfer of the transactions. A log file is displayed, giving the result of the transfer. Exiting the log file display allows the return to the initial screen to start a new transfer if required.
The path for the files to be copied can be relative or absolute. If it is relative, it is assumed to be part of the database directory of the current folder. If the # character is used in place of the server, the file is supposed to be located on the client workstation. Warning, there are opening restrictions for the files on the client workstation in Web mode.
Close
Fields
The following fields are present on this tab :
Block number 1
| Indicate the folder from which the record is going be copied. The possible syntaxes are described in the dedicated appendix. |
| Indicate the folder in which the record is going be copied. The possible syntaxes are described in the dedicated appendix. |
Grid Transactions
| This code defines the transaction type to be copied. |
| Enter the description of the relevant record. This long description is used as a title in screens and reports. |
| If the field is set to Yes, the transactions corresponding to the ranges given elsewhere are copied. |
| This field is used to give a start value to the codes to be processed. |
| This field is used to give a end value to the codes to be processed. |
Close
Action icon
Yes to all the rest
When faced with an entry grid with multiple choices and a Yes/No answer on each line, this function makes it possible to answer Yes to all the lines starting from the current line.
No to all the rest
When faced with an entry grid with multiple choices and a Yes/No answer on each line, this function makes it possible to answer No to all the lines starting from the current line.
Contents of the log file
In the transfer log file, a list of copied transactions is found with the associated messages :
- Module start_date start_time
------------------------------------------------------------
- transaction_type transaction_code
If a transferred transaction already exists in the target folder it is replaced without warning by the transaction from the source folder, however the log file includes a message for the replacement Existing record deleted.
Close
Batch task
This function can be run in batch mode. The standard task ACOPTRS is provided for that purpose.