How To Fix WXP567 - Unregistered type &1 periodicity (fiscal year variant &2)

WXP567 - Overview

• Message type: E = Error

• Message class: WXP - Retail Planning

• Message number: 567

• Message text: Unregistered type &1 periodicity (fiscal year variant &2)

What causes this issue?

You want to use the BW system to procure actual data. To do this, each
periodicity used in the planning scenario must be identified as being a
valid periodicity when using info cubes.
This is not applicable for period category &V1& (for period category P:
with fiscal year variant &V2&).

System Response

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

How to fix this error?

Go to maintenance for BW-specific settings at scenario level and
compare the planning scenario fields using the <PF>Compare scenario
fields</> function. This automatically registers the periodicities that
are used if at least one planning step for the relevant periodicity is
to supplied with data from an info cube.
You must configure your system to enable actual data from a info cube
to be used. To do this, go to <ZH>Basic Settings</> for the planning
step in question.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WXP567 - Unregistered type &1 periodicity (fiscal year variant &2) ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  WXP567 Unregistered type &1 periodicity (fiscal year variant &2)
  
  Meaning / 
  Cause:
  This warning message indicates that the system encountered a periodicity type (period type) that is not registered or defined for the specified fiscal year variant. In SAP, fiscal year variants define how the fiscal year is structured, including the number and type of posting periods and special periods.
  
  &1 = The unregistered periodicity type (e.g., "01" for monthly, "02" for quarterly, etc.)
  &2 = The fiscal year variant in which this periodicity type is missing or not defined.
  
  This usually happens when a custom or non-standard periodicity type is used in a process (such as posting, reporting, or period-end closing), but the fiscal year variant does not have this periodicity type configured.
  
  Common Scenarios:
  
  Custom fiscal year variants missing certain period types.
  Using a periodicity type in a report or transaction that is not supported