Automated lease management process using VBCS in ofc-23b

ERP Oracle Fusion Cloud
, , , , , , , ,
1

I wanted to share our successful implementation of an automated lease management process using Visual Builder Cloud Service (VBCS) integrated with Oracle Fusion Cloud 23b. This project eliminated manual entry for lease contracts and significantly improved accuracy in our lease accounting.

Previously, our lease administrators manually entered lease contract details into Fusion, which was time-consuming and error-prone. We built a VBCS application that allows business users to input lease information through a user-friendly interface, then automatically creates lease records in Fusion via REST API integration. The application also handles workflow approvals for lease contracts before they’re committed to the system.

The VBCS integration connects to Fusion’s lease management module and synchronizes data in real-time. We’ve seen a 70% reduction in data entry time and improved accuracy with automated validation rules. I’ll share more details about the architecture and implementation approach.

2

We use a hybrid approach. The VBCS application has business objects that store draft lease contracts. Users can save their work in progress, and the data stays in VBCS until they submit for approval. Once the workflow approval is complete, a service connection triggers the REST API call to create the lease in Fusion. This way, incomplete or unapproved leases don’t clutter the Fusion system. The business objects also allow us to implement custom validation rules that are more user-friendly than Fusion’s native validation messages.

3

What about data synchronization in the other direction? If someone modifies a lease directly in Fusion, does that sync back to your VBCS application? Also, how do you handle lease amendments and renewals - do those go through the same VBCS workflow or are they managed directly in Fusion?

4

We built the approval workflow entirely in VBCS using business objects and action chains. It’s a simple two-tier approval: lease administrator reviews for completeness, then finance manager approves for accounting impact. For error handling, we implemented a retry mechanism with exponential backoff. If the Fusion API call fails, the lease record stays in ‘Approved-Pending Sync’ status in VBCS, and a scheduled job retries the sync every 30 minutes up to 5 attempts. If it still fails, it generates a notification to the admin team for manual intervention.

5

How did you handle the workflow approvals within VBCS? Did you build a custom approval workflow or integrate with Fusion’s approval framework? Also, what happens if the Fusion API call fails after approval is granted - do you have error handling and retry logic?

6

Let me provide a comprehensive overview of our automated lease management implementation using VBCS integrated with Oracle Fusion Cloud 23b, covering the architecture, integration approach, workflow implementation, and data synchronization strategy.

VBCS Integration Architecture: Our solution uses a three-tier architecture that separates user interface, business logic, and data persistence:

  1. Presentation Layer: VBCS pages provide a simplified lease entry interface with guided workflows. We created custom pages for different lease types (real estate, equipment, vehicles) with conditional fields based on lease classification.

  2. Business Logic Layer: VBCS business objects store draft lease data with custom validation rules. We implemented JavaScript functions in action chains to validate lease terms, calculate present values, and determine lease classification (operating vs finance lease) before submission.

  3. Integration Layer: REST service connections to Fusion Cloud APIs handle data synchronization. We use the Lease Management REST API endpoints for creating leases and the File Import/Export API for bulk operations.

The integration flow works as follows:

// Pseudocode - VBCS to Fusion lease creation flow:

  1. User completes lease entry form in VBCS
  2. VBCS validates data using custom business rules
  3. Store draft in VBCS business object (status: DRAFT)
  4. User submits for approval - triggers workflow
  5. On approval completion, call Fusion REST API
  6. Create lease record in Fusion using POST /leases endpoint
  7. Update VBCS business object with Fusion lease ID
  8. Set status to SYNCED in VBCS // Error handling includes retry logic and admin notifications

Workflow Approvals Implementation: We built the approval workflow entirely within VBCS rather than integrating with Fusion’s approval framework. This gave us more flexibility for the pre-creation approval process:

  • Created custom business objects for approval routing (LeaseApproval) with fields for approver, status, comments, and timestamps
  • Implemented role-based approval assignment using VBCS security rules
  • Built action chains that automatically route to the next approver based on lease value thresholds and lease type
  • Configured email notifications using VBCS notification features to alert approvers

The workflow has three approval stages:

  1. Lease Administrator: Validates completeness and accuracy of lease terms
  2. Finance Manager: Reviews accounting classification and financial impact
  3. Executive Approval: Required for high-value leases (>$500K annual commitment)

Each approval stage can approve, reject, or request modifications. Rejections route back to the originator with comments. This workflow prevents incomplete or incorrect lease data from reaching Fusion.

