SAP and other folks "Best Practices"

[Dart, Jocelyn]

Folks, 
To be clear - Adobe forms are an alternative UI whose major advantages are a) it works offline as well as online and b) it's familiar and friendly environment for most users.   That's before we get into cool features such as dynamically growing tables, digital signatures and barcodes.
 
Adobe forms don't magically update data or do things with workflow - that still requires development.  
 
However if you use one of the frameworks for Adobe forms, such as PCRs (from ECC 5.0 onwards), or better still the HCM Workforce Process Management (HR Administrative services) of ECC 6.0 Extension set 2 then these frameworks minimize the development effort significantly by providing pre-built applications, BADIs, configuration, and pre-configured workflow tasks.
 
The HR Admin services is particularly impressive in the way it enables update of PA and PT infotypes (including actions) without BDC. 
 
Regards,
Jocelyn 

________________________________

From: sap-wug-bounces at mit.edu on behalf of Edward Diehl
Sent: Fri 7/12/2007 4:21 AM
To: SAP Workflow Users' Group
Subject: RE: SAP and other folks "Best Practices"


Hi Ron,
What transaction will you use for you BDC function?  I can tell you that PA40 will not work because of "dynamic actions" within the transaction.  We are needing a way to update the action infotypes and hope that we will find BAPIs that will do this.
 
Another question, you mention that the services team is involved in updating the SAP system.  I thought the Interactive Forms would "post" automatically.  Is this not the case?  What advantage is the interactive forms solution if it does not do this?
 
We are currently reviewing Interactive Forms for our PA actions workflow.  It sounds like you are thinking about getting away from this mechanism.  Would you mind sharing the reasons for this?  If you don't use Interactive Forms, what will you use?
 
Best wishes,
Ed Diehl
 
 
 
 
 
 


 


________________________________

	From: radkins1 at surewest.net
	To: sap-wug at mit.edu
	Subject: SAP and other folks "Best Practices"
	Date: Tue, 4 Dec 2007 13:23:19 -0800
	
	
	Hello Everyone,

	 

	It has fallen to my team to "Sanity Check" a request from Management to automate some of our workflow processes in the HR Instance.

	Currently, many of our processes have an ADOBE form that is completed for various personnel actions by a manager in MSS.  These are

	routed via workflow to a "One Up" manager for approval and then on to a services team who sort and process these from the various workflow 

	Inboxes.  The new process would remove the services team and populate the data directly into the system by loading the personnel data along with the 

	Changes into the BDC table and then calling the function module to update the SAP Employee data directly in R/3.

	 

	Some of the processes include:

	 

	Salary Changes

	 

	Job Code Changes

	 

	Location Changes

	 

	Title and Position Changes

	 

	Is anyone else going this far with MSS / ESS automations?  It has been suggested that SAP does not recommend that Salary and some personnel changes be 

	Automated and updated without a review layer in between.  Anyone seen any white papers or recommendations stating this?  We are a bit weary of the data integrity

	issues associated with this request and I am very interested in what you folks think.

	 

	Thank you for your time,

	 

	Ron Adkins

	Sr. SAP Analyst

	Nortel 

	 

	 


________________________________

Share life as it happens with the new Windows Live. Share now! <http://www.windowslive.com/share.html?ocid=TXT_TAGLM_Wave2_sharelife_112007>