Policies in Concur Request function much like in Concur Expense: a Policy is a container for the configurations that determine how a request behaves. The four major items the Policy controls are data entry requirements, approval processes, travel segments, and expected expenses.
When creating policies, SAP Concur recommends copying an existing policy and making your updates to the copy. This can reduce the work you must complete and preserve the original for future reference.
When working on a policy, there are four areas to configure:
- General
This area allows you to set basic settings that control the behavior of a request, such as the workflow, header, and allocation forms; agency notification e-mails; cancellation options; assignability to expense reports; and more.
- Segments
This section allows you to enable or disable travel segments for this Policy. You can also match a segment to an Expense Type and assign the entry forms that will be used to capture data about that segment. If you have a TMC that will be involved in the travel booking process, you can define which segments are managed by the TMC. This is true even if your site is not integrated with Concur Travel.
You learned how to create these segments in the previous unit.
- Expenses Types
This area allows you to enable or disable the Expense Types that you want users to be able to add to a request as expected expenses. You can assign the entry form and vendor list, define a calculation formula, and set attendee settings for each Expense Type. If your site will be integrated with Concur Expense, the expenses on a request can automatically be created on the associated expense report.
- Print Formats
This area allows you to enable or disable the options available to the user if they choose to print their request.
Resources
Select the Policies and Groups Setup Guide to open the system documentation for Request Policies.
Now that you know the basics of Request Policy configuration, let's take a look at the configuration process for CVI.