How To Fix PB335 - Infotype &: & & does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: PB - PD: Message IDs Org. Management

• Message number: 335

• Message text: Infotype &: & & does not exist

What causes this issue?

In infotype 1 person &V1& is assigned to a different organizational
unit to the one assigned in the organizational structure. This is only
allowed when the integration between Personnel Administration and
Organizational Management is deactivated completely, or at least for
person &V1& in the period &V2& - &V3&. If integration is activated,
then there must be an inconsistency in this case.

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?

Check whether the position also differs between infotype 1 and the
organizational structure. If OM-PA integration is activated, the
organizational unit of the position is automatically transfered from
the organizational structure. If the position is also inconsistent,
this could be the reason for the differing organizational unit.
If the departmental switch is altered while the program is running, the
infotype 1 records are not altered immediately. If you have altered
this switch (PPABT PPABT in table T77S0), this could also be a reason
for the inconsistency. In that case, you can alter the infotype 1
records using report RHINTE30.
Correct the organizational assignment of person &V1& in infotype 1 or
in the organizational structure in the above mentioned period. You an
also use report RHINTE30 or RHINTE00 for this.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message PB335 - Infotype &: & & does not exist ?

  The SAP error message PB335 indicates that a specific infotype does not exist in the system. Infotypes are data structures in SAP HR (Human Resources) that store employee-related information. The error message typically appears when trying to access or manipulate an infotype that is not defined in the system.
  Cause:
  
  Incorrect Infotype Number: The infotype number you are trying to access may be incorrect or mistyped.
  Infotype Not Configured: The infotype may not be configured in the system. This can happen if the infotype has not been implemented or activated in the SAP system.
  Client-Specific Configuration: The infotype may exist in the development or quality assurance environment but not in the production environment due to client-specific configurations.
  Authorization Issues: The user may not have the necessary authorizations to access the infotype, leading to the perception that it does not exist.
  
  Solution:
  
  Verify Infotype Number: Double-check the infotype number you are trying to access. Ensure that it is correct and corresponds to a valid infotype.
  Check Infotype Configuration:
  
  Use transaction code PM01 or SPRO to navigate to the configuration settings for infotypes.
  Ensure that the infotype is defined and active in the system.
  
  
  Check Client Settings: If you are working in a specific client, ensure that the infotype is available in that client. You can check this by switching to a different client where the infotype is known to exist.
  Authorization Check: Ensure that the user has the necessary authorizations to access the infotype. You can check this using transaction code SU53 after the error occurs to see if there are any authorization issues.
  Consult Documentation: If you are unsure about the infotype, consult the SAP documentation or help resources to understand its purpose and configuration.
  
  Related Information:
  
  Infotype List: You can view a list of available infotypes using transaction code PA20 (Display HR Master Data) or PA30 (Maintain HR Master Data).
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address specific issues related to infotypes.
  Custom Infotypes: If you are dealing with custom infotypes, ensure that they have been properly developed and activated in the system.
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP Basis or HR module team for further investigation.