ORSOFT for Campaign Planning supports functions for
- Creating campaigns
There are two basic tasks in creating campaigns:
- Initialize Campaign: generate a number of new orders that form a campaign.
- Merge Orders: select a number of available orders to be merged into a campaign according to predefined conventions.
In campaign initialization, master data is required. The campaign recipe was introduced for this purpose. Analogous to transferring an SAP planning recipe in an SAP process order, a campaign recipe can be transferred in a campaign. The campaign recipe consists of many independent orders, which are connected through order relationships and offset times.
In order merging, there are a number of various methods; for example, the following:
Method 1: Derivation from a campaign recipe.
Method 2: Derivation from a number of orders with common campaign numbers over material flow, taking goods receipt processing time into consideration.
Method 3: Creation of a campaign complex from orders and a campaign recipe.
Method 4: Creation of a logistical tree originating from an issue element, whose orders receive the requirement identification number as their campaign number.
Campaigns can be (complying with order relationships and offset times):
- permissibly scheduled
- implemented (namely, disregarding competing orders scheduled on the resources)
- permissibly shifted
- postponed and moved
- expanded and reduced, in relation to the quantity after cross multiplication
- expanded through additional orders
- reduced in orders
- split into two campaigns
- created from two campaigns through merging
As a result:
- Extension over shift breaks is possible for every order.
- Individual campaign orders can be "pushed away" when scheduling other competing orders.
- Individual campaign orders could just be implemented in infinite planning and not permissibly scheduled.
Campaign splitting is supported through editors (see the following image).
The solution is fully integrated in SAP ERP / SAP S/4HANA. In contrast to campaign planning with SAP APO (since SAP SCM 5.1), there is no necessary campaign consistency check as in the report for CIF comparison or in comparing transaction data. Additionally, no solution strategies are required to eliminate planning inconsistencies in SAP ERP, SAP S/4HANA and SAP SCM. Also, differing campaign numbers (external number of the production campaign in ERP system vs. SAP APO campaign number) do not exist.