Full To Delta (changing load type)

Hello Everybody
I am planning to convert few laad type from FUll to delta because its just taking too long to load. But here are my questions.
Besides the fact that (full load)it's a business requrement(snapshot); i cannot change it right or there is still a way.
1. what are the technical considerations for converting full load from a dso to a cube . If ths dso is getting a full load itself does it have to be set to overwrite to further do a delta to a cube. what if the dso is getting delta load . do i have to consider from source to dso as well if its delta or full; how does it affect it.
2. what happens to the existing laods/requests in a cube/dso if i change the load type. (does it get affected)
thanks

Hi,
1. When changing the data load to delta from DSO to cube, just you can go ahead an do init. Since the base leve is DSO it doesnot matter if the base level data load is full or delta. Also make sure the DSO is standard one. If the source is DSO there is no problem in converting from full to delta.
2. Make sure only one full load exist in cube. Then do a init and going further you can pull delta. The existing data in DSO will not be affected or cube data. Since delta will fetch data from change log table there will not an issue.
Regards
Akhan

Similar Messages

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.

Changing From Full to delta load

Could someone please help with this
i have used a Functional Module to extract data from R/3
i have created a new InfoCube and did a full load and everything is fine
There is NO ODS involved
i now want to change data loads from FULL to DELTAs
Can i do this without using an ODS and RECORDMODE - if so, how?
Thankyou
Pushpa

HI Pushpa,
For generic DS we need to maintain the generic delta. We can define in three ways.
1.Calday
2.Numeric Pinter
3.Timestamp
If we go for calday then there should a field (0calday). Which holds both created and changed the date of the record. We have 1 drawback in this we can only run the load only at the end of the day.
Numeric Pointer will only fetches the changed records.
Most of the time we preffer we go for timestamp.
U will get these option in RSo2 in R/3
Regards

Full-Init-Delta Loads

Friends
I have done full loads into a ODS and then I did Init with no data transfer. But the Message said that the request cannot be activated because the ODS has had full loads and activating INIT and DELTAS is not possible...Any Ideas?
Regards
VISHAL

Hi Ashwin,
there is a seperare procedure to activate delta mechanism in ODS. After you load the full requests you cannnot run init without making all the full requests to "Reapir full requests".
See SAP Note: 689964
Symptom
You want to switch the upload procedure for an ODS object from full to delta. However, the delta initialization fails with a message indicating that there are already full uploads in the ODS object and therefore inits or deltas cannot be posted or activated.
Other terms
Delta; ODS object: delta initialization, RSM 098, full, Init
Reason and Prerequisites
If a full upload occurs once for an ODS object, you can no longer activate an init for the same DataSource/source system combination in this ODS object. The system does not check for overlapping selection conditions.
Solution
In the case if an ODS object, you can change the upload procedure from full to delta by subsequently marking the full requests that exist in the ODS object for this DataSource/source system combination as repair full requests.
These requests are therefore characterized by the fact that they can be posted into any data targets in any sequence. The repair full requests are never checked in a data target, that is, you can activate initializations and deltas (also with selections) in the ODS object. All ODS objects filled with these full requests behave as if the full requests did not exist in the ODS object.
Checks do not take place in all of these ODS objects.
Note the following:
Since the repair full requests are not checked, duplicate data records may be created or data may disappear if there is a subsequent init.
Since the repair full requests are not checked, you should take account of the extractor behavior, update modes, aggregational behavior of key figures and characteristics, among other things, when you are deciding whether you want to mark the full requests as repair full requests.
If you perform an init simulation after changing to repair full requests, make sure that no data is updated between the last full upload and the first delta upload.
Procedure for changing full requests to repair full requests:
After you import Support Package 19 (3.0B) or Support Package 13 (3.1C), the RSSM_SET_REPAIR_FULL_FLAG report is available which you can use to convert all full requests for a DataSource/source system combination that are in an ODS object into repair full requests.
Before you import this Support Package:
Use transaction SE16 to call the RSSELDONE table.
Here, enter an "x" in the "Repair_Full" field for all full request records that you want to mark as repair full requests.CAUTION: This ONLY concerns those requests that begin with 'REQU_...'. The repair flag CANNOT be set for activation requests that begin with 'ODSR_'.
If the full requests still exist in the PSA, you can also use the scheduler under the 'Scheduler' menu option in the PSA tree (when you post from the PSA) to switch a PSA full request to a repair full request before loading.
If you load new requests with an InfoPackage, you can also assign the repair indicator to this full report.

