参考字段XBLNR只能个支持16位,没有办法支持20位的数电发票号码。只能增强了。
目前还是无解!觉得SAP还是不太重视中国的用户!
Do you need to extend RBKP-XBLNR to handle more characters? You’re not alone. | SAP Blogs
SAP Knowledge Base Article, Version: 3, Released On: 26.09.2023
You would like to increase the lengths for XBLNR due to business requirement. For example, having INVFO-XBLNR being filled with 20 characters or more in order to make the reference field being unique. You would like to increase the lengths of XBLNR for invoice duplication check.
Go to transaction code MIRO and input the posting date and reference date.
This is standard behavior.
Since ERP is being built up, reference document number (XBLNR) can only handle 16 characters.
The reference document (XBLNR) is not only defined/designed in MM area, such as invoice headers table RBKP, FI header table BKPF, (index for vendor validation of double document) BSIP, purchase order history table EKBE, goods receipt header table MKPF and other applications as well. As the result, for this matter, we can not provide system change, as it would be caused un-expect effect not just from MM, FI area, also other application processes.
For duplication check, you may consider to fill up the "TEXT" field and develop your own program under FM MRMBADI_HEADER_CHECK in order to meet up with your requirement. However, this BadI is only valid from MM invoice process. Please notice that this is a workaround and SAP will not provide support for this custom solution.
Blog: Do you need to extend RBKP-XBLNR to handle more characters? You’re not alone.
305201 Description: Check for duplicate invoices
213929 MIRO: Check duplicate invoices does not work
924769 MIRO: M8 108 is not issued for archived FI documents
XBLNR, RBKP, BSIP, BKPF, EKBE, MRMBADI_HEADER_CHECK, duplication check, INVFO-XBLNR, MIRO, MIR7, length