LIS Update Mode

Hello Experts,
I am working in BI 7.0.
I have a question about 'Direct Delta'. I have planned to use 'Direct Delta' update mode for 2LIS_11_VAITM, 2LIS_13_VDITM and 2LIS_12_VCITM. There would be delta extractions of documents up to 10000 for my customer. Am I right about using Direct Delta' ?
And, when using 'Direct Delta' , what happens about Setting Tables? I mean, could you explain technically and step by step how to load data from R/3 while using 'Direct Delta' ? Should I use set-up tables?
Thank you very much.
Points waiting for you.

HI Muju,
In case of queued delta LUW's r posted to extractor queue
by scheduling V3job we move the documents from Extactor
queue to Delta queue and we extract LUW's from Deltaqueue
to SAP BW by running Delta loadsQueued delta maintains
Extractor log to handle the LUW's which r missed.
In case of Direct delta LUW's r directly posted to Delta
Queue(RSA7)and we extact the LUW's from DeltaQueue to SAP
BW by running Delta loads.It degrades the OLTP performance
becoz when LUW's r directly posted to DeltaQueue the
application is kept waiting until all the enhancement code
is executed.
Queued Delta is better than Direct Delta for performance reasons.
Hope it Helps
Srini

Similar Messages

V1, V2, V3 update modes

Hi,
Can anyone tell me what are V1, V2, V3 update modes. Please tell me the difference between all the three. Are there any other update modes? How are the above different from - Direct Delta , Queued delta and unserialized v3 update methods?
Am actually very confused with the above topics.
It would be great if someone could explain in details.
Thanks in advance,
maddy

Hi Maddy.
V1 denotes time-critical updates used for updating the
actual transaction tables.
V2 denotes non-time-critical updates used for updating
statistics tables related to the transaction tables.
For instance, after a sales order entry transaction
is completed, the corresponding sales order tables would be
updated in V1 mode, and the corresponding statistics tables
would be updated in V2 mode.
V3 update mode(Uses delta queue technology) is similar
to the V2 update mode. The main difference is that V2
updates are always triggered by applications, while V3
updates may be scheduled independently. Many extraction
programs available for mySAP.com applications today use the
delta queue technology to identify deltas.
and also check this
hi
V1,V2,V3 updates
v1, v2,and v3 updates
V1, V2 and V3 updates in LO
LO Cockpit contains a set of extract structures and enable extraction of logistics data to your SAP BI system via logistics DataSources.
Check the following links
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
LOGISTIC COCKPIT DELTA MECHANISM - Episode two: V3 Update, when some problems can occur...
LOGISTIC COCKPIT DELTA MECHANISM - Episode three: the new update methods
LOGISTIC COCKPIT - WHEN YOU NEED MORE - First option: enhance it !
LOGISTIC COCKPIT: a new deal overshadowed by the old-fashioned LIS ?
Also check the step by step guide below.
http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
thanks
sreeni

Lock records when in Update Mode / problem with 2 users on 1 document

Hi,
when user A updates e.g. a purchase order and user B goes into this purchase order and updates e.g. the remark before user A, then user A cannot save his changes. Imagine user A has put in several new lines and has made several price adjustments, his work will be gone.
In most cases this should not happen very often, but it could. Since B1 recognizes when another user has updated the document before, it should be possible to solve this situation more convenient (either by lock, saving to a new document, comparing to the old version, etc).
Thank you
Sebastian

Hi Sebastian,
Your request is understandable. It may not have big problem to change current process by coding. However to lock records whenever in update mode, that could create too many locks. It is basically not good for performance. The trade off may be allowing save as function. However, this may not be a desirable solution for most end users.
Thanks,
Gordon

Master Data loading got failed: error "Update mode R is not supported by th

Hello Experts,
I use to load master data for 0Customer_Attr though daily process chain, it was running successfully.
For last 2 days master data loading for 0Customer_Attr got failed and it gives following error message:
"Update mode R is not supported by the extraction API"
Can anyone tell me what is that error for? how to resolve this issue?
Regards,
Nirav

Hi
Update mode R error will come in the below case
You are running a delta (for master data) which afils due to some error. to resolve that error, you make the load red and try to repeat the load.
This time the load will fail with update mode R.
As repeat delta is not supported.
So, now, the only thing you can do is to reinit the delta(as told in above posts) and then you can proceed. The earlier problem has nothing to do with update mode R.
example your fiorst delta failed with replication issue.
only replicating and repeaing will not solve the update mode R.
you will have to do both replication of the data source and re-int for the update mode R.
One more thing I would like to add is.
If the the delat which failed with error the first time(not update mode R), then
you have to do init with data transfer
if it failed without picking any records,
then do init without data transfer.
Hope this helps
Regards
Shilpa
Edited by: Shilpa Vinayak on Oct 14, 2008 12:48 PM

ERROR: Update mode C is not supported by the extraction API - R3 11

Hi gurus,
I just tryed to implement the solution I found at this link:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-dbb4356cf4bf
The data source is based on an Infoset on the KONV R/3 Table.
I setted the AIM delta process and I did all the activities as written in the document.
The process works if I load data to bw in "full", with "Init without data transfer" and "delta" mode. Of course if I change a Purchase document, it will be posted in the delta queue and then loaded to bw with the next delta load.
The "initialize delta process" (with data) doesen't work and returns the following error:
Update mode C is not supported by the extraction API
the error code is R3 11.
have you any idea about it???
Thanks!!!
Regards!
Matteo

Hi,
for me it sounds quite simple. It is that the update mode 'C' get flagged as 'not allowed' for this extractor. Did you check with rsa3? I guess you will get the same error message. May be you can start debugging in rsa3 to find the place where the update mode gets checked.
Anyway, it shouldn't be a issue as you have a workaround. May be you should raise a error message at sap because of this.
regards
Siggi

How to use a single page for create and update mode.

Hi,
I need to develop a single page to be used for both create and update modes.
I am going to use a variable MODE
and i will set this in the emp summary page.
Based on the button clicked by the user i have to render the JSF page.
For tis if the user selects a perticular and cliks on update thn i will pass the empno to the next.
so there in the next i will appy a ViewCreiteria on my View Obj to fetch only that row so that only that emp will be displayed ion update mode.
This is working fione for me.
So now the issue is
when the user clicks on CreatEmp button.
i need to enable my VO for insert operations.
for this i wrote the code like this in the beforePhase event
FacesContext ctx = FacesContext.getCurrentInstance();
ValueBinding valBinding = ctx.getApplication().createValueBinding("#{data}");
BindingContext bContext = (BindingContext) valBinding.getValue(ctx);
DCDataControl dcControl = bContext.findDataControl("DataControl");
Application app = ctx.getApplication();
ApplicationModule am = (ApplicationModule) dcControl.getDataProvider();
System.out.println("After Appmodule initiation");
// get the VO reference and initiate the query
System.out.println("Before Page VO initiation");
PrismDmPageSectionViewImpl vo = (ViewImpl)am.findViewObject("View");
//ViewRowImpl row = (ViewRowImpl) vo.createRow();
/* TO CREATE AN EMPTY ROW*/
Row row=vo.createRow();
System.out.println("New Row is created");
//vo.createKey(row);
vo.insertRow(row);
vo.setCurrentRow(row);
By doing this a new empty page is rendered.
But when i fill up the values and click on ok.. i am getting the error like this..
JBO-27023: Failed to validate all rows in a transaction.
JBO-27027: Missing mandatory attributes for a row with key null of type View3
JBO-27014: Attribute Id in View3 is required
JBO-27014: Attribute PageeId in View3 is required
Please point me out where i am missing.
Thanks

Hi,
In my opinion you are over complicating things.
This is what I do for using the sme page as both create and update without all this code.
1) Create a browse page containing a an adf table with a select one component bound to your view object.
2) Create an additional edit page containing only an edit form containing fields of your view object that your users must enter in order to add or edit rows.
3) Link the pages in the JSF diagram with an "edit" navigation case from browse to edit page and a "return" navigation case from edit to browse (make sure that redirect option is NOT set on both cases)
4) Remove the submit button from the edit page and add two application module bindings for the commit and rollback operations as command buttons in the form footer facet. Make sure that both buttons has an action of return and that their disabled property is set to false. You will probably change their labels to ok and cancel respectively.
5) Drop a create action for your view object from the data control palette inside your page as a command button and set the action property to edit also.
3) Set the action property of the view button to edit
This should basically work without any code from your part. -- at least it does so for me -- if you like to make it a bit more funcy you may add am action listener inside your buttons and set a requeScope variable for example #{requestScope.editing} to true or false depending on the button clicked. Then add a title to your page with a value like #{requestScope.editing == true ? 'Editing record' : 'Adding a new record'}..
Hope that helps.
Thanassis

Changing update mode in Error DTP

