Modeling a Messaging BDoc Type 
Use
You need to model an mBDoc type to exchange data between the CRM server and other systems, such as CRM Online and R/3 backend systems.
The process of modeling an mBDoc type is different from the process of modeling a Mobile Application BDoc type or sBDoc type. This is because an mBDoc type does not contain mapping of segments to database tables.
In the mBDoc type, the container of business data is a complex ABAP Dictionary structure.
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.
In addition, you can create a BDoc type by using BDoc ® Create BDoc.
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 |
Dep. |
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 Messaging.
· The Mobile Application Processing Type group box is disabled because it is not applicable for mBDoc types.
· In an EBP system, when you model a new BDoc type, the BDoc Class and Mobile Application Processing Type group boxes are disabled. Therefore, you can now model only messaging BDoc types with the processing type as Standard. However, the processing type for existing messaging BDoc types is maintained.
5.
In the Related Data Type field under the General
Data group box, you can specify the ABAP Dictionary structure name that
serves as a container for business data. For details on how to create such
structures, see the 
ABAP Dictionary
documentation.
An mBDoc type does not contain any parameter information. Therefore, when you are modeling an mBDoc type, the Parameters tab is disabled.
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 Types.
8. Enter the transport request and choose Enter.
To create a transport request, choose Create request.
Result
You have modeled an mBDoc type. You can now proceed to create segments for the new mBDoc type. In addition, you can map the mBDoc type to a site type. For more information, see Mapping a BDoc Type to a Site Type.
See also: