Error in delta process

Hi people,
I'm using the process delta, but it occurred one problem. When i execute the initialization of process delta, i extract 536 registers, but when i execute delta, i get 0 registers. I went to font (R3 ) and created one document to test the delta, but nothing happened. In R3, i executed RSA3 and my document that i created is there, but not in process delta.
Note: i created a filter in initialization and delta (period 2006) and the document that i created to test, was also in period 2006.
I apreciate your help in resolution of my problem. Thanks!
JA

I have other problem... i went to table BWOM_SETTINGS and changed the parameter BWFIOVERLA to X, and i can extract data from delta. The problem is.. i execute one time the delta, and the changed data appears, but when i execute again the delta, it was supposed just appear the data changed after the last time i executed the delta, and that not occurs.
Suppose.. in the first time i execute the delta, it appeared 20 registers.. then, i changed one document, 2 new registers, when i execute the delta, appears 22 registers, and not just 2..
Anyone can help me?
Thanks!

Similar Messages

2LIS_11_VAHDR - Initialize delta process error

Hi,
I have an issue initializing infosource 2LIS_11_VAHDR for delta process on a new BW3.1c instance created from a system copy. Other delta loads work properly but not this one.
In the AWB monitor, the status indicates 'no data available' even if the source system LIS setup tables have been recreated with some records available. What's more puzzling is the fact that the error also indicates that 'the data request was a full update' even if the update mode is set to initialize delta process.
Any tips would be appreciated.
Thank you,
Frank

RSA3 simulated 0 records but the R/3 table had plenty of records to be processed.
But what resolved the problem was deleting and re-creating the BW infopackage and re-initializing the delta process.
Thank you all for your time.
Frank

Error in delta run in the process chain

Hello Experts,
I have a delta infopackge that runs everyday , since many days the process chain is giving error at the IP.
The IP is red everyday and the following objects does not start, however when I check in the monitor the ip is completed successfully without any errors.
I checked the logs which is in greeen in the batch job , please find the details below.
Job started
Step 001 started (program RSPROCESS, variant &0000000111903, user ID ALEREMOTE)
Last delta upload not yet completed. Cancel
Data saved successfully
Start InfoPackage ZPAK_4EH1CYBST65PTYCQVFAQY6ZI7
Last delta upload not yet completed. Cancel
Last delta upload not yet completed. Cancel
InfoPackage ZPAK_4EH1CYBST65PTYCQVFAQY6ZI7 created request
Request REQU_4L001XOSR2IQQ14M90QLO1CTA could not be generated with InfoPackage REQU_4L001XOSR2IQQ14M90QLO1CTA without errors
Last delta upload not yet completed. Cancel
Error After Starting InfoPackage ZPAK_4EH1CYBST65PTYCQVFAQY6ZI7 in Process Chain ZIM_INT_ORDER
Entire chain now has status 'A'
Job finished
Could you please suggest.

Hello
Thanks for your reply
the problem was with the way it was schudled, the chian was ticket at periodic run , as a result it as running automatically, and causing problem.
I have removed the periodic n saved it again ...the error stopped appearing !
The issue is resolved now.
Thanks for your help.

Error when perform init delta process (w/data)

Hello all!
when i perform init delta process (without data transfer), i am receiving the follow message:
SUBRC= 2 The current application triggered a termination wi
Recently we upgrated to SapNetWeaver 7.31 (before was 7.0).
Is there anything that i need to do to execute a init delta (without data transfer)?
SPK 731 LEVEL 10.
thanks.

Hi,
What data source and at which server you doing this?
Can you check your extract structure(source system side) was active or not?
replicate your data source into bw and activate it.
later try to do init without data transfer.
Thanks

ODS Delta Process, DataSource and Delta Queue

