Oracle® Retail Merchandising System Operations Guide, Volume 1 - Batch Overviews and Designs 16.0.024 E89599-02 |
|
Previous |
Next |
Item induction is a process for importing item related information into RMS from an external source. For many retailers, item creation is initiated in a system outside RMS. Some retailers receive item information from their vendors, others initiate items in a planning application, and still others use a product lifecycle management (PLM) application, or a product hub (such as,. a PIM application).
RMS offers a flexible method of importing items, which supports inducting items into RMS with a bare minimum of data and provides a working area for enrichment of those items prior to upload into the production tables in RMS. Item induction functionality allows users and systems to upload item data into a staging area or directly into RMS using any of the below modes
Batch
RIB
Manual upload
Data uploaded into the staging area though any of the above modes can be downloaded into a spreadsheet, enriched and re-uploaded into the staging area or into RMS. Maintainence of items that already existing in RMS can also be achieved by downloading the data into a spreadsheet which in turn offers mass maintenance, filtering, and sorting capabilities.
The processing of upload or download requests of item data through manual and batch options is linked to a template definition that specifies which tables and columns are to be made available to the user or system for data entry and update. Templates can be created based on user role, business line, item type, and so on. and provide the flexibility to define default values for one or more fields.
Overall management of data in the staging area is achieved through provision of a dedicated purge batch.
For more information on the RIB options for uploading items into the staging area, see the Oracle Retail Merchandising Foundation Cloud Service Operations Guide, Volume 2 - Message Publication and Subscription Design.
The following batch designs are included in this functional area:
loadods.ksh (Item Induction)
iindbatch.ksh (Upload Item Data)
ld_iindfiles.ksh (Upload Data From Templates)
Module Name | loadods.ksh |
Description | Spreadsheet Tables Upload |
Functional Area | Admin |
Module Type | Integration |
Module Technology | ksh |
Catalog ID | RMS473 |
Runtime Parameters | Database connection, Path of input File |
This batch program is used to upload data from template files to S9T_FOLDER table. The path of template files (ODS_SYSTEM_TEMPLATE_FOR_OUTPUT_FILES.ods and template_config.ods) are passed as input parameter to this batch.This program will be called from other shell script ld_iindfiles.ksh which does initial validations to check if template files exist and post processing of uploading data from S9T_FOLDER table to other spreadsheet tables.
The restart recovery is different from the conventional RMS batch. There are two points on the batch upload process where users can evaluate the successful load of the data.
SQL load - In this program control and data files are created dynamically. In case of any error while creation of data/control file a non-fatal code is returned by the program and a message will be written to the log file.
User Action: When such conditions exist, the user should check if template files passed are valid and in expected format.
Other Validation - At this point data from the file(s) are loaded into the staging table(s). PL/SQL function is used to get the next sequence for each file_id. In case of any error while getting next sequence value from sequence - s9t_folder_seq fatal code is returned by the program and a message will be written to the log and error file.
User Action: When this condition exists, the user needs to check for DB connection and state of sequence should be valid in DB.
Module Name | iindbatch.ksh |
Description | Upload Item Data |
Functional Area | Item Maintenance |
Module Type | Integration |
Module Technology | Ksh |
Catalog ID | RMS474 |
Runtime Parameters | Database connection,
Input File Name, Template Name, Destination (Optional Input Parameter) |
This batch program is used to Bulk upload xml file data from template files to S9T_FOLDER table (into content_xml column).
This batch will be responsible for validating the input parameters, below are the list of validations.
The Input file should exist.
The Input file's extension must be ".xml".
The template_name should be valid. Function S9T_PKG.CHECK_TEMPLATE is called for validation.
Destination (Optional Parameter) should be STG or RMS. If destination is not passed then default it to STG.
Once xml data is loaded into S9T_FOLDER table, the script will do post processing by calling below packages
ITEM_INDUCT_SQL.INIT_PROCESS - This initialize a row in svc_process_tracker for asynchronous processing.
RMS_ASYNC_PROCESS_SQL.ENQUEUE_ITEM_INDUCT - This function en-queues the record for processing.
Module Name | ld_iindfiles.ksh |
Description | Updload Data From Templates |
Functional Area | Item Maintenance |
Module Type | Integration |
Module Technology | ksh |
Catalog ID | RMS199 |
Runtime Parameters | Database connection, Input Directory |
This batch program is used to upload data from template files to S9T_FOLDER table calling another script loadods.ksh. Once data is loaded into S9T_FOLDER table it will do post processing, uploading data to other spreadsheet tables. This batch will be responsible for validating if input files (ODS_SYSTEM_TEMPLATE_FOR_OUTPUT_FILES.ods and template_config.ods) are present in input directory (passed as parameter).
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 | NA |
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 RMS 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 RMS. The process tracker record for that process should not be deleted if there are other item records that are not uploaded to RMS.
Restart ability is implied, because the records that are selected from the cursor are deleted before the commit.
Table 23-8 Key Tables Affected
Table | Select | Insert | Update | Delete |
---|---|---|---|---|
PROC_DATA_RETENTION_DAYS |
Yes |
No |
No |
No |
SYSTEM_OPTIONS |
Yes |
No |
No |
No |
SVC_PROCESS_TRACKER |
Yes |
No |
No |
Yes |
SVC_PROCESS_ITEMS |
No |
No |
No |
Yes |
SVC_ITEM_COST_DETAIL |
No |
No |
No |
Yes |
SVC_ITEM_COST_HEAD |
No |
No |
No |
Yes |
SVC_ITEM_COUNTRY |
No |
No |
No |
Yes |
SVC_ITEM_COUNTRY_L10N_EXT |
No |
No |
No |
Yes |
SVC_ITEM_MASTER |
No |
No |
No |
Yes |
SVC_ITEM_MASTER_TL |
No |
No |
No |
Yes |
SVC_ITEM_MASTER_CFA_EXT |
No |
No |
No |
Yes |
SVC_ITEM_SUPPLIER |
No |
No |
No |
Yes |
SVC_ITEM_SUPPLIER_TL |
No |
No |
No |
Yes |
SVC_ITEM_SUPPLIER_CFA_EXT |
No |
No |
No |
Yes |
SVC_ITEM_SUPP_COUNTRY |
No |
No |
No |
Yes |
SVC_ITEM_SUPP_COUNTRY_CFA_EXT |
No |
No |
No |
Yes |
SVC_ITEM_SUPP_COUNTRY_DIM |
No |
No |
No |
Yes |
SVC_ITEM_SUPP_MANU_COUNTRY |
No |
No |
No |
Yes |
SVC_ITEM_SUPP_UOM |
No |
No |
No |
Yes |
SVC_ITEM_XFORM_DETAIL |
No |
No |
No |
Yes |
SVC_ITEM_XFORM_HEAD |
No |
No |
No |
Yes |
SVC_ITEM_XFORM_HEAD_TL |
No |
No |
No |
Yes |
SVC_PACKITEM |
No |
No |
No |
Yes |
SVC_RPM_ITEM_ZONE_PRICE |
No |
No |
No |
Yes |
SVC_XITEM_RIZP_LOCS |
No |
No |
No |
Yes |
SVC_XITEM_RIZP |
No |
No |
No |
Yes |
SVC_ITEM_SEASONS |
No |
No |
No |
Yes |
SVC_UDA_ITEM_DATE |
No |
No |
No |
Yes |
SVC_UDA_ITEM_FF |
No |
No |
No |
Yes |
SVC_UDA_ITEM_LOV |
No |
No |
No |
Yes |
SVC_VAT_ITEM |
No |
No |
No |
Yes |
SVC_ITEM_IMAGE |
No |
No |
No |
Yes |
SVC_ITEM_IMAGE_TL |
No |
No |
No |
Yes |
SVC_ITEM_HTS |
No |
No |
No |
Yes |
SVC_ITEM_HTS_ASSESS |
No |
No |
No |
Yes |
SVC_COST_SUSP_SUP_HEAD |
No |
No |
No |
Yes |
SVC_COST_SUSP_SUP_DETAIL_LOC |
No |
No |
No |
Yes |
SVC_COST_SUSP_SUP_DETAIL |
No |
No |
No |
Yes |
SVC_CFA_EXT |
No |
No |
No |
Yes |
CORESVC_ITEM_ERR |
No |
No |
No |
Yes |
S9T_ERRORS |
No |
No |
No |
Yes |
SVC_PROCESS_CHUNKS |
No |
No |
No |
Yes |
S9T_FOLDER |
No |
No |
No |
Yes |