Console

Add Elements Separately

One method for creating a context is to add a process area, object, planning group and load cycle separately, then assign them to a wave.

Add a Wave

Add a Wave on the Waves page, the first page that opens when Console opens (also accessible by clicking Waves on the Navigation pane).

A Wave is a categorization for a migration project and is the first level of the hierarchy. A migration project must have at least one Wave, but can have multiple Waves. A Wave could be a country where a migration project is rolled out or a specific work location.

A Wave contains a data source which contains the target tables downloaded from an ERP system.

To add a Wave in Console:

  1. Click Add on the Waves page.

    View the field descriptions for the Waves page

  2. Enter a Wave name in NAME field.

    NOTE: This name and the name of the Process Area are combined to create a context.

    NOTE: A Wave name can be a maximum of 10 characters long.

    NOTE: The ACTIVE check box is checked by default. If the check box is not checked for a Wave, the contexts that use this Wave will not display in the Context bar and cannot be used in ADM.

  3. Add a description of the Wave in the DESCRIPTION field.
  4. Click Save; the Vertical View displays.
  5. Select an option from the Target System list box.

    NOTE: A Wave can have multiple target systems. Refer to Add Multiple Target Systems at the Wave-Process Area Level for more information.

    NOTE: To use Syniti’s Migration dashboard, set the Start Date and End Date. Refer to Configure the Migration Dashboard for more information.

  6. Click Save.

A Wave can also be added by copying an existing Wave. Refer to Copy Elements for more information.

NOTE: If a user is currently working in a context (as in, that context displays on the user’s Context bar), neither the Wave nor Process Area in the context can be deleted.

Continue with Add a Process Area.

Add a Process Area

A Process Area is used to group an ERP system’s objects. It is the second level of the hierarchy and is assigned to a Wave.

NOTE: If security for ADM is restricted, as in, users only work with certain Wave-Process Areas and Wave-Process Area-Objects, an additional step must be taken when adding a Wave-Process Area. Refer to Set Up Security for ADM for more information.

NOTE: The combination of a Wave and Process Area is a context and is used on the Context bar to drive the work in other components. Refer to Context, the Context Bar, and Navigation in ADM for more information.

Examples of Process Areas for an ERP integration are Sales and Distribution (SD), Purchase to Pay (P2P) or Human Capital Management (HCM).

To add a Process Area to be used in a hierarchical structure:

  1. Select Elements > Process Area from the Navigation pane.

  2. Click Add.

    View the field descriptions for the Process Area page

  3. Enter a Process Area name in the Process Area field.

    NOTE: A Process Area name can be a maximum of 15 characters long.

  4. Enter a description of the Process Area in the DESCRIPTION field.
  5. Click Save.

The Process Area displays in the Process Area ID list box on the Wave : Process Areas page, and can be assigned to a Wave to create a context.

A Process Area can also be added by copying an existing Process Area. Refer to Copy Elements for more information.

NOTE: If a user is currently working in a context (i.e., that context displays on the user’s Context bar), neither the Wave nor Process Area in the context can be deleted.

Continue with Add an Object.

Add an Object

An Object is a migration object, and is assigned to a Wave-Process Area combination. Examples of Objects include customers, basic materials, price lists or sales orders.

NOTE: If security for ADM is restricted, as in, users only work with certain Wave-Process Areas and Wave-Process Area-Objects, an additional step must be taken when adding a Wave-Process Area and Wave-Process Area-Object. Refer to Set Up Security for ADM for more information.

An Object can also have contacts and decisions and its history can be tracked.

To add a migration object: 

  1. Select Elements > Object from the Navigation pane.

  2. Click Add; the Vertical View displays.

    View the field descriptions for the Objects page

  3. Enter an object name in the NAME field.
  4. Enter an object description in the DESCRIPTION field.

  5. Enter a value in the PRIORITY field.

    NOTE: The value is the order the object displays on the Objects page’s Horizontal View.

    NOTE: When a Wave-Process Area uses the object, the object priority cascades down to Target Design. Once the target that belongs to the object is synced with Map, the priority is also available in Map and displays on the Objects page. The priority is also used in Transform, but can be updated in Transform on the Targets page to change the order the object is processed.

  6. Enter a COMMENT if necessary.

  7. Select a planning group from the Default Planning Group list box. The Default Planning Group displays on the Wave Process Area Object Planning Data page to filter objects based on the planning group.

    NOTE: Use this field to assign a default planning group to an object. When the object is assigned to a process area, and if the assigned planning group is associated with the wave, then the selected planning group is defaulted on the object. If the planning group is not assigned to the wave, then either the Default Planning Group is assigned, or if there is not a Default Planning Group, the planning group must be manually assigned.

  8. Click Save.

The object displays in the OBJECTID list box on the Process Area: Object page, and can be assigned to a Process Area.

An object can also be added by copying an existing object. Refer to Copy Elements for more information.

Once an object is added in Console, it can be viewed in Map and Transform.  If the object is deleted in Console, it no longer displays in Map and Transform. An object cannot be deleted if it is being used in Map or Transform in a data migration project.

Continue with Add a Load Cycle.

Add A Load Cycle

Migration projects run load cycles to test migration processes, support system testing and to cutover to new systems. A project's planned load cycles can now be reflected in the Stewardship Tier. Load cycles can be automatically applied to all new waves using the Auto Include feature. The Stewardship Tier delivers load cycles that cannot be deleted or edited, but users can add custom load cycles. Refer to Manage Load Cycles for more information about delivered load cycles.

