ERPI FDMEE and EBS : Error initialize source system EBS

ODI-1227: Task SS_0 (Loading) fails on the source ORACLE connection EBS_DATA_SERVER.
Caused By: java.sql.SQLSyntaxErrorException: ORA-00904: "LEDGER_ID": invalid identifier
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:548)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:217)
at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:947)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1283)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1441)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3769)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3823)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1671)
at oracle.odi.query.JDBCTemplate.executeQuery(JDBCTemplate.java:189)
at oracle.odi.runtime.agent.execution.sql.SQLDataProvider.readData(SQLDataProvider.java:94)
at oracle.odi.runtime.agent.execution.sql.SQLDataProvider.readData(SQLDataProvider.java:1)
at oracle.odi.runtime.agent.execution.DataMovementTaskExecutionHandler.handleTask(DataMovementTaskExecutionHandler.java:70)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2913)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2625)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:577)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:468)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2128)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1930)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:580)
at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:513)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1073)
at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126)
at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$1.run(DefaultAgentTaskExecutor.java:49)
at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor.executeAgentTask(DefaultAgentTaskExecutor.java:41)
at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doExecuteAgentTask(TaskExecutorAgentRequestProcessor.java:92)
at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.process(TaskExecutorAgentRequestProcessor.java:83)
at oracle.odi.runtime.agent.support.DefaultRuntimeAgent.execute(DefaultRuntimeAgent.java:79)
at oracle.odi.runtime.agent.invocation.support.InternalLocalRuntimeAgentInvoker.invoke(InternalLocalRuntimeAgentInvoker.java:49)
at oracle.odi.runtime.agent.invocation.support.InternalRemoteRuntimeAgentInvoker.invokeStartScenario(InternalRemoteRuntimeAgentInvoker.java:173)
at oracle.odi.runtime.agent.invocation.support.InternalRemoteRuntimeAgentInvoker.invokeStartScenario(InternalRemoteRuntimeAgentInvoker.java:140)
at com.sunopsis.dwg.tools.StartScen.actionExecute(StartScen.java:271)
at com.sunopsis.dwg.function.SnpsFunctionBaseRepositoryConnected.execute(SnpsFunctionBaseRepositoryConnected.java:162)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execIntegratedFunction(SnpSessTaskSql.java:3437)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.executeOdiCommand(SnpSessTaskSql.java:1509)
at oracle.odi.runtime.agent.execution.cmd.OdiCommandExecutor.execute(OdiCommandExecutor.java:44)
at oracle.odi.runtime.agent.execution.cmd.OdiCommandExecutor.execute(OdiCommandExecutor.java:1)
at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2913)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2625)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:577)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:468)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2128)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1930)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:580)
at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:513)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1073)
at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126)
at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
at java.lang.Thread.run(Thread.java:662)
I am use EPM 11.1.2.3
Someone can help me ?

