These notes are prerequisities to see and be able to activate the field.

2283397 – Country-specific VAT implementations.

2256603 – Country-specific VAT implementations.

2263523 – FB09: Feld BKPF-REINDAT ist nicht änderbar.

2240873 – Country-specific VAT implementations.

2258535 = Country-specific VAT implementations 5.

2259658 = Country-specific VAT implementations: UDO 5.

2244343 = Country-specific VAT implementations 4.

2255858 = Country-specific VAT implementations: UDO 4.

2250498 = Country-specific VAT implementations: UDO 3 (Only for DE – optional, but it can’t be implemented after 2255858 note!).

2231165 – Country-specific VAT implementations 3.

2221947 = Country-specific VAT implementations 2.

2237363 = Country-specific VAT implementations: UDO 2.

2241853 – RFUMSV00(CZ): Combining entries for input tax.

2213503 – Country-specific VAT implementations.2172952 – Enhancing the structure BAPIVBRKOUT.2219418 Country-specific VAT implementations: UDO.Which listed following notes to be implemented: Same applies to REINDAT field – it was activated for usage of Czech companies due to VAT Ledger requirements by note:Ģ193486 – FAQ /regular update/ for Legal Change CZ VAT Ledger Statement for 2016 The question is how to make it visible? PrerequisitesĪs you know the fields in document header are controlled in different places, mainly by coding – there is no field status variant available like it is for posting lines. However if you look in to BKPF table then you will spot the receipt date available in form of REINDAT field:

VAT Date (if activated in company code).However hardly anybody knows that the same date can be stored in non-OCR scenario – this is because the field Invoice Receipt Date is not visible in any of FI/ LIV transactions by default settings. Many of the customers use OCR solutions like VIM where incoming invoice data is stored including the date of invoice receipt.

Garmin activation code without receipt