Ansicht
Dokumentation

ICA_DS - Maintain Data Sources

BAL_S_LOG - Application Log: Log header data   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Define the data sources for the subsequent matching method definition.

Data sources are used to restrict the data range to be analyzed by the matching program. Each data source has one or more CDS views assigned to it, along with some business semantics such as which fields are used as leading unit and partner unit respectively.

SAP delivers the data sources for comparing journal entry data from the Universal Journal Entry Line Itemstable ACDOCA for entity pairs such as company and trading partner company, as well as profit center and partner profit center. The names of pre-delivered data sources start with "S".

You can define your own data sources either by copying an existing data source or by creating from scratch. Follow the procedure below to create a new data source:

1. Enter the data source name and, optionally, a short and a long description.
2. Assign a Main CDS Viewto the data source. The CDS view must contain the following fields:

Field Name	Label	Usage
RCLNT	SAP Client	Mandatory
METHOD_ID	Matching Method	Mandatory and initial value set to empty
DOCNR	Matching Document No.	Mandatory and initial value set to '0000000000'
DOCLN	Line Item Number	Mandatory and initial value set to 0
RCOMP	Company	Mandatory if leading unit is set to RCOMP
RASSC	Trading Partner	Mandatory if partner unit is set to RASSC
GRREF	Assignment Number	Mandatory and initial value set to '000000000000'
PSTAT	Processing Status	Mandatory and initial value set to '00'
CSTAT	Communication Status	Mandatory and initial value set to '00'
DUE_DATE	Due Date	Mandatory and initial value set to '00000000'
TIMESTAMP	Timestamp	Mandatory for data cutoff

Note: If possible, avoid aggregations in the CDS view so that the data can be matched at line item level. Press F1 key to get the list of CDS views SAP delivers.

1. Optionally, select organizational units in Leading Unit Fieldand Partner Unit Field. These fields must exist in the DDIC structures ICA_S_DIMand ICA_S_DIM_Pas well as in theassigned CDS view. If a superordinate field exists, such as controlling area as the superordinate field for profit center, or you want to achieve matrix reconciliation based on two organizational dimensions, you should also specify the superordinate fields.

Note: You can choose the same field as both the Leading Unit Fieldand the Partner Unit Field. This is used in intra-unit matching scenarios, for example, a company wants to match its own G/L postings with bank statements. Later, when defining a matching method, you also need to specify two data sources (one for G/L postings and one for bank statements) with the same leading and partner unit definitions. This is different for inter-unit matching scenarios, where two different fields are selected as leading and partner unit fields and only one data source is specified in the matching method.

If necessary, you can extend the structures ICA_S_DIMand ICA_S_DIM_Pin the back-end system to include your custom fields. Accordingly, the CDS view also needs to be extended by using the SAP ABAP Development Tools (ADT).

1. If the leading unit field is specified, you need to assign a Unit Entity CDS View to check the validity of the unit values or for data filtering purposes. The partner unit field, if specified, shares the same CDS view.

Note: The Unit Entity CDS View must have the same technical field name as the leading unit field. Press F1 key to get the list of CDS views SAP delivers, such as the CDS view “ICA_Company" (Company Master Data), which contains the unit field Company (RCOMP) and can only be assigned to data sources that have Company (RCOMP) defined as the leading unit field.

1. By default, any user with authorization to execute the Fiori apps for Intercompany Matching and Reconciliation (ICMR)has access to any data that is available via the assigned data sources. If you want to restrict access to the data, you need to specify an Authorization Object. By doing so, the related Fiori apps can grant users the different permissions for accessing leading units accordingly.

Note: The authorization object must have the authorization field name same as your leading unit field with two exceptions: RBUNIT is the leading unit field for consolidation unit while BUNIT is its authorization field, and RBUKRS is the leading unit field for company code while BUKRS is the authorization field.

Press F1 key to get the list of authorization objects SAP delivers.

1. On the Field Semanticspage, do the following:

• For each field, the data element text is retrieved to display on UIs of the related apps, such as Manage Assignments and Reconciliation Balances. If you want to overwrite the data element text, assign a Field Labelto each relevant field.

• If necessary, assign a search help name for the relevant fields.

• Select the Update from Original Doc. checkbox for the fields that need to be updated in ICMR when their values are changed in the original documents. This is typically required for the fields such as clearing status, reversal status, any fields containing reference numbers to be used in matching, and texts for the original documents. Meanwhile, you also need to select Key Fieldfor the fields that are used for selecting the matching items relevant to the value update. For example, you may want to select fields such as company code, fiscal year, and accounting document number to identify such matching items.

Note The Key Fieldsetting is only relevant if the data source has at least one field marked as Update from Original Doc.

• Optionally, enter the Global Field Namefor each field. It can help maintain text consistency between miscellaneous apps and API service interfaces. Refer to the predefined data source SF_JOURNAL_ENTRIES_01 when filling in the global field names for your own data sources.

1. Optionally, on the Mandatory Filter Fieldspage, you can define fields as mandatory filter fields (also known as context fields).

