Last updated on AUGUST 17, 2016
Applies to:Oracle Retail Merchandising Analytics - Version 184.108.40.206 and later
Information in this document applies to any platform.
In Oracle Retail Analytics (RA) 220.127.116.11, there is a design concern with "PLP_RETAILBASECOSTCORPORATEORGITDYAGGREGATE" for batch job CSTISLPLP.KSH. The scenario runs two interfaces:
- PLP_RetailBaseCostITDyTempLoad (Source: W_RTL_BCOST_IT_LC_G; Target: W_RTL_BCOST_IT_DY_TMP)
- PLP_RetailBaseCostITDyLoad (Source: W_RTL_BCOST_IT_DY_TMP; Target: W_RTL_BCOST_IT_DY_A)
The target table for the first interface is the source table for the second interface. However, the two interfaces are not connected properly, meaning that if interface "PLP_RetailBaseCostITDyTempLoad" fails, interface "PLP_RetailBaseCostITDyLoad" will still run.
Steps to Reproduce:
- Run batch CSTISLPLP.KSH, ensuring that interface PLP_RetailBaseCostITDyTempLoad fails for some reason.
- Interface PLP_RetailBaseCostITDyLoad will still run, even though the target table for the first interface is the source table for the second interface
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms