Documentation on SWIA transaction code

Hi,
I need documentation on SWIA transaction code. Where can I get it?
Regards.
Krishna

Hai Krishna,
Find the detailed notes about SWIA in the link below
<a href=" http://help.sap.com/saphelp_erp2005vp/helpdata//EN/f4/843233cb0211d1950d0000e82dec10/frameset.htm ">http://help.sap.com/saphelp_erp2005vp/helpdata//EN/f4/843233cb0211d1950d0000e82dec10/frameset.htm</a>
Rgds,
Farooq.

Similar Messages

Documentation transaction code

Hi
I need to edit a object documentation. can anyone give some idea,what is the transaction code for documentation?
the program id Program ID 'LIMU
object type is and 'DOCU'
plz help me here

Hi,
If you want to change the documentation of that object then.
Follow this steps:
Press F1 keeping the cursor on the object that you want to change.
Opens the performance assistance window in which 5th buton from left you will have EDIT DOCUMENTATION. Click that and proceed with the changes.
If i am wrong correct me.
Hope my answer help you!!
Cheers!!

What are the main transaction codes in XI?

What are the main transaction codes in XI?

SAP XI TRANSACTION CODES
ALRTCATDEF- Alerts Configuration.
ALRTDISP - Display of Alerts Created
SXMB_IFR -> Start Integration Builder
SXMB_MONI -> Integration Engine - Monitoring
SXI_MONITOR -> XI: Message Monitoring
SXI_CACHE -> To Access IS runtime cache
SXI_SUPPORT -> Test all the Repository and Directory Objects
SXI_CACHE -> XI data directory cacheidx1 -> idoc adapter
IDX2 -> idoc metadata
IDX5 -> monitor idoc adapter
SM21 -> log di sistema
ST22 -> dump abap (analisi di eccezioni)
SMQ1 -> messages inbound e outbound queue
SMQ2 -> messages inbound e outbound queue
SMICM -> J2EE administration
ST06 -> stato della macchina cpu memory filesystem machine status - cpu, memory and file system.
ST03 -> workload.
SCC4 -> visualizza mandanti del sistema
WE20 -> partner profiles
sale - ale settings
RZ10 - edit system profile
SM59 ->mantain rfc destinations
BD64 -> mantain distribution model (trasformazioni)
SU01 -> users
AL08 -> list all logged users(user login logon)
SE10 -> Change Request
SE09 -> Change Request
WE05 -> All idocs
WE19 -> IDoc Test Tool
WE21 -> port definition
SE11 -> Data dictionary
SM21 -> log sistema xi
se37 -> mantain funcion modules
SICF -> http server configuration
SMGW -> trace, alzare livello di trace.
BD13 ->
BD64 -> modelli di distribuzione
PFCG -> Roles
tabella TSTC -> sap transactions codes
tabella TSTCT -> transaction descriptions
STMS -> transports management
SPAM -> apply ABAP support packages
SPAU -> manage objects after apply support packages
SE01 -> manage change requests
SLDCHECK -> Test SLD Connection
SLDAPICUST-> SLD API Customizing
SXMB_ADM -> Integration Engine - Administration
SXMB_MONI_BPE -> Process Engine - Monitoring
SE38 -> ABAP Editor
SE11 -> ABAP Dictionary
ST22 -> ABAP dump analysis
SPROXY-> ABAP Proxy Generation
SE80 -> Object Navigator
ABAPDOCU -> ABAP Documentation and Examples
SE24-> Class Builder
SM21-> Online System Log Analysis
SMQ1-> qRFC Monitor (Outbound Queue)
SMQ2-> qRFC Monitor (Inbound Queue)
RZ70-> SLD Administration
SM58-> Asynchronous RFC Error Log
SM59-> RFC Destinations (Display/Maintain)
SMICM-> ICM Monitor
WE60-> Documentation for IDoc types
BD87-> Status Monitor for ALE Messages
IDX1-> Port Maintenance in IDoc Adapter
IDX2-> Meta Data Overview in IDoc Adapter
WE05-> IDoc Lists
WE02-> Display IDoc
WE19-> Test tool
WE09-> Search for IDocs by Content
WE20-> Partner Profiles
WE21-> Port definition in XI
SE16-> Data Browser
SE93-> Maintain Transaction Codes
SM30-> Call View Maintenance
SU01-> User Maintenance
SM02-> System Messages
BD54 -Logical System Creation.
SWXF_PBUILDER -> for Detail BPM Process
SMQS - > to register the destination in QOUT scheduler
WEOUTQUEUE - > to start the queue processing
SMQR - > to register the queue
IDXPW - > to activate the IDOC message package
IDXP - > to monitor the message packages.
SWF_XI_CUSTOMIZING -> transaction to check prerequisites for integration processes.
http://www.erpgenie.com/abaptips/content/view/452/62/

