# Presentation: 125868

## Lesson 4: Fleet Transactions 

**Notes:**
  Summarize / Paraphrase Course Description Paragraph In Student Outline. 
  Note:  This Lesson Is Best Presented Using Dual Projectors; One for This PowerPoint Presentation, and a Second for Showing the PCMS Application.

  If the Classroom Does Not Have Dual Projectors/Screens, the Instructor Can Switch Back & Forth Between PCMS and PowerPoint.

  If the Instructor Is Uncomfortable Switching, Pick Most Suitable Option for Situation 

## Training Objectives

**At the conclusion of this lesson, PCMS LFPC’s and AFHC’s will be able to: **** **
* **Query, view, and dispute transactions. *

**Notes:**
  Ask Students To ‘Take A Moment To Review The Training Objectives For This Class.’ 
  Do Not Read Them To The Students.

## Overview - Main Window 

**Notes:**
  Orient Class to Graphical User Interface. 
  Work Top-to-Bottom, Left-to-Right. 
  Specific Field Descriptions Are Covered in Subsequent Slides.

## Main Window (Cont.)

**Main Window (Cont.)**

| Field Name | Description | Query? |
| --- | --- | --- |
| Query by Date | Check box to Query by date range.  | No |
| From Date | Enter the start date (in the format mm-dd-yyyy).  | Yes |
| To Date | Enter the end date (in the format mm-dd-yyyy).  | Yes |
| Sort Order | Select Ascending or Descending order of the Purchase Date, to specify how the transactions should be sorted.  | Yes |

**Notes:**
  Review Field Names and Descriptions Listed in Table. 
  Refer to Location of Fields on Main Screen Graphic.

## Main Window (Cont.)

**Main Window (Cont.)**

| Field Name | Description | Query? |
| --- | --- | --- |
| Tag\Equipment No | The tag/equipment number as it appears on the fleet credit card.  There is a list available to select a value from. | Yes |
| Voyager\Aviation No | The Fleet Card Voyager/Aviation account number.  There is a list available to select a value from. | Yes |

**Notes:**
  Review Field Names and Descriptions Listed in Table. 
  Refer to Location of Fields on Main Screen Graphic.

## Main Window (Cont.)

**Main Window (Cont.)**

| Field Name | Description | Query? |
| --- | --- | --- |
| Action Code         | Last action requested for the record. | Yes |
| Merchant Name  | The name of the merchant where the transaction took place.  | Yes |
| Ref No | The number assigned to the transaction by the input source.  | Yes |
| Purchase Date  | The date the purchase was made.  | Yes |

**Notes:**
 Review Field Name and Description Listed in Table. 
  Refer to Location of Fields on Main Screen Graphic.

## Main Window (Cont.)

**Main Window (Cont.)**

| Field Name | Description | Query? |
| --- | --- | --- |
| Agency Code  | The agency code that the purchase is to be charged against.   | No |
| Acctg Station  | The station code (region and unit) that the purchase is to be charged against.   | No |
| Acctg Class Code | The accounting code against which this portion of the transaction is charged.   | No |

**Notes:**
 Review Field Names and Descriptions Listed in Table. 
  Refer to Location of Fields on Main Screen Graphic.

## Main Window (Cont.)

**Main Window (Cont.)**

| Field Name | Description | Query? |
| --- | --- | --- |
| Treas Symbol | Treasury Symbol Description | No |
| Object Class  | The BOCC.  This code defines the nature of the services or goods being obligated.  | No |
| Distribution Amount | The percentage of this account to be applied to the transaction amount.  | No |

**Notes:**
 Review Field Names and Descriptions Listed in Table. 
  Refer to Location of Fields on Main Screen Graphic.

## Querying Transactions

- Query all their transactions OR specific transactions.
- Query by date range.
- Combine date range and specific transaction queries.

**Notes:**
  Slide Is Self Explanatory. 
  Touch on Each of the Points on the Slide, and Expand on Those As Necessary.

## Querying All Transactions

- Click **Find** on the Command Bar.
- Transaction records will appear in the middle section of the screen.
- Use scroll bar to navigate between transactions.

**Notes:**
  Slide Is Self Explanatory. 
  Touch on Each of the Points on the Slide, and Expand on Those As Necessary.

## Querying Specific Transactions

- Click **Find** on the command bar.
- Position the cursor in any field in the Fleet Transactions area and enter a value.  Click **Find**.
- The query results will appear.

