Plan - Implementation

Prerequisites

Activity codes

Functional

  CCM:  Change control management

  ECC:  Product version management

General parameters

The following general parameters can change the way the function is working:

Common Data

  CCMDEPT (defined at level User): Department

  CCMEMAILAC (defined at level Folder): Email actioner

  CCMEMAILCM (defined at level Folder): Email change manager

  CCMEMAILP (defined at level Folder): Email planner

  CCMPLANNER (defined at level User): Planner

  CCMROLE (defined at level User): Role

Authorizations

This function is object managed. The creation, modification, and cancellation operations can be activated or deactivated for a given user. Filters by roles can also be associated with this function.

Users

All employees that are permitted to be involved in your Change Control Management (CCM) process need to have an active Sage X3 user record. The checkbox X3 connection on their User record (Users (GESAUS)) needs to be selected as this provides connection rights to Sage X3.

Visibility of and access to change requests is controlled using the standard Sage X3 user profile and access functionality:

  • Access to a change request is controlled through the user’s profile. Their profile is defined on the General section of their user record and controlled through the permissions defined for their profile code (Function profile (GESAFT)).
     For unrestricted visibility and access to change requests, users assigned to the following CCM roles should have administrator rights:
  • Access to specific roles in your Change Control Management process is controlled through parameters. Roles are assigned and approved in the Parameters section of the user record (TC chapter, CCM group).
  • For users that do not have administrator rights, access to selected fields on a change request is controlled through the user’s access codes. These are specified in the Access section of their user record.
  • The user’s functional profile also controls their site access and therefore the individual change requests visible to them.
    You need to ensure your users have site access for Change control management, if you restrict your users’ access to Sage X3 by site. Site authorization is defined using the Functional authorisation (GESAFP) function for the function code GESCCM (Change request).
    With site authorization set up, visibility of and access to individual change requests will be determined by the Site field on the change request, as follows:
    • If the Site field contains a value, the users assigned to the CCM roles above need to have a profile code which has approval for the defined site.
    • If the Site field is blank, that is, the change request is valid for multiple sites, the users assigned to the CCM roles above will have unrestricted visibility and access to the change request. The users assigned to the following CCM roles need to, however, have a profile code which has approval for the transaction site.

      • Approvers: Site authorization will be required for each transaction type to which an approver user will be assigned.

      Actioners: Site authorization will be required for each transaction site to which an actioner user will be assigned.

  • The user’s menu profile needs to provide access to the Change control functions appropriate to their role in your CCM process.

Other prerequisites

Tables to be completed

The following tables are used by the function. Their content needs to be updated if necessary:

Table

Table description

CCMACTION [CCMACT]

Actions

AUTILIS [AUS]

Users

Local menus

The following parameterizable local menus are used by the function. Their content needs to be updated if necessary:

  Local menu number 2032: Actions

  Local menu number 2036: User Role

  Local menu number 2037: User Department

  Local menu number 2039: Transaction type

  Local menu number 2055: New planner email text

  Local menu number 2063: Plan complete email text

  Local menu number 2066: Actioner email text

  Local menu number 2067: Old planner email text

 Local menu 2039–Entity: This local menu is intrinsically linked to the Change control Plan function. Do not amend or delete the existing values in this menu. If your organization requires additional transaction types or entities for action plans you can add new codes and messages starting at value 16.

Email notification texts

The text contained in a notification email is defined in the local menus listed above (Local menu titles suffixed email text). You can amend the text as required.

  • Line number 1 (Code S) is the subject of the email.
    There can only be one line defined as a CodeS.
    The '$1$' part of the message is a parameter that is replaced by the Change Request ID at runtime, that is, when the email is triggered. Sage advises that you retain this parameter if you amend this message text.
  • Lines 2 to n (Code B), where n is the last line of the email text, form the body of the email.
    There is no restriction on the number of lines you can use in an email. You should, however, consider the length of the email if you add lines.
  • Line n+1, where n is the last line of the email text, is a system-generated uniform resource locator (URL) to the change request or implementation plan, as appropriate.
    This line is not available for amendment because the URL needs to be included by default in the email.

Tables used

The following tables are implemented by the function:

Table

Table description

CCMPLAND [CCMPD]

Change request plan detail

CCMPLANH [CCMPH]

Change request plan header