ERROR while sceduling infopackage BI7.0

hi experts
I am loading flatfile(CSV) data to Datasource by infopackage(BI7.0)....fields are SMID,PID,QTY,SALES,PROFIT......in preview tab of datasource....I am unable to see data...
it shows error:
Error 'Overflow converting from '1000.00'' while assigning character to application structure.
my sales keyfigure values are like 1000.00,2000.00,......
even if I try to load with figures like 1000,2000.....I am getting same error.....
what can be the mistake I did....
thanks for your inputs....
NR

I checked the datatype and its CURR(fixed) and gave decimal places as 2.....
so donot know where I failed....
I used same format before(one week back)...it worked.....

Similar Messages

Error while creating INFOPACKAGE to load transaction data

Hi,
I am getting the following error while creating infopackage:
"Error in Conversion exit CONVERSION_EXIT_CUNIT_INPUT"
I am getting this error when I click on the Start button under the schedule tab in the screen Administrator Workbench: Modelling.
I clicked on Monitor icon to view the diagnosis. The diagnosis is mentioned below:
the screen is Performance Assistant Window and the diagnosis message appears in italics.
Message No RSAR137
DIAGNOSIS
An error occurred in record 1 during execution of conversion exit CONVERSION_EXIT_CUNIT_INPUT for field UNIT.
Procedure
Check that the record where error occurred has the correct format and correct it accordingly. 
Please note that I have succesfully created update rules as I didn't get any error.
Also I would like some one to explain me clearly the differences between transfer rules and update rules with a clear explanation please.
Please help me.
Thank you.
Tristan.

Hello Tristan,
I was used to get the same kind of problems before.
I got the problem with the data source type-Flat File (.csv)
One solution that I have done:
1) checked the particular record in which the error message refer to
2) tested the particular unit from the transaction se37
 Function Module = CONVERSION_EXIT_CUNIT_INPUT
 Press F8 in order to execute
 This would be help a bit
3) corrected data from the flat file
 another alternative solution was by:
 handling the data using routine in the transfer rules
For my case, before executing the InfoPackage, data from flat file could be previewed. At this point, I could check which records caused the problems.
I'm not sure about your case whether data came from which type of data source.
That's all I could share for now.
-WJ-

Error While sending infopackages from OLTP to BI/urgent

Hi BW friends
im workin on production support and im new to it.while
running infopackage X ,it is throwing a error
error:While sending infopackages from OLTP to BI/urgent
In status tab it shows traingular yellow colour
and diagnosis says that No idocs could be sent to bi using rfc.
so if u know please reply me
Thank you
Amarnath k

while loading data into the target we got this message and the solution is do manual update for that.

Error While activating 0Material(BI7)

Dear Gurus,
I am trying to Activate 0Material Infoobject after deleting a Navigation attribute(Classification characteristics) ,the system throws a error " Error while activating Type Info object".And when i navigated to the Detailed error message it says " error : Internal Activation(info object) - error while converting master data tables .Can anyone help me out with this.
manythanks
arun

Dear gurus,
We posted the error message to SAP and they have replied " while we deleted the attributes from the Info object(0material) it broke the D-Version of the Object and so to Transport the Info object from another Working system to the Problem(Dev)system ,Install and then activate".
1). Does it mean we can install them object in PRODUCTION Server and then transport to the Development.???
2). Now i tried installing 0Material in RSORBCT in Produciton,but gets a message "Cant make any changes in the repository-changes in this client prohibited". Guys could u help us with this??
manythanks
arun

Error while transporting Openhub (BI7)

Hi Gurus,
I am getting an error while transporting the open hub. In the dev system it worked perfectly but when i transport it to quality, it is showing the following error.
"Unable to activate table /BIC/OHZxxxxxx ."
When i checked the table in quality it says that /BIC?OHZxxxxx-0UNIT ( Reference field ) does not exists. But 0UNIT is there in the DSO on which i developed the openhub and the infoobject 0unit is also active in quality system.
Why this error is happening?
Regards,
Raghavendra.