- Range operators such as < or >, and wildcards such as %, can be used in queries.
- Lists are available for the “Tag\Equipment No’ and “Voyager\Aviation No” fields.

**Notes:**
  Slide Is Self Explanatory. 
  Touch on Each of the Points on the Slide, and Expand on Those As Necessary.

 Point out that a range of operators such as < or >, and wildcards such as %, can be used in queries; 

## Querying by Date Range

- Click **Find **on the command bar twice.
- Click the **Query By Date** check box.
- Enter dates in the **From Date** and **To Date** fields and select  the **Sort Order** of the purchase date.
- Click **Query**.

**Notes:**
  Slide Is Self Explanatory. 
  Touch on Each of the Points on the Slide, and Expand on Those As Necessary.

 Point out that a date range query can be combined with a specific transaction search.

## Practical Exercise 

- Query all transactions accounts, then query a specific Tag\Equipment number from the list available.
- Execute a specific query to find all transactions with an Action Code of “D” (Disputed).
- Query transactions greater than $50.00.
- Query a specific Merchant name and view a list of transactions associated to various vehicles\equipment.  E.g. Russell or Spectrum.

**Notes:**
  This Practical Exercise Can Be Conducted as an Individual or Instructor-Led Exercise. 
  Ensure Every Student Successfully Completes This Exercise Before Proceeding.

## View Transaction Details

**View Transaction Details**

- To view details of a specific transaction, place the cursor on a particular transaction line in the Card Transaction section of the screen and click **Trans Detail**.

**Notes:**
  Slide Is Self Explanatory. 

## Transaction Details

- The Transaction Details screen appears detailing the transaction you selected.
- Click **Transactions** to return to the transactions window.

**Notes:**
  Slide Is Self Explanatory. 

## Practical Exercise 

- Query all transactions.
- View the first transaction in the list.
- Return to the transactions screen.

**Notes:**
  This Practical Exercise Can Be Conducted as an Individual or Instructor-Led Exercise. 
  Ensure Every Student Successfully Completes This Exercise Before Proceeding.

## Disputes 

- When Should a Transaction Dispute Be Filed?
- When the invoice amount of goods\services received is not in keeping with what the Fleet card holder purchased.
- Transactions to investigate are:  if there are duplicate transactions on the same day, or if the vehicle does not use the type of fuel purchased.
- Cardholders have 60 days following Purchase Date to dispute a transaction.

**Notes:**
  Introduce the Topic of Disputes. 
  Cover Each Point on Slide. 
  More Detail on Disputes in Subsequent Slides.

## Disputing a Transaction  

- From the Fleet Transactions screen click **Dispute** next to the specific transaction you wish to dispute.

**Notes:**
  Cover Each Point on Slide. 
  More Detail on Disputes in Subsequent Slides.

## Disputing a Transaction (cont.) 

- The Transaction Dispute window opens.
- Certain fields are automatically populated with data from the transaction you are disputing.  These cannot be edited.

**Notes:**
  Orient Class to the Transaction Disputes Screen.
Review the fields that are populated by the transaction and can not be edited:
  Tag\Equipment No
  Voyager\Aviation No
  Visa Account No
  Merchant Name
  Merchant City
  Reference Number 

## Disputing a Transaction (cont.)

| Field | Description |
| --- | --- |
| Amount | The amount of the transaction.  |
| Dispute Date  | This field defaults to the current date.  Update it to reflect the actual date the dispute was initiated.  |
| Merchant Contact Date | Enter the date the merchant was contacted.  |
| Resolved Date | Will be entered when the dispute has been resolved.  |
| Dispute Code  | Enter the appropriate dispute code.  A list of values is available for this field.  |
| Short Desc  | Provides a brief description of the dispute.  This field is automatically populated when the Dispute Code is selected.  |
| Long Desc | Provides a detailed description of the dispute.  This field is automatically populated when the Dispute is selected. |
| Comments  | Available for additional comments |

**Editable Fields**** **

**Notes:**
  Review Field Names and Descriptions Listed in Table. 
  Refer to Location of Fields on Dispute Maintenance Screen Graphic.

## Disputing a Transaction (cont.) 

- Click **Save** on the command bar to save the dispute details.
- Click **Fleet Trans** to return to the Fleet Transaction window.

**Notes:**
  Orient Class to the Transaction Disputes Screen.

## Resolving Disputes 

- To Resolve a dispute, query the specific transaction and enter the Dispute window.

**Notes:**
  Revisit the Business Process of Resolving Disputes, and Tie into Using the Dispute Maintenance Screen to Perform Task. 
  More Detail in Following Slides.

## Resolving Disputes 

- Enter date in **Date Resolved** field.
- Update the **Comments** field.
- Click **Save** on the Command Bar.
- Click **Fleet Trans** to return to the Fleet Transactions screen.
- If the dispute is resolved in the LFPC’s favor, a credit will be issued by the Merchant.  If the dispute is resolved in the Merchant’s favor, no further action will be taken.

**Notes:**
  Cover Each Point on Slide. 
  Refer to Screen Graphic When Referring to Specific Data Entry Fields.

## Transaction Credits & Debits

- A transaction must be paid before it can be disputed.
- After payment has been made, the Description Field of the transaction will display the message ***Accepted by FFIS***.
- If an LFPC disputes a transaction, the Bank issues a temporary credit to equipment account while reviewing the dispute.

**Notes:**
  Cover Each Point Shown on Slide.

## Transaction Credits & Debits

-  **If the Dispute Is Found in the LFPC’s Favor:**
- A *Transaction Credit* will be issued by the Merchant.
- This transaction will display the Merchant name in the **Merchant Name** field and will have a minus ( - ) sign in front of the transaction amount.
- The Bank will then issue a *Retail Debit* in PCMS with the words ***Retail Debit Adjustment*** in the **Merchant Name **field.

**Notes:**
  Cover Each Point Shown on Slide.

## Transaction Credits & Debits

-  **If the Dispute Is Found in the Merchant’s Favor:**
- The Bank will issue a *Retail Debit* to offset the temporary credit.
- A Credit from the merchant will not be generated.  The original charge to the equipment account will stand.
- The LFPC is not informed by the bank when a dispute is found in the merchant’s favor.

**Notes:**
  Cover Each Point Shown on Slide.

## Practical Exercise 

- Query all transactions.
- Select a transaction and place it in a Disputed state;

**Notes:**
  This Practical Exercise Can Be Conducted as an Individual or Instructor-Led Exercise. 
  Ensure Every Student Successfully Completes This Exercise Before Proceeding.

## Summary and Review

- How do you query a specific transaction that occurred in a particular month?
- How do you query transactions valued greater than $200?
- What is the process for disputing a transaction?
- What is the process for resolving a disputed transaction?

**Notes:**
  Cover Review Questions. 
  Ensure There Are No Other Questions About Accessing And Navigating In The PCMS Application.

## Intro

**Lesson 5 - *****Messages***

**Notes:**
 BRIEFLY SUMMARIZE INFORMATION CONTAINED IN LESSON PLAN DESCRIPTION OF STUDENT LESSON PLAN.

## Training Objectives

- At the conclusion of this Lesson, you will be able to:
- Respond to user messages, statistical samples and system errors.

**Notes:**
  GIVE STUDENTS A MINUTE TO REVIEW THE LESSON’S TRAINING OBJECTIVES. 
  DO NOT READ THEM TO STUDENTS

## Bulletin Board

- Located in the Center of the Main Menu
- Provides updates about PCMS.
- System Upgrades and Downtime
- Notification of Specific System Problems
- PSD is responsible for the posting of all messages to the Bulletin Board

**Notes:**
 REMIND STUDENTS TO CHECK BULLETIN BOARD REGULARLY FOR IMPORTANT INFORMATION. 

## System Edits

- If data is entered into PCMS incorrectly or functionality is not allowed, the system will generate an error message known as a system edit.
- Appears in a Dialog Box.
- Provides information that will help you determine how to proceed.

**Notes:**
 STATE “SYSTEM EDITS ARE MORE COMMONLY KNOWN AS ERROR MESSAGES.” 
 REVIEW EACH OF THE BULLETS ON THIS SLIDE. 

 Hint:  To generate this error message to demonstrate to students:
 From Fleet Card Set up screen query all records
 Hit the “Copy Rec” button on the command bar

## System Edits (Cont.)

- Click **OK** to close the error message.
- Ensure the data has been entered correctly.

**Notes:**
  REVIEW EACH BULLET ON THIS SLIDE. 

## User Messages - General

- An Oversight Tool That Monitors PCMS Transactions.
- Assists LFPC’s in their oversight role of maintaining Fleet Card accounts and purchases
- The LFPC Is Expected to Routinely Review Fleet Transactions.

**Notes:**
  REVIEW EACH OF THE BULLETS ON THIS SLIDE. 

## User Messages Screen Overview 

