Help required for Listing out Activities to be performed for setting up a new concur test instance

[justinkthomas]

Hello all,

Our client is planning for setting up a new test instance/environment for concur.

We have listed few activities below. Reaching out for suggestions/ feedback:

1. Instance Provisioning

• Request a dedicated test instance from SAP Concur (usually via your SAP account manager).
• Confirm that the instance includes necessary modules (Expense, Invoice, Travel, etc.).

2. User & Role Setup

• Create test users with different roles (e.g., employee, approver, finance).
• Use the Test User Admin Tool to simulate real-world scenarios without affecting production data.

3. Policy & Workflow Configuration

• Replicate or redesign expense policies, approval workflows, and audit rules.
• Configure test-specific workflows to validate edge cases and exception handling.

4. Forms & Fields

• Create custom forms and fields required for testing.
• Ensure mappings align with your SAP backend (e.g., cost centers, GL accounts).

5. Data Preparation

• Import sample employee data, cost objects, vendors, and credit card feeds.
• Use CSV uploads or API calls to populate the test environment.

6. Integration Testing

• Validate API connectivity for:
  • Expense report creation
  • Data retrieval
  • Posting to SAP backend
• Test App Center integrations (if applicable) using sandbox credentials.

7. Validation & UAT

• Perform end-to-end testing:
  • Expense creation → Approval → Posting
  • Invoice processing
  • Credit card tokenization
  • Attachment uploads
• Document test cases and expected outcomes.

---

🔹 Basis/Infra Technical Setup

1. SAP Add-On Installation

Ensure the following add-ons (if applicable) are installed in the SAP backend:

• CTE_FND – Foundation
• CTE_HCM – Human Capital Management
• CTE_FIN – Financial Integration
• CTE_INV – Invoice Integration
• CTE_FGM – Funds/Grants Management

2. System Connection Setup

• Use transaction CTE_SETUP to initiate integration.
• Configure system connections, including:
  • Client credentials
  • SSL certificates
  • Endpoint URLs

3. Data Export Configuration

• Set up export of:
  • Employee master data
  • Cost objects (Cost Centers, Internal Orders, Projects)
  • Vendors and Purchase Orders
• Configure field mappings and object hierarchies.

4. Data Import Configuration

• Configure import of:
  • Expense reports
  • Payroll data
  • Invoices and attachments
• Validate mapping to SAP FI/CO modules.

5. Security Setup

• Install SSL certificates (GeoTrust, DigiCert) for secure communication.
• Ensure PCI compliance for credit card data handling.

6. Monitoring & Logging

• Enable communication monitors to track data flow.
• Set up logging for:
  • API calls
  • Integration errors
  • Data sync status

[PoojaKumatkar · Accepted solution]

Hi @justinkthomas ,

You don't have to worry about all of these activities. Once test site is purchased, there is a provision to replicate your production site setup/information into test instance. After that you can play around with configuration or can create separate new configuration for your testing purposes if required.

Regarding integration related activities, as you know PROD and TEST these are two different instances, hence, integration needs to be done accordingly with the ERP. Meaning, PROD instance will always be connected to your ERP PRDO and TEST instance needs to be always connected to your ERP DEV/QA. 

In addition, please note that any integration will not happen automatically. For this you need to raise a support ticket with Concur and get it done as per your requirement and need.

For additional information there is one FAQ document available on production sandbox environment which can clarify all your queries regarding this topic. For that, I have sent you private msg. Can you please check and respond.

If this answers your query, then please mark solution as accepted.

[justinkthomas]

Thanks Pooja!

Regards,

Justin