How To Fix /SAPAPO/LOM035 - Location type for location &2 (external: &1) does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/LOM -

• Message number: 035

• Message text: Location type for location &2 (external: &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 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 /SAPAPO/LOM035 - Location type for location &2 (external: &1) does not exist ?

  The SAP error message /SAPAPO/LOM035 indicates that there is an issue with the location type for a specific location in the Advanced Planning and Optimization (APO) module. The message states that the location type for the specified location (external ID) does not exist in the system.
  Cause:
  
  Missing Location Type: The location type that is being referenced for the specified location has not been defined in the system.
  Incorrect Configuration: There may be a configuration issue where the location type is not properly assigned or is incorrectly set up.
  Data Inconsistency: There could be inconsistencies in the master data, such as missing or incorrect entries in the location master data.
  Transport Issues: If the system has recently undergone a transport of configuration or master data, the location type may not have been included or properly transported.
  
  Solution:
  
  
  Check Location Type Configuration:
  
  Go to the configuration settings in SAP APO and verify that the location type exists.
  Use transaction code /SAPAPO/LOC1 to check the location types and ensure that the required location type is defined.
  
  
  
  Create or Modify Location Type:
  
  If the location type does not exist, you may need to create it. This can be done in the configuration settings.
  If it exists but is not correctly configured, modify it as necessary.
  
  
  
  Verify Location Master Data:
  
  Check the master data for the location in question. Ensure that the location is correctly defined and that it references a valid location type.
  Use transaction code /SAPAPO/LOC1 to view and edit location master data.
  
  
  
  Check for Data Consistency:
  
  Run consistency checks to ensure that there are no discrepancies in the master data.
  Use transaction codes like /SAPAPO/MC62 to check for inconsistencies.
  
  
  
  Transport Issues:
  
  If the issue arose after a transport, check the transport logs to ensure that all necessary objects were included in the transport.
  If needed, re-transport the missing configuration or master data.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to location types in APO for additional guidance.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  /SAPAPO/LOC1: To manage location master data.
  /SAPAPO/MC62: To check for inconsistencies in master data.
  
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  
  
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it.