Manage Matching Assignments
Application component: S/4HANA Intercompany Matching and Reconciliation
App type: Analytical
Line of business: Finance
Leading industry: Cross Industry
Solution capability: Corporate Close (S/4)|Entity Close (S/4)
Scope items: Intercompany Reconciliation Process
Description:  With the Manage Assignments app, for the data read from underlying database table or data sources, you can launch a matching run, view matching results, make manual assignments, and trigger and monitor any follow-up activities. 
An application to manage matching assignments
Key features: This app provides the following key features: Specify Filter Values In addition to selecting a matching method, you may need to specify values for some other mandatory filter fields derived based on the underlying data source, such as fiscal year/period and the leading unit. By choosing Go, only the data that interests you will be displayed.Note Which filter fields are available and have default values depend on the Main CDS View you specified in the data source for the matching method. For more information, see Data Source. You can choose to save your frequently used filter values into a new view variant by choosing Select View ( icon) and then Save As. You can also set the view variant as the default view. This setting is matching method-dependent.  View Matching Results You can view the matching results up to last matching run. Along the data matching process, a matching item may go through the following phases/processing statuses until it achieves the ultimate Matched status:  00 New: The item is newly inserted into the underlying data sources, but hasn't yet rolled in to the matching engine, that is, was not copied to database table ICADOCM (Matching Entries). These items are therefore not allowed for actions such as Assign and Communicate. You must execute the auto-match function to roll them in first.  01 Roll-In: The item has been processed by the matching engine, that is, data has been copied to the matching database table but was not hit by any matching rule. Items with this status are listed in the Unassigned Items table and require manual assignment.  05 Unassigned: You can revert any assignment with status 20 Assigned, 25 Pending Confirmation, or 30 Matched by choosing Unassign. The assignment number is therefore invalidated, and the matching items involved will need to be processed again.   10 In Contact: The item had status 01 Roll-In or 05 Unassigned, and is now under communication, or more specifically, you have added a public note or sent a notification to someone else for clarifications.   20 Assigned: The item has either passed a matching rule of Auto-Assign, Group as Assigned, or Auto-Assign as Exception type or has been assigned manually. Depending on the reason code you specified, this kind of item needs further processing, for example, completing an approval workflow, to achieve the final Matched status.   25 Pending Confirmation: An adjustment posting request has been approved in the workflow. You then need to confirm the adjustment by choosing Process. Following a successful posting, the assignment can achieve the final 30 (Matched) status (or 29 (Auto-Adjusted) if the reason code is set to Temporary Resolution). Note This status is only relevant when the approval workflow includes Confirm Variance Adjustments as the last workflow step. Note that the predelivered workflow has Post Variance Adjustments as the last step, therefore, the variance adjustment is posted directly after the approval.   29 Auto-Adjusted: When the item has this status, it can no longer be processed manually to prevent redundant adjustment postings. This status is mainly applicable to the assignments with reason codes that have automatic adjustment logic implemented and are set as Temporary Resolution. When processing this type of assignment, the status changes from 20 Assigned or from 25 Pending Confirmation to 29 Auto-Adjusted after the adjustment was posted. In this way, the adjusted data is grouped together with the original items to achieve a perfect match in the next matching run. Bear in mind the original assignment is unassigned, and a new assignment number is given for the changed item group.   30 Matched: The item has achieved the final status. Generally, no follow-ups are needed, but you can still unassign the item if necessary.    The status changes can be illustrated by the following graphic:   Based on the processing status, the matching result display is divided into the following sections:  Tables in upper area:   Leading Unit - Unassigned Items: The unassigned items of your selected leading unit. More specifically, the items have a status lower than 20 Assigned. That is, no matching run was executed for the item, the item didn't hit any matching rules during the auto-matching, or it was manually unassigned.   Partner Units - Unassigned Items: The unassigned items of the partner units that have trading records with your selected leading unit.  Note Items with 00 New status are also shown in the two tables after being read directly from the underlying source table.You can choose to change the visible columns and their sort order and save as your own view variant by choosing Select View ( icon) and then Save As. You can also set the view variant as the default view. In this way, you can have the most relevant columns displayed by default. This setting is matching method-dependent.  Tables in lower area:  Assignments: Once certain items hit a matching rule or were manually assigned and therefore have a status 20 Assigned or higher, an assignment number is generated to group the items together as they are regarded as belonging to the same business transaction.   Processing Status: The assignment has the same processing status with all its contained items. Depending on the reason code assigned during the automatic or manual assignment, an assignment may have achieved 30 Matched status or is still undergoing an adjustment posting or approval process.  Matching Rule: The rule that was met during an auto match. In case of manual assignments where matching rule is not involved, the rule ID is shown as 0000. Reason Code: The default reason code assigned to the matching rule or the reason code you specified during a manual assignment. Reason code determines if any follow-up activities are required for the assignment to reach 30 Matched status. For more information, see Reasons and Solutions. Temporary Resolution: The setting defined in the relevant reason code. If an assignment is a temporary resolution, it gets unassigned in the next matching run. The new matching run reads and rematches the latest data from the relevant data sources, refreshes the processing status, and triggers any follow-ups required by the reason code. Note If the assignment is still in the process of automatic adjustment or approval workflow, the auto-match run skips it. Workflow Status: This status is relevant for the assignments that have a reason code with variance adjustment workflow configured. The workflow can be initiated by choosing Process or, in case of manual assignments, directly after assigning the relevant reason code. Note that: The workflow approvers receive the approval tasks in both Verify Intercompany Variance Adjustment - Inbox app and Notifications ( icon) area. Once the adjustment is approved or rejected, the workflow initiator receives the alert in the Notifications ( icon) area. For more information, see Automatic Variance Adjustment. Adjustment Log: Shows if the adjustment posting was successful and how many adjustment documents were posted. You can also navigate to the Application Log - Automatic Adjustments app for details.   Assigned Items: This table is only visible when you select an assignment and click on Show Items. The table then lists all the items the assignment groups.   By default, the screen includes all sections. By choosing Change Layout (  icon) and then Upper Area Only or Lower Area Only, you can change the screen layout. The following graphic illustrates the screen sections described above:    View Assignment Details By choosing arrow icon () of an assignment, you can navigate to its Matching Detail page, where the contained items are separated into Leading Unit and Partner Unit tables according to data slice settings in the respective matching rule. To be more specific, the items from data slice 1 are tagged with SLICE value “1” and displayed in the Leading Unit table, while the items from data slice 2 are tagged with “2” and displayed in the Partner Unit table. Note The expression fields you defined in the matching rule as a basis for data matching are marked with colors: Green stands for the expression fields with operators "Equal to" or "Opposite", while yellow stands for the expression fields with other operators.  The following screenshot shows how the detail screen looks:    Run Matching Choose Auto-Match to run matching for newly rolled-in or unassigned items, so that the items are compared by all matching rules sequentially. Once the matching run is finished, you can choose Check Results to view the updated matching results as described above.Note The specified entity and its partner units will be involved in the matching run. Meanwhile, they are all locked to prevent concurrency issues.  Work with Items For any items, matched or unmatched, you can take the following actions:  Communicate: Add a communication message as follows:  Add Note: Add a public comment and optionally, a due date. It results in the communication status Note Added. Based on your set due date, any overdue matching items are highlighted with a red indicator.   Send Notification: Send a notification to your specified users, and optionally, a due date. As a result, the communication status changes to Notification Sent and the recipients receive the notification in the header bar of the SAP Fiori launchpad ( icon).  Send Email: Send an email to your specified email addresses. You can use the standard email template or the one you have defined and assigned to the relevant matching methods. For more information, see Define and Assign Email Templates.Note The default notification and email recipients are determined based on the assignment of ICAM_COMM (Intercompany Communication) function in Intercompany Teams and Responsibilities. You can also send notifications or emails to any recipients other than those assigned in Manage Teams and Responsibilities.Auto determination of recipients in the communication process is currently only supported for the organizational dimension company. Consolidation unit is not yet supported as a dimension in ICMR communication and variance adjustment workflows. Set to Done: When a certain comment or notification is addressed, you can set the item to done so that the due date and overdue alarm are cleared.  You can view the communication history by choosing the communication status.   Assign: If you think certain unmatched items should be exempted from matching rule validation and be assigned manually, for example, when amounts agree but with different currencies due to the negligence in posting, you can select the items and choose Assign to match them manually and give them an assignment number. The assigned items are then moved to the lower-area table Assignments.  During the manual assignment, you are prompted to specify a reason code. The assignment can then be changed to either of the following processing statuses:  Ultimate status 30 Matched: The reason code is set to No Follow-Ups.  Interim status 20 Assigned: The reason code is not set to No Follow-Ups. This kind of reason code usually has additional settings such as for variance adjustment or approval workflow. To achieve the 30 Matched, you need to trigger the follow-up activities by choosing Process. For more information, see the next section Work with Assignments. Note For the manual assignment, you need to select multiple unassigned items that have the same leading unit and partner unit pair.    Work with Assignments For any existing assignments, matched or unmatched, you can take the following actions:  Assign: You can also merge any unassigned items to an existing assignment number if they all have the same leading unit and partner unit pair.Note Within an assignment, items belong to the leading unit have the “SLICE” value 1, while items belong to the partner unit have the “SLICE” value 2. If company A is regarded as the leading unit in the two upper tables, you cannot add its matching items to an assignment that has company B as the leading unit. Instead, you need to go to the filter bar area, change the leading unit to company B, select the corresponding matching items and the matching assignment, then choose Assign to add the items to the assignment.   Unassign: You can revert any assignment with status 20 Assigned or higher to 05 Unassigned. The assignment number is therefore invalidated, and the involved matching items need to be processed again. Process: For any assignment with processing status 20 Assigned, you can trigger the follow-up activity by choosing Process. You can also change its reason code and choose Process to trigger a different follow-up activity. Based on the assigned reason code, the assignments are moved to the next possible status as follows:  Reason Code Settings User Action/Follow-Ups Status changes to    No Follow-Ups None 30 Matched   Comment Required Entered a comment 30 Matched   With Adjustment Class specified and Temporary Resolution not selected None 30 Matched   With Adjustment Class specified and Temporary Resolution selected None 29 Auto-Adjusted   Triggered a rematch First 05 Unassigned and then 30 Matched   With Workflow Scenario specified Variance adjustment posting approved 25 Pending Confirmation   Variance adjustment posting confirmed 30 Matched  For more information about reason code and workflow configuration, see Reasons and Solutions. Filter: For the Assignments table, you can use the quick filters to show a filtered list of assignments. SAP pre-defines the following standard filters:  Show All   Show Assigned but Not Matched   Show Created in Last 30 Days   Show Obsolete Assignments  In addition, you can also define your own filters. For more information, see Define Custom Filters.  The following animated GIF (English only) shows the main aspects described above:    Manage Assignments - By Reconciliation Case This app mode allows you choose a reconciliation case instead of a matching method. In addition to what is described above, the following features are available:  Three additional filter fields:  Display Group is required to determine the leading unit and partner unit side and their respective data sets.  Amount Field and Currency are provided for the drill-through feature from Reconciliation Balances report.Note Which amount types are available for your selected reconciliation case depends on the data source of its assigned matching method.   You can choose Show Balances to display the aggregated amounts of your specified leading unit and partner unit pair based on the display group of the reconciliation case. The quick view is equivalent to the Reconciliation Balances app but limited to only one pair of leading unit and partner unit.  When choosing the app mode to be used, By Reconciliation Case or By Matching Method, data permission is to be taken into account. In the reconciliation case mode, a user can be limited to accessing the data set defined by a display group. For example, if a user is only permitted to manage accounts receivable (AR) of a company and accounts payable (AP) of its trading partners (the "AR-driven" approach), then he or she should not have the access to the AP of the company. In contrast, when using the matching method mode, a user can access both AR and AP of the company, as well as that of its trading partners. The matching method mode has no permission control applied and gives a more comprehensive view. 
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.