Source System set error

We are seeing a weird error with a source system we are trying to re-create after a refresh. Our basis folks have tried many things, and they finally deleted the source system and are trying to re-create it again. They error they cannot get past is in automatic source system set up process when the EDI profiles are generated.
We are seeing the following series of errors:
Error during insert in port table - E0552
EDI Partner Profile not available - E0332
Entry in outbound table not found - E0400
Entry in inbound table not found - E0414
Entry in inbound table not found - E0414
Port Description contains errors. Incorrect destination - RSAR 669
We debuged some last night, and we were seeing that in the function module RSAR_LOGICAL_SYSTEM_CREATE_NEW, it was returning a 'no_free_namespace' error.
I check SDN and OSS, but there was not any notes for the error above.
Has anyone seen this before?
Thanks in advance!
Bill

Hi Bill,
I experienced a lot of system setting phase project in the past...I think you missed your Partner profiles (WE20)...take a look to this transaction, here you should find under Partner type LS the logical name of your BW (if missed you have to recreate it !)...here you have to insert as outbound parameter 'RSRQST' as message type and 'RSINFO', 'RSSEND' as inbound parameters, BIW as partner class, status 'A'...
Let me know something...
Bye,
Roberto

Similar Messages

Error in codepage mapping for source system. Error

Hi BW Experts,
I am facing following error:
Error message: Error in codepage mapping for source system. Error text:
Details: Inbound Processing ( 1000 Records ) : Errors occurred
Error in codepage mapping for source system. Error text:
Update PSA ( 0 Records posted ) : Missing messages
I repeated the delta working and everything fine.
Does anybody know why this error occurs?

Run rsa13 (for bi 7.0) find your source system which one you are using for data transfer and double click on it and find special options there select the optioned i mentioned already.
Please search SDN you can fin threads related to this thread
if not let me know.
Regards.

Error in codepage mapping for source system. Error text:

guyz,
im facing the below issue in prod.
Error in codepage mapping for source system. Error text:
Message no. RSDS_ACCESS013
Collection in source system ended
Error message during processing in BI
Diagnosis
An error occurred in BI while processing the data. The error is documented in an error message.
System Response
A caller 01, 02 or equal to or greater than 20 contains an error meesage.
Further analysis:
The error message(s) was (were) sent by:
Inbound Processing
Procedure
Check the error message (pushbutton below the text).
Select the message in the message dialog box, and look at the long text for further information.
Follow the instructions in the message.
need your guidance,
cheerz,
raps.
Edited by: raps on Mar 1, 2012 9:39 AM

Hi ,
Kindly go throught the following threads for your issue resolution::
Error in code page mapping for Source System
Erroe in source system
Regards,
Arpit

Source system connection error

Dear BW Experts,
Now, i am in a critical situation,that the source system giving error in the quality system.So unable to extract data for testing.we have tried a lot getting any solution.
But now planning to connect the sand box system to the bw quality system.
The confusion is that if the sand box is connected to the bw quality system,then can i use all the developed objects(infocubes,ds objects,multi providers etc) which i had created before or design and activate all the objects again for the new source system.
If any body attended this type of issues earlier,please suggest me how to proceed....
Thanks & Regardas
Debasish

Hi,
u can connect ur bw quality system to ur sand box.
but u have to reimport all requests from Bw development to bw qualty.
Imp. u have to delete Source conversion routine before importing request.
Steps will be same like
1. replicate data source.....
2.....
etc..
/Sachinkumar.

Source system set up for internal / external access

Hi all.
We have an EP 6.0 (NW04 SP16) system delivering BW data from a back-end BW 3.1/3.2 system. We are using BW Report iViews to deliver all reports to external and internal users. I am having a very specific problem when setting up the source system for the BW system.
The BW Report iView object uses the WAS hostname parameter(found under: System Administration -> System Configuration -> Systems -> BWSourceSystem -> Open ->Object -> "Web Application Server (WAS)") when retrieving the back-end BW report.
When this parameter is set using an internal host id (internal_host.company.com) internal users can access the report in question, but external users can't. Alternatively, when this parameter is set using an external host id (ie. the host of our DMZ proxy server) external users can access the report, but internal users can't.
I need to find a way to use one hostname for this parameter that will work for both internal and external users. I have worked with the HTTPURLLOC table and this solution works great for URL iViews, but not for BW Report iViews. Does anyone have any suggestions? Thanks!

