1. Introduction to General Fund Enterprise Business System (GFEBS)
U.S. ARMY SOLDIER SUPPORT INSTITUTE
NONCOMMISSIONED OFFICER ACADEMY
Show Slide #1: Introduction to General Fund Enterprise Business System (GFEBS)
Title: Introduction to General Fund Enterprise Business System (GFEBS)
References:
AR1-1 – Planning, Programming, Budgeting, and Execution System
DFAS-IN Regulation 37-1, Finance and Accounting Policy Implementation
DFAS-IN MANUAL FY, The Army Management Structure
GFEBS Performance Support Website (PSW)
Section I. Administrative Data
Academic Hours/Methods
02 hrs. / 30 min. DSL (small or large group discussion)
01 hrs. / 00 min. PE (Practical Exercise)
00 hrs. / 00 min. Test
00 hrs. / 00 min. Test Review
03 hrs. / 30 min. Total Hours
Section II. Introduction:
Method of Instruction: DSL - Discussion (large or small group)
Facilitator's to Learner Ratio: 1:25
Time of Instruction: 00 hrs. / 05 min.
Media: PowerPoint Presentation
Facilitator Material: Each primary facilitator should possess a lesson plan, evaluation sheet, scenario event list for exercises, and summary sheet containing the above noted references.
Learners Material: Learners should possess course handouts, access to all systems for exercises, summary sheet containing the above noted references portable laptop, and standard classroom supplies.
Note: "All required references and technical manuals will be provided by the local Command“
Motivator (Concrete Experience): Motivator: In today’s Army, we define ourselves as being the best trained, equipped and the best led Army that the United States has ever known. So to keep this image we as Financial Leaders and Managers have to become the best at financially supporting our Soldiers and being stewards of taxpayer dollars. Knowing this we have embraced Standard Financial Information System (SFIS) and the General Fund Enterprise Business System (GFEBS) in that it provides our Army decision makers with accurate, reliable, timely business and financial information to keep our War Fighters within their fiscal responsibilities. 1

2. Terminal Learning Objective
Action: Conduct Introduction to General Fund Enterprise Business System (GFEBS)
Conditions: FM Leaders in a classroom environment using doctrinal and administrative publications, personal experience, handouts, discussion and access to GFEBS.
Standard: With at least 80% accuracy learners must show proficiency with:
Communicate the background, purpose, and functions of the GFEBS program
Show Slide #3: Terminal Learning Objective
Facilitator’s Notes: Read/State the TLO
Action: Conduct Introduction to General Fund Enterprise Business System (GFEBS)
Conditions: FM Leaders in a classroom environment using doctrinal and administrative publications, personal experience, handouts, discussion and access to GFEBS.
Standards: With at least 80% accuracy learners must show proficiency with:
- Communicate the background, purpose, and functions of the GFEBS program
Safety Requirement: In a training environment, leaders must perform a risk assessment in accordance with DA PAM , Risk Management. Leaders will complete a DD Form 2977 RISK MANAGEMENT WORKSHEET during the planning and completion of each task and sub-task by assessing mission, enemy, terrain and weather, troops and support available-time available and civil considerations, (METT-TC). Local policies and procedures must be followed during times of increased heat category in order to avoid heat related injury. Consider the work/rest cycles and water replacement guidelines IAW TRADOC Regulation
Risk Assessment Level: Low.
Environmental Considerations: Environmental protection is not just the law but the right thing to do. It is a continual process and starts with deliberate planning. Always be alert to ways to protect our environment during training and missions. In doing so, you will contribute to the sustainment of our training resources while protecting people and the environment from harmful effects. Refer to FM Environmental Considerations and GTA ENVIRONMENTAL-RELATED RISK ASSESSMENT.
Evaluation: You will be given a graded 25 question exam, which will cover this task. A passing score on the exam is 80%.
Instructional Lead-In: Financial Management Technicians are obligated with the task of ensuring our input data is accurate, reliable, and useful to others. Knowing all particular requirements and methods utilized in GFEBS will keep technicians and commanders safe. It is important that we understand GFEBS, how to navigate within GFEBS, how to research transactions and job aids and to understand the different fields of the GFEBS system. During this lesson you will gain and understanding of GFEBS and the impact GFEBS has on all Army organizations.
Instructor Note: Adjust the Lesson Timeline as necessary to facilitate class schedule, your teaching style, and student learning. There are no time constraints during any particular phase of the ELM model. This lesson requires all students to be provisioned in GFEBS. Students will use the GFEBS training portal & PSW for this lesson. 2

3. Concepts What is General Funds Enterprise Business System (GFEBS)?
A web-based financial, asset, and accounting management system that provides the Army relevant, reliable, and timely financial information
GFEBS standardizes and streamline’s financial business processes
GFEBS is deployed to over 200 locations and supports more than 79,000 end-users
GFEBS integrates several different modules to access the same database and use the same master data. Master data includes vendors, functional locations, etc.
Show Slide #4: Concepts
General Funds Enterprise Business System (GFEBS) is a web-based financial management system that provides the Army relevant, reliable, and timely financial information. GFEBS results in a multitude of benefits for the Army’s financial professionals. Currently, the Army spends a large percentage of its efforts processing transactions, controlling interfaces and generating reports. With GFEBS, the Army’s financial professionals are now able to devote more time to financial analysis and reduce the amount of time spent on processing transactions. GFEBS was implemented into the Army in 8 phases, with 8b being the last phase for Operations (deployed environment). 3

4. General Fund Enterprise Business System Overview
Two primary types of data exist in GFEBS
Master data is information about a person or an object, such as a cost object, vendor, or General Ledger (GL) account.
Transactional data is transaction-specific data that is associated with master data. Transactional data is created from a single business event such as a purchase requisition or a request for payment.
Show Slide #5: General Fund Enterprise Business System Overview
Master data: A vendor master record contains the vendor’s name, address, and payment terms. Using master data helps users to avoid data redundancy. Integrating master data through a single source like GFEBS eliminates data redundancy and conflicting information, and provides a single view of master data information. There are many types of master data, including vendor master data, billing master data, asset master data, and customer master data.
Transaction data: When you create a requisition, GFEBS will create an electronic document for the transaction. 4

5. BI GFEBS Overview (Cont.)
Active Army
Army
National Guard
Army Reserve
Transactions
GFEBS is organized for reports, analysis and development activities into 6 functional areas.
All users across the Army draw common data from and record transactions in the Enterprise Central Component (ECC) (Real-Time).
Periodically, data is transferred from the real-time ECC to the business warehouse, Business Intelligence (BI), which also includes analytic and reporting capabilities.
Show Slide #6: GFEBS Overview (Cont.)
GFEBS organized analysis and development activities into 6 functional areas.
1. Funds Management: includes General Fund management, budget execution, and budget formulation below HQDA level.
2. Property, Plant, and Equipment: includes real property management and maintenance, materials management, equipment and asset management, and environmental liabilities.
3. Spending Chain: includes initiating purchase requisition, checking funds, recording obligations, managing goods and services receipts, and logistics integration and inventory management.
4. Cost Management: includes full costing, and payroll and travel interfaces.
5. Financials: includes United States Standard General Ledger accounting (USSGL), workflow journal voucher approval process, financial statements, and month end and year-end closing processes. Also includes sub-processes of reimbursable management and accounting.
6. Reimbursable(s): includes reimbursable order processing and debt management.
All users across the Army draw common data from and record transactions on the central ERP. All input from transactions is simultaneously available to all related actions.
All data are available in the Business Intelligence module for analyses – and support decision-making across the staffs and the Army.
FI - Finance
FM - Funds Management
SC - Spending Chain
CM - Cost Management
RM - Reimbursables
EA - Equipment and Assets
RP - Real Property
PM - Plant Maintenance
PS - Project Systems BI
GFEBS processes a million transactions a day! 5

6. AKO/ GFEBS Access URL: https://us.army.mil2
Show Slide #7: AKO/GFEBS Access
Facilitator’s Note: Students should be provisioned at this point ; have the students navigate to (AKO) and follow the instructions on the slide. 1 3
NOTE: Students must be provisioned prior to gaining access to the GFEBS portal. 6

7. AKO/GFEBS Access (Cont.)1 2
Show Slide #8: AKO/GFEBS Access (Cont.)
Select the link listed on the slide from the search results. 3 7

8. AKO/GFEBS Access (Cont.)
Adding the GFEBS Page to your “Favorites” for easy access
Show Slide #9: AKO/GFEBS Access (Cont.)
Follow the instructions on the slide if you wish to add the GFEBS home page to your favorites. 1 8

