sap in-store ad hoc inventory for windows mobile (an sup template application)

8/12/2019 SAP in-Store Ad Hoc Inventory for Windows Mobile (an SUP Template Application)

http://slidepdf.com/reader/full/sap-in-store-ad-hoc-inventory-for-windows-mobile-an-sup-template-application 1/44

SAP COMMUNITY NETWORK scn.sap.com

© 2012 SAP AG 1

SAP In-Store Ad Hoc Inventory forWindows Mobile (An SUP TemplateApplication)

Applies To:

- SAP ERP Retail system with minimum release ERP EHP6 SP04

- Sybase Unwired Platform (SUP) 2.1.2

- Windows Mobile 5 (or higher)

Summary

This article describes the mobile template application SAP In-Store Ad Hoc Inventory for Windows Mobile.It illustrates the benefits of Sybase Unwired Platform in a straightforward offline-enabled mobile Retail

business scenario. Linked to the article you‟ll find the deployment configur ation files for SUP and theWindows installer files for the native client application.

Author: Matthias Röbig-Landau

Company: SAP AG

Created on: August 2012

Author Bio

Dr. Matthias Röbig-Landau joined SAP in 1996.

Since 2006, he has been working in the area of Trade and Retail software development and

architecture, in multiple projects on various technical platforms.



SAP In-Store Ad Hoc Inventory for Window s Mobi le ( An SUP Template Application)


© 2012 SAP AG 2

Table of ContentsIntroduction ......................................................................................................................................................... 4

Prerequisites ....................................................................................................................................................... 4

Backend System ............................................................................................................................................. 4

Partner Profiles - ALE Interfaces .................................................................................................................................. 4

Enable Direct Creation of Inventory Docs .................................................................................................................... 4

Standard Retail Inventory Interface .............................................................................................................................. 4

Monitoring and Approval .............................................................................................................................................. 5

Links to Standard Documentation ................................................................................................................................ 5

Sybase Unwired Platform................................................................................................................................ 5

Mobile Device .................................................................................................................................................. 5

Downloads .......................................................................................................................................................... 6

Scenario - In-Store Ad Hoc Inventory ................................................................................................................. 6

Detailed Use Case Description ........................................................................................................................... 6

Business Goal ................................................................................................................................................. 6

Trigger Event ................................................................................................................................................... 6

Basic Scenario ................................................................................................................................................ 6 Features and Details ....................................................................................................................................... 7

Article Identification ...................................................................................................................................................... 7

Displayed Article Information ....................................................................................................................................... 7

Supported Parameters ................................................................................................................................................. 7

Packages Overview and Correction ............................................................................................................................. 7

Submit .......................................................................................................................................................................... 8

Boundaries and Conditions .......................................................................................................................................... 8

Process Steps ................................................................................................................................................. 8

Count Phase ................................................................................................................................................................ 8

Submit Phase ............................................................................................................................................................... 8

Architecture Layers ............................................................................................................................................. 8

General Architecture ....................................................................................................................................... 8

Realization ...................................................................................................................................................... 9

Platform........................................................................................................................................................................ 9

Platform Adaptation ..................................................................................................................................................... 9

Consumer Adaptation ................................................................................................................................................ 11

Consumer - Mobile Device Application ...................................................................................................................... 15

Implementation Details and Tips ...................................................................................................................... 16

Logging ......................................................................................................................................................... 16

Code Generation in SUP Unwired Workspace ............................................................................................. 17

Client Binaries ............................................................................................................................................... 17

Client Connection and Authentication ........................................................................................................... 18

Synchronization ............................................................................................................................................. 19

Data Access .................................................................................................................................................. 20

Single Data Entry ....................................................................................................................................................... 20

List of Entries ............................................................................................................................................................. 20

Deployment Unit ............................................................................................................................................ 21





© 2012 SAP AG 3

Installation and Deployment ............................................................................................................................. 22

SUP Server Deployment ............................................................................................................................... 22

SUP Security Configuration .......................................................................................................................... 22

SUP Domain ................................................................................................................................................. 24

SUP Connection Pool ................................................................................................................................... 26

Deployment of Application Package ............................................................................................................. 27

SUP Application Connection ......................................................................................................................... 31

Installation on Windows Mobile Device ......................................................................................................... 32

Application Walkthrough ................................................................................................................................... 35

Setup ............................................................................................................................................................. 35

Counting ........................................................................................................................................................ 36

Submit ........................................................................................................................................................... 39

Summary........................................................................................................................................................... 40

Glossary ............................................................................................................................................................ 40

Related Content ................................................................................................................................................ 41

Appendix 1: Paths in SAP Easy Access Menu ................................................................................................. 41

Copyright........................................................................................................................................................... 43





© 2012 SAP AG 4

Introduction

