Determining Issues The next issue or an additional issue can be determined using
determination modules
and
check modules
. The framework component
Determine Additional Issue
also contains a
number module
, which contains the maximum number of additional issues that can be delivered to a customer.
Example
For example, a check module can determine whether a customer has already purchased an issue from their customer history. If this is the case, they do not receive the issue again.
You might use another check module to ensure that a customer only receives issues that do not exceed their credit limit.
The determination and check modules, as well as the number module, are contained in the strategy you define in Customizing for the media product master:
Framework component |
Path in Implementation Guide |
|---|---|
Determine next issue |
|
Determine additional issue |
|
Execute additional processes |
|
See also: Framework
You can define a maximum of five determination modules, and check modules are optional (if you use them, you can also define a maximum of five). The following graphic illustrates the issue determination process:

Issue determination takes place as follows:
The determination modules are called one after the other.
When a determination module finds an issue, the check modules are called one after the other.
The issue found by the determination module is not confirmed until all the check modules report a positive result.
The next determination module is called in the framework component
Determine Additional Issue
until the number of additional issues is reached.