Hi to all,
loading data from a SAP source system into SAP BW 7.0 via generic 3.x datasource causes problems.
Here is a short description:
The data flow is from a source table using a generic extractor into a target ODS in full update mode.
Update rules should move data from table structure into ODS structure in this way:
Source table structure
CustKey1     Key2
13386          C23
13386          B14
13387          A13
13387          E25
ODS structure
CustKey1     col1     col2
13387          A13     E25
This works pretty well - as long as all records with the same CustKey1 are transfered in the same data package. Data Browser (SE16) shows the situation in ODS-"New data" view (data is not activated):
Request    Data_packet_number     Data_record_number      CustKey1
112           000003                  1.061              0000013386
112           000004                      1              0000013386
112           000004                      2              0000013387
There are two records for CustKey1 0000013386 with
data record 1.061 in data packet 000003   and
data record       1 in data packet 000004.
The obove constellation is the cause for errors in the ODS Delta Queue and subsequent data processing.
I think there may be one solution to solve the problem by changing the Delta Process of the Data Source.
The properties are:
- Record type: Full, delta, before, after images
- Delta type: Delta from delta queue or from extractor
- Serialization: No serialization, serialization of request, serialization of data packages
But how can I change these settings? Transactions RSA2 RSO2 RSO6 RSO8 don't do this.
What is the right delta process to use?
I have tried changing the delta process generating several 3.x datasources with the following delta processes (see table RODELTAM)
- " " (Full-upload)
- AIE
- ADD
Unfortunately with no effect.
Who can help?
Regards
Josef
Edited by: Josef L. on Mar 20, 2009 7:44 PM

hi venkat,
whenever you load a delta from ods to cube , whatever the data changed in ods since last delta will be updated, hence from you case, both req1 and req2 will be loaded to cube.
Assign Points if useful
Ramesh

Error handling in process chain-doubts

Hi ,
I have some doubts in error handling of process chains.
1) I have aprocess load infopackeage and subsequent process is update fromPSA.
process load infopackage got failed , so i loaded the IP manually and repeated the next i.e process update from PSA .
How to correct the process chain from now?
2) I have aprocess load infopackeage and subsequent process is Delete request in infocube .process load infopackage got failed , so i loaded the IP manually and repeated the next process i.e Delete request in infocube. Chain continued by deleting the right request . How this is possible ?
Plz help me as this is urgent and daily i have to deal with this issues. If any documents on error handling is greatly appreciated.
My mail id is [email protected]
Regards,
Pavan

Hi Pavan,
Hope the following links will give u a clear idea about process chains and clear ur doubts.
Business Intelligence Old Forum (Read Only Archive)
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/c08b3baaa59649e10000000a11402f/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/8da0cd90-0201-0010-2d9a-abab69f10045
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/19683495-0501-0010-4381-b31db6ece1e9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/36693695-0501-0010-698a-a015c6aac9e1
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9936e790-0201-0010-f185-89d0377639db
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3507aa90-0201-0010-6891-d7df8c4722f7
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/263de690-0201-0010-bc9f-b65b3e7ba11c
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
Errors in monitoring of process chains can be categorized into 4 different sections...
Master data - Full Update
Master data - Delta Update
Transaction data - Full Update
Transaction data - Delta Update.. in terms of loading of data which can be due to server shut down or system maintenance... errors due to incorrect entries in the OLTP system in which case you'll have to fix the errors in the PSA and manually load the data...
Otherwise it can have errors on Attribute change run being locked by some other job... Aggregate Roll up failing because of attribute change run being run at the same time... Problem with hierarchies and save hierarchies...
There can be problems with the data store activation if the ODS object contains any incorrect request sitting inside it... then, you need to delete the incorrect request and reload the data again...
In case of Transaction Delta failure, you'll have to request for a repeat either manually in the infopackage or using the repeat option if available on right clicking the load event...
For Master Data Delta failures, you need to do an Re-init by deleteing the previous initalization condition in the "initalization option for source systems" in the menu scheduler or reschedule the enitre chain... because, master data generally do not support repeat of last delta ...
U can even look into these links:
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
For common data load errors check this link:
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
****Assign Points if Helpful****
Regards,
Ravikanth.

Short dump error for delta load to 0CFM_C10 via 0CFM_DELTA_POSITIONS flow

hi all,
i am getting short dump error for delta load to 0CFM_C10 via 0CFM_DELTA_POSITIONS flow.
not able to figure out the actual issue and how to solve it.
can anyone suggest?
below is the details of the short dump
Short text
    Exception condition "UNKNOWN_TRANSCAT" raised.
What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    A RAISE statement in the program "CL_SERVICE_TRG================CP" raised the
     exception
    condition "UNKNOWN_TRANSCAT".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "RAISE_EXCEPTION" " "
    "CL_SERVICE_TRG================CP" or "CL_SERVICE_TRG================CM003"
    "SORT_TRANSACTIONS"
    or
    "CL_SERVICE_TRG================CP" "UNKNOWN_TRANSCAT"
    or
    "SBIE0001 " "UNKNOWN_TRANSCAT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.

