Transports(transfer rule)Problem

Hi Experts,
Bi Patch :16   BI_CONT :8
We are moving from DEV to QA.i ve transported infoareas,infoobject catalogs and infoobjects.
now im trying to transport master data infosources UR and transfer rules.
im collecting the objects in the following manner.
Ex:0material
Grouping :in data flow before
collection mode : automatic
Here im unable see the transfer rules but UR and infosources are there.(in transport connection screen)
Conversion of logical system names
in Dev i didnt maintain any thing
in QA i ve mainted Conversion of logical system names as
*Original S S            Target S S
BI DEV                     BI QA
R3 DEV                    QA DEV
I havnt chkd the box 7.0.
Assgnment of source system to source system id
here i clicked on suggest source system ids
i ve AU and AU.
Even i did a trail with transporting the request to QA but no luck it ended with error 4,but not getting anything even info source or UR etc.........
Plz help me,suggest me solution its very urgent.
Thanks,
Yunus

hii check the foll links and award some points
Re: Transfer rule error
Re: Transfer structure problem

Similar Messages

Problem while transporting transfer rules in BW 3.5

Hi All,
I have a problem while transporting transfer rules in BW 3.5.
I have just checked the box for conversion to Transfer structure / Transfer rules of an infoobject and tried to transport it to quality. I got this below error message:
The selections T ZBW_ZBILLRATP_TEXT_BA specify more than one DataSource
Diagnosis
You need to select an individual DataSource based on the selection conditions
InfoSource =
Source System =
Object Version = T
Transfer Structure = ZBW_ZBILLRATP_TEXT_BA
although the select event is not unique.
Procedure
Check the objects to which the selection applies.
Reference to transfer structure ZBW_ZBILLRATP_TEXT_BA not available. No activation possible.
Message no. RSAR436
Diagnosis
Transfer structure ZBW_ZBILLRATP_TEXT_BA should be transported into this system.
However, no DataSource mapping refers to this transfer structure.
System response
The transfer structure was not activated or deleted.
Procedure
Ensure that DataSource mapping, with a reference to the transfer structure ZBW_ZBILLRATP_TEXT_BA is on the same transport request. Use the transport connection to create a consistent request.
Can any one provide me details of how to overcome this issue. I tried transporting all related objects.
Regards
Lakshmi

Hi Lakshmi,
Befor Transporting the Transfer rules, make sure that you are transporting the Active Versions of your Datasource & DataTarget between which your transfer rules exist.
Also make sure that the Transfer rules are active before it is transported.
Hope it helps!
Regards,
Pavan

Error when transporting transfer rules

Hi, i got an error when i transport transfer rules. i got the following errors in various transfer rules:
Mapping between data source 0CUSTOMER_ATTR and source system EMP300 is inconsistent
AND
Reference to transfer structure 0CUSTOMER_ATTR_BB not available. No activation possible.
I tried to activate the data sources and transport them several times, but i got the same errors. Checking manually i can see the data sources active in my source system, in development and productive instances.
Thanks in advance.
Diego Lombardini

Hello Diego
Do you choose the correct Transfer Structure in DEV?
I mean the one that is assigned to EMP300.
Are you saying that your PROD have the following:
0customer_text_BA
And that your DEV only have the following:
0customer_text_BB
If the answer to the above questions is YES;
Find out if some one has assigned ATTR to 0CUSTOMER directly in PROD or somebody has changed 0CUSTOMER_ATTR in DEV without transporting it to PROD.
I think that one way to resolve this problem is to use the option "overwrite origanls" in STMS.
Use it with caution and do not mass transport when you use this option.
Good luck
/FZA
Message was edited by: Fariborz Zangoui
Message was edited by: Fariborz Zangoui

Error in Transporting Transfer rule/structure to Q for generic DS

Hi,
We're in NW2004s. we're getting error when we transport Transfer Rules and Structure of generic data sources to Q.
In R3 Q the DS is active and it pulls data in RSA3 and it is replicated and all the fields are available in BW side as well, but when we transport TR/TS i still get error saying the Datasource is not active. This happens only for generic ones.
Any idea.
thanks
Mayil

