SA_CREATE_RTLOG Job Is Not Processing Sale Transaction When Ref Item Not In The System (Doc ID 2931421.1)

Last updated on FEBRUARY 28, 2023

Applies to:

Symptoms

ACTUAL BEHAVIOR
---------------
SA_CREATE_RTLOG JOB NOT PROCESSING SALE TRANSACTION WHEN REF ITEM NOT IN SYSTEM

Whenever you are giving a barcode SKU that is not available in the system, the TITEM record in SVC_RTLOG_DATA_LOAD is updated as 'S' even though the store day is open and it remains the same.

On executing the SA_CREATE_RTLOG job it's not getting picked up or not throwing any error either.

EXPECTED BEHAVIOR
-----------------------
On executing the SA_CREATE_RTLOG job it should pick the data.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a Sale transaction Via API.
2. Pass the sales transaction header and item details.
3. Mention the item type as REF and barcode SKU value in the refItem attribute, which is not available in MFCS and ORI.
4. Data will be processed successfully in API.
5. In the SVC_RTLOG_DATA_LOAD table, INPROGRESS_UPDATED shows as 'S' for TITEM.
6. Execute the SA_CREATE_RTLOG job.
7. Job will not pick the transaction we processed.
8. SVC_RTLOG_DATA_LOAD.INPROGRESS_UPDATED remains 'S' for TITEM record.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.