Free IFPUG I40-420 Practice Exam with Questions & Answers | Set: 5

The Stock Purchasing (SP) and Point of Sale (POS) applications have the following requirements.

• The POS application maintains details of customer purchases in the Item Purchases logical file.
• The SP application is used to place orders with suppliers based on daily inventory levels.
• The SP application is used to maintain supplier information. The Supplier Information logical file contains descriptions of items the supplier stocks and supplier contact information.
• The Inventory logical file is maintained by the SP application through a daily batch process which references the Item Purchases logical file.
• When the batch process is complete, the SP application displays a list of items that are below 20% of normal inventory levels. The user selects items to be ordered and specifies the supplier. The SP application then generates a purchase order for each supplier. The purchase orders are sent electronically to each supplier and stored in the Order logical file.
• From the Names of Possible Functions listed identify the data function both the SP and POS applications. Select N/A if a Name of Possible Function does not apply.

Identify the functions used:

A Call Center (CC) application is being enhanced to maintain and display 2 new pieces of information. The CC will add the 2 new DETs to all 5 of the modified transactional functions.

• The Product Summary Report had 2 FTRs and 12 DETs.
• Add Literature and Change Literature had 4 FTRs and 19 DETs.
• The Literature Report (no calculations or derived data) had 4 FTRs and 19 DETs.
• The Call Log Report (no calculations or derived data) had 1 FTRs and 19 DETs.

What is the complexity of the transactional functions after the enhancement?

Select the complexity for each function:

The Human Resources (HR) application includes functionality to maintain the Department logical file.

• The user enters a department number and presses the View button to display an existing department. An error message is displayed if the department does not exist.
• When the user adds or updates a department, the cost center is validated against the Cost Center logical file. The Cost Center logical file is maintained in the Payroll application.
• The user Adds a new department by entering department #, Name, phone #, mail stop, cost center and manager. The user completes the add by pressing the Add button. An error message displayed if the department # already exists.
• The user Updates information about the displayed department. Name, phone #, mail stop, cost center and manager may be changed. The user completes the update by pressing the Update button.
• The user Deletes the displayed department by pressing the Delete button.
• A manager must be selected using the Manager Drop Down list, which displays manager name and department number. The Employee logical file is maintained in the HR application and is the source for the Manager Drop Down list.

Determine the complexity for department transactions.

Select the complexity for each function.

Several data functions are described in the scenario for the Accounts Receivable fAFO application:

• From the main menu, the user selects the receive payment option.
• The receive payment option opens a screen which allows the user to enter payment information in the Payment Information logical file. The receive payment option updates the Customer Payment logical file to store the outstanding balance due. If there is no existing outstanding balance, the current balance is added to the Customer Payment logical file.
• The Currency Translation file is imported daily from the Banking Application and updates the AR application's Customer Currency logical file. The Customer Currency logical file is used by the AR application to translate the currency from the customer's local currency to the Euro. The user also maintains the country code and full country name in the Customer Currency logical file.
• The user maintains the customer name, address and account number in the Customer Information file in the AR application.
• From the main menu, the user selects the balance review option.
• The balance review option accesses the Customer Payment logical file. The balance summary option allows the user to create a balance summary report by customer. This report is viewable on the screen, can be emailed to a user, downloaded to a spreadsheet, and printed to hardcopy. For audit purposes, every balance summary report is saved to the Audit Balance Summary logical file.
• The balance detail option accesses the Customer Information, Customer Payment and Customer Currency logical files. A printed report is created that contains a list of all customers with balance changes in the current month. The balance is shown in both customer local currency and the Euro. The report also includes the customer address with country name after translating the country code using the Customer Currency logical file.

From the Names of Possible Functions listed identify the data functions for the AR application. Select N/A if a Name of Possible Function does not apply.

Identify the functions used:

The Patient Billing application includes functionality to maintain the Patient logical file.

• The user enters a patient id and presses the View button to display an existing patient record, including diagnosis description and insurance company name. An error message is displayed if the patient record does not exist.
• The user Adds a new patient by entering a patient ID and the remaining values. The user completes the add by pressing the Add button. An error message is displayed if the patient id already exists.
• The user Updates information about the patient. All attributes can be modified except for patient id. The user completes the update by pressing the Update button
• A diagnosis code must be selected using a drop down list for the primary diagnosis and the secondary diagnosis. The drop down list function is identical for primary and secondary diagnosis. The Diagnosis logical file is maintained in the Patient Billing application and is the source for the Diagnosis Code Drop Down list. The Diagnosis Code Drop Down list displays the diagnosis code, description and authorized days of hospitalization.
• An insurance company code must be selected using the Insurance Company Drop Down list. The Insurance logical file is used as the source. The Insurance Company Drop Down list displays the insurance company number, group type and name.
• All other drop down lists use static data as the source.

Determine the complexity for the following functions:

Select the complexity for each function:

