The Reclassification Done In Item Parent Does Not Reflect In Item Child

(Doc ID 1910470.1)

Last updated on JUNE 29, 2016

Applies to:

Oracle Retail Merchandising System - Version 13.2.5 and later
Information in this document applies to any platform.


After reclassification is assigned to Item Parent, New Fiscal Attribute was not reflecting to Item Child while Item Parent was changed.

Steps to Reproduce
1. Create a regular Item Parent in Item Maintenance screen. Ensure that Tran Level field is assigned as Line Extension to configure the item as Item Parent. Associate a NCM code to the parent item in Localization Flexible Attributes screen. Note the NCM value.
2. Create or associate a child item for the created Item Parent in Item Maintenance screen by clicking Create Children button.
3. In itemchildren, select Oracle Retail Number from Item Number Type dropdown list. Enter a descript for th child item. Notice that all attributes from Item Parent was inherited by the child item including the NCM code. Click OK button.
4. In itemmaster, submit and approve the item parent. Notice that it will also submit and approve its child item.
5. In SQL Developer, check if items (parent and child) is populated in “A”pproved status in ITEM_MASTER table. These items are also posted in ITEM_COUNTRY_L10N_EXT table. Notice that their NCM Codes are the same which is VARCHAR2_3 column field.
6. Create a Fiscal Item Reclassification for the Item Parent. Navigate to Items, rtkstrt  Items  Reclassification  Fiscal Reclassification  New
7. In l10nbrfreclass, select the item parent for reclassification and a New NCM Code (different from the old NCM Code). Set other required fields as same as the old values like Old/New Merchandise Origin as same and Old/New Service ID as same. Leave other fields as NULL or unpopulated.
8. In l10nbrfreclass, select a date equal to tomorrow’s date (or VDATE+1) and then click OK button. Ensure to note the Reclassification ID.
9. In SQL Developer, check the item parent registered in L10N_BR_FISCAL_RECLASS table. Notice that Old NCM Code field holds the original NCM when it is created while New NCM Code field will be the target NCM after reclass. Notice also that Status is set as “N” value while Processed Date field is not yet populated.
10. Run Reclass Item Retail KSH batches in sequential order below and check for any error logging messages:
a. l10n_br_fiscal_reclass_item_finish_retail.ksh
b. l10n_br_fiscal_reclass_item_process_retail.ksh
c. l10n_br_fiscal_reclass_item_setup_retail.ksh
11. In SQL Developer, check L10N_BR_FISCAL_RECLASS table of the item parent. Notice that status was flipped to “P” value and Processed Date was populated with VDATE value.
12. In SQL Developer, check also ITEM_COUNTRY_L10N_EXT table of both item parent and item child. Notice that VARCHAR2_3 column field for Item Parent is changed with the new NCM code set from the Fiscal Reclassification screen while NCM code was not reflected to the Item Child.


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