We’ll talk about contract tables in Oracle Fusion in this post. In Oracle Fusion, contract tables are used to hold contract-related data. I’ll go over some of Oracle Fusion’s most essential contract tables. These contract tables can be used to create custom BIP reports for contracts in Oracle Fusion. Please see the list of Contract tables in Oracle Fusion below for more information.
Contract Frequent table used in BIP Report
Contract table descriptions and uses
OKC_K_HEADERS_ALL_B: A contract’s top level component, the contract header, is used to collect contract information such as the number, kind, parties, business unit, start date, currency, and so on. In addition, certain header-level characteristics can be set to contract lines by default.
OKC_K_HEADERS_TL: As per MLS guidelines, columns from OKC K HEADERS B can be translated. A description of the table can be found in OKC K HEADERS B.
OKC_K_LINES_B: A CONTRACT LINE is a super type of CLIN (contract line item number), SUBCLIN, and LINE DETAIL, all of which group a group of deliverable ITEMS into a logical set that is usually specified by unitary price, delivery, or some other classification. It also serves as a connection point for any special RULES that regulate the delivery’s performance. LINES are arranged 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 its parent, rather than the LINE. Until overridden, a LINE’s RULE or PARTY association applies to all child lines. A specific LINE STYLE must be used for each CONTRACT LINE.
OKC_K_PARTY_ROLES_B: A contract is a legally binding agreement between two or more parties. Within a contract, each side has a specific function to play. The fundamental responsibilities for a party are Buyer and Seller (Vendor), although other roles such as third party, buyer, and so on can be defined. Each party will have contacts, which will be captured as child entities called party contacts.
OKC_K_SALES_CREDITS: Sales credits for the selling of services in a contract are kept in this file. In Order Management, it works in the same way as sales credits.
OKC_K_STATUS_HISTORY_B: The history of Oracle Contracts is stored in this table. Oracle Fusion has information.
OKC_PRICING_TERMS: Pricing terms for parent entities such as Sales Agreements, Promotions, and Discount Lists are stored in this table.
OKC_CONTACTS: Contract contacts are Contract parties’ children. A contact, like parties, has a defined role in a contract, such as Contract Manager, Buyer, and so on. In the framework of the created contract, the contact is the party’s point of contact.
OKC_CONTRACT_TYPES_B: The Contract Type Setup information is stored in this entity.
OKC_K_CHARGE_COMPONENTS: Charge modifications for a line charge are represented by this field.