HR Tables: SWEHR2/3
ABAP Code user Exit: SWE_EVENT_CREATE
Change Document: SWEC
Status management:
Message Control:
Event Linkage: SWE2
Subtype: Key field cannot be created. Methods and attributes can be created.
Delegate: If you want to change the functionality of a method, define a sub type, redefine the method, delegate the parent business object to child object.
Interface: Interface is a combination of Attributes, Methods and Events, to reduce the redundancy in definition.
IFSAP: Common interface for all BOs. It has following methods
Method: Display
Method: Existence Check
Attribute; ObjectType
Function Module that creates workflow:
SAP_WAPI_START_WORKFLOW:
SAP_WAPI_CREATE_EVENT
SAP_WAPI_WORKITEM_RECIPIENTS
SAP_WAPI_GET_WORKITEM_DETAIL
Requested Start: When this date is met, only then the work item will start execution, or available for taking action (dialog).
Latest Start: When a date mentioned here is met, it can send an email, or can be modeled to do something action.
Requested End: Same as Latest Start
Latest End: Same as Latest Start
Workflow provides numerous advantages to SAP users and consultants:
Tcode SWFVISU
Portal config file for UWL
Containers:
1 Workflow Container:
2 Task Container:
Event Container:
Method Container:
Rule Container: For resolving rules
Business Objects
Key Fields:
Attributes:
Database: Automatically gets populated by system code
Virtual: You determine the content and use SWC_SET_CONTAINER to populate
Methods: Can be created using FM, Transaction, Report, Dialog Module, Other
Synchronous: Finish execution before handling the control back to the task.
Asynchronous: Return the control back immediately. Cannot have export parameters. They depend on events to return results back to the calling program.
Dialog: Something to user
Background: Cannot have messages or exceptions.
Enable event queue. It will ensure that triggered events are received in a phased manner. This needs to be done while providing event linkages.
You may consider using deadline monitoring facilities.
For example:
Requested start, requested end; Latest start or latest end on tasks;
Yes.
A work item created as part of synchronous in locked until end of the method execution. But in asynchronous, work item is locked only until start of method execution.
At least one terminating event is required for a task using Asynchronous task.
SWETYPECOU – Type Linkage Table
SWEINSTCOU – Instance Linkage Table
Example:
BUS7051: Notification,
BUS1001: Material,
BUS2012: Purchase Order,
BUS1065: Employee
Various status of BO
Modeled: Not accessible at runtime
Implemented: Not ready to be used, Internal use only
Released: For customer to use
Obsolete: Don’t use anymore
To change attribute values from methods of a BO
No. What you can do is restart the workflow using SWUE. This will be the same as recreating the workflow because it will start at the point where it has logically been deleted.
You can accomplish this by setting up the work item priority to the highest level.
There are three ways a parallel processing can be implemented:
Dynamic parallel processing using a multi-line container element
Fork (3 out of 5) Work queue
In dynamic processing the type of each entry in the table have to be of same type.
Same task will be processed for each line of the multi-line container. It can be a dialog or background task. Deadline monitoring, binding, agent determination will be same for each work item generated To achieve, go to “Miscellaneous” in the activity, and enter the multi line container element.
we can develop it by giving the code in PBO (process before output) giving table control line = @it will give only 3 lines and we can make 2 lines disable in screen painter options available in table control
Elementary search helps, Collective search help.
Elementary search helps defines a search path where we will define the table from which the data has to be read and the selection criteria. Through import and export parameters. Used when we gets the data rom a single table.
Collective search helps: Combination of elementary search helps. When we need to fetch data based on multiple selection criteria’s. More than one tables are Selection from multiple tables
Difference between Search Helps and Match Codes:
search help: adding f4 functionality is search help(adding help for any topic)
match code: adding search help for the input field is called as math code object.
Mark the priority as ‘1’ Express
The Main Transaction Code Involved in Performance Tuning is SE30-Run Time Analysis and ST05-SQL Tracer.
The Default method of the object type is executed if a space is passed as the method parameter value. You can find the default method by viewing the applicable object using transaction SWO1 and going to menu option “Goto -> Basic Data” and clicking on the Defaults tab. The default method is located in the field “Method”.
SWWDHEX – For deadline monitoring
SWWERRE – For error Monitoring
SWEQSRV – For Event Queue Delivery
Tcode SWEHR2
A background work item (code B) represents tasks that do not require any user interaction.They are controlled and executed automatically by the workflow system, and do not appear in the Business Workplace. However, you may view them using the Work Item Selection Report.
Tables which can be access by all user are client independent (no mandt field in table)
Tables which can be access by some specific user are client dependent (use mandt field in table)
Yes, if we have customised data to store in table , we create a table.
Dialog Work item – W
Background work item
Workflow work item
Work queue work item
Missed deadline work item: When a deadline is missed a missed deadline workitem with the message appears in inbox.
At the time of creating table through, there is a check box for table maintenance allowed.So if you want to activate the table maintenance, just mark this box. Once table gets activated, u can change its contents through SM30 ot Through Table Maintenance.
If started by an event:
If started directly (e.g. with function module SAP_WAPI_START_WORKFLOW; not recommended if it can be avoided):
@Possible Agents:
@Responsible Agents:
The users to whom the work item needs to be sent.
This is set during Step definition. Note that Possible agents are defined during Task definition. (Org Unit, Position, User, Work Center, Role, Rule, Container Element)
Note: The work item recipients is determined by intersection of Possible Agents and Responsible Agents.
@Actual Agents: Actual user who executed the dialog task.
4.Excluded Agents: Users who are not supposed to execute the dialog task (even if they are in possible agents)