9. AKO/ GFEBS Access (Cont.)
Accessing GFEBS through the “Favorites Menu” 1 3
Show Slide #10: AKO/GFEBS Access (Cont.)
Return to the AKO home page. Click on the “Home” drop down in the top left corner of the webpage. Select “AKO Home” to return to the AKO home page.
Follow the slide instructions to access the GFEBS home page. 2 9

10. GFEBS Home Screen
The Performance Support Website (PSW) allows you to access GFEBS simulation and walk-through training materials by course name, course topic, and by role.
Show Slide #11: GFEBS Home Screen
Click on the GEFBS Training Portal (End User Training)”. This site offers a full replica of the live version of GFEBS SAP access.
Click on the “GFEBS Training and Performance Support Website (GFEBS Help)”. This site offers a full range of training packages and support to enhance the end-users ability to use GFEBS.
Access to the GFEBS Training Portal (TED) and/or production 10

11. GFEBS Login Procedures
CAC Access
NOTE: The PSW Page may be left open while running the GFEBS page.
Show Slide #12: GFEBS Login Procedures
Follow the slide instructions. 3 1 2 11

12. Performance Support Website (PSW)
GFEBS Access Screen
Performance Support Website (PSW)
Show Slide #13: GFEBS Access Screen
Follow the slide instructions. Walk students through the key functions which are GFEBS User Roles & GFEBS Materials A-Z.
Expand the menus to view the available options for each course name, course topic, and by role. Click the “+” signs to expand. 12

13. GFEBS Access Screen (Cont.)
Performance Support Website (PSW)
Show Slide #14: GFEBS Access Screen (Cont.)
The Performance Support Website is a multi-faceted system designed to provide comprehensive and collective training through application tutorials, job aids, and user procedures excerpts.
Explain Application Tutorials
Automatic walk through of a transaction or action and the Standard will be at your own pace.
Job Aids
Describe the process and is used to support users as they complete their training. They also show step by step instructions for processing transactions. The course material will display in a PDF format as shown below. You can print this material or save it to your hard drive for future access.
Application Tutorials: step-by-step interactive transaction simulations
Job Aids: step-by-step in-detail transaction walkthroughs
User procedures: step-by-step explained transaction based on the Job Aids (shorter and more concise) 13

14. GFEBS Main Body Screen Shortcuts to up-to-date training materials
To exit the Main Body screen, click on the “ERP” tab to access GFEBS (only available in the production database).
For training, select “User training” then “TED357”
Shortcuts to up-to-date training materials
Show Slide #15: GFEBS Main Body Screen
Facilitator’s Note: Explain to the students that this is how the screen will appear when using the live system. To use the system click on the ERP tab. To retrieve reports click on the Business Intelligence tab.
The Welcome to GFEBS! Box displays current alerts and/or messages.
The Available Resources list the Performance Support Website (PSW), ALMS etc.
Support section list numbers, , and hours of operation for the support section.
The Upcoming DCOs/Hotlines give information of future training and current hot topics or issues.
Important system announcements
Note: This screen is only seen in the Production (real-life) GFEBS environment.
GFEBS technical support information 14

15. GFEBS Universal Worklist
The Universal Worklist is another screen accessed from the GFEBS Home page tab. The worklist maintains a running list of all work items assigned to a particular user at a particular time. The user is one of the recipients of each of the work items.
On the Universal Worklist screen below, notice the tabs located along the top. Similar tabs appear in other areas of GFEBS. The tabs enable the user to view and/or input multiple pages of data while staying in the same transaction or function.
Show Slide #16: GFEBS Universal Worklist
Review slide information.
The “Universal Worklist” can be accessed at any time under the “GFEBS Home” tab 15

16. SAP Easy Access - User Menu
Menu Toolbar
Clicking “Help” will open the PSW in a separate window
Menu tool bar: The Menu Toolbar is dynamic and will differ depending on the transaction. This example shows the Command field on the toolbar; however, at times this field is collapsed. The Command field accepts both commands and T-codes. Spending Chain Transaction and Command Codes Job Aids will be discussed during this class. The black lower right corners on buttons (see example below) indicate a sub-menu. This convention is used throughout GFEBS.
Show Slide #17: SAP Easy Access – User Menu
Facilitator’s Note: Have the students follow along in GFEBS as you walk through the slides.
The Menu Button can be used to drill down to different areas within the system. 16

