Import Balance Register and Entitlement Plan

You can now import subscription balance registers, allowances, and related adjustments in Oracle Subscription Management via CSV import. This feature provides new import objects such as “Subscription Balance Register,” “Subscription Allowances,” “Subscription Allowances Adjustments,” “Subscription Estimates,” “Subscription Commitments,” and their respective adjustments and true-up records. The import supports standard (not high volume) and hierarchical data, with defined mandatory fields such as Balance Register Number, Subscription Number, Product Number, and others. Certain derived fields (e.g., Remaining Quantity) are automatically calculated. The feature also allows for the export and update of these records, and supports the negotiation and updating of entitlement plans via CSV.

  1. Enables customers to migrate balances from legacy or third-party systems, facilitating onboarding and transition to Oracle Subscription Management.
  2. Supports lifecycle management for subscription balances, including allowances, commitments, and adjustments, improving data accuracy and audibility.
  3. Provides flexibility to update entitlement plans in bulk, supporting real-world contract negotiation and management.
  4. Eliminates manual data entry by allowing bulk import and update operations, increasing efficiency and reducing error risk.
  5. Strengthens integration options with external processes or systems by supporting standard CSV import/export capabilities

Steps to Enable and Configure

You don't need to do anything to enable this feature.

Tips And Considerations

  1. The import is supported for standard volume only—not for high-volume scenarios.
  2. Pay attention to mandatory fields such as Balance Register Number, Product Number, Subscription Number, Amount, Consumed Amount, and associated dates.
  3. Only active balance register numbers should be used during import for allowances, estimates, and commitments.
  4. For numeric entries like Consumed Quantity, only positive values are allowed, and updates are permitted only if current value is null or zero.
  5. When designing CSV files, consider required field types and derived field logic (e.g., remaining values = total – consumed).
  6. Hierarchy import is available—ensure hierarchy is accurate if using this option.
  7. Negotiated entitlement plans support export and update via CSV but not full create operations—in those cases, use system job for initialization first.
  8. Export/import/update functionality is supported for several objects, but CRUD (create, read, update, delete) is only available for volume rating data.
  9. When updating material content or dependencies, track changes carefully and notify relevant stakeholders as per process guidelines for traceability and compliance