My Oracle Support Banner

RMS Itemhdr.dat File Pads Zeros To The Item Column Once Consumed Using Dataloader (Doc ID 2428488.1)

Last updated on AUGUST 01, 2018

Applies to:

Oracle Retail Xstore Point of Service - Version 17.0.1 to 17.0.1 [Release 17]
Oracle Retail Merchandising System - Version 16.0.1 to 16.0.1 [Release 16.0]
Information in this document applies to any platform.

Symptoms

In Xstore 17.0.1


When generating a momzip file from RMS 16.0.1 and running the data through Xstore 17.0.1, item data will not be processed for items whose parent(4) and grandparent(5) are not available.

 

Steps to reproduce:

1. Using RMS 16.0.1, create a .dat file for Xstore consumption.

Example:

ITEMS|FULLHDR|60111|ABC1234|||N|N|1|2|Y|GROUP|C|ALL_COLORS|GROUP|S|ALPHA|||||| 
|108|131|40|131|50|A|LAYAWAY 
DEPOSIT||LAYAWAYDEP||N|N|1000|EA||||E|N||USD||USD|||Y|Y|N|N|N|MANL|||||N||||Y| 
N|Y|Y||||N|N|N|N||||||||N|N| 

2. Copy the .dat file created into Xstore 17.0.1 C:\xstore\download

3. Run dataloader2.bat

Actual: 

The Item will import, but zero padding will be entered into the item ID changing 60111 to 00000060111.

Expected:

Item ID will not be changed during the dataloader import into the database. 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.