17. SAP Easy Access - User Menu (Cont.)
Option Icon, Status Bar and User-to-SAP Menu toggle
Log Off (closes portal session)
Options Icon: enables the user to open multiple sessions at one time (it is recommended that a user not have more than three sessions open at once), add favorites to internet Browser and Portal favorites.
Log Off (closes GFEBS session)
Buttons to toggle between “User Menu” and “SAP Menu”.
Show Slide #18: SAP Easy Access – User Menu (Cont.)
Facilitator’s Note: Have the students follow along in GFEBS as you walk through the slides.
Field utilized for Command code entry, Transaction code navigation, report request, etc. (most utilized)
Status Bar: displays information such as system and input error messages
System information: displays transaction being processed, system and user data 17

18. SAP Easy Access - SAP Menu
SAP Navigation pane
Expand the menu by utilizing the Black arrows for navigation
Unexpanded
Expanded
Show Slide #19: SAP Easy Access – SAP Menu
Facilitator’s Note: Have the students follow along in GFEBS as you walk through the slides.
The Navigation pane (or panel) shows the user’s Favorites, User Menu (transactions and reports available to the user based on roles assigned), and SAP menu. 18

19. SAP Easy Access - SAP Menu (Cont.)
Adding/Changing Favorites (most commonly processed transactions for user)
Click on MENU 1
ME21N 3
Click Continue 4
Enter desired transaction T-Code
Show Slide #20: SAP Easy Access – SAP Menu (Cont.)
. Facilitator’s Note: Have the students follow along in GFEBS as you walk through the slides.
Add to Favorites: You can save the T-codes you utilize on a regular basis. You are not limited to what you can save in your favorites folder. By saving your T-codes you can access your t-codes faster than you can using drill down procedures.
Favorites are a saved reference in the form of a link to a particular function, location, or site. To add a favorite, you must locate the transaction you would like to save from the menu path on the GFEBS Portal Home Screen.
Adding Favorites
To add a transaction to your Favorites folder, drill into the menu path on the GFEBS Portal Home Screen. Select and highlight the transaction and click the button. Review the following screen shot that highlights how to add a favorite.
After you have saved the transaction to your favorites, you can edit the name by right clicking on the transaction you want to change. A drop down will appear, select “Change Favorites” and you can personalize your favorite 2
Click “Insert Transaction” 19

20. SAP Easy Access - SAP Menu (Cont.)
Adding/Changing Favorites (most commonly processed transactions for user)
Show Slide #21: SAP Easy Access – SAP Menu (Cont.)
Facilitator’s Note: Have the students follow along in GFEBS as you walk through the slides.
The saved favorite will appear in both the SAP Easy Access and User Menus. Double-clicking on the favorite will navigate the User directly to the saved transaction. 20

21. Command and Transaction Codes
GFEBS uses command codes, transaction codes (T-codes) and shortcuts to relay instructions to the system. T-codes and command codes are slightly different.
A T-code is a unique identifier attached to each transaction in SAP. A command code is the text typed into the Command field in order to access a transaction. It consists of the T-code when the user is on the home screen (the SAP Easy Access Menu) or of the T-code and a prefix if the user is currently working within a transaction.
With any system, shortcuts are popular with users. These shortcuts are keys or key combinations that command the system to take action. Within GFEBS ECC transactions, the shortcuts shown below are available.
Show Slide #22: SAP Command and Transaction Codes
T-Codes allow the user roles to perform some of the following functions:
Create (01)
Change (02)
Display (03)
Run reports
These functions allow the flexibility of daily tasks performed and is also instrumental in Job Role Mapping
Example: VA01 Create a sales order, a VA02 change a sales order
VA represents Sales order and the 01/02 represent a create and change 21

22. Command Codes Command Code Action
Takes the user to the associated transaction if currently at the SAP Easy Access Menu. In this case, create a PO.
ME21N
Ends the current transaction and returns the user to the SAP Easy Access Menu (the water screen). /N
Ends the current transaction and starts a new specified transaction. In this case, an Invoice.
/NMIRO
Displays an overview of the open sessions. /O
Starts a new session with the specified transaction while keeping the current session open.
Show Slide #23: Command Codes
Review slide information.
/OMIGO
Closes the active session. /I
Ends the current transaction and prompts the user to log off SAP.
/Nend
NOTE: Mission Specific Transaction Codes will be covered in depth during the following class 22

