Impact analysis

Use this function to help with the question “If we make this "change", what impact will it have on us and our marketplace?”.

You can access this function from the Change control menu or from the Action panel in a change request.


Changes to products being prepared for, or currently in the marketplace can have a significant impact on current and future sales, and profits. The ability to evaluate the "impact" of any request for a "change" is critical, therefore, in the assessment of the business case for the requirements.

This function supports the assessment process by providing easy access to data associated with a request for a design or a production "change". With quick and easy access to the business case, and snapshot, dynamic commitment data available on request, this function offers a dual purpose:

  • Used as a risk analysis tool, it supports a change manager when determining if there's a business or technical justification for the modifications.
  • Used as a communications tool, it supports subject matter experts or members of a change control team identifying the potential consequences of that "change".

By providing this functionality from a single location, the Impact analysis function becomes a critical tool for making an informed decision. It provides direct access to the details of the business case for a specific "change" to a design or a production model. It also provides direct access to all current, and any future commitments associated with that design or production model. The risks associated with any potential modifications can therefore be assessed quickly and effectively as the key data is easily and readily accessible. All stakeholders can therefore carry out an initial assessment and comprehensive reviews when making their decision whether to approve or to reject the requested "change".

A Sage X3 Change Control impact analysis actually comprises multiple sets of analysis data:

  • The first set of analysis data is a high-level assessment of the impact a change to the product defined on a change request could have. This summary impact analysis shows for key groups of commitments, the "need to know", or key quantities that will be impacted by the change.
    If the change request is for a specific version of the product, the key quantities are adjusted. They’ll reflect the impact on the specified version plus those commitments where a version has not been specified and the version is blank.
    Where appropriate, the financial implication in the base currency of that change is included.
  • Where a commitment group in the summary impact analysis contains analysis figures, detailed analysis data can be displayed for the commitments that will be impacted. The data provided includes summary totals and a list of the individual commitments that will be impacted by the change.
    If the change request is for a specific version of the product, the detailed analysis data will be adjusted as for the summary impact analysis. The data provided will be for the specified version plus those commitments where a version has not been specified.

For version managed products especially, this approach provides a safety net and peace of mind throughout the change cycle that no commitments have been overlooked. This is especially important where the version of the product might not be known, either when a change request is created or until designated manually.

You can access key information from the summary and the detailed impact analysis using the standard Sage X3 functionality provided with selected fields. For example, you can jump to critical information associated with the change request and into the change request itself. From the displayed list of commitments you can jump to information such as the order details, partner, or site from which the transaction was created. Access to this level of detail supports gathering critical information in the assessment of the business case for a specific requirement. As a change manager or subject matter expert you’ll find it invaluable when assessing or reassessing the importance and urgency of the requirement.

For the purposes of Change control management, a "commitment" is a key Sage X3 transaction type, for example, sales orders or work orders. A commitment group is a related set of those transaction types (commitments) such as sales and purchasing, manufacturing, or stock. An individual commitment needs to have one or more open lines for the product defined on the change request to be included in the figures. In the manufacturing group, the individual commitments might be associated with the product defined on the change request.

To obtain or run an impact analysis, a change request needs to be at In review status.

Summary impact analysis

A summary impact analysis is a high-level assessment of the impact to your organization a "change" to the product defined on a change request could have.

You use the summary impact analysis to obtain a quick overview of the potential impact of the modification on specific channels. When assessing the business case for the requirements, it enables you to assess the potential consequences of a design or production change quickly and easily.

Each summary impact analysis is subdivided into the key groups of commitments or transaction types that could be impacted by the change.

Where the change will have an impact on the commitments in that commitment group, the key quantities that could be impacted are displayed.

Where the change is for a specific version of the product, the quantities reflect that version plus those where the version is not specified.

A specific version of the product is where the major, or major and minor version has been specified.

Where the key quantities will have an impact financially, the financial implication in the base currency is displayed.

The summary totals are repeated and displayed with each detailed impact analysis. To obtain a detailed impact analysis for a specific commitment, select the appropriate action in the Action panel.

Detailed impact analysis

A detailed impact analysis identifies the individual commitments that could potentially be impacted by a "change" to the product defined on a change request.

You use the detailed impact analysis to assess the extent of the change.

