The part I of the SAP Solution Manager 4.0 series of weblogs targets on the functionality of Roadmaps in Solution Manager. The Part II of weblogs series, Project Preparation or Administration phase of Solution Manager 4.0 is explained. In subsequent parts, other features of Solution Manager will be explained.

What is SAP Solution Manager:

SAP Solution Manager is a tool, which assists in application management as per ITIL (IT Infrastructure Library) environment. The tool supports the entire lifecycle of solutions mainly having six phases – Requirements, Design, Build, Deploy, Operate & Optimize as per ITIL standard.
It runs in a separate central system to which all the other SAP systems are connected. These other systems are called as Satellite Systems.

Latest Version:

SAP Solution Manager 4.0.

Features of SAP Solution Manager:

• Solution Manager helps in all types of project management like Implementation, Upgrade, Maintenance, Rollout etc. by providing the project specific template.
• It is in line with SAP’s AcceleratedSAP. And provide Roadmaps for the different types of projects.
• It has Business Process Repository, which talks about SAP’s best practice of running the business.
• It has eLearning feature, which offers the training along with feedback over web.
• It has test management feature, which offers the central storage repository for storing the automated eCATT scripts along with manual scripts. The results of testing are centrally stored and always available.
• It has its own standard Helpdesk feature, which is both SAPGUI based and web based.
• The Helpdesk feature is totally linked with Change Request Management, which helps in transport for changes required in production issues.
• It has Solution Monitoring as well as Diagnostic feature, which helps in Operation Phase of project.
• Solution Manager has lots of inbuilt reports, which server the different areas of it.
• It is linked with SAP Service Market Place.
• It can generate Installation/Upgrade key.
• It has its own Knowledge Warehouse for central documentation storage.
• It can integrate with ARIS, a detailed graphical business process modeling tool
• It can also integrate with Mercury tools like QTP for testing in web based environment.

Phases of Project Management As per AcceleratedSAP (ASAP) Model:

• Project Preparation Phase
• Business Blueprint Phase
• Realization (Configuration) Phase
• Testing Phase
• Final Preparation for Cutover Phase
• Production Go Live Phase
• Support Phase

What is Project Preparation Phase:

In the project preparation phase of any project, the team is identified, the landscape is identified. The quality standards for the project are identified, which will be used for quality audit. The deadline of projects is identified at higher level. High level scope is planned.
All above activities with lots of advanced features are available in Solution Manager, which integrates different phases of the project and the satellite systems too.

SAP GUI based Transaction for Project Preparation Phase:

SOLAR_PROJECT_ADMIN

Web based Wizard’s Transaction for Project Preparation Phase:

AI_SPS (Quick Project Set-Up)

Menu Path for Project Preparation Phase:

SAP Menu -> Tools -> SAP Solution Manager -> SOLAR_PROJECT_ADMIN Project Administration

Prerequisite of using Project Preparation in Solution Manager:

The logical components of the satellite systems landscape should be created in SMSY transaction. The quality standards of documentation templates should be available. The list of team members along with their role in the project should be available.

Types of SAP Projects in Solution Manager:

There are following different types of Projects in Solution Manager based on the functionality that is offered in different phases like Blueprinting, Configuration etc.
• Implementation Project: A Project to implement business processes in an SAP landscape
• Template Project: A project to create a template. A template makes project structure, or parts of it, with its assigned objects (documentation, test cases, IMG activities), available to other projects. This is mainly used in Rollout Projects.
• Upgrade Project: A project to upgrade existing systems.
• Maintenance Project: A project for maintenance of existing systems.
• Optimization Project: A project to optimize the flow of business processes, or the use of a software solution.
• Safeguarding Project: A project to resolve a critical situation in the implementation or use of an SAP solution.

Web Wizard (Quick Project Set-Up) for Project Creation:

• Web wizard is especially useful in the cases, when someone is using Solution Manager for the first time & does not have much knowledge about the Solution Manager.
• The project setup can be done without the satellite landscape details mapped into it. Further the project can be taken into Blueprint phase. And as needed, the satellite landscape can be mapped back using SOLAR_PROJECT_ADMIN transaction.
• The prerequisite for using this web wizard is that there has to be an entry of the Solution Manager server into the host file of the desk, where this application will run & the proxy should be turned off from the web browser.
• Now, log in to Solution Manager with a user ID having authorization of AI_SPS transaction.
• Goto transaction AI_SPS transaction. It will open the Project Administration transaction over web.

Project Preparation in Detail:

• Log in to Solution Manager with a user ID having authorization of SOLAR_PROJECT_ADMIN transaction.
• Goto transaction SOLAR_PROJECT_ADMIN transaction.
• The list of existing projects will be displayed in the transaction. Click on Create button from the application toolbar to create a new Implementation Project.
  
• In the Create Project popup, give some significant name of the Project & select the type of the project from the standard dropdown of SAP. Here Implementation Project type is selected from the dropdown. Click on Continue to create the project.
  
• Once the project gets created, the Project Administration screen appears with different tabs like General Data, Scope, Proj. Team Members, System Landscape, Milestones, Organizational Units and Project Standards. Give the project title as Demo for Implementation Project in the Title at the header, which is a mandatory field.
  
• General Data tab:
  • General Data tab contains the information about the Project Management, Project Status, Project Language and details on the planned & actual dates along with resources in Person Days (PD).
  • Project Language is mandatory field. Once selected and saved, language can not be changed. The further phases of Project Management in SolMan will be available in this language. Project Description can also be maintained, which is a long text field.
    
  • The Project Status can be selected from the standard dropdown. The values in the dropdown can be customized as per need in the Project Standards tab here.
  • The Planned start date & end date can be given along with the resource allocation in person days. The actual date values can be also entered here.
• Scope Tab:
  • The Scope tab contains the different tabs for Template Selection, Roadmap Selection, Industry Selection and Country Selection.
  • The Template tab can be used for the selection of Templates. Templates with public visibility are available for other projects to reuse. The templates are mainly used for Rollout projects, where the reference location’s implementation becomes template for the rolling out implementations of other locations. If Template is selected in Project Administration phase, all the relevant details of Business Blueprint, Configuration & other phases of template are imported automatically in the current project.
  • The Roadmap tab shows, the ASAP roadmaps for different kinds of project management in SAP. Here, select the Roadmap for mySAP ERP Implementation so that team members can use this roadmap for each of the phase of the Project Management.
    
  • In the Country Selection tab, countries can be restricted for the team members.
  • There are other settings also available here in the Scope tab, which can restrict the usage of Business Blueprint Structure & Blueprint relevant documentation to the team members.
• Proj. Team Members Tab:
  • The Project Leader can specify here the SAP Team members & generic team members also, which might not necessarily be a SAP ID in system. There is a button as Check Against User Master Record, which will highlight the non SAP users.
  • For SAP users, the ID can be selected from the search help and Role in the Project can be selected from the dropdown. The Role can be managed from the Roles in Project button. Also, the User Administration (SU01 transaction) can be done directly from this tab.
    
  • There is a check box option for restricting the access of Project Structure to users. If the checkbox is selected, only the users mentioned in this tab will have access to project in edit made. Other users can access the project structure nodes in display mode.
  • This project members list is linked to the different phases of SolMan like Roadmaps -> Project Team Members tab, Business Blueprint -> Administration tab, Configuration -> Administration, Configuration & Development tabs.
  • Save the Project by clicking the Save button from standard toolbar.
    
  • A popup comes for the Enhancements for Documents. This is for the Knowledge Warehouse of Solution Manager, where all the documentation will be stored for the current project. Click on Continue to save the project.
    
