how to guide: creating data model from data dictionary ... · onwards. this article provides step...

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2010 SAP AG 1

How to Guide: Creating Data Model

from Data Dictionary Structures

using Bapi Wrapper Wizard

Applies to:

SAP Net Weaver Mobile 7.10. For more information, visit the Mobile homepage.

Summary

This article is mainly for the application developers to mobilize their business using NW Mobile 7.10 onwards. This article provides step by step procedure to create data model from existing data dictionary structures using Bapi Wrapper Wizard tool.

Author: Suma S

Company: SAP Labs India Pvt Ltd

Created on: 09 Sep 2010

Author Bio

Suma S is working with SAP Net Weaver Mobile team from past 5 years at SAP Labs India Pvt. Ltd.

https://www.sdn.sap.com/irj/sdn/nw-mobile

How to Guide: Creating Data Model from Data Dictionary Structures using Bapi Wrapper Wizard


© 2010 SAP AG 2

Table of Contents

Introduction to Data Orchestration Engine (DOE) .............................................................................................. 3

Role of BapiWrapper Wizard in DOE .............................................................................................................. 3

BAPI Wrappers and its types .............................................................................................................................. 4

Usage of BapiWrapper Wizard ........................................................................................................................... 5

Focus............................................................................................................................................................... 5

Prerequisites for BapiWrapper Wizard ............................................................................................................ 5

Steps to create Backend tables ...................................................................................................................... 6

Steps to create BapiWrappers using Wizard: ................................................................................................. 8

Modifying the BAPI Wrappers ....................................................................................................................... 15

Sample Code Snippet is provided for reference. .......................................................................................... 16

Related Content ................................................................................................................................................ 21

Copyright........................................................................................................................................................... 22



© 2010 SAP AG 3

Introduction to Data Orchestration Engine (DOE)

Data Orchestration Workbench is an ABAP-based development tool that allows user to model a data object, define distribution models and so on. In other words, the tool allows user to define all the metadata required to stage data in the Net Weaver AS (NWAS) and distribute this data to various receivers. This tool is available in the NWAS and is a part of the design time component of the DOE

The DOE workbench the hierarchy looks as below:

Software Component Version holds all the data objects, backend adapters and distribution models.

A data object represents a business object that allows user to stage data relevant for mobile applications in SAP Net Weaver AS. It contains processing information in the form of a flow definition.

Back-end adapter will have BapiWrappers which can exchange data with back-end systems.

Distribution model will have distribution rules and dependencies that ensure data distribution to various receivers.

Role of BapiWrapper Wizard in DOE

