Delta update for Cube : 0CRM_PRI - Service Orders and Confirmations: Item

Dear experts,
For Cube : 0CRM_PRI - Service Orders and Confirmations: Item
Source data is from Two ODS
1. Confirmations (Item Data) : 0CRM_CNFI and
2. Service Orders: Item Data : 0CRM_PROI
I have done Init upload to this cube from both this ODS.
I am not getting delta option to this.
When I am trying update Delta after init from ODS message is No new deltas in DataStore object 0CRM_PROI for update. No delta option available . It is showing Initial and Full Update option only.
How i can initiate delta option for this Cube ? Please update us.
Thanks in advance.
Regards,

Hi,
you can use DTP's to laod data from ODS to cube .. it will take deltas ..
With a data transfer process, you can transfer data either in full extraction mode or in delta mode. In full mode, the entire dataset of the source is transferred to the target; in delta mode, only the data that was posted to the source since the last data transfer is transferred. The data transfer process controls delta handling and therefore allows you to fill several targets with different deltas from one source. With a data transfer process, you do not need to explicitly initialize the delta method as you do when copying data with an InfoPackage.
or you can create a sepeate Ip for delta apart form full and init .. that will laod delat data in cube ..
Regards,
shikha

Similar Messages

BW - Process Chain for Service Orders and Confirmations

Hi,
I need advice on the creation of my process chain and basically I'm still new in this BW technical area.
I have done on the infopackage (full update) , DTP from PSA (delta once update) and DTP from ODS (delta update). My datasource is 0CRM_SRV_PROCESS_H and my ODS is ZSOL_O01. while my cube is ZSOL_C01.
my plan for the step of the process chain is as below. this is based on my understanding after doing 'try and error' things using the update mode for infopackage and DTP.
1. delete the old PSA/datasource - the infopackage is run in full update
2. delete the old ODS - after afew loading, seems there are afew ODS request created with same number of record and data. that's why i plan to delete the old ODS
3. run the infopackage - new PSA request will be created
4. run the DTP (PSA to ODS) - new ODS request will be created based on the new PSA request
5. run the DTP (ODS to Cube) - new cube request will be created based on the new ODS request
izzit ok with my above step? i'm not sure on the deletion of cube index. izzit needed?
thanks

i need advice on below things since this is my 1st BW task..
1. transport list - how do i group all the objects into this transport list? if the object is attach to other TR, how do i trace it and put into my transport list? should I group all the objects into 1 TR or is there any sequence should i follow? maybe characteristic/key figures 1st or DTP first...
i'll tel you the most easy way to collect transport that you will never have issues
go to RSA1--> transport conenctions
when you get your item on on left ,you have to set up few things.. on the right there is a display mode ,, do the drop down on it and do it a list and do cloeection mode manually.
you wil always get alist of items under or over then way you can pick waht you want to transport very easily withouth missing objects or figuring out what did you miss
and you can collect all in 1, Bw is smart enough to transport and activate dependences on its way as long they are in 1 transport
2. currently my source data is from my solution manager (SOLMAN) development server. should i create 1 more infopackage for SOLMAN testing server? how about production? is that means, at the end i will have 3 different infopackage for dev, testing and prod?
once you transport infopackages they autmatically gets assigned to the new system.
3. is there any step i left or missed?
not that i can think off. if any transports are locked go to se03 and unlock your transport , make sure you unlock any underlying transports, youc an find the transports in se09 or se10

Table for satatus, CS, service order and notification

There is a field of status at the CS notifications. The tcode for customizing this field is OIBS but in which table can I find the related data? I'm also looking for the other tables of CS, service order and notification.
Edited by: Yasar Demircan on Jan 27, 2010 10:06 PM

Hi,
You can refer the table JEST, TJ30, TJ30T for object status and user status

Pricing date for Service Order and Service Confirmation

Hi,
I cretated a Service Confirmation as followup for Service Order.
Client is asking "Pricing Date" should be same Same in Service Order and Service Confirmation. But, I am not seeing any such field in the screen.
I need to check T&C field and Zone field. But, I am not seeing these fields also.
Can you please let me know, where can I find this fields. (In which assignment block).
Thanks,
Sandeep
Edited by: Sandeep Reddy on May 31, 2010 7:21 PM