• System Landscape Tab: In the System Landscape tab, there are four sub tabs mainly Systems, Central Objects, IMG Projects and Change Requests.
  • Systems Tab:
    • Here the details about the Satellite system are maintained in the form of Logical Component. To this logical component, the satellite system of one landscape is attached. Select the search help for selection of Logical Component (which are already created in SMSY transaction). More than one logical component can be attached in the Solution Manager project.
      
    • The list of the Logical Components is displayed. Select the required one & click on Continue.
      
    • The Logical Component with the details will be added into the project.
      
    • The logical component can be completely replaced with some other logical component in the entire project structure using Replace Log. Components icon at the bottom.
      
    • The logical components can be even selected from the Business Blueprint Scenarios, if in case they don’t’ exist already. There is button called Select Scenario at the bottom.
      
    • System Landscape Check: Using the System Landscape Check button at the bottom, one can ensure the consistency of the system landscape, which is added in the project. It ensures the smooth navigation to the satellite systems in different phases of project like Business Blueprint, Configuration, and Test Management etc. It checks for the presence of logical components for the SolMan project, logical components and the logical system based on the same product release, the releases and the Support Package statuses of the logical systems sufficient to be able to navigate in the component systems with the SAP Solution Manager, the logical systems having RFC connections and the RFC connections functionality. It generates the information or error message depending on the check performed for the selected logical component.
      
    • System Roles: The default system role appears like Evaluation System, Development System, Quality Assurance System, Production system, Training System etc., which can be changed as per the requirement. The system roles are specific to a project.
      
      To meet the system landscape needs, more number of system roles can also be added using the System Role Assignment button at the bottom. The system roles, which are in use, can not be deleted.
      
    • The transport route between the landscapes of the logical components in the satellite systems can be managed using Shipment Routes button at the bottom.
      
  • Central Objects Tab:
    • In the Central Objects tab, the central system for objects like eCATT Test, Manual Test Cases and External Applications is maintained. By default the central server is the same server i.e. Solution Manager Server.
    • As per requirement, any other system can be specified here as central landscape for storage, which will be connected to Solution Manager via RFC connection. Solution Manager will interact with this system using this RFC.
    • Once the RFC connection is established between the central server & Solution Manager, the central system appears in the search help list. Select the one central system as per need.
      
    • There is an obligatory flag, which will forces all the team members to use only this central system for storage of eCATT Test development, Manual Test Cases & External Applications in Test Cases tab of Configuration phase.
      
    • If no logical component is selected in Test Cases tab of Configuration phase, Solution Manager will automatically store the contents in to this central system.
  • IMG Projects Tab:
    • If the logical components are assigned in the Systems tab & project is saved then the IMG Projects tab will have the IMG projects. Corresponding to the number of the logical components, IMG Projects entries are automatically created in this tab. The IMG projects are created in the satellite system for configuration settings under it.
      
    • The green and red traffic lights indicate whether Project IMGs have already been generated and distributed in the satellite system.
    • To generate & distribute the IMG projects, use the icon Create IMG Project at the bottom.
      
    • This will take the control to the satellite system for IMG Project creation. Follow the steps & create the project. As the project gets created, the message appears in satellite system and the status changes to green signal in the Solution Manager.
      
    • If any IMG project already exists in the satellite system, that project can be linked to the current Solution Manager project instead of creating new IMG project. This can be done by using the Replace icon at the bottom.
  • Change Requests Tab or Projects Cycles Tab:
    This tab is related to activating Change Request Management, Helpdesk, Task List along with Variants, Creation of CTS Project and assignment of cProjects project to the project landscape.
    
• Milestones Tab:
  For monitoring the progress of project in Roadmap, milestones can be defined under this tab. This is integrated with the Roadmap of the project.
• Organizational Units Tab:
  This tab is used to enter the organizational units of the project including functions, time zone & country.
• Project Standards Tab:
  • Status Values Tab:
    • Status Values tab shows the default status available in Solution Manager.
    • These statuses are mainly used in different phases of Solution Manager like Project Administration phase -> Project Status values, Blueprint phase -> Documentation status values, Administration status values, Configuration Phase -> Documentation status values, Administration status values, Development status values and Configuration status values.
    • One can edit the status values as per need using Project Template button at the bottom.
      
    • Click on Project Template button at the bottom for creation of new status values. On the right side of the Status tab, give the new value with details. Move this entry to the left side for the current project so that it can be utilized for the current project.
      
    • As the entry comes on the left side, Check and Save the value. Close this dialog box.
      
    • Now, the entry appears on the right side, which is common pool of the status values. Select the entry and move it to left side for the current project.
      img src="https://weblogs.sdn.sap.com/weblogs/images/37984/PA26.JPG" mce_src="https://weblogs.sdn.sap.com/weblogs/images/37984/PA26.JPG" width="569" height="258" border="0" alt="image">
    • As the entry comes on the left side for the current project, save the project.
      
    • After saving the project, this newly created status value starts appearing in the Project Status dropdown in the General Data tab.
      
  • Keywords Tab:
    • Keywords are the words, which can be used for reporting purposes. They are part of the Project Documentation or General Documentation attributes in the Business Blueprint phase and Configuration phase.
      
    • To create keywords, click on the Project Templates button at the bottom in the Keywords tab. Create the entry for the keyword on the right side and move it to the left side for Project keywords.
      
    • As the entry comes on the left side, check & save the keyword.
      
    • The Keyword now appears on the right side of the unused pool of keywords. Move the keyword on the left side.
      
    • The keyword appears on the left side for the current project. Now, this keyword is available for use for further phases of this project. Save the project.
      
  • Documentation Types Tab:
    • This tab contains lots of SAP standard documentation templates by default.
    • As per the quality standard of organization, different types of documentation type can be maintained along with their templates. The life cycle of the document through different status values can be maintained via Status Schema IMG setting. The approval process can be mapped via Digital Signature IMG setting.
    • For maintaining the custom documentation type, click on the Project Template button at the bottom.
      
    • Enter the Documentation Type, Name, and File Extension. Select the checkboxes for Global (document type will be available to all projects), several (Under the same node of business scenario/process, several documents of this document type can be created), Business Blueprint Relevant (If the document contents are required to insert in the business blueprint document, which can be generated automatically in the blueprinting phase). Status schema, if created in IMG, can be entered here.
      
    • To upload a document template for this new documentation type, select the document type and select Document Template -> Import option from the bottom.
      
    • Select the template from the desktop and save it. While uploading the template, click on Yes for popup of Enhancements of Documents & Released status for template. Move the document type to left side.
      
    • Once the document is moved on the left side, check and save this dialog box.
  • Tabs Tab:
    • The Tabs tab is used to control the different tabs in different phases of project.
    • Here, the required tabs can be hided and they will never be available for the team members in the relevant phase.
      

The Part I of eCATT Introduction gives the basic details about usage of eCATT & features involved. In Part II, the creation of eCATT scripts using TCD mode of recording is explained in detail. In the Part III, the creation of eCATT Scripts using SAPGUI mode is explained in detail. In Part IV chaining, parameterization, creation of Test Configuration, Test Data Container, and System Data Container are explained in detail. In Part V, the management of eCATT Scripts via Testworkbench is explained. In Part VI, the eCATT Logs is explained in detail. In Part VII, creation of eCATT Scripts using Non-User Interface mode is explained along with the details of Copy, Rename, Delete, Upload and Download of eCATT objects. In the Part VIII, tips & links of eCATT are covered.

In part IX, the checkpoints using eCATT will be covered.

What are Checkpoints in Testing:

Checkpoints are the values to be verified which confirms the successful testing. These Checkpoints will have always predefined values as per the business requirements and should match to the output results after testing. So Checkpoints are used for cross verification of the results of testing.

Why are Checkpoints needed in Automated Testing:

• In case of manual testing, once the testing is done by the business analyst for the given scenario, the analyst will manually cross verify the value of the checkpoint either in the table or in some transaction.

• This value might be coming from SPRO settings, which is placed in those tables or transactions as a result of execution of the testing scenario.

• Once the checkpoint value is verified then only the testing is confirmed as successful. This process of verification is fine in case of manual testing but in case of automated testing, the checkpoints need to be part of automation.

