RSYST-CODE-input data too long

we have implemented ESS on EP 7..when we try to naviagte through my workspace and if select any services such as Performance Mangement , Leraning and development it will take us to a screen where prompt us to log for Production system ,,...
Service :WEBGUI
RSYST-CODE-input data too long
if i give necessary acces it will connects to the R/3 ..
is there any coonection based configuration to be check in order to by pass getting this screen..
regards
Buddhike

Hi Lynton,
As mentioned in the thread you listed, it is possible that this error is being caused by using certain characters, such as ü, á, $, &, -. In order to check if any catalog has strange characters, please check in transaction SPRO -> Supplier Relationship Management -> SRM Server -> Master Data -> Define External Web Services. Check in "Web Service ID" if any catalogs contain strange characters.If so, remove them and retest the issue.
Kind Regards,
Conor Harkin

Similar Messages

SP2-0027: Input is too long -error on pl/sql procedure

Hi,
We are on Oracle 11.2.0.2 on Solaris 10. I have a procedure call that errors out with this error:
SP2-0027: Input is too long (> 2499 characters) - line ignored
It is one single procedure but it takes too many long inputs in it. This giant procedure call -with some names changed - is as below - is there a way I can avoid this errro? I will be thankful for inputs on it.
SQL> exec func_j23k_TYPE_ADD( 'coR-EXECUTION-SUCCEEDED-XLS-PDF-HTM-TXT-CSV-XML-FLF','co Reporting','NOT',func_j23k_TYPE_ACTION_ARRAY(func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Find in Report List'),LANG_TEXT_TYPE('en_CA', 'Find in Report List'),LANG_TEXT_TYPE('fr_CA', 'Chercher dans la liste des rapports'),LANG_TEXT_TYPE('es_US', 'Buscar en lista de informes')),'/Reporting/el/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open using Excel'),LANG_TEXT_TYPE('en_CA', 'Open using Excel'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format Excel'),LANG_TEXT_TYPE('es_US', 'Abrir usando Excel')),'/Reporting/el/xls/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open in PDF'),LANG_TEXT_TYPE('en_CA', 'Open in PDF'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format PDF'),LANG_TEXT_TYPE('es_US', 'Abrir en PDF')),'/Reporting/el/pdf/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open in HTML'),LANG_TEXT_TYPE('en_CA', 'Open in HTML'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format HTML'),LANG_TEXT_TYPE('es_US', 'Abrir en HTML')),'/Reporting/el/html/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open in TXT'),LANG_TEXT_TYPE('en_CA', 'Open in TXT'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format TXT'),LANG_TEXT_TYPE('es_US', 'Abrir en TXT')),'/Reporting/el/txt/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open in CSV'),LANG_TEXT_TYPE('en_CA', 'Open in CSV'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format CSV'),LANG_TEXT_TYPE('es_US', 'Abrir en CSV')),'/Reporting/el/csv/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open in XML'),LANG_TEXT_TYPE('en_CA', 'Open in XML'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format XML'),LANG_TEXT_TYPE('es_US', 'Abrir en XML')),'/Reporting/el/xml/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Download Data Extract File'),LANG_TEXT_TYPE('en_CA', 'Download Data Extract File'),LANG_TEXT_TYPE('fr_CA', 'TÃ©lÃ©charger le fichier d''extraction de donnÃ©es'),LANG_TEXT_TYPE('es_US', 'Descargar archivo de extracciÃ³n de datos')),'/Reporting/el/flf/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL)), 'MC');
SP2-0027: Input is too long (> 2499 characters) - line ignoredThanks,
OrauserN

