To improve system performance, you can specify which objects are to be read for the object overview from the database. You can also limit the selected amount of data further by using the
Reduced Reading
indicator.
Example
You want to have an overview of the status of all orders with a particular order type. In this case you should select the
Order Header
object type.
You want additional information about partially released or confirmed operations (for instance, the operation status). In this case you must also select the
Operations
object type. The system then automatically selects the
Sequence
object type, because operations come below sequences in the hierarchy.
You can select/deselect the following database objects:
Production order |
Process order |
---|---|
Order headers |
Order headers |
Items |
Items |
Documented goods movement |
Documented goods movement |
Sequences |
‑‑ |
Operations (including suboperations) |
Operations (including phases and secondary resources) |
Components |
Components |
Confirmations (order, operation, suboperation) |
Confirmations (order, operation/phase, secondary resource) |
Production resources/tools |
‑‑ |
Trigger points |
‑‑ |
Capacities (operation, suboperation) |
Capacities (operation, secondary resource) |
Automatic goods movements (backflushing, automatic GR) |
Automatic goods movements (backflushing, automatic GR) |
Goods movements with errors (backflushing, automatic GR) |
Goods movements with errors (backflushing, automatic GR) |
Purchase requisitions (externally processed operations) |
Purchase requisitions (externally processed operations) |
Purchase orders (externally processed operations) |
Purchase orders (externally processed operations) |
Document links (order, operation) – only if the layout-based ALV display in used. |
‑‑ |
In an overall profile you define which objects are read from the database.
You can change the settings manually on the
Object Selection
tab page, on the initial screen or in the results list. In the results list, choose
Object Selection
or
.
The objects are stored in the database in a hierarchical structure. The order header is at the top of the hierarchy, followed by the order items and so on.
With regard to the selection of objects that are to be read from the database: To display an object, the object itself and all objects situated above it in the hierarchy are read .
Example
You want to generate a list of all components that are required for a particular group of orders. To be able to display components, the system has to read the relevant order headers, operation sequences, operations and components. When you select the
Components
object, the system automatically selects all other objects that are required for the selection.