Work flow in Credit Management

Hello SAP Gurus,
we need to trigger a mail to the finance manager whenever the credit limit of the sales order exceeds
Please suggest us the business object which can be used for credit management for sales orders when credit limit is exceeded.

Hi
Check the following link;
http://wiki.sdn.sap.com/wiki/display/ESpackages/CreditManagementBusiness+Objects
Regards
Chandrasekhar

Similar Messages

Regarding work flow for credit block release in sales order

Dear Experts,
Kindly help me with work flow-
my scenario is if customers credit limit of 5000$ exceeds in sales order it should be blocked and notification should go to authorize person through simple mail to release this block.
for this i have done settings in out control i have used output type krml and determined partner as employee responsible to release block in customer master but mail is not triggered to authorized person for credit block and how i can create work flow for this so that authorized person should get notify for credit block as well he releases block also.
Regards
Supriya

Dear supriyaparimal,
Please find the below points to fix your issue.
1. Configure the out put determination by using the condition type KRML.(Hope oyu have done it already).
2.Maintain the condition records in VV11 for condition type "KRML"
3.Then select the condition record and click the communication tab .
4. If you want to give any information you can use "Note for recipient".
5. If the information has to be sent to relevant person you recipient name in the recipient column.
Save the documnet.
If you raise the sales order and if it is blocked then system automatically send the information to respective person.
You can get this in formation in ""SBWP" transaction code.
Check the in box, the information what you have mentioned in the condition records will be appeared.
Please let me know if you have any clarifications
Thanks&Regards
raghu.k

Work flows In Travel Management

Hi! Folks
I need help to set up workflow in travel management(including OM set up).
We don't have HR implemented and currently Travel Management is implemented through FI (Now we want to Automate this TR process).we are in ECC 5.
I am new to this area So can any body send me
the relevant documents/step by step guides etc.etc.
to my ID:[email protected]
Points will be rewarded
KSP

Hi Rajagopalan,
Thanks a lot for your prompt reply. So sorry for mentioning the incorrect BAPI.
The FM 'Swk_Wi_Container_Read' provides the trip number and employee number as part of container element table field, given the work item as input. There are five rows in container element table, only 3 fields are populated which are extended, note reference and trip. Trip number and employee number are not populated.
Is this because there is some binding problem issue? i have checked the steps and binding, but no luck.
Your inputs are highly appreciated.
Thanks & regards,
Rizwana

Regarding open items in credit management

Dear friends
My query is that is it possible to restrict credit management for credit and debit open items? See i am using oldest open item blocking in my scenario. Now credit and debit amounts are both considered as open item for credit management. I want only invoice (Debit entry) for consideration and not his payment(credit entry).
Please advise is it possible or not and if possible where to define that???
With regards
Inder

Hi,
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
SM30 - Table/View
V_TVTW Define Distribution Channel
V_TVTA_KKB Assign sales area to credit control area
V_T014 FI - Define Credit Control Area
T001CM - FI Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
Distribution Channel Division Distribution Channel Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
Check Credit
A Credit limit check and warning message
B Credit limit check and error message (no sales order can be created)
C Credit limit check and delivery block (block delivery if hit credit limit)
Options B and C -> used for checking open order values (when you create/change the sales order)
D Automatic credit control with open order values
More control in transaction OVA8 - Automatic credit control
You check for open orders and deliveries, or just open deliveries.
or open order values with other options
Credit group
Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D automatic credit check).
SAP default credit groups
01 credit group for sales order
02 credit group for delivery
03 credit group for goods issue
OVA8 - Automatic credit control Double click on the line items
You can have the followings credit limit check :-
Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.
Max open items %
The customer balance must not exceed a certain percentage.
Oldest open items
If you dont want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
Days oldest item
No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system only reblocks the sales document if the new order quantity is above a certain % amount.
Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document day is in April then the credit limit is zero.
You can use the NextReview date and Number of days fields and combined it with the Last int.review field in customer credit master Status view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
regards,
Siddharth.

Work flow of sd mm & fico with transaction codes

hai friends
could u send me the work flow of "material management" and
"sales & distribution" and "finance management" with their transaction codes ...................plz
kindly send me the me details as soon as possible

HI Yoga.
Flow for SD
ENQUIRY----
>VA11
QUATATION---->VA21
SALES ORDER-->VA01
PICKING----
>VL03
PACKING----
>LT03
DELIVERY----
>VL01
INVOICE----
>VF01
Flow For MM
PURCHASE REQUISATION-----> ME51
REQUEST FOR QUOTATION------> ME41
MAINTENACE OF QUOTATION---->ME47
PRICE COMPARISION----
> ME49
PURCHASE ORDER -
> ME21
GOODS RECEIPT -
> MIGO
INVOICE VERIFICATION -
> MIRO

Credit management....sales area data

hi gurus,,
I have some doubts in Credit Management>
1. In my development Server....Customer Master data > Sales Area Data > Billing Tab Page>CREDIT CONTROL AREA...is not reflecting.
using version 4.7... why is was not reflecting... any configaration settings is required??.
Anybody having configuration material of CREDIT MANAGEMENT and FREE GOODS DETERMINATION..
MAIL ID::: [email protected]

Hi ravi,
Notes on Credit mangement
SAP SD Credit Management
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
SM30 - Table/View
V_TVTW - Define Distribution Channel
V_TVTA_KKB - Assign sales area to credit control area
V_T014 - FI - Define Credit Control Area
T001CM - FI - Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
                  Distribution Channel
                              Division
                  Distribution Channel
                              Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
Check Credit
A - Credit limit check and warning message
B - Credit limit check and error message (no sales order can be created)
C - Credit limit check and delivery block (block delivery if hit credit limit)
Options B and C -> used for checking open order values (when you create/change the sales order)
D - Automatic credit control with open order values
More control in transaction OVA8 - Automatic credit control
You check for open orders and deliveries, or just open deliveries.
or open order values with other options
Credit group
Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents - Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D - automatic credit check).
SAP default credit groups
01 - credit group for sales order
02 - credit group for delivery
03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items
You can have the followings credit limit check :-
Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.
Max open items %
The customer balance must not exceed a certain percentage.
Oldest open items
If you don't want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
Days oldest item
No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system only reblocks the sales document if the new order quantity is above a certain % amount.
Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document day is in April then the credit limit is zero.
You can use the "NextReview date" and "Number of days" fields and combined it with the "Last int.review" field in customer credit master "Status" view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
Free goods determination
Free Goods Determination in Sales Order
Free goods has the following limitations:
- Free goods can only be supported on a 1:1 ratio. This means that an order item can lead to a free goods item. Agreements in the following form are not supported: With material 1, material 2 and material 3 are free of charge or If material 1 and material 2 are ordered at the same time, then material 3 is free of charge.
- Free goods are not supported in combinations with material structures (for example, product selection, BOM, variants with BOM explosion).
- Free goods are only supported for sales orders with document category C (for example, not quotations).
- Free goods are not supported for deliveries without reference to a sales order.
- Free goods cannot be used in make-to-order production, third-party order processing and scheduling agreements.
- If you defined a free goods for variants in a generic article (only SAP Retail), you can only process the variants in the purchase order and goods receipt individually (as single articles). In other words, you cannot process them using the generic article matrix.
4.6x
Not all Sales Order can be used for free goods determination. You have to check the SD document category if it does not work. Only category 'C' are supported. Check transaction VOV8.
Assume that you want to configure an inclusive FREE goods routine. Customers must order a minumum quantity of 5 before any free goods can be assign. For every quantity of 3, the customer will be given 1 free goods.
WC07 - Maintain Number Range Intervals
e.g.
No   From number       To number
01    0000010000         0000099999
IMG -> Sales and Distribution -> Basic Functions -> Free Goods ->
Maintain Access Sequences
New Entries
Acsq
NA00
Save
Maintain Condition Types
New Entries
Ctyp   Name             AcSq
FREE Free Goods    NA00
Save
Maintain Pricing Procedures
Procedures
New Entries
Procedure   Description
FREE           Free Goods
Select Procedure FREE then click Control data
Step   Cntr   Ctyp
10       10      FREE
V/N6 - Activate Free Goods Determination
Assign Order Type OR with Document Procedure A with Procedure FREE
VBN1 - Create free goods determination
e.g. FREE inclusive
Material Min qty   From   are free good   Calc Rule   Free Goods
                       5           3                1                      1                1
In this example, if you create a Sales Order for a quantity of 10, SAP will prompt you 7 as the customer order qty and 3 will be free. Customer only pay for the 7 quantity.
Reward points if it helpful

Credit Managment : Profile tab is not visible in BP

Hi All ,
I am working on FSCM credit managment project.
For FSCM credit managment :
I have activated the Badi : activation of SAP credit managment (Interface Set Active and FI_AR_Upadte mode)
1)Set Active
E_ACTIVE_FLAG = 'X' .
E_ERP2005 = 'X'
2)FI_AR_Upadte mode
E_DIRECT_UPDATE = 'X'.
But when I am selecting the Bussiness partner under (SAP credit managment role ).Profile tab is not visible .
Please help me out .
Regards
Rahul

Hi,
Pls check note 956054 and see if you have set up the business partner the correct way. This is the basis.
Rgds,
Richard

MORE OF CREDIT MANAGEMENT

HI,
APART FROM GLEN WILLIAMS CAN ANYONE TELL ME MORE OF CREDIT MANAGEMENT & BILLING ?
RAJARSHI

Hi,
Notes on Credit mangement
SAP SD Credit Management
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
SM30 - Table/View
V_TVTW - Define Distribution Channel
V_TVTA_KKB - Assign sales area to credit control area
V_T014 - FI - Define Credit Control Area
T001CM - FI - Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
Distribution Channel
Division
Distribution Channel
Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
Check Credit
A - Credit limit check and warning message
B - Credit limit check and error message (no sales order can be created)
C - Credit limit check and delivery block (block delivery if hit credit limit)
Options B and C -> used for checking open order values (when you create/change the sales order)
D - Automatic credit control with open order values
More control in transaction OVA8 - Automatic credit control
You check for open orders and deliveries, or just open deliveries.
or open order values with other options
Credit group
Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents - Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D - automatic credit check).
SAP default credit groups
01 - credit group for sales order
02 - credit group for delivery
03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items
You can have the followings credit limit check :-
Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.
Max open items %
The customer balance must not exceed a certain percentage.
Oldest open items
If you don't want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
Days oldest item
No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system only reblocks the sales document if the new order quantity is above a certain % amount.
Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document day is in April then the credit limit is zero.
You can use the "NextReview date" and "Number of days" fields and combined it with the "Last int.review" field in customer credit master "Status" view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
Reward points if it helpful
Sree

Credit Management functionality not working properly during Delivery Execut

Dear All,
Complain from the Client: While creating Delivery documents the system permits the creation of Delivery in some cases when the Customer's Credit Limit is not sufficient to allow Delivery creation.
Findings: After detailed analysis of System Configuration and transactional work flow following significant findings were noted;
1.     Risk Category assignment & Credit Control Area assignment is no disabled at any stage of the business process in discussion.
2.     The Delivery was created with transactional Credit Status "A" (Credit Approved) in cases when it should have been Credit Status "B" (Credit Not Approved) as the customer account did not have sufficient funds to accommodate the delivery.
3.     Following Deliveries on PRD which were reported to have the above mentioned error, i-e, 80207442, 80224422, 80228126, 80230859, 80230863, 80230864, 80231004, after checking the deliveries it was established that system was not changing the Credit Status at Delivery Level to "B" in cases when it should be "B" rather than "A".
4.     The above scenarios have been configured and checked in the QA server, where system reacted as per the standard and no discrepancy was identified.
5.     If the user deleted the delivery which had the bug reported as above, after deletion of that delivery and recreation of the delivery referring to the same Sales Order the system performed correctly unlike in the first case.
thanks
Shahid

Hi,
Please go through the link below, hope this help
http://www.sap-img.com/sap-sd/credit-management.htm

Work flow block in credit memo request

Hi Friends,
I want to create a credit memo. I am creating the credit memo like: Sales order>Invoice>Credit memo request-->credit memo. Now my credit memo request is got created but is assigned with Workflow block at header level, now when I am going back in VA02 and saving it after removing the block at header level, but when I am again checking in VA02/VA03 work flow block is there. Now when I checked that in my workflow , it is in outbox and but I am not able to approve it becoz it is in outbox.
Where it is going for approval , it is only created by me and I don't see any approver field in credit memo request screen.
In the wrokflow outbox am getting that block CMR --as completed and get CMR approver as Error.
How can I remove the workflow block ? Any pointers.
Regards
Ashu
Edited by: ashutosh p on May 20, 2010 1:39 PM

Please check the Workflow log. By default whenever you create or act on any workflow workitem it will appear by default in your SAP Outbox.
Thnaks
Arghadip

Work flow - user is not reciving mail,once CREDIT MEMO submits for approval

Hi All,
Please find the issue as below.
User created the credit memo and submitted for approval. user is expecting the mail in his mail-box, once he submitted the credit memo for approval and same way once approver approved the credit memo, user is expecting mail such that credit memo has been approved.
He informed that previously he is receiving the mails as expected.
Now all of sudden he is not receiving mails.
I have checked work flow mailer, mailer is up and running.
I have gone through the wf_notifications table, here i can see that MAIL_STATUS column having value of "MAIL".
even i have gone through WF_USERS table this particular user is existing and status is "ACTIVE".
But user is not yet received any mail.
Kindly some one help me to sort out this issue.
Thanks in Advance.
Edited by: user627525 on Jun 8, 2011 5:58 AM

Thanks RK for your quick reply.
I was gone through the details you have provided. every thing is fine as expected.
Later i have checked workflow mailer, it was down, due to that notifications are not reached to users/customers.once it is up and running mail notifications sent to respective users successfully.
Many Thanks.

Grant the access rights to manager run the work flow history report without edit /delete rights

I found that only Team Member / Workspace creator / Administrator can run
the work flow history report. However, we have a Purchase Order request
which need ask the supervisor for 1st approval and manager for 2nd approval.
But those managers want to see who prepare the P.O. and supervisor done the
first approval before their 2nd approval. How can I can grant the access
right to the manager to run the work flow history report for this purpose? I
tried grant the role "team member" to those manager, however, it will also
allow them to modify or delete the entry as they are the team member, but we
only want allow those managers can approve the entry and view the work flow
history without other acces such as add/delete/edit to prevent the human
mistake.
Pls advise how can I do this? Thanks!
Regards

Create a new role in teaming can fulfill this requirement. Thanks!
"Joey" wrote in message news:_Cvqo.66903$[email protected]. .
I found that only Team Member / Workspace creator / Administrator can run
the work flow history report. However, we have a Purchase Order request
which need ask the supervisor for 1st approval and manager for 2nd approval.
But those managers want to see who prepare the P.O. and supervisor done the
first approval before their 2nd approval. How can I can grant the access
right to the manager to run the work flow history report for this purpose? I
tried grant the role "team member" to those manager, however, it will also
allow them to modify or delete the entry as they are the team member, but we
only want allow those managers can approve the entry and view the work flow
history without other acces such as add/delete/edit to prevent the human
mistake.
Pls advise how can I do this? Thanks!
Regards

Could you explain the work flow logic in dispute management

Hello,
Could any one explain the the work flow logic in dispute management .
When will the first work flow initiate and who will recive the first notification and what are the action he/she usually perform. How it trigger to next level and what is the events consider for the next work flow trigger.
If some one could share a real work flow example in line with Dispute management will be great...
regards
Sibichan

Dispute management workflow will help to automate business process.
When some action or information is expected form individual or department then
Workflow can be triggered on editing some field in dispute case and workitem is send
to individual or group, So that they can respond to it.
We can use function email notifications to speed up the process.
Based on organizational needs triggering events can vary.
Regards,
Raju

Work Flow Management in SAP EHS

Dear Friends
Are there general requirements of work flow management in SAP EHS. Actually, i dont have much idea on this. Please guide me.
As far as my understanding goes, i know one process where EHS manager/officer can give approval for work permit in PM. Here we might need work flow management.
Are there such cases/scenarios where we need work flow management in EHS. Please let me know.
Regards
Vikram Sethi

Hi,
Work flow managment shall be considered part of Product life cycle Management, the important steps are are: Design, sales & production and service: which may be disaggregated into Product idea, start of production, end of production and discontinuation of product.
In the work flow management, phases involved are product design phase, production phase, sales & transportation, service phase. Each phase has its importance starting from design to reduce waste generation to disposal mode of waste generates from the disappearence of the product.
I hope the above info is useful to good extent and to ahead further.
regards,
mahesh

