PCM_OP_BILL_WRITE_OFF and PCM_OP_PYMT_COLLECT Opcodes Do Not Propagate Ebuf Accordingly To Caller Opcode (Doc ID 3029111.1)

Last updated on JUNE 17, 2024

Applies to:

Symptoms

After having an error during PCM_OP_BILL_WRITE_OFF opcode, the error is not propagated to the wrapper opcode so transaction cannot be managed correctly. Similar issue is also seen with PCM_OP_PYMT_COLLECT. 

The user has a custom Multi-Thread Application (MTA) which calls the out-of-box opcodes PCM_OP_BILL_WRITE_OFF, PCM_OP_PYMT_COLLECT, PCM_OP_BILL_ITEM_TRANSFER, PCM_OP_AR_BILL_WRITEOFF. The MTA is used to zero out bills either by posting a payment or write them off. The customization is creating input flist and calling PCM_OP_AR_BILL_WRITEOFF, On no error, it call PCM_OP_BILL_ITEM_TRANSFER for allocation.

The user observes that there were some missing entries in Connection Manager (CM) pin.conf file, and it is causing the error. However, the op_bill_writeoff opcode successfully returns, allocation is not successfully done. It is found that the error buffer is cleared, which causes the custom opcode to return a success.


ERROR
----------------

STEPS
----------------
1. Create a bill with negative due
2. Comment out
  - cm fm_module ${PIN_HOME}/lib/fm_installment${LIBRARYEXTENSION} fm_installment_config - pin
  - cm fm_module ${PIN_HOME}/lib/fm_installment_pol${LIBRARYEXTENSION} fm_installment_pol_config - pin
3. Wrapper code call PCM_OP_AR_BILL_WRITEOFF
See that cm.pinlog has errors, but PCM_OP_AR_BILL_WRITEOFF does not have ebuf populated

Cause

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