How To Fix 42370 - LOIO '&1' '&2' without PHIOs

42370 - Overview

• Message type: E = Error

• Message class: 42 - Information Workbench

• Message number: 370

• Message text: LOIO '&1' '&2' without PHIOs

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message 42370 - LOIO '&1' '&2' without PHIOs ?

  The SAP error message 42370, which states "LOIO '&1' '&2' without PHIOs," typically relates to issues with the handling of Logical Object Identifiers (LOIO) in the context of SAP's Archive Management or Document Management System (DMS). This error indicates that the system is trying to access a logical object (LOIO) that does not have any physical objects (PHIOs) associated with it.
  
  Cause:
  
  Missing PHIOs: The primary cause of this error is that the logical object identified by the LOIO does not have any associated physical objects. This can happen if the physical objects were deleted or if there was an error during the archiving process.
  Data Inconsistency: There may be inconsistencies in the database where the logical object exists without any corresponding physical objects.
  Incorrect Configuration: Misconfiguration in the archiving settings or document management settings can lead to this issue.
  
  
  Solution:
  
  Check for PHIOs: Use transaction codes like SARA (for archiving) or the relevant DMS transaction