A detailed impact analysis reproduces the totals from the summary impact analysis for a selected commitment or transaction type. It also lists the individual commitments or transactions that have one or more open lines for the product defined on the change request.

Where the change is for a specific version of the product, the commitments listed are as follows:

A specific version of the product is where the major, or major and minor version has been specified.

  • Those commitments that have one or more open lines for the version of the product specified.
  • Those commitments that have one or more open lines where the version of the product has not been specified and the major or minor version is blank.

The analysis details include the following:

  • The transaction destination or origin, for example, the customer or the supplier
  • The transaction quantity
  • The financial implication in both the folder and the base currency, where applicable
  • The status of the transaction line and of the transaction itself
  • Relevant dates

Running an impact analysis

As the number of change requests in your organization’s database could be significant, the way you access this function determines how best to use it:

  • If you access this function from the change request itself using the Impact analysis action, a high level assessment or summary impact analysis is displayed. You can obtain a detailed impact analysis for each commitment by selecting the appropriate action in the Action panel.
  • If you access this function directly from the menu, all change requests at a minimum status of In review are displayed in a grid or table. You can find a specific change request quickly and easily by reordering the data, switching the columns, and applying filters to the columns. Use the standard Sage X3 functionality available on every row to select your change request from the final filtered list. The high level assessment or summary impact analysis will display for your selected change request. You can obtain a detailed impact analysis for each commitment by simply selecting the appropriate action in the Action panel.

An impact analysis displays a snapshot view of the data associated with the product on a change request at the point that it's run. The data might, therefore, reflect the point at which the change request was advanced to the In review stage of the processing cycle. Alternatively, it might reflect the point at which the change manager for the change request regenerated it manually.

You can manipulate the results of a detailed impact analysis using the standard Sage X3 query functionality. With the query functionality you can reorder the data, switch the columns, and apply filters to the columns. There are no restrictions on the number of times that you can run or clear filters or sort orders, or move columns. You can manipulate the data until the results you need are displayed.

An impact analysis can only be refreshed or updated by the change manager and only while the change request remains at In review status. If you’re a subject matter expert, this does mean you can request revised data if you need it. If a detailed impact analysis is updated, the key quantities and figures for that specific commitment on the summary impact analysis are also updated.

If you’re viewing an impact analysis when the change manager updates the snapshot data, select the standard browser Refresh (F5).

After the status of a change request has advanced beyond In review status, for example, to the planning stage and In planning status, it cannot be refreshed. The impact analysis remains fixed at the In review results.

Blocking transactions

A potential consequence of a "change" can be that processing transaction lines associated with a specific change request needs to be halted, or blocked. If this becomes necessary, you need to manually block the transaction lines affected by the requirements.

Manual blocking is different for the different transaction types. Purchase order lines, for example, can be closed if the supplier has not shipped the goods. Sales order lines can either be closed or the stock deallocated. You need to choose the most suitable blocking method for the type of transaction.

The detailed sales orders impact analysis displays the quantities processed at each stage of an order’s preparation and delivery cycle. This information helps if you have to make a blocking decision against a sales order line.

You’re advised not to reactivate a blocked transaction until the approved scope for the change request has been delivered in full. This will not be until the action plan has been implemented and the change request is complete.

Prerequisites

See also  Refer to documentation Implementation

Screen management

The commitment groups Sales and purchasing, Manufacturing, and Stock are a related set of "commitments" or key Sage X3 transaction types.

Where a "change" to the product defined in the home section impacts the commitments, the key quantities that could be impacted are displayed.

An individual commitment needs to have one or more open lines for the product defined in the home section to display figures. In the manufacturing group, the individual commitments might be associated with the product defined in the home section.

Action panel

A change request needs to be at In review status for the selected action to provide dynamic, transactional data.

Return to request

Select the Return to request action to display the business case for the change request. The full details of the change request itself.

List of change requests

Select the List of change requests action to return to the full list of change requests in the database.

The following actions display the list of commitments for the selected commitment type that have one or more open lines for the following:

  • The product, or the specific major or minor version of the product on the change request.
  • Where the product version has been specified, those commitments where the version of the product has not been specified and the major or minor version is blank.
  • An assembly associated with the product, or the specific version or revision of the product on the change request. This includes lines where the product or product version on the change request is a component or subassembly of a bill of material (BOM). All commercial sales, production, and subcontract BOMs are included.

