!--a11y-->
What's New in This Release 
The following table lists the enhancements in the CRM BDoc Modeler.
|
Enhancement |
Description |
|
Short name of the BDoc type |
The Short Name field is now read-only and is automatically populated with the name of the BDoc type. |
|
Filter screen |
The filter screen is enhanced to allow filtering based on packages. In addition, in an Enterprise Buyer Professional (EBP) system, you cannot filter based on the BDoc class, as the BDoc Class group box is removed from the filter screen. |
|
BDoc type details |
A new tab, Attributes, is added to display the following information: · The date, time, and person who last modified the BDoc type. · The date, time, and person who last released the BDoc type. · The name and description of the package that contains the BDoc type. · The original language in which the BDoc type was modeled. |
|
Namespace |
In the previous release, customers were allowed to model BDoc types only in the Z namespace. However, customers can now register their own namespaces. For more information, see Namespace. |
|
Object directory entry for a BDoc type |
In the previous release, BDoc types did not have an entry in the object directory. Now, when you model a BDoc type, an entry is created in the object directory. For more information, see Object Directory Entry for a BDoc Type. |
|
Object directory entry |
A new menu option added to the context menu of a BDoc type. It allows you to view the object directory entry for a BDoc type. For more information, see Processing BDoc Types. |
|
Write transport entry |
A new menu option added to the context menu of a BDoc type. It allows you to change the transport request of a BDoc type that is locked in another transport request. For more information, see Processing BDoc Types. |
|
Requests (Organizer) |
A new menu option added to the Utilities menu that invokes the Transport Organizer. It allows you to organize your transport requests. |