Hi,
have you inserted both the transfer rule and the communication structure in the same change request?
When you transport an InfoSource, all it's dependent objects must be present in the same change request; in this way the datasource will be activated.
I hope it helps you,
Vito

Cannot transport transfer rules!

Hi,
We have a problem transporting the transfer rules from BWD to BWQ.
Here are the steps I did :
New object ZZRANK was added to user exit on R/3 dev. and transported
New infor object ZZRANK was created in BWD
ZZRANK was added as attribute to 0PLANT (mater data)
Transfers were created and comm struc updated.,
testing was successful in Dev, r3 changes were transported to Q and BWD transports to BWQ. ALL info objects transported successfull but the transfer rules failed. Cannot determine why.,
   Start of the after-import method for object type R3TR ISMP (Activation Mode)
   Mapping between data source 0PLANT_ATTR and source system PR2200LS is inconsistent
   Field ZZRANK will not be delivered from DataSource 0PLANT_ATTR in source system PR2200LS
   Mapping between data source 0PLANT_TEXT and source system PR2200LS is inconsistent
   Field KEY1 will not be delivered from DataSource 0PLANT_TEXT in source system PR2200LS
   Errors occurred during post-handling RS_AFTER_IMPORT for ISMP L
   The errors affect the following components:
      BW-WHM (Warehouse Management)
Any help is appreciated.

You may have to replicate your data source on BWQ.
First replicate and then send your transport again from BWD to BWQ.
Regards.
Sanjay
Message was edited by:
        Sanjay Sinha

Unable to transport transfer rules in BI 7(Partition in PSA)

Hi,
I want to activate T.R in Production but not able to that due to Partition in PSA.
Errors accessing partition parameters for table /BIC/B0000341000 (-> long text)
We used the programmed called RS_TRANSTRU_ACTIVATE_ALL but still the same error.
Even when we transported (T.R) from QA to PRD not able to transport to PRD with error 8.In the error analysis it is giving the same MSG u201CPSA partitionu201D
T.R: Transfer Rules
Object Type: Master data Text(0ACTIONREAS_TXT)
Thanks,
Gattu.
Thanks= Points in SDN

Laxman,
Try to repair PSA table at RSRV --> All Elementary Tests --> PSA Tables --> Consistency Between PSA Partitions and SAP Administration Information##.
After repair try to activate.
If still not working, then empty PSA data in production system (if not required...) and import transfer rules and activate if required.,
Hope it Helps
Srini

Transfer Rules problem - Version problem ?

Hello all,
I've got a "little" problem (or bug?).
I created an infosource which sends its datas to a cube.
The infosource has got datas from a datsource (TXT file) .
All was good. I could see datas on Bex...
But i wanted to change (and not create) a routine for 0CALMONTH in the transfer rule. This routine works. But when I manage the Infocube and i look at the new request, i'v got the datas of a previous request.
I clear all (PSA, demands...). And it keeps a old version of datas...
All is saved and actived!
I test to put "nothing" at 0CALMONTH (0CALMONTH <- X), i save, i active, i clear old datas, i launch infopackage, and i look at results for 0CALMONTH in the InfoCube.
And..... i still see results from the older version, and not an empty column....
So, can you help me for this problem???
Thanks.
Vince.

Hello,
Just requests and PSA were deleted.
I just want why an older version (seemed to be deteled) can appear in my results ?
I heard that "buffer" could be the cause of my disappointment.
Vince.

Activate transfer rules - problem

I was creating transfer rules for DSO 0FIGL_O02 for infosources 0FI_GL_4. Activate transfer rules bring me mistake :Data element for InfoObject BELNR 0AC_DOC_NO could not be created.
Information from log:
Data element for InfoObject BELNR 0AC_DOC_NO could not be created
Message no. RSAR274
Diagnosis
Special data elements of the type and length of the source system are required for creating the transfer structure. Errors occurred while creating a data element of this type for InfoObject BELNR 0AC_DOC_NO. The data element should be of type CHAR and length 000010. The technical name of the data element is /BIC/OW_######################.
Procedure
Check the log.
Check data element /BIC/OW_###################### in the repository. Activate data element /BIC/OW_###################### in the repository and check the activation log, if necessary.
0AC_DOC_NO - is important because this is key in DSO. This object have type CHAR and length 10. What i shoult do?

