Sblive and Delta-L

Hi guys!
I have a problem that i really need some help in.
I have this old Sblive OEm card that im trying to install on my Athlon Xp 2500+, MSi Delta-l mainboard and 2 cruicial 256 mb ram. My graphics card is a Geforce 2 (yeh yeh i know, im embarrased).
Anyways, so i put my card into a free PCI slot and the computer goes fine into WinXP. However, when detecting the drivers for the sblive card, the computer freezes. Ive tried disabling the soundcard on the mailboard, but without any help.
So.. Do you guys have any piece of advice for me?
Thnx alot in advance.
Stian

Thanks Deathstalker! Hi from Vero Beach btw
i had tried to use the SBLive on my board but i kept getting crackling/stuttering phases. it wasnt a loose connection or debris or anything, and i updated the bios and drivers. it still had this problem so i removed the SBlive and went back to the onboard. the problem persisted with the onboard! oddly, when i removed the promise UltraATA card that came with the WD Hard drive, the sound is absolutely fine with the onboard, and now im considering putting the SBlive back on. i had wanted to settle this issue before buying the audigy2 platinum, and i hope going to IRQ 5 helps when i get home (i bet it will). you seem to be into online gaming, would you mind putting your two cents in here?
http://www.msi.com.tw/program/service/forum/index.php?threadid=29987&sid=

Similar Messages

Get rid babylon and delta search, uninstall wont work because it doesn't show up, please help

I want to keep my firefox but have caught this babylon and delta search and no matter what i do it will not go

Remove Babylon Features:
Remove Toolbar (from Extensions)
1. Open Mozilla Firefox. Go to FF menu button.
2. Select Add-ons & than select Extensions. (delete excess text)
3. Remove/Disable the Babylon Toolbar 1.5.0.
4. Restart your browser.
Remove Toolbar (from Add/Remove Programs)
1. Click the Start button on your computer.
2. Select Add-ons & than select Extensions. (delete excess text)
3. Select Programs and Features.
4. Select Babylon Toolbar from the Programs list.
5. Right click to uninstall.
6. Press YES on the popup message.
Remove Search Provider
1. Open Mozilla Firefox. Click on the Search bar, located on the right side of your address bar
2. Press the F4 key and select Manage Search Engines from the drop down list that appears.
3. Select Search the Web (Babylon) and click on the Remove button.
4. Click OK to save your changes.
Remove/Change Home Page:
5. Open Mozilla Firefox. Click on the FF menu button.
6. Select Options.
7. Now select the General tab.
8. In the section of the popup labeled "Home Page," insert the URL of your desired Home Page.
9. Click OK to save the changes.
Remove Babylon Search from New Tab
If when you open a new tab in Firefox, Babylon Search still appears:
1. Type in the address bar line about:config and press enter.
2. Confirm the popup message.
3. In the search field, type "browser.search.selectedEngine". (remove excess text here)
5. Restart your Browser.

No initial load of Customers, Material and delta load of Sales Orders.

Hi Experts,
I am facing a very troublesome issue. I am not able to setup the Middleware portion for initial and delta loads. I read a lot of documents and corrected a lot of things. finally, the connectivity is done with R/3 and CRM. Initial load of all objects is successful (as per Best PRactices guide). Customizing load is successful.
But after now I have these open issues for which I am unable to find any answers (am really exhausted!!):
- Customer_main load, it was succesful, but no BP's of R/3 are available.
- Material, it failed in SMW01, SMQ2, the errors are:
Mat. for Initial Download: Function table not supported
EAN xxxxxxxxxxxxxxxxxx does not correspond to the GTIN format and cannot be transferred
EAN yyyyyyyyyyyyyyyyyy does not correspond to the GTIN format and cannot be transferred
Plant xx is not assigned to a business partner
- Sales order, it shows green bdoc, but error segments says "No upload to R/3" and the order does not flow to R/3.
We had our system setup 3 years back for data transfer and Middleware. But few things changed and connectivity stopped. I did all that again now, but am not yet successful. Any inputs will be greatly appreciated.
Thanks,
-Pat