23. Types of Transaction Codes
GFEBS uses numerous T-codes. Some will become familiar to the user due to frequency of use. Those T-codes are recommended for the user’s Favorites list. The following hints may assist in understanding T-codes that are less familiar. These hints are guidelines and not true in all cases.
T-Code
ending in:
The T-Code will:
Example 1
Create a new transaction
FMZ1 – Create Funds Commitment 2
Show Slide #24: Types of Transaction Codes
To access various transactions within GFEBS, users must enter transaction codes in the Command Field.
T- Codes are a sequence of characters that identifies a transaction or function in GFEBS.
Basically, T-Codes allow the user to perform their various job functions in GFEBS.
Transaction codes and command codes are slightly different:
A transaction code is a unique identifier attached to each transaction in SAP.
A command code is the text typed into the command field in order to access a
transaction. It consists of the transaction code when the user is on the home screen
(the SAP Easy Access Menu), or the transaction code and a prefix if the user is
currently working within a transaction.
Change a saved transaction
FB02 – Change Document 3
Display a transaction
XK03 – Display Vendor
Transaction Codes for Reports will usually start with the letter “S”. Example: S_P99_ – Payment List
NOTE: Mission Specific Transaction Codes will be covered in depth during the following class 23

24. User Roles
A role is defined as a major grouping of activities that reflect a specific aspect of a person’s job. While a role may have several activities aligned to it, an activity can only be aligned with one role.
Show Slide #25: User Roles
A user role is defined as a major grouping of activities that reflect a specific aspect of a person’s job. While a role may have several activities aligned to it, an activity can only be aligned with one role.
GFEBS roles determine what activities an end user performs when using the system, what sections of the system an end user has access to, and what training an end user needs to perform their new roles successfully.
A person may be assigned one or more roles, and roles can be assigned to one or more persons.
Facilitator’s Note: There should be a separation of duty amongst the roles to prevent fraud and abuse. For example; a processor should not have the role of a certifier or approver. 24

25. SAP System Shortcuts
With any system, shortcuts are popular with users. These shortcuts are keys or key combinations that command the system to take action. Within GFEBS ECC transactions, the shortcuts shown below are available.
Show Slide #26: SAP System Shortcuts
Review slide information. 25

26. Note: Some Tabs and Fields are not used due to cost effectiveness.
GFEBS Screen Elements
Navigation Tabs
Fields
Show Slide #27: GFEBS Screen Elements
Navigation Tabs will take you to certain screens that need to be filled based on the T-code and user role you are serving in at that time of input. There are different navigation tabs that display on the screen based on the t-codes or reports you are requesting.
Fields are used to input information needed to support the specific transaction code.
Note: Some Tabs and Fields are not used due to cost effectiveness. 26

27. GFEBS Screen Elements (Cont.)
Status Bar System Messages
Message Type
Symbol
Error
Information
Warning
Show Slide #28: GFEBS Screen Elements (Cont.)
This chart displays the appearance of the messages. The messages will be located in the lower left corner of the screen. 27

28. Input Fields Required, Optional and Conditional
For additional Field Information click in the field and press F1
Required Fields
Show Slide #29: Input Fields
There are 3 types of data entry fields:
Required Fields = R
Optional Fields = O
Conditional fields = C
The R/O/C column in the field description table represents the three types of data entry fields in SAP.
R is for required fields that must be populated to complete a transaction.
O is for optional fields that are not mandatory to complete a transaction.
C is for conditional fields that are dependent on population of related fields and specific transactional events. On certain screens you may need to scroll to view additional data fields.
You will see these data entry fields when you utilize the user procedures and job aides within the PSW and Milwiki.
During the GFEBS training we will use only the Required Fields. Your unit policies or supervisor will designate what fields will be used for that location.
Optional Fields
Conditional Fields 28

29. Radio Buttons and Checkboxes
Show Slide #30: Radio Buttons and Checkboxes
NOTE: Radio buttons offer a single select, while check boxes offer the ability of multiple selection.
Check boxes 29