I loaded Mac OS X v10.7 Lion yesterday. Everything's running fine, except for a simple problem. Any time I want to copy a file, JPEG, etc., I am prompted "Finder wants to make changes. Type your password to allow this." I don't want this!! Is there a way

I loaded Mac OS X v10.7 Lion yesterday. Everything’s running fine, except for a simple problem. Any time I want to copy a file, JPEG, etc., I am prompted “Finder wants to make changes. Type your password to allow this.” I don’t want this!! Is there a way to unlock “Finder” or rid this process?

Back up all data.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. You can demote it back to standard status when this step has been completed.
Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:20 ~ $_ ; chmod -R -N ~ $_ 2> /dev/null
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you don’t have a login password, you’ll need to set one before you can run the command.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2
Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
resetpassword
That's one word, all lower case, with no spaces. Then press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

Issue with Info Object Transport after changing Data Type

Hi Experts,
We have a DSO which is running past 5 years. And recently(3 days back) we added new fields into that DSO. Delta loaded for last three days and new info object (Say XXX) data populated into DSO.
Now the problem is, We identified that, info object data type is not correct. We used data type NUMC instead of CHAR.So Character information is missing for that field.
Example:
Data from ECC: ABC123
Data Loaded to DSO: 123 (Missed character ABC)
So we deleted data from DSO and changed the info object data type in Development system.
And also I have deleted only last three days delta records from DSO and transported my info object to Production. But its giving error as: Info object contains data in DSO".
But that info object field is empty in DSO. I have already deleted last three days delta.
Do I need to Delete all 5 years data from DSO to change the data type of recently added new info object ?
Please give me your solutions and ideas to solve this issue.
Thank you,
Best Regards,
Santhosh

Hi Raman,
Thank you for your answer.
When I changed the data type of info object in Dev, I deleted the content of DSO. And same thing transported to QA as well. Before importing changed info object, I just deleted the content of DSO from QA. So transport done successfully QA.
But in Production we have a history of past 5 years. So I cant delete all contents of DSO.
So just deleted only the delta request's which contains data for that info object(3 days back, we moved that info object(NUMC data type) to production,So last 3 days delta only loaded for that info object). And tried to transport it. But it was failed. I am sure we need to drop all data from DSO, if I am interested to go with same info object.
I have some comments on your first approach,
1. If we delete info objects from Dev DSO and transport to Production will give transport failure, Why because, my previous transports errors clearly saying that info object contains data in DSO . So it wont allow to remove that info object from DSO.
2.We are using same info object technical name in BO Data federator also. So if we change add new info objects again we need to make changes with BO as well. I am thinking this point as my last option if i cant find any other solution.
Thank you.
Best Regards.

R/3 Delta changes in BW

Hello Everyone,
When we do an Init or Full data extraction from R/3 to BW for the first time for any extractor, the data gets loaded in BW. When we load delta changes from R/3 by doing a delta load into BW, how does BW know to extract only the changed R/3 records and not all records.
How are R/3 changes tracked in BW? where is the previous request information stored in BW?
Thanks in advance

Hi,
After initial full upload if there is any change in the records or any new records found then only the delta will work, if there is no new records then even u do the delta there is no updation..
One morething in RSA7 of detail view u will get the previous posted records and next delta records..the old records will me maintained untill the old request is successful and a new request was reached in r\3 from BW.
Regards-
Siddhu

Two Extractor logics for full and delta?

