How to work with SIS structures Field Catalog........................................................................................................................2 Info Structure.......................................................................................................................6 Maintain Update Groups....................................................................................................10 Assign Update Group at Item/Header Level.....................................................................12 Maintain and Assign Statistics Groups..............................................................................13 Updating Definitions.........................................................................................................18 Update Check ....................................................................................................................25 Maintain Standard Analysis Settings.................................................................................27 Perform Setup – Sales and Distribution.............................................................................31 ALV Display of SIS information.......................................................................................34 Appendix A - Formula Sample..........................................................................................35 Appendix B – Requirement Sample..................................................................................36 Appendix C – Programs.....................................................................................................37 Database Utility.................................................................................................................39
Field Catalog In most cases SAP catalogs will suffice but to use Z fields, for example, you will have to create a custom Field Catalog (which is just a group of fields). The field can not be used in the SIS structure until it’s included in a catalog. In case of the Z fields, make sure that the fields are also appended to the communication structure for the corresponding database table (MC
, e.g. MCVBAP for VBAP) in SE11. Otherwise you will not be able to include the Z fields in a catalog. Transactions: MC18. Create field catalog MC19. Change Field Catalog MC20. Display Field Catalog To create a new catalog, go to either MC18 or to MC19 (go to menu Field catalog -> Create). Enter catalog name, description, select Application (01 for Sales) and Catalog category. Characteristics are the database keys (e.g. Customer Numbers, Material Number), key figures are the figures that we are going to track (e.g. MTD Sales, Receipt Quantity). Date catalog is for the dates only (e.g. Billing Date, Delivery Date, etc.).
Click on [Key Figures], [Characteristics] or [Dates] (depending on the Catalog Type selected on the previous screen).
Select the fields that you want to add by double-clicking on the field name. Use [Switch Display] to switch between technical names and field descriptions. Note that communication structure names (start with MC) are displayed here instead of plain DB table names. When done, click [Copy + Close].
Note that if you have selected a field by mistake it can not be deselected - you will have to remove it on the next screen.
On the next pop-up screen you can change the field sequence. To do so, first select the field you’d like to move by double-clicking on it (it will turn blue). Then single-click on the field where you’d like to move it to. (In the example below Ship-to is being switched with Billing Date.) Click on Move button (Shift-F4) to move the field. Note that Move button is not visible until a field is selected. Note: It seems that the fields can only be moved in upwards direction.
By clicking on [Selection List] you can go back to the selection screen and add more fields. Fields can be deleted by clicking on Delete button. Click [Copy] when done. Save the catalog.
Info Structure Transactions: MC21. Create Info structure MC22. Change Info structure MC23. Display Info structure MCSI. Standard Analysis of Sales (here you can see the user-defined info structures) To create an info structure, go to transaction MC21. Enter Info structure name as Snnn where nnn is a number between 500 and 599. Enter Description and Application (01 for Sales). Note: ‘Plng. possible’ check box enables different versions of info structure and it is probably better to leave it checked since it can only be checked when the structure is created and must not be changed later. When changing the characteristics, the data will be deleted (MC22 will prompt to delete) and Updating Definitions will have to be deleted and re-created. When saving the structure, a warning message will be displayed in MC22 – hit [Enter] to get through.
On the next screen select Characteristics (which are the database key fields) and Key Figures (which are basically cumulative fields like MTD sales) by clicking on the corresponding [Choose...] button. Number of characteristics is limited to 9 (16 in total, 7 already used by standard SAP fields).
On the selection screen, select the fields that you need. First, double-click on the catalog name (right side), then double-click on the field name. If you have previously created your own field catalog, it should be on the ‘Field catalogs’ list.
After Characteristics and Key Figures have been selected, you can change Units, if necessary. Use Base Unit of Measure (EA) to track sale quantities. Click on Generate (red-and-white circle) button to generate the program for this info structure. The generation log will be displayed. If there were no errors (warnings are generally OK) on the log, close the log. Now structure’s status must say ‘Active’.
Maintain Update Groups Transaction SPRO. Click on [SAP Reference IMG]. Go to: Logistics General Logistics Information System (LIS) Logistics Data Warehouse Updating Updating Definition General Definition... Maintain Update Groups Click Process button.
On this screen you can add, delete, change or display Update Groups that apply to all info structures. Update Groups are used when creating Update Definitions (see Updating Definitions). Need
Assign Update Group at Item/Header Level Go to transaction OVRP to assign update group at item level. To display settings for our sales org, click on ‘Position’ button and enter WWL. On this screen we enter for which distribution channel we need the statistical information. To create a new entry, click on [New Entries] and enter sales org, distribution channel, division 01 (this is SAP division, which we are not using), description and ‘1’ in other fields. Transaction OVRO (Header Level) is basically the same.
Maintain and Assign Statistics Groups Transaction SPRO. Click on [SAP Reference IMG]. Go to: Logistics General Logistics Information System (LIS) Logistics Data Warehouse Updating Updating Control Settings: Sales and Distribution Statistics Groups
In this section, you can make application-specific update settings for Sales and Distribution. The business events from the application influence the statistics update via the update group. You may choose to update the info structure differently for different customers, materials and sales documents (or not to update at all). For instance, you can create an info structure with MTD sales on trade customers and non-trade customers and have it updated based on the customer’s settings. To do so, you will need to add 2 statistics groups (e.g. 4 – trade accounts, 5 – non-trade accounts) and then assign all the trade customers to group 4 and non-trade to group 5. You will also need to create 2 updating
definitions (see Create Updating Definitions) for your info structure: one for group 10 and one for group 11. The same can be done for materials and sales documents. Maintain and assign Statistics Groups for Customers Go to transaction OVRA (or use SPRO) to maintain the Statistics Groups for Customers. Click Delete button to delete a group, click [New Entries] to create a group. Save when done. Here, for example, I have created 2 new groups – 4 and 5.
To assign a statistics group to a customer, go to transaction XD02, enter Customer Number. Click on [Sales Area Data] button. On the ‘Sales’ tab, change ‘Cust.stats.grp.’ field to 4 or 5. Save changes.
Maintain and assign Statistics Groups for Materials This is done in the same fashion as for the customers. Go to transaction OVRF (or use SPRO) to maintain the Statistics Groups for Materials. To assign a group, go to MM02, enter Material Number, select ‘Sales: sales org. data 2’ view and update ‘Matl statistics grp’ field:
Maintain and assign Statistics Groups for Sales Documents Go to ‘Maintain Statistics Groups for Sales Documents’ in SPRO. Click Delete button to delete a group, click [New Entries] to create a group. Save when done.
These statistics groups can then be assigned to the following: - sales document type - sales document item type - delivery type - delivery item type on the corresponding screens in SPRO.
Updating Definitions THIS MUST BE DONE IN CLIENT 100 AND THEN TRANSPORTED TO OTHER CLIENTS Transactions: MC24. Create Updating MC25. Change Updating MC26. Display Updating Go to MC24 to create updating definition. Enter info structure name and select Update Group. For SIS use 1 (Orders, etc.) and 2 (Returns, etc.). If SIS must be updated for both Orders and Returns, must create 2 update definitions. Note: If Info Structure fields have been changed, Updating must be deleted in MC25 and created again in MC24. Don’t forget to transport the changes.
Click on [Rules for key figures].
A pop-up window will appear. Click on [Suggest rules], it will fill in the required data with suggested values.
Most of the time suggested values are OK. But if you need to perform any manipulations with a field or set up conditions for updates, it must be done here. a. Check if the field names are correct and the date field for date determination is correct. b. Event: this tells from where to update (e.g. VA from orders, VD from invoices). I’ve learned that the events can not effectively be mixed within one structure (at least not in our system), so stick with one for all key figures. Suggested one should be OK. c. Update Type: select A = cumulative if figures must be accumulated (i.e. it will add to the value), select B = Data Transfer if no need to accumulate (i.e. it will simply overwrite the value). Use option B for things like Volume which are there just for reference. d. To apply a formula to the field, select a formula from the drop-down box. You can use standard SAP formulas or create your own. Formula tells how to update the field (not whether to update or not). e. To apply a requirement, select a requirement from the drop-down box. You can use standard SAP requirements or create your own. Requirement is to decide whether update the field or not. If the same requirement (e.g. update only for certain order type) applies to the whole table, it must be selected for each field. f. You can also apply a program or a FORM routine. Transactions: MC1B – Create a requirement MC1C – Display a requirement MC1D – Create a formula MC1E – Display a formula. When you are done with the field, click on [Key Figure <down> ] and set up the rules or the next field. When you are done with all of the fields, click [Copy] to return to the previous screen. Note: Formulas and requirements are in client 200.
Save. Generate. Click on Activate Updating (this is transaction OMO1).
Double-click on your SIS table name (S5...). A pop-up window will appear. Select the period for which the table should be maintained. Table will be actually updated all the time, but the system will populate different date fields (only year/month, week #, etc.) depending on the period split. Select Updating mode. Select Synchronous if the table must be updated immediately, Asynchronous if it can wait a few seconds. Asynchronous will basically wait for the network etc. resources to be less busy to update (as I was told).
Transport the changes from client 100 to DEV client (400, 200?). - In the destination client, go to transaction SCC1. - Select the Transport Request that you’ve used to create the updating. - Check ‘Including Request Subtasks’ checkbox - Click on [Start Immediately] button to execute.
Update Check To check whether the SIS tables have been actually updated for a specific sales document by the document number, go to transaction: MCVR – Orders MCVV – Billing MCVT – Delivery MCVVK – Sales Activities MCVW, MCVY – INVCO update check
Hit Enter and double-click the SIS structure you want to check:
Maintain Standard Analysis Settings Go to transaction OMOJ. Enter the info structure name and hit Enter. On the subsequent screen you can select characteristics, key figures and parameters that will be used in the Standard Analysis for all users.
To add/remove characteristics, click on [Choose Characteristics]. Only the characteristics on the left side will be used in standard analysis.
There is similar button and screen for Key Figures.
Click on [Parameters] button to change parameter settings:
Check ‘Version selectable’ checkbox if you want users to be able to select the version (for current vs. historic data, for example). Click on [Standard Drilldown] button to go back. Save.
This transaction is also accessible from SPRO (Change Settings – Sales and Distribution):
Perform Setup – Sales and Distribution Transaction SPRO. Click on [SAP Reference IMG]. Go to: Logistics General Logistics Information System (LIS) Logistics Data Warehouse Data Basis Tools Setup of Statistical Data Application-Specific Setup of... Perform Setup – Sales and Distribution Click Process button.
Copy/Delete Versions (OLIX) This transaction is used to create a copy of the data in info structure (could be partial copy) with another version number or into another info structure. Enter info structure name and select either Copy, Delete or Copy+Delete version. By deleting version 000 entire data content of the info structure will be deleted.
SIS Setup: Orders (OLI7). This transaction can be used to populate info structure from existing orders, e.g. if a new structure is created and we want to add historic data to it. Enter info structure name, version 000 (for current), enter Run name (any). Set the Termination time in the future. Other transactions: OLI1 – populate from movement types, OLI8 – populate from deliveries, OLI9 – populate from invoices.
Click on Execute button. Hit [Enter] several times to get past the warning messages. A message [Start Order Processing] will pop up, then it will go back to the screen. Back out of the transaction completely and go to MCSI to check the data.
ALV Display of SIS information See ZS504_DISP for an example. Create a program and make sure to include type-pools: slis, kkblo. include . include <symbol>.
lines at the top. Main ALV functions are REUSE_ALV_GRID_DISPLAY (pass IS_VARIANT parameter so that users could save the variants) and REUSE_ALV_LIST_DISPLAY. First one displays a grid, second – a list. For more ALV examples see: http://www.sap-basis-abap.com/sapabap01.htm
Appendix A - Formula Sample FORMULA_VALUE – FORMULA_VALUE_OBJECT -
Appendix B – Requirement Sample RETURN_CODE = 4
Appendix C – Programs When info structure is created, an ABAP program is generated to update it. The program name can be found on the generation log. Go to transaction MC26 in client 100. Enter info structure name and update group, hit Enter. On the next screen go to menu Environment -> Generation Log. On the generation log, expand the last node:
This program can be debugged, if necessary. Main program that updates SIS structures is SAPLMCS1, include LMCS1V01. To find this name, set a breakpoint in the RMC... program right at the end of the updates. When it jumps out of the program, you’ll see the main program where it’s called from.
In RMC... program there are routines named FORM_F<...>_UPDATE that update key figures. Key figures are updated in the same sequence they are entered on the info structure.
Database Utility If there was already some data in the database and you are changing the structure, run DB utility in the dictionary. Go to SE11, enter menu Utilities -> Database Utility
Related Documents