30. Status Bar System Messages
The Status bar is located on the lower left corner of the screen. It displays information such as warning and error messages. There are three different types of status messages. Review the message types listed below.
Message Type Description
Error Message - Messages indicating incorrect entry in the system such as required or inaccurate data. You will not be able to continue with your transaction until these messages are addressed.
Info Message - Affirmative system message or messages displaying information on a transaction.
Warning Message - Messages that identify information that may possibly be an error. These messages may or may not allow you to continue with your transaction, depending on its function within the system.
Show Slide #31: Status Bar System Messages
Status Bar
The Status bar is located on the lower left corner of the screen. It displays information such as warning and error messages. There are three different types of status messages. Review the message types listed below.
Message Type Description
Error Message - Messages indicating incorrect entry in the system such as required or inaccurate data. You will not be able to continue with your transaction until these messages are addressed.
Info Message - Affirmative system messages or messages displaying information on a transaction.
Warning Message - Messages that identify information that may possibly be an error. These messages may or may not allow you to continue with your transaction, depending on its function within the system. 30

31. Wildcard Characters Using Wildcard Characters
Performing wildcard search will increase system performance since fewer records will be pulled from the system. Here are some examples of using a Wildcard search:
Placing the * at the end of a string causes the system to return all records that begin with the letters before the *.
Placing the * at the beginning of a string, the system will find all records that contains the characters at the end.
If you place the * at the beginning and end of the string, the system returns all records that contain the string at the beginning, middle, and/or end.
Show Slide #32: Wildcard Characters
Facilitator’s Note: Write an example on the board for the students:
Using Wildcard Characters
Performing wildcard search will increase system performance since fewer records will be pulled from the system. Here are some examples of using a Wildcard search:
Placing the * at the end of a string causes the system to return all records that begin with the letters before the *.
Placing the * at the beginning of a string, the system will find all records that contains the characters at the end.
If you place the * at the beginning and end of the string, the system returns all records that contain the string at the beginning, middle, and/or end.
For example if we were looking for jackson or information with jackson in it.
You can type in Jac* everything beginning with JAC will appear.
If you typed in *son, this will display all records that contain these characters.
If you type *jackson*. This will show al records that contain Jackson at the beginning, middle, and/or end. 31

32. Match codes allow users to select or search for a value from a list.
Show Slide #33: Match Codes
Match codes allow you to search for data that pertains to a particular field or transaction. This data is already in GFEBS and can be chosen as part of the transaction. Match codes generate lists with several possible options they allow users to select or search for a value from a list. Match code search is used in any transaction in GFEBS where a field has the icon .
Match code Icon
Wildcard Characters 32

33. Help / Logging Off General Help and Logging Off F1 Field Explanation
Log off link
Help link to access Performance Support Website
Show Slide #34: Help / Logging Off
Help link will take you to the Performance Support Website (PSW).
Logoff, select this button to logoff or close out GFEBS. 33

34. LSA #1 Check on Learning
Q1: What is the difference between master and transactional data? A1: Master data is information about a person or an object, such as a cost object, vendor, or General Ledger (GL) account. Transactional data is transaction-specific data that is associated with master data. Transactional data is created from a single business event such as a purchase requisition or a request for payment. Q2: The ______________allows you to access GFEBS simulation and walk-through training materials by course name, course topic, and by role. A2: Performance Support Website (PSW) Q3: T/F: A transaction code is the text typed into the command field in order to access a transaction. A3: False
Show Slide #35: LSA #1 Check on Learning
NOTE: Read and ask the following check on learning question and facilitate discussion on answers given.
NOTE: The answer to each question will appear when you hit enter.
Q1: What is the difference between master and transactional data?
A1: Master data is information about a person or an object, such as a cost object, vendor, or General Ledger (GL) account. Transactional data is transaction-specific data that is associated with master data. Transactional data is created from a single business event such as a purchase requisition or a request for payment.
Q2: The ______________allows you to access GFEBS simulation and walk-through training materials by course name, course topic, and by role.
A2: Performance Support Website (PSW)
Q3: T/F: A transaction code is the text typed into the command field in order to access a transaction.
A3: False(command code) 35