EXAM SCHEDULING SYSTEM (ESS) - EXAM SCHEDULING FUNCTIONS

• The controller uses the Maintain Exam Schedule screen to schedule exams for various courses and subjects.
• The exam serial number from the University Master logical file is entered in the screen. On pressing the Retrieve key, the exam name, controller number, finals week start date and finals week end date efe displayed from the University Master logical file. In addition, exam status, course id, subject id, exam date, start time, end time, proctor and message are displayed from Schedule Information logical file.
• The Add or Modify options allow addition/update to the course id, subject id, exam start date, start time, end time, proctor and message using the exam serial number as the key field. The data in the add/update mode gets saved in the Schedule Information logical file with the 'pending approval' in the exam status, no other data is stored.
• Course id, subject id and exam date pick lists provide data from static tables.
• The exam dates should be within the finals week start and end dates

Determine the complexity for functions listed:

Select the complexity for each function:

LIBRARY INFORMATION SYSTEM (LIS) - REPORTS

LIS produces five reports:

• Text Out On Loan

• References Customer logical file
• References Text logical file
• Displays 8 fields

• Text Overdue

• References Customer logical file
• References Text logical file
• Displays 4 fields

• Text With Multiple Hold Requests

• References Text logical file
• References Publisher Guide logical file
• References Customer logical file
• Displays 25 fields

• Inventory List

• References Inventory logical file
• Displays 12 fields including 1 calculated field

• Text On Order

• References Order logical file
• References Publisher Guide logical file
• References Text logical file
• References Employee logical file
• Displays 15 fields including 2 calculated fields

Determine the complexity of the following functions.

Select the complexity for each function:

CORPORATE INFORMATION SYSTEM (CIS) - EMPLOYEE DATA TRANSFER

• From the CIS main menu, the CIS user selects the Transfer Employee Data option.
• The Transfer Employee Data option creates a transaction file of CIS Employee logical file records that have a status flag equal to Add or Change. Each record in the transaction file contains employee badge number, first name, last name, phone number, facility, supervisor badge number, organization, job code, and status flag.
• The CIS transaction file is written to the Financial System (FS) server's temporary file work area. This data transfer is a user requirement for both applications.
• From the FS main menu, the FS user selects the Load Employee Data option.
• The Load Employee Data option accesses the CIS transaction file from the FS server's temporary file work area. The Load Employee Data option processes the input records according to the status flag, initiating different processing logic for Add and Change. The Load Employee Data option loads all attributes from each record to the FS, except the status flag.
• As part of the same elementary process, when an employee is being Added or Changed to the FS Employee logical file it also saves the employee's pay grade code, retrieved from the Payroll System.
• Both applications have a requirement to access a version of the Employee logical file.

Determine the complexity for the functions listed.

Select the complexity for each function:

The Robot Automation Program (RAP) is an application which allows factory technicians to create and edit the weld placement programs for various robots on the assembly line. Both transactions maintain the Weld Specification and Robot logical files.

The use may select and view reboot details:

The user may print individual welding program details:

From the Names of Possible Functions listed identify the transactional functions for the RAP application. Select N/A if a Name of Possible Functions does not apply.

Identify the functions used:

ITEM CHECK-OUT SCREEN

• Library employees use the Item Check-Out screen when a member is ready check out the book(s) and/or magazine(s) he wishes to borrow. The library employee enters the member id number, and when the employee exits the member id attribute, if the member id is valid, the member name is retrieved from the Member Information logical file and displayed in the member name attribute. The library employee enters the item type (b for book, m for magazine) and the item code; the item title is retrieved from the Book Information logical file and displayed in the item title attribute. The library employee then enters the lending date and the due date, and presses the Add button. The information is stored in the Check-Out logical file.
• Library employees use the Item Check-Out screen to update the due date of a book or magazine if a member requests additional lending time. The employee enters the member id number, and when the employee exits the member id attribute, if the member id is valid, the member name is retrieved from the Member Information logical file and displayed in the member name attribute, the library employee enters the item type (b for book, m for magazine) and the item code; the item title is retrieved from the Book Information logical file and displayed in the item title attribute and the lending date and due date are retrieved from the Check-Out logical file. The library employee then updates the due date, and presses the Update button. The new due date is stored in the Check-Out logical file.
• The head librarian receives two reports from the Library Check-Out application. The first report is the Overdue Report which is a list of overdue items categorized into < 30 days overdue, 30 - 90 days overdue and > 90 days overdue.
• The second report is the Low Usage Report that calculates which fiction books have not been checked out in the last 24 months and lists the title of those books. This report is run on demand. A High Usage Report with the number of times an item has been checked out has been put on hold and will not be released.
• A proposed Member Check-Out Report with a list of books checked-out and recommended titles will not be developed until privacy issues have been resolved.
• From the Names of Possible Functions listed identify the transactional functions for the current Library Check-Out application. Select N/A if a Name of Possible Function does not apply.

Identify the functions used: