Delta upload errored

Hi all:
In a process chain we upload delta to ODS 0figl_o10, then update target cube 0figl_c10 with that delta (after activating ODS).
That process is erroring out making R/3 and BW out of sync. Can someone suggest what's the best option now?
I wanted to delete the ODS and the cube data, then init load the ods, activate ods, send data to the target cube and then restart the process chain. Not sure if there is any better way.
Thanks in advance,
Pranab

Why you want to delte your init load? where exactly u r getting the error..could you please elobrate more?

Similar Messages

Delta upload Error

Hi Friends
I am loading data from R/3 with delta update.Firstly i schedulled the delta init load and then schedulled the delta load.Init load was successful but delta load failed.
Bellow is the error message:
"Error message from the source system
Diagnosis
An error occurred in the source system.
System response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request."
I couldn't understand what is the problem.
Please provide me some solution for this.
Regards,
Chama.

Hi
Datasource name is 0CML_DELTA.
I have checked in sm37 and following the message.
    Job                              Ln Job CreatedBy   Status          Start date Start time Duration(sec.) Delay (sec.)
BI_WRITE_PROT_TO_APPLLOG            NB161256        Released                                          0            0
    BI_WRITE_PROT_TO_APPLLOG            NB161256        Finished        09.03.2007 09:38:08               3            0
    BI_WRITE_PROT_TO_APPLLOG            NB161256        Finished        09.03.2007 09:43:37               0           29
    BI_WRITE_PROT_TO_APPLLOG            NB161256        Finished        09.03.2007 09:48:37               0           29
    BI_WRITE_PROT_TO_APPLLOG            NB161256        Finished        09.03.2007 09:53:37               0           29
    BI_WRITE_PROT_TO_APPLLOG            NB161256        Finished        09.03.2007 09:58:37               0           29
    BI_WRITE_PROT_TO_APPLLOG            NB161256        Finished        09.03.2007 10:03:37               0           29
*Summary                                                                                3          145
Regards,
Chama

LO Extraction - error in delta upload

Hi,
I try to do some delta upload. The delta initialization works fine. I run OLI8BW and created an InfoPackage for delta initialization.
Now I have problems with the delta upload. I selected update method 'queued delta' in LBWE and run the job. If I try to start the loading via InfoPackage (delta upload) an error occurs. In RSA7 I can see the delta's, but there is nothing in LBWQ. The error message in the BW monitor is the following: 'Transfer structure field not contained in DataSource'. There is one field in Transfer structure, which isn't contained in data source, but I fill it via a routine. Any ideas what the problem could be?
Thanks a lot.
Gabi

hi,
check sap oss note
881207
Symptom
You load data in Delta mode and the system issues error message R3 037 in the monitor:
Transfer structure field not contained in DataSource.
Note 868059 did not deliver a complete correction.
In Delta requests or repeat requests that contain time-dependent selections, these time dependencies are always transferred to the source system with the 'DATETO' and 'DATEFROM' field names.
Time selections are also transferred to the source system if the time-based fields are not known as selectable fields in the DataSource.
Other terms
Scheduler, Update tabstrip, repeat, DATETO, DATEFROM,
Delta, Init, date selection, InfoPackage, selection, M, X, 1. R3 037
Reason and Prerequisites
The problem is caused by a program error.
You have implemented Note 868059 as an advance correction or you have imported it using a Support Package.
Solution
BW 3.0B
           Import Support Package 29 for 3.0B (BW3. 0B Patch 29 or SAPKW30B29) into your BW system. The Support Package is available when Note 0783251 "SAPBWNews BW3.0B Support Package 29", which describes this Support Package in more detail, is released for customers.
BW 3.10 Content
           Import Support Package 23 for 3.10 (BW3. 10 Patch 23 or SAPKW31023) into your BW system. The Support Package is available when Note 0783253 "SAPBWNews BW3.1 Content Support Package 23", which describes this Support Package in more detail, is released for customers.
BW 3.50
           Import Support Package 15 for 3.5 (BW3.50 Patch 15 or SAPKW35015) into your BW system. The Support Package is available, when Note 0836440 "SAPBWNews BW Support Package 15 NetWeaver'04 Stack 15", which describes this Support Package in more detail, is released for customers.
BW 7.0
           Import Support Package 05 for 7.0 (BW7.0 Patch 05 or SAPKW70005) into your BW system. The Support Package is available, when Note 0829625 "SAPBWNews BW 7.0 Support Package 05", which describes this Support Package in more detail, is released for customers.
To provide advance information, the notes mentioned above may be available before the Support Package is released. In this case, the short text of the note still contains the words "Preliminary version".

Deal the Error messge in Delta upload

Hi,All:
   Now we face this problem:
   The value of characterstic in record is not standard.
