Implementation Method Configuration

The following tables are system-wide setup tables that have setup specific to Travel and Expense Management. This setup should be done before all the others.

Advantage Footprint

The following Application Parameter is the primary setting for implementation method. Any change to this parameter requires a bounce of all servers used for the CGI Advantage Financial.

Parameter

Description

Dual HRM/Financial Site

(DUAL_HRM_FIN_SITE)

This parameter defines whether the site uses both Advantage HRM and Financial or uses Advantage Financial only. The primary use of this setting is to determine where travelers are defined. There are other corresponding settings within this section that refer to this control.

False: Also known as Financial Only because travel is used only with Advantage Financial. Travelers are defined as Vendor Customers. While they are still employees, they are given a Vendor/Customer code, which may or may not be their employee number.
True: Also known as Dual site because both Advantage HRM and Financial are used with travel. Employees are defined as travelers.

Please note this control is used outside of travel to allow the configuration of the “Advantage” Employee ID field on Fixed Asset, Journal Voucher, Accounting Based Spending, Receivable, Cash Receipt and Charge transactions.

Financial Only

The following configurations should be in place:

Travel and Expense Landing Page – On the Application Page Registration, ensure the Travel and Expense Landing Page Code of TRVLLP is not searchable and FTRVLLP is searchable.

Travel Authorizations Tab – On the Application Page Registration, ensure the Travel Authorizations Page Code of TRAUTHC is not searchable and FTRAUTHC is searchable.
Expense Reports Tab – On the Application Page Registration, ensure the Expense Reports Page Code of TRERC is not searchable and FTRERC is searchable.
Upcoming Trips Tab – On the Application Page Registration, ensure the Upcoming Trips Page Code of UPCOMC is not searchable and FUPCOMC is searchable.
Pending Payments Tab – On the Application Page Registration, ensure the Pending Payments Page Code of PAYMTC is not searchable and FPPYMTC is searchable.

Traveler Home Unit – Use of a ‘home unit’ for a traveler is optional. However, if Transaction Unit is required for security purposes in the creation of travel transactions or there are Department Travel Policy by Expense Type rule where the Unit for the rule is specified (not the ALL wildcard), then Unit on the Vendor Customer record of a traveler must be populated. A Configurable Validation must be put into place so the UNIT_CD field on R_VEND_CUST cannot be blank when TRVLR_FL is 1.
Business Role – As the delivered day zero business role for Traveler and the one for Travel and Expense Management include only Dual Site pages, the landing page of TRVLLP needs to be replaced with FTRVLLP as a System Resource.
Payments – With payments to travelers and direct vendor payments, are disbursement options on the Traveler and Trip Details (Expense section on the wizards) such as Schedule Payment Date and Vendor/Customer fields that need to be made visible.

Dual Site

Manager Security – On the User to Business Role Association page, the managers of travelers must be assigned a Business Role where the Role Type Information setting is Manager to connect to the Application Security Roles necessary for travel management.
Hire Date Validation – If there is a need to edit that the Expense Date will not or did not occur before the hire date of the employee/traveler. This can be put in as the following Configurable Validations:

TRVL_DOC_COMMImpl.getTrvlrsEmplHrDt(TRVLR_ID, this.getSession()) == null
or
TRVL_DOC_COMMImpl.getTrvlrsEmplHrDt(TRVLR_ID, this.getSession()) >= TRAN_DT