What are the importent transaction codes in edi

what are the importent transaction codes in edi

hi,
=>sale - ALE Customizing
=>bale - Distribution Administration (ALE)
=>wedi - IDOC Type and EDI Basis
=>shdb - BDC (Transaction Recorder)
=>lsmw - LSMW
=>bapi - BAPI
=>spau - Display Modified DE Objects
=>spdd - Display Modified DDIC Objects
=>sara - central idoc archiving
=>stms - Transport Management System
=>wedi - IDOC Type and EDI Basis (IDOC Configuration)
=>bd21 - Analyze change pointers - create IDOC from change pointer
=>bd10 - Send Material Master
=>bd12 - Send Customer Master
=>bd14 - Send Vendor Master
=>bd50 - Activate Change Pointer for Message Type
=>bd55 - Conversion rule user exit (Link conversion rule user exit to the different system \ partner combinations)
=>bd54 - Maintain Logical Systems
=>bd71 - Distribute Customer Model
=>bd87 - Process Inbound IDOCs
=>bd88 - Process Outbound IDOCs
=>bdm2 - Cross-system IDOC Reporting
=>bdm7 - ALE Audit - statistical analyses
=>bdm8 - ALE Audit - sending confirmations
=>bd61 - Activate Change Pointer generally
=>bmv0 - Direct Input Data Transfer Administration
=>rz04 - Operation Mode
=>rz12 - RFC Server Group Maintenance
=>sar3 - Archiving object customizing
=>s001 - SAPoffice Inbox
=>s010 - Standards Texts (SAP Script)
=>se01 - Transport Organizer (Extended View - Performing and managing the transport of development object across different systems)
=>se09 - Transport (Workbench) Organizer (Controlling and keeping track of Development work and Development Objects)
=>se78 - Administration of Form Graphics (Import Graphics into SAP System)
=>se84 - ABAP Repository Information (search for SAP objects)
=>su01 - User Maintenance (Security)
=>su02 - Maintain Authorization Profiles
=>su03 - Maintain Authorizations
=>sm36 - Background Job Scheduling
=>sm37 - Background Job Monitoring (display batch jobs)
=>sm31 - Table Maintenance
=>sm30 - Calling View Maintenance
=>sm35 - Batch Input Monitoring (Error Logs)
=>sm50 - Process Overview
=>sm58 - Transactional RFC Monitoring
=>sm59 - Maintain RFC Destinations (Define RFC Configuration)
=>snro - Number Range Objects (for IDOCs)
=>we02 - Display IDOC
=>we05 - IDOC lists
=>we07 - IDOC statistics
=>we12 - Inbound processing of outbound file - convert outbound to inbound file
=>we14 - Process (dispatch) IDOCs through Port - RSEOUT00
=>we15 - Outbound IDOC from NAST - message control
=>we16 - Inbound File
=>we18 - Generate status file
=>we19 - Test tool
=>we20 - Add new Message Type to Partner Profile
=>we21 - Maintain Port Definition
=>we30 - IDOC Type development
=>we31 - IDOC Segment development
=>we41 - Process Code Outbound
=>we42 - Process Code Inbound
=>we46 - IDoc Administration
=>we47 - Status Code Maintenance
=>we57 - Assign function module to logical message and IDoc type
=>we63 - IDOC Type for Parser Output
=>we82 - Assign IDOC to Message Type
=>we60 - IDOC Documentation - IDOC Types
=>we61 - IDOC Documentation - IDOC Record Types
=>we81 - Create new IDOC Message Types
=>we82 - Assign IDOC to Message Type
=>pa20 - Display HR Master Data
=>pa30 - Maintain HR Master Data
=>bd59 - Create and assign Filter Object Type for Message Type
=>bd64 - Maintenance of ALE or any other Distribution Model
Hope this helps, Do reward.

Transaction code for debugging

CAN ANYONE TELL ME WHAT IS THE TRANSACTION CODE FOR ABAP PROGRAM

Hi,
As far as I know there is no transaction code to debug, however when you run the transaction SDMO and give the search string as 'DEBUG' this will list the following transactions,
Tcode Transaktionstext
@@D   Debugger -> Documentation
DBG_A Debugger -> ABAP Editor
DBG_B Debugger -> Repository Browser
DBG_S Debugger -> Screen Painter
LAST_ Debugger -> ABAP Editor
PACC PF debugger
STDA Debugger display/control (server)
STDC Debugger output/control
STDU Debugger display/control (user)
Not able to navigate to most of the transactions mentioned here,
Rgds,

Hi, all transactions codes are saved in which table?some transaction codes?

