Results for “api_timestamp”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AS_TRANSFER_QUES is a Sales Foundation (AS) table owned by the OSM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to support Lead Sharing functionality, one of the core capabilities of the Oracle Sales and TeleSales foundation layer. When a lead is shared or reassigned between partners within the lead management workflow, the request and its outcome are captured in this table, providing a transactional record of the sharing event and the state of the asynchronous API call that processes it.

The table is classified heuristically as a standalone object rather than as a pure hub, link, or satellite. In Data Vault modeling terms, this classification should be treated as a suggestion: the presence of both source and destination identifiers (lead and partner on each side) gives the table link-like characteristics, since it records a relationship between two leads and two partners. However, because it also carries status, timestamps, and API tracking attributes, it simultaneously exhibits satellite behavior. A modeler might therefore treat AS_TRANSFER_QUES as a link table with an attached satellite, or as a self-contained transaction log depending on the breadth of the surrounding model. The table is a transactional staging and tracking table rather than a static master entity.

Key Information Stored

The table is documented with nine columns, of which the following are the most significant:

• PARTNER_TRANSACTION_ID — The surrogate primary key, enforced by the constraint AS_TRANSFER_QUES_PK and the unique index AS_TRANSFER_QUES_U1. It also serves as the documented business-key candidate and is the column referenced by dependent tables.
• SOURCE_LEAD_ID — The lead from which the share or transfer originates.
• DESTINATION_LEAD_ID — The lead record created or assigned as the target of the transfer.
• SOURCE_PARTNER_ID — The partner that currently owns or holds the source lead.
• DESTINATION_PARTNER_ID — The partner receiving the shared lead.
• TRANSACTION_STATUS — The processing state of the transfer request, indicating whether the share has completed, is pending, or has failed.
• CREATE_TIMESTAMP — The date and time the transfer request record was created.
• API_TIMESTAMP — The timestamp associated with the API invocation that processed the transfer.
• LEAD_CR_TIMESTAMP — The creation timestamp of the lead, useful for aging and cycle-time reporting.

Together these attributes allow the system to correlate a share request with its origin, destination, and processing lifecycle.

Common Use Cases and Queries

Typical scenarios include auditing who shared which lead with whom, tracking the success rate of lead-sharing API calls, and producing lead-distribution reports by partner. A basic query to review pending or failed transfers is shown below:

• SELECT PARTNER_TRANSACTION_ID, SOURCE_LEAD_ID, DESTINATION_LEAD_ID, TRANSACTION_STATUS, CREATE_TIMESTAMP FROM OSM.AS_TRANSFER_QUES WHERE TRANSACTION_STATUS <> 'SUCCESS' ORDER BY CREATE_TIMESTAMP DESC;
• Partner-to-partner volume analysis can be built by grouping on SOURCE_PARTNER_ID and DESTINATION_PARTNER_ID.
• Performance monitoring uses the gap between CREATE_TIMESTAMP and API_TIMESTAMP to measure API turnaround.
• Lead aging uses LEAD_CR_TIMESTAMP against the transfer date.

Related Objects

The documented foreign-key relationship ties this table to its detail lines:

• AS_TRANSFER_DETAILS — Referencing table via AS_TRANSFER_DETAILS.PARTNER_TRANSACTION_ID → AS_TRANSFER_QUES.PARTNER_TRANSACTION_ID. This is the principal child of the table and holds the line-level content of each transfer request.
• AS_TRANSFER_QUES_PK / AS_TRANSFER_QUES_U1 — The primary key constraint and unique index that enforce uniqueness on PARTNER_TRANSACTION_ID.

Given the Sales Foundation context, the table also logically relates to lead (AS_LEADS) and partner master entities through the source and destination identifier columns, though those relationships are not documented as physical foreign keys in the supplied metadata and should be validated against the actual schema before being relied upon in custom reporting.