Skip to Content

Printing the house air waybill (HAWB) was introduced with SAP Transportation Management 9.0. The HAWB printing functionality makes use of the newly introduced transient action concept of the post-processing framework (PPF). Basically it means that you can execute PPF actions from one business object in the context of another business object. In this case: You can execute the HAWB print actions, which belong to the freight unit, from the “Output Management” tab of the forwarding order. The necessary customizing is shipped with TM, so no necessary steps must be taken here.

But still it is required to follow certain guidlines e.g. in regards of charges customizing and masterdata, which will be outlined in this blog. A second blog deals with the mapping of the data, so that you know what you have to enter where so that it appears in the correct spot on the HAWB: How to Print HAWB in TM 9.0 – Data Mapping

 

In short, the following steps must be taken:

  1. Define/adapt/select customizing settings in SAP Customizing IMG:
    • Forwarding order type, freight unit 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 Forwarding Order Type

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

Create or choose a forwarding order type which fulfills the following criteria:

  • Charge calculation is enabled
  • Output profiles contain /SCMTMS/TRQ_FWO_PRINT
  • Transportation mode: Air
  • Traffic direction: Export
  • Freight unit building rule (see next point)
  • Text schema: DEFAULT or FWOAIRHDR

Parts of these criteria are also the requirements for the HAWB print actions to show up in the “Output Management” tab of the Forwarding Order, namely the transportation mode (air) and the traffic direction (export). I.e. the HAWB should not be printable from a road, rail or sea forwarding order and/or from an import forwarding order, therefore the print action will not be available in these cases.

1.2 Freight Unit Type

Path: SPRO -> SAP Customizing Implementation Guide -> SAP Transportation Management -> Transportation Management -> Planning -> Freight Unit -> Define Freight Unit Types

The freight unit type should contain the output profile /SCMTMS/TOR_PRINT_AIR_FU. If you don’t use a freight unit building rule in your FWO type and therefore don’t specify a separate FU type for your scenario, the default one is used. Since the default one might not only serve air freight scenarios, you better not change it, but create a building rule with your own FU type.

1.3 Charge Calculation Settings

1.3.1 Charge Categories

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

Charge categories are used to group and categorize charge types. E.g. you could have a charge category for air freight-related charge types.

1.3.2 Charge Subcategories

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

Charge subcategories are used to group and categorize charge types in a more granular way. E.g. you could have charge subcategories for the charge type classifications (weight, valuation, other). One charge category can contain several charge subcategories.

1.3.3 Charge Types

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

Charge types are used to support the actual charge calculation. They are entities that are grouped together in a calculation sheet, which is then applied to the order and/or its items. There should be weight-related types, which e.g. define a fee for the product that is being transported (e.g. 100 KG computer accessories, weight charge of 5 EUR per KG => result 500 EUR charge), furthermore you have “Other charges” with charge codes classified by the IATA, and valuation charges. All types also have basic information about the payer (carrier or agent).

Charge type grouping is not supported at the moment.

1.3.3.1 Weight Charges

The weight charge type should look like this:

/wp-content/uploads/2013/01/wch_174322.png

Important is that you:

  • Assign your charge category and subcategory
  • Set the type class to “Weight”

The charge due information is not important for the print, since the differentiation only exists on the HAWB print form for other charges.

1.3.3.2 Other Charges

The other charge types should look like this:

/wp-content/uploads/2013/01/och_174381.png

Here, you must set the type class to “Other” and assign a IATA charge code (besides the category and subcategory).

The charge due information of other charges is relevant for the HAWB print. You can either maintain it here or later in the calculation sheet.

1.3.3.3 Valuation Charges

The valuation charge type should look like this:

/wp-content/uploads/2013/01/vch_174380.png

Set the type class accordingly to “Valuation”.

Again, the charge due information of valuation charges is not relevant for printing.

1.3.4 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 profile looks like this:

/wp-content/uploads/2013/01/calcprof_174382.png

The relevant setting is the calculation level, which stands for the level the system creates charge items for: Header, stage or item. The charges system switches automatically to stage level calculation once you use an incoterm.

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.3.5 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 calculation profile and organization, i.e. the profile you want the system to use when calculating transportation charges for a specific sales organization (for creating sales organizations see next chapter).

/wp-content/uploads/2013/01/assprof_174383.png

2. Masterdata