Long before the trend for mobile business applications of the last few years, Retail industries used handhelddevices. SAP also supported retailers in the past with browser-based online technologies like “WebDynproJava for mobile” or “ITSmobile”.

With the Sybase Unwired Platform (SUP) as an infrastructure layer, SAP provides a reliable backbone formobile Retail applications. This article proves that usage of SUP for offline-capable mobile applications is notrocket science. SUP is a mobile enterprise application platform that enables developers to simply and quicklydevelop applications that connect business data to mobile workers.

An already published application is the SAP In-Store Product Lookup mobile app for iPhone. By means ofSAP In-Store Product Lookup you can answer your customers' questions about products and their availabilityand adjust your inventory anywhere, anytime. The iPhone app connects to the components in SAP ERP thatsupport retail applications and allows you to display product details and stock levels in your store and instores nearby.

SAP In-Store Ad Hoc Inventory is an offline-enabled inventory scenario for Windows Mobile devices.

Prerequisites

Backend System

The SAP ERP backend system has to be an SAP ERP Retail system with minimum release ERP EHP6

SP04.This can be checked using transaction SFW5, and the Retail menu (transaction W10T) must be available. Bevery careful not to change anything by means of transaction SFW5, because changes cannot be reversed!In addition, the package WOST_MOBILE should exist (transaction SE80) as part of ERP EHP6 SP04 (orhigher).

Partner Profiles - ALE Interfaces

Access the partner profile via transaction WE20. Ensure that for participating stores, a partner profile ismaintained with the following attributes:

- Partner Type KU

- Inbound ParameterMessage Type WVINVE

Without the mentioned ALE settings, the IDoc is not processed and remains. After maintenance of the ALEsettings it can be re-processed.

Enable Direct Creation of Inventory Docs

The responsible POS inbound profile needs to support the direct creation of inventory IDocs. The assignedPOS inbound profile can be found in the plant details on tab POS (transaction WB03 POS).

The corresponding IMG customizing setting can be found via transaction SPRO

SAP Reference IMG Sales and Distribution POS Interface Inbound Enhancement: Store Physical Inventory Control

The relevant POS inbound profile has to be assigned to the value “4 Create phys. inv. docs directly”.

Standard Retail Inventory Interface

The mobile SAP Retail applications utilize the standard IDoc-Inventory interfaces. In case this interface isalready in use within other scenarios at customer site, you need to be aware about the simultaneous feed viamultiple input channels.

http://help.sap.com/saphelp_nw04/helpdata/en/7d/28fa3e7cb1d861e10000000a114084/frameset.htm




http://wiki.sdn.sap.com/wiki/display/HOME/ITSmobile



http://itunes.apple.com/us/app/sap-in-store-product-lookup/id518252454?mt=8











© 2012 SAP AG 5

Monitoring and Approval

The monitoring of IDoc inventory documents can be executed by means of the POS Interface Monitor(transactions WPER and/or WE05). The activation of posted changes needs an approval of possible stockdifferences, for example via transaction MI07.

Links to Standard Documentation

Physical Inventory

Standard Inventory (MM-IM-PI) Inventory Management

Sybase Unwired Platform

Sybase Unwired Platform is an integrated mobile middleware that supports multiple client device types andoperating systems as the platform for mobile enterprise applications. You can find comprehensive and fulldocumentation under: Sybase Unwired Platform 2.1.2

Mobile Device

The mobile application template “SAP In-Store Ad Hoc Inventory Count" is based on a physical procedurewhich is manually controlled via a Rugged Handheld Mobile Computer (RHMC) (for example, MotorolaMC9500). The mobile device RHC (Ruggedized Handheld Computer) is equipped with a barcode scanner

(1D,2D) and/or other comparable data input devices.

A mobile device running on operating system Windows Mobile 6.1 (or higher) is needed. The application wasbuilt and tested mainly on a Motorola MC9500 (WM 6.1). In principle it runs on any Windows Mobile 5 (orhigher) device. It‟s optimized for a rectangular screen (320x480) and typical device settings of Motorola(namely MC 9500).The mobile device has to be enabled for wireless connection against the SUP server. The best verificationmethod is to connect by means of Internet Explorer against SUP‟s SCC (Support Control Center).

The device has to have a laser barcode scanner and a suitable device application installed to read thescanner information (for example Data Wedge from Motorola). In the SAP In-Store Ad Hoc Inventoryscenario, the barcode scanner libraries are not embedded, due to legal reasons. Instead the barcodescanner information is posted to an invisible input field. In order to identify the start and end of a relevantGTIN, the posted scanner information starts and ends with @ (prefix and suffix, see Figure 1).

http://help.sap.com/erp2005_ehp_04/helpdata/en/12/08640e470311d1894a0000e8323352/frameset.htm




http://help.sap.com/erp2005_ehp_04/helpdata/en/a5/632fea43a211d189410000e829fbbd/frameset.htm