Where there are variations, this is explained below with the action.

Sales orders

You can jump to the Journal traceability inquiry (CONSPIV) function for each individual sales order in the displayed list to view its sales journal history log. This log traces the documents associated with the selected line, from the origin of the line (quotation, order, prepayment etc.) to the payment. If the Customer relation module is enabled, it traces the journals linked to CRM activities.

Sales quotes

Purchase orders


Purchase requests


Work orders


Sub contract orders


Demand forecasts

The forecast sales order quantities cover time horizons for each month. These are measured in weeks from the first of the month in which the impact analysis was created or updated. The calculations reflect those used by the Demand forecasts functions (Stock > Reorders > Demand forecasts (GESORZS) / Manufacturing > Planning > Demand forecasts (GESORZ)). Planned and firm sales order quantities are included in the figures.

The list displayed does not segregate those forecasts that are for a specific major or minor version of the product.

Stock

This action displays key stock status figures by site.

BOMs

This action displays a list of assemblies and subassemblies that are associated with the product on the change request. All commercial sales), production, and subcontract BOMs are included.

  • The sales BOMs are those used on sales orders.
  • The production BOMs are those used in cost calculations, work order management, Material Requirements Planning (MRP), and the Master Production Schedule (MPS).
  • The subcontract BOMs are those used on subcontract orders, in cost calculations, MRP, and the MPS.

This action only shows the assemblies and subassemblies on a summary line. The Level column displays the level the product on the change request is used in the assembly listed.

Routing

This action displays the list of routes, this is the sequence of operations, materials, and tools needed to produce or process a product that are associated with the following:

  • The product on the change request.
  • An assembly (BOM) associated with the product on the change request. This includes lines where the product on the change request is a component or subassembly put together using a route and the bill of material.

The list displayed does not segregate those routes that are for a specific major or minor version of the product.

You can jump to the following functions for each individual product in the displayed list using the standard Sage X3 functionality available on every line:

  • Routing management function (GESROU). You can use this function to inquire into (and if necessary, to update) the sequence of operations, materials, and tools in the selected route.
    From the Routing management function, you can also load the Multi-level routings function (VISUROUG) to display the multiple levels of the route in a graphical or tabular format.
  • Routing codes function (GESTRO). You can use this function to inquire into (and if necessary, to update) alternative routes for the selected master route.

The following actions are available from the commitment type selected above.

Return to summary

Select the Return to summary action to redisplay the high level assessment summary for the change request. The data is refreshed for you automatically.

You can access detailed information for a different transaction type after you’ve selected this action.

Update

Select the Update action to repopulate the displayed impact analysis with new snapshot, dynamic data. The figures for that commitment on the summary impact analysis are also updated. To display the updated lines, you need to select the standard browser Refresh (F5).

The Update action is only displayed when the following conditions are met:

  • The change request is at In review status.
  • You’re logged in as the current change manager for the change request.

Stock by site

This action is available after you’ve selected the Stock action.

Select this action to use the Stock by site report inquiry (CONSSFC) (Stock > Inquiries > Stock > Stock by site report). You can use this function to perform a detailed inquiry into stock levels listed by site for the product on the change request.

From the Stock by site report inquiry, the standard options available from the Action panel are also available. These ensure you can inquire further into stock levels by stock unit and status, stock that has not yet been allocated and stock management information.

The default user site (as defined in the User parameters) is displayed in the Site field when the Stock by site report function is loaded. You need to either type in or select the site to inquire upon. To inquire into stock levels for all the sites in which the product on the change request is defined, clear the field. The site code (if defined) on the change request is simply a memorandum field for the change request.

Error messages

In addition to the generic error messages, the following messages can appear during the entry:

Updating Impact analysis data. Please wait and then refresh this page.
or
Impact analysis data is currently being created by Batch Server Task: $1$. Please wait and then refresh this page.

This message is displayed by the batch server process while the impact analysis is being created or updated. It’s also displayed if you attempt to refresh the screen while 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). When it shows Finished status, you can view the impact analysis.

Tables used

See also Refer to documentation Implementation