Page Comparison

To adjust an existing view, it is recommended to copy the template view into a new form within the customer name space (Y* or Z*). Otherwise a product delivery can and will override your changes. The name of this new form must be entered as a parameter in the corresponding widget (e.g. CUSTOM_VIEW_* for Simple Data Widget or CUSTOM_VIEW_DRAW for Document Data Widget). For the corresponding customizing settings, refer to the corresponding customizing manual.

All structural adjustments to the form are done always in the view structure widget.

Options to adjust

Important forms are:

...

To remove sections or fields from a form, it is recommended to hide the respective elements, instead of removing it. This way, it is possible to show the fields again, in case they are needed. Fields can be removed by setting their visible attribute to not visible or via the context menu function hide element. The function hide element is also available on row level. In this case, all elements of the row will be set to not visible. Via multi select, it is possible hide multiple elements at once.

If an element shall be removed from the form, you can delete it via the context function delete element or by pressing the delete button while the elements are selected.

...

Elements can be reordered in the view structure widget by dragging the elements, which shall be reordered, to their new destination. The dragged elements are moved by the following rules:

• If dropped on a non structured element, the elements are moved directly before the element on which they were dropped.
• If dropped on a row, the elements are moved at the end of the row.
• If dropped on a container element, a popup for selecting one of the following options is provided:
  • Move before this element - all elements are moved directly before the element on which they were dropped.
  • Move as sub objects(s) (at the end) - all elements will be moved as last objects to the container.
• Rows behave like any elements, with the exception that they move all elements of the row at once.

...

New fields can be added via dragging the fields from the widget available Elements and drop them at the desired location in the view structure widget.
The available Elements widget is structured by the technical content providers (e.g. MARA for material or DRAW for document). It is possible to drag and drop multiple elements from the available Elements widget to one target element in the view structure widget at a time. In this case, one or multiple elements are dragged, they will be added to the view using the following rules:

• The system tries to determine the correct order of the fields (first label, second data field, third description field)
• All data fields are added as text fields.
• If dropped on a non structured element, the elements are inserted directly before the element on which they were dropped.
• If dropped on a row, a popup for selecting one of the following options is provided:
  • Insert as new row at this position - all elements are added as a new row directly before the row on which they were dropped
  • Insert as sub objects(s) (at the end) - all elements will be added as last objects to the row.
• If dropped on a container element, a popup for selecting one of the following options is provided:
  • Insert before this element - all elements are inserted directly before the element on which they were dropped
  • Insert as sub objects(s) (at the end) - all elements will be added as last objects to the container

If a data field shall display a different type, the type can be changed afterwards via the context menu function Change type by selecting the desired type.

...

Due to their structural difference, structuring data in simple data (tree) forms and screen forms is slightly different. Simple data forms structure the content usually as folder in the tree where a screen form may structure data within areas, groups or trays.

...

If a new folder shall be added to the Simple Data form, a container element from the CVO types of the available elements widget folder needs to be dragged to the location where the folder shall be added. The display / behaviour can be influenced by the following attributes:

...

Expanded

...

Defines if the Folder is expanded when the form is displayed initially

...

Container layout

...

• Flow - all fields are displayed (with their respective width) directly behind one another.
• Fixed flow - the length of the first element (usually the label field) among all lines is calculated, so that the first element of all rows has an identical length
• all other layouts are not supported in Simple Data. If used, Flow layout is used instead.

...

Load on expand

...

Load on expand can be used to reduce the initial data loading for the content. Data below the node is not transported to the GUI and, in case this is supported by the feeder, the data is loaded only when the node is expanded.

...

Title

...

Defines the title of the Folder in the Simple Data Tree. It is recommended to use One of the supported Text Symbols for internationalization.

...

Auto. hide when empty

...

The Folder is not displayed, if no visible sub element is below. This can be used to hide folder, which are not relevant for the current Object (e.g. data not present at the current object) or the user has no access to the corresponding data.

All other attributes are ignored in case the ProFramework form is displayed as a Simple Data widget.

...