hi,
all transactions codes are saved in which table?i want some transaction codes?

All transaction codes are stored in table TSTC. Their texts are displayed in TSTCT.
Here are some T-CODE's..
OSS1      SAP Online Service System
OY19      Compare Tables
S001      ABAP Development Workbench
S002      System Administration.
SA38      Execute a program.
SCAT      Computer Aided Test Tool
SCU0      Compare Tables
SE01      Old Transport & Corrections screen
SE09      Workbench Organizer
SE10      Customizing Organizer
SE10      Customizing organizer requests for user (To release for transport enter user name, press Enter. Select changed object and select ReleaseSE10 New Transport & Correction screen
SE11      ABAP/4 Dictionary Maintenance SE12 ABAP/4 Dictionary Display SE13 Maintain Technical Settings (Tables)
SE11      ABAP/4 Dictionary.
SE12      Dictionary: Initial Screen enter object name
SE13      Access tables in ABAP/4 Dictionary.
SE14      ABAP/4 Dictionary: Database Utility.
SE14      Utilities for Dictionary Tables
SE15      ABAP/4 Repository Information System
SE15      ABAP/4 Repository Information System.
SE16      Data Browser
SE16      Data Browser: Initial Screen.
SE16      Display table contents
SE17      General Table Display
SE30      ABAP/4 Runtime Analysis
SE30      ABAP/4 Runtime Analysis: Initial Screen.
SE30      Run Time Analysis (press Tips and Tricks button for good stuff)
SE32      ABAP/4 Text Element Maintenance
SE35      ABAP/4 Dialog Modules
SE36      ABAP/4: Logical Databases
SE37      ABAP/4 Function Library.
SE37      ABAP/4 Function Modules
SE38      ABAP Editor
SE38      ABAP/4 Editor.
SE38      ABAP/4 Program Development
SE39      Splitscreen Editor: Program Compare
SE41      Menu Painter
SE43      Maintain Area Menu
SE51      Screen Painter
SE51      Screen Painter: Initial Screen.
SE54      Generate View Maintenance Module
SE61      R/3 Documentation
SE62      Industry utilities
SE63      Translate Short/Long Text.
SE63      Translation
SE64      Terminology
SE65      R/3 documents. Short text statistics SE66 R/3 Documentation Statistics (Test!)
SE68      Translation Administration
SE71      SAPscript layout set
SE71      SAPscript Layouts Create/Change
SE72      SAPscript styles
SE73      SAPscript font maintenance (revised)
SE74      SAPscript format conversion
SE75      SAPscript Settings
SE76      SAPscript Translation Layout Sets
SE77      SAPscript Translation Styles
SE80      ABAP/4 Development Workbench
SE80      Repository Browser: Initial Screen.
SE81      SAP Application Hierarchy
SE82      Customer Application Hierarchy
SE84      ABAP/4 Repository Information System
SE85      ABAP/4 Dictionary Information System
SE86      ABAP/4 Repository Information System
SE87      Data Modeler Information System
SE88      Development Coordination Info System
SE91      Maintain Messages
SE92      Maintain system log messages
SE93      Maintain Transaction Codes
SE93      Maintain Transaction.
SEU      Object Browser
SHD0      Transaction variant maintenance
SM04      Overview of Users (cancel/delete sessions)
SM04      Overview of Users.
SM12      Deletion of lock entries (in the event you have you are locked out).
SM12      Lock table entries (unlock locked tables)
SM21      View the system log, very useful when you get a short dump. Provides much more info than short dump
SM30      Maintain Table Views.
SM31      Table Maintenance
SM32      Table maintenance
SM35      View Batch Input Sessions
SM37      View background jobs
SM50      Process Overview.
SM51      Delete jobs from system (BDC)
SM62      Display/Maintain events in SAP, also use function BP_EVENT_RAISE
SMEN      Display the menu path to get to a transaction
SMOD/CMOD      Transactions for processing/editing/activating new customer enhancements.
SNRO      Object browser for number range maintenance.
SPRO      Start SAP IMG (Implementation Guide).
SQ00      ABAP/4 Query: Start Queries
SQ01      ABAP/4 Query: Maintain Queries
SQ02      ABAP/4 Query: Maintain Funct. Areas
SQ03      ABAP/4 Query: Maintain User Groups
SQ07      ABAP/4 Query: Language Comparison
ST05      Trace SQL Database Requests.
SU53      Display Authorization Values for User.
Human Resources
PA03      Change Payroll control record
PA20      Display PA Infotypes
PA30      Create/Change PA Infotypes
PP02      Quick Entry for PD object creation
PU00      Delete PA infotypes for an employee. Will not be able to delete an infotype if there is cluster data assigned to the employee.
Sales and Distribution (SD)
OLSD      Config for SD. Use Tools-Data Transfer-Conditions to setup SAP supplied BDC to load pricing data
VA01      Create Sales/Returns Order Initial Screen
VB21      Transaction for Volume Lease Purchases (done as a sales deal)
VK15      Transaction used to enter multiple sales conditions (most will be entered here)
VL02      Deliveries
SAP Office
SO00      send a note through SAP, can be sent to Internet, X400, etc
Financial Accounting (FI)
FGRP      Report Writer screen
FM12      View blocked documents by user
FST2      Insert language specific name for G/L account.
FST3      Display G/L account name.
KEA0      Maintain operating concern.
KEKE      Activate CO-PA.
KEKK      Assign operating concern.
KL04      Delete activity type.
KS04      Delete a cost centre.
KSH2      Change cost centre group delete.
OBR2      Deletion program for customers, vendors, G/L accounts.
OKC5      Cost element/cost element group deletion.
OKE1      Delete transaction data.
OKE2      Delete a profit centre.
OKI1      Determine Activity Number: Activity Types (Assignment of material number/service to activity type)
OMZ1      Definition of partner roles.
OMZ2      Language dependent key reassignment for partner roles.
Material Management (MM)
MM06      Flag material for deletion.
OLMS      materials management configuration menu, most of the stuff under this menu is not under the implementation guide
MM configuration transactions
OLMB      Inventory management/Physical Inventory
OLMD      MM Consumption-Based Planning
OLME      MM Purchasing
OLML      Warehouse Management
OLMR      Invoice Verification
OLMS      Material Master data
OLMW      MM Valuation/Account Assignment
Configuration related
OLE      OLE demo transaction
OLI0      C Plant Maintenance Master Data
OLI1      Set Up INVCO for Material Movements
OLI8      Set Up SIS for Deliveries
OLIA      C Maintenance Processing
OLIP      C Plant Maintenance Planning
OLIQ      New set-up of QM info system
OLIX      Set Up Copying/Deleting of Versions
OLIY      Set Up Deletion of SIS/Inter.Storage
OLIZ      Stat Set Up INVCO: Invoice Verify
OLM2      Customizing: Volume-Based Rebates
OLMB      C RM-MAT Inventory Management Menu
OLMD      C RM-MAT MRP Menu
OLME      C MM Menu: Purchasing
OLML      C MM Menu for Warehouse Management
OLMR      C RM-MAT Menu: Invoice Verification
OLMS      C RM-MAT Master Data Menu
OLMW      C RM-MAT Valuation/Acct. Asset. Menu
OLPA      SOP Configuration
OLPE      Sales order value
OLPF      SPRO Start SAP IMG (Implementation Guide).
OLPK      Customizing for capacity planning
OLPR      Project System Options
OLPS      Customizing Basic Data
OLPV      Customizing: Std. Value Calculation
OLQB      C QM QM in Procurement
OLQI      Analysis OLVD C SD Shipping Menu
OLVF      C SD Billing Menu
OLQM      Customizing QM Quality Notifications
OLQS      C QM Menu Basic Data
OLQW      C QM Inspection Management
OLQZ      Quality Certificates
OLS1      Customizing for Rebates
OLSD      Customizing: SD
OLVA      C SD Sales Menu
OLVS      C SD Menu for Master Data
Regards,
Pavan

Transaction code which using method of a class as start object

Hi all,
I'm creating a new tcode 'Z123' which is tied to a method of a class in SE93. However, when I run this tcode and into debug mode, SY-TCODE will always return OS_APPLICATION. How can I get the actual tcode, which is 'Z123' into my program?
Thanks in advance

You can try using the method GET_CURRENT_TRANSACTION of class CL_DYNPRO. Check this SAP documentation for details:
... the method GET_CURRENT_TRANSACTION of the class CL_DYNPRO can be used to obtain the transaction code of the current transaction. This method returns the transaction code during a parameter transaction or variant transaction instead of the transaction code of the implicitly called dialog transaction.
But if i try checking sy-tcode in a tcode bound to a method of a class i get the correct tcode & not OS_APPLICATION.
Br,
Suhas

User Exit for CO11n transaction code

Dear friends,
I have a requirement that in T-Code CO11n the user enters the order confirmation and when they go for the goods movement, the screen shows the BOM list with quantities.
My requirement is that the user will put one quantity for the main material and the rest of the quantities should be calculated through the input value and appear in the respective fields.
For that I need an enhancement so please suggest me a userexit or any possible solution for the same.
Thanks in advance.
Regards,
Mubashir

Hi mubhasir,
The following are the list of available user-exits in transaction code co11n, go thru the documentation of all userexit in Tcode SMOD and choose a appropriate one for ur requirement.
Reward points, if helpful....
Regards
Karthik D
<b>Transaction Code - CO11N                    Single Screen Entry of Confirmations
Enhancement/ Business Add-in            Description
Enhancement</b>
CONFPP01-                                PP order conf.: Determine customer specific default values
CONFPP02-                                PP order conf.: Customer specific input checks 1
CONFPP03-                                PP order conf.: Cust. specific check after op. selection
CONFPP04-                                PP order conf.: Customer specific input checks 2
CONFPP05-                                PP order conf.: Customer specific enhancements when saving
CONFPP06-                                PP Order Confirmations: Actual Data Transfer
CONFPP07-                                Single Screen Entry: Inclusion of User-Defined Subscreens
CONFPS01-                                PS confirmation: Determine customer specific default values
CONFPS02-                                PS confirmation: Customer specific input checks 1
CONFPS03-                                PS confirmation: Customer specific check after op. selection
CONFPS04-                                PS confirmation: Customer specific input checks 2
CONFPS05-                                PS confirmation: Customer specific enhancements when saving
CONF0001-                                Enhancements in order confirmation
CONFPI01-                                Process order conf.: Calculate cust.specific default values
CONFPI02-                                Process order confirmation: Customer spec. input checks 1
CONFPI03-                                Process order conf.: Cust. spec. check after op. selection
CONFPI04-                                Process order conf.: Customer specific input checks 2
CONFPI05-                                Process order conf.: Cust. spec. enhancements when saving
CONFPI06-                                Process order confirmation: Actual data transfer
CONFPM01-                                PM/SM order conf.: Determine cust. specific default values
CONFPM02-                                PM/SM order confirmation: Customer specific input checks 1
CONFPM03-                                PM/SM order conf.: Cust. spec. check after op. selection
CONFPM04-                                PM/SM order conf.: Customer specific input check 2
CONFPM05-                                PM/SM order conf.: Cust. specific enhancements when saving
<b>No.of Exits:         24</b>

Error when launching transaction code CRMBS02

Hello all...whenever we attempt to launch the t-code CRMBS02 or BS02, we get a popup that says:
Error in object editing: This syntax cannot be used for an object name
Selecting the documentation drop down provides:
Message no. TK103
Diagnosis
The syntax of the transferred objects is incorrect. R3TR BSVS made this check.
This could be caused by the following:
The object type R3TR BSVS is unknown
The syntax of the object name is incorrect
The object is a component of a system object
System Response
The function terminates.
Procedure
Correct the syntax.
Any suggestions? When this occurs, it does not enable editing and allows for display only. I have SAP_ALL assigned to the user, so I don't see any authorization errors when I trace the transaction code.
Suggestions?
Thanks in advance!
Joe

Hello Joe,
Tasks template of type T and Workflow Task of type WF, are no more used after release 45b. The were substituted by the TS Templates and by Workflow Template.
Please notes: 114811 -
From release 4.5 onwards only WS/TS tasks can be created via the standard workflow editor transaction however WF tasks created in previous releases may still be maintained. If it is important to be able to create WF flows in release 4.5 then you may still do so with transaction PFWF. This transaction has been removed from the menu to encourage the use of WS flows wherever possible.
A copy utility to copy WF flows and it's components to WS flows will be made available to speed up the transfer to client independent flows.
"Check also note: *152871 Release Upgrade considerations for workflow 3. WS / WF workflows (all releases)
"From Release 3. 1 onwards, it is possible to create customer workflows
of type 'WS'.
Solution: If you have 'WF' workflows, they will continue to run after an upgrade. You can modify them too. However, some of the new features of future releases only apply to 'WS' workflows. See note 114811 for a complete discussion of this subject.
You should pass from T and WF templates to the New WS and TS templates.
1) In relation to workflows of type 'WF' (Workflow Task) and task 'T' they have not been developed since release 40B, instead the Workflow Template (WS) was introduced and Tasks 'TS'. This error has seldomly
been observed in the case of trying to work with WFlow tasks of type WF instead of type WS.
Existing WF will run also in higher releases, however if you change a WF task in a higher release it may produce dumps or numerous errors. This is valid too for Tasks.
Please refers to note 114811.
If you want to change them please copy them first to templates type WS or TS rather than WF or T. Use PFTC in order to copy them and then you can make the changes and you will have much more functionality than type
WF or T.
Additional Inforamtions:
Note 1068627 - Composite note about workflow upgrade
thanks
Willie

Restrict this transaction code only to create sets starting with 'ZMR'

Hello,
I need to create custom transaction code for 'GS01' and restrict this transaction code only to create sets starting with 'ZMR' No other sets should be allowed to be created.
If anyone have done before with the same scenario. Please give me clear documentation on this .
Reagdrs
Kiran

YOu cannot find the call to the badi's by searching the main program.
The badi is called a t run time.
To find a badi attached to a main program, goto se38,
GIve the program name.
Goto->Object Directory Entry. Find the package.
Go to se18 transaction, Press f4.
give the package name in the popup.
you can get the badis associated with the main program.
Regards,
Ravi

How to attach two maintenance views to one transaction codes

Hi
I have created two master Ztables and also created two maintenance views in SM30 for them.
Now my req is i have to attach these two maintenace views to one TCODE only Not two transaction codes.
How i can do that.
Pls give me some inputs.
Regs
Manas Ranjan Panda.

Hi,
Goto SE54..Click on the edit cluster view..Enter a cluster view name...Then press the create button..IN the resulting screen you can add multiple maintenance views..
Check this documentation for creating cluster views..
http://help.sap.com/saphelp_46c/helpdata/EN/d0/999246b2aa11d1a5700000e82deaaa/frameset.htm
Once you create the cluster view..
Then you can a parameter transaction in SE93 with the transaction as SM34 and give the cluster view name ...
THanks,
Naren

ABAP Transaction codes

Hi all,
I'm a bit confused in using the transaction codes in ABAP like se11,...so on.
What code can be used for what application....so on.?
Can any one please help me out in giving the transaction codes in ABAP.
Please give them in a list wise...i.e.,
Transaction code -
What Application(such as editor, smartforms, function modules).
ID: [email protected]
Bye,
SAI KUMAR

HI,
USMM Pressing F8 will display all hotpacks applied.
SEARCH_SAP_MENU Show the menu path to use to execute a given tcode. You can search by transaction code or menu text.
DI02 ABAP/4 Repository Information System: Tables.
LSMW Legacy System Migration Workbench. An addon available from SAP that can make data converstion a lot easier. Thanks to Serge Desland for this one.
OSS1 SAP Online Service System
OY19 Compare Tables
SM13 Update monitor. Will show update tasks status. Very useful to determine why an update failed.
S001 ABAP Development Workbench
S001 ABAP/4 Development Weorkbench. (from [email protected])
S002 System Administration. (from [email protected])
SA38 Execute a program. (from [email protected])
SCAT Computer Aided Test Tool
SCU0 Compare Tables
SE01 Old Transport & Corrections screen
SE03 Groups together most of the tools that you need for doing transports. In total, more than 20 tools can be reached from this one transaction.
SE09 Workbench Organizer
SE10 New Transport & Correction screen
SE11 ABAP/4 Dictionary Maintenance SE12 ABAP/4 Dictionary Display SE13 Maintain Technical Settings (Tables)
SE12 Dictionary: Initial Screen - enter object name. (from [email protected])
SE13 Access tables in ABAP/4 Dictionary. (from [email protected])
SE14 Utilities for Dictionary Tables
SE15 ABAP/4 Repository Information System
SE16 Data Browser: Initial Screen. (from [email protected])
SE16N Table Browser (the N stands for New, it replaces SE16). Provided by Smijo Mathew.
SE17 General Table Display
SE24 Class Builder
SE30 ABAP/4 Runtime Analysis
SE32 ABAP/4 Text Element Maintenance
SE35 ABAP/4 Dialog Modules
SE36 ABAP/4: Logical Databases
SE37 ABAP/4 Function Modules
SE38 ABAP Editor
SE39 Splitscreen Editor: Program Compare
SE41 Menu Painter
SE43 Maintain Area Menu
SE48 Show program call hierarchy. Very useful to see the overall structure of a program. Thanks to Isabelle Arickx for this tcode.
SE49 Table manipulation. Show what tables are behind a transaction code. Thanks to Isabelle Arickx for this tcode.
SE51 Screen Painter: Initial Screen. (from [email protected])
SE54 Generate View Maintenance Module
SE61 R/3 Documentation
SE62 Industry utilities
SE63 Translation
SE64 Terminology
SE65 R/3 document. short text statistics SE66 R/3 Documentation Statistics (Test!)
SE68 Translation Administration
SE71 SAPscript layout set
SE71 SAPScript Layouts Create/Change
SE72 SAPscript styles
SE73 SAPscript font maintenance (revised)
SE74 SAPscript format conversion
SE75 SAPscript Settings
SE76 SAPscript Translation Layout Sets
SE77 SAPscript Translation Styles
SE80 ABAP/4 Development Workbench
SE81 SAP Application Hierarchy
SE82 Customer Application Hierarchy
SE83 Reuse Library. Provided by Smiho Mathew.
SE84 ABAP/4 Repository Information System
SE85 ABAP/4 Dictionary Information System
SE86 ABAP/4 Repository Information System
SE87 Data Modeler Information System
SE88 Development Coordination Info System
SE91 Maintain Messages
SE92 Maintain system log messages
SE93 Maintain Transaction. (from [email protected])
SEARCH_SAP_MENU From the SAP Easy Access screen, type it in the command field and you will be able to search the standard SAP menu for transaction codes / keywords. It will return the nodes to follow for you.
SEU Object Browser
SHD0 Transaction variant maintenance
SM04 Overview of Users (cancel/delete sessions)
SM12 Lock table entries (unlock locked tables)
SM21 View the system log, very useful when you get a short dump. Provides much more info than short dump
SM30 Maintain Table Views. (from [email protected])
SM31 Table Maintenance
SM32 Table maintenance
SM35 View Batch Input Sessions
SM37 View background jobs
SM50 Process Overview. (from [email protected])
SM51 Delete jobs from system (BDC)
SM62 Display/Maintain events in SAP, also use function BP_EVENT_RAISE
SMEN Display the menu path to get to a transaction
SMOD/CMOD Transactions for processing/editing/activating new customer enhancements.
SNRO Object browser for number range maintenance. (from [email protected])
SPRO Start SAP IMG (Implementation Guide). (from [email protected])
SQ00 ABAP/4 Query: Start Queries
SQ01 ABAP/4 Query: Maintain Queries
SQ02 ABAP/4 Query: Maintain Funct. Areas
SQ03 ABAP/4 Query: Maintain User Groups
(Queries,Funct. Areas,User Groups are stored in table AQGQDOC and AQLQDOC )
SQ07 ABAP/4 Query: Language Comparison
ST05 Trace SQL Database Requests. (from [email protected])
ST22 ABAP Dump analysis
SU53 Display Authorization Values for User. (from [email protected])
WEDI EDI Menu. IDOC and EDI base.
WE02 Display an IDOC
WE07 IDOC Statistics
rgds,
bharat.

