Update-S &D Info structures

Hi
In Updating-Sales &Distribution Info structures (OMO1) what are the importance of the controlling fields
1. period split
2. updating
Regards
Debasish

Hi,
Period split: info structure
Period, or time unit, in which the information structure is updated. That means here you can set the info structure sholud be updated Daily, weekly, monthly.
Indicator for U1/U2/U3 updating of info structures
Indicator that defines the type of updating. i,.e No update, update in V1, V2, V3 Info structure.
Thanks,
Raja

Similar Messages

User exit for update rule of info structure

Hi gurus,
Can anybody tell me how to implement a user exit of update rule for LIS info structure, for ex,S140.
Thanks
Eric xu

There is no user exit and we are not allowed to modify the update rules of the standard SAP info structures. However, you can create your own info structure with the same or similar configuration and then apply a formula or a requirement in the update definitions (MC25 transaction), as you please.
After that you can just turn off the update of S140 (in OMO1 transaction) and use your own info structure instead in MCSI transaction.

RMCA0768 - LIS update program for info-structure S076 will not regenerate

Does anyone know how to trigger this program to regenerate?
I was able to regenerate S501 - S999 using RMCSISIGN via SAP note 99507.
However this one remains a problem.
Thank you,
Michelle

By the way this is a unicode problem. The unicode flag is not checked on the program. The program is $TMP program that is generated by SAP for info-structures.

Updating of QM info structures on the basis of inspection lot creation date

Dear Gurus,
Our business requirement is as follow:
Suppose MM has received 10 consignment of a material (Goods receipt) against a material in month of Feb-2008 from a particular vendor.
Inspection lot statistics in MCXA is updated on the basis of inspection lot generation, which is as per our requirement.
Suppose this inspection take 2 days for analysis at laboratory.
Now FI has to make payments for the month of Feb-2008 against this inspection results. They need the value of average quality parameter for the month of Feb-2008. (Average value of all quality parameter for the material of all the inspection lot which are generated in Feb-2008)
I want that QMIS should update on the basis of Inspection Lot creation date not on the basis of result recording system date.
I think there should be some configuration settings available for this purpose.
Please help me out.
Regards
Honyal

Any valuable input are welcome
regards
Honyal

Info structure in not updated

Dear all,
I am creating one info structure containing Customer Group is added to characteristics.
But when i am updating the info structure then it dosenot update.
Can u plz send me the detail customization for creating new infostructure.
Also why it is not updating?
Plz sent me the details regarding the same.
Thanks & Regards,
PM

Goto OMO1 tcode and select ur info structure and double click on it and sel;ect the radio button "synchronus updating" and check.
compare ur settings with the below configuration.
please gothough this config
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
Figure 17: Maintain Update Rules for Structure S990 and Update Group
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 LIS Update
Lastly, Activate LIS 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 LIS structure S990 with period as Month and update option of Asynchronous Updating (2).
Figure 33: Activate LIS Update for S990
Finally u go through t.code MCSI, select ur info structure. Then execute the LIS report.
rewards if it helps
Edited by: kishore gopala on Feb 14, 2008 6:43 AM

Settings for updating info structures of purchasing and inventory managemen

Hi Experts,
Infor structures of MM aren't updating in my system. Is there any indicator to be maintained in material and vendor master for updating these info structures? and kindly tell me the settings for this.
Thanks
Harmandeep

Plz some one help

Process flow of info structure updation through plan version.

Hi Experts,
Can you please suggest me that how info structure get updated through plan versions ???
Helpful response will be rewarded.
Thanks.

Hi,
Logistics → Production → SOP → Tools → Planning Type/Macro → Change or TCode MC8B
-> Create or MC8A
Select Planning Type SOPKAPAM → Enter
You will find the Info Structure -> In the Application Toolbar Select the Header Icon (Planning Type Info or CtrlShiftF2)
In the window Define Planning Type:
Update the information in the Historical Periods as well as the Planning Start Date (Planning Horizon).
Transaction MC88 - Version
Regards,
Naveen.

Info structures update

