⤷ LO-LIS (Application Component) Logistics Information System (LIS)
⤷ MC0C (Package) Customizing Logistics Information System
|ID||LIS_MC3V||U3 Update (Collective Update)|
|Transaction Code||S_ALR_87000701||IMG Activity: LIS_MC3V|
|Customizing Attributes||LIS_MC3V||U3 Update (Collective Update)|
|Customizing Activity||LIS_MC3V||U3 Update (Collective Update)|
|Document Class||SIMG||Hypertext: Object Class - Class to which a document belongs.|
In this step, you make the settings for updating information structures.
You determine when information structures are updated. You have the following options:
- Synchronous update (V1 update)
The statistics update is carried out synchronously with the document update.
However, if an error occurs when updating, and statistics update terminates, then the corresponding documents are no longer available and must be reentered.
- Synchronous update (V2 update)
In this case, the document update and the statistics update are separate. A termination of the statistics update has no influence on the updating of the documents in the operative application.
In addition, you have the option of executing the document update and the statistics update on two separate systems.
- Collective update (V3 update)
Updating type V3 (collective update)is a special type of asynchronous update. The update tasks are collected and then executed together in a background job. This means that you can specify when the statistics are to be updated.
V3 updates thus allow you to move statistic updates to times when there is less load on the system, for instance at night. The collective nature of the process also means that the number of write operations to the database are considerably reduced.
These two factors can improve general system performance noticeably.
Obviously, if it is necessary the statistics are completely up-to-date, you should not use V3 updating.
The document update and the statistics update are also separate here. A termination of the statistics update also has no influence on the updating of the documents in the operative application.
However, contrary to the V2 update, the V3 collective update must be scheduled as a job.
- No update means that updating is switched off.
|ASAP Roadmap ID||207||Establish Reporting|
|Mandatory / Optional||2||Optional activity|
|Critical / Non-Critical||1||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|
|Maintenance object type||C||Customizing Object|
|Customizing Object||Object Type||Transaction Code||Sub-object||Do not Summarize||Skip Subset Dialog Box||Description for multiple selections|
|IMGDUMMY||D - Dummy object||MC3V||MC3V LR||U3 Update (Collective Update)|
|Last changed by/on||SAP||19990526|
|SAP Release Created in|