Sales information system-customer report

Hi!,SAP gurus,
Brief description about the project:I am in a support project,and facing the issue that the standard sis reports are not running properly.
Analysis:On analysing the problem i found that the reports based on sales organisation-transaction MC(1,
the transaction-MCY,MC2 and MC(u, in the path way information system-logistics-sd-customer,material,sales org,shipping point,sd documents,apart from customer,all are the information structures are generating report,but the customer structure when selected(transaction-mc(a,is showing that no record exists
I have checked the spro settings,and found that with respect to structure-of customer in the transaction omo1,the updating information structure was selected as no update,i have checked it to asynchronous update,still i find the structure is generating no data in the sis report.
also the statistical indicator in the customer master was already set.
please guide me,
Thanks in advance,
Regards,
Anshuman chakraborty.

Hi,
Please check whether the entries maintain in LIS update or not?
Path:
SPRO --> IMG --> Logistics-General -->Logistics Information System --> Logistics Data Warehouse --> Updating --> Updating Control --> Settings: Sales --> Update Group
--> Assign Update Gropu at Header Level
Maintain following data, sperately in two rows:
Sales Org: say,1234
DstCh:
Division:
Customer Statistic Group: +
Statistics group for sales document type: 1
and
Sales Org:
DstCh:
Division:
Customer Statistic Group: +
Statistics group for sales document type: 2
SPRO --> IMG --> Logistics-General -->Logistics Information System --> Logistics Data Warehouse --> Updating --> Updating Control --> Settings: Sales --> Update Group
--> Assign Update Group at Item Level
Maintain following data, sperately in two rows:
Sales Org:
DstCh:
Division:
Customer Statistic Group: +
Material Statistic Group: 1
Statistics group for sales document type: 1
Statistics group for the item category: 1
and
Sales Org:
DstCh:
Division:
Customer Statistic Group: +
Material Statistic Group: 1
Statistics group for sales document type: 2
Statistics group for the item category: 2
Best Regards,
Amit.
Note: Once, you will maintain Settings for LIS-Update, it will update onwards transactions and will not update for already done transactions.

Similar Messages

  • Sales Information System (SIS) Reporting- Alternative Units of Measure

    Guys,
    Does anyone know how can we view SIS Reports (either using Standard or Flexible Analysis) in Alternative Units of Measure? Currently, all the quantities (example Order Quantity) are displayed in Base Unit of Measure .
    Thanks a Lot

    Hai john ,
          If i copy the mc.1 to make -Z report in this how can i view the stock in alternative units  as Kgs..But in master datas we maitained as BUM-Nos . For the same material master we are maitaining in additional datas as 1000 nos =40 kgs, if i take the report system will calculate the current stock with the AUM as kgs .for this pls suggest ie have 1000 nos stock if i choose AUM it should shows as 40 Kgs  .How to make program for calculating formulas.PLs  reply me asap
    Thanks in advance
    viswa

  • Sales information systems

    please help me in SIS how i can configure the system so that based on the order type say OR standard order type i can get all the related information in SIS based on the order type

    Hi Vikas,
    Please find below the complete document on SIS:
    Step-by-Step Guide to Activating a Self-Defined SIS Structure
    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.
    Figure 44: 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.
    Figure 45: Summary – Information Structures reflects correct values depending upon the status of transaction: whether order created, shipped or invoiced
    Please Reward If Really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • Restricting the user options in the sales information system

    Hi,
    We use user information system for sales managers. We use T-code MCSI and the we choose customized information system S904.
    Our goal is to restrict the options of each sales manager because we want that the sales manager only have access to his own information.
    We try with the Parameter_ID VKB (sales office) but in this case the field is previosly filled but the sales manager can change it.
    We use Authorization Data also but the sales manage still also can access to the sales of the others sales manegers.
    How can i solve it?
                 Best Regards
                     João Fernandes

    hi.
    Please find the answer below :
    "In addition to the type of update, you can also define the period unit to be used in the updating
    process.
    The period unit specifies the intervals in which the statistical data is to be cumulated. You can
    choose from the following periods:
      Day
      Week
      Month
      Posting period (you may also need to specify a fiscal year variant)
    You can determine the period unit of the update for every standard information structure.
    In the SAP standard system, the default period unit for updating all the information structures in
    the Sales Information System is month."
    Hope this will help you .
    Regards,
    Krishna O

  • Events Sales Information System - Key figures

    What key figure is updated in Net incoming orders 1 and Net incoming orders 2 as defined under update group 000001. I can understand Net incoming order and Gross incoming order.........

    Hi Sanjay,
    In order to separate both of the key figure groups the updating process is controlled via various update groups. Update group 000001 is assigned to the key figure group for incoming order information and update group 000002 to the group of returns key figures.
    Assigning the business transactions to a certain update of statistics data takes place in two steps.
    In the first step, you compile certain characteristics of the business transactions such as customer, material, document type into statistics groups. In the second step, you assign the statistics groups to the various update groups.
    In the special case incoming order/returns, all of the returns order types are assigned to statistics group 02 and all other order types to statistics group 01. These different statistics groups are assigned to different update groups and thus key figure groups.
    You can assign an update group to certain business transactions using the Customizing function in Sales
    The two types of key figure groups used in the Sales Information System are invoice values and credit memo values. These key figure groups are differentiated by the different update groups (000001/000002).
    Assigning certain types of invoices to the update group 000001 and types of credit memos to update group 000002 is done automatically by the types of orders belonging to them.
    Just go through the following very useful link below:
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/c1/3756d5449a11d188fe0000e8322f96/frameset.htm
    Hope it helps...

  • Using general hierarchy of sales information system

    Hi,
    The sales manager uses oftenly the general hierarchy in order to sort the information that could extract from sales information system.
    So, firstly he uses the tranasction MCK1 to create a hierarchy and after that he executes the transaction MCSI in order to extract sales information.
    So my question is, how can use the hierarchy in a abap program? I want to offer the hierarchy as selection parameter.
         Thank for your cooperation
                     Best Regards
                           João Fernandes

    Hi,
    Thank you for your answer but my question has not been answered.
    The hierarchies i am talking are in table MCSHIERK. When i use program RGSEX000 i can not use the hierarchies of table MCSHIERK.
    Can you give me somo more information now?
                    Best Regards
                          João Fernandes

  • Sales Information System Procedure with example

    Hi Experts,
    i need some documents or notes on the Logistics Information System (Specially Sales Information System) procedure wth some example.
    my mail id :  <REMOVED>
    Thanks in advance
    raj
    Message was edited by:
            Yathish K

    Hi,
    Please <b>read the rules of engagement</b> before posting.
    <b>- Do not ask to send you an email.</b>
    The question you ask and the solution to it is often also interesting for other users of the community. If you ask somebody to send you the answer per email, you deprive others of also learning to know the answer. Therefore any requests for sending material or answers to an email address will be modified by the forum moderators.

  • Sales Information System Performance Transaction MCSI

    Hi,
    We create a few years ago some Sales Information System using structures and tables Snnn. This structures/tables are accessible from transaction MCSI .
    Right now the performance of the access to this information is very bad. We need a lot of time to use this SD Information System.
    What can we do about this? Is it some notes about that, or some best practices?
                Best Regards
                      João Fernandes

    Please help any while creating sales order facing problem company code and language DE is not maintained, where i mis to maintain?

  • Sales information systems(SIS) benefits

    Hi BW experts:
    Can some body explain me the benefits and use of BW SIS reports over R/3 standard SIS reports and also SD reports over R/3 SD standard reports/.
    Your inputs are highly appreciated.
    Thanks in advance.
    mahantesh

    Hi Mahantesh,
    Your question is somewhat vague. As far as I understood you want to compare BW std SD reports and R/3 std SD reports?
    SIS is a part of Logistics information system (LIS). SIS reports use the following characteristics:
    -     Customer
    -     Material
    -     Sales org.
    -     Shipping point
    -     Sales Employee
    -     Sales office
    There are number of SIS std reports. But as you can see they concerned mainly sales and distribution area. They are build on LIS structures. However, you can create custom structures and build non-std reports.
    BW SD reports may be build on data provided by these old LIS structures (practically the same reports as in SIS). But LO cockpit provide new data sources with more information. So, std BW SD-related reports give more information and more flexible.
    Additionally, to this SD reports we can add CRM reports.
    And finally, BW flexibility allows us not only to get data from sales info, but also to join it with data from the other application areas, for example with materials management or controlling. 
    Best regards,
    Eugene

  • Sales informations systems issue

    Dear Gurus,
    I have problem in SALES INFO SYSTEMS, unable to generate standard  reports like Customer, material wise MCTA,MCTC  and MCTE sales orgn wise etc.
    I maintained Satistics currency in Sales Orgn and maintained Relevant for statistics in Customer and material but unable to generate above mentioned standard reports ( I am using SAP ECC6).
    Thanks in Advance
    Regards
    Anush

    See if the update is turned on in the OMO1 transaction. Also, just to verify - have you created any new documents since you have maintained all the configuration and data? The tables won't be updated for the documents that existed before that.
    Check if the S... tables have any records in SE16. If there are records but you don't see the reports than it's some other problem.
    Do Search on the forum - LIS/SIS has been discussed many times already.

  • To activate Sales information system for new sales area

    Hello Gurus,
    Please inform how to activated SIS for newly created sales organization i have done the following configurations:
    header level: (t-code: OVRP)
    Sales Org: say,1234
    DstCh:
    Division:
    Customer Statistic Group: +
    Statistics group for sales document type: 1
    and
    Sales Org: 
    DstCh: 
    Division:
    Customer Statistic Group: +
    Statistics group for sales document type: 2
    Item Level: (t-code: OVRO)
    Sales Org: say,1234
    DstCh:
    Division:
    Customer Statistic Group: +
    Statistics group for sales document type: 1
    and
    Sales Org: 
    DstCh: 
    Division:
    Customer Statistic Group: +
    Statistics group for sales document type: 2
    After doing the configuartion i have craeted some documents but still if i go to t-code: MCTA to view the report i dont see any information.
    Kindly inform if i am missing on anything
    Thanks in advance

    Hie,
           I think that the system does it, there is no particular transaction to activate the SIS. And if you have created the documents then it should reflect in SIS. I hope that you have created the documents till billing i.e. till the accounting document is generated.
    If you can say something more bout wht you are facing may be the thread will help you.
    Regards
    Denish

  • Can anyone pls..  give me the material for sales information system?

    hi,
    good evening to all gurus,
    this is arunteja vasan
    pls.. if anybody have material for SIS, u will send me.
    thanks to all.

    Hi,
    1.create information structure by selecting the key figures and characteristics. After creating the information structure u must activate and generate.
    2.include updating rule for information structure. After including the updating rule the information structure u must activate and generate
    3.select the updating rule is whether for day, week, month, or year by double clicking on the information structure.
    4.Maintaining all seetings ie; customer statistics group, materialstatistics group, sales document, sales item, billing document, and assign all these to sales document type, sales item, billing type,
    5.Assign sales area to updating rule.
    6.check the sales area whether all settings are maintained or not.
    7.maintained customer statistics group in the customer master record, and material statistics group in the material master record.
    8.After all the settings use T.c. MCSI enter the sales area customer material and see the results, now u get the report or sales of a particular customer or organization.
    Note: Before doing the last step create a sales order, delivery, AND billing.
    Award points if useful.
    Regards,
    Amrish Purohit

  • Sales information system

    Dear Sap Gurus,
    Credit info structure (S066) is not updated in some sale order.
    kindly let me know what are possiblities of changes that  might occured in a sale order , for which credit info structure is not updated.
    Please clarify.
    Regards
    divya

    The possibilities here are almost endless. First of all, check STAFO field in VBAK/VBAP. If it's blank, then no SIS updates will be carried. This field is populated based on the configuration and "statistics" field in the customer and material master.
    Also check if there was an update termination for this order - transaction SM13.

  • Sales Information System : Variants S138

    hi,
    We need sales figures for our different materials configuration.
    f.e material XY is sold with variants 1 and 2 with each their prices. Also i made a planning profile with the char's i want to report on.
    I copied structure S126 to S137 with method v003 and then S137 to S138 without method.
    Suppose sales figures for XY1 is 100 (sold 1 unit) and for XY2 150 (also 1 unit)
    In transaction MC(b ,  i am able to consult total sales of material XY eg 250 but when i drill down to the variants i see the right number of sold units per variant but not the sales figure per variant.
    Is this normal ? When i look at structure S138 i see everything is aggregated but in S137 there is a clear distinction.
    with regards
    Erik

    I would suggest to move this to the functional forum since this is not an ABAP question IMHO.
    Based on my limited experience with SIS - you get what you have configured. Take a look at the update definitions in MC26 to find the difference between the updates. I din't quite get though why did you do all this copying... IMHO it's a good idea to leave the SAP's structures alone and to build your own (in 501-999 number range) for any experiments.

  • Authorization control in Sales Information System - Flexible Analysis MCSG

    Dear Friends,
    I have created  certain evaluation report which we execute using Tcode MCSG.  This fetches data from CE1GNPL (COPA table).  We are not able to restrict the data in the report based on the authorization available to relevant user.  We have to restrict the view based on sales office and sales group. 
    I have checked thru Tcode SU22, there is no such object for tcode MCSG based on which I can restrict the view on Sales Office and Sales group.
    Please help.
    Satish

    Hi,
    Below is list of objects
    G_800_GRP
    G_800S_GSE
    G_803J_GJB
    K_REPO_CCA
    M_AUSW_MCC
    M_INFO_MCB
    M_INFO_MCC
    S_CTS_ADMI
    S_DATASET
    S_DEVELOP
    S_OC_DOC
    S_OC_ROLE
    S_OC_SEND
    S_PRO_AUTH
    S_PROGRAM
    S_SPO_DEV
    S_TABU_DIS
    S_TCODE
    S_TRANSPRT
    kapil

Maybe you are looking for