Replenishment v. 2.0.2

XML Standards	>	Replenishment Proposal	Replenishment Request

Message Description

REPLENISHMENT v. 2.0.2

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

In the current gs1 XML standard no XML documents are available to address the replenishment process in a wider scope than the replenishment part of CPFR, which is also only defined for the downstream supply chain. Specific XML documents for data interchange with material suppliers don't exist as well as specific documents for the combined data interchange of sales or sales forecasts and inventories as well as material requirements and inventories.

The fact that inventories and even the status of these (like unrestricted, restricted, in transit, blocked, reserved etc.) are of importance also implicates the opportunity of an integrated data interchange including inventory data for a replenishment request and replenishment proposal.

Besides the external supply chain also the internal supply chain of manufactures based on sales units and factories should be able to use the replenishment XML documents

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 warehoused.

Business Context

Industry: All
Geopolitical: All
Product: All
Process: Plan
System Capabilities: EAN.UCC
Official Constraints: None

Business Transaction View

Use Case Diagram

Use Case Description

Process Use Case Name	Replenishment
Use Case Identifier (Traceability)	UC-1
Use Case Description	The data interchange originates from the 'buying' party in all scenarios. The interchange, the replenishment request, includes always the data for finished goods, semi-finished goods, ingredients, packaging materials or raw materials. In more collaborative scenarios also inventory data of the 'buying' party can be included. The interchange is not defined for only inventory data. The response of the 'supplying' party, the replenishment proposal, includes data on the delivery of the demanded goods or materials. Delivery is based on time buckets, e.g. day, week, and month. It can cover periods of time with different buckets. Inventory data of the 'supplying ' party can be included. Also for the response to the demand the interchange is not defined for only inventory data. For interchange of only inventory data other scenarios need to be used. It's more common to use the inventory data in the demand interchange than in the supply interchange. However in specific collaborative processes and in internal supply chain processes they supply interchange can include inventory data as well. The replenishment request and the replenishment proposal data interchange are the two basic interchanges for the replenishment process. For specific needs a confirmation of the replenishment proposal is included as well. This is often the case in the downstream supply chain. Both interchanges can be based on location and then item (location based approach) or first item and then location (product or item based approach). The data interchange does not support the specific replenishment part of the CPFR process that currently only is defined for downstream. This CPFR process is supported by a dedicated set of ANSI EDI messages and EAN-UCC CFPR XML documents
Actors (Goal)	Buying party: Any party who issues a replenishment request (including inventory data if appropriate) Supplying party: Any party who issues a replenishment proposal as a response to a replenishment request
Performance Goals	N/A
Preconditions	The 'buying' and 'supplying' party need to have agreed to the exchange of this data and to the business process that this supports. The partners need to have agreed that this message is the vehicle of data interchange as well as the definition of the data. The replenishment process starts with a replenishment agreement, describing the business rules.
Postconditions	No specific post conditions are relevant
Scenario	Begins when: The data interchange originates from the 'buying' party in all scenarios. The interchange includes always the data for finished goods, semi-finished goods, ingredients, packaging materials or raw materials. In more collaborative scenarios also inventory data of the 'buying' party can be included. 1 Buying party Issues a replenishment request; Possible types: actual sales and inventory forecast and inventory 2 Supplying party Responds to the replenishment request by issuing a replenishment proposal; Possible type(s): delivery plan (per site or per item) 3 Buying party Issues an Order if applicable. Ends when: The process ends with the response of the 'supplying' party including data on the delivery of the demanded goods or materials. Or with an order in case acknowledgement with an order.
Alternative Scenario	N/A
Related Requirements	N/A
Related Rules	N/A

Business Transaction Activity Diagram

Step #	Actor	Activity Step
1	Buying party	Issues a replenishment request; possible types: actual sales and inventory forecast and inventory
2	Supplying party	Responds to the replenishment request by issuing a replenishment proposal; possible type(s): delivery plan (per site or per item)
3	Buying party	Issues an Order if applicable

Replenishment downstream

Step #	Actor	Activity Step
1	Buying party	Issues a replenishment request; possible types: material requirements material requirements and inventory
2	Supplying party	Responds to the replenishment request by issuing a replenishment proposal; possible types: - production plan in case of a request based on material requirements (per item) - delivery plan (per site and per item) in case of a request based on material requirements and inventory
3	Buying party	Issues an Order in case of a replenishment proposal based on a production plan

Replenishment upstream

Business Transaction Sequence Diagram

Replenishment Scenarios

Replenishment without acknowledgement by order

TOP

Code Lists

Date of Publication: March 2007