Before any workflow configuration can begin, a set of basic workflow settings must be maintained in the system. If an application is using the workflow module for the first time, these settings will most likely be missing.
The steps to carry out the Basic workflow settings are not in the scope of ALE/EDI settings, but we will have to verify that these settings are maintained. These settings establish a basic infrastructure for the various workflow components.
At the bottom of the screen are two sets of lights: one for the definition components and one for the run time components of workflow. A green light indicates that all the necessary settings are correct. However, a red light does not necessarily mean that workflow will not work; that depends on the item that is not configured correctly.
We can use the Automatic Customizing button, but we must be logged on with the highest authorization level. A Basis person is usually the best person to execute Automatic Customizing because his or her ID should have all possible authorizations.
Developing a Strategy for developing a work flow error notification :
Our objective is to design the organization structure so that the right person is notified and the workload can be managed efficiently. The following steps will help you build a strategy.
1.Develop a list of messages being used in the ALE/EDI process. Identify the tasks associated with each message.
2.Develop a list of users who will handle application errors for each of the identified messages. When selecting a user, make sure that you select a business person and not a technical person, because mostverrors that occur during production are data related, and business people are the best equipped to fixvdata errors.
3.Identify a key technical person who will handle technical problems with the interface. This person becomes the IDoc administrator; he or she does not need detailed functional knowledge.
4.Identify the number of positions that will be required to handle the ALE/EDI process. This number depends on the organization's complexity, the number of EDI messages, and the volume of EDI transactions. It is usually best to define a position for each business function. For example, one position can handle all messages related to the purchasing cycle, and another position can handle messages related to invoicing. Your organization might require one person per message type.
5·Identify backups for each user.
Building an Organizational Unit
We can reach it from the Organizational Plan node on the SAP standard menu or with the following transactions.
Further part will be continued in the next post.
Related Posts
Work item in work flow
SAP WORK ITEM AND INBOX
EDI Tasks and Roles
SAP ABAP BDC PART 1
The steps to carry out the Basic workflow settings are not in the scope of ALE/EDI settings, but we will have to verify that these settings are maintained. These settings establish a basic infrastructure for the various workflow components.
At the bottom of the screen are two sets of lights: one for the definition components and one for the run time components of workflow. A green light indicates that all the necessary settings are correct. However, a red light does not necessarily mean that workflow will not work; that depends on the item that is not configured correctly.
We can use the Automatic Customizing button, but we must be logged on with the highest authorization level. A Basis person is usually the best person to execute Automatic Customizing because his or her ID should have all possible authorizations.
Developing a Strategy for developing a work flow error notification :
Our objective is to design the organization structure so that the right person is notified and the workload can be managed efficiently. The following steps will help you build a strategy.
1.Develop a list of messages being used in the ALE/EDI process. Identify the tasks associated with each message.
2.Develop a list of users who will handle application errors for each of the identified messages. When selecting a user, make sure that you select a business person and not a technical person, because mostverrors that occur during production are data related, and business people are the best equipped to fixvdata errors.
3.Identify a key technical person who will handle technical problems with the interface. This person becomes the IDoc administrator; he or she does not need detailed functional knowledge.
4.Identify the number of positions that will be required to handle the ALE/EDI process. This number depends on the organization's complexity, the number of EDI messages, and the volume of EDI transactions. It is usually best to define a position for each business function. For example, one position can handle all messages related to the purchasing cycle, and another position can handle messages related to invoicing. Your organization might require one person per message type.
5·Identify backups for each user.
Building an Organizational Unit
We can reach it from the Organizational Plan node on the SAP standard menu or with the following transactions.
- PO10 Organizational unit
- PO03 Job
- PO13 Position
- PO01 Workcenter
- PFCT Task catalog
- PP01 General
Further part will be continued in the next post.
Related Posts
Work item in work flow
SAP WORK ITEM AND INBOX
EDI Tasks and Roles
SAP ABAP BDC PART 1
No comments :
Post a Comment