Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Value Chain Planning - EBS (MOSC)

Modifying select query of MV in ASCP standard collection

Mar 17, 2015 6:53AM edited Mar 25, 2015 10:04AM in Value Chain Planning - EBS (MOSC) 1 commentAnswered

Hi All,

As you are aware ASCP will not collect custom item relationship types as part of standard collection program.

Reason being the select query of the MV - MTL_ITEM_RELATIONSHIPS_SN is hardcoded with only few relationship type.

We have requirement where in we need to collect the custom relationship type.

(1) Is it right approach to modify the above MV query where clause?

(2) If yes, what will be the impact? Will it affect any other data collection entity? How about performance?

(3) If no, can you please advice on the right approach to collect the data.

Thanks in advance,

1

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month