X

The Oracle BI Application Blogs provides the latest and tips and tricks on Oracle BI Applications Product (OBIA)

Including Fusion-on-Cloud Extensions in BIAPPS

Authors: "Guna Vasireddy - Oracle" and "Yadukrishna Munugoti - Oracle "

The blog explains how to get Fusion DFFs into BI Apps when Fusion is On Premise. This blog explains how you can do the same if Fusion Applications is on Cloud.

When using BI Apps for Fusion (Cloud adaptor), certain Flex VOs are already seeded out of the box. The steps to follow for getting Fusion Flex Extensions into BIAPPS for such VOs are as below.

Extract and Load Fusion Custom Flex Extensions(VO already seeded):

Note:This is only for cases where the VO is already seeded.

  1. Do the required extensions in Fusion
  2. Run BI Extender to get the VO/Flexfields into RPD. Documentation (Section 2.3.6). Note if the VO/Columns do not come into the RPD, then we cannot extract data from it.
  3. Ensure extraction for that Flex VO is enabled in BICC. BICC does a select * for such VOs. So if the VO is very wide and you are having extraction issues, consider disabling certain fields as BI enabled. Run an extract for that VO. Refer to BICC documentation for more details.
  4. If the VO is already seeded and support exists for that VO in ODI for that Fusion Release, then the flex columns will get auto-extended and mapped both in ODI and OBIEE. Nothing additional needs to be done.

Refer to BIAPPS Configure Fusion Source in BIAPPS Installation Guide for details around Flex VOs that are supported out of the box.(this varies with BIAPPS release, so ensure you are looking up the right release).

If the VO you need is not seeded out of the box, certain additional steps will need to be performed. The second blog in this series covers this use-case.

The third blog in this series explains how to troubleshoot common issues when trying to  work with Fusion Flex Extensions.

 

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.