Which of the following must be defined when creating a new pipeline in Oracle Cloud EPM?

When configuring a new pipeline in Oracle Cloud EPM Data Integration, administrators must specify the pipeline details, including source and target connections/applications and the sequential steps necessary to process data. A pipeline serves as an orchestration framework that executes stages such as data extraction, transformation mappings, validation, and loading into target applications. While global period mappings and security roles exist as prerequisite system configurations, they are managed independently in administrative consoles rather than created inside the individual pipeline definition. Similarly, financial reporting templates belong to the EPM Reporting module. Thus, defining the source, target, and transformation execution steps forms the fundamental required structure of any EPM data pipeline.

A. User roles and permissions for each data source: Access permissions and user roles are configured globally in Access Control and security settings, not defined during individual pipeline creation.
B. The financial reporting templates for each data load: Financial reporting templates are created and maintained in EPM Reporting or Management Reporting modules, independent of data pipeline definitions.
D. The period mappings for each target system: Period mappings are predefined system-wide or application-level configurations in Data Integration, not created inside the pipeline definition itself.

1. Oracle Help Center, Administering Data Integration for Oracle Enterprise Performance Management Cloud, "Defining Pipelines," Section: "Adding Pipeline Details and Job Steps."

2. Oracle Cloud EPM Documentation, Administering Data Management for Oracle Enterprise Performance Management Cloud, Section: "Setting Up Source and Target Applications."