Defining Scenarios

This scenario begins with a purchase order created in your ERP system. The purchase order is subsequently replicated to SAP Logistics Management, where it is transformed into an inbound logistical demand and an open inbound warehouse request.

• Goods Receipt: Upon arrival, the incoming goods are posted to a designated receipt bin. This action automatically triggers the goods receipt posting in the ERP system, ensuring real-time synchronization of inventory data.
• Putaway: Next, a putaway task is generated to move the goods to their designated storage location. This can occur in two ways:
  • Automatic Putaway: The system automatically directs the goods to a pre-defined fixed bin based on predefined rules.
  • Manual Putaway: A warehouse employee selects the appropriate storage bin based on factors like available space and product characteristics.
• Task Confirmation: The inbound task is confirmed, finalizing the putaway process and making the goods available in their designated storage bin.

This scenario applies when the incoterm in the outbound delivery is EXW (Ex Works) or FCA (Free Carrier). In these cases, the shipper isn't responsible for transportation, so no transportation request is generated.

• Immediate Replication: The outbound delivery created in ERP is immediately replicated to SAP Logistics Management.
• Direct Warehouse Processing: In SAP Logistics Management, the outbound logistical demand and outbound warehouse request are created immediately, allowing warehouse processes to begin without delay.
• Picking and Packing: A picking task is created for the outbound warehouse request item. Optionally, the goods can be packed into a shipping handling unit (HU).
• Goods Issue: After staging confirmation, the goods issue is posted, completing the process.

This is an outbound scenario involving transportation activities, triggering the creation of a transportation request.

• Parcel Determination: The transportation request for the outbound delivery (with an incoterm other than EXW or FCA) initiates the parcel scenario based on processing variant determination rules.
• Automated Carrier Selection: The warehouse request is created immediately, and picking can begin directly, as the carrier is automatically determined.
• Mandatory Packing: Packing is a mandatory step in this scenario, as the shipping HU triggers the creation of a transportation consignment in the background.
• Tracking ID Assignment: The parcel carrier web service, called during HU printing, provides a tracking ID that is assigned to the shipping HU for parcel tracking.
• Pickup Document Processing: The HU is also assigned to an open pickup document in the background. After staging and goods issue, the pickup document is checked-in, set to loading complete, and checked-out. A loading list can be printed based on the pickup document's content.

This outbound scenario also involves transportation, generating a transportation request.

• Automatic Carrier Determination: In an LTL scenario, transportation capacity is assumed to be pre-contracted, so carrier determination occurs automatically.
• Consolidation Options:
  • No Consolidation: The warehouse request is created automatically, and no consignment is created at the start.
  • With Consolidation: The consignment is created immediately, and new transportation requests are consolidated to an open consignment until a cutoff time. After cutoff, a new consignment is opened. Once consolidation is complete, the warehouse request is created, and warehouse activities can begin.
• Warehouse Execution: After warehouse request creation, picking tasks are created and confirmed. The transportation request is assigned to a pickup document.
• Optional Packing: Packing into a shipping HU is optional. If used, the shipping HU is assigned to the pickup document.
• Final Steps: After staging and goods issue, the pickup document is checked-in, set to loading complete, and checked-out. A loading list can be printed based on the pickup document's content.

Similar to LTL, this is an outbound scenario with transportation, triggering a transportation request.

• Carrier Collaboration: In a direct LTL scenario, a consignment is tendered using carrier collaboration in a system like Business Network for Logistics (BN4L). The consignment is tendered, and carriers can submit proposals.
• Proposal Acceptance: The shipper can accept or deny the carrier's proposal in BN4L.
• Consolidation Options:
  • No Consolidation: Each consignment can be tendered immediately.
  • With Consolidation: The consignment can be tendered after consolidation is completed.
• Warehouse Process Initiation: After proposal acceptance, the consignment is subcontracted to the carrier, finalizing the carrier collaboration steps. The warehouse process can now begin.
• Warehouse Execution: After warehouse request creation, picking tasks are created and confirmed. The transportation request is assigned to a pickup document.
• Optional Packing: Packing into a shipping HU is optional. If used, the shipping HU is assigned to the pickup document.
• Final Steps: After staging and goods issue, the pickup document is checked-in, set to loading complete, and checked-out. A loading list can be printed based on the pickup document's content.