Create PO API Has Issues With The Way HTS Is Processed
(Doc ID 2997012.1)
Last updated on JANUARY 15, 2024
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version 23.1 to 23.1 [Release 23.1]Information in this document applies to any platform.
Symptoms
When the Create PO API has HTS array populated for pack items, the HTS details are not processed consistently
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Buyer Pack Item level PO
2. Item HTS Assess exits with est assessment value for component
3. Item has multiple HTS codes associated
4. Create PO API - with HTS array populated with pack item as item
5. Observe that ordsku_hts is populated for both the item (as expected) and pack item (not expected)
6. Delete PO HTS
7. Create PO HTS
8. Observe that the HTS details are not populated correctly
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 |
| Cause |
| Solution |
| References |