Ideas

Consider a scenario: User scans a global credit note (Note: The credit note gets locked in web). Now if while clearing the bill/closing the software/system shutdown, the credit note doesn't get unlocked due to no web database connectivity/didn't try to connect, etc. This will lead to support calls for changing the locked CN's state to unlocked state.

Failure Reasons:

1. Removing Adjusted CN (Web DB connection fails)
2. Clearing bills (Web DB connection fails)
3. Bill held (Web DB connection fails)
4. Application Closed
5. System shutdown

Solution [Discussed between RBR, SIDD, Arpita Bhattacharya]:

• Allow to select locked credit notes as well BUT THE ONES WHICH ARE LOCKED FROM THAT STORE ITSELF.
• Before saving the bills, system will check the existence of GlobalPOSBillCNNo in local table and that too its adjustment status [to handle GCN issued and being adjusted in the same store]. If exists and adjusted, system will restrict bill saving, else, it will allow saving of the bill and normal process will follow.
• Note: The aforesaid changes will be done for POS Bill, Collection Bill, GV Bill, Deposit Bill [from all modules], Refund Bill.

ASSUMPTION: If still locked credit note doesn't get unlocked due to any of the above scenarios and the credit note is tried to be adjusted in any other store, the credit note won't be allowed to be adjusted and support call will be logged for the same.