SAP ABAP Data Element OFFLINE_MAPPING (Data Mapping Mobile Engine <-> R/3)
Hierarchy
☛ SAP_ABA (Software Component) Cross-Application Component
   ⤷ CA-TS (Application Component) Time Sheet
     ⤷ BACTEXP (Package) Functions for Offline Travel and Time Sheet Manager
Basic Data
Data Element OFFLINE_MAPPING
Short Description Data Mapping Mobile Engine <-> R/3  
Data Type
Category of Dictionary Type     Direct Type Entry
Type of Object Referenced     No Information
Domain / Name of Reference Type      
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 0   
Medium 0   
Long 0   
Heading 0   
Documentation

Definition

Data Transfers between offline applications and the R/3 System take place, via the Mobile Engine, using Inbound and Outbound Containers.

These containers have the structure BWAFCONT with the fields:

FIELDNAME     LINENUMBER     FIELDVALUE

EMPLOYEENUMBER     0     00002932

The aim is to map the inbound container data to specific BAPI parameters and to prepare the outbound container data for use in the offline application.

In order to standardize this process, the data in the containers is structured using a specific format. This format splits the parameter (field, structure or internal table) into three components.

Example: Table Parameter EXPENSE_TYPES for BADI_TRIP_GET_OPTIONS

  1. Meta Parameter

Contains     Example

- Parameter Number     01

- Parameter Name     EXPENSE_TYPES

- DDIC Type for Parameter     BAPITR706B

- Parameter Category     T = Table

    R = Record/Structure

    F = Field

  1. Meta Detail

- Parameter Number     01

- Field Number     001

- Field Name     PR04_SORT

- Length     1

- Number of Decimal Places     0

- Field Type     CHAR

- Parameter Number     01

- Field Number     002

- Field Name     EXP_TYPE

- Length     4

- Number of Decimal Places     0

- Field Type     CHAR

  1. Generic Record

- Parameter Number     01

- Line Number     00001

- Field Numbe     001

- Field Value     A

- Parameter Number     01

- Line Number     00001

- Field Number     002

- Field Value     HOTL

- Parameter Number     01

- Line Number     00002

- Field Number     001

- Field Value     B

- Parameternummer     01

- Zeilennummer     00002

- Feldnummer     002

- Feldwert     TAXI

An example container entry would, therefore be:

FIELDNAME     LINENUMBER     FIELDVALUE

METAPARAMETER     1     01 EXPENSE_TYPES BAPITR706B T

METADETAIL     1     01 001 PR04_SORT 1 0 CHAR

METADETAIL     1     01 002 EXP_TYPE 4 0 CHAR

GENERICRECORD     1     01 00001 001 A
GENERICRECORD     1     01 00001 002 HOTL
GENERICRECORD     1     01 00002 001 B
GENERICRECORD     1     01 00002 002 TAXI

The transformation of mobile engine data into R/3 Data takes place using class:

CL_OFFLINE_TRANSFORM_INBOUND

The transformation of R/3 data into mobile engine data takes place using class:

CL_OFFLINE_TRANSFORM_OUTBOUND

History
Last changed by/on SAP  20020827 
SAP Release Created in 620