Symptom
You are creation such a purchasing document (purchase order, scheduling agreement, contract, request for quotation), in which the S/4hana output control (a.k.a. BRF+ output) logic is used for output handling.
You setup the document's number assignment in a way that a special character also included in its number, or the document's number has external number range, namely the document number is defined by you directly.
You notice that in such numbered document no output determined from OPD transaction's BRF+ rule set, and/or you observe "Uncaught exception" ABAP dump from /BOBF/CX_FRW_CONTRCT_VIOLATION (mainly after reopening the document and trying to save again):
But if you use such a document numbering in which such character(s) is not there then the output determination happens without issues.
Read more...
Environment
SAP S/4Hana On-Premise and Public Cloud
Product
Keywords
BRF+ rule role BRFplus BOBF CL_APOC_OR_V_APPL_OBJECT_ID /BOBF/IF_FRW_VALIDATION~EXECUTE NAST output document numbering EBELN document number belegnummer belegart purchase order PO SA scheduling agreement OPD contract request for quotation RFQ , KBA , MM-PUR-GF-OC , Message determination and printing , CA-GTF-OC , SAP S/4HANA output management , BC-SRV-BR , BRFplus - ABAP based Rule Framework , MM-FIO-PUR-PO-OM-2CL , Purchase Order Output Management (Public Cloud) , BC-SRV-BRF , Business Rule Framework (For BRF+, use BC-SRV-BR) , MM-FIO-PUR-PO-OM , Purchase Order Output Management , MM-PUR-GF-OC-2CL , Message determination and printing (Public Cloud) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.