Subject: | Journal Lines and FMIS Ref is not generated for purchase of MISC item. |
Summary: | Hi Sanjay,
Journal Lines and FMIS Ref is not generated for purchase of MISC item. Set up - JIWA database - JIWA701 on QA1
- Linksoft database - LINKSOFTHQ
Steps to Replicate - On 233, set the Non-Inventory Posting Account code as :-
- RETAIL - Part No as "RETAIL" is created in JIWA. Posting Accounts are set.
- Create a PO with MISC item. Refer to HQPO000006.
- Receive the PO.
- Post PO from 577
- GL Journal View does not show the journals nor the FMIS. However, the status is completed. Refer to Figure 1.
Figure 1;
|
Audit Notes: | |
20 Feb 2018 | 04:01PM Comment 1 by Alvis (Link Technologies) Case 9118 added to project 8.3 |
20 Feb 2018 | 04:02PM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 20-02-2018 04:02 PM Time Taken: 1.00 |
| Hi Rashna, We have added validation to create Journal entries when there is any stock item received. If only misc items are received then journals are not created. regards Alvis |
|
20 Feb 2018 | 04:32PM Comment 3 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 20-02-2018 04:32 PM Time Taken: 1.00 |
| Hi Team, As per the Skype conversation with Alvis, the below has been discussed. - There is no journal for misc items purchased because it does not affect stock
- The posting account from "Non-Inventory Posting Account" is used to create the AP invoice for non-inventory
- The above has been verified in the system.
Case added to documentation que.
|
|
21 Feb 2018 | 09:44AM Comment 4 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 21-02-2018 09:44 AM |
| Please UAT in BETA4 as per comment 2. |
|
21 Feb 2018 | 03:46PM Comment 5 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 21-02-2018 03:46 PM Time Taken: 1.00 |
| Hi Sanjay, The case has been successfully tested. Refer to table 1 for details. Documentation has been completed under - Backoffice --> Purchasing --> Technical Reference --> Purchasing Configuration.
Please review and close the case. Thanks
QA Results Step 1 - Developer will perform test based on test cases provided Step 2 - Product expert to complete Product QA based on test cases.
Test cases are provided on the case header before the case is approved for development. Test Results Summary Scenario 1: Vaid Accounts No | Test Description | Pass/Fail | 1 | Create a Product as Retail in JIWA. Create a posting account as Retail in Link. Set valid GL codes. Set Non-Inventory Posting Account as RETAIL | Pass | 2 | Create a PO for item PNT01 ( Physical Item) 50@ $5.00 and for BAG (misc item) 50 @ $5.00. PO Total $408.75 Local Creditor.Receive PO
| Pass | 3 | Post PO from 577. This should create the Journal for the only item PNT01. Value 250 | Pass. Figure 1 | 4 | The Creditor Purchase should be created with the PO total amount of $408.75
| Pass. Figure 2
| 5 | Create another PO. Item - NAILP (misc item) Supplier - Foreign Purchase 100 @ 2.00 This should not create a journal as the stock is not affected. Creditor Purchase should be created with $200.00. No tax
| Pass, Figure 3 | 6 | Set Non-Inventory Posting Account as "blank". Copy the PO in 5 above. This should give error "Invalid GL" for AP Invoice | Pass | 7 | Set Non-Inventory Posting Account as "BASHOP". Copy the PO in 5 above. This should give error "Invalid GL" for AP Invoice as BASHOP is not a posting account
| Pass |
QA Environment Details - OS version:Windows 7
- Application version:9.2.4.0
- Database (Demo/New/Client): Demo- LINKSOFT on QA1
Steps to reproduce failed scenarios: Figure 1: PO with MISC and Normal Item Figure 2: Creditor Purchase for Local Creditor
Figure 3: Creditor Purchase for Foreign Supplier
|
|
21 Feb 2018 | 05:44PM Comment 6 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 21-02-2018 05:44 PM |
| Thanks Rashna |
|
09 Oct 2019 | 08:14AM Comment 7 by Sanjay (Link Technologies) Quality control status: Pass. QC Not required - This case was created before quality check was implemented in version 11 on 30/06/2019 |