| REPLENISHMENT PROPOSAL v. 2.1 | |||||||||||||||||||||||||||||||
| Problem Statement | |||||||||||||||||||||||||||||||
|
The replenishment process in broader sense
addresses the business practice to exchange data between a buying party (e.g.
buyer) and a supplying party (e.g. seller/supplier) related to the future
demand of finished or semi-finished products, ingredients, packaging and raw
materials. In fact a replenishment request and a replenishment proposal.
Between retailer and manufacturer (the downstream supply chain) the data is basically based on future demand based on finished products and time series but it can also be restricted to actual sales date for a certain period of time. Feed-back from the manufacturer on his availability to deliver is required, where available inventories (of both sides) are taken in account. Between manufacturer and material supplier (the upstream supply chain) the data is basically based on material requirements for production and the timing for it. And also the feedback from the material supplier on his availability to deliver and the schedule for delivery. Inventories (on both sides) are taken in account for the actual delivery schedule. Based on the delivery schedule (replenishment proposal), a transport and shipping planning can be derived. |
|||||||||||||||||||||||||||||||
| Objective | |||||||||||||||||||||||||||||||
|
To supply the detail design of the (specific) business transaction needed to meet the requirements of the referenced BRAD(s). |
|||||||||||||||||||||||||||||||
| Audience | |||||||||||||||||||||||||||||||
|
Anyone involved in the replenishment process with another party in the (extended) supply chain process. These parties basically are retailers, manufactures and suppliers of ingredients, packaging and raw materials. But can also be parties in between like wholesalers or logistic service providers managing warehouses. |
|||||||||||||||||||||||||||||||
| Business Context | |||||||||||||||||||||||||||||||
| Industry: All Geopolitical: All Product: All Process: Plan Official Constraints: None Roles: Buyer, Seller System Capabilities: EANCOM, XML |
|||||||||||||||||||||||||||||||
| Business Transaction View | |||||||||||||||||||||||||||||||
| Business Transaction Use Case Diagram | |||||||||||||||||||||||||||||||
 |
|||||||||||||||||||||||||||||||
|
Figure 1 – Use Case Diagram: Business Transaction |
|||||||||||||||||||||||||||||||
| Use Case Description | |||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
| Business Transaction Activity Diagram | |||||||||||||||||||||||||||||||
| Not Available | |||||||||||||||||||||||||||||||
| Business Transaction Activity Diagram | |||||||||||||||||||||||||||||||
| Not Available | |||||||||||||||||||||||||||||||
| Business Document Example | |||||||||||||||||||||||||||||||
| Code Lists | |||||||||||||||||||||||||||||||
TOP |