Do you have any question about this error?
Message type: E = Error
Message class: 26 - Dokumentenverwaltung
Message number: 112
Message text: No screen source maintained for object &
One of the following situations triggered this message:
You want to maintain an object for links to a document type and have
entered a screen for which no screen source is maintained.
You are defining a document type and in field <LS>AltSc</> you entered
the number of a screen for which no screen source is maintained.
Check your entry.
If a new screen needs to be created, note the following points:
The processing logic for the new screen must follow the logic of screen
0101 in program SAPLCV00.
A program must be created in which the PBO and PAI form routines are
processed at the required time.
The name of the program is communicated to the system via a setting in
the IMG for document managemement (Define document types) in field
<ZH>AScEx.</>.
Error message extract from SAP system. Copyright SAP SE.
26112
- No screen source maintained for object & ?The SAP error message "26112 No screen source maintained for object &" typically indicates that there is a missing or improperly configured screen source for a specific object in the SAP system. This error can occur in various contexts, such as when trying to access a transaction or a specific function that requires a screen definition.
Cause:
- Missing Screen Definition: The screen (or GUI) definition for the specified object is not maintained in the system.
- Incorrect Configuration: The object may not be properly configured in the relevant customizing settings.
- Transport Issues: If the object was transported from one system to another (e.g., from development to production), the screen definitions may not have been included in the transport request.
- Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the screen associated with the object.
Solution:
Check Screen Definition:
- Go to transaction SE80 (Object Navigator) or SE41 (Menu Painter) and check if the screen for the specified object exists.
- If it does not exist, you may need to create or maintain the screen definition.
Maintain Object Configuration:
- Use transaction SPRO to navigate to the relevant customizing settings for the object in question. Ensure that all necessary configurations are in place.
Transport Check:
- If the issue arose after a transport, check the transport logs to ensure that all necessary objects, including screen definitions, were included in the transport request.
Authorization Check:
- Verify that the user has the necessary authorizations to access the screen. You can check this using transaction SU53 to see if there are any authorization failures.
Debugging:
- If you have access to debugging tools, you can set breakpoints in the relevant program to see where the error is being triggered and gather more information about the missing screen source.
Related Information:
If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or development team for further assistance.
Get instant SAP help. Start your 7-day free trial now.
26111
No assignments found
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
26110
Make entry in field
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
26113
Previous status not found
What causes this issue? You are processing the document status detail screen for a particular document type and have entered a previous status for th...
26114
Invalid entry
What causes this issue? You want to edit a document and have entered the special character "<LB>*</> in the field <LS>Document...
Click on this link to search all SAP messages.