Hi Ashvin,
The error messages in SMW01 for MAterial initial load is :
     Mat. for Initial Download: Function table not supported
     EAN 123456789000562 does not correspond to the GTIN format and cannot be transferred
     EAN 900033056531434 does not correspond to the GTIN format and cannot be transferred
     Plant 21 is not assigned to a business partner
I have done the DNL_PLANT load successfully. Why then the plant error?
Some of the messages for BP:
Messages for business partner 1331:
No classification is assigned to business partner 1331
For another,
     Partner 00001872(469206A60E5F61C6E10000009F70045E): the following errors occurred
     City Atlanta does not exist in country US
     Time zone EST_NA does not exist
     You are not allowed to enter a tax jurisdiction code for country US
     Validation error occurred: Module CRM_BUPA_MAIN_VAL, BDoc type BUPA_MAIN.
Now, the time zone EST is assigned by default in R/3. Where do I change that? I do not want to change time zones as this may have other impacts. Maybe CRM I cna change this, not for sure in R/3. City check has been deactivated in R/3 and CRM, still the error.
Till these 2 are not solved, I cannot go into the Sales order loads.
Any ideas will be greatly appreciated.
Thanks,
-Pat

Full and delta Data loads in SAP BI 7.0

Hi,
Kindly explain me the difference between full and delta data loads in cube and DSO.
When do we select change log or active table(with or without archive) with full/delta in DTP for DSO.
Please explain the differences in data load for above different combinations.
With thanks and regards,
Mukul

Please search the forums. This topic has already been discussed a lot of times.

Middleware: BDoc to IDoc conversion - init and delta

Hi,
First of all let me just say, that I know nothing about CRM (I'm an XI guy), but need to investigate on a matter, so please take that into accound when reading this post and responding to it.
Scenario:
Business Partners, Business Transaction Messages (orders and activities) need to be replicated to an external system. This is achieved by converting BDocs for the respective messages into IDocs via CRM Middleware and then sending IDoc to XI which in turn posts data to external database. This process should function both INIT and DELTA.
So far so good.
The problem is when having created for instance a new direct order and saved it. The BDoc is generated and converted to IDoc (CRMXIF_ORDER_SAVE02). In the fields OBJECT_TASK in the IDoc I get the expected 'I' for INSERT. This is what I expect.
Now, if I make a change to the order and saves it again the generated IDoc still contains just an 'I' for INSERT in the before mentioned fields. This is not to be expected - should be an 'U' for UPDATE, but this does not happen.
Anybody have any ideas why this happens and what is wrong?
Best Regards,
Daniel

Hi,
Thanks for your answer. I'm on CRM 5.0. The note you mentioned seems not to be related to my problem. My question is regarding "download" of data from CRM to XI through CRM middleware. When trying to do this the "change pointers" (fields OBJECT_TASK and/or TASK) are not set correctly in the IDoc's generated by middleware (everything is writtens INSERTs), which means I cannot from XI determine by the data received if I'm to perform an update/insert/delete into the database.
Best regards,
Daniel

Basic Question on Copy and Delta link which one to use when?

Hi
Its basic question
My understanding about copy and Delta link is
Copy doesnot ahve direct relationship with source object (but it acts as a sibling) any changes done to spurce object does not affect target object.
Where as Delta link will have a parent child relation ship between source object bacially its a copy of source and inherits id properties. in case if i change source object does this affect target object, we can delete, add content to delta link target object.
let's say if i want to use standard quickpoll iView do i need to use copy or delta link similarly for other iviews, worksets, roles which one will be better.
Regards,
Murali

Murali,
Yes, your understanding is right.
Case 1 : Copy
A- Object
B- Copy of A
Both of them are independent.Any changes in A are not dependent on B and vice versa.
Case 2 : Delta Link
A - Object
B - Copy of A (via Delta link)
Any changes to A are reflected in B, as A is a parent and B a child.
But B would be an independent entity.Any changes to B would not effect A.
When you use either of them, depends on your need. When you are working with standard iviews or roles or workset, you can do a copy of the original, because in most cases we would not make changes to the standard roles or worksets or iviews. There by eliminating the process of making a delta copy.
But, if you are dealing with the roles that you have created and want to make a copy of it, you can use a delta link, because, even if you want to add more iviews and worksets to that role, they would get reflected when you make a delta copy.
Hope that helps.
Consider rewarding points for handy posts!
Cheers,
Sandeep Tudumu
Edited by: Sandeep Tudumu on May 6, 2008 2:10 AM

Error in Full and Delta CPACache refresh.

Hi Experts,
In our production environent we have a SOAP -> XI - > PROXY scenario [Synchronous].
The Consumer of the WebService has reported an error:
500_Internal_Server_Error = SOAP:Server_Server_Error_XIAdapter_ADAPTER.JAVA_EXC
When I checked there are no messages in SXMB_MONI , but when I checked the Cache Refresh History I found that
there was error in both Full and Delta Cache Refresh. But the restart of the XI(Production) server resolved the issue.
The error is as shown below:
<?xml version="1.0" encoding="UTF-8" ?>
- <CacheRefreshError>
<EngineType>AE</EngineType>
<EngineName>af.pxi.su0956</EngineName>
<RefreshMode>F</RefreshMode>
- <GlobalError>
<Message>Couldn't parse Configuration Data cache update XML string from Directory.</Message>
org.xml.sax.SAXException: JavaErrors Tag found in cache update XML. at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataSAXHandler.startElement(DirectoryDataSAXHandler.java:157) at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.startElementEnd(SAXDocHandler.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java(Inlined Compiled Code)) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java(Inlined Compiled Code)) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java(Compiled Code)) at javax.xml.parsers.SAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataParser.updateCentralCache(DirectoryDataParser.java:56) at com.sap.aii.af.service.cpa.impl.cache.CacheManager.updateCacheWithDirectoryData(CacheManager.java:871) at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:640) at com.sap.aii.af.service.cpa.impl.servlet.CacheRefresh.process(CacheRefresh.java:104) at com.sap.aii.af.service.cpa.impl.servlet.CacheRefresh.doGet(CacheRefresh.java:53) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code)) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code)) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code)) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code)) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code)) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
Can anyone tell me what is the cause of this error and how restart of the XI server resolved the issue?
Thannks,

