Samrtform in Hindi Language

Language translation is the facility given by SAP for handling the output text font, location or login language wise. The following case shows how we can handle language hindi in smartforms for display. The same can be replaced with any other language that SAP supports or can be included explicitly.

Pre-requisite:-

1.       You must have Unicode enabled SAP version.

2.       Your PC must have hindi language installed on it.

           That is if you open MS word then you must be able to type Hindi.

Now coming back to SAPScript/Smartforms.

1.       Check using T-code I18N, whether Hindi pack is included in SAP environment. It is basically a Basis activity.

2.       Maintain Text Modules for Smartforms in T-code Smartforms. These Text modules we will use to convert it into Hindi.

3.       Use standard Translation Environment (T-code SE63) for maintaining the Hindi Translation of Text Modules. Goto SE63 -> Translation -> ABAP objects -> Other Long Texts -> B5 SAPscript: Forms and Styles -> SSF SAP Smart form. Here provide the Text Module you created previously and give source Language as EN and Target Language as HI and maintain the corresponding Hindi text for the same.

4.       Now in T-code Smartforms when creating new smartform, give Text Module as Text Type, Text Module Name, the one you created earlier and select ‘HI’ as the translation language. The corresponding Text Module with Text will be shown below.

5.       Now Test the new smartform created. It will now show the desired text converted into Hindi Font.

Technical Upgrade - SPDD & SPAU Phase

In upgrade project SPDD and SPAU are the main transactions. In general, a upgrade project are like

• Technical Upgrade
• Functional Upgrade

In a typical technical Upgrade project process steps like

1. System preparation and stack level patch upgrade – Basis Team
2. SPDD Phase – ABAP and Functional
3. Up grade of the system – Basis Team
4. SPAU Phase – ABAP and Functional
5. DBACOCKPIT for indexing –  (Issue resolution and error tracking) – ABAP TEAM and Functional
6. Custom programs corrections – obsolete function modules and objects

SPDD Phase

This transaction code SPDD is the core step in an upgrade project. The system compares all the dictionary objects – data elements, database tables and structures of the latest system (say CRM 70. EPH1) with the previous or the old system (e.g CRM 4.0).

These all elements are present under two nodes – with modification assistant and without modification assistant. Objects present under with modification assistant have the modification assistant ‘ON’ and we can see the modification logs.The objects in green color as shown below are the objects processed already and the ones in blue are the ones which still need to be processed. Apart from the nodes – ‘With modification assistant ‘and ‘Without modification assistant ‘, there is one more node sometimes – ‘Deleted objects’. This node contains objects which are deleted in the newer version of SAP and this node is to be left as it is. The objects under ‘With modification assistant’ and ‘Without modification assistant’ are to be processed by the ABAP team.

The ABAP team clicks on the objects one by one – it takes us to the corresponding object – data element, structure or database table in the SE11 transaction code where we need to do the version comparison of the object. Click on Utilities -> Versions ->Version Management. There it shows all the versions of the object. The topmost or the latest version is of the Latest SAP Version and the versions below are the previous or modified versions.

Now, we need to compare the Latest SAP version with the previous versions. Click on the check boxes of the two versions to compare and then click on the ‘compare’ button. We have to choose two and only two versions in order to compare them. In the comparison, it shows the differences in the two versions. We can click the Delta Comparison to see the delta differences between the two versions of the object. Now, after seeing the comparison, the developer has to decide whether he/she wants to keep the Latest SAP version (CRM) of the object. (Reset to Original) or he/she wants to keep the changes made or modifications made (Adapt Modification) in the previous system (4.0).

When we click on it and go to the version comparison, suppose it shows that 2 new fields are added in the Latest SAP version (CRM), when compared to the older version (4.0).The developer has to analyze the pros and corns of this objects – If he/she resets the table to original in SPDD, the 2 new fields would be added in the table MARA. If he Adapts modification, whenever any transaction or any program tries to store or read any value from the two new fields, it might give a short dump. So in this case, it is better to go for ‘Reset to original’.

SPAU Phase

