PCM_OP_CUST_FIND Adds Extra "0" To PIN_FLD_ACCOUNT_NO (Doc ID 2008092.1)

Last updated on MARCH 29, 2019

Applies to:

Symptoms

On : 7.5.0.10.0 version, Customer Registration

Issue:

When running the opcode PCM_OP_CUST_FIND, the dm_tt process adds a "0" to the provided PIN_FLD_ACCOUNT_NO field, thus it will never find the account in the OBRM database.

Moreover, even during a simple search (sample input flist shown below) on the /account or /uniqueness objects, dm_tt will add an extra "0" (or two "0" for /uniqueness), thus never finding the account in OBRM.

Note: This problem is not present when searching by other PIN_FLDT_STR fields (ex: PIN_FLD_NAME in /account).

Steps to reproduce:

1. Pass below input list to PCM_OP_CUST_FIND from testnap:
   
   # number of field entries allocated 20, used 3
   0 PIN_FLD_POID POID [0] 0.0.0.1 /account -1 0
   0 PIN_FLD_RESULTS ARRAY [0] allocated 20, used 1
   1 PIN_FLD_ACCOUNT_NO STR [0] ""
   0 PIN_FLD_ARGS ARRAY [0] allocated 20, used 1
   1 PIN_FLD_ACCOUNT_NO STR [0] "70124293"
   
   
2. Check the cm pinlog that the input flist is modified by dm_tt as follows:
   
   0 PIN_FLD_POID POID [0] 0.0.0.1 /account -1 0
   0 PIN_FLD_RESULTS ARRAY [0] allocated 20, used 1
   1 PIN_FLD_ACCOUNT_NO STR [0] ""
   0 PIN_FLD_ARGS ARRAY [0] allocated 20, used 1
   1 PIN_FLD_ACCOUNT_NO STR [0] "0177799681"

Actual Result:
Account is not found as a result

Expected Result:
Since account actually exists in the database, it should be found and returned in the result.

Cause

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