http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.pubs.docset-SUP-2.1.2/doc/html/title.html


http://business.motorola.com/mc9500/index.html



https://docs.symbol.com/ReleaseNotes/Release_Notes_-_DataWedge_3.1.htm













© 2012 SAP AG 6

Figure 1 shows the Data Wedge configuration for the SAP In-Store Ad Hoc Inventory application.

Downloads

Here you can find the deployment configuration files for SUP and the Windows installer file for the nativeclient application.

Scenario - In-Store Ad Hoc Inventory

Spontaneous, unplanned inventory counts are used to count small sets of articles in a store. An ad hoc

inventory enables the retail store to provide proof of all individual movements involving storage bins orproducts over the fiscal year. A store employee checks the stock of specific articles. Typical candidates for SAP In-Store Ad Hoc Inventoryare articles with a high leakage rate (for example, razor blades, lipsticks) or items with a high seasonal turnover (for example, ice cream, anti-freeze protection, snow shovel).In both cases the stock numbers need to be kept up to date, in higher cycles than for "normal" articles.

SAP In-Store Ad Hoc Inventory is an offline-scenario, meaning that most (but not all) of the operations stillwork while the device is offline.

Detailed Use Case Description

Business Goal

Adjust stock of a single article, a group of articles, or a shelf. Counting has to work “offline”.

Trigger Event

The user (store associate or store manager) has to update the stock inventory for an article group orsuspicious single articles.

Basic Scenario

SAP In-Store Ad Hoc Inventory Count focuses on following the basic employee scenario:

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c07ff05f-d1be-2f10-6bbf-cc32a7ff4e80







© 2012 SAP AG 8

Packaged articles can be scanned via the package GTIN. Articles are always counted in the unit of

measurement that has been scanned. Employee is informed about counting of package units.

Entered stock information items can be edited or deleted.

The whole elaborated list of counted articles can be:

- Deleted every time

- Deleted on exit of the application

- Kept temporarily on exit of the application

Submit

The inventory data has to be transferred promptly, to minimize the possibility of inconsistencies. After havingscanned and counted all requested articles, the employee submits inventory count information. Submissionof inventory data requires the device to be "online".

Boundaries and Conditions

The mobile device is not regarded as being online all the time, but it has been connected recently, ideallystart-of-day.The SAP In-Store Ad Hoc Inventory Count must not interfere with a planned or continuous inventory and has to be in accordance with legal regulations.In order to be offline-enabled, all required information of the article is available in the backend and isreplicated on the device.

The inventory document in the backend is limited to 300 items. If there are more than 300 scanned articlesthe backend document (IDoc) is split into more than one document.

Process Steps

The recurring process steps of the SAP In-Store Ad Hoc Inventory scenario:

Count Phase

- Article is identified

- Article information is displayed

- User specifies counted number of articles

- User specifies shelf information (available only with multiple placement)

- Application is ready to identify the next article

Submit Phase

- User has a final chance to correct or delete entries

- Submission of inventory data (requires device to be online)

- Success message is displayed

Architecture Layers

General Architecture

The general component architecture of a mobile offline SUP application consists of a high-level view of fourlayers (see Figure 2).

Platform, also called backend layer, comprising ERP, CRM, SCM - SAP Business Suite

Adaptation layer - RFC Wrappers

Consumer adaptation layer - Mobile Business Object modeled in DOE/SUP

Consumer - Mobile Device Application

http://help.sap.com/saphelp_ewm70/helpdata/en/4c/b4e7dc4c1f1921e10000000a15822b/content.htm








© 2012 SAP AG 9

Figure 2 displays the general architecture of SUP-based offline applications. The DOE Connector components (shaded areas) are

not used in the SAP In-Store Ad Hoc Inventory scenario. The orange areas mark the application-specific coding and modeling

components.

Realization

Platform

The ERP basis is an SAP ERP EHP6 SP04 (or higher) Retail system.

Platform Adaptation

The RFC adaptation layer is realized within the development package WOST_MOBILE .





© 2012 SAP AG 10

Implementation Scheme

The main focus is on simple master data access. Specialized dictionary structures and RFC (remote-enabledfunction modules) are optimized on low data volume master data access. Nevertheless the main functionsare not performance-optimized and not integrated into change and update processes.In a productive high data volume scenario, the master data retrieval should be embedded into a commonlyused standard retail process, for example POS outbound process or assortment list versions.

Components The main elements are:

GET function modules (SRSMOB_GET_XX ) that retrieve the relevant master data from the backend

system

Submit function module (SRSMOB_SUBM_ADHOC_INV ) for reporting back inventory data to the

backend system

Underlying adaption dictionary structures that serve as “volume-reduced” data exchange structures

(SRSMOB*)

Figure 3 is a screenshot of the content of development package WOST_MOBILE.