The SPAU transaction contains the objects – Programs, Reports, Screens, Messages, Notes, Function Modules etc. which have difference in the Latest SAP request and the previous ones. This SPAU phase can be done either just after SPDD or after the Upgrade of the system by the Basis team.

The same way we need to compare the objects in ‘Version Management’ and decide weather to ‘Reset to Original’ or ‘Adapt Modification’. The ‘Adapt Modification is however slightly different for codes – Function modules, reports etc. In adapt modification, the SPAU gives us the empty space to write our code – by having a reference to the code in previous request, we can decide and write the code with some corrections when required. This is in the case of objects present in ‘Without Modification Assistant’.

In case of ‘With modification Assistant’, it opens a the program code in grey mode and we can insert or delete or modify code by pressing corresponding buttons in a similar way we do to modify any SAP standard code by using the access key.

The objects present in SPAU do not require any access key for a period of around 15-20 days after which SAP automatically locks those codes and after this locking, if we want to change or delete any code in SPAU objects, we would require an access key. So it is a good practice to finish the SPAU phase in 10-15 days time. In SPAU also, only one transport request is to be made for all objects as a best practice.

Distribution List for sending mails to multiple Id's

By creating distribution list you can maintain as many email id’s as you want in one distribution list and then attach that distribution list name while scheduling the background job so by doing this you can send mail to multiple people through single distribution list object.

T-Code: SO15

Give Distribution List Type as Private and give name and Title of distribution List. Click on Create.

In Attributes Tab Take F4 at Folder Option.

Select Private Radio Button and Continue(Press Enter).

Double click on OUTBOX.

Click Continue(Press Enter).

Go To Disstr. List Content Tab.

Enter Email IDS and SAVE.

Go to transaction SM36 to Schedule a program and send mail to all EmailIDS in newly created distribution List.

Click start condition.

Click immediate and check and save.

Click Step.

Give Program Name.

Choose Variant & then save.

Click Back & Click Spool list Recipient Button.

Take F4 on recipient Box.

Choose Distribution lists Radio Button & click Continue.

Click Continue.

Choose distribution list which we have created.

Choose (Enter).

Choose (Enter).

Click Save.

See Status below that new job has been saved with status Released.

Check Own Jobs.

Find your Job on list.

Once the job is complete go to transaction: sost.

Mails are sent to all Email IDS in the Distribution List.

Enhance Standard Search Help - Append Search Help SAP ABAP

Hi All,

Below article discuss how to enhance a standard search help. When there is a standard collective search help and you are required to add another search help criteria to the same, you can use this "append search help" method. Newly appended help will shown in the standard search help as another tab.

In this example standard search help 'AANL' which is the search help for assets would be enhanced. New custom append 'Serial Number Help' will be added as below.

Before append:

After append:

Summary of steps:

1. Create database view.
2. Create elementary search help.
3. Append standard search help.

Step 1: Create Database View.

In order to create elementary search help in step 2 we make use of a database view in this example. You can use any other method depending on your requirement.

Go to transaction SE11 and provide view name.

Tables used for view are ANLA and ANLZ. 

Set the join conditions.

Set view fields.

Set selection filter criteria.

Save and activate.

Step 2: Create Elementary Search Help.

Go to transaction SE11.

Select "Elementary Search Help" option.

Set the selection method with the database view created above.

Set import and export parameters of the search help. Import parameters are the selection criteria of the search help and export parameters set the output of the hit-list.

Save and active the search help.

Step 3: Append Standard Search Help.

Go to transaction SE11. Set the search help name and click display.

Select append from "Goto" under main menu.

Press "Create".

Set append name.

Select "Include Search Help" tab and add elementary search help created under step 2.

Select the elementary search help added and click "Param. Assignment". Click propose button to get the system proposed parameters.

Save and activate.

Newly added search help will be shown in a new tab under the collective search help.

search help, elementary search help, collective search help, database view, se11, DDIC, SAP, ABAP, append, search help append, enhancement, modify, enhance search help, Isuru Fernando earn money , stock, cars,bike,