Purpose

This process describes how contract items that are suitable for a billing dataset are determined by the system and contract assignments created.

It is a system process that you cannot control manually. It is part of contract determination.

See also: Contract Determination

Prerequisites

You have triggered contract determination by confirming the sales document data or by billing the billing dataset.

Final settlement has not been performed and the contract is active.

Process Flow

The system creates a contract assignment for each billing dataset that has been generated for a sales document item. The following check logic is performed:

In the first step, the system checks whether the billing dataset data matches the data for an exclusion requirement.

a. If this is the case, the billing dataset cannot be assigned to any contract item and contract determination is completed following step 1.

b. If the data does not match, contract determination is continued in step 2 of the check logic.

In the second step, the system checks whether the billing dataset data matches the data for a rate requirement.

a. If this is the case, you can assign this billing dataset to a contract item with the rate indicators that have been selected in this requirement. If the Counts towards discount fulfillment and Counts towards bonus fulfillment indicators have been selected in the rate requirement, these indicators also apply to the assignment. The system deletes the Qualifies for discount and Qualifies for bonus indicators from the assignment. Contract determination is continued with step 3 of the check logic.

b. If the billing dataset data does not match the rate requirement data, the billing dataset can be assigned to a contract item with the Qualifies for discount, Counts towards discount fulfillment, Qualifies for bonus, and Counts towards bonus fulfillment rate indicators. Contract determination is continued with step 3 of the check logic.

In the third step, the system identifies the order partners for which temporary contract assignments can be created.

Temporary contract assignments are assignments that are determined during contract determination.

The business partners for whom temporary assignments can be created are defined in the partner access sequence that has been assigned to the sales area in which the sales document was created.

Sub-steps a) – e) of the check logic are performed for each contract and each order partner specified in the partner access sequence. If you have assigned partner access sequence V001 to a sales area, the system can check whether the advertiser is the contract holder, beneficiary or group subsidiary.

See also: Partner Access Sequence

When temporary assignments are determined, sub-steps a) – e) of the check logic are performed for all contracts held by the order partners specified above:

a. In the first sub-step, the system checks whether contracts to which the billing dataset can be assigned temporarily have been created in a sales area that is admissible according to the partner access sequence.

i. If the sales area in which a contract has been created is not admissible according to the partner access sequence, no billing datasets can be assigned to this contract. Contract determination is completed for this contract following sub-step a) of the check logic.

ii. If the sales area in which a contract has been created is admissible according to the partner access sequence, billing datasets can be assigned to this contract. Contract determination is continued with sub-step b) of the check logic.

b. In the second sub-step, the system checks whether the billing dataset data matches the data in the contract header. The header data that is checked here includes the validity period, target to be sold and the contract status ( Confirmed indicator).

If you have not selected the Assignments to unconfirmed contracts indicator in Customizing, billing datasets can only be assigned to contracts for which the Confirmed indicator has been selected on the Status tab page.

You can select the Assignments to unconfirmed contracts indicator as follows in Customizing:

c. In the third sub-step, the system checks whether the billing dataset data matches the data in this contract item for each contract item. “Matches” means that the inclusive requirement in the contract item applies and the exclusive requirement does not.

If several contract items or a contract item with several requirement elements have been created in a contract, you should note that the first requirement element of the inclusive requirement for the first contract item is granted discount conditions.

When checking the inclusive requirement, the system checks whether a requirement element applies.

If a requirement element is fulfilled, the inclusive requirement is also fulfilled. Requirement elements are linked using an or operation. If a requirement element applies, the system does not check the remaining requirement elements (with a higher element number). In this situation, with the exception of the “Requirement applies” decision, the rate indicators and the “original” indicator if necessary are determined. These can be used to assign the billing dataset to this contract item. The system first determines which rate indicators are actually used to perform the assignment in the next step. The sequence of the requirement elements can therefore determine the rate indicators used to create a contract assignment.

The system checks the booking unit when checking the requirement elements.

i. If the booking unit for the billing dataset matches the booking unit for a requirement element, the billing dataset can be assigned to the contract item as an original assignment with all rate indicators from step 2. The billing dataset can still be assigned to the contract item as an original assignment even if no booking unit has been specified in the requirement element.

ii. If the booking unit for the billing dataset does notmatch the booking unit for a requirement element, the billing dataset cannot be assigned to the contract item as an original assignment. The system checks whether the booking unit for the billing dataset is part of a booking unit hierarchy as a result of the rate indicator. The system checks all booking unit hierarchy types here.

Various search directions are used in the booking unit hierarchy types to determine the rate indicators. A media customer who has a contract in the Local total combined booking unit but only places an ad in one of the lower-level booking units, for example Local A is to be granted discount but this ad is not to contribute towards contract fulfillment.

Each unsuccessful search in a booking unit hierarchy type means that a specific rate indicator is excluded when the billing dataset is assigned to this contract item. If all rate indicators are excluded during the search, the requirement element does not apply. Other requirement elements in the requirement cannot apply.

If the Discount inheritance block indicator has been selected in a contract, the system does not check whether the billing dataset booking unit is an element in a booking unit hierarchy in this situation (ii). The billing dataset cannot then be assigned to this contract item as qualifying for discount and bonus.

