standard reports in SD

[Former Member]

Hi all,

Can any one please clarify this issue.

I am trying to run some of the standard reports in SD, but I am getting NO DATA EXISTS FOR CHOOSEN SELECTION.

Is there any configuration to activate SIS.

Thanks & regards,

Praveen.

[Former Member]

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

[Former Member]

LIS & SIS configuration might be incomplete or master data mighr not have been maintained accordingly. Incase if Material statistics Group is left blank, data for same will not flow in Standard reports, similarly if Customer statistic group is left blank, then data will not flow in Standard reports.

Standard SAP SD Reports:=

Statistic Group:

Purpose – To capture data for Standard Reports, we require to activate Statistic Group as under:

--> Item category (Configuration)

--> Sales document type (Configuration)

--> Customer (Maintain in Master data)

--> Material (Maintain in Master data)

When you generate statistics in the logistics information system, the system uses the combination of specified statistics groups to determine the appropriate update sequence. The update sequence in turn determines for exactly which fields the statistics are generated.

Configuration:

IMG --> Logistics Information System (LIS) --> Logistics Data Warehouse --> Updating --> Updating Control --> Settings: Sales --> Statistics Groups -->

1. Maintain Statistics Groups for Customers

2. Maintain Statistics Groups for Material

3. Maintain Statistics Groups for Sales Documents

4. Assign Statistics Groups for Each Sales Document Type

5. Assign Statistics Groups for each Sales Document Item Type .....

All Standard Reports which are available are as under:

SAP Easy Access: Information Systems -> Logistics -> Sales and distribution ->

1. Customer -> Incoming orders / Returns / Sales / Credit memos / Sales activities / Customer master / Conditions / Credit Master Sheet

2. Material -> Incoming orders / Returns / Sales / Credit memos / Material master / ...

3. Sales organization -> Sales organization / Sales office / Sales employee

4. Shipping point -> Deliveries / Returns

5. SD documents -> Orders / Deliveries / Billing documents ...

& so on.

Some of the Standard reports in SD are:

Sales summary - VC/2

Display Customer Hierarchy - VDH2

Display Condition record report - V/I6

Pricing Report - V/LD

Create Net Price List - V_NL

List customer material info - VD59

List of sales order - VA05

List of Billing documents - VF05

Inquiries list - VA15

Quotation List - VA25

Incomplete Sales orders - V.02

Backorders - V.15

Outbound Delivery Monitor - VL06o

Incomplete delivery - V_UC

Customer Returns-Analysis - MC+A

Customer Analysis- Sales - MC+E

Customer Analysis- Cr. Memo - MC+I

Deliveries-Due list - VL04

Billing due list - VF04

Incomplete Billing documents - MCV9

Customer Analysis-Basic List - MCTA

Material Analysis(SIS) - MCTC

Sales org analysis - MCTE

Sales org analysis-Invoiced sales - MC+2

Material Analysis-Incoming orders - MC(E

General- List of Outbound deliveries - VL06f

Material Returns-Analysis - MC+M

Material Analysis- Invoiced Sales - MC+Q

Variant configuration Analysis - MC(B

Sales org analysis-Incoming orders - MC(I

Sales org analysis-Returns - MC+Y

Sales office Analysis- Invoiced Sales - MC-E

Sales office Analysis- Returns - MC-A

Shipping point Analysis - MC(U

Shipping point Analysis-Returns - MC-O

Blocked orders - V.14

Order Within time period - SD01

Duplicate Sales orders in period - SDD1

Display Delivery Changes - VL22

Regards,

Rajesh Banka

Reward points if helpful.

[Former Member]

Have you done Transaction MC21 (Create Info Structure) ?

FYI some more Transactions MC18, MC19, MC20, MC21, MC22, MC23

You can also refer OSS Note 174141 - SIS: Collective note - Customizing

Regards,

Vishal

[Former Member]

Hi

Be more specific, are u running an Info structure?