This fact table contains the header level information of cross charge journal transaction which is generated between subsidiaries that provided business services to each other.
Module:
id
| Name | Datatype | Length | Precision | Not Null | Comments | Referred Table | Referred Column |
|---|---|---|---|---|---|---|---|
| id | NUMBER | 38 | 0 | True | Transaction Identifier. | ||
| SOURCE_RECORD_ID | VARCHAR2 | 999 | This column is for Oracle Internal use only. Composite key that consists of all PK values of the transaction. This consists combination of columns that defines the granularity of the table and identifies a row uniquely. | ||||
| ns_number | NUMBER | 38 | 0 | Transaction Number. | |||
| postingperiod | NUMBER | 38 | 0 | Period identifier to which this transaction is posted. | DW_NS_accountingPeriod_D | id | |
| createddate | TIMESTAMP | Transaction creation date. | |||||
| transactionnumber | VARCHAR2 | 256 | The internal transaction number for a transaction. This number is assigned to each transaction by NetSuite and is not editable. | ||||
| posting | VARCHAR2 | 16 | Flag to indicate if this transaction is posting and therefore has General Ledger impact. | ||||
| isbookspecific | VARCHAR2 | 16 | Flag to Indicate if the transaction is a book specific and not book generic. | ||||
| intercotransaction | NUMBER | 38 | 0 | Identifier of the Paired Intercompany Transaction. | DW_NS_CROSS_CHARGE_JOURNAL_F | id | |
| typebaseddocumentnumber | VARCHAR2 | 512 | Another identification for the transaction, which also contains the transaction type info. (eg. SO25). | ||||
| trandisplayname | VARCHAR2 | 999 | Name of transaction, which also contains the transaction type info. The name is a combination of transaction type and document number. | ||||
| entity | NUMBER | 38 | 0 | Entity identifier, Types could be Customer, Partner, Vendor, Employee. | DW_NS_entity_D | id | |
| type | VARCHAR2 | 16 | Transaction type. | DW_NS_STATUS_D | key | ||
| lastmodifieddate | TIMESTAMP | Last Modification Date. | |||||
| trandate | TIMESTAMP | Posting or occurring date of this transaction. | |||||
| createdby | NUMBER | 38 | 0 | Transaction creator identifier. | DW_NS_entity_D | id | |
| tranid | VARCHAR2 | 256 | The document number for a transaction. Examples include invoice numbers on an invoice, entry numbers on a journal entry, or reference numbers on vendor bills. | ||||
| currency | NUMBER | 38 | 0 | Transaction currency identifier. | DW_NS_currency_D | id | |
| recognizedrevenue | NUMBER | Revenue amount that recognized. | |||||
| status | VARCHAR2 | 16 | Read-only field that indicates the status identifier of the transaction. | DW_NS_STATUS_D | code | ||
| foreigntotal | NUMBER | Total amount for a transaction in the transaction's currency, for transactions which include a total amount. | |||||
| foreignamountunpaid | NUMBER | Amount which has not been paid in the foreign transaction currency. | |||||
| foreignamountpaid | NUMBER | Amount paid in the foreign transaction currency. | |||||
| lastmodifiedby | NUMBER | 38 | 0 | ID of the last entity who modified the transaction details. | DW_NS_entity_D | id | |
| memo | VARCHAR2 | 999 | Textual description provided by transaction creators. | ||||
| closedate | TIMESTAMP | Date on which the transaction is closed. | |||||
| billingstatus | VARCHAR2 | 16 | Billing Status shows where the billing document is in the payment workflow process. The workflow is designed to help you identify discrepancies between vendor bills you enter and their originating purchase order before payment is issued for the bill. | ||||
| base_total | NUMBER | Total transaction amount which is recorded in base or subsidiary currency. | |||||
| base_recognizedrevenue | NUMBER | Revenue amount that recognized; which is recorded in base or subsidiary currency. | |||||
| base_amountunpaid | NUMBER | Amount unpaid which is recorded in base or subsidiary currency. | |||||
| base_amountpaid | NUMBER | Amount paid which is recorded in base or subsidiary currency. | |||||
| location | NUMBER | 38 | 0 | Location Identifier. | DW_NS_location_D | id | |
| class | NUMBER | 38 | 0 | Class identifier. Classes are categories that can be created to track records such as financials, transactions, and employees. For example, a company own a janitorial service and want to track income and expenses separately for household and commercial accounts. In this case class can be set up for each account type to track the financial performance of each class over any time period. | DW_NS_classification_D | id | |
| department | NUMBER | 38 | 0 | Department identifier. Departments are categories that you can create to separate and track records such as financials, transactions, and employees. | DW_NS_department_D | id | |
| subsidiary | NUMBER | 38 | 0 | Subsidiary identifier associated with this transaction. | DW_NS_subsidiary_D | id | |
| base_currency | NUMBER | 38 | 0 | Subsidiary currency identifier. | DW_NS_currency_D | id | |
| base_exchangerate | NUMBER | Currency conversion rate between transaction and base or subsidiary currency. | |||||
| is_receiving | VARCHAR2 | 16 | Flag to indicate if a Cross Charge Journal belongs to the Subsidiary acting as a Vendor. | ||||
| is_paying | VARCHAR2 | 16 | Flag to indicate if a Cross Charge Journal belongs to the Subsidiary acting as a Customer. | ||||
| payment_status | VARCHAR2 | 16 | This indicates the payment status of a cross charge journal, it could be of open status or closed status. |
Copyright © 2019, 2025, Oracle and/or its affiliates.