Implementing ERP - Sandbox Pros and Cons

Hello All - Looking for experiences of users.

We are implementing a new ERP (in our case, Oracle Fusion). It is a global implementation that will take several years to complete. During the first phase of implementation, involving only the US, we used our Concur Test instance to configure and test integrations from our HR system as well as from Fusion. These integrations include employee cost center and location lists, as well as project accounting lists and others.

We are considering moving forward to future implementations without a Test instance. These implementations will also mainly impact Concur through integrations.

Have any of you tried this? I'm concerned that integration testing will not be adequate if done in Production. One example is the need to place test employees in a 'Test Group' rather than their natural employee group. The next implementation will cover 8 countries, and this one example alone sounds so much more difficult and potentially confusing than using a Test instance.

However, perhaps I'm not seeing all the possibilities, so any advice or experiences you share will be appreciated. Thank you --

Re: Implementing ERP - Sandbox Pros and Cons

Hi,

I have always used the test environment for builds, changes, and implementations including integration testing. The test environment does cause some mauanl effort to test integrations but its well worth it. No one, Concur, or company admin is "messing with" production resources. Secondly, the test environment will offer limitations (as you prob. already know) such not able to kick off email notices etc... but you can kick off your own imports etc, which is nice.

Have you signed up for Web Services? If not, highly recommended as it gives you a level of piece of mind, you can set integration scchedules to almost real time, and it's easier than building staging tables etc....

Re: Implementing ERP - Sandbox Pros and Cons

First, I am assuming that you are on the Professional platform vs. Standard. In either case, you should check with Concur to review your options.

Depending on your Company structure, you would have different options.

Rlipsey64 is right on with test environments for software development.

Saying that, Concur does not normally provide a Test Environment. You would set up a Test Group with Test Employees (do not use real employees) and build out your Test environment: the test group is in your Production Site. Generally, the implementation starts using a TEST entity and then moves to a PROD with the PROD implementation./rollout. But a client can purchase a TEST environment unless Concur provided it with as a part of the sale.

Now you have special circumstances: Multiple Counrties. (consult your Concur). It is my understanding that you would get a Test group for each country. You would configure all aspects of Expense (policy, expense types, workflows, audit rules, etc) for each county including test group employees that have all of the natural employee group data, followed by user acceptance testing and signoff.

Then the last step is to move the TEST County to production users and update the production policy, expense types, workflows and audit rules required for the new county.

The “TEST” in PROD scenario does look “much more difficult and potentially confusing than using a Test instance” but actually requires less effort. One major factor that is present here is that the ERP is the same for all countries So the structure of the integrations is equal with the variance the country requirements.

From experience, this would be a Phase II rollout and may require a MOD to your contract for Concur Implementation support. Again check with Concur.