Refer to documentation Implementation
The Non-conformance Actions function contains a single screen for creating and managing 'actions'.
Presentation
You use this screen to match (or link) business processes commonly carried out within your organization with specific types of business transactions. The resulting matched, or linked business process (action) plus transaction type is identified by a unique code which you assign manually. This gives you complete control and flexibility over your identification codes. The code is used in Non-conformance Action plans.
You can link multiple actions (processes) with a single transaction type. You must assign each linked transaction type plus action a unique code.
Consider creating 'catch-all' or 'include-all' actions. For example, you could match the description 'Block' with a transaction type 'All'. These associations would give planners (project managers) unlimited or unrestricted scope in terms of your business setup or your business activities for their planning schedules.
Close
Fields
The following fields are present on this tab :
| Use this field to identify this 'action'. Type in a value which must be unique. 'Action' is the general term given to a business process that has been matched, or linked with a specific type of business transaction. Planners (project managers) will append individual action codes to their planning schedules to deliver a requested preventive or corrective 'change'. |
| Use this field to identify a standard business process which is commonly carried out in your organization for a specific type of transaction. For example, if your company disassembles faulty products to reuse the component parts, you could select a value 'Disassemble'. To be available for a Non-conformance management Action plan you must match, or link an action (business process) with a type of transaction, for example, you could link your value 'Disassemble' with the transaction type 'BOMs'. The resulting matched, or linked, business process plus transaction type is given the general term 'Action'. Each 'Action' should reflect a 'process' commonly carried out within your organization. The list of actions (business processes) is defined in Miscellaneous table 806 - Actions. |
| Use this field to identify a type of business transaction which is commonly carried out in your organization. For example, if your company returns faulty purchased goods to the supplier select the value 'Purchase orders'. Transaction types are used with Non-conformances that need Approvers (reviewers) input. Transaction types are also used with Non-conformance management Action plans. To be available for an Action plan you must match, or link a transaction type with an action (business process), for example, you could link the value 'Purchase orders' with a 'returns' action such as 'Return to supplier'. The resulting matched, or linked, business process plus transaction type is given the general term 'Action'. Each 'Action' should reflect a 'process' commonly carried out within your organization. The list of transaction types is defined in Miscellaneous table 807 - Transaction type. |
Close
In addition to the generic error messages, the following messages can appear during the entry :
The value you have entered in the field does not exist in the Miscellaneous table associated with the field. Either enter a different value or add the record you require to the Miscellaneous table (Miscellaneous table 806 - Actions or Miscellaneous table 807 - Transaction type).
The Action (field TRANACTION) and Transaction type (field TRANTYPE) are already linked under a different code (field ACTIONID). You cannot duplicate linked business processes (actions) and transaction types under different codes.