Configuring the Framework
Setup Guide — Building the Blueprint for a Conversion
| Last updated: September 2026
Contents
- Overview
- Finding Your Way Around
- The Structure at a Glance
- Frameworks
- Phases
- Sub Phases
- Owner Types and Sign-Off
- Building a Framework from Start to Finish
- Quick Reference
1. Overview
This page is where you build the blueprint — the reusable method a conversion follows. You define the phases the work moves through, the individual steps inside each phase, and the roles that are responsible for and approve each step. You set this up once and reuse it for every conversion, adjusting it only when your method changes.
Everything here is configuration. Nothing on this page converts any data by itself — it simply describes how a conversion should be structured. The actual work happens later, in the Conversion module, which follows the blueprint you define here.
WHERE TO FIND IT — Open the Implementation Framework Configuration page:
- Left navigation menu → Pipeline Configuration → Implementation Framework
- or Management → Config → Implementation Framework
It's organised into tabs: Framework, Phase, Sub Phase, and Owner Type. (Don't confuse it with the Implementation Framework module under Process, which is where a conversion is run — see Using the Conversion Module.)
WHO SETS THIS UP — Building the blueprint is usually a one-time job for an administrator or a conversion lead. Most team members never need to come here — they work in the Implementation Framework module (under Process) instead.
2. Finding Your Way Around
The configuration page has one tab per building block. You'll generally fill them in from left to right, because each one builds on the one before it.
| Tab | What you define here |
|---|---|
| Framework | The conversion methods themselves — the top level |
| Phase | The major stages inside a framework |
| Sub Phase | The individual steps inside each phase |
| Owner Type | The roles, and which roles are responsible for or approve each step |
3. The Structure at a Glance
The first three tabs form a simple three-level hierarchy. The fourth — Owner Type — applies across all of them.
Framework ← the whole method (e.g. "S/4HANA Data Conversion")
└─ Phase ← a major stage, done in order (e.g. "Build")
└─ Sub Phase ← a step within the stage (e.g. "Cleansing")
Owner Type ← a role (e.g. "Data Owner"), mapped to sub-phases
as Responsible and/or Approver
Each phase belongs to one framework, and each sub-phase belongs to one phase. Phases and sub-phases both carry a sequence number that fixes the order they appear in.
4. Frameworks
A framework is the whole method for a conversion, from the first stage to the last. A conversion follows exactly one framework.
To add a framework: open the Framework tab and click Add. Fill in the fields below, then Save. Only the first two are required; the rest are descriptive notes that help others understand the method.
| Field | Required | What it means |
|---|---|---|
| Framework | Yes | The name of the method (for example, "S/4HANA Data Conversion"). This is what identifies it everywhere else. |
| Vendor | Yes | The provider or origin of the method — for example the software vendor or partner whose approach it follows. Useful when you keep more than one framework. |
| Description | No | A short note on what this framework is for. |
| Focus | No | What the method concentrates on — the kind of conversion or the outcomes it's aimed at. |
| Method Type | No | The style or category of the method (for example, the type of approach it follows). |
| Key Differentiator | No | What sets this framework apart — the notable strengths or distinctive features worth recording. |
ONE FRAMEWORK RUNS A CONVERSION — A conversion uses the framework set as your data domain's default. You can define more than one framework, but each conversion follows a single one. If you're unsure which is the default, your administrator can confirm it.
5. Phases
A phase is a major stage of the conversion, and phases run in order — for example moving from planning, to building, to testing, to go-live. They're the large steps shown across the top of the Implementation Framework module when a conversion is run.
To add a phase: open the Phase tab and click Add. Fill in the fields below, then Save.
| Field | What it means |
|---|---|
| Phase | The name of the stage (for example, "Discover" or "Build"). |
| Framework | The framework this phase belongs to. Pick it from the list. |
| Sequence | A number that sets the order of this phase among the others. Lower numbers come first. |
| Description | A short note on what happens in this phase. Optional. |
ORDER MATTERS — The sequence number is what puts your phases in the right order. If a phase appears in the wrong place, check its sequence number here.
TURNING A PHASE OFF — A phase can be made inactive if you're not using it. Inactive phases still appear but are shown greyed out and can't be worked in, so you can retire a stage without deleting its history.
6. Sub Phases
A sub phase is a single step within a phase — and this is the level where the actual work screens live. When someone clicks a step in the left menu of the Implementation Framework module, it's a sub-phase they're opening. Examples include "Set Scope", "Object Inventory", "Cleansing", and "Mock Load".
To add a sub phase: open the Sub Phase tab and click Add. Fill in the fields below, then Save.
| Field | What it means |
|---|---|
| Sub Phase | The name of the step (for example, "Cleansing"). |
| Phase | The phase this step belongs to. Pick it from the list. |
| Sequence | A number that sets the order of this step within its phase. Lower numbers come first. |
| Left Navigation Label | The short label shown for this step in the left-hand step menu of the Implementation Framework module. Use it to keep the menu tidy when a step's full name is long. |
| Description | A short note on what this step involves. Optional. |
| Fragment Name | The screen (fragment) this step opens. Pick it from the list — this is what links the step to the right tool, for example a scope screen or a status-tracking grid. |
Sub Phase Name, Phase, Sequence, and Left Navigation Label are required; Description and Fragment Name are optional.
THE STEP IS THE WORKPLACE — Phases give the conversion its shape, but sub-phases are where people actually work. Each sub-phase opens a screen, and that screen shows the objects in scope for the team to act on.
WHERE THESE SETTINGS SHOW UP — Two fields here decide what a user sees when a conversion is run in the Implementation Framework module (Process → Implementation Framework): the Left Navigation Label is the text that appears for this step in the module's left step menu (grouped under its phase), and the Fragment Name is the screen that opens when they click it. So choosing "Set Scope" as the fragment is what makes that step open the Set Scope screen. If a step has no fragment, it still appears in the menu but opens a placeholder. This is the link between the blueprint here and the day-to-day screens covered in Using the Conversion Module.
7. Owner Types and Sign-Off
An owner type is a role in the conversion — for example "Data Owner", "Functional Lead", or "Approver". Roles are defined once here, and then real people are assigned to them for each object when a conversion is running.
Owner types do two jobs:
- They give you a consistent set of roles to assign people to.
- For each step, they record who is Responsible for the work and who is an Approver of it — a clear line of accountability built into the method itself.
To add an owner type: open the Owner Type tab and click the + (add) button in the corner. Give the role a name and, optionally, a description, then Save.
| Field | What it means |
|---|---|
| Owner Type | The name of the role (for example, "Data Owner"). |
| Description | A short note on what this role covers. Optional. |
New roles appear as rows in the Owner Type list. You can edit the name and description straight in the grid, and there's one more setting to be aware of:
| Column | What it means |
|---|---|
| Can Have Multiple Per Object | Tick this if more than one person can hold this role on the same data object (for example, several data owners for one object). Leave it clear if only one person may. |
(The Created By / Created Date / Updated By / Updated Date columns are filled in automatically and can't be edited.)
7.1 Setting what a role does at each step
Saying which steps a role is Responsible for and which it Approves is done on a separate screen, one role at a time — the Object Owner Phase page.
To open it:
- Go to the Owner Type tab.
- Find the role's row in the list.
- In the Action column, click the Object Owner Phase button (the icon next to Delete — hovering over it shows the label "Object Owner Phase").
The Object Owner Phase page opens, with the role's name shown at the top and a Go Back To Summary button to return to the Owner Type list when you're done.
On this page you build the list of steps the role takes part in. Click the + (add) button, then for each step set:
| Setting | What it means |
|---|---|
| Sub Phase | The step this applies to. Pick it from the list of sub-phases. |
| Responsible | Tick if this role does the work at this step. |
| Approver | Tick if this role signs off the work at this step. |
Each step you add becomes a row on the page. You can change the Responsible and Approver ticks directly in the grid at any time, and remove a step with the Delete button in its Action column. Add a row for every step the role is involved in.
RESPONSIBLE VS. APPROVER — A role can be responsible for a step, an approver of it, both, or neither. This is what lets OnCoor show, later, exactly who owns and who signs off each object as it moves through the conversion.
8. Building a Framework from Start to Finish
If you're setting up a brand-new method, this is the order that works best. Each step builds on the one before it.
- Create the framework (Framework tab) — give the method a name and vendor.
- Add the phases (Phase tab) — the major stages, each with a sequence number so they line up in order.
- Add the sub-phases (Sub Phase tab) — the steps inside each phase, each with a sequence number and a work screen.
- Define the owner types (Owner Type tab) — the roles involved.
- Map each role to its steps — for every owner type, open its Object Owner Phase page and mark the sub-phases where it is Responsible and/or an Approver.
- Make it the default — have your administrator set this framework as the default for your data domain, so conversions follow it.
Once that's done, the blueprint is ready. Everything from here on happens in the Conversion module.
REVIEW BEFORE YOU BUILD — Because OnCoor usually ships with a standard framework, check the existing one first. Adjusting a few phase or step names is far quicker than building a method from scratch.
9. Quick Reference
| I want to… | Do this |
|---|---|
| Define a new conversion method | Framework tab → Add → name and vendor → Save |
| Add a stage to a method | Phase tab → Add → choose framework, set sequence → Save |
| Add a step to a stage | Sub Phase tab → Add → choose phase, set sequence and screen → Save |
| Reorder phases or steps | Change their Sequence numbers |
| Retire a stage without deleting it | Make the phase inactive |
| Define a role | Owner Type tab → + → name → Save |
| Allow more than one person in a role per object | Owner Type tab → tick Can Have Multiple Per Object on the role |
| Say who does and who approves a step | Owner Type tab → role's Object Owner Phase button → + → choose sub-phase → tick Responsible / Approver |
| Change a step's short label | Set its Left Navigation Label on the Sub Phase tab |
Source: OnCoor Implementation Framework product documentation, written for end users. For the latest screens and options, always refer to the in-app interface.