POFA - CONTROL2
Integration of Asset Data
This common code tells the system how to determine the In-Service date, where to transfer the Product ID, and the minimum threshold for processing depreciation (via FADPRD/FADPDS). It also has a setting for use with the AP to FA migration setup where the code APOHPA is defined for use with the FA Potential Asset (FAUPPA) page.
Only the first ten characters of a product code will be transferred to the FA system.
Code Category: POFA
Code Value: CONTROL2
Short Description: Not required. Used to describe the common code.
Medium Description: Not required. Used to describe the common code.
Long Description: Not required. Used to describe the common code.
AP to FA Interface
Asset migrates to FAUPAS via FAUPPA after posting via APOHBTDS or APOHINVP
Associated Numeric Values
1-4: Reserved for future use.
5: Threshold for Depreciation. Tells the system a minimal dollar amount to allow an asset to depreciate.
Associated Codes
1: OLDEST, LATEST or blank.
OLDEST: Use the earliest receiving date and PO Item amount as the asset's default In-Service Date and Purchase Amount upon migration to the FAUPAS, Asset ID tab.
LATEST: Use the latest receiving date and PO Item amount used as the asset's default In-Service Date and Purchase Amount upon migration to the FAUPAS, Asset ID tab.
Blank: Defer the setting of the In-Service Date to POFA/CONTROL3 to make the Check Date and amount the In-Service Date and purchase amount.
2-4: Reserved for Future use.
5: APOHPA to bring payables identified as assets into the FA Potential Asset (FAUPPA) page for further handling.
Associated Descriptions
1-5: Reserved for future use.
PO to FA Interface
Asset migrates to FAUPAS via POUPRC
When the Item is received, the system can default in the Receive date as the In-Service Date. Associated Codes (1) and (3) are used for this purpose.
Associated Numeric Values
1-4: Reserved for future use.
5: Threshold for Depreciation. Tells the system a minimal dollar amount to allow an asset to depreciate.
Associated Codes
1: OLDEST or LATEST. Consider using a receiving date as the In-Service Date whenever an asset is created from POUPRC.
OLDEST: Use the earliest receiving date and PO Item amount as the asset's default In-Service Date and Purchase Amount upon migration to the FAUPAS, Asset ID tab.
LATEST: Use the latest receiving date and PO Item amount used as the asset's default In-Service Date and Purchase Amount upon migration to the FAUPAS, Asset ID tab.
2: Reserved for Future use.
3: PARCEL. Tells the system to put the Product code (from Purchase Item screen of POUPPR) into the Prod ID on FAUPAS, Asset ID tab, General Info tab (or Parcel field of Land Info tab).
4: Reserved for Future use.
5: [LOCATION]. Tells the system to put the default location code entered here into the location field on FAUPAS when POUTBC is run. (Code entered here is defined on FAUPCD). Note: Do not use "APOHPA" in this field as it will double the Asset IDs Purchase Price. APOHPA is only used when the PO General Information (POUPGN) page is not using the "Use PO to FA Interface"; no checkmark.
Associated Descriptions
1-5: Reserved for future use.