<div><b>Acceptance Criteria for Goods Receipt with Purchase Order (PO):</b><br> </div><div><span style="font-weight:600;"><br></span> </div><div><span style="font-weight:600;">Integration:</span><br> </div><div><h4 style=""><span style="">&nbsp;1. SAP Integration:</span> </h4><ul style=""><li>The application must seamlessly integrate with SAP to fetch Purchase Order (PO) data and update Goods Receipt Note (GRN) records. </li> </ul><div><h4><strong>2. </strong>Draft Mode Functionality </h4><ul><li><strong>&nbsp;Draft Creation:</strong><br>Users must be able to create and save GRN records in draft mode without requiring all mandatory fields to be fully populated. </li><li><strong>Draft Editing:</strong><br>Users must be able to edit saved drafts. However, once a GRN is submitted, it should be locked from further editing. </li><li><strong>View-Only After Submission:</strong><br>After submission, the GRN should become view-only, with any subsequent changes restricted to viewing mode. </li> </ul><div><h4><strong>3. GRN Creation and Editing</strong> </h4><ul><li><strong>Mandatory Fields Input:</strong><br>Users must be able to create a new GRN by inputting the following mandatory fields: Goods Receipt Type, Reference Number, Invoice Number, GRN Date, Item Code, UOM, and Receive Quantity. </li><li><strong>GRN Date Management:</strong><br>The GRN Date should auto-populate with the current date, but users must have the option to edit it. </li><li><strong>Quantity Validation:</strong><br>The Receive Quantity field must be validated to ensure it does not exceed the Order Quantity and after decimal should have only 2 Zeros. </li> </ul><div><h4><strong>4. Mandatory Fields Validation</strong> </h4><ul><li><strong>GRN with PO Type Validation:</strong><br>The following fields must be mandatory when the GRN type is &quot;GRN with PO&quot;: </li> </ul><ol><ol style="list-style:lower-alpha;"><ol style="list-style:lower-roman;"><li><span style="">Goods Receipt Type</span> </li><li><span style="">Reference Number</span> </li><li><span style="">Invoice Number</span> </li><li><span style="">GRN Date</span> </li><li><span style="">Item Code</span> </li><li><span style="">UOM</span> </li><li><span style="">Receive Quantity</span> </li> </ol> </ol> </ol><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Other fields where displayed while choosing PO number </div><div><ol><ol style="list-style:lower-alpha;"><ol style="list-style:lower-roman;"><li><span style="">Currency</span> </li><li><span style="">Supplier Name</span> </li><li><span style="">PO Date</span> </li><li><span style="">Item Image</span> </li><li><span style="">Conversion Factor</span> </li><li><span style="">Unit Price</span> </li><li><span style="">Order Quantity</span> </li> </ol> </ol> </ol> </div><ul><li><strong>Error Messaging:</strong><br>The application should prompt clear error messages if any mandatory fields are missing or invalid upon GRN submission. </li><li><strong>Data Accuracy:</strong><br>These fields must display accurate data corresponding to the PO selected by the user.<br> </li> </ul><div><h4><strong>6. Traceability</strong> </h4><ul><li><strong>Traceability Options:</strong><br>The application must allow users to specify if an item is a Normal Item, Serial Item, Batch Number, or requires an Expiry Date. </li><li><strong>Mandatory Traceability Information:</strong><br>Traceability information must be mandatory </li> </ul><div><b>7. Line Items Handling<br></b> </div><div><ol><li>The application must allow users to add, edit, and view line items within a GRN. </li><li>Each line item must include Item Code, Item name, UOM, Conversion Factor, Unit Price, Order Quantity, and Receive Quantity. </li><li>Users must be able to review a list of all line items added to a GRN before saving . </li> </ol><div><b>8. Submission and Finalization</b><br> </div> </div><div><ol><li>The application should validate all mandatory fields and ensure that all line items meet the required criteria before allowing submission. </li><li>Once a GRN is successfully submitted, it should be marked as finalized with a status change from &quot;Draft&quot; to &quot;Submitted&quot; and become non-editable. </li> </ol><div><b>9. Viewing and Navigation</b><br> </div> </div><div><ol><li>Users must be able to view a list of draft GRNs, displaying key details such as GRN number, supplier, and date. </li><li>Users must be able to navigate seamlessly between the list view, GRN creation/editing screens, and detailed line items view. </li><li>The application should ensure that the correct GRN data is displayed based on user selections and actions. </li> </ol><div><b>10. Error Handling and Alerts</b><br> </div> </div><div><ol><li>The application should provide clear and actionable error messages for any validation failures during GRN creation, editing, or submission. </li> </ol> </div><div><br> </div><div><b>**Note: Follow screenshots and Tables (fields) are listed in FSD**</b> </div><div><div style=""><br> </div><div style="font-weight:bold;"><span style="font-size:11.04pt;font-family:Calibri;color:rgb(0,0,0);"> </span> </div><br> </div><div><br> </div><br> </div><br> </div><br> </div><br> </div><br> </div>