sap grants management for grantorpds15.egloos.com/pds/200912/23/94/unit04_webrequest.pdf2 ¤sap ag...

1

SAP Grants Managementfor Grantor

Unit 4: Web Request

2

SAP AG 2005, Title of Presentation / Speaker Name / 2

General

Use

Prior to having similar data structures across all grantor program, a webrequest offers the possibility to capture program dependent data structure andlink it a CRM one-order object

Comparison

X-Mandatory FieldCheck

X-Draft UI creation

X-Out of the box AdobeIntegration

X-Automatic linkage toCRM One-OrderObject

X-VersioningWeb RequestBSPFeatures

3


Request Category

Use

For each Request Category you define a set of fields „Request DataStructure“. These fields are available within the programming environment.In the case of grantor, the Request Category should always be linked to aCRM transaction type.*

Grantor delivers three samples

CRM -> IMG -> Customer Relationship Management -> E-Commerce -> E-Service -> Web Requests -> Define Request Categories

*The linkage between the Request Category and the crm transaction type isevaluated for the field „Web request“ on assignment block „process assignment“ onthe CRM program UI.

4


Request Category – Request Data Structure

Use

Define fields and field properties

5


Request Category – Implementation

Use

Create BadI Implementation in order to link web request values and one-order object fields

6


Request Category

Use

Mark the field „Request Categor is active“

7


Request Category View

Use

Define one or several views per Request Category

8


Request Category View – Business Server Page

Use

Create a view which uses BSP technolgy. Clicking on the „Generate“ buttonwill automatically create a draft Business Server Page which contains allthe fields.

9


Request Category View – Business Server Page

10


Request Category View – Adobe Interactive Form

Use

Create a view which uses Adobe Interactive Form Technology. Clicking onthe „Generate“ button will automatically create an interface and a form.

In order to design the adobe form, press the „Change“ button

11


Request Category – Adobe Interactive Form

1) Make sure you are in Change Mode

2) Insert Web Dynpro Script*

3) Drag the Data view (all fields from the data request structure) into the „Body Pages“ section

4) Change the layout

5) Press the „activate“ button in the SAP menu bar

*Click on the SAP menu entry „Utilities“ and click „Insert Web Dynpro Script“

12


Request Category View – Adobe Interactive Form

13


Request Category – Adobe Interactive Form

Additional Software Requirements*

- ABA SP13

- Adobe Designer

- Adobe Reader (see note 834573)

* The use of adobe interactive forms is not included in the grantor pricing

14


Appendix – Adobe Interactive Form

Mandatory Fields

In order to block the submission of an adobe form in case of mandatoryfields defined in the „request data structure“

which are not filed, additional coding needs to be added at the end ofmethod „FORM_ON_EVENT“

15



Mandatory Fields

DATA: ls_wr_message TYPE uxb_s_message.IF cd_event EQ 'SUBMIT'.

* check if there are error messages in the formls_wr_message = cl_uxx_message=>get_most_severe_error( it_message = it_message ).

* stop in case of error messagesIF ls_wr_message-type EQ 'E' OR et_message IS NOT INITIAL.CLEAR cd_event.ENDIF.

ENDIF.

16



F4 help – Fix Values

1) Assign to your request data structure one DDIC element with adomain value range

17




2) Add field to the form*

3) Define binding for enumerated drop-down box **

*In case the form interface already existed, you have to regenerate it**http://help.sap.com/saphelp_nw2004s/helpdata/en/42/fb2fe500553ee4e10000000a1553f7/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/42/fb2fe500553ee4e10000000a1

18




4) Result

19



F4 help – Dynamic Values

1) Copy the default Web Dynpro Application “CRM_WEBREQ_IAF”

2) Start workbench and launch the copied web Dynpro Component

3) Go to the view FORM and to tab METHODS. Double click on methodWDDOINIT

20




4) Add similar coding* to this method

5) Assign the copied Web Dynpro Application to your web request view

* customer coding to set value setsDATA:lr_generic_node TYPE REF TO if_wd_context_node,lr_generic_node_info TYPE REF TO if_wd_context_node_info,ls_attr_info TYPE wdr_context_attribute_info,lv_path TYPE string,ls_key_value TYPE wdy_key_value.

ls_key_value-key = 'KEY1'.ls_key_value-value = 'VALUE1'.APPEND ls_key_value TO ls_attr_info-value_set.ls_key_value-key = 'KEY2'.ls_key_value-value = 'VALUE2'.APPEND ls_key_value TO ls_attr_info-value_set.

* translate all nodes to upper CASE, the leaf node is the attribute* XML: //request/applicant/name/first_name ->* Context: REQUEST.1.APPLICANT.1.NAME -> attribut name = FIRST_NAME

lv_path = 'REQUEST.1.APPLICANT.1.NAME'.lr_generic_node = wd_context->path_get_node( path = lv_path ).lr_generic_node_info = lr_generic_node->get_node_info( ).lr_generic_node_info-

>set_attribute_value_set( name = 'FIRST_NAME' value_set = ls_attr_info-value_set ).

21




6) Add field to the form*

7) Define binding for enumerated drop-down box **

*In case the form interface already existed, you have to regenerate it**http://help.sap.com/saphelp_nw2004s/helpdata/en/42/fb2fe500553ee4e10000000a1553f7/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/42/fb2fe500553ee4e10000000a1

22




8) Result

23


No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks ofMicrosoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®,OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informixand Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® andother Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium,Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology inventedand implemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, R/3, mySAP, mySAP.com, xApps, xApp and other SAP products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks of SAP AG in Germany and in several othercountries all over the world. All other product and service names mentioned are the trademarks of their respectivecompanies.

Copyright 2003 SAP AG. All Rights Reserved

sap grants management for grantorpds15.egloos.com/pds/200912/23/94/unit04_webrequest.pdf2 ¤sap ag...

Documents