CLIENT of the source system in the Transfer Rules

Hi,
Can I get the CLIENT of the source system dynamically in the Transfer Rules (and assign it to an InfoObject)?
I have a generic extractor from a R/3 source system. The table in the source system & the extract structure the DataSource both contain MANDT, but its not coming in the RSO2 screen (which, if I'm not wrong, is how it should be).
I need the CLIENT info. in my BW data targets. I do not want to hardcode this value in Trans Rules as the client in Dev & Prod is different for my R/3 sys.
If I can't get it directly from the DataSource, is there any way I can get it from any system field using routine?
If I'm not wrong - SYST-MANDT in the Formulas will give me only my BW CLIENT.
Thanks in advance for your help.
Regards,
Melwyn

hi,
i think if your bw dev and prod client is different you can try in transfer rules
if sy-mandt = xxx. ( bw dev client number)
result = 'yyy'. (source system dev)
else.
result = 'zzz'. (source system prod)
endif.
or enhance the extract structure/ append structure with zz field for mandt and field in user exit zxrsau01 with sy-mandt
or if use infoobject 0LOGSYS, populate in transfer rules with result = g_s_minfo-logsys.
hope this helps.

Similar Messages

How to assign the source system to the virtual provider

Hi
How to assign the source system to the custom virtual provider with services in BW 3.5 ?
Regards
PWnuk

Hi PWnuk,
Refer this link on how to implement a virtual provider with services.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4752ec2d-0a01-0010-ecb0-a145cf2e3e92
Hope this helps
Regards
Karthik

How to Identify the Source System in a Transformation Rule?

Hi,
   In a 3.x system if I needed to identify the source system, the interface had a parameter SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS. I do not see the same in a Transformation Rule. Can anyone tell me how can I make a decision in my transformation rule depending on the Source System?
    Say for instance I want to change the following Update Rule from a 3.x System to a Transformation in BI7:
IF SOURCE_SYSTEM = 'ABC'.
   RESULT = 1.
ELSEIF SOURCE_SYSTEM = 'A11'.
   RESULT = 2.
ELSEIF SOURCE_SYSTEM = 'AZ1'.
   RESULT = 3.
ELSE.
   RESULT = 0.
ENDIF.
Can anyone help? Points will be rewarded.
Regards,
Kazmi.

Hi Siggi,
   But how would I know the Request ID within a transformation ? REQUID is the key of the table rsbkrequest ? The interface of the transformation method has the following parameters:
IMPORTING
    request     type rsrequest
    datapackid type rsdatapid
    SOURCE_FIELDS
   EXPORTING
     RESULT
So all I can be aware of is the Request Name and the Data Packet Number. For instance when I took your approach, I got the Request Name as "DTPR_8E3VKVN0RJPDNXAKMP0PZJ99B" now I cannot look up with this against the key of the table because REQUID is a number field. Now, if I look up against the field "Data Transfer Process ID (DTP)" I do not find any entry in this table.
   Any more info?
Regards,
Thanks.

NO PSA for InfoSource and source system 120 : Maintaing Transfer Rules

Hello BI Experts ,
I am working on Generic data source extraction.
Earlier I mapped all fields infoobjects in Transfer Rules and then loaded data to ODS properly.
But later on I made few changes in Generic data source view and exits in the R3 and replicated the data source to BI.
Then Remapped the fields to infoobjects in Transfer Rules.
Now I can see Transfer Rules Green and all fields are mapped properly.
But when I activated Transfer Rules I am getting message that ,
"There is no PSA for InfoSource ZPS_DATA_BB and source system 120 "
Data source is active in R3.
Communication Structure and Infosource are Active in BI.
Regards ,
Amol K.

hello Surendra ,
I did the same thing already.
I was looking for some otherway.
Thanks for reply.
Regards ,
Amol K.

How to crete the source system for the SQL Server 2000 to BI 7.1

Dear All,
We want to extract data from SQL server 2000 data base to BI 7.1
Please provide us the step-by-step procedure to be followed in BI as well as SQL server 2000 BD
Thanks & Regards,
sarasu

Hi,
You have two options, you can use DB Connect but you need SAP DBSL for SQL Server 2000 and the DB Client and this could be have a additional cost, or you can use UD Connect, that make the connection with Java, using JCo's and the Driver Java for SQL Server 2000, please review this link: [http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/58f4db47-0501-0010-a2bf-ff01b150fdff|http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/58f4db47-0501-0010-a2bf-ff01b150fdff]
I recomend if you dont have the SAP DBSL and DB Client for SQL Server 2000 that use UD Connect is really useful.
Regards

Change of the source system

Hi
all
Background installation from SAP r/3 was already done and the system is up and running.
Now i would like to replace the SAP R/3 with ECC version , where I must replicate the same extractor now with obviously a different version of ECC.
I wonder if the source system change will effect the similar infoobjects which were already installed and assigned to a different source system.
Please explain me the effect and defects, or if any changes on the master data already existing.
thanks

When you change the source system - all your transfer rules , data sources etc will be gone and you will have to do them again.
The master data and transacton data will not be affected only that you will have to init the same again and deltas subsequently...
You could instead - keep the old system connection alive and then create a new set of transfer rules , data sources etc for the new system - that way you can have the old Transfer rules , data sources active and then have the coding done the for same alive for reference as well..

Data load problem - BW and Source System on the same AS

Hi experts,
Im starting with BW (7.0) in a sandbox environment where BW and the source system are installed on the same server (same AS). The source system is the SRM (Supplier Relationship Management) 5.0.
BW is working on client 001 while SRM is on client 100 and I want to load data from the SRM into BW.
Ive configured the RFC connections and the BWREMOTE users with their corresponding profiles in both clients, added a SAP source system (named SRMCLNT100), installed SRM Business Content, replicated the data sources from this source system and everything worked fine.
Now I want to load data from SRM (client 100) into BW (client 001) using standard data sources and extractors. To do this, Ive created an InfoPackage in one standard metadata data source (with data, checked through RSA3 on client 100 source system). Ive started the data load process, but the monitor says that no Idocs arrived from the source system and keeps the status yellow forever.
Additional information:
BW Monitor Status:
Request still running
Diagnosis
No errors could be found. The current process has probably not finished yet.
System Response
The ALE inbox of the SAP BW is identical to the ALE outbox of the source system
and/or
the maximum wait time for this request has not yet run out
and/or
the batch job in the source system has not yet ended.
Current status
No Idocs arrived from the source system.
BW Monitor Details:
0 from 0 records
but there are 2 records on RSA3 for this data source
Overall status: Missing messages or warnings
- Requests (messages): Everything OK
o Data request arranged
o Confirmed with: OK
- Extraction (messages): Missing messages
o Missing message: Request received
o Missing message: Number of sent records
o Missing message: Selection completed
- Transfer (IDocs and TRFC): Missing messages or warnings
o Request IDoc: sent, not arrived ; Data passed to port OK
- Processing (data packet): No data
Transactional RFC (sm58):
Function Module: IDOC_INBOUND_ASYNCHRONOUS
Target System: SRMCLNT100
Date Time: 08.03.2006 14:55:56
Status text: No service for system SAPSRM, client 001 in Integration Directory
Transaction ID: C8C415C718DC440F1AAC064E
Host: srm
Program: SAPMSSY1
Client: 001
Rpts: 0000
System Log (sm21):
14:55:56 DIA 000 100 BWREMOTE D0 1 Transaction Canceled IDOC_ADAPTER 601 ( SAPSRM 001 )
Documentation for system log message D0 1 :
The transaction has been terminated. This may be caused by a termination message from the application (MESSAGE Axxx) or by an error detected by the SAP System due to which it makes no sense to proceed with the transaction. The actual reason for the termination is indicated by the T100 message and the parameters.
Additional documentation for message IDOC_ADAPTER 601 No service for system &1, client &2 in Integration Directory No documentation exists for message ID601
RFC Destinations (sm59):
Both RFC destinations look fine, with connection and authorization tests successful.
RFC Users (su01):
BW: BWREMOTE with profile S_BI-WHM_RFC (plus SAP_ALL and SAP_NEW temporarily)
Source System: BWREMOTE with profile S_BI-WX_RFCA (plus SAP_ALL and SAP_NEW temporarily)
Someone could help ?
Thanks,
Guilherme

Guilherme
I didn't see any reason why it's not bringing. Are you doing full extraction or Delta. If delta extraction please check the extractor is delta enabled or not. Some times this may cause problems.
Also check this weblog on data Load errors basic checks. it may help
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Thanks
Sat

Restoring the source system connection in BW

Hi all,
Ive been trying to upload data for 2 of my infocubes, and the extractions are bouncing. The message in R/3 is told me to check the connection. The RFC are fine. But when I tried to restore the source system connection (RSA1 in BW), it sent me the following error messages:
1.- Basic type ZS 118 does not exist.
2.- The following error in the source system:
3.- Incorrect IDoc type ZSAB023 in the ALE definition of the source system.
The description in each error is:
Error #1:
Diagnosis
    IDoc type ZS 118 could not be found.
System response
Procedure
   Please enter an IDoc type that exists.
Error #3:
Diagnosis
    Incorrect IDoc type ZSAB023 in the ALE definition of the source system.
System response
    Error when sending data to BW.
Procedure
    Enter IDoc type ZS 118 .
They told me this IDocs are created automatically by the connection. Is that true?
How can I fix this, so that I can restore my connection and do the data extraction?
Thanks a lot
Regards,
Vic

Hi Victor Tostado
1.- Basic type ZS 118 does not exist.
Type Transaction WE30. Check iDoc types Obj. Name : RSSEND -> press F7
a.) Enter 'RSSEND' in the Obj. Name field. You will see an entry similar to the one below:
          RSSEND                          Data transfer from the source system (template)
                [-] E1RSSH               Data transfer IDoc: Header information
                         [+] E1RSHIE    Data transfer Idoc: Hierarchy header information
                                E1RSTXT   Data transfer IDoc: Texts
     b.) Enter RSREQUST in the Obj. Name field. You will see an entry similar to the one below:
            RSREQUST                    Data request to the source system
                 [-] E1RSRH               Data request IDoc: Header segment
                         [+] E1RSRHI     Data request IDoc: Hierarchy
                         [+] E1RSRTX    Data request IDoc: Texts
                         [+] E1RSRMD   Data request IDoc: Master data
                         [+] E1RSRIS      Data request IDoc: InfoSource
     c.) Enter RSINFO in the Obj. Name field. You will see an entry similar to the one below:
            RSINFO                         Info IDoc
                [-] E1RSHIN             InfoIDoc: Status segment
                        E1RSPIN            InfoIDoc: Data packet segment
                        E1RSEIN            InfoIDoc: Error segment
d.) If any of the above do not exist, contact your BASIS Team.
2.- The following error in the source system:
Type Transaction SM59. Maintain RFC destinations
a.)     Open the RFC Destinations. b.) Find your Source System and double click on it. c.) Technical setting should contain information regarding your source system d.) Logon Information should contain source system client and name & password for you remote logon.
3.- Incorrect IDoc type ZSAB023 in the ALE definition of the source system
Type Transaction WE21. iDoc Processing Ports.
receivers port is not available go to WE21 -> create port
a.) Select 'Ports' and then 'Transactional RFC'. b.) Click on the Port # for you source system. c.) Verify description & SAP R/3 versiond. RFC Destination should be one created in SM59. If non-existent then create one.
I) Type Transaction SE16. Data browser (for R/3 -> BW Connections)
Enter RSBASIDOC Print out copy of all entries in table.
II) Type Transaction SM30. Msg Types & Assignment to iDocs
Enter 'EDIMSG' in the Table/View field. Click on the 'Enter Conditions' option for Restrict Data Range. Click 'Maintain'. Select Message Type. Then enter 'RSSEND' in "From' field. Verify that the Basic Type matches what is in your RSBASIDOC table for each of your connections. If any are missing any entries you must create them as follows: Create another session and type Transaction WE30. Enter IDoc Type (ZSBAXXX) in Obj. Name field (Suggestion: Start new type with 'ZS' + Transfer Structure Prefix + (3)#'s) Select Create. Select "Create from Copy'. Enter 'RSSEND" in 'Copy From' field Enter Description (i.e. IDoc Type for BW Development) Execute (Green Check). Repeat for other missing entries.
Regards
Sangram Sutar

Error Infosource is not defined in the source system

I am extracting data into ODS. It was running perfectly till now. But today i am getting this error.and for all packages i run. whether it is transaction data or master data.
I replicated the DataSource and activated all the objects and transfer structure.but still getting the same error.
I even created a new DataSource and infosource but still the error persists. please help me in this matter.
Thanks

the data is extracted from BW system itself (Self System).
there are three tables linked to each other.I have created an infoset query and creted datasource on that infoset query.
the source system is the same bw system.
The detailed error report is -
InfoSource is not defined in the source system.
Message no. R3005
Diagnosis
The InfoSource specified in the data request, is not defined in the source system.
System response
The data transfer is terminated.
Procedure
In the Administrator Workbench of the Business Information Warehouse, update the metadata for this source system, and delete the InfoPackages belonging to InfoSources that no longer existing .

An error occurred in the source system, DBIF_RSQL_SQL_ERROR

Dear All,
last 4 days my process chain stop, now todya i activate the process chain. i found a error In 0FI_AR-4.
the error i found
Error message from the source system
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.
i already check in RSA3 , Once execute 0FI_AR_4 I Found a dump
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"BWFIR_READ_BSID_CPUDT_DATA" "(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:
How to correct the error
The exception must either be prevented, caught within the procedure
"BWFIR_READ_BSID_CPUDT_DATA"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-25153: Temporary Tablespace is Empty"
Internal call code.........: "[RSQL/FTCH/BKPF_BSID ]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"SAPLBWFIR" or "LBWFIRU10"
"BWFIR_READ_BSID_CPUDT_DATA"
please any one help on this issue
Advance in thanks
Regards
Priya

