sapna.modi

Whats in the Name

Sapna Modi — Sat, 27 Jun 2009 01:50:36 GMT

A product nomenclature is very important aspect. It not only gives unique identity to the product but also helps a customer to understand the product evolution with different versions.

Recently I have gone through the complete business suite of SAP. While looking into different products, I found that product names are not consistent and changes year after year. The release document was required to be handy to know what the given product was named earlier and how it is known today. It is not possible for someone who is out of SAP for some time to understand what current trend is.

It makes consultant's life difficult as the information is not available at one central place. One has to search through different SAP portals (help.sap.com, service.sap.com etc) to assure the products information. E.g. SAP SRM 2007 & SAP SRM 7.0 are many a times interpreted as same product versions by consultants. This is due to the fact that most of products were renamed to 7.0 version after NetWeaver 7.0 release. Another example for this is of SAP Solution Manager 4.0, which was renamed to SAP Solution Manager 7.0. Commonly known Web Application Server (WAS) is now known as Application Server.

E.g.

Product Versions Evolution for SAP SRM -

SAP SRM 3.0

SAP SRM 4.0

SAP SRM 5.0

SAP SRM 2007

SAP SRM 7.0

Old Name - SAP Supplier Relationship Management 6.0

New Name - SAP Supplier Relationship Management 2007

Old Name - mySAP Supplier Relationship Management 2005

New Name - SAP Supplier Relationship Management 2005

Old Name - mySAP ERP 2005

New Name - ERP 6.0

Old Name - SAP NetWeaver 2004s

New Name - SAP NetWeaver 7.0

Old Name - SAP NetWeaver Composition Environment 1.0

New Name - SAP NetWeaver Composition Environment 7.1

SAP Solution Manager 4.0 - Project Preparation Phase (Part II)

Sapna Modi — Mon, 17 Sep 2007 00:09:37 GMT

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:

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:

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:

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.

SAP Solution Manager 4.0 Project Management - Business Blueprint Phase (Part III)

Sapna Modi — Thu, 28 Jun 2007 01:58:58 GMT

The part I of the SAP Solution Manager 4.0 series of weblogs targets on the functionality of SAP Solution Manager - Roadmaps Introduction (Part I). The Part II of the weblog series targets on Project Administration. In Part III, the Business Blueprint Phase is explained in detail. 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 SAPs AcceleratedSAP. And provide Roadmaps for the different types of projects.
It has Business Process Repository, which talks about SAPs 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 Phase
Testing Phase
Final Preparation for Cutover Phase
Production Go Live Phase
Support Phase

What is Business Blueprint Phase:

In any SAP Project, first the project is planned out in terms of scope, roles, resources, landscape, time line, documentation templates, quality processes to be followed etc. Once the initial administration happens, the details of the business is planned and worked out in the Business Blueprint phase. All the business scenarios related documentation also happens in this phase following quality standards and templates. The complete documentation is placed on central file server for further reference. Once the scope is designed and frizzed, Business Blueprint document is prepared finally and signed off from the client. The Microsoft Project will be then designed depending on the outcome of this phase, which will be used in the further phases. Business Blueprint acts as a prerequisite for Realization & Testing Phase. This is classical way of doing Business Blueprint if no Solution Manager is in picture.
Above activates are now available in Solution Manager with all the required features of Business Blueprinting in advanced way along with lots of other key utilities.

Transaction for Business Blueprint Phase:

SOLAR01

Menu Path for Business Blueprint Phase:

SAP Menu -> Tools -> SAP Solution Manager -> SOLAR01  Business Blueprint

Prerequisite of using Business Blueprint in Solution Manager:

Project created in Solution Manager using SOLAR_PROJECT_ADMIN transaction in the Project Administration phase.

Key Features of Business Blueprint Phase in Solution Manager:

In Business Blueprint phase of Solman, following items can be organized in hierarchical structure 
- Organization Units
- Master Data
- Business Scenarios
- Business Processes
- Process Steps
In the Business Blueprint, the Business Scenarios/Processes structure can be planned out referring the standard SAPs Business Process Repository (BPR).
Business Process Repository (BPR): Standard SAPs Business Process Repository is a repository of reusable predefined business scenarios/processes. The contents are Industry specific Best Practices for the given landscape. Landscape is available from Project Preparation Phase. BPR also includes Scenario Documentation, Transaction assignments, IMG Assignments, Configuration Guides, and Preconfigured Process delivered through BC Sets, Predefined Test Cases. Latest content of BPR can be downloaded from SAPs Service Market Place from www.service.sap.com/solutionmanager
The business scenarios can also be taken from other existing solution manager project and/or from existing Solution Directory.
Also, the Business Scenarios/Processes will be automatically available if any template (custom or standard) is selected during Project Administration phase.
In this phase, the integration of ARIS can be done with Solution Manager for getting the detailed business process modeling done out of ARIS. And further the Solman Business Blueprint features can be used.
Custom Business Scenarios/Processes can be added & positioned as per requirement.
Graphically the business scenarios are available.
Maximum of three level hierarchies of the business scenarios/processes can be inserted into Solman.
Project specific documents can be created here specific to business scenarios/processes.
The documentation is stored in the central Knowledge Warehouse of Solman.
Support Desk messages can be created.
Transaction specific to the given scenario/process can be launched in the satellite system via Business Blueprint.
Automatic generation of Business Blueprint Document is featured.
Automatic generation of MS Project is also featured.
User specific settings can be done in terms of visibility of tabs, sequencing of tabs etc.
Translation of project specific documents, URLs, knowledge warehouse documents, project structure can be done depending on the target language. If the standard documents are not available in the target language than they are displayed in the original language.
Document Management, which is one of the key features of Solution Manager, can be implemented here in Business Blueprint Phase.
Lots of standard reports are available for Business Blueprint Phase.

Business Blueprint in Detail:

Log in to Solution Manager with a user ID having authorization of SOLAR01 transaction.
Goto transaction SOLAR01.
The Business Blueprint transaction will open with the last worked project in change mode.
Click on Other Project ..(Shift+F5) button from the application toolbar.
From the list of projects displayed, select the required project. And click on Select Project (Enter) button at the bottom.
The selected project will open in change mode. There are different tabs in the Business Blueprint like Structure, Gen. Documentation, Proj. Documentation, Transactions, Messages, Graphics & End User Roles on right side. On the left side, the hierarchy of Organization Units, Master Data & Business Scenarios appear. The Business Scenarios will further drill to Business Process & actual steps (i.e. transaction in SAP).
Structure Tab:
- In the Organization Units, Structure tab helps to add Organization Area/Unit from the BPR below a business scenario. In case of Master Data, Structure tab helps to add Master Data Records from BPR below a business scenario. The Organization Units/Master Data Records are only used if they are exclusively relevant to the Business Scenarios/Processes.
- Select the Business Scenarios option from the left side, click on Structure tab on the right side.
- From the Source dropdown, select Business Process Repository.
- Now, click on the Search Help (F4 Help) of Scenario Name.
- The search helps shows, industry specific details mapping to the logical component of the current project. Select SAP for Retail -> Instore Customer Relationship Management & click on Continue (Enter).
- This will add the selected Business Scenario along with all the underlying processes into it in the Structure tab.
- Click on Save button from the standard SAP toolbar to save the project.
- Now drill down the Business Scenario node on the left side, it will show the underlying Business Processes.
- The level of hierarchy of Business Scenarios/Processes is restricted to level 3 on left side. After third level, system doesnt allow to add any more structure elements. And system shows a message in the Structure tab as you cannot maintain any more structure node below this hierarchy level.
- The execution icon before the business process on the left side indicates that there is a standard SAP transaction in the Transactions tab to carry out that step.
- One can add custom business scenarios in the Structure tab. Also the standard SAP Scenarios can be deleted. The sequence of business scenarios/processes can be planned as per requirement of project.
- Select the Business Scenarios at the top level on the left side. On the right side in the Structure tab, add custom business scenario as per requirement.
- After adding the custom scenarios, click on Save button from the standard SAP toolbar.
- The Business Scenarios can be moved up/down depending on the required sequence of scenarios in Structure tab. Select the Custom Scenario 2 in the Structure tab and click on Move Up button.
- The scenario will be moved one position up in the tab. Click on Save button from the standard SAP toolbar.
- The History of the Structure tab is also available here.
- At the Business Processes level, the name of the standard process can be changed and if needed adjusted back to original.
Gen. Documentation Tab:
- General Documentation tab contains the standard SAP delivered documents if the business scenario is selected from BPR.
- It also contains the documents from the template project.
- For the business scenarios, which are not taken from standard SAP BPR, wont have any documentation in this tab. Their documentation need to be created in Proj. Documentation tab.
- No document can be added or deleted in this tab. Also the feature of Changing the document, Check In/Check Out etc. are not available in this tab. Only documents can be opened in display mode in this tab.
- Features of Where Used List, Export, Attributes etc are available.
- There is feature of copying document to Proj. Documentation tab. This is useful in case if the document needs any changes. For this, first change the project in Display mode. Now, select the document & click on Copy Link-> Copy to Proj. Documentation Tab button.
- A popup appears for Documentation Type to be used for the new copied document in the Proj. Documentation tab. Select the appropriate type from the search help & click on Copy button at the bottom.
- The document gets copied into the Proj. Documentation tab.
- Also, user specific settings are available here to open document in the Gen. Documentation tab or in separate window. Refer the Menu Settings -> User Specific -> General Settings.
- The Gen. Documentation tab documentation is stored in the Solution Manager Knowledge Warehouse.
Proj. Documentation Tab:
- Proj. Documentation tab is used to store the documentation for the current project specific to business scenario/process on the left side.
- The documentation is stored in the Context of Knowledge Warehouse, which is specified in the Project Administration phase.
- In case of Template project, the documentation specified in the Proj. Documentation tab doesnt appear in the rolled out implementation project.
- The document can be created using the template following all the required quality standards. These are the different templates like functional specification template, technical specification template etc. It also has lots of standard SAP delivered templates.
- The document can be either created or copied to existing Solman document or linked to existing Solman document or uploaded from desk or linked to web link.
- The documents added here can be made Business Blueprint Relevant. This means that the contents of the documents will be taken while generating the Business Blueprint Document in the sequence in which they are added.
- To add a document, select the business scenario/process on the left side & click on Insert Document button on the right side in Proj. Documentation tab.
- In the Add Document popup, give the Title for the document; select the Documentation Type as Customer Input Template (standard SAP template) from the dropdown. This dropdown will contain the custom documentation templates added during Project Administration phase. Click on Enter to continue.
- The document will open using the template of the specified document type in the tab itself. Edit the document as per requirement and click on Close.
- Click on Yes to save the changes in the document.
- The document will be saved in the Proj. Documentation tab.
- The document can also be created by uploading it from desk. For this, select the business scenario/process on left side & click on Insert Document button in the Proj. Documentation tab on right side.
- In the Add Document popup, give Title as Demo for Documentation  Upload File, select the Upload File radio button and click on Ok (Enter) to continue.
- Select the Document from the Desktop & click on Open button to upload it in Solman.
- The document gets stored in the Solution Manager under Proj. Documentation tab. Further the document can be viewed/changed as per the requirement.
- The document can also be linked to any existing Solman document. For this, select the business scenario/process on the left side & click on Insert Document button.
- In the Add Document popup, select the radio button for Link to a Solution Manager Document. And click on Ok (Enter) button.
- Give the project name whose the document needs to be linked & click on Execute button.
- From the displayed documents, select the required document for linking and click on Ok (Enter).
- The document gets linked to the business scenario/process in Proj. Documentation tab.
- During the documentation, lots of changes happen to the document and different versions are maintained normally. These different versions are placed on the centralized file server. During these modifications by multiple people, multiple copies are made. This results in duplication of documents for the same scenario. Also the integrity of the document is also lost. To overcome such classical situation, there is feature given in Solution Manager for Document Check In/Out. If any document is checked out for modification then for other users that document is available only for display. The document needs to be checked in again so that it can be made available to other for editing.
- For Checking out a document for modification, select the document from the Proj. Documentation tab, click on button Check Document Out/In & select the option Check Document Out from the dropdown.
- Give the path on local desk to save the file. Click on Save button.
- Message is displayed at the bottom in the project as File Demo for Documentation  Upload File.txt has been checked out.
- Now, try to modify the same document in Solman, which was just checked out. Select the document and click on Change button.
- System prompts a message saying The document is locked by user SAPNA. The document is opened in display mode. This means the document is not available for editing if it is checkedout by somebody. Click on Cancel.
- Do the necessary modification in the document on desk and then check it again in the Solman. For this, select the document in Solman first & then click on button Check Document Out/In & select the option Check Document In from the dropdown.
- Give the path & click on Open button to get the document back into Solman.
- The document gets checked in the system and message is displayed at the bottom in the Solman project as File Demo for Documentation  Upload File.txt has been checked in.
- Now, the document is available for others to edit. To do so, select the same document & click on Change button.
- The document will be opened in change mode. Do the necessary modification & click on Close. The document status is shown as Copy Editing here. This status is part of document attribute.
- Click on Yes to save the changes to document.
- There are attributes associated with each document. A document status schema can be configured for the planned life cycle of document.
  E.g. this means first the document may have some default status linked say Copy Editing. A Solman consultant responsible say Mr. A can be given for this status. The Solman consultant Mr. A can draw a report for getting the work to be done by him. He will then edit the document as per requirement. Now the next document status will be available like In Process, Review. He will set the document to In Process and will put another person say Mr. B responsible for this status. Mr. B will do the further changes in the document and will set the status next available. This way the document will flow and complete its life cycle till it reaches to a status where the document is locked for editing.
  This status flow can be configured in document status schema.
- To view the attribute of document, select any document & click on Attribute button.
- The Maintain Attribute window has four tabs  General, Comments, Link & History. Comments can be maintained in the Comments tab. The History tab shows the history of changes on the document.
  In the General tab, select the Document Status as In Process from dropdown. Click on Check & then Save button at the bottom.
  
  Here Priority, Person Responsible, Business Blueprint Relevant checkbox, Keywords etc can also be maintained. Here a URL link can also be generated by Generate button at the bottom and this when executed in browser opens the document on web.
- The status is reflected back in the Proj. Documentation tab.
Transaction Tab:
- Transaction tab is used to assign transaction or programs or URL etc to the business scenario/process. These programs, transactions can be executed in the satellite system from Solman directly provided System Landscape with logical components is defined in Project Administration phase.
- When executed, the transaction or program or URL will result into the desired functionality of that process step.
- If the business scenarios/processes are taken from BPR then Transaction tab may contain the relevant transaction or program etc to carry out that process step.
- Each individual transaction will be taken as unit test case, when test plan will be generated from this project.
- Select any of the business process taken from BPR on left side having execution icon along with it & click on Transactions tab on the right side.
- Here the Transactions tab contains the standard SAP transactions to carry out the selected business process on left side i.e. Billing in ERP. The Logical Component is automatically selected when the process is inserted from BPR. To execute the transaction in the satellite system, select the transaction & click on Start Transaction execute button.
- The system will prompt for the user Id & password of satellite system. Give the necessary details.
- Now, the transaction VF01, which was selected in the Solman Transactions tab, is opened in the Satellite System having Logical Component Z_FOX in Solman. Work with the transaction as per requirement & click on Back till Solman is reached.
- If nothing is specified in the Transactions tab for scenarios/processes which are either from BPR or custom, one can manually add the required transaction or program etc. For this, select any process on left side not having execution icon along with it & click on Transactions tab on the right side.
- Select Transactions from the Type dropdown, ZFOX from Logical Component dropdown, select the checkbox of In Scope for making the transaction in the current project scope; select the radio button of Standard option. And now click on search help icon of Object to select a transaction.
- Select VA01 transaction from the search help. And click on Save button from application toolbar for saving the project. Now an execution icon will come beside the business Scenario Custom Scenario 2.
- In the above case, even if the transaction or program etc. wont exist in the satellite system, system will just prompt that information and will allow for adding it in Solman.
- The radio button for Standard option in the Transactions tab is used for identifying the transaction, which will first execute among all the transactions for that scenario/process. This will happen when the execution icon present beside the scenario/process is clicked.
Messages Tab:
- In the Messages tab, helpdesk message can be created in case of any issue occurred during Business Blueprint phase. These messages can be monitored and addressed by helpdesk team. Effective reports are preset for messages monitoring.
- To create a message, select the business scenario/process on left side against whom the issue will be logged & click on Create button.
- Give the necessary details like System/Base number, Component, Short Text, Long Text, Attachment if any in the popup Create Support Message and click on Save button at the bottom.
- A unique message number will be generated and the message will be stored in Solman.
Graphic Tab:
- The Graphic tab displays the hierarchy of business scenarios/processes, logical component, transaction assignment, documentation etc. graphically. It makes simple to understand the complete business scope graphically. Smooth navigation is possible between the process steps, processes & scenarios.
- The prerequisite of using Graphic tab is availability of Internet Explorer 5.5 or more, active activex controls in the browser, settings from the Menu Settings-> User Specific for viewing the transaction, documentation etc. in the graphics. Also, changes to graphic is only possible in Business Blueprint phase & is available in display mode in Realization phase as we can not change the business scope in Realization phase.
- To view graphic, select any business scenario/process on the left side and click on Graphic tab on right side.
- Click on any of the displayed graphics, it will drill down to the lower level steps.
- Different features are available like exporting graphic to MS Word or MS PowerPoint, font change for look & feel, zoom up/out, print etc.
End User Roles Tab:
The End User Roles tab has significance for assigning the roles to end users, which will be used in filtering the training material in eLearning phase of project. This will be covered in Realization phase of project management.

Generating Business Blueprint Document:

Business Blueprint document can be generated in this phase after completing all the activities.
This can be done from the Menu Business Blueprint -> Generate Blueprint Document
Select the checkboxes for Graphics & click on Execute icon at the bottom.
The system will show the message for downloading the file at the path specified. Click on Continue to download the file.
Then system will show that the download is complete and execute a Macro SAP_BUSINESS_BLUEPRINT in the downloaded MS Word file. Click on Ok to continue.
Execute the Macro in the MS Word file from the menu Tools -> Macro -> Macros -> SAP_BUSINESS_BLUERPINT. It will automatically generate the blueprint document.

Generating Microsoft Project:

Similar to Blueprint document, Microsoft Project can be generated from the menu Business Blueprint -> MS Project Download..
Select the appropriate path on desk to store the MS Projct. Click on Save button.
System shows the Path at which the file is downloaded. Click on Continue to open the MS Project.
The MS Project opens with all the details about Project Administration in terms of date etc along with the business scenarios/processes details.
Now this can be used ahead for the entire project related activates.

Checkpoints in eCATT (Part IX)

Sapna Modi — Fri, 18 May 2007 06:30:50 GMT

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.

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.

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.

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.

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.

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.

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.

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.

SAP Solution Manager - Roadmaps Introduction (Part I)

Sapna Modi — Sun, 06 May 2007 20:04:24 GMT

