| Line | Field Name | Data Type | Description |
|---|---|---|---|
| 1 | str:fixedAssetAdditions | Table | Fixed asset additions schedule for each fixed asset addition by fixed asset identifier per fixed asset master data. |
| 2 | term:acquisitionDetails | Term (Text/String) | |
| 3 | term:additionType | Term (Text/String) | |
| 4 | term:approvedBy | Term (Text/String) | User ID (from User_Listing file) for person who approved the entry. |
| 5 | term:approvedByDate | Term (Date) | Date the entry was approved. |
| 6 | term:businessUnitCode | Term (Text/String) | Used to identify the business unit, region, branch, and so on at the level that financial statements are being audited and for which the trial balance is generated. For example, you may use a code aligned with the concept of a reportable segment as defined in FASB Accounting Standards Codification (ASC) 280, Segment Reporting. |
| 7 | term:enteredBy | Term (Text/String) | User_ID (from User_Listing file) for person who created the record. |
| 8 | term:enteredDate | Term (Date) | Date the order was entered into the system. This is sometimes referred to as the creation date. This should be a system-generated date (rather than user-entered date), when possible. This date does not necessarily correspond with the date of the transaction itself. |
| 9 | term:fixedAssetAdditionDate | Term (Date) | |
| 10 | term:fixedAssetAdditionId | Term (Text/String) | |
| 11 | term:fixedAssetCost | Term (Decimal) | |
| 12 | term:fixedAssetId | Term (Text/String) | |
| 13 | term:fixedAssetUniqueId | Term (Text/String) | |
| 14 | term:glAccount | Term (Text/String) | |
| 15 | term:glTransactionId | Term (Text/String) | |
| 16 | term:lastModifiedBy | Term (Text/String) | User_ID (from User_Listing file) for the last person modifying this entry. |
| 17 | term:lastModifiedByDate | Term (Date) | |
| 18 | term:lotNumber | Term (Text/String) | |
| 19 | term:placedInService | Term (Text/String) | |
| 20 | term:purchaseOrderDate | Term (Date) | The date of the purchase order, regardless of the date the order is entered. If no purchase order leave blank. |
| 21 | term:purchaseOrderId | Term (Text/String) | Unique identifier for each purchase order. Must match Purchase_Order_ID in the Purchase_Orders_YYYYMMDD_YYYYMMDD file. If no purchase order, leave blank. |
| 22 | term:purchaseOrderRaisedDate | Term (Date) | |
| 23 | term:segment01 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 24 | term:segment02 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 25 | term:segment03 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 26 | term:segment04 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 27 | term:segment05 | Term (Text/String) | Reserved segment field that can be used for profit center, division, fund, program, branch, project, and so on. |
| 28 | term:serialNumber | Term (Text/String) | |
| 29 | term:supplierId | Term (Text/String) | Identifier of the supplier to whom payment is due or from whom unused credits have been applied. Must match the Supplier_Account_ID in the Supplier_Listing_YYYYMMDD file. |
| 30 | term:supplierName | Term (Text/String) | Name of the supplier |
| 31 | term:vatCode | Term (Text/String) |