Use this form set level rule to reset the pRPS structure after the GVM variables have been remapped.
Normally, after it loads the transaction, the system uses the options in the DocSetNames and Trn_Fields control groups to map GVM variables into the pRPS structure for GroupName1, GroupName2, and TransactionID. There are other fields, but GroupName1, GroupName2, and TransactionID are the primary ones.
When you use the MergeWIP rule, or an rule that imports the document field information normally mapped by the transaction rule, you may need to use the GVM2GVM rule to map the options in the Trigger2WIP control group back to GVM variables. Because the names of the Key1 and Group1 fields sometimes differ, this means the mapping occurs too late to also be mapped to the pRPS structure member. Therefore, you must use the ResetDocSetNames rule to reset the pRPS structure after the GVM variables have been remapped.
When you use the Ext2GVM rule to get the values for GroupName1, GroupName2, and GroupName3, especially in an XML implementation, be sure to include the MapBeforeReset parameter to re-map the RPS structures. With the parameter, this rule gets the GroupName values from global memory and converts them into the long values using the Key1Table andKey2Table control groups. This is typically used to convert company codes to company names and so on.
Here is an example:
;UseXMLExtract;;;
;Ext2GVM;;!/Forms/Key1 1,10,Company;
;Ext2GVM;;!/Forms/Key2 1,15,LOB;
;ResetDocSetNames;;ConvertBeforeReset;
To avoid using this rule, make sure the primary keys are defined the same way in these DFD files:
Here is an example:
< Base Form Set Rules >
;WIPTransactions;;BATCHPRINT;
;GVM2GVM;;Trigger2Wip;
;ResetDocSetNames;;;
© Copyright 2014, Oracle and/or its affiliates. All rights reserved. Legal notices.