- LFPCs view messages regarding fleet transactions for their designated  vehicles\equipment accounts.

**Notes:**
 REVIEW EACH OF THE BULLETS ON THIS SLIDE. 

 REVIEW FIELDS ON THIS SCREEN.

## User Message Details

- Part of an effort to identify possible card misuse or fraud.
- The LFPC should review the transaction and investigate and determine whether the card was used inappropriately.
- The LFPC may request the Fleet card user’s assistance during the review process.

**	****User messages are listed below:**

| Invalid SIC Code.  |
| --- |
| Profile Accounting changed more than twice a month.  |
| Purchase made on holiday.  |
| Disputed transaction not resolved within 45 days of dispute date.  |
| Invalid product code.  |
| Card has been reported lost or stolen 3 or more times.  |
| Tag Number xxxxxxxx is not in PROP.  Please enter Tag Number into PROP.  |
| This transaction has been selected for statistical sampling.  |
| Charges to aircraft for fuel other than product codes 25 and 27 which are AV gas and Jet Fuel for an aircraft card.  |

**Notes:**
 Discuss User Message details.

 Make sure students understand why they are receiving them and why it is important they respond. 

## Querying User Messages 

- Query All Messages for all of the LFPC.
-                         OR
- Query Specific Messages.

**Notes:**
 REVIEW STEPS TO PERFORM EACH TYPE OF QUERY.

 USE SCROLL BAR TO NAVIGATE.

 “TAG\EQUIPMENT NUMBER” FIELD HAS A LIST AVAILABLE.  

## Reading and Responding to Messages 

- Click **View Transaction** to view transaction details

**Notes:**
Screen is self explanatory.

## Card Transaction Screen 

**Card Transaction Screen **

- The Card Transactions window opens.
- Use the scroll bar to view more information.
- Place the cursor in the line of the specific transaction and click **Trans Detail**.

**Notes:**
 LFPC reviews transactions.

 Note:  To view transaction details place the cursor in the line of the specific transaction, in the “Card Transactions” area of the screen.  Hit the “Trans Details” button. 

## Transaction Details 

- Review transaction details.
- Click **Transactions** to return to the Card Transaction window.

**Notes:**
 LFPC reviews transaction details.

Contacts Fleet card user and AFHC for assistance if necessary.

Hit the “Transactions” button to return to the Card Transactions screen.  Then go to Action\exit to Return to the User messages screen.

## Close User Messages 

- Change message status to ***Read***.
- Add Comments.
- Be sure to save.

**Notes:**
 Review how to close a User message.

## Practical Exercise 

**Query your user messages.**** **** **
**Select a Tag\Equipment number.**** **
**Read User Messages that Vehicle\Equipment. **
**View the transaction details.**** **
**Add comments to the user message.**** **
**Change the status from ‘Unread’ to ‘Read’.**** **** **
**Save User Message.**
**Exit user message screen.**

**Notes:**
  ENSURE EACH STUDENT SUCCESSFULLY COMPLETES EACH ELEMENT OF THIS PRACTICAL EXERCISE.

## Statistical Sampling 

- Complete form for audit purposes.
- You MUST enter a comment!

**Notes:**
 Explain what a Statistical Sample is.

 Review screen and fields.

 Review how to respond to a Statistical Sample.

## Summary & Review

- You Receive a System Edit:
- What is the Likely Cause of the Problem?
- What Steps Do You Need to Take to Resolve It?
- How Does PSD Distribute System Information, Such As System Upgrades, to the LFPC’s?
- After Reading a User Message How Do You Ensure That It Does Not Show in the List Again?
- Why Will an LFPC Receive a User Message?

**Notes:**
REVIEW & SUMMARIZE LESSON BASED ON TRAINING OBJECTIVES AS RE-STATED BELOW: 
Respond to user messages, statistical samples and system errors. 

## Summary & Review (cont.)

- How Frequently Should You Check Your Messages?
- What is the purpose of a Statistical Sample?

**Notes:**
REVIEW & SUMMARIZE LESSON BASED ON TRAINING OBJECTIVES AS RE-STATED BELOW: 
Respond to user messages, statistical samples and system errors. 

## Lesson 6 – Fleet Card Setup

**Notes:**
  SUMMARIZE / PARAPHRASE COURSE DESCRIPTION PARAGRAPH IN STUDENT OUTLINE.

## Training Objectives

- At the conclusion of this lesson, PCMS LFPC’s and AFHC’s will be able to:
*Create, maintain, and query Fleet card accounts in FAMS;*
*Delete, and replace Fleet cards; *

