Here are specific SAP transaction codes (Tcodes), configuration paths, and step-
by-step procedures to help you correct revenue postings and manage contract/WBS
updates in SAP Revenue Accounting and Reporting (RAR):
Key SAP RAR Transaction Codes for Revenue Posting and Corrections
Tcode Description
RARCONFIG Configure SAP RAR system (initial setup, accounting principles, contract
categories, etc.)
RARMD_MAIN Maintain master data for customers, contracts, and revenue
recognition
RARCMOD Handle contract modifications and adjust revenue recognition
accordingly
RARPOST_SIM Simulate revenue recognition posting to verify correctness before
actual posting
RARANALYZE Analyze simulation results and revenue data for accuracy
RARPOST_EXEC Execute actual posting of revenue recognition documents
FARRIC_RR_CORR Correction of revenue postings after transfer date (used in migration or
error correction)
VF47 Verify inconsistencies in revenue tables
FARR_CONTR_CHEC Validate contracts and performance obligations consistency
K
FARR_CONTR_MON Monitor contracts and performance obligations
FBL3N / FB03 Review accounting entries generated by revenue recognition
Configuration Path for SAP RAR (IMG)
Access SAP IMG via transaction SPRO
Navigate to:
Financial Accounting (New) → Revenue Accounting and Reporting (FARR_IMG)
Key configuration activities include:
o Activation of revenue accounting item classes and interface generation
o Setup of accounting principles and company code assignments
o Creation of contract categories and performance obligation (POB) types with
number ranges
o Maintenance of BRF+ applications for business rules in RAR
o Account determination for RAR-specific P&L and balance sheet accounts
Step-by-Step Procedure to Correct Revenue Postings in RAR
1. Simulate Revenue Posting
o Use RARPOST_SIM to simulate revenue recognition postings. This helps
identify errors before actual posting.
2. Analyze Simulation Results
o Run RARANALYZE to review the simulation output and detect inconsistencies
or incorrect postings.
3. Execute Revenue Posting
o Once simulation is verified, execute actual posting with RARPOST_EXEC.
4. Identify and Correct Errors
o If errors occur after posting (e.g., due to contract/WBS updates post-invoice):
Run FARRIC_RR_CORR to correct revenue postings after
transfer date or to fix inconsistencies.
Use VF47 to check for inconsistencies in revenue tables.
Validate contracts using FARR_CONTR_CHECK and
monitor with FARR_CONTR_MON.
5. Reverse and Repost if Needed
o For reversing and reposting revenue postings, use the UI or program described
in SAP Help for reversal and reposting of revenue postings (refer to SAP Note or
documentation). This process generates a run ID for tracking.
6. Review Accounting Entries
o Use FBL3N or FB03 to verify the accounting documents generated by the
revenue recognition process.
Additional Tips
Avoid Contract/WBS Updates Post-Invoice: Always try to prevent contract or
WBS changes after invoice posting to avoid RAR inconsistencies.
Use Change Management: Restrict changes via authorizations and monitor
changes with audit logs.
Consult SAP OSS Notes: For specific issues, check SAP OSS Notes such as
2715378 for migration and correction guidance.
Issue Summary
You mentioned that after invoice booking, there is a contract update for WBS in SAP
Revenue Accounting and Reporting (RAR), which is causing a mess in RAR booking.
Understanding the Problem
In SAP RAR, revenue recognition is tightly linked to contracts and their associated objects
such as WBS elements. If an update to the contract or WBS happens post-invoice
booking, it can cause discrepancies or inconsistencies in revenue recognition postings,
leading to errors or incorrect revenue postings.
Possible Causes
1. Post-Invoice Contract Changes: Modifying contract data or WBS elements after
invoice posting can cause RAR to recalculate or adjust revenue postings incorrectly.
2. Incorrect Integration Settings: The integration between SAP PS (Project System),
FI (Financial Accounting), and RAR might not be properly configured, causing data
inconsistencies.
3. Timing Issues: Changes made after invoice posting but before revenue recognition
is complete can disrupt the RAR process.
4. Master Data or Customizing Errors: Incorrect master data or configuration in
RAR or PS modules can lead to booking issues.
Corrective Measures
1. Avoid Post-Invoice Contract/WBS Updates
Best Practice: Once the invoice is posted and revenue recognition started, avoid
making changes to the contract or WBS elements linked to that invoice.
If changes are absolutely necessary, consider reversing or adjusting the invoice and
revenue recognition before updating the contract or WBS.
2. Review and Correct Integration Settings
Check the integration points between SAP PS, FI, and RAR.
Ensure that the contract update process is aligned with RAR requirements and that
no unauthorized changes occur post-invoice.
Validate the configuration in transaction codes such as RARCONTRACT or related
customizing paths.
3. Use Proper Change Management Procedures
Implement controls to restrict contract or WBS updates after invoice posting.
Use change documents and audit logs to track modifications.
Train users on the impact of post-invoice changes on RAR.
4. Reconcile and Correct Existing Mess
Identify affected contracts and WBS elements with inconsistent RAR postings.
Use SAP standard tools or reports to analyze revenue recognition errors.
Reverse or adjust revenue postings as per SAP guidelines.
If needed, consult SAP Notes or OSS messages related to RAR and contract updates.
5. Consult SAP Support or Expert
If the issue persists or is complex, raise a support ticket with SAP, providing detailed
logs and error messages.
Engage SAP PS and RAR functional consultants to review your process and
configuration.
Summary
Avoid contract/WBS updates after invoice posting to prevent RAR booking issues.
Review integration and configuration settings between PS, FI, and RAR.
Use proper controls and procedures for contract changes.
Reconcile and correct existing errors carefully.
Corrective Measures for RAR Booking Issues After WBS/Contract
Update
When a contract or WBS (Work Breakdown Structure) update occurs after invoice booking
in SAP Revenue Accounting and Reporting (RAR), it can result in inconsistencies or errors
in revenue recognition. Below are the recommended corrective measures and best
practices to address and prevent such issues:
1. Avoid Post-Invoice Contract/WBS Updates
Do not make changes to contracts or WBS elements once an invoice has been
posted and revenue recognition has begun.
If changes are unavoidable, first reverse or adjust the invoice and any related
revenue recognition postings before updating the contract or WBS.
2. Review and Correct Integration Settings
Check the integration settings between SAP Project System (PS), Financial
Accounting (FI), and RAR to ensure proper data flow.
Confirm that the contract update process is compliant with RAR requirements and
does not allow unauthorized changes after invoicing.
Validate configuration using relevant transaction codes (such as those related to
RAR contracts and customizing).
3. Implement Change Management Controls
Restrict the ability to update contracts or WBS elements after invoice posting
through system controls and user authorizations.
Use change documents and audit logs to monitor and track any modifications.
Train users on the impact of post-invoice changes on RAR processes.
4. Reconcile and Correct Existing Errors
Identify all contracts and WBS elements affected by inconsistent RAR postings.
Utilize SAP standard tools and reports to analyze and pinpoint revenue recognition
discrepancies.
Reverse or adjust incorrect revenue postings according to SAP guidelines.
Consult SAP Notes or OSS messages for specific guidance on RAR and contract
update issues.
5. Seek Expert Assistance if Needed
For complex or unresolved cases, raise a support ticket with SAP, including detailed
logs and error messages.
Engage SAP PS and RAR consultants to review business processes and system
configuration.
Summary Table: Actions and Recommendations
Step Description
Avoid Post-Invoice Do not update contracts/WBS after invoice posting; reverse/adjust postings if
Changes changes are needed.
Review Integration Ensure correct integration and configuration between PS, FI, and RAR.
Settings
Implement Controls Restrict post-invoice changes; use audit logs and user training.
Reconcile Errors Identify and correct inconsistent postings using SAP tools and guidelines.
Consult Experts Contact SAP support or consultants for unresolved or complex issues.
