SIS - Re-organization of info structure data

Hi, can anyone advise if there's std SAP transaction to re-organise SIS data if there are errors due to update rules or master data such that we would like to re-update the values in the info structures?
Thanks
PP

IMG / LIS / Data warehouse / Database / Tools

Similar Messages

Info structure data

hi gurus,
which date is captured when creating info structure?
VBRP is the table. will it get the billing date or the created on date?
thanks!

Hi,
Is it for standard structure?
For customized infostructure you can assign field Billing date / Creation date.
-Alpesh

How to correct wrong data in SIS info structures

Hi,
Let's say at some point in time I configured the LIS wrongly such that the Sxxx (e.g. S001) tables were wrongly updated when I completed the sales order.
So now I go back to the LIS configuration to correct it, the Sxxx tables data remain the same.
Anybody knows which program I should run to correct the wrong data in the Sxxx tables? I have search in OSS notes and in this forum but could not find.
Thanks!

Hi Hweeling,
You can remove the incorrect data from info-structure using transaction OLIX.
Then you can reload the data using transactions:
OLI7 : Sales Order
OLI8 : Delivery
OLI9 : Billing
Be very careful when you execute transaction OLIX, delete only the specific Sales Document data which you want to. Then also reload those specific Sales Document data.
Hope this helps ...if yes then pls reward liberally
Kind Regards
Sachin Bhonsle

Info Structure rebuilt historical data

Hi All,
Iam planning to rebuilt historical data some self defined info structures, i tried with one info structure for orders/deliveries/invoices, it took more than 36 hours, is there any way to reduce this time??
Thanks in advance.

I recommend going through OSS Note 174134 - SIS: Collective note - reorganization (and allied notes inside it) and Note 19056 - SIS reorganization: Shorter runtimes by parallel processing
Regards,

Error when SIS info structure is generated

Hi All,
I have created in info structure for SIS. I am trying to generate it in MC24 transaction. I get the below error.
Message no. M2078
Diagnosis
The sum of the offset and length (=52) exceeds the
length of the start (=44) of
Can anybody help me how to correct this.
Regards,
Gijoy

Hi Nani
What error message the system gave??
Thanks
G. Lakshmipathi

Recovering data lost during change of unit of time for Info structure S061.

Dear Sir,
I have changed the period unit from 'month' to 'week' through SPRO>Logistic Data Warehouse>Activate update.
Due to this the data of Info Structure S061 is lost and when MCI3 transaction is executed the message " No Data found"
message is shown.
Kindly guide me how to get back the past data in MCI3.
Thanks and Regards,
R N Sabat.
Edited by: rnsabat on May 25, 2011 11:01 AM