**Notes:**
  ASK STUDENTS TO ‘TAKE A MOMENT TO REVIEW THE TRAINING OBJECTIVE FOR THIS CLASS.’ 
  DO NOT READ TO STUDENTS.

## Fleet Card Setup - Workflow

- LFPC sets up Fleet card accounts for vehicles and equipment, establish specific vehicle\equipment profile information, and replace or delete Fleet cards.

**Notes:**
  TOUCH BRIEFLY ON EACH POINT 

## Screen Overview

**Notes:**
  Review Fleet Card Setup screen.

  Discuss each field.  Provide examples of values they would enter in fields and identify fields that have lists.

  Card info and other three sub-screens will be discussed in subsequent slides.

## Screen Overview (cont.)

- CARD INFO - Enter Card information
- EQUIP INFO – Enter equipment details
- LIMIT INFO – Enter spending\usage limits
- DRIVER INFO – Not currently used by USDA.

**Notes:**
  Review each of the four screens and their fields.

## Query Fleet Records

- Query ALL records
- Click **Find** twice
- Use scroll bar to Navigate records
- OR
- Query Specific records
- Click **Find**
- Enter value in field and click **Find**
- Use scroll bar to navigate

**Notes:**
  Discuss each type of query.

  Demonstrate queries to the class.

  Mention available lists for fields.

## Practical Exercise 

- Query all vehicle\equipment records attached to the LFPC UserID you logged on with.
- Query all records that have card plastic type value of “S”.
- Query all records that have an “Equipment State” of California (CA) or Arizona (AZ).

**Notes:**
  This Practical Exercise Can Be Conducted as an Individual or Instructor-Led Exercise. 
  Ensure Every Student Successfully Completes This Exercise Before Proceeding.

## Fleet Card Setup 

- Enter the User ID in the “LFPC User ID” field.
- Enter the account details:
- Tag\Equipment Number
- Cardholder’s hierarchy (e.g. program Code, agency, unit)

**Notes:**
  Walk the class through setting up a Fleet Card account.  

  Provide examples of values to enter in the fields.

  Demonstrate to the class.
  Make students aware that if an incorrect Tag Number is sent to the Bank they can not change the record.  A new Tag Number will have to be assigned to the vehicle and a new account will need to be created.

## Fleet Card Setup (cont.) 

- Enter the setup\maintenance details
- Card INFO (e.g. Type of Plastic, Type of Card)
- Equip INFO (e.g. Fuel and maintenance, Odometer Indicator)
- Limit INFO (e.g. Cost\Fuel Trans Limit, Daily Trans Limit)

**Notes:**
  Walk the class through setting up a Fleet Card account.  

  Provide examples of values to enter in the fields.

  Demonstrate to the class.

## Fleet Card Setup (cont.) 

- Enter the Profile Accounting details
- Accounting entered during Fleet Card Setup is the default accounting for the Fleet Card
- Profile Accounting can be updated through the Profile Accounting screen

**Notes:**
  Walk the class through setting up a Fleet Card account.  

  Provide examples of values to enter in the fields.

  Demonstrate to the class.

## Fleet Card Setup (cont.) 

- Save the record by clicking **Save **on the command bar
- After the data is downloaded to the Bank, the **Date sent to the Bank** field is populated.
- A record can only be removed if it has not yet been sent to the Bank.  Click **Remove** then **Save.**
- Accounting can only be changed if the record has not yet been sent to the Bank.

**Notes:**
  Walk the class through setting up a Fleet Card account.  

  Provide examples of values to enter in the fields.

  Demonstrate to the class.

  Stress to students that they should check the Tag Number is correct before hitting “Save”.

## Copying Records 

- Enter initial record and save
- Click Record on the menu bar and select **Copy Record**
- Change all unique values in fields
- Save new record
- Repeat process to quickly create similar records

**Notes:**
  Walk the class through copying a Fleet Card record.  

  Provide examples of values fields that would have unique values:  e.g. Tag\Equipment Number or Profile Accounting.

  Demonstrate to the class.

## Modifying Accounts 

- Query a Fleet Card account
- Modifications can only be made if the following fields have values entered:
- Sent to the Bank
- Returned Fm Bank
- Save record

**Notes:**
  Walk the class through modification steps.  

## Modifying Accounts (cont.)

