How To Fix SCI143 - Non-assigned include. Check only possible for main program

SAP Error Message - Details

• Message type: E = Error

• Message class: SCI - Code Inspector

• Message number: 143

• Message text: Non-assigned include. Check only possible for main program

What causes this issue?

This include is not included by a main program.

System Response

Because the Code Inspector only checks main programs (for example
function groups), the include is not checked..

How to fix this error?

Include the include in a main program.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SCI143 - Non-assigned include. Check only possible for main program ?

  The SAP error message SCI143 "Non-assigned include. Check only possible for main program" typically occurs when there is an issue with the inclusion of a program or include file in the context of an ABAP program. This error indicates that the include file is not properly assigned to the main program, which can lead to issues during program execution or compilation.
  Cause:
  
  Include Not Assigned: The include file is not assigned to the main program, meaning that the system cannot find or access the include when trying to compile or execute the program.
  Incorrect Program Type: The include might be referenced in a program that is not a main program (e.g., a subroutine or function module).
  Transport Issues: If the include was recently transported from another system, it may not have been properly assigned or activated in the target system.
  Syntax Errors: There may be syntax errors in the include file that prevent it from being recognized correctly.
  
  Solution:
  
  Check Include Assignment: Ensure that the include file is correctly assigned to the main program. You can do this by checking the program attributes in the ABAP Editor (SE38 or SE80).
  Activate Include: If the include file is not activated, activate it using transaction SE80 or SE38. This can resolve issues related to non-assignment.
  Review Program Type: Make sure that the include is being used in a valid context. It should be included in a main program, not in a subroutine or function module.
  Check for Syntax Errors: Open the include file and check for any syntax errors or issues that might prevent it from being compiled correctly.
  Transport Management: If the include was transported, ensure that all related objects are also transported and activated in the target system.
  Recompile the Program: After making changes, recompile the main program to see if the error persists.
  
  Related Information:
  
  Transaction Codes: Use SE38 (ABAP Editor) or SE80 (Object Navigator) to check and modify the program and include files.
  Documentation: Refer to SAP documentation or help resources for more information on handling includes and program structures in ABAP.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  
  If the problem persists after trying the above solutions, consider reaching out to your SAP Basis or ABAP development team for further assistance.