Asset Management Integration Process

Transcription

1 Asset Management Integration Process User Guide June 6, 2013 V2

2 Asset Management Integration Process To jump to an area within the User Guide, click on the topic in the Table of Contents. Table of Contents INTRODUCTION... 2 SECTION 1: ASSET INTEGRATION PROCESS FLOW... 3 Overview... 3 ASSET INTEGRATION PROCESS FLOW...4 Topic Overview... 4 SECTION 2: REVIEWING AM PRE-INTERFACE TABLES Overview ACCESSING THE PRE-INTERFACE LOADER TABLES THE RECORD IS A NON-ASSET Topic Overview NON OPEN PERIOD Topic Overview DUPLICATE TAG NUMBER Topic Overview DUPLICATE ASSET ID Topic Overview SECTION 3: REVIEWING ERRORS IN THE TRANSACTION LOADER TABLES Overview ACCESSING THE TRANSACTION LOADER TABLES LESSON SUMMARY Page 1

3 Introduction This reference guide explains the changes to the SWIFT asset integration process effective June 10, The sequence of processes that integrate asset data from purchasing and payables into asset management has not changed, however, the timing has been structured to create an opportunity to review assets and correct or flag errors. Users will be able to block items from continuing through the integration process if the item is not supposed to be an asset. Users will also be able to change or add certain fields, e.g., Location and Custodian. There are some fields that cannot be edited in the loader tables; users will be able to identify those assets that will require updates in the asset management pages if these fields are incorrect. This document contains three sections: Asset Integration Process Flow Explanation of the process flow to integrate assets from the purchasing module into Asset Management. Description of how each step along the way functions. Reviewing the Pre-Interface Loader Tables How to review the assets placed on the pre-interface loader tables as part of the integration process. What to do if an item should not be there, and how to correct errors on items that should. Errors in the Transaction Loader Process What happens when an asset causes an error in the Transaction Loader process, and how do you fix it? Page 2

4 Section 1: Asset Integration Process Flow Overview Most assets enter the Asset Management module in SWIFT via integration from the Purchasing/Payables or Project Costing modules. This lesson covers the integration process related to items that come from Purchasing and Payables. Items that come from Project Costing are not affected by the integration processes and are not reviewed in the same way as items from Purchasing and Payables. Items that are added manually via Express Add are also not affected by the integration process. After completing this lesson, you should be able to: Explain how assets integrate into AM from the Purchasing and Accounts Payable modules Page 3

5 Asset Integration Process Flow Topic Overview The vast majority of assets enter SWIFT via integration with the Purchasing and Accounts Payable modules. In certain cases, such as a donated item, you may need to enter asset information directly into the Asset Management module. Some errors in the integration process also require manual entry of the asset record. This diagram shows the overall process flow for assets entering Asset Management via integration. The Transaction Loader process, at the bottom right, is the mechanism within SWIFT that creates asset records. The rest of this section explains each step in the integration process. Page 4

6 Asset Purchasing Asset purchasing is the first input of data into the integration process. It is very important that the correct information is entered on the purchase order so that correct asset information passes through to the integration process. The buyer uses an Item ID or an Item Category Code to identify the item to be purchased. If the Item ID or Item Category Code has a default Profile ID attached, the Profile ID passes through to the distribution line of the purchase order. The Profile ID identifies the item as an asset and establishes various defaults for the item in Asset Management. The Purchasing and Accounts Payable steps provide an opportunity to review the purchase and make corrections to the asset details before the integration process. For example, if the purchase record includes an asset Profile ID, but the purchased item is not an asset, you can remove the Profile ID from the purchase order before integration. Page 5

7 Asset Receiving The vendor sends the asset to the agency on the basis of the purchase order. The asset is then received and a PO receipt created in SWIFT. The purchase order must be received in order for SWIFT to create the complete asset record. This is the preferred method of creating the asset record. If the purchase order is not received, either by agency decision or error, it is an option to mark the PO as received when processing the payment voucher. In this case, SWIFT will create the asset record with only the financial information that comes from the payment voucher. You must add the physical information later after the Asset ID is created in AM. If the agency identifies an error when processing a PO receipt, such as an incorrect Profile ID, do not save the receipt. The adjustment should not be made on the PO receipt. The correction/adjustment should be made on the original purchase order. Once the receipt is processed, no corrections can be made. All corrections must be processed in the Pre- Interface Loader Table or in asset management after integration is completed. Page 6

8 Asset Vouchered Typically, payment vouchers are issued when the invoice is received. With a payment voucher, the state can then issue payment to the vendor. Payment vouchers include information from the requisition, purchase order, invoice and the PO receipt. SWIFT requires a PO receipt and payment voucher to properly create an asset record. Page 7

9 Integration to Pre-Interface Loader Tables (PRE_AM) Asset information is passed to the PRE_AM tables in two ways. Physical details are integrated from purchasing and financial details are integrated from payables. Both sets of data should be reviewed before being loaded to the AM Pre-Interface Loader Tables. Depending on when the PO receipt and payment voucher are processed, physical and financial data for a single asset may not be in the Pre-Interface Loader Tables at the same time. Integration from Purchasing 1. SWIFT runs the Receiver Interface Push process (PO_RECV_PUSH) every two hours, between 8 AM and the last instance at 2PM, to load the physical details of the asset record into the Pre-Interface Loader Tables. These details come from the purchase order and PO receipt records. Physical details include the Profile ID, tag number, serial ID, description, location, custodian, and manufacturer information. With the exception of the Profile ID, these values can be added or changed in the Pre-Interface Loader Tables to correct errors. If the Profile ID is incorrect, you must flag the asset and make the necessary change directly in the AM record after integration is completed. DO NOT make any changes on the purchase order or PO receipt. Note: If the record includes a Profile ID but the item is not an asset, you can change the status of the record to On Hold to prevent the record from moving forward in the integration process. Page 8

10 Integration from Payables 2. SWIFT runs the Load Assets process (INTFAPAM) as part of the nightly batch process to load the financial details of the asset record into the Loader Tables. These details come from the payment voucher record. Financial details include the cost, quantity, and chartfield values. These cannot be changed in the Pre-Interface Loader Tables. If you determine there is an error in these values, you must identify the asset and make changes directly in the AM record after integration is completed. Note: The Load Assets process is run at the end of the overnight batch process. This means that the financial records created in the Pre-Interface Loader Tables is available the next day for agency review. Any records in Pending status will be picked up the following night and moved further through the integration process to become asset records in AM. Page 9

11 Reviewing assets in the Pre-Interface Loader Tables SWIFT asset integration processes are structured with a delay between the time the data are moved onto the Pre-Interface Loader Tables and when the data are moved from the Pre-Interface Loader Tables through the rest of the integration process and into AM. This is deliberate to create a window for agencies to review the data before the assets end up in AM. As part of the review, agencies can correct errors in the physical data-except for the Profile ID, identify assets that need corrections to the financial data or the Profile ID, and prevent non-assets from moving forward in the process. The Load Assets process (INTFAPAM) runs in the nightly batch process, so agencies can review the financial side of the asset records any time during the following day. The PO Receiver Push Process runs throughout the day, but does not run after 2 PM. No new physical asset records will be placed in the Pre-Interface Loader Tables until the following day. Agencies have that window of opportunity between 2:30 PM and the end of the day to review those records. SWIFT will not run any additional process if there are records in Errored status in the Pre-Interface Loader Tables. Agencies must correct these errors before any further asset integration can occur. Page 10

12 Asset Management Payable/Purchasing Interface Process If there are no assets in Errored status in the AM Pre-Interface Loader tables, SWIFT next runs the Asset Management Payable/Purchasing Interface process (AMPS1000). This process retrieves payment voucher, PO receipt, and purchase order information into the Transaction Loader Tables. This process is run automatically in nightly batch processing. The process will not run if there are errored asset records in the Pre-Interface Loader tables, and no further asset processing can be done until those errors are cleared. The asset records derived from the AMPS1000 process are placed in Transaction Loader Tables separated into the physical and financial components of the record. No agency action is required at this step, unless there are errors as a result of the next process, Transaction Loader. Page 11

13 Transaction Loader Tables The AM Payable/Purchasing Interface process gathers asset information from the payment vouchers and PO receipts sitting on the AM Pre-Interface Loader Tables and moves that information to the Transaction Loader Tables. The information is all the same, although it is structured and presented differently. Any changes made on the Pre-Interface Tables, such as adding a tag number or changing the location, will be reflected on the Transaction Loader Tables. Asset information resides on the Transaction Loader Tables in Pending status briefly before the Transaction Loader process picks it up and moves it through to create the asset record in Asset Management. There is no need to review these tables as long as there are no errors. Once the asset record is created in AM, the records on the Transaction Loader Tables change to Loaded status. If there are asset records in Errored status, you must go in and correct the error on the table. As with the Pre- Interface Loader Tables, no additional asset integration processing can occur if there are assets in error on the Transaction Loader Tables. Page 12

14 Transaction Loader Process The last step in moving assets from Purchasing and Accounts Payable to Asset Management is to run the Transaction Loader process (AMIF1000). This process moves lines in Pending status from the Transaction Loader tables to the Asset Management tables. SWIFT runs this process in nightly batch processing. Page 13

15 Agency Touchpoints with Asset Data Agencies have three opportunities to touch the asset record and manage the data during the course of asset integration: Purchasing and Payables Correct information on the purchase order, PO receipt, and payment voucher will result in fewer errors in the integration process. Check that the purchase order contains the correct Profile ID on the distribution line. Remove the defaulted Profile ID if the item is not an asset. On the PO receipt and payment voucher, leave the Accounting Date as the current date. Do not backdate it-if necessary, you can change the In Service date later in AM. If you add a tag number or manual Asset ID, be sure it is not a duplicate. Pre-Interface Loader Tables You can change or add all of the physical information except the Profile ID. You can review the financial information and identify any assets to be edited in AM. You can fix any assets in Errored status. You can prevent non-assets from moving further through the process. Transaction Loader Tables Under normal circumstances, if all asset data are correct, you will not need to access and edit assets in these tables. You must access and edit these records if there are Errored assets. Page 14

16 Asset Management Tables The process to move assets from purchasing into asset management is now complete. You can now view the asset in the Asset Management tables using the Basic Add pages, which show both the physical and financial information. The asset record includes acquisition information-the Purchase Order ID, PO Receipt ID, and Voucher ID, provided that both the AP and PO files loaded. You can view assets on the Define Asset Operational Information page, which shows just the physical information. Any changes to the asset record must now be made directly in Asset Management. Do not change any of the source documents, such as the purchase order or PO receipt. You may have noted certain errors, such as an incorrect Profile ID or chartfield value, when reviewing the asset information during the integration process. Those corrections can now be made in Asset Management, generally by using the Cost Adjust/Transfer Asset page. Page 15

17 Section 2: Reviewing AM Pre-Interface Tables Overview The first stage of the asset integration process is moving asset data onto the AM Pre-Interface Loader Tables from the Purchasing and Payables modules. The Receiver Interface Push process (PO_RECV_PUSH) moves physical data from Purchasing onto the tables, and the Load Assets process (INTFAPAM) gathers financial data from Payables. The integration process is structured so that agencies have an opportunity to review the asset records on the AM Pre-Interface Loader Tables before they move forward in the integration process. This section of the reference guide discusses some of the factors to review and how to make corrections. SWIFT sends a notification by when the Transaction Loader process generates an errored record for your Business Unit. There is also a query you can run to search for errored records: M_AM_PREINTFC_CHECK Page 16

18 There are several reasons you might need to correct or flag an asset record in the Pre-Interface Loader Tables. This reference guide presents the more common situations; however, if you encounter an issue that is not explained here, please contact the help desk for guidance on how to resolve the issue. Remember that the asset integration process will not move forward if there are any assets in Errored status in these tables. The record is a non-asset In some cases, the purchase order includes an asset Profile ID, but the item is not an asset. This record should not move further through the integration process. Note: In this example, the asset record would be in Pending status, not Errored. SWIFT thinks it is valid; you know it s not and need to change the status to On Hold. Non-open period If the Accounting Date in the asset record falls outside the current period, the record will error in the Pre-Interface Loader Tables. Duplicate Tag Number The tag number must be unique within the Business Unit. SWIFT checks the record against existing assets and errors any new records with a duplicate tag number. Duplicate Asset ID Generally, SWIFT auto-assigns the Asset ID. Some agencies assign the Asset ID manually. Just like the tag number, the Asset ID must be unique within the Business Unit. SWIFT validates new records against existing Asset IDs and errors any duplicates. After completing this lesson, you should be able to: Navigate to the AM Pre-Interface Loader Tables Locate specific asset records Review and correct assets that are in error Prevent non-assets from moving further through the integration process Page 17

