4 Item Maintenance

Mirror of Oracle documentation

Converted for search and offline reading. Authoritative source: Oracle. Diagrams and some complex tables are simplified — check the PDF when in doubt.

4

Item Maintenance

This chapter contains information about the batch processes that relate to item maintenance.

Program Summary

Table 4-1 Item Maintenance - Program Summary

Program	Description
gtsbuilder	Global Tax Solution Builder
item_loc_purge_job	Daily Purge of Item-Location Data
itemupchrgcleanup	Item Up-Charge Cleanup
itm_indctn_purge.ksh	Purge Item induction staging tables
sitmain.pc	Scheduled Item Maintenance
vatdlxpl.pc	Mass VAT Updates for Items/Locations

Daily Purge of Item-Location Data (item_loc_purge_job)

Module Name item_loc_purge_job Description Daily Purge of Item-Location Data Functional Area Administration Module Type Admin - Adhoc Module Technology Background Processing Catalog ID N/A Wrapper Script b8dwrap.ksh

Schedule

Oracle Retail Merchandising Batch Schedule

Design Overview

This background job is composed of two steps processing. It will have a threading assignment and a business logic processing.

When users ‘delete’ an item-location record in the Merchandising user interface, information is generally not immediately deleted at the database level; instead, data is marked as being in deleted status and also inserted into the DAILY_PURGE table.

Thread assignment program (ITEM_LOC_PURGE_THREAD) will filter eligible records from daily purge (DAILY_PURGE) table wherein all entities ready for purging are exclusively related to Item-Location (ITEM_LOC table) records. These records are chunked and Thread ID is

assigned for each. They will be stored temporarily in a staging table B8D_ITEM_LOC_PURGE_STG.

The Business logic program (ITEM_LOC_PURGE) will process all records from the staging table. Using bulk processing, this program will delete item-location data from item-location related and associated tables. Complex referential integrity relationships determine whether data can actually be deleted from the database. This program checks these complex rules. If the deletion request passes the rules, this job will continues to delete the data. If it is not able to delete the data, it writes a record to the DAILY_PURGE_ERROR_LOG table for further investigation. This program will continue to attempt to delete marked data until all references have been purged from the system and the deletion of the item-location data finally succeeds. It will free up and clean the staging table afterwards. There is a STOP ON NEXT feature in bulk processing (through a loop) where Administrators can stop this batch with a flip of this indicator.

Restart/Recovery

N/A

Key Tables Affected

Table 4-2

Table	Select	Insert	Update	Delete
RMS_BATCH_STATUS	Yes	No	No	No
B8D_PROCESS_CONFIG	Yes	No	No	No
JOB_AUDIT_LOGS	No	Yes	No	No
B8D_ITEM_LOC_PURGE_STG	Yes	No	No	No
DAILY_PURGE	Yes	No	No	Yes
DAILY_PURGE_ERROR_LOG	Yes	Yes	No	Yes
REPL_RESULTS	Yes	No	No	Yes
BUYER_WKSHT_MANUAL	Yes	No	No	Yes
SUB_ITEMS_DETAIL	Yes	No	No	Yes
SUB_ITEMS_HEAD	Yes	No	No	Yes
REPL_ATTR_UPDATE_EXCLUDE	Yes	No	No	Yes
MASTER_REPL_ATTR	Yes	No	No	Yes
REPL_DAY	Yes	No	No	Yes
REPL_ITEM_LOC	Yes	No	No	Yes
REPL_ITEM_LOC_UPDATES	Yes	Yes	No	Yes
REPL_ITEM_LOC_SUPP_DIST	Yes	No	No	Yes
COST_SUSP_SUP_DETAIL_LOC	Yes	No	No	Yes
FUTURE_COST	Yes	No	No	Yes
ITEM_LOC_MFQUEUE	Yes	No	No	Yes
ITEM_LOC	Yes	No	No	Yes
ITEM_LOC_SOH	Yes	No	No	Yes
ITEM_LOC_TRAITS	Yes	No	No	Yes
ITEM_LOC_CFA_EXT	Yes	No	No	Yes

Table 4-2 (Cont.)

Table	Select	Insert	Update	Delete
ITEM_SUPP_COUNTRY_BRACKET_COST	Yes	No	No	Yes
ITEM_SUPP_COUNTRY_LOC_CFA_EXT	Yes	No	No	Yes
ITEM_SUPP_COUNTRY_LOC	Yes	No	No	Yes

I/O Specification

N/A

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

Schedule

Oracle Retail Merchandising Batch Schedule

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.

Restart/Recovery

In case of failure, the GTS builder batch will continue picking new or updated rules to process. During activation if any rule fails an error will be stored and the rule will have it status modified to “worksheet” for further review.

Design Assumptions

N/A

Item Up-Charge Cleanup (itemupchrgcleanup)

Module Name	itemupchrgcleanup.ksh
Description	Item Up-Charge Cleanup
Functional Area	Foundation
Module Type	Admin (Ad Hoc)
Module Technology	ksh
Catalog ID
Wrapper Script	rmswrap.ksh

Schedule

Oracle Retail Merchandising Batch Schedule (Ad Hoc)

itemupchrgrecalc

Design Overview

