2420034 - SII retroactive first term 2017. XBLNR: duplicate info?

01.01.2017 to 30.06.2017 is a period "affected" by SII (Immediate Supply of Information), because even if SII comes into place on July first 2017, there is a requirement (for those Companies subject to SII), to send data from invoices posted on the first half of 2017, subsequently, between 01.07.2017 and 31.12.2017.

Till 01.01.2017 you might be also subject to other informative declarations such as model 340, that reads the vendor invoice number from field XBLNR (Reference Document Number) of table BKPF (Accounting Document Header).The vendor invoice number provided by vendors not using SAP, might be longer than 16 characteres. (XBLNR length is just 16). SAP announced in note 2409025 that the solution for SII, will provide with further options to read the vendor invoice number also from other fields of table BKPF besides than from XBLNR.

You want to know if opting for storing the vendor invoice number in some other field as of january 2017,  would it be required to continue storing also the vendor invoice number in field XBLNR at BKPF from January 1st to June 30th 2017.

SAP ECC 6 EhP 0 (SAP Netweaver 700)
S/4HANA 1511

Sistema Inmediato de Información, Immediate Supply of Information, SII, Spain, Spanish, localized solution, localization, country specific,  ID-FI-ES, SAP for Me. Real Decreto 596/2016, de 2 de diciembre, "Los sujetos pasivos que apliquen el SII desde el 1 de julio de 2017 estarán obligados a remitir los registros de facturación del primer semestre de 2017 en el período comprendido entre el 1 de julio y 31 de diciembre de 2017." January, June, July, December. Vendor Invoice Number. , KBA , suministro inmediato de información , XX-CSC-ES-FI , use FI-LOC-FI-ES , XX-CSC-ES , Spain , Problem