My Oracle Support Banner

Using ADM to Export Updated LOVs (Doc ID 509839.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel System Software - Version 7.8.2 [19213] and later
Information in this document applies to any platform.
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213]



***Checked for relevance on 18-Nov-2013***

Symptoms

While using ADM to export Child LOV Types that are associated to a Parent Vanilla LOV Type, the LOVs are not being displayed when validating the filter.

We determined that our best filtering is based on Updated > 01/01/1980 and Language code being ENU.  Yet, we are not seeing the results that we expect.

Given the following filter:

[Updated] > '01/01/1980'
OR
[List Of Values Child (UDA).Updated] => '01/01/1980'


The filter does not output vanilla LOVs that have been modified. Only new parent and child LOVs that were added are retrieved by the filters.

Why do these filters NOT display the updated vanilla child LOVs?


We then created another filter to capture our modified vanilla parents and child LOVs.

Note the following filter:

([Value] = 'MR_MS'  OR  [Value] = 'OFFER_MEDIA'  OR [Value] = 'REVENUE_TYPE' OR  
 [Value] = 'SALES_STAGE_STATUS' OR
 [Value] = 'TODO_TYPE')
 AND ([List Of Values Child (UDA).Language] = 'ENU')


However, the Integration Object is not able to filter on the language field for these LOVs: this filter retrieves the child LOVs for all languages.

Why are these filters are not working?  What can be done to make them behave as we expect?

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

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.