Hi Raghavendra,
There are chances of missing some objects in transport request wile assigning objects to request...please check the objects list and open hub structure.
and also plsease check the 0Unit field status in Quality system.if it is in modified status means make it it active ststus.
Please create one more transport request and validate the tr objects...
Best Regards,
maruthi

Error while Scheduling InfoPackage

When i am scheduling a full load in the infopackage to load data to PSA but am getting an DBIF_RSQL_INVALID_REQUEST error. The desciption is "An invalid request was made to the SAP database interface in a statement in which the table "EDID4 " was accessed".
Can anyone help me overcome this and resolve the issue, please.
Thanks
Neha

check OSS Note 89384 if it is relevant to ur issue.

Error while executing infopackage of 2lis_03_bx

Hi,
I am using a multiprovider which gets data from 3 cubes OIC_C03 ,ORT_C37 and my customized ZRT_C37.
When i am executing infopackage 2LIS_03_BX(Stock Initialization) which updates data into three specified cubes , its giving me below specified error
"Cannot select cube OIC_C03 for full data from DataSource 2LIS_03_BX"
I have tried with both updates 1. Full update
2. Generate Initial Status
I have also deleted and fill setup tables for inventory.
If i remove 0IC_C03 from datatargets den i am getting error for other cubes
"Cannot select cube ORT_C37 for full data from DataSource 2LIS_03_BX"
With regards,
Montz

I am assuming that you are using BW 3.x
The error suggest your Cube has not bee properly connected to datasource. check that all intermediate things like update rule, infousource etc (between datasource and the cube) are in place and activated. Also check that cube is activated.

Error while running InfoPackage - Goods Movement from Inventory Management

Hi,
We first encountered an error No storage space available for extending table IT_ 3, Error 7 when sending an IDoc, Errors in source system upon running the infopackage (inside a process chain). The step was accidentally repeated and now the error log shows that the delta request is incorrect in the monitor and that a repeat needs to be requested.
What should be our corrective steps for this kind of problem? Would a selective deletion and repair suffice?
Kindly advice. Thanks.

Yes, I think it's safe. But there is no guarantee that the process will not fail again. You'd better contact basis guys for space increasing.
Also you can try to clean the system by yourself:
1. Delete PSA that you don't need.
2. Delete old system logs (SLG2 tcode).
Though, it's not a fact that additional room will appear in that spaces that your PC uses.
Best regards,
Eugene

Error while opening infopackage

Hi,
I get a short dump when i open infopackage for 2LIS_02_SCLdelta/
MESSAGE_TYPE_X.
Information on where terminated
    Termination occurred in the ABAP program "SAPLRSS1" - in
     "RSM1_CHECK_FOR_DELTAUPD".
    The main program was "RSAWBN_START ".
    In the source code you have the termination point in line 1530
    of the (Include) program "LRSS1F11".
I am not understanding this dumo and that to i am not starting the load but just opening infopackage and getting this dump. Pl help me in resolving this.
Thanks & Regards,
Vijaya

