Administration Help   I   Human Resource Management Help  I   Performance Budgeting Help

Automatic Shell Generation

This option controls the default value of the Shell Indicator field of the payment request Commodity Line.

• Off – No Shell Process: The Fixed Asset Shell Generation system process will not be used and the only value allowed on the payment request will be No Shell.

• On – No Shell (Default): The Fixed Asset Shell Generation system process is a possibility only if the defaulting value of No Shell on a payment request is manually changed to either ‘shell’ choices.

• On – Single Shell (Default): The default on the payment request, given other edits passed, will be Single Shell, even if the quantity is greater than 1.

• On – Multiple Shells (Default): The default on the payment request when the quantity is greater than 1, given other edits passed, will be Multiple Shell. Single Shell being the default when 1.

Program Fixed Asset Linking

An indication that the Program Asset Generation functionality shared between Cost Accounting and Fixed Assets is used.

Require Fixed Asset Catalog

An indication that when Yes will require entry of the Fixed Asset Catalog field on the Header tab for a composite asset. If not a composite asset, then the field must be entered on the Component tab.

Custodian Required

An indication that when Yes will require the entry of a custodian for all composite assets on the Header tab or on the Component tab if not a composite asset.

Catalog Powerful Inference

An indication that when Yes makes  any settings defined for a Fixed Asset Catalog a powerful inference to the Fixed Asset Transaction, where they cannot be changed. This will enforce consistency for assets within the same catalog.

Allow Memo Classification of Capitalization Criteria Assets

An indication that when Yes  will allow the Memo Asset indication to be true even if the asset meet or surpassed the Fixed Asset Capitalization Criteria for Minimum Dollar Threshold and Minimum Useful Life.

Valid Location Custodian Combination Validation

An indication that when Yes enables the Valid Location Custodian Combination (VLOCC) page to edit the combination of Custodian, Department and Location to ensure accurate fixed asset information.

Valid Fund Dept Unit Custodian Combination Validation

An indication that when Yes enables the Valid Fund Department Unit Custodian Combination (VFDUCC) page to edit the combination of Custodian, Fund, Department and Unit to ensure accurate fixed asset information.

Enable Department Required on Custodian

This option is the first of several steps to define each custodian for a department and assure accurate asset association with the Responsibility Center Department. When selected, Custodian records edit and filter with the Department on various pages and transactions. Editing and row filtering then occurs, where the custodian is editable throughout various fixed asset pages and transactions.

When left unselected, it is the responsibility of a user to associate a custodian correctly with an asset.

Other steps include making the Department field visible on the Custodian reference page, adding the required field indication, and adding a Configurable Validation that the field is required (for example, empty (DEPT_CD)).

Auto Component Numbering

This option exists to provide structured and sequential numbering to Fixed Asset Component Numbers at the time of acquisition. when a number has not been manually entered. This field defines that numbering convention. That convention can be alpha-numbering (0001, 001, 01, 1, C1, C01, so forth) and starts with 1 for each new asset.

The component number can always be automatically assigned using this option and by protecting the Fixed Asset Component Number field on transactions using Configure Page (DESIGNER).

For betterment, the component number is arrived at by adding one number to the last available component number from the Fixed Asset Registry Component (FARCOMP) and by adding draft Fixed Assets, if any.

Infer Payment Details on Accounting

As the Fixed Asset transaction type has fields for Payment Request on both the component and accounting lines where those at the component serve as a location to enter the information once to infer to all accounting lines within the component line, the inference is a weak one. This allows a user to supply different values at the accounting line. Doing this on a fixed asset shell is not common, but on manually entered acquisitions that could have spanned multiple payment requests, a user can capture each of those separately on different accounting lines.

Leaving this indication as no/false ensures that override capability at the accounting line. Setting the indication to yes/true changes that inference behavior from a weak one to a powerful one that does not allow for variation of the Payment Request Code, Department, ID, Vendor Line, and Commodity Line fields. Please note that this inference is not based on any particular Fixed Asset Classification.

Infer Payment Details on Accounting from Component for Memo Classification

While the acquisition of memo assets can be done through the Fixed Asset Shell process, they are often uploaded in bulk or manually entered as the capitalized threshold is often not reached. In all cases, the Memo Asset header indication must be yes/true and the Fixed Asset Classification set to Memo. In each of those cases, Payment Request information is optional unless made required through a Configurable Validation. When entered on a component line, the information is not pushed to accounting lines unless the Infer Payment Details on Accounting indication is yes/true. If that setting is no/false and this indication is also no/false, then Payment Request details for a memo asset are recorded only at the component line level. However, if this indication is yes/true, then those details from the component are inferred to the accounting line.

Note: When both Infer Payment Details on Accounting and Infer Payment Details on Accounting from Component for Memo Classification are set to Yes, and the Payment Request details are also present in the accounting section, then Payment Request details from Component will be used.

Registry Summarization

The two Funding Year fields and the twenty-seven COA fields have a separate indication that when Yes means that the value for the field will be retained for display (no data is summarized off) on the Fixed Asset Registry Accounting inquiry page. Those fields that must be retained for display are protected. These settings can be modified at any time and when the next time the page is accessed the display summarization will reflect the new settings.

Responsibility Center Requirements

The twenty-seven COA fields have a separate rule for the respective Responsibility Center COA field. Those that must be entered are protected. The rules only apply to when the Responsibility Center COA are being used for posting (for example, Responsibility Center Posting indication at the Accounting Line is set to true). When that is true, Fund is always required in addition to Department and Unit, which are required at all times.

The common values for requirements exist: Optional, Prohibited and Required. However, there is a fourth value that is unique to this set of rules: Infer Blank. If this value, the system defaults a hard inference of BLNK to that designated COA element so that it will clear out any value in the respective Accounting Line field. Program, Phase, and Program Period are common COA for this Infer BLNK setting because they have a definite end date that will likely be before the asset is disposed.