LIS configuration

[Former Member]

DEAR ALL

I had activated LIS after doing certain transaction so i am not getting

reports of these transactions. I want the reports of all transaction

before activation of LIS so for that there is any solution.

If any solution is available please send me immiditely.

Thanks,

Shashikant Chaudhari

[Former Member · Accepted solution]

Hi Sasikanth,

Step-by-Step Guide to Activating a Self-Defined SIS Structure

by Mitresh Kundalia, Senior FI/CO Consultant, Zen & Art

Note that the screen shots shown here are from IDES system ver. 4.6B and results might vary slightly in your system, depending upon the version.

IMG menu path for SIS: IMG>Logistics General>Logistics Information System (LIS)

Figure 1: IMG menu path for SIS configuration steps

Task 1: Create Self-Defined Information Structure

• Use transaction code MC21 (menu path Logistics Data Warehouse>Data Basis>Information Structures>Maintain self-defined information structures> Create) to create a Self-Defined Information Structure. Give a customer-range number 990 (any available number between 501 and 999). To make it easier, use ‘copy from’ to copy structure from S001.

Figure 2: Create a Self-Defined Info Structure

Figure 3: Structure S990 is created as a copy of S001

Structure S990 is created as a copy of S001. Accordingly, you will see defaulted characteristics and key figures. Review various settings (unit, sum, etc.).

• Add two more characteristics: Sales Order Number and Item Number.

Click on ‘Choose Characteristics’ Icon and then click on ‘Selection List’ icon to choose fields from ‘field catalogs’.

Choose field catalog ‘SD: Bus transaction (order)’ by double-clicking it. Double-click on ‘Sales Document’ and ‘Sales document item’ from ‘field catalog fields’ (you may need to scroll-down).

Figure 4: Choose fields ‘Sales Document’ and ‘Sales Document Item’ from Field Catalog

You can view technical names by toggling the Switch Display icon.

Figure 5: ‘Switch display’ to view technical names

Make sure that you have selected correct characteristics as: ‘MCVBAK-VBELN’ and ‘MCVBAP-POSNR’.

Click on ‘Copy + Close’ icon and then click on ‘Copy’ icon to accept the changes.

• Review information

Double-click on characteristics and key figures to review technical information. This step is not mandatory, just for information.

Figure 6: Review technical field information for characteristics: Customer (KUNNR), Sales Order (VBELN), Item (POSNR) and Key figures: Incoming Order (AENETWR), Open Order (OAUWE)

System displays the generation log.

Figure 7: Generation log for Structure S990. Table S990E is ‘Structural Information’ for Table S990

Task 2: Maintain Update Groups

• SIS IMG>Logistics Data Warehouse>Updating>Updating Definition>General Definition Using Update Groups>Maintain Update Groups

Figure 8: Update Groups for Sales and Distribution

No new entries need to be created. You can use the existing system-delivered update groups. Use Update Group (UpdGrp) 1 for the standard order process of: SIS: Sales Document, Delivery, Billing Document and use UpdGrp 2 for the SIS: Returns, Returns Delivery, Credit Memo.

Task 3: Maintain Update Rules

• SIS IMG>Logistics Data Warehouse>Updating>Updating Definition>Specific definition using Update Rules>Maintain Update Rules>Display

Info Structure S001 and Update Group 1.

Before we create update rules for S990, let's review how update rules are defined for S001. Review rules for Characteristics and key figures.

Figure 9: Update Rules for combination of Structure S001 and Update Group 1

Double-click to review specific details of the update rule for Key Figure ‘Incoming Orders’. Note that the event is ‘VA – Sales Order creation’.

Figure 10: Update rules for Key Figure ‘Incoming Orders’

Figure 11: Characteristics for Incoming Orders

Similarly review details of Key Figure ‘Sales’. Note that the Invoiced Amount (Sales Amount) is updated by event ‘VD – Billing Document’.

Figure 11: Update rules for Key Figure ‘Sales’

