Use this form set level rule to copy the data from one GVM variable to another GVM variable.
You specify the two variables using INI options, for example:
< Trigger2WIP >
Company = Key1
LOB = Key2
The contents of the Company
variable is copied to Key1
.
The contents of the LOB
variable is copied to Key2
.
Parameter |
Description |
ControlGroup |
Specify the name of the control group in the INI file that defines the variables. |
Note | Although this rule was created for use with GenData WIP Transaction Processing, you can also use it to map a group of GVM variables from one name to another name. |
For GenData WIP Transaction Processing, this rule copies GVM data from the WIP.DBF file into GVM variables for GenData execution. You define the GVM variables in the Trigger2WIP control group.
Assume the FSISYS.INI or FSIUSER.INI file has these options:
< Trigger2WIP >
Company = Key1
LOB = Key2
Here is an example:
;GVM2GVM;;Trigger2WIP;
This example copies the contents of the Key1 and Key2 GVM variables found in the WIP.DBF file into the GenData Company and LOB GVM variables.
© Copyright 2014, Oracle and/or its affiliates. All rights reserved. Legal notices.