Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 211 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Improvement of the different the OTBI subject name with field name of ERP screen.

Description
This is regarding all subject area.
There are many items in subject area that has different name with field name of ERP screen.
We usually check field name of ERP screen, and try to find appropriate item in subject area.
If there is difference between those, it takes long time to find appropriate item in subject area.
Use Case and Business Need
Oracle says OTBI is userfriendly tool, but we don't see any of that because of above thing.
We have stumbled across creating OTBI report. We really hope it resolves in near future.
This issue is a matter of life and death for us.
More details
In addition, we are designing to utilize the output of OTBI for the data connection between each module for the purpose of establishing a business process, as follows.
ex) PO of OC -> OTBI -> Excel macro -> FBDI or API -> AP of OC and so on...
Original Idea Number: beb2b80a4a
Comments
-
Label name in subject area and column name in ERP screen should be identical if it indicates the same thing. There are so many items in subject area to choose when we try to create a report for various purposes. When label name in subject area and item name in ERP screen refers the same but named differently, it would confuse users and makes it hard for them to show exactly what they want in their report.
0 -
It should be common sense, but between the interface name, business object name and OTBI field name.... we have too much wording. Keep it simple !
0 -
While I agree that the field names should remain the same between ERP, PVOs & OTBI Subject area and they are is most cases. Though we also need to note that the ERP developers are different than those for OTBI and thus causing the differences. It will definitely help new users of OTBI however with experience users learn which subject area provides the relevant field.
0 -
Common Sense if OTBI were to be userfriendly
0 -
Hi there,
Thank you for your idea. I am relocating it to our Transactional Reporting (OTBI) Idea Lab for proper review: https://cloudcustomerconnect.oracle.com/resources/b2df648d2a/summary
Best,
Brendan J. Doyle
0