Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-LIS (Application Component) Logistics Information System (LIS)⤷
MC0C (Package) Customizing Logistics Information System
IMG Activity
| ID | SIMG_OLIS001 | Cross-Application Selection Parameters |
| Transaction Code | S_ALR_87001005 | IMG Activity: SIMG_OLIS001 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_OLIS001 | Cross-Application Selection Parameters |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_OLIS001 |
The following section describes the selection parameters that are used by several applications for the setup of statistical data.
Specifications for the target structures:
- Information structure to be set up
Here, you can specify which information structures you would like to supply with data.
The information structures that you specify here will be set up.
- Save under a version
To optimize saving the statistical data, the actual data will not be overwritten by the data of the statistical setup.
During the statistical setup, the statistical data is stored under the version that you specify here, whereas statistical data is stored in the information structures under the version "000" (actual data) in the case of online entry and online updating of an order.
The "000" version is the version that is used by the information systems to refer to their data.
The reports for the statistical setup do not prevent the data that already exists from being unavailable. The old data is not replaced by the new data until later, in a subesequent step of the setup.
After completing the setup of statistical data you can analyze the results and then copy them to the actual version (report RMCVISCP). This report also allows you to save the old actual values in a version.
Note
All versions, that begin with "&(" are reserved for the setup of statistical data.
The other versions (i.e. version A00 and all numerical versions except version 000) are available as planning versions.
You can use a standard analysis to look at the SAP standard information structures, by specifying the version number of the version that you would like to analyze (to see the various options available to you here, refer to the section Setup of Statistical Data under "Procedure"). The standard analyses then read the data of the version you have specified, and no longer read the actual data.
Restriction of the document data :
- Archive file
Here, you specify the name of the archive file from which the archived documents are to be read.
If you do not specify an archive, the documents will be read from the residence (the documents located in the system).
- Archiving run
Archiving runs are numbered consecutively, and called up automatically and sequentially.
The numbers for the archiving runs are applicable to all objects.
Control of the setup run:
- Name of the run
In order to continue an interrupted or a terminated setup, you must assign a name to each run of the report, under which the status of the run will be permanently stored.
The system then searches for the first document that has not yet been processed and subsequently begins to process it under this name.
Note
To avoid similarities in the names, use the transaction se16 to check the list of names that already exist in the table TMCW3.
- New run
If you set this indicator, document processing then begins with the first selected document if an entry for restarting still exists under the run name used.
- Termination date and termination time
You can determine when processing should end.
If a report runs over the weekend, for example, it would make sense to stop processing on Monday morning when online operations begin again.
This is particularly necessary if you have selected the option "Lock all documents".
- Redetermining the update group
If you set this indicator, the update group will be redetermined for the documents processed during the setup in accordance with the settings that you have made in Customizing for the respective application.
- Update documents
If you set this indicator, the redetermined update groups will be written to the documents.
The advantage here is that if a change is made to a document, the current update group is taken into account when the change is updated.
If you have changed the Customizing settings, you should definitely make use of this option.
Specifications for the use of ALE (Application Link Enabling:
- Statistical setup: partner system
In the case of distributed systems, if you set this indicator, only the partner system will be set up, and not the local one.
- Logical target system
Here, you specify the name of the system that is to be set up.
Further information about logical systems can be found in the Implementation Guide for "Distribution (ALE)", under Cross-Application Components -> Distribution (ALE) -> Basic Configuration -> Set up logical system.
Business Attributes
| ASAP Roadmap ID | 207 | Establish Reporting |
| Mandatory / Optional | 2 | Optional 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_OLIS001 | 0 | HLA0006423 O HLA0009513 O HLA0006051 O HLA0009540 O HLA0006662 | |
| SIMG | SIMG_OLIS001 | 1 | O HLA0009605 |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 19990324 |
| SAP Release Created in |
