Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture
Comments
-
Your customer is insistent on using an antiquated and out of service piece of software? Really? +1 to @Christian Berg -- I find this a little suspicious as well ...in addition to nothing substantial to base an answer on.
-
What fact table depends on a good deal of analysis on what is there OOTB and how you intend to use the metrics: Do all the components/measures/columns for your metrics exist in the physical tables - at grains that can be combined? Are you looking to add these to the physical tables or in the logical models? Do you need the…
-
You've got different data types between your keys TAB_ID and TABID ...
-
I can google as well as you ... https://blogs.oracle.com/biapps/entry/implementing_oracle_bi_applications_using I recommend you enlist the aide of an OBI Apps partner ... customization MUST be done with the view to upgrading and patching.
-
My miss!
-
Thanks ... I would have gone there, but OP has no version ... so it would be hard to give proper link.
-
Some tables get used based on the source type (PSoft 9.2 versus eBS) ... you might need to resort to sourcing via the universal adapters if these SDE tables aren't part of the OOTB prebuilt content in ODI.
-
What you posted answers your question ... W = Warehouse OOTB (not custom) AP = Accounts Payable INV = Invoicing DIST = Distribution F = Fact (base fact grain; not aggregated) Now if you don't know what a distribution is from an accounting perspective that's a different matter: "Distribution details include invoice…
-
If the ETL is writing the dimensional row WID into the fact, then the AS-WAS is being strictly enforced and it's very difficult to undo once you are under way (need a warehouse reset) ... check to see if the ETL is writing the SCD WID or not. Ex. Dimension ROW_WID SCD_WID EFF_START EFF_END CURRENT 302 123 12/2/2008…
-
I'll see if I kept any notes from my past implementations on the changes made to the Headcount logic ...
-
-B is base_repository_pathname ... if you aren't running the executable in the same folder as the RPD, then you need to tell it where the RPD is ... You might be able to skip -B if you are using the executable to create a new RPD ... but it's needed if you are applying the script to modify an RPD…
-
It does work OOTB ... do you have the Data Model Reference, Product Guides, etc for your version of OBIA? What version do you have?
-
I suggest you enlist the aide of an OBIA implementation partner ... there's no way I can walk you through a change like this over a forum. Your risk to upgrading is too high if it's not done properly. Partners usually have a customization approach and you should select based on comfort level to that.
-
Customization in OBIA MUST BE DONE with upgrades in view ... if you've never done customization on OBIA then seek the help of a partner who has. It's worth the extra cost.
-
Off the top of my head: you could mimic the one fact with a custom one that has the GL date in the grain and not the Create date; OR you could add the GL data as a custom column to the OOTB fact (be very careful that you do this properly so any upgrades apply to OOTB and don't erase your customization)
-
Most implement via a partner - partners bring the value of understanding the source system(s), the ETL, the BI models and the visualizations -- having established practices and having done it many times. In addition to that they also have customization approaches which are essential when upgrading the OBIA in the future…
-
The error is a telling you what the issue is: you have dimensional tables outer joined to fact tables in which you might have the content levels mixed (various granular levels at play)
-
Why would your development warehouse be based on a moving target as the development source? That source is up and down and you are at their mercy ... sources for EDW should be much more stable than the DEV ERP.
-
Anything in here: https://imdjkoch.wordpress.com/tag/how-to-format-numbers-in-bi-publisher-template/ to help you?
-
1 - Serious: high functioning OBI teams have their own DBA -- you've found the reason why 2 - Partly facetious: if you don't have one then you've got to do two (or more) serious jobs for one paycheck ... so ... here's the manual Managing Optimizer Statistics - 11g Release 2 (11.2) 3 - Serious: without knowing what you've…