Supply Chain Management Blogs by SAP
Expand your SAP SCM knowledge and stay informed about supply chain management technology and solutions with blog posts by SAP. Follow and stay connected.
cancel
Showing results for 
Search instead for 
Did you mean: 
michael_goeck
Active Participant

Following my blog posts about HAWB printing (How to Print HAWB in TM 9.0 - Customizing & Masterdata and How to Print HAWB in TM 9.0 - Data Mapping), I would like to share information in a similar fashion about the printing of the master air waybill (MAWB). In contrast to the HAWB, which "belongs" to the freight unit and can be printed from there or directly from the forwarding order, the MAWB print can be initiated from the freight booking.

Since there are only few differences to the HAWB case, I combine the customizing and masterdata requirements plus the data mapping in this one blog post.

In short, the following steps must be taken:

  1. Define/adapt/select customizing settings in SAP Customizing IMG:
    • Freight booking type
    • Charge calculation settings (profile, categories, settings, types etc.)
  2. Create/adapt/select master data:
    • Business units/Organizational units (forwarding house)
    • Calculation sheets (maybe rate tables, scales)

-         

1. Customizing

1.1 Freight Booking Type

Path: SPRO -> SAP Customizing Implementation Guide -> SAP Transportation Management -> Transportation Management -> Freight Order Management -> Freight Booking -> Define Freight Booking Types

Create or choose a freight booking type which fulfills the following criteria:

  • Charge calculation is enabled
  • Output profiles contain /SCMTMS/TOR_PRINT_AIR
  • Transportation mode category: Air

1.2 Charge Calculation Settings

The only differences to the HAWB print deal with calculation profiles and their assignment to the purchasing organization.

1.2.1 Calculation Profiles

Path: SPRO/IMG -> SAP Transportation Management -> Transportation Management -> Basic Functions -> Charge Calculation -> Basic Settings for Charge Calculation -> Define Calculation Profile

In the calculation profile, you define the settings that you want the system to use when calculating transportation charges.

The relevant setting is the calculation level, which stands for the level the system creates charge items for: Header, stage or item. FB charge calculation only supports header level calculation. Furthermore, set the Air Waybill Printing to "TACT Rate" and AWB Settlement to "Contract Rate".

The other fields are not really relevant for the printing itself, but for the actual charge calculation, which provides the charge data to the printing.

1.2.2 Assign Calculation Profile to Organization

Path: SPRO/IMG -> SAP Transportation Management -> Transportation Management -> Basic Functions -> Charge Calculation -> Basic Settings for Charge Calculation -> Define General Settings

Here you define a combination of purchasing calculation profile and organization, i.e. the profile you want the system to use when calculating transportation charges for a specific purchasing organization (for creating purchasing organizations see next chapter).

2. Masterdata

2.1 Business Units/Organizational Units

2.1.1 Purchasing Organization

You need one organizational unit which has either "Purchasing" or "Forwarding House" as function, so that you can use it as purchasing organization in the charge calculation settings and in the freight booking later. So either pick and/or modify an existing one that you "own" or create a new one, e.g. by using the transaction PPOCE.

2.2 Calculation Sheets

See HAWB blog, especially the part about the calculation resolution base of weight charges. The information about main stage restrictions doesn't apply of course, since the FB charge calculation only works with header level, not stage or item level calculation.

2.3 Freight Agreements

In the freight order management area, freight agreements are used to manifest the business relationship between partners and to set the basis for the charge calculation. See HAWB blog (use purchasing instead of sales organization).

--------------------------------------------------------

 

Finally, let’s come to the data mapping of the MAWB, so that you know which values from the freight booking go into which field of the print form, when the values displayed and when not etc. Again, there are only a few differences to the HAWB print form.

Here is an empty MAWB, with numbers for the single areas. Under the images, you will find a table which explains what will we displayed when for each of the numbers.

Number

Explanation

1 + 2 + 3

AWB number:

  • A combination of carrier, airport and document information

1

AWB code of airline

  • Numeric, three digits
  • Comes from the business partner master data of your carrier (020 for LH in the following example):

3

MAWB number

  • Created from freight booking via toolbar action “Follow Up” -> “Draw MAWB Number”

2

IATA code of airport of departure

4

Address of the shipper in FB

  • Sequence according to availability:

·         4-line address from business partner

·         5-line address from business partner

·         Maximum 4 lines of default address from business partner

·         Maximum characters per line: 35

5

Shipper’s business partner number

6

Address of the consignee in FWO

  • Sequence according to availability:

·         4-line address from business partner

·         5-line address from business partner

·         Maximum 4 lines of default address from business partner

·         Maximum characters per line: 35

7

Consignee’s business partner number

8

Issuing carrier’s agent name and city

  • Comes from the FB -> Booking -> Organizational Data -> Issuing Carrier’s Agent (business partner)

9

Agent’s IATA code

  • Comes from the FB -> Booking -> Organizational Data -> IATA Agent Code + CASS Account

