Ansicht
Dokumentation

Collaborative Transportation Planning ( RELNAPO_30A_SP1_CLP_TP )

Collaborative Transportation Planning ( RELNAPO_30A_SP1_CLP_TP )

General Material Data   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Collaborative Transportation 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 Transportation Planning is an integrated part of the APO Transportation Planning / Vehicle Scheduling (TP/VS) application. This type of collaboration takes place between supply chain partners such as manufacturers and their carriers. After a TP/VS planning run in the manufacturer's APO system, the optimizer generates shipments and assigns them to one of the carriers maintained in the system. Once a match has been made, the partner receives a notification via the Internet or EDI indicating that an offer has been made. The transportation planner of the carrier company either accepts or rejects the offer. If the offer is accepted, the shipment is generated in the execution system. If the offer is rejected, the manufacturer's transportation planner receives an alert. The planner then has the option to select another carrier either manually or via the optimizer.

Effects on Data Transfer

For Collaborative Transportation Planning, there are two options for transferring data:

  • If only one partner (for example, the manufacturer) has APO and the other (the carrier) accesses the system through a Web browser, APO sends the carrier an email containing a link to the Internet page where the carrier's planner can view, accept or reject offers. In this case, the partner can use an Internet style sheet to determine the display format of the shipment data.
  • If one partner has APO and the other 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 Customizing

From the SAP APO Easy Access menu, choose Supply Chain Collaboration -> Environment -> Current settings. Maintain the following settings for all collaborative planning activities:

  • Define partners
  • Assign users
  • Maintain communication channels for each user (enter email addresses, specify type of data transfer, etc.)

Further Information

For detailed information on Transportation Planning, see Release Note: Transportation Planning / Vehicle Scheduling






Vendor Master (General Section)   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 3642 Date: 20240425 Time: 133907     sap01-206 ( 115 ms )