2. Acclimation Pty Ltd Introduction Acclimation is an Australian consulting services company offering a full range of services for SAP’s NetWeaver solutions. Adobe Partner SAP Partner Acclimation’s Usability and User Productivity team focuses solely on SAP Interactive Forms by Adobe (IFbA), SAP Portal and their related Workflows and Guided Procedures Our Offices: Melbourne Sydney Canberra
3. Acclimation Pty Ltd Forms Project Considerations Where to Start: Which Form Where Where to Start: Typical Use Cases SAP Integration Options Reviewing the Process & Form After the Form – Maintenance Considerations Metrics Business Case Considerations Acclimation’s Roadshow Starter Offerings
4. Where to Start: Which Form Where? Form Based Interaction in Your Organisation: Output Forms Stand Alone Interactive Forms Integrated Interactive Forms Other Considerations: Maximum Exposure High Business Priority High volume Low Levels of Computer Literacy Hybrid Approach
5. Acclimation Pty Ltd Where to Start : Typical Use Cases Paper Forms Repetitive Admin Tasks High error situations or incomplete information issues Data Stewardship beyond the firewall Off-line user base Legal compliance issues Stakeholder Interaction Sustainability Concerns Consistent look and feel with corporate image/branding SAP HR forms and processes provided with ECC 6.0
6. SAP Integration Options Output Form Technologies: IFbA Smart FormsSapscript Stand Alone Interactive Forms Technologies: (IFbA) Email to SAP into Idoc or Workflow Upload to Guided Procedure or WebDynpro Web service submit directly from the form Integrated Interactive Forms Technologies :(IFbA) Web Dynpro (ABAP/JAVA) Guided Procedures Business Process Management
7. Reviewing the Process and Form Consider the dynamic options available Help notes Building relevancy via hide and reveal Pre-population of drop down fields Field level Validation Process Relevancy: The Form’s contents The overall process Fields become active depending on selection start Real-time tips real-time validation
8. After the Form - Maintenance Making Design Changes Making Field Level Changes Making Integration Changes Adding Form Logic Submit
9. Metrics Implementation Timings Technical Skills requiredTechnical Systems requirements Other Considerations: One way v. 2 way – instantaneous connectivity Integration options Document Storage & Management Digital Signatures Approx Project Percentages: Set up 20% Form Design 50% Back-end Integration 30%
10. Business Case Considerations Areas of Value Identified by Acclimation Consultants: User Productivity Reduction in admin Up-skilling staff for business impact actions Improving motivation Leverage SAP System Extend the reach of your ERP Implementation Business Process Automation into SAP Data Integrity Right decision first time Data Stewardship Cost avoidance Compliance with regulatory bodies Legal implications Payback Period often less than one month
Form based interaction in your organisation – Forms are a user interaction methodOutputOne way communication – usually one way communication of specific information to a large audience (e.g. customer statement, invoice, picking slip, etc)Technologies:Interactive Forms by Adobe (IFbA) – of course Smartforms, (newer technology but future is IFbA)SAPScript, (legacy)Stand Alone Interactive FormsForm filling based user interface with minimal online dependancy. Similar to an automated paper based formTechnology: IFbA via:Email to SAP into Idoc or Workflow, etc.Upload into Guided Proceedure or WebDynproWeb service submit directly from formIntegrated Interactive FormsStill form based user interface but with more real time integration with the back endTechnology: IFbA integrated into:WebDynpro (ABAP/JAVA)Guided ProceeduresBPMConsiderations: wide impact v high impact v a combination business impact top management impact
Technologies:Interactive Forms by Adobe (IFbA) – of course Smartforms, (newer technology but future is IFbA)SAPScript, (legacy)Stand Alone Interactive FormsForm filling based user interface with minimal or no online dependancy. Similar to an automated paper based formTechnology: IFbA via:Email to SAP into Idoc or Workflow, etc.Upload into Guided Proceedure or WebDynproWeb service submit directly from formIntegrated Interactive FormsStill form based user interface but with more real time integration with the back endTechnology: IFbA integrated into:WebDynpro (ABAP/JAVA) Webdynpro context mapping which will call the model for form data submissionGuided Proceeduresform data is captured and taken to the next step, or triggers are new processBPM
Options available: Field level help options to guide the user to correct answerBuilding relevancy, one form with more than one output Admin section not revealed until received in-house for further info to be added by account rep etc Drop down fields to ensure data integrity and guide the user for correct answers Ensure mandatory fields have been filled in (offline) Validation to ensure info is correct in back end system (via web services)Process relevancy:Chance to emphasise the opportunity Interactive Forms give to allow the rethinking and redesigning of how information flows into their enterprise information systems. Real potential to open up brand new efficiencies in parts of the business that were previously unreachable due to the simplified yet powerful interface of a pdf (as an interactive form). Look at areas in the business that have maximum exposure, high business priority, low cost but high volume, users with low computer literacy….Effort needs to be put into thinking about the design of the business process, user interaction and reach of the solution. Well designed forms can produce data input scenarios that happen at the source with zero training and high brand visibility / affection (building the brand)?...
Each change requires a form generation, quick processVersion control: Source form and version form managementHow does the form reach the users, how do they know If changes are likely to be made need to think about how users access forms to ensure updated version is used If not, or if used often, then forms can be kept on local desktops v intranets?
10 Field form:Form design is first step, involves colour schemes, page layout, fonts etc, anywhere up to 5 daysAdding validation could be anything up to a dayMandatory field checks add an extra dayAdding digital signatures, if the server is set up then approx a day per signatureSkills:Form design and creation:Livecycle designer specialist (with design experience, javascript/formcalc) Integration specialist – depends on the integration systemTechnical System: Acrobat or SAP Adobe licenses SAP Java Stack either from NW2004 or NW2004s or CE SAP Liveycycle designer 8.0
User Productivity – removing unnecessary admin Ability to take on business impacting tasks Increasing motivation levels by playing an active part in the business, more likely to stay reducing costs of hiringData Integrity – acting on and decision making using up-to-date info Data Stewardship – move the responsibility back to the owner, without giving access to your systems Decision making – ensuring data is accurate when making decisionsCost Avoidance – ATO, Regulatory bodiesPayback periods
* No additional fields will be included.
* Forms are one page and contain less that 15 fields. Validation will be limited to no more than 10 fields per form with no dynamic display elements. Forms are offline and will submit to one integration point through standard SAP BAPIs and RFCs. No return data elements back to the form. Price is exGST.