Hi,
A update period of day/week will not work for S061. Any structure with costs must be set to month or posting period. See note [180047|https://service.sap.com/sap/support/notes/180047].
If you want to make cost evaluations in the information system, only use the period unit 'month' or the posting period.
Once you adjust the customizing it will be necessary to rebuild the info-structure S061 with OLPM transaction. This works on the basis that a temporary version is created e.g. &(1
This temporary version must then be copied to the live version 000 using transaction OLIX.
-Paul

Deleted data of info structure

Hi PP Gurus,
As per user's requirement I changed selection field period to day in report MCIS info structure S818. At that time I click ok in warning message of deletion previous data with the business approver's permission. But now he is saying that he wants historical data. Can anybody help me in this how to recollect historical data?
Jayesh
SAP PP
Edited by: Jayesh Narvankar on Feb 15, 2012 9:02 AM

Hi Ajit Kumar,
Thanks for your valuable help to me. I followed below steps -
1) Regenerate order cost: File PMCO - Removed test run, selected my order types and executed
2) PMIS: Statistical stup of infostructures - Info structure S818, save under version &(, number of parallel process 10, name of run TP02222012, packet size 1000 and clicked check box new run?. Then executed
3) Copy / delete version of an info structure - Info stucture S818, clicked on copy + delete. source version &(, target version 000, alredy radio button selected no copy method and checked box do not copy initional records. Then executed.
Suggest me me anything missed or any unnecessary step is there.
Everything ran succesfully in development server, but in quality server I am unable to do third step. When I am doing this third step in background system completeing this job in few seconds where as in development server it took more than 2 - 3 hours. In quality server log is showing 0 records converted.
Quality server is not allowing to do anything with version 000. Not allowing to take back up of version 000 or not allowing to delete data of version 000.
Ajit this is critical issue for me. Any cost client want historical data of infostructure S818. I am worried that in development server system allowed everything correctly and not allowing in quality server. Then how can do in production server.
Please help me
Jayesh Narvankar
9820477364

How to re-organize/reset the Info Structure S071?

Hello Everyone,
This is an extension to my previous thread [[No condition update from the sales orders exist - VK322 Message;]
How to re-organize the S071 info structure as I tried to re-organize it with Standard Program ' RV15F001' but it is not re-organizing this info structure... Any idea on this?
Regards,
Hrishi
Edited by: Hrishikesh Bhalwankar on Oct 11, 2011 2:35 AM

Hi Shiva,
I will check and get back to you on this.
Can you elaborate more on " To me it looks the issue is due to incorrect routine coding assigned in the value scale." please?
Regards,
Hrishi

Date fields for info structure S032 are not generated

Hi Experts,
I am trying to update set up tables for '02' using OLI2BW. I excluded some plants from selection and executed the set up. But the job run for few mins and completed with the message "Date fields for info structure S032 are not generated".
I couldn't see any records in RSA3.
Please through some light on this issue.
Points reward for usefull help.
Please no wild guess.
Regards,
-N-

Did you find out why. I am getting same message.
Thanks
Shalini

Variant selection for SIS Info Structures

Greetings all,
Our management is heavily reliant on using SIS for reporting key sales figures. We just implemented ECC 6.0, and a new Info Structure table was created.
Their main complaint is with the Get Selection Variant process. When the icon is clicked, the "Find Variant" popup window displays with the User Name. When User Name is cleared, all variants are displayed. They want to bypass the Find Variant popup, and go directly to the complete variant display grid. This is the behavior they see on other Info Structures that were defined.
I have tried searching in a number of places, including SCN, SDN, SAP Notes using various search terms, with no success.
Would someone kindly point me in the right direction?

Hai Robert,
In general the GET VARIANT will show all the variant list.
And it is not created for user specific.
Could you please give the Info structure fields and report to displays the field.
In case if you created the Variant please check with your ID is it asking for the User name.
Even with a user id input is there any change in the list of Variants?
Regards,
Mani

Rebate, see rebate payments in user defined info structure (SIS)

Hi Gurus...i hope you can help me
The client need to see the rebate payments for each material in a user define info structure (S500) where the material is a characteristic of the infostructure and the payment is a ratio
I get to show the accrued value per material but no the payment
If the system show me the accrued value for at material level in a infostructure..i supose is possible to show the payment value?
I did create a S520 info structure as copy of S060, but when i try to create a update rule for the payment ratio the system show me the follow message
"Only source fields from MC communications structures allowed"
please let me kow how i did wrong....
tx a lot

Payments of rebates in SAP ERP are credit notes (billing documents).
Therefore you should see them in the sales infosystem as billing documents.
If you add the billing document type in the sales infostructure as a characteristic, then you will be able to report on rebate payments because they always have a specific billing document type.

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 JAMPANI

Hi,
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

Creating a new info structure

Hi all,
I'm creating a new SIS info structure with MC21.
When save, the system warns me the followiing.
The warning appears when I remove the sales org. as characteristics.
My query is that what should I do? How to know which characteristcs link to the unit? Thanks.
Warning: inconsistencies may occur when units updated => please check
Message no. M2 314
Diagnosis
The characteristics you have chosen could lead to inconsistencies in the updating of the units.
Example:
The information structure does not contain a characteristic that clearly indicates the currency in which data is to be updated (for example, the sales organization); furthermore, the currency itself is not a characteristic of the information structure. If documents in differing currencies are now updated to the statistics, this can cause the system to add different values together in a data record.
Procedure
There are two possible ways you can guarantee that updating is consistent:
1. Add a field to your information structure that clearly identifies the unit, or add the unit itself as a characteristic.
2. Make sure that only documents which clearly refer to a unit are created.

Forgot to attach the code:
<cfset cfc_array = arrayNew(1) />
<cfset cfc_info = structNew() />
<cfset cfc_info.type = "error" />
<cfset cfc_info.message = "User Name and Password are both
required." />
<cfset ArrayAppend(cfc_array,cfc_info) />
<cfset cfc_info = structNew() />
<cfset cfc_info.type = "error" />
<cfset cfc_info.message = "dgdfgdgd dgdg dg dfg " />
<cfset ArrayAppend(cfc_array,cfc_info) />
<cfset cfc_info = structNew() />
<cfset cfc_info.type = "error" />
<cfset cfc_info.message = "Another structure test" />
<cfset ArrayAppend(cfc_array,cfc_info) />
<cfif isDefined("cfc_array")>
<cfdump var="#cfc_array#" />
<cfloop index="message" array="#cfc_array#">
<cfoutput>TYPE = #message.type# MESSAGE =
#message.message# </cfoutput>
</cfloop>
</cfif>

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

Info Structures

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,
Raj

Hello
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

SIS - Re-organization of info structure data

Similar Messages

Maybe you are looking for