Hi,
I have a situation where in the logics for full upload and delta uploads are drastically dfifferent!
What is best way to deal it?
shuould i have two different extractors for full and delta ?
Raj

Hi Raj,
I hope that u are working with the Generic Extractors. If the volume of the posting is too high then u need to restrict the data definitely from R3 side interms of the performance. And u need to maintain the Delta Functionality for the same.
If u cannt maintain the Delta from the R3 side then atleast try to restrict the same from BW side at the infopack level where u can extract the data based on the changed on and created with the two different IP's and update the same to the ODS(here make sure all the objects are with the overwrite).... and then u can maintain the Delta load from ODS to the Cube easily..
If the volume of the data is pretty less then u can use Full load to the ODS and then Delta to the Cube.
Thanks
Hope this helps..

Full and Delta DTP doubts

There was a ongoing delta load happening between DSO 1 to DSO 2.
I deleted all requests from DSO 2.
And then ran first Full DTP ( DSO 1* to DSO 2) and immediately after full DTP ran Delta DTP ( DSO 1 to *DSO 2).
In Full DTP : There were 10,000 Records added into DSO 2
In delta DTP : there were 2,000 records added into DSO 2
I was bit surprised when I saw some data added in delta since before ( just 5 mins back ) I had ran full DTP therefore my understanding was delta would not bring anything.
By looking at various thread , I came to know that Full DTP get data from Active table and delta DTP get data from change log table.
However what if , if same records present in Active table and change log , so same records will be pick up by Full DTP run and also while delta DTP run , assume target DSO is in addictive mode then in such scenario duplicate record will be added and final result would be diffrent 9( i.e data get double up ).
How do we avoid such situation ?.
Any thoughts ?.
Edited by: Prashant on Aug 12, 2010 2:24 PM

HI,
DTP FULL: if you have 1 request in psa today and your dtp extraction mode is full it will load the data into the target.
                  in the next day you have run the infopackage and you habve got another request wich means in totall you have got
                  2request in psa so what the full dtp does is it will try to load both of them and you will get error saying duplicate records.
DTP DELTA:   it will load only the the fresh request from the source.
howe ever we dont do any initialisation in dtp the full and delta are only the extraction modes of data from the source. and its the infopackage which will fetch the deltas once the intialisation is done.
hope it helps.
Thanks & Regards
krishna.y

Criteria to upload Master Data by Full or Delta

Dear Experts,
In our project, all the master data are extracted bu the Full Upload method. However, our users asked for the criteria to judge whether we should use Full or Delta for master data.
E.g.
1) the volume of data - (If there are a few records for master data, use full upload) - What is the exact figure that we can use to check? For example, more than 10000 records, use delta upload.
2) the change of master data - (if the master data is changed every day, use delta upload)
etc.
Is there any SAP document recommending these things?
Thank you in advance.

Hi,
One criteria that you can consider is to check whether the datasource is delta enabled or not.
In few cases where frequent changes of data is not expected e.g. 0PLANT_ATTR (plant master data) , SAP delivers without the option of enabling delta load. In such case, you can go only for full update. In other cases , where data change is expected more frequently like 0MATERIAL_ATTR , it is delta enabled.
Regards,

Difference between Delta "Change Log" and "Active Table (Without Archive)"?

In BI7.0 environment, we perform our Delta loads (the DTP settings under the Extraction tab, there is a field called Extraction Mode and it's value is selected as "Delta") every day among all our DSOs.
There is a section called "Delta Init. Extraction From..." under the same tab in DTP, there are four radio buttons:
Active Table (With Archive)
Active Table (Without Archive)
Archive (Full Extraction Only)
Change Log
Then what is the difference between "Change Log" and "Active Table (Without Archive)" if both Extraction Mode is "Delta" for two Delta loads?
Thanks!

Hi ,
The new options SP16 has are:(Chk Note 1096771)
Active Table (with Archive)
The data is read from the active table and from the archive or from a near-line storage if one exists. You can choose this option even if there is no active data archiving process yet for the DataStore object.
Active Table (Without Archive)
The data is only read from the active table. If there is data in the archive or in a near-line storage at the time of extraction, this data is not extracted.
Archive (Only Full Extraction)
The data is only read from the archive or from a near-line storage. Data is not extracted from the active table.
Change Log
The data is read from the change log of the DataStore object.
Delta will always be picked from change log table.Only during intialization you can choose between getting data from change log or active table.If you are doing the load first time and are initializzing delta in subsequent data targets, then pulling data from active table will get lesse volume of data then it would have got from change log table....All subsequent deltas will be picked up from the change log. And when we need to reload data into the data target (which would be a full load) - we use active table.
From change log : you can take below ones as targets
1) Cube 2) DSO with Addition as the update for the Keyfigures
From Active table: you can take below ones as targets
1) Cube ,if and only if, the records are never changes in the source once after creation
2) DSO with Addition as the update for the Keyfigures ,if and only if, the records are never changes in the source once after creation
3) DSO with Overwrite as the update for the Keyfigures ( incase deletions is not happening in the source system)
Pls check this link
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/47/e8c56ecd313c86e10000000a42189c/frameset.htm
Regards,
CSM Reddy

Delta changes in R/3 sales document are not coming into CRM

Hi Middleware experts,
We are on CRM 5.0 SP 005 with ECC 5.0 SP 007 and using the scenario X for sales documents replication.
Now the order is created in CRM and successfully transfered to R/3. I can see 3 Bdocs in SMW01 with green lights. First Bdoc says 'R/3 adapter is called', second Bdoc says 'the order is successfully saved' and displays a warning 'The sales document is not yet complete: Edit data' and third Bdoc has no messages. Also I do not see any struck queues in CRM and in R/3
I am able to edit the sales document in both the systems as per the scenario X. Now I have completed and saved the document in R/3. Surprisingly these changes are not coming into CRM and no new entries in SMW01. Also R/3 SMQ1 and CRM SmQ2 doesn't show any entries. I am also not able to debug, since I do not see any Bdocs in SMW01.
Now, if I changes the document in CRM and these changes are coming into R/3.
Also all documents created in R/3 are successfully going into CRM including delta changes in R/3.
I do not have any clue on what is happening? Highly appreciated, if you can help me.
Thanks,
PK

Hi PK,
In R3AC1 only we put the filter. So if you do not have any other filter then make sure that you are changing the order which was created not before the date mentioned.
I would recommend you to just deregister the CRM system in R/3 Transaction SMQS and do some changes in the orders and check any queues are getting created corresponding to that order, If yes that means filter is not an issue. Then debug the queue and find the exact problem. Also make sure that the order you are changing in R/3 is of the same order type what you have mentioned in the filter.
Make sure to registor back the CRM other wise all the queues will get stuck in R/3 outbound.
Reward points if it helps!!
Best regards,
Vikash.
Message was edited by: Vikash Krishna

How to change data type of content type column.

Hi all,
I am having one content type. I have 10 columns in it. There are two rich text columns in my content type. I have attached this content type to pages library. I want to change the data type of this rich text column to "Full
HTML content with formatting and constraints for publishing".
Please assist me with this issue.
amol

Hi,
From your description, my understanding is that you want to change the data type for rich text column in content type.
The field type of Full HTML content with formatting and constraints for publishing is "Invalid", you could refer to this article:https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spfieldtype.aspx.
You also could test it by create a Full HTML content with formatting and constraints for publishing column and get the its type with C# code below:
//change the URL to your SharePoint site
using (SPSite site = new SPSite("http://sp/sites/sharepoint2013"))
using (SPWeb web = site.OpenWeb())
SPFieldType type = web.Fields["Column name"].Type;
I have tested it with the PowerShell, it cannot hange the rich text column to “Full HTML content with formatting and constraints for publishing” column. If you want to edit the rich text column, you could not change the type of the column as the screenshot
below:
As a workaround, you could follow these steps to accomplish your requirement:
Create a “Full HTML content with formatting and constraints for publishing” type column in the content type.
Enter your site columns by clicking gear icon -> Site Settings -> Site columns under Web Designer Galleries under section.
Find and delete the rich text column you want to change.
Find the column you have created in step 1, and change the column’s name to the name of the text column you have deleted in step 3.
But you will lose the data of the rich text column in pages library with this method.
Best Regards,
Vincent Han
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

