Message type: E = Error
Message class: HRBAS00CUST - HR: Customizing Checks
Message number: 112
Message text: Infotype &1 is not allowed for any object type
Although infotype &V1& is defined in the system settings, there is no
object type for which this infotype would be valid.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Enter the object types for this infotype in table T777I.
Error message extract from SAP system. Copyright SAP SE.
HRBAS00CUST112
- Infotype &1 is not allowed for any object type ?The SAP error message HRBAS00CUST112 indicates that a specific infotype (in this case, represented by &1) is not allowed for any object type in the system. This typically occurs in the context of Human Resources (HR) module configurations, where certain infotypes are restricted based on the object types defined in the system.
Cause: Configuration Issue: The infotype may not be configured correctly in the system. This could be due to missing settings in the customizing (SPRO) for the infotype or the object type. Object Type Restrictions: The infotype might be restricted for the specific object type you are trying to use it with. For example, certain infotypes are only applicable to specific employee groups or personnel areas. Authorization Issues: There may be authorization restrictions preventing the use of the infotype for the specified object type. Data Model Changes: If there have been recent changes to the data model or infotype configurations, it could lead to
Get instant SAP help. Sign up for our Free Essentials Plan.
HRBAS00CUST111
The dialog module &2 for infotype &1 does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRBAS00CUST110
Program &2 for infotype &1 does not exist
What causes this issue? For infotype &V1& the system checks the existence of the program &V2&. However, the program does not exist. T...
HRBAS00CUST113
The relationship &1 is not internal or external
What causes this issue? Although relationship &V1& is maintained in the table of possible relationships (T778V), it is valid neither for an i...
HRBAS00CUST114
The time constraint for relationship &2 for object type &1 is missing
What causes this issue? The time constraint for object type &V1& and relationship &V2& is not defined. The system cannot save such a ...
Click on this link to search all SAP messages.