Hi!
I'm new to info structures (I'm otherwise ABAPer) and I'm probably not posting this question on the right forum. If so, please redirect me.
Anyway, here's the question:
How do I set an info structure to be filled with data on certain actions? My first idea (as ABAPer) is to use brutal force like user-exit and direct table insert. But I suppose that info structures were not ment to be treated this way, because otherwise they wouldn't differ from Z* tables. Does anyone know the proper way to do this(or proper forum for this question)?
Kind regards,
Igor Barbaric
SAP Consultant (ABAP)
Kaufland Croatia

Our LIS structures were set up by the implementation team so I'm getting this second hand by looking at SPRO. I have loaded them and made mods in the past. I'll tell you what I can.
We use LIS to capture order and sales data. I'm not familiar with the event you're talking about but it is likely in there some place. I'll tell you what I can about how mine is set up and maybe you can get a clue therein. I must say that is is one area of SAP that I really dislike. Very complicated and documentation is hard to find.
I'm not sure how far you are but if you've managed to build an infostructure (it should be an empty transparent table. ex. S501) then let's see if just turning on the update is all you need. If not, we'll have to look at the structure and update rules.
See the section under LIS called Updating/Updating Control. Run the Activate Update tran, select the area you data comes from, and take a peek at that list. For each structure, there is an update control. It shows the level up rollup of the data (daily, monthly, etc.) I believe. IN the updating section, you'll see update methods K 1 2 3. K is "OFF", no updates. 1 is synchronous (V1 update, transaction save waits until LIS is updated), 2 is async (V2 update, transaction requests an update but let's it run async), 3 is the same as 2 accept that the update is scheduled differently. Just check the F1 help on each of these radio buttons.
Once you turn on an update, your transaction should spawn an entry into the LIS structure if all went well.
See if that clue gives you a boost. If not, let me know what specific questions you have and I'll try to assist.

Info structures S031, S032 & S033 stopped updating since 09/2009.

Hello friends,
In our DEV system, Info Strucres S031, S032 & S033 stopped updating after 09/03/2009. There are material documents after that date, but infostrucres are not updated. All these info structures are active, and all their requirements are also active. So, what could have gone wrong - how to resolve this ? BTW, in QAS and PRD, these info structures are being updated. Kindly help.
Thanks,
- Chetan

HI,
The structures are always updated when you execute a transaction that is supposed to update the struture, almost real time. The small technical difference: it is updated asynchronous.
Means you have a time difference of a few milliseconds to seconds from the synchronous posting of a material document and its update in the infostructure.
And if the update of the infostructure fails for some technical reason, then this would have no impact to the original material document. In other words, an update error of an infostructure can lead to inconsistencies.
Tthe regeneration of the infostructure is certainly the way to get the info back to have good numbers in the infostructures. However, you have to investigate first why you have this inconsistencies and what caused them, then you have to make sure that this failure will not happen again (maybe by implementing an OSS note), and then you can think about regenerating the infostructure.
For re-generation, nobody must post anything that updates this infostructure, and the re-generation can last some hours, so it is not a task that can be executed every week.
Regards
KK

Report generation and Info Structure updation

Hi
When are the Tables: S094 and other info structures gets updated?? For Example S094 is updated with materials and has the stock details and it have Goods issue MRP Goods issue Valuation etcu2026 I tried creating a material and created a PIR and run MRP for it and checked the tables its not updated in the S094 table.
Also I am not able to execute Transaction MCEC and MCEA transaction for generating reports for LTP run.
Is there any configurations that has to be done for the above??? Like the LIS (Logistics information system settings) that has to be done for generating the above reports.

Hi,
See different links about LIS :
What's an infostructure ? : http://help.sap.com/saphelp_47x200/helpdata/en/bd/a140eb44d511d188fe0000e8322f96/frameset.htm
Events Updating in SIS : http://help.sap.com/saphelp_47x200/helpdata/en/c1/3756d5449a11d188fe0000e8322f96/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/c1/3756d5449a11d188fe0000e8322f96/frameset.htm
For SIS, all documents (if custo is activated) can update LIS :
- Sales order --> Event : VA
- Delivery --> Event : VC
- Invoice --> Event : VD
If you look at the custo of update rules for the standard analysis S001, you can see the link between key figures and event --> Tcode : MC26 for Infostructure S001 / Update group 1)
Regards,
Lionel

