PJB_BI_REPORT_DETAILS
The table is used to store report data for BIP report. The table gets populated by following processes : a) Invoice Generation b) Revenue Generation c) Revenue Diagnostics d) Invoice diagnostics e) Ar Interface . The data in the table is purged in the after report trigger of the BIP report.
Details
-
Schema: FUSION
-
Object owner: PJB
-
Object type: TABLE
-
Tablespace: Default
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| ID | NUMBER | 18 | Yes | Unique Identifier of the report | |
| REPORT_NAME | VARCHAR2 | 30 | Yes | Indicates name of the report. | |
| REPORT_LINE_TYPE | VARCHAR2 | 250 | Yes | Indicates type of report line.Example : SUCCESS, ERROR, ERROR_02,SUMMARY_01 etc. ***** | |
| REPORT_LINE_NUM | NUMBER | 18 | Yes | Indicates number of report line. | |
| REPORT_LINE_ID | NUMBER | 18 | Yes | Unique identifier of the report line. | |
| ORG_ID | NUMBER | 18 | Indicates the identifier of the business unit associated to the row. | ||
| BILLING_TYPE_NAME | VARCHAR2 | 80 | Indicates name of billing type. | ||
| BILLING_EXTENSION_NAME | VARCHAR2 | 30 | Indicates name of the billing extension. | ||
| EVENT_TYPE | VARCHAR2 | 240 | Indicates type of the event. | ||
| COST_PLAN_TYPE | VARCHAR2 | 240 | Indicates type of cost plan. | ||
| BUSINESS_UNIT_NAME | VARCHAR2 | 240 | Indicates name of the business unit. | ||
| LEGAL_ENTITY_NAME | VARCHAR2 | 240 | Indicates name of the legal entity. | ||
| CONTRACT_NUMBER | VARCHAR2 | 120 | Indicates contract number. | ||
| CONTRACT_NAME | VARCHAR2 | 300 | Indicates contract name. | ||
| CONTRACT_DESC | VARCHAR2 | 600 | Indicates contract description. | ||
| CONTRACT_TYPE | VARCHAR2 | 150 | Indicates type of contract. | ||
| BILL_TO_ACCOUNT_NAME | VARCHAR2 | 360 | Indicates account name to which the bill belongs. | ||
| STS_NAME | VARCHAR2 | 80 | Indicates name of status. | ||
| MAJOR_VERSION | NUMBER | 18 | Major version number of the contract. | ||
| BILL_PLAN_NAME | VARCHAR2 | 240 | Indicates name of bill plan. | ||
| BILL_METHOD_NAME | VARCHAR2 | 50 | Indicates bill method name. | ||
| CONTRACT_LINE_NUMBER | VARCHAR2 | 150 | Indicates contract line number. | ||
| PROJECT_NAME | VARCHAR2 | 255 | Indicates name of the project. | ||
| PROJ_ELEM_NAME | VARCHAR2 | 255 | Indicates name of the project element. | ||
| TRANSACTION_ID | NUMBER | 18 | Unique identifier of the transaction. | ||
| BILLABLE_FLAG | VARCHAR2 | 1 | Flag that indicates if the item can accrue revenue. Upon entry, this flag is defaulted from the task to which the item is charged, or is based on transaction controls. | ||
| BILLABLE_FLAG_DESC | VARCHAR2 | 80 | Indicates description of the billable flag. | ||
| HOLD_FLAG | VARCHAR2 | 1 | Flag that indicates if the item is held from invoicing or revenue depending on report_name. Upon entry, this flag is defaulted to 'N'. | ||
| HOLD_FLAG_DESC | VARCHAR2 | 80 | Indicates description of the hold flag. | ||
| PLAN_HOLD_FLAG | VARCHAR2 | 1 | This column is used to indicate if a bill plan record is on hold. When in hold, no billing downstream processing can occur for the bill plan or revenue plan. Allowed values are, 'Y' or 'N'. | ||
| PLAN_HOLD_FLAG_DESC | VARCHAR2 | 80 | Indicates description of plan hold flag. | ||
| TRANSACTION_DATE | DATE | Indicates date of transaction. | |||
| TRANSACTION_TYPE_CODE | VARCHAR2 | 30 | Indicates type of transaction. | ||
| INVOICE_ID | NUMBER | 18 | Unique identifier of invoice. | ||
| INVOICE_NUM | NUMBER | 18 | Indicates invoice number. | ||
| EVENT_NUM | NUMBER | 18 | Indicates event number. | ||
| READY_TO_ACCRUE_FLAG | VARCHAR2 | 1 | Flag to indicate whether Invoice has been accepted. This flag is used for AS_BILLED revenue | ||
| READY_TO_ACC_DESC | VARCHAR2 | 30 | Indicates description of ready to accrue. | ||
| RA_INVOICE_NUM | VARCHAR2 | 20 | The Oracle Receivables invoice number that is determined upon release of the draft invoice and passed to Oracle Receivables upon transfer. This number can be user-entered or system-generated as defined in the implementation options. | ||
| SYSTEM_REFERENCE | NUMBER | 18 | The reference to the invoice created in Oracle Receivables from the draft invoice. The column is populated by Tieback Invoice and holds the RA_CUSTOMER_TRX.CUSTOMER_TRX_ID | ||
| ACCOUNTING_EVENT_TYPE | VARCHAR2 | 80 | Indicates type of accounting event. | ||
| INVOICE_DATE | DATE | Indicates date of invoice. | |||
| INVOICE_CURRENCY_CODE_DESC | VARCHAR2 | 30 | Indicates description of invoice currency code. | ||
| INVOICE_CURRENCY_AMOUNT | NUMBER | Indicates invoice currency amount. | |||
| LEDGER_CURRENCY_CODE_DESC | VARCHAR2 | 30 | Indicates description of ledger currency code. | ||
| LEDGER_CURRENCY_AMOUNT | NUMBER | Indicates ledger currency amount. | |||
| ACCOUNTING_DATE | DATE | Indicates accounting date. | |||
| ACCOUNTING_PERIOD | VARCHAR2 | 30 | Indicates accounting period | ||
| ERROR_CODE_1 | VARCHAR2 | 30 | Indicates the first ineligiblity message code. | ||
| ERROR_CODE_2 | VARCHAR2 | 30 | Indicates the second ineligiblity message code. | ||
| ERROR_CODE_3 | VARCHAR2 | 30 | Indicates the third ineligiblity message code. | ||
| ERROR_CODE_4 | VARCHAR2 | 30 | Indicates the fourth ineligiblity message code. | ||
| ERROR_CODE_5 | VARCHAR2 | 30 | Indicates the fifth ineligiblity message code. | ||
| 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. | ||
| REQUEST_ID | NUMBER | 18 | Enterprise Service Scheduler: indicates the request ID of the job that created or last updated the row. | ||
| JOB_DEFINITION_NAME | VARCHAR2 | 100 | Enterprise Service Scheduler: indicates the name of the job that created or last updated the row. | ||
| JOB_DEFINITION_PACKAGE | VARCHAR2 | 900 | Enterprise Service Scheduler: indicates the package name of the job that created or last updated the row. | ||
| RUN_ID | VARCHAR2 | 4000 | Indicates the run id when record is populated from Diagnostics. | ||
| EXECUTION_ID | VARCHAR2 | 4000 | Indicates the execution id when record is populated from Diagnostics. This is used in combination with Run id to determine the unique run of Diagnostics | ||
| PROCESS_MODE | VARCHAR2 | 30 | Indicates whether record is populated from Diagnostics or otherwise . If populated from Diagnostics the record shall have value of 'DIAGNOSTICS' else 'REPORT' | ||
| SHIP_TO_ACCOUNT_NAME | VARCHAR2 | 360 | Identifier of Ship to Account Name | ||
| SHIP_TO_SITE_NAME | VARCHAR2 | 360 | Identifier for Ship to Site Name | ||
| SOLD_TO_ACCOUNT_NAME | VARCHAR2 | 360 | Identifier for Sold to Account Name. | ||
| SOLD_TO_SITE_NAME | VARCHAR2 | 360 | Identifier for Sold to Site name | ||
| BILL_TO_SITE_NAME | VARCHAR2 | 360 | Identifier for Bill to Site name | ||
| BILL_TO_SITE_USE_ID | NUMBER | 18 | Identifier for Bill to site use id | ||
| BILL_TO_CUST_ACCT_ID | NUMBER | 18 | Identifier for Bill to customer account | ||
| SHIP_TO_SITE_USE_ID | NUMBER | 18 | Identifier for Ship to Site use | ||
| SHIP_TO_ACCT_ID | NUMBER | 18 | Identifier for Ship to Account | ||
| SOLD_TO_ACCT_ID | NUMBER | 18 | Identifier for Sold to Account | ||
| SOLD_TO_SITE_ID | NUMBER | 18 | Identifier for Sold to Site | ||
| BILL_PLAN_ID | NUMBER | 18 | Identifier for Bill Plan | ||
| CONFIGURATION_ID | NUMBER | 18 | Unique identifier of configuration. | ||
| ERROR_CODE1_TOKEN1 | VARCHAR2 | 30 | First message token pertaining to message ERROR_CODE_1 | ||
| ERROR_CODE1_TOKEN2 | VARCHAR2 | 30 | Second message token pertaining to message ERROR_CODE_1 | ||
| ERROR_CODE2_TOKEN1 | VARCHAR2 | 30 | Message Token pertaining ERROR_CODE_2 | ||
| ERROR_CODE3_TOKEN1 | VARCHAR2 | 30 | Message Token pertaining ERROR_CODE_3 | ||
| ERROR_CODE4_TOKEN1 | VARCHAR2 | 30 | Message Token pertaining ERROR_CODE_4 | ||
| ERROR_CODE5_TOKEN1 | VARCHAR2 | 30 | Message Token pertaining ERROR_CODE_5 | ||
| ERROR_CODE1_VALUE1 | VARCHAR2 | 2000 | First message token value pertaining to ERROR_CODE_1 | ||
| ERROR_CODE1_VALUE2 | VARCHAR2 | 2000 | Second message token value pertaining to ERROR_CODE_1 | ||
| ERROR_CODE2_VALUE1 | VARCHAR2 | 2000 | Message Token value pertaining to ERROR_CODE_2 | ||
| ERROR_CODE3_VALUE1 | VARCHAR2 | 2000 | Message Token value pertaining to ERROR_CODE_3 | ||
| ERROR_CODE4_VALUE1 | VARCHAR2 | 2000 | Message Token value pertaining to ERROR_CODE_4 | ||
| ERROR_CODE5_VALUE1 | VARCHAR2 | 2000 | Message Token value pertaining to ERROR_CODE_5 | ||
| ADDL_INFO1 | VARCHAR2 | 2000 | Additional information related to ineligibility | ||
| ADDL_INFO2 | VARCHAR2 | 2000 | Additional information related to ineligibility |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| PJB_BI_REPORT_DETAILS_N10 | Non Unique | Default | PROCESS_MODE, REPORT_NAME, RUN_ID |
| PJB_BI_REPORT_DETAILS_N2 | Non Unique | Default | REPORT_LINE_NUM |
| PJB_BI_REPORT_DETAILS_N3 | Non Unique | Default | ERROR_CODE_1 |
| PJB_BI_REPORT_DETAILS_N4 | Non Unique | Default | ERROR_CODE_2 |
| PJB_BI_REPORT_DETAILS_N5 | Non Unique | Default | ERROR_CODE_3 |
| PJB_BI_REPORT_DETAILS_N6 | Non Unique | Default | ERROR_CODE_4 |
| PJB_BI_REPORT_DETAILS_N7 | Non Unique | Default | ERROR_CODE_5 |
| PJB_BI_REPORT_DETAILS_N8 | Non Unique | Default | REPORT_LINE_ID, TRANSACTION_ID |
| PJB_BI_REPORT_DETAILS_N9 | Non Unique | Default | REQUEST_ID, TRANSACTION_ID, REPORT_NAME, REPORT_LINE_ID |
| PJB_BI_REPORT_DETAILS_U1 | Unique | Default | ID |