Info structure activation
Dear friends,
I createated a new plant... But I am not able to run the reports which are PP infostucture related. while running the reports Like MCRX, MCRV etc.. system is giving a message saying that no data exists for chosen selection. In the remaining plants I am able to run these reports. Please let me know ... what could be the problem. Please note that I already confirmed and did goods movements in this plant.
Regards,
Surya.
Dear,
Message no M5017 ??
When the Info structures are re-generated, the old data is deleted.
U can run the transaction for archive set-up to get the old data back into the Info structure MCSI
updated rules and then transports it.
Goto COR4 or OPL8 -> activate "Statistics" / update check box Under the Shop floor infor sytem at implementaion tab for order type/Plant combiantion.
Then create New order and do the confirmation with GI & GR,
Now run the reports and check.
Regards,
R.Brahmankar
Similar Messages
-
Info structure activation problems in data archiving
Error in info structure ARCH_IS_DSSCOPA analysis program in line 412
Message no. Q6227
Diagnosis
There is a syntax error in line 412 of the generated reporting
program for the archive information structure ARCH_IS_DSSCOPA.
The error message is: Field "AINT01" already defined ...
Field "AINT01" already defined
Procedure
It is probably caused by a system error. The following activities may
solve the problem:
Check the definition of the archive information structre and the underlying field catalog.
You should contact the SAP Hotline if the problem appears for an SAP- standard info structure or an SAP-standard field catalog.
Further notes
Alternatively you can find a program whose name begins with "GP$ERR$" (search with "GP$ERR$*"). This program contains the incorrectly generated code.
Kindly let me know , how to activate the same.
Regards,
BALAMURALI JAMPANIHi,
This forum is for SAP Business One users only. Please check the subject of the forum. Post it on a proper forum and close this one.
Thanks,
Gordon -
Caution: Info structures S026 and S226 are active for repetitive mfg
Hi,
When I run the standard report MCRO - Material Usage Analysis: Repetetive Manufacturing, I am getting the message
Caution: Info structures S026 and S226 are active for repetitive mfg
How to overcome this.
thanks and regards
muruHi,
Try Thi - might work.:
1) Before running the tcode MCRO - (i.e type MCRO in the commond prompt and then do the next steps)
2) Menu- Got to- User settings
3) Default your user name will be there.
4) Now start selecting key figures and charecteristics.
Save and try to execute. -
Hi All,
We have a requirement where we need to enhance CRM UI archive search with custom fields for CRM activity Object CRM_ACT_ON. As per my analysis Standard Archive Search for activity Uses info structure SAP_CRM_ACT for searching archived data.
But when we are trying to add custom fields into above field catalog, it is treated as modification. But Modification is not allowed in our landscape.
Standard infostructure is harcoded in SAP standard method ARCHIVING_READ of class CL_CRM_REPORT_ACC_DYNAMIC which is called as part of the process. So we are not able to go ahead with custom info structure.
Can you please le me know if there are any alternative way to meet above requirement or I have missed any steps.
Thanks & Regards,
SujitHello Thomas,
Maybe this link can help.
add new field to search criteria and result.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0747ac2-ffd9-2910-de9a-8a3dc44da8b4?QuickLink=index&overridelayout=true&12966506314316
Search Options - Knowledge Management - SAP Library
regards,
Grace -
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
SurupaHi 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 -
Hi All,
we have an info structure S901 which has characteristics
Sold-to party
Sales Organization
Distribution Channel
Division
Material
WBS Element
Document currency
Controlling Area
Profit Center
My question is if i add a filed "Business Area" to the existing info structure (S901) will there be any data inconsistency?
Regards,
RajHello
Yes because you are changing the infiostructure and adding new characteristics.When you do this you will have to delete the data in the active version in Production system.And then update the new infostructure again with the old documents.Depending on the old data it may take more than a day and requires system outage as well.
Thanks
Vikas -
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,
- ChetanHI,
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 -
LIS Info Structure with table MKPF/MSEG
Hi Gurus,
I have a view made up of table MKPF/MSEG (74 fields in totals). Based on my requirement (loading archived and non archived marerial movements data) I am looking to create an Info structure with the same 74 fields - to connect the LIS infostructures to BW.
I need to create a char. as KF fields catalog.
my issue is while doing that I am not able to have the 74 fields I am looking for (I am just getting around 50).
I know how to create an Infostructure/ Catalogue (Transaction MC21/MC18)
Any Idea how to Create an Info Structure that would have all the fields from table MKPF and MSEG?
Regards
Edited by: Blaiso on Jun 2, 2011 6:10 PMHi,
Steps in LIS EXTRACTION:
T.code u2013 :MC18 u2013 create field catalog
1. Characteristic Catalog
Application-01-Sales and Distribution, 02-Purchasing, 03-Inventory Controlling, etc..
Catalog category 1. Characteristic catalog, 2. Key figures catalog 3. Date catalog Select characteristic catalog and enter, click on characteristic select the source table and it will be display the relevant source field and select the source field, copy + close, copy.
Save, similarly create key figures catalog
T.code : MC21 u2013 create infostructure
Example u2013
Inforstructure : S789
Application u2013 01
Choose characteristic select the catalog, select the fields, copy + close Choose key figures catalog select the key figures ,copy + close, save and generate
T.code u2013 MC24 u2013 create updating
Infostructure : S789
Update group : 01- Sales document, delivery, billing document ,enter Select the key figures click on rules for key figures give suggest rules, copy save and generate Click on updating (activate updating) Select the infostructure set periodic split 1. Daily, 2. Week, 3. Month, 4. Posting period Updating u20131)No updating,2)Synchronous updating (V1), 3)As synchronous updating (V2), 4)As synchronous updating (V3),
T.code u2013 LBW0 u2013 Connection of LIS Information structures to SAPBW Information structure : S786 Select the radio button-Setup LIS environment and Execute.
Select the radio button-Generate data source and Execute.
For Delta update:
Select the radio button-Generate updating and Execute Select the radio button -Activate / deactivate and Execute.
T.code u2013 SBIW u2013 Display IMG (implementation guide) Setting for applications specific data source u2013 logistics u2013 Managing transfer information structure u2013 setup of statistical data u2013 applications specific setup of statistical data u2013perform statistical setup u2013 sales.
Choose activity
Setup u2013 Orders, deliveries, billing
Choose the activities enter the infostructure (S789), give name of the run, date of termination, time of termination, No. of tolerated faulty documents. Then execute
T.code u2013 RSA3 u2013 Extractor checker
Give the data source name eg. 2LIS 01S789 and execute, result will get some records Go to BW side replicate data source u2013 Assign infosource u2013 Create infocube u2013 Create update rules u2013 create infopackage and schedule the package with initialize delta process.
For delta update :
In R/3 side
T.code u2013 MC25, set update (V1) or (V2) or (V3)
T.code u2013 LBW0, choose generate updating and execute then choose activate / deactivate and execute
BW side u2013 create infopackage and schedule the package with delta update.
First time if your scheduling the infopackage -in R/3 side T.code :MC25 -Udating set to No update,insted of selecting the update V1,V2,V3.
If your doing the Delta update:in R/3 side T.code :MC25-Updating set to either V1 or V2 or V3. and the to T.code :LBW0 -Select the radio button Active/deactivate and Execute.
and schedule the infopackage with delta update.
Modules for LIS : SD,MM, PP,QM.
Deltas for LIS:
After setting up the LIS environment, 2 transparent tables and 1 extract structure is generated for this particular info structure. Within transaction SE11 you can view the tables u2018SnnnBIW1u2019, u2018SnnnBIW2u2019 and the structure u2018SnnnBIWSu2019 and the InfoStructure itself u201ASnnnu2018
The tables S5nnnBIW1 & SnnnnBIW2 are used to assist the delta update process within BW.
Extract structure u2018SnnnnBIWCu2019 is used as an interface structure between OLTP InfoStructure and BW
The OLTP system has automatically created an entry in the control table u2018TMCBIWu2019. Within transaction u2018SE16u2019 youu2019ll see, that for your particular InfoStructure the field u2018BIW activeu2019 has the value u2018Xu2019 and the field u2018BIW statusu2019 is filled with value u20181u2019 (refers to table SnnnBIW1).
The orgininal LIS update program u201ARMCX#### will be enhanced within the form routines u201Aform Snnnbiw1_update_u2026.u2018 and u201Aform Snnnbiw2_update
With the transaction u2018SE38u2019 youu2019ll see at the end of the program starting at line 870 / 1006, that the program is enhanced within a u2018BIW delta updateu2019 coding
Within the flag u201AActivate/Deactivateu2018 the update process into the delta tables (SnnnBIW1/Sn5nnBIW2) is swichted on/off. In the table u201ATMCBIWu2018 is defined, which table is active for delta update.
Regards,
Prakash -
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 -
Querry regarding Info Structure
Dear All,
I have created a Info structure by copying S070 info structure. I have created an update rule and activated the updating also, but when i use this info structure in MCI7 (Info system) no data is displayed in that screen. Only ' 0 ' is displayed in all the fields.
I am not able to understand where am i going wrong, I would request you to please help me solve the above issue.
If possible please reply with detail procedure of creating new Info Structure.
Regards,
Rashmi PotdarHi
Characterstics used as criteria according to which the data record is selected in info structure, in this case you can add new characterstics for searching creteria, but it is not recomanded to delete the old one as this is only searching creteria. yes you need to re-generate the info structure after every updates.
regards
Vivek. -
Product Allocation S140 Info structure.
Hello Experts,
We have configured the setting related Availability check against Product Allocation.
Everything is fine except for S140 Infostructure. We are using Flexible Plan. The Info structure is getting updated whenever we create an order and the qty is confirmed. How do the other fields gets updated?( Product allocation qty & customer requirements are initial upload by the client. Order qty is getting updated whenever order is created. Other fields Def.division, Open product allocation qty and requirements not covered are not getting updated. formulas have been activated.
How and when the other fields will be updated? Aniticipating your answers.
Thanks In Advance.Yes
-
Hi all,
I have created one info structure S987. Updation rules are also applied to it. The problem is when i am activating this info structure in t code OMOR the contro indicator under updating tab are in grey mode .i.e not changable(By default no updating control indicator is on ) where as for standard infostructure it is allowing me to change
Because of above problem i am not getting any data in this newly created info structurethanks
-
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,
PMGoto 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 -
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 -
Dear All,
I am trying to run T-code MCRX. But the system Is not generating any results.On some investigation I found that the Info structure SO26 is not activated Which I subsequently did in COR4. Now Still I am not able to generate any result. I cam across one thread where it was mentioned that doing this cause the Old data to get deleted. If that is the case how to bring that data back.
Is there any way.
Please advice.
Regards,
VIvekplease create new data (or wait for someone) and run MCRX again.
(make sure your info-structure is activated)
good luck.
Maybe you are looking for
-
Any help appreciated jsp...
hi ive got a problem regarding jsp.... for starters i cant even view the jsp examples on the tomcat index page.... the servlet examples run fine and i can create my own servlets as well.. but when i try to create my own simple jsp page or run the exa
-
I have an old version of InDesign CS5, have not used in a while..about a year. It will not load nor allow me to uninstall and reinstall, please help. I have original discs and serial number. How can I fix this?
-
Where do email attachments go after they are saved?
I tap the pic attached to the email and "save" appears. I tap "save" and enter a filename, and then "ok." So...where is the picture now? I've looked in the pictures folder, and all through file manager, and re-started the playbook and repeated all of
-
How to stop autoplay of videos?
June 2013: videos on websites start playing without my permission, how to stop this? What I tried: I uninstalled Adobe Flash (disabling Flash add-on didn't work), existing "stop autoplay" add-ons are no longer working according to reviews, tried solu
-
Make field in Material master mandatory based on the material group
Hello all, I need to make the field "post to inspection flag" mandatory based on the material group while creating the Material master. I found options for making the field mandatory based on Material type,Industry sector and plant NOT based on the m