BADI’s in 5 Minutes
Generally if you are a developer you know all about BADI’s, if you are a functional person you possibly only know that they exist. This is what every functional person, at least needs to know about them:
A BADI is similar to a user exit.
It stands for Business Add In.
BADIs are object orientated.
You do not need to register the code change in SAP SSCR. (SAP Software change registration).
In ECC the transaction code to display/change/create a BADI definition is SE18.
In SE18 you can also see detailed descriptions of the use and examples of standard SAP BADI’s for example use: ME_DEFINE_CALCTYPE - To reset the calculation type in a purchase order.
In ECC you can see the business implementation that calls the BADI in transaction SE19.
- In the definition, SE18 you create an enhancement that is called from the application code
- In the implementation, SE19 you save the code for the functions for the enhancement
How do you find a BADI:
Go to the transaction code you wish to check, for example MM02. Click on a field, select help, select technical details. (F1-F9), then double click on the program name.
- Search in the program for the string CL_EXITHANDLER you should find the string “CALL METHOD CL_EXITHANDLER=>GET_INSTANCE” where you will find the relevant BADI.
- Alternatively you can find out the BADI name by following this post: http://saptricks.com/2438/find-a-badi
How to unprotect a variant
Quite often, program variants are protected to avoid any unauthorised users from changing them.
For example, if this variant is for a program which is part of a batch plan, you don’t want to this variant to be modified as it will disturb your automatic processes. So you protect your variants. But a protected variant can only been changed by the user who has protected this variant.
The issue could arise when the original user has left the company or the variant is required to be changed for an urgent issue?
The solution – Go to transaction SE38, execute program RSVARENT, “Cancel Variant Protection” enter the program and the variant you want to unprotect and execute. The program variant is now available for any changes.
Submitted by Robin Ferali – Thank you for contributing to the webs largest database of SAP tricks!
Find a BADI
There are some cases where we need to add some functionality when a transaction is called or an action is done in SAP.
In some cases we are not able to know which BADI to change in order to have our customized behaviour for a determined action.
Well, following the following steps we will be able to identify the BADI that we will need to change:
Step 1: SE37 display Function Module – SXV_GET_CLIF_BY_NAME.
Step 2: Set a BREAKPOINT on call function SXV_ADD_PREFIX .
Step 3: In another SESSION run the desired transaction, parameter ‘name‘ gives the BADI; (parameter ‘clif ‘ gives implementation, e.g. for TCode MIGO name = MB_MIGO_BADI, clif = CL_EX_MB_MIGO_BADI.)
Submitted by an anonymous SAPtricks User – Thank you for contributing to the webs largest database of SAP tricks!
How to activate or deactivate MS-Word as default text editor
When you want to activate/deactivate MS Word as the text editor for SAPscript/Smartforms.
- Call transaction se38, enter program RSCPSETEDITOR and press Execute (F8). On the next screen, select the checkbox SAPScript/Smartforms and press ‘Activate’.
- This is a fantastically fast method to produce multiple texts in multiple languages provided they are supported by your code page. Check out the OSS note below for comprehensive instructions on MS Word setup and available options.
OSS Note: 742662.
Submitted by an anonymous SAPtricks User – Thank you for contributing to the webs largest database of SAP tricks!
EDI IDOC Tables
Requirement: You wish to investigate the contents of an IDoc. Or you need to locate a specific IDoc based upon a specific IDoc segment value.
Solution: The best solution is not to use tables, but instead to use the standard SAP transaction WE09. (The IDoc search for business content.) Here you can locate for example, all Sales Order IDocs that were for a specific product. (You search for a value (material) in a field (IDTNR) within a segment for example (E1EDP19) for a Basic Type for example (ORDERS05).
In some instances you may wish to use the tables in which case there are 3 main reference tables:
- Control Record Table = EDIDC
- Data Record Table = EDID4
- Status Record Table = EDIDS
Search Transports by IMG
So picture the scenario: You see an article which is configured has been changed in the IMG, but you do not know which transport was responsible. You could search with SE10 via table names , but did you know there is an easier method?
If you are trying to locate a transport/s of a specific IMG activity or object it is very easy to do, without even using the table names, simply use transaction SE 10 with the following steps:
1) Select Transport and organizer tools (Shift +F6).
2) Select “Search for Objects in Requests/Tasks”.
3) Select 1/2 down the page for “IMG Activity” then select F4.
4) Now select the place in the IMG, the lowest drill down level possible, for which you wish to search for transports, which include those changed objects.
5) Then select the date range and Status “modifiable” or “Released” and execute.
Place your image in the right-hand side of the initial screen
You can place your image/company logo in the right-hand side of the initial screen, simply proceed as follows:
Transcation SMW0 – Create and import the picture/logo in the database with the transaction SMW0 and radio button “Binary Data For WebRFC applilcations” e.g. in “.GIF” format.
Transaction SM30 – with table SSM_CUST – Enter a record with the picture name in the key “START_IMAGE“.
If you wish to resize the image – Transaction SM30 – with table SSM_CUST – You can use values of ”YES” or “NO” with parameter key “RESIZE_IMAGE“.
If you wish to hide user specific picture display settings – Transaction SM30 – with table SSM_CUST – You can use values of ”YES” or “NO” with parameter key “HIDE_START_IMAGE“.
- I have heard that an HTML page may also be included, however have not tested it – If anyone has used an HTML page with hyperlinks please tell us as this would be great functionality to use.
Execute a Function Module without using SE37
A number of companies restrict the execution of function modules in quality, pre-prod and prod environments, for good reason. Therefore you may find you do not have access to the transaction code SE37. Generally experienced developers may however have access to SE38.
So how do you execute or test a function module in a system/client but wish to get around the authorization issue? Simply use SE38 with program RSFUNCTIONBUILDER.
TIP – You can sometimes use the same technique by using SE93 with the problem transaction and using the program name however do not expect to be able to bypass all authorizations.
Deactivate SAP menu or All user menus
You may have a requirement to control your user navigation in SAP, either you may wish to create your own area menus, or you may wish to restrict a user specific menu from being created.
You can deactivate the menus for the entire system by creating or changing records in the global settings table SSM_CUST in the view maintenance transaction SM30.
- To globally deactivate the SAP menu, enter a record “SAP_MENU_OFF” “YES” in upper-case letters.
- To globally deactivate all user menus enter a record “ALL_USER_MENUS_OFF” “YES” in upper-case letters.
(Note the value “CUSTOMER_MENU_OFF” is obsolete and has no effect.)
For more information refer to OSS Note 380029.
–> Dont forget you can use transaction SSM2 to set which area menu in a system is to be used as the SAP menu.
Change SAP menu
Do you know you can set the default area menu that all users will go to when opening a new session, system wide. This is beneficial should you wish to create a specific area menu for your company. If no setting is made, the standard entry point (area menu S000) is used.
The SAP menu entry point is specified in the transaction SSM2.
Customer-specific text on the SAP Gui logon screen
Why change the SAP login Screen?
Some companies choose to modifiy the login screen to:
- Give security notice warnings to potential unauthorised access.
- List client numbers and their use within a system.
The history:
Before Release 4.6 the logon screen was modified through program SAPMSYST screen 0020. From release 4.6 onwards it is simply modified using transaction SE61.
Proceed as follows:
Go to Transaction SE61and select the document class ‘General Text’ (selection using F4 help).
Create a text with the name ZLOGIN_SCREEN_INFO in the system language. (If the text does not exist in the system language, no output is made.)
TIP – Check profile parameter “zcsa/system_language” in transaction RZ11 to determine your system language.
Title lines may be used, as well as very basic text formatting. You may also include standard SAP icons within the message. A tip is to change the editor from within SE61 (Goto–>change editor), this will clearly show you the available character and paragraph codes.
Note: Creating/changing this text requires a changeable system. Therefore, for production systems, SAP recommends maintaining the text in the upstream system and then transporting it. To do this, select a transportable (customer) development class when you create the text and save the active version prior to the export.
The transport is done via the transport object R3TR DOCT ZLOGIN_SCREEN_INFO
What to use to measure performance improvement
You know of ST05, ST01 and SE30. But do you know why you would use one transaction code and not the other? What are the main purposes of each one when it comes to performance improvement and measurement?
To measure and improve performance of ABAP programs – Use SE30 to measure:
- Excessive or unnecessary use of modularization units
- CPU-intensive program functions
- User-specific functions that could be replaced with ABAP statements
- Inefficient or redundant database access.
In addition you may want to analyze or fine-tune a program’s database accesses – Use ST05 to measure:
- Database accesses (SQL trace)
- Table buffers
- RFC calls
- Lock operations (client side)
If you wishto fine tune the system – use ST01 to measure:
- Authorization checks
- Kernel functions
- Kernel module
In addition ST01 encompasses the majority of the functionality of ST05.
How to find the IP address of a SAP system
Scenario – You wish to connect to your SAP system from a remote connection, you require your SAP system IP address and port.
Option 1 – There are a few methods to discover the IP address of a system the easiest being to simply use the menu path:
System–>Status–> then press (SHIFT+F5) –> You will see your current systems IP address under the System Information.
Option 2 – Alternativly you may use SM59 then select R/3 connections and double click on the system (RFC destination), then select the menu path:
System Information–>Target System –> You will see the target systems IP address under the “Network address”.
Check IDoc number
Is there any way to check the IDOC number from a sending system, within a receiving system?
Yes there is a way to do this. In the receiving system, execute transaction BD87. Select the node for analysis and select “Trace IDOCS”. You will then see all IDOCS as well as the field, IDOC No. partner. (The external IDOC number).
SGEN – The SAP Load Generator
The SAP Load Generator is executed through transacion code SGEN. SGEN may be required to be executed after a large upgrade or release of functionality in a system. If you don’t run SGEN and try to access specific objects the programs may start to be compiled as they are individually accessed.
Quick Overview
- SGEN is used to “compile” ABAP programs.
- It can be used to re-generate all the SAP programs after you change version of your SAP kernel, upgrade your SAP system or apply support packages.
- It is best to execute it during a period of time with very low user activity.
- SGEN is a client independent transaction.
- SGEN can also be used to re-generate objects within a Transport Request from SGEN menu–>Regenerate Existing Load
- If you want to regenerate loads, make sure that there is enough space available in the database. The space required can be several hundred MB. Generation over all components requires around 2 GB of free space.
- The runtime depends on the type of hardware configuration and number of objects being generated. (It would not be uncommon for this to take 5 hours.)
- You can limit the components to be generated, in order to reduce the runtime.
- You can schedule RSGENINVLAS to automatically regenerate invalidated loads. (Note this report has no selection screen)
Use
1. Select the generation task.
On the initial screen of transaction SGEN you can select the task that suits the purpose of the generation:
Generate all Objects of Selected Software Components
Choose this strategy if you want to generate the loads of all objects of certain software components. This may be the case, for example, if your system has been reinstalled. Here, the loads that are required for operation are not yet available and must be regenerated.
After selecting this task, the Selection of the Generation Set by Software Components screen appears. Here, you can restrict the amount of objects to be generated by selecting software components. Use the pushbuttons to select the software components you require.
Regenerate After an SAP System Upgrade
After an upgrade, you have to regenerate the ABAP object load in the system.
Regenerate the Objects of the Last Run
This task is suitable, for example, in the following cases:
- The generation of objects of the generation set that was used in the previous run was terminated and you want to regenerate the remaining objects.
- You want to regenerate all objects of the generation set that was used in the previous run.
After selecting this task, the following two options are available to you:
- Restart
The generation set that was used in the previous run in transaction SGEN is used. Only those objects that were not generated in the previous run or whose generation was terminated due to a system error, are generated.
- Generation:
All objects of the generation set used in the previous run of transaction SGEN are generated.
Regenerate Existing Loads
This task allows you to regenerate all ABAP loads and invalidated loads that exist in your system, and to generate loads for objects of a Support Package queue. You have the following options:
- Generate all Objects with Existing Load
- Generate Objects with Invalidated Load Only
An object load is invalidated if, since the time the load was generated, activated changes were made to the object or to objects used by this object, such as includes or tables. This may occur by importing a Support Package (SPAM) or a kernel patch.
If you want to generate loads for objects from a Support Package queue, start the task after importing the queue. The task determines the generation set using the invalidated loads in the system. Unlike the Generate objects of a transport request task, this task also takes into account ABAP loads that were invalidated by modified Dictionary objects.
Note: You can also periodically schedule an automatic regeneration of invalidated loads (every night, or at other times when the system load is low, for example). To do this, schedule the RSGENINVLAS report for the relevant time and period. The report then determines the invalidated loads for every type of host in your system at the specified time, and regenerates them.
Generate Objects from a Transport Request
You can use this generation task to regenerate the ABAP load for all objects in a transport request that can be generated. However, this task does not take into consideration ABAP loads that were invalidated by modified Dictionary objects. To include these loads, choose Regenerate Existing Loads -> Generate Objects with Invalidated Load Only.
After choosing this task, a screen appears that allows you to search for the name of the transport request using the selection button, or to specify it directly.
Generation of BSP Applications
This task enables you to generate BSP applications of selected software components.
Each Business Server Page is realized technically by an ABAP object class. When BSP applications are generated, these classes and their ABAP loads are generated. BSP applications are not included in the generation sets of the Generate All Objects of Selected Software Components, Regenerate After an SAP System Upgrade and Regenerate All Existing Loads tasks, since they are optional. You can use this task to deal with these.
After selecting this task, the Selection of the Generation Set by Software Components screen appears. Here you can restrict the amount of BSP applications to be generated by selecting software components. Use the pushbuttons to select the software components you require.
If you quit the generation of BSP applications before it has finished, or if the system terminates generation, the Regenerate the Objects of the Last Run task allows you to resume the generation.
2. Select the servers for parallel generation.
The generation is based on a method where the generation set is divided into small subsets that are processed by parallel processes. Depending on resources, available servers are included in the parallel processing, whereby multiple parallel processes run on one server.
From the Selection of Servers for Parallel Generation screen, you can select the servers that are to be used in the parallel processing. Note that loads depend on the machine type (MT) of a host. This means that it only makes sense to parallel process the generation set of servers of the same machine type.
The default selection uses the server that you are logged on to. It corresponds to your logon server and all servers on your system that have the same machine type. If you want to use the default selection, choose Continue.
If you want to exclude individual servers from the generation, or if you want to generate the load for a particular machine type that is different to that of the logon server, then use the pushbutton to select the corresponding servers and choose Continue.
Note: The parallel servers are depicted via the logon groups in transaction RZ12. For transaction SGEN, logon group ‘parallel_generators‘ is created. Do not use this group for your own purposes, as transaction SGEN uses and continually redefines this group.
After you have selected the servers, the system starts to define the generation set dynamically, and stores it in the database (database table GENSETC). This can take several minutes.
Job Monitor Pushbutton
This function allows you to call the job process control directly, without redefining the generation set. By choosing Job Monitor -> Job Overview -> Spool or Job Log, you can display logs from previous generation jobs.
Measure specific portions of ABAP Runtime
Most people know about SE30 which can be used to do an ABAP runtime analysis. However did you know that you are able to dynamically call the runtime analysis for a portion of source code for example a section of a user exit, or for a specific function module?
This is easily done by changing the user variant as follows:
- Open SE30
- On Measurement restrictions (1/2 way down the page) create/change your user defined variant.
- Within the variant under program parts, select the “particular Units” check box and save.
Now from within SE38 for the code you wish to measure – set your breakpoint for the position from which you wish to measure and another for the position to which you wish to measure.
Go back to SE30 and execute your code when you reach the breakpoint activate the runtime analysis from System–>Utilities–>Runtime Analysis –> Switch On.
Run through the code by selecting F8.
When you reach your end point de-activate the analysis by selecting System–>Utilities–>Runtime Analysis –> Switch Off.
TIP: You can activate the runtime performance analysis start by entering the command prompt code /RON in the transaction box. You can de-activate the analysis by using the command prompt code /ROFF.
NOTE: If you get the message “The Particular “units” option is not selected – S7100. It means you are not using your new changed default user variant for the execution.
Debug and change in SE16
Not a very common procedure – however you may have an instance where you are required to change a value of a record or field in a table. If you are unable to change the value using SM30. You may wish to debug and manipulate the abap controls of the field permissions using SE16. You can do this as follows:
1) SE16 using the table name, extract the record you wish to change.
2) /h to enter debug mode.
3) Double click on the record you wish to change.
4) Press F7.
5) Change the code from “SHOW” to “EDIT” by changing the field contents.
6) Press F8 to run to end.
The authorization to proceed in step 5 should generally only be available for advanced ABAP developers who are in an integrated or development environment and need to adjust variables to develop their code. It is very possible that the majority of the readers of this site will not have the authorization.
BD56 and WE20 ALE IDoc Segment Filtering
Problem with ALE IDoc segment filtering?
A common problem related to ALE IDoc segment filtering is a mis-alignment between the partner profile settings in WE20 and the segment filtering settings in BD56. Normally the settings in BD56 are maintained and transported where the values in WE20 are maintained manually in each system. If the settings in WE20 are not maintained with the same expected parameters in BD56 the segment filtering will not work. Specifically one needs to make special note that:
- BD56 – Message Type = WE20 – Message Type
- BD56 – Logical System Type = WE20 – Partner Type
- BD56 – Receiver = WE20 – Partner Number
- BD56 – Receiver Role = WE20 – Partner Role
Specifically if Receiver Role is blank then Partner role must be blank. Alternatively if a value exists such as LS (Logical System) the same value must be in both fields.
Transport of Copies
Issue: Imagine you create and release a few transports before setting up the target system and Landscape. Because of this, the transports can be released without target clients. How do you fix this problem?
Fix: Fix is done using Transport of Copies Method:
- Execute transaction SE10
- Select the create icon.
- Select “Transport of Copies”
- Enter short description and save, this will create your transport number.
- Now follow the menu path to place your objects into this transport copy:
- Request Type–>Object List–>Include Objects
- Select “Object List from Request” and enter your old transport number.
Thats it! Your new transport is a copy of your old transport with all associated objects.
———-
Post contributed by: Sundar Raghuraman
Contact: sundar.raghuraman@gmail.com
How to Scan ABAP Sources for Specific Strings
It is simple to locate a string within a program but have you ever wondered how to find all programs where a specific ”string”, or line of text, or object name, is used.
There is a wonderful report which is I use to find ABAP programs related to specific search terms.
- The Report name is – RPR_ABAP_SOURCE_SCAN
- You can execute it from transaction SA38 or SE38.
Some useful benefits of this report are:
You can limit the search range of the programs for example to your custom built developments only for example all programs starting with Y* or Z*.
Tip - Another similar program is RKCTSEAR.
So which system is connected?
I work on a large landscape of 110 SAP systems (not clients). Every now and then someone asks if a specific system is connected to another, there is no way I can remember which systems are connected. Depending on what system they are referring to one may be able to execute a system specific transaction. However as a dependable alternative one may simply use SM59 and view the connected systems.
Here you can view the following connections:
- R/3 connections
- HTTP Connections to R/3 System
- Internal connections
- Logical destinations
- TCP/IP connections
- Connections via ABAP/4 driver
Tip – Depending on your settings (If the logon data is saved on the Logon/security tab) you may even be able to login to a connected system remotely from within SM59, simply select the R/3 connection and selecting “Remote logon” button.
ABAP Code Inspector
Do you need to easily check the performance of an ABAP program or do some analysis on its code?
You can use the transaction SCI.
This is a very powerful transaction code, which can do more than a performance check.
However here is an example of one of the more simpler uses:
From transaction SCI.
-Enter Person responsible
-Enter A name and version and select the “Create” Icon.
From the new screen
-Select the “Single” radio button
-From the drop down select “PROG Program”
-Enter the program/report you wish to analyse in the adjacent field.
-Under the check variant section enter “PERFORMANCE_CHECKLIST” (If this value does not work simply select the value from the F4 match-code selection list).
-Select Execute
From the next screen select the “Results” Icon (Shift + F6).
SAP Table Editing Function
This is a SAP Trick that is possibly too powerful, if authorizations are not in place in your system you dont want to use this too liberally:
To edit the contents of a table (Virtually any table from customizing to database records):
- Use transaction SE16n or in some systems transaction n.
- Enter the table name and see the records. (Sometimes you may be able to change a tables contents depending on its attributes.)
However if you wish to change most tables regardless of table attributes/control you can do the following:
- Use transaction SE16n or in some systems transaction n.
- Then enter &sap_edit in the command field.
- You will see a message “SAP editing function is activated”.
- Now enter the table name and execute to see the records. You will now be able to change the contents of the table.
This SAP technique may be useful to maintain faulty data in your system. But should only be used by a very experienced person.
Spool – Output
The output controller – Spool Request Selection Screen can be used in transaction code SP01.
This will give you spool requests and output requests by system.
If you wish to limit a user access to their own individual spool requests you can give them access to SP02.
If you wish to completely control the spool and output functionality of a system you can use the administration transaction SPAD (or additionally transaction SPAT.)
When working with output/messages you can access the objects message status in table NAST.
If you are looking for a simple single table overview of all output/message condition types which have a condition record you can use table NACH. (This will give you the Condition Type+Access Sequence Table+Application+Partner function and a variable key which will show you the key fields for the access sequence table.)
Batch Input Reports
Here are some reports related to batch input:
- RSBDCSUB - Process sessions outside transaction SM35
- RSBDCDRU - Print session contents (transactions and data)
- RSBDCLOG - Process logs
- RSBDCREO - Reorganize processed sessions that are still in the system Reorganize logs (delete logs and shrink log file to actual size)
- RSBDC_REORG - Same as old report RSBDCREO but with selection screen for reorganizing processed sessions.
- RSBDCTL3 - Analyze Batch Input logs
Batch Input Recordings SM35
What: A Batch Input Recording is a recording of a series of screens and fields
Why: A Batch Input Recording can be used for multiple uses, some of the more common ones are:
- To test functionality after a change has been done in the system.
- To enter data into a system.
- To create a Function module.
- To create a program.
How: Create a Batch Input Recording via transaction SHDB.
Brief Process:
- Transaction SHDB
- Select New Recording button.
- Enter a recording name and a transaction code for example VD02. (Update mode = A, CATT mode = No CATT, Defualt size checked and all other fields unchecked.)
- Start Recording –> Follow the screen and field sequence you wish to record.
- At Commit (save) the recording will end and you will be provided with a list of program and screen and field names, with entered values.
- Now Save
- What you have created now is a simple recording of a sequence of steps with 1 unique set of transactional or master data. As you have no variables in the load/runtime you cannot use this recording to load data or for any other purposes than simple test executions.
- An idea on its use – Execute this same recording any time you change customising and wish to run a series of automated non regression tests.
- To execute it you need to create a batch input session, from within SHDB select “Create Session”, which will then create a session to be executed in SM35.
- Go to SM35 select your session and execute it.
I will do another post with the steps to create a data transfer program using a Batch Input Recording.
Tips:
- Not all BDC OK codes work such as /nxxxx where xxxx is a transaction code. Another code which does not work is /i
- If you wish to set the cursor on a field in a screen in the batch input use
- Utility field BDC_CURSOR and specify the field name: For example: Cursor on field HUGO, then BDC_CURSOR = HUGO. - To go to the Batch Input menu, choose “System” -> “Services” -> “Batch input”
- With batch input running, you can:. Delete a running transaction OK code /bdel or BI menu. Call the next transaction /n -”-. Terminate batch input /bend -”-. Set the processing mode . Process in foreground OK code /bda or BI menu . Display errors only /bde -”-. Activate expert mode OK code /bdx or BI menu. Deactivate expert mode /bdy -”
- You can record sessions using SHDB (The transaction Recorder).
- You can examine logs/print/export and archive them with SM35P.
ABAP System Fields – Use of structure SYST
Often one needs to use the values of the system structure SYST. Here is an alphabetical list of the different fields followed by a few sentences on the usage of their values.
Alphabetical List
| Name | Type | Length | Use | Description | |
| ABCDE | CHAR | 26 | Constants | Alphabet (A,B,C,…) | |
| APPLI | RAW | 2 | Obsolete | ||
| BATCH | CHAR | 1 | Background processing | Program runs in the background | |
| BATZD | CHAR | 1 | Obsolete | ||
| BATZM | CHAR | 1 | Obsolete | ||
| BATZO | CHAR | 1 | Obsolete | ||
| BATZS | CHAR | 1 | Obsolete | ||
| BATZW | CHAR | 1 | Obsolete | ||
| BINPT | CHAR | 1 | Batch input | Program runs under batch input | |
| BREP4 | CHAR | 4 | Obsolete | ||
| BSPLD | CHAR | 1 | Obsolete | ||
| CALLD | CHAR | 1 | ABAP Program | Call mode of ABAP program | |
| CALLR | CHAR | 8 | Printing Lists | ID for print dialog function | |
| CCURS | DEC | 9 | Obsolete | ||
| CCURT | DEC | 9 | Obsolete | ||
| CDATE | DATS | 8 | Obsolete | ||
| CFWAE | CUKY | 5 | Internal | ||
| CHWAE | CUKY | 5 | Internal | ||
| COLNO | INT4 | 10 | Creating Lists | Current column in the list | |
| CPAGE | INT4 | 10 | List processing | Current page number | |
| CPROG | CHAR | 40 | ABAP Program | External procedure call | |
| CTABL | CHAR | 4 | Obsolete | ||
| CTYPE | CHAR | 1 | Obsolete | ||
| CUCOL | INT4 | 10 | Screens | Horizontal cursor position at PAI | |
| CUROW | INT4 | 10 | Screens | Vertical cursor position at PAI | |
| DATAR | CHAR | 1 | Screens | Displays user input | |
| DATLO | DATS | 8 | Date and time | Local date of user | |
| DATUM | DATS | 8 | Date and time | Current (application server) date | |
| DAYST | CHAR | 1 | Date and time | Daylight saving time flag | |
| DBCNT | INT4 | 10 | Database accesses | Number of processed table rows | |
| DBNAM | CHAR | 20 | ABAP Program | Linked logical database | |
| DBSYS | CHAR | 10 | R/3 System | Name of central database system | |
| DCSYS | CHAR | 4 | Obsolete | ||
| DEBUG | CHAR | 1 | Internal | ||
| DSNAM | CHAR | 8 | Internal | ||
| DYNGR | CHAR | 4 | ABAP Program | Screen group of current screen | |
| DYNNR | CHAR | 4 | ABAP Program | Number of current screen | |
| ENTRY | CHAR | 72 | Internal | ||
| FDAYW | INT1 | 3 | Date and time | Factory calendar weekday | |
| FDPOS | INT4 | 10 | Character strings | Offset in character strings | |
| FFILE | CHAR | 8 | Internal | ||
| FLENG | INT4 | 10 | Internal | ||
| FMKEY | CHAR | 3 | Obsolete | ||
| FODEC | INT4 | 10 | Internal | ||
| FOLEN | INT4 | 10 | Internal | ||
| FTYPE | CHAR | 1 | Internal | ||
| GROUP | CHAR | 1 | Internal | ||
| HOST | CHAR | 8 | R/3 System | Name of application server | |
| INDEX | INT4 | 10 | Loops | Current loop pass | |
| INPUT | CHAR | 1 | Internal | ||
| LANGU | LANG | 1 | R/3 System | Current language | |
| LDBPG | CHAR | 40 | ABAP Program | Program of logical database | |
| LILLI | INT4 | 10 | List processing | Selected list row | |
| LINCT | INT4 | 10 | Creating Lists | Page length of list | |
| LINNO | INT4 | 10 | Creating Lists | Current row | |
| LINSZ | INT4 | 10 | Creating Lists | Column width of list | |
| LISEL | CHAR | 255 | List processing | Content of selected row | |
| LISTI | INT4 | 10 | List processing | Index of selected list | |
| LOCDB | CHAR | 1 | Obsolete | ||
| LOCOP | CHAR | 1 | Obsolete | ||
| LOOPC | INT4 | 10 | Screens | Number of rows visible in table | |
| LPASS | CHAR | 4 | Internal | ||
| LSIND | INT4 | 10 | List processing | Index of detail list | |
| LSTAT | CHAR | 16 | List processing | ID for list levels | |
| MACDB | CHAR | 4 | Obsolete | ||
| MACOL | INT4 | 10 | Printing Lists | Columns from SET MARGIN statement | |
| MANDT | CLNT | 3 | R/3 System | Client number from logon | |
| MARKY | CHAR | 1 | Obsolete | ||
| MAROW | INT4 | 10 | Printing Lists | Rows from SET MARGIN statement | |
| MODNO | CHAR | 1 | R/3 System | Index of external modes | |
| MSGID | CHAR | 20 | Messages | Message class | |
| MSGLI | CHAR | 60 | Messages | Message line | |
| MSGNO | NUMC | 3 | Messages | Message number | |
| MSGTY | CHAR | 1 | Messages | Message type | |
| MSGV1 | CHAR | 50 | Messages | Message variable | |
| MSGV2 | CHAR | 50 | Messages | Message variable | |
| MSGV3 | CHAR | 50 | Messages | Message variable | |
| MSGV4 | CHAR | 50 | Messages | Message variable | |
| NEWPA | CHAR | 1 | Internal | ||
| NRPAG | CHAR | 1 | Internal | ||
| ONCOM | CHAR | 1 | Internal | ||
| OPSYS | CHAR | 10 | R/3 System | Operating system of application server | |
| PAART | CHAR | 16 | Print parameters | Print formatting | |
| PAGCT | INT4 | 10 | Obsolete | ||
| PAGNO | INT4 | 10 | Creating Lists | Current page: | |
| PAUTH | NUMC | 2 | Internal | ||
| PDEST | CHAR | 4 | Print parameters | Output device | |
| PEXPI | NUMC | 1 | Print parameters | Retention period | |
| PFKEY | CHAR | 20 | Screens | Current GUI status | |
| PLAYO | CHAR | 5 | Internal | ||
| PLAYP | CHAR | 1 | Internal | ||
| PLIST | CHAR | 12 | Print parameters | Name of spool request | |
| PNWPA | CHAR | 1 | Internal | ||
| PRABT | CHAR | 12 | Print parameters
|
Part of cover sheet | |
| PRBIG | CHAR | 1 | Print parameters | Selection cover page | |
| PRCOP | NUMC | 3 | Print parameters | Number of copies | |
| PRDSN | CHAR | 6 | Print parameters | Name of spool dataset | |
| PREFX | CHAR | 3 | Obsolete | ||
| PRI40 | CHAR | 1 | Internal | ||
| PRIMM | CHAR | 1 | Print parameters | Print immediately | |
| PRINI | NUMC | 1 | Internal | ||
| PRLOG | CHAR | 1 | Internal | ||
| PRNEW | CHAR | 1 | Print parameters | New spool request | |
| PRREC | CHAR | 12 | Print parameters | Recipient | |
| PRREL | CHAR | 1 | Print parameters | Delete after print | |
| PRTXT | CHAR | 68 | Print parameters | Text for cover sheet | |
| REPI2 | CHAR | 40 | Internal | ||
| REPID | CHAR | 40 | ABAP Program | Current main program | |
| RSTRT | CHAR | 1 | Internal | ||
| RTITL | CHAR | 70 | Print parameters | Title of printing program | |
| SAPRL | CHAR | 4 | R/3 System | Release status R/3 System | |
| SCOLS | INT4 | 10 | Screens | Number of columns | |
| SFNAM | CHAR | 30 | Obsolete | ||
| SFOFF | INT4 | 10 | Internal | ||
| SLSET | CHAR | 14 | Selection screens | Name of variant | |
| SPONO | NUMC | 10 | Printing Lists | Spool number | |
| SPONR | NUMC | 10 | Obsolete | ||
| SROWS | INT4 | 10 | Screens | Number of rows | |
| STACO | INT4 | 10 | List processing | First displayed column | |
| STARO | INT4 | 10 | List processing | Uppermost displayed row | |
| STEPL | INT4 | 10 | Screens | Index of current table row | |
| SUBCS | CHAR | 1 | Internal | ||
| SUBRC | INT4 | 10 | Return value | Return value after ABAP statement | |
| SUBTY | RAW | 1 | Internal | ||
| SYSID | CHAR | 8 | R/3 System | Name of R/3 System | |
| TABID | CHAR | 8 | Internal | ||
| TABIX | INT4 | 10 | Internal Tables | Current row index | |
| TCODE | CHAR | 20 | ABAP Program | Current transaction code | |
| TFDSN | CHAR | 8 | Obsolete | ||
| TFILL | INT4 | 10 | Internal Tables | Current number of rows | |
| TIMLO | TIMS | 6 | Date and time | Local time of user | |
| TITLE | CHAR | 70 | Screens | Text in header line | |
| TLENG | INT4 | 10 | Internal Tables | Row size | |
| TLOPC | INT4 | 10 | Internal | ||
| TMAXL | INT4 | 10 | Obsolete | ||
| TNAME | CHAR | 30 | Obsolete | ||
| TOCCU | INT4 | 10 | Obsolete | ||
| TPAGI | INT4 | 10 | Obsolete | ||
| TSTIS | INT4 | 10 | Internal | ||
| TTABC | INT4 | 10 | Obsolete | ||
| TTABI | INT4 | 10 | Obsolete | ||
| TVAR0 | CHAR | 20 | Creating Lists | Text variable for headers | |
| TVAR1 | CHAR | 20 | Creating Lists | Text variable for headers | |
| TVAR2 | CHAR | 20 | Creating Lists | Text variable for headers | |
| TVAR3 | CHAR | 20 | Creating Lists | Text variable for headers | |
| TVAR4 | CHAR | 20 | Creating Lists | Text variable for headers | |
| TVAR5 | CHAR | 20 | Creating Lists | Text variable for headers | |
| TVAR6 | CHAR | 20 | Creating Lists | Text variable for headers | |
| TVAR7 | CHAR | 20 | Creating Lists | Text variable for headers | |
| TVAR8 | CHAR | 20 | Creating Lists | Text variable for headers | |
| TVAR9 | CHAR | 20 | Creating Lists | Text variable for headers | |
| TZONE | INT4 | 10 | Date and time | Time difference to Greenwich Mean Time | |
| UCOMM | CHAR | 70 | Screens | Function code that triggered PAI | |
| ULINE | CHAR | 255 | Constants | Horizontal line with length 255 | |
| UNAME | CHAR | 12 | R/3 System | Logon name of user | |
| UZEIT | TIMS | 6 | Date and time | Current (application server) time | |
| VLINE | CHAR | 1 | Constants | Vertical line | |
| WAERS | CUKY | 5 | Obsolete | ||
| WILLI | INT4 | 10 | Obsolete | ||
| WINCO | INT4 | 10 | Obsolete | ||
| WINDI | INT4 | 10 | Obsolete | ||
| WINRO | INT4 | 10 | Obsolete | ||
| WINSL | CHAR | 79 | Obsolete | ||
| WINX1 | INT4 | 10 | Obsolete | ||
| WINX2 | INT4 | 10 | Obsolete | ||
| WINY1 | INT4 | 10 | Obsolete | ||
| WINY2 | INT4 | 10 | Obsolete | ||
| WTITL | CHAR | 1 | Creating Lists | Flag for standard page header | |
| XCODE | CHAR | 70 | Internal | ||
| XFORM | CHAR | 30 | Internal | ||
| XPROG | CHAR | 40 | Internal | ||
| ZONLO | CHAR | 6 | Date and time | Time zone of user |
Thematic Overview
The following is a thematic summary of the system fields with notes on their use:
Introduction to SOA – Service Oriented Architecture
Definition
Service oriented architectures (SOA) is an architectural pattern which requires all exposed functionality to be published as services in a platform-independent manner. These services can be consumed by other applications.
To successfully utilize SOA on an enterprise level, you need to consider:
- All interfaces need to be clearly defined and stable and to make use of global data types they should avoid superfluous transformations caused by technically different definitions of semantically identical information.
To establish additional reliability, all services must follow clearly defined communication and behavioral patterns. For example – Clients need to know whether services are synchronous or asynchronous, whether they return an answer, how they handle exceptions, which security policy they use etc.
The overview
- A service in SOA is best explained as “Structure, Typing (as in Object Orientated and system design) and behaviour”.
- Best understood as “Message Based Integration”.
- A “Service Object” gives access to a business object and business functionality.
- A “Service Object” uses a “Service Interface”.
- A “Service” has a related signature and message types, which control the structure of the operation.
General categorization of Services
- A service can do a Query operation
- A service can do an Action operation
- A service can do a CRUD (Create Retrieve Update Delete) operation
The Service can be Synchronous or Asynchronous.
Basic Summary
Essentially SAP SOA can be seen as a set of standardizations of interfaces. For example one could move from having 3 different mapping rules and possible interfaces for a single business process, for example a price and availability check, to a single standardized SOA service.
Share Quick View Reports
Have you ever created a Quick View Report using SQVI and then wanted to share that report with another user?
You can do this simply by doing the following:
- Run SQVI
- Select the report name
- Select the menu path: Quick View–>Additional Functions –>Display Report Name
This will give you a dialog box with the report name sometimes with unusual characters such as “=” signs. Select the entire report name and share it with any user whom will be able to execute thee report by using the transaction code SA38.
EDI – IDoc Segment Qualifiers Actions Sundry tips
Have you ever looked for documentation on an IDoc type, listing all segments, all fields including descriptions in the segment and all actions/qualifiers or possible selection values for a field?
You can get all this information by generating a report on a specific IDoc type by using the following function module in Se37: IDOCTYPE_READ_COMPLETE
Put the IDoc basic type for example “ORDERS05” in the field “PI_IDOCTYP” then select the Test Icon.
Alternatively Should you wish to see all qualifiers for a specific segment you can use the Function module “SEGMENT_READ_COMPLETE”.
Enter the segment, for example “E1EDK02” in the field “PI_SEGTYP” and select the Test Icon. In this example segment you will find there are 92 possible qualifiers.
Unrelated Sundry EDI OSS notes
A great OSS note regarding EDI with 27 questions and answers is “SAP Note 456127 – FAQ: Electronic Data Interchange (EDI)in purchasing” .
Another OSS note which gives the settings to use in WE20 when you use the Message Control tab – ”SAP Note 389713 – VE 561: Partner nnn is not an EDI partner”.
