How To Fix RFM_ST_PICK_REQ035 - Picking request is not identified; contact administrator

SAP Error Message - Details

• Message type: E = Error

• Message class: RFM_ST_PICK_REQ - Message Class for Picking Request BO

• Message number: 035

• Message text: Picking request is not identified; contact administrator

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message RFM_ST_PICK_REQ035 - Picking request is not identified; contact administrator ?

  The SAP error message RFM_ST_PICK_REQ035 indicates that a picking request could not be identified. This error typically arises during the picking process in warehouse management or inventory management scenarios. Here are some potential causes, solutions, and related information for this error:
  Causes:
  
  Missing Picking Request: The picking request may not exist in the system, or it may have been deleted or not created properly.
  Incorrect Document Number: The document number or picking request number entered may be incorrect or not formatted properly.
  Authorization Issues: The user may not have the necessary authorizations to access the picking request.
  Data Inconsistencies: There may be inconsistencies in the database or issues with the data integrity related to the picking request.
  System Configuration: There may be configuration issues in the warehouse management settings that prevent the picking request from being recognized.
  
  Solutions:
  
  Verify Picking Request: Check if the picking request exists in the system. You can do this by using transaction codes like LT03 (Create Transfer Order) or LT12 (Confirm Transfer Order) to see if the request is listed.
  Check Document Number: Ensure that the document number you are using is correct. Double-check for any typos or formatting issues.
  User Authorizations: Verify that the user has the necessary authorizations to access and process the picking request. This may involve checking roles and permissions in the user profile.
  Data Consistency Check: Run consistency checks on the database to identify any issues. This may involve using transaction codes like SE11 (Data Dictionary) or SE16 (Data Browser) to inspect the relevant tables.
  Consult with Administrator: If the issue persists, contact your SAP administrator or support team. They can check system logs, configuration settings, and perform deeper troubleshooting.
  Review Configuration: Ensure that the warehouse management configuration is set up correctly. This includes checking settings related to picking, storage types, and movement types.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as LT03, LT12, VL01N (Create Outbound Delivery), and VL02N (Change Outbound Delivery) for managing picking requests.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search the SAP Support Portal for specific notes that may address this error.
  Documentation: Review SAP documentation related to warehouse management and picking processes for best practices and troubleshooting steps.
  
  If the problem continues after trying the above solutions, it may be necessary to escalate the issue to SAP support for further assistance.