Impact analysis - Implementation

Activity codes

Functional

  CCM:  Change control management

  ECC:  Product version management

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.

Tables used

The following tables are implemented by the function:

Table

Table description

CCMIMPBOD [CCMIBOD]

Impact analysis-BOM lines

CCMIMPBOH [CCMIBOH]

Impact analysis-BOMs

CCMIMPFOD [CCMIFOD]

Impact analysis-Forecasts

CCMIMPFOH [CCMIFOH]

Impact analysis-Forecasts

CCMIMPITM [CCMIITM]

Impact analysis-Stock

CCMIMPITMDET [CCMITMD]

Impact analysis-Stock sites

CCMIMPMFGD [CCMMFGD]

Impact analysis-Work orders

CCMIMPMFGH [CCMMFGH]

Impact analysis-Work orders

CCMIMPPOD [CCMIPOD]

Impact analysis-Purchases

CCMIMPPOH [CCMIPOH]

Impact analysis-Purchases

CCMIMPPRD [CCMIPRD]

Impact analysis-Purchase req

CCMIMPPRH [CCMIPRH]

Impact analysis-Purchase req

CCMIMPROD [CCMROD]

Impact analysis-Routing lines

CCMIMPROH [CCMROH]

Impact analysis-Routing

CCMIMPSCD [CCMSCD]

Impact analysis-Subcontract

CCMIMPSCH [CCMSCH]

Impact analysis-Subcontract

CCMIMPSOD [CCMSOD]

Impact analysis-Sales orders

CCMIMPSOH [CCMSOH]

Impact analysis-Sales orders

CCMIMPSQD [CCMISQD]

Impact analysis-Sales quotes

CCMIMPSQH [CCMISQH]

Impact analysis-Sales quotes