Sequencing Is Incorrect in the STKU Files Generated by the 'ThirdPartyStockCountParser' Batch Program (Doc ID 1574835.1)

Last updated on JULY 01, 2016

Applies to:

Oracle Retail Store Inventory Management - Version 13.2.3 to 13.2.6 [Release 13.2]
Information in this document applies to any platform.

Symptoms

In Oracle Retail Store Inventory Management (ORSIM), line sequence numbers are incorrect in the STKU files generated by the 'ThirdPartyStockCountParser' batch program.
  

Steps to Reproduce:
 
  Create Product Group:
 
  1. In SIM, select Admin > Product Group > Unit and Amount from the Product Group Detail Type.
  2. Add a Product Group description.
  3. Enter a Variance (can be anything).
  4. Select Third Party under Counting Method.
  5. Hierarchy Breakdown set to None.
  6. Select All Stores.
  7. Select Product Group Components.
  8. Select All Departments in the New Product Group Element section.
  9. Select Add to Group.
 10. Select Done.
 
  Create Product Group Scheduler:
 
  1. Select Product Group Scheduler > Create > Unit and Amount from Product Type.
  2. Select the Product group created from the Product Group.
  3. Select Locations and click the right arrow.
  4. Enter data in the Description field.
  5. Enter the date.
  6. Select Done.
  7. Run ExtractUnitAmountStockCount.sh job on SIM server to create a snapshot.
  8. Run the ThirdPartyStockCountParser.sh job on SIM server that creates STKU files in stockcountUpload directory in SIM.


The ThirdPartyStockCountParser.sh job needs the count files as input which can be created by running the following query on the database:


  9.  Create file with header record as: FHEAD|storenumber|stockcountnumber.  Append the result from the query above after header.  Store number and Stock Count need not match in the file with filename.
10.  Copy same file and change header record and file name to create multiple files for multiple stores.

Observe: Sequencing is off in the STKU files: i.e., the sequence numbers for the new file start from where the sequencing in one of the other files ended.  Sequencing should always start with 1.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms