Kontakt

Ansicht
Dokumentation

SIMG_CFMENUOLSDOB49 - Define Customer Matchcodes

SIMG_CFMENUOLSDOB49 - Define Customer Matchcodes

CPI1466 during Backup   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

In this process step, you define matchcodes for customer master records. If you want to change or display a customer master record but do not know the account number, you can search for it using a matchcode. The system saves certain fields from a customer master record in a matchcode. You can search for the customer account using these fields, known as matchcodes.

Matchcodes are made up from the master data tables via database views and database indexes (= update type I).

You are looking for a specific customer account number, but only know the long text name of the account and its relevant company code. You can find the account number with the help of a matchcode search using the company code or long text.

The standard system includes the following matchcodes for customer accounts:

  • The matchcode with ID A lets you search using address data.
  • The matchcode with ID C lets you search using classes. The vendors need to be classified beforehand.
  • The matchcode with ID D lets you search using the "Search term" field in the master record. This field usually contains the essential part of the name. This ID also lets you search by company code.
  • The matchcode with ID E lets you search by country/region. This matchcode is used to search for foreign customers.
  • The matchcode with ID K lets you search by account group.
  • The matchcode with ID S lets you search by sales organization. This matchcode is used in the Sales and Distribution (SD) application.
  • The matchcode with ID Z lets you search by account number of the head office. This matchcode is used to find the branches of a head office.

The matchcode object for customer accounts is called DEBI.

The matchcode object determines which database tables and which fields are required for the matchcode IDs. You can create several matchcode IDs for one matchcode object. The matchcode ID determines which fields and/or combinations of fields are used in searches.

Since proper capitalization is required for searches using the name (NAME1) and city (ORT01) of a customer, special substitute fields were created for these fields. All entries are automatically converted to capital letters in these substitute fields (MCOD1 for NAME1 and MCOD3 for ORT01). Therefore, when entering the name or city of the customer within a matchcode selection, you do not need to take capitalization into account.

If you require other matchcode IDs than the ones supplied with the standard software, which should include the fields for the name or city of the customer, you have to enter matchcode fields MCOD1 and MCOD3 for the search fields (NAME1 and ORT01) in the matchcode ID field list.

The substitute fields MCOD1 and MCOD3 are delivered with the standard SAP system for the search fields NAME1 and ORT01. The search field NAME2 is not contained in the standard matchcodes. Therefore, you can configure a field other than the standard one. You can, for example, use the field STRAS (street) instead of NAME2 if you require the street as a search field. To do this, you must enter the field STRAS instead of NAME2 in the "Check search fields for matchcodes" step.

  1. Define which matchcodes are needed in your company.
  2. Check the standard matchcode IDs. Among other things, it is imperative that the required fields are specified in the correct sequence. Add your own matchcode IDs if required.
  3. If you want to carry out a matchcode search using classes, make sure that classes have been created using the cross-application functions in the Implementation Guide and are saved in the vendor master records.

For more information about matchcodes, see BC ABAP/4 Dictionary. For more information about classification, see the relevant section of the Basis Implementation Guide.






CL_GUI_FRONTEND_SERVICES - Frontend Services   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 4681 Date: 20240523 Time: 195045     sap01-206 ( 88 ms )