The purpose of this standalone ad-hoc batch program is to remove Item Charges that exactly match Department Charges to reflect exception-based, item-level up charges. Running this batch will delete unnecessary records from ITEM_CHRG_HEAD and ITEM_CHRG_DETAIL , helping improve performance on processes referencing these tables.

Given the significant volume of the ITEM_CHRG_* tables, the batch runs multi-threaded by department. The optional job parameter specifies the number of threads; when it is omitted, the batch uses six threads.

Prior to deleting records, this batch also updates

ITEM_MASTER.TSF_ALLOC_UP_CHRG_SOURCE_TYPE to D for those items, since Dept Charge details exactly match Item Charge Details for that item.

This batch will be mainly used by customers who have applied the new Exception-Based ItemLevel Up-Charge Enhancement feature in MFCS 26.1.101, where the new attribute TSF_ALLOC_UP_CHRG_SOURCE_TYPE was introduced and initially defaulted to I (Item only) and several Item Charges defaulted from Dept Charges still exist.

Restart/Recovery

This batch can be restarted after an abort if the cause of the failure is expected not to recur. It will restart the sequence of operations starting after the last item that was committed.

I/O Specification

N/A

Design Assumptions

N/A

Mass VAT Updates for Items/Locations (vatdlxpl)

Module Name vatdlxpl.pc Description Mass VAT Updates for Items/Locations Functional Area Item Maintenance Module Type Business Processing Module Technology ProC Catalog ID RMS384 Runtime Parameters rmswrap_multi.ksh

Schedule

Oracle Retail Merchandising Batch Schedule

Design Overview

This batch program updates VAT information for each item associated with a given VAT region and VAT code.

Restart/Recovery

This batch program performs commits to the database for every commit max number of rows.

Design Assumptions

N/A

Purge Item Induction Staging Tables (itm_indctn_purge.ksh)

Module Name itm_indctn_purge.ksh Description Purge item induction staging tables Functional Area Foundation-Items Module Type Admin

Module Technology Shell Script Catalog ID RMS498 Runtime Parameters N/A

Design Overview

The purpose of this module is to remove old item records from the staging tables. Records that are candidates for deletion are:

• Processes that have successfully been processed or processed with warnings that have been uploaded to Merchandising or downloaded to S9T

• Processes that have status = ‘PE’, processed with errors and have no linked data

• Processes in error status where all other related records containing the process ID have been processed successfully

• Processes that have errors and are past the data retention days (system_options.proc_data_retention_days)

• All item records within a process where all related records for the item in the other staging tables are successfully uploaded to Merchandising. The process tracker record for that process should not be deleted if there are other item records that are not uploaded to Merchandising.

Scheduling Constraints

Table 4-3 Scheduling Constraints

Schedule Information	Description
Processing Cycle	Ad Hoc
Frequency	Daily
Scheduling Considerations	N/A
Pre-Processing	N/A
Post-Processing	N/A
Threading Scheme	N/A

Restart/Recovery

Restart ability is implied, because the records that are selected from the cursor are deleted before the commit.

Scheduled Item Maintenance (sitmain)

Module Name sitmainsqls.pls/sitmainsqlb.pls Description Scheduled Item Maintenance Functional Area Item Maintenance Module Type Business Processing Module Technology PLSQL

Catalog ID RMS357 Wrapper Script rmswrap_plsql.ksh

Schedule

Oracle Retail Merchandising Batch Schedule

Design Overview

Scheduled item maintenance is a method of performing mass changes on item/location information. Scheduled item maintenance uses item and location lists to make the process of changing lots of information very easy for end users.This program explodes the intersection of these items and location lists to make the scheduled changes at the specific item/location level.

Restart/Recovery

This program has inherent restart ability because records are deleted from the scheduled item detail table as they are processed. The logical unit of work is an item/location combination.

Design Assumptions

N/A

---

In this guide

• Guide: Batch Operations Guide
• Previous: 3 Foundation Data Maintenance
• Next: 5 Purchase Order

Related chapters

• 11 Replenishment — Batch Operations Guide · shares BUYER_WKSHT_MANUAL, REPL_RESULTS
• G Appendix: Tables List — Merchandising Cloud Services Data Conversion Implementation Guide · shares COST_SUSP_SUP_DETAIL_LOC, ITEM_CHRG_DETAIL, ITEM_CHRG_HEAD, ITEM_LOC_CFA_EXT
• 2 Administration Batch — Batch Operations Guide · shares DAILY_PURGE, DAILY_PURGE_ERROR_LOG, GTS_ITEM_TAX, GTS_MERCH_TAX
• 3 Custom Validation Rules — Merchandising Cloud Services Customization and Extension Guide · shares FUTURE_COST, ITEM_CHRG_DETAIL, ITEM_CHRG_HEAD, ITEM_LOC_CFA_EXT
• 2 Data Entities — Merchandising Cloud Services Data Conversion Implementation Guide · shares FUTURE_COST, ITEM_SUPP_COUNTRY_LOC
• 5 ReSTful Web Services — Inbound and Outbound Integration Guide · shares COST_SUSP_SUP_DETAIL_LOC, DAILY_PURGE, ITEM_LOC_CFA_EXT, ITEM_LOC_TRAITS