Install Base and Asset Tracking - EBS (MOSC)

MOSC Banner

12.2.5 Customer IB and the WIP Tree in the Output for the Interface Install Base Lines

edited Oct 22, 2016 5:00AM in Install Base and Asset Tracking - EBS (MOSC) 3 commentsAnswered

We are trying to understand in detail how Oracle is building serial genealogy in the IB. We know csi_cust_ib_wip_merge using WIP to do this, but we want to understand exactly all the conditions that must be met to create the proper genealogy in the IB to accurately reflect what is being shipped to the customer. We are stepping through the code, but have some questions in the meantime.

We are seeing in the WIP tree output wip_included_rp and also wip_included (no RP). It appears that for BUY items the non- RP is present. What is the different between  WIP_INCLUDED_RP and  WIP_INCLUDED - what does RP means?

Howdy, Stranger!

Log In

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

Register

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

Category Leaderboard

Top contributors this month

EBS Install Base Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center