| # Blocking operations Introduction Sometimes a problem occurs that must be solved before an operation proceeds. Examples of such situations are: The quality of an intermediate product must first be inspected. A machine is in repair. A supplier cannot deliver an essential component in time. A customer is late with its payments. In these situations the operation can get the operation status Blocked. An operation can be blocked: Manually. Automatically by Quality Management. Blocking reasons Every blocked operation must have a blocking reason. The blocking reason of a blocked operation has two purposes: To indicate why the operation is blocked. To determine which actions you can no longer perform on the operation. Types of blocking The following actions can be blocked by means of a blocking reason: Reporting a quantity completed. Reporting a quantity rejected. Reporting a quantity to be inspected. Reporting an operation completed. You normally carry out these actions in the Report Operations Completed (tisfc0130m000) session. You can define blocking reasons in the Blocking Reasons (tisfc2100m000) session. Manual blocking Use the Report Operations Completed (tisfc0130m000) session to block an operation. When you block an operation, you must also enter a blocking reason. If Quality Management has already blocked the operation, you can only enter a blocking reason, which is more restrictive than the blocking reason of Quality Management. Blocking by Quality Management Quality Management uses the blocking reasons specified in the Quality Management Parameters (qmptc0100m000) session, to block operations. For details, see the Using QM for manufacturing operations topic. Note The Blocked Operations (tisfc0540m000) session displays the blocked operations. Related topics Using QM for manufacturing operations Operation status Defining blocking reasons for QM |