Guys,
I have deployed the below components and after this repository could not be started which gives the below error.
1000.7.11.10.18.20130529165100
SAP AG
sap.com
SAP_XIAF
1000.7.11.10.11.20130529165100
SAP AG
sap.com
SAP_XIESR
1000.7.11.10.15.20130529165100
SAP AG
sap.com
SAP_XITOOL
We have the same issue. Still the Restart did not solve ths issue.
Can anybody help? We are not able to start the XI Repository.
Our PI components are as below
com.sap.engine.services.ejb3.runtime.impl.refmatcher.EJBResolvingException: Cannot start applicationsap.com/com.sap.xi.repository; nested exception is: java.rmi.RemoteException: [ERROR
CODE DPL.DS.6125] Error occurred while starting application locally and wait.; nested exception is:
        com.sap.engine.services.deploy.container.DeploymentException: Cannot activate endpoint for message-driven bean sap.com/com.sap.xi.repository*xml|com.sap.xpi.ibrep.server.jar*xm
l|CacheRefreshMDB^M
        at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.startApp(DefaultContainerRepository.java:315)^M
        at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.getEnterpriseBeanContainer(DefaultContainerRepository.java:106)^M
        at com.sap.engine.services.ejb3.runtime.impl.DefaultRemoteObjectFactory.resolveReference(DefaultRemoteObjectFactory.java:55)^M
1000.7.11.10.6.20121015232500
SAP AG
sap.com
MESSAGING
Regards
Omkar

Setup table and delta mechanisim

Hi,
Can anyone explain in detail setup table concept in LO extraction and
Delta mechanisim?
Sridhar

Hi
LO Cockpit Step By Step
Here is LO Cockpit Step By Step
LO EXTRACTION
- Go to Transaction LBWE (LO Customizing Cockpit)
1). Select Logistics Application
       SD Sales BW
            Extract Structures