19 Accessing the Pre-Interface Loader Tables Navigation: Asset Management>Send/Receive Information>Preview AP/PO Information Enter the AM Business Unit and any other variables needed. You can select a Load Status from the dropdown list to filter the search. For example, to find assets with errors, select Errored as the Load Status. Assets in Pending status are new and will be picked up in the next process if no changes are made. Use this status to search for records with a Profile ID that are not assets. You can also search for records associated with a specific purchase order, PO receipt, or payment voucher. Page 18

20 The Record is a Non-Asset Topic Overview Agencies should have processes in place to review and validate the information entered on the purchase order to ensure the asset details are correct. SWIFT looks for PO lines with asset information, specifically the Profile ID. Many item category codes have a default asset Profile ID; however, in some cases the specific item referenced by that category code is not an asset. For example, the buyer might have used the item code (Automobiles or cars > Passenger) to purchase spark plugs. Those are supplies or parts and should not end up as assets in AM. Buyers should take care to enter the correct category code, account, and Profile ID (or delete the Profile ID). If the Profile ID is on the purchase order, SWIFT will pick it up in the PO_RECV_PUSH as well as the INTFAPAM process for the payment voucher, and create records on the Pre-Interface Loader Tables. As part of your review of the tables, you should look for these types of items and prevent them from moving further in the integration process. After completing this topic, you should be able to: Change the status of non-asset records in the Pre-Interface Loader Tables Page 19

21 To review assets in the Pre-Interface Tables that might need to be blocked from further integration, search for records using the Business Unit and the Load Status Pending. Remember that, to SWIFT, these records are valid. The category code defaulted an asset account and Profile ID. If no action is taken, the records will be picked up in the next step of the process and moved on to the AM tables as assets. Click the link in the search results to open the tables for that record. Page 20

22 The financial and physical details are on separate tabs within the same record. The Pre-AM Financial tab contains Load Status (A) and the financial details: B) Transaction Date and Accounting Date C) Chartfield Values D) Cost and Quantity Information All of the fields are locked for editing except the Trans Date and Accounting Date and the Load Status. It s not easy to determine whether this record should be an asset from this tab. Click the Pre-AM Physical tab to view the physical information. Page 21

23 The Pre-AM Physical tab contains the physical details including the Profile ID. You can tell from the description that this is not an asset. This page also provides the PO number and Receiver number. You can refer to these documents for more information about the item. Note that you cannot change the Profile ID. If it is incorrect, allow the item to move through the integration process and correct the Profile ID in AM. You ll be able to locate it there by searching for the asset using the PO number. You can change or add other physical information on this page, such as tag number, custodian, or location. Page 22

24 The asset record comes from Line 5 of the purchase order. The Distribution shows the asset information for the record on the Pre-Interface Loader Table. Page 23

25 Once you determine that the asset record is not an asset, you must prevent it from moving further through the asset integration process. Change the Load Status to On Hold and click Save. You can change the status on either tab. Assets that are On Hold will not be processed any further and will allow new asset records to be processed. On Hold records will simply be held on the tables. Page 24

26 Non Open Period Topic Overview SWIFT will only process asset records when the Accounting Date falls within the current open accounting period. If the Accounting Date is outside the current open period, SWIFT places the asset record in an Errored status. This is only one of several reasons an asset record might be errored. The following topics cover other examples. After completing this topic, you should be able to: Correct the Accounting Date and change the status of an asset in the AM Pre-Interface Loader Tables Page 25

27 Search for all assets within the Business Unit in Errored status and process each based on the reason for the error. Remember that SWIFT will not process any new asset records until all errors are cleared from this table. Click to open the first record from the search results. Page 26

28 In this example, this record is in error because the Accounting Date is outside the current period. Usually, this is because the Accounting Date was changed when the PO was received or when the payment voucher was created. This is often done in an effort to manage the date the asset went into service. However, when the date is outside the current period, SWIFT will not complete the asset integration process. Also, changing the Accounting Date has no effect on the In Service Date. Page 27

29 To correct this error, first change the load status to Pending. Then change the Accounting Date to a date that is in the current period. Often the Transaction Date will work, however, make sure that the Accounting Date entered is current. Click Save. SWIFT will then pick up this record and move it further through the integration process. Page 28

