Input File/Table Hard Validations (Asset_Table)

When importing asset records, Costpoint validates the imported information and stores it in different tables.

Four separate tables store Asset Master data, as shown below.

Table Name	Table Description
ASSET	This table holds data for the majority of Asset Master fields.
ASSET_OTHER_INFO	This table holds “government” user-defined field information as well as other asset information (as an overflow from the ASSET table) for Asset Master records.
ASSET_OTH_BK_DEPR	This table holds optional book information for Books 2-10, as applicable, for Asset Master records.
ASSET_BOOKS_DISP	This table holds depreciation adjustment information for all books, as applicable, related to a disposal.

Except for the Input Row, Status and Record Type record for each table’s input, the fields below belong to the ASSET table, which holds most of the data for Asset records. The fields in the ASSET_OTHER_INFO table hold “government” user-defined field information as well as other asset information (as an overflow from the ASSET table).

When you enter and save an Asset Master record through the Costpoint Fixed Assets Manage Asset Master Information screen, the system automatically creates matching rows in the ASSET and ASSET_OTHER_INFO tables. For the input file involved with this preprocessor, you must establish a “matching” row in both the ASSET and ASSET_OTHER_INFO tables in which the Asset ID and Item No data are identical.

Contents

Field	Description
Input Row	This field (INPUT_ROW) is not a field in the ASSET table, but must be included in the data to be uploaded into the ASSET table by the input file. This field is required. It must be numeric, and it can hold up to10 integers. The value in this field will display on the Error report to help identify records that did not pass one or more validations.
Status	This field (STATUS) is not a field in the ASSET table, but must be included in the data to be uploaded into the ASSET table. This field is required and it can only hold one of these values—“I,” “E,” or “NULL,” as follows: I: records have been successfully uploaded into the Fixed Assets and GENL_UDEF tables E: record that failed hard validations during a previous import attempt that can be fixed and validated for import again. U: records that have been uploaded but have not yet been imported or failed validations during a previous attempt.
Record Type	Record Type is not a field in the ASSET table, but must be included in the data to be uploaded into the ASSET table by input row. This field is required and is only used for the input file. It can only hold one of the following alphabetic characters: H: Header table A: Asset table B: Other Books table O: Other Info/Books Disposal tables U: User-Defined tables The purpose of the record type designation is to indicate whether the row is a header row or whether it should be linked with the ASSET, ASSET_OTH_BK_DEPR, or other tables that store Asset Master data (such as ASSET_OTHER_INFO or ASSET_BOOKS_DISP or GEN_UDEF).
Asset ID	This field Asset ID (ASSET_ID), together with the Item No field (ITEM_NO), supplies the unique two-part key identifier for each Asset Master record. Although this field in an Asset Master record will accept up to 10 alphanumeric characters, you must have previously designated the size of this field in the Length of Asset Number field on the Configure Fixed Assets Settings screen (FA_SETTINGS.ASSET_ID_LEN_NO). The designated length must exceed 3 characters and be 10 characters or less. The length of numeric Asset ID's must equal the length designated on the Configure Fixed Assets Settings screen and cannot exceed that number. The length on alpha-numeric Asset ID’s must not exceed this number. The Asset ID/Item No combination must not already exist in the destination database, and it must be unique within the ASSET table. If the Asset ID and Item Number are missing and the Automatic Numbering for Asset Records has been selected on the screen, the system will automatically insert the next asset number in the sequence that displays in the Last Asset Number field on the Configure Fixed Assets Settings screen. Note that the system will increment the right-most numeric digit for that asset number and will not automatically increment alphabetic characters. You must have previously enabled the automatic numbering feature on that screen by selecting the Enable Automatic Numbering for Asset Master Records check box on that screen (Configure Fixed Assets Settings). You must enter data for the Last Asset Number field if you have selected the Enable Automatic Numbering for Asset Master Records check box. If the Asset ID and Item No are missing and the Automatic Numbering for Asset Records has been selected on the screen but the Enable Automatic Numbering for Asset Master Records check box on the Configure Fixed Assets Settings screen is cleared, there will be an error message saying that the check box on the Configure Fixed Assets Settings screen must be selected to use this option. Either the check box on Configure Fixed Assets Settings must be selected with a valid value in the Last Asset Number field, or the Automatic Numbering for Asset Records field must be cleared. When importing with an ASCII import file, the order of the rows is critical, particularly when one or more asset records will not be having asset/item numbers on the import file. The records must be arranged on the file in the following order for each asset, assuming the Header row is listed first: A (Asset table data,) B (Other Books table data,) O (Other Info/Books Disposal table data,) and then any U (User-defined table data.) When importing by scripting data into the input tables, the rows for each asset must have a temporary, unique value in the AUTO_NO_GRP column in each table. This unique value will be the same for all of the records associated with an asset record, so that the import application assigns the same asset/item number to all of the asset’s records. If the Asset ID and the Item Number are missing and you have NOT turned on the automatic numbering feature, the record will fail validations and the applicable Row Number for the record will display on the Error report. Each Asset ID/Item No combination must have a record with the same Asset ID/Item No for the ASSET_OTHER_INFO table with Record Type B . If the asset’s status is D (Disposal), this Asset ID/Item No combination must have a record with the same Asset ID/Item No for the ASSET_BOOKS_DISP table with Record Type O. The system will not allow duplicate asset/item numbers for the same record type except for the User-Defined table data having Record Type U. (For example, in the ASSET table, record type A cannot exist more than once for the same asset/item number.) Preprocessor Default Rules: If Asset Number and Item type are missing, the asset number following the value in the Last Asset Number field in Configure Fixed Assets Settings (FA_SETTINGS.LAST_ASSET_ID) will be inserted if Enable Automatic Numbering is selected on the Configure Fixed Assets Settings and Automatic Numbering for Asset Records is selected on the preprocessor screen. The Last Asset Number field will be incremented by 1 when this occurs. Possible Error Messages: ERROR MESSAGE: This numeric Asset ID length is too short per FA Settings. Note: Numeric Asset ID’s can be front-loaded with zeroes so that the length of the desired asset ID value matches the Length of Asset Number value in Configure Fixed Assets Settings. ERROR MESSAGE: Asset ID is NULL and Auto numbering is not activated. ERROR MESSAGE: Asset ID is less than 3 characters in length. Note: Any Asset ID, whether numeric or alphanumeric, can be front-loaded with zeroes to increase the length of the value to a valid length. ERROR MESSAGE: This Asset ID/Item No’s ASSET_OTHER_INFO record is missing. ERROR MESSAGE: This Asset ID/Item No’s ASSET_BOOKS_DISP record is missing. ERROR MESSAGE: Asset ID exceeds value from FA Settings. ERROR MESSAGE: This Asset ID/Item No already exists in the database. Note: This record may have already been loaded into the database, so this validation helps to prevent duplicate asset records. If the asset represented by the record to be loaded is unique from an asset already in the destination database but is related to the existing record with the same asset number, a different item number can be assigned to the record being imported so that the asset ID doesn’t have to be changed. ERROR MESSAGE: This Row Type “A” asset is duplicated in the input file. Note: This error occurs when two records in the input file with Row Type A have the same Asset ID/Item No combination. If the two records actually represent two different assets, consider increasing the item number so that the Asset ID/Item No combinations are unique. If you do this, remember to also modify the Item No of related records having Record Types B, O or U. ERROR MESSAGE: This Asset is duplicated in the table FA_IMP_ASSET. Note: This error occurs when two records in the import table data have the same Asset ID/Item No combination. If the two records actually represent two different assets, consider increasing the item number so that the Asset ID/Item No combinations are unique. If you do this, remember to also modify the Item No for related records in the other import tables. ERROR MESSAGE: AUTO_NO_GRP must be populated when Asset/Item No are blank. Note: This error occurs when the Asset ID/Item No and AUTO_NO_GRP are blank when adding records using table data.
Item No	This field Item No (ITEM_NO), together with the Asset ID field (ASSET_ID), supplies the unique two-part key identifier for each Asset Master record. Each asset number must have a unique item number that is numeric, greater than zero, and does not exceed “99999.” If you previously enabled the automatic numbering feature by selecting the Enable Automatic Numbering for Asset Master Records check box on the Configure Fixed Assets Settings screen, the system will automatically assign “00001” as the default item number for records in which the Asset ID and the Item No are missing. You must populate this required field if you have not enabled the automatic numbering feature on the Configure Fixed Assets Setting screen and selected Automatic Numbering for Asset Records on the preprocessor screen. Even if you have enabled the automatic numbering feature on the Configure Fixed Assets Setting screen and selected Automatic Numbering for Asset Records on the preprocessor screen, you must populate this field if the Asset ID field is populated. Preprocessor Default Rules: The system will assign “00001” for the Item Number if the Asset ID and Item No fields are not populated and you have enabled the automatic numbering feature on the Configure Fixed Assets Setting screen and selected Automatic Numbering for Asset Records on the preprocessor screen. Possible Error Messages: ERROR MESSAGE: Item No must be a numeric value. ERROR MESSAGE: Item No is NULL and Auto numbering is not activated. ERROR MESSAGE: Item No exceeds 5 characters.
Template No	This Template No field (FA_TEMPLATE_ID), together with the optional Rev No field, supplies the unique two-part key identifier for each Asset Template record. The template identifier can hold up to 30 alphanumeric characters. Each user-defined template represents a set of user-specified default data that can be easily imported into Asset Master records, where it can be edited as desired. Template numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If a field is blank in the input file/table for which there is a corresponding template data field that is populated, the system will use the Template No value to determine the data for that field. In the circumstance that data exists in the input file/table field, even if there is a corresponding template data field that is populated, the system will bypass any reference to the Template No. Preprocessor Default Rules: If the FA_TMPLT_ID is NULL in the input file/table, insert a space (‘ ‘), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: This Template No exceeds 30 characters. ERROR MESSAGE: This Template No/Rev No combination does not exist.
Revision No	This optional field (FA_TEMPLATE_REV_NO), together with the optional Template No field, supplies the unique two-part key identifier for each Asset Template record, as applicable. A revision number is not required when you set up an Asset Template. If you have set up a template number with an associated revision number, however, the revision number must be entered along with the template number to supply the unique Asset Template identifier. The revision number can hold up to a maximum of 3 numeric characters. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If a field is blank in the input file/table for which there is a corresponding template data field that is populated, the system will use the Template No value to determine the data for that field. In the circumstance that data exists in the input file/table, even if there is a corresponding template data field that is populated, the system will bypass any reference to the Template No. Preprocessor Default Rules: If the FA_TMPLT_REV_NO is NULL in the input file/table, insert a space (‘ ‘), since NULLs are not permitted by the system for this field. Possible Error Message: ERROR MESSAGE: Rev No exceeds 3 characters.
Short Desc	This optional field (SHORT_DESC) holds up to 30 alphanumeric characters, as applicable, and can be populated by manual entry or by importing data from a specified Asset Template record. This field is not system-validated in an Asset Master record. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the short description field is blank in the input file/table for which there is a corresponding template data field that is populated, the system will use the Template No value to determine the data for that field. In the circumstance that data exists in the input file/table for short description, even if there is a corresponding template data field that is populated, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file/table and template, insert a space (‘ ‘), since NULLs are not permitted by the system for this field. Possible Error Message: ERROR MESSAGE: Short Desc cannot exceed 30 alphanumeric characters.
Long Desc	This optional field (LONG_DESC) holds up to 60 alphanumeric characters, as applicable, and can be populated by manual entry or by importing data from a specified Asset Template record. This field is not system-validated in an Asset Master record. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the long description field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No value to determine the data for that field. In the circumstance that data exists in the input file/table for long description, even if there is a corresponding template data field that is populated, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file/table and template, insert a space (‘ ‘), since NULLs are not permitted by the system for this field. Possible Error Message: ERROR MESSAGE: Long Desc cannot exceed 60 alphanumeric characters.
Addt’l Desc	This optional field (ADDTL_DESC_NOTES) holds up to 254 alphanumeric characters, as applicable, and can be populated by manual entry or by importing data from a specified Asset Template record. This field is not system-validated in an Asset Master record. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the additional description field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No value to determine the data for that field. In the circumstance that data exists in the input file/table for the additional description field, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file/table and template, insert a space (‘ ‘), since NULLs are not permitted by the system for this field. Possible Error Message: ERROR MESSAGE: Addtl Desc cannot exceed 254 alphanumeric characters.
Classification Code	This required field (FA_CLASSIF_CD) holds up to 6 alphanumeric characters, and can be populated by manual entry or by importing data from a specified Asset Template record. Classification Codes are validated against user-specified data initialized on the Manage Classification Codes screen. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Classification Code field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No value to determine the data for that field. In the circumstance that data exists in the input file/table for the Classification Code field, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Possible Error Messages: ERROR MESSAGE: Class Code is a required field. ERROR MESSAGE: Class code exceeds 6 characters. ERROR MESSAGE: This Class Code does not exist.
Property Type	This required field (PRPTY_TYPE) holds up to 6 alphanumeric characters, and can be populated by manual entry or by importing data from a specified Asset Template record. Property Types are validated against user-specified data initialized on the Manage Property Types screen. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Property Type field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No value to determine the data for that field. In the circumstance that data exists in the input file/table for the Property Type field, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Possible Error Messages: ERROR MESSAGE: Property Type is a required field. ERROR MESSAGE: Property Type exceeds 6 characters. ERROR MESSAGE: This Property Type does not exist.
Depr Status	This required field (S_DEPR_STATUS_CD) holds a single-character “D” (Depreciable) or “N” (Non-Depreciable) selection. The system default for this field is “D” (Depreciable), which can be changed by manual entry or by importing data from a specified Asset Template record. If a record is depreciable, the system requires additional data, including the basis for depreciation, a valid depreciation method code, and codes for valid G/L depreciation expense and accumulated depreciation account combinations. If a record is non-depreciable, the system automatically disables access to the G/L Book and Other Book data fields in the Asset Master record. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the depreciation status field is blank in the input file/table for which there is a corresponding template data field, the system will use the Template No value to determine the data for that field. In the circumstance that data exists in the input file/table for the depreciation status field, even if there is a corresponding template data field, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file/table and there is no template, enter “D” or “N” as the default for this field. Possible Error Messages: ERROR MESSAGE: Depr Status is not “D” or “N.” ERROR MESSAGE: Depr Status exceeds 1 character.
Record Status	This required field (S_STATUS_CD) holds a single-character A (Active), I (Inactive), or D (Disposal) selection. The system default for this field is A (Active), which can be changed by manual entry or by importing data from a specified Asset Template record. If an Asset Master record is inactive or has a disposal status, the system will automatically exclude it from depreciation calculations and from reports that do not specify its inclusion. If disposal data exists, the system requires that the record status must be equal to D (Disposal). Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Record Status field is blank in the input file/table and a template has been assigned, the system will use the Template No value to determine the data for that field. In the circumstance that data exists in the input file/table for Record Status, even if a template has been assigned, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file/table and there is no template, enter “A” or “I” for this field. Possible Error Messages: ERROR MESSAGE: Record Status is not “A,” “I,” or “D.” ERROR MESSAGE: Record Status exceeds 1 character. ERROR MESSAGE: Record Status must be “D” when disposal data exists.
Depr Based On	If a record is depreciable, the system requires additional data, including the basis for depreciation, a valid depreciation method code, and codes for valid G/L depreciation expense and accumulated depreciation account combinations. This required field (S_DEPR_BASED_ON_CD) holds a single-character Y (Years), U (Units of Usage), or L (Lease Pds) selection, which specifies the depreciation methodology to be used for depreciable assets. The system default for this field is Y (Years), which can be changed by manual entry or by importing data from a specified Asset Template record. Because this field is required, you should automatically enter Y (Years) for a non-depreciable asset record. Because each of the three base methods (Years, Units, Leases) for depreciating assets uses some specific terminology and concepts that are not mutually shared, the purpose of this selection is to ensure the display of the appropriate screen when you access the G/L Book subtask from an Asset Master record. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Depreciation Based On field is blank in the input file/table and a template has been assigned, the system will use the Template No value to determine the data for that field. In the circumstance that data exists in the input file/table for the Depreciation Based On field, even a template has been assigned, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file/table and there is no template, enter “Y”, “U” or “L” for this field. Note: When you enter a non-depreciable record through the Manage Asset Master Information screen, the system automatically populates this field with a “Y.” Possible Error Messages: ERROR MESSAGE: Value does not equal “Y” for a Non-Depreciable asset. ERROR MESSAGE: Depr Based On exceeds 1 character. ERROR MESSAGE: Depr Based On is not “Y,” “U,” or “L.”
Vendor ID	This optional field (VEND_ID) holds up to 12 alphanumeric characters, and can be populated by manual entry or by importing data from a specified Asset Template record. This field is not system-validated in an Asset Master record. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Vendor ID field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No value to determine the data for that field. In the circumstance that data exists in the input file/table for Vendor ID, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Possible Error Message: ERROR MESSAGE: Vendor ID exceeds 12 characters.
Vendor Name	This optional field (VEND_NAME) holds up to 25 alphanumeric characters, and can be populated by manual entry or by importing data from a specified Asset Template record. This field is not system validated in an Asset Master record. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Vendor Name field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No value to determine the data for that field. In the circumstance that data exists in the input file/table for Vendor Name, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file/table and template, insert a space (‘ ‘), since NULLs are not permitted by the system for this field. Possible Error Message: ERROR MESSAGE: Vendor Name exceeds 25 characters.
Manufacturer ID	This optional field (MANUF_ID) holds up to 10 alphanumeric characters, and can be populated by manual entry or by importing data from a specified Asset Template record. This field is not system-validated in an Asset Master record. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Manufacturer ID field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No value to determine the data for that field. In the circumstance that data exists in the input file/table for Manufacturer ID, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Possible Error Message: ERROR MESSAGE: This Manuf ID exceeds 10 alphanumeric characters.
Manufacturer Name	This optional field (MANUF_NAME) holds up to 30 alphanumeric characters, and can be populated by manual entry or by importing data from a specified Asset Template record. This field is not system validated in an Asset Master record. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Manufacturer Name field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No value to determine the data for that field. In the circumstance that data exists in the input file/table for Manufacturer Name, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file/table and template, insert a space (‘ ‘), since NULLs are not permitted by the system for this field. Possible Error Message: ERROR MESSAGE: This Manuf Name exceeds 30 alphanumeric characters.
Model No	This optional field (MODEL_NO) holds up to 30 alphanumeric characters, and can be populated by manual entry or by importing data from a specified Asset Template record. This field is not system-validated in an Asset Master record. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the model number field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No value to determine the data for that field. In the circumstance that data exists in the input file/table for model number, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file/table and template, insert a space (‘ ‘), since NULLs are not permitted by the system for this field. Possible Error Message: ERROR MESSAGE: This Model No exceeds 30 alphanumeric characters.
Condition Code	This required field (S_CONDITION_CD) holds a single-character N (New) or U (Used) selection. The system default for this field is N (New), which can be changed by manual entry or by importing data from a specified Asset Template record. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Condition Code field is blank in the input file/table for which there is a template attached, the system will use the Template No value to determine the data for that field. In the circumstance that data exists in the input file/table for Condition Code, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file/table and there is no template, enter “N” or “U” for this field. Possible Error Messages: ERROR MESSAGE: This Condition is not “N” or “U.” ERROR MESSAGE: Condition exceeds 1 alphanumeric character.
City	This optional field (CITY_NAME) holds up to 25 alphanumeric characters. You should enter data in this field only if you have not specified a Location Group and have not designated an Asset Template that contains a Location Group. If this field is populated for a record containing a Location Group or for a record containing an Asset Template that contains a Location Group, then the value in this field in the input file record will be ignored. The imported record will contain the value assigned to this field in the designated Location Group. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Location Group field is blank in the input file/table and a template containing a Location Group is assigned to the record, the system will use the value in the City field of the Template (if it exists) to determine the data for the City field. In the circumstance that data exists in the input file/table for Location Group, even if there is a corresponding template data field value for Location Group or City, the system will bypass any reference to the Template No. Preprocessor Default Rules: If the Location Group (FA_LOC_GROUP_CD) is not NULL in the input file/table, enter the City associated with the Location Group Code in the Receiving database. If the Location Group (FA_LOC_GROUP_CD) is NULL in the input file/table but not NULL in the Template, enter the City associated with the Template Location Group Code in the Receiving database. If the Location Group field is NULL in the input file/table and template and City are also NULL, insert a space (‘ ‘) for City since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: This City exceeds 25 alphanumeric  characters. ERROR MESSAGE: City cannot be entered when Location Group is used.
State/Province	This optional field (MAIL_STATE_CD) holds up to 15 alphanumeric characters. You should enter data in this field only if you have not specified a Location Group or designated an Asset Template that contains a Location Group. If this field is populated for a record containing a Location Group or for a record containing an Asset Template that contains a Location Group, then the value in this field in the input file record will be ignored. The imported record will contain the value assigned to this field in the designated Location Group. States/provinces are validated against user-specified data initialized on the Manage Postal Codes screen. If you enter state/province data, you must also enter valid data in the Country field. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Location Group field is blank in the input file/table and a template containing a Location Group is assigned to the record, the system will use the value in the City field of the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for location group, even if there is a corresponding template data field value for Location Group or State/Province, the system will bypass any reference to the Template No. Preprocessor Default Rules: If the Location Group Code (FA_LOC_GROUP_CD) is not NULL in the input file/table, enter the State/Province associated with the Location Group Code in the Receiving database. If the Location Group Code (FA_LOC_GROUP_CD) is NULL in the input file/table but not NULL in the Template, enter the State/Province associated with the Template Location Group Code in the Receiving database. Possible Error Messages: ERROR MESSAGE: This State/Province exceeds 15 alphanumeric  characters. ERROR MESSAGE: This State/Province does not exist. ERROR MESSAGE: State/Province cannot be entered  when  Location Group is used.
Postal Code	This optional field (POSTAL_CD) holds up to 10 alphanumeric characters. You should enter data in this field only if you have not specified a Location Group or designated an Asset Template that contains a Location Group. If this field is populated for a record containing a Location Group or for a record containing an Asset Template that contains a Location Group, then the value in this field in the input file record will be ignored. The imported record will contain the value assigned to this field in the designated Location Group. Postal codes are validated against user-specified data initialized on the Manage Postal Codes screen. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Location Group field is blank in the input file/table and a template containing a Location Group is assigned to the record, the system will use the value in the Postal Code field of the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Location Group, even if there is a corresponding template data field value for Location Group or Postal Code, the system will bypass any reference to the Template No. Preprocessor Default Rules: If the Location Group (FA_LOC_GROUP_CD) is not NULL in the input file/table, enter the Postal Code associated with the Location Group in the Receiving database. If the Location Group (FA_LOC_GROUP_CD) is NULL in the input file/table but not NULL in the Template, enter the Postal Code associated with the Location Group in the Receiving database. If the Location Group field is NULL in the input file/table and Template No and Postal Code are also NULL, insert a space (‘ ‘) for Postal Code since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: This Postal Code exceeds 10 alphanumeric  characters. ERROR MESSAGE: This Postal Code does not exist. ERROR MESSAGE: Postal Code cannot be entered when  Location Group is used
County	This optional field (COUNTY_NAME) holds up to 25 alphanumeric characters, and is not system-validated in an Asset Master record. You should enter data in this field only if you have not specified a Location Group or designated an Asset Template that contains a Location Group. If this field is populated for a record containing a Location Group or for a record containing an Asset Template that contains a Location Group, then the value in this field in the input file record will be ignored. The imported record will contain the value assigned to this field in the designated Location Group. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Location Group field is blank in the input file/table and a template containing a Location Group is assigned to the record, the system will use the value in the County field of the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Location Group Code, even if there is a corresponding template data field value for Location Group Code or County, the system will bypass any reference to the Template No. Preprocessor Default Rules: If the Location Group (FA_LOC_GROUP_CD) is not NULL in the input file/table, enter the Postal Code associated with the Location Group in the Receiving database. If the Location Group (FA_LOC_GROUP_CD) is NULL in the input file/table but not NULL in the Template, enter the Postal Code associated with the Location Group in the Receiving database. If the Location Group field is NULL in the input file/table and Template No and Postal Code are also NULL, insert a space (‘ ‘) for Postal Code since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: This Postal Code exceeds 10 alphanumeric  characters. ERROR MESSAGE: This Postal Code does not exist. ERROR MESSAGE: Postal Code cannot be entered when  Location Group is used
Country	This optional field (COUNTRY_CD) holds up to 8 alphanumeric characters. You should enter data in this field only if you have not specified a Location Group or designated an Asset Template that contains a Location Group. If this field is populated for a record containing a Location Group or for a record containing an Asset Template that contains a Location Group, then the value in this field in the input file record will be ignored. The imported record will contain the value assigned to this field in the designated Location Group. Country data is validated against user-specified data initialized on the Manage Countries screen. In addition, Country data is also validated against any value entered for State/Province. The Country and State/Province combination is initialized on the Manage States and Provinces screen. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Location Group field is blank in the input file/table and a template containing a Location Group is assigned to the record, the system will use the Country field value in the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Location Group Code, even if there is a corresponding template data field, the system will bypass any reference to the Template No. Preprocessor Default Rules: If the Location Group (FA_LOC_GROUP_CD) is not NULL in the input file/table, enter the Country associated with the Location Group in the Receiving database. If the Location Group (FA_LOC_GROUP_CD) is NULL in the input file/table but not NULL in the Template, enter the Country associated with the Template Location Group Code in the Receiving database. Possible Error Messages: ERROR MESSAGE: Country exceeds 8 alphanumeric  characters. ERROR MESSAGE: This Country Code does not exist.
Location Group	This optional field (FA_LOC_GRP_CD) holds up to 10 alphanumeric characters. A location group identifies a set of pre-established location data that includes the city, state, country, and county fields, as well as any user-specified location codes data. If you do not specify a location group, you can enter city, state, country, and county data on a field-by-field basis. Note: If a location group is included on a record in the input file or in a template included on a record in the input file, any input file values for the City, State/Province, Country, Postal Code, and County fields will be ignored during the import process. These fields will instead be populated by the pre-established location data associated with the location group on the Manage Location Groups screen in the receiving database. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Location Group field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Location Group set up for the  Template No (if it exists) to determine the value for Location Group. In the circumstance that data exists in the input file/table for Location Group, even if there is a corresponding template data field, the system will bypass any reference to the Template No. Possible Error Messages: ERROR MESSAGE: Location Group exceeds 10 alphanumeric characters. ERROR MESSAGE: This Location Group does not exist.
Location 1 Code	If you designated a value for Location 1 Label field on the Manage Asset Master Field Labels screen, your label description for Location 1 will automatically display at this field. Note: It is not a system requirement that you establish a label for this field. If you did not establish a label for this field, “Location 1” displays as the default label for this field. This optional field (FA_LOC1_CD) holds up to 8 alphanumeric characters, and can be populated by manual entry or by assigning a Location Group or by importing data from a specified Asset Template record. Location 1 Codes are validated against user-specified data initialized on the Manage Location 1 Codes screen. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Location Group field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Location Group set up for the Template No to determine the value for that Location 1 Code. In the circumstance that data exists in the input file/table for Location Group, even if there is a corresponding template data field, the system will bypass any reference to the Template No. If the Asset Template does not contain data in this field from which to provide a default, you may find that this field is already populated with data from a specified Location Group on the asset record. In any case, after the Location Group value for the Location 1 Code field has been applied to the record during the import process, you can overwrite that Location 1 Code with other validated data, as desired. Possible Error Messages: ERROR MESSAGE: Location 1 Cd exceeds 8 alphanumeric characters. ERROR MESSAGE: This Location 1 Cd does not exist.
Location 2 Code	If you designated a value for Location 2 Label field on the Manage Asset Master Field Labels screen, your label description for "Location 2" will automatically display at this field. Note: It is not a system requirement that you establish a label for this field. If you did not establish a label for this field, “Location 2” displays as the default label for this field. This optional field (FA_LOC2_CD) holds up to 8 alphanumeric characters, and can be populated by manual entry or by assigning a Location Group or by importing data from a specified Asset Template record. Location 2 Codes are validated against user-specified data initialized on the Manage Location 2 Codes screen. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Location Group field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Location Group set up for the Template No to determine the value for that Location 2 Code. In the circumstance that data exists in the input file/table for Location Group, even if there is a corresponding template data field, the system will bypass any reference to the Template No. If the Asset Template does not contain data in this field from which to provide a default, you may find that this field is already populated with data from a specified Location Group on the asset record. In any case, after the Location Group value for the Location 2 Code field has been applied to the record during the import process,  you can overwrite that Location 2 Code with other validated data, as desired. Possible Error Messages: ERROR MESSAGE: Location 2 Cd exceeds 8 alphanumeric characters. ERROR MESSAGE: This Location 2 Cd does not exist.
Location 3 Code	If you designated a value for Location 3 Label on the Manage Asset Master Field Labels screen, your label description for Location 3 will automatically display at this field. Note: It is not a system requirement that you establish a label for this field. If you did not establish a label for this field, “Location 3” displays as the default label for this field. This optional field (FA_LOC3_CD) holds up to 8 alphanumeric characters, and can be populated by manual entry or by assigning a Location Group or by importing data from a specified Asset Template record. Location 3 Codes are validated against user-specified data initialized on the Manage Location 3 Codes screen. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Location Group field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Location Group set up for the Template No to determine the value for that Location 3 Code. In the circumstance that data exists in the input file/table for Location Group, even if there is a corresponding template data field, the system will bypass any reference to the Template No. If the Asset Template does not contain data in this field from which to provide a default, you may find that this field is already populated with data from a specified Location Group on the asset record. In any case, after the Location Group value for the Location 3 Code field has been applied to the record during the import process you can overwrite that Location 3 Code with other validated data, as desired. Possible Error Messages: ERROR MESSAGE: Location 3 Cd exceeds 8 alphanumeric characters. ERROR MESSAGE: This Location 3 Cd does not exist.
Accumulated Depreciation Account Code	This field (ACCUM_DEPR_ACCT_CD) is required for depreciable assets only, and cannot be entered for non-depreciable assets. The accumulated depreciation account code holds up to 6 alphanumeric characters, and can be populated by manual entry or by importing data from a specified Asset Template record. Accumulated Depreciation Account Codes are validated against user-specified data initialized on the Manage Accumulated Depreciation Account Codes screen. An accumulated depreciation account code specifies the required General Ledger account and organization (as well as the project and reference 1 and 2 numbers, as applicable) to which accumulated depreciation will be posted for the asset record Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Accumulated Depreciation Account Code field is blank in the input file/table for which there is a corresponding template data field, the system will use the Template No to determine the value for that Accumulated Depreciation Account Code. In the circumstance that data exists in the input file/table for Accumulated Depreciation Account Code, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Possible Error Messages: ERROR MESSAGE: Accum Depr Acct Cd exceeds 6 alphanumeric characters. ERROR MESSAGE: A code cannot be entered for a Non-Depreciable asset. ERROR MESSAGE: This Accum Depr Acct Code does not exist.
Depreciation Expense Account Allocation Code	This field (DEPR_EXP_ALC_CD) is required for depreciable assets only, and cannot be entered for non-depreciable assets. The depreciation expense account allocation code holds up to 6 alphanumeric characters, and can be populated by manual entry or by importing data from a specified Asset Template record. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already recorded depreciation to avoid unexpected results. Depreciation Expense Account Allocation Codes are validated against user-specified data initialized on the Manage Depreciation Expense Acct Allocation Codes screen. A depreciation expense account allocation code specifies the required General Ledger account and organization (as well as the project and reference 1 and 2 numbers, as applicable) to which depreciation will be posted for the asset record. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Depreciation Expense Account Allocation Code field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No (if it exists) to determine the value for that Depreciation Expense Account Allocation Code. In the circumstance that data exists in the input file/table for Depreciation Expense Account Allocation Code, even if there is a corresponding template data field value, the system will bypass any reference to the Template No.
Tag Number	This optional field (TAG_NO_S) holds up to 30 alphanumeric characters, can be populated by manual entry, and the data is not system-validated. If it is your company policy to assign the physical property tag number as the unique identifier for an asset record, the data in this field will be the same as the identifier in the Asset No field. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a space (‘ ‘), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: This Tag Number exceeds 30 alphanumeric characters.
Acquisition Date	This optional field (ACQ_DT) holds date-formatted data (YYYY-MM-DD) to designate an acquisition date. It can be populated by manual entry and the data is not system-validated. Note: The acquisition date displays in a specific field with both the Purchase Info and the Govt Info in an Asset Master record. User edits to this field in one location automatically display in both field locations. The acquisition date is normally associated with a “purchase” date, based on how you define it. Although there is no system validation of the data in this field, you may want to develop some internal rules on its use, since there are four additional (and optional) date fields already related to Purchase Info data (PO Date, Receipt Date, Invoice Date, and Voucher Date) as well as two additional date fields related to depreciation ( Depr Start Date and In-Srvc Date) in an Asset Master record. You will likely correlate the optional acquisition date with other required purchase-related data in the Asset Master record, such as the Fiscal Year, Acct Pd, and Subperiod information (although there is no requirement to do so). There is no corresponding Asset Template field.
PO Date	This optional field (PO_DT) holds date-formatted data (YYYYMMDD) to designate a purchase order date and can be populated by manual entry. The data for this field is not system-validated in an Asset Master record. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: PO Date is an invalid date format. ERROR MESSAGE: PO Date exceeds 10 characters.
PO No	This optional field (PO_ID) holds up to 10 alphanumeric characters and can be populated by manual entry. The data for this field is not system-validated in an Asset Master record. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: This PO No exceeds 10 alphanumeric characters.
Rel No	This optional field (PO_RLSE_NO) holds up to 3 numeric characters and can be populated by manual entry. The data for this field is not system-validated in an Asset Master record. The release number applies to a blanket purchase order. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: PO Rlse No exceeds 4 characters. ERROR MESSAGE: PO Rlse No is not numeric.
PO Line No	This optional field (PO_LN_NO) holds up to 4 numeric characters and can be populated by manual entry. The data for this field is not system-validated in an Asset Master record. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a “0” (zero), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: PO Line No exceeds 4 characters. ERROR MESSAGE: PO Line No is not numeric.
Receipt Date	This optional field (RECPT_DT) holds date-formatted data (YYYYMMDD) to designate a receipt date and can be populated by manual entry. The data for this field is not system-validated in an Asset Master record. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: Receipt Date is an invalid date format. ERROR MESSAGE: Receipt Date exceeds 10 characters.
Packing Slip	This optional field (PS_ID) holds up to 15 alphanumeric characters and can be populated by manual entry. The data for this field is not system-validated in an Asset Master record. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: This Packing Slip exceeds 15 alphanumeric characters.
Invoice Date	This optional field (INVC_DT) holds date-formatted data (YYYYMMDD) to designate an invoice date and can be populated by manual entry. The data for this field is not system-validated in an Asset Master record. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: Invoice Date is an invalid date format. ERROR MESSAGE: Invoice Date exceeds 10 characters.
Invoice No	This optional field (INVC_ID) holds up to 15 alphanumeric characters and can be populated by manual entry. The data for this field is not system-validated in an Asset Master record. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a space (‘ ‘), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: This Invoice No exceeds 15 alphanumeric characters.
Vchr Date	This optional field (VCHR_DT) holds date-formatted data (YYYYMMDD) to designate a voucher date and can be populated by manual entry. The data for this field is not system-validated in an Asset Master record. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: Voucher Date is an invalid date format. ERROR MESSAGE: Voucher Date exceeds 10 characters.
Vchr No	This optional field (VCHR_NO) holds up to 9 numeric characters and can be populated by manual entry. The data for this field is not system-validated in an Asset Master record. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a “0” (zero), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Voucher No exceeds 9 numeric characters. ERROR MESSAGE: Voucher No is not numeric.
Serial No	This optional field (SERIAL_ID) holds up to 20 alphanumeric characters and can be populated by manual entry. The data for this field is not system-validated in an Asset Master record. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: This Serial No exceeds 20 alphanumeric characters.
Acquisition Fiscal Year	This required field (ACQ_FY_CD) holds up to 6 alphanumeric characters and can be populated by manual entry. There is no corresponding Asset Template field. You will normally enter data in this field that reflects the fiscal year related to the purchase (or acquisition) date for the Asset Master record, and not necessarily the current fiscal year. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field to avoid unexpected results. Possible Error Messages: ERROR MESSAGE: This Acquisition Fiscal Year does not exist. ERROR MESSAGE: Invalid Acquisition Fiscal year/Period combination. ERROR MESSAGE: Acquisition Fiscal Year is required. ERROR MESSAGE: Fiscal Year exceeds 6 alphanumeric characters.
Acquisition Acct Pd	This required field (ACQ_PD_NO) holds up to 2 numeric characters and can be populated by manual entry. There is no corresponding Asset Template field. You will normally enter data in this field that reflects the accounting period related to the purchase (or acquisition) date for the Asset Master record, and not necessarily the current accounting period. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field to avoid unexpected results. Possible Error Messages: ERROR MESSAGE: Acq Pd No is required. ERROR MESSAGE: Acq Pd No is not numeric. ERROR MESSAGE: Invalid Fiscal Year/Period combination. ERROR MESSAGE: Acq Pd No exceeds 2 characters.
Acquisition Subperiod	This required field (ACQ_SUB_PD_NO) holds up to 2 numeric characters and can be populated by manual entry. The data for this field is not system-validated in an Asset Master record. There is no corresponding Asset Template field. You will normally enter data in this field that reflects the accounting subperiod related to the purchase (or acquisition) date for the Asset Master record, and not necessarily the current accounting subperiod. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field to avoid unexpected results. Possible Error Messages: ERROR MESSAGE: Acq Subpd No is required. ERROR MESSAGE: Acq Subpd No is not numeric. ERROR MESSAGE: Acq Pd No exceeds 2 characters.
Quantity	This optional field (UNITS_QTY_NO) holds up to 4 numeric characters and can be populated by manual entry. The data for this field is not system-validated in an Asset Master record. The data in this field is for information purposes only and is not used by the system for any calculations. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a “0” (zero), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Quantity exceeds 4 characters. ERROR MESSAGE: Quantity is not numeric.
Unit of Measure	This optional field (UM_S) holds up to 10 alphanumeric characters and can be populated by manual entry. The data for this field is not system-validated in an Asset Master record. The data in this field is for information purposes only and is not used by the system for any calculations. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a ‘ ‘ (space), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: This Unit of Measure exceeds 10 characters.
Unit Price	This optional field (PRICE_AMT) holds the asset’s total cost before taxes, shipping and handling and other costs associated with purchasing the asset, as applicable. The value cannot exceed 999,999,999,999.99. The unit price can be populated by manual entry and the data is not system validated. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. There is no corresponding Asset Template field. The system automatically adds the value from this field to the value(s) entered in any other cost component field(s), and displays the results in the Total Cost field in the Asset Master record for Book 1. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a “0” (zero), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Price exceeds 14 characters. ERROR MESSAGE: Price is not numeric.
Sales Tax	This optional field (SALES_TAX_AMT) holds the sales tax amount, as applicable. The value cannot exceed 999,999,999,999.99. The sales tax amount can be populated by manual entry and the data is not system-validated. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. There is no corresponding Asset Template field. The system automatically adds the value from this field to the value(s) entered in any other cost component field(s), and displays the results in the Total Cost field in the Asset Master record for Book 1. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a “0” (zero), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Sales Tax exceeds 14 characters. ERROR MESSAGE: Sales Tax is not numeric.
Shipping/Handling	This optional field (SHIP_AMT) holds the shipping/handling amount, as applicable. The value cannot exceed 999,999,999,999.99. The shipping/handling amount can be populated by manual entry and the data is not system-validated. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. There is no corresponding Asset Template field. The system automatically adds the value from this field to the value(s) entered in any other cost component field(s), and displays the results in the Total Cost field in the Asset Master record for Book 1. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a “0” (zero), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Shipping/Handling exceeds 14 characters. ERROR MESSAGE: Shipping/Handling is not numeric.
Transportation	This optional field (TRANSP_AMT) holds the transportation costs, as applicable. The value cannot exceed 999,999,999,999.99. The transportation costs can be populated by manual entry and the data is not system-validated. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. There is no corresponding Asset Template field. The system automatically adds the value from this field to the value(s) entered in any other cost component field(s), and displays the results in the Total Cost field in the Asset Master record for Book 1. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a “0” (zero), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Transportation exceeds 14 characters. ERROR MESSAGE: Transportation is not numeric.
Other Costs	This optional field (OTHER_CST_AMT) holds any other costs, as applicable. The value cannot exceed 999,999,999,999.99. The other costs can be populated by manual entry and the data is not system-validated. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. There is no corresponding Asset Template field. The system automatically adds the value from this field to the value(s) entered in any other cost component field(s), and displays the results in the Total Cost field in the Asset Master record for Book 1. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a “0” (zero), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Other Cost exceeds 14 characters. ERROR MESSAGE: Other Cost is not numeric.
Amount Posted Curr Pd	This field (CUR_POSTED_AMT) is not available for user entry in an Asset Master record. For all records, both new and historical, blanks display in this field in the Asset Master record at the beginning of each accounting period. The system automatically populates this field when you post depreciation for the first time in the accounting period. Subsequent postings of depreciation expense (within the same accounting period) will automatically increase or decrease the value in this non-editable field, since the system displays the cumulative results of all postings for the accounting period. When you close the current Fixed Assets accounting period, the system automatically clears this field on the screen and sets the database value back to “0.00.” There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a “0” (zero), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Amt Posted Cur Pd exceeds 14 characters. ERROR MESSAGE: Amt Posted Cur Pd is not numeric.
Estimated Units Useful Life	This field (USAGE_UM_S) is only available in an Asset Master record if the asset is depreciable and you have designated Depr Based On equal to U (Units of Usage). This optional field (UNITS_LIFE_NO) holds up to nine numeric characters to indicate the estimated units of useful life (such as hours or miles). This field is similar to the Total Cost field for an asset whose basis is Y (Years) or L (Lease Periods), in that it defines the maximum number of units beyond which the system should not calculate depreciation. The value cannot exceed 999,999.999. The estimated units of useful life can be populated by manual entry, and the data is not system-validated. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Estimated Units of Useful Life field is blank in the input file/table for which there is a corresponding template data field, the system will use the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Estimated Units of Useful Life, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file/table and template, insert a “0” (zero), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Units Useful Life exceeds 9 characters. ERROR MESSAGE: Units Est Life is not numeric. ERROR MESSAGE: Units Useful Life must be NULL if Depr Based On is not U.
Unit of Measure Description	This field (USAGE_UM_S) is only available in an Asset Master record if the asset is depreciable and you have designated Depr Based On equal to U (Units of Usage). This optional field holds up to 10 alphanumeric characters to indicate the type of unit for the asset, such as hours, miles, and so on. The unit of measure description can be populated by manual entry, and the data is not system-validated. The value in this field is for data purposes only, and is not used in system calculations. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Unit of Measure Description field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Unit of Measure Description, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file/table and template, insert a ‘ ‘ (space), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Unit of Measure cannot be used unless Depr Based On is “U.” ERROR MESSAGE: Unit of Measure exceeds 10 alphanumeric characters.
Std Depr Rate Per Unit of Usage	This field (UNIT_DEPR_RT_AMT) is only available in an Asset Master record if the asset is depreciable and you have designated Depr Based On equal to U (Units of Usage). The value for this optional field cannot exceed 999,999,999,999.99. The standard depreciable rate per unit of usage field can be populated by manual entry, and the data is not system-validated. Although this field is not system-required, depreciation calculations cannot take place if this data is missing. The system multiplies the value from this field time the value in the Current Units Used field to derive the value in the Current Pd Depreciation field. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Std Depr Rate Per Unit of Usage  field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Std Depr Rate Per Unit of Usage, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file/table and template, insert a “0” (zero), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Depr Rt Per Unit cannot be used unless Depr Based On is “U.” ERROR MESSAGE: Depr Rt Per Unit is not numeric. ERROR MESSAGE: Depr Rt Per Unit exceeds 14.0 characters.
Prior Units Used	This field (PRIR_UNITS_USED_NO) is only available in an Asset Master record if the asset is depreciable and you have designated Depr Based On equal to U (Units of Usage). The value for this optional field cannot exceed 999,999,999,999.99. The prior units used can be populated by manual entry, and the data is not system-validated. You will normally populate this field only when you are initializing historical records, as the system will automatically update this field during the Fixed Assets period close process. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a zero (‘0‘), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Prior Units Used cannot be used unless Depr Based On is “U.” ERROR MESSAGE: Prior Units Used is not numeric. ERROR MESSAGE: Prior Units Used exceeds 14 characters.
Current Units Used	This field (CUR_UNITS_USED_NO) is only available in an Asset Master record if the asset is depreciable and you have designated Depr Based On equal to U (Units of Usage). The value for this optional field cannot exceed 999,999,999,999.99. The current units used can be populated by manual entry, and the data is not system-validated. You will normally populate this field each month before you compute depreciation. Although this field is not system-required, depreciation calculations cannot take place if this data is missing. The system multiplies the value from this field times the value in the Std Depr Rate Per Unit of Usage field to derive the value in the Current Pd Depreciation field. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a zero (‘0‘), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Cur Units Used cannot be used unless Depr Based On is “U.” ERROR MESSAGE: Cur Units Used is not numeric. ERROR MESSAGE: Cur Units Used exceeds 14 characters.
Capitalized Lease	This field (CAPTLZD_LEASE_FL) is only available in an Asset Master record if the asset is depreciable and you have designated Depr Based On equal to L (Lease Periods). This required one-character field will accept Y (Yes) or N (No). This field is for information purposes only and is not used in any system calculations. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Capitalized Lease field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Capitalized Lease, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file and there is no template, enter “N” as the default for this field. Possible Error Messages: ERROR MESSAGE: Captalizd cannot be used unless Depr Based On is “L.” ERROR MESSAGE: Capitalized Lease exceeds 1 character. ERROR MESSAGE: This Capitalized Lease Flag is not “Y” or “N.”
Lease Start Date	This field (LEASE_START_DT) is only available in an Asset Master record if the asset is depreciable and you have designated Depr Based On is equal to L (Lease Periods). Data in this optional field must be in date format (YYYYMMDD). This field, which can be an historical, current, or future date, is for information purposes only and is not used in any system calculations. (When the system calculates amortization, it checks only the date from the Depreciation/Amortization Start Date field.) Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Lease Start Date field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Lease Start Date, even if there is a corresponding template data field, the system will bypass any reference to the Template No. Possible Error Messages: ERROR MESSAGE: Lease Start Dt cannot be used unless Depr Based On is “L.” ERROR MESSAGE: Lease Start Dt is an invalid date format. ERROR MESSAGE: Lease Start Dt exceeds 10  characters. ERROR MESSAGE: An invalid year was entered for Lease Start Dt. ERROR MESSAGE: The Lease Start Dt is later than the Lease End Dt.
Lease End Date	This field (LEASE_END_DT) is only available in an Asset Master record if the asset is depreciable and you have designated Depr Based On is equal to L (Lease Periods). Data in this optional field must be in date format (YYYYMMDD). This field, which can be an historical, current, or future date, is for information purposes only and is not used in any system calculations. (When the system calculates amortization, it checks only the date from the Depreciation/Amortization Start Date field.) Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Lease End Date field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Lease End Date, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Possible Error Messages: ERROR MESSAGE: Lease End Dt cannot be used unless Depr Based On is “L.” ERROR MESSAGE: Lease End Dt is an invalid date format. ERROR MESSAGE: Lease End Dt exceeds 10  characters. ERROR MESSAGE: An invalid year was entered for Lease End Dt. ERROR MESSAGE: The Lease End Dt must be greater than the Lease Start Dt.
Total No Payments	This field (TOT_LEASE_PMTS_NO) is only available in an Asset Master record if the asset is depreciable and you have designated Depr Based On is equal to L (Lease Periods). The value (and format) for this optional field cannot exceed three numeric characters (that is, 999). The total number of payments can be populated by manual entry, and the data is not system-validated. The value in this field is for information purposes only and is not used in system calculations. (The system uses the value from the Lease Payments Remaining field to determine how many more accounting periods the asset should be amortized over.) There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a zero (‘0‘), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Lease Ttl Pments cannot be used unless Depr Based On is “L.” ERROR MESSAGE: Lease Ttl Pments exceeds 3  characters. ERROR MESSAGE: Lease Ttl Pments exceeds maximum value allowed: 999.
Monthly Amount	This field (MTH_LEASE_PMT_AMT) is only available in an Asset Master record if the asset is depreciable and you have designated Depr Based On is equal to L (Lease Periods). The value for this optional field cannot exceed 999,999,999,999.99. The monthly payment amount can be populated by manual entry, and the data is not system-validated. You will normally populate this field at time of initialization. There will, of course, be instances in which the monthly payment changes. In this circumstance, you should enter the revised monthly payment in this field for the first month in which it is effective, before you compute monthly depreciation/amortization. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. If you have selected the Auto Calculate check box and the asset’s book value does not equal zero, you must enter data in both the Monthly Amount and Lease Pds Remaining fields to save a new record. Although this field is not system-required (except in the instance previously mentioned), amortization calculations will not take place for a record if blanks display in the Monthly Amount field. The system does not automatically compute a value for this field (by dividing the total lease value by the total number of payments) because of inherent rounding problems and changing lease conditions. Each month when you compute depreciation/amortization, the system copies the data from this field to the Current Pd Amortization field. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a zero (‘0‘), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Lease Mth Pment cannot be used unless Depr Based On is “L.” ERROR MESSAGE: Lease Mth Pment exceeds 14.0 characters. ERROR MESSAGE: Lease Mth Pment is not numeric.
Lease Periods Remaining	This field (LEASE_PDS_REMN_NO) is only available in an Asset Master record if the asset is depreciable and you have designated Depr Based On is equal to L (Lease Periods). The value (and format) for this optional field cannot exceed three numeric characters (that is, 999). This data is not system-validated. The system uses the value from the Lease Pds Remaining field to determine how many more accounting periods the asset should be amortized over. If you have selected the Auto Calculate check box and the asset’s book value does not equal zero, you must enter data in both the Monthly Amount and Lease Pds Remaining fields to save a new record. Although this field is not system-required (except in the instance previously mentioned), amortization calculations will not take place for a record if blanks display in the Lease Pds Remaining field. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a zero (‘0‘), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Lease Pments Rem cannot be used unless Depr Based On is “L.” ERROR MESSAGE: Lease Pments Rem exceeds 3 characters. ERROR MESSAGE: Lease Pments Rem exceeds maximum value allowed: 999. ERROR MESSAGE: Lease Pments Rem is not numeric.
Disposal Date	This field (DISP_DT) is only available in an Asset Master record if the Record Status for the asset is equal to D (Disposal). The format for this optional field must be in date format (YYYYMMDD). A disposal date is required on the Manage Disposal Transactions screen during data entry. When a disposal is posted, the system automatically moves the disposal date from the appropriate disposal entry screen to this field. Disposal data that displays in Asset Master records as a result of G/L postings is treated as a “System-Generated” (SYSTEM) disposal for which manual edits are not permitted. For an historical disposal that was not system-generated, you can manually enter the appropriate data during initialization. In this circumstance, the disposal data is treated as a “Manual” (MANUAL) disposal and manual edits are permitted. Although there is no system validation of the disposal date, you may find that the disposal date is a valuable selection parameter when using Query or designing custom reports. Because there are no system rules regarding the disposal date, you may want to develop some internal rules on the relationship of the date to the actual disposal and its consistency with your entries in the disposal Fiscal Year, Period, and Subperiod fields. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: Disp Date is an invalid date format. ERROR MESSAGE: An invalid year was entered for Disp Date.
Fiscal Year	This field (DISP_FY_CD) is only available in an Asset Master record if the Record Status for the asset is equal to “D” (Disposal). The disposal fiscal year field holds up to 6 alphanumeric characters and the data is not system-validated. Disposal fiscal year data is required on the Manage Disposal Transactions screen during data entry. When a disposal is posted, the system automatically moves the disposal fiscal year from the appropriate disposal entry screen to this field. Disposal data that displays in Asset Master records as a result of G/L postings is treated as a “System-Generated” (SYSTEM) disposal for which manual edits are not permitted. For a historical disposal that was not system-generated, you can manually enter the appropriate disposal fiscal year during initialization. In this circumstance, the disposal data is treated as a “Manual” (MANUAL) disposal and manual edits are permitted. Although there is no system validation of the disposal fiscal year, you may find that the disposal fiscal year is a valuable selection parameter when using Query or designing custom reports. Because there are no system rules regarding the disposal fiscal year, you may want to develop some internal rules on the relationship of the disposal fiscal year to the actual disposal and its consistency with your entries in the disposal Date, Period, and Subperiod fields. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: Disp Fiscal Year exceeds 6 alphanumeric characters.
Period	This field (DISP_PD_NO) is only available in an Asset Master record if the Record Status for the asset is equal D (Disposal). The disposal period field holds up to 2 numeric characters and the data is not system-validated. Accounting period data is required on the Manage Disposal Transactions screen during data entry. When a disposal is posted, the system automatically moves the disposal accounting period from the appropriate disposal entry screen to this field. Disposal data that displays in Asset Master records as a result of G/L postings is treated as a “System-Generated” (SYSTEM) disposal for which manual edits are not permitted. For a historical disposal that was not system-generated, you can manually enter the appropriate disposal accounting period during initialization. In this circumstance, the disposal data is treated as a “Manual” (MANUAL) disposal and manual edits are permitted. Although there is no system validation of the disposal accounting period, you may find that the disposal accounting period is a valuable selection parameter when using Query or designing custom reports. Because there are no system rules regarding the disposal accounting period, you may want to develop some internal rules on the relationship of the disposal accounting period to the actual disposal and its consistency with your entries in the disposal Date, Fiscal Year, and Subperiod fields. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: Disp Pd No exceeds 2 characters. ERROR MESSAGE: Disp Pd No is not numeric.
Subperiod	This field (DISP_SUB_PD_NO) is only available in an Asset Master record if the Record Status for the asset is equal to D (Disposal). The disposal subperiod field holds up to 2 numeric characters and the data is not system-validated. Accounting subperiod data is required on the Manage Disposal Transactions screen during data entry. When a disposal is posted, the system automatically moves the disposal accounting subperiod from the appropriate disposal entry screen to this field. Disposal data that displays in Asset Master records as a result of G/L postings is treated as a “System-Generated” (SYSTEM) disposal for which manual edits are not permitted. For a historical disposal that was not system-generated, you can manually enter the appropriate disposal accounting subperiod during initialization. In this circumstance, the disposal data is treated as a “Manual” (MANUAL) disposal and manual edits are permitted. Although there is no system validation of the disposal accounting subperiod, you may find that the disposal accounting subperiod is a valuable selection parameter when using Query or designing custom reports. Because there are no system rules regarding the disposal accounting subperiod, you may want to develop some internal rules on the relationship of the disposal accounting subperiod to the actual disposal and its consistency with your entries in the disposal Date, Fiscal Yr, and Period fields. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: Disp Subpd No exceeds 2 characters. ERROR MESSAGE: Disp Subpd No is not numeric.
Price	This field (DISP_PRICE_AMT) is only available in an Asset Master record if the Record Status for the asset is equal to D (Disposal). This optional field holds the disposal price amount, as applicable. The value cannot exceed 999,999,999,999.99. The disposal price amount can be populated by manual entry and the data is not system-validated. The disposal price amount is optional on the Manage Disposal Transactions screen during data entry. “0.00” displays in this field as a default value. When a disposal is posted, the system automatically moves the disposal price amount, as applicable, from the appropriate disposal entry screen to this field. Disposal data that displays in Asset Master records as a result of G/L postings is treated as a “System-Generated” (SYSTEM) disposal for which manual edits are not permitted. For a historical disposal that was not system-generated, you can manually enter the appropriate disposal price amount during initialization. In this circumstance, the disposal data is treated as a “Manual” (MANUAL) disposal and manual edits are permitted. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a zero (‘0‘), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Disp Price exceeds 14 characters. ERROR MESSAGE: Disp Price is not numeric.
Desc	This field (DISP_DESC) is only available in an Asset Master record if the Record Status for the asset is equal to D (Disposal). The optional disposal description field holds up to 30 alphanumeric characters, as applicable. This field can be populated by manual entry, and the data is not system-validated. The disposal description is optional on the Manage Disposal Transactions screens during data entry. Blanks display in this field as a default value. When a disposal is posted, the system automatically moves the disposal description, as applicable, from the appropriate disposal entry screen to this field. Disposal data that displays in Asset Master records as a result of G/L postings is treated as a “System-Generated” (SYSTEM) disposal for which manual edits are not permitted. For a historical disposal that was not system-generated, you can manually enter the appropriate disposal description during initialization. In this circumstance, the disposal data is treated as a “Manual” (MANUAL) disposal and manual edits are permitted. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table and in the Template, insert a space (‘ ‘), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: This Disposal Description exceeds 30 characters.
DISP_S_JNL_CODE	This field is only available if the Record Status for the asset is equal to D (Disposal). Data in this field cannot exceed 3 characters. Enter “FA” if the disposal was processed in Costpoint or leave as NULL. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: Disp Jnl Cd  exceeds 3 characters. ERROR MESSAGE: Disp Jnl Cd  must be “NULL” or “FA.”
Disposal Post Sequence No	This field (DISP_POST_SEQ_NO) is only applicable for an Asset Master record if the Record Status for the asset is equal to D (Disposal) and holds up to 10 numeric characters, as applicable. The disposal post sequence number is not available for manual entry in the Asset Master record, regardless of whether the disposal was “System-Generated” or “Manual.” The system will display the sequence number in this field from the posting that changed the record status to disposal. Identical posting sequence numbers are assigned by the system to all entries posted in a specific session. If a record has a posting sequence number, you will not be able to save any changes made to other fields in an Asset Master record. If the system displays “SYSTEM” in the Disposal System Code (S_DISPOSAL_CD) field for a specific Asset Master record, the system can automatically create and display a Fixed Assets posting sequence number, as applicable, when you post disposal data from the Manage Disposal Transactions screen. In the rare circumstance that a sequence number already exists, you should make sure that you record that sequence number in this field. If the system displays “MANUAL” in the Disposal System Code field for a specific Asset Master record, you should record no data for this field. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: Disp Post Seq No exceeds 10 characters. ERROR MESSAGE: Disp Post Seq No is not numeric.
Disposal System Code	This field (S_DISPOSAL_CD) is only applicable for an Asset Master record if the Record Status for the asset is equal “D” (Disposal). This field is not available for user entry on the Manage Disposal Transactions screen or in Asset Master records. The only acceptable data for entry in this field, as generated automatically by the system, is SYSTEM, MANUAL, PREPRO, or NULL (‘ ‘), as follows: The system automatically displays SYSTEM in the Disposal System Code field for a specific Asset Master record if a disposal has been entered via the Manage Disposal Transactions screen or the Create Multiple Disposal Transactions screen, and then posted to the General Ledger. The system automatically displays MANUAL in the Disposal System Code field for a specific Asset Master record for which manual disposal data was added by the user and for which a disposal has not been posted to the General Ledger. The system automatically displays PREPRO in the Disposal System Code field for a specific Asset Master record for which disposal data was added using preprocessor disposal import functionality and the disposal record was subsequently posted. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table and in the Template, insert a space (‘ ‘), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: Disposal Code exceeds 6 alphanumeric characters. ERROR MESSAGE: Disp Sys Cd must be “SYSTEM,” “MANUAL,” “PREPRO,” or NULL.
Depr Method Code	This field (B1_DEPR_MTHD_CD) is only available in an Asset Master record if the asset is depreciable and you have designated Depr Based On is equal to Y (Years). This field should not be populated if you have designated Depr Based On as L (Lease Periods) or U (Units of Usage). In the circumstance above, in which Depr Based On is equal to Y (Years), this required field for Book 1 (the General Ledger book) holds up to 6 alphanumeric characters and can be populated by manual entry or by importing data from a specified Asset Template record. The methodology parameters that you set up with each depreciation method during initialization provide the system with the instructions for depreciation calculations. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. Depreciation Method Codes are validated against user-specified data initialized on the Manage Depreciation Methods screen. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Depr Method Code field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for the Depr Method Code, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Possible Error Messages: ERROR MESSAGE: B1 Depr Mthd Cd exceeds 6 alphanumeric characters. ERROR MESSAGE: Cannot enter a Method when depreciation not based on years. ERROR MESSAGE: Cannot enter a method when the asset is non-depreciable. ERROR MESSAGE: B1 Depr Mthd Cd is missing. ERROR MESSAGE: B1 Depr Mthd Cd does not exist.
Useful Life	This field (B1_USEFUL_LIFE_NO) is only available in an Asset Master record if the asset is depreciable and you have designated Depr Based On is equal to Y (Years). This field should not be populated if you have designated Depr Based On as L (Lease Periods) or U (Units of Usage). In the circumstance above, in which Depr Based On is equal to Y (Years), this optional field for Book 1 (the General Ledger book) holds up to 4 numeric characters to specify the useful life of the asset (which may not be obvious from the G/L Book Depr Method Code you have assigned). This field can be populated by manual entry or by importing data from a specified Asset Template record. The data in this field is for information purposes only and is not used in system calculations. (When the system calculates depreciation, the depreciation year and percentage for that year are derived from the data in the Depr Method Code that you have assigned to the Asset Master record.) Depreciation Method Codes are validated against user-specified data initialized on the Manage Depreciation Methods screen. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Useful Life field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No (if it exists) to determine the data for that field. In the circumstance that data exists in the input file/table for Useful Life, even if there is a corresponding template data field, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file/table and in the Template, insert a zero (‘0‘), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: B1 Useful Life exceeds 4 characters. ERROR MESSAGE: This record’s Depr Based On is not set to “Y” for Years. ERROR MESSAGE: Cannot enter B1 Useful Life when the asset is not depreciable. ERROR MESSAGE: B1 Useful Life is not numeric.
Auto Calculate Depreciation	This field (B1_AUTO_CALC_FL) is available in an Asset Master record if the asset is depreciable. Depr Based On can be equal to Y (Years), U (Units of Usage), or L (Lease Periods). This required field for Book 1 (the General Ledger book) can accept only a Y (Yes) or N (No) entry to indicate whether the auto calculation feature should be enabled. In an Asset Master record, this check box can be selected by manual entry or by importing data from a specified Asset Template record. The system default for this field is Y (Depreciable), which can be changed by manual entry or by importing data from a specified Asset Template record. If the Auto Calculate Depreciation check box is selected for an Asset Master record, the system will automatically include the record in depreciation computations (provided all other rules of eligibility for depreciation calculations are met). In addition, the system will re-set the Current Pd Depreciation field back to zero during the Fixed Assets period close process. You should enter N (No) for this field if you want to disable the automatic system calculation of depreciation for this Asset Master record. In this circumstance, however, you will need to manually enter the amount of depreciation in the Current Pd Depreciation field in order to be able to post any depreciation for the record. In general, if you need to make a one-time adjustment to current depreciation expense, you should manually override the current period depreciation amount calculated by the system rather than change the default for this check box. If, however, you want to post a depreciation expense entry to the General Ledger as a recurring override to system calculations, you can set this field to N (No) and enter the recurring override amount in the Current Pd Depreciation field. You can select/clear this check box, as desired, at any time in Asset Master records. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Auto Calculate Depreciation field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Auto Calculate Depreciation, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file/table and in the Template, insert a “Y,” since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: B1 Auto Calc exceeds 1 character. ERROR MESSAGE: B1 Auto Calc is not “Y” or “N.”
(Salvage) Percent	This field (B1_SLVGE_RT) is only available in an Asset Master record if the asset is depreciable and you have designated Depr Based On = “Y” (Years) or “U” (Units of Usage). This field should not be populated if you have designated Depr Based On = “L” (Lease Periods). This field for Book 1 (the General Ledger book) holds integers up to 100 and four decimal places (that is, 100.0000 or 99.9999) and can be populated by manual entry or by importing data from a specified Asset Template record. In an Asset Master record, if you enter a salvage value percentage in this field, note that the system automatically computes and displays the equivalent salvage value in the (Salvage) Value field. The (Salvage) Percent and (Salvage) Value fields in an Asset Master record are reciprocal in that the entry in one field automatically calculates and displays the appropriate data in the other field. The system subtracts the amount from the Value field from the amount in the Total Cost field, and automatically displays the result in the Amount to Depreciate field, which, in turn, as applicable, affects the amount of depreciation computed for the asset. Note: If you selected the Subtract Salvage Value Before Calculation check box on the Manage Depreciation Methods screen (the check box is selected by default), the system will subtract the salvage value from the cost of the asset before performing depreciation calculations. If you have cleared this check box, the system will ignore salvage value from the Value field when computing the amount for the Amount to Depreciate field. The value in this field must be equal to the (Salvage) Value amount divided by the Total Cost amount for the Asset Master record. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Salvage Percent field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Salvage Percent, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field and the (Salvage) Value field are NULL in the input file/table and this field is NULL in an entered template, insert a zero (“0”), since NULLs are not permitted by the system for this field. If the (Salvage) Value field is populated and this field is not populated, compute and insert this value in the field, (Salvage) Value (B1_SLVGE_VAL_AMT) divided by Total Cost (B1_TOT_COST_AMT). Possible Error Messages: ERROR MESSAGE: Percent exceeds maximum value allowed:  100.0000. ERROR MESSAGE: B1 Salvage Rate is not numeric. ERROR MESSAGE: Depr Status is not set to “D” for Depreciable. ERROR MESSAGE: B1 Salvage Percent must be 0 for a Lease.
(Salvage) Value	This field (B1_SLVGE_VAL_AMT) is only available in an Asset Master record if the asset is depreciable and you have designated Depr Based On equal to Y (Years) or U (Units of Usage). This field should not be populated if you have designated Depr Based On as L (Lease Periods). This field for Book 1 (the General Ledger book) holds the salvage value amount, as applicable. The value cannot exceed 999,999,999,999.99, and the salvage value amount can be populated by manual entry. In an Asset Master record, if you enter a salvage value amount in this field, note that the system automatically computes and displays the equivalent salvage rate in the (Salvage) Percent field. The (Salvage) Percent and (Salvage) Value fields in an Asset Master record are reciprocal in that the entry in one field automatically calculates and displays the appropriate data in the other field. The system subtracts the amount from the Value field from the amount in the Total Cost field, and automatically displays the result in the Amount to Depreciate field, which, in turn, as applicable, affects the amount of depreciation computed for the asset. Note: If you selected the Subtract Salvage Value Before Calculation check box on the Manage Depreciation Methods screen (the check box is selected by default), the system will subtract the salvage value from the cost of the asset before performing depreciation calculations. If you have cleared this check box, the system will ignore salvage value from the Value field when computing the amount for the Amount to Depreciate field. The value in this field must be equal to the (Salvage) Percent multiplied by the Total Cost amount for the Asset Master record. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field and the (Salvage) Percent field are NULL in the input file/table and this field is NULL in an entered template, insert a zero (“0”), since NULLs are not permitted by the system for this field. If the (Salvage) Percent field is populated and this field is not populated, compute and insert this value in the field, (Salvage) Percent (B1_SLVGE_RT) multiplied by Total Cost (B1_TOT_COST_AMT). Possible Error Messages: ERROR MESSAGE: B1 Salvage Val exceeds 14 characters. ERROR MESSAGE: B1 Salvage Value is not numeric. ERROR MESSAGE: Depr Status is not set to “D” for Depreciable. ERROR MESSAGE: B1 Salvage Val must be 0 for a Lease. ERROR MESSAGE: B1 Salvage Val does not equal Salvage Rt time Total Cost. ERROR MESSAGE: Book 1 Salvage Val exceeds Total Cost.
FYTD Depreciation	This field (B1_FYTD_DEPR_AMT) is only available in an Asset Master record if the asset is depreciable. Depr Based On can be equal to Y (Years), U (Units of Usage), or L (Lease Periods). Note: If Depr Based On is equal to L (Lease Periods), the label for this field will read “FYTD Amortization” in the Asset Master record. This field for Book 1 (the General Ledger book) holds the depreciation expense already posted for the current fiscal year for all previously-closed periods in the current fiscal year, and excludes any value in the Current Pd Depreciation field. The value cannot exceed 999,999,999,999.99, and the FYTD depreciation amount can be populated by manual entry. The system automatically adds the value from this field to the values in the G/L Book Prior FY Depreciation and G/L Book Current Pd Depreciation fields to derive the total calculated value displayed in the G/L Book Accum Depreciation field. For a new Asset Master record, this field should be blank, as there has been no current fiscal year activity. Each accounting period except for the last period in the fiscal year, the system will automatically increase (or possibly decrease) the value in this field by the amount of depreciation posted when the Fixed Assets current period is closed and the next period exists in the same fiscal year. For both new and historical records that are being initialized, the system will increase or decrease the value in this field by the amount of the total depreciation posted for the period when you close the Fixed Assets current period. The system will also update the value in this field when you perform the Fixed Assets period close process on the last period in your current fiscal year. The system adds the value in the G/L Book FYTD Depreciation field to the value in the G/L Book Prior FY Depreciation field and then sets the value in the G/L Book FYTD Depreciation field back to zero. Note: If you use a “Date of Purchase” basis for the depreciation method linked to an Asset Master record, the cumulative value in this field for a historical record will normally be different from the value in the Amt Taken Purch YTD field (except when the date of purchase coincides with the start of your fiscal year). The FYTD Depreciation field displays fiscal year data, while the Amt Taken Purch YTD field displays purchase year data. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a zero (“0”), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: B1 FYTD Depr exceeds 14 characters. ERROR MESSAGE: B1 FYTD Depr is not numeric. ERROR MESSAGE: Depr Status is not set to D for Depreciable.
Prior FYTD Depreciation	This field (B1_PFY_DEPR_AMT) is only available in an Asset Master record if the asset is depreciable. Depr Based On can be equal to Y (Years), U (Units of Usage), or L (Lease Periods). If Depr Based On is equal to L (Lease Periods), the label for this field will read “Prior FY Amortization” in the Asset Master record. This field for Book 1 (the General Ledger book) holds the cumulative depreciation expense posted for ALL prior (and previously-closed) fiscal years. The amount in this field should exclude any posted amounts for the current fiscal year. The value cannot exceed 999,999,999,999.99, and the prior FY depreciation amount can be populated by manual entry. The system automatically adds the value from this field to the values in the G/L Book FYTD Depreciation and G/L Book Current Pd Depreciation fields to derive the total calculated value displayed in the G/L Book Accum Depreciation field. For a new Asset Master record, this field should be blank, as there has been no current fiscal year activity. For both new and historical records, the system will automatically update the value in this field when you perform the Fixed Assets period close process on the last period in your current fiscal year. The system will add the values from the G/L Book FYTD Depreciation and Current Pd Depreciation fields to the value in the G/L Book Prior FY Depreciation field, and will set the value in the G/L Book FYTD Depreciation field back to zero. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a zero (“0”), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: B1 Cur Pd Depr  exceeds 14 characters. ERROR MESSAGE: B1 Cur Pd Depr is not numeric. ERROR MESSAGE: Depr Status is not set to D for Depreciable.
Current Pd Depreciation	This field (B1_CUR_DEPR_AMT) is only available in an Asset Master record if the asset is depreciable. Depr Based On can be equal to Y (Years), U (Units of Usage), or L (Lease Periods). Note: If Depr Based On is equal to L (Lease Periods), the label for this field will read “Current Pd Amortization” in the Asset Master record. This field for Book 1 (the General Ledger book) holds the current period depreciation expense amount. The value cannot exceed 999,999,999,999.99, and the depreciation expense amount can be populated by manual entry. The system automatically adds the value from this field to the values in the G/L Book Prior FY Depreciation and G/L Book FYTD Depreciation fields to derive the total calculated value displayed in the G/L Book Accum Depreciation field. For a new Asset Master record, this field should be blank unless you want to overwrite the system calculation of annual depreciation and you do NOT select the G/L Book Auto Calculate Depreciation check box. If you have cleared the G/L Book Auto Calculate Depreciation check box and you manually entered a value in this field last period, this field should still display the manually-entered value. For both new and historical records, the system will automatically populate/update this field when you calculate depreciation for this record [if you have selected the G/L Book Auto Calculate check box and the date in the G/L Book Depr Start Date field is not a future date (later than the end of the current period)]. (The "current" Fixed Assets period is specified on the Configure Posting Settings screen.) When you close the current Fixed Assets accounting period, the system sets back the value in this field to zero unless you have cleared the G/L Book Auto Calculate Depreciation check box. You can perform depreciation calculations multiple times within the same Fixed Assets period. If you have made no manual corrections to critical fields (such as asset cost, annual depreciation, current depreciation year, periods remaining, and so on), there is no danger that the system will post the same depreciation expense for the same asset in the same Fixed Assets period after you re-calculate depreciation. The system tracks monthly postings for each record and compares the value in the G/L Book Current Pd Depreciation field with the value in the G/L Book Amt Posted Curr Pd field. If these values are equal, there can be no additional postings to the G/L for the current period. Only changes to the G/L Book Current Pd Depreciation field can generate additional positive or negative depreciation expense entries if additional postings are performed for the current Fixed Assets period. Changes can take place by means of manual overwrites in this field or as a result of depreciation calculations performed after changes have been made to other critical fields. As long as the value in the G/L Book Current Pd Depreciation field is different than the value in the G/L Book Amt Posted Curr Pd field, the system will, within the same Fixed Assets period, always post the value needed to bring the G/L Book Amt Posted Curr Pd amount up to or down to the value in the G/L Book Current Pd Depreciation field. For example, if you have calculated depreciation and the G/L Book Current Pd Depreciation field displays $50.00, the value in the G/L Book Amt Posted Curr Pd field will also display $50.00 after posting to the General Ledger. If you now change the amount in the G/L Book Current Pd Depreciation field to $75.00 and post again within the same Fixed Assets period, the system will recognize that an additional $25.00 is needed to bring these values to an equal condition, and will post $25.00 more. After this second posting, the amounts in the G/L Book Current Pd Depreciation field and the G/L Book Amt Posted Curr Pd field will be equal. When you close the current FA accounting period, the amount displayed in the G/L Book Amt Posted Curr Pd field will be added to the amount in the G/L Book FYTD Depreciation field and the value in the G/L Book Amt Posted Curr Pd field will be set back to zero. Current period depreciation expense is computed as a result of the Date of Purchase or Fiscal Year basis assigned to each depreciation method (established on the Manage Depreciation Methods screen). Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. Depreciation Calculations When Depr Based On is Y (Years) The basic premise for depreciation calculations in which the "catch-up" amount is to be spread among remaining periods is as follows: If you have linked a Date of Purchase depreciation basis method with the asset, the G/L Book Current Pd Depreciation field will display the annual depreciation expense less the amount taken this purchase year divided by the number of periods remaining in the calendar year. If you have linked a Fiscal Year depreciation method basis with the asset, the G/L Book Current Pd Depreciation field will display the annual depreciation expense less the FYTD amount divided by the number of periods remaining in the fiscal year. Actual depreciation calculations may be more complex than in this simplified explanation because you may have selected to use "catch-up" depreciation calculations for the current period or to compute depreciation on a "days" basis. In the following simple example, consider the basic differences in current period depreciation calculations for a $9,000 asset, useful life of five years, no salvage value, using straight-line depreciation, for both the FY and DP basis. For this example, the current fiscal year is CY 2007, the current Fixed Assets accounting period is 10, the number of accounting periods in the fiscal year is 12, and the start date is 10-01-07. DP (Date-Purchased) FY (Fiscal Year) Asset Cost $ 9,000 $ 9,000 Annual Depreciation $ 1,800 $ 1,800 Current Pd Depreciation $ 150 $ 600 The computed annual depreciation expense is identical for both the DP and FY basis. The current period depreciation expense, however, is different. Using the Date of Purchase basis for depreciation, the annual depreciation expense of $1,800 is divided by the number of accounting periods remaining in the purchase year (12). One period of expense is charged for the current period, irrespective of the fiscal year. The depreciation year begins at the date in the G/L Book Depr Start Date field (10-01-2007). Using the Fiscal Year basis for depreciation, the annual depreciation expense of $1,800 is divided by the number of accounting periods remaining in the fiscal year. In the example above, there are only three accounting periods remaining in FY 2007 over which to spread the annual depreciation cost of $1,800 Depreciation Calculations When Depr Based On = U (Units of Usage) The system will compute current period depreciation expense using a units of usage methodology by multiplying the value in the Current Units Used field by the value in the Std Depr Rt Per Unit of Usage field. Data must also be present in the Current Units Used field and in the Std Depr Rt Per Unit of Usage field before the system will include these records in depreciation calculations. Depreciation Calculations When Depr Based On = L (Lease Pds) Using a lease periods methodology, the system will move the value from the Monthly Amount field to this field when depreciation is calculated. The system does not compute a value for this field (by dividing the total lease value or the amount to amortize by the total number of payments) because of inherent rounding differences and changing lease terms. You must enter the desired value in the Monthly Amount field, and this value will display in the G/L Book Current Pd Depreciation field after the system calculates depreciation for the current period (and for subsequent periods as well if there are no changes). If the monthly payment amount changes, you should record the revised amount in the Monthly Amount field for the first month in which it is effective, before amortization calculations take place. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a zero (“0”), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: B1 Cur Pd Depr exceeds 14 characters. ERROR MESSAGE: B1 Cur Pd Depr is not numeric. ERROR MESSAGE: Depr Status is not set to D for Depreciable.
Annual Depreciation	This field (B1_ANNL_DEPR_AMT) is only available in an Asset Master record if the asset is depreciable and the value in the Depr Based On field is equal to Y (Years). This field is not available if the value is U (Units of Usage) or L (Lease Pds). This field for Book 1 (the General Ledger book) holds the system-computed annual depreciation expense already posted for the current fiscal year. The value cannot exceed 999,999,999,999.99, and the Annual depreciation amount can be populated by manual entry. You can leave this field blank for both new and historical records unless you want to overwrite the system calculation of annual depreciation and you do not select the G/L Book Auto Calculate Depreciation check box. The system will populate this field when you calculate depreciation for this record if you have selected the G/L Book Auto Calculate Depreciation check box and the date in the G/L Book Depr Start Date field is not a future date (later than the end of the current period). Manual entries in an Asset Master record are always permitted in this field, regardless of the status of the G/L Book Auto Calculate Depreciation check box and the date in the G/L Book Depr Start Date field, but should be entered with caution. The timing of any manual entries to this field in an Asset Master record is especially important; if you have selected the G/L Book Auto Calculate Depreciation check box and make any manual edits to the G/L Book Annual Depreciation field, the system will re-compute and re-populate this value during the calculation and overwrite your manual edits. For both new and historical records, the system uses the value from this field during depreciation calculations. You can perform depreciation calculations multiple times within the same accounting period. If you have made no manual corrections to critical fields (such as asset cost, annual depreciation, current depreciation year, periods remaining, and so on), there is no danger that the system will calculate a different annual depreciation value for the same asset in the same accounting period. The system computes annual depreciation by multiplying total cost (or cost minus salvage value) times the depreciation percentage (from the depreciation method assigned to the asset) for the year specified in the G/L Book Current Depr Yr field. The system does not re-set the value in this field to zero during the period close process. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a zero (“0”), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: B1 Annual Depr exceeds 14 characters. ERROR MESSAGE: B1 Annual Depr is not numeric. ERROR MESSAGE: Depr Status is not set to D for Depreciable.
Depr Start Date	This field (B1_DEPR_START DT) is only available in an Asset Master record if the asset is depreciable. Depr Based On can be equal to Y (Years), U (Units of Usage), or L (Lease Periods). Note: If Depr Based On is equal to L (Lease Periods), the label for this field will read “Amortization Start Date” in the Asset Master record. Data in this optional field must be in date format (YYYYMMDD). Even though data entry in this field is not required to save an Asset Master record, this field is the most important date for depreciable assets because the system uses this date during depreciation calculations. Depreciation calculations will not take place if blanks display in this field, or if this date is later than the end of the current accounting period. (The Fixed Assets "current" accounting period is specified on the Configure Posting Settings screen.) If you anticipate a depreciation start date delay due to installation or calibration requirements, for example, you can enter a future date in this field, if desired. In this circumstance, depreciation calculations will not begin until the future date coincides with your current accounting period. The date in this field must be on or before the end of the current accounting period for depreciation calculations to take place. For an existing asset record, you should enter the historical date that depreciation began for this record and NOT the date that you began depreciating this record using Costpoint Fixed Assets. Because system calculations use this date to determine whether depreciation computations should take place for each record, use extreme caution if you change the depreciation start date for property records once they have begun depreciating in the system. The relationship between the data in this field and the values in the G/L Book Current Depr Yr and G/L Book Days/Pds Remaining fields are critical to the accurate calculation of depreciation for new records in which Depr Based On is equal to Y (Years). You can use the Compute/Update Depreciation Computation Data utility to assist you in verifying the relationship of the G/L Book Depr Start Date field to the G/L Book Current Depr Yr and G/L Book Days/Pds Remaining fields. Using the value in the G/L Book Depr Start Date field, the system prints a report by asset/item number, by book, that includes a side-by-side comparison of both the current values displayed in the Asset Master record AND the values that the system would have computed for the G/L Book Current Depr Yr and G/L Book Days/Pds Remaining fields. Although you can print this report for all selected records, you can also print the report for exceptions only, which may make discrepancies easier to identify. After the report has printed, you can activate the option in this utility that applies the system-computed values to your asset records. This process updates the existing data in the G/L Book Current Depr Yr and G/L Book Days/Pds Remaining fields by replacing your data and writing the system-computed values to these fields. Warning: Always carefully review and agree with the reported results on a record-by-record basis, using the Compute/Update Depreciation Computation Data utility, before performing the update process. You should run this utility to verify (and optionally update) your data after you initialize your historical records and reconcile the detail Asset Account and Accumulated Depreciation Account values with your General Ledger and before you compute depreciation for the first time. After initialization, you may want to run this utility on a regular basis each period as part of your company's standard procedures, to confirm that your period additions have been initialized correctly. When you enter data for new records or for historical records during the initialization process, there are no system restrictions regarding the appropriateness and/or accuracy of the start date. Because of the important relationship between the start date and the data in the G/L Book Current Depr Yr and G/L Book Days/Pds Remaining fields, however, in most cases you should enter the date at which depreciation originally began for this record. Note: Regardless of the Date of Purchase or Fiscal Year basis assigned to any depreciation method, to ensure the accurate calculation of depreciation, you must set up all Fiscal Year/Period data in Costpoint Fixed Assets for the current fiscal year and one future fiscal year. Use the Manage Fixed Assets Fiscal Years and Manage Fixed Assets Accounting Periods screens to manually enter this data or use the Update FA FY/Pd Information from GL FY/Pd Information screen to copy existing GL data into Costpoint Fixed Assets. It is imperative that you set up this data as part of your initialization procedures before you compute depreciation for the first time. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: B1Depr Start exceeds 10 characters. ERROR MESSAGE: B1Depr Start is an invalid date format. ERROR MESSAGE: An invalid year was entered for B1 Depr Start Dt. ERROR MESSAGE: Depr Status is not set to D for Depreciable.
In-Srvc Date	This field (B1_IN_SERVICE_DT) is only available in an Asset Master record if the asset is depreciable. Depr Based On can only be equal to Y (Years) or U (Units of Usage) methodology. This field is not available if the depreciation is based on L (Lease Pds) methodology. Data in this optional field must be in date format (YYYYMMDD). This date is for information purposes only and is not used in system calculations. (When the system calculates depreciation, the system checks only the date from the G/L Book Depr Start Date field.) The optional date in this field can be a historical, current, or future date. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: B1In-Srvc Dt exceeds 10 characters. ERROR MESSAGE: B1In-Srvc Dt is an invalid date format. ERROR MESSAGE: An invalid year was entered for B1 In-Srvc Dt. ERROR MESSAGE: B1 In-Srvce Dt must be null for a Lease. ERROR MESSAGE: Depr Status is not set to “D” for Depreciable.
Current Depr Yr	This field (B1_CUR_DEPR_YR_NO) is only available in an Asset Master record if the asset is depreciable and you have designated Depr Based On equal to Y (Years). This field should not be populated if you have designated Depr Based On as U (Units of Usage) or L (Lease Periods). This field for Book 1 (the General Ledger book) holds the current depreciation year for the Asset Master record. The format cannot exceed 2 numeric characters (99) and the data can be populated by manual entry. The current depreciation year, along with data in the G/L Book Days/Pds Remaining and G/L Book Depr Start Date field, plays an integral role in the system calculation of depreciation. The value in this field signifies which depreciation year of the asset's useful life is current. As a result of this data, the system can use the appropriate percentage for the current year of life from the depreciation method linked with this record. (Years of useful life and percentages for each year are set up on the Manage Depreciation Methods screen.) For a new asset record, blanks normally display in this field as a default. You can leave this field blank, if desired, because the system will insert "1" in this field for a new blank record the first time that depreciation is calculated for this asset. Alternately, you can manually enter the depreciation year (which should be 1 for a new record), if desired. If you enter a value in this field, however, you must also enter a value in the G/L Book Days/Pds Remaining field, or you will not be able to save the asset record. This field must be blank for the system to populate it with a "1" the first time that depreciation is calculated for this record. If you have entered any number in this field, the system will not replace your entry during depreciation calculations. Although this field is not required, system calculations cannot take place if you have overwritten the system-populated value in this field with blanks. The reason for this is that the system cannot find the appropriate percentage to use from the Manage Depreciation Methods screen if the current depreciation year is not specified. During the initialization of your historical records, you will need to enter the correct current depreciation year for each asset. If, for example, you have an asset for which you have defined a depreciation method with a useful life of five years (the Manage Depreciation Methods screen), you should enter the current year of that life (for example, 1, 2, 3, 4, or 5). In this way, the proper depreciation percentage for the current depreciation year can be used during system calculations. For both new and historical records, once this field is initialized, the system increases the value in this field when required during the appropriate Fixed Assets period close process. The current year increments during the closing process if there are additional years of useful life remaining for the record, and the G/L Book Days/Pds Remaining field displays a 1 (for assets using period-based depreciation) or if the number of days remaining is less than or equal to the number of days in the Fixed Assets period being closed (for assets using a Date of Purchase basis with depreciation calculated based on the number of days owned). At the same time, the value in the G/L Book Days/Pds Remaining field will also change appropriately. Note: Because manually-entered data in the G/L Book Current Depr Yr and G/L Book Days/Pds Remaining fields is especially prone to user error and misinterpretation, you can use the Compute/Update Depreciation Computation Data screen to assist you in verifying the relationship of these two data fields with the G/L Book Depr Start Date field. You can access the Compute/Update Depreciation Computation Data screen from the Fixed Assets Utilities menu. You can run it for any range of asset/item numbers. The utility produces a report, based on the depreciation start date, which shows a side-by-side comparison of both the current values displayed in the Asset Master and the system-computed values for the G/L Book Current Depr Yr and G/L Book Days/Pds Remaining fields. You can print the report for all selected records or for exceptions only, which makes discrepancies easier to identify. After printing the report, you can activate the option in this utility that applies the system-computed values to your asset records. This process updates the existing data in the G/L Book Current Depr Yr and G/L Book Days/Pds Remaining fields by replacing the existing data with the system-computed values. If you do not apply the system-computed values to your data, you may need to manually adjust some values in the G/L Book Current Depr Yr and G/L Book Days/Pds Remaining fields (or, in some cases, the G/L Book Depr Start Date field) to ensure the accuracy of depreciation calculations. Because the Update portion of this utility will overwrite your existing data with system-generated data, you should always carefully review and agree with the reported results on a record-by-record basis before performing the Update process. The Update process is similar to posting routines in that the report must first be printed before you can continue with the Update process. Never run the Update process as a matter of routine unless you agree with the system data changes that will take place in each Asset Master record. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: B1Cur Depr Yr exceeds 2 characters. ERROR MESSAGE: B1Cur Depr Yr is not numeric. ERROR MESSAGE: Depr Based On is not set to “Y” for Years. ERROR MESSAGE: Depr Status is not set to “D” for Depreciable.
Days/Pds Remaining	This field (B1_PDS_REMAIN_NO) is only available in an Asset Master record if the asset is depreciable. Depr Based On can only be equal to Y (Years) methodology. This field is not available if the depreciation is based on L (Lease Pds) or U (Units of Usage) methodology. This field for Book 1 (the General Ledger book) holds the number of periods or days remaining, as applicable, in the current depreciation year for the Asset Master record. The value (and format) cannot exceed 3 numeric characters (999) and the data can be populated by manual entry. The days/periods remaining field, along with the G/L Book Current Depr Yr and G/L Book Depr Start Date fields, plays an integral role in the system calculation of depreciation. The value in this field indicates the number of days or periods remaining in the current depreciation year of the asset's useful life. (Years of useful life and percentages for each year are set up on the Manage Depreciation Methods screen.) For a new asset record, blanks display in this field as a default. You can leave this field blank, if desired, because the system will insert the correct value in this field for a new blank record the first time that depreciation is calculated for this asset. Alternately, you can manually enter the days or periods remaining in this field. If you enter a value in this field, however, you must also enter a value in the G/L Book Current Depr Yr field, or you will not be able to save the asset record. The value in this field will depend on the Date of Purchase or Fiscal Year basis assigned to the depreciation method for this asset. If you have linked a Date of Purchase basis for depreciation method with this record, the value in this field should reflect the number of days or periods remaining in the current purchase year, depending on the option you selected in the System-Wide Configuration for DP Basis Depreciation Methods group box on the Configure Fixed Assets Settings screen. If you have linked a Fiscal Year basis for depreciation method with this record, the value in this field should reflect the number of periods remaining in the current fiscal year. The number of periods remaining cannot be more than 18. This field must be blank for the system to populate it the first time that depreciation is calculated for this record. If you have entered any number in this field, the system will not replace your entry during depreciation calculations. Although this field is not required, if you have over-written the system-populated value in this field with blanks, system calculations cannot take place. The reason for this is that the system cannot depreciate correctly for the current period if the G/L Book Days/Pds Remaining field is not specified. For both new and historical records, once this field is initialized, the system changes this value, as required, during the Fixed Assets period close process. The system increments the current year during the closing process if there are additional years of useful life remaining for the record, and the G/L Book Days/Pds Remaining field displays a 1 (for assets using period-based depreciation) or if the number of days remaining is less than or equal to the number of days in the Fixed Assets period being closed (for assets using a Date of Purchase basis with depreciation calculated based on the number of days owned). At the same time, when the value in the current year increases, the value in the G/L Book Days/Pds Remaining field will also change appropriately for the basis used (Date of Purchase or Fiscal Year). Note: Because manually entered data in the G/L Book Current Depr Yr and G/L Book Days/Pds Remaining fields are especially prone to user error and misinterpretation, you can use the Verify/Update Depr Computation Data screen to assist you in verifying the relationship of these two data fields with the G/L Book Depr Start Date field. You can access this screen from the Fixed Assets Utilities menu. The utility produces a report, based on the depreciation start date, which shows a side-by-side comparison of both the current values displayed in the Asset Master and the system-computed values for the G/L Book Current Depr Yr and G/L Book Days/Pds Remaining fields. You can print the report for all selected records or for exceptions only, which makes discrepancies easier to identify. After printing the report, you can activate the option in this utility that applies the system-computed values to your asset records. This process updates the existing data in the G/L Book Current Depr Yr and G/L Book Days/Pds Remaining fields by replacing the existing data with the system-computed values. If you do not apply the system-computed values to your data, you may need to manually adjust some values in the G/L Book Current Depr Yr and G/L Book Days/Pds Remaining fields (or, in some cases, the G/L Book Depr Start Date field) to ensure the accuracy of depreciation calculations. Because the Update portion of this utility will overwrite your existing data with system-generated data, you should always carefully review and agree with the reported results on a record-by-record basis before performing the Update process. The Update process is similar to posting routines in that the report must first be printed before you can proceed with the Update process. Never run the Update process as a matter of routine unless you agree with the system data changes that will take place in each Asset Master record. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: B1Days/Pds Rem exceeds 3 characters. ERROR MESSAGE: B1Days/Pds Rem is not numeric. ERROR MESSAGE: Days/Pds Rem exceeds maximum value allowed: 366. ERROR MESSAGE: Depr Based On is not set to “Y” for Years. ERROR MESSAGE: Depr Status is not set to “D” for Depreciable.
Amt Taken Purchase YTD	This field (B1_DP_DEPR_YTD_AMT) is only available in an Asset Master record if the asset is depreciable. Depr Based On can only be equal to Y (Years) methodology. This field is not available if the depreciation is based on L (Lease Pds) or U (Units of Usage) methodology. This field for Book 1 (the General Ledger book) holds the dollar amount of depreciation posted for the current purchase year, exclusive of any amounts posted during the current accounting period. The value cannot exceed 999,999,999,999.99, and the data can be populated by manual entry. This field is available only for depreciation methods that use the Date of Purchase basis. (You must select a Date of Purchase or Fiscal Year basis on the Manage Depreciation Methods screen when you set up each depreciation method.) If the method from the G/L Book Depr Method Code field on this screen references a method that uses a Date of Purchase basis, this field is available. If the method from the G/L Book Depr Method Code field on this screen references a method that uses a Fiscal Year basis, this field is not available. The amount taken purchase YTD, along with data in the G/L Book Current Depr Yr and the G/L Book Days/Pds Remaining fields, plays an integral role in the system calculation of depreciation for methods using the Date of Purchase basis. For a new asset record, no data should display in this field. You should leave this field blank for a new record because the system will increase (or possibly decrease) the value in this field by the amount of depreciation posted each time you close the Fixed Assets period. The value in this field will be different from the value in the G/L Book FYTD Depreciation field except when the date of purchase coincides with the start of your fiscal year. The G/L Book Amt Taken Purch YTD field displays purchase year data, while the G/L Book FYTD Depreciation field displays fiscal year data. During the initialization of your historical records, for records linked to depreciation methods that use the Date of Purchase basis for depreciation, you should enter the correct value in this field for the current purchase year of the asset. For both new and historical records, once this field is initialized, the system will automatically change the value in this field by the total amount of depreciation posted for the current accounting period when you perform the Fixed Assets Period Close process. Once each purchase year is complete, the system automatically resets the value in this field to zero, as appropriate. Note: Because-manually entered data in the Amt Taken Purchase YTD field is especially prone to user error and misinterpretation of the system “rules” for this field, you can use the Compute/Update Amount Taken Purchase Year-To-Date screen to assist you in verifying the relationship of this data field with the G/L Book Depr Start Date, G/L Book Current Depr Yr, and G/L Book Days/Pds Remaining fields. This utility generates data based on the premise that no depreciation adjustments were posted in the current asset year prior to the asset’s initialization into Costpoint. You can access this screen from the Fixed Assets Utilities menu. This utility will verify/update Asset Master data only for books in which the assigned depreciation method uses a Date of Purchase basis and whose depreciation start date is prior to the current Fixed Assets posting Fiscal Year, Period, and subperiod. (For assets in the first period of a purchase year, the G/L Book Amt Taken Purchase YTD value will be set to zero.) Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a zero (“0”), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: B1Amt Taken PYTD exceeds 14 characters. ERROR MESSAGE: B1Amt Taken PYTD is not numeric. ERROR MESSAGE: Depr Based On is not set to “Y” for Years. ERROR MESSAGE: Depr Status is not set to “D” for Depreciable.
Asset Account	This field (ASSET_ACCT_ID) is required for both depreciable and non-depreciable Asset Master records, regardless of the depreciation basis methodology, that is, Depr Based On is equal to Y (Years), U (Units of Usage), or L (Lease Periods). This field holds up to 15 alphanumeric characters to designate the asset account, is system-validated, and can be populated by manual entry or by importing data from a specified Asset Template record. Asset accounts denote "ownership" and can include balance sheet combinations, expense account combinations (to track items not capitalized), and/or project combinations for property that should be identified with a contract. The asset account combination specifies the General Ledger asset Account, Organization, Project, Reference 1, and Reference 2 numbers, as applicable, that should be linked with the ownership of an Asset Master record. The Account and Organization are always required; Project, Reference 1, and Reference 2 numbers are always optional (unless a project has been designated as required for the combination). There are no special rules regarding the types of Account/Organization/ Project/Reference 1/Reference 2 combinations that can be used as an asset account. Note: If you enter a project account abbreviation in the Proj Acct Abbrev field in an Asset Master record, the system will populate the Asset Account field with the account previously associated with the project account abbreviation. To use this feature, you must have previously set up optional project account abbreviations codes on the Manage Project Account Groups screen in Costpoint Project Setup. For additional information about this feature, please refer to specific documentation for the Manage Project Account Groups screen and Projects related topic , Project Account Groups. When you save an Asset Master record, the system will validate that the account is a detail account and that it is active. If the account fails one of these validations, you will need to either make corrections to the account or enter a different account number. [Additional validations regarding the Account/Organization/Project/Reference 1/Reference 2 data, as applicable, will also be performed before the record can be saved. The system will validate that the account is valid for the organization and, if project-required, is also valid for the project. If a project has been associated with the account, it must allow charges and be active for the PAG (Project Account Group). Additionally, if “Limit Accounts” applies to the project, the related account must have been linked to the project on the Link Projects/Accounts application. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Asset Account field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No (if it exists) to determine the data for that field. In the circumstance that data exists in the input file/table for Asset Account, even if there is a corresponding template data field value, the system will bypass any reference to the Template No.
Asset Organization	This field (ASSET_ORG_ID) is required for both depreciable and non-depreciable Asset Master records, regardless of the depreciation basis methodology, that is, Depr Based On is equal to Y (Years), U (Units of Usage), or L (Lease Periods). This field holds up to 20 alphanumeric characters to designate the asset organization, is system-validated, and can be populated by manual entry or by importing data from a specified Asset Template record. Asset organizations, as with accounts, denote "ownership" and can include balance sheet combinations, expense account combinations (to track items not capitalized), and/or project combinations for property that should be identified with a contract. The asset account combination specifies the General Ledger asset Account, Organization, Project, Reference 1, and Reference 2 numbers, as applicable, that should be linked with the ownership of an Asset Master record. The Account and Organization are always required; Project, Reference 1, and Reference 2 numbers are always optional (unless a project has been designated as required for the combination). There are no special rules regarding the types of Account/Organization/ Project/Reference 1/Reference 2 combinations that can be used as an asset account. Note: If you enter a project account abbreviation in the Proj Acct Abbrev field in an Asset Master record, the system will populate the Asset Organization field with the organization previously associated with the project account abbreviation. To use this feature, you must have previously set up optional project account abbreviations codes on the Manage Project Account Groups screen in Costpoint Project Setup. For additional information about this feature, please refer to specific documentation for the Project Account Groups screen and Projects related topic, Project Account Groups. When you save an Asset Master record, the system will validate that the organization is active. If the organization fails this validation, you will need to either make corrections to the organization or enter a different organization. Additional validations regarding the Account/Organization/Project/Reference 1/Reference 2 data, as applicable, will also be performed before the record can be saved. The system will validate that the organization is valid for use with the account and, if project-required, is also valid for the project. If “Limit Orgs” applies to the project, the related organization must be included on the Link Projects/Organizations screen. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Asset Organization field is blank in the input file/table for which there is a corresponding template data field, the system will use the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Asset Organization, even if there is a corresponding template data field value, the system will bypass any reference to the Template No.
Asset Project	This field (ASSET_PROJ_ID) is optional for both depreciable and non-depreciable Asset Master records (unless a project has been designated as required for the account/org combination). It can be used regardless of the depreciation basis methodology, that is, Depr Based On is equal to Y (Years), U (Units of Usage), or L (Lease Periods). This field holds up to 30 alphanumeric characters to designate the asset project, as applicable, is system-validated, and can be populated by manual entry or by importing data from a specified Asset Template record. Asset projects, as with accounts and organizations, denote "ownership" and can include balance sheet combinations, expense account combinations (to track items not capitalized), and/or project combinations for property that should be identified with a contract. The asset account combination specifies the General Ledger asset Account, Organization, Project, Reference 1, and Reference 2 numbers, as applicable, that should be linked with the ownership of an Asset Master record. The Account and Organization are always required; Project, Reference 1, and Reference 2 numbers are always optional (unless a project has been designated as required for the combination). There are no special rules regarding the types of Account/Organization/ Project/Reference 1/Reference 2 combinations that can be used as an asset account. Note: If you enter a project account abbreviation in the Proj Acct Abbrev field in an Asset Master record, the system will populate the Asset Project field with the project previously associated with the project account abbreviation. To use this feature, you must have previously set up optional project account abbreviations codes on the Manage Project Account Groups screen in Costpoint Project Setup. For additional information about this feature, please refer to specific documentation for the Project Account Groups screen and Projects relate topic, Project Account Groups. When you save an Asset Master record, the system will validate that the project is active. If the project fails this validation, you will need to either make corrections to the project or enter a different project. Additional validations regarding the Account/Organization/Project/Reference 1/Reference 2 data, as applicable, will also be performed before the record can be saved. The system will validate that the project is valid for use with the account. The project must allow charges and be active for the PAG (Project Account Group). Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Asset Project field is blank in the input file/table for which there is a corresponding template data field, the system will use the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Asset Project, even if there is a corresponding template data field value, the system will bypass any reference to the Template No.
Ref 1 (or your label)	If you designated a different label for Reference 1 on the Configure General Ledger Settings screen in Costpoint General Ledger, your label displays at this field. If you did not set up a different label for Reference 1, “Asset Ref 1” displays as the label for this field. This field (ASSET_REF1_ID) is optional for both depreciable and non-depreciable Asset Master records, regardless of the depreciation basis methodology, that is, Depr Based On is equal to Y (Years), U (Units of Usage), or L (Lease Periods). This field holds up to 20 alphanumeric characters to designate the optional asset Reference 1 data for this record, as applicable, is system-validated, and can be populated by manual entry or by importing data from a specified Asset Template record. The asset account combination specifies the General Ledger asset Account, Organization, Project, Reference 1, and Reference 2 numbers, as applicable, that should be linked with the ownership of an Asset Master record. The Account and Organization are always required; Project, Reference 1, and Reference 2 numbers are always optional (unless a project has been designated as required for the combination). There are no special rules regarding the types of Account/Organization/ Project/Reference 1/Reference 2 combinations that can be used as an asset account. When you save an Asset Master record, the system will validate that the reference 1 designation is active and valid, as applicable. If the validation fails, you will need to make corrections to the reference number, enter a different reference number, or delete the reference number. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Asset Ref1 field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Asset Ref1, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Possible Error Messages: ERROR MESSAGE: Ref 1 cannot exceed 20 characters. ERROR MESSAGE: Ref1 ID does not exist for this company.
Asset Ref 2 (or your label)	If you designated a different label for Reference 2 on the Configure General Ledger Settings screen in Costpoint General Ledger, your label displays at this field. If you did not set up a different label for Reference 2, “Asset Ref 2” displays as the label for this field. This field (ASSET_REF2_ID) is optional for both depreciable and non-depreciable Asset Master records, regardless of the depreciation basis methodology, that is, Depr Based On is equal to Y (Years), U (Units of Usage), or L (Lease Periods). This field holds up to 20 alphanumeric characters to designate the optional asset Reference 2 data for this record, as applicable, is system-validated, and can be populated by manual entry or by importing data from a specified Asset Template record. The asset account combination specifies the General Ledger asset Account, Organization, Project, Reference 1, and Reference 2 numbers, as applicable, that should be linked with the ownership of an Asset Master record. The Account and Organization are always required; Project, Reference 1, and Reference 2 numbers are always optional (unless a project has been designated as required for the combination). There are no special rules regarding the types of Account/Organization/ Project/Reference 1/Reference 2 combinations that can be used as an asset account. When you save an Asset Master record, the system will validate that the Reference 2 designation is active and valid, as applicable. If the validation fails, you will need to make corrections to the reference number, enter a different reference number, or delete the reference number. Although the system permits you to edit the data in this field in an Asset Master record as you choose, use caution if you make changes to this field after the system has already posted depreciation to the G/L to avoid unexpected results. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Asset Ref2 field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Asset Ref2, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Possible Error Messages: ERROR MESSAGE: Ref2 cannot exceed 20 characters. ERROR MESSAGE: Ref2 ID does not exist for this company.
B1_DP_DEPR_NY_AMT	This field exists only in the ASSET table and is hidden from view in an Asset Master record. This field (B1_DP_DEPR_NY_AMT) only applies if: You have designated that the system should compute current period depreciation based on Actual number of days “owned” in the System-Wide Configuration for DP Basis Depreciation Methods group box on the Configure Fixed Assets Settings screen. The asset is depreciable. You have designated Depr Based On as Y (Years). You have enabled the system-wide configuration for Date of Purchase basis depreciation calculations based on actual number of days “owned” (rather than the number of periods is a purchase year) on the Configure Fixed Assets Settings screen. The depreciation method you have assigned to the Asset Master records uses a Date of Purchase basis. You are initializing this data for a historical record with actual history. This field for Book 1 (the General Ledger book) holds any applicable “next year” amount taken purchase YTD needed to true up the “leftover” amount for an Asset Master record that does not coincide with the end of the actual purchase year. The value cannot exceed 999,999,999,999.99. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table, insert a zero (“0”), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: B1 DP Depr NY exceeds 14 characters. ERROR MESSAGE: B1 DP Depr NY is not numeric. ERROR MESSAGE: Depr Based On is not set to “Y” for Years. ERROR MESSAGE: Depr Status is not set to “D” for Depreciable.
Post Seq No	This field (POST_SEQ_NO) is only temporarily assigned to asset master records. The value should be NULL at the point at which an asset record is to be imported into Costpoint. The post sequence number is not available for manual entry in the Asset Master record. The system will display a sequence number in this field for entries that were unsuccessfully posted or if the system is currently in the process of posting an entry for another Asset Master record. Identical posting sequence numbers are assigned by the system to all entries posted in a specific session. If a record has a posting sequence number, you will not be able to save any changes made to other fields in an Asset Master record. After the entry has been successfully posted for the asset, the sequence number will no longer display in this field. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: Post Seq No must be NULL. ERROR MESSAGE: Post Seq No is not numeric. ERROR MESSAGE: Post Seq No exceeds 10 characters.
Disposal Post Date	This field (DISP_POST_DT) is only applicable for an Asset Master record if the Record Status for the asset is equal to D (Disposal). This field is not available for user entry on the Manage Disposal Transactions screen or in Asset Master records, whether the disposal was system-generated as a result of a posted disposal or manually entered. The field holds the system-generated disposal posted date in date format (YYYYMMDD) for SYSTEM and PREPRO disposal system codes. If the disposal system code is MANUAL, the system displays blanks in this non-editable field. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: Disp Post Date is an invalid date format. ERROR MESSAGE: An invalid year was entered for Disp Post Dt. ERROR MESSAGE: Disp Post Date exceeds 10 characters.
User ID	This field (DISP_POST_USER_ID) is only applicable for an Asset Master record if the Record Status for the asset is D (Disposal). This field is not available for user entry on the Manage Disposal Transactions screen or in Asset Master records, whether the disposal was system-generated as a result of a posted disposal or manually entered. The field holds up to 20 alphanumeric characters to identify the user ID that ran the disposal posting process for SYSTEM and PREPRO disposal entry types. If the disposal entry type is MANUAL, the system displays blanks in this non-editable field. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: Disp Post User does not exist. ERROR MESSAGE: Disp Post User exceeds 20 alphanumeric characters.
Receipt ID	This optional field (RECPT_ID) holds up to 10 alphanumeric characters to record the receipt identifier for this record, as applicable. This field can be populated by manual entry and is not system-validated in an Asset Master record. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: This Receipt ID exceeds 10 alphanumeric characters.
Vchr Line No	This optional field (VCHR_LN_NO) holds up to 5 numeric characters and can be populated by manual entry. The data for this field is not system-validated in an Asset Master record. There is no corresponding Asset Template field. Possible Error Messages: ERROR MESSAGE: Voucher Ln No exceeds 5 characters. ERROR MESSAGE: Voucher Ln No is not numeric.
Post Disposal to G/L	This required field (ND_POST_DISP_FL) holds a single-character Y (Yes) or N (No) selection. The system default for this field is Y (Yes), which can be changed by manual entry or by importing data from a specified Asset Template record. This check box is available only if you have specified that the Asset Master record is non-depreciable (Depr Status is Non-Depreciable). The default for this check box is selected. If you select this check box for a non-depreciable asset, you can post a future disposal entry for this record to the General Ledger. In the case of non-depreciable assets (for example, land), the G/L entry on disposal can consist only of debits and credits, as appropriate, to the Cost and the Gain/Loss on Sale of Fixed Assets account(s) because there is no accumulated depreciation associated with a non-depreciable asset. You cannot clear this check box for depreciable assets because disposal entries will always be posted to the General Ledger for depreciable assets. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the Receiving database, as follows: If the Post Disposal to G/L field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No  to determine the data for that field. In the circumstance that data exists in the input file/table for Post Disposal to G/L, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Preprocessor Default Rules: If this field is NULL in the input file and there is no template, enter “Y” as the value for this field. If S_DEPR_STATUS_CD = “D,” enter “Y” as the default for this field. Possible Error Messages: ERROR MESSAGE: Post Disp to G/L exceeds 1 alphanumeric character. ERROR MESSAGE: Non-Depreciable Post Disp to GL is not Y or N.
Disposal Document No	This optional field (DISP_DOC_NO) is only available in an Asset Master record if the Record Status for the asset is D (Disposal). The optional disposal document number (or other data) field holds up to 20 alphanumeric characters, as applicable. This field can be populated by manual entry, and the data is not system-validated. The disposal document number is optional on the Manage Disposal Transactions screen during data entry. Blanks display in this field as a default value. When you post a disposal, the system automatically moves the data, as applicable, from the appropriate disposal entry screen to this field. Disposal data that displays in Asset Master records as a result of G/L postings is treated as a “System-Generated” (SYSTEM) disposal for which manual edits are not permitted. For a historical disposal that was not system-generated, you can manually enter the appropriate disposal description during initialization. In this circumstance, the disposal data is treated as a “Manual” (MANUAL) disposal and manual edits are permitted. There is no corresponding Asset Template field. Preprocessor Default Rules: If this field is NULL in the input file/table and in the Template, insert a space (‘ ‘), since NULLs are not permitted by the system for this field. Possible Error Messages: ERROR MESSAGE: This Disp Doc No exceeds 20 alphanumeric characters.
Subclass Code	This optional field (FA_SUBCLASS_CD) holds up to 6 alphanumeric characters, and can be populated by manual entry or by importing data from a specified Asset Template record. Subclass codes are validated against user-specified data initialized on the Manage Subclass Codes screen. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the destination database, as follows: If the Subclass Code field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Subclass Code, even if there is a corresponding template data field value, the system will bypass any reference to the Template No.
Employee	This optional field (EMPL_ID) holds up to 12 alphanumeric characters to designate a valid employee ID “owner” for the Asset Master record. The system validates employee data entered in this field against employee data from the Manage Employee Information screen. If you need to enter data for custodians that are not valid employees (or if you do not want to use this field), you can use the other non-validated user-defined "government" fields and/or the user-defined fields to accept and hold this data. Template Numbers (along with any applicable revision numbers) are permitted in the input file/table. If the Template No/Rev No is populated on an input file/table record, the asset record will be populated with the values associated with the Template No/Rev No as they exist in the destination database, as follows: If the Employee field is blank in the input file/table for which there is a corresponding template data field value, the system will use the Template No to determine the data for that field. In the circumstance that data exists in the input file/table for Employee, even if there is a corresponding template data field value, the system will bypass any reference to the Template No. Possible Error Messages: ERROR MESSAGE: Employee ID exceeds12 alphanumeric characters. ERROR MESSAGE: This Employee ID does not exist.
Disposal Type	This optional field (FA_DISP_TYPE) holds up to 6 alphanumeric characters to designate a valid disposal type for the Asset Master record (such as “Scrapped,” “Obsolete,” “Sold,” and so on), as applicable. This field can be populated by manual entry. Disposal types are validated against user-specified data initialized on the Manage Disposal Types screen. The disposal type is optional on the Manage Disposal Transactions screen during data entry. Blanks display in this field as a default value. When you post a disposal, the system automatically moves the data, as applicable, from the appropriate disposal entry screen to this field. Disposal data that displays in Asset Master records as a result of G/L postings is treated as a “System-Generated” (SYSTEM) disposal for which manual edits are not permitted. For an historical disposal that was not system-generated, you can manually enter the appropriate disposal description during initialization. In this circumstance, the disposal data is treated as a “Manual” (MANUAL) disposal and manual edits are permitted. There is no corresponding Asset Template field.
UID	This field (UID_CD) holds up to 78 alphanumeric characters to designate a valid Unique Item Identifier (UID) for the Asset record. If data originated in Costpoint Purchasing and/or Receiving (regardless of whether the data was captured at the time of receipt or at time of posting), this column on the Manage Autocreation Transactions screen may display optional data entered in the UID field in the Fixed Assets tab during the Receiving function. The subtask is available for data entry or edits (using the Fixed Assets link) from both the Manage Purchase Order Receipts and Manage Quality Control Inspections screens of Costpoint Receiving if the account combination charged on the PO Line has been set up as an Autocreation Account and if the account does not have an inventory abbreviation. Note: The system requires receipt identification data in order to establish linkage when copying Fixed Assets data entered in the Fixed Assets subtask (on the Manage Purchase Order Receipts and/or Manage Quality Control Inspections screens in Costpoint Receiving) to this column on the Manage Autocreation Transactions screen. (To enable the system to write optional Fixed Assets data entered in the subtask to the Manage Autocreation Transactions screen, you must also enter receipt identification data in the normally optional Rcpt field on the Manage Purchase Order Vouchers screen in Costpoint Accounts Payable.) If data originated in Costpoint Accounts Payable (on either the Manage Purchase Order Vouchers or the Manage Accounts Payable Vouchers screen), this column on the Manage Autocreation Transactions screen will be blank, because this field is not available on those screens. You can make changes to this column, but exercise caution. The UID field is intended to be a unique identifying value for an asset record. Although there are controls to ensure that duplicate UID values do not exist in the Costpoint database, the system cannot prevent you from entering an invalid UID value, either using an invalid UID construct method or using a value duplicated outside the database. This column is not duplicated in a template. When you run the final autocreation process, the system populates the UID field on the Govt Info tab of the Manage Asset Master Information screen (and to the Manage Asset Government Information screen) with data from this column. You can make changes to the UID field after autocreation, but exercise caution. The auto-generate UID capability is not available after the record on the Manage Autocreation Transactions screen is converted into a Fixed Assets record.
UID Type	This field (S_UID_TYPE) holds up to 5 alphanumeric characters to designate a valid UID type that indicates what construction method was for the UID code. If data originated in Costpoint Purchasing and/or Receiving (regardless of whether the data was captured at the time of receipt or at time of posting), this column on the Manage Autocreation Transactions screen may display optional data entered or populated when a UID value was auto-generated on the Fixed Assets tab during the Receiving function. The subtask is available for data entry or edits (using the Fixed Assets link) from both the Manage Purchase Order Receipts and Manage Quality Control Inspections screens of Costpoint Receiving if the account combination charged on the PO Line has been set up as an Autocreation Account and if the account does not have an inventory abbreviation. Note: The system requires receipt identification data in order to establish linkage when copying Fixed Assets data entered in the Fixed Assets subtask (on the Manage Purchase Order Receipts and/or Manage Quality Control Inspections screens in Costpoint Receiving) to this column on the Manage Autocreation Transactions screen. (To enable the system to write optional Fixed Assets data entered in the subtask to the Manage Autocreation Transactions screen, you must also enter receipt identification data in the normally optional Rcpt field on the Manage Purchase Order Vouchers screen in Costpoint Accounts Payable.) If data originated in Costpoint Accounts Payable (on either the Manage Purchase Order Vouchers or the Manage Accounts Payable Vouchers screen), this column on the Manage Autocreation Transactions screen will be blank, because this field is not available on those screens. You can make changes to this column, but exercise caution. The UID Type is used in the auto-generation of a UID value. The UID Type tells the auto-generation process what data should be used in the construction of the UID. If a UID was auto-generated either on the Manage Autocreation Transactions screen or in the Fixed Assets subtask (on the Manage Purchase Order Receipts and/or Manage Quality Control Inspections screens in Costpoint Receiving), then the UID Type that was used to generate the UID will appear in this column. Changing the UID Type value that was used to generate the UID for an asset will cause a miss-match between the UID value and the record of the method used to create the UID value. If the UID Type field was populated when a UID was auto-generated, then that UID Type value was used to determine the construction of the UID. If the UID Type column was empty when the UID auto-generation was performed, then a default UID Type that is visible on the Configure Autocreation Settings screen was used to create the UID. As part of the UID auto-generation process, when the default UID Type is used, the default UID Type value is entered into the UID Type column for the asset(s) as part of the auto-generation process. See the Help for the Generate UID button on the Manage Autocreation Transactions screen for additional information about the UID auto-generation process. This field is not duplicated in a template. When you run the final autocreation process, the system populates the UID Type field on the Govt Info tab of the Manage Asset Master Information screen (and to the Manage Asset Government Information screen) with data from this column on the Manage Autocreation Transactions screen. You can make changes to the UID Type field after autocreation, but exercise caution.
Issuing Agency Code	This field (UID_IAC_CD) holds up to 3 alphanumeric characters that identify the issuing agency code who assigned the enterprise identifier for the UID. If data originated in Costpoint Purchasing and/or Receiving (regardless of whether the data was captured at the time of receipt or at time of posting), this column on the Manage Autocreation Transactions screen may display optional data entered in the UID Issuing Agency field or populated when a UID value was auto-generated on the Fixed Assets tab during the Receiving function. The subtask is available for data entry or edits (using the Fixed Assets link) from both the Manage Purchase Order Receipts and Manage Quality Control Inspections screens of Costpoint Receiving if the account combination charged on the PO Line has been set up as an Autocreation Account and if the account does not have an inventory abbreviation. Note: The system requires receipt identification data in order to establish linkage when copying Fixed Assets data entered in the Fixed Assets subtask (on the Manage Purchase Order Receipts and/or Manage Quality Control Inspections screens in Costpoint Receiving) to this column on the Manage Autocreation Transactions screen. (To enable the system to write optional Fixed Assets data entered in the subtask to the Manage Autocreation Transactions screen, you must also enter receipt identification data in the normally optional Rcpt field on the Manage Purchase Order Vouchers screen in Costpoint Accounts Payable.) If data originated in Costpoint Accounts Payable (on either the Manage Purchase Order Vouchers or the Manage Accounts Payable Vouchers screen), this column on the Manage Autocreation Transactions screen will be blank, because this field is not available on those screens. You can make changes to this column, but exercise caution. The UID Issuing Agency is a component of the UID Prefix used in the auto-generation of a UID value when the UID Type value is UID1 or UID2. In both cases, the UID Issuing Agency (as the first part of the UID Prefix,) becomes the first part of the UID value. If a UID was auto-generated either on the Manage Autocreation Transactions screen or in the Fixed Assets subtask (on the Manage Purchase Order Receipts and/or Manage Quality Control Inspections screens in Costpoint Receiving), then the UID Issuing Agency value that was part of the UID Prefix used to generate the UID will appear in this column. Changing the UID Issuing Agency value that was used as part of the UID Prefix to generate the UID for an asset will cause a miss-match between the UID value and the components that make up the UID value. If the UID Issuing Agency field was populated for a record when a UID was auto-generated, then the UID Issuing Agency on the record was NOT used to determine the construction of the UID. The UID Issuing Agency column should be empty when the UID auto-generation is performed. At that time, the default UID Issuing Agency visible on the Configure Autocreation Settings screen will be used to construct the UID. (This assumes that the UID Prefix set up on the Configuration screen correctly includes the default UID Issuing Agency as the first part of the UID Prefix.) As part of the UID auto-generation process, the default value is entered into the UID Issuing Agency column for the asset as long as the record’s UID Issuing Agency column is empty. See the Help for the Generate UID button on the Manage Autocreation Transactions screen for additional information about the UID auto-generation process. Note: If an incorrect value has been entered into the UID Issuing Agency field either before or after the UID auto-generation is performed, that incorrect UID Issuing Agency will not match the UID Issuing Agency value that was part of the UID Prefix used to create the new UID value, and there will be a mismatch on the screen between the UID value and the UID Issuing Agency. As a business practice, the UID Issuing Agency field should be empty when the auto-generation of UID values takes place. This field is not duplicated in a template. When you run the final autocreation process, the system populates the UID Issuing Agency field on the Govt Info tab of the Manage Asset Master Information screen (and to the Manage Asset Government Information screen) with data from this column on the Manage Autocreation Transactions screen. You can make changes to the UID Issuing Agency field after autocreation, but exercise caution. The auto-generate UID capability is not available after the record on the Manage Autocreation Transactions screen is converted into a Fixed Assets record.
Enterprise Identifier	This field (UID_EID_CD) holds up to 13 alphanumeric characters that designates the code that was assigned by the issuing agency to the manufacturer, vendor, contractor or other entity responsible for creating the UID. If data originated in Costpoint Purchasing and/or Receiving (regardless of whether the data was captured at the time of receipt or at time of posting), this column on the Manage Autocreation Transactions screen may display optional data entered in the UID Enterprise Identifier field or populated when a UID value was auto-generated on the Fixed Assets tab during the Receiving function. The subtask is available for data entry or edits (using the Fixed Assets link) from both the Manage Purchase Order Receipts and Manage Quality Control Inspections screens of Costpoint Receiving if the account combination charged on the PO Line has been set up as an Autocreation Account and if the account does not have an inventory abbreviation. Note: The system requires receipt identification data in order to establish linkage when copying Fixed Assets data entered in the Fixed Assets subtask (on the Manage Purchase Order Receipts and/or Manage Quality Control Inspections screens in Costpoint Receiving) to this column on the Manage Autocreation Transactions screen. (To enable the system to write optional Fixed Assets data entered in this subtask to the Manage Autocreation Transactions screen, you must also enter receipt identification data in the normally optional Rcpt field on the Manage Purchase Order Vouchers screen in Costpoint Accounts Payable.) If data originated in Costpoint Accounts Payable (on either the Manage Purchase Order Vouchers or the Manage Accounts Payable Vouchers screen), this column on the Manage Autocreation Transactions screen will be blank, because this field is not available on those screens. You can make changes to this column, but exercise caution. The UID Enterprise Identifier is a component of the UID Prefix used in the auto-generation of a UID value when the UID Type value is UID1 or UID2. In both cases, the UID Enterprise Identifier (as the second part of the UID Prefix,) becomes the second part of the UID value. If a UID was auto-generated either on the Manage Autocreation Transactions screen or in the Fixed Assets subtask (on the Manage Purchase Order Receipts and/or Manage Quality Control Inspections screens in Costpoint Receiving), then the UID Enterprise Identifier value that was part of the UID Prefix used to generate the UID will appear in this column. Changing the UID Enterprise Identifier value that was used to generate the UID for an asset will cause a miss-match between the UID value and the components that make up the UID value. If the UID Enterprise Identifier field was populated on a record when a UID was auto-generated, then that UID Enterprise Identifier was NOT used to determine the construction of the UID. The UID Enterprise Identifier should be empty when the UID auto-generation is performed. At that time, the default UID Enterprise Identifier on the Configure Autocreation Settings screen will be used to construct the UID. As part of the UID auto-generation process, when the default UID Enterprise Identifier is used and the Enterprise Identifier column is empty, the default value is entered into the UID Enterprise Identifier column for the asset as part of the auto-generation process. See the Help for the Generate UID button on the Manage Autocreation Transactions screen for additional information about the UID auto-generation process. Note: If an incorrect value has been entered into the UID Enterprise Identifier column either before or after the UID auto-generation is performed, that incorrect UID Issuing Agency will not match the UID Issuing Agency value that was part of the UID Prefix used to create the new UID value, and there will be a mismatch on the screen between the UID value and the UID Enterprise Identifier. As a business practice, the UID Enterprise Identifier field should be empty when the auto-generation of UID values takes place. This field is not duplicated in a template. When you run the final autocreation process, the system populates the UID Enterprise Identifier field on the Govt Info tab of the Manage Asset Master Information screen (and to the Manage Asset Government Information screen) with data from this column on the Manage Autocreation Transactions screen. You can make changes to the UID Enterprise Identifier field after autocreation, but exercise caution. The auto-generate UID capability is not available after the record on the Manage Autocreation Transactions screen is converted into a Fixed Assets record.
CAGE ID	This field (CAGE_ID_FLD) holds up to 5 alphanumeric characters that designates the Commercial and Government Entity (CAGE) ID which identifies the government contractor for the Asset record. If data originated in Costpoint Purchasing and/or Receiving (regardless of whether the data was captured at the time of receipt or at time of posting), this column on the Manage Autocreation Transactions screen may display optional data entered in the CAGE ID field on the Fixed Assets tab during the Receiving function. This subtask is available for data entry or edits (using the Fixed Assets link) from both the Manage Purchase Order Receipts and Manage Quality Control Inspections screens of Costpoint Receiving if the account combination charged on the PO Line has been set up as an Autocreation Account and if the account does not have an inventory abbreviation. Note: The system requires receipt identification data in order to establish linkage when copying Fixed Assets data entered in the Fixed Assets subtask (on the Manage Purchase Order Receipts and/or Manage Quality Control Inspections screens in Costpoint Receiving) to this column on the Manage Autocreation Transactions screen. (To enable the system to write optional Fixed Assets data entered in this subtask to the Manage Autocreation Transactions screen, you must also enter receipt identification data in the normally optional Rcpt field on the Manage Purchase Order Vouchers screen in Costpoint Accounts Payable.) If data originated in Costpoint Accounts Payable (on either the Manage Purchase Order Vouchers or the Manage Accounts Payable Vouchers screen), this column on the Manage Autocreation Transactions screen will be blank, because this field is not available on those screens. You can make changes to this field. This field is not duplicated in a template. When you run the final autocreation process, the system populates the CAGE ID field on the Govt Info tab of the Manage Asset Master Information screen (and to the Manage Asset Government Information screen) with data from this column on the Manage Autocreation Transactions screen. You can make changes to the CAGE ID field after autocreation. Lease Type (S_LEASE_TYPE_CD: Should be O (Operating) or F (Finance) for Capitalize, S (Straight Line) for Depreciable Lease and NULL for others (Depreciable Years, Depreciable Units and Non Depreciable) Commencement Start Date (COMM_START_DT) First Payment Date (FIRST_PYMT_DT) Interest Rate (INT_RATE) B1 Lease Liability Amount (B1_LEASE_LIABL_AMT