My Oracle Support Banner

Oracle Payments: Data Model For Funds Capture Transactions Starting From TangibleID (PSON) (Doc ID 1219993.1)

Last updated on JULY 13, 2019

Applies to:

Oracle Payments - Version 12 to 12.1.3 [Release 12.0 to 12.1]
Information in this document applies to any platform.

Purpose

The purpose of this article is to give information about Oracle Payments Data Model for the transactional part of the Funds Capture portion of the product.

For a script based on information from this article refer to <NOTE 1233263.1> Oracle Payments: Funds Capture Transaction Data Gathering Script

Scope

The aim of this document is to assist in understanding the data model, and track existing transactions for research or investigation of issues. Consultants customizing may find this article useful as well.

The article will focus on looking up all data starting from a central ID within Oracle Payments: the Tangible_ID (Also known as PSON or Payment System Order Number) which is a unique identifier for Credit Card Transactions.

Details

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
Purpose
Scope
Details
 A. Central view: IBY_TRXN_EXT_AUTHS_V
 B. Tangible_Id central table: IBY_TANGIBLE
 C. Core transactional table: IBY_TRXN_SUMMARIES_ALL
 D. Relationships with Order management
 D.1. Test case from OM to IBY
 D.2. To retrieve details of an iPayment transaction from an order
 E. Relationship with Receivables 
 E.1. Test Case From AR to IBY
 E.2 Payment System Order Number field (PSON) or Tangible_Id in Receivables
References

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