Symptom
You have performed the Revenue Recognition Run for the contract AAA (AAA represents the Contract ID) and Revenue Recognition run finishes with the below error message:
'Please create an incident, reason "An exception with the type CM_FIA_PERIOD_LOCK occurred, but was neither handled locally, nor declared in a RAISING clause"'
Environment
SAP Business ByDesign
Reproducing the Issue
-
Go to the Cost and Revenue work center.
- Go to the Revenue Recognition view and select the run in question.
- Click Log Result link.
- Navigate to Messages tab.
You can see the error message:
'Please create an incident, reason "An exception with the type CM_FIA_PERIOD_LOCK occurred, but was neither handled locally, nor decleared in a RAISING clause"'
Cause
You are working with a customized fiscal year variant. The error is triggered as the end date of Contract AAA is set to YYYY (YYYY represents Fiscal Year ID). However, the accounting periods of fiscal year YYYY are not maintained in the Other Fiscal Year fine tune activity.
When working with a customized fiscal year variant then all accounting periods until the end date of the contract must be maintained in Fine Tuning.
Resolution
You must maintain the period details for the used fiscal year variant for all accounting periods until the end date of contract AAA:
- Go to the Business Configuration work center.
- Go to the Overview view.
- Access the Other Fiscal Year fine tune activity.
- Search for the Fiscal Year Variant for the relevant Company and Set of Books.
- Go to the Period Details tab.
- Maintain the period details to include the future end date of the contract. For example if you contract End date is 31.07.2028, maintain Fiscal and period details up to this date.
Once you have maintained the above information complete a new Revenue Recognition Run.
Keywords
Revenue Recognition run, Contracts, CM_FIA_PERIOD_LOCK, Variant Fiscal Year , KBA , contracts , revenue recognition error , exception with the type cm_fia_period_lo , SRD-FIN-COR , Cost & Revenue , How To