How To Fix 1H070 - Position &1 exists for Bank area &2, Position type &3 and Account no. &4

1H070 - Overview

• Message type: E = Error

• Message class: 1H - BKK: Scheck-/Wechselverwaltung

• Message number: 070

• Message text: Position &1 exists for Bank area &2, Position type &3 and Account no. &4

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 1H070 - Position &1 exists for Bank area &2, Position type &3 and Account no. &4 ?

  The SAP error message 1H070 indicates that there is an issue related to a specific position in the context of bank accounting. The message typically means that a position already exists for the specified bank area, position type, and account number, which is causing a conflict when trying to create or modify a position.
  
  Cause:
  The error can occur due to several reasons:
  
  Duplicate Entry: You are trying to create a new position that already exists in the system for the specified bank area, position type, and account number.
  Incorrect Data Entry: There may be a mistake in the data you are entering, leading to a conflict with existing records.
  
  Configuration Issues: There might be issues with the configuration settings in the bank accounting module that are causing the system to incorrectly identify existing positions.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Existing Positions:
  
  Use transaction codes like FBL3N (Display G/L Account Line Items)