• If the checkpoint is not part of automated testing then the chances of having successful automated test result with incorrect checkpoint value increases & hence resulting in incorrect testing. As here the checkpoint needs to verify manually for the automated result set.

• Hence the need of adding checkpoints in the automated testing is must to confirm the successful testing.

Advantages of Checkpoints in Automation:

0.1.

0.2. If the checkpoint will be as part of automation of test case then the manual error of cross verification is avoided.

0.3.

0.4. If the test scenario is automated but checkpoint is manual then the chances of missing the cross verification for the checkpoint is more. This happens mostly when the integration test happens and go live is about to happen with cut over activities on the head of business analyst. As lots of activities are needed to be done in less time, the checkpoint cross verification may be missed out.

0.5.

0.6. It will be done automatically. Hence time efficient.

0.7.

What is required if the Checkpoints should be added as a part of Test Automation:

0.1.

0.2. Checkpoints should be added as a part of manual script at the design time.

0.3.

0.4. Where the checkpoints will be verified for the given scenario should be clearly mentioned in the manual script. e.g. whether table value will be verified or any value in the transaction will be verified.

0.5.

0.6. At what stage in the complete test scenario, checkpoints should be verified should also be mentioned very clearly in manual test script.

0.7.

0.8. The value of the checkpoints for the given scenario should be clearly given as input in the manual test script.

0.9.

What are commands in eCATT for Checkpoints:

0.1.

0.2. There are different eCATT commands are available, which can be used for verification of checkpoints as follows –

CHEGUI, CHETAB, CHEVAR, CHEATTR, CHESTATIC etc.

Details about checkpoint commands in eCATT:

0.1.

Most frequently used commands for checkpoints are CHEGUI, CHETAB, and CHEVAR.

0.2. CHEVAR command:

0.1.

0.2. CHEVAR command compares one parameter with other parameter or fixed value.

0.3.

0.4.

Syntax: CHEVAR (<parameter1> <comparison operator> <parameter2>).

         For comparison, the operators are =, <>, <, >, <=. >=. For complex expressions, the operators like AND, OR & NOT are available. 0.1.

0.2. CHEVAR command is useful when two values need to be compared. One value will be as an input for verification and the other one may be either input vale or fixed value or outcome from the execution of the business scenario as Export variable. Also this is useful when depending on some output value; the further steps need to be verified for execution.

0.3.

0.4. If this command fails at runtime, then error log is generated.

0.5.

0.6. Example:

0.1.

0.2.

Goto transaction SECATT.0.1.

0.2.

Give the name for a Test Script. Click on Create.0.1.

0.2.

Give the suitable Title & Component in the Attributes tab.0.1.

0.2. Record a transaction.

0.3.

0.4. Parameterize the fields of the transaction.

0.5.

0.6. Position the cursor in the eCATT editor after the transaction recording.

0.7.

0.8.

Now click on Pattern (Insert Statement CtrlF6)+ button from the application toolbar.

Select Params from the Group dropdown, CHEVAR from the Command dropdown. In the Condition, enter P_IV_NAME_FIRST = P_CV_FNAME and click on Enter.

!https://weblogs.sdn.sap.com/weblogs/images/37984/CheVAR.JPG|height=128|alt=image|width=405|src=https://weblogs.sdn.sap.com/weblogs/images/37984/CheVAR.JPG|border=0!0.1.

0.2. The CHEVAR command is inserted in to the command editor of eCATT.

0.3.

0.4.

Now, give the suitable values to input as well as checkpoint variable in the Parameter section.0.1.

0.2. Execute the script.

0.3.

0.4.

The log will be generated. Here the input value is different than the checkpoint value so the CHEVAR command should fail & hence the script.

!https://weblogs.sdn.sap.com/weblogs/images/37984/ErroLog.JPG|height=335|alt=image|width=519|src=https://weblogs.sdn.sap.com/weblogs/images/37984/ErroLog.JPG|border=0!0.1.

0.2. And if the correct value is passed to the checkpoint, success log is generated as follows -

0.3.

0.1.

0.2.

0.3. CHEGUI command:

0.1.

0.2. CHEGUI command is useful when the field value to be verified is present in any transaction.

0.3.

0.4. There are two ways of using the CHEGUI command, one is dynamically adding this command during record time in SAPGUI recording mode & other is manually in eCATT Editor. The first approach is very simple and should be followed for errorless recording.

0.5.

0.6.

If the transaction is not part of the business scenario then record this transaction in SAPGUI recording mode after the normal business scenario is recorded in the same script. And if in case the transaction, which contains the checkpoint to be verified is part of the given business scenario then make sure that at least transaction is getting recorded in SAPGUI mode. 0.1.

0.2. If this command fails at run time then error log is generated.

0.3.

0.4. Example:

0.1.

0.2.

Goto transaction SECATT.0.1.

0.2.

Give the name for a Test Script. Click on Create.0.1.

0.2.

Give the suitable Title & Component in the Attributes tab.0.1.

0.2.

Record a transaction in SAPGUI mode. For this click on Pattern (Insert Statement CtrlF6)+ button from the application toolbar.

Select All Commands from Group dropdown & SAPGUI Rec from Command dropdown. Click on Enter.0.1.

0.2.

Now from the Record SAP GUI Command popup, select the checkboxes for Automatic Generation & give the transaction name to be recorded. Click on Start Recording button.

!https://weblogs.sdn.sap.com/weblogs/images/37984/SAPGUIRecrd.JPG|height=219|alt=image|width=448|src=https://weblogs.sdn.sap.com/weblogs/images/37984/SAPGUIRecrd.JPG|border=0!0.1.

0.2.

On the Record SAP GUI Command popup, click on Yes to record the session.0.1.

0.2. On the +Record Running…+popup, click on Enter. This is the screen having Insert CHEGUI Command into, which we will utilize for checkpoint.

0.3.

0.4. Now start recording of the transaction on the session just behind the above popup. Record the transaction as per requirement. Now here while recording, wherever the checkpoint field comes on the screen, just bring the popup of +Recording Running…+ on this checkpoint screen. This popup remains till we stop the recording.

0.5.

0.6.

Now click on Insert CHEGUI Command from this popup & point towards the required field on the transaction.

The moment mouse is moved over on the screen, the area is highlighted. So go to the required field and click there once.

!https://weblogs.sdn.sap.com/weblogs/images/37984/cheguiintoscript.JPG|height=167|alt=image|width=353|src=https://weblogs.sdn.sap.com/weblogs/images/37984/cheguiintoscript.JPG|border=0!0.1.

0.2.

The moment the checkpoint field is clicked, which got highlighted, another popup comes up Selection of Properties & Methods to Be Recorded. Expand the node Checks. And select all the checkboxes. Click on Insert & Exit at the bottom.

!https://weblogs.sdn.sap.com/weblogs/images/37984/GetVal.JPG|height=320|alt=image|width=318|src=https://weblogs.sdn.sap.com/weblogs/images/37984/GetVal.JPG|border=0!0.1.

0.2. After this, just go to the recording of transaction and walk through the transaction as required. Come back till SAP Easy Access screen.

0.3.

0.4.

Once the recording is done, click on the Stop Recording... from the Recording Running... popup. This will get back the recorded script in Solution Manager.

!https://weblogs.sdn.sap.com/weblogs/images/37984/CHEGUICode.JPG|height=293|alt=image|width=396|src=https://weblogs.sdn.sap.com/weblogs/images/37984/CHEGUICode.JPG|border=0!0.1.

0.2.

Now parameterize the fields of the transaction along with the checkpoint. For checkpoint parameterization, double click on the interface name on the left side in the command editor. On the right side, expand the Text node. In the Expected Result, on the rightmost side, enter the name of the parameter. This is the parameter to which input values will be passed for verification of checkpoint.

!https://weblogs.sdn.sap.com/weblogs/images/37984/CHGUIParam.JPG|height=263|alt=image|width=479|src=https://weblogs.sdn.sap.com/weblogs/images/37984/CHGUIParam.JPG|border=0!0.1.

0.2.

Now give some input value to checkpoint parameter in the Parameter section and execute.Goto transaction SECATT.0.1.

0.2. Give the name for a Test Script. Click on Create.

0.3.

0.4.

Give the suitable Title & Component in the Attributes tab.0.1.

0.2. Record a transaction.

0.3.

0.4. Parameterize the fields of the transaction.

0.5.

0.6. Position the cursor in the eCATT editor after the transaction recording.

0.7.

0.8.

Now click on Pattern (Insert Statement CtrlF6)+ button from the application toolbar.

!https://weblogs.sdn.sap.com/weblogs/images/37984/Pattrn.JPG|height=89|alt=image|width=362|src=https://weblogs.sdn.sap.com/weblogs/images/37984/Pattrn.JPG|border=0!</body>

What are SAP Business Workflows:

What is Workflow Builder:

Transaction for Workflow Builder:

Menu path for Workflow Builder:

Features of Workflow Builder:

• Version management for workflows is featured. (Menu Workflow -> Generate Version).
  
• Import/Export feature is available for workflows with some restrictions. This import/export happens through the XML version of workflows. (Menu Workflow -> Import/Export..).
• Option of printing is available for the workflows. This option is for graphical display as well as for individual step details, which are selectable for printing. (Menu Workflow -> Print..).
• Testing of workflows within builder is possible. (Menu Workflow -> Test).
• Block operations like Cut/Copy/Paste are available. (Menu Edit -> Block..).
  
• Insertion an existing workflow/subworkflow into the current workflow is possible by selecting the appropriate node in the graphical display. This is same as creating steps according to the rules of block orientation. (Menu Edit -> Insert Workflow).
• Triggering Event for workflow can be entered in the workflow builder by menu Goto -> Basic Data.
  
  Here enter the relevant business object and the event name in the Start Events tab. Activate the link and binding.
  
• Many times it so happens that changes are made but they don&#146;t reflect in workflow results due to buffer synchronization. One can synchronize the runtime buffer from workflow builder directly. This synchronization happens for Tasks (single-step tasks, multistep tasks), Organizational environment (assignment of tasks), Workflow System Settings (RFC Destination, and so on).
  
  From the menu Extras->Transport->Synchronize runtime buffer, one can goto transaction SWU_OBUF of buffer synchronization.
  
  Clicking on Start Synchronization will refresh the buffer.
• There are different options available in workflow builder for Views/Default Settings/Hidden Step Types from the Menu Extras -> Options. Here depending on the values selected in View tab, the modeling view of workflow changes as follows &#150;
  • L &#150; Event Driven Process Chains:
    • Goto menu Extras -> Options -> tab View.
    • Select the value from the Display of Modeling View &#150; View dropdown as L Event Driven Process Chains (EPCs).
      
    • Click on Enter.
    • The graphical modeling view changes to as follows where All triggering events, outcomes, steps and operators are displayed. Steps are displayed as green rectangles, triggering events and outcomes as red hexagons and operators as circles. The step name is displayed in the graphical symbols.
      
  • C- Classic Event Driven Process Chains (ClassicEPCs):
    • Goto menu Extras -> Options -> View tab.
    • Select the value from the Display of Modeling View &#150; View dropdown as C- Classic Event Driven Process Chains (ClassicEPCs).
      
    • Click on Enter.
    • All triggering events, outcomes, steps and operators are displayed. Steps are displayed as green rectangles, triggering events and outcomes as red hexagons and operators as circles. The node number and the node type are displayed with the step name in the graphical symbols. The step type area is not displayed.
      
  • N &#150; Without Event-Driven Process Chains (NoEPCs): (Default Mode of View):
    • Goto menu Extras -> Options -> View tab.
    • Select the value from the Display of Modeling View &#150; View dropdown as N &#150; Without Event-Driven Process Chains (NoEPCs).
      
    • Click on Enter.
    • All steps, triggering events and the workflow start and end are displayed using symbols. Outcomes are displayed in text on the connecting lines.
      
• There are lots of other display settings available in menu Extras->Options for Block Display, Tips & Tricks display at start, display of percentage progress of a syntax check, indicator for steps Drag & Drop by mouse etc.
• In the menu Extras->Options->Default Settings tab, there is an option for workflow definition modeling as Use Top-Down Modeling.
  
  If used this option, then one can model the workflow without actually defining the steps. So when a step is added to workflow, it is only added to graphics.
  
  This way one can have the actual picture of the final definition of workflow. To use such type of workflows, all the inserted steps should be complete.
  
• Other settings like hiding steps types etc are also available in menu Extras->Options.
• One can go to SAP Business Workplace directly from workflow builder from the menu Environment->Business Workplace.
• There are lots of workflows available as examples, which can be reached via workflow builder. The menu path is Environment->Start Workflow.
  
  Select the required workflow from the list on the left side and click on either Start or Start with Details on the right side for execution. Once the workflow is started, the log can be viewed from the Workflow Outbox button from the application toolbar.
  
• One can directly go to the different development environment like ABAP Dictionary, Class builder, Business Object Builder, Correlation objects, proxy objects, Web Services etc. from workflow builder. The menu path is Environment->Development..
  

Workflow Builder Details:

• Go to transaction SWDD for workflow builder.
• By default, the builder shows the last workflow worked in the builder. To go to the required workflow, click on Other Workflow/Version..(Ctrl+F5) from the application toolbar.
  
• In the Task, give the name of the required workflow, following the F4 search help if needed.
  
• The required workflow is now displayed in the workflow builder. The workflow builder is divided into different areas like Information Area, Navigation Area, Step Types, Graphical Model, Results of Syntax check etc as shown below.
  
• In the Information Area, the information about the workflows like workflow number, version and the status of the workflow are displayed.
• In the navigation area, all the steps of workflow definition are displayed in sequence.
• The Step Types appear in the Objects section of the workflow builder. This object section consists of following options in the dropdown, one which can be viewed in the workflow builder. e.g. in the current case, Step Types are displayed.
  • Step Types That Can Be Inserted are Activity, web activity, Send Mail, Form, User Decision, Document from Template, Condition, Multiple Condition, Event Creator, Wait, Container Operation, Process Control, Loop(Until), Fork, Block, Local Workflow etc.
  • Workflow Container
  • My Workflows and Tasks
  • Document Templates
  • Workflow Wizards
  • Teamworking
  • Workflows of this Definition (Outcome)
  • Note It!
• At the bottom of the workflow builder, the syntax check results are shown as either informatory, warning or error messages.
• In the Graphical view, the actual definition of workflow is build by dragging the steps from the steps list or by right clicking the step directly on undefined one. The default steps in every workflow are Workflow Started, Undefined step and Workflow Completed.

What are SAP Business Workflows:

Why Workflows:

• Finding out what work needs to be done
• Planning of work that needs to be done amongst the group of people
• The identification of roles & responsibilities on who will do what, when & in how much time
• Working in coordination with others
• Informing next person about his work to be done, when the earlier one has finished his own
• Duplication of work that has been already done because of communication gap,inefficient knowledge transfer & the incomplete documentation in the central repository
• Identification of delay in the completion of the work
• Preparing status on this delay
• 
  Workflows help to optimize each of the above scenarios. In workflows the processes are linked to each other and flow one after the other. At each step, a right person (Agent) will take care of the process. If the step doesn&#146;t need any interaction then the process flows automatically.
  Here deadlines can be set for the activities depending on the fair time that step needs to complete. Once this deadline is reached and the process is not performed by the concern then the administrator (manager) gets the notification mail. Here as the right people can be kept in loop in this automated process so a disciplined work atmosphere is automatically planned in the organization.
  Due to this automated system, the process becomes transparent to all the users and the risk of manual errors is also reduced. Again the time required to complete any work manually is simply reduced in this automated system. So this adds to the quicker completion of targets and hence leads to the financial growth of the organization.

