Mobysis integrated with SAP

-
The MSB Device Connector enables you to connect weighing systems or automatic racking systems, for example. In addition to traditional 1D bar codes, the use of 2D bar codes or RFID labels is becoming increasingly common in logistics. mobisys also supports these technologies on mobile devices, which means you can adjust your processes at any time and always be up to date.
  1. Goods receipt for purchase order
    • Using this standard transaction, you can post the receipt of the goods for a purchase order or for a scheduling agreement (movement type: 101).
  2. Transfer Posting from Plant to Plant
    • Using this standard transaction, you can perform a material transfer posting from one plant to another.
  3. Goods issue for order
    • Using this standard transaction, you can post or reverse a goods issue for an order.
  4. Stock putaway
    • This standard transaction lets you post stock putaways in a warehouse managed with WM.
  5. Stock transfer postings
    • This standard transaction lets you post stock putaways in a warehouse managed with WM.
  6. Picking and packing
    • Using this standard transaction, you can carry out document-free picking and packing for an SD delivery.
  7. Inventory
    • These standard transactions facilitate the entry and further processing of inventory count quantities in WM.

Mobisys Solution Builder (also referred to as "MSB"), an SAP-certified ABAP addon:
  • develop applications that can be executed on mobile end devices on the basis of the SAP NetWeaver Application Server and the corresponding SAP applications. All mobile applications are defined in the SAP system.

Installation 

  • MSB on systems with an SAP application
  • MSB on your own SAP NetWeaver Application Server (RFC, BAPI)

The MSB can also be configured as middleware if necessary. Data can then be exchanged with the SAP application either synchronously or asynchronously. Firewall with MSB on a proprietary NetWeaver Application Server.

Structure of an MSB application

An MSB application is subdivided into one or several transactions. Each transaction consists of one or several screens. On each screen, one or more components can be found.

An MSB application usually has a transaction called MAIN (you can also provide any other name for it). This is a type of menu transaction that contains only buttons that are linked to further transactions of the application.
  • Application
    • Name 
    • FG
    • Device type  (MSB client, screen size)
  • Transaction
    • FG
    • Screen (menu or standard)
      • Subsequent screen
      • Rows and columns 
      • Component
        • Label, Button, List box, Image, RFIT read, write, Data grid, Signature, Camera
      • Device dependency (layout, (X,Y))
  • Events - Action
  • Message 
  • Roles 

MSB Administration

Device management


Comments

Post a Comment