Skip to main content
Skip table of contents

POFA - CONTROL

Fixed Asset (FA) Flagging and Settings
This common code tells the system how to determine a Fixed Asset. Assets are tagged an Asset per the Object Code used and/or the unit price of each line item of the PO Purchase Request (POUPPR) page's order being processed. When the record meets the criteria set by this common code, the item may be flagged as a fixed asset. "Flag" means that the Fixed Asset column within the POUPPR page will update with a "Y."
Both the "PO to FA" and "AP to FA" interfaces use this common code for automatically flagging purchases as fixed assets based on the object code and/or purchase value.
The PO to FA interface can be configured to create an FASITE record (LOC tab) and/or an FAWARR record when an asset is created during the receiving process using Associated Codes (3) and (4).
Note: Optionally, Associated Numeric Values 1 and 2 may be used to define the minimum and maximum fixed asset item amounts. When the values are left blank, the user controls asset acquisitions strictly by Object Code (typically capital outlay expenses should be using these Objects).
Code Category: POFA
Code Value: CONTROL
Short Description: "AUTO" will automatically flag, "MAN" will require flagging manually. Feature used by the PO to FA interface (POUPGN question "PO to FA Interface" active (checked)); this option will assign the Asset ID/FAID automatically when enter "AUTO" rather than the user needing to click on the ellipse to populate the field with the seed value.
Medium Description: Used to describe the common code
Long Description: Used to describe the common code
AP to FA Interface (Migrate Asset data to FAUPAS from FAUPPA)
Associated Numeric Values
1: Minimum FA Item Amount to be considered an Asset (optional).
2: Maximum FA Item Amount to be considered an Asset (optional).
3-5: Reserved for future use.
Associated Codes
1: Enter either the four-character description of the Object Code (from GLUPGN) or an object Group Code (from GLUPGN).
2-5: Reserved for future use.
Associated Descriptions
1-3: List of Object Codes (or groups) that qualify as assets. Enter the criteria (like selection criteria, which is defined on GLUPOB/OS) to select the FA object codes. Separate multiple codes with a comma, or use a dash for a range. An example is 010,310,350-399. In this example, assuming the first Associated Description says "OBJ," which is GLUPGN's Object Code, 010, 310, and code in the range 350 through 399, are defined objects on GLUPOB (or GLUPOS) and will be considered FA object codes. Also note that if the Short Desc says "AUTO," line items on POUPPR with any of these object codes that fit within the threshold defined in the 1st and 2nd Associated Numeric Value will automatically be flagged as assets.
2: Do not use "ADD"
4-5: Reserved for future use.
PO to FA Interface (Migrate Asset data to FAUPAS from POUPRC)
Associated Numeric Values
1: Minimum FA Item Amount to be considered an Asset (optional).
2: Maximum FA Item Amount to be considered an Asset (optional).
3-5: Reserved for future use.
Associated Codes
1: Enter either the four-character description of the object code or the object part.
2: Enter "ADD" to generate a system-assigned Asset ID number when receiving entries are created and saved within the PO Receiving (POUPRC) page (optional). When "ADD" is entered here, the system will automatically "add" or assign the Asset ID and display a message that says "Item [item no.] has been recorded in Fixed Assets under Asset ID [FAID#].(PO124)." (Note that the Asset ID will be based on the seed defined in the NU common code with a Code Category/Value of SYNO/FAIDNUMS, per ledger). When not using this feature (field is blank), the Asset ID will need to be assigned manually or the following message will display, "Item marked as Fixed Asset. Asset ID is required. (FA46)."
3: LOC. Notifies the PO to FA interface to create an FASITE record within the PO Receiving (POUPRC) window, and will insert with asset into FAUPAS, LOC tab. Also see common code POFA/LOCDEFS for option to default location details.
4: A user-defined PO Association Code (typically FAWARR) that will be used for creating a warranty record for the asset at receiving time. The purchasing item association value will be placed into the warranty field of the FAWARR record for the asset, which is FAUPAS, Warranty tab. Note that the PO Association codes are created in NUUPCD with a Code Category / Value of POAS / XXXX where XXXX is the code for the specific association. Therefore, if type "FAWARR" in the 4th Assoc Code field, there needs to be a record in NUUPCD defined for POAS / FAWARR.
5: "POPRINT" - A client-specific option that requires customization of the Fixed Asset Module. Contact BusinessPLUS for details.
Associated Descriptions
1-3: List of Object Codes (or groups) that qualify as assets. Enter the criteria (like selection criteria) to select the FA object codes. Separate multiple codes with a comma, or use a dash for a range. An example is 010,310,350-399. In this example, assuming the first Associated Code says "OBJ," object codes 010, 310, and any object code in the range 350 through 399, are considered FA object codes. Also note that if the Short Desc says "AUTO," line items on POUPPR with any of these object codes that fit within the threshold defined in the 1st and 2nd Associated Numeric Value will automatically be flagged as assets.
4: "Y" to require the location and an asset id if the asset flag on the item is "Y." The Location must be defined within the FA Code Values (FAUPCD) page.
5: Client specific customization.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.