Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-MD-BP (Application Component) Business Partners⤷
FB0C (Package) Financial Accounting customers
IMG Activity
| ID | SIMG_CFMENUORFBOB50 | Maintain Matchcodes for Vendors |
| Transaction Code | S_ALR_87003154 | IMG Activity: SIMG_CFMENUORFBOB50 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUORFBOB50 | Maintain Matchcodes for Vendors |
| Customizing Activity | SIMG_CFMENUORFBOB50 | Maintain Matchcodes for Vendors |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUORFBOB50 |
In this activity you define matchcodes for vendor master records. If you want to change or display a vendor master record but do not know the account number, you can search for it using a so-called matchcode. The system saves certain fields from a vendor master record in the matchcode. You can search for the vendor account using these fields, the so-called matchcodes.
Matchcodes are set up in master data tables using database views and indexes (= update type I).
Example
You are looking for a specific vendor account number, but you only know the long text name of the account and its relevant company code. Using a matchcode search with the company code or long text, you can identify the account number.
Default settings
The standard system includes the following matchcodes for vendor accounts:
- The matchcode with the identification A allows you to search via the address data.
- The matchcode with the identification C allows you to search via classes. The vendors first need to be classified.
- The matchcode with the identification E allows you to search via the search term and further master record fields. In particular, it allows you to search via the purchasing organization.
- The matchcode with the identification I allows you to search via the country in which the vendor resides. This matchcode is used to search for foreign vendors.
- The matchcode with the identification K allows you to search via the search term and further master record fields. In particular, it allows you to search via the company code.
The matchcode object for vendor accounts is called KRED.
The matchcode object basically determines which database tables, and therefore which fields are required for matchcode IDs. One or more matchcode IDs can be created for a matchcode object. The matchcode ID determines which fields and/or combinations of fields are used for searches.
Note
Since proper capitalization is required for searches using the name (NAME1) and city (ORT01) of a vendor, 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 vendor within a matchcode selection, you do not need to take capitalization into account.
Caution
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 vendor, 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.
Activities
- Find out which matchcodes are needed in your company.
- Check the standard matchcodes. It is very important that the required fields are specified in the correct sequence. Add your own matchcodes if necessary and delete the matchcodes you do not need.
- If you want to carry out a matchcode search using classes, make sure that classes have been created via the Cross-Application Components in the Implementation Guide and are saved in the vendor master records.
Additional information
For more information on matchcodes, see the BC ABAP/4 Dictionary manual. You can find further information on classification in the relevant section of the Basis Implementation Guide.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENUORFBOB50 | 0 | HLA0001263 | Master Data |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| DWBDUMMY | D - Dummy object | OB50 | 43 | Define Matchcodes |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
