Ansicht
Dokumentation

RILM_STOR_GENERATE_CUSTOMIZING - Generation report for ILM Store customizing

TXBHW - Original Tax Base Amount in Local Currency   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Purpose

You can use this report to generate the required ILM Store Customizing details for basic settings.

The report creates an ILM Store client with the name GEN_ILM_STOR_CLIENT, an administrative origin with the name gen_ilmstor_adm, an operational origin with the name gen__, and routing table entries based on the values provided by the user.

For advanced settings, you can change the generated ILM Store settings in the following Customizing activities:

• Define Settings for Administrative Customizing - Transaction ILM_STOR_ADM_CUST

• Define Settings for Operational Customizing - Transaction ILM_STOR_OPR_CUST

Integration

Prerequisites

• Business function ILM_STOR should be activated in the system.

• Users should get assigned to the authorization object SILMSTORAD with the activity values 02,07,39.

Features

Selection

• System ID and Client of Archive files - Enter the values for System ID and Client fields. These values are used to create entries in routing table.

• Transport Details - Enter valid transport requests in the Workbench Request and Customizing Request fields. These transport requests are used to lock the changes. The visibility of the Customizing Request field is based on client settings of the system.

• Storage Media - Choose any one of the following supported storage media. The storage media Hadoop is not supported by this report.

• Default - Database connection is not required.

• File System - Database connection is not required but you must ensure that relevant configurations are done in transaction FILE.

• SAP HANA or SAP IQ - The Database Connection field appears. You must enter the Database Connection details. You can create database connection using transaction DBCO.

• Microsoft Azure - HTTP Destination and OAuth Client Configuration fields appear. You must enter the details for HTTP Destination and OAuth Client configuration. You can create the HTTP Destination using transaction SM59 and OAuth Client Configuration using transaction OA2C_CONFIG.

• Generated Customizing Details - Default values are used for Store Client and Administrative Origin fields. Operational Origin name can be derived from the entered system ID and client details.

Output

• If an operational origin exists with the same name, the report displays an error.

• If the store client and administrative origin exist in the system, the system displays an information message that an operational origin is created and is associated to the existing administrative origin. Click the green light icon to display the generated Customizing details along with storage media properties.

• If the store client and administrative origin do not exist in the system with the default names, click the green light icon to display the generated Customizing details, that is, store client, administrative origin, and operational origin along with storage media properties.

• If the following ILM delivered logical filenames are already used in the system, the report displays an error message that ILM store client cannot be created:

• ILM_STOR_ADK_FILE

• ILM_STOR_AN_FILE

• ILM_STOR_FILE

• ILM_STOR_REQ_SHARED_FILE

Activities

Example

ROGBILLS - Synchronize billing plans   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 5085 Date: 20240520 Time: 055943     sap01-206 ( 76 ms )