Global Tax Solution Builder (gtsbuilder)
|
Module Name |
gtsbuilder.ksh |
|
Description |
GTS Builder Processing |
|
Functional Area |
Foundation |
|
Module Type |
Business Processing |
|
Module Technology |
Ksh |
|
Catalog ID |
TBD |
|
Runtime Parameters |
rmswrap_shell.ksh |
Design Overview
This batch program is used to process new, modified or expired rules of the global tax solution. The criteria to find these rules are based on the rule status and the field END_DATE.
Any rule with status UPDATED or APPROVED will be considered to be processed. Rules in status ACTIVE but with the field END_DATE filled with a date older than the tax builder execution date will also be picked for processing.
The processing logic in each of the above scenarios will be:
-
Processing rules in status UPDATED: rules can be updated exclusively in the field END_DATE. In this case the date informed in the rule will be updated in GTS_MERCHT_TAX and GTS_ITEM_TAX tables. Once these updates are done, the status of the rule will be changed back to ACTIVE.
-
Processing rules in status APPROVED: rules in this status are basically new rules included in the system. The GTS builder process will also identify rules with conditions at parent level regions or higher level of merchandise hierarchy (dept or class) and will store new records into GTS_MERCH_TAX and GTS_ITEM_TAX table for the lowest level of region (child regions) and merchandise hierarchy (subclass). Once these updates are done, the status of the rule will be changed to ACTIVE.
-
Processing rules in status ACTIVE: the process will look for the field END_DATE in active rules. If this field is filled with a date older than the execution date, the process will simply change the rule status to CLOSED. No updates will be performed at merchandise level tax tables nor item level tax tables.