Ansicht
Dokumentation

Distribution Item Type ( RELNISMAM_401_CB_VERT1 )

Distribution Item Type ( RELNISMAM_401_CB_VERT1 )

Fill RESBD Structure from EBP Component Structure   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Distribution Item Type

Description

As of Release 4.01, the distribution item type has been added to the order-publishing-media.

The distribution item type (distribution of flyers [1] independently of a carrier object) is structured similarly, as regards the master data required, to the ad insert item type (inserts [1] in a carrier object). You use the ad insert item type to sell AI booking units and the distribution item type to sell distribution booking units.

Planned coverages for distribution are assigned to these distribution basic booking units and can be included in the hierarchy using distribution combined booking units.

The distribution item type supports the following types of booking:

  • Full booking of a distribution basic booking unit
  • Selective booking of a distribution basic booking unit [2]
  • Full booking of a distribution combined booking unit
    All basic BUs assigned below the combined booking unit will be booked.
  • Selective booking of a distribution combined booking unit
    This order is incomplete. You must use the positioning functions to position the lower level basic BUs in the combined BU.

Master data

Booking units

The system makes a distinction between basic and combined booking units.

  • Basic booking units
    The basic booking units are used to store information that describes the object to be sold. A basic booking unit is a combination of one or more geographical objects (districts, cities, city districts, streets etc.) which are distribution elements. It describes the smallest saleable unit.
  • Combined booking units
    You can use combined booking units to group together combined booking units. If several basic booking units are frequently sold together, it is sensible to group these together in a combined booking unit. If this combined booking unit is booked, all of your lower level basic booking units are booked. Combined booking units thus facilitate the description of a distribution order.
    You can assign combined booking units to other combined booking units. This allows you to create a distribution hierarchy.

Booking units can be defined as follows: Logistics -> Advertising Management -> Master data -> Booking.

It is necessary to generate production units for ad inserts. This is not the case for distribution booking units in this release, meaning that distributions can be sold on a daily basis.

Planned coverages for distribution

You must assign at least one planned quantity for distribution to the basic booking units. Firstly, you should define the planned quantity types for distribution in Customizing. These planned coverages are planned quantities and describe the quantity that can be sold to the customer. Therefore, one distribution planned coverage type can represent the overall amount that can be sold to the customer, an additional distribution planned coverage type can be used for detached houses only.

You can assign a basic booking unit in connection with a distribution planned coverage type and a validity period in the master data booking menu: Booking unit -> Distribution booking unit -> Planned coverage Planned quantities for distribution. You can also define an extra quantity for distribution.

Distribution item

A distribution item is created in IS-M/AM using the same procedure as that for other item types. However, unlike the ad insert, it cannot be accessed via Environment -> Planning in Release 4.01.

You must specify a booking unit, date and the planned quantity type for distribution on the distribution item detail screen. Alternatively, you can define a distribution item using the distribution button.

If a combined booking unit was booked selectively in an initial step, you can use the position button to position lower level basic booking units in the combined booking unit.

The distribution item has several different types of quantity:

Distribution quantity for full booking
Distribution quantity
Calculation quantity for distribution
Delivery quantity for distribution
Extra quantity for distribution
You can change the distribution quantity, calculation quantity and the extra quantity in the schedule line list.
In Customizing you can determine in: Sales area-specifc settings -> General settings which quantities are used for pricing.

An ad insert object is also required for distribution. This object describes what is distributed. This is usually a flyer.

Further notes

IS-M/SD supports the management of M/AM distribution orders [2]. To do this, M/SD elements should be assigned to the distribution basic booking units. Generation of Deliveries for M/AM Distribution Orders

Disribution supports a runtime object for the distribution booking unit hierarchy. This runtime object should be used to speed up processing if the distribution hierarchy contains more than 100 entries. You can access this via the booking unit menu: Generation -> Generate BU hierarchies. If you wish to use this runtime object, you should ensure that the runtime object is generated again each time a change is made to the distribution BU hierarchy. This function is only available for the distribution hierarchies in the current release.

You can check the completeness of distribution hierarchies, using the booking unit menu: Environment -> Check master data -> BU completeness.

  • [1]
    The ad insert describes the object that is inserted or distributed for both item types.
  • [2]
    The distribution quantity can be changed at schedule line level in the M/AM order. In release 4.01, the M/SD shipping functions are used with theplanned covergaes that have been maintained for the M/SD district. This means that M/SD will not support selective booking in this release.





rdisp/max_wprun_time - Maximum work process run time   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 6895 Date: 20240520 Time: 153340     sap01-206 ( 126 ms )