DBA Data[Home] [Help] [Dependency Information]


VIEW: APPS.PJM_REQ_COMMITMENTS_CMPRJ_V

Object Details
Object Name: PJM_REQ_COMMITMENTS_CMPRJ_V
Object Type: VIEW
Owner: APPS
FND Design Data: ViewPJM.PJM_REQ_COMMITMENTS_CMPRJ_V
Subobject Name:
Status: VALID

View Type

A public view which may be useful for custom reporting or other data
requirements.


PJM_REQ_COMMITMENTS_CMPRJ_V returns project-related requisition distributions in Oracle Purchasing with a destination of Inventory or Shop Floor that have not yet been purchased on a purchase order.
Most of the project information required by Oracle Projects is derived using the following algorithm:
- If a project is directly referenced on the purchase requisition distribution, it will be used; otherwise, if the destination organization is associated with a common project in the Project Manufacturing organization setup, the common project will be used.
- If Task AutoAssignment is implemented, task is derived from the predefined assignment rules if a task is not directly referenced on the purchase requisition distribution.
- Expenditure item date is derived from the need-by date of the requisition line, and if not entered, the creation date of the requisition line.
- The destination organization will be used as the expenditure organization if the destination is inventory, otherwise the expenditure organization will be derived from the BOM department of the receiving routing operation if the destination is shop floor.
- Expenditure type is derived from the expenditure type associated with the first material sub-element of the item.
Due to differences in Task AutoAssignment attributes, this view is split into two UNION sections, one part for inventory destination purchase requisition distributions and the other part for shop floor destination purchase requisition distributions.
This view is used by the Oracle Projects Commitments module.


[View Source]

Columns
Name Datatype Length Mandatory Comments
REQ_NUMBER VARCHAR2 (20) Yes Purchase requisition number
DOCUMENT_TYPE VARCHAR2 (4000)
Procurement document type
APPROVED_FLAG VARCHAR2 (1)
Flag indicating purchase requisition is approved
REQ_LINE NUMBER
Yes Requisition line number
ITEM_DESCRIPTION VARCHAR2 (240) Yes Item description
NEED_BY_DATE DATE

Purchase requisition need-by date
CREATION_DATE DATE

Date purchase requisition created
VENDOR_NAME VARCHAR2 (240)
Supplier name
VENDOR_ID NUMBER

Supplier unique identifier
REQUESTOR_PERSON_ID NUMBER (9) Yes Requestor unique identifier
REQUESTOR_NAME VARCHAR2 (4000)
Requestor name
DENOM_CURRENCY_CODE VARCHAR2 (15)
Transaction currency code
DENOM_AMOUNT NUMBER

Requisition amount in purchase requisition currency
ACCT_CURRENCY_CODE VARCHAR2 (15) Yes Functional currency code
ACCT_RATE_DATE DATE

Functional currency exchange rate date
ACCT_RATE_TYPE VARCHAR2 (30)
Functional currency exchange rate type
ACCT_EXCHANGE_RATE NUMBER

Exchange rate to functional currency
UNIT VARCHAR2 (4000)
Unit of measure
UNIT_PRICE NUMBER

Cost per unit of the project-related commitment distribution
QUANTITY NUMBER

Quantity requested
AMOUNT NUMBER

Requisition amount in functional currency
PROJECT_NUMBER VARCHAR2 (25) Yes User-entered number that uniquely identifies a project or seiban
PROJECT_NAME VARCHAR2 (30) Yes User-entered project/seiban name
TASK_NUMBER VARCHAR2 (25) Yes User-entered string that uniquely identifies a task within a project
TASK_NAME VARCHAR2 (20) Yes User-entered task name
EXPENDITURE_TYPE VARCHAR2 (30) Yes Commitment expenditure type
EXPENDITURE_CATEGORY VARCHAR2 (30) Yes Expenditure category of the commitment
REVENUE_CATEGORY VARCHAR2 (30) Yes Revenue category of the commitment
EXPENDITURE_ITEM_DATE DATE

Date on which you expect to incur the commitment costs
EXPENDITURE_ORGANIZATION VARCHAR2 (240) Yes Expenditure organization incurring the commitment
REQUISITION_HEADER_ID NUMBER
Yes Purchase requisition header unique identifier
REQUISITION_LINE_ID NUMBER
Yes Purchase requisition line unique identifier
REQ_DISTRIBUTION_ID NUMBER
Yes Purchase requisition distribution unique identifier
PROJECT_ID NUMBER (15) Yes System-generated number that uniquely identifies a project or seiban
TASK_ID NUMBER (15) Yes Task unique identifier
EXPENDITURE_ORGANIZATION_ID NUMBER (15) Yes Unique identifier of the expenditure organization incurring the commitment
INVENTORY_ITEM_ID NUMBER

Inventory item unique identifier
INVENTORY_ITEM_NAME VARCHAR2 (4000)
Item Name
WIP_RESOURCE_ID NUMBER

Resource unique identifier
WIP_RESOURCE_NAME VARCHAR2 (4000)
Resource name
UOM_CODE VARCHAR2 (4000)
Code for Unit of Measure
UNIT_OF_MEASURE VARCHAR2 (4000)
Unit of Measure
Query Text

Cut, paste (and edit) the following text to query this object:


SELECT REQ_NUMBER
,      DOCUMENT_TYPE
,      APPROVED_FLAG
,      REQ_LINE
,      ITEM_DESCRIPTION
,      NEED_BY_DATE
,      CREATION_DATE
,      VENDOR_NAME
,      VENDOR_ID
,      REQUESTOR_PERSON_ID
,      REQUESTOR_NAME
,      DENOM_CURRENCY_CODE
,      DENOM_AMOUNT
,      ACCT_CURRENCY_CODE
,      ACCT_RATE_DATE
,      ACCT_RATE_TYPE
,      ACCT_EXCHANGE_RATE
,      UNIT
,      UNIT_PRICE
,      QUANTITY
,      AMOUNT
,      PROJECT_NUMBER
,      PROJECT_NAME
,      TASK_NUMBER
,      TASK_NAME
,      EXPENDITURE_TYPE
,      EXPENDITURE_CATEGORY
,      REVENUE_CATEGORY
,      EXPENDITURE_ITEM_DATE
,      EXPENDITURE_ORGANIZATION
,      REQUISITION_HEADER_ID
,      REQUISITION_LINE_ID
,      REQ_DISTRIBUTION_ID
,      PROJECT_ID
,      TASK_ID
,      EXPENDITURE_ORGANIZATION_ID
,      INVENTORY_ITEM_ID
,      INVENTORY_ITEM_NAME
,      WIP_RESOURCE_ID
,      WIP_RESOURCE_NAME
,      UOM_CODE
,      UNIT_OF_MEASURE
FROM APPS.PJM_REQ_COMMITMENTS_CMPRJ_V;

Dependencies

[top of page]

APPS.PJM_REQ_COMMITMENTS_CMPRJ_V references the following:

SchemaAPPS
ViewGL_SETS_OF_BOOKS
SynonymHR_ALL_ORGANIZATION_UNITS_TL
SynonymPA_EXPENDITURE_TYPES
SynonymPA_PROJECTS_ALL
SynonymPA_TASKS
PL/SQL PackagePJM_COMMITMENT_UTILS - show dependent code
SynonymPO_REQUISITION_HEADERS_ALL
SynonymPO_REQUISITION_LINES_ALL
SynonymPO_REQ_DISTRIBUTIONS_ALL

APPS.PJM_REQ_COMMITMENTS_CMPRJ_V is not referenced by any database object