Modeling a Synchronization or Mobile Application BDoc Type 

Use

You need to model an sBDoc type to exchange data between the consolidated database (on the CRM server) and the user database (on the mobile client). If you need to exchange data between CRM server applications, you need to map the sBDoc type to an mBDoc type.

·         You can map more than one sBDoc type to an mBDoc type. However, you can define this mapping only when modeling a new sBDoc type.

·         To map the sBDoc type to an mBDoc type, one validation service and two mapping services are required. For more information, see Creating Interfaces for New BDoc Types in the message flow documentation.

You need to model a Mobile Application BDoc type to read data from the user database on the mobile client.

Mobile Application BDoc types are used only in the mobile client.

Procedure

...

       1.      Log on to the CRM server and choose Architecture and Technology ® Middleware ® Development ® Meta Object Modeling ® BDoc Modeler.

The CRM BDoc Modeler screen appears.

       2.      Choose .

The Attributes, BDoc Overview, and Parameters tabs appear.

       3.      In the BDoc Identity group box, enter the following details:

Field name	Description	Req./Opt./Dep.	User action and values	Comment
Name	Indicates the name of the BDoc type	Req.	Enter a name for the BDoc type. For information on the naming convention for BDoc types, see Namespace.	The name of the BDoc type must not exceed 14 characters.
Short Name	Indicates the short name of the BDoc type	Req.	This field is read-only.	This field is automatically populated with the name of the BDoc type. Therefore, the name of the BDoc type is also the short name of the BDoc type.
Description	Indicates the description of the BDoc type	Opt.	Enter a description for the BDoc type.

       4.      In the BDoc Class group box, select the required BDoc class.

       5.      In the Mobile Application Processing Type group box, select the required processing type.

In the General Data group box, you can specify the name of the mapped mBDoc type only if you select the Synchronization (Write) BDoc class.

       6.      Save the BDoc type.

The Create Object Directory Entry dialog box appears.

       7.      Enter the name of the transportable package in the Package field and choose Enter.

The Prompt for transportable Workbench request dialog box appears.

To save the BDoc type locally, choose Local object. In such a case, the BDoc type is part of the $TMP package and is not transported. However, at a later point of time, to transport the BDoc type, you can assign the locally saved BDoc type to a transportable package. For more information, see Processing BDoc Type.

       8.      Enter the transport request and choose Enter.

To create a transport request, choose Create request.

Result

You have modeled a synchronization or Mobile Application BDoc type. After you model the BDoc type, you need to create segments, map segment fields to table fields, and add parameters if required. In addition, you can map the BDoc type to a site type. For more information, see Mapping a BDoc Type to a Site Type.