Hi,
It seems like some routine are there and check your rotines , transformation etc.
Regards
sivaraju

"Caller 09 contains an error message "in Process chain

Hi
Most of my process chains have failed today.All are showing the same error i.e
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.
If I am repeating the process it is showing the same error again
Please help

Hi,
Even I got the same problem. All you need to do is:
1) Go to Infopackage
2) Update Tab:
Choose: Initialize Delta process
under that choose: Initialization with Data Transfer
3) Save
4) Go to Schedule Tab:
5) Start the Load
6) Refresh the page: /nRSA1
7) Once it is done, then again go to the Update tab of the Infopackage
8) Select Delta Update
9) Save
And now run the Process Chain.
You should be able to run it smoothly.
Thanks & Regards
Hemendra Sharma

How to identify what are all the errors appears in process chain,

Hi all,
i have a process chain running, but i want to find out what are all the errors that the process chain has thrown
thanks
pooja

Hi Pooja,
Errors in monitoring:
SID error
Reason: If the corresponding master data is missing for the particular transaction data.
         1. Check for the load timing for the respective master data, if it less than an hour then make the request red and repeat the ip.
         2. If the data is loaded to PSA then you have to delete the request from target and manually push the data to from PSA.
         3. If we are required for selective update then note down the info source from header and find it in RSA1,select the one with Single as postfix.
         4. Goto data selection tab and change the range.
Tip: change the last 4 digits for from to 0000and the last 4 digit for to     9999.
        5. Repeat the ip.
         6. In case only of failure in one target goto RSA1 find the PSA, put he request no. and reschedule it.
Note: IF PSA is present never make the request red rather delete it.
Replication error
Reason: Data source replication Failed.
         1. In order to handle this error you should be known to IP, info source and source system.
         2. Goto RSA1, find the data source in the source sys tab.
         3. Right click on the data source and replicate it.
         4. Since all the transformation rules pertaining to this data source need to be reactivated so go to SE38 and execute rs_transtru_activat_all, data source and sys name.
         5. Delete the red request from the target.
Update R not supported
Reason: The corresponding initialization flag for the ip is lost.
         1. Goto header click on the ip and goto schedule tab and click initialize in the source system, whatever screen appears delete the only request present(the initialization flag).
         2. Goto RSA1, find the ip in the info source (one with the Adhoc initialize flag).
         3. Goto update tab and select Initialize delta process try going for with data transfer.
         4. Reschedule the IP.
Duplicate Record Error
Reason: Duplicate error records for the loaded master data.
         1. Goto info package via header or via RSA1.
         2. Goto processing tab and change the ip setting, selecting only PSA and ignore duplicate records and re run the ip.
         3. Do remember to change the ip settings back to the original once after the second step.
ODS activation failure
Reason: Prerequisites for ODs activation not satisfied i.e. unique key.
         1. Goto maintain variant.
         2. Check for the QM status of the requests in the target they should be green.
         3. Then click the ODS activation tab.
         4. In the screen which appears put the requests for which ODS activation failed.
         5. Activate these and keep on refreshing them until status reverts from green,
Remember to refresh these requests one at a time.
         6. If requests are red then delete them from target.
         7. Reschedule the IP.
Note: Never Try activating ODS manually if it is Y1.
Aggregate Rollup error
Reason: No aggregate found for the respective rollup.
         1. Click on the variant in which the error occurred.
         2. Goto chain tab and copy the variant and instance.
         3. Run the nestle provided program YBW05.
         4. Put in info in there and put the status as g green.
         5. Execute and refresh the status.
Lock issue
Reason: The same ip is been locked by other user or may be used by other process chain.
         1. We can see the locked entries and in the transaction SM12.
         2. Wait for the other process to get complete once the ip loads to target in that process then there is no need for running it for the process.
         3. In other case make the request red, when PSA is present then goto environment tab ->schedule->initiate update.
         4. In the box appears select update in the background.
         5. And the manually update the failed IPs by selecting manual update in the context menu.