How to retrive delta changes in Infotype

Dear All
I am working on development of New Interface program from SAP to 3rd party application and this will run on daily.
I want to retrive delta changes record alone in 10 infotype tables.
I checked the Tech.setting of these 10 infotype table and came to know that log data changes & Maintain as transparent table check box is selected.
But i couldn't find any record in the table: DBTABLOG
Is there is any other table where the delta change in the Infotype get saved.
The infotype am checking is IT0000,IT0001,IT0002..etc
Could any one help me to solve this issue...
Definitely I will reward for best answer
Regards
Babu

Hi Babu,
please use RPUAUD00 program.
you can do assign above program in your interface by using SUBMIT.
another way. you create one Z function module, here you do submit RPUAUD00 program.
Please find sample code as below.
RP_PROVIDE_FROM_LAST p0167 space pn-begda pn-endda.
IF p0167-aedtm GT wa_last_create_date.
l_search_text = '.Benefit Plan.'.
l_infotype = '0167'.
PERFORM check_for_change USING l_search_text l_infotype
CHANGING wa_changes.
IF wa_changes EQ c_checked.
RETURN.
ENDIF.
*& Form CHECK_FOR_CHANGE
text
FORM check_for_change USING p_search_text TYPE zdesc_15
p_infotype TYPE choic
CHANGING p_changes.
CALL FUNCTION 'ZHR_GET_INFOTYPE_FIELD_CHANGES'
EXPORTING
search_text = p_search_text
infotype = p_infotype
pernr = p0000-pernr
bypass_type_check = 'X'
IMPORTING
old_value = wa_old
new_value = wa_new
TABLES
date_range = s_datum
EXCEPTIONS
no_change_found = 1
OTHERS = 2.
IF sy-subrc EQ 0.
p_changes = c_checked.
ENDIF.
ENDFORM. " CHECK_FOR_CHANGE
I assigned RPUAUD00 program in Z function module.
Cheers,
Guru.

Loading custom Generic Loader type extracts broken after patch 7616161

Before applying 7616161, we could perform full ETL operations within iSetup using custom apis for a seeded .lct file. After applying this patch, extracts still work using the same custom apis, but loads fail with the following error:
Validating Primary Extract...
Parsing driver.xml
Time taken to parse the Driver file and construct setup objects:25 milliseconds
Sorting Apis based on their dependency...
null
java.lang.NullPointerException
     at oracle.apps.az.r12.api.APISorter.sortBySeqNum(APISorter.java:599)
     at oracle.apps.az.r12.loader.cpserver.APILoader.groupApis(APILoader.java:449)
     at oracle.apps.az.r12.loader.cpserver.APILoader.loadAPIs(APILoader.java:226)
     at oracle.apps.az.r12.loader.cpserver.APILoader.callAPIs(APILoader.java:141)
     at oracle.apps.az.r12.loader.cpserver.LoaderContextImpl.load(LoaderContextImpl.java:66)
     at oracle.apps.az.r12.loader.cpserver.LoaderCp.runProgram(LoaderCp.java:65)
     at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
Concurrent program completed.
Any help would be most appreciated.

In an instance that was cloned with 12.0.6 after applying 7616161, then upgrading the instance to 12.1.1, still getting this problem, specifically the nullpointerexception error in the APISorter class. Will the patch 8871713 work under this upgraded instance as well? Or do I need different code to patch up iSetup to get the Generic Loader type extensions working in 12.1.1?

Full To Delta (changing load type)

Similar Messages

Maybe you are looking for