How to identify a faulty line when posting to SAP is blocked

[AntonFarenyk]

Hello,

We use Concur Expense with SAP ECC6. We use native integration ICS. When a report gets blocked for posting we can see it in CTE_DOC_MONI or CTE_SETUP transactions. Usually an error is in one of the line items of report, e.g. tax related. One example could be Expense Report 12345 / 1 of system Concur could not be posted. Error code CTE_FND_POSTING010 with Tax entry not possible in this item error code FF724. But then in Concur a report may have 20 lines and it is difficult to identify which exact line is causing a posting problem. How do you approach such cases?

We can use ABAP debugger and for some cases are able to put a break-point, e.g. in class CL_CTE_FIN_POSTUC_SINGLE_TAX, but it is very much dependent of error message and takes a LOT of time and special access in productive ECC6 environment. There must be an easier way. 

Thank you!

[cjmarimo]

Hello @AntonFarenyk 

Have you checked the application log in transaction SLG1 in SAP ECC?

BR,

cj

[AntonFarenyk]

Thank you for your answer. There is a small typo in my initial post, the class/interface name is actually CL_CTE_FIN_POST_UC_SINGLE_TAX. But for SLG1 this class name is useless, because the program punched in log is CTE_FIN_PROCESS_POSTING_DOCS.

Anyways,  SLG1 gives exactly the same information as in Document protocol within CTE_POST_MONI. For my External ID (which is Report ID in Concur) I have exact same information as in CTE_*

No line item or anything useful to identify which exact line item of this expense report is causing this error. 

[cjmarimo]

Hello @AntonFarenyk 

Occasionally, some reports throw errors, almost 100% of the time because the Business Partner/Employee (BP) has posting blocked. Normally, I see the document number in the CTE_POST_MONI file in ECC. With that document number, I go to Expenses->Processor->Process Report in Concur, and within the report, I check the Details->Report->Audit Trail. The error message indicates that the BP is blocked from postings, but I'm not sure if it would show the affected line item in your case.

Br,

cj

[AntonFarenyk]

BP blocked is an easy case because it affects the whole report which could not be posted. We have similar cases when say Cost centre is blocked ,  WBS element is blocked etc.  Those are easy because error is self-explanatory. But when TAXES in ONE item are blocking the posting, THAT is difficult to catch, thus my question. There MUST be easier way in CTE_* to find out which item is in error.  In debug it takes often several tries to get to the line item, doing Feedback loop, Recall-Submit in Concur etc. It is too cumbersome and time-consuming. 

[cjmarimo · Accepted solution]

Hello @AntonFarenyk 

One possible approach would be to create a custom Z table in ECC to log the processing steps. This would allow you to trace the workflow and quickly identify which specific line item triggered the error.

BR,

cj

[AntonFarenyk]

Thank you! This is a very interesting idea. I’ll review the available enhancements and explore further. Ultimately, though, I believe it’s up to SAP to develop this functionality and add more details to the document protocol screen.

[cjmarimo]

Hello @AntonFarenyk 

Sure. I agree with you that SAP should provide a more detailed log to facilitate error identification. Since this relates to system design, could you please create an improvement request in Customer Influence and share the link with us? I would like to vote for it.

Br,

cj

[MicheleW]

I think the solution is easier than you think. We saw this error when testing our ICS and the root cause was this flag was not checked in the GL master record in ECC. (Transaction FS00, Posting without tax allowed)

Most of us probably don't use too many different GL accounts for expense reports. Take a quick look in your SAP system at the contents of field SKB1-XMWNO to see if any of your expense accounts are missing the X. Check the box, then recall and resubmit the expense report in Concur. No need to know which line item is the offender necessarily. 

[AntonFarenyk]

Hello Michele,

Thank you for your answer. We’ve been running ECC6 with ICS since early 2017, and those kinds of master data issues were ironed out in the early days.

The example above was just one case with one tax authority, and that issue was resolved—it was, as usual, within the ER in Concur.

However, users keep getting creative:

• City of purchase wrong or in the wrong country
• Mileage linked to the wrong city
• Selecting taxable where no tax applies
• Choosing No tax receipt while providing one and claiming taxes
• Entering wrong VAT amounts in the wrong field

I could go on…We only catch posting errors, like in my case above when ECC tax code does not correspond to information coming from Concur. And because we deal with a US, Canada (with two layers of taxes), Great Britain VAT and mileage, Germany with VAT and per diems, and other flows, it’s extremely difficult to correct ERs without more details in the document protocol. Thus - recall-resubmit- ABAP debug is my only way for some of those cases. 

What I really wish for is to have some specifics about the line item blocking the posting in the document protocol—such as amount, expense type, etc.