Hi,
Can you please try adding the datafile to the PSAPTEMP tablespace in the source system, and try to start the process chain again. If required you have to contact the Basis Administration. Also please find the system logs and dumps in the source system at the point of time.
Can you please let me know if it got fixed.
Thanks & Regards,
VR

'Error Occured in the Source System' for Non SAP system

Hi Gurus,
We have an Info Package which is getting the data from the Source System 'DOCP' and it has failed due to 'Error Occured in the Source System'.Since the source system is Non SAP system there is no option 'Replicate Data Sources'.So,First I activated the transfer rules by the program and ran the package again .But again the same error occured.
Please suggest me how to proceed for this error for Non SAP Systems?

Hi,
Check the RFC connection in SM59 and reactivate the source system again.
Hope this helps..
Thank you,
S R.

R/3 connection to BIW - No Idocs arrived from the source system

Question,
Hi Team,
I have issues during loading attribute data from R/3 source system to BI,
I go to the path
Data Warehousing Workbench - Modeling window. In the DataSources view, my application component Group ##. On my DataSource i Create Info Package and save it,
Later I select the following options
Full Update = select
On the Processing tab page, select only PSA.
On the Schedule tab page, choose Start Data Load Immediately and start the data load.
Till here everything is in active version and saved, and connection to the source system is active and working fine.
However when I do loading I received following messages, what I observed in Monitor window,
Data was requested OK
Request still running
Diagnosis
No errors found. The current process has probably not finished yet.
System Response
The ALE inbox of BI is identical to the ALE outbox of the source system
or
the maximum wait time for this request has not yet been exceeded
or
the background job has not yet finished in the source system.
Current status
No Idocs arrived from the source system.
When I go to detail tab, under transfer section, I receive the following message
Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
But when I actually go to PSA maintain section and select data and no of records, I can see the that data is loaded into PSA section,
But when I chose to run the transformation I donu2019t get data here,
Kindly help me to resolve this issue,
Regards,
BluSKy

Hi,
the BIW i am using , its compact BIW, which is in EXI, and i execute transaction /nrsa1 to go biw development workbench,
i am not sure about transactions settings about r/3 side,
could you plz throw some light on this issue,
regards
blusky

Refresh of BW System without deleting the source system

Hello experts
I want to know, is it possible to refresh BW system without deleting the source system.
That means I just do the renaming via BDLS and reconnect.
If I do so, do I have a post refresh activities.
According to OSS note 886102 and 184447, there are 3 scenarios:
Scenario A: You want to copy the entire system infrastructure connected by the BW source system connections (that means the entire system group).
Scenario B: You want to copy a single BW system of the group, the sourcesystem is not copied.
Scenario C: You want to replace a single sourcesystem of a BW-system with another system using a database or client copy (Example: Refresh of the OLTP consolidation system by a copy of the OLTP production system). The BW system is not copied
Assuming I use Scenario A, can I refresh BW system without deleting the source system.

Hi:
The primary source of information is the how to paper on this topic:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
YOu are correct, you can refreh the BI system without deleting the source system.
Thanks for any points you assign (after all, I wrote the paper!).
Best Regards -
Ron Silberstein
SAP

Job failing in the source system.

Hi all,
I am loading data to a data store object from a R/3 system.
The job is failing in the source system with the error - ABAP/4 processor: UNCAUGHT_EXCEPTION
Can anyone help me resolving this error?
Thanks in advance.
Regards,
Deepti.

HI,
This is very generic and seems like a short dump...can you check in ST22 in the source system and see if there is any entry for ALEREMOTE check the the error log and the step where it failed??If you can analyze it and come up with the answers then people can help you here.
Also what kind of data source it is??
Was the load full or delta??
Thanks
Ajeet

Error in the Source system while data loding through Process Chain

Hi,
I am facing issue while data loading for certain extractors through Process chain. Load of 0BPM_WIHEAD, 0BP_LOGHIST, OBPM_OBJREL, 0BPM_DEADLINES(there are 2-3 more extractors) is getting failed daily with message Error occurred in the source system and if we repeat the same it is getting executed successfully.
Regards,
Javed

Hi..
It means that the extraction job is failing in the source system..
Please check the Job log in the source system --> Copy the request nimber --> In the source system go to SM37 --> Give * then the request number......execute --> Check the Job log..
Look there may be multiple reasons behind this....
1) Connection problem : Go to SM59 and test the connection, If you don't have the access in SM59...then go to RSA1 --> Source Systems --> Right click --> Connection Parameters --> Connection Test
2) Or may be work processes are not available and due to which jobs are failing due to time out...
In both the cases you can check with the Basis Team if they can suggest something....or you can change the process chain scheduling time if possible, and schedule it in such a time when less no of jobs are running..
Regards,
Debjani..

CLIENT of the source system in the Transfer Rules

Similar Messages

Maybe you are looking for