Do you have any question about this error?
Message type: E = Error
Message class: GI - FI-SL update
Message number: 355
Message text: No selection screen could be assigned to summary table &
Program &V2& is called up in such a way that a selection screen is
assigned to every ledger in line with the totals table used. In this
case, no such selection screen was found for totals table &V1&. Totals
tables GLTPC, JVT01, and JVT02 are not available for use with this
program.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
The desired procedure cannot be executed.
Error message extract from SAP system. Copyright SAP SE.
GI355
- No selection screen could be assigned to summary table & ?The SAP error message GI355, which states "No selection screen could be assigned to summary table &," typically occurs when there is an issue with the configuration of a summary table in the SAP system. This error can arise in various contexts, such as when trying to generate reports or when accessing certain transactions that rely on summary tables.
Cause:
- Missing Configuration: The summary table may not have a corresponding selection screen defined in the system.
- Incorrect Table Assignment: The summary table might not be correctly assigned to a selection screen in the configuration settings.
- Transport Issues: If the configuration was transported from one system to another (e.g., from development to production), there may have been issues during the transport process.
- Custom Development: If there are custom developments or modifications, they may not have been properly implemented or tested.
Solution:
Check Configuration:
- Go to the relevant configuration settings in the SAP system (usually in the IMG - Implementation Guide).
- Verify that the summary table is correctly configured and that a selection screen is assigned to it.
Assign Selection Screen:
- If no selection screen is assigned, you may need to create or assign an appropriate selection screen to the summary table.
- This can typically be done in the transaction codes related to the specific module you are working with (e.g., MM, SD, etc.).
Review Transport Requests:
- If the issue arose after a transport, check the transport logs for any errors or warnings.
- Ensure that all necessary objects were included in the transport request.
Debugging:
- If you have access to debugging tools, you can analyze the program or report that is generating the error to identify where the issue lies.
Consult Documentation:
- Review SAP documentation or notes related to the specific module or functionality you are working with to see if there are any known issues or additional configuration steps required.
Contact SAP Support:
- If the issue persists and you cannot resolve it, consider reaching out to SAP support for assistance. Provide them with details about the error and the context in which it occurs.
Related Information:
By following these steps, you should be able to identify and resolve the cause of the GI355 error in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
GI354
No reference documents available for the documents selected
What causes this issue? The reference document cannot be displayed because no reference document exists.System Response The system issues an error m...
GI353
Internal error while calling up function module &
What causes this issue? An internal error occurred when calling up the function module &V1&.System Response The system issues an error messa...
GI356
Enter a ledger from General Ledger
What causes this issue? This transaction is used to display General Ledger data records.System Response The system issues an error message and will ...
GI357
Error when calling function module & (transaction &, program &)
What causes this issue? When calling the function module &V1&, an error occurred within transaction &V2& of program &V3&.Syst...
Click on this link to search all SAP messages.