Delta document for 3.0 to 3.1 upgrade

Hello All,
We are upgrading from BW 3.0 to 3.1. can anyone please provide me with link for delta document.
Regards,
Ruby

Hi
Hope it helps.........
Re: BW 3.0 vs 3.1
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e62b9990-0201-0010-42a7-ddcf5c93cafd
Regards
Lalit K Tyagi

Similar Messages

Delta load for 2LIS_06_INV is failing after EHP5 upgrade of ECC system

Hi Experts,
Our ECC Production system was upgraded to EHP5 last weekend.
Since then Delta load for datasource 2LIS_06_INV is failing. This is the only datasource got impacted. Full Load and Initialization Loads are running fine. Only Delta load is failing because of following error:
Error in the ABAP Application Program
The current ABAP program "SAPMSSY1" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "/BI0/SAPLQI2LIS_06_INV " in
include "/BI0/LQI2LIS_06_INVU04 " in
line 1:
"Function "/BI0/QI2LIS_06_INV0002" not found in Function Library."
Thanks and Regards,
Sandeep Sharma

SAP suggested Note to fix this issue.

Export and import change document for user master data

Dear Gurus,
I have two queries on change document for user master data:
1. Are there any approaches to export and import change document for user master data?
We often do system copy from PRD to QAS for UAT and troubleshooting. Before system copy we export the user master data from QAS and then import after the copy process. We would like to keep the change document for user master data on QAS from being refreshed from PRD for security reason.
2. Change document for Role change in QAS
When the role is created or modified in DEV and then transported to QAS, the role change document doen't include this change log. The role change document in QAS only records those role changes directly made in QAS.
Could you advise this is by SAP design or are there any approaches to record this transported role change in the role change document in QAS?
Thanks
YBY

1. Perhaps you want to consider a system copy to a "virtual system" for UAT?
2. Changes in QAS (as with PROD as well) will give you the delta. They should ideally be clean... You need to check the source system.
Another option is to generate the profiles in the target system. But for that your config has to be sqeaky clean and in sync, including very well maintained and sync'ed Su24 data.
Cheers,
Julius

I can not make delta load for some component of public sector management

Hello All:
I´am using these three data source 0PU_IS_PS_31, 0PU_IS_PS_32 and 0PU_IS_PS_42 and I realize that I can not make delta loads. When I make the full load everything is correct even when I made the delta, the problem is that the Delta load is not extracting any new data or changed data.
Do you have any idea to fix this issue?
Thanks
Message was edited by: Víctor Olivera

Hello Victor,
As u have already tried the delta load,I assume that u have already done the init load too.As system will not allow u to do delta load without doing an init load first.
The first datasource u talked about..31..it needs new records created in table FMIOI table.
What happens is..if u run a delta load immediately after an init load,there might not be new or changed records created in the system..therefore there arent any records in the delta queue.
Could u try creating some commitment document transaction data,so that records get added in FMIOI table.Then see if the delta queue for this datasource shows any records.
Links to BC pages for these datasources are below..
http://help.sap.com/saphelp_nw04/helpdata/en/1a/8c425e8afe11d496d80000e835339d/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/1a/8c42618afe11d496d80000e835339d/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e1/46a53ec5f0c0428fa8b9cfcdcd9fcd/frameset.htm
Note that for 42 datasource..page says that delta update is not supported(though it does talk about updating delta queue).
For 32 datasource source tables are FMIFIIT and FMIFIHD.
For 42 datasource table is FMBDP.
cheers,
Vishvesh

Delta documentation for SEM BCS/CPM 6.0

Hi Team,
Please let me know the link or document for SEM 6.0 delta changes compared to SEM 4.0 In BCS componet and CPM component.
Regards
Naveen.KV

In the SAP Support Portal click on Release and Upgrade Info, then choose Release Notes > SAP Solutions > SAP ERP > ECC 6.0. Chapter 10 refers to BCS changes.

