Transaction Copy Forward Control
To control which transaction codes can be copied forward into a new transaction for referencing, the Transaction Copy Forward Control page is provided. Entries added do not guarantee that a reference can be made between two transactions. The Transaction Allowable References page controls what transactions can reference others. Copy Forward Control connects a transaction sub action, defining which fields copy forward and which do not, with two transaction codes and a description.
The transaction sub actions used are controlled though security on the Access Control page. A specific action is determined when a user selects the Copy Forward action in a transaction menu. The Copy Forward window opens to display the various target transaction codes available for the source transaction. For more information, refer to the "Copy Forward from a Transaction" topic, located in the CGI Advantage Transactions User Guide.
The Transaction Copy Forward Control page supports configuration options to exclude components when using the Copy Forward action, include/exclude fields within a component, or infer target transaction fields from source transactions. One example would be to not copy an accounting template from one accounting line to another because the target accounting line will have very different chart of account values entered and the source accounting line template would interfere with that, requiring a user to clear the field.
Please be aware that if the Infer Codes option is selected on Transaction Control for the referencing transaction code and the copy forward creates a Partial, Final, or Inverse Reference Type, if the copy forward drops a chart of account, the inference logic infers the field right back to the target accounting line.
The fields on Transaction Copy Forward Control (DCFCTL) are as follows with the common ones omitted.
|
Field Name |
Field Description |
|
Sub Action |
The Sub Action directing the application in terms of what to copy forward along with any settings that should be automatically made on the target transaction. |
|
Source Transaction Type |
The referenced transaction type that will be used as the source to create a referencing transaction. |
|
Target Transaction Type |
The referencing transaction type that will be created as the target of the source transaction. |
|
Source Transaction Code |
The referenced transaction code that will be used as the source to create a referencing transaction. |
|
Target Transaction Code |
The referencing transaction code that will be created as the target of the source transaction. |
|
Description |
An optional description entered of up to 30 characters to provide end users with assistance in determining the proper Target Transaction Code. |
|
Active |
If it is set to Yes, the copy forward entry will be displayed while copy forwarding the source transaction. If set to No, the copy forward entry will not be displayed. |
Component MappingComponent Mapping
The component mapping section of the page is used to map the source and target transaction components.
|
Field Name |
Field Description |
|
Source Component |
A unique identifier for each event types requirement record. |
|
Include/Exclude |
Component level action that needs performed for creating the target transaction. If Exclude, the component will be excluded during copy forward. Most rules are Include to modify results only slightly. |
|
Target Component |
Components of the referencing transaction used as target. Note: New target component mapping is not supported. |
Include/ExcludeInclude/Exclude
The Edit Mapping action in the row level menu of Component Mapping opens a new page to include or exclude fields in a copy forward from the source transaction component.
|
Field Name |
Field Description |
|
Columns |
List of fields of the referenced transaction used as the source. There are certain field filtered out of this list that should not be used in the configuration of a copy forward variant. |
|
Include/Exclude |
Field level action that needs performed while creating the target transaction. |
Inference MappingInference Mapping
The Inference Mapping section is used to map fields of the target transaction to the source transaction. The framework fields are filtered from Target Component fields. If the field types do not match, during copy forward it will skip the field and issue a warning message during copy forward. Meaning, only date to date, amount to amount, yes/no to yes/no, and variable character to variable character (of an equal or greater size).
|
Field Name |
Field Description |
|
Target Component Fields |
Field on the target transaction that will be derived. This listing is also filtered so only functional fields that could apply to the copy forward are displayed. |
|
Source Component Fields |
Field on the source transaction that is used to derive the target component field. |