Figure 12: Characteristics for ‘Sales’

• Similar to Update Rules of ‘S001’, we need to create Update Rules for our Self-Defined Structure ‘S990’.

SIS IMG>Logistics Data Warehouse>Updating>Updating Definition>Specific definition using Update Rules>Maintain Update Rules>Create (transaction code MC24). To make it easier, use ‘copy from’ to copy update rules from S001.

Figure 13: Create Update Rules for Structure S990

Please make sure the Source information is properly updated for all the characteristics. Since you copied the rules, the sales order and item rules are defaulted too. Make sure appropriate changes are made for events VC (delivery) and VD (Invoice).

Figure 14: Source Characteristics for Sales Document and Item

Since we copied the Update Rules, the source field and table information is also copied. We need to change appropriately to make sure correct source information is populated. Click on “Rules for charact” and verify source information for every key figure, by clicking on ‘previous key figure’ and ‘next key figure’.

Figure 15: For Event ‘VD – Billing Document’, Sales Document and Item are present in MCVBRP table

Figure 16: For Event ‘VC – Shipping’, Sales Document and Item are present in MCLIPS table

Change Source information for following to MCVBRP-AUBEL and MCVBRP-AUPOS:

o Sales

o Gross Invoiced Sales

o Net Invoiced Sls 1

o Net Invoiced Sls 2

o Inv freight Chrgs

o Bill Docmnt PS5

o Bill Docmnt PS6

o Invoiced Qty

o Invoiced sls – cost

Change Source information for following to MCLIPS-VGBEL and MCLIPS-VGPOS:

o Open Orders

o Open Order Qty

- Save and Generate by clicking on the Generate icon.

• Similarly, copy update rules for Update Group 2. Transaction Code MC24.

Repeat these rules for the combination of information structure S990 and update group 2. (“Copy from” info structure S001 and Update group 2).

Figure 17: Maintain Update Rules for Structure S990 and Update Group 2

Again, click on “Rules for charact” and verify source information for every key figure, by clicking on ‘previous key figure’ and ‘next key figure’.

Change Source information for following to MCVBRP-AUBEL and MCVBRP-AUPOS:

o Credit Memos

o Gross Credit Memos

o Net Credit Memos 1

o Net Credit Memos 2

o Credit memos – freight

o Credit memos – subtotal 5

o Credit memos – subtotal 6

o Credit memos qty

o Credit memos – cost

Task 4: Maintain Statistics Groups

• Maintain Statistics Groups

Maintain Statistics Groups for Customers, Materials, SD Document Types etc. Most of the pre-defined settings are enough. Make sure that settings are updated for customized objects too, e.g., SD document types for your organizations.

Also, make sure that the customer (sales view) and material Master records are updated with appropriate Statistics Groups.

Figure 18: Maintain and assign statistics groups. IMG path: Updating> Updating Control> Settings: Sales> Statistics Groups

- Maintain Statistics Groups for Customers (OVRA)

Figure 19: Statistics Groups for Customers

- Maintain Statistics Groups for Material (OVRF)

Figure 20: Statistics Groups for Materials

- Maintain Statistics Groups for Sales Document

Figure 21: Statistics Groups for Sales Documents

- Assign Statistics Groups for relevant Sales Document Type

Figure 22: Assign Statistics Groups to relevant Sales Documents

Assign Statistics Groups for each Sales Document Item Type

Figure 23: Assign Statistics Groups to relevant Item Categories

-Assign Statistics Groups to each Delivery Type

Figure 24: Assign Statistics Groups to relevant Delivery Types

-Assign Statistics Groups to each Delivery Item Type

Figure 25: Assign Statistics Groups to relevant Delivery Item Categories

- Determine Billing Document Types Relevant to Statistics

Figure 26: Assign Statistics Groups to relevant Billing Types

Note: As mentioned earlier, most of the settings are already set in standard system. Make sure that customized objects specific to your company are also updated appropriately.

- Update Customer Master for Statistics Relevancy

Transaction Code XD02 (Sales view, field “Cust stats.Grp”)

Figure 27: Assign Statistics Groups to Customer Master Records (Sales view)

- Update Material for Statistics Relevancy

Transaction Code MM02 (Sales 2 view, field “Matl statistics grp”)

Figure 28: Assign Statistics Groups to Material Master Records (Sales view)

Task 5: Assign Update Groups to Header and Item Levels

• Assign Update Groups on Header and Item levels

For combinations of Sales Area (Sales Org, Distribution Channel, Division), assign Update groups (transaction codes OVRO and OVRP).

SIS IMG>Logistics Data Warehouse>Updating>Updating Control>Settings: Sales>Update Group

- Update Groups at Item Level

Figure 29: Update Groups at Item Level

Figure 30: Update Groups at Item Level - details

- Update Groups at Header Level

Figure 31: Update Groups at Header Level

Figure 32: Update Groups at Header Level - details.

Task 6: Activate SIS Update

• Lastly, Activate SIS Update for the Structure (transaction code OMO1)

SIS IMG path: Logistics Data Warehouse>Updating>Updating Control>Activate Update>Choose Activity as Sales and Distribution.

Let's update our SIS structure S990 with period as ‘Month’ and update option of ‘Asynchronous Updating (2)’.

Figure 33: Activate SIS Update for S990

SIS tests with Sales Order Processing (Order>Delivery>Invoice)

• Create a Sales Order, transaction code VA01

Figure 34: Create a standard Sales Order and Sales Order 6437 is saved

(Pricing details)

Figure 35: Pricing Details for the Sales Order

• Execute transaction ‘MC30’ to find out which information structures are updated. Please note that this step is not mandatory.

Transaction code ‘MC30’ is worth mentioning here. This transaction code, provided user parameter MCL is set to ‘X’ in user’s master record, provides analysis of which structures are updated for the activity. It generates a log of updates to Information Structures and detailed analysis. Since, it can take resources, it is advisable not to set user parameter MCL in productive system.

Figure 36: Transaction MC30 lists that Structure S990 is updated

Double-click on S990 line to view more details.

Figure 37: Transaction MC30 details for Structure S990

• Execute Standard Analysis Report.

SAP>Logistics>Sales & Distribution>Sales Information System>Standard Analyses>Self defined analysis (transaction code MCSI). (Choose Structure S990). Enter appropriate values and execute.

Figure 38: Standard Analysis report for Structure S990

Figure 39: Standard Analysis report for Structure S990 for given criteria

• Create a Delivery/PGI and review its impact on Standard Analysis Report.

Delivery 80007493 Saved, execute MC30 to review the update log.

Figure 40: At the time of Delivery/PGI, Structure S990 is updated

Figure 41: At the time of delivery, since Order is no more open, Open Order value is reduced

Please note in the Standard Analysis report that the Open Order value is reduced accordingly.

Figure 42: Standard Analysis report reflects correct Open Order value

• Create an Invoice and review SIS report.

Invoice 90021696 saved. Review Update log with MC30.

Figure 43: Invoiced/Sales amount is updated at the time of invoice

Note that in the Standard Analysis report, Sales value has increased.

: Standard Analysis report reflects correct Sales Amount

• Summary changes in Information structure depending upon Sales activity

Sales Order: Note Open Order has EUR 49.60 value.

Delivery: Note Open Order value is reduced.

Invoice: Note Sales column reflects correct invoiced amount.

: Summary – Information Structures reflects correct values depending upon the status of transaction: whether order created, shipped or invoiced

Reward points if u helpful

Cheers,

Govind.

[Former Member · Accepted solution]

Hi Govind,

thanks for u r reply.

u have given me the procedure of configuration of LIS. I had already activiated LIS. Now in LIS reports, I am not getting the information of the transcations which we have done before activiation of LIS.

For ex.