2.1 Business Units/Organizational Units

2.1.1 Sales Organization

You need one organizational unit which has either “Sales” or “Forwarding House” as function, so that you can use it as sales organization in the charge calculation settings and in the FWO 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.1.2 Carrier

The carriers that you plan to use should have IATA airline codes and AWB prefixes maintained. Use the transaction BP to verify this (display in BP role “Carrier”, switch to the “Vendor Data” tab and check the table “Airline Codes”).

/wp-content/uploads/2013/01/carr_174384.png

2.1.3 Misc

Furthermore, you should have some organizational units which you can use as business partners in an FWO (shipper, consignee, agreement party, ordering party etc.). You should be able/allowed to modify them, so that you can define/change their address data (default address data through transaction PPOME as well as business partner address defined under “Additional Texts” through transaction BP).

2.2 Locations

Your airport locations should have maintained IATA code (e.g. FRA) and city name (e.g. Frankfurt). Check it in NWBC under Master Data -> Transportation Network -> Locations -> Define Location: The IATA code can be found on the “General” tab and the city name on the “Address” tab.

2.3 Calculation Sheets

Use the entities you created/chose above to setup a calculation sheet. This is done in NWBC under Master Data -> Charge Management and Service Product Catalogs -> Calculation Sheets.

For testing, add one weight charge item with a fix amount and one using a rate table. With a rate table, you can create e.g. flexible weight-based charges, in contrast to the fix amount, which just adds the amount without caring about weight, volume etc.

Important is the calculation resolution base of your weight charges, because this defines on which item entity the charges are being applied. For the HAWB, it makes sense to have either PRODUCT or MAIN_ITEM/PACKAGE/CONTAINER, since the respective items will be displayed in the weight charges table of the HAWB. There should be one common resolution base for all weight charges of a calculation sheet; otherwise you have a mix of packages and products, which will falsify the totals on the bottom of the HAWB weight charges table (like “mixing apples and pears”). So other calculation resolution bases like ROOT or STAGE are not supported by the print program.

You set this resolution base when you mark a charge item, switch to the tab “Basic Data” of the item’s details and enter the desired value into the field “Calculation Resolution Base”. Again: This affects only weight charges, not valuation or other charges.

One more thing: It is a requirement that only weight and valuation charges from the main stage(s) should be printed. In order to have a consistent view in the FWO’s “Charges” screen and the HAWB, you could restrict charge items of these types in your calculation sheet to the stages with the category “Main”. To do so, mark the charge item, switch to the tab “Basic Data” of the item’s details and fill in “M” into the field “Stage Category”.

/wp-content/uploads/2013/01/cprof1_174385.png

2.4 Forwarding Agreements

The forwarding agreement collects all customizing settings and master data you created and sets the strategy for charge calculation. You have to assign a sales organization and add the calculation sheet.

Background: When you click the “Calculate Charges” button in the FWO, the system searches for an agreement that fits to the sales org you used and then uses the agreement’s data. It is recommended to have one agreement per sales org, so that you can switch quickly by modifying the sales org in your FWO, which should trigger the determination of the respective agreement. Here is a simple overview diagram that illustrates how charges are calculated and where you find the agreement and calculation sheet in this process:

/wp-content/uploads/2013/01/fagproc_174390.png

You can influence this agreement determination process by specifying more data in the agreement, e.g. ordering party, transportation mode etc. Your FWO must then have the same data so that the connection to the agreement is established.

Note that if you want to add the ordering party as criteria in the agreement, you have to specify the same business partner in the FWO as ordering party and as prepaid/collect agreement party.

A special case is header-level charges. These are charges that are not appearing e.g. for every stage, but for the complete carriage. Only other charges are supported here, since it is impossible to assign these “global” charges to items. Example, showing one calculation sheet item declared as header-level charge in the agreement:

/wp-content/uploads/2013/01/hlchar_174389.png

Such header-level charges look like this on the charges screen:

/wp-content/uploads/2013/01/hlcharf_174391.png

Important: Don’t forget that you have to set the status of the agreement to “Released”, before it can be used! To do so, select the toolbar action “Set Status” -> “Released”.

/wp-content/uploads/2013/01/foa_174395.png

2.5 Other Data

Certain data will only be available when the main stage is planned, i.e. a freight booking exists which contains this data (e.g. flight number).

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply