SAP Note 21278 - MC object IFLM: Foreign key to table ILOA

Symptom:

Index matchcodes for the functional location defined by the customer do not work with fields from table ILOA.
The standard matchcodes with the update type 'P' do not always work either.

Cause and prerequisites

The foreign key relationship in MC object IFLM between table IFLOT and table ILOA is not maintained correctly:
Before (incorrect):

• Check table: IFLOT

• Foreign key table: ILOA

• Check field: TPLNR
  

Corrected:

• Check table: ILOA

• Foreign key table: IFLOT

• Check field: ILOAN
  

Note:
Before Release 3.0, other names were used:

• Check table = referred table

• Foreign key table = dependent table

Solution

Procedure: Transaction SE11, change matchcode object IFLM

• Select 'Tables'

• Place cursor in 'Tables' on secondary table ILOA

• Choose 'Delete secondary table'

• Place cursor in 'Tables' on primary table IFLOT

• Choose 'Choose secondary table'
  Scroll down in the dialog box and place the cursor on table ILOA under the heading 'Referred tables'. Press 'Choose':
  Then, the line is selected.
  Then press 'Continue':
  The dialog box disappears and the entry is copied.
  The check field must now be called ILOAN.

• Activate

• Menu: Utilities --> Matchcode data --> Set up
  See Note 15760 for working with the matchcode utilities.

Note:
In Release 4.0, the physical matchcodes of the matchcode objects IFLM and IRLM were changed to search functions with database view.Before Release 4.0 this corresponds to the update type 'I' (database index). As a result, the problems dealt with here can no longer occur.

Additional key words

Matchcode, pooled table, M_IFLMC, cost center