Hi Shashi.
We did find a solution using web dispatcher. We actually installed two instances of web dispatcher... one in our DMZ for external access and another one our corporate LAN. The web dispatchers are configured identically and the EP instance knows only one hostname:
name.company.com
The port passed to the URL https://name.company.com:port is what tells web dispatcher what to do with the request (ie. pass the request to EP, BW, ECC, R/3, etc.).
Be aware that EP allows for only one hostname for Source System Setup - my name.company.com in my example above -(this is the EP Web Application Server hostname (WAS) parameter found under System Admin - System Config - Systems) - so you may need to do something like we did:
register name.company.com on the internet as a public address and use that DNS mapping for external users (using your DMZ version of webdispatcher). Subsequently, use internal DNS or host name mapping to register an internal private addresss for name.company.com (using your LAN version of web dispatcher). this will allow both internal / external users access to the portal and other SAP back-end systems.
It may sound a bit kludgy, but believe me - we tried everything to make this work. I took this all of the way to SAP and this was the recommendation SAP made for allowing both internal and external users access to portal and BW data.
Hope this helps!

RRI using Tcode in source system giving error

Hi,
I am trying to run a report in BW in tcode RSRT using RRI mechanism and the same is throwing an exception - An error occurred with the report to report interface during the jump. The same when run in BExAnalyzer throws an error "A critical error occured".
The selections I have applied are as under:
Target system -> Source System(ECC)
Report Type -> Transaction
Report Destination -> ME2L
Assignments as under:
0DOC_NUM -> EBELN
Any trace to the cause of the error would be helpful.
Thanks,
Amogh

Try creating a program in source whihc calls t-code ME2L and then from RRI try to call the program., and also check if you have authorization to t-code RSRR_WEB &RSBBS_WEB in you source system,
If this did not help give us more detial on the error you are faceing.
Shashi

2LIS_02_HDR : Source System ID error

Trying to upload from this datasource in 3.5 environment. I keep getting error while extracting, erroneous data in PSA.
Source System ID not found, how do I fix this?
Thanks in advance
Fran

Fran
Go To RSA1>Tools>choose assignment of source system to source system ID-->assign ID. assign your source system ID to source system and save it
You could find source system ID in your source system tab
Hope this helps
Thnaks
Sat

R/3 source system creation error(Idoc is missing)

Hi expert's.
i have created an r/3 source system in BI 7. but it's showing error when i am activating it.
error as follows.
1. Basic type ZSMA087 does not exist     EA     447
2. Incorrect IDoc type ZSDF085 in the ALE definition of the source system     RSAR     373
for the above error 1 i checked in the RSBASIDOC table. it showing the idoc type. when i am checked with the source system that is r/3 system in the partner profile for logical system. it's showing the incorrect idoc type in RSSEND outbound parameters for that logical system
when i am changed that idoc type it's showing error as follows.
"entry RSSEND zsma087 does not exit in edimsg.
after that i checked with this table edimsg. for the rssend outbound option it's won't have the idoc type zsma087. table edit is also not possible on that.
so please help me to solve the issue.
regards
Harikrishna N

Hi Hari,
                Are you using ECC6.0 system or Bw(bi7.0) & R/3 source system
Regards,
Vijay.

Source System RFC Error in BI

Hello SAP Experts,
I have installed BI 7.0. And i have created an RFC connection for BI to R3. It was working fine but now the SAP R/3 source system in RSA1 is giving an error "Result of the destination check:Name or password in incorrect(repeat logon)". And also when i am logging in, moving between screens or T-codes, it is taking a long time and the status in the bottom of the screens shows that it is checking all the destinations that is the RFC connection created. Not able to trace the reason behind this. Please help. BL consultants are waiting to work.
Thanks a lot
Regards
Vani

Hello MLN,
This is not the first time i am configuring SS. I have done it long back. I created a user manually long back and i used that user while configuring the SS. All these months it worked fine and no issues. As far as i know,ALEREMOTE and BWREMOTE are service users which we get by default after installation. And during configuration, i remember, i gave the passwords for both the users. But my question is, all these days it went fine and now it is giving an error. And why is it checking all the destinations when i execute any transaction. Please clarify. BI consultants practiced SPRO, so is there any chance that they might have changed or ececuted something and the result is this error? If so what can that be. Please suggest
Thanks a lot
Regards
Vanitha

Source System creation error

Hi..
I cannot create R/3(productive) source system at BW (development)
I checked password, cross-client and client specific are all changeble (t-code SCC4) and namespaces, sofeware are also modifiagle (t-code SE06) at R/3.
At BW, RFC connection is Ok (SM59) and R3 side, RFC also connected w/o problem.
But the error is still not resolved.
What I have to do now..

Hi Ravi..
Error massage is...
Massage No. RSAR502
Diagnosis
With Remote Function Call to system error Screen output without connection to user. ccurred.
and runtime error massage is (ST22)
DYNPRO_SEND_IN_BACKGROUND
Rita

