SAP Business Suite

To create a PDM with support for features specific to the SAP Business Suite, select the DBMS on which your installation is running in the DBMS field of the New Model dialog, click OK to create an empty PDM, and then select Start of the navigation path Tools Next navigation step SAP Business Suite Import SAP Business Suite Data Dictionary End of the navigation path . To view these extensions to the PowerDesigner metamodel in the Resource Editor, select Model Extensions , select the SAP Business Suite extension, click the Properties tool, and expand the Profile node.

PowerDesigner supports importing any recent version of SAP® Business Suite.

The following sections list the extensions provided for SAP Business Suite.

Model

The following extensions are available on the Data Dictionary tab:

Name	Description
Host name	Specifies the host name or IP address of the server on which the Business Suite installation is running. Scripting name: `HostName`
User name	Specifies the user who connects to the Business Suite server. Scripting name: `UserName`

Name

Description

Host name

Specifies the host name or IP address of the server on which the Business Suite installation is running.

Scripting name: HostName

User name

Specifies the user who connects to the Business Suite server.

Scripting name: UserName

ABAP Components

ABAP components are based on standard PowerDesigner packages with a ABAP Component stereotype. The following extensions are available on the Data Dictionary tab:

Name	Description
Created by	Specifies the user who created the object and when the change was made. Scripting name: `CreatedBy, CreatedOnDate, CreatedOnTime`
Changed by	Specifies the user who last changed the object and when the change was made. Scripting name: `ChangedBy, ChangedOnDate, ChangedOnTime`
Parent	Specifies the ABAP component that is the parent of the present component. Scripting name: `Parent`
Customized by / Release notes by	Specify the users who customized the component and wrote the release notes for the customization. Scripting name: `CustomizingResponsible, ReleaseNoteResponsible`
Released	Provides release information about the component. Scripting name: `Released`
Support web / desktop	Specify that the component can be displayed in the SAP NetWeaver Portal and in the desktop NetWeaver client. Scripting name: `SupportWeb, SupportDesktop`
Visible	Specifies that the component should be visible to users. Scripting name: `Visible`

ABAP Packages

ABAP packages are based on standard PowerDesigner packages with an ABAP Package stereotype. The following extensions are available on the Data Dictionary tab:

Name	Description
Created by	Specifies the user who create the object and when it was created. Scripting name: `CreatedBy, CreatedOnDate, CreatedOnTime`
Changed by	Specifies the user who last changed the object and when the change was made. Scripting name: `ChangedBy, ChangedOnDate`
Parent	Specifies the ABAP component or package that is the parent of the package. Scripting name: `ApplicationComponent`
Software component	Specifies the software component to which the package is a support package. Scripting name: `SoftwareComponent`
Main package	Specifies whether the package is a: <empty> - Development Package X - Main Package, which does not contain any development elements itself; and provides a structure for its children S - Structure Package Scripting name: `MainPackage`
Namespace	Specifies a deprecated method for organizing package structures. Scripting name: `Namespace`
Owner	Specifies the user currently responsible for the package. Scripting name: `Owner`

Tables/Structures

The following extensions are available on the Data Dictionary tab:

Name	Description
Changed by	Specifies the user who last changed the object and when the change was made. Scripting name: `ChangedBy, ChangedOnDate, ChangedOnTime`
Parent package	Specifies the ABAP package that is the parent of the table or structure. Scripting name: `PackageCode`
Physical table	Specifies the database table on which the table or structure is based. Scripting name: `PhysicalTableCode`
Is extended	Specifies that the table contains extensions. Scripting name: `IsExtended`

Columns (Fields)

Business Suite fields are represented as columns in PowerDesigner. The following extensions are available on the Data Dictionary tab:

Name	Description
Field type	Specifies whether the field is: <Empty> - Built-in type E - Data element S - Structure L - Table type Scripting name: `FieldType`
Domain	Specifies the domain attached to the column. Scripting name: `Domain`
ABAP data type	Specifies the data type used by the runtime environment: B, S, I - 1-byte, 2-byte, or 4-byte integer C, N, B, F, G - Character, numerical, binary, float, or string D, T - Date, or time X, Y - Fixed or variable length raw Scripting name: `ABAPDataType`
Data dictionary data type	Specifies the data type used in the Dictionary. Scripting name: DataDictionaryDataType
Data element	Specifies the data element attached to the field, if of type E. Scripting name: `DataElement`
Include structure	Specifies the included structure attached to the field, if of type S. Scripting name: `IncludeStructure`
Lookup table	Specifies that lookup table from which to draw key values, if of type T. Scripting name: `LookupTable`
Reference field / table	For numerical or currency columns, specify the reference field and table. Scripting name: `ReferenceField, ReferenceTable`
Input help	Specifies the origin of input help: <empty> - No input help exists X - Explicit search help attachment to field P - Input help implemented with check table D - Explicit search help attachment to data element F - Input help with fixed values T - Input help based on data type Scripting name: `InputHelp`

Indexes

The following extensions are available on the Data Dictionary tab:

