Ansicht
Dokumentation

LGEBS42 - Maintain Selection Profile

CL_GUI_FRONTEND_SERVICES - Frontend Services   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

In this activity, you can define selection profiles to specify status combinations for selecting objects (for example, orders or operations). A selection profile is useful if you repeatedly select a large number of objects based on the same selection conditions (for example, orders to print shop papers for collective release or to create order valuations).

The selection conditions are evaluated top-down and the following rules apply:

• Several lines following one another that are linked by an OR are combined and evaluated together. At least one selection condition must be fulfilled in the block.

• AND links blocks or individual conditions. All the blocks or individual conditions linked by AND must be fulfilled. An order is no longer part of the evaluation when a block or individual condition is not fulfilled. This means that with every newly inserted AND,a bracket is inserted around the preceding expressions (conjunctive normal form). To select the desired status combinations, the selection conditions must be reformatted.

You want to define a selection profile in which orders with the following status combinations are selected:

• REL (released)

• CRTD UND MACM (created and material committed)

To do this, formulate:

REL OR (CRTD AND MACM)

But the system interprets:

(REL OR CRTD) AND MACM

Orders with the following status combinations are selected:

• REL AND MACM

• CRTD AND MACM

Therefore, the original formulation must be reformulated by "multiplying out" to:

(REL OR CRTD) AND (REL OR MACM)

You can also define the state of a status based on which of the following options is selected:

• If you select the "active" state, the system searches for objects where the status is currently active.

• If you select the "inactive" state, the system searches for objects where the status is currently inactive.

• If you select the "never active" state, the system searches for orders where the status was never active.

The following is an example of a selection profile that should select all released orders with a missing material or a missing PRT.

link status state

REL (released) active

AND MMAT (missing material availability) active

OR MPRT (missing PRT availability) active

The selection is carried out in tthe following way:

1. All released operations ( orders with the active status "REL") are selected.
2. From this group, the system selects all the orders with missing material or PRT availability (orders with the active status of "MMAT" or "PRT").

All the orders are selected with the following status combinations:

• RELEASED and MMAT

• RELEASED and MPRT

• RELEASED and MMAT and MPRT

In specific cases, you can use the "not" indicator to reduce the effort required to maintain selection conditions. Many status conditions can be represented more simply by setting the indicator to "not".

Selection conditions without the "not" indicator:

link not state

_ inactive

OR _ never active

The same selection condition with the "not" indicator:

link not state

X inactive

For performance reasons, conditions that strictly imit the selection should be placed at the beginning of the selection profile.

You can enter system status and user status in a selection profile. To select objects based on a user status, enter the appropriate status profile.

If you maintained a status profile in the status selection profile, assign the status profile to all objects. Selection is restricted by the status selection profile only if you assigned the status profile to the objects. If you enter a system status, in addition to entering a status profile, the system ignores it unless it has been assigned to the status profile.

The status profile is assigned to the objects using the:

• Project profile for the project definition and the WBS elements

• Network type for the network header and the activities

If a selection profile has been created in a language, it can be used in all languages defined in the system. If user statuses are defined in a selection profile, ensure that the user statuses are translated in the corresponding status profile. If no translation exists, enter the user status in the language in which it was created.

Define your own selection profiles if necessary.

Vendor Master (General Section)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 5562 Date: 20240523 Time: 201348     sap01-206 ( 84 ms )