Features of Workflows:

• New business processes can be easily defined with the workflows.
• Workflow uses the existing transactions and functions without changing them.
• Workflow uses the Organization structure. This helps in the term of changes to organization structure, which will be immediately in effect in the execution of workflows.
• Lots of tools are available in the workflow like tools for definition, analysis and monitoring of work processes.
• Workflow template (transaction: PFTC) can also be created for the workflow definitions.
• Workflow Builder is a very effective tool available for creation, change and display of workflow definition.
• Agents can be easily maintained in the workflows. They receive the work item in their SAP Business Workplace, which they will process.
• Deadline monitoring can be easily used against the tasks for the defined agents.
• Using Business Object Editor (transaction: SWO1), we use the business objects in workflows. These business objects help to use the SAP standard functionality in workflows.
• ABAP Classes can also be used in workflows along with the business objects.
• Business Workflow explorer gives the overview of all the tasks.
• Workflow can also be used on Internet. This is especially useful for the managers, who might not be directly accessing the SAP transactions. So the approval forms generated via workflows can be sent on internet. This is even useful for the people who mainly preparing SAP data and not knowing much about the SAP transactions. They can be given a simple web form for entering data & on submitting data of this web form workflow can be started.
• Several workflow wizards are also available for supporting the workflow definition
• Version management is available for workflows. Only one version can be active at one time, which is referred while execution.
• Lots of administrative tools are available for control and analysis of workflows.
• Lots of diagnostic tools are also available in workflows.

Prerequisites of using Workflows:

• System Requirement: R/3 Release 3.0 & above
• Mail servers involved should be SMTP Compliant if the workflow involves email notifications.
• As the workflow may execute lots of background jobs so it may require lots of system resources. Hence the hardware should be enough to fulfill all these requirements along with the normal functionality of the server without affecting the speed.
• Customization Settings:
  • Following are the customizing settings needed to use workflows-
    • With the System Supervisor ID, go to transaction SWU3(Automatic Workflow Customizing)
    • Click on the button Perform Automatic Workflow Customizing (F9) from the application toolbar for performing automatic customization of the workflow.
      
    • Once this is done, all the check marks below should turn green
    • Along with so many settings available in the workflow customizing, system automatically creates a batch user WF-BATCH. This user has SAP-ALL authorizations to execute the workflow.
    • Now, go to table T78NR from Customizing SPRO transaction.
      
    • Click on Create button from the application toolbar to create a new prefix range.
      
    • Give the Prefix Number as 900 for custom development & click on Save button.
      
    • The newly created prefix appears as activated in the table.
      
  • The user triggering the workflow should have his email ID maintained in the SU01 transaction.
    
  • 
    
  • SMTP Configuration:
    From SAP WAS 6.10, SAP directly supports SMTP (Simple Mail Transfer Protocol). This means that the emails can be exchanged directly between SAP system and any SMTP compliant mail server. From SAP WAS 6.20, faxes, pager & SMS can also be exchanged via SMTP.
    • Goto transaction SCOT.
    • Goto menu View -> Node
      
    • Goto SMTP node. Double click on the required node which is * in this case.
      
    • Click on the Maintain Node button.
      
    • Give the Mail Host & Mail Port for outgoing mails. Click on Set for Internet options to set.
      
    • Give the Address Area as * for the receipt addresses. Also set the Output formats for the SAP Documents as shown in the image below. In the specified format the output will be sent as attachment in the email.
      
      Confirm the settings.
    • Similarly Pager/Fax settings can be done. For Pager(SMS), the prerequisite is that in transaction SA14, the paging services should be defined. Once this is done, the here in the SCOT transaction, click on Set adjacent to Pager (SMS).
    • Mention as * in the Address area for the receipt number and Domain name in the Domain input.
      
    • Confirm the entries. The SMS will be of the format SMS=+ReciptNumber@Domain

Transactions Involved:

Lots of transactions are involved in the Workflow tool. Majority of them are for runtime analysis and diagnosis. The details of these transactions can be found from SAP Easy Access menu.


Following are the frequently used transactions -

• Customization Settings:
  • SWU3 - Automatic Customizing Workflow.
  • SCOT - SAP to mail server Configuration
  • SU01 - User Maintenance
• Workflow Design:
  • SE37 - Function Builder
  • SE38 - ABAP Editor
  • SWO1 - Business Object Builder
  • PFTC - Task Maintain
  • SWDD - Workflow Builder
• Runtime Behavior/Analysis:
  • SBWP - Business Workplace
  • SWUD - Workflow Diagnosis
  • SWU_OBUF - Synchronize Runtime Buffer
  • SWPR - Workflow Restart After Error

Workflow Terminologies:

• Workflow builder: Workflow builder is the business workflow tool for creating, editing and displaying the workflow definition.
  The Workflow Builder provides a graphical modeling view, which gives a direct overview of the processes of the different steps. Also there is a tree view to shows all steps of the workflow definition in a hierarchical view.
• 
  
• Workflow Container: The workflow container contains workflow-specific system elements as well as other container elements, which are defined explicitly.
  Container elements for which the import or export indicator is set form the interface of the workflow. This interface is valid for all versions of the workflow definition. Container elements for which no import or export indicators are set are local container elements of the workflow definition and are valid only in the versions of the workflow definition in which they were defined.
• 
  
• Workitem: Workitem is runtime representation of a task or a step in the workflow definition. There are various types of work item.
  The SAP System determines the recipient(s) of a work item i.e. Actual Agent from the intersection of responsible and possible agents. If this intersection is empty then no body will get this workitem for further processing.
• 
  
• Dialog Workitem: A work item (type W) which at runtime represents a workflow step or a task that requires dialog with the user. Typically, dialog work items are displayed in the Business Workplace. When a dialog work item that is based on a task is executed, the underlying object method is called. You can monitor deadlines for dialog work item execution.
• 
  
• Triggering Event: Triggering event is the one, whose occurrence triggers or starts the workflows or tasks.
  The event must be entered as a triggering event for the task or workflow that is to be started. The event linkage must be activated. The event must be defined as an object type component in the Business Object Builder. A task or workflow can have several triggering events. Information from the event creation context can be passed in the binding from the event container to the task container or workflow container.
• 
  
• Block: Block is an element of workflow definition. It contains the consistently arranged steps and operators. It has one start and one end. The consistency and robustness of a workflow definition is ensured because a block is always created when a new step is created, or an undefined step is changed. Similarly, when individual steps are deleted, cut, or inserted, the entire block in which the step is located is affected.
• 
  
• Step: A step is an entity, which can be inserted into the workflow builder. Whenever executed, step gives the predefined desired results.
  The step is always defined in block. There are different types of steps available in workflow builder to perform different kinds of operations. These steps are Activity, Web Activity, Send Mail, Form, User Decision, Document from Template, Condition, Multiple Condition, Event Creator, Wait, Container Operation, Process Control, Loop(Until), Fork, Undefined, Ad hoc Anchor, Local Workflow & Block.
• 
  
• Task: Task (Standard Task, Customer Task) is used to define the Activity step in workflow definition. Task can be executed independently also.
• 
  
• Task Container: Task container is a location for storing data from the task environment. The task container contains the information about the object reference to the object to be processed, the actual agent of workitem, necessary input parameters for the method. These parameters come from workflow container after the binding between workflow container and task container. It also stores the information available after the method processing.
  The task container contains some predefined workflow system elements. One can define more container elements in the task container. It is also known as a work item container at runtime.
• 
  
• Responsible Agent: Responsible Agent is a user assigned to a step in the step definition. Expressions, organizational objects, or rules can also be used to assign the responsible agents.
• 
  
• Possible Agent: Possible agent is a user who is authorized organizationally to start a task and execute the relevant work item.
• 
  