GRC delta doc for 5.1 to 5.3

Hello all, I'm looking for a GRC 5.1 - 5.3 delta doc that outlines all the new/improved features in CC and FF 5.3. I already have the delta doc for 5.1 - 5.2. So if anyone even has the 5.2-5.3 delta changes I'd appreciate it.
Thanks
Dave Wood

David,
I am also looking for such a document.

Delta update for ... is invalidated

I try to load my cube from another cube (as an infosource) via an ODS.
In the InfoPackage I select 'Full update'. Under 'Processing' I have checked 'Data Targets Only'. Under 'Data Selection' I have selected a limited set of data to load (one month).
When the loading process is finished, I get a popup message "Express document "Check Load from InfoSource 8ZOSACTCV" received..." When opening this document I read "Check Load from InfoSource 8ZOSACTCV , Packet Delta Package for Update by ODS ZOSACTCV".
The loading of the ODS is completed successfully. When monitoring the InfoCube loading process, I get a red light. The error message is "Delta update for ZOSACTCV is invalidated".
Both the ODS and the cube was empty before loading (although I first tried it with existing data in the cube). What is wrong? I see the request in the cube is called "Delta Package for Update by ODS ZOSACTCV". Why is it called a delta package when I requested a full load? Is this a part of the problem? I have tried "Delta Update" and "Initialize Delta Process" with "Initialize Without Data Transfer". I always get the same result.

Hai,
I understand that you are loading from Cube to ODS and then to another cube from this ODS. The data load from Cube to ODS is sucessful but the full load from ODS to Cube doesnot work. Is it?
Check few things below for load between ODS and the final cube:
1. See if there is any active initialization in the infor package. Go to your infopack and in Menu>Scheduler>Intilization option for source system.
If there is any delete it and try the load. A full load destroys a prior initilaztion.
2. If step is not the case, delete all the contents of the Cube and load. You can do this by hitting 'Delete' icon and 'delete all entries' or by right clicking on the cube and 'delete data'.
3. If even thats not the case, try to just load till PSA and then go to your PSA and simulate the upadte. See whats the problem is...you can find more details in the details tab screen in Monitor.
Let em know if these doesn't work. Provide me any other relavent information. We can work it out.

Delta Update for Characteristic info object

Hi
Can anyone tell me how can i adjust a delta update for a characteristic?
Regards
S