Source system initialization error in ERPI using EBS,

Hi,
I am trying to initialize source system details in ERP Integrator(workspacce) using EBS detials,for loading to Planning.
Add source system is success,then click on Initialize button I got this error:
Error encountered while launching the ODI Process :Agent didn't prepare this command:Error during Session Preparation:No suitable driver
can you please tell me ,why i am getting this error.
Regards,
SV

Hi There,
I am trying to extract metadata out of EBS and target is Essbase. Everything is setup and connection working fine.
My problem is that the chart of accounts is getting built in Essbase as a flat structure? How do I get the roll ups from EBS into Essbase? Is there a certain seeting that I must choose to be able to build the Parent Child relationships?
Thanks for the help
Regards
Henk

Conversion of source system names --- error in transport

hi
i want to transport my object from Dev111 to Quality222
but the transport ended up in error 8
it gave the error...
Source system PRODUCTION333 does not exist
I am confused,
shouldnot it should give error related to Quality system ???
how should be the mapping in Source system names?
after research it seems it should be maintained in
RSA1-TOOLS-mapping of SOURCE SYSTEM NAMES.
i have following systems...
BW- DEV111 QUTY222 PDN333
R3 DEV121 QUTY242 PDN363
What should the entries look like in which system

Landscape is -Transport should be send from Deve-Quality---Production
BW....................................
DEV111 QUTY222 PDN333
R3.....................................
DEV121 QUTY242 PDN363
CAN you advise if the entries SHOULD look like below in Quality and Production System???
Quality system should have entries like:
bw DEV111.............. bw Quality 222
r3 DEV121................ bw Quality222
Production system should have entries like:
bw Quality222.............. bw Production333
r3 DEV242................ bw Production333
Q1 ......IS THIS HOW ENTRIES SHOULD BE IN Quality & Production system???

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

Source System Activation Error

Hi,
We Upgraded BW3.1 to BI7.0, we did successfully on Development. but when in QA when I was trying to activate RFC by going to RSA1 and right click and activate it is showing errors like
Source system XXX300 is inactive     RSAR     5
BI unknown in source system     RSAR     8
BI IDoc type ZSBB025 is not the same as source system IDoc type     RSAR     371
The following errors occurred in the source system:     RSAR     374
EDI: Partner profile not available     E0     332
Entry in inbound table not found     E0     414
Entry in outbound table not found     E0     400
Entry in outbound table not found     E0     400
Am I missing anything ?
Thanks,
Chander

Hi
As a part of sanity check did you perform rituals as below -
Below deletes the BW-specific information in the source system that does not have a connection to the BW System.
1. Log on to the source system in question
2. Call Transaction SE37
3. Enter function module name 'RSAP_BIW_DISCONNECT'
4. Select the 'Sngl. test' function.
5. Enter the name of the BIW system for the import parameter 'I_BIW_LOGSYS' that matches the one prior to the new installation
6. Enter the name of the source system for the import parameter 'I_OLTP_LOGSYS'
7. Choose the function 'Execute'
and then
Transaction SE37 - function module RSAP_BIW_CONNECT - Single Test. Parameter:
                        I_LANGU        <language of the destination to BW>
                        I_SLOGSYS      <OLTP Source system (SLOGSYS from RSBASIDOC in BW)>
                        I_LOGSYS       <BW system (RLOGSYS from RSBASIDOC in BW)>
                        I_STEXT        <name of the OLTP system>
                        I_BASIC_IDOC   <BIDOCTYP from RSBASIDOC in BW>
                        I_SAPRL        <SAPREL from RSBASIDOC in BW>
                        I_RESTORE
                        I_TSPREFIX     <TSPREFIX from RSBASIDOC in BW>
                        I_PREFIXE <35 times second byte of TSPREFIX from RSBASIDOC in BW
                                       (Example TSPREFIX = 'BA', then
                                         I_PREFIXE = 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA')>
Hope it Helps
Chetan
@CP..

Source system activate error

Hi,
I have created new source system for R/3 quality , when i am activating then getting following error. Kindly suggest how to resolve this error. Thanks in advance.
BI unknown in source system RSAR 8
BI IDoc type ZSDB018 is not the same as source system IDoc type RSAR 371
EDI: Partner profile not available
Entry in inbound table not found
Entry in outbound table not found
Rgrds
Rakesh

Hi,
Check the source system RFC connection in SM59, if this is ok then check the tcode WE20 for EDI partner profiles and inbound and out bound Idocs defined.
In BW Out boud IDOC type should be same in ECC in bound Idoc type, and in ECC out Bound IDOC type should be same in BW in bound IDOC type then the source system activation is possible in RSA1.

Source System set error

Similar Messages

Maybe you are looking for