If the Discount optimization indicator has been selected in Customizing, the system determines the most favorable discount condition for the media customer from those that can be determined in the booking unit hierarchy. If this indicator has not been selected in Customizing, the system determines the next highest discount condition in the booking unit hierarchy and evaluates this in conflict control.

The system then checks other data in the requirement element, for example the content component, item category or other specific item-type data. This data must match the data in the billing dataset so that the requirement element can apply.

If you have defined individual customer attributes in the JHV10001 enhancement in user exit SAPLJHAC_004 , the system checks these attributes.

The system also checks whether the exclusive requirement applies. If the exclusive requirement for the contract item applies, the contract item cannot be assigned even if the inclusive requirement applies.

d. In the fourth sub-step, the system selectsone contract item, to which a billing dataset can be assigned, from those determined for a contract.

i. If a billing dataset is assigned to several contract items for a contract as an original assignment, the system selects the first of these original assignments.

ii. If a billing dataset is not assigned to any contract item for a contract as an original assignment, the system selects the assignment that is granted discount.

iii. If rate indicators have been selected manually in the contract item to which the billing dataset has been assigned, the rate indicators in the billing dataset are overwritten by those in the contract item.

If a billing dataset can be assigned to contract items in a number of contracts, the system determines suitable assignments for each contract. Conflict control in step 4 is used to select those contract assignments that are granted discount conditions from the suitable contract assignments that are determined.

e. In the fifth sub-step, the system creates temporary contract assignments.

Rate indicatorsare entered in the contract assignments.

i. If the Explicit sales areas indicator has not been selected in a contract, meaning that no sales areas have been assigned to this contract, the system assigns billing datasets with the remaining rate indicators from the contract sales area. This can include the Qualifies for discount, Qualifies for bonus , Counts towards discount fulfillment and Counts towards bonus fulfillment rate indicators. Billing datasets from other sales areas can only be assigned to the contract with the Counts towards discount fulfillment and Counts towards bonus fulfillment rate indicators if these indicators are still available.

ii. If the Explicit sales areas indicator has been selected in a contract and no sales areas have been assigned to this contract, the system assigns billing datasets with the remaining rate indicators from the contract sales area. This can include the Qualifies for discount, Qualifies for bonus , Counts towards discount fulfillment and Counts towards bonus fulfillment rate indicators. The system does not assign billing datasets from other sales areas to the contract.

iii. If the Explicit sales areas indicator has been selected in a contract and sales areas have been assigned to this contract, the system assigns billing datasets from other sales areas with the rate indicators that have been specified during sales area assignment . The system does not assign billing datasets from sales areas other than those specified to the contract.

The contract standing is updated. During this process, the system adds any contract assignments determined to the contract standing that counts towards discount and bonus and determines the discount conditions:

i. If the target to be sold is exceeded and the No over-fulfillment indicator has been selected in the contract, the system does not create the contract assignments determined.

ii. If the target to be sold is exceeded and the No discount/price adjustment indicator has been selected in the contract, the system creates the contract assignments determined and retains the discount conditions specified during contract creation. The customer is not granted the more favorable discount conditions until interim or final settlement of the contract.

iii. If the target to be sold is exceeded and the Automatic discount/price adjustment in the order indicator has been selected in the contract, the system creates the contract assignments determined and determines discount conditions according to the quantity sold.

Discount conditions determined are selected for conflict control.

The system enters discount conditions (discount, bonus, fixed quantity price) in the contractassignments.

i. If you have selected the Automatic discount/price adjustment in the order indicator in the contract, the system enters the discount conditions from the new discount determination in the contract assignments.

ii. If you have selected the No discount/price adjustment or the No over-fulfillment indicator in the contract, the system enters the discount conditions from the contract in the contract assignment.

iii. If you have changed the assigned billing datasets manually, the system enters the discount conditions from the changed billing dataset in the contract assignment.

iv. If the Gross contract indicator has been selected in the contract and the Advance bonus indicator has not been selected, the system does not take account of discount and bonus during pricing.

The number and quantity are entered in the contract assignments.

Number and quantity are entered without leading signs in the contract assignment. The system updates number and quantity with negative leading signs or zero in the contract standing if the relevant settings have been made in Customizing. If you have created a correction item for full credit memos, you usually want to update number and quantity with negative leading signs in the contract standing. If you have created a correction item for partial credit memos, you usually want to update number with zero in the contract standing.

The system also determines the positioning factors in addition to the leading signs when updating the number and quantity. If you have specified in Customizing that the positioning factor for number in a particular booking unit is 2, the system evaluates each ad placed in this booking unit as 2 ads.

In the fourth step, the system selects those contract assignments that can be created according to conflict control from all temporary contract assignments determined.

During this process, temporary contract assignments are divided into three discount classes and predefined sort criteria are used to determine the first contract assignment in a discount class.

See also: Conflict Control

If contract assignments can be created for a media customer, the process is completed with step 4 of the check logic.

If no contract assignments can be created for a media customer, the system checks whether the billing dataset can be assigned to a system contract in the fifth step.

If the billing dataset fulfills a system contract requirement and the media customer is a contract customer, the billing dataset can be assigned to a system contract.

If the billing dataset cannot be assigned to a system contract, the process is completed with step 5 of the check logic.

Result

Contract assignments have been created but not updated.

Once these assignments have been created, they are updated with the billing dataset and the contract standing. Discount conditions determined are transferred to pricing and the assessment bases are entered in the contract assignments.

See also: Contract Determination