The part I of the SAP Solution Manager 4.0 series of weblogs targets on the functionality of Roadmaps in Solution Manager. In subsequent parts, other features of Solution Manager will be explained. h5. 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+. h5. Latest Version: SAP Solution Manager 4.0. h5. 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. ** h5. What are AcceleratedSAP (ASAP) Roadmaps: AcceleratedSAP Roadmaps are the proven procedures for Project Management. Roadmaps provide a methodology for the executing successful SAP projects of any kind like Implementation, Upgrade & Global Rollout. The methodology has a defined framework for different kinds of projects and has lots of tools, services etc. Special Accelerators are available in Roadmap structure, which help in following the best offered practices of project management and hence accelerates the speed of project. Accelerators are in terms of templates, examples, documentation, links etc. h5. Latest Version of Roadmaps: Latest version of Implementation roadmaps is V3.6 (December 2006), Upgrade Roadmap is 3.1 & Rollout Roadmap is 3.5. Roadmaps are released in the span of 6-8 months. The latest version at any time can be found on SAP Service Marketplace. (http://service.sap.com/roadmaps (http://service.sap.com/roadmaps)). h5. Transaction Codes involved in Roadmaps: 0.1. 0.2. For launching Roadmap: RMMAIN 0.3. 0.4. For creating Custom Roadmaps(without structure change): RMDEF Using this option, one can use copy of SAP’s roadmaps with custom contents. No changes can be made to the structure of the roadmap. Only header data like name & attributes (flavors, roles & subject areas) can be defined. 0.5. 0.6. For creating Custom Roadmaps(with structure change & entry screen): RMAUTH Using this option, one can define his own structure of roadmap or make changes to copied structure of standard roadmap. The documentation created or changed in terms of accelerators or so is stored in SAP NetWeaver Knowledge Warehouse. 0.7. Though the feature is given to create a new or modify copied standard roadmaps, one should be careful in using the custom functionality here. As SAP releases new roadmap, it may become difficult to adjust those parameters in custom roadmaps. So it is recommended to strictly keep track of all changes in standard roadmap and then change the custom roadmap accordingly. h5. What are different types of Roadmaps: 0.1. There are different types of Roadmaps available in SAP Solution Manager, meeting the requirements of different kinds of SAP projects. 0.2. Implementation Roadmaps: The Implementation Roadmap methodology covers the necessary project management, the configuration of business processes, testing and training aspects as well as technical implementation activities. There are following types of Implementation roadmaps available in Solman. 0.1. 0.2. ASAP Implementation Roadmap: The ASAP Implementation Roadmap provides implementation methodology for mySAP Business Suite (mySAP ERP, mySAP CRM, mySAP SCM, mySAP PLM, mySAP SRM), SAP xApps, SAP NetWeaver and SAP Solutions for Mobile Business. 0.3. ASAP Implementation Roadmap for SAP Enterprise Portal: 0.4. 0.5. ASAP Implementation Roadmap for SAP Exchange Infrastructure: 0.6. 0.7. Solution Management Roadmap: The Solution Management Roadmap provides a methodology for the implementation of the technical infrastructure and its operation. The Solution Management Roadmap complements the Implementation Roadmap. 0.8. 0.3. 0.4. Upgrade Roadmap: The Upgrade Roadmap provides SAP latest upgrade methodology to plan and execute an SAP upgrade. It bundles SAP's latest knowledge and best-practices for basic project management, functional and technical aspects to upgrade an entire SAP system landscape. 0.5. 0.6. Global Template Roadmap: The Global Template Roadmap describes how to organize and how to run a project in which a corporate template is developed. The Global Template Roadmap is geared to more complex implementation or harmonization projects, typically involving more than one kind of mySAP solution, and a variety of sites, possibly in different countries. The corporate template is rolled out to other sites in a follow-up project. 0.7. h5. Features of Roadmaps: 0.1. 0.2. Roadmaps can be Solution Manager Based or even in HTML form. The Solution Manager based roadmaps need solution manager to access them. While HTML roadmaps can be accessed via web. Though there are some features, which won’t be available in HTML form but it increases the ease of use. HTML roadmaps can not be edited, modified or filtered. 0.3. 0.4. There is Display option available in Roadmaps. There is always an initial display available for roadmaps as they are called. From this initial display, hyperlinks are given, which takes to structure display of the roadmaps. This initial display can be set as default to structure display from the menu +Settings -> User Specific+ in the +RMMAIN+ transaction. So next time when +RMMAIN+ will be called, structure will be displayed instead of initial view. 0.1. 0.2. There are filter options available in roadmaps for Flavors, Roles, and Subject Areas from the menu +Settings->Filter..+ in the +RMMAIN+ transaction. This feature enables to filter the display accordingly in the initial and structure view. 0.1. 0.2. Filter Subject Area: One can select one or more subject area from the menu +Filter-> Subject Areas+ option of +RMMAIN+ transaction. Accordingly the display will change in the initial and structure view of roadmap. 0.1. 0.2. Filter Roles: One can select one or more roles. The roadmap structure items, to which the selected roles are assigned will be displayed in the initial & structure view. 0.3. 0.4. Filter Flavors (Variants): One can select one or more flavors. The structure items to which the selected flavors are assigned will be only displayed in the initial & structure view. Flavors are selected during the Project preparation phase in +SOLAR_PROJECT_ADMIN+ transaction. 0.1. 0.2. Finally the changed structure can be viewed – 0.3. 0.4. Apart from these filters, there can be filter on Keywords & Scope when project relevant roadmap is used. 0.5. 0.6. One can directly view the Accelerators used in the project from the menu +GOTO -> Accelerators+. 0.1. 0.2. This will give a popup showing the accelerators used in the current project’s roadmap. Double clicking on the required line, will locate that accelerator in the project structure. 0.3. 0.4. Also, different view options are available in the menu +Settings -> View -> ….+ Here one can view +Complete View (Default)+ or +Method View+ or +Output View.+0.1. 0.2. Roadmaps can be downloaded into the +HTML version+ or in +MS Project Version+ from the menu +Roadmaps -> Download ->…+ h5. Structure of Roadmaps: 0.1. 0.2. The structure of Roadmap is divided into Project relevant Phases at level 1, Deliverable Groups (DG) at level 2, Deliverables, Methods (M) & Outputs (O) at level 3, Activities & Tasks at level 4. Milestones & Services Checks are also present at level 2. At different levels, the Accelerators are available in Solman to accelerate the project. 0.3. 0.4. On the left side, the above structure can be seen. On the top right +Topics+ can be viewed. These topics describe the +Outputs+ and also +Activities & Tasks+, which also result into +Outputs+. 0.1. 0.2. On the bottom right, Accelerators are present. These Accelerators contain templates, examples, link SAP online Help, link to information on Service Marketplace. It helps in speeding up the project. 0.3. 0.4. On the bottom right, many more tabs are present like Reference, Status/Notices, Proj Team Members, Issues/Message, Proj Documentation, Keywords etc. 0.5. h5. Project Specific Usage of Roadmaps: 0.1. 0.2. Roadmaps are assigned to project in transaction +SOLAR_PROJECT_ADMIN+ in the +Scope-> Roadmap Select+ tab. 0.1. 0.2. Once assigned, the Project Manager can refer to +RMMAIN+ transaction for the specific use of Roadmap for given project. 0.1. 0.2. In the Roadmap structure view, lots of accelerators, project documentation is specified. Reference material can be maintained. For each step on the left side tree, one can change the status in the Status/Notices tab. Project team members can be assigned to individual task on the left side. These team members are added during +SOLAR_PROJECT_ADMIN+ transaction. Here whatever note will be written will be automatically stored as the tab is left. Also one can maintain the issue logs in Issues/Messages tab. Helpdesk Messages can also be created here for the give task from the left side tree. For Issues/Messages tab to be used, necessary Issues & support desk settings are needed. Project documentation & Keywords can also be maintained here. h5. Project Independent Usage of Roadmaps: 0.1. 0.2. Goto transaction +RMMAIN+.0.1. 0.2. The transaction will show the roadmap of last used project. Click on +Other Project (Shift + F5)+ button from the application toolbar. 0.3. 0.4. From the popup, click on +No Project+ at the bottom of the popup. This will display the roadmap used in the earlier project. 0.1. 0.2. Now click on +Other Roadmaps (Shift + F6)+ from the application toolbar.

Workflows for Dummies - Workflow Builder(Part II)

Sapna Modi — Fri, 27 Apr 2007 07:22:46 GMT

The Part I of Workflows Introduction gives the basic details about the workflow usage as a tool and the features involved. In Part II, the details about the workflow builder will be explained. In the part III, more details about Workflow Builder will be covered. In subsequent parts Business Object Builder & details about the runtime analysis tools of workflows will be discussed.

What are SAP Business Workflows:

Using SAP Business workflows, one can define the business processes that are not yet mapped into SAP system. Workflows are suitable for the situations where the given task is executed repeatedly or when the large number of people is involved in the completion of that work. Workflows can be used in conjunction with the existing business scenarios e.g. during the standard functionality errors or exceptions occurs then workflow can be triggered on these actions.
There are lots of standard workflows available from SAP for different areas like Sales & Distribution (SD), Travel Management (TV), Treasury (TR), General Logistics (LO), and Personnel Management (PA) etc.

What is 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. For graphical modeling view, the prerequisite is to have SAPGUI for Windows.

Transaction for Workflow Builder:

SWDD

Menu path for Workflow Builder:

SAP Menu -> Tools -> Business Workflow -> Development -> Definition Tools -> Workflow Builder -> 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 dont 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 
- L  Event Driven Process Chains:
  - Goto menu Extras -> Options -> tab View.
  - Select the value from the Display of Modeling View  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  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  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  View dropdown as N  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.

SAP Solution Manager - A Concern Area

Sapna Modi — Fri, 20 Apr 2007 06:00:51 GMT

This weblog gives brief introduction of SAP Solution Manager. The main concern here is to mention some areas in solution manager which require some more enhancement and few are mentioned from the better usage perspective of Solution Manager.

What is SAP Solution Manager:

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 SAPs AcceleratedSAP. And provide Roadmaps for the different types of projects.
It has Business Process Repository, which talks about SAPs 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.

Template Project Type:

In Template project type, only the documentation under Gen. Documentation tab in Business blueprint phase is shared to the rolling out implementation project. The requirement of sharing the Project Documentation tab arises many a times.

SOLAR02 Transaction code: Configuration:

The development objects are required to develop first in the satellite system and then only the objects can be linked in solution manager. This option increases the chances of missing the objects for those business scenarios. Also the transport request won't be tracked back in solman.
The dropdown of the development object shows only limited type of objects. Ideal expectation is that for all the connected satellite systems, the respective development object types which can be attached to a transport request should be automatically populated in the dropdown.

Test Management:

The reporting feature of test management is not so user friendly. Specifically in a scenario where the testing is done successfully and logs are recorded in solution manager with few scripts failed. For the failed scripts one has to drill down a lot in the log till the consultant gets the exact issue. This is more painful if the external tool like Mercury QTP is connected to Solution Manager for web based testing like SRM/CRM.
The eCATT logs are not at all user friendly. If there is a functional error like GL account doesn't exist then it will be conveyed very clearly in the log. But if is related to some screen mismatch at the run time for that recorded script the such technical errors are very hard to find out from the logs.
The SAPGUI pattern of recording is extremely slow and take too much of time for recording enjoy transactions. It not only takes long time for recording but also long time for execution.
eCATT doesnt serve the web based transactions for testing.

Helpdesk Application:

There is a BAPI for creating the helpdesk message but no BAPI is available for modification.
One has to follow the transaction for helpdesk ticket changes via BDC or so. e.g. CRM_DNO_MONITOR or CRMD_ORDER transaction can be used to modify the ticket. The problem with these transactions is that BDC of these transactions doesn't work if it is run under workflow/background job.
The CRM_DNO_MONITOR transaction has a feature of 'Mine' in the selection screen, which shows the tickets created by logged in user. Here all the tickets created by logged in user for different satellite systems should appear. But it shows only tickets created for only one of the satellite systems, whos external Business Partner(employee type) is linked with solution mananger ID. As per the concept of CRM, only one external Business Partner (employee type) can be connected to solution manager ID. Hence rest other satellite systems external business partner are never connected to Solman ID. So the logged in user can not see all his tickets created in different satellite systems.
The web interface for the helpdesk application is not really very user friendly. E.g. selection of Component End users won't be aware about the link between their problem and the relevant SAP Component.
There should be easy provision available for linking this helpdesk application to SAP Portal as most of the clients do have portal as a central point of access via their users.
Automatic assignment of tickets should happen while creation depending on the skills with consideration of availability on that day & workload. And then the concern person should be informed on different communication channel like emails, pager message etc.
The functionality of Solution Manager Helpdesk should be like service marketplace with the provision for customized escalation.
Generally the clients have some or other legacy system for helpdesk and end uses are very much used to that. Considering this, the layout of the solution manager helpdesk for ticket creation should be very flexible to give the end users enough comfort level in new helpdesk environment.
Linking of External Helpdesk to Solution Manager Helpdesk has lots of problems like status profile synchronization etc if the other system is also SAP Solution Manager. And if the connected system is a legacy system then issues of Sold-to-Party etc fields without any values are assigned to them is also there.

Common concerns:

Transaction codes are too long to remember.
Lots of configuration settings are available in solution manager. A simple handy guide should be available for the different areas of Solman considering this configuration. Even recorded tutor files in this concern will also help to utilize these features efficiently.

Workflows for Dummies - Introduction(Part I)

Sapna Modi — Mon, 19 Feb 2007 05:27:06 GMT

The Part I of Workflows Introduction gives the basic details about the workflow usage as a tool and the features involved. In Part II, the details about the workflow builder will be covered. In the subsequent parts, more details about the runtime analysis tools of workflows will be discussed.

What are SAP Business Workflows:

Why Workflows:

Following are the scenarios, which occur on daily basis in each organization -

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 doesnt 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:

There is three level of two way Binding concept involved in workflows. Here binding is meant by the interaction between two consecutive levels using variables (Import/Export parameters). The first level of binding exists between the event triggering the workflow and the workflows container i.e. workflow gets the necessary inputs for processing. The second level of binding exists between this workflow container and the step (task) container. And the third level of binding exists between the step (task) container and the method inside this step (task).
Here the values in the variables are passed to workflows, which then flows to tasks & finally to corresponding methods as Import parameters. The outcome of these methods if needed can be passed back to task & then finally to workflow. The outcome of one task can also be passed to next tasks using this 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:

Workflow can be triggered in following different ways 

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.

eCATT Tips Of Recording, Testing & Links (PART VIII)

Sapna Modi — Mon, 24 Apr 2006 02:54:27 GMT

Tips To Be Followed Before or During Recording:

Test case is generally a series of transactions pertaining to one business scenario. Before recording of the script via eCATT, work with the script on R/3 system directly with a given set of valid data for the entire script. Execute the script manually directly on R/3 for at least 2-3 times with the same set of data. On 2nd time onwards, system may prompt some error messages, warning messages etc. Correct the data only for the error messages and let the warning messages & popup be as it is. This way the data is ready which gives all possible behavior of the transaction. Now record the script with this data. Recording will now include the extra popup, warning messages, which normally dont come. Make these screens optional in SAPGUI mode. After recording, without parameterization check for the errorless recording by execution. If the recording is successful, then only go for parameterization otherwise do the corrections by rerecording if needed.
There can be some default settings for the parameters values on the user ID by which the recording is done. Make sure that before replaying those recorded eCATT scripts, the default user ID settings are done on the system on which the final execution will happen. Following such prerequisites in terms of user ID settings or some behavior of transaction of first run, in same session with some default data etc. always help in the successful execution of the scripts.
If the transaction to be recorded on R/3 involves dropdown list box, do the following setting before recording of that transaction. Due to following settings, the keys will be assigned to each item in the dropdown in sorted manner and recording will happen for these keys values. This helps in replaying the transaction successfully.
- Log on to target R/3 system. On any transaction, click on Customizing Of Local Layout (Ctrl+F12) icon from the application toolbar. Select the Options -> Expert.
- On the Expert tab, in the Controls section select the checkboxes of Show keys in all dropdown lists & Sort items by keys.
- Transaction with dropdown without keys setting 
  
  Transaction with dropdown keys settings 
If the recording includes, adding some value to the table then dont scroll up to blank line. Use directly the Create Item icon and then add the new values. Scrolling fails at the time of replay.
If the recording includes searching some value from ALV grid and the value is known then dont scroll and look for the value. Use the Search icon from the ALV toolbar for searching. Once the search item is found, then click on the item for further processing.
It happens at times that the screen size reduces at the time of recording in width and height. In such scenario if the field to be captured during recording is present somewhere at the bottom, then dont scroll. Use the TAB key till that field is reached. Due to Scroll functionality possibility of script failure becomes high.
It is not possible to capture the value from a dynamically generated list. If the recording includes a dynamically generated list and one value (which is not known until execution) from this list needs to pass to the subsequent step in recording then use foreground mode of recording for this dynamically generated list. Use WAIT XXX statement after its recording. During this WAIT XXX seconds, capture the value from the generated list manually and pass it to the next recording.

SAPGUI & TCD Recording Modes:

Error messages can be recorded and replayed by Only SAPGUI recording mode and NOT by TCD mode.
Warning messages are automatically handled by TCD mode but in SAPGUI recording mode they need to be handled if they require user intervention for further processing. (E.g. Pressing and enter key will enable all the fields after warning message)
Screens can be made Optional for execution in SAPGUI mode. This optional screen will be handled automatically at runtime even if not in the screens flow. But in TCD screens cant be made optional which may or may not occur during execution. Rather in TCD screens can be made active or deactivated in the cases where depending on some input values, the recording can be reused. The screens sequence should be known well in advance in TCD for making any screen active or not.
Only local variables from the eCATT Parameters can be used in Inline ABAP code. Import and Export parameter are not allowed.
Passing values to subsequent screens at runtime is only possible in SAPGUI and not in TCD mode.
SAPGUI Confirm Popup:
In order to avoid the following popup for SAPGUI recording, option is available in R/3 System.

Click on the icon with tool tip Customizing Of Local Layout (Alt+F12) in the standard toolbar on any transaction of R/3 system. Select the Options menu.

From the Options -> Scripting, uncheck the check box of Notify when a script attaches to a running GUI. Click on Apply -> Ok. The popup wont appear onwards.
Making SAPGUI Screen Optional:
It is possible in SAPGUI recording mode to make screens optional.
Double click on the screen or message popup, which needed to make optional on the left side in the command editor. On right side, the interface will open. Under the ProcessedScreen node, first option is Active 'X'.

Change Active 'X' to 'O'.

'X' - Active (Compulsory will execute)
'O' - Optional (will execute only when it will be in execution flow).

eCATT Commands:

An eCATT script consists of individual eCATT commands. Each command begins with a command word and ends with a period. Comments (*) and assignments (=) are exceptions to this rule.
There can be several commands on the same line. Comments (*), assignments (=), and inline ABAP are exceptions to this rule.
E.g. of eCATT Commands are -
*, =, ABAP, CHETAB, CHEVAR, CLEAR, DO, ELSE, ELSEIF, ENDABAP, ENDDO, ENDIF, ENDMESSAGE, EXIT, FUN, GETTAB, IF, LOG, MESSAGE, ON_LAST_MESSAGE_CHECK, REF, REFCATT, REFEXT, REMOTECATT, RESTAB, SAPGUI, SENDEXT, SETTAB, TCD, WAIT, WAIT_ON_DYNPRO
There are examples involving these eCATT commands, which can be found from the menu Goto-> Use Of Command.
On the next screen eCATT  Search Of eCATT Commands in Test Script, in the Command input field, give the name of the eCATT Command from the F4 help.

And click on Execute (F8) button from the application toolbar. List of examples will be in the output.

Key Points Can Be Followed For Successful Testing Via eCATT:

Analysis of transactions with different behaviors for different sets of data. Finally selecting the set of data, which gives maximum possible messages/popup for the given transaction.
Automation along with the verification before final regression on Quality Server.
Preparation of variant files with details having comments on each value, which helps in preparation of data for the scripts before execution.
Analyzing the behavior of transactions for the background/ foreground execution mode. Accordingly preparation of packages for background & foreground execution.
Preparing the prerequisites for the regression as a whole considering the user ID settings. Also the transaction settings for those user IDs.
Maintaining the results in scorecard with log IDs for each location the scripts being tested during regression on Quality. This helps for future reference of script results. Scorecard can be something like as follows -

eCATT Weblog Links From SDN:

eCATT An Introduction (Part I)
eCATT - An Introduction (PART I)
eCATT Scripts Creation - TCD Mode (Part II)
/people/sapna.modi/blog/2006/04/10/ecatt-scripts-creation-150-tcd-mode-part-ii
eCATT Scripts Creation - SAPGUI Mode (Part II)
eCATT Scripts Creation - SAPGUI Mode (PART III)
eCATT Chaining, Parameterization, Creation Of Test Data, Test Configuration, System Data (Part IV)
eCATT Chaining, Parameterization, Creation Of Test Data,Test Configuration, System Data (PART IV)
eCATT Scripts Management Via Test Workbench (Part V)
eCATT Scripts Management Via Test Workbench (PART V)
eCATT Logs (Part VI)
eCATT Logs (PART VI)
eCATT Scripts Creation Non User Interface Mode & Rename, Copy, Delete, Upload & Download eCATT Objects:
eCATT Scripts Creation Non-User Interface Mode & Rename, Copy, Delete, Upload, Download eCATT Objects(PART VII)
eCATT - Creating A Test Case For WebDynpro:
eCATT : Creating a Test Case for a Web Dynpro Application

eCATT Links From SAP Help:

Online SAP Help For eCATT:
http://help.sap.com/saphelp_nw04/helpdata/en/20/e81c3b84e65e7be10000000a11402f/frameset.htm
TCD Parameterization:
http://help.sap.com/saphelp_erp2004/helpdata/en/b5/c5f60a2b5bc74f8ca0eef40158806c/content.htm
TCD Command Interface:
http://help.sap.com/saphelp_erp2004/helpdata/en/82/fc193c66f5dc1ce10000000a11405a/frameset.htm
Setting Field Values Dynamically In TCD:
http://help.sap.com/saphelp_erp2004/helpdata/en/05/33384162316532e10000000a1550b0/frameset.htm
SAPGUI Command Interface:
http://help.sap.com/saphelp_erp2004/helpdata/en/bc/6d7290f64c11489f2c9b03458ef53f/frameset.htm
Execution Start Options:
http://help.sap.com/saphelp_erp2004/helpdata/en/bc/6d7290f64c11489f2c9b03458ef53f/frameset.htm

eCATT Links From SAP Service Marketplace:

For accessing site from SAP Service Marketplace, user ID & Password is required.

eCATT Details On Service Marketplace:
https://websmp204.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700003012112003E
eCATT Frequently Asked Questions:
https://websmp104.sap-ag.de/~sapidb/011000358700003021722003E#availablesince
eCATT Security Guide:
https://websmp204.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700003043282003E

Useful eCATT Links From SDN Forum:

How To Find eCATT Version:
Re: How to see the patch level installed in ECC5.00
eCATT Error - Error In Control Details:
Re: Error in Control in eCATT
eCATT Error  Control Data Obsolete Details:
Re: eCATT error
Testing Custom Report Output Using eCATT:
Re: Testing Report Output with eCATT
eCATT - Problem With ME21/MIRO/MIGO:
Re: ECATT: ME21N fails if run twice
eCATT Error  Screens Smaller When Replayed & Caused Error:
Re: Ecatt screens smaller when replayed and cause error
eCATT - Executing Several Variants At Once:
Re: Executing eCATT several variants at once
eCATT  Creating Summary Report Based On Logs:
Re: ECATT: Creating a summary report based on the script logs.
eCATT Error -GUI Recording Not Working With VA01 (RE) Return:
Re: eCATT: Gui recording not working for VA01 (RE) return order
eCATT  Which Dynpro Of Recording Corresponds To Which Screen Of Transaction:
Re: How to parameterize to limit the code
eCATT  Running eCATT Scripts In Batch:
Re: Running eCATT script in background/batch job
eCATT  SAPs Best Practice For eCATT:
Re: eCATT: SAP's Best Practice For eCATT
eCATT  Updating Automatic Execution Result In Solution Manager:
Re: Testing -No status update happ after a test case is run in solution manager
eCATT  Testing eCATT Scripts In Multiple System:
Re: Testing the same eCATT script in two test systems
eCATT  Meaning Of Transactions Containing Controls (SAPGUI):
Re: eCATT SAPGUI meaning
eCATT  Workflow Testing By eCATT:
Re: eCATT with Workflow
eCATT  SAPGUI Mode  Making Screen Optional:
Re: Optional step (screen)
eCATT  Parameterize The Input Date As System Date:
Re: If i want to parameterize date as system date
eCATT  Impact Of Solution Manager Version Upgrade On eCATT:
Re: Impact Of eCATT Version Upgarde From 3.1 To 3.2
eCATT Error - Problem In Recording ME5J/ME53N:
eCATT - Problems In Recording ME5J, ME53N
eCATT  Security Testing Via eCATT:
Re: Security Testing using eCATT
eCATT Error: Problems Due To Changed Configuration & Master Data:
Re: eCATT: Failure of eCATT Scripts Due To Changed Configuration & Master Data
New To eCATT:
Re: I am new to eCATT
eCATT  Uploading Data From Excel:
Re: Uploading a file from excel
eCATT  SAPGUI Recording Queries:
Re: eCATT SAPGUI Recording Queries
eCATT Error  Testing Webdynpro Logon Error:
Testing Web Dynpro appliction Using eCatt
eCATT  TCD Mode  Dynamically Assigning Parameter Value 
Re: Multiple Line items
eCATT - Difference Between CATT & eCATT:
difference between CATT and ECATT
eCATT - RFC Functions In eCATT:
A question of eCATT
eCATT Error  eCATT Not Supported In SAPGUI For JAVA:
eCATT not supported in SAPGUI for Java
eCATT  Log Export RFC Function Module:
ecatt-log export rfc

eCATT Scripts Creation Non-User Interface Mode & Rename, Copy, Delete, Upload, Download eCATT Objects(PART VII)

Sapna Modi — Wed, 19 Apr 2006 06:33:39 GMT

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 are explained in detail.

In Part VII, creation of eCATT Scripts using Non-User Interface mode will be explained along with the details of Copy, Rename, Delete, Upload and Download of eCATT objects. In the subsequent Part, tips & l inks of eCATT will be covered.

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:

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.
Click on the Pattern (Ctrl+F6) button from the application toolbar.

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.

The FUN with the function module/BAPI name along with the command interface will be inserted into command editor.

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.

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.
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.

The output message variables, like the other recording modes, can be captured from the Exporting node.

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

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.

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.

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.
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.

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

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

After the confirmation of error free recording, one can go ahead with the preparation of TD, TC for the TS.
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).
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).
Finally the TC can be executed from SECATT directly by giving the required variant name at runtime. (Weblog Part IV).
The TC is used in managing the scripts in plans/packages using SCAT transaction. (Weblog Part V).

