In this article, we`ll talk about contract tables in Oracle Fusion. Oracle Fusion uses contract tables to store contract data. I`ll go over some of Oracle Fusion`s key contract tables. These contract tables can be used to create custom GDP reports for contracts in Oracle Fusion. For more information, see the list of contract tables in Oracle Fusion below. We tried many tables such as OKC_K_HEADERS_ALL_B, OKC_K_HEADERS_TL HZ_PARTIES. OKC_K_LINES_B: A CONTRACT LINE is a supertype of CLIN (contract item number), SUBCLIN and LINE DETAIL, all of which group a group of deliverable items into a logical quantity generally specified by unit price, delivery or other classification. It also serves as a connection point for special RULES that govern the execution of the delivery. LINES are organized in a hierarchy.

A LINE can have children and be related to only one parent. The top line (also known as the top line) has the CONTRACT HEADER as the parent, not the LINE. Until it is replaced, the RULE or PARTY association of a LINE applies to all child lines. A specific LINE STYLE must be used for each CONTRACT LINE. OKC_K_STATUS_HISTORY_B: Oracle contract history is stored in this table. Oracle Fusion contains information. We try to get the contractor`s name, contract value, and some custom object fields to create a receipt report with BIp. OKC_K_HEADERS_ALL_B: The top component of a contract, the contract header, is used to collect information about the contract such as number, type, parties, business unit, start date, currency, etc.

In addition, some characteristics at the header level can be set by default on the contractual elements. OKC_CONTACTS: Contractual contacts are children of the contracting parties. A contact, like the parties, has a defined role in a contract, e.B. contract manager, buyer, etc. Within the framework of the established contract, the contact is the contact person of the party. OKC_K_HEADERS_TL: According to MLS guidelines, columns can be translated from OKC K HEADERS B. For a description of the table, see OKC K HEADERS B. OKC_K_SALES_CREDITS: Sales credits for the sale of services in a contract are kept in this file. In order management, it works in the same way as sales credits. OKC_PRICING_TERMS: The pricing terms of parent entities, such as sales contracts, promotions, and discount lists, are stored in this table. OKC_CONTRACT_TYPES_B: The contract type configuration information is stored in this entity. OKC_K_PARTY_ROLES_B: A contract is a legally binding agreement between two or more parties.

Under a contract, each party has a specific function to play. The basic responsibilities of a party are buyers and sellers (sellers), although other roles such as third parties, buyers, etc. can be defined. Each party has contacts that are saved as subordinate entities called party contacts. . Please assist us if there are any other details that would provide the details of the contract. OKC_K_CHARGE_COMPONENTS: Load changes for a line load are represented by this field. You can use Oracle REST APIs to view and manage data stored in Oracle Applications Cloud. Whether you have experience or are new to REST, use this guide to find what you need, including: We can`t find the details of the main parties in the contract table… .