How To Fix D9436 - Pointeur ALE existe déjà pour table &1 avec RECN_LOC/ACTN_LOC &2

SAP Error Message - Details

• Message type: E = Error

• Message class: D9 - Environment Management System

• Message number: 436

• Message text: Pointeur ALE existe déjà pour table &1 avec RECN_LOC/ACTN_LOC &2

Quelle est la cause de ce problème?

An ALE pointer could not be inserted into table ESTALE, because a line
exists already with the same primary key or with a unique secondary
index in the database table. The unique key of the table ESTALE is made
up of the fields MANDT, RECN_LOC, ACTN_LOC, and ALE_OBJECT. However, the
ALE pointer that was not inserted contains the following values:
,,MANDT,,,,,,= Client Number
,,RECN/ACTN,,,,= &V3&
,,LOGSYS,,,,= logical system name of the ALE source system
,,ALE_OBJECT,,,,= <LB>S</> for specifications or <LB>P</> for phrases
,,OBJECTID,,,,= &V4&
,,RECN_LOC/ACTN_LOC,,= &V2&
,,TABLENAME,,,,= &V1&

Le système émet un message d'erreur et ne vous permettra pas de poursuivre cette transaction tant que l'erreur n'est pas résolue.

Réponse du système

Processing of the IDoc is stopped and the IDoc changes to status 51
<LS>Application document not posted</>.

Comment corriger cette erreur?

The error can occur because of varying reasons, for example,
The primary key (RECN field) of a data record is determined using the
number range ESN_RECN. A number range that was set up incorrectly can
cause a number to be determined that is already used in the respective
table as the primary key. The system fails to create a data record. To
check the number range, perform the following:
Determine the current number of the number range ESN_RECN, Interval
<LB>01</>. To do so , start transaction SNRO, specify the object name
ESN_RECN, and choose <LS>Display</>. Then, choose the menu option
<LS>Goto</> -> <LS>Number Ranges</> and click <LS>Display Intervals</>.
Make a note of the number in the <LS>Current Number</> field for
interval <LB>01</>. This number contains the primary key that was last
assigned for a data record.
Next, check whether database table ESTALE contains primary keys
(RECN_LOC field) that have a value greater than or equal to the number
you noted from number range ESN_RECN. To do so, start transaction SE16N,
enter the relevant table, and define the selection criterion RECN_LOC >=
current number of number range ESN_RECN. Then, start the search.
If you find values, you must adjust the number range in such a way that
the current number of the number range ESN_RECN (interval 01) is greater
than the highest number in the RECN_LOC field in table ESTALE. To adjust
the number range, you can use the transaction SNRO again. If no values
were found, the ALE pointer cannot be created again because of another
problem.
This error can occur when certain data records were deleted logically
(delete indicator is set), but not physically. For this reason, you must
run the reports <LS>Set Missing Deletion Indicator and Physically Delete
Data</> (RC1PHDEL) on the ALE target system and select the <LS>Set
Deletion Ind.</> and <LS>Physically Delete</> parameters. Also refer to
the Customizing activity
<DS:SIMG.EHS_MD_110_05_7>Set Up Job for Deleting Data</> and the
information about running report RC1PHDEL in the Customizing activities
<DS>
<DS:SIMG.EHS_MD_120_40_02>Set Up Distribution of Specification Data</>
</>,
<DS:SIMG.EHS_MD_140_40_04>Set Up Distribution of Phrase Data Between
Systems</>, and
<DS:SIMG.EHS_MD_150_40_01>Set Up Distribution of Reports</>. After you
have executed the report, you can post the incorrect IDoc with
transaction BD87 again.
Data inconsistencies.

Procédure pour les administrateurs système

Extrait du message d'erreur du système SAP. Copyright SAP SE.