Ansicht
Dokumentation

Collaborative Supply and Demand Planning ( RELNAPO_30A_SP1_CLP_SDP )

Collaborative Supply and Demand Planning ( RELNAPO_30A_SP1_CLP_SDP )

Fill RESBD Structure from EBP Component Structure   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Collaborative Supply and Demand Planning

Scope of Functions

APO Collaborative Planning enables enterprises to carry out collaborative supply chain planning activities with their business partners via the Internet. Collaborative Planning functionality for release 30A focuses on the relationship between suppliers, manufacturers, retailers and the carriers responsible for delivering goods to and from these entities.

All APO Collaborative Planning scenarios operate on the premise that at least one partner has an APO system. If only one partner has APO, other partners can display and change APO data via a Web browser. Other possibilities include an APO system for each partner, or a combination of APO and other systems. APO Collaborative Planning was designed to:

  • Enable exchange of required planning information with business partners
  • Allow the use of browser to read and change data
  • Restrict user access to authorized data and activities
  • Support consensus planning processes
  • Support exception-based management

Collaborative Supply and Demand Planning is an integrated part of the Supply and Demand Planning applications. In the Collaborative Demand Planning scenario, the buyer and seller develop a single forecast and update it regularly based on information shared over the Internet. It is a business-to-business workflow, with data exchanged dynamically, designed to decrease customer stock and cut inventory. The basic process consists of seven steps:

  1. Agree on the process: define role of each partner, establish confidentiality of shared info, commit resources, agree on exception handling and performance measurement.
  2. Create a joint business plan and establish products to be jointly managed including category role, strategy and tactics.
  3. Develop a single forecast of consumer demand based on combined promotion calendars and analysis of sales and causal data.
  4. Identify and resolve forecast exceptions. This is achieved by comparing current measured values such as stock levels in each store adjusted for changes such as promotions against the agreed-upon exception criteria (in-stock level, forecast accuracy targets).
  5. Develop a single order forecast that time-phases the sales forecast while meeting the business plan's inventory and service objectives and accommodating capacity constraints for manufacturing, shipping, etc.
  6. Identify and resolve exceptions to the forecast, particularly those involving the manufacturer's constraints in delivering specified volumes, creating an interactive loop for revising orders.
  7. Continue with the succeeding planning steps.

Within Collaborative Supply Planning the manufacturer and supplier exchange information on the material requirements of the manufacturer and collaborate on exceptions. This type of collaboration enables both the manufacturer and supplier to create more accurate supply network and production plans. The plans can be updated regularly based on information shared over the Internet. It is a business-to-business workflow, with data exchanged dynamically, designed to decrease inventory. The basic process consists of seven steps:

  • Both partners agree on the process: define role of each partner, establish confidentiality of shared info, commit resources, agree on exception handling and performance measurement.
  • The partners create a joint business plan and establish products to be jointly managed including category role, strategy and tactics.
  • The manufacturer creates a supply/production plan, based on a single forecast of consumer demand.
  • The manufacturer and supplier exchange information on the component requirements and create a joint forecast.
  • The supplier creates a supply/production plan based on the joint forecast..
  • Both partners identify and resolve exceptions particularly those involving the supplier's constraints in delivering specified volumes, creating an interactive loop for revising orders.

Both partners continue with succeeding planning steps.

Effects on Data Transfer

For Supply and Demand Planning, there are three options for transferring data:

  • If both partners have an APO system, data transfer takes place automatically via BAPIs and the Business connector if the Internet is used.
  • If only one partner (for example, the manufacturer) has APO and the other (the supplier) accesses the system through a Web browser, APO sends the partner an email containing a link to the Internet page where the partner can view and enter data.
  • If one partner has APO and the other has another system, the data transfer takes place via IDOCs and ALE technology. In this case, the partner must maintain the data storage and IDOC destination.

Effects on System Administration

The APO system administrator must complete the following steps for each user who will participate in collaborative supply and demand planning:

  • Create users in the appropriate roles, for example, Demand Planner, and define authorizations for transactions and planning books for each user.
  • Assign users to planning books. From the SAP APO Easy Access menu, choose Demand Planning -> Current Settings -> Assign user to planning book.
  • Maintain selection assignments. From the SAP APO Easy Access menu, choose Demand Planning -> Environment -> Selection Organization -> Maintain Selection Assignments.
  • Maintain communication channels for each user (enter email addresses, specify type of data transfer, etc.)

Effects on Customizing

No further Customizing is necessary.

Further Information

For detailed information on Supply and Demand Planning, see the relevant Release Notes.






BAL Application Log Documentation   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 6527 Date: 20240419 Time: 113148     sap01-206 ( 100 ms )