My Oracle Support Banner

Franchise Cost Template Is Not Populating End Date Correctly For Event Costtmpreldel (Doc ID 2507820.1)

Last updated on DECEMBER 03, 2019

Applies to:

Oracle Retail Merchandising System - Version 16.0.1 and later
Information in this document applies to any platform.

Symptoms

Franchise Cost Template is not populating end date correctly for event costtmpreldel.
Franchise Cost Template Upload batches (fcosttmplupld and fcosttmplprocess ) are incorrectly updating franchise cost for fixed cost scenario.

The issue can be reproduced at will with the following steps:

  1. New Cost Template created for same item (fixed cost): "Data Point: Vdate:19-JAN-2018; Message Type: Add (costtmpadd & costtmpreladd); New Start date:20-JAN-2018; New End Date:20-MAY-2018 "
  2. File Created  for fcosttmplupld
  3. Execute fcosttmplupld
  4. Execute fcosttmplprocess
  5. Data Loaded and View
  6. Franchise Cost template header and template relation has been created successfully based on START_DATE and END_DATE
  7. Same Item / Location are modified for new cost  price for a future start date.
     To achieve this , existing template is deleted (with costtmpmod and costtmpreldel combination ) and new template is been added (costtmpadd and costtmpreladd).
     Observe Issue (1) : Fixed cost price for cost template cannot be modified using costtmpmod AS WITH IN fcosttmplprocess record is getting failed.
    "Cost template header information cannot be modified as a relationship exists for the template"
  8. "Deactivate current Template relation: "Data Point :Vdate:19-FEB-2018; Message Type: Add (costtmpmod & costtmpreldel); Start date:20-JAN-2018; End Date:20-MAY-2018; New Start date:20-JAN-2018; New End Date:28-FEB-2018"
  9. File Structure for fcosttmplupld
  10. Execute fcosttmplupld
  11. Execute fcosttmplprocess
  12. Observe Table Data
    Observe Issue (2): Even file contains new end date as 28-FEB-2018 , WF_COST_RELATIONSHIP.END_DATE is updated with vdate i.e 20-Feb 02018 .
    WF_COST_RELATIONSHIP.END_DATE should  be this updated this with 28-Feb-2018 as mentioned in file .

Cause

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
Symptoms
Cause
Solution
References


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