We have activiated LIS on 15.5.2007. I created the order on 1.5.2007 and invoice of this order was created on 26.5.2007. This invoice information is not reflected in LIS reports. T-code MCTC.

If there is any solution for getting reports of transcations before activiation of LIS.

Regards,

Shashikant Chaudhari.

[Former Member · Accepted solution]

Hi,

Kindly refer to Glynn Williams page no :-418,it says that should one create a new structure and require historical data to be updated into it,refer to OSS note number 0064636.This explains the methods of procedding with statistical update.

Summary

Symptom

This note describes the standard procedure for setting up the statistical data in the Logistics Information System (LIS). However, in addition to this standard procedure, you should also read the application-specific documentation which is stored for each application (Purchasing, Sales and Distribution, Production, Inventory Controlling) in Customizing. This documentation can be found as follows (starting from the top level of the Customizing tree):

+ Logistics - General + Logistics Information System (LIS) + Logistics Data Warehouse + Data Basis + Tools + Setup of Statistical Data + Application-specific Setup of Statistical Data

The programs which carry out the setup in the individual applications are also called at this point in Customizing.

Procedure for statistical data setup

The setup reads all original documents or only the original documents required by the user (such as purchase orders, production orders, material documents, billing documents and so on), and sets up statistical data from these documents. Here, every document is updated in the LIS information structures corresponding to the update rules defined in Customizing.

Does the statistical data setup work correctly?

Since a setup can take a number of hours, it is best to just set up one or two (incorrect) documents at first, to check the result before a complete setup is carried out. This is carried out with the following steps:

1. Call the setup program for a few test documents

Call the statistical data setup for the respective application via Customizing. (Path -> see above) Enter the information structure to be set up, and, for example, '&(T' as a version. Important: the version '&(T' must not yet exist, that is, '&(T' must be empty.

Explanation of the version: All data records of an information structure begin with a three-character version number. The current statistical data (actual data) has the version number 000. Data is selected from this version when a standard analysis is carried out. So that the actual data is not modified, the setup must be carried out into another version. The versions into which a setup is carried out must begin with '&(' - by convention.

Enter the document numbers for which the setup is to be carried out as a test on the setup selection screen. Start the setup after this. (If there are not many documents, this can take place online).

2. Check the result of the setup

To display the set up documents in the standard analysis, the standard analysis must access the version '&T'. Via the menu path "System -> User profile -> User parameters", enter and save the parameter ID 'MCR' with the value 'X'. As a result, an input field appears on the standard analysis selection screen, in which a version other than '000' can be entered.

Now call the standard analysis in question. On the selection screen (at the very bottom), overwrite the version '000' with '&(T' (if you have followed the above suggestions). The standard analysis then displays the data which was set up.

3. The user parameter 'MCR' can be reset again.

Standard procedure for the statistical data setup in the LIS

The data of the actual version (000) should be replaced with the set up data when setting up a complete information structure. Two procedures (A and B) are described below. These procedures have the following advantages and disadvantages:

Advantages of procedure A:

It is possible to compare the old actual data with the set up data.

Disadvantages of procedure A:

Data is stored 1 or 2 times (3 times if the actual data is saved)

R/3 operation must be shut down during the entire procedure

Longer runtime than procedure B

Advantages of procedure B:

Data is only stored 1 or 2 times (3 times if the actual data is saved)

R/3 operation must only be shut down during the actual setup.

The runtime is shorter than for procedure A

Disadvantages of procedure B:

It is not possible to compare the old actual data with the set up data.

Procedure A is the "normal" method", and is suitable for normal datasets. On the other hand, procedure B should be used for large datasets.

Although the correctness of the setup should already have been checked using a few documents - as described above, it can nevertheless be a good idea to compare the entire data with the old data (or at least taking random samples) after carrying out the setup. Only procedure A offers this possibility.

Important additional information on deleting and converting data