Hi,
I think by PRICING DATE they mean BILLING DATE.
In date profile of SERVICE ORDER and SERVICE CONFIRMATION you assign the BILLING DATE date type (i think it is there in the standard itself- however just ensure it).
Or customize a PRINCING DATE date type in the DATE PROFILE of SERVICE ORDER and CONFIRMATION and copy the date set in SERVICE ORDER to SERVICE CONFIRMATION.
This is one strategy you can use.
Regards
Surendra More

Resumable downloads and delta updates for App Store

Hi all,
since I didn't find any place where to add product improvement suggestions, I post it here and hopefully someone can point me (and or this post) to the correct location.
I'd like to vote for resumable downloads (even a shutdown is in between) and delta updates for the Mac App Store. The main reason for this are big apps (i. e. Xcode) which I simply can't update without having the mac running the whole day (and night).
Thanks and regards,
Michael

Hi Michael!
Apple employees are not going to see feature feedback posted here, but you can use the Apple Feedbck site. There is not currently a category for the App Store but you can use the OSX feedback form here:
http://www.apple.com/feedback/macosx.html
The main reason for this are big apps (i. e. Xcode) which I simply can't update without having the mac running the whole day (and night).
Curious, are you on dial-up or satellite? As I live in a low-population state with lots of miles between towns of even modest size, I hear the slow connection issue a lot when helping users locally. We get 50mbps service in Lewiston, but people in the back country are struggling with some really slow satellite providers.

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

Please help me!!!!!!! what can I do with the message " no service " I have already updated for 5.0.1 (9A406) and nothing happened. Please Help me!!!!! I´m thinking to came back to my nokia. It´s work at least!!!!

Please help me!!!!!!! what can I do with the message " no service " I have already updated for 5.0.1 (9A406) and nothing happened. Please Help me!!!!! I´m thinking to came back to my nokia. It´s work at least!!!!

Please DO go back to your Nokia. I'm sure people on their support forums will love your whining and idle threats just as much as we do.

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.
According to the assignment InfoObject/table, the following steps must be executed:
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

SRM Service Orders and Entry sheets,

Hi Friends,
Is SRM service orders able to provide the u2018price changeu2019 field? In the R/3 equivalent Service Order entered with item category Service, the u2018price changeu2019 field is available (table ESLL, field PRS_CHG) and we have a business requirement to have this available when we enter SRM Order Service confirmation sheets in R/3. If a service sheet is created from a SRM PO with item category service, u2018price changeu2019 is greyed out. If a service sheet is created from a service PO entered directly in R/3 the u2018price changeu2019 field is not greyed out for input and can be changed. Please can somebody explain how we can make this field available.
Previous experiences with using functionality this would be highly welcome.
Thank you. Steven

Hi,
You can assign the service master records administered in your company to different groups, according to their usage. Such a group is described by the service category.
To characterize the service categories in more detail, the latter are assigned an organization status. The organization status indicates the areas in which service master records are used.
For example, units of your company may use services provided internally by other units of the company, or procure services externally (from other companies). Your company may also provide services for others.
AS01: If you select this the service master data is at basic data level. That means basic data about the service will be depicted here.
AS02: Service master stored at basic and CO level. To maintain the information at CO level this organizational status is required.
AS03: Service master stored at basic plus purchasing level. For procurement purpose(MM), THIS LEVEL is useful.
Create a po with service activity number in me21n with account assignment category K & and item category D.
For the SES, the creation date would still be same. Only field ESSR-BUDAT (posting date) would get changed.
That shouldn't be a problem, since you would know anyway when the SES was created from ESSR-ERDAT, the SES creation date.
Also the last change date would also be correctly updated.
You have another field Doc Date ESSR-BLDAT which records the date the SES was posted
Thank's
Raj

Delta update for datastore is invalidated

