Académique Documents
Professionnel Documents
Culture Documents
Information Systems are tools for analyzing and gathering specific data in different areas
like purchasing, inventory etc.
In case of user defined info structures, once the info structure is created with
required updating, it will be updated along with standard tables during every relevant
transaction. The same info tables can be used for other reporting purposes like
zReports etc.
Analysis of Standard Info Structures:
Transaction: MCDG (Path: SAP Easy Access Information Systems Logistics
Purchasing Tools Flexible analysis Evaluations MCDG (Execute)
Execute.
Output:
Apart from standard info structure, we can define user defined info structure based
on business requirement. For example, we can define an LIS table to update full
purchasing cycle from PO to Invoice.
Here, you can define the key fields required in the table.
Click on Characteristics:
Now, select the required field and click on Copy, or double click on the field.
The selected Items will be visible with tick mark:
The fields can be selected from multiple tables.
Enter the field catalog name, description and select the application.
Press ENTER.
Select the required fields as explained in the previous step and click on Copy+close
An information structure defines a group of fields and is used for collecting and
reducing data from an operative application such as sales or purchasing. It forms the basis
for analyses and evaluation and includes:
Enter info structure name A four digit key between S501 and S999 (up to S500, is
reserved for standard)
Application Press F4 and select the Application. 02 stand for purchasing. The
Applications available are listed below:
Select the info-structure type. The following are the examples:
Standard type ( )
Please Note that the info structure type cant be changed once its created.
It is not possible to change the planning characteristic after creating the information
structure.
Double click on the fields to be selected to the selection screen. The fields can be selected
from any field catalog.
If its a test system and you dont want to transport, you can save it as local object.
The definition of the update rules depends on the information structure and update
group.
Update rules consist, for example, of the source field, the event which triggers the update,
requirements and formulas.
Once you have defined the update rules, the corresponding update programs are
automatically generated.
Select the update group: (standard update group: PURCH Purchase Order header
Update Group)
Press ENTER.
Select the required fields from F4 list manually or click on Suggest Rules
Click on next key figure as shown below:
Repeat the same process for all key figures and click on Copy:
Now define the update rules for characteristics for each key figure:
Select the first key figure and click on Rules for characteristics
Repeat the Rules for the characteristics for each key figure.
Note:
In the update rules, you could find the following options:
1. Period split:
Here, you can define the period for which the report / info table to be analyzed. If you
select day, you can analyze based on date, if you select week, you can analyze based on
week and so on. The corresponding period only will be updated in the table.
2. Updating:
Here, you can define the time / sequence when the info table to be updated. The
following options are available.
Synchronous Updating (V1 update): The info table will be updated simultaneously
along with standard tables after every relevant transaction. In this case, the
document update will be terminated in case there is any error in the info table
update, as in case of standard tables.
Asynchronous Updating (2) (V2 update) : Here, the info table is updated after actual
document update, that is the document update and the statistics update take place in
different tasks. In case any error occurs in info table update, it doesnt have any
effect on actual document update. However, It doesnt require any scheduled job for
update.
Asynchronous Updating (3) (V3 update) : Here, the document update and info table
update are carried out separately. The difference between V2 update and V3 update
is that in V3, the update can be carried out at a later time. In short, it is a collective
update with a separate (scheduled) job.
Here, I choose the period as Month in order to analyze the report on monthly basis and
the update as Synchronous Update in order to update the table simultaneously along with
standard tables.
Transaction Code:: MCSJ (Path: Easy Access SAP Menu Information Systems
Logistics Purchasing Tools MCSJ_User Defined Analysis
( for purchase MCSJ, for Sales MCSI )
Go to MCSJ and select the info structure: and click on User Settings
Click on Key figures for setting the output layout.
Note: 1. You may follow the same logic for creation of info structure for other areas like
inventory, LIV, sales etc.
2. For more details about LIS transporting, refer the documentation in the path: SPRO-
Logistics General > Logistics Information System (LIS) > Logistics Data Warehouse
Technical information about the transport of LIS objects
Also, refer the notes: 37845 Technical Information: Transporting Info
Structures and 50237 Techn. info.: transport of update, field catalog
3. For further FAQ, please refer the following notes:
552152 FAQ: General questions for LIS
552503 FAQ: Questions for updating and reporting in LIS
Note: Currently, the info table will be updated from the date the info table is
created. If you want the info table to be updated with previous data, you may
follow the procedure explained in the doc: Update History Data to user defined LIS
(Purchasing)