All language-dependent information is retrieved in all available languages, assuming that they all mightbecome relevant on the front end side as they are maintained.

The naming of the modules (see Figure 3) is descriptive, and the implementation of the retrieval backend RFC modules shows two differenttypes.

These RFCs perform a full table scan of the relevant single table:





© 2012 SAP AG 11

- SRSMOB_GET_CUSTOMER_SITES (customer sites = stores)

- SRSMOB_GET_MATERIAL_GROUPS

- SRSMOB_GET_MEAS_UNIT

- SRSMOB_GET_STOCK_TYPES

- SRSMOB_GET_STORAG_LOCATIONS

The following RFCs are a little more complex.

- SRSMOB_GET_ARTICLES

All listed articles, corresponding article texts, relevant sales units, and GTIN numbers. Retrieval

of information is partly realized in single article mode and does not contain store-specific

information.

- SRSMOB_GETMULTIPLE_PLACED

All multiply-placed articles (according to layout information) of a store are listed. This is the

only store-specific retrieval RFC.

- SRSMOB_SUBM_ADHOC_INV

Submit Ad Hoc Inventory data collected on the mobile device. This RFC is based on the popular

function module WOSI_SAVE_AND_PROCESS_IDOC_IN , which is used by customer

implementations for non-planned inventory.

Consumer Adaptation

The consumer adaptation is realized by means of the development tool Sybase Unwired Workspace. Thistool provides developers with visual modeling of Mobile Business Objects (MBO), direct deployment testingand code generation of interfaces for different device platforms.

SUP MBO Data Model

In the SAP In-Store Ad Hoc Inventory template application, the optional component DOE (Data OrchestrationEngine, part of SAP NetWeaver Mobile) is not used. SAP NetWeaver Mobile DOE is suitable for backendcommunication with complex data distribution and conflict handling. This is not the case for the templateapplication SAP In-Store Ad Hoc Inventory. All data is retrieved via JCo-Connector and is buffered in SUPConsolidated Database (CDB).

The MBO data model (see Figure 4) is gathered within one single SUP project, which is recommended forsuch a moderate amount of objects. Data is stored in one SUP CDB only, and the usage of generated codeis less complex.

http://help.sap.com/nwmobile








© 2012 SAP AG 12

Figure 4 illustrates the mobile application diagram inside Sybase Unwired Workspace - MBO Model.





© 2012 SAP AG 13

1

1

n

1

1

1

1

1

n

1

n

1

n

1

SRSMOB_GET_ARTICLES à

CT_ARTICLES

MBO_Articles

ArticlesMaterial Number

Base Unit + Base Unit ISO

Material Group

Unit + Unit ISO

Sales Unit + Sales Unit ISO


CT_ARTICLE_TEXTS

MBO_ArticleTexts

Article TextLanguage (ISO)

Material Number

Material Text


EANS

MBO_EANs

EANMaterial Number

EAN

Unit + Unit ISO

Numerator + Denominator

SRSMOB_GET_MATERIAL_GROUP

Sà MATGRT

MBO_MeasureUnits

Measure UnitLanguage (ISO)

Unit

Unit 3 Digit

SRSMOB_GET_MATERIAL_GROUPS

à MATGRT

MBO_MaterialGroups

Material Group TextLanguage (ISO)

Material Group

Material Group Text

SRSMOB_SUBM_ADHOC_INV à

Attributes

MBO_AdHocInv (Operation)

Stock InventorySite ID

User Name

Inventory Date

Inventory Time

Store Location

Stock Type


ADHOCINV

MBOS_AdHocInv

Stock Inventory ItemEAN

Stock

Sales Unit

Inventory Date

Inventory Time

SRSMOB_GET_STOCK_TYPES à

STOCKTYPE

MBO_StockTypes

Stock TypesLanguage (ISO)

Stock Type ID

Stock Type Text

1

1

SRSMOB_GET_MULTIPLACED_AR

TCLS à ITEM_SHELF

MBO_MultiPlacedArticles

Multiplaced ArticlesSite ID

EAN

Layout Group

Sort Sequence

Shelf Board Number

1

1

SRSMOB_GET_CUSTOMER_SITE

S-PLANT

MBO_CustomerSites

Store

Site ID

1

1

SRSMOB_GET_CUSTOMER_SITES

-PLANT

MBO_StorageLocations

Storage LocationsSite ID

Storage Location

Storage Location Text

1

n

Figure 5 presents the data model of SUP MBOs of SAP In-Store Ad Hoc Inventory.

The SUP Mobile Business (MBO) groups essentially surround the entity Article, which is represented by theMBO_Articles. It gathers all relevant articles, and all necessary side information is provided via related MBOs(MBO_EANs, MBO_MultiPlacedArticles and MBO_ArticleTexts).

The following MBOs gather non-single-article-specific data that is necessary as side information:

- MBO_MaterialGroups - Material group text