Hi,
We need to make some changes in delta settings.
See this SAP Note providing exact solution. Need to delete some table entries in PRD and BW DEV BOX.
Refer Note # 852443.
Summary
Symptom
If a MESSAGE_TYPE_X runtime error occurs in the LRSSMU36 include program in the SAPLRSSM ABAP program of the RSSM_OLTPSOURCE_SELECTIONS function module, proceed as described in the solution below.
This dump occurs if you try to open an InfoPackage for a DataSource/source system combination for which an initialization terminated incorrectly and a new INIT with overlapping selections was executed without the delta-administration being cleaned up.
The dump can also occur if you import a system copy/backup into only one of the two BW/OLTP systems without first deleting all delta queues for this BW/OLTP combination because the delta administration is always inconsistent. In such cases, contact the SAP consulting department.
A similar dump occurs in
perform "RSM1_CHECK_FOR_DELTAUPD in the LRSS1F11 include if the source system does not recognize any more inits (the roosprmsc and roosprmsf tables are empty) but if there are still entries in the RSSDLINIT/RSSDLINITSEL tables in the BW system.
This is the same as the problem described in Notes 424848 and 591382.
Other terms
Dump, include LRSSMU36, RSSM_OLTPSOURCE_SELECTIONS, MESSAGE_TYPE_X,
Init, delta queue, system copy, backup, initialization, InfoPackage,
RSM1_CHECK_FOR_DELTAUPD, LRSSMU36, LRSS1F11,
RSSDLINIT, RSSDLINITSEL, RSSM_OLTP_INIT_DELTA_UPDATE.
Reason and Prerequisites This problem is caused by a program error.
Solution
You can implement this correction only for load times from an OLTP system because transaction RSA7 is used for the delta administration/deletion.
For a DataMart, you may have to delete using transaction SE16 or a native SQL.
1. The entries for the initialization in the BW system are contained in the RSSDLINIT table for the DataSource/source system combination. Compare these with the entries in the ROOSPRMSC table in the OLTP system.
2. If there are NO entries in the RSSDLINIT table in BW, use transaction RSA7 to delete the delta queue for this DataSource/BW application combination in the source system (OLTP). For a DataMart source system, manually delete the entries in the ROOSPRMSC and ROOSPRMSF tables for your DataSource using transaction SE16 or a native SQL on the database. A DataMart can be identified by the DataSource that starts with '8', and by the fact that you CANNOT find it in RSA7 of the source system.
3. If the RSSDLINIT table in the BW system already contains entries, check the requests listed there in the RNR column in the monitor (transaction RSRQ). Compare these entries with the entries in the ROOSPRMSF and ROOSPRMSC tables with the INITRNR field. If, in the ROOSPRMSF and ROOSPRMSC tables for your DataSource source system combination, there are more entries with different INITRNR numbers, use transaction RSA7 in an OLTP source system to delete all entries and then use the RSSM_OLTP_INIT_DELTA_UPDATE report mentioned in the next section. For a DataMart source system, delete the entries that you cannot find in the RSSDLINIT table using the procedure described above.
4. Read also Notes 591382 and 424848. The errors described there also occur if you delete entries using transaction RSA7 in the source system but there is no RFC connection to the BW system. In the source system, there are no more entries in the ROOSPRMSC and ROOSPRMSF tables, but in the BW system, there are still entries in the RSSDLINIT and RSSDLINITSEL tables. Execute the RSSM_OLTP_INIT_DELTA_UPDATE report and then delete all init selections in the 'Scheduler/Init selections in the source system' menu in the InfoPackage.
5. When you have completed this procedure, you should be able to create a new InfoPackage or open an InfoPackage.
You can then open the InfoPackage again.
Check that there are no more entries in the
'Scheduler'/'Initialization options for source system' menu
If you do find some entries, delete them.
You can then start a new initialization.
If, despite the first incorrect init, you want to be able to create a second init with overlapping selections, which means that this dump will then occur, enter a detailed description of your procedure in a customer message and send it to Development. SAP has never been able to reproduce this behavior, therefore, a great deal of testing and the option to debug in your system would be required.
OR
Note 405943 - Calling an InfoPackage in BW causes short dump
Symptom
Calling an InfoPackage in BW causes a short dump (MESSAGE_TYPE_X).
Other terms
OLTP, DataSource, extractor, data extraction, delta, MESSAGE_TYPE_X
Reason and Prerequisites
The following conditions must be met:
1. The DataSource that is extracted using this InfoPackage must be a delta-capable transaction data DataSource or a master data or text DataSource if there is flexible updating of InfoObjects in BW. Additional prerequisites are listed below (there are several cases in which the dump may occur):
2
Case 1
3. There are several initialization selections for this DataSource.
4. A subset of the initialization selections was deleted before the dump.(Scheduler -> Menu scheduler -> Initialization selections source system)
5. The RSSDLINIT table in BW and the ROOSPRMSC table in the source system display different entries concerning the DataSource in question. More precisely: The RSSDLINIT table contains entries for the DataSource that have no corresponding entry in the ROOSPRSMC.
Case 2.
Alternatively, the problem may occur after a BW 12B upgrade.
Case 3.
Alternatively, the problem may occur if you have copied your OLTP system.
Case 4.
Alternatively, the problem may occur if you have installed a back-up in the OLTP system but not in BW.
Case 5.
Alternatively, the problem may occur if you load master data with flexible updating as a delta requests (0MATERIAL_ATTR, 0VENDOR_ATTR, 0CUSTOMER_ATTR and others).
Solution
You can apply note 0424848 if you are sure that this behavior only occurred because an upgrade was carried out 1.2B to 2.0B or 2.1C (Case 2) and, therefore, the roosprmsc and roosprmsf tables do not contain any entries for their Datasource/source system combination.This will copy the entries from BW into the source system and fill the roosprmsc and roosprmsf tables.
You can also use this solution for case 5 (as a workaround; the final solution is currently in progress).
IMPORTANT: You must only use this program in case 2 or case 5. We recommend that you do not use it in any other case as it may lead to data inconsistencies in BW.
If the problem is caused by individually deleted Delta Inits (Case 1), then implement the following steps according to your source system release:
1. As of 4.0B
Currently the only solution is reinitializing the delta update.To eliminate all inconsistencies, call the transaction RSA7 in your source system and delete the corresponding DataSource's delta queue for the relevant BW system.After that you must request the data again in the DeltaInit mode from BW.
If you no longer have any entries in the delta queue (RSA7) in OLTP, the inconsistencies must be eliminated by SAP BW support service.
The next PI patch contains a correction that no longer deletes all initialization selections in the source system when the deletion of a subset is called in the scheduler.
Alternatively you can import the correction instructions provided in this note into the OLTP.
2. 3.1H and 3.1I
The only way of eliminating the inconsistency is to reinitialize the delta update.In the scheduler menu, delete all the remaining initialization selections and reload data in 'Initialization of delta process' mode with or without the 'Simulation of delta initialization' flag.
If you can no longer access the scheduler because of a dump displaying this problem, ask your system consultant to implement note 419923.
If the problem is caused by a system copy (Case 3):
Ask your system consultant or SAP Support service to clean up the BW delta tables (the consultant can find the names of the tables in Note 419923 mentioned above) because you will have to reinitialize the delta again in all cases.
OR
Execute the FM "RSS1_QUEUE_DELETED_IN_OLTP", by giving OLTP source & logical system.
In RSSDLINIT table in BI entry for this datasourceROOSPRMSC table in OLTP.
Error - RSM1_CHECK_FOR_DELTAUPD
Short Dump when opening Info Package
Delete Initialization request
Hope this helps.
Thanks,
JituK

