Define Matching Methods
Application component: S/4HANA for Group Reporting
App type: Transactional
Line of business: Finance
Leading industry: Cross Industry
Solution capability: Corporate Close (S/4)|Entity Close (S/4)
Description:  With the Define Matching Methods app, you can create, display, change, or delete matching methods.  
An application to define matching methods
Key features: This app provides the following key features: Create Matching Method Follow the procedure below to create a matching method from scratch:  Choose Create to open the detail page.  Specify a 5-digit alphanumeric ID and a meaningful description, and optionally, a long description. In the Attributes section, select the storage type:  Select Master data if you want to set the matching method as master data, which is usually defined directly in the production system or replicated between systems via file export and import. Note If a system is configured as the production system, Master data is selected automatically and cannot be changed.  If you select Configuration Data, the matching method is part of configuration, which can be transported between systems, for example, from the quality system to the production system, via transport requests. Any necessary changes can only be made in the source system where the matching method was originally defined.Remember If you are creating a new matching method, remember to also transport its number range for matching documents by using transaction ICAN1 (Define Number Range for Matching Documents) after the creation.  In the Data Sources section: Select a data source that forms the matching context. Depending on the data source you choose, a second data source might be required:  If you choose a data source that has different fields defined as Leading Unit Field and Partner Unit Field, no second data source is needed. The matching is executed by comparing the data between the leading unit and partner unit.  If you choose a data source that has a same field defined as Leading Unit Field and Partner Unit Field, such as in intracompany use cases, a second data source is required. In this case, you need to specify different names in Alias for each data source to differentiate them later in the reconciliation case definition, assignment management, and reconciliation report apps.Note The second data source must have the same leading unit field, partner unit field, mandatory filter fields, unit entity CDS views, and authorization objects as the first data source. This also means that you can use the same data source as first and second data sources.Example For the transaction matching within one company (intracompany matching), such as the matching between invoices issued and payments received, you need to define two data sources that meet the above criteria. After that, you select here the first data source for invoice postings and the second data source for payment postings.  You can use the Filter By fields to define method-level filters to restrict the data scope of the matching method. For example, if you define two filters: Ledger equal to 0L and Account Number between 10000000 and 19999999, data not meeting the filter criteria is excluded from any method-specific process, such as matching run, flexible upload, and reconciliation report display.Note After running matching based on the method, don't change the method-level filters, because it may cause data inconsistency between ICMR and the data source. For more information, see 3114279 .You can create a maximum of 100 filters. The limitation is applied to ensure system performance in the follow-on processes. If you have more filter conditions, try to merge them by using the operator between. For more information about how to maintain data sources, see Data Source. In the Matching Rules section, create a new matching rule as follows. Specify a meaningful description, and optionally, a long description. By default, the system automatically assigns a 4-digit numeric ID, which you can change to another unique numeric ID. Maintain the settings in the Attributes subsection. First, select one of the following available match types:  Exact Match: Select this match type if data records assigned according to this rule do not require any follow-up activities. The assignment generated will have the 30 Matched status.  Auto-Assign: This match type results in a suggested assignment. Any data assigned based on such a rule will have the 20 Assigned status, meaning you need to check the assigned data and complete any required follow-up activities, for example, trigger a workflow or an automatic adjustment posting or confirm the item matching after communicating with others. Group as Matched: This match type groups the filtered data together and assigns the 30 Matched status with no further actions needed. For example, you may want to apply this kind of matching rule to reversed journal entries that are not relevant for intercompany reconciliation. Group as Assigned: This match type groups the filtered data together and assigns the 20 Assigned status. User action is required to achieve the final status 30 Matched. For example, you may want to apply this kind of matching rule to journal entries that lack the trading partner information. Auto-Assign as Exception: Can be used for some common or known exceptional matches, for example, the documents have the same reference number and amount but different currency codes. Other than that, it has the same system behavior as Auto-Assign and helps filter assignments.  Select a Default Reason Code for the data matching records assigned by the rule. If necessary, you can still change the reason code so that a different follow-up activity can be performed.Note Reason code controls whether any follow-up activities are required for assigned data. For example, you may need to enter comments, go through an approval workflow, or make adjustment postings. For more information about how to maintain reason codes, see Reason Code.In auto match, any data records pass a matching rule with match type Exact Match will reach the ultimate status 30 Matched, regardless of the reason code setting. Select the Inactive checkbox if you want to deactivate a rule instead of deleting it permanently. The rule won't be processed as long as the Inactive indicator is set. In the Data Slices subsection, you can change the data slice descriptions and define additional filters in basic or expert mode. For more information, see Expert Mode for Defining Filters.Note Data slices represent user-defined data subsets of the data set defined on the matching method level. You can slice the data set into subsets by defining filters on the fields derived from the underlying data sources. Matching rules only process data included in the data slices. You should avoid having intersections between the two data slices. If any data records are included in both data slices, they are treated only as part of data slice 1. Depending on the match type you chose earlier, one of the following options is available for each data slice:  Aggregate: Select the checkbox if you want to aggregate the amount fields and group by the characteristic fields as defined in the matching expressions for this data slice. This is mainly used in “m:n”-type matching cases. For example, two accounts receivable (AR) items are to be matched with one accounts payable (AP) item. For more information, see Example.  Group items on this data slice: Between the two data slices, only one can be selected as a basis for data grouping. For this data slice, you define its filters so that the data not relevant for reconciliation can be filtered and grouped together and later be merged into one matching assignment number.   In the Matching Expression subsection, define any necessary matching expressions for comparing values of both data slices. A matching expression is an equation that consists of left- and right-hand matching fields, a comparison operator, and optionally, conversion functions for either or both fields. Note that if any conversion function, such as CONVERT_CURRENCY or SUBSTRING, is used for a data slice that has Aggregate selected, value conversion is executed after the aggregation.The available functions and operators depend on the data type of your selected expression field. For a complete list, see Functions and Comparison Operators.Note Matching expressions are not needed for matching rules with the match type Group as Assigned or Group as Matched. And it is also not mandatory for the other three match types. For example, if a matching rule with the type Auto-Assign doesn’t have any matching expressions, it means all the items filtered by the two slices are grouped into one assignment. For more information about data selection, aggregation, and matching, see Example. Save your matching rule.Tip You can create more matching rules by choosing Copy. And when in display mode, you can switch to a different rule by using the dropdown list in top-right corner of the page. Note that if you have multiple rules, in each matching run, the system checks documents using the rules according to their sequence, therefore the rule sequence is very important. You can change the sequence by choosing the Move Up or Move Down buttons after selecting a rule.   You can also create a matching method by copying from an existing one and making any necessary changes.  Display/Change Matching Method You can view all your available matching methods on the list page. By navigating to the detail screen of a matching method, you can check or change any of its attributes, settings, and contained rules described above. After making any changes, choose Save to apply the changes.  Delete Matching Method You can also delete any matching methods that are no longer needed. However, once any matching documents are generated for the data records passed a matching rule, deletion of the corresponding matching method is not allowed unless the matching documents are deleted. 
Business roles: General Ledger Accountant - Intercompany
General Ledger Accountant - Intercompany : 
Manages intercompany transaction documents matching and accounts reconciliation, coordinates with other business users for mismatching explanation and derivation correction, etc.