Error in RSA3 for Delta

Hi,
The data load for 0FI_AR_10 (payment history) delta load is fetching zero records after we did EPH4 (Golden Tax) Upgrade to the ECC 6.0 system.
When we check in RSA3 for Delta it is throwing error as -> Message no. RJ012
There is no other info. The data load looks successful in BW but with zero records.
Please suggest.
We are facing some what similar issue for 0CUSTOMER_ATTR as in the Ticket:
[0CUSTOMER data from Unicode R/3 to Non-Unocode BW Error|0CUSTOMER data from Unicode R/3 to Non-Unocode BW Error]
Thanks,
Joe

Hi
Go to RSO2 and give the data source name 0FI_AR_10 -- there you ahve extractor BWFI3D_GET_FIAR_CM_PH(functional module) ---> reset the function and module and reactivate it
mostely the problem will be solved.
incase if it is not solved the reason might be as below
These datasources have extraction type as F1 and the function module used is BWFI3D_GET_FIAR_CM_PH( Tcode: RSA2).
When we go through the code of the Function module, there is a Case statement with update mode which is written in such a way that when the update mode is full it throws one type of error and when the extraction mode is others(which includes init, delta etc) it throws another type of error.
This update mode field in the Function module will take the value when we run the Infopackage and we will get an error saying: 'Update mode when others is not supported by extraction API'(this error occurs as the update mode takes the value of c and executes 'when other' case).
In extractor checker(RSA3), the default value taken by the update mode will be F (since we are not executing any infopackage and the update mode value will be F by default).
So ultimately when that function module is executes it will throw an error no matter what type of load(delta or full) we select.The error will occur but it will be handled differently when you run in RSA3 and when you run the Infopackage.
so i would suggest you to raise a note to SAP on the same
and i will post if I find any solution going in future on the same.
Very intresting Question
pleasure answering
Santosh

Similar Messages

Error in RSA3 for 0GL_ACCOUNT_T011_HIER

Dear All,
I have tried to extract the data in RSA3 for the Data Source 0GL_ACCOUNT_T011_HIER. As the hierarchy name is mandatory, I have pressed F4 to get the hierarchy names. System gives following shortdump
Runtime Errors: SAPSQL_ARRAY_INSERT_DUPREC
Except : CX_SY_OPEN_SQL_DB
Any one could you please tell me what could be the cause and the solution.
With Regards,
Balachander

Hi Bala,
Try this notes
839094
890680
1158109
852935
949194
Hope this will give you some idea for your problem.
Good Day!!!
Regards
Arun S

Error in LBWE for Delta

Hi,
I am using 2LIS_13_VDKON for extracting Invoice data from SAP R/3. I initialized the data and extracted the data successfully .Then I need to schedule the Job in LBWQ to collect the delta queue records from Extraction Queue.I am using 'Queued Delta ' Update mode.
But when I tried to schedule the Job using the Job Control I am getting an error. I am able to set the start date for the Job. When I try to schedule the Job , I am getting an error says that 'Error Generating Job' and I am not able to complete the Job.
Hence all the extraction queue records are not moving to Delta queue.
I am not sure how to rectify this error ,since there is no more information for the error.
Please let me know the solution if anyone faced this issue earlier .
Thanks for your time.
Thanks & Regards,
Raja

Hi,
Did you perform any enhancement on this data source....did you lock the users at the time when you were doing the data source enhancement...?
otherwise delta queue may face some problems and deltas may stop coming into the delta queue even if you have initialized before...
In fact, if not taken with care, can lead to various errors: delta requests terminate, the update from the extraction queue does not finish or V3 update is no longer processed, the initialization on data that was generated before the change no longer works, the protocol terminates...in short, a real tragedy !
Therefore, you should carry out the following steps before you change the extract structure (also for an R/3 release upgrade or plug-in/support package import):
close your system and make sure that no updates are performed (both by users or batch/background process);
start the update collective run directly from LC (that concerns either the V3 update or the Delta Queued update);
At this moment, with "delta direct" method, the delta queue (RSA7) must be empty, with "delta queued" method, the extraction queue (LBWQ) and delta queue (RSA7) must be empty, with "unserialized V3 update", the extraction queue (SM13) and the delta queue (RSA7) must be empty.
load all data of the respective datasources into your BW System.
To completely empty the delta queue, request a delta twice, one after the other: in this way the second upload will transfer 0 data records, but only with the second upload is the data of the delta queue that is available as a delta repeat deleted.
Now, that all data containers of the relevant data flow are empty, you can make (import) the data source enhancement or import the transport request for that data source.
For more information, please visit
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
Also...filling of set up tables should be performed during posting free period/ when the users are locked..otherwise similar problems as mentioned above may arise..
Note : also when you are importing the treansport request, at that time also the users should be locked and queues should be empty...
Thanks,
Tarun Brijwani.

DBIF_RSQL_INVALID_CURSOR : Error extracting records in RSA3 for 2LIS_02_ITM

Hi
I'm extracting the data in R/3 system using tcode RSA3 for transaction datasource (2LIS_02_ITM). When i extracted the transaction data , it was giving time out error. Then i went into debug mode to find the error. While debugging the code it gave me a DBIF_RSQL_INVALID_CURSOR short dump.
NOTE : Data extraction is working for all 02 transaction data like 2LIS_02_SCL , 2LIS_02_S012. It s failing for only 2LIS_02_ITM only.
I have pasted the eror message below for reference. Urgent help required.
From
Bobby
ERROR MESSAGE DUMP for DBIF_RSQL_INVALID_CURSOR
Runtime Errors         DBIF_RSQL_INVALID_CURSOR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          09.04.2008 12:47:09
Short text
Invalid interruption of a database selection.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLMCEX" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Unable to perform database selection fully.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in
procedure "MCEX_BW_LO_API" "(FUNCTION)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
One of the database selections included a database Commit.
The selection was then supposed to continue. Before a
database commit, however, all outstanding database selections
must be concluded.
Possible causes in the application program:
While a read process from a database cursor is taking place
(within a loop SELECT/LOOP/EXEC SQL or before a FETCH command),
one of the following statements is used:
- MESSAGE (apart from MESSAGE S...)
- COMMIT WORK
- ROLLBACK WORK
- BREAK-POINT
- WAIT
- CALL FUNCTION ... DESTINATION (synchronous RFC)
- CALL FUNCTION ... STARTING NEW TASK
- RECEIVE RESULTS
- CALL DIALOG
- CALL SELECTION-SCREEN
- CALL TRANSACTION
- CALL SCREEN, or any other statement that results in the display of a
new screen
Whenever a program runs in debugging mode, a "COMMIT WORK" can
possibly be triggered during database selection. This abnormal
termination can also occur in debugging mode even with a correct
program.
A "COMMIT WORK" during debugging may be due to the following reasons:
1. A program or screen was regenerated during debugging
and updated in the database.
2. Each user needs a separate process in debugging mode, but
the number of available processes is restricted. If this
limit is exceeded, each debugging step then requires a
"COMMIT WORK".
The error occurs in a statement in which the table "MC02M_0ITMSETUP " is
accessed.
Missing RAISING Clause in Interface
Program                                 SAPLMCEX
Include                                 LMCEXU06
Row                                     1
Module type                             (FUNCTION)
Module Name                             MCEX_BW_LO_API
Trigger Location of Exception
Program                                 SAPLMCEX
Include                                 LMCEXU06
Row                                     220
Module type                             (FUNCTION)
Module Name                             MCEX_BW_LO_API
Source Code Extract
Line
SourceCde
190
at end of fieldnm.                   "PI 2000.2 SP_353722
191
if not <fs_field> in cond_select_tab.
192
cond_select = false.
193
refresh cond_select_tab.         "PI 2000.2 SP_353722
194
exit.
195
endif.
196
refresh cond_select_tab.             "PI 2000.2 SP_353722
197
endat.                               "PI 2000.2 SP_353722
198
endloop.
199
if cond_select eq true.
200
append &2 to e_t_data.
201
add 1 to counter.
202
endif.
203
endloop.
204
if s_maximum_size le counter.
205
exit.
206
endif.
207
else.
208
close cursor g_cursor.
209
s_flg_no_more_data = true.
210
exit.
211
endif.
212
enddo.
213
END-OF-DEFINITION.
214
end macro *****
215
216
CASE s_estruc.
217
          extractstruc   internal table    setup table
218
*-- MM-PUR
219
sel 'MC02M_0HDR'   mc02m_0hdr_tab    mc02m_0hdrsetup.
>>>>>
sel 'MC02M_0ITM'   mc02m_0itm_tab    mc02m_0itmsetup.
221
sel 'MC02M_0SCL'   mc02m_0scl_tab    mc02m_0sclsetup.
222
sel 'MC02M_0SGR'   mc02m_0sgr_tab    mc02m_0sgrsetup.
223
sel 'MC02M_0SCN'   mc02m_0scn_tab    mc02m_0scnsetup.
224
sel 'MC02M_0CGR'   mc02m_0cgr_tab    mc02m_0cgrsetup.
225
sel 'MC02M_0ACC'   mc02m_0acc_tab    mc02m_0accsetup.
226
*-- Application '03' (Inventory Management)
227
sel 'MC03BF0'      mc03bf0_tab       mc03bf0setup.
228
sel 'MC03BX0'      mc03bx0_tab       mc03bx0setup.
229
sel 'MC03UM0'      mc03um0_tab       mc03um0setup.
230
*-- Application '04'
231
sel 'MC04P_0MAT'   mc04p_0mat_tab    mc04p_0matsetup.
232
sel 'MC04P_0ARB'   mc04p_0arb_tab    mc04p_0arbsetup.
233
sel 'MC04P_0COM'   mc04p_0com_tab    mc04p_0comsetup.
234
sel 'MC04PE0MAT'   mc04pe0mat_tab    mc04pe0matsetup.
235
sel 'MC04PE0ARB'   mc04pe0arb_tab    mc04pe0arbsetup.
236
sel 'MC04PE0COM'   mc04pe0com_tab    mc04pe0comsetup.
237
*-- Application '05' (Quality Management)
238
sel 'MC05Q1_0INSP' mc05q1_0insp_tab mc05q1_inspsetup.
239
sel 'MC05Q2_0INSP' mc05q2_0insp_tab mc05q2_inspsetup.

Hi Bobby,
Did you already find a solution for this 'issue'?
I encounter the same problem. In my humble opinion this has nothing to do with the difference between structures.
When loading data in normal modus, there is no problem. When loading in debug, there is an error.
I also tested with other data sources and the same issue occurs there while nothing has changed.
If someone knows how to solve this issue, please reply.
Thanks!
Kind regards,
Bart

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

Error in Process Chain for Delta pack

Hi All,
Here I am facing error in process chain for delta pack.
Error:
Last delta upload not yet completed. Cancel I
Please send me the solution asap.
Thanks

Hi,
This message means there may be a load triggered by the same infopackage that may be still running or may be still having yellow status. Go to the monitor screen from this IP itself and it will show the paricular request (it will be the latest one). See if that load is active and running. If its active try to find out if load is happening, if its happening you may let it progress. If its not active you need to force the status to red and delete from the target. Once this is done you can retrigger the load. If its a datamart load you may need to reset the data mart status before the triggering the load.
Refer
Last delta update is not yet completed
Last delta update not yet completed-PC Chain Error
Last Delta Not Yet Completed
This is the same issue as yours.
Thanks,
JituK

Error in activating init flag for delta load

Hi everybody, I am trying to activate the init flag for delta load, when I schedule the infopak it is taking too long to execute and the status is remaining in yellow for a week. I checked in details tab the error message is u201C no data available in source system u201C Please helpu2026

Hi Vinod,
When there is no data available in the source system, you will have yellow flag for the delta init request. Check for the delta queue entry (RSA7) on the source system. Delta mechanism starts working once this flag is created. After that schedule the delta infopackage.
Also check on the source system whether there is any data avilable in the application tables related to this datasource. Take the help of functional consultants if required.
Regards,
Sreenivas.

RSA3 for 0BBP_PROD_HIER on EBP gets error msg

Run RSA3 on EBP system (similar to R3) for datasource 0BBP_PROD_HIER, and at the lower part of RSA3, there is a section called "Selections(internal format)", there are two fields listed:
HIENM
LANGU
The 1st field is list with the following two values:
R3MATCLASS Material group
R3PRODSTYP Product Subtype
Pick up 1st one, and run the extraction, but get the following error "Error 6 in function module RSS_PROGRAM_GENERATE
Message no. RJ028".
Check RSA6 for this datasource 0BBP_PROD_HIER, find the datasource only contains one field:
OLTPSOURCE DataSource
The extraction structure for it is ROHIEROS.
What could cause the above problem when running RSA3 for this datasource?
Thanks

Hi kevin,
Have u checked for SAP notes? Check these notes
705212 and 637303
Regards
Sriram

"Errors occurred during the extraction" for delta Extraction

Hi All,
I have one data source which is getting extracted by using the FM.Initially this is only full load.But now I have enabled delta on this data source.
While extracting the data from RSA3, with delta option, I am getting the error "Errors occurred during the extraction".
But I have given Target System, replicated the data source in target system and reactivated it again.
But again I am getting the error "Errors occurred during the extraction".
Could you please help me on this.

Hi
I have done the Data Source Initialization.

Error: - No service for system port, client in Integration Directory

Hi
In Idoc to File scenario, My Idoc 've been successfully send from the sender system.
but its neither getting displayed in the SXMB_PATH nor saved in the specified path.
I checked in SM58 in R3 that RFC user has access to send data to XI. But it showing below Error:_
ERROR:-
No service for system Sender Port (SAPDEV) client sender client (300 ) in Integration Directory
Please do the needful
Thanks,
Anshul

Hi Anshul,
Go to:
TCODE SXMB_ADM -> Integration Engine Configuration
Please change the system rile to be "Application System", then retest if the similar issue happen again after that.
If not helped, follow:
1. Clear SLD Delta Cache Referesh in the Integration Directory
2. Open the Business System in edit mode and select Adapter specific identifiers following the menu path:
Service -> Adapter Specific Identifiers
3. Please click in the button next to "Apply" button to pick up the Logical system from SLD.
Regards,
Caio Cagnani

Different number of records in RSA3 for Full and INIT

Hi All,
I am about to load the data from 0FI_GL_4 and checked it in RSA3 for the number of records. It returned different number of records when I run the extract with options 'F' and 'C'. Why is it so? This is the first time I am loading the data into BW for this datasource. I would expect the number of records to be same if I do either a full extract or an init but surprised by seeing different number of records.
Best Regards,
James.

Hi James,
Probably it's because of the time stamps stored in table BWOM2_TIMEST.
If you run a delta init and than a delta update then the number of the records should match with the record of the full update.
You can find some more info about table BWOM2_TIMEST here:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a7f2f294-0501-0010-11bb-80e0d67c3e4a#527,7,Timestamp%20Mechanism:%20New%20documents
Bye,
Zsolt

Generic function module for delta - which FM ?

Hi all,
I want to create a custom generic datasource in R3 which uses a function module for delta extraction. This is straight forward for full extract (copy FM RSAX_BIW_GET_DATA_SIMPLE - I already did this and have a full extraction working to BW). However I need to extract delta - and the above function module does not have example code for that (I have seen some forum posts that it 'can' be used - but this looks like a pseudo get around where the delta field name is passed in I_T_SELECT).
FM RSVD_BW_GET_DELTA_DATA seems to be an example code of a FM which can allow delta (i.e. manually codes how to fill date/time stamp information). However when I code this and try test in RSA3 it seems to try to populate the delta selection field before calling my function module! I need it to call my function and allow the function to specifiy the date criteria.
Can anyone help with an example of how this should best be done ?
Or can it only be done in a pseudo form using 'RSAX_BIW_GET_DATA_SIMPLE' example FM.
Note: I have setup the RSO2 datasource to allow delta.
Also - I have spent several hours searching the forum - but please answer with a link if you think it does answer exactly this problem.
Thanks for any help
Martin

Hi again,
Have had a few requests for the code I used - I created a new custom function copied from 'RSAX_BIW_GET_DATA_SIMPLE'. AEDAT has been set as the delta date for this data source in transaction RSO2.
Main sample code is -
1. Code to receive selection criteria and store in internal ranges -
FUNCTION zbw_sodetail_get_detail.
""Global interface:
*"   IMPORTING
*"       VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR
*"       VALUE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE
*"       VALUE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE
*"       VALUE(I_INITFLAG) TYPE SRSC_S_IF_SIMPLE-INITFLAG
*"       VALUE(I_READ_ONLY) TYPE SRSC_S_IF_SIMPLE-READONLY
*"       TABLES
*"              I_T_SELECT TYPE SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL
*"              I_T_FIELDS TYPE SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL
*"              E_T_DATA STRUCTURE ZBW_SODETAIL OPTIONAL
*--- Sales order item create date
   LOOP AT i_t_select INTO l_s_select WHERE fieldnm = 'ERDAT'.
      MOVE-CORRESPONDING l_s_select TO r_erdat.
      APPEND r_erdat.
   ENDLOOP.
*--- Sales order item change date - DELTA only - auto filled before
   this function is called.
   C (Initialise Delta) - Low = blank, High = today - safety limit
   D (Delta) - low = , High =   .       *from roosgendlm
   LOOP AT i_t_select INTO l_s_select WHERE fieldnm = 'AEDAT'.
      MOVE-CORRESPONDING l_s_select TO r_aedat.
      APPEND r_aedat.
   ENDLOOP.