• Actual Agent: Actual Agent is the person who receives a work item for further processing. The agent can be directly assigned to step or agent determination can happen dynamically at run time either from rule or from the organization structure.
• 
  

Workflow Binding Concept:

Workflow Builder in Brief:

• Transaction for workflow builder is SWDD.
• The workflow builder is divided into different areas like Information Area, Navigation Area, Step Types, Graphical Model, Results of Syntax check etc as shown below.
  
• In the Information Area, the information about the workflows like workflow number, version and the status of the workflow are displayed.
• In the navigation area, all the steps of workflow definition are displayed in sequence.
• The Step Types appear in the Objects section of the workflow builder. This object section consists of following options in the dropdown, one which can be viewed in the workflow builder. e.g. in the current case, Step Types are displayed.
  • Step Types That Can Be Inserted
    
  • Workflow Container
    
  • My Workflows and Tasks
    
  • Document Templates
    
  • Workflow Wizards
    
  • Teamworking
    
  • Workflows of this Definition (Outcome)
    
  • Note It!
    
• At the bottom of the workflow builder, the syntax check results are shown as either informatory, warning or error messages.
• In the Graphical view, the actual definition of workflow is build by dragging the steps from the steps list or by right clicking the step directly on undefined one. The default steps in every workflow are Workflow Started, Undefined step and Workflow Completed.
• Triggering Event for this workflow can entered in the workflow builder by menu Goto -> Basic Data. Here enter the relevant business object and the event name. Activate the link and binding.
  
• Once the workflow is built here. It needs to be activated so that it can be used further.
• Workflows can be locally tested at the Builder level also.
• 
  
• Following types of steps can be inserted into the workflow builder.
  

Symbol	Step Name	Function
	Activity	Activity is used to execute the methods of Business Objects. At runtime it does the execution of a task or sub workflow
	Web activity	The content of container elements is sent to a URL unchanged or in the form of a generated XML document. The step can wait for a reply. Communication with a process started by a Web activity is possible. A process started by an XML message can communicate with its caller.
	Send mail	This is used to send mails to SAP, Internet mail addresses. The text entered in this step type is sent as an e-mail.
	Form	The data in a container element that refers to a structure can be displayed, processed, or approved as a form.
	User decision	The actual agent will be given choices to execute the workitem with different decisions. The process flow of the current workflow is controlled on the basis of a decision made by the current agent.
	Document from template	A document is created from a document template.
	Condition	One of two branches defined in the workflow definition is processed. The system makes the decision based on defined conditions. When doing this, this system takes account of information from the context of the workflow or the application objects processed.
	Multiple condition	One of several branches defined in the workflow definition is processed. To do this, the system checks the value of a container element in the workflow container.
	Event creator	An event is created.
	Wait for event	The system waits for a specific event. The work item is only completed if the expected event occurs. The event can also be triggered by the occurrence of an XML document.
	Container operation	Elementary arithmetic operations or value assignments are applied to individual elements of the workflow container. E.g. Setting up flag values for processing can be done here.
	Process control	The functions Cancel work item or Set work item to obsolete are applied to other work items of the current workflow.
	Loop (UNTIL)	A sequence of steps is processed repeatedly until the defined termination condition occurs.
	Loop (WHILE)	A sequence of steps is processed repeatedly as long as the defined comparisons apply. The system leaves the loop when the basis of comparison does not agree with any of the comparison values.
	Fork	The processing that follows takes place in a fork. One can define how many branches have to be executed for the fork to be successfully completed, or can define an end condition in the condition editor.
	Undefined step	No function at runtime. Undefined steps always have an outcome.
	Ad hoc anchor	In the definition, one can save workflows that can replace this step. At runtime, an authorized user can select one of the saved workflows. The ad-hoc anchor is then replaced by the steps of this workflow.
	Block	Steps can be grouped together in workflow block.
	Local Workflow	Local workflow in the caller workflow has the local container and has full access to the workflow container as well. The local workflow gets triggered by local events in the caller workflow.

How Workflow can be Started/Triggered:

• Automatically By Triggering Events: Workflows can be triggered using events. Whenever this event occurs, workflow automatically gets triggered. For this, the event must be specified as the Triggering Event.
• Automatically By using Workflow: Workflow can be triggered if it is specified as the step of another workflow.
• Manually:
  • Workflows can be triggered manually in the standard environment where the necessary input data is given to workflow with triggering event.
  • Also workflows can be triggered in testing environment i.e. in development environment for testing purpose.
  • Workflow can be stared using Start Transaction. Start Transaction is the one whose execution allows all the import parameters of a workflow to be entered. After the start transaction has been executed, the SAP System starts the associated workflow with this data.
  • A user can start a workflow or task from a message issued by the system. A workflow or task must be assigned to the message. An appropriate function for this is available to the user in the message long text.

Key Features Of Non-User Interface Recording Mode:

• The non-user interface can be used for testing back-end R/3-specific modules, such as function modules and BAPIs.
• 
  
• It should be the preferred driver for interface tests in the mySAP environment.
• 
  
• It is fast, efficient, and suitable for load testing.
• 
  

Steps For Recording Using Non-User Interface Recording Mode:

1. 
   
2. Transaction SECATT.
3. 
   
4. Give the name of the Test Script(TS) in Test Script input box. The Version input by default is with value 1.
5. 
   
6. In the Attributes ->General Data Tab, the value of the component will be BC-TWB-TST-ECA for eCATT.
7. 
   
8. In the Attributes ->General Data Tab, the values of the SystemDataContainer should be given which contains all target systems with RFCs on which the script will be either executed or recorded & in the TargetSystem the name of target system (e.g. recording R/3 server) should be mentioned.
9. 
   
10. Click on the Pattern (Ctrl+F6) button from the application toolbar.
11. 
    
    

1. From the Command dropdown, select FUN. In the Function Module give the name of the function module/BAPI, which needs to be tested. Click on enter. The Interface name will automatically appear (E.g. Here BAPI_MATERIAL_SAVEDATA is used). Click on enter.
2. 
   
   

1. Double click on the Command Interface (e.g. BAPI_MATERIAL_SAVEDATA_1) from this FUN syntax in the command editor. On the right side, the command interface will open in a window. The command interface will have all the IMPORT/EXPORT/TABLES/EXCEPTIONS parameter of the given function module/BAPI.
2. 
   
   

1. Under the IMPORTING/EXPORTING/TABLES/EXCEPTIONS node, all the import parameters, export parameters, tables & the exceptions belonging to that function module/BAPI are present. These parameters can be parameterized.
2. 
   
   
   If the function module or BAPIs are called in the ABAP Program then the way the values are passed to those parameters, similar ways values will be passed here in terms of Parameterization. The declaration of these parameters will happen at the Parameter List as either Import/Export/variable.
3. 
   
   

1. All the parameters needed for the execution of the function module/BAPI will be declared in parameter list and then parameterized.
2. 
   
   

1. In the current example, BAPI is used for Material create and saving this data. Before this a unique material number is generated by system using another BAPI. This is written in ABAP-ENDABAP block. After the number is generated, this newly generated number is assigned to a variable. As import and export parameters cannot be used in inline ABAP code. So the variable is used. This variable is then passed as import parameter to BAPI, which is to be tested via this recording.
2. 
   
   

1. Once the parameterization is done. The script is ready for execution. There is no specific Start Options mode available for Non-User Interface mode at execution time. It always executes in Background mode.
2. 
   
   

1. If the recording is error free, then success log will appear. And if there is any error in recording of the transaction and its replay then error log with details will appear.
2. 
   
3. Analyze the generated log (weblog Part VI). Following is the log generated for the example mentioned here. It shows Import, Export parameter along with the execution mode and time taken for each of the individual step and complete execution.
4. 
   
   

1. Inline ABAP code is also shown in the log. It shows the results also.
2. 
   
   

1. The function module/BAPI is also shown in log. The Importing/Exporting parameters along with the message generated.
   
   