Alfa confirming value error, Time conversion error, Chain didnt start, Delay due to long running job, Poor system performance,Heirarchy node exist in duplicate.
Reasons:
Alfa confirming error: Data format mismatch.
Time conversion error: Date, time format mismatch.
Chain didnt start: A scheduled chain didnt triggered at the prescribed timing.
-For all the above error we have to raise a ticket.
Idoc or TRFC error
Reason: An Idoc is been stuck somewhere.
         1. Reload the Master Data manually again from Info-package at RSA1.
         2. Release the Idoc.
         3. In the source system level got environment->transaction->Transaction RFC or Data ware housing level.
         4. In the Screen if the status is Transaction Recorded it means its stuck goto edit and click Execute LUW or press F6.
         5. If status is Transaction executing then it means its fine wait.
         6. Or raise ticket.
Error Due to short Dump
Reason: Error due to Short dump could be due to many reasons i.e. memory, table space, lock, error record, page allocation, failed change run.
Process terminated in the Source system.
           Reason: Sometimes we face that a load has failed due to job Termination at Source System.
      This happens due to unavailability of the source system or some connectivity problem between source and target systems.
1.      Make the request red.
2.      Delete the request from the data target.
3.      Reschedule the ip.
4.      If still the job fails raise the ticket.
And also check in following links:
Process Chain Errors
/people/mona.kapur/blog/2008/01/14/process-chain-errors
Common Process chain errors
For Data Load Errors check this blog:
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Pls assign points if it helps u,
Thanks & Regards,
Madhu

Bdoc error in Delta load

Hi Experts,
I have an issue in Delta processing.
When new customer is created in ECC with complete address information, it is ended with BDOC error in CRM2007. The error is
Incomplete address; enter country AM 216
if i maintain the Vendor ID in ECC, this error is not appearing. As per our requirement Vendor ID is not required to maintain.
Any suggestions for next steps to resolve these errors with out maintain vendor id in ECC? Thanks for any input anyone can offer.
Regards,
A

Hi,
I have looked into your issue.
This is a very generic error. General context is, if you have not filled the country you will get this error. But yes there are other reasons for this error to occur:
When you have some user exits in your system, at the time of Main data getting mapped to BAPIMTCS, exits might be defaulting the BAPIMTCS data of Address before it is sent to CRM server.
So this error occurs very much when there are user exits present and which might modify the data before it is sent to CRM and in CRM, when the address data is not present then obviously this is going to be raised.
This has to be checked in your system. I hope this helps.
Regards,
Venkat

Initialize Delta Process without data transfer

Dear Gurus,
I am facing a problem when I try to "initialize Delta Process without data transfer" an ODS.
I first deleted the initialization request in Scheduler->Initialization Options for Source system and then I executed the Infopackage.
The status of the new init. request is red and I get the following error message :
Request REQU_DMJI1J66397EM5OZMC1EQJLWZ (192.384) for DataSource 8ZSALETXT from source system PW1CLNT600 has the status green and a lesser SID (and is therefore older) than the request that you currently want to update into the DataStore object.
This is not possible because the sequence of requests has to be followed.
Delta- and init requests have to be updated to the DataStore object in the request sequence.
The problem is that I can't find this request (REQU_DMJ...) anywhere.
Could you please explain me what to do with this issue and tell me if it is possible to make the system just ignore this request ?
Thank you in advance
Fabien

Hi............
U r not able to find REQU_DMJI1J66397EM5OZMC1EQJLWZ in the Manage screen of the ODS right?.........
Go to RSRQ...................give this request number and check...........if the Status is green........in the Header tab check whether the load is till PSA or not............if it is till PSA............then go to the Status tab and click on Process Manually to push the request in the target........otherwise just make the QM status red here..............then do the load.......
Regards,
Debjani.........

Error Occured while processing a Request-openning a another coldfusion page from old page link

in one page there is dynamic link in that i want to open anather page...
code is compiled ok and page is at place where i refered a link but it gives error 'error occured while processing a request'
Error Diagnostic Information
An error has occurred.
HTTP/1.0 404 Object Not Found
this error shows please help me...
i am new in coldfusion.
Thanks.

Hi Salvatore,
This is a very wide error. You did not provided any other info as specified by Michael. Just a wild guess, this sort of error occurs generally when classpath or java_home properties are not set correctly. But, as i said it is very wide, some more info will be useful.
Regards
Chander Kararia

Duplication of data in BI, with 0FI_GL_10" which has a AIED delta process.

