Skip to Content

This is a continuation for the document: How to Create an LIS info structure – Purchasing – Part 1

Now, Select the Key figures (Output fields)

Double click on the key figures created in the first step:

  • Double click on the fields to be selected to the selection screen.
  • You can select the fields from any key figures.

Click on Copy + Close.Click on “Copy”


Generate the info structure:


Now, click on “Generate” as shown below:


  • System will ask the package name. Enter the package name and click on “save button”
  • If it’s a test system and you don’t want to transport, you can save it as local object.

Table Generate Log will be displayed:


  • If there is no error, the table will be generated.
  • Go back to the previous screen and save .

  • You may check the table created (here, S973) in SE16.

  • Check the number of entries:

Step 4:Create updating:

     By defining the update process, you define the flow of statistical data from the application to the information system. Means you can define when the data to be updated in the info table created in the previous step.

            The definition of the update rules depends on the information structure and update group.

Update rules consist, for example, of the source field, the event which triggers the update, requirements and formulas.

            Once you have defined the update rules, the corresponding update programs are automatically generated.

Transaction Code: MC24

  • Enter the info structure created in the previous step.
  • Select the update group: (standard update group: PURCH – Purchase Order header Update Group)

  • Press ENTER.

Now, you can define the update rules:

  • Click on the “Rules for Key Fig”

Select the required fields from F4 list manually or click on “Suggest Rules”

  Click on next key figure as shown below:

Repeat the same process for all key figures and click on “Copy”:

Now define the update rules for characteristics for each key figure:

Select the first key figure and click on “Rules for characteristics”

Repeat the Rules for the characteristics for each key figure.

Click on “Generate” as shown below:

Generation Log will be displayed:

Go back and click on “Activate Updating”

Place the cursor on the info structure created and go to details:


Maintain the update rules as shown below:

Note:

  In the update rules, you could find the following options:

1. Period split:

        Here, you can define the period for which the report / info table to be analyzed. If you select “day”, you can analyze based on date, if you select week, you can analyze based on week and so on. The corresponding period only will be updated in the table.

2. Updating:

        Here, you can define the time / sequence when the info table to be updated. The following options are available.

  • No Updating: The info table wont be updated.
  • Synchronous Updating (V1 update): The info table will be updated simultaneously along with standard tables after every relevant transaction. In this case, the document update will be terminated in case there is any error in the info table update, as in case of standard tables.
  • Asynchronous Updating (2) (V2 update) : Here, the info table is updated after actual document update, that is the document update and the statistics update take place in different tasks. In case any error occurs in info table update, it doesnt have any effect on actual document update. However,  It doesnt require any scheduled job for update.
  • Asynchronous Updating (3) (V3 update) : Here, the document update and info table update are carried out separately. The difference between V2 update and V3 update is that in V3, the update can be carried out at a later time. In short, it is a collective update with a separate (scheduled) job.

     Here, I choose the period as “Month” in order to analyze the report on monthly basis and the update as “Synchronous Update” in order to update the table simultaneously along with standard tables.

Save the update:

Now, the configuration part is over:


Testing:

Complete a purchasing cycle and check whether the table is updated correctly: (Create PO – GR – Invoice) and check the table in SE16

To  Analyze the report:

Transaction Code:: MCSJ  (Path: Easy Access – SAP Menu – Information Systems – Logistics – Purchasing – Tools – MCSJ_User Defined Analysis

( for purchase – MCSJ, for Sales – MCSI )


Select  the info structure.

Enter the selection parameters and execute:

Click on “Switch drill down” for further analysis.

You may select any other analysis criteria for analysis.

You may change the output layout as below:

Go to MCSJ and select the info structure: and click on “User Settings”

Click on Key figures for setting the output layout.


Note: 1. You may follow the same logic for creation of info structure for other areas like inventory, LIV, sales  etc.

          2. For more details about LIS transporting, refer the documentation in the path: SPRO- Logistics General –> Logistics Information System (LIS) –> Logistics Data Warehouse – “Technical information about the transport of LIS objects”

Also, refer the notes: 37845 – Technical Information: Transporting Info Structures and 50237 – Techn. info.: transport of update, field catalog

          3. For further FAQ, please refer the following notes:

552152 – FAQ: General questions for LIS

552503 – FAQ: Questions for updating and reporting in LIS

Note: Currently, the info table will be updated from the date the info table is created. If you want the info table to be updated with previous data, you may follow the procedure explained in the doc: Update History Data to user defined LIS (Purchasing)


Reference: SAP Library – Logistics Information System (LO-LIS)

To report this post you need to login first.

12 Comments

You must be Logged on to comment or reply to a post.

  1. Jürgen L

    Very detailed information, still missing an important part which is frequently asked in the forums (an in our company too): You usually have characteristics like order quantity, goods receipt quantity and invoice receipt quantity. And if the order is created in January, but the receipt is in February, then the people wonder why the receipt is not shown when they execute the report for February.

    I am sure you know the answer and it would be good to mention it in detail where this customizing is done.

    Maybe you could as well explain why you have chosen synchronous updating 1 instead of an other setting, what does it mean?

    (0) 
    1. PRASOON AK Post author

      Hi Jurgen,

         Thanks a lot for your valuable feedback…

         Your first question is a bit tricky and unfortunately I dont have a direct answer for the question. Is it because we have choose the period to analyze as month and the GR date is not there in the key fields of the info table?? Or we have to set the quantity reliability option in customizing??… Could you please explain how to approach the case….:'(

         Regarding second suggestion about the updating, I have modified the document to include the details about synchronous update and other updates…

      Thanks & Regards,

      AKPT

      (0) 
      1. Jürgen L

        Depending on the chosen date field for the characteristic e.g. GR quantity or invoice quantity, SAP determines the period in which the statistical data is captured.

        If you use BUDAT then the posting date of the GR or IR is used to determine the period, in case of SYDAT or BEDAT it is the date from the purchase order that determines the period for goods receipt and invoice receipt.

        update_budatPNG.PNG

        Thanks for updating the document with the clarification about version number  and  synchronous and asynchronous updating.

        (0) 
        1. Ajit Kumar

          What about multiple receipts, even though it is A ( cumulative) , will it create individual records if the posting date ( budat ) is different. ( cumulation based on posting date only )  In my system , i dont find budat in the list for S012.update group SAP.

          (0) 
  2. Ajit Kumar

    An Informative and easy to use document for LIS IS,

    I think there is no month wise GR figures since there is only one record; date / period / month being a primary key and updates only cumulate / overwrite or act as a counter in this one record.

    (0) 
  3. G S

    good information, and the question I am going to ask may not be relevant here. But is it possible to pull in key figures from various applications (sales, production and purchasing) in the custom key figure catalog for purchasing application 02 ? I am asking this as I want to set up flexible planning info structure which will hold last yrs sales qty (this will then be forecasted) and then I want to add stock key figures like target stock level, target, target days supply, production qty, work center key figures. Some of these key figures come from INVCO, some from SIS and some from SFIS.

    (0) 
  4. nilesh sankpal

    Hi Prasoon,

    Thanks for detailed document.

    I am working on INVCO information structure. I want to update consumption posting qty along with receipt and issue quantity for characteristics like material, plant, storage location, Movement type. I have created custom info structure with all relevant details and have maintained updated rules.

    I am facing issue in case of stock transfer order scenario. We are doing one step stock transfer with 641 issue and 101 receipt. System creates one document for both movement types. Now in custom info structure all relevant characteristics are getting updated for MVT 641 but for 101 characteristics like material, plant are not getting populated. In MSEG table, there are 2 entries with same document number.

    My question is why info structure is not getting updated for 101 movement type.

    If you know anything about this that will be great help.

    Regards,

    Nilesh

    (0) 

Leave a Reply