It is a fact, that the tendering error messages we get are not precise and don't really explain the problem. In many of the TM systems, F1 help doesn't work properly on the web browser. To understand the problem was a big nightmare for me, until I found this, thought to share here and make life easier for similar people out there.

1) In TM system - go to transaction SAAB

2) Enter checkpoint group "/SCMTMS/TEND_LOG" & Press "activate"

3) Switch to tab "Activation" & Press button "server"

4) Double click global settings, a window will pop up. In the popup, match the settings as in below screenshot:

5) Once you match the above settings, save the checkpoint group. There will be a popup asking maximum validity period of the activation, set a suitable end date for the activation (I don't recommended to activate the logging longer than required, it might be sufficient to activate the log for a couple of days)

This setups the log. Now to view the log follow below steps:

1) Once the log is active, whenever an error or unexpected situation occurs in the tendering process it is logged in keys(as shown below). If you want to look up a specific instance log then copy the key highlighted below and go to step 2 or else go to step 2 ignoring the copying of key.

2) In TM - box go to transaction SE38. Execute report /SCMTMS/DISPLAY_LOG

3) If you have copied the key in step 1, insert it in the yellow marked fields below, else keep them blank and execute.

4) The log details will provide (1) The callstack of the running program at the point in time when the error or unexpected situation

occured (2) Context information, which is created at the point in time when the error or unexpected situation occured

5) You can also see the error message numbers like "/SCMTMS/TEND175" - to get further information on this, you can go to SE91, enter "/SCMTMS/TEND" as message class and hit display

5) You now look for the message number, which is last three digits of error message (eg:- for error "/SCMTMS/TEND175", you should lookup 175)

Once you find the message, and you understand or can figure the problem, well and good. Or else a experienced ABAPer can easily help you now using "Where used" list to trace the problem using breakpoints.

All the best!

Test determination is a feature that allows filling automatically Text Collection of SAP TM documents with, well, texts. For instance, in Air Freight scenarios, the texts for Nature of Goods are quite standardized and can be filled automatically with predefined templates that need only minor adjustments. Other scenarios require an automatic propagation of e.g. shipping instructions - from forwarding orders or ERP-based requirements (OTR/DTR) to the freight documents, so that they can be transmitted to carriers during subcontracting.

The functionality was intended actually for SAP TM 9.0, but it required a coordinated development in two software components – in SAPTM as well as in Business Suite Foundation (SAP_BS_FND), since the Text Collection is actually a reusable business object from this layer. Due to some TM-specific modelling particularities, the out-of-the-box BS FND functionality did not work properly in TM 9.0.

The development can be used fully in 9.1 and 9.2 – even if it took some additional SAP Notes (2111951, 2113678, 2113736, 2114090, 2116402 and 2116403) to have it working satisfactorily.

The text determination can be set up in the customizing of Text Schema (IMG path Cross-Application Components -> Processes and Tools for Enterprise Applications -> Reusable Objects and Functions for BOPF Environment -> Dependent Object Text Collection -> Maintain Text Schema). I assume the reader is familiarized with the text collection concepts – if not, feel free to consult the documentation. Also, it should have gone without saying: some basic knowledge about TM internal modelling (business objects, nodes, associations) is a prerequisite when setting up this feature.

Text Schemas can be attached to SAP TM documents via type customizing (e.g. IMG path Transportation Management -> Forwarding Order Management -> Forwarding Order -> Define Forwarding Order Types).

Coming back to Text Schema customizing, the functionality is activated by specifying an Access Sequence for a text type while maintaining Text Type to Text Schema Assignment. The access sequence is a collection of so-called Accesses– steps that attempt to find a text according to some logic. Both concepts can be maintained in the same customizing cluster – we’ll see immediately how.

When an access sequence is maintained in the type-schema assignment, the flag Reference becomes meaningful:

• If left empty, the result of the determination is written immediately in the target document, but there is no “update handling” (if the source of the texts changes, the text in the target document remains untouched).
• If the flag is set, the result of text determination is not persisted completely in the target document – the text content is left intentionally empty. Every time the collection is accessed, the text determination is executed again and the consumer (e.g. the UI) sees its current result. As soon as the text is modified in the target document, it becomes “local”: the changed value is saved in the text content and the reference flag is removed. It's worth noting that this option poses a certain runtime overhead, since the determination must be executed more often.

There are four types of accesses: (1) association navigation, (2) association navigation with node attributes, (3) external BO access and (4) external source. #1 and #2 are similar to each other – they attempt to follow some BOPF associations to reach another text collection representation node, from which the requested text type is copied (if existing). #3 and #4 rely on external classes, implementing certain ABAP interfaces.

I am going to describe now the necessary steps required to set up the text determination for the following use cases:

1. Use a given standard text (maintained using t-code SO10) as soon as the TM document is created.
2. Copy a text from one related TM document
3. Copy and/or adjust texts from more related TM documents

--

Use-case 1: standard text

