Requesting information regarding SAP in transportation domain

Hi,
I am Shailesh, have been working (no SAP) in Transportation domain since 4 years.
I would like to learn SAP. Could you please suggest which module of SAP is related to the transportation domain.

Hi Shailesh,
I will suggest to do in SAP LSM (Logistics and Supply Chain Management) module if you are currently engaged in Transportation. It will help you..
Thanks & Regards,
Bhipra Sakti

Similar Messages

All Information regarding Change and Transport management System in SAP

Hello Experts,
Iam into Basis . I need all information ,fundamentals and concepts over Change and Transport management system in SAP .Its fundamentals,the way it works ,how requests r transporteded etc. I want more of this information in regards to practical scenario. Plz dont provide help link as iam aware of that. I need good explanatory content ,in your own words shall be appreciated more. If any body has any self prepared good explanatory and procedural matter , tat will be of help.requested to revert at earliest as this is a bit urgent. My Email Id is [email protected]
Useful answers shall be rewarded points.
Thanks and Regards,
Somya

check this link
http://help.sap.com/saphelp_47x200/helpdata/en/d7/8eb9361a75ea43e10000009b38f839/frameset.htm

Information regarding SAP Tables

HI All,
I am new to SAP.As a part of archiving project,we recently archived the entire SAP database using a tool.When we started archiving we stopped the SAP and all the jobs which are running to make sure that all the tables are stagnant.This is due to the fact that once we archive, we do a row count on the Oracle(SAP) and archived tales to make sure every thing is archived.
But unfortunately, As we archiving the oracle database(SAP) got restarted as there was a backup job which ran and restarted the server.Now when we completed the full archiving and did a row count comparision we found that the below tables have different counts from the Oracle(SAP) i.e source.I think that these tables are SAP metadata and when system got restarted due to the back p job, these tables might have been updated.
Please see the list of tables below and let me know whether these tables contain any Data which might e useful to the customer or is it just some metadata used by SAP and nothing else...
DBABARL
DBAML
DBATL
DBSNP
DDLOG
MONI
PAHI
SDBAD
SDBAH
SGOSHIST
SNAP
TBTCO
TBTCP
TSP01
TSP02
TSPEVDEV
TSPEVJOB
TST01
TXMILOGRAW
UTAB
VARI
Thanks in Advance

> Please see the list of tables below and let me know whether these tables contain any Data which might e useful to the customer or is it just some metadata used by SAP and nothing else...
Well - you can check the content of the tables in SE11 and SE16. Whether the data is used or not depends on the customizing of the system and the applications/modules used. Whether this is "only" metadata can only be determined by the customer himself.
Markus

Need information/training material regarding SAP CRM Functional

Hello,
I am a SD Consultant.
I want to learn SAP CRM (Functional) on my own without going to any training institute or some thing.
Therefore, can anyone help me in forwarding the link(s) or document(s) with which I can learn about SAP CRM (Functional).
I want information/training material regarding SAP CRM 7.0 (on system/software working, not the general information, for example- why CRM, where CRM, etc)
For example, about org data, org structure, possible scenarios, etc.
Thanks in advance for spending your valuable time for me.
Regards,
T. Chaitanya

Hi ,
In the SDN lot of documents are there search in the WIKI.check the standard sap doc cr100.

Systems in same transport domain, but PRD import queue is empty

Hi all!
I have previously set up ERP 2005 development and QAS system, and there has been some development and transporting occuring between these two systems. Now I have installed the production system and added it to the transport landscape in STMS. The three system are in the same transport domain and the same transport group. In STMS I have created the Delivery route to the PRD system.
When I check the import queue for the production system, only transports created AFTER the installation of the production system appear in the import queue. Transports created and released from DEV to QAS before the production system was available is not displayed in the queue.I know that I can add single requests to the import queue easily, but that required a lot of manual work and making sure that the transports are added to the queue in the correct sequence.
How can I get all the transports to appear in the PRD system import queue? In AL11 in PRD, I am able to access the TRANS_DIR and I see all the transport requests in the directory.
Regards,
Thomas

Hi Thomas,
"Only transports created AFTER the installation of the production system appear in the import queue." - This is expected
From table E070, you can get a list of all transport imported into QAS system. Sort that list according to the date imported, and save the transport requests into a text file.
Run this below script from production by logging in as <sid>adm.
Provide the transport text file as an input to the script. It will add the transports to queue automatically one by one.
@echo on
set SID=<Prd SID>
set CL=<Client>
set filename=<drive>:\usr\sap\trans\scripts\transports.txt
FOR /F "tokens=1,2* delims=K" %%i in (%filename%) do (
tp addtobuffer %%iK%%j %SID% client%CL% pf=<drive>:\usr\sap\trans\bin\TP_DOMAIN_%%i.PFL >> )
Before running the script, take a backup of the production buffer at the OS level, incase u need to restore it.
Cheers,
Fahad

Help regarding SAP SCRIPT

Hi!
can any one help me regarding SAP SCRIPT. i unable to write a print program for sap script . can any one can send me sample code using ITCSY structure.
Thanks in advance.
Thanks & Regads,
DurgaPrasad.k

Hi,
refer this to write print program:
The Print Program
Structure of a print program
OPEN_FORM function
CLOSE_FORM function
WRITE_FORM
START_FORM function
END_FORM function
CONTROL_FORM function
The print program is used to print forms. The program retieves the necesary data from datbase
tables, defines the order of in which text elements are printed, chooses a form for printing and
selects an output device and print options.
Function modules in a printprogram:
When you print a form you must used the staments OPEN_FORM and CLOSE_FORM. To combine
forms into a single spool request use START_FORM and END_FORM.
To print textelements in a form use WRITE_FORM. The order in which the textelements are printed,
is determined by the order of the WRITE_FORM statements. Note: for printing lines in the body, you
can also use the WRITE_FORM_LINES function module.
To transfer control command to a form use CONTROL_FORM.
Structure of a print program
Read data
Tables: xxx.
SELECT *
FROM xxx.
Open form printing - Must be called before working with any of the other form function modules.
Must be ended with function module CLOSE FORM
call function 'OPEN_FORM'.....
To begin several indentical forms containing different data within a single spool request, begin each
form using START_FORM, and end it using END_FORM
call funtion 'START_FORM'.....
Write text elements to a window of the form
call function 'WRITE_FORM'.....
Ends spool request started with START_FORM
call funtion 'END_FORM'.....
Closes form printing
call function 'CLOSE_FORM'...
OPEN_FORM function
Syntax:
CALL FUNCTION 'OPEN_FORM'
EXPORTING
APPLICATION = 'TX'
ARCHIVE_INDEX =
ARCHIVE_PARAMS =
DEVICE = 'PRINTER'
DIALOG = 'X'
FORM = ' '
LANGUAGE = SY-LANGU
OPTIONS =
MAIL_SENDER =
MAIL_RECIPIENT =
MAIL_APPL_OBJECT =
RAW_DATA_INTERFACE = '*'
IMPORTING
LANGUAGE =
NEW_ARCHIVE_PARAMS =
RESULT =
EXCEPTIONS
CANCELED = 1
DEVICE = 2
FORM = 3
OPTIONS = 4
UNCLOSED = 5
MAIL_OPTIONS = 6
ARCHIVE_ERROR = 7
INVALID_FAX_NUMBER = 8
MORE_PARAMS_NEEDED_IN_BATCH = 9
SPOOL_ERROR = 10
OTHERS = 11
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Some important parameters:
FORM Name of the form
DEVICE PRINTER : Print output using spool
TELEFAX: Fax output
SCREEN: Output to screen
OPTIONS Used to control attrubutes for printing or faxing (Number of copies, immediate output....
The input for the parameter is structure ITCPO.
CLOSE_FORM function
CALL FUNCTION 'CLOSE_FORM'
IMPORTING
RESULT =
RDI_RESULT =
TABLES
OTFDATA =
EXCEPTIONS
UNOPENED = 1
BAD_PAGEFORMAT_FOR_PRINT = 2
SEND_ERROR = 3
SPOOL_ERROR = 4
OTHERS = 5
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Paramerters:
RESULT Returns status information and print/fax parameters after the form has been printed.
RESULT is of structure ITCPP.
WRITE_FORM function
CALL FUNCTION 'WRITE_FORM'
EXPORTING
ELEMENT = ' '
FUNCTION = 'SET'
TYPE = 'BODY'
WINDOW = 'MAIN'
IMPORTING
PENDING_LINES =
EXCEPTIONS
ELEMENT = 1
FUNCTION = 2
TYPE = 3
UNOPENED = 4
UNSTARTED = 5
WINDOW = 6
BAD_PAGEFORMAT_FOR_PRINT = 7
SPOOL_ERROR = 8
OTHERS = 9
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Some important parameters:
ELEMENT Specifies which textelement is printed
WINDOW Specifies which window is printed
TYPE Specifies the output area of the main window. This can be:
TOP - Used for headers
BODY
BOTTOM - Used for footers
FUNCTION Specifies whether text is to be appended, replaced or added
Example of how to use the WRITE_FORM function module together with a script.
Form layout of the MAIN window
/E INTRODUCTION
Dear Customer
/E ITEM_HEADER
IH Carrier, Departure
/E ITEM_LINE
IL &SBOOK-CARRID&, &SPFLI-DEPTIME&
/E CLOSING_REMARK
The print program
Writing INTRODUCTION
CALL FUNCTION 'WRITE_FORM'
EXPORTING
ELEMENT = 'INTRODUCTION'
FUNCTION = 'SET'
TYPE = 'BODY'
WINDOW = 'MAIN'
EXCEPTIONS
OTHERS = 8
Writing ITEM_HEADER
CALL FUNCTION 'WRITE_FORM'
EXPORTING
ELEMENT = 'ITEM_HEADER'
FUNCTION = 'SET'
TYPE = 'BODY'
WINDOW = 'MAIN'
EXCEPTIONS
OTHERS = 8
Set ITEM_HEADER into TOP area of main window for subsequent pages
CALL FUNCTION 'WRITE_FORM'
EXPORTING
ELEMENT = 'ITEM_HEADER'
FUNCTION = 'SET'
TYPE = 'TOP'
WINDOW = 'MAIN'
EXCEPTIONS
OTHERS = 8
Write ITEM_LINE
LOOP AT .....
CALL FUNCTION 'WRITE_FORM'
EXPORTING
ELEMENT = 'ITEM_LINE'
FUNCTION = 'SET'
TYPE = 'BODY'
WINDOW = 'MAIN'
EXCEPTIONS
OTHERS = 8.
ENDLOOP.
Delete ITEM_HEADER from TOP area of main window
CALL FUNCTION 'WRITE_FORM'
EXPORTING
ELEMENT = 'ITEM_HEADER'
FUNCTION = 'DELETE'
TYPE = 'TOP'
WINDOW = 'MAIN'
EXCEPTIONS
OTHERS = 8
Print CLOSING_REMARK
CALL FUNCTION 'WRITE_FORM'
EXPORTING
ELEMENT = 'CLOSING_REMARK'
FUNCTION = 'SET'
TYPE = 'BODY'
WINDOW = 'MAIN'
EXCEPTIONS
OTHERS = 8
START_FORM function
CALL FUNCTION 'START_FORM'
EXPORTING
ARCHIVE_INDEX =
FORM = ' '
LANGUAGE = ' '
STARTPAGE = ' '
PROGRAM = ' '
MAIL_APPL_OBJECT =
IMPORTING
LANGUAGE =
EXCEPTIONS
FORM = 1
FORMAT = 2
UNENDED = 3
UNOPENED = 4
UNUSED = 5
SPOOL_ERROR = 6
OTHERS = 7
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
END_FORM function
CALL FUNCTION 'END_FORM'
RESULT =
EXCEPTIONS
UNOPENED = 1
BAD_PAGEFORMAT_FOR_PRINT = 2
SPOOL_ERROR = 3
OTHERS = 4
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CONTROL_FORM function
The CONTROL_FORM function module alows you to create SapScript control statements from within
an APAB program.
Syntax:
CALL FUNCTION 'CONTROL_FORM'
EXPORTING
command =
EXCEPTIONS
UNOPENED = 1
UNSTARTED = 2
OTHERS = 3
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Example:
Protecting the text element ITEM_LINE
CALL FUNCTION 'CONTROL_FORM'
EXPORTING
COMMAND = 'PROTECT'.
CALL FUNCTION 'WRITE_FORM'
EXPORTING
TEXELEMENT = 'ITEM_LINE'.
CALL FUNCTION 'CONTROL_FORM'
EXPORTING
COMMAND = 'ENDPROTECT'.
rgds,
latheesh
Message was edited by: Latheesh Kaduthara

Password issue in Transport Domain

Hi
We was getting some problem while releasing the transport request in ERD (SAP Dev server). We was getting error 12. I tried different option but did not worked and then we decided to re-configure the Transport domain (deleted old trasnport route using SE06 and then re-created transport domain using STMS). Now, ERD is the domain controller and ERQ (QA server) and ERP (Producation server) is the part of domain controller. I created one test transport request in ERD and moved to ERQ.
Everything work fine but have one issue. When i was creating the domain controller using my user ID in client 000 (with sap_all authorization), it asked me couple of times password for productive client and client 000. When i was adding ERQ and ERD, it again asked for my passwords (2 to 3 times for each system). I'm not able to understand it.
I created transport request in ERD and release it. When i was trying to move the same transport to ERQ server (i logged on ERQ server to transport request), it again asked password for ERD, ERQ and ERD servers.
Looking forward the solution of this problem.Not sure, if i need to set some profile parameter to avoid to enter pasword or something else.
Pls suggest to solve this problem.
Thanks
Amar

Thanks Siva for quick reply.
I checked the connection as you mentioned. Connection test is ok but Auth test failed:
'Connection Test TMSADM at ERQ.DOMAIN_ERD '
Password logon no longer possible.
Same error for all three system. I think, something worng with the 'TMSADM'.
As mentioned earlier, there was some issue in transport domain. To solve the problem, we deleted all RFC for TMS* in SM59 of ERD/ERQ/ERP server. Deleted transport route using SE06 and re-cretaed Domain controller and then added the ERQ/ERP in domain controller. ERD is the domain controller.
I had not deleted user TMSADM in client 000 before re-configuring the transport domain. Not sure, if i should delete user TMSADM in all three servers and re-create the domain contoller. Any suggestion on this?
Problem seem to be for the password of TMSADM user ID. Checking more in details.
Thanks
Amarjit

Include a system in two different Transport Domain Controller

Hi folks,
I s it possible to configure a system in two different transport Domain Controller?
The two domain controllers will be in the same /usr/sap/trans file system.
thanks,
Má

Hello Má
Firstly to include system in the transport domain you need to have systems sharing common transport directory. Which you confirmed is the case.
Now when you try to change the Transport Domain of the system to make it part of another system it will overwrite current configuration.
Hence you wont be able to make one system part of two Domains.
There is no workaround available best of my infomation.
Regards
DG

Adding a new system to the transport domain

Gurus ,
   currently our landscape is a 3 system landscape . We are SAP BUSINESS SUITE users . we are using ECC 6.0 on AIX with AS ABAP .
   we are planning for one sand box system on AIX with both AS ABAP and AS JAVA . but we have certain confusions and lack of clarity on certain portions . hope over which you all can throw light ,
   - Will there be any difference in license info for using ECC with AS ABAP (or) ECC with AS ABAP + JAVA .
- would be able to add this system to our transport domain without including the system in solution manager
- can we make clinet copies from a ECC system with ABAP alone to a ECC system with ABAP +JAVA
- How to get more clarity on the license perspective of adding this system
please guide us

1. Will there be any difference in license info for using ECC with AS ABAP (or) ECC with AS ABAP + JAVA .
According to me there is not any differences in license, when you apply for the license you have to select the system as ABAP+JAVA and i dont think that you need to install any license for java in ECC
2. would be able to add this system to our transport domain without including the system in solution manager
Yes if Solution manager is not your domain controller. You can add the system into your domain, For the transport between 2 system is the requriement is that both system should be same relase with Same ABAP support pack and Kernel (as per my understnading).
3. can we make clinet copies from a ECC system with ABAP alone to a ECC system with ABAP +JAVA
This is think might not be possible but not sure for this, becuase there must be some ddic difference in both system.
Please correct me if i am wrong.
Regards,
Subhash

Information on SAP: ERP 2004 ECC Component

Hi All,
We are performing a Pilot Project for one of our client, by integrating and harnessing the functionalities of technologies like SAP: Netweaver Portal (GUI), SAP: Exchange Infrastructure (Middleware), Manufacturing Execution System (MES) along with SAP: ERP 2004 (Client's scope).
Request all to suggest a good source (website) for collecting information on ECC component of SAP: ERP 2004.
Thanking you all in anticipation.
With regards,
Deepak Pai

Hi Deepak,
Help.sap.com is the best. Anyways what is area of information you are looking at? is it installation and configuration of the product or is it like what the product would offer.
You can close this thread as you have already posted the same query in the forum "Integration with mySAP ERP 2004"
Information on SAP: ERP 2004 ECC Component
Regards,
Naresh
[email protected]

Not able to include the system to its transport domain

Hello,
We are not able to include the system to its transport domain. We are getting the same error:
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Except.                CX_SY_OPEN_SQL_DB
Date and Time          01.10.2010 11:27:35
Please advice
Sankar

Hi Shyam,
This is actually a program error and the same can be rectified by implementing the [SAP NOTE 1412609 - DUPREQ when configuring the transport domain|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1412609] using the tcode SNOTE.
This will resolve ur issue.
Regards,
Varadharajan M

SAP query transport error - need help

hello,
The system is throwing the following error when importing the query from development to QA client.
We already have the query imported the first time without errors. This is happening with subsequent transports if there is a change or any modification to the query.
Below is the error log from SAP regarding the failed transport :
R3TRAQQUFI was repaired in this system
Message no. TW104
Diagnosis
Object R3TRAQQUFI is in repair status. Therefore, it cannot be imported.
System Response
The object is not imported.
Procedure
If you still want to import the object, release the relevant repair and repeat the import.
Please help
Thanks in advance.

Hi
Here I am sending the step by step procedure for the SAP Query. Hope this helps you, if so please issue points.
1. Go to SQ02 .
Select Environment -> Query Areas
Select Standard Area (Client specific) as show below
2. Select Environment -> Transports
Select Import radio button
Check Overwriting allowed (only with import/upload/copy)
Remove Check for Test Run
Select Transport InfoSets and queries radio button
Fill Infoset and Query with corresponding names
Fill Import option with transport request number.
3. Click on Execute button
With this it will be done.
Thanks for your patience

Regarding SAP R/3

hiii to all
can any suggest 3tier architecture with real time application (R/3) how exactly it works or what exactly the concept is?
thanks in advance
bhabani

Many people try for placements with fake experience. While they are being trained the words like "Real Time" are used to tell them what is done practically .
SAP R/3 SYSTEM ARCHITECTURE
SAP based the architecture of R/3 on a three-tier client/server model. Presentation ServerApplication ServerDatabase Server
Presentation ServerThe presentation server is actually a program named sapgui.exe. It is usually installed on a user's workstation. To start it, the user double-clicks on an icon on the desktop or chooses a menu path. When started, the presentation server displays the R/3 menus within a window. This window is commonly known as the SAPGUI, or the user interface (or simply, the interface). The interface accepts input from the user in the form of keystrokes, mouse-clicks, and function keys, and sends these requests to the application server to be processed. The application server sends the results back to the SAPGUI which then formats the output for display to the user. Application ServerAn application server is a set of executables that collectively interpret the ABAP/4 programs and manage the input and output for them. When an application server is started, these executables all start at the same time. When an application server is stopped, they all shut down together. The number of processes that start up when you bring up the application server is defined in a single configuration file called the application server profile. Each application server has a profile that specifies its characteristics when it starts up and while it is running. For example, an application sever profile specifies: · Number of processes and their types · Amount of memory each process may use · Length of time a user is inactive before being automatically logged off The application server exists to interpret ABAP/4 programs, and they only run there-the programs do not run on the presentation server. An ABAP/4 program can start an executable on the presentation server, but an ABAP/4 program cannot execute there. If your ABAP/4 program requests information from the database, the application server will format the request and send it to the database server. Discovering the Database ServerThe database server is a set of executables that accept database requests from the application server. These requests are passed on to the RDBMS (Relation Database Management System). The RDBMS sends the data back to the database server, which then passes the information back to the application server. The application server in turn passes that information to your ABAP/4 program. There is usually a separate computer dedicated to house the database server, and the RDBMS may run on that computer also, or may be installed on its own computer. Configuring the ServersIn a three-tier client/server configuration, the presentation servers, applications servers, and database server all run on separate machines. This is the most common configuration for large systems, and is common in production. In the distribution presentation configuration, the application and database servers are combined on one computer and the presentation servers run separately. This is used for smaller systems, and is often seen on a development system. In the two-tier client/server configuration, the presentation and application servers are combined and the database server is separate. This configuration is used in conjunction with other application servers. It is used for a batch server when the batch is segregated from the online servers. A SAPGUI is installed on it to provide local control. When all servers are combined onto a single machine, you have a central configuration. This is rarely seen because it describes a standalone R/3 system with only a single user. Defining an R/3 SystemThe simplest definition of an R/3 system is "one database." In one R/3 system, there is only one database. To expand the definition, R/3 is considered to be all of the components attached to that one database. One R/3 system is composed of one database server accessing a single database, one or more application servers, and one or more presentation servers. By definition, it is all of the components attached to one database. If you have one database, you have one system. If you have one system, you have one database. During an implementation, there is usually one system (or one database) assigned to development, one or more systems designated for testing, and one assigned to production. The term R/3 system landscape denotes a description of the number of systems within an SAP installation and how they are designated, such as development, test, or production. Defining an R/3 InstanceWhen you hear someone say the word instance, most of the time, that person will be referring to an application server. The term instance is synonymous with application server. The term central instance refers to the database server. If an application server and database server both reside on the same machine, the term central instance refers to the computer on which both reside. In the most general terms, an instance is a server. It is a set of R/3 processes providing services to the R/3 system. Application Server ArchitectureAll requests that come in from presentation servers are directed first to the dispatcher. The dispatcher writes them first to the dispatcher queue. The dispatcher pulls the requests from the queue on a first-in, first-out basis. Each request is then allocated to the first available work process. A work process handles one request at a time. To perform any processing for a user's request, a work process needs to address two special memory areas: the user context and the program roll area. The user context is a memory area that contains information about the user, and the roll area is a memory area that contains information about the programs execution. Understanding a User ContextA user context is memory that is allocated to contain the characteristics of a user that is logged on the R/3 system. It holds information needed by R/3 about the user, such as: · The user's current settings · The user's authorizations · The names of the programs the user is currently running When a user logs on, a user context is allocated for that logon. When they log off, it is freed. It is used during program processing, and its importance is described further in the following sections. Understanding a Roll AreaA roll area is memory that is allocated by a work process for an instance of a program. It holds information needed by R/3 about the program's execution, such as: · The values of the variables · The dynamic memory allocations · The current program pointer Each time a user starts a program, a roll area is created for that instance of the program. If two users run the same program at the same time, two roll areas will exist-one for each user. The roll area is freed when the program ends. NOTE
When speaking to a Basis consultant, you might hear the term roll area used to refer to all roll areas for one user or even all roll areas on one application server. You usually can determine the intended meaning from the context in which it is used.
Both the roll area and the user context play an important part in dialog step processing. Understanding a Dialog Step NOTE
A dialog step is used by Basis consultants as the unit of measure for system response time.
A dialog step is the processing needed to get from one screen to the next. It includes all processing that occurs after the user issues a request, up to and including the processing needed to display the next screen. For example, when the user clicks the Enter key on the Change Vendor: Initial Screen, he initiates a dialog step and the hourglass appears, preventing further input. The sapmf02k program retrieves the vendor information and displays it on the Change Vendor: Address screen, and the hourglass disappears. This marks the end of the dialog step and the user is now able to make another request. There are four ways the user can initiate a dialog step. From the SAPGUI: · Press Enter. · Press a function key. · Click on a button on the screen. · Choose a menu item. It is important for an ABAP/4 programmer to know about dialog steps because they form a discrete unit of processing for an ABAP/4 program. Understanding Roll-In/Roll-Out ProcessingAn ABAP/4 program only occupies a work process for one dialog step. At the beginning of the dialog step, the roll area and user context are rolled in to the work process. At the end of the dialog step, they are rolled out. During the roll-in, pointers to the roll area and user context are populated in the work process. This enables the work process to access the data in those areas and so perform processing for that user and that program. Processing continues until the program sends a screen to the user. At that time, both areas are rolled out. Roll-out invalidates the pointers and disassociates these areas from the work process. That work process is now free to perform processing for other requests. The program is now only occupying memory, and not consuming any CPU. The user is looking at the screen that was sent, and will soon send another request. When the next request is sent from the user to continue processing, the dispatcher allocates that request to the first available work process. It can be the same or a different work process. The user context and roll area for that program are again rolled in to the work process, and processing resumes from the point at which it was left off. Processing continues until the next screen is shown, or until the program terminates. If another screen is sent, the areas are again rolled out. When the program terminates, the roll area is freed. The user context remains allocated until the user logs off. In a system with many users running many programs, only a few of those programs will be active in work processes at any one time. When they are not occupying a work process, they are rolled out to extended memory and only occupy RAM. This conserves CPU and enables the R/3 system to achieve high transaction throughput. NOTE
ABAP/4 programs do not have the capability to intercept many common Windows events. The events that generate a lot of messages such as key presses, focus changes, and mouse movements are not passed to ABAP/4 programs. As a result, there is no way of performing some of the functions that are found in other Windows programs. For example, in ABAP/4, you cannot validate the contents of a field when the user presses the Tab key. You must instead wait until the user initiates a dialog step.
Discovering How the Data Is Sent to the Presentation Server The messages exchanged between the presentation server and the application server are in an SAP proprietary format. The SAPGUI accepts the screen information sent from the application server and formats it appropriately for the platform it is running on. This enables different end-user hardware platforms to connect to a single application server. For example, an OS/2 PC and a Windows PC can both connect to the same application server at the same time. Understanding the Components of a Work ProcessEach work process is composed of the following: · A task handler · An ABAP/4 interpreter · A screen interpreter · A database interface All requests pass through the task handler, which then funnels the request to the appropriate part of the work process. The interpreters interpret the ABAP/4 code. Notice that there are two interpreters: the ABAP/4 interpreter and the screen interpreter. There are actually two dialects of ABAP/4. One is the full-blown ABAP/4 data processing language and the other is a very specialized screen processing language. Each is processed by its own interpreter. The database interface handles the job of communicating with the database. Understanding the Types of Work ProcessesThere are seven types of work processes. Each handles a specific type of request. The type of work processes and the types of requests that they handle are shown in Table 1.2.Table 1.2 Types of Work Processes and the Types of Requests they Handle WP Type Request Type
D (Dialog) Dialog requests
V (Update) Requests to update data in the database
B (Background) Background jobs
S (Spool) Print spool requests
E (Enqueue) Logical lock requests
M (Message) Routes messages between application servers within an R/3 system
G (Gateway) Funnels messages into and out of the R/3 system
Understanding the Logon ClientThe term logon client has nothing to do with Client/Server-it is completely different. The number entered here by the user corresponds to a set of rows within each client-dependent table within the database. Understanding Client-Dependent and Client-Independent Tables There are two types of tables in an R/3 database: client-dependent and client-independent. A table is client-dependent if the first field is of type CLNT. The length will always be 3, and by convention, this field is always named mandt. If the first field is not of type CLNT, the table is client-independent. This program selects rows from table lfa1 and writes out lfa1-lifnr. When this program is run, only two rows are selected: only those where mandt equals 800. This happens automatically because the first field in the table is of type CLNT. There are five rows in the table, but the program writes out only those rows where mandt equals 800. If the user were to log on to client 700 and run the same program, three rows of data would be found and written out. If the user were to log on to client 900, only one row of data would be found. The logon client mechanism divides the rows within a client-dependant table into distinct groups. To access a different set of data, the user logs on and specifies a different client number. NOTE
The user master records (containing R/3 user IDs) are client-dependent. Therefore, to gain access to a client, the security administrator must create a new user ID for you within that client.
Developers and testers use the logon client mechanism to create and access multiple, independent sets of data within a single table. For example, assume two typical, asocial programmers are working on an enhancement to the billing system. Jim is modifying the update transaction and Jane is creating a new report to go with Jim's modifications. Jane sets up data for her test run, executes her report and obtains output. Jim works in the next cubicle, but due to his antisocial tendencies is blissfully unaware that his transaction uses the same tables as Jane's report. He runs his transaction and updates the data. Jim got what he wanted, but Jane then modifies her code and runs her program again. Her output differs from the last run, and the differences many not result from her changes, but rather they may result from Jim's changes. What we have here is a failure to communicate. If the tables used by Jim and Jane's programs were client-dependent, they could each log in to separate clients, set up independent sets of data, and test their programs without ever talking to each other. They could perform all of their testing in the comfort of their cubicles and in isolation from their coworkers. To make their tables client-dependant, they only need mandt as the first field and the R/3 system will take care of the rest. When records are added to the table, the system automatically moves the current logon client into the mandt field when the record is send to the database. Their Open SQL select statements will only return rows where the client number in the table is equal to the their current logon client number. The Open SQL database statements insert, update, modify, and delete also provide automatic client handling. If the tables involved are all client-dependent, there can be more than one group of testers working at a time in one test system. Two teams of testers can test divergent functionality in the same set of programs at the same time provided they log on to different logon clients. The updates done by one team will not change the data belonging to the other team. A training client could also exist on the test system. The students could log on to one client and the testers could log on to another. Both would run the same set of programs, but the programs would access independent sets of data.NOTE
The average R/3 installation has three systems: development, test, and production. By default, each system comes with three clients installed: 000, 001, and 066. It is common to have from three to six clients in the development and test systems, but rarely will you see more than one client in production.
regards,
srinivas
*reward for useful answers*

ChaRM - Support for 46C as Transport Domain Controller

Good day.
We are currently testing ChaRM with the Transport Domain Controller being on a 46C box. We are getting the following error when trying to create a Task List:
Function module "TMW_DISPLAY_TRANSPORT_ROUTES" not found.
Is the use of a TDC on 46C supported with ChaRM?
Thanks,
Charles.

Hey Charles,
CHARM can only be implemented on satellite Systems with SAP Version 4.6 C onwards and above...
However, even then domain controller needs to be on 4.7.. i.e it requires WAS 620 aplication server...
Therefore we can conclude that CHARM cannot be implemented with the satellite system you had mentioned above..
Please Reward for useful points...
Regards,
Anand

Same transport domain. different transport directory, possible?

Hi SAP folks,
A quick query, I work on multiple systems within a single SAP transport domain. Recently we have requirements to move 2 non-ABAP systems to a different transport directory while keeping the rest intact.
The reason for this is we are doing CTS+ for the 2 non-ABAP system and do not want to share the transport directories for the rest of the ABAP system.
Please advise if this can be done and how?
The following link for SAP suggested that it's possible but stop short of how to do it.
http://help.sap.com/saphelp_nw04/helpdata/en/c4/6045377b52253de10000009b38f889/content.htm
Anyone done similar setup? care to share?
Thank you.
Regards,
Jansen

Hi,
You can do this very well. First you should remove the two systems that you wanted to configure for CTS+ from your existing transport domain. To do this, login to your existing transport domain controller and delete the systems you wanted to remove from transport domain.
To perform this:
STMS --> Overview -> Systems -> < choose the system u want to delete> -> SAP Systems -> Delete. Confirm the deletion and save and activate the changes made to ur configuration.
And then add your Non-ABAP systems you wanted to configure for CTS+ using the domain controller you decided for CTS+.
I hope this help you to perform your action.
Best Regards,
Vasanth Govindaraj

Requesting information regarding SAP in transportation domain

Similar Messages

Maybe you are looking for