1. After the confirmation of error free recording, one can go ahead with the preparation of TD, TC for the TS.
2. 
   
3. In SECATT transaction using Test Data (TD), variants can be prepared for the recorded test script. In the Parameters tab, add all the parameters from the test script. This will appear as ECATTDEFAULT in the Variants tab. Add multiple variants, as per requirement in the Variants tab. Test Data is independent of test script. Hence can be reused wherever required. (Weblog Part IV).
4. 
   
5. In SECATT transaction using Test Configuration (TC), the TD & TS can be linked together on the Configuration tab. On the Variants tab, using Variant Maintenance Assistant required variants values from TD could be linked to TC. (Weblog Part IV).
   
6. Finally the TC can be executed from SECATT directly by giving the required variant name at runtime. (Weblog Part IV).
7. 
   
8. The TC is used in managing the scripts in plans/packages using SCAT transaction. (Weblog Part V).
9. 
   

How To Copy, Rename & Delete eCATT Objects:

1. 
   
2. One can copy all the eCATT Object i.e. Test Configuration, Test Script with Version, Test Data & System Data.
3. 
   
4. Transaction SECATT.
5. 
   
6. Click on Copy Object (Ctrl+F5) icon from the application toolbar.
7. 
   
   

1. Copy dialog box appears with the copy detail for the eCATT Object whose radio button was selected on SECATT.
2. 
   
3. For Test Configuration copy, give the name of the new TC and click on Copy button. The new test configuration will be ready.
4. 
   
   

1. Similar way, for Test Data and System Data, give the new names and click on Copy button.
2. 
   
   

1. For copying Test Script, system gives one Version input field on Copy dialog box. If this field is left blank then all the versions are copied to new name. Otherwise only the specified version is copied.
2. 
   
   

1. Rename eCATT Object: Similar to copying the eCATT objects, renaming can be done. On the application toolbar of SECATT transaction, click on Rename Object (Ctrl+F6) icon from the application toolbar.
2. 
   
   

1. Deletion Of eCATT Objects: Similar to Copying & Renaming, all the eCATT objects can be deleted. Click on Delete Object (Shift+F2) from the application toolbar of SECATT transaction.
2. 
   
   

How To Download eCATT Objects:

1. 
   
2. eCATT objects can be downloaded in XML & XSD format. These files can be further uploaded to any system. Hence the reuse of objects and their transfer amongst the R/3 system is facilitated. All the objects i.e. Test Script, Test Configuration, Test Data & System data can be downloaded via SECATT transaction. For a script to work successfully, the entire linked object should be present along with it like System Data, Test Configuration & multiple Test Data containers. This linking of objects can be known and the entire related object could be downloaded in one shot.
3. 
   
4. Transaction SECATT.
5. 
   
6. Give the name of Test Configuration or Test Script or Test Data or System Data, which needs to be downloaded.
7. 
   
8. Menu Goto -> Reference List.
9. 
   
   

1. One List Of Referenced Objects screen comes. Object Type & Object Name automatically appears depending on the selected eCATT object on SECATT screen.
2. 
   
   

1. Click on Execute (F8) button from the application toolbar. List of referenced objects will appear.
2. 
   
   

1. Click on Download All Objects (F5).
2. 
   
   

How To Upload eCATT Objects:

1. 
   
2. eCATT objects i.e. Test Script, Test Data, Test Configuration as well as System Data can be uploaded via SECATT transaction from the XML, XSD files. The prerequisite is that both the XML & XSD files should be present in the same folder.
3. 
   
4. Transaction SECATT.
5. 
   
6. Menu eCATT Object -> Upload.
7. 
   
   

1. Select Files For Upload dialog box appears. Select the file and click on Open button.
2. 
   
3. Change eCATT objects to be uploaded window appear. Select the eCATT object, give the target object name if not present & click on Enter. The object will be uploaded and directly taken to SECATT window.
4. 
   
   
   In case of Test Script, the Target Version (TV)

System Data Container Upload/Download:

What Are Parameters:

• Parameters are export, import interfaces or local variables of a script. Parameter name can be 30 char long. The first letter should be either an underscore or character.
• 
  
• Their visibility within the script is same and outside it is of import parameter, export parameter or local variable. The visibility can be set from the parameters list.
• 
  
  

1. ONLY local variables can be used in the inline ABAP block in the test script editor. Import & Export parameters CANNOT be used in the inline ABAP block.
2. 
   
3. Import Parameters (IP): Import parameters are input values to the script. They are passed to the script during execution. They are locally available and test script version independent. Import parameters can hold default value also.
4. 
   
5. Export Parameters (EP): Export parameters are outcome of the test script execution. The result value is passed into the export parameter when the test returns from the test module. They are test script version independent.
6. 
   
7. Local Variables (LV): Local variables are used in test scripts for calculations, or to receive export parameters from referred test cases or called function modules. They are also used for passing values to and from inline ABAP blocks & are version-dependent – that is, a local variable defined in one version is not automatically defined in another version.
8. 
   
9. System fields can also be used in command editor. They are read-only and are available from SYST structure.
10. 
    
11. There are special read-only eCATT variables, which can also be used in command editor. e.g. &YEARB, &YEARA, &YEAR, &VARID, &USER, &TIME, &SYSTEM, &SUBRC, &SCRIPTVERSION, &SCRIPTNAME, &SAPRL, &REFVERSION, &REFNAME, &REFLEVEL, &OPSYS, &MSX, &MST, &MSN, &MSI, &MSG, &MS4, &MS3, &MS2, &MS1, &M04, &M03, &M02, &M01, &LPC, &LOGID, &LANGUAGE, &HOST, &EXCEPTION, &DBSYS, &DATE, &CLIENT etc.
12. 
    

Why Parameterization Is Needed:

1. 
   
2. After recording of the transaction. Transaction can be checked without parameterization for errorless recording. Once the successful recording is confirmed, automation can be parameterized.
3. 
   
4. Due to parameterization, the recording becomes reusable. Different sets of data can be passed via parameters and the recorded script can be used again and again.
5. 
   
6. This is very similar to concept of Constants in Program (Without parameterization) and using variables for those values (with parameterization).
7. 
   
8. If parameterization is not done than before next execution of automated script, input data will be checked and changed at Test Script level. Due to this the errorless recording time data will be disturbed.
9. 
   Hence parameterization is necessary.
   

TCD Mode Parameterization:

1. If a transaction is recorded via TCD mode, then the screens can be simulated via screen simulation. Screen simulation can be used to edit and parameterize the fields. Screen simulation icon is present in the command interface of the TCD mode. Using Screen simulation Import parameters, Export parameters, field check, and values in the input field can be assigned. To delete the default values space characters (‘ ‘) can be passed via screen simulation. For parameterization, if the field has any value, one can clear it.
2. 
   
   

1. Fields having mode ‘S’ (Set) under each dynpro of the command interface contain some value entered during the recording. This is the value one needs to parameterize as Import Parameter so that with next run a new set of data will be passed to the recording. And recording becomes reusable.
2. 
   

1. 
   
   
   
2. Defining Import Parameters:
   

1. 
   
   
2. Defining Export Parameters:
   

1. 
   
2. The output results of the transaction are assigned to export parameters. Export parameter are necessary for chaining of transactions wherein output of one transaction becomes input for other transaction. Here export parameters can be linked between the two transactions interacting.
3. 
   
4. Fields having ‘G’ (Get) as mode are assigned to export parameters. Last dynpro in the dynpro list just before the MSG node in the command interface contains the output messages and other outcomes. Export parameters can be assigned for these values.
5. 
   

1. 
   
   
2. Defining Field Checks:
   

1. 
   
2. One can check whether the runtime value of a field is the expected value or not. The check value can be a constant or a parameter value.
3. 
   
4. Follow step 3. After step 3, screen simulation window appears. Select the field. If the field has already some value, clear the value of the field.
5. 
   

SAPGUI Mode Parameterization:

1. Defining Import Parameters:
   