2. Code to use selection criteria to get initial or delta. Note that for delta the delta date field to be used is automatically populated with the date of the last delta run (from table roosgendlm) -
   SELECT VBAK~KNUMV
          VBAPVBELN VBAPPOSNR VBAPMATNR VBAPARKTX VBAP~SPART
          VBAPWERKS VBAPERDAT VBAPAEDAT VBAPNETWR VBAP~WAERK
          VBAPABGRU VBAPZPROMISE VBAP~CUOBJ
          VBEP~EDATU
      INTO CORRESPONDING FIELDS OF TABLE ZBW_SODETAIL_ITAB
      FROM VBAK JOIN VBAP ON VBAKVBELN = VBAPVBELN
                JOIN VBEP ON VBAPVBELN = VBEPVBELN
                         AND VBAPPOSNR = VBEPPOSNR
   WHERE VBAP~VBELN IN R_VBELN        "Order number
     AND VBAP~POSNR IN R_POSNR        "Order item number
     AND VBAP~ERDAT IN R_ERDAT        "Order item date created
    AND ( VBAP~ERDAT IN R_AEDAT OR   "Created date in      Delta range
              VBAP~AEDAT IN R_AEDAT OR   "Order item change    Delta range
              VBAK~AEDAT IN R_AEDAT ).   "Order header change Delta range
Note that if the data source is called in initial or full extract mode the delta change date (aedat) will automatically be blank.
I have been using this successfully.
I hope this helps
Martin.

0GLACCEXT_T011_HIER error using RSA3

I have a problem when execute RSA3 for data source 0GLACCEXT_T011_HIER
The error information:
Runtime Errors         SAPSQL_ARRAY_INSE
Except.                CX_SY_OPEN_SQL_DB
Short text
    The ABAP/4 Open SQL array insert results in duplicate database records
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLFAGL_FSV" had to be terminated b
    come across a statement that unfortunately cannot be executed.

Hi,
This dump occurs if the storage of original files is not happening in a Content Server, which is recommended by SAP. You can check this easily if you go to transaction DC10 and check if the flag 'Use KPRO' is set for the used document type.
SAP do not recommend storing such larger files in SAP DB. If you try to store any original in the SAP DB, the file will be stored in the table DRAO. That means you are consuming table space memory. For one original we can have maximum of 9999 rows in the table. To store larger originals in SAP DB more than 9999 rows in the table are needed and this is not possible. That's the reason behind this dump. Storing such huge files inthe SAP DB will also affect the performance of the system while accessing the original
Refer the thread
"http://wiki.sdn.sap.com/wiki/display/PLM/SAPSQL_ARRAY_INSERT_DUPRECwhilesaving+original"
Thanks,

"Error when reading ATP delta records"

Hi,
I have created Integration models for Location, Product, ATP Check, ATP Configuration, Stock and Sales Order.
After creating IM's when I tried to run ATP on my Sales Order I'm getting error " "Error when reading ATP delta records".
Can anyone provide me why I'm facing this error.
Thanks in Advance.
Ram

Dear Ram,
For the product/locations you are checking, it appears that ATP objects in the liveCache are missing which normally are created automatically when products and locations are created in APO.
I would advise to recreate all needed products and locations.
In APO, i.e. make again an initial data transfer of the master data from R/3. Previously the existing ones should be deleted to be sure that they will be created again. Then the problem should be solved.
If this does not help please check the the connection and LC settings to LDA and please try to restart the livecache. A potential explanation for the error would be an incorrectly maintained LDA connection to liveCache. Please check this by running transaction /SAPAPO/OM13 and selecting the 'checks' section.
The problem with the LDA connection could be e.g. very simple. If you check the table dbcon, which contains the description of the liveCache connections , if the liveCache names for LCA and LDA are different you should ensure, that the connections LCA and LDA are setup for the same liveCache (con_env in dbcon).
I hope this helps.
Regards,
TIbor

ALE change Pointers for delta load

The master data datasource is 0CRM_BPSALESCL_ATTR, which is in my source system use change pointers for delta loading. When I use delta loading, the error is "ALE change pointers are not set up correctly". I went to the source system, and use BD61 to activate change pointers. But it does not work. Then I created new Business partners to make changes. I can find these new records in table CDHDR and CDPOS, but there is no records found in table BDCP. And my delta loading still got the error as "ALE change pointers are not set up correctly."
Can anybody give me advice?
Thanks,
Wenjie

Hi, Ron,
Thanks for your reply. I already assign points to you.
I relicated the datasource, and re-active the transfer structure, but it still doesn't work. My one more question is that do I run BD61 on BI system or on source system? I did on source system only. And is there any more setting need to be done on source system? Because my error message said setting on source system is wrong.
Thank you very much.
wenjie

Error in RSA3 for Delta

Similar Messages

Maybe you are looking for