How To Fix PK343 - Status sequence does not apply to the one-card kanban

PK343 - Overview

• Message type: E = Error

• Message class: PK - Production - KANBAN

• Message number: 343

• Message text: Status sequence does not apply to the one-card kanban

What causes this issue?

You work with the one-card kanban system. In the control cycle, a value
has been entered in the
<DS:DE.PKLOG>Trigger Replenishment</> field and you have entered a
status sequence. This status sequence does not define that the status
<LS>WAIT</> is a mandatory or a "should" status.
However, in the one-card kanban, you must set the kanban container to
the status <LS>WAIT</> before it is set to <LS>EMPTY</>.

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?

Change your status sequence to ensure that the status <LS>WAIT</> is set
or change the master data of the control cycle so that you no longer
work with the one-card kanban system.

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 PK343 - Status sequence does not apply to the one-card kanban ?

  The SAP error message PK343, which states "Status sequence does not apply to the one-card kanban," typically occurs in the context of Kanban processing within SAP's Production Planning (PP) module. This error indicates that there is a mismatch between the status sequence defined for the Kanban and the one-card Kanban setup.
  
  Cause:
  
  
  Configuration Issues: The status sequence defined in the system does not match the requirements for a one-card Kanban. This can happen if the status sequence is not properly configured for the specific Kanban control cycle.
  Incorrect Kanban Control Cycle: The Kanban control cycle may not be set up correctly, leading to the system not recognizing the status sequence for one-card Kanban.
  Master Data Issues: The material master or the Kanban master data may not be correctly configured, leading to inconsistencies in the status sequence.
  
  
  Solution:
  
  
  Check Status Sequence Configuration:
  
  Go to the configuration settings for Kanban (Transaction code: SPRO).
  Navigate to Production > Kaban > Control