MergeWIP

Use this job level rule to initialize GenData WIP Transaction Processing. This rule creates a transaction memory list to which it adds transactions from the WIP file that have status codes which match those in the rule’s parameters.

The status codes identified by this rule do not have to be identified by the WIPTransactions rule. You can include status codes for transactions that you want to delete from the WIP file. Transactions with status codes not including in this rule’s parameters remain in the WIP file when processing finishes.

These other rules are also used when you run WIP Transaction Processing:

• WIPTransactions – This rule replaces the RULStandardTransactionProc or NoGenTrnTransactionProc rules in the AFGJOB.JDT file. This rule starts GenData WIP Transaction Processing at the form set level. It also identifies the status codes for the transactions in the WIP file that are processed. The status codes can be a subset or all of the status codes identified on the MergeWIP rule or none.
• GVM2GVM - This rule copies GenData execution data from the Trigger2WIP INI control group.
• WIPImageProc – This rule replaces the RULStandardImageProc or StandardImageProc rule.
• WIPFieldProc – This rule replaces the RULStandardFieldProc or StandardFieldProc rule.

Using these rules in a simplified AFGJOB.JDT file and with appropriate INI files, GenData WIP Transaction Processing adds the transactions from a WIP file to a transaction memory list. It then processes the transactions from the memory list, appending the data from the WIP file to the MRL recipient batch, NewTrn, NA, and POL files. If these files do no exist, it creates them. Each transaction in the memory list is deleted from the WIP file after it is processed.

Syntax

;MergeWIP;;StatusCode1,StatusCode2,...;

WIP selection performance during batch processing

The system automatically limits the result sets queried from DBMS systems by the MergeWIP rule to the rule's parameters for the STATUSCODEs to significantly improve query speeds when this rule is run against large WIP index tables.

When the WIP index table is in a DBMS, the appropriate WHERE clause for the STATUSCODE is added to the query automatically. A separate query for each STATUSCODE provided to the MergeWIP rule is used to retrieve the WIP list.

To improve performance on very large WIP tables, add an index on the DBMS WIP index table on the STATUSCODE column to avoid full table scans. An index on the WIP index table on the CURRUSER and STATUSCODE columns can also improve the performance of other queries to the WIP index table when the query to build a WIP list for a specific user is performed.

Using dates to select transactions

The MergeWIP rule can check a date field in the WIP index to determine whether to insert the WIP record into the batch. By default the field name is ScheduleDate. You can use this INI option to change the name of the field that is used:

< MergeWIP >

ScheduleDateFieldName = ScheduleDate

If the data in the field is eight bytes, the system assumes the date is in YYYYMMDDD format. If the data in the field is 14 bytes, the system assumes a YYYYMMDDhhmmss format. You can change the format the MergeWIP rule expects for the date using this INI option:

< MergeWIP >

ScheduleDateFieldFormat = D4%1

You can combine date and time formats into one string separated by percent signs (%). This table shows the date formats:

This table shows the time formats:

Returning a warning message

Instead of returning an error if it comes across an empty WIP list when merging WIP, the system can issue a warning. To have the system issue a warning instead of an error, set the WIPWarnOnEmpty option to Yes, as shown here:

< RunMode >

WIPWarnOnEmpty = Yes

Changing the WIP Status

You can tell the system not to delete WIP records and files during the MergeWIP/WIPTransactions process if an error occurs, but instead change the WIP status to something you define.

This way, if an error occurs during batch processing, the WIP will still exist in its normal place. But since its status has changed, the system will not include it in the next batch run. You can then examine the transaction to determine what caused the error.

Use the following INI option to set up the transaction error code you want to use:

< Status_CD >

TransErrCode = E

Example

Here is an example:

;MergeWIP;; Approved, Accepted, Rejected;

This example adds to the memory list the transactions in the WIP file which have these status codes: Approved, Accepted, and Rejected. Those codes must be specified in the Status_CD control group.

See also

• GVM2GVM
• WIPFieldProc
• WIPImageProc
• WIPTransactions
• GenData WIP Transaction Processing

© Copyright 2014, Oracle and/or its affiliates. All rights reserved. Legal notices.

Open table of contents

Open table of contents