[Home] [Help]
[Dependency Information]
| Object Name: | PA_CUSTOMER_RECEIVER_PRJECTS_V |
|---|---|
| Object Type: | VIEW |
| Owner: | APPS |
| FND Design Data: | PA.PA_CUSTOMER_RECEIVER_PRJECTS_V
|
| Subobject Name: | |
| Status: | VALID |
A supplementary view used to simplify forms coding.
Warning: Oracle does not recommend you query or alter datausing this view. It may change dramatically in subsequent minor or major
releases.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SEGMENT1 | VARCHAR2 | (25) | Yes | The project number that uniquely identifies the project. The project number can be user-entered or system-generated as defined in the implementation options. |
| TASK_NUMBER | VARCHAR2 | (25) | Yes | User-defined number that uniquely identifies the task within a project. It is recommended to number tasks based on the wbs since that is how tasks are ordered in some reports. However note: task numbers do not record the wbs structure |
| TASK_NAME | VARCHAR2 | (20) | Yes | User-defined short name of the task |
| TASK_ID | NUMBER | (15) | Yes | The system-generated number that uniquely identifies the task |
| CUSTOMER_ID | NUMBER | Customer identifier for the operating unit to be used for intercompany AR invoice. This is required if cc_ic_billing_recvr_flag = Y | ||
| CUSTOMER_NAME | VARCHAR2 | (360) | Yes | Customer name |
| ORG_ID | NUMBER | (15) | Yes | Operating unit identifier for multi-organization installations |
| PROJECT_ID | NUMBER | (15) | Yes | The system-generated number that uniquely identifies the project |
Cut, paste (and edit) the following text to query this object:
SELECT SEGMENT1
, TASK_NUMBER
, TASK_NAME
, TASK_ID
, CUSTOMER_ID
, CUSTOMER_NAME
, ORG_ID
, PROJECT_ID
FROM APPS.PA_CUSTOMER_RECEIVER_PRJECTS_V;
APPS
HZ_CUST_ACCOUNTS
HZ_PARTIES
PA_IMPLEMENTATIONS_ALL
PA_PROJECTS_ALL
PA_PROJECT_UTILS
- show dependent code
PA_TASKS
APPS.PA_CUSTOMER_RECEIVER_PRJECTS_V is not referenced by any database object
|
|
|
|