Limited period discount :Sponsored Articles, Homepage Banners and News Release. Write to us - [email protected]
Uncategorized

SAP Risk Management for Steel Manufacturers: How to Handle Late Process Changes Before Go-Live

6 Mins read

Introduction

Five days before an ERP go-live, a steel service centre changes its rule for releasing reworked coils. The original process makes a coil available once rework is recorded. The revised process requires a second inspection. Quality has identified a gap, but planning has already allocated some of those coils to customer orders scheduled for the first week after launch.

What looks like one extra approval can affect inventory availability, delivery commitments, and work instructions already shared with shift teams. It can also create two groups of coils that need different treatment: those already in rework at cutover and those that enter rework after launch. The manufacturer has to decide whether it can implement and test the revised process in time, whether a temporary procedure will meet the requirement, or whether the change needs to wait.

Use SAP Risk Management to Decide Whether the Change Can Wait

SAP risk management starts with asking what would happen if the plant launched with the approved process. Ask the requester to demonstrate the issue using a test transaction, an open order, or an example from current operations. In the coil scenario, the first question is whether material could be allocated or loaded before the required inspection is complete. The second is how often the plant encounters that scenario and which shipments could be affected.

The SAP project management team should record the plant and transactions affected, the deadline for a decision, and the person authorised to make it. For SAP risk management, there are three practical options:

  • Implement before launch. Use this route when the current process prevents a critical transaction or leaves a required control unmet. Confirm that there is time to configure the change, retest the affected steps, and brief the shifts before cutover.
  • Approve a temporary procedure. Define how employees will meet the requirement until a permanent change is available. Name the person who performs the check, the independent reviewer where required, and the person who covers absences.
  • Schedule a later release. Use this route when the existing process can support day-one operations and the request would improve efficiency or visibility. Assign an owner and a review date so the request stays visible after launch.

Follow the Change Through Planning, Inventory, and Dispatch

SAP risk management should follow a representative coil through the revised process. If the coil remains on hold longer, can production planning still assign it to another order? Can dispatch add it to a loading list prepared before the hold? Who reviews existing allocations once the new rule takes effect?

This is where SAP supply chain management connects the quality decision to production and delivery commitments. Ask planners to check whether they can find substitute material of the required grade and dimensions, resequence work, or flag a shipment that may miss its planned date. Ask dispatch to verify which status staff actually consult before loading. A coil can appear on a loading list prepared earlier even after its current status has changed, so test the point at which staff make the final decision.

Use SAP governance risk compliance to review any change to approval authority. If the revised process allows the same supervisor to record rework and approve the second inspection, the control owner should determine whether that combination is permitted. If the plant requires an independent decision, test that the designated reviewer can access the inspection record and act when the primary approver is unavailable.

Decide How to Handle Coils Already in Rework

For SAP risk management, identify the records that will cross the cutover boundary. A coil may enter rework in the legacy system and undergo its second inspection after launch. Decide which status that coil should carry into the new system, where the original inspection evidence will be available, and who confirms that the migrated record reflects the coil’s physical condition and location.

Create a list of affected coils before the final migration. Include each coil’s identifier, current location, rework status, inspection status, and any order allocation. After migration, ask quality and stores to reconcile the list and assign each unresolved item to a named owner. When an affected coil is already reserved for shipment, tell planning and dispatch who will confirm its eligibility and by when.

The same review applies if the plant splits a coil or relabels it during rework. Check that the staff carrying out the second inspection can connect the new identifier to the source record. Otherwise, they may have the correct physical material but lack the evidence needed to release it.

Retest the Transactions That Depend on the Change

The SAP project management team should reserve time for the test cases that could affect the go-live decision. Run them with the access, reports, and equipment that staff will use after launch. Ask each team to demonstrate what it would do when the result differs from the expected one.

  • A coil passes inspection. Confirm that an authorised user can release it and that planning and dispatch can see the updated status before taking their next action.
  • A coil fails inspection. Verify that the hold remains in place. Check who reviews any existing allocation and how the team prevents the coil from appearing on an active loading instruction.
  • A coil crosses cutover. Confirm that the material identifier, rework status, and available inspection evidence carry through to the new process.
  • The regular approver is unavailable. Ask the backup to complete the decision using the permissions and equipment available on that shift.

Involve the SAP supply chain management team in the retest. Have planners demonstrate what they would do with the orders affected by a failed inspection. If they rely on a report that refreshes at set intervals, confirm how they will verify the coil’s current status before committing it to an order.

Review Temporary Access and Deployment Activity

SAP risk management should account for any temporary permissions needed to deploy or verify the change. Use SAP governance risk compliance to document the purpose, permitted activities, approver, expiry, and reviewer. Once deployment is complete, compare the configuration with the approved request and confirm that temporary permissions have been removed.

Where SAP Enterprise Threat Detection is in scope, confirm that the security team has coverage during the deployment window. If SAP Enterprise Threat Detection surfaces unusual activity involving a temporary account, the responder can compare the event with the authorised work and available system records. Give the responder a named project contact who can confirm the scheduled work, especially when deployment takes place overnight.

Prepare Shift Teams and Set a Decision Deadline

SAP change management should focus on what each role will do differently. Operators need to know where reworked coils should wait. Quality staff need to know what triggers the second inspection. Planners and dispatch teams need to know which status permits allocation or loading. Update the relevant job aids and ask employees from each affected shift to demonstrate the revised steps.

Set a deadline that leaves time to make the go-live decision before cutover starts. For SAP risk management, record the test evidence, any issue that remains open, and who accepts the remaining risk. If the second inspection works on the day shift but the night shift has no authorised backup, identify whether approved coverage can be arranged before relying on the process at launch.

If a temporary procedure is approved, use SAP governance risk compliance to record its scope and the conditions for ending it. The SAP project management team can track the permanent fix, while SAP change management can verify that affected crews understand when to switch to the permanent process. Review the first few affected transactions after go-live to see whether the procedure worked as intended.

Conclusion

SAP risk management helps steel manufacturers decide whether a late process change is ready for launch. Follow the change through open records, downstream transactions, and shift responsibilities before approving it. When the change affects material availability or customer orders, include SAP supply chain management in the decision so planners and dispatch teams can confirm how they will respond when a coil is held, released, or reassigned.

FAQ

How can a manufacturer tell whether a late change is critical?

Use SAP risk management to assess what would happen on the first operating day if the request were deferred. Give priority to changes that affect required controls, critical transactions, or confirmed production and shipment commitments.

Should the team retest orders already in progress?

Yes. Include at least one representative order or coil that starts under the previous process and finishes under the revised one. Verify that staff can find the records they need to make the next decision.

What makes a temporary procedure workable?

It needs a named owner, clear instructions for each affected shift, a way to record exceptions, and an end date or condition. Demonstrate it with the staff who will perform it before relying on it at launch.

How should teams communicate a change after training is complete?

Use SAP change management to update the instructions for the affected roles. Ask users and backup approvers to demonstrate the revised task before sign-off.

Can security monitoring help review late deployment activity?

Where configured for the relevant activity, SAP Enterprise Threat Detection can surface events for investigation. Compare those events with approved deployment records and temporary access authorisations.

1124 posts

About author
Andrew Sabastian is a tech whiz who is obsessed with everything technology. Basically, he's a software and tech mastermind who likes to feed readers gritty tech news to keep their techie intellects nourished.
Articles