Standard texts can be defined in transaction “Define Standard texts” (SO10):

To use them in text determination, we need an access of type External Source (we obviously cannot use BOPF associations to get there, and we need to provide some parameters – the identification of the text). External source require a so-called external text determination class. For this particular case, there is already a library class that can be used, delivered in BS Foundation software component - /BOFU/CL_ACCESS_SO10_TEXT:

The parameters accepted by this (unfortunately still undocumented) class are ID, NAME and OBJECT, which correspond to the unique identification of a SO10 text:

Afterwards, create a new access, using this external source:

Set the actual values for the parameters (this way, you can create more accesses with the same external source, each one pulling a specific standard text):

Create a new access sequence:

Add the created access to the sequence. You can have more accesses here, the processing stops as soon as one of them successfully finds a text (so the sequence number is important):

Now go the text type to text schema assignment and fill in the created access sequence for the desired text type:

In the my example, I modified the SAP-delivered schema FWOHDR, which is assigned to the forwarding order type FWO. As a result of the steps above, creating a forwarding order of this type leads to the automatic creation of a NOTE text having content To be packed with extra care.

Use-case 2: copy FWO/OTR/DTR text to freight unit

Here we can use the simplest method – association navigation. The “business entities” must be defined in advance in another Foundation customizing (IMG path Cross-Application Components -> Processes and Tools for Enterprise Applications -> Reusable Objects and Functions for BOPF Environment ->General Settings -> Maintain Business Entities) and represent a combination of BOPF business object and node:

The path to be followed must described in Access Details– starting from the target documents to the requested text collection object representation node of the source document. So we’ll use the association BO_TRQ_ROOT to navigate from freight unit header (the ROOT node of business object /SCMTMS/TOR) to forwarding order/ERP-requirement header (ROOT node of /SCMTMS/TRQ), then the association TEXTCOLLECTION from there to the representation node. It looks like a rudimentary version of the TM Data Crawler:

Then create an access sequence:

Attach the new access to the new sequence:

Finally, attach the sequence to the desired text type of the relevant text schema (here I use a newly created schema, since there is no SAP-delivered schema for freight units... yet):

As soon as a freight unit (which has a type that references this schema…) is created, the corresponding NOTE text from FWO/OTR/DTR header is copied.

One side-remark: in most FWO-based scenarios, the freight unit is created automatically soon as the consistency checks allows it – entering a text in forwarding order after this point does not lead to the update of the freight unit! This can be overcome by either disabling the automatic creation of freight units (in FWO type customizing), or by changing the items in FWO (which usually lead to a rebuild of the freight unit). In ERP integration scenarios, however, the document (OTR/DTR) is usually created completely in one step, including texts, before freight units are built. But if some texts are added manually in OTR/DTR afterwards, these too are not propagated automatically.

Who knows, perhaps SAP will offer in the near future a possibility to manually trigger the text determination to overcome such cases (e.g. a button in the Notes UI).

This procedure can be used every time when a 1:1 relationship between business entities exists. For instance, you can use it to propagate FOW/OTR/DTR header/item texts to freight order items as well.

Copy texts from more source documents into one text

Let’s consider a more exotic requirement - to propagate the freight unit texts to the freight order header. Here there is a problem: usually there are more freight units assigned to a FO, but a certain text can only be created only once in a text collection. Therefore, the association-based approach described above does not work (the text from one freight unit only will be determined).

One solution is to concatenate the text content – but this is a more complex procedure, that can only be covered again by a specialized determination class. We’ll use again external source as access type.

The most important step is to create a class, implementing the interface /BOFU/IF_ACCESS_EXTERNAL_TEXT, and then write the code for method GET_EXTERNAL_TEXTS. I attached the source code of my demo class to this article. In a nutshell, my implementation finds all freight units attached to a freight order by using the association REQ_TOR, then goes to their header-level text collection and finally concatenates the matching texts into one content, inserting in the process some contextual information (the identfication of the freight unit) as separator. When the texts are available in the requirement documents (FWO/OTR/DTR), one can use in coding the association BO_TRQ_ROOT_ALL to directly access the ROOT nodes of these documents - this avoids the additional determination required to propagate the texts from there to freight units.

After the class is created and activated, create a new external source and specify the new determination class; my implementation does not require parameters (although one can imagine a more generic class that can find texts in various documents):

Create a new access, and specify the new external source:

Then again create a corresponding access sequence:

Attach the access to it:

And attach the access sequence in the type-schema assignment (again, there is no standard text schema delivered by SAP for freight orders, so I created a new one and attached it to my FO type):

After attaching some freight units to my freight order, the text NOTE contains now a concatenation of the corresponding freight unit texts:

My sample code takes data from the NOTE text of the freight units, but with external access some other options are possible, like combining more text types into a single entity in the target document.

Another fact worth mentioning: text determination is usually executed only when the corresponding node instance is created. For freight orders, there is a special logic - the determination at header level is executed every time a requirement is added to (or removed from) the freight order.

Hello,

     I searched but couldn't find a right answer.

I would like to know where the TOR BO is used, and where the TRQ is used.

Also, difference between freight order, and forwarding order, and what BOs they use?

Sorry for the pretty elementary question.

Regards, Bharat

Hi,

Is there any way we can capture driver license number in the freight order since I did not see it in general data tab or resouce master data

Hi Experts,

I hope you can help me with the following question. I have the Business partner 'Goods Buyer' available in the OTR which represents the Sold-to in the respective Sales Order on ERP side.

I'd like the system to copy the partner Goods Buyer from the OTR to the Freight Unit automatically since I need the partner to be considered in incompatibilties on FU-FU level.

Can you please let me know what is the easiest way to accomplish this requirement?

Thanks for your help

Thomas

Hello Sirs,

After created a sales order in ECC and transferred to TM via XI, the queue remains with STOP status. Entering in transaction /SAPPO/PPO2 I’m facing the error “Schedule Line Item 100001 delivery date is missing”. The delivery date is filled in ECC side.

Is there something that I need to check in TM regarding delivery date?

Thanks.

Hi Experts!

I hope you are fine.

I need help with error in my TM. When I'm try generate Settlement Document, the system show me this message:

I've already configured CHARGES PROFILE with this Purch. Org:

My freight order type, is set for my FDS TYPE too:

This is my configuration for FSD TYPE:

This is my configuration for FREIGHT SETTLEMENT PROFILE:

Anyone have idea why my settlement don't work?

Thanks a lot.

BD
Renato

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

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.

I am working on shipper scenario where  it shows that we will not be sending back DTR to TM system once we have created the FO and sent the Delivery proposal back to ECC. But say in case

1.  I change the quantity in Delivery in ECC , then the SO in ECC will have an open quantity which will not be visible in TM as the FU will show as fully consumed . Then how do we manage this.

2. Plus the Qty in TM and ECC Delivery will always be different . What will be the way to remove this inconcistency.

Hi,

Can you let us know the best practise/method available to upload the master data like freight agreement/lane/location/resource  details in TM system for a shipper scenario.

Message was edited by: Michael Appleby

Hi,

Since for LSP scenario we have export /import process related to export/import FWO, similarly do such process exist for shipper scenario since we dont have export/import FWO .

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.

Actual event date/time is not updated in Freight Unit

After changing the actual event date/time in the Freight Order the FU’s actual event date/time are not updated.

The current logic for the execution information does not propagate changes to other documents. The event date is changed in FO manually. The event date is not propagated to the FU in this case because of the event origin. Changes are not propagated, if the origin of the execution information is not the document itself.

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.

Hi experts

Can any one help me out that how the details are updated in the following table /SCMB/HRP5561 in SAP TM ?

Thanks in advance

Sudharsanan

Hi Experts,

I am facing an issue during Scheduling of Freight Orders. I have maintained 1 hr for Loading and Unloading times in the Planning Profile and set the system up to consider Freight Unit Dates.

The Freight Order has only 1 Freight Unit stage - so a fairly easy example.

Now when I look at the Freight Unit Dates after the scheduling run, the unloading starts at 02/13 23:00 , so even before the acceptable start date.

Therefore my question: Is it a bug or a feature? According to my understand this should not happen.

Thanks,

Thomas

hi,

There is a requirement to create FSD document after the PGI (of the delivery) automatically. Could you suggest a way to do that? Please note this is for a Shipper scenario.

Options that was explored & discarded.

1. Use txn: /n/scmtms/sfir_create - report does not have anything related to the PGI status

2. Use selection profile to filter out freight orders (using additional selection attributes using selection values) for which the deliveries are PGI'ed- the

3. Conditions in selection profile - could not find a condition type appropriate for the freight order selections.

4. Use txn: /n/scmtms/sfir_create with Freight order life cycle status - Life cycle status are not directly dependent on PGI status

Could you suggest me the options?

Thank You,

Vasu

Dear Experts,

We are looking for some suggestions from your side.

When we should unlock the object and when we should not with respect to releasing the transport request.

Like what would be the best practice.

Thanks in advance.

With Regards,

Tejas Dave.

Hi,

I have 2 test systems in my landscape, one is for system test(system 1) and another is for integration test(system 2).

now i have a requirement to differentiate transports while releasing from Dev system. Drop A transports should be imported to both systems(system 1 & 2) and drop B transports should be imported to system 1 only. Both transports should be going live in different months.

How this can be implemented(Will creating projects in SPRO or creating transports groups in STMS is possible)?

Can any one please suggest me.

Regards

Chandu

Hi All,

How to add Rate Tables/Calculation Sheets/Agreements etc in a Transport Request ?
Because while creating its not asking for Transport reequest.

Reply ASAP pls.

TM - 9.0

Thanks,
Michael.

Hi TM Gurus,

How the following validation can be be turned off.

In our scenario, some times Net Wt may be more than Gross weight.Thanks in advance.

Thanks,

Michael.