oh sorry ,
I failed in step initialize source system in FDMEE...
Source System :
select
#AIF.p_ledger_column_name as SOURCE_LEDGER_ID,
null as SOURCE_COA_ID,
'BUDGET' as LOOKUP_TYPE,
ver.BUDGET_VERSION_ID as LOOKUP_CODE,
bud.BUDGET_NAME as LOOKUP_DISPLAY_CODE,
case when bud.DESCRIPTION is null then bud.BUDGET_NAME
else substr(bud.DESCRIPTION,1,150 )end as LOOKUP_CHAR_VALUE
from GL_BUDGETS bud, GL_BUDGET_VERSIONS ver
where
bud.BUDGET_TYPE=ver.BUDGET_TYPE and
bud.BUDGET_NAME=ver.BUDGET_NAME
Target System :
INSERT INTO AIF_LOOKUP_STG
( SOURCE_SYSTEM_ID,
SOURCE_COA_ID,
SOURCE_LEDGER_ID,
LOOKUP_TYPE,
LOOKUP_CODE,
LOOKUP_DISPLAY_CODE,
LANGUAGE,
LOOKUP_CHAR_VALUE
VALUES
( #AIF.p_source_system_id,
:SOURCE_COA_ID,
:SOURCE_LEDGER_ID,
:LOOKUP_TYPE,
:LOOKUP_CODE,
:LOOKUP_DISPLAY_CODE,
'#AIF.p_source_system_base_language',
:LOOKUP_CHAR_VALUE
Thanks

Similar Messages

Failure of infopackage step in process chain - Error in source system.

Hello Experts,
We are experiencing this during the execution of process chain.
All the step for data loads within BW(DSO to DSO, DSO to cube) are failing with error -
- Error in source system
- Error during data selection
Please note that we are 3.5 data flow and thus, data load within BW is through emulated data source and the infopackage. Steps running such infopackages for emulated data source are failing in process chain with error above.
Surprisingly, when I run the infopackage manually out of process chain it runs successful without any error. But when I run through process chain it fails.
Any clue or suggestion? We have already tried doing re-initialization for infopackage.
Appreciate your inputs.
Regards,
PK.

Hi,
When we run data loads thru process chain it will run in background. as per the available background application servers your request will be processed.
as my your during your load time server will be on high load.
please check your system busy schedule and schedule your process chains.
Check Tx - SM50, if you have less application servers, then ask basis to create few more to application servers to process the request at busiest time.
check about increasing parallel processing and default data transfer settings.
go to info package---> menu scheduler--> data settings for default data transfer.
Thanks

Errors in source system

Hi Friends,
 I got an failure with a data load... The data was loading into ODS from r/3. The data source name 2lis_03_bf... I got an error like this in status Tab -
Error message from the source system
Diagnosis
An error occurred in the source system.
System response
An error occurred in Extractor .
Check the error message.
Procedure
The procedure for removing errors takes place depending on
the error message:
Note
If the source system is a Client Workstation, then it is possible that the file that was to be loaded was being edited at the time of the data request. Make sure that the file is in the specified directory and is not being edited, and restart the request.
And when we click on the error message push button... we are having the following errors : -
Message Type Message Class Message Class 
Errors in source system RSM 340
Queue 2LIS_03_BF is not available in the source system RSQU 9
Activation of data records from ODS object terminated RSM1 102
Answering Getz appreciated,
Thanks & Regardz,
Aluri

Hi,
On BW go to SE16. Look at RSSDLINIT table. Match up the LOGSYS with your OLTPSOURCE (for the infopackage that is causing the problem).
Delete that line
Now you can open the infopackage. (be sure to delete the initialization) before you run the info pack again.)
Regards
Srini

Error in source system while extracting the data from R/3!

Hi,
i had created FM and extract strcucture in R/3 .
using the above two, i had created data source using RSO2 T code.
when i checked the extractor ( RSA3 T code) in R/3 it was working fine .
(status messege displayed as 1000 records selected).
then i assigned this data source to infocurce and creted info cube using the same info source.
but when i schedule the info package it is syaing in the monitor screen "error in source system".
what could be the problem?
Thanks,
Ravi

Hi
trhese are the possiblies
1.first check the source system connection and find if there is any error in it.
2.Go to sm37 and find whether the request is completed or not if its terminated find out the time. how long does it takes to complete the process.
3.once again relicate the data source and find whether is it again extract data.

Error in source system in BI 7.0...

Hi,
When creating a source system in Bi 7.0, when i am going to t code- rsa1- client-right click and then check,it's giving an error like:
EDI- partner profile not available and then detail for this error is-- a partner profile cannot be found with this key- /DBICLNT300/LS
THIS INVLOVES THE KEY FIELD OF THE TABLE EDPP1-
PARNUM-PARTNER NUMBER
PARTYP-PARTNER TYPE
Please help me in solving this. Thank You.

Hello,
Try a restore on your source system (rightclick -> restore) This way idoc ports and agreements are regenerated between BW and R/3. If this does not solve the problem ceck this:
Hi,
Did you do a system copy for BW ?
Try a restore (rightclick on your source system) in most cases this will solve the problem.
If not check the notes below:
184322 Procedure after DB copy of BW source systems
886102 System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
325470 Activities after client copy in BW source systems
325525 Copying and renaming systems in a BW environment
184754 Procedure after BW database copy
184447 Building a BW-system landscape
184971 Notes on BW source system connections
140276 Error in source system assignment
524554 Storing destinations in the BW environment
538052 Maintenance of Myself destination in BW
Regards, Patrick Rieken

"Error in source system" while creating source system

Hello,
I don't know what's our general problem (I suppose that it's ageneral problem) but we always have the following eror while creating a source system:
When we want to create a source system on BI, we first get an error "No connection to source system possible". After checking the RFC connection and correct the password of the remote user on the automatically created _DIALOG RFC connection the exception changes to "Error in source system".
The error occurs after the information "Please log on as an administrator in the following screen".
The remote user on R/3 side has got profiles S_BI-WHM_RFC and S_BI-WX_RFC (found two conflicting statements regarding this profiles), on BI side it has got SAP_ALL and some more profiles
What else could be the problem?
Greetings & Thanks
Bettina

Hello,
now we know that
1. the remote user needs profiles SAP_ALL and SAP_NEW and has to be dialog user with a password unequal that password it should have in the future (otherwise you don't see the error messages that appear during the login process)
2. the system has to be changeable (scc4 and se03)
After the source system is created the changeability can be changed to the original values and the remote user can be changed to a communication user again.
Thanks for the tip regarding the authorizations.
Greetings
Bettina

Error in Source System, Time series does not exist

Hi Guys,
I am loading the data from APO system and i am getting the below error after scheduling the info Packs.. can you analyze and let me know your suggestions
Error Message : Time series does not exist,
Error in Source System
I have pasted the ststus message below
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
Thanks,
YJ

Hi,
You better search for the notes with the message ""Time series does not exist". You will get nearly 18 notes. Go through each note and see the relevence to your problem and do the needful as it is mentioned in the note .
Few notes are:
528028,542946,367951,391403,362386.
With rgds,
Anil Kumar Sharma .P

Error while source system creation/Source system transport

Hi,
     In our BW implementation, the system landscape is only 2 servers. One is BW Dev, another is BW Prd. All configurations are done in BW Dev and I extracted the data from QAS for this BW Dev system.
     Since we cant create the source systems in the BW Production system, I tried to create the source system for the SAP R3 Production system in BW Dev and trying to transport this to BW Production Instance.
     I have two queries.
1. Is this way is correct for creating the Source System for BW Production system?
2. When I tried to activate the source system I am getting the following error messages. (I tested the RFC Destinations. There is no problem, I also done the configurations for logical system creation and client assignment in both the systems).
Error in source system GWPCLNT900
     Message no. RSAR502
Diagnosis
     With Remote Function Call to system GWPCLNT900 error connection closed
     (no data) ccurred.
Procedure
     Remove the cause of the error.
When tried again I got the following error message
Basic type ZSBB030 doesnt exist. EA 447
Result of the destination check: Timeout RSAR 375.
Could anyone throw some light on these errors?
Thanks in advance.
Krishna

Hi,
you need to maintain the logical systems on both R/3 and BW. You also need to set up the RFC connection with users that can log in to the other system. The R/3 system must be open for customizing in scc4.
In transaction se03 the system change options for 'Business Information Warehouse: SAP Namespace' and 'Business Information Warehouse: Customer Namespace' may need to be modifiable. I am not completely sure about this.
The last thing I will mention is that I have seen source system creation fail when the RFC-users are system users, and the source system creation worked if the RFC-users was display user while creating the source system. The RFC-users must be changed back to system user later...
Please look at best practice documents on a more step-by-step guide...
Best regards,
Christian Frier

Urgent Help! Errors in source system(RSM 340)

Need urgent help. Issue in production.
I added fields to the COPA datasource, by changing the operating concern. I recreated the datasource with the same name replicated into BW & ran delta again. The whole procedure worked fine in Dev & Quality but in production it gives me the below error. I thought its a delta issue so I deleted the data & try reload but still same issue. Below is the error. I checked the connection with R3. its an ok. All other loads work fine. Before deleting delta, it gives below error & when you rerun, it finishes with zero records. I also tried activating update, transfer & ods & cube in BW. I also asked functional guy to check operating concern & its active. kindly help
Errors in source system RSM 340
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.

Hi PK,
caller 09 error mainly because of source(target system) and destination(bw system) not configured correctly.
i think you get the error message as follows. file is in the client workstation as like.
better you contact basis people. they will resolve this.
hope this help you
Regards
Harikrishna N

Time series does not exist, Error in Source System

Hi friends,
I am loading the data from APO system and i am getting the below error after scheduling the info Packs.. can you analyze and let me know your suggestions
Error Message : Time series does not exist,
Error in Source System
I have pasted the ststus message below
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
Thanks,
YJ

Hi,
You better search for the notes with the message ""Time series does not exist". You will get nearly 18 notes. Go through each note and see the relevence to your problem and do the needful as it is mentioned in the note .
Few notes are:
528028,542946,367951,391403,362386.
With rgds,
Anil Kumar Sharma .P

DYNPRO_SEND_IN_BACKGROUND errors in source system

Hi All,
Yesterday night we kicked DELTA Process Chain.
The PC failed While loading the 0GL_ACCOUNT Attributes, and showing the message Errors in Source System.
and also Failed at Cost Element Attributes but both the error messages are same.
Checked the source system connections and repeated the process, but it was failed again. and tried to load manually and again failed.
When we check the DUMP in Source system (ECC) in ST22 showing the message as below:
"DYNPRO_SEND_IN_BACKGROUND" Current screen: "SAPLSTRD " 0351
Note: We ran FULL load day before yesterday and Ran INITIAL yesterday, We are running DELTA TODAY.
one thing is we just deleted the GL attirbutes Requests manually and loaded INIT , we are able to do INIT load perfectly. but while trying DELTA only this problem is causing.
Thanks in Advance,
Teena

Hello ,
Sometimes the problem happens because the background users do not have the correct authorization. Please check the information in the SAP note 150315.
Kind Regards,
Des

Error in the Data Selection - Errors in Source System RSM 340

Hey Everyone,
I'm having an issue with loading a Delta for 0MAT_PLANT_ATTR. This is the second night it has happened, where I get the error "Error in the Data Selection". This error happens in the EXTRACTION part of the Monitor. And, we cannot run another Delta to see if it'll work, we have to delete the old Delta Init, and run a new one. The other error is "Errors in Source System - RSM340". That's as much it gives.
Could anyone suggest why this would be happening? I checked RSA3 in R/3, and no errors on the extraction. I also checked sm37 against the job that loads that data, and it completed successfully. I honestly don't think there's an issue with the data. We cannot have this happen often, and I just need to know if this is something that can be corrected.
Thanks,
John

There is nothing wrong with the TID's or anything like that. There is also no selection criteria in the infopackage.
When the Delta fails, the error occurs under EXTRACTION in the monitor. It seems to be successful under TRANSFER and PROCESSING in the monitor, which I find strange. Also, I run a new Delta Init with Data Transfer, and that works just fine.
So, I'm not sure what it could be?

Error activating source system

hi all
in bi7.0 i have source system which is connected to r/3 4.7
while activating its showing error "Result of the destination check: Name or password is incorrect (repeat logon)"
I have given the right password for biwuser in BI and aleremote in r/3 side
when i am trying to restore after giving all password in the restore option of the source system its showing message "rfc user logon failed check connection"
what may be the reason as i have crosschecked all the password is right.

Hi,
I have faced similar issue. It is due to the version of R/3. R/3 4.7 stores the password in uppercase. When you activate source system, it supplies upper case password to biwuser in BI.
Change the biwuser password to uppercase and try restoring the source system with uppercase password.
Hope it helps,
regards,
Pruthvi R

Error in source system TD1511

hello gurus, I have a Infosource name 2LIS_05_QE2, I haved assigned 4 Source System namely (CD1513, GP1590, TD1511, WD1511), It uses a Function Module in R/3 and Appended Structure (I've already transported the FM, Appended DS, Function Group and the Zsextractor assignment), I don't have any problems in activating other Source System (CD1513, GP1590, WD1511) only in TD1511, I can't activate the Transfer Rule and Im getting the error,
"Error in source system TD1511 "
Ive already replicated the Source Ssytem and only in T Cluster Im currently experiencing the said problem, I even go to Source System and right click on the T Cluster to check, and the connection is ok, What maybe the caused of the said problem? thank you very much... I really appreciate any help...

Ive fixed it, Ive check all the R3 box 2 by 1, and T Cluster was down, by the way thanks, The Checking of connection in BW is so confusing because it says "OK", but when I check each cluster individually, I noticed it was down, Thank you very much,I will give you a score

Error deleting source system with error message: "incorrect input for....."

Hi,
I'm trying to delete the source system using tcode RSA1 => Source systems => select the 'source system' and delete, but I got an error message as follows:
"incorrect input for activating transported shadow IPacks"
Fyi, I have opened up the client configuration (SCC4) prior to delete this source system but the source system still cannot be deleted and I receive the above error message.
Please let me know what is the caused of the error and how to solve the problem.
Thanks for your kind help.
Regards,
Mark

Hi Mark,
Which version of BW are you in?
check this thread and also the note 709581
Error Deleting Source system connection
Thanks,
Raj

ERPI FDMEE and EBS : Error initialize source system EBS

Similar Messages

Maybe you are looking for