Quantcast
Channel: SCN : Document List - SAP Transportation Management (SAP TM)
Viewing all 64 articles
Browse latest View live

How to Use the Generic Extraction for SAP EM in SAP TM

$
0
0

This document illustrates how the generic extraction for SAP EM can be used in SAP TM and which prerequisites have to be met. With the generic extraction, which is based on customizing only, additional parameters, expected events or event types can be extracted for SAP EM.

View this Document


Consulting Notes for SAP Extended Warehouse Management

$
0
0

SAP consulting notes cover a host of useful information to support you with your SAP implementation projects - tips and tricks on solution processes,configuration, customizing, coding etc.

All SAP notes can be accessed via: http://service.sap.com/notes

Here a selection of useful consulting notes with the direct link to the details to help you in your SAP Extended Warehouse Management projects.

 

Consulting NoteNumber
SAP EWM deployment option best practices1606493
Recommendations for using ERP-EWM integration1423321
Questions/answers relating to ERP/EWM integration1100049
Connecting ERP QM to EWM1278425
Legacy System Integration with EWM Delivery1465477
Overview: Communication & integration of ERP <> EWM batches1305698
Preventing outbound delivery split1600871
Technical documents for software development in EWM1414179
Overview: Batch Management1305605
Overview: Best-before date/expiration date batches1305608
EWM - Batch management requirement at plant level1550626
EWM:Distribution of packing instruction to packaging specification1600321
Release Restrictions for EWM 20071062246
Recommended notes and best practices for Delivery Archiving1402220
Hardcoded logical transactions in standard code1521250
Global product master fields are ready for input in EWM1451123
Factory Calendar expires 20101529649
How to create Basic Measurement Service1178089
Goods receipt for "confirm service" items for EWM1662673
Sizing of Extended Warehouse Management - Best Practices1896197

How to set up an export import process

$
0
0

This document describes how to set up an export import process for the scenario where the export organization as well as the import organization works on the same SAP TM system (one system case).

 

The document is structured in a chapter where the customizing settings are described, the needed master data and how to create the needed business documents.

 


1.  Master Data


1.1 Freight Unit Building Rule (FUBR)

 

NWBC -> Application Administration -> PlanningàGeneral Settings -> Freight Unit Building Rule

 

Create FUBR for import:

 

Document Type:your freight unit type (see 2.3)

Freight Unit Building Strategy: Consolidate per Request

Critical Quantity: Gross Weight

Planning Quantities: Gross Weight

Unit of Measure: e.g. KG

Split Quantity: e.g. 500


2.  Customizing


2.1  Forwarding Order

 

2.1.1  Create a forwarding order (FWO) types

 

IMG -> SAP Transportation Management -> Transportation Management -> Forwarding Order Management -> Forwarding Order -> Define Forwarding Order Types

 