How To Copy, Rename & Delete eCATT Objects:

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

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

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

System Data Copy-

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.

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.

Depending on the eCATT object selected, the Rename dialog box will appear. Give the new name and click on Rename button. The object will be renamed.

Similar ways all other eCATT objects can be renamed.

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.

Confirmation Prompt dialog box will appear. Click on Yes for the deletion of object.

There is no dependency on objects for deletion. Meaning deletion of TC won’t affect the TD & TS inside it. In case of Test Scripts deletion, to delete specific version mention it in the transaction. If the version field is left empty, all the versions are deleted. Similar way all the other eCATT objects can be deleted.

How To Download eCATT Objects:

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.
Transaction SECATT.
Give the name of Test Configuration or Test Script or Test Data or System Data, which needs to be downloaded.
Menu Goto -> Reference List.

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

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

Click on Download All Objects (F5).

All the objects from the referenced list will be downloaded at the path given in the Browse For Folder dialog box. Click on Ok.

The files will be downloaded at the given destination in XML XSD format.

Similar way other eCATT objects can be individually downloaded.

How To Upload eCATT Objects:

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.
Transaction SECATT.
Menu eCATT Object -> Upload.

Select Files For Upload dialog box appears. Select the file and click on Open button.
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.
In case of Test Script, the Target Version (TV)

