SAP ABAP Online Magazine

Common Unicode Errors ( SAP Version ECC6.0 )

2009-09-08T09:26:00.000-07:00

Transaction Code to Perform Unicode Compliance check

TCode to perform Unicode Check : UCCHECK

How to Set the Unicode Flag Active

After resolving all the errors under the Unicode Check, we can set the Unicode Flag.
This can be done in either of the two ways.

1.From the Transaction UCCHECK itself, by selecting the success message of the
object and then clicking on the Set Unicode Attribute button .

2.Go directly to the object, Go To -> Attributes -> Change Display -> Check the
Unicode Flag Active -> Save -> Activate.

Some of the Common Errors in UCCHECK and their resolution.

Case - 1:

Error : Upload/Ws_Upload and Download/Ws_Download are obsolete, since they are not Unicode-enabled; use the class cl_gui_frontend_services

Cause : From Version ECC6.0 (Unicode complaint environment), the Function Mod-ules UPLOAD / WS_UPLOAD / DOWNLOAD / WS_DOWNLOAD has become obso-lete. In replacement of these Function Modules, we have GUI_UPLOAD / GUI_DOWNLOAD.

Solution: All the UPLOAD / WS_UPLOAD function modules need to be replaced with GUI_UPLOAD FM and all the DOWNLOAD / WS_DOWNLOAD with the GUI_DOWNLOAD function modules.

For replacing WS_UPLOAD :

*{ REPLACE EMPK900094 1
*\ call function 'WS_UPLOAD'
*\ exporting
*\ filename = p_filel
*\ filetype = 'DAT' "'ASC' "'DAT'
*\ tables
*\ data_tab = record
*\ exceptions
*\ conversion_error = 1
*\ file_open_error = 2
*\ file_read_error = 3
*\ invalid_type = 4
*\ no_batch = 5
*\ unknown_error = 6
*\ invalid_table_width = 7
*\ gui_refuse_filetransfer = 8
*\ customer_error = 9
*\ others = 10.

** Begin of Changes - 46C To ECC6 - IN9AGARWAL
DATA : L_P_FILEL TYPE STRING.
** End of Changes - 46C To ECC6 - IN9AGARWAL

** Begin of Changes - 46C To ECC6 - IN9AGARWAL
Clear: L_P_FILEL.
L_P_FILEL = P_FILEL.

CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
FILENAME = L_P_FILEL
FILETYPE = 'ASC'
TABLES
DATA_TAB = RECORD
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
NO_AUTHORITY = 6
UNKNOWN_ERROR = 7
BAD_DATA_FORMAT = 8
HEADER_NOT_ALLOWED = 9
SEPARATOR_NOT_ALLOWED = 10
HEADER_TOO_LONG = 11
UNKNOWN_DP_ERROR = 12
ACCESS_DENIED = 13
DP_OUT_OF_MEMORY = 14
DISK_FULL = 15
DP_TIMEOUT = 16
OTHERS = 17.

IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

Clear: L_P_FILEL.
** End of Changes - 46C To ECC6 - IN9AGARWAL
*} REPLACE

Note - 1 : The parameter FILENAME in GUI_UPLOAD is of type STRING for version ECC6.0. In 4.6C version (Non Unicode complaint environment), for the above code, ex-port parameter filename in UPLOAD / WS_UPLOAD was of data type “Character”. This need to be taken care of otherwise if an Extended Syntax Check is performed using the transaction SLIN, there would bet a Call Function Interface Error because of this. So to avoid that, one needs to declare a variable L_P_FILEL of type STRING and assign-ing that to the Parameter FILENAME. Also it’s better to have file type ‘ASC’.

For replacing WS_DOWNLOAD:

*{ REPLACE RE2K900049 1
*\ CALL FUNCTION 'WS_DOWNLOAD'
*\ EXPORTING
*\ FILENAME = W_FILENAME
*\ FILETYPE = 'ASC'
*\ TABLES
*\ DATA_TAB = TAB_PC2
*\ EXCEPTIONS
*\ FILE_OPEN_ERROR = 1
*\ FILE_WRITE_ERROR = 2
*\ INVALID_FILESIZE = 3
*\ INVALID_TYPE = 4
*\ NO_BATCH = 5
*\ UNKNOWN_ERROR = 6
*\ INVALID_TABLE_WIDTH = 7
*\ GUI_REFUSE_FILETRANSFER = 8
*\ CUSTOMER_ERROR = 9
*\ OTHERS = 10.
*\

** Begin of Changes - 46C To ECC6 - IN9AGARWAL
DATA : L_W_FILENAME TYPE STRING.
** End of Changes - 46C To ECC6 - IN9AGARWAL

** Begin of Changes - 46C To ECC6 - IN9AGARWAL
Clear: L_W_FILENAME.
L_W_FILENAME = W_FILENAME.

CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
FILENAME = L_W_FILENAME
FILETYPE = 'ASC'
TABLES
DATA_TAB = TAB_PC2
EXCEPTIONS
FILE_WRITE_ERROR = 1
NO_BATCH = 2
GUI_REFUSE_FILETRANSFER = 3
INVALID_TYPE = 4
NO_AUTHORITY = 5
UNKNOWN_ERROR = 6
HEADER_NOT_ALLOWED = 7
SEPARATOR_NOT_ALLOWED = 8
FILESIZE_NOT_ALLOWED = 9
HEADER_TOO_LONG = 10
DP_ERROR_CREATE = 11
DP_ERROR_SEND = 12
DP_ERROR_WRITE = 13
UNKNOWN_DP_ERROR = 14
ACCESS_DENIED = 15
DP_OUT_OF_MEMORY = 16
DISK_FULL = 17
DP_TIMEOUT = 18
FILE_NOT_FOUND = 19
DATAPROVIDER_EXCEPTION = 20
CONTROL_FLUSH_ERROR = 21
OTHERS = 22
.
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 of Changes - 46C To ECC6 - IN9AGARWAL

For replacing UPLOAD :

PARAMETERS: I_NFILE LIKE RLGRAP-FILENAME DEFAULT
'c:\fi\docgen.prn'.

Note : Please make sure that default location is given if its not then dont use default file-name parameter in your Function module.

*{ REPLACE RE2K900049 1
*\ CALL FUNCTION 'UPLOAD'
*\ EXPORTING
*\ FILENAME = I_NFILE "NOME FILE
*\ FILETYPE = 'ASC'
*\ TABLES
*\ DATA_TAB = FILIN
*\ EXCEPTIONS
*\ CONVERSION_ERROR = 1
*\ INVALID_TABLE_WIDTH = 2
*\ INVALID_TYPE = 3
*\ NO_BATCH = 4
*\ UNKNOWN_ERROR = 5
*\ OTHERS = 6.
*\

So we will be using the method ` GUI_UPLOAD` of the class `CL_GUI_FRONTEND_SERVICES`. Now in 4.6, while using FM UPLOAD, a pop-up used to appear, prompting you to get/locate the path of the file. To get the same function-ality in GUI_UPLOAD use code as below-

** Begin of Changes - 46C To ECC6 - IN9AGARWAL
data: ft type filetable,
rc type i,
l_i_nfile type string,
l_i_nfile_temp type string.

data: l_ft type line of filetable.
** End of Changes - 46C To ECC6 - IN9AGARWAL

** Begin of Changes - 46C To ECC6 - IN9AGARWAL
clear: l_i_nfile_temp, rc, l_ft, l_i_nfile.
refresh: ft.
l_i_nfile_temp = i_nfile.

CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_OPEN_DIALOG
EXPORTING
WINDOW_TITLE = 'File open'
DEFAULT_FILENAME = l_i_nfile_temp
CHANGING
FILE_TABLE = ft
RC = rc
EXCEPTIONS
FILE_OPEN_DIALOG_FAILED = 1
CNTL_ERROR = 2
ERROR_NO_GUI = 3
NOT_SUPPORTED_BY_GUI = 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.

read table ft into l_ft index 1.

l_i_nfile = l_ft-filename.

CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
FILENAME = l_i_nfile
FILETYPE = 'ASC'
TABLES
DATA_TAB = FILIN
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
NO_AUTHORITY = 6
UNKNOWN_ERROR = 7
BAD_DATA_FORMAT = 8
HEADER_NOT_ALLOWED = 9
SEPARATOR_NOT_ALLOWED = 10
HEADER_TOO_LONG = 11
UNKNOWN_DP_ERROR = 12
ACCESS_DENIED = 13
DP_OUT_OF_MEMORY = 14
DISK_FULL = 15
DP_TIMEOUT = 16
OTHERS = 17.

IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

clear: l_i_nfile_temp, rc, l_ft, l_i_nfile.
refresh: ft.

** End of Changes - 46C To ECC6 - IN9AGARWAL

For replacing DOWNLOAD :

DOWNLOAD is obsolete function module for storing SAP data in a file in the file sys-tem of the presentation server.
EXAMPLE :

PARAMETERS: PC_FILE LIKE RLGRAP-FILENAME DEFAULT
'c:\test.txt' modif id LOC.

* CALL FUNCTION 'DOWNLOAD'
* EXPORTING
* FILENAME = PC_FILE
* FILETYPE = 'DAT'
* IMPORTING
* FILESIZE = W_FSIZE
* ACT_FILENAME = W_FNAME
* ACT_FILETYPE = W_FTYPE
* TABLES
* DATA_TAB = TAB
* EXCEPTIONS
* CONVERSION_ERROR = 1
* INVALID_TABLE_WIDTH = 2
* INVALID_TYPE = 3
* NO_BATCH = 4
* UNKNOWN_ERROR = 5
* OTHERS = 6.

So we will be using the method `GUI_DOWNLOAD` of the class `CL_GUI_FRONTEND_SERVICES`. Now in 4.6, while using FM DOWNLOAD, a pop-up used to appear, prompting you to to put the path to save the file. To get the same functionality in GUI_DOWNLOAD use code as below-

** Begin of Changes - 46C To ECC6 - IN9AGARWAL
data: l_filename type string,
l_path type string,
l_fullpath type string,
l_filename_temp type string.
** End of Changes - 46C To ECC6 - IN9AGARWAL

** Begin of Changes - 46C To ECC6 - IN9AGARWAL
Clear: l_filename, l_path, l_fullpath, l_filename_temp.
l_filename_temp = PC_FILE.

CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_SAVE_DIALOG
EXPORTING
WINDOW_TITLE = 'File save'
DEFAULT_FILE_NAME = l_filename_temp
CHANGING
FILENAME = l_filename
PATH = l_path
FULLPATH = l_fullpath
EXCEPTIONS
CNTL_ERROR = 1
ERROR_NO_GUI = 2
NOT_SUPPORTED_BY_GUI = 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.

CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
FILENAME = l_filename
FILETYPE = 'ASC'
TABLES
DATA_TAB = tab
EXCEPTIONS
FILE_WRITE_ERROR = 1
NO_BATCH = 2
GUI_REFUSE_FILETRANSFER = 3
INVALID_TYPE = 4
NO_AUTHORITY = 5
UNKNOWN_ERROR = 6
HEADER_NOT_ALLOWED = 7
SEPARATOR_NOT_ALLOWED = 8
FILESIZE_NOT_ALLOWED = 9
HEADER_TOO_LONG = 10
DP_ERROR_CREATE = 11
DP_ERROR_SEND = 12
DP_ERROR_WRITE = 13
UNKNOWN_DP_ERROR = 14
ACCESS_DENIED = 15
DP_OUT_OF_MEMORY = 16
DISK_FULL = 17
DP_TIMEOUT = 18
FILE_NOT_FOUND = 19
DATAPROVIDER_EXCEPTION = 20
CONTROL_FLUSH_ERROR = 21
OTHERS = 22.
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 of Changes - 46C To ECC6 - IN9AGARWAL

Step-by-Step Guide for Using LSMW

2009-07-13T09:15:00.000-07:00

For Example :
LSMW to Update Customer Master Records with Transaction Recording

Call Legacy System Migration Workbench by entering transaction code LSMW. Every conversion task is grouped together as Project / Subproject / Object structure. Create a Project called LSMW_DEMO and a Subproject as CUSTOMERS and Object as CUST_REC as shown in

Figure 1.

The main screen of LSMW provides wizard-like step-by-step tasks, as shown in Figure 2. To complete your data conversion, you need to execute these steps in sequence. Once a step is executed, the cursor is automatically positioned to the next step.

Note that these steps may look different depending upon your Personal menu settings. You could make step numbers visible by ‘Numbers on’ icon or hidden by ‘Numbers off’ icon. You can execute a step by double-clicking on the row. Toggle icon ‘Doubleclick=Display’ or ‘Doubleclick=Edit’, makes the step in ‘display’ mode or ‘change’ mode.

Download Complete material :

Step By Step Guide

LSMW Guide

Ultimate SAP Course available on Net

2009-05-11T07:30:00.000-07:00

Still struggling to learn SAP? If you want to obtain SAP certification easily, I've got good news ...
“ Announcing: Former Siemens SAP Consultant Reveals The Goldmine Of SAP Materials & Courses Previously Only Available To SAP Insiders ... ”

Ultimate SAP Course : Certification Material Only in $47

Be among the rare few to own this highly-exclusive "plug-and-play" Ultimate SAP CBT Course System before it vanishes. This is previously available only to insiders and professionals in the SAP job industry.

Ultimate SAP Course : Certification Material Only in $47

The Fastest, Easiest Way To Learn Everything About SAP ... Previously Only Available In Seminars & SAP Training Centres.

Hundreds of high quality SAP software computer based training (Interactive CBTs) that guide you every step of the way

This Ultimate SAP course covers all major SAP modules including R/3, ERP, ABAP, DB, MM, Basis and more
Certification materials and resources with industry handbooks, workbooks and examination software applications
Step-By-Step Instructions walk you through the most common questions, issues and task you'll encounter with SAP.
Case study-based exercises help you build and test your knowledge and tips to warn about potential problems.
Learn about SAP module implementation, SAP business webflow and master SAP object programming
Flash enabled visual lessons with text and user interactivity to make learning SAP fun and simple.
Complete SAP modules with intelligent self assessment that advice and guides you like a real-life instructor
Exercises and study exam guides with Q&A to allow you to pass your certification examination with ease.

Ultimate SAP Course : Certification Material Only in $47

Workflow Step3 : Create a method.

2009-02-15T06:06:00.000-08:00

Next a method must be created without using any function module template. When creating the method ensure that the method call is synchronous - this means that the method doesn't require a terminating event.

A method can be synchronous or asynchronous. Synchronous Method
Method that, for the duration of its execution, assumes the process control and, after its execution, reports to the calling component (work item manager, in this case).
Synchronous methods can return the following data, if defined: Return parameters, one result and Exceptions.

Terminating events can also be defined for a single-step task described with a synchronous method. At runtime, the relevant work item is then terminated either when the synchronous method is successfully executed or when one of the defined terminating events occurs.

Asynchronous Method
Method that, after its execution, does not report directly to the calling component (work item manager, in this case).
Asynchronous object methods do not return results, parameters or exceptions.
At least one terminating event must be defined for a single-step task described with an asynchronous object method.
At runtime, the relevant work item is only terminated if one of the defined terminating events occurs.

Next set the status of this object type component to implemented. The methods are not implemented unless you once open their program. Select the method and open its program. It gives a message “Do you want to generate a template automatically for the missing section”. Click “Yes”. Inside the program insert the code “CALL TRANSACTION ‘FB03’. Display Financial Document.

Method: Z_METHODXX
Name: Method name: XX
Description: Method Description: XX

Edit à Change Release Status à Object Type Component à Implemented

Step 2 : WorkFlow Step2 : Create a business object

Step 3 : Workflow Step 3 : Create an event.

Workflow Step 3 : Create an event.

2009-02-08T04:43:00.000-08:00

Open the Object type in change mode. When you change your subtype the first step is to create a new event, this is done by selecting the Event node and clicking the create button. Give the event a name and a description. Next set the status of this object type component to implemented.

Event: Z_EVENT_XX
Name: Event name: XX
Description: Event Description: XX

Click on the new event and…

Edit à Change Release Status à Object Type Component à Implemented
(A small box sign vanishes from the right side of the event, indicating that it is implemented)
There can be multiple triggering events for a standard/customer task.

In R/3 4.0 the release strategy for new Object Types and Object Type Components (methods, attributes, events, etc.) was enhanced. Now when an object type and/or components are created, there are different statuses to select, based on its required purpose. The statuses are:

· Modeled - objects cannot be accessed at runtime. This is the status that is automatically set when an object type or component is created. Items with a modeled status cannot be referenced in any type of workflow task.

· Implemented - objects can be used internally in a test environment. They are accessible, but may not be stable (especially if no delegation has been defined).

· Released - objects are ready for production. Note: Local objects cannot be released.

· Obsolete - objects are typically replaced by new functionality or incompatible with previous versions. This status is optional.

WorkFlow Step2 : Create a business object

2009-02-01T09:11:00.000-08:00

Give the business object name prefixed with Z_.

Enter the following fields with values:
Object type: Z_TESTXX
This is the internal technical key. Page: 1
Object type can have maximum 10 characters. This must be unique across all object type. Objects are specific instances of object types at runtime.

Object name: Object_Name_for_XX
The object type is addressed with this name by external applications. This is a descriptive English name and can be up to 32 characters. This also must be unique across all object type.

Name: Object Name: XX
This is a meaningful name of the business object.

Description: Object Description: XX
Page: 1
Object description, can be up to 40 characters.

Program: Z_TESTXX
Each object type has an ABAP/4 program in which methods of the object are implemented. This program is generated automatically when you create or revise an object type.

Application: *
Page: 1
* indicates cross application.

Should you need to extend the components of an SAP delivered object, you can create a subtype and then “delegate” it back up to its supertype. This means that the supertype transparently acquires the new functionality. If this supertype is referenced by any SAP or custom application, the new functionality is available. Any supertype may have at most one delegation assigned to it. Delegations are client independent. Use the menu path Settings >System-wide to create a delegation.

Read More :

Step 1 : http://www.abapcode.info/2008/12/work-flow-for-beginners-step1.html

How to find BADI?

2009-01-20T20:05:00.000-08:00

1. Go to the TCode SE24 and enter CL_EXITHANDLER as object type.

2. In 'Display' mode, go to 'Methods' tab.

3. Double click the method 'Get Instance' to display it source code.

4. Set a breakpoint on 'CALL METHOD cl_exithandler=>get_class_name_by_interface'.

5. Then run your transaction.

6. The screen will stop at this method.

7. Check the value of parameter 'EXIT_NAME'. It will show you the BADI
for that transaction.

Five Ways to Delete Entry from Table

2008-12-29T22:53:00.000-08:00

Tip 1. Write the abap program.

loop at itab.
DELETE FROM "For Single Record
DELETE FROM TABLE " For Multiple Records
endloop.

2. Write BDC program.
Deletion data should be in flat file and Delete the Entry when required.

3. If data is in Custom tables

a. if table Maintenance exits : go to sm30, give the table name ---> display --> change
Select the Entries - ---> delete.
4. se11 ---> Table---> Display ---->Table content ---> Give Selection data ---> Edit ---> Delete selection entries.

or

Display data ----> Select Entries to be deleted---> table entry (menu item) ----> delete.

5. Go to se16 --> Enter table name ---> Enter selection entries --->
Execute --> Edit ---> Delete selection entries.

Work Flow For Beginners-Step1

2008-12-20T09:41:00.000-08:00

1:Find a standard business object - which relates to the desired master data.

Transaction SWLD

Definition Tools àSAP Business WorkflowàDevelopmentàDefinition ToolsàBusiness Object Builder (Transaction Code SW01)

Click on the Business Object Builder. The initial screen appears as follows.

Either search for an object by name in short description. Or use the IMG structure, which is accessed via the Business Object Repository button.

Position mouse cursor in the field Object/interface type and hit F4àIn the pop up window click Information SystemàSearch the business object created earlier or SAP standard business object. àSelect it and click display

Select all object types and the following screen appears. Here the businisess object BUS2054 has been explored, which is under Project Systems.

A business object has following components as shown in the figure:

A screen showing the components of the object is dispalyed as the following figure:

To be Continueed...................

Macros used in Workflow Programming

2008-12-15T23:16:00.000-08:00

The include file must have been included into the program in order to use these macros.
INCLUDE .

Declaring Container

SWC_CONTAINER . "Declaration
SWC_CREATE_CONTAINER . "Initialization

Writing value into container
SWC_SET_ELEMENT .
SWC_SET_TABLE .

Reading value from container
SWC_GET_ELEMENT .
SWC_GET_TABLE .

Creating a variable for the object reference
DATATYPE SWC_OBJECT.

Create the object reference.
SWC_CREATE_OBJECT .

To get Object Key and Object Type
SWC_GET_OBJECT_KEY .
SWC_GET_OBJECT_TYPE .

To execute Mehtod of Object
SWC_CALL_METHOD .
SWC_GET_TABLE_PROPERTY .
SWC_GET_PROPERTY SELF .

Raising Exceptions
EXIT_RETRUN
EXIT_OBJECT_NOT_FOUND

Setting Result Parameter of Synchronous method
SWC_SET_ELEMENT Result

Important Function Module of Workflow

2008-12-15T23:10:00.000-08:00

Function Modules Description
SWU_START_WORKFLOW To start Workflow
SWE_EVENT_CREATE To create Event
SWW_WI_DISABLE For locking of work items against execution
SWW_WI_ENABLE For enabling of work items against execution
SWW_WI_CONTAINER_READ To read the container elements of a particular work item
SWW_WI_DEADLINES_CHANGE To change the attributes of the deadline monitoring for a particular work item
SAP_WAPI_EXECUTE_WORKITEM To execute workitem of another user

Other Useul Link :
Important Transaction in Workflow
Workflow Benefits for the company
Introduction to SAP Workflow
Workflow ?
Org units in workflow steps?
Workflow performance tips

Important Transaction in Workflow

2008-12-15T22:46:00.000-08:00

SWDD Workfow Builder
PFAC Maintain Standard Role
PFTC Maintain Tasks
PFOM Create Organizational Assignments
PPOME Organization and Staffing Change
PPWFBUF Refresh client buffer
SWB_COND Workflow start conditions
SWEC Events for change document overview
SWEL Display Event Trace
SWELS Switch Event Trace on/off
SWES Consistancy Check for Event Linkage
SWETYPV Event Type Linkage
SWI1 Selection Report for Work Items
SWI11 Where used list for Tasks
SWI13 Authorization to Execute and Start Tasks
SWI14 Display workflow from object type
SWI2_DIAG Diagnosis of work item with errors
SWI2_FREQ Work items per task
SWI5 Workload analysis (by org unit)
SWI6 Workflows for object
SWIA Execute work items without agent check
SWL1 Dynamic columns for business workplace
SWPR Workflow restart after error
SWU0 Event simulation

SWU10 Workflow Trace Delete
SWU3 Verify workflow customizing (traffic light summary)
SWU8 Workflow Trace On/Off
SWU9 Workflow Trace Display
SWUD Workflow diagnostic tool
SWUE Event creation
SWUF Administration of workflow run time systems (delete work items, error monitoring)
SWUI Start Workflow (Split Screen)
SWUS Start Workflow (Test Environment)
SWWL Delete Work Item

What is the difference between unicode and nonunicode.For what purpose it is used?

2008-12-09T09:41:00.000-08:00

Unicode is a character encoding system similiar to ASCII. You can see the definiton for Unicode by Unicode consortium below.

Unicode is the universal character encoding, maintained by the Unicode Consortium.
This encoding standard provides the basis for processing, storage and interchange of text data in any language in all modern software and information technology protocols". Unicode covers all the characters for all the writing systems of the world, modern and ancient. It also includes technical symbols, punctuations, and many other characters used in writing text

The Unicode Standard is intended to support the needs of all types of users, whether in business or academia, using mainstream or minority scripts.

Most of the SAP implementations are done on Unicode system as it support all kind of languages, which is good for a company to expend their business. Another things is Unicode system requires 70% more storage area and processing speed to run the system perfactly.
There are systems like XI, which can work only on Unicode so it is always advisible to go for unicode then to non-unicode.

Reason for the SAP R/3 System Running Slow

2008-12-09T09:33:00.000-08:00

Check if there are long running jobs in the background during the peak times (SM50) or if users are running long running

transactions/big lists.

System performance cannot improve if Dia and Bck workprocess increased. In fact those itself will bring down the performance of the system.

* Do not allocate more the 2 bck process in peak hours
* Check if your hardWARE is adequately sized for these many users.
* Check for any jobs consuming more than 60% of you resource.
( STO6-DETAIL ANALYSIS-TOP CPU)

* Check if there is any NETWORK COLLISION AT SERVER AND USER END.
* Rate of ARCHIEVE LOG SWITCH OVER .
* All USERS use SAME SERVER AT A TIME
* Even USER with ALL SUPER USER AUTHORISATIION can bring DOWN SYSTEM PERFORMANCE AT TIMES
* TRANSPORTS, providing AUTHORISATION and EXECUTING RESOURCE CONSUMING REPORTS TO BE AVOIDED at PRIME TIME.

SAP Authorization, Profiles, Address

2008-11-29T09:32:00.000-08:00

The R/3 authorization concepts permits the assignment of general or finely detailed user authorizations. These assignments can reach down to the transaction, field and field value level. These authorizations are centrally administered in user master records and most allow the handling of certain R/3 components applicable to specific operations. Actions by a user may required several authorizations.
For example, to change a material master record, authorizations are required for the :
· Transaction change
· Specific material
· General authorization to work within the company code
RSUSR010 - Transaction Lists According to Selection With User, Profile or Object.
List of Transaction codes of the user.
RSUSR007 - List Users Whose Address Data is Incomplete
The program check for space in the address data field. To print the whole list, tick a field which is always
space. (e.g. Room No.)

Version 4.6x
RSUSR002_ADDRESS - Users by address data

In 4.6x you used Role for each users and SAP will generate the necessary profiles and authorizations.
PFCG - Basic Maintenance
Type in a meaningful ZXXX role name and click Create
Menu -> Transaction (insert all the transaction code for this role)
Authorization -> Change authorization data -> Generate

What is Transaction RZ10- Edit Profiles?

If you want to change things like the default Client 000 to 999, rdisp/max_wprun_time (dialog abap program runtime - standard = 300 seconds).
choose the instance profile
click Extended maintenance
click the display or change button
look for this parameter name login/system_client

Work Processor :-
rdisp/wp_no_dia DialogProcessor
rdisp/wp_no_vb UpdateProcessor
rdisp/wp_no_vb2 Update 2 Processor
rdisp/wp_no_enq Enquiry Processor rdisp/wp_no_btc BackgroundProcessor rdisp/wp_no_spo Spool Processor

Basis interview questions

2008-11-29T09:28:00.000-08:00

Ask him/her to describe how SAP handles Memory Management?
ST02 / ST03 In general via table buffers, you could go into the whole Work Process, roll in, roll out, heap (private) memory, etc. however just as a Unix or DBA admin would know, is you look this up when needed for the exact specifics.
Ask him/her to describe where they would look at the buffer statistics, and what steps they would use to adjust them?
ST02, RZ10

Ask him/her to describe how to setup a printer in SAP or where they would look to research why a user/users can not print?
SPAD, SP01, SM50, SU01

Interview to 3 general areas:
DB (what is the directory structure/ where are the files kept oracle alerts, init.ora, redo logs, archive logs, etc.; possibly some basics stuff like what to do "high level" when the archive directory fills up, etc. Keep this minimal as from a SAP basis admin point of view Oracle is just a big giant bit bucket and SAP can handle to the daily monitoring and maintenance itself.
OS (what is the directory structure (what is NFS mounted and why / where are the message files contained for the OS error log; basic commands for the OS eg. Unix, mv, cp, ls, grep, ps-ef, df-k, etc. That is pretty much all the SAP basis admin will need to know. Client/Server architecture.
SAP (what is the directory structure / where are files located ie. profiles - start, instance, default (what are they and what is the order of precendence) start is for statup only, instance is the first to be read then the default and if a given parameter cannot be found in the instance or then the default then the internal standard is taken from RZ10 setting.
You can ask them to ran Transaction codes to you. Menus constanly change so go with T-codes. He should have a good knowledge of the following areas; transports, user / print / spool / batch management, monitoring, client tools and copies, support packages, kernel patches, workload analysis, Roles and Security, etc.
The standard list of t-codes is pretty much
SM50, SM51, SM66, SM12, SM13, SM21, DB01, DB02, DB13, ST01, ST02, ST03, ST04, ST05, ST06, SU01, SUIM, PFCG, SCC4, SE01, SE09, SE10, SPAM, SM35, SM36, SM37, SPAD, SP01 SCC3, SCCL, SCC9 this are pretty much you heavy hitters for monitoring and support.
I would ask in general how he would troubleshoot the following:
- User cannot connect to SAP
check SAP logon settings, ping the host, check message server, check dispatcher, etc.
- User cannot print
check SAP user setup, check SPAD, check spools, check unix queue or print queue at the os level, etc
- System seems slow
check SM66, SM51, SM50, SM21, ST06, ST03, SMLG, AL08 etc.
Some important things to remember is to ask not get specific to your installation or specific system setup as all SAP instances are different, keep your question to general topics and general answers.
The most important thing to notice when choosing a candidate is not how they parrot back answers to you, but if they can a) think for themselves and b) they actually like to and will keep on learning as no one knows it all and c) they have a good background and willingness to perform analyis and will keep on digginging until the answer is found or until their resources are exhausted and then they will pull in what is required to figure it out.

Question about Go Live Check

2008-11-29T09:22:00.000-08:00

What's Go-Live Check?
Who's responsible for Go-Live Check?
What should we prepare before Go-Live Check?
How many times for Go-Live Check?(I mean that Go-
Live Check seperate into how many steps/types such as 3 times for 1 Month before Go-Live, 2 Weeks before Go-Live
and 2 Weeks after Go-Live etc.) What's recommend schedule for each time?
How can we proceed Go-Live Check?

You have to open a message in component XX-SER-TCC to find out if your installation is scheduled for a Go-Live check which is conducted by SAP and it’s partners.
Go-Live Functional Upgrade Analysis – ideally 6 months before Golive – basically checks your hardware requirement , will it be able to accommodate the increase in the functionalities caused by the Go-Live, also some parameter recommendations to fine-tune your system.
Go-Live Functional Upgrade Verification – This is normally 2 months after the Go-live which is to see e’thing is fine after the upgrade.
Then you have normal Earlywatch session , each installation is entitled for 2 free earlywatch session in a year, in this performance tuning is done for your system, hardware,memory, I/0 bottlenecks are identified.

Reports of all these sessions carried out by SAP is then sent to you in form a MS-Word document and you can follow the guidelines mentioned and call up SAP or mail the person who has done the session for you for any clarifications.
Usually once a session is scheduled.
SAP will contact you to open the connections for them, so that they can prepare the system before the actual session takes place , in which they see , if SDCC version is good enough so that they can download the data from your system into their internal system on which they carry out the analysis, see if SAPOSCOL is running and enough history data is there in ST03n for them to carry out reasonable analysis. If e’thing is set a download is scheduled on your system using SDCC for a day prior to the actual session , and on the day of the session you open the connections for them again and provide them with userid and password normally it is earlywatch in 066 client.

Get IDOC Number From Delivery Number and Invoice Number

2008-11-02T07:53:00.000-08:00

For Outbound IDOC ( Delivery) :

You can use the Tables SRRELROLES and IDOCREL outbound use LIKP

Steps :

(i) First get the ROLEID using the Delivery number as Objectkey and object type LIKP from the table SRRELROLES

(ii) Then pass the ROLEID to the table IDOCREL to ROLE_A , get the ROLE_B.

(iii) Use this ROLE_B supply to ROLEID of SRRELROLES table and put object type IDOC and get the objkey which is nothing But IDOC.

Inbound IDOC :

If it is inbound delivery the use the business object type BUS2015.

For Outbound IDOC ( Invoice ) :

You can use the Tables SRRELROLES and IDOCREL outbound use VBRK
Steps :
(i) First get the ROLEID using the Delivery number as Object key and object type VBRK from the table SRRELROLES

(ii) Then pass the ROLEID to the table IDOCREL to ROLE_A , get the ROLE_B.

(iii) Use this ROLE_B supply to ROLEID of SRRELROLES table and put object type IDOC and get the objkey which is nothing But IDOC. Inbound IDOC :
If it is inbound delivery the use the business object type BUS2015.

Abap code to add a check box for each record when a list is displayed

2008-09-30T10:21:00.000-07:00

REPORT ZSACHIN2.

TYPE-POOLS: slis.

*---internal tables

DATA: BEGIN OF it_flight OCCURS 0,
SEL, " add a single character field in the final output table
carrid LIKE sflight-carrid,
connid LIKE sflight-connid,
fldate LIKE sflight-fldate,
seatsmax LIKE sflight-seatsmax,
seatsocc LIKE sflight-seatsocc,
END OF it_flight,

*--internal tables for alv

it_fieldcat TYPE slis_t_fieldcat_alv,
wa_fcat LIKE LINE OF it_fieldcat,
layout TYPE slis_layout_alv,
it_sort type slis_t_sortinfo_alv,
wa_sort like line of it_sort.

DATA: BEGIN OF it_flight_sel OCCURS 0,
SEL,
carrid LIKE sflight-carrid,
connid LIKE sflight-connid,
fldate LIKE sflight-fldate,
seatsmax LIKE sflight-seatsmax,
seatsocc LIKE sflight-seatsocc,
END OF it_flight_sel.

data: wa_flight like it_flight.

* In the layout set give the name of the field
* whose checkbox will be created ( SEL as it has 1 char only )

layout-box_fieldname = 'SEL'.

*---start-of-selection .

START-OF-SELECTION.

CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'

EXPORTING
i_program_name = sy-repid
i_internal_tabname = 'IT_FLIGHT'
i_inclname = sy-repid
CHANGING
ct_fieldcat = it_fieldcat
EXCEPTIONS
inconsistent_interface = 1
program_error = 2.

*----get data

SELECT carrid
connid
fldate
seatsmax
seatsocc
FROM sflight
INTO CORRESPONDING FIELDS OF TABLE it_flight
UP TO 20 ROWS.

wa_fcat-do_sum = 'X'.
MODIFY it_fieldcat FROM wa_fcat TRANSPORTING do_sum
WHERE fieldname = 'SEATSOCC' .

wa_sort-fieldname = 'CARRID'.
wa_sort-group = 'UL'.
wa_sort-up = 'X'.
APPEND wa_sort TO it_sort.
clear wa_sort.

wa_sort-fieldname = 'CONNID'.
wa_sort-subtot = 'X'.
wa_sort-up = 'X'.
APPEND wa_sort TO it_sort.
clear wa_sort.

CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
EXPORTING
i_callback_program = sy-repid
I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
is_layout = layout
it_fieldcat = it_fieldcat
it_sort = it_sort
TABLES
t_outtab = it_flight
EXCEPTIONS
program_error = 1.

FORM user_command USING r_ucomm LIKE sy-ucomm
rs_selfield TYPE slis_selfield.

* Check function code
CASE r_ucomm.

* WHEN '&IC1'.
** Check field clicked on within ALVgrid report
* IF rs_selfield-fieldname = 'EBELN'.
** Read data table, using index of row user clicked on
* READ TABLE it_ekko INTO wa_ekko INDEX rs_selfield-tabindex.
** Set parameter ID for transaction screen field
* SET PARAMETER ID 'BES' FIELD wa_ekko-ebeln.
** Sxecute transaction ME23N, and skip initial data entry screen
* CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.
* ENDIF.

WHEN '&IC1'. "'&DATA_SAVE'. "user presses SAVE
loop at it_flight into wa_flight.

if wa_flight-Sel EQ 'X'.

* collecting records in table it_flight_sel to process further
append wa_flight to it_flight_sel.
clear wa_flight.

endif.
endloop.
ENDCASE.

ENDFORM.

Example ABAP Code to colour Selected row in ALV

2008-09-30T10:15:00.000-07:00

*&---------------------------------------------------------------------*
*& Report ZSACHIN_ALV_DEEP32

REPORT ZSACHIN_ALV_DEEP32.

TABLES: MARA.

TYPE-POOLS: SLIS.

DATA: BEGIN OF ITAB OCCURS 0,
MATNR TYPE MARA-MATNR,
ERSDA TYPE MARA-ERSDA,
ERNAM TYPE MARA-ERNAM,

* create a field of 4 char to fill the color
WA_COLOR(4) TYPE C,

END OF ITAB.

DATA: GT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
WA_FIELDCAT TYPE SLIS_FIELDCAT_ALV.

* create a field symbol to add color for the selected row
FIELD-SYMBOLS: LIKE ITAB.

DATA: gd_layout type slis_layout_alv.

START-OF-SELECTION.

SELECT MATNR ERSDA ERNAM FROM MARA INTO TABLE ITAB UP TO 100 ROWS.

WA_FIELDCAT-SELTEXT_L = 'MATERIAL NUMBER'.
WA_FIELDCAT-COL_POS = '1'.
WA_FIELDCAT-TABNAME = 'MARA'.
WA_FIELDCAT-hotspot = 'X'.
WA_FIELDCAT-no_zero = 'X'.
WA_FIELDCAT-FIELDNAME = 'MATNR'.

APPEND WA_FIELDCAT TO GT_FIELDCAT.
CLEAR WA_FIELDCAT.

WA_FIELDCAT-SELTEXT_L = 'Created On'.
WA_FIELDCAT-COL_POS = '2'.
WA_FIELDCAT-TABNAME = 'MARA'.
WA_FIELDCAT-FIELDNAME = 'ERSDA'.
WA_FIELDCAT-emphasize = 'C110'.

APPEND WA_FIELDCAT TO GT_FIELDCAT.
CLEAR WA_FIELDCAT.

WA_FIELDCAT-SELTEXT_L = 'Name of Person'.
WA_FIELDCAT-COL_POS = '3'.
WA_FIELDCAT-TABNAME = 'MARA'.
WA_FIELDCAT-FIELDNAME = 'ERNAM'.
WA_FIELDCAT-just = 'R'.
*WA_FIELDCAT-emphasize = 'C600'.

APPEND WA_FIELDCAT TO GT_FIELDCAT.
CLEAR WA_FIELDCAT.

* loop through thetable to update the color forthe selected row
LOOP AT ITAB ASSIGNING .

IF SY-TABIX = '5'.
-WA_COLOR = 'C311'.
ENDIF.

ENDLOOP.

*PERFORM GET_EVENTS.

* Give the name field in which we have filled the color code
gd_layout-info_fieldname = 'WA_COLOR'.
gd_layout-zebra = 'X'.

*GD_LAYOUT-edit = 'X'. " this will make the alv editable
" and for each record make a box on left side
GD_LAYOUT-no_vline = 'X'.

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
* I_INTERFACE_CHECK = ' '
I_BYPASSING_BUFFER = 'X'
* I_BUFFER_ACTIVE = ' '
I_CALLBACK_PROGRAM = sy-repid
* I_CALLBACK_PF_STATUS_SET = 'ZSACHIN1111'
I_CALLBACK_USER_COMMAND = 'FRM_USR_COMMAND'
I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
* I_CALLBACK_HTML_TOP_OF_PAGE = ' '
* I_CALLBACK_HTML_END_OF_LIST = ' '
* I_STRUCTURE_NAME = MARA etc
* I_BACKGROUND_ID = ' '
I_GRID_TITLE = 'TITLE OF THE GRID'
* I_GRID_SETTINGS =
IS_LAYOUT = GD_LAYOUT
IT_FIELDCAT = GT_FIELDCAT
* IT_EXCLUDING =
* IT_SPECIAL_GROUPS =
* IT_SORT =
* IT_FILTER =
* IS_SEL_HIDE =
* I_DEFAULT = 'X'
I_SAVE = 'A'
* IS_VARIANT = i_varient1
* IT_EVENTS =
* IT_EVENT_EXIT =
* IS_PRINT =
* IS_REPREP_ID =
* I_SCREEN_START_COLUMN = 0
* I_SCREEN_START_LINE = 0
* I_SCREEN_END_COLUMN = 0
* I_SCREEN_END_LINE = 0
* I_HTML_HEIGHT_TOP = 0
* I_HTML_HEIGHT_END = 0
* IT_ALV_GRAPHICS =
* IT_HYPERLINK =
* IT_ADD_FIELDCAT =
* IT_EXCEPT_QINFO =
* IR_SALV_FULLSCREEN_ADAPTER =
* IMPORTING
* E_EXIT_CAUSED_BY_CALLER =
* ES_EXIT_CAUSED_BY_USER =
TABLES
t_outtab = ITAB
EXCEPTIONS

PROGRAM_ERROR = 1
OTHERS = 2
.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

*FORM SAC_LAYOUT.

*ENDFORM.

FORM FRM_USR_COMMAND USING OK_CODE TYPE SY-UCOMM RS_SELFIELD TYPE SLIS_SELFIELD .

CASE OK_CODE.

WHEN 'PICK'.

READ TABLE ITAB INDEX RS_SELFIELD-TABINDEX.

PERFORM CALL_TRANS USING ITAB-MATNR.

ENDCASE.

ENDFORM.

FORM CALL_TRANS USING MATNR.

SET PARAMETER ID 'MAT' FIELD MATNR. "Global memory sap memory.

CALL TRANSACTION 'MM02' AND SKIP FIRST SCREEN.

ENDFORM.

form PFSTATUS.

*SET PF-STATUS 'ZSACHIN1111'.

ENDFORM.

FORM TOP_OF_PAGE.

WRITE: 'SACHIN THE BOND'.

ENDFORM.

Example ABAP Code to colour individual box in ALV

2008-09-30T10:13:00.001-07:00

REPORT ZSACHIN_ALV_DEEP33.

TABLES: MARA.

TYPE-POOLS: SLIS.

DATA: BEGIN OF ITAB OCCURS 0,
MATNR TYPE MARA-MATNR,
ERSDA TYPE MARA-ERSDA,
ERNAM TYPE MARA-ERNAM,
* Create a field CELL of type SLIS_T_SPECIALCOL_ALV
CELL TYPE SLIS_T_SPECIALCOL_ALV,
END OF ITAB.

DATA: GT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
WA_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
* Create a work area of type SLIS_T_SPECIALCOL_ALV
DATA: FS_CELL LIKE LINE OF ITAB-CELL.

* Create a layout
DATA: gd_layout type slis_layout_alv.

*-----------------------------------------------------------------*
* START OF SELECTION *
*-----------------------------------------------------------------*

START-OF-SELECTION.

SELECT MATNR
ERSDA
ERNAM
FROM MARA
INTO CORRESPONDING FIELDS OF
TABLE ITAB UP TO 100 ROWS.

*-----------------------------------------------------------------*
* Creating field catalog *
*-----------------------------------------------------------------*

WA_FIELDCAT-SELTEXT_L = 'MATERIAL NUMBER'.
WA_FIELDCAT-COL_POS = '1'.
WA_FIELDCAT-TABNAME = 'MARA'.
WA_FIELDCAT-hotspot = 'X'.
WA_FIELDCAT-no_zero = 'X'.
WA_FIELDCAT-FIELDNAME = 'MATNR'.

APPEND WA_FIELDCAT TO GT_FIELDCAT.
CLEAR WA_FIELDCAT.

WA_FIELDCAT-SELTEXT_L = 'Created On'.
WA_FIELDCAT-COL_POS = '2'.
WA_FIELDCAT-TABNAME = 'MARA'.
WA_FIELDCAT-FIELDNAME = 'ERSDA'.
WA_FIELDCAT-emphasize = 'C611'.

APPEND WA_FIELDCAT TO GT_FIELDCAT.
CLEAR WA_FIELDCAT.

WA_FIELDCAT-SELTEXT_L = 'Name of Person'.
WA_FIELDCAT-COL_POS = '3'.
WA_FIELDCAT-TABNAME = 'MARA'.
WA_FIELDCAT-FIELDNAME = 'ERNAM'.
WA_FIELDCAT-just = 'R'.
*WA_FIELDCAT-emphasize = 'C600'.

APPEND WA_FIELDCAT TO GT_FIELDCAT.
CLEAR WA_FIELDCAT.

* Fill the workarea with the field to be colored,
* the color to be appeared
* and give NOKEYCOL = 'X'.

FS_CELL-FIELDNAME = 'ERSDA'.
FS_CELL-COLOR-COL = 3.
FS_CELL-NOKEYCOL = 'X'.
APPEND FS_CELL TO ITAB-CELL.

* To the specific row modify the contents of the CELL
MODIFY ITAB INDEX 8 TRANSPORTING CELL.

*PERFORM GET_EVENTS.

gd_layout-info_fieldname = 'WA_COLOR'.
gd_layout-zebra = 'X'.

* Give the name field in which we have filled the color code
gd_LAYOUT-COLTAB_FIELDNAME = 'CELL'.

*GD_LAYOUT-edit = 'X'. " this will make the alv editable
" and for each record make a box on left side
GD_LAYOUT-no_vline = 'X'.

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
* I_INTERFACE_CHECK = ' '
I_BYPASSING_BUFFER = 'X'
* I_BUFFER_ACTIVE = ' '
I_CALLBACK_PROGRAM = sy-repid
* I_CALLBACK_PF_STATUS_SET = 'ZSACHIN1111'
I_CALLBACK_USER_COMMAND = 'FRM_USR_COMMAND'
I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
* I_CALLBACK_HTML_TOP_OF_PAGE = ' '
* I_CALLBACK_HTML_END_OF_LIST = ' '
* I_STRUCTURE_NAME = MARA etc
* I_BACKGROUND_ID = ' '
I_GRID_TITLE = 'TITLE OF THE GRID'
* I_GRID_SETTINGS =
IS_LAYOUT = GD_LAYOUT
IT_FIELDCAT = GT_FIELDCAT
* IT_EXCLUDING =
* IT_SPECIAL_GROUPS =
* IT_SORT =
* IT_FILTER =
* IS_SEL_HIDE =
* I_DEFAULT = 'X'
I_SAVE = 'A'
* IS_VARIANT = i_varient1
* IT_EVENTS =
* IT_EVENT_EXIT =
* IS_PRINT =
* IS_REPREP_ID =
* I_SCREEN_START_COLUMN = 0
* I_SCREEN_START_LINE = 0
* I_SCREEN_END_COLUMN = 0
* I_SCREEN_END_LINE = 0
* I_HTML_HEIGHT_TOP = 0
* I_HTML_HEIGHT_END = 0
* IT_ALV_GRAPHICS =
* IT_HYPERLINK =
* IT_ADD_FIELDCAT =
* IT_EXCEPT_QINFO =
* IR_SALV_FULLSCREEN_ADAPTER =
* IMPORTING
* E_EXIT_CAUSED_BY_CALLER =
* ES_EXIT_CAUSED_BY_USER =
TABLES
t_outtab = ITAB
EXCEPTIONS

PROGRAM_ERROR = 1
OTHERS = 2
.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

*FORM SAC_LAYOUT.

*ENDFORM.

FORM FRM_USR_COMMAND USING OK_CODE TYPE SY-UCOMM RS_SELFIELD TYPE SLIS_SELFIELD .

CASE OK_CODE.

WHEN 'PICK'.

READ TABLE ITAB INDEX RS_SELFIELD-TABINDEX.

PERFORM CALL_TRANS USING ITAB-MATNR.

ENDCASE.

ENDFORM.

FORM CALL_TRANS USING MATNR.

SET PARAMETER ID 'MAT' FIELD MATNR. "Global memory sap memory.

CALL TRANSACTION 'MM02' AND SKIP FIRST SCREEN.

ENDFORM.

form PFSTATUS.

*SET PF-STATUS 'ZSACHIN1111'.

ENDFORM.

FORM TOP_OF_PAGE.

WRITE: 'SACHIN THE BOND'.

ENDFORM.

How to put Logo or photo in ALV Report

2008-09-30T10:05:00.000-07:00

Logo should be uploaded into application server using transaction 'OAER'.
1. Go to Transaction OAER,
2. Give Class Name as PICTURES
3. Class type as OT
4. Object Key is the name you want to search or you want to upload.
5. Then select the Document from below after double click on it .Choose in screen for logos.
6. Upon execution you would be prompted to give the file path details. Just upload which ever logo u want to display
7. Now you can use the same name in your ALV FM.
In your ALV program, you need to have event for TOP_OF_PAGE, and also this works only in case of Grid not in ALV LIST.

Look at the sample code to display LOGO.

**********************

call function 'REUSE_ALV_GRID_DISPLAY'
exporting
i_callback_program = i_repid
it_fieldcat = header
is_layout = gt_layout
i_callback_top_of_page = 'TOP-OF-PAGE1'
i_grid_title = xyz
it_sort = gt_sort[]
i_default = 'X'
i_save = 'U'
is_variant = gt_variant
it_events = gt_events
tables
t_outtab = t_output.

*****************

*-------------------------------------------------------------------*

* Form TOP-OF-PAGE1

*-------------------------------------------------------------------*

form top-of-page1.

data: header type slis_t_listheader,
wa type slis_listheader.

* TITLE AREA

wa-typ = 'S'.
wa-info = text-h04.
append wa to header.

wa-typ = 'S'.
write sy-datum to wa-info mm/dd/yyyy.

concatenate text-h03 wa-info into wa-info separated by space.
append wa to header.

wa-typ = 'S'.
concatenate text-h02 sy-uname into wa-info separated by space.
append wa to header.

wa-typ = 'S'.
concatenate text-h01 sy-repid into wa-info separated by space.
append wa to header.

********" LOGO

call function 'REUSE_ALV_COMMENTARY_WRITE'

exporting

it_list_commentary = header

i_logo = 'ENJOYSAP_LOGO'.

*********" LOGO

endform.

Here in TOP-OF-PAGE form it will show you the Prog name,Date, User Name

How to Hide Parameters on Selection Screen

2008-09-25T07:33:00.000-07:00

REPORT ZSACHIN_ALV_DEEP27.

*----------------------------------------------------------------------*
* T A B L E S *
*----------------------------------------------------------------------*

tables: mara, skb1, BSEG.

*----------------------------------------------------------------------*
* S E L E C T I O N S C R E E N *
*----------------------------------------------------------------------*

selection-screen: Begin of block b1 with frame title text-001.

parameters : R1 radiobutton group g1 default 'X' user-command AA.

select-options : s_bukrs for skb1-bukrs MODIF ID AA.
parameters : p_GJAHR type bseg-GJAHR MODIF ID AA.
parameters : p_MONAT type bkpf-MONAT MODIF ID AA.
select-options : s_SEG for BSEG-SEGMENT MODIF ID AA.

parameters : R2 radiobutton group g1.

select-options: s1_bukrs for skb1-bukrs MODIF ID CC.
parameters: p1_GJAHR type bseg-GJAHR MODIF ID CC.
parameters: p1_MONAT type bkpf-MONAT MODIF ID CC.
select-options: s1_SEG for bseg-SEGMENT MODIF ID CC.
select-options: s1_PRCTR for bseg-PRCTR MODIF ID CC.

selection-screen: end of block b1.

*----------------------------------------------------------------------*
* AT S E L E C T I O N S C R E E N O U T P U T *
*----------------------------------------------------------------------*

At selection-screen output.

If R1 = 'X'.

loop at screen.

if screen-group1 = 'AA'.
screen-input = '1'.
modify screen.
endif.

if screen-group1 = 'CC'.
screen-input = '0'.
modify screen.
endif.

endloop.

elseif R2 = 'X'.

loop at screen.

if screen-group1 = 'AA'.
screen-input = '0'.
modify screen.
endif.

if screen-group1 = 'CC'.
screen-input = '1'.
modify screen.
endif.

endloop.

endif.

ALV Report Code to add a check box for each record when a list is Displayed

2008-09-11T10:54:00.001-07:00

SELECTING THE VARIANTS FOR INITIAL ALV LIST DISPLAY

2008-09-04T08:20:00.001-07:00

The variants in the list display can be both user-specific and general. The user can programmatically set the initial (default) variant for list display.
The default variant can be found using the function module 'REUSE_ALV_VARIANT_DEFAULT_GET'.

Sample code:

CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
EXPORTING
i_save = variant save condition (A=all, U = user-specific)
CHANGING
cs_variant = internal table containing the program name (and the default variant---optional)
EXCEPTIONS
not_found = 2.
The user can also choose from the list of existing variants using the function module ‘REUSE_ALV_VARIANT_F4’.

Example:

Initialization.
v_repid = sy-repid.
* Display default variant
PERFORM SUB_VARIANT_INIT.

AT SELECTION-SCREEN ON P_VAR.
* Once the user has entered variant, check about its existence
PERFORM SUB_CHECK_PVAR.

AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_VAR.
* Display a list of various variants of the report when the User presses F4 key in the variant field
PERFORM SUB_VARIANT_F4.

*&---------------------------------------------------------------------*
*& Form SUB_VARIANT_INIT
*&---------------------------------------------------------------------*
* Display default variant
*&---------------------------------------------------------------------*
Form SUB_VARIANT_INIT.
I_VARIANT1-REPORT = SY-REPID.

* Search default variant for the report
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
EXPORTING
i_save = 'A'
CHANGING
cs_variant = i_variant1
EXCEPTIONS
not_found = 2.
* If default variant is found, use it as default.
* Else, use the variant LAYOUT1.
IF sy-subrc = 0.
p_var = i_variant1-variant.
ELSE.
p_var = 'LAYOUT1'.
ENDIF.
endform. “SUB_VARIANT_INIT

*&---------------------------------------------------------------------------------*
*& Form SUB_CHECK_PVAR
*&---------------------------------------------------------------------------------*
* Once the user has entered variant, check about its existence
*&---------------------------------------------------------------------------------*

FORM SUB_CHECK_PVAR.
* If the name of the variable is not blank, check about its existence
if not p_var is initial.
clear i_variant.
i_variant-report = sy-repid.
i_variant-variant = p_var.
CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
EXPORTING
I_SAVE = 'A'
CHANGING
CS_VARIANT = I_VARIANT.
* If no such variant found, flash error message
If sy-subrc ne 0 .
Message e398(00) with 'No such variant exists'.
Else.
* If variant exists, use the variant name to populate structure
* I_VARIANT1 which will be used for export parameter: IS_VARIANT
* in the function module : REUSE_ALV_GRID_DISPLAY
Clear i_variant1.
Move p_var to i_variant1-variant.
Move sy-repid to i_variant1-report.
endif.
Else.
Clear i_variant.
endif.
ENDFORM. “SUB_CHECK_PVAR

*&---------------------------------------------------------------------------------*
*& Form SUB_VARIANT_F4
*&---------------------------------------------------------------------------------*
* Display a list of various variants of the report when the User presses F4 key in the variant field
*&---------------------------------------------------------------------------------*
Form SUB_VARIANT_F4.
i_variant-report = sy-repid.
* Utilizing the name of the report, this function module will search for a list of
* variants and will fetch the selected one into the parameter field for variants
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
EXPORTING
IS_VARIANT = I_VARIANT
I_SAVE = 'A'
I_DISPLAY_VIA_GRID = 'X'
IMPORTING
ES_VARIANT = I_VARIANT1
EXCEPTIONS
NOT_FOUND = 1
PROGRAM_ERROR = 2
OTHERS = 3.
IF SY-SUBRC = 0.
P_VAR = I_VARIANT1-VARIANT.
ENDIF.
endform. “SUB_VARIANT_F4