Default Exception Code#CONOAPPR provided by Concur Expense?

[rkushwah]

Hi
Can we de-activate the Default Exception: Code: CONOAPPR, Level: 2147483647; No approvers were found for cost object...provided by Concur Expense?

Rohit

[PoojaKumatkar]

Hi @rkushwah ,

All of these are system-generated exceptions, and there are no audit rules associated with them. Therefore, it is not technically feasible to deactivate the rule or prevent these exceptions from being generated when no CO approvers are configured.

The only available option is to maintain a CO approver for all cost objects.

Attaching below support article for your further reference:

Article Number	000062637
Title	Why am I seeing the level 2147483647 on an exception?
Details	I went to Expense Admin > Exceptions and found some exceptions with the level 2147483647, while I was under the assumption that they should only go to 99. Is it a bug? If not, what is the reason for that?
Resolution/Answer	If you go to Administration > Expense > Exceptions and find an exception with level 2147483647, this should mean that this is a system exception. That means it cannot be modified and also that it doesn't need to have any audit rules connected to it in order to be active.
Cause	System exception.

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

[rkushwah]

Thanks @PoojaKumatkar. But this expection create confusion with the employees however there is no COA required in particular report. So is there any way to fix it?

[PoojaKumatkar]

Hi @rkushwah ,

Is it possible for you to provide your workflow screenshot or attachment.

There must be COA step configured in your workflow where approver is not currently configured and that's why system is triggering this error message. 

If step is added in your workflow then you must configure all COA approvers to avoid this error.

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

[KevinD]

@rkushwah what is the name of the report and could you send me the employee's name in a private message who owns this report. I would like to take a look and see what is happening. The exception shouldn't be triggered if there isn't a COA step in the workflow and the user didn't cross charge any expenses. 

I'll await you private message with details I've asked for.

[rkushwah]

Hi @KevinD Thanks for your information. I checked the Workflow and found the COA step however there is No COA approver setup which cause this exception. We have the scenarios where report of the Employee doe'snt need to stop on COA step but it does due to COA step. So to avoid confusion, we want to de-activate but as per the @PoojaKumatkar reply it's system generated exception and can't be deactivated.

Is it possible to  change the Icon to Yellow rather then Red Flag to avoid confusion to employee?

Rohit

[PoojaKumatkar · Accepted solution]

Hi @rkushwah ,

Technically it’s not possible to change exception from hard stop to warning as there is no scope for us to update the rule. 

Currently you have below two options:

Role Required - Expense Configuration Administrator (Unrestricted)

1. Remove COA step if it's no longer required in workflow.

2. Create dummy profile or use admin profile and configure in COA section at global folder level. After that in workflow at COA step write below skip condition:

If employee: employee Id
Is Not
Value: Blank
Then
Action: Skip

With this, rule will be applied to all employees and the COA step will be skipped. Since a dummy profile has been assigned as the COA approver, the system will allow users and approvers to submit and approve reports without triggering the hard-stop message. This is a workaround solution intended solely to bypass the COA approval step.

In case if you don’t have required access then you may raise a support case with Concur and get required changes done.

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

[KevinD]

@rkushwah based on what you have said, which sounds like there are some occasions when COA is needed, you should create a skip step in your workflow to Skip COA if it isn't needed. 

Likely you'll need to submit this to Concur Support unless you have someone at your company with unrestricted access.