Hi experts,
we're on SCM 7.0 and I'm trying to copy data from livecahce into a cube for backup. Have set up the datasource, dso and cube and this has been working. We had this process running with the data extracting to the cube all fine.
Something has happened to cause this error below and I'm not able to fix.
The delta update for the InfoCube DS_PAGGL 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.
Procedure
Initialize your delta update again.
The data load to the dso work no problem but when it trys to transfer to the cube where it errors. it shows as a Repeat of the last delta in the type of data update. Request status stays yellow but if you call the monitor is shows as red with message above.
Error message no. is RSBM113
The dso is on a full update and the cube is on a delta.
I can't reinatialise this as when i call up the IP this option is greyed out.
I've deleted the update from the cube, dso and psa but when its rerun it comes up with the same error each time.
If we can't initialise, then what other options do we have?
Thanks
Edited by: Paul_111 on May 11, 2011 5:15 PM

Hi Venkat,
Delta request REQU_429VZAIHRVBTP2OUFU2AP8T4Q is incorrect in the monitor A repeat needs to be requested
This is bcoz, Your last delta from ODS to CUBE is not success full.
Just delete the initialization from ODS to CUBE and reinitalize with out data transfer. And pull the delta from ODS to cube after initialization. It will solve the problem.
Hope it Helps
Srini

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 0FIA_DS11 is invalidated

Hi All,
The below description explain about the error that I am facing. But it is in the case of an Info cube that this description is valid. Now, I am facing this error when I am updating data into DSO, Info Cube from another DSO. I am performing delta update from DSO 0fia_ds11 to 0fia_ds12, 0fia_ds13 and Info cube 0fiaa_c11. Can anyone suggest if you know about this how to resolve.
Delta update for 0FIA_DS11 is invalidated
Message no. RSBM113
Diagnosis
The delta update for the InfoCube 0FIA_DS11 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.
Procedure
Initialize your delta update again.

Hi,
Have you checked whether the initialization was successful? Go to the info package and select Initialization options for source system and check initialization is successful.
It is better to re initialize the delta after deleting contents of the cube.
With Regards

Delta update for 0FIGL_O02 is invalidated"

Hi Gurus,
I am facing the above stated message when i am loading the delta from ODS to Cube.
What happened.
we r deleted a request which is having data mart satus ok.
After that we reconstructed the same request into ODS.
After that the delta to cube from the same ods is giving the message like
"Delta update for 0FIGL_O02 is invalidated"
What i have to do in this case.
May i reinit cube.
Or any other way to solve this .
The data mart status for all requests in ODS is vanished.

Hi
See if the steps followed for delta are Init without data transfr, full repair and then delta if this is not the case follow the steps mentioned and if it is so u can do one more thing
do init with data transfer once again this will include each and every data but first delete the previous req of init. There is no need to do delta up till the time next delta comes after init with data transfer is done
Hope it helps Assign Points if applicable
Thanks
Puneet

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

How to create a service order and check the internal order in R/3

Required Solution:
1. How to copy existing service order and create new one and check the internal order in R/3, whether the certain service order is correctly created in r/3, can you polease explain the steps plz.
2. If i am creating service order by service template finally the service order is getting created but it is not showing me in the table iaom_crm_aufk, how to check this.
can any one help me in this issues as soon as possible.

Hello Zita,
Try to restart your portal after creating ServiceUser in both UME and KM.
One more major difference between ServiceUser and normal portal user is that a ServiceUser does not have a UserAccount (IUserAccount)
Object serviceContext = null;
 try {
 serviceContext = AccessController.doPrivileged(new PrivilegedExceptionAction() {
 public Object run() throws WcmException {
 return ResourceFactory.getInstance().getServiceContext(CONTRACT_SERVICE_USER);
 } catch (PrivilegedActionException e) {
 logger.severe(e, "ResourceContext for the technical " + serviceUser +
 " user could not be retrieved.");
IResourceContext resCtx = (IResourceContext) serviceContext;
So I modify all KM resources with this resCtx.
Hope this helps ...
Greetings,
Praveen Gudapati
p.s. Points are always welcome for helpful answers

Delta update for Cube : 0CRM_PRI - Service Orders and Confirmations: Item

Similar Messages

Maybe you are looking for