By using BapiWrapper wizard, users can convert their business data dictionary structures into data models. (Prerequisite: RFC destination from this NWAS to the backend system (where Business data is placed).

Using this wizard following entities can be created:

BAPI Wrappers

Data Objects (DO)

Backend Adapter (BA)

Software Component Version (SWCV)



© 2010 SAP AG 4

BAPI Wrappers and its types

BAPI Wrappers are normal function modules which are RFC enabled. It should conform to certain rules to be used for Data Object interface.

All the business logic of the application resides inside the BAPI Wrappers (coding)

There are 5 types of BAPI wrappers:

GETLIST: Returns a list of business object header data based on the selection criteria specified in the Import parameters.

GETDETAIL: Returns one header data as Export parameter, based on the object key(s) specified in the Import parameters. It also returns one or more list of child/children entries associated with header data.

CREATE: Creates a single business object and returns object key(s)

MODIFY: Modifies the business object header and also its child data.

DELETE: Deletes the specified business object (including the children).

All the wrappers are not mandatory, only Getlist and Getdetail are mandatory.

Rules for BapiWrappers:

It should be RFC enabled.

Parameter named “RETURN” of type BAPIRET2 structure needs to be defined as Export or Table parameters.

Parameters can only refer to a structure or field of a structure.

It should not have changing parameters.

It should not have Exceptions.

There should be consistency between all the 5 BapiWrappers while defining Export, Import, Table parameters.

All BapiWrappers must be stored in the same Function Group.



© 2010 SAP AG 5

Usage of BapiWrapper Wizard

BAPI Wrapper Wizard ensures that all the Pre-requisites/Conditions which are defined in the section BapiWrapper and Its Type are met.

The following activities can be performed by using BapiWrapper Wizard:

Create BAPI wrappers and assign them to an existing function group or create a new function group if it does not exist. Creating Data Objects and Backend Adapters using these BAPI wrappers

Create function modules to exchange attachments between the backend and the DOE. Creating Data Objects and Backend Adapters using these attachment function modules along with BAPI wrappers.

Importing the existing BAPI wrappers and attachment function modules as data objects and backend adapters into the DOE

Focus

The screen shots in this document covers creation of data dictionary tables, new BapiWrappers, new DO and new SWCV.

Prerequisites for BapiWrapper Wizard

Before proceeding with BAPI wrapper creation, ensure that the following prerequisites have been met:

The backend destination in which the BAPI wrappers have to be created has to be maintained in SM59. Creating an RFC Destination to the Back End

User has defined structures and tables in the backend system together with information about key fields to uniquely identify instances.

Example: Let us create a Data Object using BapiWrapper wizard which refers to VAL_PRODUCT header table and VAL_PRD_SUPPLIER child table.

VAL_PRODUCT Header Table contains following data fields:

FIELD NAME TYPE SIZE KEY

PRODUCT_CODE CHAR 6 BEKEY

PRODUCT_NAME CHAR 12

UNITS_IN_ORDER INT 4

UNIT_PRICE INT 4

VAL_PRD_SUPPLIER Child Table contains following data fields:

FIELD NAME TYPE SIZE KEY

SUPPLIER_CODE CHAR 6 BEKEY

PRODUCT_CODE CHAR 6 BEKEY

SUPPLIER_DESC CHAR 50

QUANTITY CHAR 6

http://help.sap.com/saphelp_nwmobile71/helpdata/en/c2/342ae91cbe4b099a18806deb0ab740/content.htm



© 2010 SAP AG 6

Steps to create Backend tables

1. Table Creation Transaction SE11, Select Database table, provide the name for table and click on Create Button

2. Provide the Short Description for the Table, „Under Delivery and maintenance‟ tab, select „Delivery Class‟ as „A‟ (Application table –Master and transaction data), and „Data Browser/Table View Maint‟ as „Display/maintenance Allowed„. This will allows enhancing the table in future.

Save the table.



© 2010 SAP AG 7

3. Provide the Field names and the corresponding data types. Click on the Technical Settings, to provide the technical details for the table.

Provide the technical details as shown below:

After this Save and activate the table.



© 2010 SAP AG 8

Steps to create BapiWrappers using Wizard:

Follow the below mentioned steps to create SWCV, DO and BapiWrappers using the wizard:

1. Go to SDOE_WB transaction, Select BAPI Wrapper Wizard from Utilities Menu or Directly Click on the BAPI Wrapper Wizard Button.

2. Click on Continue



© 2010 SAP AG 9

3. Provide the RFC Destination and Function Group to connect to the backend system. If the Function group is already available in the Backend System it will use the same, otherwise it will create the function group.

4. Provide the BAPI Wrapper names to be created and click on Next.



© 2010 SAP AG 10

5. Provide the details of root node and the child node in the next screen. Select the Radio button against the Root node for the header node, if the node have attachment fields, provide the attachment function module for the node and click on continue.

6. Select the Key Fields of the Node, and check „Import the BAPI Wrappers into DOE‟



© 2010 SAP AG 11

7. In the following screen, we have an option to import the BAPI Wrappers into new SWCV or into the Existing SWCV.

Click on Create new SWCV; provide the Name of SWCV, and its vendor and version.

Provide the Data object Package; this will store the SWCV, Data Objects in that Package.

Provide the Data Object Name; select the category as STD, and Bidirectional as the Direction,

And click on Continue.

Note: If we need to import the BapiWrappers into the existing SWCV, click on „Importing to existing SWCV‟ and provide SWCV and DO details.



© 2010 SAP AG 12

8. In the following screen, if DO needs to be Backend Triggered, provide the Backend BO. Otherwise leave the field blank. Check the „Generate runtime objects on import‟ which helps in generating the DO automatically once the DO is created.

Note: If the nodes have attachment fields (Text or Image) Click on the attachment Function Modules tab and provide the

attachment function module for each field in a node.



© 2010 SAP AG 13

9. Select the Key Field of the child node in the Next Screen.

10. Click on Continue and finish. Save it and trigger generation as shown below:



© 2010 SAP AG 14

11. After the Generation, search for the created SWCV, it looks like below

Note: If Data object have more than two levels, then explicit key mapping has to be done after the DO creation, from the DOE workbench. After this activate the DO and then Backend Adapter.



© 2010 SAP AG 15

Modifying the BAPI Wrappers

Once the BAPI Wrappers are created, go to function builder (transactionSE37) in the Backend system, edit the contents based on the need.



© 2010 SAP AG 16

Sample Code Snippet is provided for reference.

Go To SE37 and edit the generated BapiWrappers and add the following code snippet and activate the function modules:

VAL_PRD_GETLIST:

*"--------------------------------------------------------------------

*"*"Local Interface:

*" TABLES

*" PRODUCT STRUCTURE VAL_PRODUCT

*" RETURN STRUCTURE BAPIRET2

*"--------------------------------------------------------------------

data: lpar1 like sy-msgv1,

lpar2 like sy-msgv2,


lpar4 like sy-msgv4 ,

lcl like sy-msgid,

ltype like bapireturn-type,

lnumber like sy-msgno,

bapireturn type bapiret2.

select * from val_product into corresponding fields of table product.

if sy-subrc <> 0

call function 'BALW_BAPIRETURN_GET2'

exporting

type = ltype

cl = lcl

number = lnumber

par1 = lpar1

par2 = lpar2

par3 = lpar3

par4 = lpar4

" LOG_NO =

" LOG_MSG_NO =

" PARAMETER =

" ROW = 0

" FIELD =

importing

return = bapireturn.

append bapireturn to return.

endfunction.

endif.

VAL_PRD_GETDETAIL:



© 2010 SAP AG 17

*"--------------------------------------------------------------------


*" IMPORTING

*" VALUE(CLIENT) TYPE VAL_PRODUCT-CLIENT OPTIONAL

*" VALUE(PRODUCT_CODE) TYPE VAL_PRODUCT-PRODUCT_CODE OPTIONAL

*" EXPORTING

*" VALUE(PRODUCT) TYPE VAL_PRODUCT

*" TABLES

*" PRO_SUPPLIER STRUCTURE VAL_PRD_SUPPLIER


*"--------------------------------------------------------------------





lcl like sy-msgid,




select single * from val_product into corresponding fields of product where product_c

ode = product_code.

if sy-subrc eq 0.

select * from val_prd_supplier into corresponding fields of table pro_supplier wh

ere product_code = product_code.

else.


exporting

type = ltype

cl = lcl

number = lnumber

par1 = lpar1

par2 = lpar2

par3 = lpar3

par4 = lpar4

" LOG_NO =

" LOG_MSG_NO =

" PARAMETER =

" ROW = 0

" FIELD =

importing



endif.

endfunction.

VAL_PRD_CREATE:

*"----------------------------------------------------------------------


*" IMPORTING

*" VALUE(PRODUCT) TYPE VAL_PRODUCT OPTIONAL



© 2010 SAP AG 18

*" EXPORTING

*" VALUE(CLIENT) TYPE VAL_PRODUCT-CLIENT

*" VALUE(PRODUCT_CODE) TYPE VAL_PRODUCT-PRODUCT_CODE

*" TABLES



*"----------------------------------------------------------------------





lcl like sy-msgid,




if product is not initial.

client = product-client.

product_code = product-product_code.

insert val_product from product.

if sy-subrc eq 0.

data: wa_val_prd_supplier like line of pro_supplier.

loop at pro_supplier into wa_val_prd_supplier.

insert val_prd_supplier from wa_val_prd_supplier.

endloop.

else.


exporting

type = ltype

cl = lcl

number = lnumber

par1 = lpar1

par2 = lpar2

par3 = lpar3

par4 = lpar4

" LOG_NO =

" LOG_MSG_NO =

" PARAMETER =

" ROW = 0

" FIELD =

importing



endif.

endfunction.

VAL_PRD_MODIFY:

FUNCTION VAL_PRD_MODIFY.

*"----------------------------------------------------------------------


*" IMPORTING

*" VALUE(PRODUCT) TYPE VAL_PRODUCT



© 2010 SAP AG 19

*" TABLES



*"----------------------------------------------------------------------

DATA: LPAR1 LIKE SY-MSGV1,

LPAR2 LIKE SY-MSGV2,


LPAR4 LIKE SY-MSGV4 ,

LCL LIKE SY-MSGID,

LTYPE LIKE BAPIRETURN-TYPE,

LNUMBER LIKE SY-MSGNO,

bapireturn type BAPIRET2.

if product is not initial.

modify val_product from product.

data: it1 type table of val_prd_supplier,

wa1 type val_prd_supplier,

wa2 type val_prd_supplier.

select * from val_prd_supplier into table it1 where product_code =

product-product_code.

loop at pro_supplier into wa1.

delete it1 where supplier_code = wa1-supplier_code and

product_code = wa1-product_code.

endloop.

delete val_prd_supplier from table it1.

loop at pro_supplier into wa2.

modify val_prd_supplier from wa2.

endloop.

else.

CALL FUNCTION 'BALW_BAPIRETURN_GET2'

EXPORTING

TYPE = LTYPE

CL = LCL

NUMBER = LNUMBER

PAR1 = LPAR1

PAR2 = LPAR2

PAR3 = LPAR3

PAR4 = LPAR4

" LOG_NO =

" LOG_MSG_NO =

" PARAMETER =

" ROW = 0

" FIELD =

IMPORTING

RETURN = BAPIRETURN.


endif.

ENDFUNCTION.

VAL_PRD_DELETE:

FUNCTION VAL_PRD_DELETE.

*"--------------------------------------------------------------------


*" IMPORTING

*" VALUE(CLIENT) TYPE VAL_PRODUCT-CLIENT

*" VALUE(PRODUCT_CODE) TYPE VAL_PRODUCT-PRODUCT_CODE

*" TABLES




© 2010 SAP AG 20

*"--------------------------------------------------------------------

DATA: LPAR1 LIKE SY-MSGV1,



LPAR4 LIKE SY-MSGV4 ,

LCL LIKE SY-MSGID,

LTYPE LIKE BAPIRETURN-TYPE,

LNUMBER LIKE SY-MSGNO,

bapireturn type BAPIRET2.

data: it_val_product type table of val_product,

wa_it_val_product like line of it_val_product.

data: it_val_prd_supplier type table of val_prd_supplier,

wa_it_val_prd_supplier like line of it_val_prd_supplier.

select * from val_product into corresponding fields of table

it_val_product where product_code = product_code.

if sy-subrc eq 0.

loop at it_val_product into wa_it_val_product.

endloop.

if sy-subrc = 0.

delete val_product from wa_it_val_product.

endif. select * from val_prd_supplier into corresponding fields of table

it_val_prd_supplier where product_code = product_code.

loop at it_val_product into wa_it_val_product.

endloop.

if sy-subrc = 0.

delete Val product from wa_it_val_product.

endif. loop at it_val_prd_supplier into wa_it_val_prd_supplier.

delete val_prd_supplier from wa_it_val_prd_supplier.

endloop.

else.

CALL FUNCTION 'BALW_BAPIRETURN_GET2'

EXPORTING

TYPE = LTYPE

CL = LCL

NUMBER = LNUMBER

PAR1 = LPAR1

PAR2 = LPAR2

PAR3 = LPAR3

PAR4 = LPAR4

" LOG_NO =

" LOG_MSG_NO =

" PARAMETER =

" ROW = 0

" FIELD =

IMPORTING

RETURN = BAPIRETURN.


endif.

ENDFUNCTION.



© 2010 SAP AG 21

Related Content

Once the Model is created, create distribution model and rules. After this, model can be used to create „Mobile Application for handheld‟ and „Mobile Application for Laptop‟.

In the Link to SAP Documentation

Refer to the section „Concepts of Distribution‟ for Distribution Model

Refer to the section „Developing Mobile Application for Handhelds‟ for Application development on handhelds

Refer to the section „Developing Mobile Application for Laptops‟ for Application development on Laptops.

For more information, visit the Mobile homepage

http://help.sap.com/saphelp_nwmobile711/helpdata/en/47/a991f27dbd3376e10000000a421937/frameset.htm

https://www.sdn.sap.com/irj/sdn/nw-mobile



© 2010 SAP AG 22

Copyright

© Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission 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 other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States 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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C 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 invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

how to guide: creating data model from data dictionary ... · onwards. this article provides step...

Documents