Posts

Introduction to workflows in ABAP

  Workflow Definition: This is the blueprint of the workflow, specifying the sequence of tasks, the roles involved, and the conditions for each step. Workflow Tasks: These are individual activities or steps within the workflow. Tasks can be standard tasks provided by SAP or custom tasks developed by ABAP developers. Business Objects: Workflows often interact with business objects, which are SAP entities (e.g., Purchase Orders, Sales Orders) that represent real-world business items. Agents: These are the users or user groups responsible for completing specific tasks within the workflow. Agents are typically determined based on roles or attributes. Events: Workflows are triggered by events, which are specific actions or changes in the system (e.g., a purchase order is created). Workflow Templates: These are reusable models that define common processes. Templates can be used as the basis for creating new workflows. Workflow Builder: This is a graphical tool used to design and configure

Trigger a workflow when PR is changed

Image
                                          Steps to trigger workflow for PR                                        Object -  BUS2105 Step-1:  Goto T-code  SWDD. Step-2:  Click on  create workflow  button (left top corner) and  save  the workflow. Step-3:  Select  workflow container  in left side and double click on  click to create . Step-4:  Give  element name ,  name ,  short description  under D.type tab. Select  import  under properties tab.  Step-5:  Press  enter  and click on  save. Step-6:  Link the object --  Goto =>  Basic data => click on  start events tab. Step-7:  Select category  'BO'  give object type  'BUS2105 ' and select event  'CHANGED'. Step-8:  Click on  binding  and press enter and click on  active. Step-9:   Save  the workflow and  back  to workflow screen. Step-10:   Right click  on undefined and  click on create  double click on  user decision. Step-11:  Give title like this ( PR &1 Approve/Reject) .  &1 replaced with paramet

Trigger a workflow when Material data (MM01) is created

Image
                                                         Steps to trigger workflow for MM01                                      Object - BUS1001006 Step-1:  Goto T-code  SWDD. Step-2:  Click on  create workflow  button (left top corner) and  save  the workflow. Step-3:  Select  workflow container  in left side and double click on  click to create . Step-4:   Give   element name ,   name ,   short description   under D.type tab. Select   import   under properties tab.  Step-5:  Press  enter  and click on  save. Step-6:  Link the object --  Goto =>  Basic data => click on  start events tab. Step-7:  Select category  'BO'  give object type  'BUS1001006 ' and select event  'CREATED'. Step-8:  Click on  binding  and press enter and click on  active. Step-9:   Save  the workflow and  back  to workflow screen. Step-10:   Right click  on undefined and  click on create  double click on  user decision. Step-11:  Give title like this ( PR &1 Approve/Reject) .  &

Trigger a workflow when PR is created

Image
                                        Steps to trigger workflow for PR                              Object - BUS2105 Step-1: Goto T-code SWDD. Step-2: Click on create workflow button (left top corner) and save the workflow. Step-3: Select workflow container in left side and double click on click to create . Step-4: Give element name , name , short description under D.type tab. Select import under properties tab.  Step-5: Press enter and click on save. Step-6: Link the object -- Goto => Basic data => click on start events tab. Step-7: Select category 'BO' give object type 'BUS2105 ' and select event 'CREATED'.   Step-8: Click on binding and press enter and click on active. Step-9: Save the workflow and back to workflow screen. Step-10: Right click on undefined and click on create double click on user decision. Step-11: Give title like this ( PR &1 Approve/Reject) . &1 replaced with parameter1. Step-12: Take search help from

How to customize the Name of Tab in Debugging.

Image
  How to customize the Name of Tab * Another rarely used options are, by default , the tab labels are like Desktop 1 , Desktop 2 , and Desktop 3 . These labels can be customized. *  To rename the Label as something other than                 Desktop 1 -> Session 1 ,                 Desktop 2 -> Session 2 ,                Desktop 3 -> Session 3 . To rename this * While debugging go to  Menu -> Debugger => Debugger Session => Designation of the User desktop .  * Enter the new label as you wish and click. Then Changed to * After result comes like this. **************************** ** ** Thank You ************************* ** **

How to change the debugging session idle Time

Image
  How to change the debugging session idle Time * When you are using debugging, there is a default time limit for idle time for each debugging session, i.e., the default time limit value is 600 seconds.  *  This time limit can be increased or decreased by using transaction RZ11. *  Enter the parameter rdisp/max_debug_lazy_time . click on display. * Click on change value and give new value and save. **************************** ** ** Thank You ************************* ** **

Progress bar in SAP ABAP

Image
Report REPORT  zab_rp_progress_bar . DATA :  lv_vbeln  TYPE  vbeln_va . SELECT-OPTIONS  :   s_vbeln  FOR  lv_vbeln . IF   s_vbeln  IS  INITIAL .    MESSAGE  ' Pls give sale order number '  TYPE  'E' . ELSE .    CALL  FUNCTION  ' SAPGUI_PROGRESS_INDICATOR '      EXPORTING       percentage  =  ' 10 '        text        =  ' Reading records started ' .    WAIT  UP  TO  5  SECONDS .    SELECT  *  FROM  vbak      INTO  TABLE  @DATA ( lt_vbak )      WHERE  vbeln  IN  @s_vbeln .    CALL  FUNCTION  ' SAPGUI_PROGRESS_INDICATOR '      EXPORTING       percentage  =  ' 50 '        text        =  ' Reading records finished  ' .    WAIT  UP  TO  5  SECONDS .    CALL  FUNCTION  ' SAPGUI_PROGRESS_INDICATOR '      EXPORTING       percentage  =  ' 80 '        text        =  ' Preparing final result data ' .    WAIT  UP  TO  5  SECONDS .    CALL  FUNCTION  ' REUSE_ALV_GRID_DISPLAY '      EXPORTING       i_call