How To Fix PK336 - Data from status sequence and replmt strategy with SD are inconsistent

SAP Error Message - Details

• Message type: E = Error

• Message class: PK - Production - KANBAN

• Message number: 336

• Message text: Data from status sequence and replmt strategy with SD are inconsistent

What causes this issue?

You want to set a kanban from status FULL to WAIT or EMPTY.
You have entered a replenishment strategy in the control cycle, in
which you have chosen the process with SD scheduling agreement. For
this replenishment strategy, the status IN USE is mandatory. However,
you have entered a status sequence in the control cycle, which does not
provide the status IN USE as a mandatory status.

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?

You have two options:
Take the status IN USE in your status sequence as a mandatory status.
Go to Customizing for KANBAN. Here you can change the status sequence
under
<LS>KANBAN-> Status-> Define status sequence</>.
Delete the indicator <LS>Kanban with SD</> in your replenishment
strategy. Go to Customizing for KANBAN. Here you can change the
replenishment strategy under <LS>KANBAN-> Replenishment strategies</>.

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 PK336 - Data from status sequence and replmt strategy with SD are inconsistent ?

  The SAP error message PK336 indicates that there is an inconsistency between the data in the status sequence and the replacement strategy in the Sales and Distribution (SD) module. This error typically arises during the planning or execution of processes related to materials management, production planning, or sales and distribution.
  Cause:
  
  Inconsistent Data: The status sequence defined for a material does not match the replacement strategy that is set up in the system. This can happen if there have been changes to the status sequence or replacement strategy without proper updates to related configurations.
  Configuration Issues: Incorrect configuration in the material master or in the planning settings can lead to this inconsistency.
  Master Data Issues: The material master data may not be correctly maintained, leading to discrepancies between the status and the replacement strategy.
  
  Solution:
  
  
  Check Material Master Data:
  
  Go to the material master record (transaction code MM03) and check the relevant views (e.g., Basic Data, Sales, MRP) to ensure that the status sequence and replacement strategy are correctly defined.
  
  
  
  Review Configuration Settings:
  
  Use transaction code SPRO to access the configuration settings. Navigate to the relevant sections for Sales and Distribution and check the settings for status sequences and replacement strategies.
  Ensure that the status sequence is correctly assigned to the material type and that the replacement strategy is compatible with the status sequence.
  
  
  
  Update Inconsistent Data:
  
  If you identify any inconsistencies, update the material master or configuration settings accordingly. This may involve changing the status sequence or the replacement strategy to ensure they align.
  
  
  
  Check for Transport Issues:
  
  If the issue arose after a transport of configuration changes, ensure that all related objects were transported correctly and that there are no missing dependencies.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific error message PK336 for any additional guidance or updates that may be relevant.
  
  
  
  Testing:
  
  After making changes, perform tests to ensure that the error no longer occurs and that the system behaves as expected.
  
  
  
  Related Information:
  
  Transaction Codes: MM03 (Display Material), SPRO (Customizing), and possibly others depending on the specific context of the error.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Forums: Consider checking SAP Community or other user forums for similar issues and solutions shared by other users.
  
  If the problem persists after following these steps, it may be beneficial to consult with an SAP functional consultant who specializes in SD or MM for further analysis and resolution.