Pass the IFPUG Certification I40-420 Questions and answers with ExamsMirror

The Procurement application requires the ability to maintain information on each new supplier. The information that must be maintained on the Supplier logical file includes:

 Supplier id

 Supplier name

 Supplier mailing address

 Supplier skill

As a result of creating a new supplier record, the supplier's annual costs should be automatically calculated and saved with the other supplier information.

Orders are maintained in the Order logical file by the Procurement application. The Accounts Payable logical file is updated for each order. Line items for each order are stored in the Order Detail subgroup of the order logical file.

Backorders and delivery errors are tracked by the Procurement application on the Transparency Track Record logical file. This file is compared to each supplier's values in the Service Level Agreement logical file which is maintained by the Contract application. The Procurement application produces a report for the Legal Office of suppliers that are performing outside of their Service Level Agreement.

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

Identify the functions used.

Determine the complexity of the data and/or transactions identified in the following scenario:

The Library Information System (LIS) user Adds new member information by entering the member code, the member name, the telephone number, the address and the starting membership date. Information is stored and maintained in the Member logical file.

The LIS user Changes some member information or Deletes it, by entering the member code. The LIS retrieves all the information related to the member code and displays it on the screen. Then, the LIS user Changes all the data displayed, with the exception of the member code, or completely Deletes the member information. If the member code is not found in the Member logical file, then an error message is displayed to the user.

The LIS user Views member information by entering the member code and/or the member name on the screen. All the member data is retrieved and displayed in the search results. If the member code and/or the member name is not found in the Member logical file, then an error message is displayed to the user.

All functions are activated by pressing the OK button.

Determine the complexity for the following functions:

Select the complexity for each function:

Several functions are outlined within the following scenario for the Accounts Receivable application:

From the main menu, the user selects the receive payment option.

The receive payment option opens a screen which allows the user to add or change payment information on the Payment Information logical file after performing an inquiry on payments received for the customer. The receive payment option updates the Customer Master logical file to store a current outstanding balance due. If there was no existing outstanding balance, the current balance is added to the Customer Master logical file.

From the main menu, the user selects the balance review option.

The balance review option accesses the Customer Master logical file and allows the user to create a summary report with customer balance totals.

The balance review summary option accesses the Customer Master and Currency Translation logical files. A report is created that contains a comprehensive list of all past balance changes in both company standard currency and customer local currency.

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

Identify the functions used:

ALERT SYSTEM - ALERT NOTIFICATION

Brokers use the Alert Profile screen to maintain the Alert Profile logical file. They can Add, Change, Delete and View alert information.

Brokers also maintain a list of many securities to monitor. The securities information is considered to be part of the Alert Profile.

The Alert Profile record is not considered complete until at least one security has been entered. The account number, alert contact name, alert phone number, and security id are required fields. The user is required to enter at least one of the remaining fields: low price threshold, high price threshold, and high volume threshold, they may enter values in all three.

When an Alert Profile record is Added a validation is performed on the account number against the Account Master logical file and a validation on the securities against the Securities logical file.

When Alert Profile records are Changed a validation is on the account number against the Account Master. All fields can be modified.

No validations are performed for the Alert Profile View.

When an Alert Profile record is Deleted the user must enter the account number, alert contact name, alert phone number. The account number is validated against the Account Master.

Error messages are displayed whenever validations fail

Select the complexity of each function:

A baseline count is to be conducted for the Payment Information Application (PIA).

Client Credit History logical file is made available to the teller while processing a customer's wire payment. The Client Credit History logical file is retrieved from the Credit Master Application (CMA).

PIA also receives an end-of-day import file of wire payments from the Foreign Banking (FB) application. PIA maintains all customer wire payments in the Wire Payment logical file. During the processing of the wire payments, the currency is converted from the customer's local currency to PIA's currency using the FB application Currency logical file.

The teller must review the client credit history, and then update the Credit Limit logical file in the PIA before processing the wire payment.

Tellers maintain the Customer Account logical file using the maintain customer account function within PIA.

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

Identify the data functions used:

INTERNET APPLICATION (IA) -MAINTAIN INTERNET DATA

From the IA main menu, the IA user selects the Purchase Item option.

The Purchase Item option opens a screen which allows the user to pay their internet shopping bill after performing an inquiry of the items selected for purchase. The Pay Bill option updates the Customer logical file to store the date of last purchase. The Inventory logical file is updated to determine when stock is depleted. The Inventory logical file contains the following information: product id, units of measure, count of product on hand, count of product on order, count of product on back-order, and reorder point.

The Product logical file is maintained by the PARTS application. Product contains product id, description, expected life of product, category, manufacturer, SKU, and weight.

Upon the customer's first purchase, the Customer Information screen captures the following information about the customer and stores it on the Customer logical file which includes: customer number, name, street address, state/province/region, country, postal code, payment type, gender, and future email offer flag.

The Purchase History logical file (PHF) is used to contain the history of customer purchases. The PHF contains a demographics section which contains the following: customer number, gender, product category, product id, and purchase frequency. The other part of the PHF contains information pertaining to the cost of purchases: customer number, purchase date, quantity, purchase cost, expected life of product. An additional part of the PHF contains information about email offers sent to the customer. This part of the PHF contains information: date of email, product id, sale price, sale end date, and offer end date.

The purchase cost is stored in the PHF in US Dollars after conversion from the customer's local currency using the Currency logical file. The Currency logical file contains the following information: country currency converting from, country currency converting to, conversion rate, date and time of conversion rate.

Determine the complexity of the data functions:

Determine the complexity of the following 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.

An enhancement project involves both the Human Resource (HR) application and the Mail Distribution (MD) application.

The HR application maintains all data elements in the Employee logical file. The users of the HR application require validations for employee pay grade and employee job title in the Employee logical file. The employee pay grade will be validated against the Pay Grade logical file which is maintained by the Finance application. The employee job title will be validated against the Job Title logical file which is maintained by the Compensation application.

The MD application maintains two data elements in the Employee logical file. The users of the MD application require additional validations for building and floor within the employee mailing address. The building and floor will be validated against the Building logical file which is a new file being developed by this project.

The users will use the MD application to maintain the Building logical file. The users of the MD application also maintain building and floor in the Employee logical file.

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

Identify the data functions used:

A Flight Reservation application has the ability to make a reservation and reserve a seat.

A passenger calls to make a reservation. The booking agent adds the information into the Flight Reservation logical file.

At a later time the passenger can make a change to the reservation through the booking agent.

The booking agent views the flight reservation record before changing it.

The booking agent can also reserve a seat for the passenger for each leg of his travel, but cannot change or delete the seat reservation once made. Seat reservations are stored in the Seat Reservation logical file.

The booking agent can view the seat reservation record.

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

Identify the functions used:

An Assets Tracking application has a batch update process. Twice a month each of the branch offices sends a transaction file to the headquarters.

Records are flagged with an "A" for equipment that is Added to the inventory; "C" for equipment that has been Upgraded or refurbished; "D" for equipment that has been Disposed of and is to be removed from inventory.

A summary inventory update report will be created that totals number of inventory records added, changed and deleted broken out by equipment type. The report will be sorted by branch and will start on a new page for each change of branch.

A detail inventory report will be available to the branches with the detail of inventory records updated.

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

Identify the functions used.