Error while creating infopackage

Hi,
i am using BI 710. I am trying to create infopackage for 0COMP_CODE master data object and i am getting following error messeges:
Data target 'ZCOMP_COD ' removed from list of loadable targets; not loadable     RSM     33
Data target 'ZCOMP_COD ' is not active or is incorrect; no loading allowed     RSM     36
Data target 'ZCOMP_COD$T ' removed from list of loadable targets; not loadable     RSM     33
Data target 'ZCOMP_COD$T ' is not active or is incorrect; no loading allowed     RSM
     36
please help with this.
Thanks & Regards,
Vijaya

Hi Vijaya,
the trigger for the popup will be described in the attached note 925304.
side effect of the note is, that the pop-up will be shown for deleted
infoprovider also, which have active updaterules in the system.
Please check table 'RSUPDINFO' for the relevant InfoProvider, if there
any active UpdateRules. With function module (SE37) 'RSAU_UPDR_DELETE'
it is possible to delete them. After that, the popup wouldn´t be
called.
There is also a chance to disable the popup when you access the
infopackage. Please see the note for that alternative.
Eventhough you are getting the above message it will not stop you to schedule the Infopackage. I had this problem 6 months back, I used to get the messages then I deleted them with the Function module.
I hope this will help you.
All the best.
Vijay.

Error while triggering Infopackage