Hi Sancho,
A great deal of InfoObjects carrying master data and texts are already delivered delta-capable (e.g. 0MATERIAL_ATTR, 0CUSTOMER_ATTR).
The master data extraction in the delta mode is possible for a large number of R/3 tables and views. To do this, the transaction for which data is to be created and changed must be linked to the change document update. This service has been implemented for most of the master data in the R/3 System.
The update occurs in most cases for the transparent tables in which R/3 master data is stored (for example, for MARA or KNA1). If a field changes in a data record of the table the key to this record is recorded in a delta table. When reading the table in a BW, this key is used to fill the extract structure. Thus, you can extract master data delta in several ways:
The extract structure equals the transparent table in the database, whose maintenance is added to the change documents.
The extract structure is a view over one or more transparent tables whose maintenance is added to the change documents, for example, a view via KNA1 (customer) and KNB1 (customer and company code).
A basic requirement for the usability of a table for an InfoObject is that the key for this table explicitly specifies a record of the extract structure (key word compounding). Besides, you should make sure that the data elements of all the extract structure fields are relevant to the change document in the respective table. In other words: as soon as a field changes a record which is part of the extract structure, it must be updated in the delta pot.
<b>According to the assignment InfoObject/table, the following steps must be executed:</b>
1. Check, whether the ALE changepointer are active in your source system (Transaction BD61) and whether the number range is maintained (Transaction BDCP).
2. In addition, check in the ALE Customizing, whether all message types you need are active (Transaction SALE -> Model and implement business processes -> Configure the distribution of master data -> Set the replication of changed data -> Activate the change pointer for each message type ).
3. Check, whether the number range for the message type BI_MSTYPE is maintained (Transaction SNUM -> Entry 'BI_MSTYPE' -> Number range -> Intervals). The entry for 'No.' must be exactly '01'. In addition, the interval must start with 0000000001, and the upper limit must be set to 0000009999.
4. Go to your BW system and restart the Admin. workbench.
All of the following activities occur in the InfoSource tree of the Admin. Workbench.
5. Carry out the function "Replicate DataSource" (1.2 local meta data upload) on the affected attached source system for the InfoObject carrying the master data and texts.
6. Activate the delta update
a) for master data and textsby activating the transfer rules.
b) for texts the entry is in the menu of the right mouse button via the source system: Activate the text delta transmission.
All changes, all initial data creations and deletions of records from now on are recorded in the source system.
7. Create an InfoPackage for the source system. In the tabstrip 'update parameter', there are three alternative extraction modes:
Full update
Delta update
Initialization of delta procedure
First, initialize the delta procedure and then carry out the
delta update.
Addition for incorrect delta requests:
After an incorrect delta request, you often have to re-initialize. A possibility of avoiding this consists in setting the incorrect request manual via QM activity to green. If the request was processed successfully in the source system, and was finished with the information IDoc 'Data selection ended', but the BW reports a processing error, the request must be re-initialized in any case in order to avoid data inconsistencies.
Constraints
The total length of the key fields in the table or view for which change pointers are produced must not exceed 70 characters.
Transferring deleted records using the ALE delta is impossible since a corresponding indicator is missing in the extracted record.
Hope this helps.
Thanks
CK

Delta update for Info cube, How it will be works, what are mode to select.

Hi all,
              How delta update works for info cube, Generic data source delta update options are
              1) time stamp
              2) Calday
              3) Nemeric pointer
Please explain briefly delta update for infocube and delta init and delta update.
Thanks,
Gowda

