ACD_REVENUE_B_INT
Product Proposal Revenue interface table for Bulk Import.
Details
-
Schema: FUSION
-
Object owner: ACD
-
Object type: TABLE
-
Tablespace: INTERFACE
Primary Key
| Name | Columns |
|---|---|
|
ACD_REVENUE_B_INT_PK |
REVENUE_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| REVENUE_ID | NUMBER | 18 | Yes | Primary Key which will be system generated Application Unique Id. | |
| 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. | |
| PRODUCT_PROPOSAL_ID | NUMBER | 18 | Yes | Refers to Product Proposal Id from ACD_PRODUCT_PROPOSAL table as Foreign key | |
| REVENUE_STATUS | VARCHAR2 | 30 | Yes | Indicates the status of revenue for Product Concept (Projected,Estimated,Actual) The supported types are defined in the Lookup type with the name ACD_REVENUE_STATUS and the look up codes are PROJECTED,ESTIMATED,ACTUAL values | |
| REVENUE_AMOUNT | NUMBER | Yes | Total revenue amount during the time-period between start and end dates | ||
| START_DATE | DATE | Yes | Start date of a time-period e.g. 04/01/2017 | ||
| END_DATE | DATE | Yes | End date of a time-period e.g. 08/01/2011 | ||
| REVENUE_TREND | VARCHAR2 | 30 | Yes | Indicates the trend of revenue for Product Concept (Point, Uniformly Distributed, Front Loaded, Back Loaded) The supported types are defined in the Lookup type with the name ACD_TREND and the look up codes are POINT,UNIFORMLY_DISTRIBUTED,FRONT_LOADED,BACK_LOADED values | |
| REVENUE_CATEGORY | VARCHAR2 | 30 | Indicates the category of revenue for Product Concept (e.g. NA,EMEA,APAC etc) The supported types are defined in the Lookup type with the name ACD_REVENUE_CATEGORY and the look up codes are custom values | ||
| REVENUE_TYPE | VARCHAR2 | 30 | Custom lookup values for the revenue type. | ||
| 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. | ||
| NAME | VARCHAR2 | 100 | This is the translatable NAME for the object. | ||
| LANG_CODE | VARCHAR2 | 4 | Indicates the code of the language into which the contents of the translatable columns are translated. | ||
| SRC_LANG_CODE | VARCHAR2 | 4 | Indicates the code of the language in which the contents of the translatable columns were originally created. | ||
| SOURCE_LANG_FLAG | VARCHAR2 | 1 | Indicates the code of the language in which the contents of the translatable columns were originally created. | ||
| IMPORT_STATUS_CODE | VARCHAR2 | 30 | IMPORT_STATUS_CODE tells status of a row in the interface table. | ||
| INTERNAL_ACTION_CODE | VARCHAR2 | 30 | This column is created for internal use and will be populated and used by bulk import logic. | ||
| ACTION_CODE | VARCHAR2 | 30 | ACTION_CODE in interface table allows source system to specify a particular operation (insert, update, etc) for a row. | ||
| LOAD_REQUEST_ID | NUMBER | 10 | When Data file uploaded and click on submit that time the load request Id generated. | ||
| INTERFACE_ROW_ID | NUMBER | 18 | INTERFACE_ROW_ID is the unique identifier for the record with in a batch. |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| ACD_REVENUE_B_INT_U1 | Unique | Default | REVENUE_ID |