My Oracle Support Banner

ORDHEAD_REV Table Is Not Populated With All Fields When First Revision Is Created (Doc ID 2467252.1)

Last updated on DECEMBER 04, 2019

Applies to:

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

Symptoms

ORDHEAD_REV table is not populated with all fields when first revision is created.

Once the Purchase Order(PO) is approved in Retail Merchandising System(RMS), revision 0 is created in ORDHEAD_REV table but the entry does not capture all the original fields from PO.
In consequence, when any amendments are done later on PO, original details of PO can not be found as they are not stored against revision 0. For example, earliest ship date and latest ship date are not populated for revision 0.

Steps To Recreate:

  1. Create a PO in RMS and approve it.
  2. Revision 0 is created in ORDHEAD_REV table but not all fields are copied from original PO onto this revision entry. For e.g. earliest and latest ship date.

Changes

 

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
Changes
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.