Create a FWO type for import FWO with the following settings:

  • Automatic Freight Unit Building: X
  • Traffic Direction: Import
  • Stage Determination: Stage Determination by Movement Type (you can also use stage determination by stage profile, but how to create a stage profile is not described in this document
  • Freight Unit Building Rule (FUBR):your FUBR (see 1.1)

 

Create a FWO type for export FWO with the following settings:

  • Automatic Freight Unit Building: X
  • Traffic Direction: Export
  • Stage Determination: Stage Determination by Movement Type (you can also use stage determination by stage profile, but how to create a stage profile is not described in this document
  • Freight Unit Building Rule (FUBR):your FUBR (see 1.1)
  • Import FWO Type: your import FWO type

 

2.1.2  Assign item types to forwarding order types

 

IMG -> SAP Transportation Management -> Transportation Management -> ForwardingOrder Management -> Forwarding Order -> Assign Item Types to Forwarding Order Types

 

Assign the following item type to your export and import FWO type

 


Item Type


Item Category


CN


TUR Container


PKG


PKG Package


PRD


PRD Product

 

 

2.2  Freight Booking

 

2.2.1  Create a freight booking (BOR) types

 

IMG -> SAP Transportation Management -> Transportation Management -> Freight Order Management -> Freight Booking -> Define Freight Booking Types


Create a BOR type for import BOR type with the following settings:

 

 

Transportation Mode Category: Sea/Air (depending on what kind a freight booking you test)

 

Shipper/Consignee Determination: Determination based on first and last location

 

Traffic Direction: Import

 

Execution track. Relevance: Execution Tracking

 

Web Dynpro Application Config.: /SCMTMS/FRE_BOOK_OCEAN (if you use ocean bookings), /SCMTMS/FRE_BOOK_CBAIR (if you use air bookings)

 

Create a BOR type for export BOR type with the following settings:

 

 

Transportation Mode Category: Sea/Air (depending on what kind a freight booking you test)

Shipper/Consignee Determination: Determination based on first and last location

 

Traffic Direction: Export

 

Execution track. Relevance: Execution Tracking

 

Web Dynpro Application Config.: /SCMTMS/FRE_BOOK_OCEAN (if you use ocean bookings), /SCMTMS/FRE_BOOK_CBAIR (if you use air bookings)

 

Import Booking Type:your import booking type

 


2.3  Create freight unit (FU) types

 

IMG -> SAP Transportation Management -> Transportation Management -> Planning -> Freight Unit -> Define Freight Unit Types

 

Create FU type for import freight units and export with the following settings:

 

No special settings needed.

 

Web Dynpro Application Config.: /SCMTMS/FRE_UNIT

 


2.4  Organizational Units

 

IMG -> SAP Transportation Management ->Transportation Management -> Master Data -> Organizational Management -> Organizational Model -> Create Organizational Model

 

Create new organizational unit structure:

  • Create new organizational unit with Org. Unit Function “Company” and Org. Unit Role “Organization.
  • Create new organizational unit as sub unit of your new “Company” with Org. Unit Function “Purchasing” and Org. UnitRole “Organization.
  • Create new organizational unit as sub unit of your new “Company” with Org. Unit Function “Sales” and Org. Unit Role “Organization.

 

Create this structure twice. One for the export business unit and one for the import business unit.

 


2.5  Enable Output Management

 

IMG -> Cross-Application Components -> Processes and Tools for Enterprise ApplicationsàReusable Objects and Functions for BOPF Environment -> PPF Adapter for Output Management ->Maintain Output Management Adapter Settings

 

Enable output agent /SCMTMS/EXP_IMP_PROC and its assigned PPF action profile /SCMTMS/EXP_IMP_PROC

 


3.  Create business documents


3.1  Create export forwarding order

 

This chapter describes which prerequisites a forwarding order must have for an export import scenario.

 

NWBC -> Create forwarding order

 

Use forwarding order type for export FWO (see 2.1)

 

Mandatory fields on General Data tab:

  • Sales Organization of export business unit (see 2.4
  • ShippingType
  • Movement Type

 

Mandatory fields on Items tab:

  • Maintain at least one item
  • Gross weight must be maintained because of your freight unit building rule (see 1.1)

 

Mandatory fields on Business Partner tab:

 

  • Shipper
  • Consignee
  • Import Organization (use business partner for sales organization of the import business unit, see 2.4

 

Mandatory fields on Location and Dates/Time:

 

  • Check whether locations were filled from business partners.

 

Mandatory fields on Stage tab:

  • Maintain locations for the main stage (these locations must fit to the locations of the
    freight booking main stage)

 

Save the forwarding order and check that freight units were created.

 

 

3.2  Create export freight booking

 

This chapter describes which prerequisites a freight booking must have for an export import scenario.

 

NWBC ->Freight Order ManagementàCreate Ocean Freight Booking

 

Use freight booking type for export BOR (see 2.2)

 

Mandatory fields on General Data tab:

  • Purchasing Organization of export business unit (see 2.4)

 

Mandatory fields on Business Partner tab:

  • Carrier
  • Import Organization (use business partner for purchasing organization of the import business unit, see 2.4 )

 

Mandatory fields on Cargo Management tab:

 

 

Assign your export FWO/FU to the freight booing. Go to tab Cargo Management and press button ‘Insert FU based on /Freight Unit ID/Forwarding Order’.

 

Save the document.

 

 

3.3  Creation of import documents

 

After completing all steps described above you can trigger the creation of the import document by set the status on

 

“Shipped on Board” in case of an ocean freight booking

 

“Uplifted confirmed” in case of an air freight booking.

 

After saving the export freight booking the import documents are created. The document flow shows the created import freight booking.

 

All import documents have lifecycle status “Draft”.

 

3.3.1  Explanation on sales/purchasing organization conversion

 

Every purchase organization and sales organization is assigned to a Business Partner (BUPA). When you create the import documents the business partner of the responsible import organization is converted to the organization ID and this ID is used for the purchase/sales organization in the import documents. The purchase organization of the export freight booking is converted to the respective business partner and is filled as “Export Organization” in the import freight booking. The sales organization of the export forwarding order is converted to the respective business partner and is filled as “Export Organization” in the import forwarding order.

 

4.  Set up a FWQ based destination call off process

 

4.1  Create forwarding quotation type

 

In addition to the above described settings there are additional settings for the so called forwarding quotation based destination call off process. For this you need to create a forwarding quotation type with the following settings.

 

IMG -> SAP Transportation Management -> Transportation Management -> Forwarding
Order Management
à
Forwarding Quotation -> Define Forwarding Quotation Types

  • Traffic Direction: Import
  • Stage Determination: Stage Determination by Movement Type (you can also use stage determination by stage profile, but how to create a stage profile is not described in this document)
  • Default FWO Type: your export FWO type

 

 

4.2  Create business document

 

The description how to create a forwarding agreement is not part of this document

 

4.2.1  Create Import forwarding quotation

 

This chapter describes which prerequisites a forwarding quotation must have for an FWQ based destination call off scenario.

 

NWBC -> Create forwarding quotation

 

Use forwarding quotation type for import FWQ (see 4.1)

 

Mandatory fields on General Data tab:

  • Sales Organization of export business unit (see 2.4
  • Shipping Type
  • Movement Type
  • Export Forwarding Agreement

 

Mandatory fields on Items tab:

 

  • Maintain at least one item
  • Gross weight must be maintained because of your freight unit building rule (see 1.1)

 

Mandatory fields on Business Partner tab:

  • Shipper
  • Consignee
  • Export Organization (use business partner for sales organization of the export business unit, see 2.4

 

Mandatory fields on Location and Dates/Time:

  • Check whether locations were filled from business partners.

 

Mandatory fields on Stage tab:

  • Maintain locations for the main stage (these locations must fit to the locations of the freight booking main stage)

 

Save the forwarding quotation.

Reporting Events in SAP TM: Define a list of allowed event codes per TOR type

$
0
0

Recently new note 2081749 has been released, which introduces a new customizing:

New maintenance view /SCMTMS/TOR_EVT allows to define a list of allowed event code per transportation order type. By this you can control per freight document type (freight unit type, transportation unit type, freight order type, freight booking type or service order type) which event codes are offered in the drop-down menu on the execution tab. This is especially useful if you define multiple custom event codes and typically only a subset of these event codes are relevant for a certain freight document type.

This new customizing is complementary to the already existing assignment of event codes transportation order categories. If for a specific transportation order type no entries are maintained in the new maintenance view, still all event codes, which are assigned to the related transportation order category are offered in the drop-down menu.

 

The list of allwoed event codes can be maintained as described in the following:

     1. Go to transaction SE16 (alternatively SE54 can also be used) and enter the view name /SCMTMS/TOR_EVT and click on Create Entries:

 

torevt.png

     2. Select the transportation oder type, for which you want to maintain the list of allowed event codes and Continue:

torevt2.png

 

 

     3. Maintain the lsit of allowed event codes for this transportation order type:

 

torevt4.png

     In this example only one event code to report delays is assigned to the freight order type 'EM01'.

 

 

 

     4. This example will look like this in the execution tab, when inserting a new event:

 

torevt5.png

For TM 9.1 and TM 9.2 the view will be included in the existing view clusters to maintain the transportation oder types, which will simplify the maintenance. This will be available with next support packages (TM 9.1 SP05, TM 9.2 SP01).

 

Cheers, Daniel

 

 

 

Transportation Management Missing Functions/User expectations - Freight Order Management

$
0
0

This document is created to summarize the functionalities which are not supported by SAP Transportation Management. These functions are real questions from customers therefore you can see here some concrete examples.

 

Create a Forwarding Order from an export Freight Booking


It is not possible to create manually an FWO from an export FRB. If you try to create it (by seleting 'Create Forwarding Order' on the FRB UI header) the following error message appears:

'Action has not been processed successfully because of failed validations'.

 

This functionality is disabled because there isn’t seen a business case behind this. It is only designed for import bookings.

An alternative solution can be if you create the export FWO out of the cargo item(s) itself. As you have to maintain anyway the forwarding data in item details you have to select the cargo item(s) and press button ‘Create Forwarding Order’.

 


Cancellation email about carrier removal

 

If a carrier is removed from an Awarded Freight Order the system doesn't send a cancellation email to the carriers even though an XML message is generated: TransportationOrderCancellationRequest_Out.

 

The cancellation email is only supported as part of the Tendering process. Once the tendering is completed, this is no longer available.

 

 

The Departure Date is can be changed in fixed Freight Order

 

An FRO can be fixed by clicking on Fixing --> Fix. After that you can check this status on tab Statuses. Even though the FRO is fixed the Depature Date is can be changed.

If you do not get a system message about the fixing you should check the message settings in Customizing (TA SPRO -> Transportation Managemen -> Basic functions -> User interface -> Define message settings).

After an FRO fixing you cannot do any further planning or change existing planning like unassign FU, unassign existing carrier and assign new one etc. But you can change the dates as there could be delays, unavailability of handling resources etc. This is allowed as per standard behavior. You can check the help document where it mentions about what is not possible to change when a document is fixed.

http://help.sap.com/saphelp_tm90/helpdata/en/62/a8e71895594a63886f30ac3187b6ba/content.htm

 

 

Freight Unit Carrier ID is not updated


If the Carrier ID is changed on the Freight Document the Freight Unit Header is not updated automatically. In standard the carrier is not updated on freight unit level. You have to trigger the update task at freight unit level when changes happens at freight order carrier assignment.


 


Create Freight Order type with transportation mode Air/Sea/Inland Waterway is impossible

If a new freight order type is created in TM Customizing you can select only 'Road' or 'Rail' for transportation mode. TM use Freight order for land based transportation and Freight bookings for air/sea based transportation. Thats why only road and rail are listed for Freight Order. When you define a Freight booking type, depending on transportation type  air or sea, other  transportation modes would be displayed.

 

An Alternative solution can be if a new transportation mode is defined under Transportation Lane --> Transportation Mode by selecting '3 - Inland Waterway' as 'Means of Transport' and '1 - Road' as 'Transportation Mode'.  This can be work but this workaround has limitations.

 

 

Freight unit cannot be added to Freight Order via BOPF

 

You cannot add a Freight Unit via action ADD_FU_BY_FUID to Freight Order because a dump is occured. The standard way is to add FUs to FROs on the UI. The Test tool used for business is not supported.

 

 

TransportationOrderGenericRequest: Creation type change from G to S

 

TM will not support the creation type S as standard solution. The creation type S influences also some other things like the UI behaviour, but this is currently only done and evaluated for freight orders.

TM is currently not supporting ERP shipment integration for Bookings. The B2B Generic Inbound Service is not the standard interface to create bookings out of shipments. Therefore there can raise more issues which are not supported by this service for shipment integration.

You could change the creation type by modification or by an implicit enhancement:


Class: /SCMTMS/CL_TOR_GENRC_RQ_IN_SRV
Method: CREATE_BOOKING_VIA_FACTORY
Change there the creation type in the call of the method /SCMTMS/CL_TOR_FACTORY=>CREATE_TOR_BO.

From a standard perspective, the A2A service TransportationOrderSCMRequest_In would have to be enhanced to support bookings, too.

 

 

Missing 'Cost Distribution' tab on Service Order


Currently the Cost Distribution is only supported for Freight Orders and Freight Bookings. Therefore the 'Cost Distribution' tab is missing from the Service Order and the checkbox 'Enable Cost Distribution' is also not available in Service Order Type in Customizing.

You can see on this URL the Stucture of the Freight Order:

http://help.sap.com/saphelp_tm91/helpdata/en/f0/759d9fb6ab4468b121c16b186cc8a5/frameset.htm

 

You can see on this URL the Stucture of the Service Order:

http://help.sap.com/saphelp_tm91/helpdata/en/1c/557cbf85a14fb880acfb4e825232ff/frameset.htm

 

You can find more information about Cost Distribution Management on this URL:

http://help.sap.com/saphelp_tm91/helpdata/en/79/d0f8ff05c84ac18a24f124542269d3/frameset.htm

 

 

 

'Use Current Value as Default' does not work as expected

 

A value of a field (for example on a FRO on General Data tab field Purchasing Organiztaion) can be set as default by right clicking on the field and selecting User Setting --> Use Current Value as Default. However, after the setting if a new FRO is created from a FU the Purchasing Organization is not the default as extected.

 

The 'Use Value as Default' feature is a pure UI functionality provided by the UI framework (WebDynpro). It works on the following way: when the screen is displayed and the field content is empty, then WD fills the default value in the input field. At the  next modifying roundtrip, this value is sent to backend as modification, as if it were typed in by the user. The TM application does not register that (neither that a field has "default" values, nor the fact that a certain value was not typed by the user).

The default value applies to the input field if there is no content in it. For this particular example, if the freight order is already created with an organization in it (via settings in FRO type, or by creating application), then the default from the UI field does not apply.

 

Also, it requires UI - more precisely, the exact field - to be rendered in edit mode. If the user creates the freight document via e.g. FU stages and does  not navigate to FRO screen to modify "General Data", then WD has no chance to populate the default value in the input field.

 

Therefore this UI feature must not be used as a reliable replacement or alternative to TM functionality . Especially when for organization units there are some well documented means to determine values automatically- including in freight documents.

 

 

 

Cancelled Freight Orders are getting recreated automatically


If a Freight Order is cancelled the Freight Unit Building Rule recreates it automatically. This is a shortcut process in which no Freight Units are created for any trabsportation request (such as delivery) but immediately a Freight Order is created. Here's used a Delivery-based Transportation Requirement type which has automatic freight unit building enabled. In this situation the Freight Order will always be equivale to the transportation requirement. Therefore if the Freight

Order is cancelled it will be recreated automatically again which is correct by design.

If a cancellation is to be done it is on the requirement side, i.e. the order/delivery must be cancelled in ERP.

 

 


Incorrect Purchasing Organization in Service Order


If a Service Order is created from a Freigth Order the Purchasing Organiztaion is not the default value which is maintained in Customizing of Service Order type. The Purch. Org. is taken over from the predecessor Freight Order. If the Service Order is created not from the Freight Order the Purch. Org. is taken from the Service Order type customizing.

A solution can be if a post exit is created for method /scmtms/cl_tor_factory=>create_tor_service_order. In this exit the Purch. Org. can be changed regarding the needs.




Scale Base Type and Calculation Base in TM

$
0
0

Scale Base

Definition

Defines how the system interprets the scale.

Use

A scale base is a parameter or a factor that can influence transportation charges. Possible scale bases include the following:

  • Product
  • Package type
  • Weight
  • Volume
  • Means of transport
  • Location
  • Distance
  • Business partner

 

 

 

Calculation Base

 

Definition

Identifies the actual base or factor with which the system calculates the charges for the scale.

 

Use

There can be various scenarios in which the system must calculate a charge for different forms of weights, for example, gross weight and net weight. In this case, both gross weight and net weight correspond to the scale base Weight (W), whose dimension is mass. However, by definition, gross weight and net weight are two entirely different charge aspects. Therefore they have two different calculation bases, such as "W1" for gross weight and "W2" for net weight.

To follow the scenario given here, you define a calculation base for every scale base. This calculation base is the final element in the charge determination. This means that the calculation base is used to determine the charges.

 

Example

For a scale based on distance, the calculation base can be the absolute distance between the source location and the destination location.

You enter data as follows:

Scale BaseD (Distance)
Calculation BaseD1 (Absolute distance between the source location and the destination location)

 

You can define scale base and Calculation Base in SPRO --->

Capture.PNG

TM中文文档 (TM Chinese Documents)

$
0
0

这里的关于SAP Transportation Management (运输管理)的中文文档,主要包括SAP TM的产品战略,路线图,功能介绍和系统演示等,以供对SAP TM解决方案感兴趣的咨询顾问、市场推广人员和客户参考和使用。

 

目前我们有如下资料:

 

SAP TM Level 1 概览

SAP TM Level 2 详细介绍

360度可视化运输计划管理

SAP供应链执行平台战略

SAP运输管理(TM)在矿业的解决方案概览

运输管理创新展示

从供应链到需求网络 - SAP供应链发展展望及路线图

 

我们会持续添加或更新相关文档。

感谢您对SAP TM的关注!

 

 

Here are some Chinese documents about SAP Transportation Management, mainly include SAP TM product strategy, roadmap, functional introduction and system demos, etc. These documents are for TM consultants, marketing people and customers who are interested in SAP TM solutions.  

 

Currently we have below documents:

SAP TM Level 1 Overview

SAP TM Level 2 Details

360 Degree Visualization of Transportation Planning

SAP SCE Platform Strategy

SAP TM Overview for Mining Industry

SAP TM Innovation Show

From Supply Chain to Demand Network – SAP Supply Chain Development Roadmap

 

We will continuously add new materials and keep them up to date.

Thank you so much for your interests about SAP TM!

SAP TM Enhancement Guide Prior Publication of Chapters 1 - 7

$
0
0

The SAP TM Enhancement Guide now with chapter 7 (print forms and PPF configuration) reworked and a new section 5.4.9 (Integrating an enhancement UI application into NWBC).

View this Document


How to Use the Generic Extraction for SAP EM in SAP TM

$
0
0

This document illustrates how the generic extraction for SAP EM can be used in SAP TM and which prerequisites have to be met. With the generic extraction, which is based on customizing only, additional parameters, expected events or event types can be extracted for SAP EM.

View this Document

Featured Content for SAP Transportation Management

$
0
0

EKT - Classroom or Virtual Bootcamp

Access here

Presentations to view and download from the

SAP Infotag für Lager- und Transport Management

TM Documentation - Update in the Help Portal

Here the link to the Help Portal for TM

SAP TM Collaboration Portal - Overview

View this presentation here

Early Knowledge Transfer for TM 9.2:

Access here

Recordings here

 

How to use 'Strategic Freight Procurement'

Business Scenarios for Strategic Freight Management

SAP Named Market Leader in Transportation Management Systems and Selected Warehouse Management System

ARC Report 2014: SAP is again Number 1 in Transportation Management Systems (TMS) and in Warehouse Management Systems (WMS)

Transport and Logistics Infoday in Mannheim

This T&L Information day is a well established highlight for the Industry

TM Optimizer - How to Guide

Latest Version

TMP028: NWBC

$
0
0

This Episode of TMP is about the NetWeaver Business client, the cool grandchild of the good old SAP GUI. We look into the settings, installation and the very cool search providers.

Download this Podcast

Podcast Type: Audio

SAP TM Enhancement Guide Publication of Chapters 1 - 8

$
0
0

The SAP TM Enhancement Guide two new sections 3.4.4 Status & Action Managent (Consistency Groups) and 3.4.5 Change Document Adapter Enhancements. In addition the new main section 8 Enhancing further Objects, Features % Functions was created with a first (draft only) topic Gantt Chart for Planning Functionality.

View this Document

SAP TM Enhancement Guide Chapter 1 - 8

TMP029: TM 9.3 Refactoring: UI

$
0
0

As good agile developers we did some refactoring in TM 9.3. This episode is about the UI part of the refactoring. We talk on why, where and how we refactored. TECH Warning: This one is really technical, if you liked the FBI episode, you will love it, if you don´t know what FBI (in TM context) is, you may skip this episode.

Download this Podcast

Podcast Type: Audio

SAP TM Enhancement Guide Chapter 1 - 9

$
0
0

Changed the sequence of chapters 8 + 9. 8 Deals with Service Enhancements and 9 is now the former chapter 8 dealing with Enhancing further Objects, Features & Functions.

View this Document


Transportation Management Missing Functions or User expectations II.

$
0
0

This document is created to summarize the functionalities which are maybe not clear on SAP Transportation Management. These functions are real questions from customers therefore you can see here some concrete examples.

 

 

 

Freight Unit is not splitted

 

You have a Freight Unit which is created from a Sales Order. The Freight Unit Builidng Rule of the Freight Unit allows to split the items. As the quantity in the created Freight Unit is more than the 'Split Quantity' which is maintained on the FUBR, it is expected to split the FU. However, the FU is not splitted after it is created on TM.

 

You have to check the item category of the item on your Sales Order. If the item category is schedule-line (SHL), during the FU creation it is checked whether partial delivery is allowed. If it is not allowed (PD_CTRL_CODE of the item is not '1 = Partial Delivery'), it is not possible to split the item during the FU creation.

 

 

FB is cancelled when Direct Shipment FWO is unassigned

 

If you unassign a Direct shipment Forwarding Order from a Freight Booking, after the unassigment the FB is automatically cancelled.

In this case you have to check the consolidation type of the Freight Unit on table /SCMTMS/TOR. If the FU has consolidation type 'Direct Shipment' (CONSOL_TYPE = '01'), after the FU is assigned to the FB, the booking itself becomes a direct shipment document and will be deleted when all freight units are removed.

 

 

Manually entered dates are not saved on the Freight Order/Booking

 

 

You have a Freight Order or Booking and a Freight Unit which is created from ERP (from Sales Order, DTR, etc.) You assign the FU to the FO/FB. The arrival and departure dates are updated on the FO/FB from the FU. After changing the dates on the FO/FB the dates automatically changing back to the original dates after saving the FO/FB.

In this case you have to check the customizing of the FO/FB type. If DEF_CHACO is maintained as 'Default Change Strategy', after saving the FO/FB this strategy performs a rescheduling and the dates change back to the original dates.
You can find more information about the DEF_CHACO and the change strategies on the following URL:
http://help.sap.com/saphelp_tm93/helpdata/en/9c/0e9410a4ff462ba259010673b64fc1/frameset.htm

 

 

Net weight is not populated on Freight Unit UI

 

 

You have a Freight Unit which was created from a Sales Order or Puchase Order (Sales/Purchasing Order -> Order-based Transportation Requirement -> Freight Unit). On the OTR both of the gross weight and the net weight are displayed however on the Freight Unit 'General Data' tab only the 'Gross weight' is populated, 'Net Weight' is blank.

This can be caused because on the relevant Freight Unit Builidng Rule 'Gross Weight' is maintained as 'Planning Quantity' therefore the sum of the items will only be built for this quantity. If the expectation is to display the 'Net Weight' on the FU header level, 'Net Weight' needs to be added to 'Planning Quantities'.
Please note that it is not possible to add net weight and gross weight to planning quantities as only one quantity of dimension mass is allowed.

TMP030: Package Builder

$
0
0

This episode is about the package builder, a new functionality introduced with TM 9.3. The package builder can consider packaging rules to find out how many packages/pallets will be most likely used when transporting the materials as defined in the orders and hence allows a more accurate planning even before the actual pallet information is available.

Download this Podcast

Podcast Type: Audio

TMP027: Strategic Freight Procument

$
0
0

Strategic Freight Procurement is focused on the target group of shippers as TM customer. The shipper is sending Freight Agreement RFQ's to carriers/LSP's in order to create/renew a Freight Agreement for a certain trade lane, mode of transport , etc . The carriers/LSP's will respond to the RFQ and the shipper can then decide which offer will get awarded.

Download this Podcast

Podcast Type: Audio

TMP031: BOPF part 1

$
0
0

It´s all about BOPF (or BOBF :->) and how we use it in TM. This part covers the main elements of BOPF, however there are some missing parts which we will cover in a follow up episode.

Download this Podcast

Podcast Type: Audio

TMP028: NWBC

$
0
0

This Episode of TMP is about the NetWeaver Business client, the cool grandchild of the good old SAP GUI. We look into the settings, installation and the very cool search providers.

Download this Podcast

Podcast Type: Audio

Viewing all 64 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>