The traffic light is red, and not activity request in ODS.
   Now we change value in source system manual,and we want to redo the delta upload and upload the data for cube.
   How to solve this problem?Can you give me some helps?
Regards&Thanks!
zagory

Hi,all:
   Now I face the new problem:
   The status of Total is yellow light, and the status of Technical is yellow light.
   The system message as follow:
<i>Request still running
Diagnosis
No errors could be found. The current process has probably not finished yet.
System response
The ALE inbox of the SAP BW is identical to the ALE outbox of the source system
and/or
the maximum wait time for this request has not yet run out
and/or
the batch job in the source system has not yet ended.
Current status
No Idocs arrived from the source system.</i>
We have 7 delta upload like this.I find something unusually is <i>211 from 0 records</i>.I think it means BW system do not upload data,and the process is running now.
How to process the step? I waiting for 2 hours.
Regards&Thanks!
zagory
Message was edited by: zagory

Delta uploading job get cancelled in SAP R/3

question, during delta loading from SAP R/3 to BW, if the delta uploading job get cancelled twice for some reason, will I lost some delta data??
Pls advise!
Many Thanks!
rajatina.

Hi,
If your delta jobs are getting error out in BW then you don't need to worry about, because till that time your delta pointer in source system is not yet updated. But if you make any request green by chance in BW monitor then your delta pointer will get updated and you might loose some delta.
You can request repeat delta multiple times without any issue.
Regards,
Durgesh.

How to re-init a delta upload?

Hi experts
I have done a delta initialization, and delta updates; but after occurs some troubles and then I must do a full update. Now when i want do new deltas uploads, the system tell me that can't find the last "mark". Im try to do an "initialization with out transfer data", but the message is that already exist delta loads for the same period in the id request 25910 (this id is the first inicialization)
How can I do a re-init delta upload?
Thank you in advance

Sorry, I think that I dont understand you well..
Please check if this right: "I can delete the init with Id request 25910 (in the way that wou tell me) , and the data in this id requist NOT will be delete in the Infocube" is this true?
In need to the re-init because when I run the delta actualizations the error msg is "Nº RSBM103 - Delta upload is possible after successfull init"
Anyway, I understand that when is do a full update i lost the mark. Is this true?
Your commets are very helpful!!

Master Delta Load - Error "38 Duplicate records found"

Hi Guys,
In one of our delta uploads for a Master data we are getting error "38 Duplicate records found". I checked the PSA data but there were no duplicate records in that.
Once the data upload fails I manually update the failed packet and it goes fine.
Please any one have solution for this.

Hi
You can see the check box in the Processing tab page. Make a tick mark for the check box Ignore Duplicate Data Records indicator . When multiple data records that have the same key are transferred, the last data record in the request is updated to BI. Any other data records in the request with the same key are ignored.
Help says that:
To maintain consistency, ignoring duplicate data records is only possible if the data is updated serially. A serial update is when data is first updated into the PSA then, after it has been successfully written to the PSA, it is updated into the master data or text tables of the InfoObject.
If a DataSource transfers potentially duplicate data records or if you manually set the Ignore Duplicate Data Records indicator, the PSA Only update type is automatically selected in the scheduler.
hope it clears ur doubt, otherwise let me know.
u can see the same in my previous thread
Re: duplicate records found while loading master data(very urgent)
Regards
Kiran

Delta upload in different times and targets

Dear BW Gurus,
I have to fill a Master Data table with a delta (for performance reasons) from an ODS object, and later fill an InfoCube with the same delta from the same ODS Object. This two step approach is necessary because the Cube uses the Master Data filled in the first step - so I cannot do the two uploads within the same InfoPackage.
My approach was the following in a Process Chain:
1. Fill and activate "source ODS"
2. Load request from "source ODS" to PSA only
3. Update Material Master from PSA using "Read PSA and Update Data Target" process with the variant setting the PSA table and the Master Data InfoObject as Data Target.
4. Run "Attribute Change" process for the Master Data IO
5. Update InfoCube from the same PSA that was used for the Master Data InfoObject. This is also a "Read PSA and Update Data Target" process with the variant setting the same PSA table as before and now the InfoCube as the Data Target.
To me this seemed logical but when I run the Process Chain I got the following error message at point 3 (update Master Data from PSA): "No request for posting found in the variant".
This appears strange to me because if I specified the request, it would only work for the first upload and not for all the others.
Can anyone please help me how to overcome this issue of Delta upload in different times and targets?
Thanks in advance,
Attila

Gopi,
If I create two delta InfoPackages, the first one clears the delta queue, so the second InfoPackage won't find any data. This is unfortunately not the way to do...
Srini,
Your proposal is quite original - if I upload the same ODS with its data (amended by the date field) that would in fact generate a new delta for the same ODS.
However, in the meantime a more simple idea came up in our BW team, inspired by your proposal. For the uploading of the Master Data I now don't use the delta functionality of the ODS export Data Source, but instead I set up a full upload filtered for the actual date. This ensures the good performance of Master Data load (load time will not increase with time) and also we will have all recent Master Data uploaded from the ODS because that load is in the same Process Chain where the "Source ODS" is updated. Later in the same Process Chain I simply start the delta upload for the Cube.
Thanks a lot for all your help.
Attila
P.s. I will be out of office for until 24th July.

Failure in Delta Upload

friends,
       we have delta upload for our purchasing data to BW. from the infopackages the data is Updated to ODS- 0PUR_O01, which provides data to Infocubes - 0PUR_C08 and 0PUR_C07 and ODS 0PUR_O02 ( which in turn provides data to infocube - 0PUR_C09 ). 3 days back one request in ODS 0PUR_O01 went into error status. WAfter marking the request "RED" it was deleted from the ODS, but since the request had the same PSA_ID as that of an another successful (GREEN) request in the same ODS with data mart status ticked, this request also got deleted by mistake, as a result the datamart status for all the request in the ODS (0PUR_O01) is missing, from this time onwards the subsequent data updates to infocubes 0PUR_C08 and 0PUR_C07 and ODS 0PUR_O02 (also to Infocube 0PUR_C09 ) are finishing in Error status. we have deleted all the requests (after marking them "RED") for previous three days from the data targets ( infocubes 0PUR_C08, 0PUR_C07, and 0PUR_C09 and ODS 0PUR_O02). we also have deleted the correposnding requests from ODS 0PUR_O01 (after marking them "RED").Now when we are trying to reconstruct the requests at 0PUR_O01, it goes successful, but when we try to activate the requests into subsequent data targets ( back ground job BI_ODSA* ) the job fails with a short dump and the following error message.
Error Message:-
Check Load from InfoSource 80PUR_O01 , Packet Delta Package for Update by ODS 0PUR_O01
Please execute the mail for additional information.
Error message from the source system
Diagnosis
An error occurred in the source system.
System response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
Short Dump:-
What happened?
   The current application program detected a situation which really
   should not occur. Therefore, a termination with a short dump was
   triggered on purpose by the key word MESSAGE (type X).
What can you do?
   Print out the error message (using the "Print" function)
   and make a note of the actions and input that caused the
   error.
   To resolve the problem, contact your SAP system administrator.
   You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
   date.
   is especially useful if you want to keep a particular message.
Error analysis
   Short text of error message:
   Request 0000017556 in ODS 0PUR_O02 must have QM status green before it i
   s activated
   Technical information about the message:
   Message classe...... "RSM1"
   Number.............. 110
   Variable 1.......... 0000017556
   Variable 2.......... "0PUR_O02"
   Variable 3.......... " "
   Variable 4.......... " "
   Variable 3.......... " "
   Variable 4.......... " "
How to correct the error
   Probably the only way to eliminate the error is to correct the program.
   You may able to find an interim solution to the problem
   in the SAP note system. If you have access to the note system yourself,
   use the following search criteria:
   "MESSAGE_TYPE_X" C
   "SAPLRSATREE" or "LRSATREEF28"
   "RSATREE_START_ACTIVATION"
   If you cannot solve the problem yourself and you wish to send
   an error message to SAP, include the following documents:
Please suggest a solution for this problem and to bring back the missing data mart statuses of the all the requests in ODS 0PUR_O01.

hi olivier,
   the said request is in ODS 0PUR_O02. will try to explain the scenario:
the data flow in this regard is:
PSA ->          Infopackages                       -
> *
          (2LIS_02_SGR, 2LIS_02_ITM etc.)
*-----> ODS (OPUR_O01) --> Infocube (OPUR_C07)
*-----> ODS (OPUR_O01) --> Infocube (OPUR_C08)
*-----> ODS (OPUR_O01) --> ODS (0PUR_O02) -
> ***
----> Infocube (OPUR_C09)
now when we try to reconstruct a request in ODS OPUR_O01, the a new request is created (Requid- 175429) with green status but without datamart icon. Now when this request is activated in 0PUR_O01 and since "Activate ODS object Data automatically and   Update Data Targets from ODS object automatically" is checked in 0PUR_O01, new requests are created in ODS 0PUR_O02 (Requid- 17566)and infocubes OPUR_C07(Requid- 17566) and OPUR_C08(Requid- 17566). All these requests are with 0 data and PSA_ID are also 0. and then the above short dump and error comes in.. one thing to note here is
"Activate ODS object Data automatically and   Update Data Targets from ODS object automatically" option is also checked in ODS 0PUR_O02.
Hope this clears up everything..
Edited by: Nivin Joseph Varkey on Jan 14, 2008 7:20 AM

Issue in CRM Delta upload to BW