**Guidelines to modifying Accounts:**
- Prior to record being sent to Bank, all fields in Fleet Card Setup can be modified:
***Last Action Code*** = ***A*** and ***Date Sent To Bank*** is blank
- After record has been sent to Bank no modifications can be made until it returns from Bank:
***Last Action Code*** = ***A***, ***M***, ***T*** or ***R*** and ***Date Sent To Bank*** field is **NOT **blank, but ***Date Returned From Bank*** is blank
- After record has returned from Bank, most fields in Fleet Card Setup can be modified:
***Last Action Code*** = ***A***, ***M***, ***T*** or ***R*** and ***Date Sent To Bank*** and ***Date Returned Fm Bank*** are **NOT **blank

**Notes:**
  Review guidelines to modifying accounts (continued on next screen).  

## Modifying Accounts (cont.)

**Guidelines to modifying Accounts:**
- Updates to Profile Accounting can be done through Fleet Card Setup only if it is a new Fleet Card record and the record has not yet been sent to the Bank
- New cards will only be issued when information in the magnetic strip or information embossed upon the card changes

**Notes:**
  Review guidelines to modifying accounts.

## Practical Exercise 

**Create a new Fleet Card record using the following information: **
**Tag\Equipment Number: A11374 **
**Cost Limits:  Fuel = $100.00, Daily trans = 03, Maint Trans = $500, Gallon limit = 40, Gallon Trans Limit = $50 **
**Card is to be used by a Vehicle, for fuel and maintenance.**
**Card should be a standard plastic.**
**Equipment City: Rockville.**
**Equipment State: MD**
**Equipment Zip Code: 20850**
**Codes: Program 448687 \ Dept 12 \ Agency 99 \ Region 01 \ Unit 02 \ Sub Unit 00000**
**Station: 0110**
**Accounting code: 7010101915**
**Distribution % = 100 **

**Notes:**
  ENSURE EACH STUDENT SUCCESSFULLY COMPLETES EACH ELEMENT OF THIS PRACTICAL EXERCISE.

## Practical Exercise 

**Copy the new Fleet Card record and create a second record using the following unique field values:**
**Tag\Equipment Number: A287622 **
**Cost Limits:  Fuel = $100.00, Daily trans = 03, Maint Trans = $500, Gallon limit = 40, Gallon Trans Limit = $50 **
**Card is to be used by a Vehicle, for fuel and maintenance.**
**Card should be a standard plastic.**
**Equipment City: Beltsville.**
**Equipment State: MD**
**Equipment Zip Code: 20705**
**Codes: Program 448687 \ Dept 12 \ Agency 99 \ Region 01 \ Unit 02 \ Sub Unit 00000**
**Station: 0110**
**Accounting code: 7010101915**
**Distribution % = 100 **

**Notes:**
  ENSURE EACH STUDENT SUCCESSFULLY COMPLETES EACH ELEMENT OF THIS PRACTICAL EXERCISE.

## Lost and Stolen Fleet Cards 

**Notes:**
  Walk through the diagram and discuss each steps in more detail.  Provide examples.  

  Discuss LFPC responsibilities.

  Discuss Action codes.

## Replace \ Delete Cards

**  ****Check “Delete Card” OR “Replace Card”.**
-   **Save record to send request to the Bank.**

**Notes:**
   Discuss when a replacement card can be requested, and when a card should be deleted.

  Walk through the steps of querying the account and requesting a replacement card, OR deleting a card.

## Practical Exercise 

**Query the following record, and request a replacement card: **
**Tag\Equipment Number:  A010214**

**Query the following record, and delete the card:  **
**Tag\Equipment Number:  010210**

**Notes:**
  ENSURE EACH STUDENT SUCCESSFULLY COMPLETES EACH ELEMENT OF THIS PRACTICAL EXERCISE.

## Update an LFPC

-  Select ***Update LFPC*** from main menu.
-  Query an LFPC.
-  Edit fields and Save.

**Notes:**
   Discuss why LFPC would require updating.  Provide examples.

  Walk the class through the steps of updating an existing LFPC and a new LFPC.
  Expand on details of process.

## Summary and Review

**What are the main functions the LFPC performs using Fleet Card Setup? **** **
**What are the steps for an LFPC when setting up a new Fleet Card account? **** **
**What would prevent a new Fleet Card record from being modified in Fleet Card Setup? **
**If a Cardholder has a damaged purchase card how do they obtain a replacement? **

**Notes:**
  COVER REVIEW QUESTIONS. 
  ENSURE THERE ARE NO OTHER QUESTIONS ABOUT REPORTING.