Hi Gurus,
I have some issues with data in PSA. I am trying to solve it using Error DTP.
While Executing DTP one record failed to load giving bad request. Now i created an error DTP. By default the extraction mode is Delta.
DTP extraction Mode->Full
Error DTP Extraction Mode -> Delta; How can i make it full. If i amm trying to change it, The option is disabled.
Thanks in advance!
Regards
Anu

Hi Anu,
In my system original DTP is full and when i create error DTP, i got error DTP extraction mode is full.
Yes you are right, it is disabled.can you check the update mode of your original DTP once.
once the error DTP is created, we can not change the update of it.
Regards,
Venkatesh.

I have updated to IOS 6, the App store won't work, is stuck in update mode for 1 day and the battery now goes flat in 3 hrs without use. Can I go back to IOS 5?

Hi, I was forced to upgrade to IOS 6 due to a restore.
Since the upgrade, I have lost information, the App store is stuck in update mode, my battery drains in hours and many more problems.
Is there a way to go back to the VERY RELIABLE IOS 5? This phone is nearly useless now.
Thanks

Just FYI - the situation is resolved. I downloaded the new snow leopard 10.6.8 update for safari and now itunes works. I have no idea what that has to do with anything - but I saw it on another forum and it actually worked.

Segment E1PITYP occurs for each subtype of Infotype 1001 in update mode

Hi,
I am using transaction PFAL and IDoc HRMD_A for transferring HR data.
In update mode the resulting IDoc contains segment E1PITYP for each subtyp (for example A002) of Infotype 1001 even if it contains no segments of type E1P1001.
Could somebody explain this and is it possible to avoid this behavior?
Thanks and regards
Patrick

Hi,
thanks for your answer.
Still I am little bit confused and want give an more detailed description of my problem.
If I export an organizational unit in initial mode I have for example 5 segments of type E1PITYP and each of them has a subsegment (for example E1P1001).
Export of the same organizational unit in update mode results in more than 200 segments of type E1PITYP and all of them without subsegment.
This seems to happen for all infotypes (not only 1001 like I thought before).
Now I want to understand why this happens and if it's possible to update an organizational unit without segments of type E1PITYP that don't have a subsegment.
Regards
Patrick

How to capture the change in the update mode (for Inventory) in a transport

Hi all,
I recently changed the update mode for Inventory Controlling from Unserialized V3 Update to Queued delta in R/3 DEV environment. When I was doing the change it did not prompt for a transport request. Now I have to somehow capture this in a transport and move it to R/3 Quality environment. How do I capture this change in a transport.
Thanks in advance,
Ram Kumar.

there are 2 options
1) try changing back and forth and see if it prompts for a request
2) Create a customizing request and add the following entry into the request
Program ID - R3TR; Object type - TABU; Object name - TMCEXUPD
and make the entry ...How ?? Click on the key that you see under the column 'Function'
client/application component.. if client is 100 and application component is 11
then the table entry should be 10011
Assign points if it helps
P.S:if you check the table TMCEXUPD shows you the update mode
Edited by: KK on May 28, 2008 1:52 PM

How to identify update mode in function module for generic extractor

Hi All,
I have created generic extractor using function module which supports delta load.
Delta logic is handeled in coding...by using ROOSGENDLM table.
Now problem is we need to identify the update mode, requested from infopackage in our function module in order to apply logic for Repair full.
I would like to know table or parameter in source system, which contain the update mode (Init , Delta , Full).
Thanks,
Niraj

Hi Niraj
You can use the FM import parameter "i_updmode" (This is of type "SBIWA_S_INTERFACE-UPDMODE") to determine if infopackage triggerred in full or delta mode.
I_REQUNR     TYPE     SBIWA_S_INTERFACE-REQUNR
I_ISOURCE     TYPE     SBIWA_S_INTERFACE-ISOURCE                               InfoSource Name
I_MAXSIZE     TYPE     SBIWA_S_INTERFACE-MAXSIZE                               Data Packet size
I_INITFLAG     TYPE     SBIWA_S_INTERFACE-INITFLAG                               Initial Flag
I_UPDMODE     TYPE     SBIWA_S_INTERFACE-UPDMODE                               Update Mode
I_DATAPAKID     TYPE     SBIWA_S_INTERFACE-DATAPAKID                               Datapacket Id
I_PRIVATE_MODE
I_CALLMODE     TYPE     ROARCHD200-CALLMODE                               Single-Character Flag
I_REMOTE_CALL     TYPE     SBIWA_FLAG
Cheers
Vasu Sattenapalli

Report to Form (in Update mode), update, "Close" back to report (just like QBE).

