How To Fix ACC_AA243 - Cmpy Code &4: Posted period &1 does not match fiscal year variant &2

SAP Error Message - Details

• Message type: E = Error

• Message class: ACC_AA - Message Class for Function Group ACC_AA

• Message number: 243

• Message text: Cmpy Code &4: Posted period &1 does not match fiscal year variant &2

What causes this issue?

The field <LS>Period of Last Depreciation Posting</> for area &V1& does
<ZH>not</> match the fiscal year variant &V2& in accounting principle
&V3& in company code &V4&.

System Response

The settings <ZH>cannot</> be saved.

How to fix this error?

Change the field <LS>Period of Last Depreciation Posting</>.
Make sure that the fields <LS>Period of Last Depreciation Posting</> and
<LS>Fiscal Year of Last Depreciation Posting</> match for all posting
areas of a ledger group. Make sure that the fiscal year matches the
transfer year and the period is smaller/equal to the transfer period,
taking the fiscal year variant into account that is relevant for the
ledger group from an asset accounting point of view.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ACC_AA243 - Cmpy Code &4: Posted period &1 does not match fiscal year variant &2 ?

  The SAP error message ACC_AA243 indicates that there is a mismatch between the posted period and the fiscal year variant for a specific company code. This error typically occurs when you attempt to post an asset transaction in a period that is not open for posting according to the fiscal year variant settings for the company code.
  Cause:
  
  Closed Posting Period: The period you are trying to post to is closed in the fiscal year variant settings.
  Incorrect Fiscal Year Variant: The fiscal year variant assigned to the company code does not match the period you are trying to post to.
  Configuration Issues: There may be a misconfiguration in the fiscal year variant settings or the posting periods.
  
  Solution:
  
  
  Check Posting Periods:
  
  Go to the transaction code OB52 (Maintain Posting Periods).
  Verify that the period you are trying to post to is open for the relevant company code and fiscal year variant.
  
  
  
  Review Fiscal Year Variant:
  
  Check the fiscal year variant assigned to the company code using transaction code OB37 (Define Fiscal Year Variant).
  Ensure that the fiscal year variant is correctly configured and that the periods align with your posting requirements.
  
  
  
  Adjust Posting Periods:
  
  If the period is closed and you need to post to it, you can temporarily open the period in OB52. However, be cautious with this approach, as it may affect other transactions.
  
  
  
  Check Asset Transaction:
  
  Ensure that the asset transaction you are trying to post is valid for the specified period and complies with the company code's fiscal year settings.
  
  
  
  Consult Documentation:
  
  If you are unsure about the fiscal year variant settings or how to adjust them, refer to SAP documentation or consult with your SAP administrator or finance team.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  OB52: Maintain Posting Periods
  OB37: Define Fiscal Year Variant
  AS01: Create Asset
  AS02: Change Asset
  AS03: Display Asset
  
  
  
  Fiscal Year Variant: This defines how the fiscal year is structured, including the number of periods and special periods.
  
  
  Company Code: This is the smallest organizational unit for which a complete self-contained set of accounts can be drawn up.
  
  
  By following these steps, you should be able to resolve the ACC_AA243 error and successfully post your asset transaction.