Structuring Data in a Screen Form is more complex than in a Simple Data form. Depending on the attributes set, the container is rendered in a different way. A new container can be added by dragging a container element from the available elements widget (folder CVO types) to the desired location in the form. The following attributes are relevant:

...

Container Type

...

• Layout container - generates a visible delimited area on the screen usually using margins in any direction
• Dummy container - generates an invisible container which may be used to group content which shall be managed together without a representation on the screen. e.g. a column based layout may use dummy container for each column.

...

Expandable

...

If the container is set to expandable, the form will generate a tray like (expandable) group

...

Expanded

...

Only applicable when the container is set to expandable. In this case, the default state (initially expanded or initially collapsed) is defined via this attribute.

...

Title

...

An expandable container must have a title, a non expandable container may have a title. If it has a title, the container is rendered as a group element, otherwise it is rendered with no further visible elements

...

Expand locked

...

Only applicable to expandable containers. If the expand is locked on a container, it is rendered as a tray without the possibility to expand / collapse the container.

...

Container layout

...

• Flow - all fields are displayed (with their respective width) directly behind one another.
• Fixed flow - The firs element is displayed with a fix length. Usually used for fields with labels in a row based manner.
• Grid and Grid Lines - Elements are displayed in a grid style. For each Column in the layout a column element has to be provided in the container declaring the width of the column. A new row is started when the amount of elements is larger than the column count or when the Insert in new line attribute is set to true. It is not possible to place more than one element into a cell. If more than one element needs to be displayed in a cell, a dummy container may be used. Grid Lines layout displays a separator (line) between each row.
• Dynamic columns - May only be used with containers as sub elements. The layout tries to display the containers in two columns when the available screen width allows this. If the screen is to small for displaying two columns side by side, they are displayed below one another.
• all other Layouts may not be used

All other attributes are ignored in case the ProFramework form is displayed as a Screen widget.

...

To get customer specific data into a CVE Form the corresponding feeder needs to be enhanced or a new Feeder must be implemented. A couple of the Feeders include a simple technique for bringing customer specific fields from the main object table (e.g. MARA or DRAW) into the Form. The following sections describe for some standard feeders how to add existing customer specific fields.

...

First of all, the business object data structures must be enhanced. Most business objects have an external and an internal view on the Business Data. Due to this fact, it is required that both structures (DB and External) must be enhanced in the same way. Please refer to the corresponding OBJ Integration & Enhancement document for more Information.
Some Business Objects (MARA, MARC and MVKE) provide additionally to the MAIN data the so called EXT data (extended data). These structure consists of all fields relevant for the business object in case of display / edit, but not relevant for basic operations.

Preconditions
The corresponding SAP Standard tables are already enhanced with the customer specific fields which shall be added to the form.
Enhancing the business Object main data structures
If not already done, append a new customer specific structure to both structures (internal and external view) and add the field to both. Make sure that the field is in the same position and that you used the same data element in both structures.

Generating Meta Data
The fields, which are provided by the CVE Feeders are stored in the database due to performance reasons. Therefore the meta data must be regenerated after the structure has been changed (e.g. fields or relations have been added or removed or the field definition has been changed). Run the transaction /PCH/CFW_METAGEN after all required fields are added to all objects.
Locating the new Elements
After the meta data generation has been finished, the new Elements are available. You can find the element below the corresponding feeder. E.g. if the Business Object MARA has been enhanced, you'll find the fields below the Feeder MARA. If the CVE form designer was already open before the new fields have been added, it may be required to reload the available CVE elements section. Normally CVE Feeder generate element names the following way: <OBJECT_TYPE>_<Fieldname used in the external view> (e.g. MARA_MATERIAL_NUMBER). The label has the suffix _LBL and, if available, the Description has the suffix _DESC.

...

For each material view, a separate business object and a separate feeder is implemented which supports the enhancement of the primary object data (data of the primary table). Currently the following views are supported:

• MARA (client specific material master data)
• MARC (plant specific material master data)
• MVKE (sales & distribution channel specific material master data)
• MARD (storage data per plant) - view only
• MBEW (valuation data) - view only
• MLGN (material data for warehouse storage number) - view only
• MLGT (material data for warehouse storage type) - view only

List of relevant Business object structures

...