Hi experts,
I am encountering an error when i am scheduling the infopackage.
I m using an Infosource which is connected by two Data sources (Excel).
when i trigger Infopackage1 for DS1 it is excuting correctly.
But When I excute the second Infopackage with Second DS then it is giving an error msg "Fiscal year variant UN is not maintained for calendar year 0710 ".
But in both above DataSources same UN has been used.
plz give me ur valueble suggetions.
thanks in advance
bhaskar

Hi Bhaskar,
Just in case check the record in the excel and check the date format / year for that record . Modify the record and then should be able to load it successfully .
Hope that helps.
Regards
Mr Kapadia
Assigning points is the way to say thanks in SDN.

COnversion Error while executing Infopackage

Hi,
I am trying to load data in a cube thur INfopackage. When I try to preview the data it gives me following error:-
Conversion_EXIT_PERIV6_INPUT1.
ANy suggestions to get rid of it?
Regards

The prob is with the data format of 0CALDAY or any such time char i believe.
For 0CALDAY, the flat file data shud be of the format 'YYYYMMDD' i believe.
Check n let me know.
Regards,
R.Ravi

Date error while scheduling infopackage

Hello Friends
I am facing a pecular problem.
Some time back we had taken a backup from production to quality system. I have loaded the data with the option "initialization without data transfer". It is successful. After that we are loading deltas and in this time it is showing errors such as
1) selection condition replaced by last init selection conditions.
2) incorrect start date 20.09.2004 start time 02:10:00
what am i suppose to do in this case?
Need ur valuable suggestions.
Regards
rohit

Hi
From which data sources are you loading data..I think it is from some copa related time stamp problem..Please bit eloborate on this issue
Thanks
Teja

Error While loading into BW using infoPackage

Hi All,
While following directions posted at the following wiki page https://wiki.sdn.sap.com/wiki/display/BOBJ/ConfiguretheLoadJobinBW%28DS+3.2%29,
we get an error while loading data into BW using infoPackage via Data services 3.2
In SAP BI side Error says :"Error while executing the following command: -sJO return code:220"
On DS side for the RFC server log we get the error" Error while executing the following command -sJOB_SQL_TO_DBI -Ubbu -P;(encrypted password) -A (encryted information) -VMODE=F"
Issue is still open with support as we still cannot excute the job from infopackage. it is succesfully executed from designer, admin console, batch file.
Any insights/help would be appreciated.
Thanks.
Edited by: rana_accn on Jan 26, 2010 6:48 PM

Sure I will.
One thing we have noticed is that in the server_eventlog parameter for the log line "Starting job with command line parameters are different"
When job is executed from DS side parameters -Ct -Cm -Ca -Cj -Cp -S -N -Q -U -P -G -r -T -Locale are used
When job is executed from BW side parameters -Ct -Cm -Ca -Cj -Cp -s -N -Q are used
Also when the job is executed from BW, log files start getting created but then trace and error file show an error that cannot open database - and that points to DSCentral repository.This repository is not even mapped to the job server and the job has been exported from the correct repository as command line execution of the job works perfectly fine.
Thnx
Just an update we were not able to figure out why this happened in the existing environment. One reason given was that somehow the commands which were being executed from BW side were getting corrupted. We had to build a new environment and this is no longer an issue in the new environment, as now all jobs can be executed from BW. Only difference between the 2 environments was we are now on 12.2.1.3 while earlier we were on 12.2.0.0.
Edited by: rana_accn on Mar 23, 2010 10:21 PM
Edited by: rana_accn on Apr 29, 2010 9:46 PM

Error while loading data to ODS in BI7

Getting such following errors when loading data to ODS through DTP(Data Transfer Process) in BI7.
Runtime error while executing rule -> see long text RSTRAN
Record filtered because records with the same key contain errors     RSM2
and many so on...
source system is ok no problem with the connection part.
plz help.

Hi Anup.
Probably your records are not Unique, while you have told the system they should be.
Try to move a discrimination characteristic from data fileds to key fileds.
Or
Try to set the "duplicate reords allowed" setting in your datasource (tab "General Settings" Delivery of Duplicate Data Recs. = Allowed)
Udo

ERROR while sceduling infopackage BI7.0

Similar Messages

Maybe you are looking for