Updation in LIS

Hi,
I am manually trying to update the sales orders and billing documents in LIS but no records are being updated.
While creating the version it shows that value is stored but when I try to copy and delete the temperory version it is not updating the order .
Please suggest how this can be resolved. ASAP
Regards!!

You should not update anything "manually" in LIS (how are you doing this, anyway?). Make sure the configuration is correct and update is set up, as suggested above. Make sure both customer and material are set up with statistical update, then create an order. LIS will be updated automatically, if everything has been done right.
Also look for update terminations in SM13.

Similar Messages

Synchronous and Asynchronous updating in LIS

Dear experts
What is the difference between
Synchronous and Asynchronous updating in LIS ?
There are three radio buttons for ASYNCHRONOUS UPDATING [1],[2],[3]
What is the significanse of each of them?
Regards
Siddharth

Hi siddarth
Difference between synchronous update & asynchronous update
Synchronous update -Immediate start, i.e., when an event takes place that triggers an update
Asynchronous update - Delayed start, i.e., updating is slightly delayed after an event that triggers an update
Regards
Srinath

Statiscal Updation of LIS Structure S026

Hi Experts
I have an issue of statistical updation of LIS structure S026.
With reference to SAP Note 64636, i have done the statiscal updation in OLI4 Transaction and saved the updates in different version.
Now i need to update the standard SAP version '000' from the version which i have generated.
Please tell me the step by step procedure to do the same. There are 2 procedures given in the note 64636, which is the best one to be followed?
Thanks & Regards
Bala

Hi,
In the SAP not itself the details will be there. I think the first solution would be good. You need not down your system, through online you can do this if the data is very less in the table.
This is to correct the data inconsistency. Copying the active version in to inactive version and delete the active version and again copy the inactive version in to active version.
Regards,
V. Suresh

Value in cusotm subtotal field is not updating in LIS (S) tables

Hello Experts,
All the existing subtotal vlues (provided by SAP) we have consumed based on the pricing procedure's requriement and we have created a new Z subtotal field (like ZZKZWI11) in pricing, it is working fine and the values are getting updated in VBAP and VBRP tables under the Z subtotal field for all the transactions.
I have included these new subtotal field in LIS table (S503 copy of S003). But the values are not getting upated in LIS table (S503). I have executing the statistical update of order and invoice with OLI7 and OLI9 transactions respectively. The all the data is updating in the S503 table except the new subtotal field.
Please let me know how to flow the data into this new subtotal field???
Thanks,
Sreehari.

The same way like from any other custom field. Have you searched SCN for similar questions before posting? Google -> 'SIS custom field site:sap.com' finds this old post and others.
SAP Help article was moved, here is the new link: http://help.sap.com/saphelp_46c/helpdata/en/fb/23ee347a34d111a4620060b03c3b0e/frameset.htm

SKF updation through LIS

I am trying to update a statistical key figure value from the production side. I have made the assignment to Production Order Quantity to LIS structure assignment. However, while doing KVA5, system is not updating anything. In fact lot of production orders were released and settled. When I analyse the messages, it was found as follows: "No statistical key figures with variants were found for object CTR 1000/110010 in fiscal year 2010 for LIS reference"

Hi
Check your material master (MRP views or Work Scheduling views) or check with your PP guys as to in which Unit of Measure (UoM) are they doing GR
Your UoM in SKF has to be the same as PP's UoM or atbest, maintain a conversion between the 2 UoMs if they are different...
there is a place in IMG where there conversions are maintained.. I dont know the path.. MM or PP person should be able to tell you that
Regards
Ajay M

Activation of updates for LIS

Dear all,
In the table TMC2S, for the field name STAFO(Update group for statistics update) i have made a group 000001 and for the field MCINF(Name of information structure) i have made one structure S990. But in the Delivery and maintenance view of the table TMC2S, Data Broswer/Table view maint. field is coming with restriction message "Display/Maintenance allowed with restrictions". How would i get rid from this restriction.Please help.
Regards,
Munmun Das Neogi.
Edited by: Munmun Das Neogi on Jan 7, 2009 5:32 PM

One option: uninstall CS4 and 8 then reinstall CS4 (no need to reinstall 8 - just insert the v8 serial no when prompted)

SAP SD LIS AND SIS UPDATION