Hi,
Activate the Infoobject 0AC_DOC_NO is not recognizing by system please re-activate this once again and check the transfer rules.
Regards,
Anand Tej.

Transporting Transfer rules

Hi All
Trasnfer rules are source system specific. In development say we have created them for BW-Dev to R/3 Dev. While transporting them to production. How will we change the assignment from BWDev-R/3DEv to BWprod-R/3 Prod.
Thanks PB

You are right,
but if you want to transport anything directly to your production environment you have to build a consequent landscape...where is your problem ?
We are talkin'about source system mapping assignment, but starting from the assumption that you can do this type of transport accordingly to your landscape !
Bye,
Roberto

Urgent....Transported Update rules active version but still not active....

Hi Gurus,
i have changed a datasource and an ODSA
and this ODSA which also acts as a datamart to ODSB
so i have transported, transfer rules, transfer structure, infosource, update rules of ODSA and also the
update rules of ODSB as well
And before realsing the request into quality i have replicated the datasource from R/3 as well and then realsed this request to Quality everything is active like transfer rules, infosource, transfer structure
ODSA update rules
But the ODSB update rules are not active kindly tell how to make them active.
so again i have regenerated the export datasource and then again i transported only update rules of
ODSB.
but still the update rules are inactive, kindly someone guide me how to make them active
as i have to send this to production which is having 4 years of historical data so please kindly
help me.
thanks and regards
Harish

Hi A.H.P, vishvesh, anil, and buvanna
thankyou guys for your info and support i tried all that u have said
except activating them manually...as it is urgent i am going with manually activating
and vishvesh i could do check the update rules by basis help. thanks for that
A.H.P i have manually activated the update rules its working fine, so i am praying that everything should be fine in production as i have requested to have permissions to activate in prd as well
thankyou very much for all the support.
i am relieved that i have at last solved it
thanks and regards
harish

Transfer rules sourse system assignment change

Hi,
XAD -- Global APO system
AAD -- America APO system
GBD - Global BW system
ABD - America BW syste,
I transported, TR,Comm STru, UR from XAD to AAD
In XAD TR,Comm Str,UR pointed to GBD,
where as now i need TR,Comm Str,UR to point to ABD
when i double clieck the transported Transfer rules in AAD, i am getting error GBD doesnt exist
BDLS doesnt work here as ABD is already created in AAD
Looking for experts advise
Thanks
Praba

Hey. Do you have the system mappings maintained in AAD to convert GBD to ABD when transporting/importing updates? In the admin workbench it's just tools-conversion of logical system names. I'm guessing that's all it is. Have you ever transported from XAD to AAD? If not, I'm sure that's the issue.
Hope it's helped.

Problems in transport of Transfer rules

Hi
I am trying to transport my objects from development to production. The problems is that not all the objects are getting transported. the cubes and infoobjects are going fine but the transfer rules and communication structure are all pointing to my development source system and hence fails during transport.
How can i transport my transfer rules without specifying the source system or point to my prodcution source system?
Regards
Sujai

Source systems are not transport portable. They have to be created in your BW_PRD system.
Assuming you have the source systems created in your BW_PRD system, example R3_PRD. then you need to do the following.
In BW_DEV you have datasources mapped to your R3_DEV system. So you need to tell your BW_PRD system that any transport with a source of R3_DEV, change it to R3_PRD.
Go to your BW_PRD system, log in and go to transaction
Go to RSA1.
Then go to the menu bar and select Tools -> "Conversion of Source System names"
You may have no entries, if you do not, hit "New Entries"
Then in the "OriginalSource System" box type in the name of your development R3 system, example R3_DEV. then in the "Target Source system" type in the name of your production system, example R3_PRD.
Save, exit and re-transport all the parts.
That should do it.
I made the assumtion that you are in 2004s/BI7.0. If not go to the RSLOGSYSMAP table and do the exact same steps.
Note: This is normally a basis function, and you will need pretty elivated rights to do this in your production environment (well you should ).
Hope that helps....
Ali