Hi,
I need some help!!
In my actual proyect, we are using DS "0FI_GL_10", which has a AIED delta process. Someone knows, if this configuration could carry on any type of extraction problem, such as a duplication of data in BI? This is what it is happening in my proyect. In the inic of "0FI_GL_10", I extract "one" record, and after a few days when I run a delta extraction, I have a new same record in the PSA, (with the same key fileds and attributes than the other). Also, in my tranformation rule, that link my PSA with a DSO, the key figure 0SALE is parameterized as summation in the aggregation, this is wrong and or i have to use a overwrite aggregation? or my problem is in the type on process delta that has the extractor "0FI_GL_10"?
Thanks in advance for any kind of help.
Regards,
Juan Manuel

Hi
There are chances that this datasource might send in the same records when run in delta mode and that is the reason a DSO is needed with overwrite mode in between.
Also there are a couple of notes stating problems related to this datasource.
Note 1002272,1153944, 1127034
Refer this if you are having specific issues with this datasource
Hope this helps
Gaurav

How to catch date errors and continue processing in a PL/SQL procedure

I'm updating a date field with dates constructed from day, month and year fields. The incoming data has many instances of day and month that are not valid dates, ex 11 31 2007. There is no 31st day in November.
I would like to write a pl/sql script to scan the table containing these values and log the rows that produce conversion errors.
I thought I could do this with exceptions but there are no exceptions that correspond to the ORA-01847 error for mismatched day and month.
Here is what I tried (the print procedure is a local wrapper for DBMS_OUTPUT.put_line):
PROCEDURE date_check IS
start1 DATE ;
BEGIN
select to_date(nvl(yearcollected,'9999') ||'/'|| nvl(monthcollected,'01') ||'/'|| nvl(daycollected,'01'),'YYYY/MM/DD'))) into start1 from incoming_data where id=1 ;
     BEGIN
          update temp_test set test_date = start1 where id=1 ;
     EXCEPTION
          WHEN OTHERS THEN
          print('Date error message from exception block');
     END;
print('Processing continues after handling date exception') ;
END date_check ;
Is there a way to catch this kind of error and continue processing after logging a message?
-=beeky

Hi, Beeky,
There are lots of different error messages associated with bad dates. Rather than try to catch them all, I use a BEGIN ... EXCEPTION block that contains nothing but a TO_DATE call. This is one of the rare occassions when I think "EXCEPTION WHEN OTHERS" is okay,
The following function comes from a package. If you want to make a stand-alone function, remember to say " *CREATE OR REPLACE* FUNCTION ...".
--          **   t o _ d t   **
--     to_dt attempts to convert in_txt (assumed to
--          be in the format of in_fmt_txt) to a DATE.
--     If the conversion works, to_dt returns the DATE.
--     If the conversion fails for any reason, to_dt returns in_err_dt.
FUNCTION     to_dt
(     in_txt          IN     VARCHAR2                    -- to be converted
,     in_fmt_txt     IN     VARCHAR2     DEFAULT     'DD-MON-YYYY'     -- optional format
,     in_err_dt     IN     DATE          DEFAULT     NULL
RETURN DATE
DETERMINISTIC
AS
BEGIN
     -- Try to convert in_txt to a DATE. If it works, fine.
     RETURN     TO_DATE (in_txt, in_fmt_txt);
EXCEPTION     -- If TO_DATE caused an error, then this is not a valid DATE: return in_err_dt
     WHEN OTHERS
     THEN
          RETURN in_err_dt;
END     to_dt
;

An error occurred when processing the spool request. (Possibly due to memory problems)

Hi SAP,
My backgroud job is failing with log as shown below
Job started
Step 001 started (program ZMRS0065, variant SUS
Step 002 started (program ZDRS0090, variant SUS
Step 003 started (program ZFRS0305, variant SUS
Step 004 started (program ZFRS0300, variant SUS
Access error
Job cancelled after system exception ERROR_MESSAGE
An error occurred when processing the spool request. (Possibly due to memory problems)
Kindly help out in this issue
Regards
Mohammed

Hello Mohammed,
Have you seen any error in your SM21 system log and developer trace of spool work process
during that time?
The maximum size when create spool is 2GB.Pls also check if you are creating a spool
larger than it.
Best Regards
Jie Bai

Error in delta process

Similar Messages

Maybe you are looking for