Transfer Requirement#
TransferRequirement.Show
A Transfer Requirement is a list that specifies quantity demands for Products (Material Definitions) that are required by a storage or production system. It groups a list of products and quantities that must be transferred from one Storage Area to another Storage Area or a Resource.
Note
The transfer requirement list may contain duplicate products.
A Transfer Requirement, during its life cycle, follows the state model as illustrated in the next picture.
graph TD
Start ==>|Create| A1[Requested]
A1 ==>|Approve| A2[Approved]
A2 -->|Unapprove| A1
A1 ----->|Cancel| A8[Canceled]
A2 ==>|All quantity released| A3[Released]
A2 ----->|Cancel| A8[Canceled]
A3 ==>|All quantity picked| A4[Picked]
A3 ----->|Cancel| A8[Canceled]
A4 ==>|All quantity in-transport| A5[In Transport]
A5 ==>|All quantity delivered| A6[Delivered]
A6 ==>|All items confirmed| A7[Closed]
classDef mermaid_start color:#000, fill:#fafafa, stroke:#fafafa, color:#fafafa, stroke-width:0x, font-size:100%, visibility: hidden;
classDef mermaid_entitylinked color:#000, fill:#FCD5B5, stroke:#FCD5B5, stroke-width:0px, font-size:100%;
classDef mermaid_state color:#000, fill:#d7e4bd, stroke:#000, stroke-width:1px, font-size:100%, font-weight:300;
class Start mermaid_start
class A1,A2,A3,A4,A5,A6,A7,A8,A9,A10,A11,A12 mermaid_state The lifecycle is further described in the table below. Note that there will be some release options that will control the options and degree of tracking that is required. For example, a transfer requirement can be marked to support partial releases and can also be considered automatically delivered after picking thus skipping the need for an explicit transfer order.
| State | Description |
|---|---|
| Requested | The Transfer Requirement has been requested |
| Approved | The Transfer Requirement has been approved (transfer requirements cannot be further be modified at this point) |
| Released | All required quantity has been released |
| Picked | All required quantity has been picked |
| In Transport | All required quantity is assigned to a transport order |
| Delivered | All required quantity has been delivered |
| Closed | All required quantity has been delivered and necessary individual packaging units created |
| Canceled | The Transfer Requirement has been canceled |
Table: Transfer Requirement lifecycle
Tying Everything Together#
graph LR
A1[Source Location] --- Main --- A2[Destination Location]
Main[Transfer Requirement] === L1[Transfer Requirement Item]
L1 --- A3[Product]
classDef mermaid_title color:#000, fill:#fafafa, stroke:#fafafa, stroke-width:0x, font-size:100%, font-weight:200;
classDef mermaid_start color:#000, fill:#fafafa, stroke:#fafafa, color:#fafafa, stroke-width:0x, font-size:100%, visibility: hidden;
classDef mermaid_businessdata color:#000, fill:#65CDE8, stroke:#65CDE8, stroke-width:0px, font-size:100%;
classDef mermaid_nonbusinessdata color:#000, fill:#B7DEE8, stroke:#B7DEE8, stroke-width:0px, font-size:100%;
classDef mermaid_entity color:#000, fill:#FB9F53, stroke:#FB9F53, stroke-width:0px, font-size:100%;
classDef mermaid_entitylinked color:#000, fill:#FCD5B5, stroke:#FCD5B5, stroke-width:0px, font-size:100%;
classDef mermaid_context color:#000, fill:#B9CDE5, stroke:#B9CDE5, stroke-width:0px, font-size:100%;
classDef mermaid_optional color:#000, fill:#B7DEE8, stroke:#65CDE8, stroke-width:1px, font-size:100%, stroke-dasharray: 5 5;
class Main mermaid_entity
class A1,A2,A3,A4,A5,A6,A7,A8,A9,A10 mermaid_businessdata
class L1,L2,L3,L4,L5,L6 mermaid_entitylinked
class C1,C2,C3,C4,C5,C6 mermaid_context
class N1,N2,N3,N4,N5,N6 mermaid_nonbusinessdata
click Main "../../business-data/transfer-requirement"
click A1,A2 "../../business-data/area"
click A3 "../../business-data/product"