Info structure update

Dear Friends,
We have changed country code in customer master data. In the billing document we can see the new country code but info structure still displays the old data. How can we solve this problem? Where should we check?
Thanks in advance,
Ali

Hi
See these notes
Note 174134 - SIS: Collective note - reorganization
Note 204130 - SIS update: Collective note
I suggest you to avoid reorg the standard info structures (I avoid to do it). The data is copied from data to documents and to info structures in the moment of the SD docs were created. Think that invoices and deliveries, and foreign data (and some declarations as INTRASTAT in EU) linked to these document have the former country.
I hope this helps you
Regards
Eduado

Reg: Error for updating info structure S001

Hi ,
While creating sales order, delivery and purchase order. iam getting the follwing error:
"Error 4 updating info structure S001". Please help me.
Thanks,
Bandi

Hello,
Updates of these reporting tables are done in asynchronous mode.
Check transaction SM13 and try to find back the update of table S001 and analyze the error.
Several OSS-notes explain what can go wrong with updates of LIS and SIS tables like S001.
Wim

Info structure - Updation of info structure.

Hi All,
I am new to info structure concept. Can someone help me out with the below query.
I have a infostructure S998, for ISU sales statics. I can see a tranparent table corresponding to the same S998.
This info structure has a date (BIS) as a characteristci field. the same field is seen in table S998. I am supposed to find out how is this field "BIS" in table S998 updated. Could someone guide me how to check the updation of this field?
Regards,
Suchitra.

Hi,
See different links about LIS :
What's an infostructure ? : http://help.sap.com/saphelp_47x200/helpdata/en/bd/a140eb44d511d188fe0000e8322f96/frameset.htm
Events Updating in SIS : http://help.sap.com/saphelp_47x200/helpdata/en/c1/3756d5449a11d188fe0000e8322f96/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/c1/3756d5449a11d188fe0000e8322f96/frameset.htm
For SIS, all documents (if custo is activated) can update LIS :
- Sales order --> Event : VA
- Delivery --> Event : VC
- Invoice --> Event : VD
If you look at the custo of update rules for the standard analysis S001, you can see the link between key figures and event --> Tcode : MC26 for Infostructure S001 / Update group 1)
Regards,
Lionel

LIS Info structure update

Hi All,
I have created new Info structure,when i execute this Info structure i am not getting the old data i.e documents which were generated before creating this Info structure,So please guide me how to update the old documents to get the data into in this Info structure.
Thanks & Regards.

Hi,
Two things:
1. You need run a reports or tcodes to populate them: OLI1, OLI2 and so on, it depends of type of data. With tcode OLIX you can clean the LIS before (OLI7 for SO, OLI8 for deliv, OLI9 for invoices for SIS, check the info icons)
2. Check that you have data in field STAFO (in tables LIKP, VBAK, and so on) if you want that the before reports work right.
What kind of data are you populating in this LIS (deliveries, SO, invoices, MM movements,...)
Regards,
Eduardo
Edited by: Eduardo Hinojosa on Dec 7, 2009 1:58 PM
Edited by: Eduardo Hinojosa on Dec 7, 2009 2:01 PM

Report MCSK: Info structure update

Hi,
In MCSK transaction we have a info structure S833.
When I check for the Updating parameters for the above info structure, I find that it is set to 'No Update'(thru transaction OMO9)
Does this mean this info structure will never get updated? Also, when I run this report it will not populate the requisite data for the given period from the time 'No Update' is set?
Thanks and regards,
Bikram

We have the same problem - but last month it works....
I can*t change it in OMO9 - all other info structure can be change.
Can it have something to do with EHP4 upgrade?
It's controlling in appl. 03

Update-S &D Info structures

Similar Messages

Maybe you are looking for