10

Account number

  • Is not filled in MAWB, so it stays empty

11

Airport of departure

  • The first airport of the main stage(s)
  • Consists of three-letter IATA code and the city name of the airport (e.g. “FRA Frankfurt”), if available. The city name comes from IATA location (customizing), not airport location.
  • Maximum characters for construct: 20

12

Accounting information

  • Text filled in FB (“Operations” tab)
  • Maximum lines: 7

13

IATA code of the first destination airport

14

Name of carrier of flight between 11 and 13

  • Maximum characters: 17

15

IATA code of the next destination airport after 13

16

IATA code of carrier of flight between 13 and 15

17

IATA code of the next destination airport after 15

18

IATA code of carrier of flight between 15 and 17

19

Document Currency (ISO code)

  • Maintained in FB’s “Charges” tab
  • Is valid for all displayed amounts in MAWB

20

CHGS Code

  • Freight term: PP for prepaid, CC for collect; first letter is for weight and volume charges, second one for other charges
  • Comes from the FB’s “Booking” tab

21-22

Payer information for weight and valuation charges

  • Option marked with X
  • Should match with 20

23-24

Payer information for other charges

  • Option marked with X
  • Should match with 20

25

Declared value for carriage

  • Comes from “Operations” tab of FB (through shipped items), field “Goods or Declared Value”
  • If empty, the term “NVD” (no value declared) is being displayed

26

Declared value for customs

  • Comes from “Operations” tab of FB (through shipped items), field “Goods or Declared Value for Customs”
  • If empty, the term “NCV” (no customs value) is being displayed

27

Airport of destination

  • The last airport of the booking
  • Consists of three-letter IATA code and the city name of the airport (e.g. “FRA Frankfurt”), if available. The city name comes from IATA location (customizing), not airport location.
  • If both components are missing, the field stays empty
  • Maximum characters: 20

28

Flight information of first flight

  • Consists of IATA code of airline + flight number (if available in freight booking) + slash + two-digit day of flight
  • Example with flight number: Lufthansa flight 1234 on 18th May: LH1234/18
  • Example without flight number (see above): LH/18

29

Flight information of second flight

  • Consists of IATA code of airline + flight number + slash + two-digit day of flight

30

Amount of insurance

  • Comes from “Operations” tab of FB (through shipped items), field “Insurable Value or Amount of Insurance”
  • If empty, the term “XXX” is being displayed

31

Handling information

  • Text filled in FB (“Operations” tab)
  • Maximum lines: 3

32

SCI code (Special customs information)

  • Two-letter code maintained in FB (“Operations” tab)

33-41

Weight charges table

  • See HAWB blog

33

Number of pieces

  • As defined for the item

34

Gross weight

  • As defined for the tem

35

kg / lb

  • One-digit code: K for KG, L for LB
  • No automatic “translation”, it is in the responsibility of the item creator that he uses a common unit of measure

36

Rate class

37

Commodity code number

  • The number is shown which is defined in the rate table and which fits to the one defined at item level

38

Chargeable weight

  • Calculated from TCC

39

Rate/charge

  • Defined in either rate table or calculation sheet (can be overwritten in “Charges” screen)

40

Total of charge item line

  • Chargeable weight x rate amount or fix amount)

41

Nature of goods

  • Defined per weight charge item in the “Charges” screen
  • Multiple lines should occur on printout in the same order as entered
  • To add more than one NOG lines, mark the freight charge line, select “Insert” -> “Nature of Goods”. An new line will appear under the selected charge line; unfortunately the new  NOG line is not indented:

42

Total number of pieces

  • Sum of number of pieces of displayed items
  • Important to have a common calculation resolution base, so that the sum doesn’t e.g. contain the number of products plus the number of packages that actually contain the products

43

Total gross weight

  • Sum of gross weight amounts of displayed items

44

Total amount

  • Sum of all displayed charge item totals

57

Other charges

See HAWB blog.

45-56

Prepaid/collect summary

  • All charges of all types are summarized across all entities (plus header-level data) regarding their payer information (prepaid or collect). This information comes from the freight term.
  • Inactive charge lines should not be added to the sums (see checkbox on FWO charges screen)
  • Other charges are further split into due carrier and due agent

55

Total prepaid

  • Sum of all prepaid charges

56

Total collect

  • Sum of all collect charges

58

Signature of shipper

  • Contains the name and city of the shipper. The name is per default the second name of the business partner master data (see transaction BP), fallback is the first name
  • Maximum characters per line: 40

59

Execution information

  • Contains carrier’s agent name (see field 😎 + “AS AGENT FOR” + carrier name (see field 61).
  • The date is the flight date, and the city is the city of the purchasing organization

60

Shipment order ID

  • Number of freight booking

61

Address of carrier

  • Sequence according to availability:

·         4-line address from business partner

·         5-line address from business partner

·         Maximum 4 lines of default address from business partner

·         Maximum characters per line: 35

1 Comment