DW_REQUISITION_DOCUMENT_HISTORY_CF

This table contains action details of all Submitted Requisitions

Details

Module: Purchasing

Key Columns

SEQUENCE_NUMBER, REQUISITION_HEADER_ID, ACTION_CODE, OBJECT_TYPE_CODE, OBJECT_SUB_TYPE_CODE

Columns

Columns
Name Datatype Length Precision Not Null Comments Referred Table Referred Column
REQUISITION_HEADER_ID NUMBER 38 0 True Document header unique identifier    
OBJECT_TYPE_CODE VARCHAR2 32   True Object Type Code    
OBJECT_SUB_TYPE_CODE VARCHAR2 32   True Object Sub Type Code    
SEQUENCE_NUMBER NUMBER     True Sequence of the approval or control action for a document    
ACTION_CODE VARCHAR2 32   True Approval or control action type DW_POR_APPR_HIST_ACTIONS_LKP_TL POR_APPR_HIST_ACTIONS_CODE
SOURCE_RECORD_ID VARCHAR2 256     This column is for Oracle Internal use only. Source record identifier    
REQUISITION_NUMBER VARCHAR2 64     Requisition Number    
REQUISITION_BU_ID NUMBER 38 0   Requisition Business Unit identifier DW_INTERNAL_ORG_D ORGANIZATION_ID
REQUISITION_LEDGER_ID NUMBER 38 0   Primary Ledger ID of Requisition Business Unit DW_LEDGER_D LEDGER_ID
FISCAL_PERIOD_SET_NAME VARCHAR2 16     Accounting calendar name #1 DW_FISCAL_DAY_D FISCAL_PERIOD_SET_NAME
FISCAL_PERIOD_TYPE VARCHAR2 16     Accounting period type #1 DW_FISCAL_DAY_D FISCAL_PERIOD_TYPE
PERFORMER_ROLE_CODE VARCHAR2 32     Role of the action performer DW_PO_USER_ROLE_LKP_TL PO_USER_ROLE_CODE
PERFORMING_PERSON_ID NUMBER 38 0   Identifier of the person performing the action DW_PERSON_NAME_CURRENT_D PERSON_ID
ACTION_TIMESTAMP TIMESTAMP       Timestamp on which the Action was taken    
ACTION_DATE DATE       Date on which the Action was taken DW_DAY_D CALENDAR_DATE
NOTE VARCHAR2 999     Note for next approver or reason for control action    
IDENTIFICATION_KEY VARCHAR2 128     Identification key for the action    
CREATION_TIMESTAMP TIMESTAMP       Indicates the date and time of the creation of the row    
LAST_UPDATE_TIMESTAMP TIMESTAMP       Indicates the date and time of the last update of the row.    

Notes

#1 In these cases to join with DW_FISCAL_DAY_D apart from FISCAL_PERIOD_TYPE and FISCAL_PERIOD_SET_NAME the relationship should be based on ACTION_DATE column

Copyright © 2019, 2025, Oracle and/or its affiliates.