Payment Event Creation Service (CIPPEVTP) Should Call Batch Only when Processing Mode is Online
(Doc ID 2174044.1)
Last updated on MARCH 03, 2019
Applies to:Oracle Financial Services Revenue Management and Billing - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
RMB v18.104.22.168.0 version, PY - Payment:
Payment Event Creation Service (CIPPEVTP): "C1-AddPayEventPay" calls batch program internally based on feature configuration C1_PAYBYBTCH count but it does not check whether the service is called from batch mode or online mode. If service is called from online mode, then this processing is fine, but if this service is called from batch mode already, then batch fails with Error saying batch is being called internally. So service should have a flag to see in what mode this service is called and should invoke batch only when processing mode is Online.
StdErr log shows following:
CM batch process goes into endless loop and payment event is not created.
CM batch should be completed and payment event to be created.
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