1. Tables and Views for Procurement
  2. POR_PURCHASE_REQ_EVENT_HISTORY

POR_PURCHASE_REQ_EVENT_HISTORY

POR_PURCHASE_REQ_EVENT_HISTORY stores information about payload of purchase request event. You need one row for each purchase request event has raised. Each row contains the payload information of event raised for purchase request.

Details

  • Schema: FUSION

  • Object owner: POR

  • Object type: TABLE

  • Tablespace: Default

Primary Key

Name Columns

POR_PURCHASE_REQ_EVNT_HIS_PK

EVENT_HISTORY_ID

Columns

Name Datatype Length Precision Not-null Comments
EVENT_HISTORY_ID NUMBER 18 Yes Unique identifier for event history
EVENT_ACTION_CODE VARCHAR2 64 Yes Raised event action code
REQUISITION_HEADER_ID NUMBER 18 Yes Header ID to identify the Requisition
EVENT_SEQUENCE NUMBER 9 Yes Sequence the events for a particular requisition header based on this sequence.
REQUISITION_NUMBER VARCHAR2 64 Yes Number for the requisition
REQUISITIONING_BU_ID NUMBER 18 Business Unit Id for the requisition
REQUISITIONING_BU_NAME VARCHAR2 240 Business Unit name for the requisition
REQUISITION_LINE_ID NUMBER 18 Unique key to identify the requisition line which invoked the event
REQUISITION_LINE NUMBER Current requisition line number
PO_HEADER_ID NUMBER 18 Unique key to identify the purchase order header which invoked this event.
ORDER_NUMBER VARCHAR2 30 Purchase Order Number
SOLD_TO_LEGAL_ENTITY_ID NUMBER 18 Id of the Sold To Legal entity
SOLD_TO_LEGAL_ENTITY_NAME VARCHAR2 240 Name of the Sold To Legal entity
PO_CHANGE_ORDER_SEQUENCE NUMBER Indicates the PO Change Order Sequence.
CHANGE_ORDER_TYPE_CODE VARCHAR2 25 Populated if PO CO is Implemented
PO_CO_ORIGINATOR_PARTY VARCHAR2 25 The role of the party who initiated the Change Order. Possible Values:BUYER,REQUESTER, SUPPLIER,CAT_ADMIN
INTERFACE_SOURCE_CODE VARCHAR2 25 The Interface Source Code stored on the Requisition Header
ORCHESTRATION_CODE VARCHAR2 20 The Orchestration Code stored on the Requisition Line
NEW_REQ_LINES VARCHAR2 100 The Line Numbers of the newly split Requisition Lines
NEW_REQ_LINE_IDS VARCHAR2 100 Requistion Line Ids of the newly split Requisition Lines
NEW_REQ_LINE_QUANTITIES VARCHAR2 200 Quantities of the newly split Requisition Lines
CANCEL_REQ_LINE_IDS VARCHAR2 1000 The Requisition Line Ids which has been canceled
CANCEL_REQ_LINES VARCHAR2 1000 The Line Numbers stored on the canceled Requisition Lines
CANCEL_REQ_LINE_ORCH_CODES VARCHAR2 1000 The Orchestration Codes stored on the canceled Requisition Lines
CREATED_BY VARCHAR2 64 Yes Who column: indicates the user who created the row.
CREATION_DATE TIMESTAMP Yes Who column: indicates the date and time of the creation of the row.
LAST_UPDATED_BY VARCHAR2 64 Yes Who column: indicates the user who last updated the row.
LAST_UPDATE_DATE TIMESTAMP Yes Who column: indicates the date and time of the last update of the row.
LAST_UPDATE_LOGIN VARCHAR2 32 Who column: indicates the session login associated to the user who last updated the row.
OBJECT_VERSION_NUMBER NUMBER 9 Yes Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried.
IS_NEW_EVENT_PATH_ENABLED VARCHAR2 1 The isNewEventPathEnabled returned by FOM APIs
RETURN_STATUS VARCHAR2 1 The status returned by FOM APIs
MESSAGE_NAME VARCHAR2 40 The message name returned by FOM APIs
MESSAGE_TEXT VARCHAR2 4000 The message text returned by FOM APIs
IS_SCHEDULE_SPLIT VARCHAR2 1 The schedule split in the purchase order change order

Indexes

Index Uniqueness Tablespace Columns
POR_PURCHASE_REQ_EVENT_HIS_U1 Unique Default EVENT_HISTORY_ID