Working With Progress Indicator and Time Triggred UI Element in Webdynpro ABAP

Atrribute TIME is of type I and TIME_PRESENT is of type string. 

 OUTPUT :

 

Switch Framework in SAP

Here i am gonna show you , how to create a switch in ECC 6.0 and how can this switch be used !!!!! Other theory we can look out from google and other Switch framework posts :

We are going to append a structure to the data base table and the append structure will be linked to our switch..

Step 1 : Create a test package via SE80.

Step 2 : Goto T-code SFW1 and create a switch .

Step 3 : Goto T-code SFW2 and create a Enterprise Bussiness Function and more we can create Bussiness Function set via T-code SFW3.

Step 4 : Create a database table and an append structure .

Step : 5 Now goto T-code SFW5 and activate the corresponding Enterprise Bussiness Function. So that global status would become ON.

But make sure do not switch ON the switch with out proper necessity. Try to make the switch reversible..

Regards
Rahul Gupta

Filter Dependent BADI with example

User exit and customer exit......... and BADIs

I can remember the day , i was sitting in the office in SAP-LABS around 7:30 pm and was busying in doing some development . Suddenly my phone was shouting and the voice said , rahul is it good time for interview....his one of the question was "do have knowledge about user exit or customer exit??"....and i think i replied convincingly but later i realized i need to work on it...so here is little about user and customer exit......

User Exit : We can call it FORM exit also because whatever modification we are gonna do will be in subroutine. Below is the example : 

FORM USEREXIT_XXXX....
 INCLUDE ZZUSEREXIT.......
  ENDFORM.  

User exit is basically provided to SD module so we may find for many other module user exits are not available.

Customer exit : SAP creates customer exits for specific programs, screens, and menus within standard applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
Customer exits are nothing but a include in customer name space will be provided in the function module which starts with CALL CUSTOMER. You can fill them with your own source code. Technically this is an enhancement. User exits generally refer to SD module while customer exits refer to all modules like MM, SD, PP, FICO etc. Advantage:
- They do not affect standard SAP source code
- They do not affect software updates

Disadvantage:
- Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System.

Types of Customer Exits
1.     Function Module exits
2.     Screen exits
3.     Menu exits

 1.     Function Module exits
Function module exits are exits developed by SAP. The exit is implemented as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
           Format:  CALL CUSTOMER-FUNCTION '910'
 The naming standard of function modules for function module exits is: 
          EXIT__<3 digit suffix>

2.     Screen Exits:
Allow customer to add fields to a screen via a sub screen in an SAP program. The sub screen is called within the standard screen's flow logic.
         Format:  CALL CUSTOMER-SUBSCREEN CUSTSCR1
 3.     Menu exits:
Menu exits allow you to add your own functionality to menus. Menu exits are implemented by SAP and are reserved menu entries in the GUI interface. The developer can add his/her own text and logic for the menu.
Function codes for menu exits all start with "+".
   Format:  +CUS (additional item in GUI status) 

To know more about SAP Enhancement Frame , please click on the below URL ...please do watch..its good :)

http://www.sdn.sap.com/irj/scn/events?rid=/library/uuid/c0365021-ffd5-2b10-9085-d7de23b1aa58&overridelayout=true

:( :(

Today its birthday of one of my best friend to whom i used to know........but i can not wish.........anyways happy birth day dear......do well in your part......... :)

Difference between classic and new badi

As we can see from above picture , there is a big variation in calling of two BADIs. New BADI improves the performance of our code because now a days BADIs are being integrated on kernel level so in a way we can introduce one more term call Kernel level BADIs.

BADIs is new concept in enhancements framework introduced by SAP and based on OOPs. We can also migrate classic BADIs into somewhat new BADI (not exactly).

STYLE in ALV .........

In many requirements we are asked to make a particular cell editable based on some condition or make a particular cell as push button....So all this stuff can be done by ALV style segment .....
1. Add one field say STYLE type lvc_t_styl into the output table structure.
2.The field whose cell you want to make editable based on some condition , make its field catalog editable
  say ls_field_cat-edit = 'X'.
3.Now in layout pass style field name like ls_layout-stylfname = 'STYLE'.
4  w_style-fieldname = 'COMMODITY' .

w_style-style = cl_gui_alv_grid=>mc_style_enabled .
  APPEND w_style TO wa-cellstyles.
  MODIFY itab FROM wa INDEX 1 TRANSPORTING cellstyles.

Now if you see the italic and bold line ....the row inwhich we want to enable or diable

we can insert the style stuff in the same line.