Home‎ > ‎SAP PP / PPPI‎ > ‎SAP MRP‎ > ‎SAP SOP‎ > ‎

SAP SOP Updating Data in an Information Structure



Study Material Contributed by Ulhas Kavle - Senior SAP Consultant
 
 

After creation of the information structure and activating the update rules, you can create the necessary transaction data in SAP development system to test the updation of the information structure from the SAP tables.

 

The Material master (or even customer masters) for which the data is to be updated in the information structure; need a “statistical group” assigned to them. This will ensure that the information is pushed into the information structure. Customer master is another place where you can assign a statistical update group. A statistical group is a very important key in the logistical information system which helps data to be pulled in the structures. And since the information structures are a part of the SAP’s logistical information system, it becomes more logically to have them in the master data.

 

Note – One should also necessarily maintain the update groups (for the update group that you have used) if it is not set automatically by the system. You have learn/check this under - Logistics Information System (LIS) > Logistics Data Warehouse > Updating > Updating Control > Settings. You can create configuration for a sales organization by copying from an existing sales organization data. If you are using the standard “01” application and the standard update groups for the application, you may not end up creating your this configuration at all.




 

Example for the Information Structure Testing:

 

In the example demonstrated, every possible sales order entered (with the entry date as the purchase order date) will become a part of the information structure “S893”. Though one can argue on the fact that not every sales order gets converted in to a business opportunity, then for those arguments you can add more logics to get only those sales order which have been delivered or for those sales order for which billing documents have been created.

 

Coming back to this illustration, it is a belief that every opportunistic sales order is an incoming business to the company and they have to be captured; one can dispute if the object was a quotation and not a sales order (since not all quotations turn in to business for the organization). So on creation of the sales order every line item material quantity entered in the sales order, with a date equal to the purchase order date’ would find an entry in the information structure.

 

So with this scenario in mind, if a sales order is created for Sales Org “3100”, Distribution Channel “10” and Division “21”, whose purchase order date is 01.2010 and the material is “ZUK_SOP_M2” with a qty of 300, then the same would be updated in the information structure “S893” as shown in the below figures. It should be noted that since the update rule is only written for the sales quantity, the order quantity will be updated for the characteristics combination and the other key figures will not be updated on a real time basis in the information structure, they would be updated when the figures are planned in the planning table (macros in the planning table play a major role in getting values for these other key figures which are not automatically updated on a real time basis).

 

Fig – SOP_8


Fig – SOP_9 

 

  

 Fig – SOP_10





Once the data is updated you can check the same using the transaction code MC30 – Update log. Enter the user ID and press execute. By keeping the cursor on the information structure number (S893) you can press the “Details” button to check the data updated in detail and “Analysis” button to check the programs updated for the information structure.


 Fig – SOP_11


Fig – SOP_12