Release Note Number (TVS7325540):-
Template
Revision History
|
Ver. No. |
Ver. Date |
Prepared By |
Reviewed By |
Approved By |
Affected Section & Summary of Change |
|
1.0 |
06th Mar 2025 |
Shriaysh M. |
- |
` |
Drafted the release summary of 06th March 2025 Points. |
Table of Contents
11. Risks & Limitations.
1. Purpose
This release includes several key updates and fixes across different transactions to enhance functionality and improve user experience. The changes include addressing issues related to pickslip & In Transit part data.
2. Scope
3. Definitions, Acronyms, and Abbreviations
|
Acronym |
Definitions |
|
PSARQ |
Part Sale Allocation Requisition |
4. References
NA
5. Release Overview
6. Deliverables in this release/Milestone
|
Release Items |
Identification and Version |
|
NA |
NA |
7. Tickets/Defects/Incidents Resolved
in the Release / Milestone
|
Sl No |
Defect ID |
Priority /Severity |
Description |
Defect Tracking System Reference |
|
1 |
#TVS5325516 |
P5 |
Pick Slip not getting Invoiced. Pick Slip No - PSARQ30105248486
|
|
|
2 |
#TVS3325506 |
P4 |
Please cancel Pick Slip- PSARQ30105248148 |
|
|
3 |
#TVS3225355 |
P5 |
Data issue for lubricant part numbers as attached.
|
|
8. New Functionality or Enhancement in the Release / Milestone
|
Sl No |
Functionality/ Enhancement |
Description |
Requirements Document Reference |
|
1 |
- NA |
NA |
|
|
Sl No |
Change Description |
Reference Document & section |
Requirements Document Reference |
|
1 |
|
|
|
|
2 |
|
|
|
|
3 |
|
|
|
|
4 |
|
|
|
|
Sr.No |
Areas of Concern |
Details |
|
1 |
Pickslip confirmed but not moving to Picklist, Invoice not getting done- Jyothi Motors - PSARQ30146243115, PSARQ30146243076; Moped House - PSARQ30105248486 |
This is happening due to backend exceptions while confirming the Pickslip. |
|
2 |
Not able to cancel pick slip PSARQ30105248148, PSARQ30105248494- Confirmed pickslip but not in picklist |
Duplicate with ID #1 |
|
3 |
Invoice issue - Incorrect customer mapping PSI3010524760 (PO 2024011969 mapped to Goyal Auto instead of KA Motors) |
Cause- There are two ways to create a PickSlip document: Using the shortcut and Through the Menu options. As per the audit trail, the APS user changed the Customer Name in the PickSlip document via the shortcut. During the screen loading time (network delay), the user forcefully changed the Customer Name in the Customer Code field, leading to a mismatch between the selected Sales Order customer and the final invoice customer. |
|
4 |
In transit data issue |
A. QA Known Finding – In stock position Report the part which are not transacted yet such part will not come in the report, whereas it is coming in pending GRN report. In this case both the report will not match.
B. Null PO – Supplier Invoice is coming against null PO in pending GRN report. Due to BSTNK
C. Trade Discount in decimal (Sale invoice Header)
In Sale Invoice Header system was not accepting the discount in decimal (eg. 10.5,0.5,0.3)
|
|
5 |
Combined Sale Order Issue – Related to acknowledgement and error. |
·The sale orders are restricted for pickslip creation without acknowledgement.
·If the user selects the sale order forcefully for which the acknowledgement has not received/ only error is received/ acknowledgement and error both are received, then the POMS will validate such sale orders while creating pickslip for combined sale order.
·The user has to remove the check from the errored-out sale order to proceed further in pickslip. |
11. Risks & Limitations
<This section should have any risks identified and limitations>