Uploadsales.ksh Not Exporting Transaction's Revision After Store Day Exported Earlier
(Doc ID 2804374.1)
Last updated on SEPTEMBER 30, 2021
Applies to:Oracle Retail Merchandising Foundation Cloud Service - Version 19.1 and later
Information in this document applies to any platform.
POSU Reject files getting generated by SAEXPRMS when there are errors yet to be corrected in ReSA UI for the store/day. After Uploadsales.ksh process executed, the execution was marked as successfully completed. But these faulty POSU files were created on FILE_UPLOAD_STATUS with STATUS column as "F", and some records were created on FILE_UPLOAD_ERRORS table, with the code: "Invalid Value Added Tax (VAT) code.".
Later ReSA UI allows to correct that error in UI but those corrections are not getting exported which results in mismatch between MFCS and SA on quantities / net retails / and vats for these store/days.
Steps To Recreate:
1 - Create an RTLOG file containing a transaction with 2 items.
1a - For item A, set IGTAX with a VAT code that exists on VAT_CODES table.
1b - For item B, set IGTAX with a VAT code that does not exists on VAT_CODES table.
2 - Run SA's batch chain and notice the following:
2a - SA_TRAN_IGTAX.VAT_CODE column is set as "ERR" for item B
2b - A record was created on SA_ERRORS for Item B
2c - The transaction was exported and a line was created for it on SA_EXPORTED
2d - The generated POSU file has the VAT code field for Item B set as "ERR"
2e - The POSU file has FILE_UPLOAD_STATUS.STATUS set as "F"
2f - There's a "Invalid Value Added Tax (VAT) code." error on FILE_UPLOAD_STATUS for the transaction
2g - Item A was exported correctly to MFCS, but not Item B
3 - Correct the VAT code for item B on SA's UI
4 - Run SA's batch chain
5 - Notice that Item B was not exported and now MFCS has no record for its sale
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document