How Oracle Service Contracts Main Billing Program Populates AR Interface (Including GL_DATE, TRX_DATE, RULE_START_DATE)
(Doc ID 1567875.1)
Last updated on MAY 13, 2020
Applies to:Oracle Service Contracts - Version 12.1.3 and later
Information in this document applies to any platform.
Oracle Service Contracts (OKS)
Oracle Receivables (AR)
This document explains how the Service Contracts Main Billing concurrent program populates the Receivables (AR) interface tables. The data populated into the interface tables is processed by the Autoinvoice program to create the invoice/credit transactions in AR.
This document is intended for use by functional and technical readers who are familiar with Service Contracts Main Billing and want to understand how it should populate the AR interface tables. This information can be used to answer questions about how AR transactions are created based on Service Contracts billing transactions.
The PL/SQL package body that contains the code for populating Service Contracts data to the AR Interface tables is OKS_ARFEEDER_PUB, the definition of which is in the file OKSPARFB.pls.
This document should be read in conjunction with <Note 1195997.1> "Description and Usage of Fields in RA_INTERFACE_LINES Table".
The document will only list fields in the RA_INTERFACE_LINES table which are particularly relevant to Service Contracts. For generic information on how other fields are populated, refer to <Note 1195997.1>.
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