Do you have any question about this t-code?
Transaction Code: CI12
Description: Deviation Record.-Selection Variants
Release: S/4HANA and ECC 6
Program:
Screen: 0
Authorization Object:
Development Package: CIIC
Package Description: CIM integration: Customizing
Parent Package: APPL
Module/Component: PP-PI
Description: Production Planning for Process Industries
Overview: The SAP transaction code CI12 is used to create and maintain deviation records in the SAP system. It is used to store information about deviations from the standard process or product specifications. This transaction code is part of the Quality Management (QM) module. Functionality: The CI12 transaction code allows users to create and maintain deviation records in the SAP system. It stores information about deviations from the standard process or product specifications. This includes details such as the type of deviation, the cause of the deviation, and any corrective actions taken. The CI12 transaction code also allows users to create selection variants for deviation records, which can be used to filter and display specific records. Step-by-step How to Use: 1. Enter the transaction code CI12 in the command field. 2. Select “Create” to create a new deviation record. 3. Enter the details of the deviation, such as type, cause, and corrective action taken. 4. Select “Save” to save the record. 5. To create a selection variant for deviation records, select “Variants” from the menu bar and then select “Create”. 6. Enter a name for the selection variant and select the fields you want to use for filtering and displaying records. 7. Select “Save” to save the selection variant. 8. To view all deviation records, select “Display” from the menu bar and then select “All Records”. 9. To view only specific records, select “Display” from the menu bar and then select “Selection Variant” followed by your selection variant name. Other Recommendations: It is recommended that users familiarize themselves with all of the features of this transaction code before using it in production environments. Additionally, users should ensure that they have appropriate authorization levels before using this transaction code in order to prevent unauthorized access to sensitive data.