number can be given.

This way multiple objects can be uploaded.

System Data Container Upload/Download:

When uploading or downloading system data containers for copying to another system, the name of an RFC destination remains unchanged in the RFC Destination field. However, in the new system, this name might not exist or might be that of a different RFC destination. In this case, RFC destination needs to be maintained.

eCATT Logs (PART VI)

Sapna Modi — Tue, 18 Apr 2006 18:18:50 GMT

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 Part III, SAPGUI recording mode of recording 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 will be explained in detail & in the subsequent parts other details of eCATT will be covered.

What Are eCATT Logs:

eCATT Logs are generated every time a test script or test configuration is executed either by SECATT or SCAT transaction.
The log is hierarchically structured according to the test script used, and displayed as a structure with nodes. Each test script in turn may contain one or many recorded transactions. This also includes any inline ABAP code or any other eCATT commands if used.
Each of the eCATT log shows the execution status of each of the step executed for the given test script along with necessary details like unique log ID, executed variants details, Import/Export/Local parameters details, Target System details, Source System details, Test Data container, time taken for each step of automated steps as well as total execution time in seconds, execution mode like With Interruption (Foreground for TCD & with user intervention for SAPGUI) or Without Interruption (Background for TCD & without user intervention for SAPGUI) etc.

Advantages Of eCATT Logs:

eCATT log stores all the steps of the test case along with lots of other useful information about systems, variants etc.
These logs help in analysis of the business process. As all the system messages are stored in the logs, which are generated during execution of the given script, it becomes simple to analyze the result set.
The expiry date of logs can be changed. So they can be maintained for the defined time frame. And hence the results of one regression testing can be used as reference for next regression testing. This helps in rollout projects.
In case of errors, system prompts the relevant messages, which help in understanding of the process that has gone wrong. After necessary corrections, the script can be again executed and the new log will be generated. The success, error or execution status is depicted by colors in logs. So it becomes much more user friendly to analyze.

How To Look In eCATT Log From Log ID:

Transaction SECATT.
Click on Logs (Ctrl+F12) icon from the application toolbar.
Under the Log Selection section, in Currt. Procedure No. Input field give the log ID.
Remove the values from the Starter & Start date input fields. They are not necessary in this case, as Log ID is known. In case log ID is not known & one wants to analyze all the logs generated on a particular date by a particular tester then give these input fields. Other input fields include Test Configuration, Test Script, Expiry date, which in this case are not mandatory. Different input combinations can be made for eCATT logs depending on what kind of input is in hand. In absence of eCATT Log ID, the combination of other input fields becomes useful.
Click on Execute (F8) button.
eCATT Log with the Log ID in title appears in next window. By click on Expand All Nodes (F5) button, all the nodes will be drilled down till end. And the detailed view of log will be displayed.

How To Look Into eCATT Logs From Test Workbench:

With the assumption that test package is executed, logs from test package will be analyzed here.
Transaction SCAT.
Menu Environment -> Manage Test Plan.
Give the name of test plan. Click on Status Analysis button from the application toolbar.
The execution status of the package is in terms of traffic lights under the Status column with description under Status Text column.
Click on the traffic light of the required test configuration. After click, Status Maintenance window appears. This window contains Test Case details, Status of execution etc. Click on Log (Shift+F1) button from the application toolbar.
Detailed eCATT Log is displayed against that test configuration with unique log ID.

Analysis Of eCATT Logs:

Top Level Information: The first line of the log displays the log identification number. Depending on the tests, other information is also displayed:
- The number of test configurations executed. (This information appears if the execution happens from the test workbench via SCAT).
- The name of the test script or test configuration executed via SECATT.
- The version number of the test script.
- The execution mode i.e. With Interruption (Foreground for TCD & with user intervention for SAPGUI) or Without Interruption (Background for TCD & without user intervention for SAPGUI) .
After the top line following information is displayed in one line: System, Client, User, Language, Release, ApplicationServer, Operating System, Database System, Date of exeuction, Time of execution.
Script Details:
After the detailed systems information, the test script details like test script name, version, description & execution time taken by the complete script is displayed in seconds. The system Data Container as well as Test Data container are also displayed. The status of execution of scripts is depicted by colors either green background color for success or red background color for error.

Successful Script

Script in Error
Maintenance System:
If a test script has a maintenance system, the RFC destination is displayed and the detailed component information is shown below it.
Comments, Duration, IF-ENDIF structure:
To display comments, duration time in seconds in the log, click on Settings(Shift+F7) icon from the application toolbar. Select the check boxes of Disp. Duration, Display Comments. Press Enter.

The log with the comments, duration time will be displayed. If the IF-ENDIF structure is executed, it is displayed with green color otherwise not.
Errors, Multiple Variants, Messages, Navigation:
- Error: If a script contains one or more errors, it is in error with background red color. If a node is marked as containing an error, the node above it in the hierarchy is also marked as containing an error with red color. Error message is immediately displayed after that step and even after the script details.
- Messages: Messages during the execution are displayed in the log under messages node. Messages can also be seen in XML data.
- Multiple Variants: Script can be executed using multiple variants. The variant names appear one after the other in the log.
- Navigation: By clicking on the hyperlinks from the log, one can navigate to the test script, system data or test data etc. When a recorded transaction uses a print function that sends a document to the spool, a message is recorded in the log.
XML Data:
XML data is generated when testing function modules and transactions. To view XML data, click the hyperlink name of the XML data in the log.

Here is an extract of XML-DATA-01 from the log shown above.

How To Change Expiry Dates/Deletion/Archiving Of eCATT Logs:

Transaction SECATT.
Click on Logs (Ctrl+F12) icon from the application toolbar.
Under the Log Selection section, in Currt. Procedure No. Input field give the log IDs by clicking on the Multiple Selection button. Multiple Selections For Currt. Procedure No. window appears. The entire log IDs should be given here. Click on Execute (F8) button.
On the Log Selection window, the multiple selection button will show green status for having multiple values of Log Ids. Click on Execute (F8) button.
Logs from the selection screen are displayed in the tabular format with the details like status, start date, end date, starter, expiry date, test script, test configuration etc.
Select all the logs by clicking on Select All icon on left top of the grid. Click on Change Expiry Date (Ctrl+F8) button from the application toolbar.
Date change window appears. Set the required expiry dates to the logs. Click on Enter. The Expiry date will change for the all the selected logs to this new value.
When the expiry date reaches for any log, the log is automatically deleted. If the automatic deletion is not required, explicitly also the log can be deleted from the menu Log Selection->Delete (Shift+F2).
Also the logs can be archived. Select the log from the list, from the menu Log Selection -> Archiving On/Off (Ctrl+F7).

How To Find Database Tables For eCATT Logs:

Transaction SARA.
In the Object Name input field give value ECATT_LOG.
Click on Database Tables button from the application toolbar.
On the Tables & Archiving Objects window, in the Tables from which data is archived section, tables are displayed for eCATT Log. These are the tables in which the log is stored in the database. Select the All Tables radio button.

eCATT Chaining, Parameterization, Creation Of Test Data,Test Configuration, System Data (PART IV)

Sapna Modi — Tue, 18 Apr 2006 18:17:44 GMT

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.

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.
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.
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.
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.
System fields can also be used in command editor. They are read-only and are available from SYST structure.
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.

The status of values, either fixed or parameterized or not define, are symbolized as follows -

Why Parameterization Is Needed:

After recording of the transaction. Transaction can be checked without parameterization for errorless recording. Once the successful recording is confirmed, automation can be parameterized.
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.
This is very similar to concept of Constants in Program (Without parameterization) and using variables for those values (with parameterization).
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.
Hence parameterization is necessary.

TCD Mode Parameterization:

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.

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.

For parameterization, select the Dynpro whose fields need to be parameterized as Import/Export parameter. Click on Screen Simulation icon of the command interface. The system will prompt for the login of recording time target system. Give the login details.

Defining Import Parameters:

After step 3, the screen simulation window will appear. Select the field value & click on Insert Import Parameter (F6) icon from the application toolbar.

One Maintain field entry window appears for the selected field with its technical name. Give the parameter name & default value in the Field contents there. Press enter. The parameter will be inserted into the parameter list. Click on Back (F3) button of the standard toolbar.

This way one can parameterize all the import values.

Defining Export Parameters:

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.
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.

Follow step 3. After step 3, the screen simulation window will appear. Select the field and click on the Read field value (CtrlShiftF3) icon from the application toolbar.

Read field value window appears. The field with the technical name appears against which the Param. Name needs to be given. Give the name of the export parameter. Click on enter. Automatically the name will be included in the Parameters list. Click on Back (F3) button from the standard toolbar.

This way one can parameterize all the export values.

Defining Field Checks:

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.
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.

Click on the Check field (CtrlShiftF2) icon from the application toolbar.

Maintain field check dialog box appears. Give the name of the variable in the Param. Name. If it doesn’t exist, it will be created automatically as import parameter in the parameter list. Give the value against this field. Click on enter. Click on Back (F3) button from the standard toolbar.

SAPGUI Mode Parameterization:

Defining Import Parameters:

Import parameters are defined for the input values given during the recording of the transaction. These values are present under the ProcessedScreen node of the SAPGUI command interface for the given screen.

Double click on the command interface of SAPGUI command from the test script editor from the left side. On right side the command interface will open. Under the ProcessedScreen -> UserChangedState node select the State node of the field, which needs to be parameterized. Double click on the field number. On the rightmost section, assign the Import parameter to Value field.

Define this import parameter in the parameter list with the type of the field & assign the default value.

This way multiple import parameters can be assigned & created.

Defining Export Parameters:

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

Export parameters are assigned to result of transaction. e.g. Material Created out of MM01 transaction. So the results are captured from Message node under the ProcessedScreen node using MESSAGE-ENDMESSAGE command.

Click on Pattern (CtrlF6)+ button from the application toolbar. From the Command dropdown, select the MESSGAE MESSAGE …END MESSAGE option. The Interface name is automatically populated by system. Click on enter.

The MESSAGE-ENDMESSAGE for interface MSG_1 will be inserted into the test script editor. Place this block around the SAPGUI command from which the export value will be captured. After that assign the respective message parameter to the export parameter.

The message variable number can be confirmed from the command interface from the right side.

Declare this export parameter in the parameter list.

This way multiple export parameters can be declared.

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.