35. LSA #1 Summary Show Slide #36: LSA #1 Summary
Facilitator's Note: During this lesson we discussed the background, purpose and the functions of the GFEBS program. We also covered how to navigate through AKO to access GFEBS. In addition, we discussed the Performance Support Website(PSW) is a multi-faceted system designed to provide comprehensive and collective training through application tutorials, job aids, and user procedures excerpts.
“Or”
NOTE: Have one learner from each group to explain the most important take away to them from this lesson. Facilitate a discussion on each answer. 36

36. Critical Thinking How else could you use this information?
How might you use this information in the future?
Show Slide #37: Critical Thinking
This phase is student-centered and instructor facilitated. Allow the students to decide how they will use the information. The definitive goal is for the students to think critically and creatively about how to use the information garnered from the lesson plan in the future. As the instructor you can direct the students to brainstorm or you can ask open ended questions such as:
How might you use this information in the future?
How else could you use this information?
How can you apply newly learned information in current or future duty positions?
Facilitator’s Note: The above listed questions are only examples. As the instructor you are free to ask varied questions. However, ensure the questions are open-ended and serves to ensure the students see the relevance of the generalized new information presented and future usage.
How can you apply newly learned information in current or future duty
positions? 36

37. Questions? Show Slide #38: Questions
Facilitator’s Note: Field any questions from the students to ensure the standards of the lesson are understood and have been met. 37

38. TLO Summary
Action: Conduct Introduction to General Fund Enterprise Business System (GFEBS)
Conditions: FM Leaders in a classroom environment using doctrinal and administrative publications, personal experience, handouts, discussion and access to GFEBS.
Standard: With at least 80% accuracy learners must show proficiency with:
Communicate the background, purpose, and functions of the GFEBS program
Show Slide #39: TLO Summary
NOTE: Reiterate TLO
Action: Conduct Introduction to General Fund Enterprise Business System (GFEBS)
Conditions: FM Leaders in a classroom environment using doctrinal and administrative publications, personal experience, handouts, discussion and access to GFEBS.
Standards: With at least 80% accuracy:
- Communicate the background, purpose, and functions of the GFEBS program 38

39. Appendix A Assessment Plan 39 Show Slide #40: Appendix A
Contribution to Group Work
30%
Written Communication
10%
Oral Communication
Module Post Assessment
50%
Total 
100%
Contribution to Group Work. See FM SLC Contribution to Group Work Rubric for specific grading criteria.
Written Communication. See FM SLC Written Communication Rubric for specific grading criteria.
Oral Communication. See FM SLC Oral Communication Rubric for specific grading criteria.
Module Post Assessment. A comprehensive post assessment consisting of multiple-choice, matching, fill-in-the-blank and ordering questions will be administered via Blackboard Academic Suite upon completion of the module. 39

40. Appendix B Presentation Outline 40 Show Slide #41: Appendix B Slides
Slide Number Description
Slide Introduction to General Fund Enterprise Business System (GFEBS)
Slide Concrete Experience
Slide 3 Terminal Learning Objective
Slide Concepts
Slide General Fund Enterprise Business System Overview
Slide GFEBS Overview (Cont.)
Slide AKO/ GFEBS Access
Slide AKO/ GFEBS Access (Cont.)
Slide AKO/ GFEBS Access (Cont.)
Slide AKO/ GFEBS Access (Cont.)
Slide GFEBS Home Screen
Slide GFEBS Login Procedures
Slide GFEBS Access Screen
Slide GFEBS Access Screen (Cont.)
Slide GFEBS Main Body Screen
Slide GFEBS Universal Worklist
Slide SAP Easy Access – User Menu
Slide SAP Easy Access – User Menu (Cont.)
Slide SAP Easy Access – SAP Menu
Slide SAP Easy Access – SAP Menu (Cont.)
Slide SAP Easy Access – SAP Menu (Cont.)
Slide Command and Transaction Codes
Slide Command Codes
Slide Types of Command Codes
Slide User Roles
Slide SAP System Shortcuts
Slide GFEBS Screen Elements
Slide GFEBS Screen Elements (Cont.)
Slide Input Fields
Slide Radio Buttons and Checkboxes
Slide Status Bar System Messages
Slide Wildcard Characters
Slide Match Codes
Slide Help/ Logging Off
Slide LSA #1 Check on Learning
Slide LSA #1 Summary
Slide Critical Thinking
Slide Questions
Slide TLO Summary
Slide Appendix A
Slide Appendix B 40