30 If you still need to back-date the in service date, access the asset once it is in Asset Management on the Basic Add page. On the General Information tab, change the Placement Date as needed. This will serve as the in service date for depreciation purposes. Page 29

31 Duplicate Tag Number Topic Overview The asset tag number must be unique within the Business Unit. If a tag is entered when the purchase order is received, that tag must be unique and assigned only to that item. SWIFT verifies this as part of the asset integration process. If the tag number is found on another asset within the Business Unit, SWIFT will not process the asset record any further through the integration process, and will set the load status to Errored. After completing this topic, you should be able to: Correct a duplicate tag error and change the status of an asset in the AM Pre-Interface Loader Tables Page 30

32 The tag number field is located on the Pre-AM Physical tab. The tag number, which usually comes from the PO receipt as a manually entered value, matches a tag number that already exists in this Business Unit. SWIFT has set the load status to Errored. Page 31

33 To correct this error, first change the load status to Pending. Search for an asset using the tag number to see what it is already assigned to. Sometimes it s hard to determine whether this new asset or the existing asset should have that tag number. There are several options for fixing the tag number: 1. Change the tag number n the existing asset 2. Change the tag number to the correct value in this field 3. Change the value in this field to a non-duplicate value This example uses the third option. The tag number value has been changed to a non-duplicate by adding a Z to the end. This will allow the asset to continue through the integration process. You can then correct the tag number in asset management. Changing the value in this way enables you to find this asset easily by searching for the tag number. It is not recommended to delete the tag number from this record because you would then need to locate the asset by searching a different value, such as the PO number. Click Save. SWIFT will then pick up this record and move it further through the integration process. Page 32

34 You can add or correct the tag number later in the AM record using the Define Asset Operational Info page. Page 33

35 Duplicate Asset ID Topic Overview This error is less common. There are two circumstances in which this error may occur: 1. Some agencies specify the Asset ID instead of accepting the NEXT value assigned by SWIFT. This is perfectly fine; however, the Asset ID, like the tag number, must be unique within the Business Unit. SWIFT checks existing Asset IDs and any record with a duplicate is placed in Errored status. 2. The agency is attempting to make a correction to the PO receipt or payment voucher after the asset record has already entered the integration process. SWIFT will not accept the new entry because the Asset ID already exists in the AM Pre-Interface Table. The error code and description will differ, but the solution for both causes of this error is the same. You will have to change the load status to On Hold to prevent the record from moving further through the integration process and then enter the asset record manually using the Express Add page in asset management. After completing this topic, you should be able to: Correct a duplicate Asset ID error and change the status of an asset in the AM Pre-Interface Loader Tables Page 34

36 The Asset ID field is located on the Pre-AM Physical tab. You can t tell just from this page why the Asset ID is in error, i.e., whether you are pushing new data onto an existing Asset ID that is already in the table, or you are using a manual ID that already exists in AM. To check, you can search for the Asset ID in AM on the Basic Add page and you can search for the Asset ID on the search page for the Pre-Interface Loader Tables. Page 35

37 To correct this error, first change the load status to On Hold. Click Save. SWIFT will ignore this record in future runs of the integration process. Page 36

38 Then, add the asset manually directly in asset management, bypassing the integration process entirely. Navigation: Asset Management>Asset Transactions>Owned Assets>Express Add The key for this step is the Asset ID you use for the manual asset. If the asset record was in error because the Asset ID already exists in AM, you will not be able to use it again and will see the error message shown here. You will need to select a new Asset ID or change the field to NEXT and let SWIFT assign the next available value. If the error was because of a duplicate record of the Asset ID within the Pre-Interface Tables only, you will be able to use that Asset ID here. The Asset ID exists in the Pre-Interface Tables, but not in the AM tables. In this example, the Asset ID entered already exists in AM. Unlike the tag number, the Asset ID cannot be changed. You would need to select a new Asset ID or enter NEXT and let SWIFT assign the value. Page 37

39 In this example, a new Asset ID has been used. Enter the complete details of the asset and click Save. Remember that Express Add requires only the financial details for the asset. You can make changes and add the physical details using the Define Asset Operational Info page. Page 38

40 Section 3: Reviewing Errors in the Transaction Loader Tables Overview The asset integration process is complete when SWIFT runs the Transaction Loader process and enters asset records in the asset management tables with an Asset ID. However, if there are any errors as a result of the Transaction Loader process, SWIFT halts the integration. The errored assets must be resolved before SWIFT can initiate any asset integration processes again. Page 39