Work flow management - SD

Dear Friends,
1.Can somebody throw light on Work Flow management?
2.How is SD integrated with Work flow and what are the business processes that needs work flow in SD?
3.Is it like a Work flow consultant is required to handle this or can we handle the workflow from SD end itself?
Thanks
Isaac

Hi,
Few points on workflow was prepared by me and screen shots are not there. You can refer
ALE, EDI and IDOC Technologies for SAP by Arvind Nagpal
For further detail.
if the requirment is minimal then SD consultant can handle otherwise Workflow consultant is required.
Introduction
The workflow management system provides procedural automation of steps in business process. A business process can consist of several steps. Historically the tasks have been coordinated manually or by some means of communication (sticky note, email, shouting and so on). The common problem in these approaches is in efficiency; each lacks a way to trace where a task is, who executed (or executing) it, and how much time is required.
In contrast, workflow management system ensures that the right work is sent to the right person at the right time in the right sequence with the right information. The ALE/EDI interface mainly uses workflow for exception (or error) handling.
Application of Workflow in ALE/EDI
Error Notification
Error notification is the primary use of workflow. When exceptions are raised in the outbound and inbound process workflow is started and handled as shown in the below flow diagram.
Active Monitoring
Active monitoring allows you to specify threshold values for the state of the system. If the system crosses the threshold limit, a person responsible for the system problem can be notified. For example you can have some one notified when the number of failed invoice IDOCS in the system exceeds 50.
Rule Based Inbound Flow
This application of workflow in ALE/EDI does not under the category of error handling. You can set up workflow to handle processing of an inbound IDOC. Normally, an inbound IDOC starts a function module that invokes the posting program to create an application document from the IDOC.
In contrast, if you use a workflow, you can set up to do whatever is needed for your business process. SAP doesnu2019t provide standard workflows for the inbound ALE/EDI process, but you can develop your own workflows and tie them to the ALE/EDI process.
For example an incoming order change IDOC can be routed via workflow to a person for review. If the change requested are acceptable the IDOC can be posted.
The Architecture of ALE/EDI Workflow
The components used in ALE/EDI workflow fall into two categories:-
u2022     PD-ORG (organizational) object
u2022     Workflow object
You can view and maintain these components by using the T-code SWLD (Area Menu for workflow).
                         PD-ORG
                                                                                Workflow