HI Friends
Please guide me where we have to do the stting for get the Standard Report updations. (LIS AND SIS).Please Give me the configuration guie lines.
Regards,
Udhay

Hi,
pls. see the answer from Naren in the below link. hope that helps you.
/message/4035570#4035570 [original link is broken]
Br, Sats.

Sales Value not updated in credit check

Hai Guys,
I am facing an important issue in the Credit check. The Sales value (SO / Dly made but not delivered / billed) is not reflecting in the credit check.
1. I created a step in the pricing procedure and assigned its 'subtotal' to A (KOMP-CMPRE) - so that it can be taken for credit update.
2. I had activated the update of LIS S066 - for Sales Order credit
3. In the automatic credit control, I have checked the Open SO & Deliveries
Still my credit check is not checking the open SO & Dly.
Can somebody help me in this regard.
Regards,
Maheshwaran. I

Hi
Check whether you have entered the credit control area to that customer in XD02.
Use the Update group 000012
o   Sales order
      -   Increases open order value from delivery-relevant schedule lines
o   Delivery
      -   Reduces open order value from delivery-relevant schedule lines
      -   Increases open delivery value
o   Billing document
Reduces open delivery value
Increases open billing document value
Financial accounting document
Reduces open billing document value
regards
Edited by: Prashanth on Jun 10, 2009 2:52 PM

Error 4 occurred while information structure S001 was being updated.

Hi experts,
I set up the environment for the 2LIS_01_S001 DataSource (InfoCube 0SD_C01) accordingly these steps (as mentioned in another thread):
1) Activating LIS update - goto OMO1 transaction code
In the Updating Info Structures(S001) - double-click the Updating radio button for Info structure S001.
In the Parameters dialog box select Synchronous updating and choose ok.
2) Goto OLI7 Transaction code - run the statistical update.
3) Goto OLIX transaction code - setup version &( will be copied to actual version 000 for reporting
4)Go back to OMO1 do deactive the LIS Update, check radio button to "No Update"
5)Now goto LBW0 and choose option "Deactivate" Delta updating in LIS.
6) In BW, Replicate DataSource, and run info Package with Initilization.
7) Now again in R/3 we need to "Activate" Delta option from transaction code LBW0.
8) and last step is to goto OMO1 to activate LIS Update to Synchronous updating and save.
But in step 2 , I am getting an error i.e
Error 4 updating info structure S001
Message no. M2022
Error 4 occurred while information structure S001 was being updated.
The update was attempted with the following key:
&V3 0100000000000000290658
I am not understanding this error,so cant proceed further.
waiting for ur replies.
Thanks in advance.

Hi Colum
I have two systems in both i am doing the same process.
But in my one system i am getting error
but in my other system i am not getting error and my set up table is filled with records.
According to that note key figures sequence in S001, S001BIW1 & S001BIW2 should be same.
but i my other system, key figure sequence is different and i am fine working with it.
so why it is not able to fill my set up table for my other system ?
thanks in advance.

About data transfer/update rules setup

Hi All,
After this BW loading project, I am wondering if anyone can confirm with my issues.
--What is the difference between'initail load & full load'? Examples to use them, please.
--If i use V3 to update, can I choose weekly? some expert told me that i can change the setting in OMO1 after first time loading. I tried it and it didn't work. Why???
--If we loaded into ODS and re-loaded to Cube, should I have the same loading schedules(update rules) for ODS and Cube?? (ex: both full load and weekly)?
--The update rule in OMO1 is for transfer datasource to BW and is nothing about ODS and CUBE loading, Am I right?
--Should I have the same keys for ODS and Cube?
--How can system not replicate loading? EX: every month sales order loading.
Thank you for helping me to understanding data loading in BW.

