Transporting Info Structure configuration - or bypassing OMO1

I'm trying to transport the settings for a custom info structure (call it S899) from my development system to production. The settings are those in transaction OMO1 and MC25.
Here's the problem: I have access to do manual config in MC25 (updating rules). I can add a requirement, and generate. However, when I click "Activate Updating" button, it returns me to OMO1. Here, when I attempt to select the update parameters for S801, it allows me to do so. But when I try to save those parameters (changed from "no updating" to "synchronous updating") it says "SAP SYSTEM NOT CHANGEABLE". Wow! That authorization will never happen!
So how do I go about changing the Update Parameters in OMO1 for an info structure? Or better yet, is it possible to transport those values?

Ferry, thanks. However, if you follow the OSS note instructions for OMO1, when you hit the "Save" button, it comes back with an error message:
The system administrator has set the system status to "not modifiable".
You cannot change Repository objects in this system.
I did find another OSS note 414163, which addresses this issue. However, the solution code is implemented in our system. And in fact, IT is the cause of the problem. It blocks the update from ever taking place!

Similar Messages

Transporting LIS info structures

Hi ,
We have a customized info structure sitting in our DEV box and we need to transport this to our QA system. There is a however info structure with the same name sitting in QA system, but it does not have any data dictionary tables. Should we just regenerate this info structure in the QA system or do we have to do a re transport of the info structure from the DEV box and overwrite the info structure in QA?
Thanks in advance for your help
Vishal

Warwick,
Also, can you tell me if the dimensions have been changed after the transport was done to the QA, and we need to do another transport, can you provide the technical details on how to transport it. The person who had created the info structure has left the company and we are trying to bring the info structure over to the QA
vishal

Info-structures used in Transportation of Logistics Execution.

Hi
Can any one send me notes, information, or any links on Info-structures used in Transportation of Logistics Execution.
Cheers
Maruthi

check this link,
http://help.sap.com/printdocu/core/Print46c/EN/data/pdf/CAARCLE/CAARCLE.pdf

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.

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

Adding new key figure in Info structure

Hi all,
I am in a need to add a new key figure to our info structure here in my company.
The way I understand it is, it would be best to create a NEW info structure and copy all existing key figure and characteristic and then insert my new key figure into this and rewrite the macro if required.
So my question is
1. How to determine which info structure is currently in use in my company? If i check in MC89 - the key figures match what is in Info structure S076. So is it safe to assume that we are using standard S&OP in my company? Is that a correct way to identify the currently used info structure?
2. For our KMAT, when i open a planned order I see that there in another info structure (not S076) under configuration tab. So can we have diff info structure in use at a same time ?
Please guide.
Thanks,

Hi Nisha,
1. First of all, How would I determine which info structure is being used at this time in my company?
I need to know this so that when I am creating my own custom (S500 - S999) info structure, i can copy the existing KFs and Characteristics and add them to my info structure and then Add a specific key figure on top of that.
Info structures are nothing but tables so in se16 you can check which are Info structures are having update values.
Yes you can add the specific key figure on existing self defined info structure in MC22 after that you need to generate it.
2. Can multiple info structure be in 'use' at the same time in any scenario?
For self defined info structure are application specific you can not have multiple info structure for same scenario. If you take the example of flexible planning with self defined info structure then you can transfer the demand from only one info structure.
Regards,
R.Brahmankar

Info Structure S031 - Information on movement type categories

How can I find out the movement type categories for the S031 info structure? For instance what movement types add to the "Goods receipt" total or the "Goods issue" total. Also, how do you "switch off the updating process for specific, individual movements" as mentioned in the SAP documentation below.
The SAP documentation says:
"Goods movements are divided into the following types:
Goods receipt
Goods issue
Stock transfer
Transfer posting
Inventory differences
You can switch off the updating process for specific, individual movement types in inventory management or in one of the subsequent applications in the logistics chain."

Hi Sherry,
I had similar requirement. You have two options:
1. Just as you've known you can use the field "Statistically relevant".
With this indicator, you control whether a movement type is statistically relevant for Inventory Controlling or not.
In the standard system, all movement types are set in such a way that all material movements for the valuated stock and for the vendor consignment stock are updated.
2. You can define by statistic group:
As of Release 3.0C, there is a customer-specific enhancement that enables you to define a maximum of 4 statistics groups for each movement type. The name for the statistics group has four digits and is freely definable. With the help of the statistics group, you can individually update key figures of Inventory Controlling.
Example: Key figure Consumption and Range of coverage
In table T156, the movement types are characterized as relevant to consumption. Consumption is correspondingly updated in Inventory Controlling. In the information system, it can be useful for the user to interpret issue quantities (that is actually no consumption) as consumption in order to calculate the range of coverage of the material.
Example: A material is always transported into another plant by stock transfer. In the issuing plant, no range of coverage can be calculated because the stock removal quantity is not affecting consumption (movement type 351).
What is to be done in detail?
a) Maintain table TMCA via Transaction SM31.
b) Use SAP enhancement MCB10001 for Inventory Controlling.
Here, you can change the field contents of communication structures MCBEST and MCBEST according to your requirements.
In the above-mentioned example, the source code in the SAP enhancement would have to be as follows:
LOOP AT XMCMSEG.
* Kommunikationsstruktur Bestandscontrolling
IF XMCMSEG-STGRP1 = '1234'.
* Statistikgruppe 1234
* Menge Gesamtverbrauch
XMCMSEG-MGVBR = XMCMSEG-MENGE.
MODIFY XMCMSEG.
ENDIF.
ENDLOOP.
Please let me know if this helps you.
Regards,
Shawn.

