use of msb standard transactions v1 en

Version: 1.0

Date: March 19, 2012

Mobisys GmbH

Altrottstr. 26 D-69190 Walldorf

www.mobisys.de

Documentation

Use of MSB Standard Transactions

Use, Installation, Configuration, Testing

Documentation Use of MSB Standard Transactions

Version 1.0, Date: March 19, 2012 Page 2

Copyright Copyright 2011 Mobisys GmbH. 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 Mobisys GmbH. The information contained herein may be changed without prior notice.

Some software products marketed by Mobisys GmbH and its distributors contain proprietary software components of other software vendors.

SAP, SAP NetWeaver, SAP ERP, ABAP, BAPI and other SAP products and services referred to in this document, as well as the corresponding logos, are registered trademarks of SAP AG in Germany or other countries. Microsoft, Windows, and other Microsoft products and services mentioned in this document are registered trademarks of Microsoft Corporation.

Citrix and Citrix products and services mentioned in this document, as well as the corresponding logos, are registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML und 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.

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. Mobisys is not liable for errors or omissions with respect to this publication. The only warranties for Mobisys 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.



Table of Contents 1 Introduction .................................................................................................................... 4 2 Installation ...................................................................................................................... 4

2.1 System prerequisites ............................................................................................... 4 2.2 Import ...................................................................................................................... 4

3 Configuration of the MSB ............................................................................................... 5 3.1 Maintain basic settings of the MSB .......................................................................... 5 3.2 Workarea management Define scheme ............................................................... 5 3.3 Workarea management Define workarea ............................................................. 6

3.3.1 MST_LGNUM................................................................................................... 6 3.3.2 MST_WERKS .................................................................................................. 6 3.3.3 MST_PRINT ..................................................................................................... 7

3.4 Workarea management, assignment of user to workarea ........................................ 7 3.5 Configuration table /MSBSTD/CONTROL ............................................................... 8 3.6 Device management ............................................................................................... 8

4 Configuration of the MSB Client ....................................................................................10 4.1 TCP/IP configuration ..............................................................................................10 4.2 System configuration ..............................................................................................10

5 Testing ..........................................................................................................................11 6 Embedding MST Transactions in Your Applications ......................................................12 7 Notes .............................................................................................................................13



1 Introduction MSB standard transactions cover frequently used processes in various application areas and can either be used productively as-is with very little configuration effort, or as a template for your own projects, where they can be enhanced and adapted to your specific needs. In the following, the configuration, structure and functioning of MSB standard transactions are described.

2 Installation MSB standard transactions are delivered as transports. These must be imported into your

SAP system using the SAP Transport Management System (SAP transaction STMS).

Technically, MSB standard transactions are made up of the MSB application and its screens and function modules on the one hand, and of the function groups and other objects in the ERP system. The objects for the MSB and for the ERP system are delivered in separate transport requests. Depending on whether the MSB is installed in a system that is separate from the ERP system (for further information, see the MSB documentation itself), the transport requests are imported into one system or into two different systems.

2.1 System prerequisites

For the MSB transports, the MSB must be installed in your system with one of the following releases and support package levels, so that you can use the standard transactions. If necessary, you can request the following support packages if they are missing: Menu path: System -> Status -> Component information

MOBISYS MSB_0360 0005

MSBDEVL MSB_DEV360 0003

The MSB itself can be used with an SAP release >= Rel. 620.

2.2 Import

The transports are imported into the destination system for the MSB and ERP with SAP transaction STMS.

Note: If the MSB transaction was already installed in this system and is to be replaced by a newer version, all the objects of the transport order will be overwritten and any changes made until then will be lost. If you want to make changes to the MSB standard transactions and make



use of future mobisys enhancements and corrections, these should be made using a copy of the MSB transaction in question.

3 Configuration of the MSB You must make the following configuration settings in the MSB (transaction

/MOBISYS/MSB_ADMIN).

3.1 Maintain basic settings of the MSB

Under the menu path: MSB Administration > MSB Basic Settings -> Maintain, you access the table /MOBISYS/MSBSETT. For the parameter MSB_NAMESPACE_MST, you must enter the parameter value

(namespace) /MSBSTD/ for the MSB standard transactions:

3.2 Workarea management Define scheme

Various MSB standard transactions use workareas. Menu path: MSB Administration > Workarea Management -> Define Scheme With the transports, three new schemes are created for MSB workarea management. For these, you must carry out further configuration steps:



3.3 Workarea management Define workarea

Menu path: MSB Administration > Workarea Management -> Define Workarea. For these three new schemes, you must create new workareas.

3.3.1 MST_LGNUM

Here you must create at least one workarea. The name of the workarea is user-defined.

3.3.2 MST_WERKS

Here you must create at least one workarea. The name of the workarea is user-defined.



3.3.3 MST_PRINT

Here you only have to create a workarea if you are using a standard transaction that also involves printing (for example, 116 Print Goods Receipt Labels).

3.4 Workarea management, assignment of user to workarea

Menu path: MSB Administration > Workarea management -> Assignment User Workarea For the MSB users, you have to maintain the assignment to the newly created workareas as follows:



3.5 Configuration table /MSBSTD/CONTROL

The configuration of a standard transaction is carried out in table /MSBSTD/CONTROL

(maintenance view transaction SM30).

Via this table, you can adapt some areas of the corresponding standard transaction to your individual needs. For this, a maintenance view is also delivered. You can get further information in the documentation of the corresponding Mobisys transaction.

3.6 Device management

Please note that for the application MST, you must enter the device type MSB CLIENT 240x320 as the default device type in MSB Device Type Management.

For this reason, you must ensure that this device type is assigned to the corresponding mobile devices in MSB Device Management.



In the case of a mobile device using a different device type (for example, the MOBISYS CE CLIENT), the following error message is displayed after logging on:



4 Configuration of the MSB Client You have to make the following configuration settings in the MSB Client:

4.1 TCP/IP configuration

Please check the IP address and the port.

4.2 System configuration

Check the entries for the application, the service and the shortcode.



5 Testing The MST application begins with a main menu, through which you can navigate to the desired transaction (here, for example, it is 111 Goods Receipt).

Alternatively, you can also enter the three-character transaction number in the menu, in order to get directly to the transaction.



6 Embedding MST transactions in your applications The delivered transactions of the MST application should preferably not be changed. We recommend that you copy the individual MST transactions to your own application. In this way, changes are not overwritten, in the case that a correction request needs to be imported for the MST application. In order to copy transactions and screens, you should use the report

/MOBISYS/MSB_COPY_APPL. In this report, you enter the start and target application, the start

and target transactions and optionally, the start and target screens. Then, the screen information and/or the contents of the PAI/PBO function modules are copied in table form. If the coding is copied, the new function modules will be created automatically using the source code. Please note that the definitions of sub-programs and variables that are used globally in function groups must be copied manually.



7 Notes

Copyright1 Introduction2 Installation2.1 System prerequisites2.2 Import

3 Configuration of the MSB3.1 Maintain basic settings of the MSB3.2 Workarea management Define scheme3.3 Workarea management Define workarea3.3.1 MST_LGNUM3.3.2 MST_WERKS3.3.3 MST_PRINT

3.4 Workarea management, assignment of user to workarea3.5 Configuration table /MSBSTD/CONTROL3.6 Device management

4 Configuration of the MSB Client4.1 TCP/IP configuration4.2 System configuration

5 Testing6 Embedding MST transactions in your applications7 Notes

use of msb standard transactions v1 en

Documents