Concur and SAP Integration Issues

[Former Member]

Hi everyone,

I am new to Concur and I am in charge of the user support.

We have the following recurring issues:
- Expense reports sent for payment by Concur are blocked / cannot be posted in SAP
- Expense reports sent for payment cannot be found in SAP

At present, I have identified two causes:
- Tax rates and/or tax amounts were changed manually by an accountant (causing a mismatch with the tax code that remains unchanged)
- Invalid values in the expense reports (e.g. Vendor ID=TBC or ZZZ...)

Could you please give me other possible causes? That will help me to further investigate.

Thanks in advance. Regards.
Victor

[cesnjuli2 · Accepted solution]

Hi,

Are you using SAE and middleware to convert the file into IDOC?

Basically with SAE there are 3. places where the problem may occur if you are using SAE and middleware.

1. File transfer from Concur to middleware has not happened (MFT problem)

2. Middleware mapping failed

3. IDOC failed due to incorrect master data and was blocked without posting

[Former Member]

Thank you Julius.

That's helped a lot!

Regards,
Victor

[former_member18923]

Hi Victor,

Hope you plugged & matured enough fixing CONCUR Posting issues.

- Expense reports sent for payment by Concur are blocked / cannot be posted in SAP - for eg: emp left, GL code might change, submission currency & posting currency different - CTE_SETUP is good place to check on error descriptions
- Expense reports sent for payment cannot be found in SAP - try changing the CTE_SETUP variant dropdowns;

[Former Member]

Hi Julius,

Yes, we are using SAE and SAP PO middleware to convert the file into IDOC.

It should be the third one but at present we cannot identify what data is incorrect.

Thank you for your help! That helps a lot.
Victor

[cesnjuli2]

Depends on your mapping logic, but normally users should be able to look for an idoc based on expense report key or reportID. Failed IDOCs usually have error messages, that may not necessarily be 100% correct, but gives a good start. From my experience most common problems are: missing employee vendor record, missing employeeID (PERNR), cost center has been blocked for posting, incorrect/incomplete GL account setup, validations.

These are the transactions you can use to check IDOCs, but I would recommend to learn your mapping logic first:

1. WE05 - IDoc overview
2. BD87 - Inbound IDoc reprocessing
3. BD88 - Outbound IDoc reprocessing
4. BDM2 - IDoc Trace
5. BDM7 - IDoc Audit Analysis