Oracle PBCS

Oracle Planning and Budgeting Cloud Service (PBCS) provides comprehensive enterprise planning and budgeting solutions, enabling organizations to streamline financial planning processes, create detailed budgets, perform scenario analysis, and collaborate on planning activities across departments.

Power end-to-end data operations for your Oracle PBCS API with Nexla. Our bi-directional Oracle PBCS connector is purpose-built for Oracle PBCS, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Oracle PBCS or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Oracle PBCS workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating an Oracle PBCS credential, you need to identify your Oracle EPM tenant base URL and obtain your Oracle PBCS username and password. Oracle PBCS uses Basic Authentication for all API requests, with the username and password sent in the Authorization header.

To obtain your Oracle PBCS credentials, follow these steps:

1. Sign in to your Oracle EPM Cloud account using your administrator credentials.

2. Navigate to your Oracle EPM tenant dashboard or service console in the Oracle Cloud interface.

3. Identify your Oracle EPM tenant base URL. The base URL is typically in the format https://{tenant-id}.{region}.epm.us2.oraclecloud.com or similar, where {tenant-id} is your tenant identifier and {region} is your region identifier. You can find this in your Oracle EPM Cloud service URL or in your Oracle Cloud account settings.

4. Your Oracle PBCS username is typically your Oracle Cloud account username or the username assigned to your Oracle EPM Cloud service account.

5. Your Oracle PBCS password is the password associated with your Oracle Cloud account or Oracle EPM Cloud service account.

6. Store all credentials securely, as you will need them to configure your Nexla credential. The username and password are sensitive information and should be kept confidential.

The username and password are sent in the Authorization header using Basic Authentication (Base64-encoded) for all API requests to the Oracle PBCS API. The base URL determines which Oracle EPM tenant your API requests will be sent to. If your credentials are compromised, you should immediately change your password in your Oracle Cloud account settings. For detailed information about Oracle PBCS authentication, API access, and available endpoints, refer to the Oracle EPM REST API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Base URL	Yes	No	Enter the Base URL for your Oracle EPM Tenant. See https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/prest/authentication_overview.html for details.
Username	Yes	No	Username
Password	Yes	Yes	Password

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Oracle PBCS

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

Oracle PBCS uses Basic Authentication for all API requests. The username and password are sent in the Authorization header using Base64 encoding to authenticate API requests to the Oracle PBCS API.

3. Enter your Oracle EPM tenant base URL in the Base URL field. This should be the base URL for your Oracle EPM tenant, typically in the format https://{tenant-id}.{region}.epm.us2.oraclecloud.com or similar. The base URL determines which Oracle EPM tenant your API requests will be sent to. Refer to the Oracle EPM documentation for the correct base URL format for your tenant.

4. Enter your Oracle PBCS username in the Username field. This is the username associated with your Oracle Cloud account or Oracle EPM Cloud service account. The username is used for Basic Authentication.

5. Enter your Oracle PBCS password in the Password field. This is the password associated with your Oracle Cloud account or Oracle EPM Cloud service account. The password is sent in the Authorization header using Base64 encoding for all API requests to the Oracle PBCS API. The password is sensitive information and must be kept confidential.

   Your Oracle PBCS credentials can be found in your Oracle Cloud account or Oracle EPM Cloud service account. The username and password are sent in the Authorization header using Basic Authentication (Base64-encoded) for all API requests to the Oracle PBCS API. The base URL should match your Oracle EPM tenant URL.

   If your credentials are compromised, you should immediately change your password in your Oracle Cloud account settings. The username and password provide access to your Oracle PBCS account data and should be treated as sensitive information. Keep your credentials secure and do not share them publicly.

   For detailed information about Oracle PBCS authentication, API access, and available endpoints, see the Oracle EPM REST API documentation.

6. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Oracle PBCS connector tile, then select the credential that will be used to connect to your Oracle PBCS account, and click Next; or, create a new Oracle PBCS credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Oracle PBCS endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get API Versions

This endpoint template returns information about which REST APIs are available and supported in your Oracle PBCS instance. Multiple versions may be supported simultaneously. Use this template when you need to discover available API versions before using other Oracle PBCS endpoints.

• This endpoint automatically retrieves all available API versions from your Oracle PBCS instance. No additional configuration is required beyond selecting this endpoint template.

This endpoint returns information about which REST APIs are available and supported in your Oracle PBCS instance. The response includes details about available API versions, which can be used with other Oracle PBCS endpoints that require an API version parameter.

For detailed information about API versions, API access, and available endpoints, see the Oracle EPM REST API documentation.

Migration API: Get all Files

This endpoint template lists the files in the Planning repository and returns information about the available file and application snapshots. Use this template when you need to discover available files and snapshots before downloading them.

• Enter the API version in the API Version field. This should be the API version you want to use for this request (e.g., v11, v12). The API version determines which version of the Oracle PBCS API will be used. You can find available API versions by using the "Get API Versions" endpoint.

This endpoint lists the files in the Planning repository and returns information about available file and application snapshots. The response includes file names, snapshot names, and other metadata that can be used with the "Migration API: Download File Content" endpoint to download specific files.

For detailed information about file management, API response structures, and available file data, see the Oracle EPM REST API documentation.

Migration API: Download File Content

This endpoint template downloads a file from the repository to the local environment. Use this template when you need to download specific files or application snapshots from your Oracle PBCS Planning repository.

• Enter the API version in the API Version field. This should be the API version you want to use for this request (e.g., v11, v12). The API version determines which version of the Oracle PBCS API will be used.
• Enter the application snapshot name or file name in the Application Snapshot Name or File Name field. This should be the name of the snapshot or file you want to download (e.g., Artifact Snapshot or s112.csv). The snapshot or file name determines which file will be downloaded from the repository.
• Select the file content type from the File Content Type pulldown menu. Available options include CSV, JSON, Text, XML, and ZIP file. If the file is a zip file, select the content type of the unzipped files. The file content type determines how the downloaded file will be processed.

This endpoint downloads a file from the Planning repository to the local environment. If the content type of the response is application/JSON, then an error with details is displayed on the server. Otherwise, the content of the file is streamed through the response. The endpoint supports various file types including CSV, JSON, Text, XML, and ZIP files.

For detailed information about file downloads, API response structures, and available file types, see the Oracle EPM REST API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Oracle PBCS data sources can also be manually configured to ingest data from any valid Oracle PBCS API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Oracle PBCS API typically uses the GET method. The endpoint URL should include your base URL (from your credential) plus the API path, e.g., /interop/rest or /interop/rest/v11/applicationsnapshots. For the Response Data Path, use $.items[*] to extract all items from the items array, depending on your endpoint; ensure the JSONPath expression matches the structure returned by your specific endpoint.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Oracle PBCS data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.