Requirement

Definition

List of advertising services that are found in contracts.

The following requirement types exist in the system:

  • Contract requirement

    • Barter deal requirement

    • System contract requirement

  • Exclusion requirement

  • Rate requirement

Use

General terms and conditions of business that define discount conditions (discount, bonus, fixed quantity price) in contracts are to be replicated in the system. Contract customers are to be granted discount conditions on all ads that are placed in the national edition of a daily newspaper.

Values for discount conditions are not specified in the requirements. These values are recorded in condition records and are determined by the system or negotiated with individual media customers during contract creation.

See also: Determination of Discount Conditions in Contracts

The validity of advertising services in contracts is to be defined for all sales areas to ensure that they are used consistently. Requirements are to be recorded as master records in the system.

Possible entries are to be made available to users responsible for creating contracts.

Advertising services that are automatically granted discount conditions during contract determination and advertising services that can contribute towards contract fulfillment if media customers hold contracts are to be defined.

See also: Determination of Contract Assignments

Structure

Requirement

A requirement is created without reference to a contract and is valid for all sales areas. You can restrict the validity of a requirement using a sales office and/or a sales group.

The requirement type determines the data that is available to you when you create a requirement. You define requirement types for a sales area in Customizing.

You can create exclusion, contract and rate requirements at any stage. You can only create barter deal and system contract requirements if these types of contract are admissible in the specified sales area. You define admissibility and definition of system contracts and barter deal contracts as follows in Customizing:

Define

Menu path

Admissibility and definition of system contracts and barter deal contracts

Start of the navigation path SAP Media Next navigation step Advertising Management Next navigation step Sales Next navigation step Contract Next navigation step Settings for Specific Sales Areas Next navigation step Make General Settings Next navigation step Contract Creation tab page End of the navigation path

Requirement element

Any number of requirement elements can be entered in a requirement to describe its features.

  • The item type for a requirement element describes its validity. If you do not specify an item type when creating a requirement element, the system cannot check the requirement element during contract determination. You can specify the ad, ad insert, distribution, service, commercial and/or online item types here.

  • The item category, planning data, product data and item type-specific data in a requirement element also restrict its validity. If you do not specify this information when creating a requirement element, the requirement element always counts as being fulfilled during contract determination.

If barter deal items in your organization count towards the fulfillment of barter deals, you must restrict the validity of the requirement to the respective item category.

If the validity of a requirement is to be restricted to a booking unit and/or content component, you must take account of the following difference:

  • Since the system checks contract-relevant booking unit hierarchies during contract determination, you can specify a combined booking unit when you restrict the validity.

  • Since the system does not check content component hierarchies here, you should specify content components that have been assigned to a structural content component hierarchy as end nodes when you restrict the validity.

Note Note

You can add additional attributes to the attributes used to define requirement elements. Enhancement JHV10001 in user exit SAPLJHAC_004 is used to check the freely definable attributes in contract determination.

End of the note.

Integration

The system checks the general data and requirement elements in a requirement during contract determination.

  • If no requirement elements have been created for a requirement, the system cannot check this requirement during contract determination. If more than one requirement element has been created for a requirement, a billing dataset can be assigned to this requirement if one of these elements is suitable. Requirement elements are linked using an or operation.

  • The system checks requirement elements using the element number sequence during contract determination. If a billing dataset is suitable for a requirement element, the system does not check the remaining requirement elements. The sequence of the requirement elements can determine the rate requirements used to assign a billing dataset to a contract item.

Note Note

You create a contract requirement with two requirement elements. The first requirement element applies to the Local total booking unit. The second applies to the Local north booking unit and a color scheme. The Local north booking unit is assigned below the Local total booking unit in the booking unit hierarchy.

Contract customer A places an ad in the Local north booking unit with a color scheme from requirement element two. This ad item fulfills both requirement elements.

During checks of the first requirement element, the booking unit for the requirement element is not identical to the booking unit for the billing dataset. Since no original assignment can be created, the system checks the booking unit hierarchies. When the system checks these hierarchies, it creates assignments with rate indicators that can be determined during this check. Requirement element two is not checked.

If you checked the second requirement element first, the booking unit for the requirement element would be identical to the booking unit for the billing dataset. The system would be able to create one original assignment in which all rate indicators are selected.

End of the note.

  • The system transfers the first requirement element in the inclusive requirement for the leading contract item to pricing during discount determination. If you create requirement elements that grant various discount conditions in a requirement, the first of these in the leading contract item may grant discount conditions to other requirement elements that are too high or too low.

A billing dataset can be assigned to a contract item during contract determination if it fulfills the following requirements:

  • If a billing dataset fulfills an exclusion requirement , it cannot be assigned to a contract item.

  • If a billing dataset fulfills a rate requirement , it can be assigned to a contract item with the rate indicators that have been selected in this requirement.

  • If a billing dataset fulfills a contract requirement , it can only be assigned to the contract item if it fulfills an inclusive but not an exclusive requirement in this item.

  • If a billing dataset fulfills a barter deal requirement , it can be assigned to a contract item in a barter deal contract if it is suitable for the barter deal.

See also: Barter Deal Contract

  • If a billing dataset fulfills a system contract requirement , it can only be assigned to an item in a system contract if it cannot be assigned to any other item for the contract customer.

See also: System Contract