Double click on interface from the SAPGUI command in which the parameter to be captured exists, in test script editor. On the right side, the command interface will open. Under the ProcessedScreen -> InitialState node, the value will exist. Make sure that the Check, of the topmost GuiElement branch under which the GuiElement exists which needs to capture, is blank ‘ ‘ instead of ‘X’.

Under the State node of the GuiElement, which is to be captured, double click on the number, which appears in square braces. On the right side, Name & Value will appear. There in Value, write the Export Parameter name.

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

Chaining Of Scripts:

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.
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.
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.

For creating chaining of the scripts, create a new script. Transaction SECATT. Click on Pattern (CtrlF6)+ button from the application toolbar.

One Insert Statement dialog box will appear. From the Command dropdown, select REF command. In the Test Script, give the name of test script, which needs to be linked. Press Enter. The Interface name will be automatically populated. Press Enter.

The REF command will be inserted into the test script editor.

Double click on the Command Interface of the inserted REF statement in the test script editor. On the right side the interface will open with the Importing/Exporting nodes. These Importing and Exporting node have import and export parameters, which were assigned while creation of that script. Double click on Importing node. On the rightmost side, all the import parameters appear under the Element column.

Declare all import parameters in the Parameter section above and assign then in Value column below against the Import parameters.

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.

Declare the variables and assign them to the export parameters.

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.
The export of one test script will be assigned as import of the next script using variables.

The import parameter of chained script is assigned to the respective Importing node element.

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.

Click on Save (CtrlS)+ button from the standard toolbar. By giving the default values in the import parameters, execute the script and ensure the correctness of chaining. Once the successful execution of the chained script is confirmed, TD and TC can be prepared.

Creation Of System Data Container (SD):

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.
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.

Give the necessary details like RFC Destination, Connection Type, Description.

In Logon/Security tab, recommended is to mention the Trusted system ‘No’. This ensures that every time, login window will be prompted when target system is referred via RFC. Hence secure. After RFC creation, the server can be added to the SD list.

For SD creation, transaction SECATT.

In the System Data input field give the name of SD. Click on Create Object (F5) icon from the application toolbar.

On the create screen, in the Attribs tab, give the Title (mandatory) for the SD.

Under the System Data tab, target system NONE is already present. Append a new row by clicking Append row icon from the toolbar. In the Test System column, give the name of the target server. By this name the target system will be referred in eCATT. Under the RFC Destination column, select the respective RFC for the target system. The Instance Description field is automatically filled by system. Click on Save (CtrlS)+ icon from the standard toolbar.

This way multiple target systems can be added to the system data.

Creation Of Test Data Container (TD):

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.

Transaction SECATT.

In the Test Data input field, give the name of the test data. Click on Create Object (F5) icon from the application toolbar.

On the create screen, under the Attributes -> General Data tab in the Header Data section, give Title (Mandatory) and Component (Mandatory). Under the Maintenance System, give the SystemData Container as well as Target System, which is present in the SD.

Under the Parameters tab, click on Append Parameter icon and the new lines will be appended in the parameter list. Add the lines to the required number of parameters. Add the parameters. The parameters name & type must match to that of the script to which the TD will be linked. Click on Save (CtrlS)+ button from the standard toolbar.

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.

To add new variants, click on Append Variant icon. Give the details of new variant with values. Add required number of variants this way. Click on Save (CtrlS)+ button from the standard toolbar.

Creation Of Test Configuration (TC):

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.

One more Advantage of using TC is that for any given script, without changing data at TS level, the script can be checked for different sets of data using Variants of TC. In turn these variant values are captured from TD. Hence the errorless recording time data is always maintained in TS. And the Last Changed script attribute (Attributes tab -> Extras tab -> Administration Data) will contain only the details of the person who has made changes to script and not to the data.

For TC creation, transaction SECATT.

Give the name of TC in Test Configuration and click on Create Object (F5) icon from the application toolbar.

On the create screen, give the Title (Mandatory) & Component (Mandatory).

Under the Configuration tab, give the System Data Container, which contains the Target System. Also give the name of Test Script. Test Data and an Alias can be added to Test Data section using Append Row icon. The Alias is an alphanumeric name up to three characters. Multiple test data can be given if required.

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.

Manually Creating Variants:

In the Test Configuration editor under Variants tab, click on the Append Variant icon. This will insert a new line for variant under ECATTDEFAULT.

In the Variants field, give the name of the variant. Under each parameter either give value or leave the field blank. Click on Save (CtrlS)+ button from the standard toolbar.

This way multiple variants can be directly added to Variants list.

Variants from Test Data Containers:

Prerequisite for this option is that Test Data Containers should be maintained under Configuration tab. To create variants from the Test Data containers, click on the wizard icon (Variant Maintenance Assistant) under the Variants tab.

The Variant Maintenance Assistant window appears. The left half of the screen displays the variants belonging to a test data container. The right half of the screen displays the variants belonging to the test configuration. Scrolling between the multiple variants of Test Data is available. Select the variant from the Test Data & click on Attach as variant button. The variant will be copied to Test Configuration side.

Linking multiple fields in Test Configuration column to a single field of Test Data variant: Select a field belonging to a test data container. Select a field belonging to the test configuration. Choose Insert in column. All the empty fields in the column are filled. The value in a field is determined by the following syntax:

Click on Save (CtrlS)+ icon from the standard toolbar. And Test Configuration is now ready to execute or to link to TestWorkbench depending on the variant selected. </li> </ul>

eCATT Scripts Management Via Test Workbench (PART V)

Sapna Modi — Thu, 13 Apr 2006 18:18:02 GMT

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 Part III, SAPGUI recording mode of recording is explained in detail. In Part IV, the parameterization, creation of Test Configuration,Test Data Container, System Data Container are explained in detail. In Part V, the management of eCATT Scripts via Testworkbench will be explained. In the subsequent parts eCATT Logs & other details of eCATT will be covered.

Why eCATT Scripts Management Is Required By Test Workbench By SCAT:

eCATT scripts can be very well executed via the transaction SECATT by which the scripts are created. In SECATT, the script execution can happen at Test Script (TS) level or Test Configuration (TC) level. At test script level execution, the data may need to be changed depending on the behavior of transaction(s) in the script. This change will override the default recording data of the script. If the script recording is error free then change of the data at TS level is not recommended. Hence execution of the script via TC is adapted. In TC, the data is changed at variant level, which are picked from Test Data (TD) Container. Changing data in TD doesnt affect the default recoding time data i.e. ECATTDEFAULT. Now even if the execution can happen via TC, then also clubbing of TCs, which are related depending on a series of functionality or the function module or location against which the test case is being executed, is not possible via SECATT transaction.
Moreover one has to maintain the log IDs of the scripts being executed via SECATT. As script executes multiple times, the logs are stored against that script. So which log has generated during the final regression testing time is difficult to make out.
Hence for the Regression Test, the requirement is that somewhere the log IDs should be present along with the scripts, which are as a result of the test carried out during final testing. These log IDs will be available for future use. So all the requirements of grouping the scripts on some defined conditions, availability of log IDs for future usage will be fulfilled by Test Workbench SCAT Transaction.

How Scripts Can Be Managed In Test Workbench:

Test cases can be managed in test workbench via Test Catalog, Test Plans & Test Packages. Also with the Test Workbench test status can be analyzed. Test status is in terms of traffic lights for eCATT logs.
Test Catalog - A Test Catalog is a set of test cases in a hierarchical hypertext structure. To be able to use the test catalog to generate test plans, one must put it in the SAP Application hierarchy. One can create test plans across several test catalogs via the SAP application hierarchy. This procedure allows creating a lot of small test catalogs, which are easier to maintain than one large test catalog.
Test Plan - A test plan is a set of test cases, which must be tested, in a particular period for a particular purpose. The relevant test cases can be divided among several test catalogs.
Test Package - A test package is a person and period-oriented view of a test plan. It contains all tests, which a tester is to perform in a specified period.
After a test, the tester sets the test case status, e.g. Pass or Fail. one can get an overview of the status of all test cases of a test plan with Status analyses.

Creation Of Test Catalogs:

Transaction SCAT or Tools->ABAP Workbench->Test->Test Workbench->Test Organizer->Manage Test Catalog.
Click on menu Environment->Manage Test Catalog.
Click on Create (F5) icon from the application toolbar.
Test Catalog Information window appears.
Give the name of System Data and Target System in the eCATT section. System Data container should contain the RFC for the Target System on which the script will execute.
In Test Catalog Header Data section give Title. The title is the name of the catalog by which it will be referred in the Test Plans.
In the Responsibility section, Name contains the logged in user name by default.
Click on Save (Ctrl+S) from the standard toolbar.
The Test Catalog is created. Now the Test Configurations need to be added to this test catalog.
Select the Test Catalog created in step 8 and click on Change (F6) icon from the application toolbar.
Under the Structure, name of test catalog will appear.
Select Test Catalog name and click on the button As Subnode (F5) from the application toolbar.
Insert Nodes window appears. Here we are adding the Test Configurations to the test catalog. So select the second radio button of Test Case. Give the value from the dropdown list as E eCATT Test Configuration.
In the Test Case Key, click on F4 help. Select the Test Configurations from the system. As the grouping of the scripts is on the basis of the location against which the test is carried out, so all the scripts, which will be specific to this particular location, should be selected.
In the Variant Selection, select the Special Variant radio button. Click on F4. Now in the list shown by system will show only the common variant to all the select Test Cases from step 13. If in case the scripts are selected which dont have common variant names then only the variants of first test case appears in the list.
- Without Variants  Only with ECATTDEFAULT.
- All Variants Including Default Variant  All the variants including ECATTDEFAULT variant.
- All Variants Excluding Default Variant  All the variants excluding ECATTDEFAULT variant.
- Special Variants  Only for the selected variants from the list, which are common to all the selected test cases.
Select the variant for the location against which testing is carried out and press enter. All the selected scripts along with the variant name will appear under the Test Catalog name.
Click on Save (Ctrl+S) button from the standard toolbar..
In order to use the test catalog in Test Plans, test catalog must be present in SAP Application Hierarchy. To achieve this, click on button Library (Ctrl+F12) from the application toolbar or click on GOTO menu -> Library.
Select path as follows => Test Organizer Library -> Application Components -> BC -> BC-TWB Test Workbench -> BC-TWB-ORG Test Organizer -> BC-TWB-ORG-CTL Test Catalog. With the Test Catalog selected, click on Nodes (Insert Nodes F5) button from the application toolbar.
One small window of Create Link appears. Click on (Find) Test Catalog button. Give the name of Test Catalog created in step 16 in the Description field. The name will appear in the search help output window. Select the catalog and press enter.
One Information popup appears  The two structures are from different mySAP components. Press Enter. The catalog will be added under the Test Catalog node.
Click on Save button from the standard toolbar. Now the catalog is present in the application hierarchy.
This way multiple test catalogs can be prepared depending on some defined conditions like different locations against which the testing will be carried out. These test catalogs then can be used for the preparation of test plans.