- MBO_MeasureUnits - Measure unit texts

- MBO_StorageLocations - Storage locations of stores

- MBO_StockTypes – General stock types and explanation texts

The submission of the inventory data is handled by MBO_AdHocInv (header info) and MBOS_AdHocInv (inventory items). The MBOs are grouped in cache groups (see Error! Reference source not found.).





© 2012 SAP AG 14

Figure 6 shows the grouping of SAP In-Store Ad Hoc Inventory MBOs in cache groups.

The cache policy is predefined to “Scheduled” for all MBOs of one cache group , with cache interval timesvarying from 1 to 12 hours (see Figure 7 and Figure 8). Especially for high data volumes, the schedule timehas been set to a high value. The cache interval time can be changed in the SUP SCC according to specificneeds.

Figure 7 shows the setting of cache policy for cache group MasterData, which contains most of the article-specific information.

Figure 8 shows the setting of cache policy settings for cache group Layout, which contains layout data of multiply-placed articles.





© 2012 SAP AG 15

Local MBOs

Within the client component of SAP In-Store Ad Hoc Inventory, local MBOs are used for storage ofapplication-specific data and preferences.

Purpose of local MBOs:

MBOL_InventoryContext – Application context

MBOL_ConnStettings – SUP server connection settings

MBOL_InventoryList – List of counted inventory items

These local MBOs enable the application to persist data in the SUP device database, even when theapplication or device is shut down or restarted (see Figure 9).

MBOL_InventoryList

Inventory ListEAN_UPC

Count

Shelf

Stock

Material Text

Unit + Unit ISO

Inventory Date

Inventory Time

MBOL_InventoryContext

Inventory ContextUser ID

Language

Creation Data + Time

Customer Site + Text

Storage Location + Text

Stock Type + Text

Inventory Mode

Demo Flag

Current Article

MBOL_ConnSettings

Connection Settings

(SUP)AppID

Server

User

Password

Port

FarmID

Activation Code

Domain

Protocol

Figure 9 lists the local MBOs that serve as a persistence structure for application-specific data and device-specific settings.

Consumer - Mobile Device Application

The client application has been developed with Visual Studio 2008 using programming language C#.

The device implementation makes full use of the SUP MBOs. A large portion of the data stored on the SUPConsolidated Database (CDB) is also synchronized to the client application. Two filters (entities in gray infigure 10) are introduced for special MBOs.

MBO Synchronization Parameters

According to the device settings, language filtering for measure units, material group text, and stock types is applied.

applied. Consequently, only language-dependent texts that match the user setting are stored on the device.The MBO for multiply-placed articles retrieves store-specific data from the CDB. A synchronization parameter on the preset store





© 2012 SAP AG 16

parameter on the preset store ID filters data synchronized to the mobile device (see

1

1

n

1

1

1

1

1

n

1

n

1

n

1


CT_ARTICLES

MBO_Articles



Material Group

Unit + Unit ISO



CT_ARTICLE_TEXTS

MBO_ArticleTexts

Article TextLanguage (ISO Code)

Material Number

Material Text


EANS

MBO_EANs

EANMaterial Number

EAN

Unit + Unit ISO


SRSMOB_GET_MATERIAL_GROU

PSà MATGRT

MBO_MeasureUnits

Measure UnitLanguage (ISO Code)

Unit

Unit 3 Digit


à M ATGRT

MBO_MaterialGroups

Material Group TextLanguage (ISO Code)

Material Group

Material Group Text


Attributes



User Name

Inventory Date

Inventory Time

Store Location

Stock Type


ADHOCINV

MBOS_AdHocInv


Stock

Sales Unit

Inventory Date

Inventory Time


STOCKTYPE

MBO_StockTypes

Stock TypesLanguage (ISO Code)

Stock Type ID

Stock Type Text

1

1


TCLS à ITEM_SHELF



EAN

Layout Group

Sort Sequence

Shelf Board Number

1

1


S-PLANT

MBO_CustomerSites

Store

Site ID

1

1


-PLANT



Storage Location


1

n

1

n

1

n

1

n1

n

Language

Language (ISO Code)

Site ID

Site ID

n1

Figure 10).





© 2012 SAP AG 17

1

1

n

1

1

1

1

1

n

1

n

1

n

1


CT_ARTICLES

MBO_Articles



Material Group

Unit + Unit ISO



CT_ARTICLE_TEXTS

MBO_ArticleTexts

Article TextLanguage (ISO Code)

Material Number

Material Text


EANS

MBO_EANs

EANMaterial Number

EAN

Unit + Unit ISO


SRSMOB_GET_MATERIAL_GROU

PSà MATGRT

MBO_MeasureUnits

Measure UnitLanguage (ISO Code)

Unit

Unit 3 Digit


à MATGRT

MBO_MaterialGroups

