HOW MANY TYPES OF transportable requests?

Hi,
In R/3 Release 4.0, SAP has introduced the Change and Transport System (CTS), comprising the following tools:
1. Change and Transport Organizers(CTO)
2. Transport management system(TMS)
The Change and Transport Organizer (CTO) provides functions for organizing software development projects. It is designed to support projects of all sizes, whether they are carried out centrally or in a distributed environment.
The Transport Management System (TMS) organizes, monitors, and performs transports for allR/3 Systems within a system landscape. In addition, TMS is used to configure and manage the setting up of R/3 Systems and transport routes within a system landscape.
The Transport Management System (Transaction STMS) enables you to:
1. Define an R/3 System's role within a system landscape or transport domain
2. Configure the transport routes using either a graphical editor or hierarchical editor
3. Configure the transport tool transport control program tp.
4. Display the import queues of all R/3 Systems in the transport domain
5.Decide whether the quality assurance testing was successful in the QA System
6.Start the import of change requests in an import queue
The transports request can be of two types :
1. Customizing
2. Workbench
Customizing adapts the R/3 software to meet a company's individual business requirements by setting up the business transactions the company requires in R/3. Most Customizing is client-specific and affects only a particular client.
Workbench - Development changes are saved to Workbench change requests. Workbench change requests concern changes to R/3 Repository objects, such as ABAP programs, screens, data dictionary objects and global documentation.
To access the Workbench Organizer, use Transaction SE09
For more details go through the following link :
http://help.sap.com/erp2005_ehp_03/helpdata/EN/57/38e1824eb711d182bf0000e829fbfe/frameset.htm
Thanks,
Nitesh Jain

Similar Messages

How many types of requests are there

hai,
how many types of requests are there plz explain it plzzzzzzzzzzz
thanks and regards,
pg babu

Hi ,
We are not at all clear about your query here. Please let us know what kind of requests you are telling about. Is it regarding data base requests?
Regards,
Abhisek

How many types of Queues exists and how to identify them.

Hello
can anyone say How many types of Queues exists and how to identify them.
What does R3R* and CSA* stands for.
Regards,
divya

Hi Divya,
The queues R3* and CSA* that you have specified are qRFC queues. qRFC queues are data queues which transport data to and fro different systems.
There are also the tRFC queues which are triggered whenever you make RFC calls to connect to another system.
Queues with prefix R3AD* - for delta download from R3->CRM
Queues with prefix R3AU* - for data upload from CRM->R3
Queues with prefix R3AR* - used to transfer data during request load from R3->CRM
Queues with prefix R3AI* - for initial load from R3->CRM
Queues with prefix CSA* - these are validation object specific queues used for processing/persisting data in CRM tables in a serialized manner. E.g. CSABUPA* for business partner,CSA_ORDER* for sales order etc.
You can administer and monitor the queues in trax. SMQR,SMQS.
Hope this helps you! Pls. do not forget to reward me some points.
Regards,
Sudipta.

How to track the transport request number for the Role/Composit Role

Hi,
How to track the transport request number for the Role/Composit Role.
Thanks,
Ravi

Use transaction SE03 Transport Organizer Tools
Execute "Search for Objects in Requests/Tasks" with objects of types:
R3TR ACGR Role
R3TR ACGT Role - User assignment
Regards

How to create a transport request with query and only with its structure.

HI guru,
how to create a transport request with query and only with its structure.transport request should not include any other query items like ( variables, conditions...etc)
thanks in advance.
venkata

Hi,
Goto RSA1 and then Transport Connection -> In SAP Transports select Object Types-> Query Elements -> Then select Query->Give Technical name of the query and then select for transfer. In the right side you can choose the components which you wanted to transport.
Regards,
anil

How many types of dunning not levels

hi how many types of dunnig

Hi
Dunning is a reminder to the customer or vendor to make payment on outstanding invoices. It typically consists of a letter that summarizes the invoices that are past due and politely requests payment to be made. When you customize dunning you have to create dunning area like at what level you want to use the dunning, like business area level or company code level. After that you have to make settings for dunning procedure, in that you have to define no of due dates and no of dunning levels. there are maximum 9 levels are there.
the dunning wizard keeps track of a customeru2019s u201Cpayment behavioru201D in the database to deliver this important information to appropriate organizations.
The dunning system covers the following documents:
·        Open A/R invoices, including invoices that are partially credited or partially paid
·        Invoices that include installments
·        A/R credit memos
·        Incoming payments that are not based on invoices
with regards,
ramanuja chary

How many types of rfcs are there

Hello,
Can any body explain about how many type of rfcs are there. give the difference also.
Thanks.

Hi,
Check this info.
These are the types of RFC
Asynchronous RFC (aRFC)
Synchronous RFC (sRFC)
Transactional RFC (tRFC)
Queued RFC (qRFC)
Parallel RFC (pRFC)
Asynchronous RFC :
This is used when you need to increase the performance of ABAP program by having system call more than one function module in parallel than forcing the program to wait for results .
Transactional RFC
This let you group one or more function module call together o tRFC LUW and ensure that fucnction module within LUW is called once . In contrast to aRFC and sRFC the tRFC belonging to tRFC LUW are executed in order .
tRFC is always used if a function is executed as a Logical Unit of Work (LUW). Within a LUW, all calls are
1.Executed in the order in which they are called
2.Executed in the same program context in the target system
3.Run as a single transaction: they are either committed or rolled back as a unit.
Implementation of tRFC is recommended if you want to guarantee that the transactional order of the calls is preserved
Asynchronous remote function calls (aRFCs) are similar to transactional RFCs, in that the user does not have to wait for their completion before continuing the calling dialog. There are three characteristics, however, that distinguish asynchronous RFCs from transactional RFCs:
When the caller starts an asynchronous RFC, the called server must be available to accept the request.
The parameters of asynchronous RFCs are not logged to the database, but sent directly to the server.
Asynchronous RFCs allow the user to carry on an interactive dialog with the remote system.
The calling program can receive results from the asynchronous RFC.
You can use asynchronous remote function calls whenever you need to establish communication with a remote system, but do not want to wait for the functions result before continuing processing. Asynchronous RFCs can also be sent to the same system. In this case, the system opens a new session (or window). You can then switch back and for between the calling dialog and the called session
RECEIVE RESULTS FROM FUNCTION Remotefunction is used within a FORM routine to receive the results of an asynchronous remote function call. The following receiving parameters are available:
IMPORTING
TABLES
EXCEPTIONS
The addition KEEPING TASK prevents an asynchronous connection from being closed after receiving the results of the processing. The relevant remote context (roll area) is kept for re-use until the caller terminates the connection.
Transactional RFC (tRFC) and Queued RFC (qRFC).
tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).
Transactional RFC:
If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.
To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.
Disadvantages of tRFC
- tRFC processes all LUWs independent of one another. Due to the amount of activated tRFC processes, this procedure can reduce performance significantly in both the send and the target systems.
- In addition, the sequence of LUWs defined in the application cannot be kept. Therefore, there is no guarantee that the transactions are executed in the sequence dictated by the application. The only guarantee is that all LUWs are transferred sooner or later.
Queued RFC:
When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously
Therefore, Queued RFC is better than Transactional RFC.
Remote Function Call:
RFC is an SAP interface protocol. Based on CPI-C, it considerably simplifies the programming of communication processes between systems.
RFCs enable you to call and execute predefined functions in a remote system - or even in the same system.
RFCs manage the communication process, parameter transfer and error handling.
http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.
Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
Synchronous RFC:
The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on synchronous communication, which means that the systems involved must both be available at the time the call is made.
Transactional RFC (tRFC) and Queued RFC (qRFC). tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).
Transactional RFC:
If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.
To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.
Queued RFC:
When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously
For more information on RFC, please go through the link.
http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
Have a look at this link.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.
Rewords some points.
Rgds,
P.Nag

How many types of joins are there?

how many types of joins are there?
Edited by: Alvaro Tejada Galindo on Feb 21, 2008 4:58 PM

Hi,
Joins are used to fetch data fast from Database tables:
Tables are joined with the proper key fields to fetch the data properly.
If there are no proper key fields between tables don't use Joins;
Important thing is that don't USE JOINS FOR CLUSTER tableslike BSEG and KONV.
Only use for Transparenmt tables.
You can also use joins for the database VIews to fetch the data.
JOINS
... FROM tabref1 INNER JOIN tabref2 ON cond
The data is to be selected from transparent database tables and/or views determined by tabref1 and tabref2. tabref1 and tabref2 each have the same form as in variant 1 or are themselves Join expressions. The keyword INNER does not have to be specified. The database tables or views determined by tabref1 and tabref2 must be recognized by the ABAP Dictionary.
In a relational data structure, it is quite normal for data that belongs together to be split up across several tables to help the process of standardization (see relational databases). To regroup this information into a database query, you can link tables using the join command. This formulates conditions for the columns in the tables involved. The inner join contains all combinations of lines from the database table determined by tabref1 with lines from the table determined by tabref2, whose values together meet the logical condition (join condition) specified using ON>cond.
Inner join between table 1 and table 2, where column D in both tables in the join condition is set the same:
Table 1 Table 2
A B C D    D E F G H
a1 b1 c1 1    1 e1 f1 g1 h1
a2 b2 c2 1    3 e2 f2 g2 h2
a3 b3 c3 2    4 e3 f3 g3 h3
a4 b4 c4 3    -
Inner Join
A B C D D E F G H
a1 b1 c1 1 1 e1 f1 g1 h1
a2 b2 c2 1 1 e1 f1 g1 h1
a4 b4 c4 3 3 e2 f2 g2 h2
Example
Output a list of all flights from Frankfurt to New York between September 10th and 20th, 2001 that are not sold out:
DATA: DATE LIKE SFLIGHT-FLDATE,
CARRID LIKE SFLIGHT-CARRID,
CONNID LIKE SFLIGHT-CONNID.
SELECT FCARRID FCONNID F~FLDATE
INTO (CARRID, CONNID, DATE)
FROM SFLIGHT AS F INNER JOIN SPFLI AS P
ON FCARRID = PCARRID AND
FCONNID = PCONNID
WHERE P~CITYFROM = 'FRANKFURT'
AND P~CITYTO = 'NEW YORK'
AND F~FLDATE BETWEEN '20010910' AND '20010920'
AND FSEATSOCC < FSEATSMAX.
WRITE: / DATE, CARRID, CONNID.
ENDSELECT.
If there are columns with the same name in both tables, you must distinguish between them by prefixing the field descriptor with the table name or a table alias.
In order to determine the result of a SELECT command where the FROM clause contains a join, the database system first creates a temporary table containing the lines that meet the ON condition. The WHERE condition is then applied to the temporary table. It does not matter in an inner join whether the condition is in the ON or WHEREclause. The following example returns the same solution as the previous one.
Example
Output of a list of all flights from Frankfurt to New York between September 10th and 20th, 2001 that are not sold out:
DATA: DATE LIKE SFLIGHT-FLDATE,
CARRID LIKE SFLIGHT-CARRID,
CONNID LIKE SFLIGHT-CONNID.
SELECT FCARRID FCONNID F~FLDATE
INTO (CARRID, CONNID, DATE)
FROM SFLIGHT AS F INNER JOIN SPFLI AS P
ON FCARRID = PCARRID
WHERE FCONNID = PCONNID
AND P~CITYFROM = 'FRANKFURT'
AND P~CITYTO = 'NEW YORK'
AND F~FLDATE BETWEEN '20010910' AND '20010920'
AND FSEATSOCC < FSEATSMAX.
WRITE: / DATE, CARRID, CONNID.
ENDSELECT.
Since not all of the database systems supported by SAP use the standard syntax for ON conditions, the syntax has been restricted. It only allows those joins that produce the same results on all of the supported database systems:
Only a table or view may appear to the right of the JOIN operator, not another join expression.
Only AND is possible in the ON condition as a logical operator.
Each comparison in the ON condition must contain a field from the right-hand table.
If an outer join occurs in the FROM clause, all the ON conditions must contain at least one "real" JOIN condition (a condition that contains a field from tabref1 amd a field from tabref2.
In some cases, '*' may be specified in the SELECT clause, and an internal table or work area is entered into the INTO clause (instead of a list of fields). If so, the fields are written to the target area from left to right in the order in which the tables appear in the FROM clause, according to the structure of each table work area. There can then be gaps between table work areas if you use an Alignment Request. For this reason, you should define the target work area with reference to the types of the database tables, not simply by counting the total number of fields. For an example, see below:
Variant 3
... FROM tabref1 LEFT OUTER JOIN tabref2 ON cond
Effect
Selects the data from the transparent database tables and/or views specified in tabref1 and tabref2. tabref1 und tabref2 both have either the same form as in variant 1 or are themselves join expressions. The keyword OUTER can be omitted. The database tables or views specified in tabref1 and tabref2 must be recognized by the ABAP-Dictionary.
In order to determine the result of a SELECT command where the FROM clause contains a left outer join, the database system creates a temporary table containing the lines that meet the ON condition. The remaining fields from the left-hand table (tabref1) are then added to this table, and their corresponding fields from the right-hand table are filled with ZERO values. The system then applies the WHERE condition to the table.
Left outer join between table 1 and table 2 where column D in both tables set the join condition:
Table 1 Table 2
A B C D    D E F G H
a1 b1 c1 1    1 e1 f1 g1 h1
a2 b2 c2 1    3 e2 f2 g2 h2
a3 b3 c3 2    4 e3 f3 g3 h3
a4 b4 c4 3    -
Left Outer Join
A B C D D E F G H
a1 b1 c1 1 1 e1 f1 g1 h1
a2 b2 c2 1 1 e1 f1 g1 h1
a3 b3 c3 2 NULL NULL NULL NULL NULL
a4 b4 c4 3 3 e2 f2 g2 h2
Example
Output a list of all custimers with their bookings for October 15th, 2001:
DATA: CUSTOMER TYPE SCUSTOM,
BOOKING TYPE SBOOK.
SELECT SCUSTOMNAME SCUSTOMPOSTCODE SCUSTOM~CITY
SBOOKFLDATE SBOOKCARRID SBOOKCONNID SBOOKBOOKID
INTO (CUSTOMER-NAME, CUSTOMER-POSTCODE, CUSTOMER-CITY,
BOOKING-FLDATE, BOOKING-CARRID, BOOKING-CONNID,
BOOKING-BOOKID)
FROM SCUSTOM LEFT OUTER JOIN SBOOK
ON SCUSTOMID = SBOOKCUSTOMID AND
SBOOK~FLDATE = '20011015'
ORDER BY SCUSTOMNAME SBOOKFLDATE.
WRITE: / CUSTOMER-NAME, CUSTOMER-POSTCODE, CUSTOMER-CITY,
BOOKING-FLDATE, BOOKING-CARRID, BOOKING-CONNID,
BOOKING-BOOKID.
ENDSELECT.
If there are columns with the same name in both tables, you must distinguish between them by prefixing the field descriptor with the table name or using an alias.
Note
For the resulting set of a SELECT command with a left outer join in the FROM clause, it is generally of crucial importance whether a logical condition is in the ON or WHERE condition. Since not all of the database systems supported by SAP themselves support the standard syntax and semantics of the left outer join, the syntax has been restricted to those cases that return the same solution in all database systems:
Only a table or view may come after the JOIN operator, not another join statement.
The only logical operator allowed in the ON condition is AND.
Each comparison in the ON condition must contain a field from the right-hand table.
Comparisons in the WHERE condition must not contain a field from the right-hand table.
The ON condition must contain at least one "real" JOIN condition (a condition in which a field from tabref1 as well as from tabref2 occurs).
Note
In some cases, '*' may be specivied as the field list in the SELECT clause, and an internal table or work area is entered in the INTO clause (instead of a list of fields). If so, the fields are written to the target area from left to right in the order in which the tables appear in the llen in der FROM clause, according to the structure of each table work area. There can be gaps between the table work areas if you use an Alignment Request. For this reason, you should define the target work area with reference to the types of the database tables, as in the following example (not simply by counting the total number of fields).
Example
Example of a JOIN with more than two tables: Select all flights from Frankfurt to New York between September 10th and 20th, 2001 where there are available places, and display the name of the airline.
DATA: BEGIN OF WA,
FLIGHT TYPE SFLIGHT,
PFLI TYPE SPFLI,
CARR TYPE SCARR,
END OF WA.
SELECT * INTO WA
FROM ( SFLIGHT AS F INNER JOIN SPFLI AS P
ON FCARRID = PCARRID AND
FCONNID = PCONNID )
INNER JOIN SCARR AS C
ON FCARRID = CCARRID
WHERE P~CITYFROM = 'FRANKFURT'
AND P~CITYTO = 'NEW YORK'
AND F~FLDATE BETWEEN '20010910' AND '20010920'
AND FSEATSOCC < FSEATSMAX.
WRITE: / WA-CARR-CARRNAME, WA-FLIGHT-FLDATE, WA-FLIGHT-CARRID,
WA-FLIGHT-CONNID.
ENDSELECT.

How to find Particular Transport Request.

Hi All Experts,
Can anybody please tell, how to find previous transport request for the scenario like mentioned below.
If I have created some objects and transported to quality system from dev system.
Now, i need to do some changes in those objects and retransport those changes, with original object.
So in the request for changes to existing objects if I need to include the request from which the object was transported before, how can i find that old request.
Your help will be surely rewarded.
Regards
Vinay

Hi,
in SE01 you can display your requests.
Alternatively you can use SE03 / Search for Objects in Requests/Tasks, enter your user ID in the Owner, select relevant status, mark the first empty checkbox in the selection of objects, enter the object type (e.g. IOBJ for infoobjects, CUBE for ICube...) and enter its name in the input box; execute
this will show all your requests packed with the selected objects...
hope this helps...
Olivier.

How to find a Transport Request no for Task or Workflow Template

Hi All,
Any body tell me.
How to find a Transport Request No for Task or Workflow Template.
Thanks,
Lakhshmi.

Hi.
Next to the options already mentioned you can also try transaction SE03.
Select: Search for objects in Requests/Tasks.
Next, fill an empty line with the objectnumber you want to search (don't forget the checkbox).
For workflow tasks use the object type PDTS, for workflow templates use PDWS.
Kind regards,
Jasper Blok

How many types of authentications in sharepoint and how to implement those authentication in sharepoint?

Hi All,
How many types of authentications in sharepoint and how to implement those authentication in sharepoint?
can any one explain the above things with examples?
Thanks in Advance!

In addition to
A Sai Gunaranjan you can also check this URL for Sharepoint 2010:
http://technet.microsoft.com/en-us/library/cc288475(v=office.14).aspx
http://www.codeproject.com/Tips/382312/SharePoint-2010-Form-Based-Authentication
***If my post is answer for your query please mark as answer***
***If my answer is helpful please vote***

How to delete the Transport Request?

Hi all,
I want to delete the Transoport Request from Production Box( we have 2 request number... one child another one parent). I released the Child Request. Now i want to delete that request. we don't have setup in our production Box i think(in order to release that we don't have setup in Production Box).
Any Idea? I know how to delete that Transport Request. If i try to release that i'm getting TP(Transport Profile error) <b>with return Code 12</b>. it suppose to handle by Basis. My basis consultant is not aware of how to work on this?
Regards,
Nagesh Ganisetti.

I am not sure I understand.
You release the request in the system you created, not in another system (in your case production). It will then go to the import queue of the target system.
Transports will be configured in all the systems in your landscape (including production).
Just by releasing a request, it will not go to the target (unless it is configured so, not likely if the target is production), someone has to import it into the target. I assume you do not want this request to go to target. In this case, release it, then go to STMS, import queue, and delete it from there.
Added -
I now see that the request is in production.
Igore the above in that case.
If you are not able to release it, let it be. If you are doing an upgrade/support pack, you will need to release it.
When you try to delete, what message do you get?
Message was edited by: Ajay Das

How many times can I request a refund on the same in-app puchases?

How many times can I request a refund on the same in-app puchases in one itunes account?

Once for each purchase

How many types of tables exists and what are they in data dictionary?

hi,
How many types of tables exists and what are they in data dictionary?
regards.

Hello Liu,
Please search in forum before posting any question .
anyhow check the below link :
http://web.mit.edu/sapr3/dev/sap_table_types.htm
Thanks
Seshu

How many types of ports are there which we use for data transfe in ale/idoc

friends let me know how many types of ports are there which we use for transfering
data in ale/idocs?

Hello,
you can use file port,trnasactional RFC port.FI you are using IDOC-XML conversion combination,then you can XML port also.
Thanks

HOW MANY TYPES OF transportable requests?

Similar Messages

Maybe you are looking for