Solution : https://service.sap.com/sap/support/notes/1125456 (SAP Service marketplace login required)
Summary :
SAP Note covers service-based revenue recognition adjustment, addressing missing functionalities with new implementations in sales documents for service-related items. Specific customer events now trigger revenue recognition, necessitating updates to event types ('X', 'Y', 'Z') in item categories through transaction OVEP or Customizing menu. The BAdI ‘BADI_SD_REV_REC_PODEV’ uses the event data to update and unblock revenue lines in VBREVE, controlled by user statuses updated via Customizing transaction BS02. Further references to existing notes detail process workflows and event-driven revenue recognition scenarios, enhancing user guidance on these modifications.
Key words :
field ----------- -------------- --------------- ------------ vbeln vbeln posnr posnr revevdat rr_revevdat revevdocn rr_revevdocn revevdocni rr_revevdocni cancel cancelled quasu rr_quasu wrbtr wrbtr rrpodevcom slsun waerk waerk rrpodevcust waerk revpoblck rr_revpoblck eindt eindt 3, status short text ltext initial low high pos, worklistvf45 - revenue recognition revenue reportvf46 - revenue recognition cancellationfor, communication structure podev-customer specific enhancement category, customer-specific podev data- vbeln, customer-specific eventadditional information----------------------------existing import parametersstructures, component component type reference table ref, distribution document number- posnr, customer-specific event xrevenue event_____'y', customer-specific event yrevenue event_____'z'
Related Notes :
| 1468536 | Subsequent corrections for event control/revenue recognition |
| 1120297 | Revenue recognition by acceptance date |
| 1025066 | Revenue recognition by proof of delivery (POD) |
| 1000830 | Revenue recognition through incoming invoice (third-party) |
| 781192 | VF42 - Updating sales and distribution documents |
| 780993 | Updating revenue recognition data in sales document |