Missing Transfer Rules in Selection Window for Transport

Hello,
Can somebody tell me why certain transfer rules are missing in the object selection list of the transport connection window? I am using BW 3.5.
Problem details:
I want to transport a transfer rule from a DEV box to a QA box. In the transport connection window, I clicked on "select objects" from under transfer rules in the middle panel. The object listing that followed showed only objects that start with numbers; no object we defined locally that starts with Z was included.
I also noticed that this appears to be a "funny" problem. One other computer connected to BW shows the correct listing while still another shows a different listing. Has this got to do with any setting?
Please help.
Wernel

Hi Wernel,
Its better to activate ur transfer rules once again. Also this Z* TRs would be displayed in last row of the Pop up window in the select Objects list.
or select them by grouping as before dataflow by selecting InfoSoruce.
Assign points if it helps...
Regards,
ARK

Problem in activating Transfer rules

Hi Experts,
I could not able to activate transfer rules using program "RS_TRANSTRU_ACTIVATE_ALL" by giving source system name and Infosource in Quality system.I am getting success status "No Transfer Structure Selected" but still transfer rules are in inactivate.I tried replicating data sources also still problem persists.
Please provide any suggestion how can i go about it.
Edited by: Sunilbm on Oct 30, 2009 12:16 PM

Hi,
Is there any error message when the transfer rules are transported from Dev to Quality?
Are the transfer rules transported from Dev to Quality successfully.
Post the message if any when the transport request is moved from Dev to Quality.
Regards,
Rama Murthy.

System copy problem...No transfer rules available

Hi ,
We are facing a problem in getting the Transfer Rules...
1.we did a system copy from PRD system and created a Sandbox system .
2.After the system copy the problem came from the source system.....i.e for the datasource's in the table RSOLTPSOURCE the mapping is showing for 2 systems....CRM PRD system & CRM SANDBOX system....
3.Coz of this issue the Transfer rules are not available and the all the DS are inactive......
4.I tried with the FM RS_TRANSTRUC_ACTIVATE_ALL but im getting message as no transfer structure is available.
5.When i tried to manually activate the DS from BW side it is asking to create TRANSFER RULE.
Please help me to sort it out.....
Thanks in Advance
BASKAR

HI ,
I also raised a OSS to SAP ....what they suggested is....
According the logs in BWS there was definitely a systemcopy from BWP to BWS, but the BDLS logs looks very strange, which actually did not converted anything, because the administration tables containing some very strange entries.
Lets take the datasource 0crm_sales_act_1 for example. If you check this datasource in table RSOLTPSOURCE you can see, that it exists currently for both source systems:
OLTPSOURCE LOGSYS OBJVERS
0CRM_SALES_ACT_1 CMPCLNT501 A
0CRM_SALES_ACT_1 CMSCLNT501 A
Unfortunately the root cause of this is unkown, but most probably it is caused by an improper copy procedure, where the consulting note
886102 was not followed.
To solve the problem, please follow the below steps:
1. Implement note 1405233 and 1336119 to your system 2. Go to RSA1 and delete the source System CMS.
3. With function module rsar_logical_system_delete delete the source system CMP:
I_LOGSYS CMPCLNT501
I_FORCE_DELETE X
I_NO_TRANSPORT X
I_NO_AUTHORITY X
4. In your productive BW (BWP) please create a transport request which contains all the source system dependent objects for CMP. Please check note 886102 scenario B3 step 2 for details.
5. In BWS, please recreate the source system to CMS and activate it but please do not replicate the datasources yet.
6. In BWS please maintain the table RSLOGSYSMAP and map CMP to CMS and import the transport request created in step 4.
Please be aware, that such a constellation happens mostly, if some steps are missed or are not carried out properly from consulting note 886102. Please get in touch with your basis colleagues and provide them this note, so the next time such a problem does not occur.
I hope this helps to solve the problem.
Thanks
BASKAR

Transports(transfer rule)Problem

Similar Messages

Maybe you are looking for