Implement the data lineage that comes with OBIA ...

basically you have to export/report all of your ETL, DW schema, RPD and Web catalog. Optionally, you could load these into a database set of tables and build an OBIEE model on it. The upgraded versions of OBIA 11g have the ODI ETL built in and it has the scenarios to also read in the exported RPD and webcat details. If you…

You can check individual parts of the RPD (right click on the object), but as Robin has stated - the repository (as a binary file) is either consistent or not.

Check configuration document for the snapshot dates and frequency setups.

You'll have to modify the query to suit your needs ... but it contains the EBS tables you need.

Did you look in the documentation? These topics are covered in the various manuals.(Configuration & Functional Configuration) Oracle Business Intelligence Applications Documentation

The base fact and the snapshot server two different business purposes ... they might both contain AR subject data, and on might be populated using the other, but they are distinct. If you change the grain of any table, then be prepared to have to rework the RPD and possibly the front end (avoid granularity changes in OOTB…

https://gist.github.com/jgilmour/4612391 ^ is employee + supervisor, but has the tables you need and can be easily modified for your needs

There is if you are an oracle partner ...

if your resources have 5 yrs of OBIA implementations, then they should be able to scope the work given the customization requirements ...

Don't change the table structure & column sizes to work around this ... as mentioned by @VAp it is a FLAG -- it's a data issue so trace the mappings back to the source and see if you've got the wrong source column coming in.

https://docs.oracle.com/cd/E63231_01/doc/BIAUP/BIAUP.pdf

They are typically based on requirements and the ability of the resource ...

Not sure what you are asking ... but when setting up OBI Apps you assign datasource numbers to various sources and assign 999 (or something similar) to your warehouse when configuring ... if you only have one source, then pick 001 ...

You'll have to modify the mapping that handles the outer query to have it selected as well. Usually these things are like onions - many layers!

Did you make your changes in SDE, SILO & PLP for W_INT_ORG_D? You might be missing a mapping in SILO or PLP if you are seeing data in _DS (stage) but not in _D (dim).

for a dashboard to show in the menu it has to be in the Dashboards folder (_portal):

Complex join ... example: a date in a fact being greater than a start date and less than or equal to an end date in a dimension would show as one of these types of joins. From BIAPPS: ^ shows as a red join in the physical diagram

since it's a dimension makes sure you know which rows by the unique constraint on the table you are to delete ... and BEFORE you delete the duplicates, make sure you have repointed ALL fact rows connected with the WIDs to be deleted with the same dimension WID that will remain. BACK up the table as-is BEFORE any deletes ...

when doing OBIA implementations, I save off a copy of the RPD and catalog BEFORE trimming - course of habit! Hopefully you have done the same.