Tuesday, January 31, 2012
| SWI1 | — | Selection report for workflows |
| SWI11 | — | Where-Used List for Tasks |
| SWI13 | — | Task Profile |
| SWI14 | — | Workflows for Object Type |
| SWI1_COND | — | Check Conditions for Work Items |
| SWI1_RULE | — | Execute Rules for Work Items |
| SWI2_ADM1 | — | Work Items Without Agents |
| SWI2_ADM2 | — | Work Items with Deleted Users |
| SWI2_DEAD | — | Work Items with Monitored Deadlines |
| SWI2_DIAG | — | Diagnosis of Workflows with Errors |
| SWI2_DURA | — | Work Items by Processing Duration |
| SWI2_FREQ | — | Work Items per Task |
| SWI3 | — | Workflow Outbox |
| SWI30 | — | Unlock Workflows |
| SWI5 | — | Workload Analysis |
| SWI5N | — | Workload Analysis |
| SWI6 | — | Workflows for Object |
| SWIA | — | WI Administration Report |
| SWIE | — | Unlock Work Item |
| SWDA | — | Alphanumeric Workflow Builder |
| SWDB | — | Create workflow |
| SWDC | — | Workflow Definition: Administration |
| SWDC_DEFINITION | — | Workflow Builder Administration |
| SWDC_INTERNAL | — | Workflow Definition: Administration |
| SWDC_RUNTIME | — | Maintain Administrator for Runtime |
| SWDD | — | Workflow Builder |
| SWDD_CONFIG | — | Workflow Configuration |
| SWDI | — | Workflow Builder (Selection) |
| SWDM | — | Business Workflow Explorer |
| SWDN | — | Number Range Maint.: SWD_WDID |
| SWDP | — | Show Graphical Workflow Log |
| SWDS | — | Workflow Builder (Selection) |
Monday, January 30, 2012
| Work item related function modules | |
| SWW_WI_AGENTS_CHANGE | Change Agents of Work Item |
| SWW_WI_BACK | Agent Returns Work Item |
| SWW_WI_DEADLINES_CHANGE | Change Deadline Attributes of Work Item (Types W, E, F, and B) |
| SWW_WI_DEADLINES_READ | Read Deadline Data of Work Item |
| SWW_WI_DELETE | Internal: Work Item Deletion -> SAP_WAPI_WORKITEM_DELETE |
| SWW_WI_DISABLE | Lock Work Item Against Execution |
| SWW_WI_ENABLE | Remove Lock Against Execution for Work Item |
| SWW_WI_EXECUTE_NEW | |
| SWW_WI_FEASIBLE_METHODS_GET | Test for Which FMs Are Allowed for the WI Depending on Status and Type |
| SWW_WI_FORWARD | Forward Work Item (All Types) |
| SWW_WI_LANGUAGE_CHANGE | Change Language of Work Item (Types W, F, and B) |
| SWW_WI_PRIORITY_CHANGE | Change Priority of Work Item (Types W, F, and B) |
| SWW_WI_REJECT | Reject Work Item (Only Type W) |
| SWW_WI_RESUBMISSION_END | End Resubmission of Work Item |
| SWW_WI_RESUBMIT | |
| SWW_WI_RETURN_READ | Read Return Data of Work Item |
| SWW_WI_SELECT | Agent Selects Work Item |
| SWW_WI_STATUS_SET_READY | Deadline: Activate Work Item (Types W, E, F, and B) |
| SWW_WI_TEXTS_CHANGE | Change Deadline/Notification Texts of Work Item (Types W, E, B, and F) |
| Workflow interfaces: Runtime | |
| SAP_WAPI_ASYNC_RULE_COMPLETE | |
| SAP_WAPI_CREATE_EVENT | Workflow interfaces: Create event |
| SAP_WAPI_CREATE_EVENT_EXTENDED | |
| SAP_WAPI_DECISION_COMPLETE | |
| SAP_WAPI_DECISION_READ | |
| SAP_WAPI_GET_EXCLUDED_FUNCTION | |
| SAP_WAPI_GET_PROPERTY | |
| SAP_WAPI_GET_TASK_CNT_SCHEMA | |
| SAP_WAPI_GET_WI_CNT_SCHEMA | |
| SAP_WAPI_READ_CONTAINER | Workflow Interfaces: Read Container |
| SAP_WAPI_SET_ERROR | |
| SAP_WAPI_SET_MESSAGE | |
| SAP_WAPI_START_WORKFLOW | Workflow interfaces: Start workflow |
| SAP_WAPI_WORKITEM_COMPLETE | |
| SAP_WAPI_WORKITEM_CONFIRM | |
| SAP_WAPI_WORKITEM_DELETE | |
| SAP_WAPI_WRITE_CONTAINER | Workflow Interfaces: Write Container |
Features of Faceless Components
- Web Dynpro components without graphical elements – that is, without windows or views.
- Only component controller included; optionally, custom controllers can be added.
- They are designed exclusively for receiving and structuring data.
- By declaring a component usage you embed them into other components; they then supply the embedding component with the required data.
Sunday, January 29, 2012
Definition:
Web Dynpro is the SAP NetWeaver programming model for user interfaces (UIs).
The Web Dynpro model is based on the Model View Controller paradigm.
Structure:
- Metamodel Concept
- Graphical Development Tools
- Separation of Business and Application Logic
- Conversion of the Model-View-Controller Programming Model
MVC Prgramming Model:
Every Web Dynpro application is structured according to the Model View Controller programming model:
- The model forms the interface to the back end system and thus enables the Web Dynpro application access to data.
- The view is responsible for the representation of the data in the browser.
- The controller lies between the view and the model. The controller formats the model data to be displayed in the view, processes the user entries made by the user, and returns them to the model.
*NOTE: If picture is not visible, please click on the picture and view in large.
- WDA - Web Dynpro ABAP applications
- WDJ - Web Dynpro Java applications
- BSP - Buiness Server Pages applications
- ITS - HTML pages
- SAP GUI - Classic dynpro programming model of SAP
- SAP Interactive forms and print forms by Adobe
Purpose:
Web Dynpro ABAP (WDA) is the main SAP standard UI technology for developing Web application UIs in the ABAP environment. It consists of a runtime environment and a graphical development environment with special tools that are completely integrated into the ABAP development environment - the ABAP Workbench (transaction SE80).
History:
WDA has been available since October 2005 (SAP NetWeaver 7.0 (2004s) – Web Application Server 7.0) and is widely used by the SAP Business Suite and will continue to be the UI technology of choice for mainstream Business Suite applications (ERP, PLM, SCM, SRM, FIM).
FPM is available since WDA 7.00 SP13 and is used by all ERP projects using WDA as of SAP EhP4 for SAP ERP 6.0.
Advantages:
- The use of declarative and graphical tools significantly reduces the implementation effort
- Web Dynpro supports a structured design process
- Strict separation between layout and business data
- Reuse and better maintainability by using components
- The layout and navigation is easily changed using the Web Dynpro tools
- Stateful applications are supported – that is, if the page is changed and the required data remains intact so that you can access it at any time throughout the entire application context.
- Note that stateless applications are not possible.
- Automatic data transport using data binding
- Automatic input check
- Automatic operation of the Web Dynpro application using the keyboard
- User interface accessibility is supported
- Full integration in the reliable ABAP development environment
Tuesday, January 24, 2012
Step by step how to download & install SAP NETWEAVER 7.01 ABAP TRIAL Version.
Saturday, January 21, 2012
Like in ABAP, While designing and developing web dynpro applications, performance is an important factor that needs to be taken into consideration. There are several tools that are available for monitoring or troubleshooting the performance in Web Dynpro ABAP based applications.
- Performance Monitor
- HTTP Watch
- STAD
- SQL Trace Tool
- Runtime Analysis tool
- Memory Snapshot
For more information on how to use Web Dynpro ABAP performance tools, Please check the below SDN link.
Friday, January 20, 2012
These instructions describe the procedure for creating simple roles.
Step 1
Enter a name for the role and choose Create Role.
You should note that the roles supplied by SAP begin with the pr
"SAP_". If you are creating your own user roles, do not use the
namespace.
Step 2
On the next screen, describe the functions that the role is to
include.
Step 3
Assign transactions to the role on the Menu tab page:
- By specifying the transactions directly
- By assigning menu branches from the SAP menu
The menu options selected in this step are displayed in the Session
Manager and on the "SAP Easy Access" logon screen as the User menu
for all users who are assigned to the role.
Step 4
On the Authorizations tab page, choose Change authorizationdata.
Depending on the transactions you have chosen, the system may
display a dialog box that asks you to maintain the organizational
levels. These are authorization fields that occur in several
authorizations at the same time and that can be maintained together,
An example is the company code, which occurs in several
authorization objects. When you assign values to the organizational
levels, you maintain the authorization fields for all authorizations
in the tree display that is displayed at the same time.
The system displays a tree display for all authorizations that are
proposed by SAP for the chosen transactions. The authorizations
already have some values.
- Yellow traffic light icons in the tree display indicate that you
need to manually postprocess authorization values. You enter
these values by clicking a white line next to the name of the
authorization field. Once you have maintained the values, the
authorizations are regarded as having been manually modified.
They are not overwritten if you include additional transactions
and reprocess the authorizations. By clicking the traffic light
icon, you can assign full authorization for the hierarchy level
for all unmaintained fields.
- Red traffic light icons indicate that there are organizational
levels that do not yet have values. You can enter or change
these values by choosing Org. levels....
- If you want additional functions in the tree display, such as to
copy or summarize authorizations, choose Utilities -> Settings
and select the appropriate option.
- Generate an authorization profile for the authorizations by
choosing Generate.
- Enter a name for the authorization profile in the next dialog
box, or use the valid name in the customer namespace that is
proposed.
- Exit the tree display once the profile is generated.
- If you change the menu selection and call up the menu display
for the authorizations again, the system tries to mix the
authorizations for the newly added transactions with the
existing authorizations. This may mean that the traffic light
icons turn yellow, as new incomplete authorizations appear in
the tree display. You need to either manually assign values to
these, or delete them.
- You can delete an authorization by first deactivating it and
then deleting it.
- General authorizations such as spool display and print are not
usually stored with transactions. For this purpose, you can add
authorization templates to the existing data. To do this, choose
Edit -> Insert authorizations -> From template... and choose one
of the templates (for example, SAP_USER_B Basis authorization
for application users or SAP_PRINT Print authorization).
Alternatively, you can create a separate role for these general
authorizations whereby the overview is much clearer.
Step 5
On the Users tab, assign the users to the role.
- The system displays the menu options for the role in the Session
Manager as the user menu for the users assigned.
- Otherwise, the generated authorization profiles are
automatically entered in the user master records when you
perform the User master record comparison . To do this, choose
Compare users on the Users tab page and choose Full comparison.
- If you do not restrict the period of the assignments and use the
default period (current date to 12.31.9999), no further action
is necessary. If you make any other time restrictions, you need
to schedule report PFCG_TIME_DEPENDENCY to run daily. This
report automatically updates the user master records. You must
also schedule this report if you are using Organization
Management.
Caution
Never enter the generated authorization profiles directly in the
user master records, as is the case with authorization profiles that
are created manually. You can only link generated profiles and users
by assigning the corresponding role to the users, and then
performing a user master record comparison. During the comparison of
the user master records, the profiles for the role are entered for
all users of the role.
Step 6
To transport the role to another system, you must enter the role in
a transport request.
- To do this choose Role -> Transport. You can now specify whether
or not the user assignment should also be transported.
- The authorization profiles are transported unless you have
explicitly specified that you do not want to transport the
explicitly specified that you do not want to transport the
profiles.
- After the import into the target system, you have to perform a
complete user master comparison again for hte imported roles.
You can start this comparison manually or use report
PFCG_TIME_DEPENDENCY to execute it automatically, if the report
is scheduled to run periodically in the target system.
Thursday, January 19, 2012
SAP enhancement packages are optional packages that deliver new or improved business functions which can be selectively deployed. Support Packages on the other hand, contain corrections like bug fixes and legal or tax changes and are therefore mandatory. SAP recommends installing enhancement packages when applying a regular support package as a maintenance activity. This combined approach reduces the downtime and manual effort for the whole installation procedure and for the testing efforts.