Hi,
I need to configure the exchange of data between CRM 7.0 and BI 7.0. I am facing facing issue of Delta upload from CRM to BI. Initial upload to BI was successful but not working Delta. I need to download the activity and the opportunity. But in transaction RSA7 the delta queue displays 0 records for 0CRM_SALES_ACT_1, 0CRM_SALES_ACT_I, 0CRM_OPPT_H and 0CRM_OPPT_I. It's status is green. In the transaction SMW01 this BDoc red in an error state with the text "Could not determine module name: BUS_TRANSACTION_MESSAGE GENKEY: REP_GET_RECIPIENT" and "Service that caused the error: SMOH_REPLICATION_WRAPPER_MSG".

Hi,
My scenario was delta was not getting loaded within BW ods and cube... Delta was getting captured from source system but it was not getting loaded from ODS--> ods/cube....
So i first deleted the data mart symbol from ODS (source) and then did the repeat delta...
Regards,
Anup

Delta upload for generic data sources.

Hai All,
I tried as per SAP online document , but still i am not getting the result i.e delta upload from the BW side. Here i explained everything what i did.
In R/3
1. I have created a table with 3 fields SNO, SNAME, DOB
2. Then i created some entries in that table.
3. With Tr Code RSO2 i created one data source. Here i took Master Attribute Datasource
4. In generic delta i took the Generic field as DOB. and Time stamp and upper limit 10 sec.
In BW side
1. I have replicated the data sources under application compone in which i have creatred in R/3..
2. Then i activated that data source and created infopackage for that.
3. in the selection i have specified 01.01.1900 to 01.01.9999
4. First i made Full Update then i get all the records from R/3.
5. In R/3 i have created 2 more entries.
6. In Infopackage UPDATE Tab i have selected the Initilize Delta Process ( Initialization with Data Transfer).
For this i am getting the error message as follows.
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
Here i closed the all things in R/3 as per the note mentioned above. Still it is giving the error message.
If i select the Intilization Delta Process( Intilization with out Data Transfer) then i am getting the option Delta Update . I selected this Delta update and scheduled but no data is coming.
Please help.
Regards
Prashanth K

Hai Sachin,
I am getting the problem at PSA only. Actually that is connected to ODS Object only. Until unless we don't get the delta data into PSA we can't proceed futher. So please help. I am working on NW 2004S.
Regards
Prashanth K

MAster Data - Delta Load Error?

Hi,
I am having error in 0COSTCENTER delta load. In the Info Package of 0COSTCENTER, it was not selected to PSA. It was selected to InfoObject directly.
Since this is a delta load for Master data, how can i correct this error?
Thanks!
Venkata

Hi Venkat,
You can done a full upload without affecting Delta upload. Make a test on Dev or Qual and you will see that a full on Master Data does not stop delta process.
Ciao.
Riccardo.

Replicated then upload error

Hello:
When I replicated source system datasource in RSA1,But upload error in monitor.
Error message tell me to repliacted the datasource and activated,and error keep on.
How can I deal with the problem.
Regards&Thanks!
zagory

Hi zagory,
I think this can happen when there is some changes done on datasource and datasource is not replicated.
Solution: Execute T code SE38 in BW give programme name as RS_Transtrucuture_activate and execute the programme. Give Infosource and Source System and and activate.This will replicate the datasource and its status is changed to active. Once this is done,delete the request by changing technical status to red and trigger Infopackage to get delta back from source system.
Thanks,
Srinivas.

Process Execute InfoPackage, variant 2LIS_12_VCHDR Delta Upload 2 has statu

Hi All,
i am loading trx data.but load was failed.failed request is showing " Process Execute InfoPackage, variant 2LIS_12_VCHDR Delta Upload 2 has status Ended with errors (instance REQU_4B9BAQK7NIXFRH9RKD0VF5LWP). why this error is comimg frequentely.i want to know the reason and how can i solve this issue? please help me.
Thanks,
Turan

Hi Turan,
Can you send the details error from DETAILS tab ?see all the process levels like Requsets,Extraction,Transfer& processing .
Regards
Pcrao.

Upload Error message: HTTPS protocol is not supported

Hi,
   Whenever I do a quick par upload i'm getting an 'Operation failed' message to check sap-plugin.log.
   Log says
Upload Error message: HTTPS protocol is not supported, please ensure this server is not using HTTPS. My webdynpro applications are getting deployed without any issues.
     How to resolve this?
Thanks
Sumathi

Hi Sumathi,
As there are often problems with the Quick PAR Upload reported, I would suggest to use the "normal" PAR upload from the icon tray (you have to activate the portal icons in the icon tray). That is almost that "quick" (one or two clicks more needed, we don't talk about more than a second) and - it works (it least it should, and at least it works in most cases even if the Quick PAR Upload fails).
Hope it helps
Detlev

Delta upload errored

Similar Messages

Maybe you are looking for