Vendor Creation Workflow

[Stephens, Monique S L]

Thanks for the info.  For some reason, I though the IMG configuration only related to changes to vendors, not creation.  If it can be set up for creation as well, that would work great.  It would not prevent users from creating their documents but it would prevent payment.

Monique
________________________________
From: sap-wug-bounces at mit.edu [sap-wug-bounces at mit.edu] On Behalf Of Metin Cansan [mcansan at gmail.com]
Sent: Friday, April 02, 2010 12:21 AM
To: SAP Workflow Users' Group
Subject: Re: Vendor Creation Workflow

Hi Stephens,
We have done a very similar case like yours. As Susan described you can use standard workflow or can create your custom one. One way or another you also need to customize sensitive fields for vendor master from SPRO under;
Financial Accounting-Accounts Receivable and Accounts Payable-Vendor Accounts-Master Data-Preparations for Creating Vendor Master Data-Define Sensitive Fields for Dual Control (Vendors)
When a user creates a vendor master data or changes of it vendor account becomes blocked (only for payment run). If you want to prevent changes during confirmation process you need to use a BTE, SAMPLE_INTERFACE_00001460 until confirmation is done through FK08.
Both LFA1 and LFB1 tables has a field called CONFS (Status of Change Authorization). When there is a change in one of the sensitive fields CONFS is updated with 1 (blocked). This may be a starting point of your workflow.
Cheers,
Melih
On Thu, Apr 1, 2010 at 10:36 PM, Stephens, Monique S L <moniques at bcm.tmc.edu<mailto:moniques at bcm.tmc.edu>> wrote:
I would like to apologize in advance if my question is very basic.  However, I'm not completely familiar with all that SAP has to offer in regards to workflow.  Our technical analyst is more familiar with this aspect.

We have several users that have the ability to create vendors (in Finance and Purchasing).  They have the ability to execute XK01 in order to do this.  We chose not to limit these areas to specific t-codes for Finance and Purchasing.  Now, with some new players, certain fields are not getting populated or not getting populated correctly.  One suggestion was to generate warning messages before saving the vendor.  I have learned that messages are normally ignored unless it is a hard error.  I would prefer to use some sort of workflow that when the vendor is created, it must be approved first.  I know there is an area in the IMG for confirmations but that relates to vendor changes, not creation.

Is there a workflow out there so that when a vendor is created, it would route to a group of people for validation?  We are on ECC 6.0.

Any help and direction would be greatly appreciated.  Thanks.

Monique Stephens
Senior SAP Business Analyst
Baylor College of Medicine
713-798-1349
713-798-1326 (FAX)


_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
http://mailman.mit.edu/mailman/listinfo/sap-wug


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20100402/ea5e3419/attachment.htm