Material Group TextLanguage (ISO Code)

Material Group

Material Group Text


Attributes



User Name

Inventory Date

Inventory Time

Store Location

Stock Type


ADHOCINV

MBOS_AdHocInv


Stock

Sales Unit

Inventory Date

Inventory Time


STOCKTYPE

MBO_StockTypes

Stock TypesLanguage (ISO Code)

Stock Type ID

Stock Type Text

1

1


TCLS à ITEM_SHELF



EAN

Layout Group

Sort Sequence

Shelf Board Number

1

1


S-PLANT

MBO_CustomerSites

Store

Site ID

1

1


-PLANT



Storage Location


1

n

1

n

1

n

1

n1

n

Language

Language (ISO Code)

Site ID

Site ID

n1

Figure 10 presents the data model of SUP MBOs of SAP In-Store Ad Hoc Inventory accessed from the mobile device client.

Language- and store-specific data is filtered according to device settings.

Implementation Details and Tips

Logging

As a logging utility for the client application, “log4net” is used. The configuration is located in the path<Application Root Directory>/logging/logging.configand can be modified in the common way. Detailed information can be found on many sites on the Internet(for example Log4Net-Tutorial).

http://www.codeproject.com/Articles/140911/log4net-Tutorial









© 2012 SAP AG 18

Code Generation in SUP Unwired Workspace

After modeling the data access layer, SUP Unwired Workspace offers an excellent way of generating theadaption layer interface in a very efficient way (see Figure 11).

Figure 11 shows how to start the code generation wizard in SUP Unwired Workspace.

The settings in the following wizard are widely self-explanatory, and its details well-documented in theDeveloper Guide: Windows and Windows Mobile Object API Applications .

Client Binaries

The Windows Mobile client component has been developed in Visual Studio 2008. The generated codingand the related SUP dll-files were placed beside the generated code inside a folder named “Dlls” , during thegeneration process.

The list of dll-files that need to be added to the solution:

- CMessaging.dll (mind to take the dll from folder “smartphone”)

- iAnywhere.Data.UltraLite.dll

- mlcrsa12.dll

- mlczlib12.dll

- sup-client.dll- ulnet12.dll

- ulnetclient12.dll

The properties have to be set as shown in Figure 12, so that the dll-files are attached to the deploymentpackage.

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01216.0212/doc/pdf/sup_devguide_windowsmobile_objectapi_applications.pdf







© 2012 SAP AG 19

Figure 12 displays property settings for SUP dll-files.

Client Connection and Authentication

The authentication against SUP is realized basically with the following code pattern. It also illustrates theusage of local MBOs.

//Sybase Application

Sybase.Mobile.Application app = Sybase.Mobile.Application.GetInstance();

app.ApplicationIdentifier = "sap_adhocinv";

//

...

Callback handlers and application handlers

...

//

// retrieve stored connection setting from local MBO

MBOL_ConnSettings connSettings =MBOL_ConnSettings.FindByPrimaryKey("sap_adhocinv");

ConnectionProperties connProps = app.ConnectionProperties;

connProps.ServerName = connSettings.Server;

connProps.PortNumber = int.Parse(connSettings.Port);connProps.ActivationCode = connSettings.ActivationCode;

connProps.FarmId = connSettings.FarmID;

LoginCredentials loginCred = new LoginCredentials(connSettings.User,connSettings.Password);

connProps.LoginCredentials = loginCred;

// register application

SAPAdHocInventoryDB.SetApplication(app);





© 2012 SAP AG 21

// set synchronization parametersMBO_MultiPlacedArticlesSynchronizationParameters SynchParamsMP =MBO_MultiPlacedArticles.GetSynchronizationParameters();

SynchParamsMP.S_CUSTOMER_SITE = invCtxt.CustomerSite;

SynchParamsMP.Save();

MBO_MaterialGroupsSynchronizationParameters SynchParamsMG =MBO_MaterialGroups.GetSynchronizationParameters();

SynchParamsMG.S_LAISO = invCtxt.Language;

SynchParamsMG.Save();

...

//open connectionSAPAdHocInventoryDB.OpenConnection();

GenericList<ISynchronizationGroup> genSynchGroups =SAPAdHocInventoryDB.GetAllSynchronizationGroups();

int n = 0;SynchronizationGroup synchGroup;

// loop an synchronization groups

while (n < genSynchGroups.Count){synchGroup = (SynchronizationGroup)genSynchGroups.ElementAt(n);n++;TimeSpan delta = DateTime.Now -

SAPAdHocInventoryDB.GetLastSynchronizationTime(synchGroup.Name);

// check if delta synch is needed for this groupif (delta.Duration().TotalHours > 10){

// delta synch SAPAdHocInventoryDB.Synchronize(synchGroup.Name);

}

}

Data Access

Single Data Entry