To create a custom load cycle in Console:

  1. Click Elements > Load Cycle in the Navigation pane.

  2. Click Add.

    View the field descriptions for the Load Cycles page

  3. Enter a descriptive name in the NAME text box.
  4. Click the AUTO INCLUDE check box to automatically include the load cycle to all new waves on the Wave Load Cycles page.
  5. Enter a comment in the DESCRIPTION text box. that explains the purpose of the load cycle as a part of the migration process.
  6. Click Save.

Continue with Add a Planning Group.

Add A Planning Group

Planning groups are a logical grouping of data objects based on the order/priority in which they are worked. Planning groups allow a migration project to be broken down into smaller work packages that can be tightly managed and reported on. Based on the language used on the migration project, planning groups may look like:

  • Tier 1, Tier 2, Tier 3
  • Master Data, Transactional Data
  • Sprint 1, Sprint 2, Sprint 3

Planning groups are assigned to waves along with baseline start and end dates for the Design, Map and Build activities of associated Objects. Through the assignment to milestones, goals (threshold) can be set and activities tracked against.

To add a planning group:

  1. Select Console > Elements > Planning Group in the Navigation pane.

  2. Click Add.

    View the page description for the Planning Group page

  3. Enter a logical grouping name in the PLANNING GROUP field.
  4. Check AUTO INCLUDE to include the planning group on a new wave.
  5. Enter a brief description about the planning group in the DESCRIPTION field.
  6. Click Save.

NOTE: A planning group cannot be deleted if it is assigned to a wave.

Continue with Add Elements to a Wave.

Add Elements to a Wave

Once the process area, object, load cycles and planning groups have been added, they can be assigned to a Wave.

To add existing elements to a Wave:

  1. Click Waves on the Navigation pane.
  2. Click the Process Areas icon for a Wave.

  3. Click Add.

    View the field descriptions for the Wave: Process Areas page

  4. Select a Process Area from the Process Area ID list box.

    Or

    Click the + icon to open the Process Area page to manually create a new Process Area ID. Refer to Create the Context by Adding a Wave and Creating Elements for more information.

  5. Click Save.
  6. Click the Objects icon for the Process Area.

  7. Click Add.

    View the field descriptions for the Process Area: Object page

  8. Select an object from the OBJECT ID list box.

    Or

    Click the + icon to open the Objects page to manually create a new OBJECT ID. Refer to Create the Context by Adding a Wave and Creating Elements for more information.

  9. Select an object owner from the OWNER list box. This user has overall ownership of the object from a reporting perspective. This list box is limited to users who have access to any Console WebApp Group via a role to which they are assigned.

  10. Click Save.

  11. Select a data source from the DATA SOURCE ID list box.

    NOTE: The DATA SOURCE ID is the data source where target tables and Target Source tables are registered.

  12. Click Save.

  13. Click Waves on the Navigation pane.

  14. Click the Load Cycles icon for a Wave.

  15. Click Add.

    View the page description for the Wave Load Cycles page

  16. Select a load cycle from the LOAD CYCLE list box to assign a load cycle to the wave.

  17. Enter a date in the PLANNED START DATE field to document when the load cycle is planned to start.

  18. Enter a date in the PLANNED END DATE field to document when the load cycle is planned to end.

    NOTE: If the load cycle is assigned to a milestone, the milestone date should be greater than the load cycle’s PLANNED END DATE.

  19. Enter a date in the ACTUAL START DATE field to document when the load cycle actually started.
  20. Enter a date in the ACTUAL END DATE field to document when the load cycle actually ended.
  21. Click Save.
  22. Click Waves on the Navigation pane.
  23. Click the Planning Groups icon for a Wave.
  24. Click Add.

    25. View the page description for the Wave - Planning Group page

  25. Check the WAVE DEFAULT PLANNING GROUP check box to assign this planning group with the fined start and completion dates to all new objects.

  26. Enter a date in the DESIGN START DATE field to indicate the default date by which the target data design of objects assigned to the planning group are expected to start.

    NOTE: The date selected for the wave planning group default is copied to the wave process area objects that are assigned to the planning group.

  27. Enter a date in the DESIGN COMPLETION DUE DATE field to indicate the default date by which the target data design of objects assigned to the planning group are expected to be complete.

    NOTE: The wave planning group default is copied to the wave process area objects that are assigned to the planning group.

    NOTE: A wave planning group’s DESIGN COMPLETION DUE DATE must be equal to or greater than its DESIGN START DATE.

  28. Enter a date in the MAP START DATE field to indicate the date by which the field mapping of objects assigned to the planning group are expected to start.

    NOTE: The date selected for the wave planning group default is copied to the wave process area objects that are assigned to the planning group.

  29. Enter a date in the MAP COMPLETION DUE DATE field to indicate the date by which the mapping of objects assigned to the planning group are expected to be complete.

    NOTE: The wave planning group default is copied to wave process area objects that are assigned to the planning group.

    NOTE: A wave planning group’s MAP COMPLETION DUE DATE must be equal to or greater than its MAP START DATE and greater than its DESIGN COMPLETION DUE DATE.

  30. Enter a date in the BUILD START DATE field to indicate the date by which the build of objects assigned to the planning group are expected to start.

    NOTE: The date selected for the wave planning group default is copied to the wave process area objects that are assigned to the planning group.

  31. Enter a date in the BUILD COMPLETION DUE DATE field to indicate the date by which the build of objects assigned to the planning group are expected to be complete.

    NOTE: The wave planning group default is copied to the wave process area objects that are assigned to the planning group.

    NOTE: A wave planning group’s BUILD COMPLETION DUE DATE must be equal to or greater than its BUILD START DATE and greater than its MAP COMPLETION DUE DATE.

  32. Click Save.