Note that when Report RMCVISCP is mentioned in the following section, it should only be used in Releases < 4.X . In all release levels as of 4.X, Report RMCVISCP has been replaced by Report RMCSISCP. So use the later report, since Report RMCVISCP in Release > 4.X is also no longer supported by Support.

Procedure A

R/3 operation must be shut down until the following steps 2 to 5 have all been carried out. In particular, no documents may be created or modified.

1. Delete the target version of the setup

If the setup is to take place in version '&(N', for example, this version must be deleted using the program RMCVISCP. Enter the affected information structures and the version to be deleted on the selection screen of RMCVISCP. (In addition, the checkbox "Delete a version?" must be marked).

The version '000' may not be chosen as a target version of the setup. This means that '000' may not be entered as the version to be deleted.

2. Carry out the setup.

In Customizing (see the path described under "Symptom"), call the setup corresponding to the required application. Since now, or at least a large proportion of the original documents are now to be set up, it is recommended that you schedule the setup in the background for a weekend.

3. Check the data which was set up

The set up data can be displayed via the standard analysis. To do this, set the MRC parameter to 'X' (see above), so that the version '&(N' can be entered on the standard analysis selection screen (if the setup was carried out in this version).

Furthermore, you can compare version '000' (old actual data) with the newly set up data (version '&(N') via the comparison of planned and actual data in the standard analysis. (The menu path for the comparison of planned and actual data in the standard analysis is as follows: Edit -> Comparisons -> Planned/actual... )

4. Delete version '000'

Delete version '000' using program RMCVISCP. If there is sufficient disk space, the version '000' can of course be saved as version '&(S', for example, before carrying out the deletion. (This version must be empty or have been deleted beforehand). However, this saving is not absolutely necessary, especially since the old actual data is presumably incorrect (otherwise there would be no need to make the setup).

5. Copy the set up data into version '000'

Using program RMCVISCP, copy the set up version '&(N' into the target version '000'. R/3 operation can start again after this.

6. Delete version '&(N'

Finally, delete the version '& (N' using the program RMCVISCP.

Procedure B:

Within procedure B, R/3 operation need only be shut down during the following steps 4 and 5.

1. Save the actual data

Copy version '000' into another version, for example, '&(S'. Call program RMCVISCP for this, and enter '000' as the source version and, for example, '&(S' as the target version. The target version must be empty or have been deleted beforehand (with the program RMCVISCP).

However, the actual data need not necessarily be saved. In particular, this is the case if the actual data contains a large number of errors. However, the saved data can be an advantage if the setup is canceled for any reason. The old actual data could then be copied back into version '000' again.

2. Deactivate updating

Deactivate the update in Customizing for the information structures to be set up. The Customizing path for this is as follows:

+ Logistics - General + Logistics Information System (LIS) + Logistics Data Warehouse + Updating + Updating Control + Activate update

Then choose the relevant application. The affected information structures can be selected by double-clicking on the subsequent screen. Then mark the radio button "No updating" under "Updating" on the following popup.

3. Delete version '000' (with program RMCVISCP)

For large dataset, deleting version '000' can take several hours. However, it is important that updating of the information structure is deactivated, and thus R/3 operation can be continued as normal.

4. Activate updating

After deleting version '000', reactivate updating of the affected information structures (as under point 3 above).

5. Carry out the setup

In Customizing, call the setup corresponding to the required application. The setup must be carried out into version '000'.

R/3 operation must be shut down during the setup. Before and after this step, R/3 operation can continue as normal.

6. Check the set up version '000' by taking random samples

A comparison with the old actual data is only possible if the old actual data was saved beforehand (for example, into the version '&(S'). However, the comparison is only useful if R/3 operation was stopped between saving the old actual data and the setup. Otherwise, there exists the danger that documents were created or changed in the meantime. These document changes would then only be taken into account in the set up data, not in the old actual data.

7. Delete version '&(S' with program RMCVISCP

The saved old actual data can than be deleted afterwards.

Reward points if useful.

Regards,

Amrish Purohit