Concur Production Only Setup – Integration Testing & Risk Concerns (S/4HANA)

[rjain]

As part of our ongoing SAP S/4HANA implementation, we are integrating SAP Concur for expense management and financial postings into S/4.

Currently, we understand that only a Production instance of Concur is being provisioned and most of the client go with it, with no dedicated test (PSE) environment available for integration and validation activities.

This raises concerns from a Finance and SAP integration standpoint, particularly around:

• Performing end-to-end integration testing (SAP Financial Connector, IDocs/APIs, FI postings)
• Ensuring no impact to live financial data in S/4HANA during testing
• Managing test data vs. production data segregation
• Validating approval workflows and user scenarios without affecting real users
• Establishing a controlled regression testing approach post go-live

Given the complexity of the S/4HANA finance design, testing directly in a Production Concur tenant does it introduces risk?

Our goal is to ensure we fully understand the recommended approach, controls, and limitations in this setup so we can make an informed decision without introducing unnecessary risk to go-live.

[cjmarimo]

Hello @rjain,

It is not recommended to perform tests directly in Production without proper controls. It is preferable to work with test users, independent workflows, and non-productive data, as there is a risk of impacting financial data, FI postings, or real users.

Another option is to use a sandbox environment, where testing can be carried out safely without affecting the production system.

In our case, we use the professional version of Concur and have dedicated test users.

In User Administration, the “Test User” flag can be activated. In the "Employee ID" field, we enter a BP number from the SAP ERP test environment, which allows us to correctly link it to that environment.

User Details-Employee ID                   User Details-Test User

I hope this answers your question. ✔️

Best Regards,

CJ

[KevinD]

@rjain I echo what @cjmarimo said, Test Users, Test Users, Test Users. This is one of the exact reasons why we have the Test User option is for testing audit rules, workflows, email reminders, etc. without the risk of mixing in real data. 🙂