PCM_RECID_ASSIGN Does Not Operate With the PCM_OP_WRITE_FLDS Opcode (Doc ID 3070098.1)

Last updated on FEBRUARY 06, 2025

Applies to:

Goal

When a new element is added to the configuration object, the new object rec_id is created with the maximum value of 2147483647.

As a result, when a new object is added, it is overwritten with the same number because the rec_id value is max(2147483647).

 For special business purposes, it is possible to save a larger value using testnap with the PCM_OP_WRITE_FLDS opcode.

2147483647 is the actual value saved. The testnap application appears to be passing only the value 2147483647 to the WRITE_FLDS opcode.

In essence, the field just shows which products/discounts are included in a bundle; thus, no external system should be concerned with the value itself.

However, it should assign the max(rec_id)+1 to the element, as it did in 7.5, and we are experiencing this issue in BRM 12.

grep PCM_RECID_ASSIGN *.h
pcm.h:#define PCM_RECID_ASSIGN 0xFFFFFFFe /* (on write) create new unique recid */

decimal value of 0xFFFFFFFe ===> 2147483647

Why is the element being inserted with the highest rec_id?

This appears to be an issue in BRM 12.

Solution

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