An artifact bundle in Oracle EPM Cloud is a packaged export of selected application artefacts — created through the EPM Cloud Lifecycle Management (LCM) interface or EPM Automate — that contains a specific subset of the application’s configuration for targeted deployment to another environment. An artifact bundle differs from an application snapshot in scope and purpose: a snapshot captures the complete application state for disaster recovery; an artifact bundle captures a selected set of configuration artefacts for controlled change promotion. In a typical EPM change management workflow, a developer creates an artifact bundle in the development environment containing the changed business rules, forms, and metadata, and promotes the bundle to test and then to production rather than exporting and importing the entire application.
Artifact Bundle Contents and Dependencies
An artifact bundle can contain any combination of EPM artefact types: dimension metadata, member formulas, business rules, Calculation Manager rule sets, data forms, task lists, smart lists, substitution variables, security filters, user role assignments, and application configuration settings. Artifact bundles are not self-contained — artefacts may reference other artefacts not included in the bundle. A business rule that references specific dimension members assumes those members exist in the target environment; if they do not, the rule deploys but fails at execution time with a member not found error. The bundle creator must understand the dependencies of the included artefacts and either include the dependencies or verify their existence in the target environment before deploying the bundle.
Design Considerations
Artifact bundle design in a change management context requires a clear categorisation of artefacts by type and dependency. A release management process built on artifact bundles needs to define which artefacts are included in which bundle, in what sequence the bundles are deployed, and which artefacts require the target environment to be in a specific state before the bundle can be deployed successfully.
What Goes Wrong in Practice
The specific artifact bundle failure that most frequently requires production incident response is deploying a bundle that includes a security artefact — a role’s data access filter — that was authored in development against a specific set of dimension members, and deploying it to production where the dimension structure has diverged from development. The security filter in the bundle contains member names that exist in development but not in production, resulting in security filters that either fail to deploy or deploy with incorrect restrictions. Users in production either lose access to data they should see, or gain access to data they should not see. Security artefact deployments must be validated against the production dimension structure before deployment.
How Loop Wise Solutions Handles This
We validate the target environment’s dimension state against the artefact bundle’s dependencies before every bundle deployment — running a pre-deployment checklist that confirms each dimension member referenced in the bundle’s artefacts exists in the target environment. Security artefact deployments are reviewed separately for access implications before deployment, and access validation testing is performed after every security bundle deployment before users are notified that the change is complete.