2). Select the desired Extract Structure and deactivate it first.
3). Give the Transport Request number and continue
4). Click on `Maintenance' to maintain such Extract Structure
       Select the fields of your choice and continue
             Maintain DataSource if needed
5). Activate the extract structure
6). Give the Transport Request number and continue
- Next step is to Delete the setup tables
7). Go to T-Code SBIW
8). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Delete the content of Setup tables (T-Code LBWG)
vi. Select the application (01 u2013 Sales & Distribution) and Execute
- Now, Fill the Setup tables
9). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Filling the Setup tables
vi. Application-Specific Setup of statistical data
vii. SD Sales Orders u2013 Perform Setup (T-Code OLI7BW)
        Specify a Run Name and time and Date (put future date)
             Execute
- Check the data in Setup tables at RSA3
- Replicate the DataSource
Use of setup tables:
You should fill the setup table in the R/3 system and extract the data to BW - the setup tables is in SBIW - after that you can do delta extractions by initialize the extractor.
Full loads are always taken from the setup tables
1. Data Flow
Relevant T-Codes
a) Initializtion
LBWE: Maintain Extract Structure, DataSource, Active Status, Job Control, Update Mode
SBIW, then follow tree menu path: Settings for App-Specific DS(PI) -> Logistics -> Managing Extract Structures -> Initialization -> App-Specific Setup of Statistical Data -> Choose XX Application -> Delete/Fill Setup(reconstructing) Table content
RSA3: Check content of setup table
b) Delta upload
SM13: Display update table/Extraction Queue content
RSA7: Display Delta Queue content
Edited by: Tapashi Saha on Jul 24, 2008 7:33 AM

Delta get once and delta request wise?

hi friends,
what scenerio we use delta get once and delta by request at DTP in BI 7.0? i studied many threads, i didnt understand , get delta once some snapshot like? what is the meaning?
can u give me any example , its great?
regards
ss

Indicator: Only Get Delta Once
Source requests of a DTP for which this indicator is set are only transferred once, even if the DTP request is deleted in the target.
Use
If this indicator is set for a delta DTP, a snapshot scenario is built.
A scenario of this type may be required if you always want an InfoProvider to contain the most up-to-date dataset for a query but the DataSource on which it is based cannot deliver a delta (new, changed or deleted data records) for technical reasons. For this type of DataSource, the current dataset for the required selection can only be transferred using a 'full update'.
In this case, a DataStore object cannot usually be used to determine the missing delta information (overwrite and creation of delta). If this is not logically possible because, for example, data is deleted in the source without delivering reverse records, you can set this indicator and perform a snapshot scenario. Only the most up-to-date request for the DataSource is retained in the InfoProvider. Earlier requests for the DataSource are deleted from the (target) InfoProvider before a new one is requested (this is done by a process in a process chain, for example). They are not transferred again during the DTP delta process. When the system determines the delta when a new DTP is generated, these earlier (source) requests are seen as 'already fetched'.
Setting this indicator ensures that the content of the InfoProvider is an exact representation of the source data.
Dependencies
Requests that need to be fetched appear with this indicator in the where-used list of the PSA request, even is they have been deleted. Instead of a traffic light you have a delete indicator.
Get Data by Request
This indicator belongs to a DTP that gets data from a DataSource or InfoPackage in delta mode.
Use
If you set this indicator, a DTP request only gets data from an individual request in the source.
This is necessary, for example, if the dataset in the source is too large to be transferred to the target in a single request.
Dependencies
If you set this indicator, note that there is a risk of a backlog: If the source receives new requests faster than the DTP can fetch them, the amount of source requests to be transferred will increase steadily.
Source : https://forums.sdn.sap.com/click.jspa?searchID=5462958&messageID=3895665
Re: Diff between Only Get Delts Once and Get Data by Request
Check this blog as well : /people/community.user/blog/2007/06/21/sap-netweaver-70-bi-data-transfer-process-with-147only-get-delta-once148

How to do delta detection and delta creation

Hi
i am new to OWB , please help me in
how to do delta detection and delta creation using OWB
Thanks

Hi Bassem,
for delta detection in your data source there are three possibilities:
1. the source data has some identifier when it has been modified and deleted data is marked an not physically deleted
In this case you just filter the data that has been changed in your owb mappings.
2. you use some change data capture technologies
You have to install this manually when using owb 11.1 or older versions (google for oracle and cdc). owb 11R2 brings built in support for change data capture.
3. you get all the data and identify the delta manually
In the owb mapping you left outer join the data from your source with the existing data in your target and filter for the data that is new or has been modified. In a second step you identify the deleted data by selecting the data in your target minus the data from your source.
Which approach is the best depends on your specific system architecture.
Regards,
Carsten.

CRL and delta CRL generation schedule not fixed (CS 2008 R2 and CS 2003 R2)

CRL and delta CRL is generated daily at the same time in test environment (sometimes offset may be about 1 minute).
Delta CRL generation statistics (effective date) in production environment :
2014.07.12 23:01
2014.07.14 00:00
2014.07.15 00:43
2014.07.16 01:22
2014.07.17 01:59
2014.07.18 03:10
2014.07.19 03:48
One can see that delta CRL generation time is constantly shifting and it's not the same as time period when delta CRL is being generated. Delta CRL validyti is 1 day, so it should be generated each day at the same time. CRL size is about 10MB, delta CRL
size is about 0,5 MB. Delta CRL generation time is about 1,5 H.
Question: is it possible to fix CRL and delta CRL generation time (make it constant), using standard ADCS tools/settings? Role separation is used in solution, therefore it's not safe to run daily task (with CA administrator's permissions)
to force publishing time in CA registry (if it's possible at all?), or similar "workoround.

Hi, Vivian! Sorry for delay - I was dealing with another urgent issue, but now it's time to return to this issue.
Vadims, thank you for information. I saw this article
http://blogs.technet.com/b/pki/archive/2008/06/05/how-effectivedate-thisupdate-nextupdate-and-nextcrlpublish-are-calculated.aspx, but it not answers all the questions.
Following links in article referred in your post, I found latest version of article moved to TechNet:
http://social.technet.microsoft.com/wiki/contents/articles/20652.how-thisupdate-nextupdate-and-nextcrlpublish-are-calculated.aspx
That article provides more detailed explanation, but there are still some questions. Below is schedule of delta CRL publishing on production and test servers which are using absolutely identical CA settings, including but not limited to CRLPeriod, CRLOverlapPeriod,
CRLDeltaPeriod, CRLDeltaOverlapPeriod, ClockSkewMinutes.
But production server has more certificates and publishing of delta CRL requires more time (about 1,5-2h). As result, CRL and delta CRL publishing time constantly shifting approx. by 1h (this timeframe is not equal to delta CRL generation time), but CRL
and delta CRL on test server are generated almost at the same time (see more info below).
Therefore, one can assume that something is missing in publishing time calculation formulas, provided in the articles mentioned above.
PROD SERVER:
CRL This Update:
2014.07.09 00:42
2014.07.10 01:20
2014.07.11 01:57
2014.07.12 03:07
2014.07.12 23:01
2014.07.14 00:00
2014.07.15 00:43
CRL Next Update:
2014.07.10 12:42
2014.07.11 13:20
2014.07.12 13:57
2014.07.13 15:07
2014.07.14 11:01
2014.07.15 12:00
2014.07.16 12:43
CRL This Publish:
2014.07.09 00:42
2014.07.10 01:20
2014.07.11 01:57
2014.07.12 03:07
2014.07.12 23:01
2014.07.14 00:00
2014.07.15 00:43
CRL Next Publish:
2014.07.10 00:42
2014.07.11 01:20
2014.07.12 01:57
2014.07.13 03:07
2014.07.13 23:01
2014.07.15 00:00
2014.07.16 00:43
TEST SERVER
CRL This Update:
2014.07.09 15:08
2014.07.10 15:13
2014.07.11 15:13
2014.07.12 15:13
2014.07.13 15:13
2014.07.14 15:13
2014.07.15 15:13
CRL Next Update:
2014.07.11 3:08
2014.07.12 3:13
2014.07.13 3:13
2014.07.14 3:13
2014.07.15 3:13
2014.07.16 3:13
2014.07.17 3:13
CRL This Publish:
2014.07.09 15:08
2014.07.10 15:13
2014.07.11 15:13
2014.07.12 15:13
2014.07.13 15:13
2014.07.14 15:13
2014.07.15 15:13
CRL Next Publish:
2014.07.10 15:08
2014.07.11 15:13
2014.07.12 15:13
2014.07.13 15:13
2014.07.14 15:13
2014.07.15 15:13
2014.07.16 15:13

Diff between update queue and delta queue

hi all
can anyone tell me wats is the diff between update queue and delta queue? wats is delta queue and update queue?
wats are the possible system generated errors and custom generated errors?
Thanks,
Shreya

Hi Shreya,
Update queue(LBWQ) comes into the picture when you choose Queued Delta for the Datasource. the data first comes to the Update queue and than goes to the Delta queue, however if you have choosen Direct Delta than the posted record will directly go to the Delta queue(RSA7).
Here is the URLS for Roberto's weblog to understand the whole LO-Extraction process.
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
Hope it helps you!!!!
Regards,
Amit
Pls do not forget to assign points, if helpful.

Full upload after INIT and Delta

Hi Experts,
a quick question - If there is INIT and Delta infopackage running and I do another infopackage with full update option, will there be any issue in Delta?
when do I need to run repair? only when there is possibility of duplicate loading?
Thanks - SM

Thanks Srini/Vikram for your respone.
when there is deltas already running for the datasource , you can't request for Full but you can request using 'Repair full' which will acts and extract data as full load and it won't disturb present delta's
>>. Thanks Srini. thats bottom line... after delta, you need to run repair full not full. and repair full will also pull data from setup table (history). I was thinking repair full is for taking care of duplicate, but dups we need to remove manually.
where is repair full option in IP?
where I can see all INIT conditions for a infopackage? for example INIT was done 3-4 times.. year 2001-2002, 2002-2003 etc, so all these INIT crit should be stored somewhere?
Edited by: toti shu on Aug 31, 2010 5:08 PM
Edited by: toti shu on Aug 31, 2010 5:11 PM

Filling of set up tables for Full and Delta updates

Dear Gurus,
How do I go about filling the set up tables if I want to load historical data to BW using LO **** pit when set up table is running on delta ?
I want to know how many set up tables will be there for each data source, Because if set up table is running on delta and using the same table I want to load historical data also then will I have to delete and fill set up tables or there will be a separate set up table for full upload and delta ?
If we have multiple set up tables for one data source then in the T-code OLI*Bw, where * -> App logistics num, so to fill I just say OLI6BW, then which set up table it is going to refer.
Clarify my doubt and get rewarded with plenty of points.
Regards
Mohan

Hi,
Filling up the set up tables depends on the datasource.
there are different T-codes for the respective extract structures
OLIIBW transaction PM data
OLI1BW INVCO Stat. Setup: Material Movemts
OLI2BW INVCO Stat. Setup: Stor. Loc. Stocks
OLI3BW Reorg.PURCHIS BW Extract Structures
OLI4BW Reorg. PPIS Extract Structures
OLI7BW Reorg. of VIS Extr. Struct.: Order
OLI8BW Reorg. VIS Extr. Str.: Delivery
OLI9BW Reorg. VIS Extr. Str.: Invoices
OLIABW Setup: BW agency business
OLIFBW Reorg. Rep. Manuf. Extr. Structs
OLIIBW Reorg. of PM Info System for BW
OLIQBW QM Infosystem Reorganization for BW
OLISBW Reorg. of CS Info System for BW
OLIZBW INVCO Setup: Invoice Verification
OLI7BW is the tcode for Sales Order.
Hope this solves Ur issue....
Assign points if helpful..
Rgs,
I.R.K

Need suggestions in doing my Init and Deltas

Hello Experts,
I am using the standard SALES OVERVIEW cube to store the sales data. I have introduced the custom built ODS to store the order level data in my flows. I am about to test my flows but I am afraid if the custom built ODS in the flows will create any problem while doing deltas as the standard Datasources are designed to update the cube directly.
One more thing is, If I do the init and deltas now for my testing, is it possible to delete all the data from ODS and the cibe and do the init again and start the deltas? Will the custom ODS be a problem in such scenarios? I am assigning the 0RECORDMODE to 0STORNO in the transfer rules.
Rgds,
Nene.
Message was edited by:
Nene BW

Hi
You can test init and delta loads in both the ODS and Cube
You can later on delete all the requests in the ODS and cube if you want to
init again
Assign points if useful
Regards
N Ganesh

Sblive and Delta-L

Similar Messages

Maybe you are looking for