41 Assets can cause an error in the Transaction Loader process for many of the same reasons as in the Pre- Interface Loader Tables. New reasons are in bold below. Non-open period Even if the Accounting Date was correct, i.e., within the current period, when SWIFT ran the initial integration processes, it is possible for the date to fall out of the current period, based on when the Transaction Loader process runs and when the period ends. Duplicate Tag Number If a tag number is entered in the Pre-Interface Loader Tables, SWIFT checks the existing tags as part of the Transaction Loader process. Duplicate tags will cause an error. Duplicate Asset ID Again, depending on the timing, a manually entered Asset ID that was previously unique may be a duplicate when the Transaction Loader process runs, and will cause an error. Invalid Chartfield Values During the Transaction Loader process, SWIFT validates the chartfield string and will error the asset record if the values are not valid. Duplicate Asset Records In previous training materials, agencies were advised to make corrections in the source documents, e.g., change the tag number, in the purchase order, PO receipt, or payment voucher and then process the record again. When SWIFT tries to process a record that has already gone through the system, it creates an error. Do not make corrections in the source documents. If there is an error, allow the initial record to complete the integration process and then make changes in AM. Or, place the record on hold to prevent further integration processing and then enter the asset manually directly in AM using Express Add. Page 40

42 All asset records that move through the Transaction Loader process end up on the Transaction Loader Tables. The only time you need to make corrections is when an asset record is in Errored status. You can review the existing asset records on these tables at any time to search for errored records. SWIFT sends a notification by when the Transaction Loader process generates an errored record for your Business Unit. There are also two queries you can run to search for errored records: M_AM_INTFCFIN_CHECK displays errors in the financial data M_AM_INTFCPHYA_CHECK displays errors in the physical data After completing this section, you should be able to: Determine when there are errors to be corrected Navigate to the Transaction Loader Tables Locate errored asset records Review and correct assets that are in error Page 41

43 Accessing the Transaction Loader Tables The AM Pre-Interface Tables present both the financial and physical information about the asset record on a single page, divided on two tabs. The Transaction Loader Tables split the financial and physical information on to two separate pages. Navigation: Asset Management>Send/Receive Information>Approve Financial Information>Review Navigation: Asset Management>Send/Receive Information>Approve Physical Information>Review-A The search screens are the same for both the financial and physical pages. Search by Business Unit and Load Status to filter the results and show only your errored asset records. Page 42

44 Although the search page is the same for both the financial and physical pages, the data pages are different. The Financial Information page contains the cost and chartfield details for the asset record. In many cases, the specific error is explained in the Error Message box at the bottom of the page. In this example, the error is a duplicate tag number, which is part of the physical information for the asset. You will need to navigate to that page to make the correction. Note that you can change the chartfield values on this page, where you could not on the Pre-Interface Table page. If the error here is an invalid chartfield string, you can make that correction here. You can also change the Asset ID if necessary, or change that field to NEXT to let SWIFT assign the next available value. After making the necessary correction, change the load status to Pending. Note: You must change the load status on both the financial and physical information pages, regardless of what the error is or where you corrected it. Be sure to change this page either before or after making the correction on the Physical Information page. Page 43

45 SWIFT makes it easy to navigate between the financial and physical pages by using the breadcrumb navigation at the top of the page. If you open the Review-A page directly using the breadcrumbs, SWIFT opens the Physical Information page for the same asset record and you don t have to search again. You can go back and forth between the financial and physical pages using the breadcrumbs. The Physical Information page contains the physical details, including the Profile ID, tag number, description, serial ID, and location. In this example, the tag number was a duplicate, so you can change that here. Note that you can change the Profile ID here where you could not on the Pre-Interface Table. You will only be able to do this if the record errors for another reason. After making the necessary correction, change the load status to Pending. Reminder: You must change the load status on both the financial and physical information pages, regardless of what the error is or where you corrected it. Go back and change the load status on the Financial Information page if you haven t already done so. Page 44

46 Lesson Summary Having completed this lesson, you should now be able to: Explain the Asset Integration Process to move asset records from Purchasing and Payables to Asset Management. Access and correct errors in the AM Pre-Interface Loader Tables Access and correct errors in the Transaction Loader Tables Page 45