Solution : https://service.sap.com/sap/support/notes/19861 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues when unexpected results occur from validations, substitutions, or rules created in an SAP system. Possible causes include errors in logical statements, missing field data, uncommented lines in rule editor, pre-evaluated field values, inactivity of rules for specific applications, or absence of generated source code. Remedies involve using simulation tools and TRACE function to check rule logic and execution. Closing comments, activating rules, setting breakpoints in specific function modules for debugging, and executing correction programs are advised. Contacting SAP is recommended if problems persist after these measures.
Key words :
generated source code belonging, generated abap/4 code, company code level, entering master data, additional key words, attached advance correction, execute program rgugbr00, entire rule entered, function module g_vsr_validation_call, function module g_vsr_substitution_call
Related Notes :
| 124745 | Invoice verification:Transfer of PO text to CO doc |
| 123218 | Validation/substitution BSEG-VBUND FI callup point 2 |
| 121857 | No substitution, although prerequisite met |
| 105534 | Coll.note:Trace/simulation of validation/substitutn |
| 100261 | Field contents are deleted by substitution |