1. 
   
   
2. Defining Export Parameters:
   

1. 
   
2. Export parameters are used to link transactions while chaining. i.e. Export parameter of first transaction becomes the import parameter in chaining.
   

1. 
   
   
2. Passing Values To Subsequent Screen: In SAPGUI mode, value from one screen can be passed to the subsequent screen. E.g. system generated value for an input field on one screen can be passed to subsequent screen. This can be achieved by assigning an Export Parameter to the required value. And then passing this export parameter as input (import parameters) to subsequent screens.
   

1. Declare this export parameter in the parameter list. And it can be passed further in same recording to subsequent screens as import parameter.
2. 
   
   

Chaining Of Scripts:

1. 
   
2. Test case is a series of steps (transactions) involving one business scenario. Each step is automated and then linked together via chaining so as to complete the business scenario.
3. 
   
4. Chaining mainly involves the linking of script by import & export parameters. The export parameter, which is outcome of first transaction, is passed as import parameter to second transaction and so on.
5. 
   
6. Create two test scripts, which are related in a way that output of one script becomes input to other. E.g. VA01 output of sales order can be given as input to VA02. Both the scripts should be parameterized as well.
7. 
   

1. Double click on Exporting node of the command interface. On the right side the export parameters, which were created during the script creation are displayed.
2. 
   
   

1. Similar ways include other test scripts also using REF command. Assign the import parameters and variables to the Importing as well as Exporting nodes respectively.
2. 
   
3. The export of one test script will be assigned as import of the next script using variables.
4. 
   
   

1. This ways multiple transactions can be linked together in the final chained script. The parameter list of this chained script contains only the import parameters as well as the variables.
2. 
   
   

Creation Of System Data Container (SD):

1. 
   
2. System data container contains the list of the target servers, which can be used at the recording time and/or at execution time. Target systems with their RFCs are mentioned in the SD.
3. 
   
4. Creation of RFC for target system:
   
   RFC destination will be created for the target systems, which will be used as recording time and/or execution time systems for eCATT scripts. Using SM59 on source system (where eCATT scripts will be available), create a RFC destination for R/3 system.
   
   

1. 
   
   
2. For SD creation, transaction SECATT.
3. 
   

Creation Of Test Data Container (TD):

1. 
   
2. Test data containers are used for creation of variants. Variant values are also maintained in TD. Variants created in TD are linked in Test Configuration. TD is independent of test script. Hence once created can be used for multiple scripts.
3. 
   

1. To create variant, minimum one parameter should be present in parameter list. Under the Variants tab, the column titles are Variant, Description & after that the parameters from the parameters list. ECATTDEFAULT variant will be present as default. This variant contains values from the Parameters under the Parameters tab.
2. 
   
   

Creation Of Test Configuration (TC):

1. 
   
2. Test Configuration contains reference to one Test Script (TS), one System Data container (SD) and can contain reference to multiple Test Data container (TD). TC is used in scripts management using TestWorkbench in R/3 system.
3. 
   

1. Variants can be added from Variants tab. The TC references the import part of the data interface of the test script. Variants can be prepared either manually by clicking the icons Append Variant/Insert Variants or from the wizard using test data containers referenced in the Configuration tab.
   

1. 
   
2. Manually Creating Variants:
   

1. 
   
   
2. Variants from Test Data Containers:
   
   

Steps Involved In Creation Of eCATT Test Scripts:

• Test script is generally series of steps (transactions) involving a business scenario. Identification of right transactions for this script, which prepares the input data for the script and also covers the planned business scenario, should be done.
• Recording of test script by selecting proper recording mode.
• Execution of test script immediately after recording without parameterization to confirm the errorless recording.
• Parameterization of the import, export & variable parameters.
• Preparing variants using Test Data Container.
• Linking Test Script (TS) & Test Data Container (TD) by Test Configuration (TC).
• Execution of TS using TC for different Variants.

How To Identify Any Transaction For SAPGUI Recording Mode:

• If the transaction runs under SAP GUI for Windows or SAP GUI for Java, it can be recorded by either TCD or SAP GUI mode.
• If the transaction doesn&#146;t have any activex controls then TCD recording mode should be used. Here SAPGUI mode can also work.
• If the transaction has activex controls and these controls ARE MANDATORY for the functionality of the transaction, then only SAPGUI mode can be used as recording mode.

Key Features Of SAPGUI Recording Mode:

• It is suitable for the transactions having activex controls, so it requires GUI playback mode.
• It is slow comparative to TCD recording mode.
• It is not suitable for load testing.

Steps For Recording Using SAPGUI Mode:

• Transaction SECATT.
• Give the name of the test script (TS) in Test Script input box. The Version input by default is with value 1.
• In the Attributes ->General Data Tab, the value of the component will be BC-TWB-TST-ECA for eCATT.
• In the Attributes ->General Data Tab, the values of the SystemDataContainer should be given which contains all target systems with RFCs on which the script will be either executed or recorded & in the TargetSystem the name of target system (e.g. recording R/3 server) should be mentioned.
• In the test script editor, choose the Editor tab.
• From the Application Toolbar, click on Record Test Script (Ctrl+F5).
• 
  
• One window appears with title &#145;Record SAP GUI Command&#146;, select each check box of the Automatic Generation section. Click On Start Recording button.
• 
  
• Login in to Target System from SAP Logon or either create a new session on target system.
• One window appears on the newly created session of target system as &#145;Record SAP GUI Command&#146;. Click on Yes for recording.
• 
• One window with title &#145;Recording Running&#146; will appear. In the section of Record initial state for value check, select the Record with inactive checks radio button. Below the radio buttons, one table control with the record/ types for GUI elements is mentioned along with check boxes. Select all the check boxes. Select the check box of Closed Recorded GUIs and click finally the Continue (Enter) button. This recording window exists till recording ends. Lots of data of initial state for the mentioned screen element types will be generated. So one can be selective in selecting the checkboxes.
• 
• Recording can be started with the transaction working as normal on the newly generated session.
• Once the transaction is complete with the functionality, from the Recording Running window, click on End Recording button. This will take the recorded details of the transaction to SECATT transaction in the test script editor.
• A SAPGUI command and its associated Command Interface will be inserted in test script editor of SECATT.
• 

Execution of Recorded SAPGUI script:

• Once the recording of the transaction is done and the details of recording are taken back to the test script editor, script can be executed.
• First of all without parameterization the script should be executed to confirm the errorless recording. At the runtime, a Start Options window appears. Give the following values on this window:
  • Error Behavior S No termination, continue with next script.
  • System Data &#150; Name of the system data container, which contains the Target System.
  • Target System &#150; Name of the server on which the execution will happen.
  • Select the Log Display check box.
  • In SAPGUI section of window, select following options:
    • Procg Mode SAPGUI - S Synchronous GUI Control
    • Error Mode for SAPGUI - C Continue (Continue on Any Error)
    • Stop When - N Do Not Stop
    • Close GUIs - R Close Generated Sessions After REF
  • Click on Execute button.
• 
• Transaction will start executing, by creating a new session. This requires GUI for playback.
• If the recording is error free, then success log will appear. And if there is any error in recording of the transaction and its replay then error log with details will appear.
• After the confirmation of error free recording, one can go ahead with parameterization of the import, export & variables.
• In SECATT transaction using Test Data (TD), variants can be prepared for the recorded test script. In the Parameters tab, add all the parameters from the test script. This will appear as ECATTDEFAULT in the Variants tab. Add multiple variants, as per requirement in the Variants tab. Test Data is independent of test script. Hence can be reused wherever required.
• In SECATT transaction using Test Configuration (TC), the TD & TS can be linked together on the Configuration tab. On the Variants tab, using Variant Maintenance Assistant required variants values from TD could be linked to TC.
• Finally the TC can be executed from SECATT directly by giving the required variant name at runtime.
• The TC is used in managing the scripts in plans/packages using SCAT transaction.