BW standard transport

Hi,
Which is better... standard transport switched off in BW or switched on? If it is switched off how will we move the work done in one environment to another? Could someone help me what is the main use... so that i can understand this.
~rahul

Hi Rahul,
Using the standard transport system in a BW system is a little problematic, or in SAP words: "The standard transport system doesn't take into account specific BW functionality". This means that due to locking problems, you won't be able to save (and change) different queries in different change requests if they use the same calculated/restricted key figure for example.
I'm not familiar with the option that Mike mentioned ('at this point you have the option to enter a transport request or skip it'). We use BW 30B and if I'll choose to skip the step that saves the changes in a change request I'll loose all the changes (there's no $TMP or Bex transport option).
So, as I see it, you don't really have the option to use the 'standard' method (for BW <=30B) since it does not work for BW objects.
btw, if anyone knows I'm wrong or knows that the problem solved as of NW4, I'll be more than happy to hear since we could really use this method.
Shiri

Similar Messages

Error in Query View Saving -The standard transport system is active.You can

Hi,
I have a query in Dev system which is moved to production and i am able to edit the query in dev.But my problem is when i tried to create a view on that query and save the view, it is throwing me a error
"The standard transport system is active.You cannot save"
Any pointers on this.
Regards,
Pra

Hi
Did you get any feedback on this one?? Im facing the same message when saving a query view..
Thanks
Willem

Error in Portal: The Standard transport system is active.You cannot save

Hi Experts
In Portal,I am trying to save a BW Query as view in 'Favorites' or 'BEx Portfolio' or 'My Portfolio',I can't able to save it as i am getting
"The Standard transport system is active.You cannot save" msg
Please update me what is the reason and how to resolve this error
Thanks in advance

Hi,
SAP Note : 356018 might be handy.
Regards,
Sandeep Tudumu

ChaRM: Standard transport layer

Hi!
I have one question regarding transport layers for usage of ChaRM.
Which standard transport layer does the ChaRM need?
a) "SAP" transport layer
2) standard transport layer "ZDEV"
What will happen when one of this (SAP or ZDEV) will be mised or used outside of ChaRM?
Thank you very much!
regards
Thom

Thom Heinemann wrote:>
>
> Which standard transport layer does the ChaRM need?
> a) "SAP" transport layer
> b) standard transport layer "ZDEV"
Anand: ZDEV should be the standard transport layer......
All SAP standard objects will only follow SAP transport layer......irrespective of whatever standard layer is mentioned.....
> What will happen when one of this (SAP or ZDEV) will be mised or used outside of ChaRM?
Anand: Little more clarity is desired on this query....can you please be more specfic about what you meant..
Inspire ppl by rewwarding !!
Regards,
Anand....

The standard transport system is active. BI querry on Poral

Hi All,
I am getting the error when saving the querry in BI ie when I click "Save As" button a dialog window opens and in "favourite" tab
i give description (any text ) and click Ok button. Then i get the following error :
The standard transport system is activeYou cannot save
This is carried out in portal.
Please help
Regards

Hi,
It's mentioned the activity of saving BI Query is carried out in Portal, so am assuming you might be using a BEx Web application for this.
If yes, then would suggest you to try once after switching off the standard transport. And instead use BEx transports in Admin workbench.
My understanding can be completely wrong, in which case request you to provide more details on the environment and the steps done.
Thanks,
Swapna Priya.

Warning "Standard Transport System is Active"

I have just installed the 710 GUI patch 11 and the 801 patch on the BI 7 tools. When I run the Report Designer or Web Application Designer against our development BI system, I get the following warning: "Standard Transport System is Active. SAP GUI connection is not activated for current connection to BI system. Do you want to reconnect to BI system and activate SAP GUI connection?" A connection dialog box appears and I put my credentials in and am connected.
Does anyone know why this warning appears on on certain systems and with certain tools? For example, I do not receive this warning running these tools against our QA BI system. How can I "fix" it so it no longer requires a second log in? I thought it was in the config on the BI side but my BI guy says "no, it's a GUI issue".
Thank you!
Jodi

Bex Pop up message - Standart transport system active - how to supress
Regards.

BEx Standard Transport Request

Dear Experts,
I have 2 questions for BEx Standard Transport Request.
Could I create more than one BEx Standard Transport Request?
For example, I create a BEx Standard 1 Transport Request for Query A.
I also create a BEx Standard 2 Transport Request for Query B.
Is it possible?
If not, could you kindly tell me the difference between standard BEx transport request & common transport request?
Thanks and best regards
Alex yang

The Bex standard transport collects changes in queries, a standard transport can transport anything.
Once a query has had a package assigned to it and transported, it can't be changed in the dev environment without a Bex transport assigned. In a multiple developer enviroment, people end up transporting incomplete changes from other developers.
A common solution is to make the changes, release the Bex transport without moving it to next system, and recollecting the query in the transport collector and transporting ONLY the query selected.
John Hawk

Activating the standard transport system in BI Dev system.

Hello All,
We have a debate going on like whether we need to activate the standard transport system or not in BW Development.
Our user is asking to enable some functionality from a Web Template using the
Save As command. This command enables a user to slice a report and
then save this view as a Portal Favorite. This functionality appears to be
blocked when the transport system is active(Switched on) but he is able to save it when transport system is switched off.
I know that it has to be switched on in order to collect the changes in transport requests in Dev other wise will be collected as Local obects in $TMP.
Also let me know the pros and crons of activating the transport system.
Appreciate if you could throw some light on this and solution to the above problem.
Regards,
Hari

Hi,
It's mentioned the activity of saving BI Query is carried out in Portal, so am assuming you might be using a BEx Web application for this.
If yes, then would suggest you to try once after switching off the standard transport. And instead use BEx transports in Admin workbench.
My understanding can be completely wrong, in which case request you to provide more details on the environment and the steps done.
Thanks,
Swapna Priya.

Can any bady send me the standard transportation (configuration) doc.

Please send me the standard transportation configuration step by step doc.

Hi Goutam,
Create Shipment Document
Use
After the status of the delivery is open for transportation planning, it is possible to create a shipment document to schedule the transportation.
Logistics  Logistic Execution  Transportation Transportation Planning  Create  Single document
T.code: VT01n
Enter your transportation planning point and shipment type. Press enter.
Creating the shipment cost document
Use
After the deliveries are scheduled by shipment and the shipment is executed, now it is time to maintain and close the shipment document in order to record all relative information and ready for the shipment cost settlement.
Logistics  Logistic Execution  Transportation Shipment cost  Create  Single document
T.code: VI01.
After creation of shipment cost doc. You settle the Shipment cost.
Go to VI02, enter shipment cost no.and press enter.
Then go to Overview -- Fright cost items, Select hte line item and double click it.
Go as main menu: Itme --> Acc. assignment, You enter G/L acc. and cost center to which the transportation cost will be posted.
On the Standard change, details Freight cost items screen, then check the check box Transfer, which means you will transfer the relative transportation cost to FI/CO, in this case, the system should determined which Purchase Order will used to settle the cost, so after you check the Transfer check box.
Press save button on the current screen.
Shipment cost settlement and documents:
Use
After the shipment cost settled in shipment cost document, it has the following affects:
It creates a service entry sheet that refers to the purchase order determined.
It posts acceptance of services performed.
It creates an accounting document for the accruals.
Further subsequent documents are created in FI.
Reward points if it helpful
Regards
Govind.

Fixing standard transport import job

Hi,
We have R/3, APO and B/W.
In R/3 and APO, when we move batches of transports from QA to Staging(STMS_QA) everything is fine.
But in the past we sometime experimented problem when doing the same in B/W. Somebody once told us that when you move many transports together, the standard import job perform first step for all transports then 2nd step for all of them, etc......
This is no problem for R/3 and APO, but we were told that does not always work in B/W. Because of that, we change our process for B/W. We run STMS_QA and the import job, one transport after the other. Since the import job is scheduled every 15 minutes, if we have 8 transports to move, it will take 2 hours to perform them all.
I was ask to write a job that would do this automatically, then replacing the standard import job.
Then I'm saying to myself: we are not the only ones to move transports in batch in the world? Do everybody reinvent the wheel each time like I am about to do?
Can somebody give me some thought over this? Any suggestion?
Thank you!

Discussion successfully moved from SAP Transportation Management (SAP TM) to SAP NetWeaver Administrator where it belongs.
Your recent question posted in SCN SAP Transportation Management community is in the wrong place. SAP TM is devoted to the SAP application which manages the physical movement of goods using trucks, trains, planes, and ships. What you posted regarding software changes from one system to another (Dev to QA, for example) should be in the Netweaver Administrator community. Please use the correct community in the future.
Regards, Mike (Moderator)

Transport an Query without the standard transport system

Hello Experts,
is there a function (similar to the report-painter-reports) to transport a query via pc to an other system?

Jurgen,
As pointed out , it is not possible to transport from production to another system without using the transports , however the query would be under a request in production , you could then use that request to transport the query into another system either by specifying a transport connection or manually importing the data and co files...
Arun
Hope it helps...

No request has been set up as the standard transport request for BEx object

Hi gurus,
I have this error in a query . Have someone any ideea what is this?
Thanks,
Ramona

Hi,
Before you create a query you have to assign a global request to Bex application.
To do this goto Transport connection of RSA1, In the tool bar you will see a icon Bex (Create transport request for Bex). Assign a request for it. After doin so, you error will be resolved.
-- Selva

Standard BEx transporting Request

Hi Dudes,
Can u explain me with a scenario, what is this Standard BEx Transporting Request and what is the purpose of this,
Thankyou.

Hi,
This is what note says:
Symptom
Editing of a query in Query Designer may return the various error messages concerning transport system. Query or query component can not be changed or saved.
The following error messages are possible:
'Query could not be saved due to a problem in transport' message R9 124;
'BEx Transport Request XXX... is not available or not suitable. Choose an existing request';
'Object ELEM XXX... could not be saved to order YYY...';
'A dependent object is being locked by the transport system' message R9 113
'The dependent objects are in different transport orders' message R9 114;
'The upgrade is already running - you are not able to change objects'.
In some particular cases using NW 2004s server with 3.x Query Designer
'Operation failed, no message available from server'.
Other terms
Query, Query Designer, Correction and Transport System, CTS, ELEM, Transport Request, Changeability.
Reason and Prerequisites
The error messages rise as the result of wrong administration of Correction and Transport System (CTS).
Transport System Mode
Two main modes of Transport System can be used for BW system: Standard Transport System and BW Transport System. Both modes require different administration efforts.
Standard Transport System (system default)
Within this mode an assignment of newly created query elements is done during save procedure. System asks for appropriated Package and corresponding Transport Request within this Package. The mode allows separating of changes done in the system different users in different Transport Requests. Users must be authorized to create new Transport Requests or to write into existing Transport Requests.
BW Transport System (recommended for handling of BEx objects)
Within BW Transport System initial assignment of newly create query elements is done automatically to $TMP Package. This is a Package for temporary objects and does not require modifiable Transport Request. Changes of those query elements can be done without further restrictions. Further assignment to a Package and corresponding Transport Request can be performed using Transport Connection of Administrator Workbench (transaction RSA1).
All kinds of changes for query elements which already have been assigned to any Package different from $TMP (for example, queries transported from another system) must be registered in so-called Standard BEx Request. Using Standard BEx Request all changes done to query elements can be also transported to any other system. If the old Standard BEx Request has been released, another one must be created immediately in order to allow further changes for query elements.
The typical reason for error messages listed above is a situation when NO Standard BEx Request is available anymore in the system. The algorithm of query SAVE contains a transport systems check. If the transport system check fails, no changes are possible.
Changeability of query elements
The recommended setting for query element (ELEM) is 'Everything Changeable'. Using of other settings, like 'Original Changeable' or 'Nothing is Changeable', will make editing of objects not possible when the general system changeability will set to 'not changeable' (SCC4).
Setting 'Original Changeable' allows changes only for query elements which have been created in this particular system. Quite often an ordinary query may contain, for example, variables or other reusable components created in the other systems. In this case changing of a query containing those objects will be not possible.
Changeability of Package
Package (Development Class) where the corresponding Transport Request has to be created must be changeable. If a Package has a property 'Package is not extendable' set to true, no requests can be created within this Package. This means no objects can be registered.
Solution
The following messages mainly happen if BW Transport System is activated. The existence of Standard BEx Request and correct settings for object changeability should be checked.
'Query could not be saved due to a problem in transport';
'BEx Transport Request XXX... is not available or not suitable. Choose an existing request';
'Operation failed, no message available from server'.
How to create a new Standard BEx Request?
Start Administrator Workbench (RSA1) --> Transport Connection. Find button BEx. Under the button user is able to create/assign a new Standard BEx Request.
How to check Changeability of object?
Start Administrator Workbench (RSA1) --> Transport Connection. Find button 'Object Changeability'. Set property 'Everything changeable' for query elements (ELEM).
How to check Changeability of Package?
Start transaction SE80 --> select corresponding Package --> find properties dialog. Check whether the property 'Package is not extendable' is set to false. Assignment of query elements (R3TR ELEM) to a corresponding Package is stored in the table TADIR (field DEVCLASS). In order to obtain a list of query elements used in a definition of a particular query having problems use the function RSZ_X_COMPONENT_GET with the I_OBJVERS = 'A', I_COMPID = technical name of a query. Execute the function and copy all elements (ELTUID) from the exporting table C_T_ELTDIR. Use this selection as the input parameter for selection from TADIR table (field OBJ_NAME). Collect all Packages and check the changeability as described above.
The following messages mainly happen if Standard Transport System is activated. The problem happens in case, when one or several objects from definition of a particular query have been already written in another modifiable Transport Request. In BW 3.x each object can be processed only within one Transport Request.
'Object ELEM XXX... could not be saved to order YYY...';
'A dependent object is being locked by the transport system';
'The dependent objects are in different transport orders';
The situation may happen, for example, if a Query A contains a variable which has been already used in another Query B assigned to different Transport Request. In this case, saving of Query A will be not possible while the Transport Request containing the shared variable is not released.
How to find an assignment of object to a Transport Request?
Start transaction SE03 and select 'Search for objects in requests/tasks'. Provide ELTUID of the element which can not be saved. Object type is R3TR ELEM. Search for modifiable Transport Requests containing this element. If corresponding Request is found, it can be released. After that is will become possible to save this query element into another Request.
Changing of query elements during running upgrage is not possible. The system sets a global lock in order to prevent any change which may potentially affect the consistency of objects. In such situation users should stop the upgrade procedures and wait until the process will finish.
Regds,
Shashank

Transport

Hi All,
I have completed of creating objects and testing in development for a project.
I have created infoobjects, infosources, ods's and cubes and now i have to send them to quality system.
i have a task before sending them.It is to organize the objects in a specific packages and requests.
can we change the package and request no for an object?
can we keep all the infoobjects in one request and in one package and similarly to infosources , ods's and cubes?
if yes, how?
is there any procedure to follow when transporting them into the quality?like sequence etc...
and what is the procedure to follow?
Kindly explain in detail of this procedure..
Thanks and Regards,
Pooja

hi,
select any one of the object example infocube, double click on the infocubeselect extra's menuthen select write transport request--there you can change the package name and save under it.
you can do it for all the object's like this.
standard transportation steps follows
*RSA1-> Transport Connection
*Select SAP Transport Folder.
*Choose your respective objects(It can be Infobjects, infoproviders or infosources)
*Drag and drop the objects which need to be transported to the right hand side of
collected objects
*click on truck icon(Transport Objects)
*Specify the package name
*save
*A new request would be created(if not create a new request )
*goto se09
*search for the request number that is created
*release
In general sequence ...
1. Info object
2. Infosource,transfer rule
3. Data Target,info provider
4. Update rules
5. queries
6. Webtemplates,workbooks
7. Roles
hope this help you
regards
harikrishna N

HELP for all 5 TYPES of STO Stock Transport Orders with detailed scenario

PLEASE help me understanding the detailed scenarios for all 5 TYPES of STO s
as in my day to day job activities , i frequently handles issues related to STO s
PLEASE HELP WITH DETAILED STEP BY STEP SCENARIOS

Hi Jagatram,
Standard SAP has the following methods For Stock transport order:
1) One Step Transfer stock without using purchasing documents; Use movement type 301.
2) Two Step Transfer stock without using purchasing documents; Use movement type 303 in Supplying plant and movement type 305 in receiving plant.
3) Using Standard Transport Order (STO) without delivery in two steps. STO created in T-Code ME27, receiving plant posts goods issue (for returns), movement type 351 and supplying plant post goods receipt from using movement type 101.
4) Using Standard Transport Order (STO) with delivery in one step. STO created in T-Code ME27, Receiving plant creates shipment and Goods issue document (for materials to be returned) with movement type 647 and goods receipt document with movement type 101 both created in one step.
5) Using Standard Transport Order (STO) with delivery in two steps. STO created in T-Code ME27, Receiving plant creates shipment and Goods issue posted (for materials to be returned) with movement type 641.Goods receipt is posted in the supplying plant, movement type 101.
6) Using Transportation scheduling agreement (TSA) with delivery in two steps. TSA created in T-Code ME37. Receiving plant creates shipment and Goods issue document (for materials to be returned) with movement type 641. Goods receipt is posted in the supplying plant, movement type 101.
To achieve it, necessary configurations has to be done in Tcode- OMGN.
SPRO>> Materials management>> Purchasing>> Purchase Order>> Set up Stock transport Order:
1. Plant: For the receiving plant, maintain customer No-Plant (If using STO with delivery), for the Sales Org, Dist channel and Division.
2. Checking Rule: Create checking rule.
3. Define checking rule : Usually no change required here.
4. Assign delivery type/checking rule: Assign the document type(UB) - Supplying plant- Delivery type(NL).
5. Purchasing document type: Maintain the supplying plant- Receiving plant relationships for the doc type-UB, either 1-step or 2-step, as per business.
Hope this helps!
Regards,
Shilpa

BW standard transport

Similar Messages

Maybe you are looking for