PD Organizational Objects
PD ORG object is used to represent the companyu2019s organizational structure in SAP. The following are the PD ORG objects.
u2022     Organizational Units (O)
An Organizational Unit can represent a department, physical location, division or subsidiary.
u2022     JOBS(C)
A job involves performing one or more business tasks. For example, sales order clerk, secretary and manager. Although it is possible to assign individual task directly to a position, it is advisable to group tasks together in a job and to assign the job to the position.
u2022     Position(S)
A position in a company represents his or her rank. If an employee is promoted, that person leaves his or her current position and is assigned to another position. For example, sales order clerk plant 1000, secretary of company code 1000 and manager of accounts.
u2022     Users (US)
A user is a person who has been granted access to the SAP system to use various functions.
All the above mentioned PD ORG objects can be created, changed and displayed by using following T-codes.
u2022     PPOCE  Create mode.
u2022     PPOME  Change mode.
u2022     PPOSE  Display mode.
Screen shot1.
Work Flow Objects
Business objects
A business object represents a business entity that has a definite state and various properties. You can carry out various functions on the object. A business object encapsulates the entire functionality of an object. A business object is given a name in SAP.
For instance, a standard material is assigned the name BUS1001006; it has properties such as material number, description, and material type. These properties are represented using attributes of the business object. The various operations that can be carried out on an object are implemented with methods. For example, if you want to create a material, you can call that business objects create method. An object also has different states. It exposes its various states by publishing events. For example, the material object has created event that is published whenever a new material is created.
The T-code for Business Objects is SW01.
Screen shot2.
Tasks (T or TS)
A task defines a piece of work that can be executed and tracked in the system. Technically, a task points to a method of an object as shown in the below screen shot. In addition, a task defines the text the purpose of the task, the triggering event based on which the task is started, the terminating event that marks the completion of the task, and a role that contains the rules to identify the person who is responsible for executing the task. A task can be started in response to an event triggered in the system. Tasks are categorized as
u2022     Standard Task
Standard Task is provided by SAP and is client independent.
u2022     Customer Task
Customer Task is client dependent and is developed by customers.
The T-code for Tasks is PFTC.
Screen shot3.
Roles
Roles are workflow objects used to determine the person responsible for carrying out a specific task. Each task has a role assigned to it.
The T-code for Roles is PFAC.
Screen shot4.
Work item
A work item represents an instance of a task that needs to be executed. The work item can have various states that govern the operations allowed. The following table describes the various states of a work item and its effect on usability.
Status      Description
Ready     A work item is created and is visible to all selected agents.
Reserved      A work item has been reserved by a user and disappears from all the inbox of other selected users.
In process     A work item is being worked on and can be seen in the inbox of the user who started working on it.
Completed      A work item is complete and cannot be seen in the inbox of any user
The SAP INBOX
The SAP inbox is an interface to manage workflow items and SAP office documents. The below screen shot shows a list of work items in a useru2019s inbox. The SAP inbox contains separate buckets for office documents and workflow items. Office documents are email documents and workflow items are work items. You can display and execute the work items from the inbox. The inbox is highly configurable.
Screen shot5.
Error Notification Process
The error notification process comprises the following steps:-
u2022     Determining the task to be started.
u2022     Routing the error to a responsible agent as a work item.
u2022     Processing of the work item by the responsible agent.
Possible Agents versus Selected Agents versus Actual Agents
A task has three types of agents based on rights to execute:
u2022     Possible agents
Possible agents represent persons who can execute a task. Not all the possible agents get a work item when a task is started.
Possible agents are configured in the system by assigning a task to
several HR objects (job, position, Org unit). A task can be set to
General task, which means that it can be executed by any one.
u2022     Selected agents
Selected agents are the users who get a work item in their inbox. They
are determined by role resolution logic. Selected agents must be a
subset of possible agents. If the selected agent is not found, the work
item is sent to all possible agents. The selected agents are configured
in the partner profile and the IDOC administrator in T-code WE46.
u2022     Actual agents
The actual agent is the person who executes the work item from the inbox. A work item can have several selected agents but only one actual agent. When a selected agent executes a work item, the actual agent for the work item is established, and the work item immediately disappears from the inbox of other selected agents. However, if an actual agent realizes that he or she cannot resolve the problem, the user can replace the work item, causing it to reappear in the selected agentu2019s inboxes.
Level of Agents in ALE/EDI process
Level 1
If a partner profile is located for the problem, the organizational object specified at the message level (inbound or outbound) in the partner profile is notified.
Level 2
If level 1 is cannot be identified because of the problem locating the record, the level 2 organizational object specified in the General View of the Partner profile is read.
Level 3
If neither level 1 nor level 2 can be identified, the system reads the EDICONFIG table for IDOC administrator and sends a notification.
Processing by the Responsible Agent
u2022     The steps necessary to fix an error for which a work item is generated are as follows.
u2022     Execute work item to display the error. Examples of errors include problems in the control record, errors in IDOC data, and incorrect configuration.
u2022     The cause of the problem can usually be determined from the error message. If applicable, additional error information is also available for certain type of errors (for example application errors).
u2022     After the cause of the problem has been determined, it must be fixed outside workflow (or in some cases, within workflow). The recovery procedure depends on the nature of the problem.
-     If the error is in the IDOC data, the IDOC can be edited and then reprocessed from workflow.
-     If the error requires restarting the process from the beginning, the IDOC has to be marked for deletion to stop it from further processing and to clear the work item from the inbox.
-     If the error involves an IDOC that has not been created yet, the work item merely informs the person about the error.
Important T-codes
T-code      Description
SWLD      Area menu for work flow
SBWP or SO01     Sap inbox
SW01     Business object builder
PFTC      Task/ Task Groups
PFAC      Roles
SWU3     Maintain standard settings for SAP business workflow
PPOM     To change ORG structure
SWUS      Start workflow(Test Environment)
SWI15
SWI13     Task profile for user
Books Referred
ALE, EDI and IDOC Technologies for SAP by Arvind Nagpal

Work flow in Credit Management

Similar Messages

Maybe you are looking for