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

SAP Error Message - Details

• 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 to view or process JIT calls.
  
  Solutions:
  
  Check JIT Call Records: Verify if JIT call records exist for the relevant production order or delivery. You can do this by navigating to the appropriate transaction codes (e.g., MD04, COHV) to check the status of the JIT calls.
  Review Configuration: Ensure that the JIT process is correctly configured in the system. This includes checking the settings in the JIT customizing (transaction SPRO) and ensuring that all necessary parameters are set up correctly.
  Data Validation: Validate the data associated with the JIT call. Ensure that all relevant information, such as material numbers and plant codes, is correct and consistent.
  Timing Adjustments: If the issue is related to timing, adjust the JIT call timing to align with the production schedule.
  User Authorizations: Check the user’s authorizations to ensure they have the necessary permissions to access and process JIT calls.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  MD04: Stock/Requirements List
  COHV: Mass Processing of Production Orders
  PK01: Create JIT Call
  PK02: Change JIT Call
  PK03: Display JIT Call
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to JIT calls and the PK335 error.
  Documentation: Review SAP documentation and help files related to JIT processes for additional insights and troubleshooting steps.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a technical consultant who can provide further assistance.