RSA3 no possible

My using standard 2LIS extractor to load the PO Item data into BW.
I have peformed the Setup Table, and loaded the data into BW.
Created the InfoPack to pull in Delta, everything seem to be OK.
Now, for some reason, I need to test and see some PO Item data.
So I go the RSA3 to pull the PO, but it say no record. Why?
Is it because of 2LIS extractor that I can pull and test the extractor in RSA3?
I have no problem with other extractor. Then how can I test and see the data in RSA3 for the 2LIS extractor. please advice.

Hi Lynn,
Are you saying that if I enter the PO that have been loaded into Setup table before, I should be able to pull some record out from RSA3 now?
Can you share with me the correct process for 2LIS?
--> Yes, After filling setup tables you can see/test data in RSA with FULL extraction mode, not with delta.
With 'Delta' mode possible, if data available in Delta Queue(RSA7).
7) If for some reason, can I delete and perform setup table again?
--> If setup tables empty, you can see any data at RSA3 while extracting in FULL mode, as datasouce pulls data from Setup tables in full mode.
8) can I perform full-load again of this setup table? Any duplication?
--> It depends. If you are loading to CUBE(means in addition), chances of duplication if same data loaded again.
9) then can I perform init-delta?
--> After Full load, initialize WITH OUT data transfer and continue deltas.
Hope it Helps
Srini

Similar Messages

Enhanced 0MATERIAL_ATTR-Extractor: Data in R/3-RSA3 but not in BW-PSA

Hi,
we enhanced our 0MATERIAL_ATTR- DataSource with a "new" Z-field.
I checkt the DataSource with RSA3 and everything seemed to be fine (right data in Z-Field).
I loaded one record to BW and this new Z-Field is empty (I expected data!).
I allready:
- activated everything on BW
- deleted Source System Assignment and assigned it new
- Replicated the Data Source (twice)
- checked Transfer Rules
- checked the assignment of the z-field (Type is Ok, it is assigned)
- searced with google and in this forum.
Monitor shows green light on DataLoading (no errors)
ST22 shows no shortdump (BW and R/3)
System BW 3.5
Why can i see data on RSA3 and BW can´t load values for this new Z-Field?
Thanks in advance!
Greetings
Daniel
Btw: Yes, i assign points!

Hi,
Full Load: It was a full load for about 100 Materials. I cant start a full load without restriction, there are to many data...
To delete all MD: This is not possible!
BW 3.5.
I'll try to delete DS and rereplicate ist. ...
thanks.

Fields missing from Data Source but displayed in RSA3

Hello Experts
I have an issue while finding for a field in the data source. As I am looking for some fields : MABST, MINBE, EISBE on BW Side but not found. When I llok the same fields in ECC Side in the table RSOSFieldmap, then I get these fields in 0MAT_PLANT_ATTR Data Source. In the same time , the fields are not available in the Data source on BW Side as well as on ECC Side(while goin thru RSA6). Also when I execute the RSA3 for the data source, I am getting the data in the Missing Fields. How it can be possible? Also plz let me know how can I make these fields available in Data Source.
I replicate the data source, also i looked for the hidden fields, but still not succeed.
Thanks in advance
Neha

Hello,
TO unhide the field,
Just Goto T.code RSO2 > press change button.> unhide the filds and --> Generate the Datasource
or
Goto RSA6 --> select the Datasource and --> press change button (pencil icon) --> unhide the filed --> Save and Generate the Datasource.
Try the above two option and check if it is working.
also go thru the below post
BI : Hidden field Datasource
Hope this helps,
Sri...

RSA3 data and PSA data not matching

Hello All,
I am in BI7.0 and trying to Load FI_GL data usng 0FI_GL_4 DS from ECC6. I was able to install, activate all necessary standard objects that are involved. I have executed data Load from Infopackage by doing Init. with data Transfer..which went okay and now i am data upto PSA Level with everything green status. But when I noticed that in PSA Maintenance screen its showing whole lot more data..it shows 103 Datapackages transferred and lot of data records in each packages.
In R3 side (RSA3) shows only 831 records. IN BI7 , monitor screen shows more then 9 million records recieved.
Could anyone tell me why this happened? Is it possible that this particular PSA already had data on it? if so How can i find and delete previous records from this PSA? please suggest...
thanks
dk

Hello,
1)The error comes if the data is wrong in the DSO.
Something like before and after image are missing for a record and thats why change log is having some issues.
you can check the data between new tables and PSA and see if its matching or not.
Try to delete all the data from the PSA and the DSO.do proper mappings again especially in the keys of the DSO and then reload it.
try to load it for a small a amount like one company code and one fiscal period.check in PSA if its matching or not from RSA3.
2)If the data is getting loaded then there should not be a any problem with the data source.DTP could be an issue.the program is to activate the data source in BI 7 system and if the data source is already activated then you dont need this again.
3)Rule proposal can be generated if the fields are same and have same technical name.in your case the field name are different since its datasource and DSO mappings and therefore you will have to do mappings manually.
4)you mean RSA3??
RSA3 displays the data from tables only in case of full mode.Also,try to do full loads till the PSA and then check for the same in RSA3 in full mode.keep the package size and number of calls maximum so that it will show you correct number of records extracted.
RSA3 is an extractor checker and can be used for verify small amount of data,dont use it for verifying the datasource for all the drecords.
use underlying tables if you want.
if init is done properly then the data will be correct and you should verify it with the tables and not RSA3.
Regards
Ajeet

Records not matching in RSA3 and my ODS(Urgent)

Hi All,
I am aware of that data in the ODS will be aggreagated in the ODS accordingly to key fields by which the records loaded in the ODS will be lesser,
My request is, Plz walk me through the best possible way in step wise to compare the records in RSA3 with my ODS ,
The scenario is like that i am getting data from ODS1 and ODS2 and the data is uploaded and consolidated into ODS3 from the above two ODS"s 1&2,
Thanks in advance,
With Regards,
Ram

Hi Ram,
There are several places where source data get modified before landing in ODS.
Well please check out every place, for possible modification of data based on Code, routine, selections, master data lookup etc.
To start with u can take data for sample selections and see how it is getting modified.
Data normally get aggregated based on Key's od ODS so, as you better aware about key of ODS, u can better understand how aggregation is taking place.
This process of Data integration will give idea of how data is getting clubbed in BW.
Hope this will help u to certain extent.

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

Is SAP BI reporting is possible in ECC 6.0 with same client

Hi all,
                         My requirement is, we need to design SAP BI data flow in ECC 6.0 with same client only. Now I am designing the BI data models as per the requirement of SD sales reports in ECC 6.0.For this, when i was extracting the data from SD datasource(2lis_11_vahdr) in RSA3 its showing 0 records,actually as per VA01 some records are available but its not showing in the RSA3.
                          My doubt is , is it possible to extract the data from ECC 6.0 and load the data to the datatargets and get the SAP BI reports in ECC6.0 with the same client.
                          Please suggest as soon as possible.
Thanks

It is possible to load the data from the same client. It all depends on the source system and the client which has been connected in the RFC connection.
Let me know if this helps.
Regards,
Avinash

Data source activated in RSA5 but error in RSA3

Hi,
I have activated data source 0CRM_OPPT_H in transaction RSA5 in our CRM system and can view this in RSA6. However when I run the extractor checker RSA3, the system generates error ( "Errors occurred during the extraction Message no. RJ012").
Upon debugging I found that this is caused by not having entry in table SMOXHEAD_S for this data source.
Also when I go to transaction BWA1 I am not able to display this data source. Other master data sources that I activated earlier are working fine. Its the transaction data source 0CRM_OPPT_H or 0CRM_OPPT_I that are having issue.
Please let me know any other steps that I may not be doing after activating the Business content data source in CRM system using transaction RSA5.
Thanks
Arunava

Bhanu,
Thanks again for your super fast reply. This really solved my issue.
However for may days I have been trying to understand this BWA transaction ( BWA1 and BWA5) and figured out some fact( Like BWA5 puts the same entry of smxhead table to snmxhead_s table to make the whole thing work, Also we can extend the mapping in the BWA1 to include additional custom object with out the badi coding( is it possible?) .
But this area still is a mystery and I would like to have a comprehensive article on this adapter layer and BDOC relationship. Is this possible for you to help here.
I would really really appreciate.
Thanks
Arunava

Error while extracting data from datasource 0GLACCEXT_T011_HIER in RSA3

Hi Experts,
While trying to extract the data for the datasource 0GLACCEXT_T011_HIER in RSA3, am getting the below Dump.
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
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 because it has
    come across a statement that unfortunately cannot be executed.
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 "FSV_TEXTS_CONVERT" "(FORM)", 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:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
    situation, processing does not terminate, but SY-SUBRC is set to 4.)
Kindly help me out in resolving this error.

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,

0PU_IS_PS_31 add selection field - possible?

Hello all
I have enhanced my extractor 0PU_IS_PS_31 (Funds Management) with a field and have activated the flag "Selection" for it in the data source maintenance. When I now restrict this field to a certain value in my infopackage it does not work. Means, the data is not restricted to my value for this field. I always receive all records.
I have checked the FM "FM_BW_ACTUAL_OI_LINE_ITEMS_IS" behind the extractor and it seems that the possible fields for "selection" are hard coded.
Is there any possibility to get this working?
Thanks for your help in advance!
Regards,
Bernd
Some additional infos about the Extractor:
Name: 0PU_IS_PS_31
Type: TRAN
Delta: AIMD
Exmethod: F1
Extractor: FM_BW_ACTUAL_OI_LINE_ITEMS_IS
Extractstructure: IFMBWACTOPIT_ISPS

Hello Prashanth and Raman
the field is populated correctly using RSA3. This is working. But when I set a filter for the field its not filtered. Below you find the code of FILL_RANGES procedure. As you can see, the selection fields seems to be hard coded. Do you see any possibility to enable filtering (DS copy, but is it possible with delta type AIMD?)?
Thanks for your help guys!!
Regards,
Bernd
*&      Form FILL_RANGES_CALI
*& Fill selection criteria of commitment actual line items into ranges
FORM fill_ranges_cali TABLES u_t_select TYPE sbiwa_t_select.
* "/ these fields don't exist in database tables
RANGES: l_r_actdetl FOR ifmbwact_isps-actdetl.
LOOP AT u_t_select.
*     "/ fill selection criteria to ranges
    CASE u_t_select-fieldnm.
      WHEN 'FIKRS' OR 'RFIKRS' OR 'FM_AREA'.
        MOVE-CORRESPONDING u_t_select TO g_r_fikrs.
        APPEND g_r_fikrs.
      WHEN 'FISCPER'.
        MOVE-CORRESPONDING u_t_select TO g_r_fiscper.
        APPEND g_r_fiscper.
        g_r_gjahr-sign   = u_t_select-sign.
        g_r_gjahr-option = u_t_select-option.
        g_r_gjahr-low    = u_t_select-low(4).
        g_r_gjahr-high   = u_t_select-high(4).
        COLLECT g_r_gjahr.
        g_r_perio-sign   = u_t_select-sign.
        g_r_perio-option = u_t_select-option.
        g_r_perio-low    = u_t_select-low+4(3).
        g_r_perio-high   = u_t_select-high+4(3).
        COLLECT g_r_perio.
      WHEN 'FISCYEAR'.
        MOVE-CORRESPONDING u_t_select TO g_r_gjahr.
        APPEND g_r_gjahr.
      WHEN 'FONDS' OR 'RFONDS'.
        MOVE-CORRESPONDING u_t_select TO g_r_fonds.
        APPEND g_r_fonds.
      WHEN 'FISTL' OR 'RFISTL'.
        MOVE-CORRESPONDING u_t_select TO g_r_fistl.
        APPEND g_r_fistl.
      WHEN 'FIPEX' OR 'RFIPEX'.
        MOVE-CORRESPONDING u_t_select TO g_r_fipex.
        APPEND g_r_fipex.
      WHEN 'FAREA' OR 'RFAREA'.
        MOVE-CORRESPONDING u_t_select TO g_r_farea.
        APPEND g_r_farea.
      WHEN 'ACTDETL'.
        MOVE-CORRESPONDING u_t_select TO l_r_actdetl.
        APPEND l_r_actdetl.
      WHEN 'ZHLDT'.
        MOVE-CORRESPONDING u_t_select TO g_r_zhldt.
        APPEND g_r_zhldt.
* Note 993252
      WHEN 'MEASURE'.
        MOVE-CORRESPONDING u_t_select TO l_r_actdetl.
        APPEND l_r_actdetl.
      WHEN 'GRANT_NBR'.
        MOVE-CORRESPONDING u_t_select TO g_r_zhldt.
        APPEND g_r_zhldt.
    ENDCASE.
ENDLOOP.
* "/ fill WRTTP range from ACTDETL (for commitments and actual)
IF NOT l_r_actdetl[] IS INITIAL.
    PERFORM fill_r_rwrttp TABLES l_r_actdetl
                                 g_r_rwrttp.
ENDIF.
ENDFORM.                    " FILL_RANGES_CALI

Query related to RSA3 transaction

Hi Guys ,
I have query related to RSA3 transaction screen in that you can see in
settings
Data Records / Calls = 100
Display Extr. Calls = 10 by default .
can this value can be made to 1000 and 1000 as a default value as soon as screen get displayed without manually changed .
can we creat any variant for this ,will it be possible .
i need some suggestion related to this .
valuble answers will be surly rewarded .
Thanks ,
Vinay .

Do any one have any suggestion how to solve the query

Extraction in debug mode without RSA3

Hi,
does anyone know, if there is a way to run an extraction in debug mode on the R/3 side without using RSA3 or RSA7? It has to be a real delta extraction triggered by an InfoPackage in BW.
I've also tried the "simulate update" function in the monitor (right-click on Data Package), but that only simulates/ debugs the BW-BW transfer.
Thanks in advance!
Gerrit

Hi Gerrit,
Your requirement is only feasible if your extarctor is based on a function module. In such a case you can set a breakpoint in the function module and when you execute the infopackage the debugger will halt at the breakpoint.
I dont think it is possible for datasource based on table/view.
Bye
Dinesh

Short Dump in Prod system in RSA3 for Datasource 2LIS_18_I0NOTIF...Help Pls

Dear Guru's
In our porod System in Tcode RSA3 when i give Dsource 2LIS_18_I0NOTIF and click on Extract i get Follwing Dump
I searched for the note but i did not found any thing proper
Here r Dump Details:-------
Runtime Error          CONNE_IMPORT_WRONG_COMP_TYPE
Exception              CX_SY_IMPORT_MISMATCH_ERROR
       Occurred on     13.08.2008 at   14:21:57
Error when attempting to IMPORT object "MC18I00NTF_TAB".
What happened?
Error in ABAP application program.
The current ABAP program "SAPLMCEX" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
When attempting to import data, it was discovered that the data
type of the stored data was not the same as that specified in the
program.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_E
was neither
caught nor passed along using a RAISING clause, in the procedure
"MCEX_BW_LO_API" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
When importing the object "MC18I00NTF_TAB", the component no. 2 in the
dataset has a different type from the corresponding component
of the target object in the program "SAPLMCEX".
The data type is "D" in the dataset, but "F" in the program.
How to correct the error
The exception must either be prevented, caught within the procedure
"MCEX_BW_LO_API"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Try to find out why the type of the object is different.
There are several possible reasons:
|
--- In the ABAP Dictionary, the type of the imported
|   field has changed. Make sure that the type of the imported
|   field matches the length of the Dictionary field.
||   If the data could not be restored from another source, this data
|   must be read with the "old" structure, then converted and exported
back with the new structure, so that future IMPORTs always work
with the new structure.
A new program version is active, and it no longer matches the
dataset. Try to solve the error by generating the program "SAPLMCEX" again
as follows:
In the SAP System, choose the transaction SE38. Enter the program
name "SAPLMCEX". Then choose the "Activate" function.
Can any one please kindly help....
Thanks

Hi,
so did you change anything at your datasource? Before transporting to prod, you need to delete the setup tables and then you need to run a delta to pick the latest delta records, then transport, replicate and activate the comm-structure. That will not effect your delta in prod. But again, for me the dump looks like a mismatch between the extract structure and the setup tables. You might have changed something after the setup tables have been filled. And additionally usually rsa3 is doing a full and so pulling the data out of the setup tables.
regards
Siggi

Short Dump Error when we check the Data Source in RSA3

Hi. Experts.
                   We are using Data Source 2Lis_13_VDITM and when we try to check in RSA3
for recorts it is going short dump. I am just providing the error information.
              An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', 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:
When importing the object "MC13VD0ITM_TAB", the component no. 96 in the dataset has a different type from the corresponding component of the target object in the program "SAPLMCEX".
                    The data type is "N" in the dataset, but "X" in the program.
        Since I don't have much knowledge in ABAP, Please help me out regarding this issue. Suggest me possible solution and let me know if you need any further information.

Hi,
Try adding a TRY CATCH block in the extractor function module to catch the exception.
For the type mismatch you will have to make sure the variables are of same type or they can be type converted.
Use the debug mode of RSA3 to find what data is being exchanged.
You will need to change your extractor to avoid the dump.. or ensure that the value being passed to that object is correctly being passed(correct format)
Cheers
Kiran

Extraction RSA3 timed out

Hi All
When i am doing extraction in rsa3 ,giving me time out error.With some selection in selection screen i am getting results,without any inputs to selection screen i am getting this error.Is there any way to solve it or runnung the extractor code in background job is possible?.This is standard extractor
Thanks
Vamsi

There is something with the computer or browser that is triggering this. I have tested the website now and found it still not problematic. Please try using a different browser than what you are using now. Also you will want to check to make sure there is no software running that is regualrly deleting the temporary internet files and cookies.
If that is still not working, you may need to run your browser in compatibility mode. For Internet Explorer, you do it by Please go into the"Tools" menu and click to turn on "compatibility view". It should allow you to sort after doing that. If you do not wish to enable compatibility view every time you want to sort, Go into compatibility view settings and add the site www.verizon.com to the list.
Anthony_VZ
**If someones post has helped you, please acknowledge their assistance by clicking the red thumbs up button to give them Kudos. If you are the original poster and any response gave you your answer, please mark the post that had the answer as the solution**
Notice: Content posted by Verizon employees is meant to be informational and does not supersede or change the Verizon Forums User Guidelines or Terms or Service, or your Customer Agreement Terms and Conditions or plan

RSA3 no possible

Similar Messages

Maybe you are looking for