Data Synchronization Strategy: We implemented bidirectional synchronization with some important design decisions:

VBCS to Fusion (Primary Direction):

  • New lease creation flows through VBCS workflow then syncs to Fusion
  • Lease amendments initiated in VBCS follow the same approval workflow
  • Bulk imports use VBCS file upload, which validates data then calls Fusion’s bulk import API

Fusion to VBCS (Read-Only Sync):

  • We implemented a scheduled integration that runs nightly to pull lease updates from Fusion back to VBCS
  • This sync updates the VBCS business objects with current lease status, payment schedules, and accounting entries
  • Users can view the complete lease lifecycle in VBCS, but modifications made directly in Fusion are read-only in VBCS

Why Read-Only Reverse Sync: We made a strategic decision that VBCS is the system of record for lease initiation and amendments, while Fusion is the system of record for accounting and payments. Direct modifications in Fusion (like payment processing or journal entries) sync back to VBCS for visibility, but users can’t edit them in VBCS. This prevents sync conflicts and maintains clear data ownership.

Validation Rules Implementation: We implemented a layered validation approach:

VBCS-Level Validations (Pre-Submission):

  • Required field validation (lessor, lessee, lease term, payment amounts)
  • Business rule validation (lease term must be ≥ 12 months, payment frequency must match term)
  • Calculation validation (present value calculation using configured discount rate)
  • Lease classification logic (determines operating vs finance lease based on ASC 842 criteria)

These validations provide immediate feedback to users with user-friendly error messages.

Fusion API-Level Validations (At Sync Time):

  • We allow Fusion to perform final validation during the API call
  • If Fusion rejects the lease creation, we capture the error details and display them in VBCS
  • The lease record stays in ‘Approved-Pending Sync’ status and users can correct issues and retry

This layered approach catches most errors early (better user experience) while letting Fusion enforce its authoritative validation rules (data integrity).

Complex Lease Scenarios: For variable payments and lease modifications, we extended the base implementation:

Variable Payments:

  • VBCS interface includes a payment schedule table where users can input varying payment amounts by period
  • The application calculates the present value of the payment stream using the incremental borrowing rate
  • This payment schedule syncs to Fusion as a detailed payment schedule attachment

Lease Modifications:

  • We created a separate VBCS page for lease modifications that loads existing lease data from Fusion
  • Users specify the modification type (term extension, payment change, scope change)
  • Modifications follow the same approval workflow as new leases
  • The sync process uses Fusion’s lease modification API endpoint rather than creating a new lease

Error Handling and Resilience: Robust error handling was critical for production reliability:

  1. Retry Logic: Exponential backoff retry for transient API failures (network issues, Fusion temporary unavailability)
  2. Error Logging: Comprehensive logging of all API calls, responses, and errors in VBCS business objects
  3. Admin Dashboard: Built a VBCS page showing all failed sync attempts with details and manual retry capability
  4. Notification System: Automated alerts to admin team when sync fails after all retry attempts
  5. Data Reconciliation: Weekly scheduled job compares VBCS and Fusion lease counts and flags discrepancies

Results and Benefits: After six months in production:

  • 70% reduction in lease entry time (from 45 minutes to 12 minutes average per lease)
  • 95% reduction in data entry errors (from 15% error rate to <1%)
  • 100% compliance with approval requirements (workflow enforcement eliminated approval bypasses)
  • Improved audit trail with complete history of lease creation, approvals, and modifications in VBCS
  • Better user adoption due to simplified interface compared to Fusion’s native lease entry

Lessons Learned:

  1. Start with a pilot for one lease type before expanding to all lease categories
  2. Invest time in user-friendly error messages - this significantly reduces support tickets
  3. Build comprehensive logging and monitoring from the start - troubleshooting integration issues requires detailed logs
  4. Plan for data migration - we had to load historical leases into VBCS for complete visibility
  5. Document the integration architecture thoroughly - knowledge transfer is critical for ongoing support

This implementation demonstrates how VBCS can extend Fusion Cloud capabilities with custom user experiences while maintaining data integrity through proper integration patterns and workflow controls.

7

I’m curious about the technical implementation of your validation rules. Did you replicate Fusion’s lease accounting validation logic in VBCS, or do you rely on the Fusion API to catch validation errors? Also, how do you handle complex lease scenarios like variable payments or lease modifications?