The data access via the synchronized MBOs is fairly simple when the primary key can be specified, which ismostly the case in the given scenario.

MBO_ArticleTexts mbo_articleText =MBO_ArticleTexts.FindByPrimaryKey(materialNo,invCtxt.Language);

In the example given, the invCtxt corresponds to the overall present context information of the applicationthat also stores the current language setting. List of Entries On retrieval of a list of entries, a query request needs to be defined.In this code example, all EAN numbers (also known as GTIN) for a given material are retrieved into a list.

Query query = new Query();





© 2012 SAP AG 22

AttributeTest ts = new AttributeTest(); ts.Attribute = "MATERIAL"; ts.Value = material; ts.SetOperator(AttributeTest.EQUAL); query.SetTestCriteria(ts);

Sybase.Collections.GenericList<MBO_EANs> genListEANs;

genListEANs = MBO_EANs.FindWithQuery(query);

Deployment Unit

The SUP Unwired Workspace offers this opportunity to directly deploy the application package to aconnected server (see Figure 13).

Figure 13 shows deployment during the development process.

For the purpose of releasing and distributing the application, a deployment package has to be generated,which defines the composition settings. The abstraction layer of the SUP Deployment Package allows you,for example, to combine varying sets of MBOs in different deployment units.

Figure 14 demonstrates the creation of an SUP Mobile Deployment Package in SUP Unwired Workspace.

For the application SAP Ad Hoc Inventory, we can stick to the default options of the wizard and include allavailable MBOs (see Figure 14 and Figure 15).





© 2012 SAP AG 23

Figure 15 illustrates distribution of all MBOs into the Mobile Deployment Package.

After finishing the wizard, the deployment package is then available in the sub-folder “Deployment” of theproject.

Installation and Deployment

SUP Server Deployment

For the deployment, a few preparation steps are necessary:

- Creation of SUP security configuration

- Creation and enablement of SUP domain

- SUP application connection (Client – SUP)

- SUP connection pool (SUP – Backend)

- Deployment of SUP application package

SUP Security Configuration

In this documentation of the template application SAP In-Store Ad Hoc Inventory, we use the most simple

authentication scenario against the SUP server, to reduce setup complexity in the local environment. This isappropriate for testing and demo cases. In a productive scenario, this must be enhanced by a securityimplementation that fits the customer ‟s needs and environment. As well-documented (Developer Guide: Windows and Windows Mobile Object API Applications), anapplication can make use of username-password authentication, as well as use single-sign- on support(X.509 certificate).

You create a security configuration that does not require user authentication by simply not specifying adedicated implementation class (see Figure 16, Figure 17, and Figure 18).









© 2012 SAP AG 24

Figure 16 illustrates the creation of a new security configuration.

Figure 17 gives an overview of the newly created security configuration.

Figure 18 displays properties of the newly created security configuration.





© 2012 SAP AG 25

SUP Domain

Create the domain name “sapadhocinv” – this is hard-coded inside the application, to reduce deploymentcomplexity, so use exactly this value in this case.Choose the newly created security configuration and enable the SUP domain (see Figure 19, Figure 20, Figure 21, Figure 22, Figure 23 and Figure 24).

Figure 19 shows how to start the creation wizard for SUP domain.

Figure 20 illustrates the naming of the new SUP domain "sapadhocinv".





© 2012 SAP AG 26

Figure 21 shows the assignment of the security configuration to the new domain.

Figure 22 indicates how to enable the new domain.





© 2012 SAP AG 27

Figure 23 displays the confirmation of the enablement of the newly created domain.

Figure 24 shows an overview of all existing domains.

SUP Connection Pool

Next, we define the connection between the SUP server and the SAP ERP backend system (see Figure 25and Figure 26). An SUP connection pool entry can be shared by multiple application packages within one

SUP domain.

Figure 25 illustrates choosing "New" for the creation of a new SUP connection pool entry.





© 2012 SAP AG 29

Figure 28 shows the start screen of the deployment wizard, with 5 deployment steps listed.

Specify the two downloaded deployment descriptor files (see Figure 29), and enter the SUP domain„sapadhocinv ‟ and the newly created security configuration on the following screen (see Figure 30).

Figure 29 shows the specification of deployment descriptor files.





© 2012 SAP AG 30

Figure 30 shows the specification of the SUP domain and security configuration.

There is no role assignment designed for the application, so choose the „Next‟ button again (see Figure 31).

Figure 31 shows skipping the role assignment.

The embedded endpoint has to be exchanged by valid SUP connection to the deployment package (seeFigure 32).





© 2012 SAP AG 31

Figure 32 demonstrates the assignment of an SUP connection to all externally-facing MBOs.

In the last step, a summary is displayed (see Figure 33). Check again whether all externally-facing MBOs arelisted in the Endpoint Updates section.

Figure 33 summarizes the deployment wizard settings.





