Change in PCM_OP_CUST_CREATE_CUSTOMER Behavior in BRM 12 PS3 (Doc ID 2692598.1)

Last updated on APRIL 03, 2023

Applies to:

Symptoms

Fields like PIN_FLD_EMAIL_ADDR and PIN_FLD_ZIP still appear (output of PCM_OP_CUST_CREATE_CUSTOMER) exactly as they are passed in the input to PCM_OP_CUST_CREATE_CUSTOMER, even though a customization is done in PCM_OP_CUST_POL_PREP_NAMEINFO to upper case the email and enrich the zip code.

For example, this is the input to PCM_OP_CUST_CREATE_CUSTOMER among other fields:

0 PIN_FLD_NAMEINFO ARRAY [1] allocated 20, used 12
1     PIN_FLD_EMAIL_ADDR STR [0] "DoNotReply@<domain_name>.com"
1     PIN_FLD_ZIP STR [0] "#########"

ACTUAL BEHAVIOR
-------------------------------
This is the output, PIN_FLD_EMAIL_ADDR has not changed even though a customization is done to convert everything to upper case.

0 PIN_FLD_NAMEINFO ARRAY [1] allocated 20, used 12
1     PIN_FLD_EMAIL_ADDR STR [0] "DoNotReply@<domain_name>.com"
1     PIN_FLD_ZIP STR [0] "#########"

Please note, the PIN_FLD_EMAIL_ADDR gets stored as upper case in the database due to the customization. However, in the output, it is not updated.


EXPECTED BEHAVIOR
---------------------------------
For the same input, this is the output in 7.5 PS21:

0 PIN_FLD_NAMEINFO ARRAY [1] allocated 20, used 12
1     PIN_FLD_EMAIL_ADDR STR [0] "DONOTREPLY@<DOMAIN_NAME>.COM" 
1     PIN_FLD_ZIP STR [0] "####-#####"

where:
PIN_FLD_EMAIL_ADDR is updated in the database as well as in the output due to customization in PCM_OP_CUST_POL_PREP_NAMEINFO
PIN_FLD_ZIP is updated in the database as well as in the output due to customization in PCM_OP_CUST_POL_PREP_NAMEINFO

Changes

Cause

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