comp 301

28
COMP301 Boeing’s Experiences Integrating Adobe Forms Into Their Business Processes Michael S. Kalich, NetWeaver Developer Kira A. Semerjian, NetWeaver Developer

Upload: koizak

Post on 29-Dec-2015

24 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Comp 301

COMP301

Boeing’s Experiences Integrating Adobe Forms Into Their Business Processes

Michael S. Kalich, NetWeaver DeveloperKira A. Semerjian, NetWeaver Developer

Page 2: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 2

1. Developing forms using SFP and Adobe Live Cycle Designer1.1. Overview developing interfaces and forms1.2. Examples, Issues

2. Integrating forms into Web Applications and Enterprise Portal2.1. Generating and displaying form in BSP, ABAP Web Dynpro, Java Web

Dynpro2.2. Zero Client Install and Active X Plug In

3. Integrating forms into the UWL and Work Processes3.1. Updating UWL’s XML configuration files3.2. Creating workflow task and coding method to convert form to a PDF

4. Using Offline Interactive Forms as part of the business process

5. Tips

Agenda

Page 3: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 3

Background

Boeing Service Company We Operate, Maintain and Sustain our customers’ systems

A wholly-owned subsidiary of The Boeing Company reporting through IDS Support Systems Integrated Logistics

Customers include DoD, other USG, commercial, and other Boeing programs

SAP as part of a service offering

Web AppServer 7.0

mySAP ERP 2005ECC 6.0EA-PS BI 7.0

ABAP Stack

EnterprisePortal 7.0

Productive Systems

Page 4: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 4

Developing Forms Using SFP and Adobe Live Cycle Designer

Overview developing interfaces and forms To create a form, first create the form interface and then create the form in

transaction SFP

Form Interface Represents the data structures to display or have the user enter on the Interactive

form

Can be simple types, structures, or tables

Form Create a form and assign the form interface.

Data elements in the form interface can be used in the form

LiveCycle Designer is displayed in the Layout tab of the form

Page 5: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 5

Design Time

Page 6: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 6

Run Time

Page 7: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 7

Interface

Page 8: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 8

Form Interface

Page 9: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 9

GUI Issues

SAP GUI for Windows

640 GUI – Designer should be installed and check location on hard drive. Default location: C:\program files\adobe\designer 7.1

Ensure that latest GUI patches are installed (LiveCycle Designer 7.1 requirement)

Adobe Reader 7.0 (minimum)

Page 10: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 10

Master Pages

Page 11: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 11

Tips for Master Pages

Create the master page before the body pages

Check for data belonging to the background of the page

Set content area, this will be where the body pages data will appear (icon)

Divide form information / data into

Header (master page) Form content (body page)

– Leaders / detail lines / trailers Footer (master page)

Page 12: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 12

Subforms

Can be placed in content area of master page.

If type Position Content, objects of subforms can be placed at their exact position at design time.

If type Flow Content, the objects will follow each other, depending on the space required at runtime.

Contents of subform can be protected against page break.

Page 13: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 13

When to Use Subforms

When to place objects in subforms:

If you want to output the element repeatedly

If you want to visually group objects

If you want to keep objects together (protect them against page break)

If you want to hide several elements at once (scripting required)

Note: Multiple nested subforms will affect performance

Page 14: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 14

Set up for Tables

Nested tables can be linked together using conditions. On the content tab inside transaction SFP, double click the table to see the details.

Click on “where conditions” button. (Example: KUNNR = TABLE1-KUNNR)

Now, for every KUNNR in the first table, it will list out all matching KUNNR’s from the second table

Nested tables are very useful for situations when you have a one-to-many / many-to-many relationship between tables

Non-nested tables can still use conditions, by clicking on “conditions” button within each table.

*Tip: On the Context tab, inactivate any unused fields from the tables. This will make it easier when adding the table to your layout

FP examples

Page 15: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 15

Integrating Forms into Web Applications

Integration into a BSP:

In OnInitialization, first use open form with the parameter “getpdf=x”:

When generating the form, make sure to import the PDF string from the “formoutput” parameter. Using the classes CL_HTTP_RESPONSE and CL_TTP_SERVER, create the URL string for the PDF and display in the layout using tag IFrame <iframe name = “pdfdisplay” src = url_string>

Page 16: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 16

Zero Client Install and Active X Plug-in

As of NetWeaver 7.0 SPS 10 two options exists for Interactive Forms client side architecture:

Recommended is the Zero Client Install (ZCI) which uses JavaScript in the Interactive Form to integrate between the browser and the Adobe Reader

Active Control Framework (ACF) requires the client to install ACF ActiveX on browser to run forms

Page 17: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 17

Updating UWL XML Configuration

Need to tell UWL about work items in the back end and what to do when user clicks on each type of work item

Need to upload XML configuration to add actions to work items that allow specific forms to be launched

Page 18: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 18

XML File

XML file representing the task

The syntax of these files can be found in the SAP help portal at Business Task Management Universal Worklist Configuration Configuration DTD.

Page 19: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 19

Workflow Task

Can get to workflow task using transaction SWDD

Page 20: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 20

Upload XML

Page 21: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 21

Clear Cache

Whenever you customize the UWL, you should clear the UWL cache afterwards.

Page 22: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 22

Why Offline Interactive Forms?

Business Scenario:

Customers at sites do not have SAP or Portal access, but they need to submit material forms.

TT: why did we need this, how to make it editable (code snippet), how to send in PDF format (vs. XML standard) show code

How to add FORMCALC for totaling

How to create dynamic data binding for drop downs

Custom code to generate and upload

Page 23: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 23

Settings for Offline Forms

For the form to be editable offline, some parameters needed to be specified:

Page 24: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 24

Tips

Page 25: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 25

ASUG and SAP: Partners in Education

ASUG, Americas’ SAP Users’ Group, is the world’s largest, customer-run community of SAP professionals and partners, with more than 50,000 individual members and 1,750 companies represented. ASUG delivers the highest value to member companies, allowing them to maximize their SAP investments.

Some highlighted benefits include: Access to a year-round community for SAP customers and partners Diverse mix of educational topics and events through a variety of formats Exclusive opportunity to influence SAP future product direction Unparalleled networking opportunities with a dynamic professional network Unprecedented partnership with SAP Access to ASUG Special Interest Groups and Chapters

To learn more about ASUG, visit the ASUG booth in the SDN Clubhouse, or visit our Web site at www.asug.com.

Page 26: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 26

Further Information

SAP Public Web:SAP Developer Network (SDN): www.sdn.sap.com

Business Process Expert (BPX) Community: www.bpx.sap.com

Americas’ SAP Users’ Group (ASUG)www.asug.com

Page 27: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 27

Thank you!

Page 28: Comp 301

© SAP 2008 / SAP TechEd 08 / COMP301 Page 28

Please complete your session evaluation.

Be courteous — deposit your trash, and do not take the handouts for the following session.

Thank You !

Feedback