My Oracle Support Banner

DM_SITE_CODE is null in staging table after running Shipment And Booking History collections (Doc ID 1392484.1)

Last updated on AUGUST 22, 2019

Applies to:

Oracle Demantra Demand Management - Version 7.3.0.1 and later
Information in this document applies to any platform.

Symptoms


On : 7.3.0.1 version, 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


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