How to Genrate Report On User defined Info-structure.

Dear Friends,
I have Info-structure having key figure as production order number, Production order qty and final comfirmation other that STD. I want to generate report but I don't want to go for the ABAP development. Is there any option we do have to generate reports.
Thanks and Regards,
Neel...

Hi Rajesh,
Yes COOIS is T-code where U could retrive any information regarding the production order. But I would like to know if I have info-structure how i could configure reports in STD-SAP. Since I managing the production in 2 units of measure one is Kg and other in Lit. In COOIS i able to get report in kg but I also want report in Lit.
Thanks in advance for ur suggestions.
Regards,
Neel

User defined Info structure

Hi all
I am trying to create an infostructure of my own which will update document posting date after each transaction.
through mc21 I created an info structure under Inventory Controlling Event.
Created a separate update group for it.
Created update through mc24 & maintained required data-field
After generating the update I activated the infostructure.
maintained the user parameter MCL= X against my user profile.
now for testing I created ome material document through MIGO.
carried out update Log through mc30,but the the log is not showing my infostructure & not showing any data in table output also.
am not able to populate data in the infostructure.Is there anything remained for updating configuration?
Regards
Surupa

Hi Rajesh,
Yes COOIS is T-code where U could retrive any information regarding the production order. But I would like to know if I have info-structure how i could configure reports in STD-SAP. Since I managing the production in 2 units of measure one is Kg and other in Lit. In COOIS i able to get report in kg but I also want report in Lit.
Thanks in advance for ur suggestions.
Regards,
Neel

LIS Info Structure

Hi all,
I got a problem when i created customized info structure.
This info structure is not getting data.Update mode is disabled.That means in OMO1 under updating tab
1."NO UPDATING"
2.Synchronous updating(1)
3.Asnnchronous updating(2)
4.Asnnchronous updating(3) are disabled. So please tell me how can we enabled them. In LBW1 I was able to change these updating, but still data is not populated into this info structure.So please inform me how the data is loaded into this info structure. Thanks in advance
N.PRASAD BABU

In OMO1 double click on the infostructure you want to change updating on. Select the update mode and periodicity and save. Make sure you set up the connections with BW and this infostructure (LBW0).
Then go into SPRO->Logistics - General->Logistics Information System (LIS)->Logistics Data Warehouse->Data Basis->Tools->Setup of Statistical Data->Application-Specific Setup of Statistical Data. Then choose application area of the data you want to set up.

Creating info structure in product allocation

Hi,
i was trying to configure to product allocation but doubt in the below step while trying to create info structure with MC21.. i am not able to find the below KF and characteristics fields as shown in the below document..kindly help.
Regards,
Vijesh

As already indicate to you in my previous post in Error product allocation
whatever doc you are following/referring, they have not using any standard infostructure for product allocation. The only difference between the Infostructure S140 & custom infostructure you are referring is of division. Instead of Customer group, you have Division in Characteristics.
So, for practicing purpose, try with infostructure S140.
Else, you need to understand how customs infostructure created or maintain in LIS/SIS. There many discussion on the same and you need to search and try. Accordingly, raise discussion for specific queries, while creating an Infostructure.
Thanks & Regards,
JP

Archiving: Info-structures and field catalogues

Hi there.
My question concerns the field catalogues which are used to configure info-structures for archiving objects.
As far as I understand it, I can only run reports via the Archive Explorer on the fields which I have included in the info-structure for an archiving object - is this correct? Or can I only use the fields in the info-structure for selection, but display all fields available in the archive-object?
As a last question: Can I create field catalogues with theoretically all of the available fields of an archiving object?
Thank you very much.
Andreas

Hello Andreas,
The fields that are transferred from the field catalog into the infostructure are used to assist with selecting the relevant archived data. The infostructure will contain the fields that have been transferred, plus the archive file name and the offset of where the archived data is stored. This gives you access to all of the data that was archived.
Technically, you can create a field catalog and relevant infostructure with all of the available fields, but I would not recommend that approach. The infostructure is a table in the database. So, the more fields that are used, the bigger this table will become and may defeat the purpose of archiving the data in the first place :-).
I hope this helps.
Regards,
Karin Tillotson
Message was edited by: Karin Tillotson

MCSI , Info structures

Hi there,
I want to read data from info structures like S920, S943, S948 etc. but i have too few key fields as parameter and each of these tables aproximately contains 20 million lines. As a result, it takes a lot of time for my 'SELECT' sentence to return results. None of these tables has indexes that works for my case and my basis team doesnt allow me to make new indexes for these tables because of DB capacity problems.
But, when i use transaction MCSI , it reads the same data from these tables and it takes much less time to return results. It uses RMCY9030 but when i set breakpoints at 'SELECT's of these program, none of these breakpoints work.
Can anyone suggest me a solution ?
Thanks.

Hi
As you want to add a new feild in the infostructure S901 then use t.code MC18 and then give your S901 infostrucuture and go to change mode go to MC19 and then add the new feild . and then in OMO1 check wheather your infostrucutre S901 is updated or not
Regards
Srinath

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

New info structure

Dear Experts,
we want to create new info structure ref to s039 i.e related to mc.9 for avarage stock purpose . in that we need to change only date option insted of month. could you provide configurarion document stpe by setp if have.
thnks in advance.
santosh

No configuration is required. For change a field in mc.9 report take ABAPer help. by default month field is given as input.

Transporting Info Structure configuration - or bypassing OMO1

Similar Messages

Maybe you are looking for