It is an sqlplus error..
Did you try this?
begin
func_j23k_TYPE_ADD( 'coR-EXECUTION-SUCCEEDED-XLS-PDF-HTM-TXT-CSV-XML-FLF',
'co Reporting',
'NOT',
end;http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:4789399600346029472

Using DBMS_REDEFINITION.START_REDEF_TABLE I get SP2-0027: Input is too long

Hello, I am using the DBMS_REDEFINITION.START_REDEF_TABLE to migrate a large table to unicore data types. When I attempt this the list of columns is too long and it generates:
SP2-0027: Input is too long (> 2499 characters) - line ignored
Below is the procedure call. Is there a way to over come this?
EXECUTE DBMS_REDEFINITION.START_REDEF_TABLE( -
'FOCUS',
'PREFERRED_CUSTOMER',
'INT_PREFERRED_CUSTOMER', -
'PREFERRED_CUST_KEY PREFERRED_CUST_KEY,SIGNUP_STORE_KEY SIGNUP_STORE_KEY,SIGNUP_ASSOC_EMPKEY SIGNUP_ASSOC_EMPKEY,PREFERRED_CUST_NUM PREFERRED_CUST_NUM, -
ALT_PREFERRED_CUST_NUM ALT_PREFERRED_CUST_NUM,TAX_EXEMPT_NUMBER TAX_EXEMPT_NUMBER,EMPLOYEE_KEY EMPLOYEE_KEY,SIGNUP_DATE SIGNUP_DATE,ALLOW_CONTACT_IND ALLOW_CONTACT_IND, -
ALLOW_DISTRIB_IND ALLOW_DISTRIB_IND, ALLOW_EMAIL_IND ALLOW_EMAIL_IND, ALLOW_EMAIL_IND_EFF_DATE ALLOW_EMAIL_IND_EFF_DATE, ALLOW_MAIL_IND ALLOW_MAIL_IND, -
ALLOW_MAIL_IND_EFF_DATE ALLOW_MAIL_IND_EFF_DATE, ALLOW_TELEMARKET_IND ALLOW_TELEMARKET_IND, ALLOW_DIRECT_MAIL_IND ALLOW_DIRECT_MAIL_IND, ALLOW_STMT_INSERT_IND ALLOW_STMT_INSERT_IND, -
CUST_SOURCE_CD CUST_SOURCE_CD, NAME_ADDR_SOURCE_CD NAME_ADDR_SOURCE_CD, NAME_ADDR_EFF_DATE NAME_ADDR_EFF_DATE, TO_NCHAR(LAST_NAME) LAST_NAME, TO_NCHAR(FIRST_NAME) FIRST_NAME, -
TO_NCHAR(MIDDLE_INIT) MIDDLE_INIT, TO_NCHAR(NAME_PREFIX) NAME_PREFIX, TO_NCHAR(NAME_SUFFIX) NAME_SUFFIX, TO_NCHAR(ADDRESS1) ADDRESS1, TO_NCHAR(ADDRESS2) ADDRESS2, -
TO_NCHAR(ADDRESS3) ADDRESS3, TO_NCHAR(CITY) CITY, TO_NCHAR(STATE) STATE, COUNTRY COUNTRY, ZIP ZIP, ZIP ZIP, ZIP5 ZIP5, HOME_PHONE HOME_PHONE, AREA_CODE AREA_CODE, -
AREA_CODE_EXCHNG AREA_CODE_EXCHNG, WORK_PHONE WORK_PHONE, DATE_OF_BIRTH DATE_OF_BIRTH, GENDER_CD GENDER_CD, INSTORE_CONTACT_EMPKEY INSTORE_CONTACT_EMPKEY, -
LAST_TRANSACTION_TIME LAST_TRANSACTION_TIME, LAST_TRANS_AMT LAST_TRANS_AMT, LAST_RETAIL_TRANS_TIME LAST_RETAIL_TRANS_TIME, LAST_CATALOG_TRANS_TIME LAST_CATALOG_TRANS_TIME, -
LAST_INTERNET_TRANS_TIME LAST_INTERNET_TRANS_TIME, LIFETIME_AMT LIFETIME_AMT, LIFETIME_RETAIL_AMT LIFETIME_RETAIL_AMT, LIFETIME_CATALOG_AMT LIFETIME_CATALOG_AMT, -
LIFETIME_INTERNET_AMT LIFETIME_INTERNET_AMT, LIFETIME_UNIT_CNT LIFETIME_UNIT_CNT, LIFETIME_RETAIL_UNIT_CNT LIFETIME_RETAIL_UNIT_CNT, LIFETIME_CATALOG_UNIT_CNT LIFETIME_CATALOG_UNIT_CNT, -
LIFETIME_INTERNET_UNIT_CNT LIFETIME_INTERNET_UNIT_CNT, LIFETIME_RETURN_AMT LIFETIME_RETURN_AMT, LIFETIME_RETAIL_RETURN_AMT LIFETIME_RETAIL_RETURN_AMT, -
LIFETIME_CATALOG_RETURN_AMT LIFETIME_CATALOG_RETURN_AMT, LIFETIME_INTERNET_RETURN_AMT LIFETIME_INTERNET_RETURN_AMT, LIFETIME_RETURN_UNIT_CNT LIFETIME_RETURN_UNIT_CNT, -
LIFETIME_RETAIL_RTRN_UNIT_CNT LIFETIME_RETAIL_RTRN_UNIT_CNT, LIFETIME_CATALOG_RTRN_UNIT_CNT LIFETIME_CATALOG_RTRN_UNIT_CNT, LIFETIME_INTERNT_RTRN_UNIT_CNT LIFETIME_INTERNT_RTRN_UNIT_CNT, -
LIFETIME_VISIT_CNT LIFETIME_VISIT_CNT, LIFETIME_RETAIL_VISIT_CNT LIFETIME_RETAIL_VISIT_CNT, LIFETIME_CATALOG_VISIT_CNT LIFETIME_CATALOG_VISIT_CNT, -
LIFETIME_INTERNET_VISIT_CNT LIFETIME_INTERNET_VISIT_CNT, LIFETIME_RTRN_VISIT_CNT LIFETIME_RTRN_VISIT_CNT, LIFETIME_RETAIL_RTRN_VISIT_CNT LIFETIME_RETAIL_RTRN_VISIT_CNT, -
LIFETIME_CATALG_RTRN_VISIT_CNT LIFETIME_CATALG_RTRN_VISIT_CNT, LIFETIME_INTRNT_RTRN_VISIT_CNT LIFETIME_INTRNT_RTRN_VISIT_CNT, LAST_CONTACT_DATE LAST_CONTACT_DATE, -
LAST_CONTACT_TYPE LAST_CONTACT_TYPE, LAST_CATALOG_SENT_DATE LAST_CATALOG_SENT_DATE, LIFETIME_CATALOG_SENT_CNT LIFETIME_CATALOG_SENT_CNT, PRIVATE_CC_ACCT_NUM PRIVATE_CC_ACCT_NUM, -
PRIVATE_CC_FIRST_USE_DATE PRIVATE_CC_FIRST_USE_DATE, PRIVATE_CC_ACCT_BALANCE PRIVATE_CC_ACCT_BALANCE, PRIVATE_CC_LIMIT_AMT PRIVATE_CC_LIMIT_AMT, PRIVATE_CC_LIMIT_SET_DATE PRIVATE_CC_LIMIT_SET_DATE, -
PRIVATE_CC_LIMIT_EXPIRES_DATE PRIVATE_CC_LIMIT_EXPIRES_DATE, PRIVATE_CC_NUM_CARDS_ISSUED PRIVATE_CC_NUM_CARDS_ISSUED, PRIVATE_CC_JC_FIRST_NAME PRIVATE_CC_JC_FIRST_NAME, -
PRIVATE_CC_JC_MIDDLE_INIT PRIVATE_CC_JC_MIDDLE_INIT, PRIVATE_CC_JC_LAST_NAME PRIVATE_CC_JC_LAST_NAME, PRIVATE_CC_APP_STORE_KEY PRIVATE_CC_APP_STORE_KEY, -
ALT_ACCT_NUMBER ALT_ACCT_NUMBER, SOCIAL_SEC SOCIAL_SEC, COMPANY_NAME COMPANY_NAME, BUSINESS_TITLE BUSINESS_TITLE, HOW_DID_YOU_HEAR_CD HOW_DID_YOU_HEAR_CD, -
HOW_DID_YOU_HEAR_EFF_DATE HOW_DID_YOU_HEAR_EFF_DATE, PREFERRED_PROMO_METHOD_CD PREFERRED_PROMO_METHOD_CD, PREF_CUST_STATUS1_CD PREF_CUST_STATUS1_CD, PREF_CUST_STATUS1_EFF_DATE PREF_CUST_STATUS1_EFF_DATE, -
PREF_CUST_STATUS2_CD PREF_CUST_STATUS2_CD, PREF_CUST_STATUS2_EFF_DATE PREF_CUST_STATUS2_EFF_DATE, PREF_CUST_STATUS3_CD PREF_CUST_STATUS3_CD, PREF_CUST_STATUS3_EFF_DATE PREF_CUST_STATUS3_EFF_DATE, -
EMAIL_ADDR EMAIL_ADDR, COUNTRY_CD COUNTRY_CD');--
Thank you,
David

I am not familiar with this. How would you recommend doing this?
David

SP2-0027: Input is too long error during Apex 4.0 installation

I have come across an error while installing Apex 4.0.
The installation reached the point where it gave a SP2-0027 error
...PAGE 72: Workspace Schemas
...PAGE 73: &PRODUCT_NAME. Workspace Creation
...PAGE 74: Page Views By Day Report
...PAGE 75: Page Views by Application and Page
...PAGE 76: Hourly Usage
...PAGE 77: Usage by Application, for selected hour
...PAGE 78: Page Performance Dashboard
...PAGE 79: Database
SP2-0027: Input is too long (> 2499 characters) - line ignored
wwv_flow_api.create_report_region (
ERROR at line 16:
ORA-06550: line 16, column 1:
PLS-00703: multiple instances of named argument in list
ORA-06550: line 16, column 1:
PL/SQL: Statement ignored
Disconnected from Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
Following this, I looked up Apex help, and so checked dba_registry
C:\apex>C:\oraclexe\app\oracle\product\10.2.0\server\BIN\sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Jul 13 15:40:05 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> connect sys as sysdba
Enter password:
Connected.
SQL> SELECT STATUS FROM DBA_REGISTRY
2 WHERE COMP_ID = 'APEX';
STATUS
LOADING
Please help
Edited by: user4477408 on Jul 19, 2010 3:35 PM
Edited by: user4477408 on Jul 26, 2010 11:29 AM

Did you keep any kind of external references to your pages/reports? From what it looks like, one of your report regions exceeds 2500 characters and APEX is having a hard time crunching it. See if you can find that page, then export that page, delete the region, and import the page on it's own later.
Not sure why it would be such a small area, though. I usually don't have any trouble until I hit 32K characters.

SP2-0027: Input is too long ( 2499 characters) - line ignored

Hi All,
I am getting SP2-0027: Input is too long (> 2499 characters) - line ignored error when running a script. It looks like it is a limitation of the buffer size to be 2500 characters. I tried both the command prompt sqlplus and SQL Plus, nothing worked. Is there any other way to avoid that as I have to migrate the whole database which is in insert statement's script form.
BTW I am using Oracle 10g
Thanks

You're going to have to add line feeds to that file to make the line sizes smaller. Hopefully you're on Unix where you can use sed.

XML Input String too long to Test Web Service in App Server

We have a Web Service that accepts an XML input string but when we deploy this web service and try to test it through the Application Server it errors out because the input string is too long. Is there any way around this??
Thanks...

Update:
Now I see that there are in fact two error messages. The second one is the one presented above. But the first one says:
Line: 145
Char: 97
Error: Expected ';'
Code: 0
My question now is to what file it is referring?? Is it to ProjectAccountingPort.js that is automatically created? THen why is it not properly created??
Please, please help me with this! The deadline is in a few days...

Nawk message input record too long

I am running a shell script which uses nawk.
I am processing a huge input file.
I get a message that an input record is too long.
What am I supposed to do to indicate to nawk the max record line length ?
My e-mail is [email protected]
Any info will be appreciated

The 6144 limit can be verified with:
% perl -e 'print "A"x6145, "\n"' | nawk '{ print length($0); }'
nawk: input record `AAAAAAAAAAAAAAAAAAAA...' too long
source line number 1
(it works, when you change the perl print statment to
6144 x "A").
Quick solution could be to use gawk instead of nawk
(/opt/sfw/bin/gawk, if you have the Solaris 8 companion
CD installed).

Error -2147467259. Data too long for column 'X' at row 1.

I am new to SQL and I get this error when I try to add another row into the SQL database whose width is different that the corresponding element on the previous row.
For eg
If I enter the string "test" as the an element in the first row, there is no error. However, if I enter "test1" , it throws the following error. I set the data type as string and size to 0( max length for SQL).
Any help is appreciated.
Thanks
HP

Stringcol sounds like a number, no? Without seeing your table definition it's hard to say, but most likely the error is correct, you're trying to enter e.g. a 5 byte string into an integer field (which is 4 bytes), or similar.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

ORA-12899 : Does it exist an option to truncate automaticly the data too...

Hi,
I work on a migration project : Sybase to Oracle 10g.
There are a lot of request INSERT writed in Sybase with data too long to be insert in a table.
Example :
create table MyTable (txt varchar(10))
insert into MyTable values ('AAAAAAAAAAAAAAAAA');
So, i have lot of error ORA-12899 ...
With Sybase, there isn't error because the data are automaticly truncated.
Does it exist an option with Oracle to have the same behavior ? Without option, i have to add substr in many request.
Any idea ?

Here is another possibility you may want to consider,
1. make the column generously large, enough that you can be sure it accommodates the longest string.
2. load the data
3. once the data is loaded write a simple query that tells you the length of the longest string that got loaded in the column
4. alter the column to be of a more reasonable size considering step 3.
This way, no need to substr everywhere and truncate values that should not have been truncated in the first place. If you do need to end up truncating the values, it will still be easier to do it once the data is loaded in a table than it is to cherrypick statements to modify in script.
HTH,
John.

Input parameter error: "string too long"

Hi,
SAP4Rails and SAPNWRFC run really well now, and I have not experienced a problem for a long, long time.
However, in an RFC I want to use, there is an import parameter (a plain value), which is of the type SYSUUID. The definition of this type says
<Format - Data Type "RAW" - No. characters "16"> and <Output Characteristics - Output Length "32">. Locally it works with 32 characters of input, but if I try to call the RFC through SAP4Rails, the error "RfcSetByte string too long" occurrs. Any idea, why this could be?
Thanks a lot in advance,
Bernd

This maybe a bug - if you can compile your own sapnwrfc can you try finding the following code:
    if (RSTRING(value)->len > max)
        rb_raise(rb_eRuntimeError, "RfcSetByte string too long: %sn", StringValueCStr(value));
and changing it to:
code]
    if (RSTRING(value)->len > max*2)
        rb_raise(rb_eRuntimeError, "RfcSetByte string too long: %s\n", StringValueCStr(value));
[/code]
and let me know what effect that has.
Cheers.

Report script taking too long to export data

Hello guys,
I have a report script to export data out of a BSO cube. The cube is 200GB in size. But the exported text file is only 10MB. It takes around 40 mins to export this file.
I have exported data of this size in less than a minute from other DBs. But this one is taking way too long for me.
I also have a calc script for the same export but that too is taking 20 mins which is not reasonable for a 10MB export.
Any idea why a report script could take this long? Is it due to huge size of database? Or is there a way to optimize the report script?
Any help would be appreciated.
Thanks

Thanks for the input guys.
My DATAEXPORT is taking half the time than my report script export. So yeah it is much faster but still not reasonable(20 mins for one month data) compared to other DBs that are exported very quick.
In my calc I am just FIXING on level 0 members for most of the dimensions against the specific period, year and scenario. I have checked the conditions for an optimal report script, I think mine is just fine.
The outline has like 15 dimensions in it and only two of them are dense. Do you think the reason might be the huge size of DB along with too many sparse Dims?
I appreciate your help on this.
Thanks

Java.sql.SQLException:ORA-01801:date format is too long for internal buffer

Hi,
I am getting the following exception when i trying to insert data in to a table through a stored procedure.
oracle.apps.fnd.framework.OAException: java.sql.SQLException: ORA-01801: date format is too long for internal buffer
when execute this stored procedure from ana anonymous block , it gets executed successfully, but i use a OracleCallableStatement to execute the procedure i am getting this error.
Please let me know how to resolve this error.
Is this error something to do with the Database Configuration ?
Thanks & Regards
Meenal

I don't know if this will help, but we were getting this error in several of the standard OA framework pages and after much pain and aggravation it was determined that visiting the Sourcing Home Page was changing the timezone. For most pages this just changed the timezone that dates were displayed in, but some had this ORA-01801 error and some others had an ORA-01830 error (date format picture ends before converting entire input string). Unfortunately, if you are not using Sourcing at your site, this probably won't help, but if you are, have a look at patch # 4519817.
Note that to get the same error, try the following query (I got this error in 9.2.0.5 and 10.1.0.3):
select to_date('10-Mar-2006', 'DD-Mon-YYYY________________________________________________HH24:MI:SS') from dual;
It appears that you can't have a date format that is longer than 68 characters.

Event Viewer cannot open the event Log or Custom view. Verify that the Event log service is running or query is too long. The instance name passed was not recognized as valid by a WMI data provider(4201).

"Event Viewer cannot open the event Log or Custom view. Verify that the Event log service is running or query is too long. The instance name passed was not recognized as valid by a WMI data provider(4201)"
This error keeps cropping up now and again on most of our domain controllers (OS-2008 AND 2008R2)...Usually a restart fixes the issue however the issue repeats and security logs don't generate.
Any advice on how to fix this issue permanently would be greatly appreciated.

Please see this: https://social.technet.microsoft.com/Forums/windows/en-US/95987ca3-a1b2-4da6-95b7-d825d06cdac7/error-code-4201-the-instance-name-passed-was-not-recognized-as-valid-by-a-wmi-data-provider?forum=w7itprosecurity
You can also try rebuilding the WMI repository: http://blogs.technet.com/b/askperf/archive/2009/04/13/wmi-rebuilding-the-wmi-repository.aspx
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

R/3 Extraction taking too long to load data into BW

HI There,
I'm trying to extract SAP Standard extractor 0FI_AP_4 into BW, and its taking endless time.
Even the Extract checker RSA3 is taking too long to execute the data. Dont know why its taking so long to execute.
Since there in not much data to take such a long time.
Enhanced the datasource with three fields from BSEG using user exits.
Is that the reason why its taking too long? Does User Exit slows down the extraction process?
What measures i should take to quicken the process?
Thanks for your time
Vandana

Thanks for all you replies.
Please go through the steps I've gone through :
- Installed the Business Content and its in version 3.5
- Changed the update rules, Transfer rules and migrated the datasource to BI 7
- Enhanced the 0FI_AP_3 to include three fields BSEG table
- Ran RSA3 and the new fields are showing but the loading is quite slow.
- Commented the code and ran RSA3 and with little difference data is showing up
- Removed the comments and ran, its fine, though it takes little more time then previous step...but data is showing up
- Replicated the datasource into BW
- Created the info package and started the init process (before this deleted the previous stored init process)
- Data isn't loading and please see the error message below.
Diagnosis
The data request was a full update. In this case, the corresponding table in the source system does not
contain any data. System Response Info IDoc received with status 8. Procedure Check the data basis in the source system.
- Checked the transformation between datasource 0FI_AP_4 and Infosource ZFI_AP_4
and I DID NOT found the three fields which i enhanced from BSEG table in the 0FI_AP_4 datasource.
- Replicated the datasource 0FI_AP_4 again, but no change.
Now...I dont know whats happening here.
When i check the datasource 0FI_AP_4 in RSA6, i can see the three new fields from BSEG.
When i check RSA3, i can see the data getting populated with the three new fields from BSEG,
When i check the fields in the datasource 0FI_AP_4 in BW, I can see the three new fields. It shows
that the connection between BW and R/3 is fine, isn't it?
Now...Can anyone please suggest me how to go forward from here?
Thanks for your time
Vandana

I participated in the mountain lion free upgrade for new mac owners but the password is too long to unlock the content code. HELP!!!

i participated in the mountain lion free upgradde for new owners but i cannot open the content code because the password is too long! HELP!

What happened was that the password was 32 characters long and the field that they give you to use would not allow you to manually type those characters in (crazy huh?) but it took it when i copied and pasted it in!

RSYST-CODE-input data too long

Similar Messages

Maybe you are looking for