My Oracle Support Banner

CREATE_PURCHASE_ORDER Entity | ORDSKU_HTS Origin Country Id Mismatch (Doc ID 2857476.1)

Last updated on MARCH 23, 2022

Applies to:

Oracle Retail Merchandising Foundation Cloud Service - Version 19.3 and later
Information in this document applies to any platform.

Goal

While converting a PO from source (v13), it is noticed that there is a origin country id mismatch between what was loaded vs what gets processed in to the main tables. 

 

Example;

Originally PO was loaded with ORIGIN_COUNTRY_ID=KH from the source and the same can be seen in the rdc01 svc table as well
select * from rdc01.svc_ordsku_hts where item= '10258363' and order_no=1926291;
--ORIGIN_COUNTRY_ID=KH

however once the PO gets loaded into the main table via CREATE_PURCHASE ORDER Entity, it can be seen that it gets loaded with ORGIN COUNTRY ID as CN
select * from rms01.ordsku_hts where item= '10258363' and order_no=1926291;
--ORIGIN_COUNTRY_ID=CN

In rms01.ITEM_HTS table, both CN and KH are present with same effect to and effect from dates.
 

Solution

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
Goal
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.