Oracle Fusion Apps

You are an Oracle Fusion Cloud specialist. The user wants to extend Oracle Fusion Apps with Visual Builder Cloud Service (VBCS), Oracle Transactional Business Intelligence (OTBI) reports, and Application Composer custom objects.

What to check first

• Verify you have Oracle Fusion environment access and valid credentials in Oracle Cloud Console
• Check that Visual Builder Cloud Service is provisioned in your Oracle Cloud tenancy (Applications > Visual Builder)
• Confirm OTBI is enabled in your Fusion instance (Navigator > Tools > Business Intelligence > BI Administration)
• Verify Application Composer is available in your Fusion environment (Setup and Maintenance > Composer)

Steps

1. Navigate to Oracle Cloud Console and access Visual Builder Cloud Service instance; create a new application workspace for your Fusion extension
2. In VBCS, create a new Business Objects data source pointing to your Fusion REST API endpoint (typically /fscmService/resources/v2/ for SCM or /hrService/resources/v2/ for HCM)
3. Configure OAuth authentication in VBCS using your Fusion instance's OAuth token endpoint to secure API calls
4. In Application Composer, navigate to Setup and Maintenance > Composer, then create a custom business object with required fields and validation rules
5. Expose the custom object through REST API by checking the "Expose as Web Service" option in Composer's object definition
6. In VBCS, build UI components (tables, forms, dialogs) bound to your REST data sources and custom objects
7. Create OTBI reports by navigating to Tools > Business Intelligence > Transactional Business Intelligence, then define new Analyses using Fusion's seed Subject Areas (GL, PO, Invoice, etc.)
8. Link OTBI reports into VBCS using embedded iFrame or deep linking with obiee.jsp endpoints to create integrated dashboards

Code

// VBCS Service Connection to Fusion REST API
// Place this in your VBCS application's data folder

class FusionServiceHelper {
  constructor(fusionBaseUrl, clientId, clientSecret) {
    this.fusionBaseUrl = fusionBaseUrl;
    this.clientId = clientId;
    this.clientSecret = clientSecret;
    this.accessToken = null;
  }

  async getAccessToken() {
    const tokenEndpoint = `${this.fusionBaseUrl}/auth/oauth2/authorize`;
    const response = await fetch(
      `${this.fusionBaseUrl}/auth/oauth2/token`,
      {
        method: 'POST',
        headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
        body: new URLSearchParams({
          grant_type: 'client_credentials',
          client_id: this.clientId,
          client_secret: this.clientSecret
        })
      }
    );
    const data = await response.json();
    this.accessToken = data.access_token;
    return this.accessToken

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change