Solution : https://service.sap.com/sap/support/notes/117189 (SAP Service marketplace login required)
Summary :
If you implement the fields "Order type (KOMK-AUDAT)" and "Sales document type (KOMK-AUART_SD)" in the pricing of the billing document in SAP, unexpected outcomes may occur during navigation to the header condition screen or upon saving. Particularly in collective batch processing modes like VF04 or VF06, using these fields in pricing formulas can cause issues due to incorrect data interpretation when the sales order context is unavailable. Currently, no standard solution exists; modifications via consulting are recommended. Ensure to avoid data fetching that affects system performance, such as through the USEREXIT_PRICING_PREPARE_TKOMK if reviewing sales order data.
Key words :
'edit billing due list', system triggers document pricing, 'create batch jobs, - sales document type, sales order data, sales order date, header condition screen, fields- order type, billing document, sales order
Related Notes :
| 1391347 | KOMK-AUGRU in the billing document |
| 1018640 | Incorrect access to sales document data |
| 410579 | FAQ: Rebate processing |
| 391314 | Missing billing documents or conditions in rebate |
| 170183 | |
| 130417 | Pricing preparation in billing document (user exit) |
| 111813 | Billing doc: Collective run differs from individual creation |
| 39818 | Condition formula and user exit in billing doc. |