Hi,
How delta update works for info cube
When you are updateing the data to cube from ods then data would extracted from change log their delta pointer get setup in the source request (in Source you can check the option beside the reqest says updated to target object.... it means the records are updated to target hence we would not update the same request )
Incase of PSA to cube Also in the PSA request get stamped as last updated .
Regarding Generic Datasource
When we don't find any standard extractor then we can go for Generic(if i want information sales along with finance information in a data source then generally we dont get standard one hence we can go for generic DS)
Check the below link for More about generic DS .
http://wiki.sdn.sap.com/wiki/display/BI/Generic+Extraction
for Delta capturing you can use
Timestamp(if the table has time stamp filed so it can stamp the last changed record in that table hence it is easy to get delta based on the time stamp)Calday- (If the table doesn't have the Timestamp filed then search for Calday where you can stamp the delta based on the date when documents are changed )
Numericpointer : If the table doesn't above both then we go for this option where you can the numeric value change stamp )
Re: Extraction, Flat File, Generic Data Source, Delta Initialization
Regards,
Satya

ALE delta extract for HR master data

We want to create some R/3 delta extracts based on the HR PA* tables using the ALE delta extract function of generic extractor. Has anyone done this before? Are there any OSS notes or documents that I should look at? Thanks!

Hi Bill Faison,
This is very old message. I think your problem must be solved. If it is not then: yes we can extract Data from R/3 with ALE Delta .
You have to perform below steps.
1.     In your Table you need to activate ALE change   pointer.
2.     Create change documents for required table.
3.     Created Generic Extractor with ALE Delta.
Hope this will help.
Let me know if you have any concern or issue in this regards
Best Regards
Sharad Verma

The delta update for the InfoCube ZCUBE is invalidated

Hi BI Experts,
I am working on BW 3.5.
For the datasource 2LIS_13_VDITM there were some requests(deltas) missing for 3 days. So I got all the documents there were missing or not updated in BW. I deleted the setup tables and filled them with the new document numbers.
I did a full repair request from the Infopackage level and the data got updated in ODS.
But the DM Status is missing for all the requests in the ODS.
And the data for the full repair request didnt get updated in the Cube and I got the following error:-
The delta update for the InfoCube ZCUBE is invalidated. The can be due to one of the following:
1. A request, which was already retrieved from the target system, was deleted from the InfoCube.
2. A request, which was not yet retrieved from the target system, was compressed in the InfoCube.
And the following delta was also not successfull.. How can I clear up this mess and ensure smooth flow of deltas. How can I set the DM status.
Thanks
Kumar

Thanks for your reply.
When I did a Full Repair Request on the ODS the data is in the New table and the DM status got reset(vanished). And the following day delta got failed( data for that request did not get updated in ODS and Cube)
How can we bring back the DM Status and make the deltas successfull.
Thanks
Kumar

Pseudo Delta Document

Hi,
We are planning to implement Pseudo Deltas for FI-SL transactional data. I don't know how to set Pseudo Deltas for FI-SL in R/3. Could any one send me the Pseudo Delta document.
Any one help is really appreciated.
Thanks,
Kiran

Hi,
Psuedo deltas are usually set up by putting in selection criteria in the infopackage selection of the full infopacakge.
Or you can write routines to filter out specific data and then load that.
Cheers,
Kedar

Why isnt there a delta extractor for CCA Commitments

Can someone explain why there is not a delta extractor for CCA Commitments; whereas there is one for CCA Actual - Line Items?
Both CCA commitments and Actuals are stored in table COSP; which has no date/time stamp. Somehow the CCA Actuals can be delta enabled, however.

The actuals are actually taken from COVP - this is a view across COBK and COEP (from memory - I could be wrong)
COBK has the timestamp that is used - there is no requirement to take changes to CO documents as you cannot change any important information in CO relevant for BW
If you do - then the change is not reflected in BW
Regarding why no delta for commitments - I can not comment - I avoid this like the plague
Have you see Note 721519 - Delta update for FI-FM DataSources

Delta mechanism for 0fi_gl_14

Hi,
We are using 0fi_gl_14 DS for extracting leading ledger's line item data.
But when I checked table BWOM2_TIMEST, there is no entry for the above data source.
Could someone help me understand delta mechanism for 0fi_gl_14?
Is it not similar to 0fi_gl_4 delta?
What is the difference between 0fi_gl_4 and 0fi_gl_14?
Regards,
Shravani

Hi,
Most of the extractors (specially one in question 0FI_GL_14) in FI related extractors work on pull mechanism via Extraction method: F1 (function module (complete interface))
Extractor: FAGL_GET_SI_DATA
1. 0FI_GL_14 extractor, considers all data from the tables FAGLFLEXA (or similar customer tables), BKPF, BSEG, and BSEG_ADD. we use this extractor if New GL configuration done in ECC or otherwise 0FI_GL_4 still holds good.
2.Coming to Delta are picked from BWFI_AEDAT table where all the changed documents/new are maintained as part of changed status.
Hope i have addressed your question!
Regds,
Karunakar P

Generate accounting document for cancel of credit memo

Hii Guy,
Need your help to solve this problem.
My user have perform VK11 to cancel of credit memo. in the sales order document flow, the status is OPEN.
my user cannot perform creating of accounting document for this cance of credit memo. what are the tcode to generate accounting document ?

Nizamkz wrote:Hi,
>
> Hii Guy,
>
> Need your help to solve this problem.
>
> My user have perform VK11 to cancel of credit memo. in the sales order document flow, the status is OPEN.
Are you sure its VK11???? I guess for the cancellation if billing document its VF11......
Try to do the manual release to accounitng....by going to VF02 and pressing the Green Flag button after entering the cancellation document number. Or Else Try to reverse the posting with FB08.
Thanks,
Raja

Delta document for 3.0 to 3.1 upgrade

Similar Messages

Maybe you are looking for