Hi John,
Here are the answer
--What is the difference between'initail load & full load'?
Ans:-Initial load means initialization which is one time activity if you do not provide any selection criteria while initialization ( this will take your all data to BW depends on extractor you are using ) once that is successful you need to switch your load to delta when you do this only records which are changed will be fetched.
Full load means al records will be fetched and will be aggregated whether you should go for initialization or full load depends on your data requirement.
--If i use V3 to update, can I choose weekly? some expert told me that i can change the setting in OMO1 after first time loading. I tried it and it didn't work. Why???
Ans :--> I think if you are using Lo then you can change this in LBWE job control . OMO1 is if you are using LIS and you want to switch your update in LIS delta tables then the procedure is to go in LBW0 first deactivate your delta mechanism by putting your infostructure name then go to OMO1 and change your control parameter to schedule your delta mechanism on.
--If we loaded into ODS and re-loaded to Cube, should I have the same loading schedules(update rules) for ODS and Cube?? (ex: both full load and weekly)?
Ans:--> Not compulsory but good to have same schedule I mean as soon as ODS is loaded successfully start the load for cube.
--The update rule in OMO1 is for transfer datasource to BW and is nothing about ODS and CUBE loading, Am I right?
Ans -->yes you are right but let me make some correction
in OMO1 update parameters are for switching of delta tables of LIS .
--Should I have the same keys for ODS and Cube?
Ans--> Not compulsory depends on your business logic.
--How can system not replicate loading? EX: every month sales order loading.
Ans--> question not clear for me.
Hope this will help you .
Suneel

P6 web service update activity date

Hi guys,
I am using P6 web service to display the activity start and finish date in a .net web application.
When I change the finish date on the website, the date in p6 will also be updated. However, the date in p6 is always one work-day earlier than date in my web site.
For example, I read the date from P6 to web. It is 02-March-2014, same in P6 and my web. Then I change it to 12-Nov-2014, click update. The UpdateActivitiesResponse is true.
Then I go to P6 and refresh the date, the corresponding date become 11-Nov-2014.
The problem only happens on those un-actualized finish date. The activity start dates and actualized finish date can be updated perfectly.
Anybody has some idea about this bug? I don't think it is the web service problem, maybe the setting up of the project.
Thank you in advance.
Michelle

Hi Kean,
when you are updating an existing line you must use SetCurrentLine so the UI knows which line you want to update. Here is a short sample where i will update the quatity and price of every line in my existing sales order:
    Dim oSO As SAPbobsCOM.Documents
    Dim i As Integer
    Set oSO = ocmp.GetBusinessObject(oOrders)
    If oSO.GetByKey(191) = True Then
        If oSO.Lines.Count > 0 Then
            For i = 0 To oSO.Lines.Count - 1
            oSO.Lines.SetCurrentLine
            oSO.Lines.Quantity = 200
            oSO.Lines.UnitPrice = 10
            Next i
        End If
    End If
    ret = oSO.Update
Cheers,
Lisa
Business One Forums Team

Creating LIS tables

Hi all,
I need to create LIS tables, tables that start with 'S'.
How can I create them?
Thanks.

hi
good
This is bound to happened especially if the users made changes to the Purchase Order and you have set the online updates for your LIS. Fields like Material groups are consider keys fields and should not be change as it somehow impact the updates to LIS.
If the figures are wrong for a particular period, you can do a reorganization for all the Purchase Order for the particular months.
Assuming that you want to reorganize the whole S012.
When you execute OLI3, it will locked any Purchase Order that it is processing. Therefore, it is advisable to run it during off office hours.
First Step :-
OLI3 - Statistical setup of info structures from purchasing documents
Info structure to be set up S012
Save under version &(
Tick Delete/create indices
Specify the Purchasing Documents or Document Date
Name of run S012-1
Tick New run?
Date of termination 99.99.9999
Time of termination 99:99:99
Tick Redetermine update group?
Tick Update documents?
NPRT - Log for Setup of Statistical Data
thanks
mrutyun^

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

Lis and lo extraction doubt

hai to every body,
i have an doubt on lis and lo extraction
In lis extraction we have an information structure(IS).before extraction we all delete the contents of IS.Then by scheduling the v1 or v2 job we update data from database tables to IS by running statistical setup.
but in los we have an setup tables.before extractiopn we all delete data from setup tables.then by running statistical setup we fill the setup tables with dtatbse data.
which job(v1 or v2) scheduling between databse tables and setup tables

Hi uday,
To tell you, we wont delete the content of Information Structure in LIS, Because, in LIS, whenever,a user do a transaction, that record will automatically updated in the Information structure.
Where as, if you consider LO, whenever, a user generates a transaction, that records wont be updated in the setup tables, they are directly moved to delta tables(like RSA7 etc). Only when you do statistical setup, this setup tables are updated, later on these tables are not updated, unlike LIS.
Only for this, we wont delete the information structure everytime,where as LO we delete the setup tables whenever we do init.
Thanks
Vijay

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

Updation in LIS

Similar Messages

Maybe you are looking for