Name	Description
Changed by	Specifies the user who last changed the object and when the change was made. Scripting name: `ChangedBy, ChangedOnDate, ChangedOnTime`
DB index name	Specifies the associated database index name. Scripting name: `DBIndexName`
DB include exclude	Specifies that a list of database systems is used as: I - List of inclusions: create index on these DB systems. E - List of exclusions: do not create index on these DB systems. Scripting name: `DBIncludeExclude`
List of database systems 1-4	Specify lists of database systems for inclusion or exclusion by the index. Scripting name: `DBSYSSEL1, DBSYSSEL2, DBSYSSEL3, DBSYSSEL4`
Extension index	Specifies that the index is an extension index. Scripting name: `IsExtensionIndex`
Status	Specifies the status of the index in the database: <empty> - Create on database. O - Do not create on database. D - Create on database depending on DB Scripting name: `Status`

Data Elements

Data elements are based on PowerDesigner extended objects with a Data Element stereotype. The following extensions are available on the Data Dictionary tab:

Name	Description
Changed by	Specifies the user who last changed the object and when the change was made. Scripting name: `ChangedBy, ChangedOnDate, ChangedOnTime`
Package code	Specifies the package containing the data element. Scripting name: `PackageCode`
Default name	Specifies the default name for components using the data element. Scripting name: `DefaultName`
Original language	Specifies the language in which the data element was defined. Scripting name: `OriginalLanguage`
Data dictionary data type	Specifies the data type of the column in terms of the ABAP Dictionary. Scripting name: `DataDictionaryDataType, DataType`
Length / Output length	Specifies the supported number of characters and the number that can be displayed in ABAP forms. Scripting name: `OutputLength, Length`
Precision	Specifies the supported number of decimal places. Scripting name: `Precision`
Reference kind	Specifies the category of dictionary type: <empty> - Direct type E - Elementary type S - Structured type L - Table type R - Reference type D - Domain Scripting name: `ReferenceKind`
Conversion routine	Specifies function modules that are executed when values are input to and displayed in the ABAP screen field. Scripting name: `ConversionRoutine`
Value table	Specifies that the permitted values for the data element are PK values of the selected table. Scripting name: `ValueTable`
Signed	Specifies that negative values are supported. Scripting name: `Signed`
Lowercase	Specifies that lowercase letters are supported. Scripting name: `Lowercase`
Fixed values	Specifies that permitted values are limited to those specified. Scripting name: `FixedValues`

Domains

The following extensions are available on the Data Dictionary tab:

Name	Description
Changed by	Specifies the user who last changed the object and when the change was made. Scripting name: `ChangedBy, ChangedOnDate, ChangedOnTime`
Package code	Specifies the package containing the domain. Scripting name: `PackageCode`
Data dictionary data type	Specifies the data type of the column in terms of the ABAP Dictionary. Scripting name: `DataDictionaryDataType`
Base domain	Specifies the domain that the present domain extends. Scripting name: `BaseDomain`
Value table	Specifies that the permitted values for the domain are PK values of the selected table. Scripting name: `ValueTable`
Conversion routine	Specifies function modules that are executed when values are input to and displayed in the ABAP screen field. Scripting name: `ConversionRoutine`
Fixed values	Specifies that permitted values are limited to those specified. Scripting name: `FixedValues`
Signed	Specifies that negative values are supported. Scripting name: `Signed`

Views

The following extensions are available on the Data Dictionary tab:

Name	Description
Changed by	Specifies the user who last changed the object and when the change was made. Scripting name: `ChangedBy, ChangedOnDate, ChangedOnTime`
Root table code	Specifies the primary table of an aggregate. Scripting name: `RootTableCode`
View type	Specifies that the view is a: H - Help view D - Database view P - Projection view S - Structure view, data selection not possible C - Maintenance view E - Entity view (no longer supported) V - View variant A - Append view Scripting name: `ViewType`
Delivery class	Specifies that the delivery class of the view is: A - Application table C - Customer table, maintained by customer L - Table for storing temporary data G - Customer table, SAP can add rows E - Control table S - System table, maintained by SAP W - System table Scripting name: `DeliveryClass`
Maintenance status	Specifies the maintenance status of the view: <empty> - Modifiable R - Read only U - Read and change M - Time dependent view Scripting name: `MaintenanceStatus`

View Columns (View Fields)

The following extensions are available on the Data Dictionary tab:

Name	Description
ABAP form name	Specifies the field's name in ABAP forms. Scripting name: `ABAPFormName`
Base table / field	Specify the table and field from which the field are drawn. Scripting name: `BaseTable, BaseField`
Data element	Specifies the data element attached to the field. Scripting name: `DataElement`
Is key	Specifies that the field belongs to a key area. Scripting name: `IsKey`
Lock mode	Specifies the lock mode for the field: E - Write lock S - Read lock X - Exclusive lock Scripting name: `LockMode`
Maintenance status	Specifies the maintenance status of the field: <empty> - View is available as normal R - View field can only be read S - View field is used to form subsets H - View field is not transferred to the maintenance screens Scripting name: `MaintenanceStatus`