The following fields are available as mandatory filter fields, provided that they also exist in the Main CDS Viewassigned to the data source:

Field Name	Field Description	Supported Default Values
PERIV	Fiscal Year Variant	Specific values
RYEAR	Fiscal Year	Placeholder $CurrentFiscalYear$or specific values
POPER	Posting Period	Placeholder $CurrentFiscalPeriod$ or specific values
FISCYEARPER	Period/Year	Placeholder $CurrentFiscalYearPeriod$ or specific values
RLDNR	Ledger	Specific values
RVERS	Consolidation Version	Specific values
RITCLG	Consolidation Chart of Accounts	Specific values

You can extend the DDIC structure ICA_S_MFF to include more fields than listed above.

These fields will be available for user input when launching a matching run or viewing a reconciliation report. Note the following:

• If you want accounts receivable and accounts payable to be matched across periods and years, you should define FISCYEARPER (Fiscal Year Period) with the comparison operator "<=".

• In a financial consolidation scenario, you may only need to match items across periods within one year, then you can define RYEAR (Fiscal Year) with operator “=” and POPER (Posting Period) with operator "<=".

• If you use the “=” operator for the Fiscal Year field and "<=" for the Fiscal Year Period field, new postings for prior periods of the current fiscal year are included in the matching process. If you use the “=” operator for both fields, only postings for the current period are included in the matching process.

• If the Main CDS Viewcontains one or more of the three fields: RYEAR (Fiscal Year), POPER (Posting Period), and FISCYEARPER (Fiscal Year Period), you need to add the PERIV (Fiscal Year Variant)field as a filter field, choose the operator “=” and enter a default value to derive the posting period for the matching and reconciliation process.

• If you select the Hide Fieldcheckbox, the respective filter field is hidden from the UI and the user cannot change the filter value there, that is, the specified value will always be used.

1. Optionally, on the Conversion Profilespage, you can define conversion profiles to enable on-the-fly conversion of amount- or quantity-type measures. Take the steps below:
1. Specify the conversion profile name and description.
2. Select a conversion type, currency conversion or quantity unit conversion.
3. Depending on your selected type, specify the necessary parameters for the conversion. That is:

• For currency conversion, select an Exchange Rate Type, such as monthly average rate or closing rate, a Reference Date, and a Target Currency. Together with a source currency, which will be available at runtime, the specific exchange rate can be determined for the conversion.

Note: The Use Derived Target Currencycheckbox is only for the Group Reporting use scenario, where the underlying CDS view of the data source is consolidation specific. If you select the checkbox, group currency is derived as the conversion target currency and takes precedence over the value you specified in Target Currency.

• For quantity unit conversion, select a Target Unit of Measure. Note that only the measurement units with a dimension are supported and the conversion is only possible for measurement units of the same dimension.

Later, when defining reconciliation cases, you can create additional measures based on these conversion profiles, so that the measures can be selected in Activate Reconciliation Close Processand reconciliation reports.

1. Optionally, on the Navigation Settingspage, you can define navigation targets for the relevant fields to allow drill-through to the target webpage or apps.
1. Select a field from the drop-down list. If you want to set up more than one navigation option for the same field, enter a Navigation IDto differentiate between the different entries.
2. In the Navigation Target URL field, enter the identifier of your target app. The identifier is usually a string that can be copied from the app URL, from "#" to the last character before "?".

For example, the Manage Journal Entriesapp has an identifier #AccountingDocument-manage. For field "REF_BELNR" (Accounting Document Number), you specify #AccountingDocument-manage as the navigation target URL. Later, from the Manage Assignmentsor Manage Matching Documents app, you can navigate to G/L journal entries to allow the drill-through to original accounting journal entries.

1. Select Open in a New Tab to open a new webpage for the target app while keep the current page open.
2. Enter a text in the Link Labelfield to help the user understand what will happen when selecting the link.
3. In addition, you can specify the URL parameters for any field defined above so that only the navigation target objects according to the specified parameters will be displayed. For example, for the field "REF_BELNR", if you define the following three parameters, only journal entries according to the specified accounting document number, company code, and fiscal year will be shown in the navigation target app:

URL Parameter Name		Parameter Value
	AccountingDocument		{{REF_BELNR}}
	CompanyCode		{{RBUKRS}}
	FiscalYear		{{GJAHR}}

Note that {{ }} is used to embrace a field name from the data source so that value of the field will be assigned to the corresponding URL parameter. You can also specify a fixed literal value for the parameter.

1. Save your changes. The system checks the consistency of your definitions. Only consistent data sources can be saved. The check mainly verifies whether all the fields contained in your assigned CDS views exist in the database table ICADOCM and fulfill the requirements listed in step 1.

You can extend ICADOCM to include additional fields. For more information, see help documentation at help.sap.com/S4_OP_ICMR -> Advanced Settings-> Data Source.

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 18668 Date: 20240607 Time: 034112     sap01-206 ( 264 ms )