Professional Documents
Culture Documents
SAP Transportation Management 9.0: System Demonstration - Less Than Container Load Scenario Air Freight
SAP Transportation Management 9.0: System Demonstration - Less Than Container Load Scenario Air Freight
0
System Demonstration Less than Container Load
Scenario Air Freight
Nikolai Lorenz
Changed by
Nikolai Lorenz
Chapters changed
All
Document Control
Author
Author name
Nikolai Lorenz
Author email
Nikolai.Lorenz@ortec.com
File Name
LCL_Scenario_AF
Path
< >
Initially Created
02.05.2013
Last Edited
02.05.2013
Number of Pages
52
Preface ....................................................................................................................... 1
Overview .................................................................................................................... 2
Background ............................................................................................................... 4
3.1 Operational .......................................................................................................... 4
3.2 Technical.............................................................................................................. 4
Process ...................................................................................................................... 5
4.1 Flight Planning & Capacity Booking ................................................................. 6
4.1.1 Create Air Booking ....................................................................................... 7
4.1.2 Send Booking to Carrier ............................................................................. 10
4.2 Forwarding Order / House Air Way Bill Creation ............................................ 12
4.2.1 Create a Forwarding Order from Template ................................................ 12
4.2.2 Create HAWB ............................................................................................ 15
4.3 Planing with the Transportation Proposal Function ...................................... 17
4.4 Capacity assignment (FB) ................................................................................ 19
4.5 Pick-up Planning ............................................................................................... 21
4.6 Confirm Customer Booking ............................................................................. 23
4.7 Air Cargo Security Status ................................................................................. 25
4.8 Execution of Pickup .......................................................................................... 26
4.9 Feeder Planning ................................................................................................ 30
4.10 Cargo Dispatch to Gateway............................................................................ 35
4.10.1 Execution of Pre-carriage ........................................................................ 35
4.10.2 Monitoring departure at BU ...................................................................... 37
4.11 Cargo Receipt & Exception Handling ............................................................ 38
1 Preface
The latest Version of the SAP Transportation Management Module is 9.0. The first mature
Version of a SAP based Transportation Management solution was 8.0. The target customers had been shippers.
The functionality of the successor SAP TM 8.1 was able to meet the requirements of Forwarders. The functionality of the SAP TM 8.1, serves as basis for the SAP TM 9.0 in the
Ocean Freight. SAP TM 9.0 has crucial enhancements in the Air Freight Functionality.
Therefore, the purpose of this document is, to demonstrate how does the latest Version
of a SAP based Transportation Management Solution is able to cover an Air Freight
Transportation Process, from a Forwarding Company perspective.
In Chapter 4 the Process will start with the creation of Air Freight Booking, in order to offer
capacity for the Main Carriage. Then a Forwarding Order will be created, which is triggering a Transportation Requirement in SAP TM. The Forwarder will capture the data from
the customer and start to plan the Main-Carriage and the Pickup. After the Execution of
the Pick-up the Pre-Carriage will be planned and then executed. Until the loading of the
cargo on the plane, the drayage between the Gateway Station and the Airport has to be
planed. The cargo will be loaded on the plane and then executed. The last event in this
scenario is the arrival of the cargo at the Los Angeles Airport. In this document the planning and execution of the On-Carriage and Delivery is not considered, as the other Sales
Organization (USA) is responsible for this stages.
3.1 Operational
This demonstration is designed on a transportation network dedicated for a LCL Air Freight
Scenario used, by Forwarding Company.
Demo Flow depicts a scenario where a Forwarding House collaborates with a Central
Freight Station to plan and execute an international transportation order Highlights:
Initial Freight Booking with Air Carriers
Multi-Modal planning of forwarding order
Execution of the respective Business Objects
3.2 Technical
Scenario is based on SAP Transportation Management 9.0
Involved Architecture:
As the SAP Event Management (EM) is not involved in the Architecture of this document,
we assume that all the Events are executed and reported to the SAP TM System, as
planed in the respective Business Objects (FWO, FOs). The Freight Settlement is not part
of this document.
The Planning and Execution will be done only for the first 3 stages (Export View), as for
the last 2 Stages (Import View) another sales organization (Container Freight Station in
Los Angeles) is responsible this.
A Gateway (AF-FWH-03) will create actual Freight Bookings (FB) from the planning data
and automatically pull MAWB Numbers from a pre-defined stock. Based on the master
flight schedule a Forwarder can create an operational flight plan. After booking confirmation with the carrier, the FB will be set to confirmed, and will be available to the Business
Unit (BU) for routing selection.
Now the Air Booking include all the data from the Air Flight Schedule.
A Number should appear in Booking tab -> MAWB No. Please check.
Assumption is that Carrier confirms this booking e.g. via fax or email. Click on Menu
Subcontracting -> Set to confirmed by Carrier. Check on Booking Tab that Booking
Confirmation Status is Confirmed by Carrier. Save the document.
After finishing the customizing it is possible to organize shipments from each shipper to
each consignee. In order to reduce the complexity, this document describes the shipment
from shipper (AF-CU-03) to consignee (AF-CO-03).
The first step involves the capture of customer data about a pending transport. This can be
communicated by the customer via phone, e-mail. A customer service agent, at this business unit origin will create a Forwarding Order (FWO) based on defined mandatory data.
At the creation of an FWO, a House Air Way Bill (HAWB) number can be generated and
be communicated to the customer.
Part of this advance notice process sequence is the ACS (Air Cargo Security) check,
based on the available data.
The Transportation Planner can use the Transportation Proposal Function of SAP TM. Go
to tab stages in the Forwarding Order. Click on Actual Route -> Define Route.
On the right side of the Transportation Proposal is the assignment to the documents for
execution (FOs, FB).
Notes: if within this step an Error Message occurs, related to the ACS check. Then go first
to step 4.7
In Order to plan manually, select in the FWO the tab Stages and Highlight the Main Stage.
Click Freight Document -> Select freight booking.
Stages 1 and 2 have status not Planned, Stage 3 has status Planned and stages 4 and 5
should have status Not Relevant. The last 2 stages are not relevant for planning right now
as these will be executed by a different organization.
Notes: if within this step an Error Message occurs, related to the ACS check. Then go first
to step 4.7.
The newly created FO should now be visible in the stages tab in column document. Click
on the newly created FO.
Now that the main stage and the pick-up is planned, the confirmation for the ordering party
is done through the FWO.
Enter the number of your FWO. Change to edit mode. Select Function Confirm. Save
your FWO.
The Air Cargo Security (ACS) check must be done, prior to the step 4.4.
Open the respective FU and go to General Data tab. Change the ACS (Air Cargo Security)
Status to X-Rayed cargo, secure.
Go to FWO tab Air Cargo Security and check that the Conutry-Specific Security Status
was synchronised with the Status of the FU.
The FWO (HAWB) was planned against a defined pre-carriage stage per origin BU (feeder) but physical assignment against a feeder is not be possible until certain status is
reached. The BU (OAF-STA-JPNGO) has to receipt the cargo, examine the physical characteristics and potential discrepancies, resolve them and assign the FWO to a feeder
based on status (chapter 4.7).
Save and change to edit mode. Go to tab Execution Information. Click on Insert Event.
Enter the Event, the actual Event Date and the Location.
Go to tab Stages of the FW. The Stage Status for the Pick-up is Arrived.
Now the (feeder) schedule that tie into the main stage transportation based on cut-off parameters and that was established previously by the Gateway, will be used to arrange the
pre-carriage.
Either go to Planning -> Transportation Cockpit or start the Transportation direct from the
FWO.
According to the steps before, the Pick-up (FO 300000645) and the Main-Carriage (FB
400000060) for the FU 4100000249 are already planned. In order to plan the PreCarriage, highlight this stage and then to to Schedules.
In the last line of the Freight Orders/Freight Bookings Window is visible now.
In the FWO on the tab Stages, the Status of the Pre-Carriage changed on Not Loaded.
Part of the procedure is the ability to enter irregularity/discrepancy codes again if required
with corresponding if an FWO should be on hold or not. Once the truck manifest (FO) is
completed and all cargo is loaded, the user will set the status departed. The FWO on the
document will inherit the status departed and will be immediately available for the gateway as expected receipt via the FO.
The Departure of the FO 300000646 is reported. Save and Close the document.
Upon physical arrival of the cargo at the GW warehouse, it is physically checked in; respective information is entered into the system and compared to the expected piece
count/quantity. The gateway receiving process will set the status of all received FWO on
received gateway warehouse.
The procedure is: select the respective FO. Go to tab Execution Information. Click Insert
Event and enter the data: Event, Actual Event Date and Location. Report the Event, save
and close the document.
Gateway Operations will now commence the load planning. As first item, they will set the
FB as closed e. g. no new FWO can be assigned. For loose cargo, the load confirmation
will consist of confirming that all shipments (FWO) have been staged and labeled.
Open the FB and choose Set Item Status -> Set to Loaded. Save the air booking. The result is: Air Booking is ready for execution, items have been loaded.
The result is: Booking Confirmation Status is now Shipping Instruction sent to carrier. If
Status Shipping Instruction sent to carrier doesnt exist, you first need to click on
Subcontracting -> send Booking. Repeat the above mentioned process again.
When booked capacity for shipments is full or deadline of airline is reached, the FB have
to be closed.
Open the FB. Change to edit mode and go to tab Capacity and Cargo. Click on button Status and Set to MAWB Finalized.
Now, no more FWOs can be assigned to FB. In Case that you want to assign a new FWO
to existing FB, you first need to open the MAWB by selecting Status -> Set to MAWB not
Finalized.
Once a consolidation has been closed out the cargo will be transferred to the carrier (AFJL-NRT).
On the General Data tab check that the Purchasing Organization and Planning and
Execution Organization are maintained, as well as the Carrier (OAF-CR-04).
Drayage FO for Pick-up of loose freight from Gateway to Airlines created and planned.
Upon loading, the confirmed load count is put into the system and the cargo is transferred
to the carrier (AF-JL-NRT). As last step of the export side from the execution perspective,
the departure (uplift) is confirmed.
After reporting the event Arrival at Destination in Los Angeles and completing the booking. The document Export Air Booking is finished and not relevant for further actions. Main
stage has been executed and final delivery is triggered.