Hi,
Plz find step by step for SIS.
Step-by-Step Guide to Activating a Self-Defined SIS Structure
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
u2022 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 u2018copy fromu2019 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.).
u2022 Add two more characteristics: Sales Order Number and Item Number.
Click on u2018Choose Characteristicsu2019 Icon and then click on u2018Selection Listu2019 icon to choose fields from u2018field catalogsu2019.
Choose field catalog u2018SD: Bus transaction (order)u2019 by double-clicking it. Double-click on u2018Sales Documentu2019 and u2018Sales document itemu2019 from u2018field catalog fieldsu2019 (you may need to scroll-down).
Figure 4: Choose fields u2018Sales Documentu2019 and u2018Sales Document Itemu2019 from Field Catalog
You can view technical names by toggling the Switch Display icon.
Figure 5: u2018Switch displayu2019 to view technical names
Make sure that you have selected correct characteristics as: u2018MCVBAK-VBELNu2019 and u2018MCVBAP-POSNRu2019.
Click on u2018Copy + Closeu2019 icon and then click on u2018Copyu2019 icon to accept the changes.
u2022 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 u2018Structural Informationu2019 for Table S990
Task 2: Maintain Update Groups
u2022 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
u2022 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 u2018Incoming Ordersu2019. Note that the event is u2018VA u2013 Sales Order creationu2019.
Figure 10: Update rules for Key Figure u2018Incoming Ordersu2019
Figure 11: Characteristics for Incoming Orders
Similarly review details of Key Figure u2018Salesu2019. Note that the Invoiced Amount (Sales Amount) is updated by event u2018VD u2013 Billing Documentu2019.
Figure 11: Update rules for Key Figure u2018Salesu2019
Figure 12: Characteristics for u2018Salesu2019
u2022 Similar to Update Rules of u2018S001u2019, we need to create Update Rules for our Self-Defined Structure u2018S990u2019.
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 u2018copy fromu2019 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 u201CRules for charactu201D and verify source information for every key figure, by clicking on u2018previous key figureu2019 and u2018next key figureu2019.
Figure 15: For Event u2018VD u2013 Billing Documentu2019, Sales Document and Item are present in MCVBRP table
Figure 16: For Event u2018VC u2013 Shippingu2019, 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 u2013 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.
u2022 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. (u201CCopy fromu201D info structure S001 and Update group 2).
Figure 17: Maintain Update Rules for Structure S990 and Update Group 2
Again, click on u201CRules for charactu201D and verify source information for every key figure, by clicking on u2018previous key figureu2019 and u2018next key figureu2019.
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 u2013 freight
o Credit memos u2013 subtotal 5
o Credit memos u2013 subtotal 6
o Credit memos qty
o Credit memos u2013 cost
Task 4: Maintain Statistics Groups
u2022 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 u201CCust stats.Grpu201D)
Figure 27: Assign Statistics Groups to Customer Master Records (Sales view)
- Update Material for Statistics Relevancy
Transaction Code MM02 (Sales 2 view, field u201CMatl statistics grpu201D)
Figure 28: Assign Statistics Groups to Material Master Records (Sales view)
Task 5: Assign Update Groups to Header and Item Levels
u2022 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
u2022 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 u2018Monthu2019 and update option of u2018Asynchronous Updating (2)u2019.
Figure 33: Activate SIS Update for S990
SIS tests with Sales Order Processing (Order>Delivery>Invoice)
u2022 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
u2022 Execute transaction u2018MC30u2019 to find out which information structures are updated. Please note that this step is not mandatory.
Transaction code u2018MC30u2019 is worth mentioning here. This transaction code, provided user parameter MCL is set to u2018Xu2019 in useru2019s 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
u2022 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
u2022 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
u2022 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.
Figure 44: Standard Analysis report reflects correct Sales Amount
u2022 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.
Figure 45: Summary u2013 Information Structures reflects correct values depending upon the status of transaction: whether order created, shipped or invoiced
Some of the main steps are here (if you are using standard SIS)
1. Maintain Statistic group for customers (OVRA)
2. Maintain Statistic group for Materials (OVRF)
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
6. Assign Statistics Groups for each Delivery Type
7. Assign Statistics Groups for each Delivery Item Type
8. Determine Billing Document Types Relevant to Statistics
9. Assign Update Group on Item Level (OVRP)
10. Assign Update Group on Header Level (OVRO)
Other than configurations you need to
1. Assign satistic groups to your customers
2. Assign statis groups to your materials.
To use SIS use the following transaction codes
1. Customer Analysis (MCTA
2. material Analysis (MCTC)
3. Sales Organization Analysis (MCTE)
Hope this will serve your purpose.
Bye Varahamurti
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.