DM_SITE_CODE is null in staging table after running Shipment And Booking History collections
(Doc ID 1392484.1)
Last updated on APRIL 04, 2025
Applies to:
Oracle Demantra Demand Management - Version 7.3.0.1 and laterInformation in this document applies to any platform.
Symptoms
On : 7.3.0.1 version AND later, LoadData
When attempting to run shipment and booking history collections for the first time
dm_site_code is populated as ::: for about some of the records. All other records are correctly populated.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Run Shipment and Booking History collections for the first time
2. Run the ebs full download workflow
3 Check t_src_loc_tmpl_err. the records show that dm_site_code is populated as ::: for about some of the records
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 |