Click the Edit action to update an existing change request.
The Createaction is only available whilst this change request is active, that is, it is not at Closed status.
Click the Excelaction to export the list of all change requests in the database to a Microsoft® Excel spreadsheet file for further analysis. |
Click the List of change requests action to return to the list of all change requests in the database. |
Click the Impact analysis action to display a high level assessment summary in real time of the impact of this "change" on key commitment groups. Appropriate quantities and the financial implication in base currency of this change are displayed for each group. Access to detailed information for each individual transaction type is available after you select this action.
|
Click the Plan action to define or view the action plan that will deliver the scope of the requirements for this change request.
|
You can use the following actions to increment or increase the version of the product to reflect the changes being delivered by this change request. The following actions are only available when the following conditions are met:
This action is displayed if your organization manufactures the product on this change request. |
This action is displayed if your organization procures the product on this change request from a subcontractor. |
This action is displayed if the product on this change request is version managed but is not manufactured or procured from a subcontractor. |
You can only assign a single product code to a change request.
Only one "active" change request is permitted per product. This is to ensure a change to a product is either seen through to its conclusion and the delivery of that change, or the change request is closed.
In addition to the generic error messages, the following messages can appear during the entry :
Each change request applies to a single product code. You have two choices when raising a change request:
1 - if you know the product code, you type the code in the Product field (or you can select the required code).
2 - if you do not know the product code, you can provide a short description of the product in the Description (if product unknown) field. A subject matter expert will use your description to trace the correct product code and they will add it to the Product field. Once the Productfield has been populated the Descriptionfield will become unavailable for entry.
The change manager for this change request can only advance it through the change cycle when the correct product code has been identified and recorded.
Each change request applies to a single product code. Also, there can only be one "active" change request per product code. This means that if another change request is being processed for the product code on this change request you can only raise this change request. The status of this change request must remain as New until the other change request has been closed.
Why are you raising this change request? How significant is this change likely to be? Please select an appropriate value for this field to ensure the appropriate "change control" team can be assigned to review the business case for the requirements.
Each change request must have a nominated change manager (Change manager field). A change manager is an active Sage X3 user who has been approved for involvement in your company's CCM process. This means that the Active check box on their Sage X3 user record is selected and their "change manager" approval CCMCHGMAN - Change manager parameter (TC chapter, CCM group) is set to Yes. One "change manager" user should be nominated as the default change manager for all new requirements. You define the default change manager by adding their Sage X3 user code to the folder level CCMCMDEF - Default change manager parameter (TC chapter, CCM group) - but only after their user parameter has been set.
Each change request must have a nominated project manager or planner (Planner field). A planner is an active Sage X3 user who has been approved for involvement in your company's CCM process. This means that the Active check box on their Sage X3 user record is selected and their "planner" approval CCMPLANNER - Planner parameter (TC chapter, CCM group) is set to Yes. One "planner" user should be nominated as the default planner for all new requirements. You define the default planner by adding their Sage X3 user code to the folder level CCMPLADEF - Default planner parameter (TC chapter, CCM group) - but only after their user parameter has been set.
This message will be displayed if the Sage X3 user code selected is invalid. This might be because they are not an active Sage X3 user or because they have not been set up as having "CCM authorization". Parameters
To be able to assign an "approver" to this change request you must be logged in as the current change manager for this change request and the status of this change request must be In review.
This message is displayed by the batch server process whilst the impact analysis is being created or updated. It is also displayed if you attempt to refresh the screen whilst the impact analysis is being created or updated.
The creation of an impact analysis can take a few minutes if the process is reading a large volume of data. You can check the status of the batch server process using the Query management function (AREQUETE). You can view the impact analysis when it shows the status Finished.
You can only assign this attachment to the Rejection category if this change request is being or has been formally rejected. To do this the status of this change request must be set to Rejected.
Why are you rejecting this change request? Please select the reason in the Reason for rejection field to ensure the decision made by the "change control" team is recorded formally. You are advised to expand upon the selected reason in the Additional information field.
Each change request must follow the standard processing cycle.
For a change request that will be processed through to completion the standard cycle is: New > In review > In planning > Being implemented > Completed > Closed.
For a change request that will be rejected the standard cycle is: New > In review > Rejected > Closed or New > Rejected > Closed.
The current stage in the processing cycle is displayed in the Status field. Controls are in place to ensure a change request can only advance to the next stage in the processing cycle when the current stage is completed. For example, the action plan must have been implemented in full before the status of a change request can be advanced to Completed.
Selected stages in the processing cycle allow the status of the change request to be reverted back one stage, for example, from Being implemented to In planning. There can, however, be consequences in doing so. Please ensure you are aware of these consequences before taking this action.
The email address on the user record is either missing or incorrect. Email notifications cannot be sent to this user.
You can only add a contact that is associated with the selected customer or supplier.
You can only delete lines if you are logged in as the current change manager for this change request.
The following tables are implemented by the function :
Table | Table description |
---|---|
CCMCHGREQ [CCMCR] | Change request |
CCMCRDESC [CCMCRD] | Change request description |
CCMCRNOTES [CCMCRN] | Change request attachments |
CCMCRORIGC [CCMCROC] | Customer originators |
CCMCRORIGE [CCMCROE] | External originators |
CCMCRORIGI [CCMCROI] | Internal originators |
CCMCRORIGS [CCMCROS] | Supplier originators |
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 |
CCMPLAND [CCMPD] | Change request plan detail |
CCMPLANH [CCMPH] | Change request plan header |
CCMREJDSC [CCMREJ] | Rejection description |
CONTACTCRM [AIN] |
Refer to documentation Implementation