My Oracle Support Banner

Service Request API: In R12 Coverage_id & Coverage_txn_group_id In CS_ESTIMATE_DETAILS Not Populated (Doc ID 858959.1)

Last updated on FEBRUARY 06, 2022

Applies to:

Oracle Teleservice - Version 12.0 and later
Information in this document applies to any platform.


Creating Charges for a Service Request in Field Service using the API "csf_debrief_charges.create_charges".

This is not populating the fields coverage_id and coverage_txn_group_id in the table CS_ESTIMATE_DETAILS.
These were populated correctly in 11i, but in Release 12 they are populated with blank values.

Above mentioned API internally calls "CS_Service_Billing_Engine_PVT.Create_Charges" which actually creates Charges.
In this API, "cs_charge_details_pvt.get_contract" is used to get the contract related information such as contract id, coverage id, po_number etc.

In 11i, the API cs_charge_details_pvt.get_contract has the out parameters
   . x_coverage_id
   . x_coverage_txn_group_id
which are not present in R12 because of which blank values are getting updated.

Also, in the API "CS_Service_Billing_Engine_PVT.Create_Charges" values for coverage_id and coverage_txn_group_id are populated as blank using:

   l_charges_rec.coverage_id := null;
   l_charges_rec.coverage_txn_group_id := null;

Because of this, discounts may not get updated properly if the Contracts API
oks_con_coverage_pub.apply_contract_coverage is invoked, since it expects the value for coverage_txn_group_id.

Other contract related fields (contract_id, contract_service_id) are populated properly.


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

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