¢ Business Process Document ADF CEM.QM.01.01.01 Raw Material Incoming inspection Version 1.0 Page 1 of 9Business Process Document ADF 1 Revision History Document Approvals Document References. TABLE OF CONTENTS Document Administration Business process summary Business Background Business Process Steps. Process flow chart Prerequisites . : Standard Reports available with this process. Special Organization Considerations. Changes to Existing Organization Improvements to existing business processes Listing of Functional Deficits. Approaches to covering Functional Deficits. System Configuration Considerations Interface Considerations. Any document / output printed for this business process. Development requirements for business process Test case. OOOOCOCOHOOMRHMONEADRYWYW Page 2 of 9Pome Taosa Business Process Document ADF 1, Document Administration Revision History Version | Date Author Changes with respect fo previous version 70 TA Document Approvals Date [Name Role Signature Wipro Consultant Core Team Member Business Process Owner Project Manager (Client) Project Manager Wipro Document References Sl.No. | Document Name Description Location ‘ADF SharePoint Page 3 of 9pated Business Process Document ADF 2. Business process summary Major Process: QM in Procurement to Payment ‘Sub Process: {Quality Inspection for Incoming Material Process Id ‘CEM.QM.01.01.01 Raw Material Incoming inspection 3. Business Background Quality Inspection component is used to determine whether Incoming Cement Raw-Material, consistently meets defined quality requirements. In Cement Industry quality inspection, we inspect an Incoming Raw-material, using inspection specifications that have been predefined in the Inspection planning component. Although the inspection results only document the current quality of Incoming Cement Raw-material, this information is also useful for quality control (for example, to optimize future Processes) Incoming Raw materials include Crushed Limestone, Coal, and Engineering Spares. Figt: Crushed Limestone. Fig2: Coal Page 4 of 9Business Process Document ADF 4. Business Process Steps Step No Description of Activity 7 Process Carried out Proposed Process details Goods Receipt against Purchase Order ‘Goods Receipt for the respective Purchase order will be performed after confirming the gate entry and MIGO transaction will be performed T code MIGO SAP R/3 menu Logistics > Materials Management-> Inventory Management Goods Movement >MIGO - Goods Movement (MIGO) + GRis done through T-code MIGO- Generates a Material Document Number. ‘+ Sample will be send to Quality department and in other cases Quality department will collect the sample. + Ifthe material is stock relevant, it can be viewed in MMBE transaction w.r. material and plant ‘= During MIGO (Goods receipt) transaction a check on certificate hard copy received with consignment can be recorded by activating Q-INFO Record + If Certificate is not received from vendor, GRN should be possible with the warning message. Certificate check and confirmation will be confirmed before: Usage decision activity else posting will not be performed. © Aqquality certificate certifies the quality of goods inspected for an inspection lot confirming with the Quality data for output of Hard copy. ‘+ Hard copy received from vendor to be mentioned at the time of GR processing Page $ of 9Business Process Document ADF 2 Inspection lot creation “An automatic Inspection Lot willbe generated during Goods receipt transaction by the system ‘© Lot Number along with GR no can be viewed in QA33 ‘© Inspection Instruction and sample drawing procedure can be printediviewed through this transaction + PO, GR details like quantity, package & samples can be viewed through this transaction T code QA33 SAP R/3 menu Logistics > Quality Management Quality Inspection >Work lst inspection >QA33 - Display Data Results Recording With respect to the inspection lot is the reference object you can record / Process the results for an inspection characteristics ‘The recorded inspection results document the quality of the inspected incoming Raw materials, and provide the basis for specifications and inspection certificates. You can use the recorded result data to make evaluations for quality control purposes Quality Lab dept. will record the results T code QEO1 SAP R/3 menu Logistics > Quality Management Quality Inspection > Inspection Result > For Operation QE01 - Record ‘= Follow the Sampling/ Results Measurement as mentioned in Inspection Instruction. + Each MICs will be valuated based on the tolerance limit defined in the each control indicators of MICs. ‘+ Deviated valuation will be highlighted through different Icon, 4 Defects Recording (Record for Non-Conformance) A defect is any property or attribute of a incoming raw materials that does not meet the inspection characteristic specifications. You record the defects with the help of predefined defect codes ‘maintained in the inspection catalogues. In case of any MIC rejection during results recording based on tolerance limits of the MIC valuation auto Defects Recording will be done as per master data setting, This can create a background Quality notification against vendor (F2 or any other relevant notification type) to follow up with Store/vendor dept. T code QF11 SAP R/3 menu Page 6 of 9Business Process Document ADF Logistics > Quality Management >Quality Inspection > Defects > Record for Inspection Lot 9QF11 - Defects Record Creating/Processing Quality Notification (Non-Conformance Report Processing) Notification functions for recording and processing different types of problems (for example, problems resulting from poor-quality goods or services). Notifications can be used to analyse the recorded defects and monitor the correction of these problems, In particular, the notifications can help you process internal or external problems. + Defects Recording will lead to the creation of Notifications automatically in the system. ‘+ Notification contains the functionalities: Mail, Prints, Letter to Vendor, and Attachments fora file etc. T code QMO1 SAP R/3 menu Logistics > Quality Management > Quality Notification > Create >OMo1 54 Copy reference data in to Notification Each quality notification type deals with different reference objects A reference object has a relationship to the problem in a quality notification. T code QMOt SAP R/3 menu Logistics > Quality Management > Quality Notification > Create QM01 (Reference Object tab page) 52 Describe Problem notifications in Subject In this process, you see how a defect determined during quality inspection is analysed and documented in a quality notification, T code QMOt SAP R/3 menu Logistics > Quality Management > Quality Notification > Create >QMO1 (Subject tab page) 53 Action plan for the Defect, ‘A task is the activity planned for the nolification. A task can be assigned and can have a slart time and end time to it T code QMO1 SAP R/3 menu Logistics > Quality Management > Quality Notification > Create QM01 (Task tab page) 54 Change Quality Notification The list called up by the system contains all outstanding complaints against vendors. These notifications exist, because you created defect data records and thereby activated a notification in the QM T code QM10 SAP R/3 menu Logistics > Quality Management > Quality Notification > Work list > Notification >QM10 - Quality Notification Change Data Page 7 of 9Business Process Document ADF ‘Select the item you processed last and choose the Causes tab page. To document the steps you have taken as a result ofthis defect, choose the Activities tab page. 5.5 | Processing Quality Notification T code QMO2 SAP R/3 menu Logistics > Quality Management > Quality Notification > Change ‘Add the information fo the long text. The system records that you have finished processing the task. T code QM12, SAP R/3 menu Logistics > Quality Management > Quality Notification > Work list > Notification Task > Change data 5.6 | Completing corrective task ‘The nolfication can no longer be changed, only displayed T code QMo2 SAP R/3 menu Logistics > Quality Management > Quality Notification > Change 5.7 | Completing the notification 5. Process flow chart uy ws) IncainginepectionInprocessnspecton bie Stone and Oto Raw Weal Cink c 6. Prerequisites + Ensure all Master data related to Quality, Characteristics, Plan, Method codes & catalogs are maintained + Inspection indication should be maintained in Quality Management of material master + Quality planning assignment to the material should be in order. 7. Standard Reports available with this process * Quality Inspection report — QA33, QGAZ + Results Print out report - QGA3 * Defects Reports — MCXX, MCVX * Quality Notification List - QM11, MCXV 8. Special Organization Considerations + This is to be documented during implementation (In this you can identify specific to this process any specific considerations require for a particular organization. If yes provide the Page 8 of 9Business Process Document ADF details, if no mention *Not Applicable” 9. Changes to Existing Organization 10. 11. 12. 13. 14. 15. 16. 17. * This is to be documented during implementation. (In this section mention the changes in process after implementation with respect to existing practice) Improvements to existing business processes * This is to be documented during implementation, (In this section mention the improvements inthe process with respect to legacy system) Listing of Functional Deficits * This is to be documented during implementation. (In this section mention if any requirement related to tis process cannot be mapped) Approaches to covering Functional Deficits + This is to be documented during implementation. In this section mention the workaround solution or any development required to address the defict in the process, System Configuration Considerations + This sto be documented Interface Considerations * This is to be documented Any document / output printed for this business process * Print output for the Shop Floor Papers + Print output for GR document Development requirements for business process + This is to be documented during implementation. (In this section capture details of developments (enhancements, outputs form development), interface list as a result of all above points Test case * Refer test case document Page 9 of 9