Transaction code to repair/check objects

Hello
Can somebody remind me transaction code to repair/check objects in BW?
Thanks

hi
you can use rsrv. it is for bw objects consistency analysis and repair.
from transaction code RSRV doc itself :
Transaction RSRV: BW Data and Metadata Test and Repair Environment.
Transaction RSRV checks the consistency of data stored in BW. It mostly examines the foreign key relationships between individual tables in the enhanced star schema of the BW system.
The transaction interface was re-designed for SAP Portals release 3.0A. A brief guide about how to use the transaction follows.
Starting the Transaction
You can reach the test and repair environment
By entering the transaction code RSRV
From InfoObject maintenance (Transaction RSD1)
By clicking on the "Analyze" button in the intial screen.
After selecting a characteristic in the maintenance screen via the "Processing -> Analyze InfoObject" menu option.
The Initial Screen
When using the test and repair environment for the first time, the message "Values were not found for all setting parameters" draws your attention to the fact that there aren't any saved settings for your user.
After confirming the dialog box, you reach the initial screen of the transaction. This is divided into two parts:
1. On the left-hand side, you can see a tree structure with the pool of available tests.
2. The right-hand side is empty at first. The tests you have selected will be put here. A selection of tests is called a Test Package here.
Combined and Elementary Tests
An Elementary Test is a test that cannot be divided into smaller tests and that can therefore only be executed as a whole.
In this regard, a Combined Test determines which elementary tests are to be executed after entering the parameters. You can remove individual elementary tests from the test package before carrying out the actual test run, in order to reduce run time, for example.
Combining a Test Package and Executing it.
Firstly select one or more tests with drag&drop or by double-clicking. Each selected test appears as a closed folder in the view of your test package. (An exception is elementary tests without parameters: These do not appear as a folder). You can also drag a whole folder of tests from the test pool across to the right-hand screen area; all tests that are located in the hierarchical structure under this folder are then added to the test package. You can also display a short description of the test, if required. Do this right-clicking on a test and choosing "Description" from the context menu.
Afterwards, you must supply the tests with parameters. Tests without parameters must not be given parameters. You are given notification of this when selecting them. You can enter parameters by double-clicking on a test (or a test package) or by expanding the folder of the test.
A dialog box appears in which you must enter the required parameters. Input help is often available. After entering the parameters, a folder with the name "Parameter" is added under the test. This contains the parameter values. The test name can change in some circumstances, enabling you to see at first sight for which parameter values the test is to be executed. It is possible to select the same test several times and give it different parameters, which may even be preferable in some situations. When you have supplied the combined test with parameters, the folder with the name "Elementary Tests" is added under this one. It contains the elementary tests, from which the combined test is built. You can delete individual elementary tests in the test pool using drag & drop.
After supplying all tests with parameters, you can start the test run by clicking on the "Execution" button. After execution, the test icons change from a gray rhombus to a red, yellow or green one, depending on whether the test had errors, warnings or was error-free.
Test Results
The test results are written to the application log. Depending on the settings, the system jumps automatically to this display, or you can reach it by clicking on the "Display" button. The results are saved in the database, and can therefore be compared later with additional test runs.
In the left-hand side of the window, you can see an overview of the most recent test runs. Double-clicking on a folder displays all messages under these nodes as a flat (non-hierarchical) list in the right-hand screen area. Long texts or detail data may be available for individual messages, which can be displayed with a mouse click.
Repairs
Some tests can repair inconsistencies and errors. Automatic correction is generally not possible: If entries are missing from the SID table for a characteristic, in which case the lost SIDs are still being used in a dimension table (and the corresponding dimension keys are still being used in the fact table) of an InfoCube, you can only remove the inconsistency by reloading the transaction data of the InfoCube. Also note that you must make repairs in the correct sequence. You must always read the documentation for the test and have a good idea about how the error occured, before making the repairs.
After executing the test run, go from the application log back to the initial screen to make these repairs. Click on the "Fix Errors" button to start an error run. Since the dataset could have changed between the test and the repair run, the required tests are executed again before the actual repair. The results can be found in the application log once again.
Test Packages
The test package is deleted if you do not save the test package in the display before leaving the test environment. Choose "Test Packages -> Save Test Package" in the option menu. You can do the following via options in the "Test Package" menu:
Load packages
Load for processing - the package is then locked against changes by others.
Delete and
Schedule execution at a later date or at regular intervals in background processing
Settings
In the "Settings" menu option, you can make settings (adjust the size of the screen areas, for example) and save them. The settings are automatically read when starting the test environment. Support packages are being delivered with additional settings options since the test environment is under development at the moment. A message notifies the user at the start if there aren't any values for the setting options.
Jobs Menu Option
You can access the job overview via the Jobs -> Job Overview menu. Use this when you want to check the status of a test package you have scheduled.
Application Log Menu Option
You can display old logs from previous test runs in the dialog box, as well as scheduled ones. The option of deleting test logs can also be found here.
New Selection Button
The currently selected test package is deleted when you press this button.
Filter Button
After a test run, click on this button to remove all elementary tests without errors or warnings from the test package.
Executing Test Packages in Process Chains
You can add a process chain to the ABAP Programm RSRV_JOB_RUNNER in the process chain maintenance transaction, RSPC. To do this, use drag & drop to select the process type "ABAP Program" under "General Services" in the process type view. When maintaining process variants you will be asked for the program name and a program variant. Enter RSRV_JOB_RUNNER for the program name. Choose a program variant name and click on "Change". In the next screen you are able to either change or display an already existing variant, or create a new variant. When creating a new variant you will be asked for the following: Package name (an imput help on this is available), the detail level for the log to which the RSRV log in the process chain log is to be integrated, and a message type severity at which process chain processing should be terminated.
The RSRV process log in the process chain is built as follows:
First is a summary specifying whether errors, warnings, or no errors occurred for each elementary test.
A log view of the RSRV test package at the specified detail level follows.
Example: If you choose the value '3' for the detail level, only messages up to and including detail level 3 will be included in the log processes for the process chain. Messages occuring at a lower layer of the test package test are not displayed in this log. Please note that, unlike the application log, the process log does not propagate errors from deep detail levels to low detail levels. For example, if a single detail level 4 error occurs the summary will show that the relevant test delivered an error. However, this error will not be listed in the second part of the log.
A complete log is always written independantly of the RSRV process log in the process chain. You can view this in the menu option "Application Log->Display Log->From Batch".
Please note that there is currently no transport object for test packages and that consequently these cannot be transported. Process chains that execute RSRV test packages must therefore be manually postprocessed after a transport to a different system: The relevant test packages must be created.

CHARM Usage and Transaction Codes

Is the ChaRM (Change Management)feature of Solution Manager being widely used? Has anyone attempted a customization of CHARM to make it more compatible with Sarbanes-Oxley guidelines? And, finally, what are the transaction codes for accessing ChaRM without going through the service desk path? Thanks, Deb

Hi Giampaolo
I would appreciate if you can please give link or documentation of configuration of CHARM in Solution Manager 4.0
thanks and regards
Rahul Kunte

Transaction code for Import from legacy

Hi SAP Guru's,
Can any one tell, which transaction code is used to Import spread sheet for the
Account balance, from the legacy system.
Thanks, and will ensure full points.
Thanks

use LSMW
if you are not familiar with it please go through this
http://help.sap.com/bp_blv1500/BL_US/documentation/LSMW_EN_US.doc
assign points if helpfull

Documentation on SWIA transaction code

Similar Messages

Maybe you are looking for