Alright, I have been through the entire board and found bit and pieces here and there on how to do this, but I am not satisfied with the results. Answers to these questions will dictate whether we use this product or not.
1) The QBE solution is great for the above EXCEPT I am unable (it seems) to make updates to the form portion of the Report/Form combination. I need to be able to lock off certain fields and disallow certain functions. Other's have asked whether this can be done. No answers issued forth.
Is there some way short of hacking into the PL/SQL code of updating the form on a wizard created QBE?
2) I was able to create my own report, link (via link object) to a custom form (update the form as I needed). Now I would like my users not to have to hit the query button (which is absurd in this case because they already have the proper record displayed). So I need to open the form in "update" mode. I have seen some different approaches to this on the board, and all kinds of code, but is there a simple way to do this (preferably from the tool, not hacking code)?
I see the code in the various posting (including the FAQ), the question is where I put in in the context of my link from report to form (if it is in the native pl/sql, this is not an answer because we will not go that route; having code blown away by the tool and have to be reentered. It goes in in the context of the tool or we don't use the tool).
Also, is there a way to utilize the "close" button from the QBE that so nicely takes you back to the report and does a refresh?
This is the simplest app I could dream up to test this product and it looks like it falls short.
In summation:
1) Generate a report. (yes)
2) Link to form (yes)
2a) Link direct to record (no query click) (no, without hacking)
3) update the form (yes, if after query click)
4) Jump back to report at spot where you left, do automatic refresh (just like QBE) (No, without hacking)
Again, this is the simplest and most common of apps, I cannot understand why it would be so hard to accomplish. What am I missing? Anybody on the board, please advise.
null

If your report is created using ‘Reports From SQL Query’ then you can modify it using the following to achieve this:
1. Remove the link from ‘Column Formatting’ section of the report object.
2. In the SQL of the report , use custom link to the column where you want to provide link using the syntax
select a.empno,’‘||a.ename||’‘ ename_link,a.deptno
from scott.emp a
Order by a.empno
and the form will always open in ‘INSERT’ mode with passed values filled in.
Thanks
Krishnamurthy

Data collection task in Update mode is not posible with Original list

Hi Friends,
When I try to Execute the Task for data collection in sa38.I am getting the Error with in 9 sec.
UPDATE MODE IS NO POSSIBLE WITH ORIGINAL LIST
Message No. UCS0111
Diagnosis :
If you select the indicator"original list"the current task status is ignored.In this case,the system simulates a task run in with all of the organisational units are not yet blocked.Thus,setting this indicator is meaningful and valid only if the task is executed in test mode at tthe same time.
procedure : select the original list & Test run together.
My problem is I can not select the Test run in production server.
Can any one please help me to solve the Issue.

I Thank you all for Responding to me.
Hi Dan,
SA38 provides all the needed parameters- Con.Group,Company,Version,Fis.Year,Period,Group currency.
Iam trying to run the task with SA38 for Data Collection.
Hi Lucio,
When I Check the Fields Both the Log & Original list . The programe gives an error message "UPDATE MODE IS NOT POSSIBLE WITH ORIGINAL LIST"
Even when I tried with Log,Test Run & Original List Iam getting the Same error Message "UPDATE MODE IS NOT POSSIBLE WITH ORIGINAL LIST"
I can run the task Successfully with selecting the Log option only. But my Client need to Use both Log & Original list ( as they used to run in BIW 3.5 ) Now it we are using BI 7.
Hi Christopher,
We are running the programe UCBATCH01,with the T code SA38.
Hi Eugene,
I will look in to the link and i will Discuss with the Basis team.
Once again Thank you all for responding
Suraj.

Stop LIS Updating

Hello friends,
I don't know so much about LIS updates but I do know I want to stop them from happening.
Can anyone tell me how to do it and whether those updates are nessecery for anythig( for example we have BW datasources, are they might be using the LIS data?).
Thanks in advance,
Gershon.

execute OMO1, double click the info strucure and set th e radio button to "not update"
repeat this for any info structure

Update Mode

Hi
I am using UDO in my Add-on. If form is in find mode then the values are filling, when we add a new value to that form it is not changing to update mode.

Hi Nageswar,
Not sure if I understand your issue completely, but wanted to mention that when the form is in find mode, edits do not result in mode change. When the form is in OK mode, any edits will change the mode to Update.
Setting the appropriate values for some of these properties may help with your issue. Please look at their descriptions in SDK Help.
Form.AutoManaged
Form.SupportedModes
Item.AffectsFormMode
Regards
Aravind

LIS Update Mode

Similar Messages

Maybe you are looking for