Creation Of Test Plans:

Transaction SCAT.
Click on menu Environment->Manage Test Plans.
Click on the Create (F5) icon from the application toolbar.
Create Test Plan window appears. In the Template, select Application Component Hierarchy. Under the Test Plan & Header Data section, give the Test Plan Title. With the Test Plan Title, the plan will be referred. In the eCATT section, give the name of System Data Container & Target system on which the scripts will execute. Click on Enter.
The system will take to Crate Test Plan screen where the Test Organizer Library is displayed. Here from this SAP Application Hierarchy, select the test catalog. This test catalog is the one whose scripts will be pulled in the test plan and then subsequently in test package of that plan. Scripts from multiple test catalogs can be taken. Select path as follows => Test Organizer Library -> Application Components -> BC -> BC-TWB Test Workbench -> BC-TWB-ORG Test Organizer -> BC-TWB-ORG-CTL Test Catalog. Select the scripts from single or multiple Test Catalogs as per the requirement.
Click on Generate (F8) button from the application toolbar. After the plan is generated save it.
Test Plan is ready now. One can prepare the Packages from this plan by some defined conditions like scripts of foreground execution, background execution or different tester or different target systems at execution time.

Creation Of Test Package:

Select the test plan created in step 6 above. Click on Test Packages (Ctrl+F9) button from the application toolbar.
Test Organizer  Test Package Management screen comes. Click on Create Test Package button.
It will display all test catalogs under that test plan. Select the scripts from the required test catalogs depending on the condition on which that package is planned. After selecting the scripts, click on Generate (F8) button. The Create Test Package window for title appears. Give the name of the package in the title. By this name the package will be referred always. Click on Enter.
Once the package is prepared, select the package name and click on Status button for refresh. Once the refresh is done, the right panel will show the number of scripts against that package under the Error/No Result/Ok columns.
The package is also now ready. This way multiple packages can be prepared which will involve all the scripts of the plan in totality.

Execution Of Test Cases Series Via Test Workbench:

Test Cases can be executed via different ways at different levels in test workbench system. Test Cases can be executed at Test Catalogs level/Test Plan level or even at Test Package level.
The scenario depicted here is by creating a pool of test cases in Test Catalogs. Then from those test catalogs preparing Test Plans depending on some defined conditions. From these plans again preparing Test Packages. And finally executing these Test Packages which give the transparent picture of how the testing was planned and carried out.
So transaction SCAT.
Click on menu Environment->Manage Test Plans.
Select the Test Plan, which needs to be executed.
Click on Test Packages (Ctrl+F9) button from the application toolbar.
Select the package. Before the execution, the status in traffic light for each of the script will be untested.
For the mass execution of the complete package, select the package. Then click on Automatic Test button from the application toolbar.
Test Case Selection window appears. If in case all the scripts need not to be executed at a given time, then select the required once. By default all the scripts under the package are selected for execution. Click on Enter.
One window with title Start Options (eCATT Mass Start) will appear. Select the following options 
- Error Behavior - S No termination, continue with next script.
- System Data  Name of the system data container, which contains the Target System.
- Target System  Name of the server on which the execution will happen.
- Select the Log Display check box.
- Select the Status In TWB check box.
- In TCD section of window, select N  Process in background, synchronous local.
- 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.
On execute button click on Start Options window, the system prompts for login & password window of Target System. Give the login details and execution of scripts will start in series.
Once the execution is completed, the logs are taken back to test workbench and the status of traffic light will either change to green for success or red for error.

eCATT Scripts Creation - SAPGUI Mode (PART III)

Sapna Modi — Mon, 10 Apr 2006 19:01:21 GMT

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 doesnt 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 Record SAP GUI Command, 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 Record SAP GUI Command. Click on Yes for recording.
One window with title Recording Running 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  Name of the system data container, which contains the Target System.
- Target System  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.

eCATT Scripts Creation TCD Mode (PART II)

Sapna Modi — Mon, 10 Apr 2006 19:00:27 GMT

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 will be explained in detail. In the subsequent Parts, SAPGUI recording mode of recording and other details of eCATT will be covered.

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 TCD 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 doesnt have any activex controls then TCD recording mode can be used.
If the transaction has activex controls and these controls are NOT mandatory for the functionality of the transaction, then also TCD mode can be used as recording mode.

Key Features Of TCD Recording Mode:

It is suitable for the transactions not having activex controls, so it doesnt require any GUI playback mode.
It is very fast.
It has its own built in screen simulation for standard screen elements. Hence while execution, the controls are deactivated and the users actions are simulated by reading the recorded data flow.

Steps For Recording Using TCD 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 test script editor, choose the Editor tab.
Choose Pattern button from the application toolbar.
The Insert Statement dialog box appears.
From the Command Dropdown List, choose TCD (Record).
In the Transaction field, enter the transaction code of the transaction that you want to record, and choose Enter.
In the Interface field, a system-generated name appears.
Accept the system-generated name or edit it.
If there is a system data container, you can enter the target system in the Target System field.
Choose Enter.
The transaction starts recording.
Work through the transaction as normal.
When you leave the transaction, the system returns you to the script editor with the Recording ended dialog box.
Choose Yes to transfer the data.
A TCD command and its associated Command Interface will be inserted in test script editor of SECATT.

Execution of Recorded TCD 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 with value S No termination, continue with next script.
- System Data  Name of the system data container, which contains the Target System.
- Target System  Name of the server on which the execution will happen.
- Select the Log Display check box.
- In TCD section of window, select N  Process in background, synchronous local.
- Click on Execute button.
Transaction will start executing, which appears at the bottom.
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.

sapna.modi

Whats in the Name

SAP Solution Manager 4.0 - Project Preparation Phase (Part II)

What is SAP Solution Manager:

Latest Version:

Features of SAP Solution Manager:

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

What is Project Preparation Phase:

SAP GUI based Transaction for Project Preparation Phase:

Web based Wizard’s Transaction for Project Preparation Phase:

Menu Path for Project Preparation Phase:

Prerequisite of using Project Preparation in Solution Manager:

Types of SAP Projects in Solution Manager:

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

Project Preparation in Detail:

SAP Solution Manager 4.0 Project Management - Business Blueprint Phase (Part III)

What is SAP Solution Manager:

Latest Version:

Features of SAP Solution Manager:

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

What is Business Blueprint Phase:

Transaction for Business Blueprint Phase:

Menu Path for Business Blueprint Phase:

Prerequisite of using Business Blueprint in Solution Manager:

Key Features of Business Blueprint Phase in Solution Manager:

Business Blueprint in Detail:

Generating Business Blueprint Document:

Generating Microsoft Project:

Checkpoints in eCATT (Part IX)

What are Checkpoints in Testing:

Why are Checkpoints needed in Automated Testing:

Advantages of Checkpoints in Automation:

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

What are commands in eCATT for Checkpoints:

Details about checkpoint commands in eCATT:

SAP Solution Manager - Roadmaps Introduction (Part I)

Workflows for Dummies - Workflow Builder(Part II)

What are SAP Business Workflows:

What is Workflow Builder:

Transaction for Workflow Builder:

Menu path for Workflow Builder:

Features of Workflow Builder:

Workflow Builder Details:

SAP Solution Manager - A Concern Area

What is SAP Solution Manager:

Latest Version:

Features of SAP Solution Manager:

Template Project Type:

SOLAR02 Transaction code: Configuration:

Test Management:

Helpdesk Application:

Common concerns:

Workflows for Dummies - Introduction(Part I)

What are SAP Business Workflows:

Why Workflows:

Features of Workflows:

Prerequisites of using Workflows:

Transactions Involved:

Workflow Terminologies:

Workflow Binding Concept:

Workflow Builder in Brief:

Symbol

Step Name

Function

How Workflow can be Started/Triggered:

eCATT Tips Of Recording, Testing & Links (PART VIII)

Tips To Be Followed Before or During Recording:

SAPGUI & TCD Recording Modes:

eCATT Commands:

Key Points Can Be Followed For Successful Testing Via eCATT:

eCATT Weblog Links From SDN:

eCATT Links From SAP Help:

eCATT Links From SAP Service Marketplace:

Useful eCATT Links From SDN Forum:

eCATT Scripts Creation Non-User Interface Mode & Rename, Copy, Delete, Upload, Download eCATT Objects(PART VII)

Key Features Of Non-User Interface Recording Mode:

Steps For Recording Using Non-User Interface Recording Mode:

How To Copy, Rename & Delete eCATT Objects:

How To Download eCATT Objects:

How To Upload eCATT Objects:

Whats in the Name

eCATT Scripts Creation TCD Mode (PART II)