Ansicht
Dokumentation

Secondary table fields are not filled
Tip-No.: 3171 ( INFO3171 )

Short text

Secondary table fields are not filled
Tip-No.: 3171

Symptom

During synchronous construction of a matchcode that is defined via two
or tables, only the fields from the primary table are filled. During
matchcode construction via matchcode utility SAPMACO, both the
fields from the primary table and those from the secondary table(s)
are filled.

Cause

The described system hints that dependent records in the secondary table
were added before the referred record was written in the primary table.
Adherance of the "proper" INSERT sequence - first the referred record,
then the dependent record - is not checked by the DB interface for
performance reasons. Nevertheless, the sequence must be adhered to
for tables on which the synchronous matchcodes were defined, in
order to guarantee correct matchcode selection.

Solution

When performing an INSERT or DELETE on tables that were defined via
synchronous matchcodes, the correct insert and delete sequence must
be adhered to in order to guarantee correct matchcode construction.
INSERT: first add the referred record (from the primary table),
then add the dependent records (from the secondary table(s)).

DELETE: First delete all the dependent records, then delete the
referred record.