© 2012 SAP AG 32

Back in the packages view of SCC, the newly deployed application is displayed (see Figure 34).

Figure 34 displays the application package of SAP Ad Hoc Inventory.

After a reasonable synchronization time, which strongly depends on volume and connection bandwidth, youshould see entries in the cache group overview of the application (Figure 35).

Figure 35 illustrates the synchronized cache group entries that correspond to MBO items in SUP CDB.

SUP Application Connection

Before a mobile device may connect against the SUP server, an application connection has to be defined,which serves in the given application scenario as the entrance door to SUP (see Figure 36, Figure 37, Figure38, and Figure 39).

Figure 36 shows the registration of an application connection within SUP SCC.





© 2012 SAP AG 33

Figure 37 shows the properties of an application connection.

Figure 38 lists the not yet activated SUP application connection.

Figure 39 presents the activated SUP application connection.

This finishes the setup of the SUP server application component. All data is now available on the SUP serverand can be consumed by a mobile client. It will be updated according to the cache group settings.

Installation on Windows Mobile Device

Ensure that the mobile device is cradle-connected via Active Synch, or to the workplace environment.Download the Windows installer file under section Downloads. Execute the installation of the SAP Ad Hoc Inventory client application by double click (see Figure 40 andFigure 41).





© 2012 SAP AG 34

Figure 40 illustrates the deployment of the SAP In-Store Ad Hoc Inventory application, started from the workplace environment.





© 2012 SAP AG 35

Figure 41 gives an overview of the deployment of the SAP In-Store Ad Hoc Inventory application on a Windows Mobile device.





© 2012 SAP AG 36

Application Walkthrough

Setup

Start the application via Windows Start Menu as shown in Figure 42. At first startup, there is the opportunityfor a demo mode, which operates on embedded data.

Figure 42 illustrates the start screens of the SAP In-Store Ad Hoc Inventory application.

When you choose „Start‟, the application prompts a definition of connection settings. As no security handlinghas been specified, the password is not checked at all. Make sure to set the activation code to the onespecified for the SUP application connection (see Figure 43).

After a successful SUP server connection setup, the application requests inventory parameters, for example,the store ID (see Figure 44).





© 2012 SAP AG 37

Figure 43 shows the application connection settings for SUP server access.

Figure 44 shows the maintenance of inventory settings.

Counting

The inventory process offers two operation modes:





© 2012 SAP AG 39

Figure 45 shows example screens of SAP In-Store Ad Hoc Inventory on Windows Mobile.

Multiple entries for the same item are allowed and accumulated in a backend procedure.

The specified layout information is neither stored nor processed in the backend, and is therefore notavailable. It is merely a reminder for the person counting that this item is located in different places in thestore.





© 2012 SAP AG 42

Related Content

There is plenty of documentation and articles on SUP MBO architecture.

Sybase Unwired Platform Developer Center

Here is a selection of more general architecture documents:

SUP Concepts

Sybase Unwired Platform Version 2.1 - Architecture SUP 2.1.2 and 2.1.3 Architecture White Paper

Sybase Unwired Platform 2.1.2 Sizing Guide

Specific business examples and tutorials:

How To Implement a Simple Application using Sybase Unwired Platform 2.0

Windows Mobile Application Development using Custom Development - Sybase Unwired Platform 1.5.2

Appendix 1: Paths in SAP Easy Access Menu

Transaction WE20 (Partner Profile)

SAP menu Logistics Materials Management Foreign Trade/Customs Communication / Printing Communication / Printing Environment IDoc / EDI Basis Administration Partner Profile

Transaction WB03 (Plant) SAP menu Logistics Materials Management Purchasing Master Data Subsequent Settlement Vendor Rebate Arrangements Environment Condition / Arrangement Conditions: Sales Bonus Buy Environment

Material Environment Material Groups Environment Information System Environment Master Data Plant

http://scn.sap.com/community/developer-center/mobility-platform


http://scn.sap.com/docs/DOC-15248






















© 2012 SAP AG 43

Transaction WPER (POS Interface Monitor)

SAP menu Logistics Sales and Distribution Master Data Products Assortments Environment Assortment List POS Interface Monitor

Transaction WE05 (IDoc Lists)

SAP menu Logistics Materials Management Foreign Trade/Customs Communication Communication / Printing IDoc Lists

Transaction MI07 (Post Difference)

SAP menu Logistics Materials Management Physical Inventory Difference Post




Copyright

© Copyright 2012 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 SystemsIncorporated 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 ofCitrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.

Java is a registered trademark of Oracle Corporation.

JavaScript is a registered trademark of Oracle Corporation, 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 mentionedherein 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, andother Business Objects products and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks 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 documentserves 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 ("SAPGroup") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in theexpress warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting anadditional warranty.

sap in-store ad hoc inventory for windows mobile (an sup template application)

Documents