Skip to Content

COBK-REFBN being overridden by external Concur document

We are in the midst of a Concur implementation, and are seeing an impact with respect to COBK-REFBN field. Currently, when we use an ER document type in our productive system, BKPF-AWKEY is populated with the accounting doc + comp code + year, for example 1900663472ZA012018.

With the Concur implementation, we are seeing the following behaviour in our DEV system. The BKPF-AWKEY is populated with the external Concur document, for example 1483 1 1. This in turn populates COBK-REFBN with 1483 1 (takes 10 characters). It's worth noting that COBK-AWORG is also affected, and now carries the remaining character from BKPF-AWKEY, for example 1.

As we have a mature environment, we have relied for many years on the data in COBK-REFBN being the accounting document in alignment with COBK-REFBT being equal to "R". I'm interested to know if anyone has encountered this, and how they handled the population of COBK-REFBN for an FI document sourced from an inbound Concur document (e.g. doc type ER where BKPF-AWTYP = CTE).

Appreciate any thoughts or guidance.

Thanks,

Jason

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • May 23 at 03:38 PM

    Example of differences that I am referring to shown in the attached document. Again, appreciate any input that someone may have.

    This type of analysis was based on previous post where Jason Shao (SAP) had analyzed - Archived Post

    dev-with-concur-cte.jpg

    prd-without-concur.jpg

    Thanks,

    Jason

    Add comment
    10|10000 characters needed characters exceeded