How To Fix PSSC_GROSS035 - GED &1 item &2 refers to a non-existent item in SXP &3

SAP Error Message - Details

• Message type: E = Error

• Message class: PSSC_GROSS - Gross Entitlement and Payment

• Message number: 035

• Message text: GED &1 item &2 refers to a non-existent item in SXP &3

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 PSSC_GROSS035 - GED &1 item &2 refers to a non-existent item in SXP &3 ?

  The SAP error message PSSC_GROSS035 indicates that there is a reference to a non-existent item in the SXP (Supplier Experience Portal) system. This typically occurs in the context of procurement or supplier management processes where items are being processed or referenced.
  Cause:
  
  
  Non-Existent Item: The item referenced in the error message does not exist in the SXP system. This could be due to:
  
  The item was deleted or not created in the system.
  There is a mismatch in item numbers or identifiers.
  Data synchronization issues between different systems (e.g., between SAP and external systems).
  
  
  
  Data Entry Errors: Incorrect data entry when creating or referencing items can lead to this error.
  
  
  Configuration Issues: There may be configuration issues in the system that prevent the proper recognition of items.
  
  
  Solution:
  
  
  Verify Item Existence: Check the SXP system to ensure that the item referenced in the error message actually exists. You can do this by:
  
  Navigating to the relevant transaction or report in SXP to search for the item.
  Confirming that the item number or identifier matches what is being referenced.
  
  
  
  Correct Data Entry: If the item does not exist, ensure that the correct item number is being used. If it was supposed to be created, you may need to create it in the system.
  
  
  Data Synchronization: If there are multiple systems involved, ensure that data synchronization processes are functioning correctly. This may involve checking integration settings or running synchronization jobs.
  
  
  Check Configuration: Review the configuration settings in SAP and SXP to ensure that they are set up correctly to recognize and process items.
  
  
  Consult Documentation: Refer to SAP documentation or support resources for any specific notes or updates related to this error message.
  
  
  Contact Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. Provide them with the error message details and any relevant context to help diagnose the issue.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP that may help in troubleshooting, such as ME23N (Display Purchase Order) or ME21N (Create Purchase Order).
  SAP Notes: Check for any SAP Notes related to this error message for additional guidance or patches that may resolve the issue.
  User Roles and Permissions: Ensure that the user has the necessary permissions to access and manage items in the SXP system.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.