How To Fix PK335 - System will find no message records for a JIT call

PK335 - Overview

• Message type: E = Error

• Message class: PK - Production - KANBAN

• Message number: 335

• Message text: System will find no message records for a JIT call

What causes this issue?

You have selected a process that triggers material replenishment per JIT
call (summarized JIT call, sequenced JIT call). The release of these JIT
calls is controlled via message management.
The system cannot generate a message for a JIT call with the current
settings in message management. However, the release of such a message
is an essential element in the JIT call process. Therefore an error
message appears for JIT calls for which the system cannot generate
messages. The system does not then generate a summarized JIT call.

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?

Maintain message management in such a way that a message record is
created when a JIT call is generated.
You can check the current settings in message management in the message
determination analysis.

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 PK335 - System will find no message records for a JIT call ?

  The SAP error message PK335, which states "System will find no message records for a JIT call," typically occurs in the context of Just-In-Time (JIT) delivery processes. This error indicates that the system is unable to find any message records related to a JIT call, which can disrupt the supply chain and production processes.
  Causes:
  
  Missing JIT Call Records: The most common cause is that there are no JIT call records created for the specific delivery or production order.
  Incorrect Configuration: The JIT process may not be configured correctly in the system, leading to issues in message generation.
  Data Inconsistencies: There may be inconsistencies in the data related to the JIT call, such as incorrect material numbers, plant codes, or other relevant parameters.
  Timing Issues: The timing of the JIT call may not align with the production schedule, leading to a lack of available message records.
  Authorization Issues: The user may not have the necessary authorizations