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 events in the drop-down menu are sorted ascending in alphabetical order.

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/V_TOREVT and click on Create Entries:

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

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

     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:

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

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.

Possible to save the FO without Vehicle Resource

It is expected and standard behavior that the FO can be saved if the field VEH_RES_ID_T is blank. Many times when a FU is planned or a FO is created the vehicle resource is not finalized or this informtaion is not available. For example:

• The FO can be created from the FU stage where the vehicle information is not available.
• The FO can be created from the FWO stage where this infomrtaion is also not available.
• In Transportation Cockpit we can just use the option 'Create Freight Document' for a FU stage.
• A FO is created separately and the FU is assigned to the FO. The vehicle might be added later.
• When a FO is created from a schedule, the vehicle information may not be available.
• A pickup/delivery FO could be created from a FB where the vehicle information is not available.

Therefore it is not desired to make a the vehicle field as mandatory for FO while saving.

Freigth Orders created from DTR has no service level assigned

The service level is intentionally not taken over from the DTR (or from the FU) into the freight order. It can be defined in the Customizing of the FO type. The service level in a DTR is defined by the customer order service level in ERP which indicates urgency of that order for the customer. The service level of the frieght order defines the service level for the freight order agreed between your company and the LSP which can have completely different levels. Additionally, if FU is created, there can be multiple freight units assigned to the same freight order with different service levels on freight unit level.

Hence the service level is only taken over into the item of the freight order.

If in your specific case you want to take over the value, you can e.g. create a strategy for the freight order or enhance the planning strategy.

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 events in the drop-down menu are sorted ascending in alphabetical order.

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/V_TOREVT and click on Create Entries:

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

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

     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:

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

The Federal Maritime Commission is the independent federal agency responsible for regulating the U.S. international ocean transportation system for the benefit of U.S. exporters, importers, and the U.S. consumer.

The FMC ensures competitive and efficient ocean transportation services for the shipping public by:

• Reviewing and monitoring agreements among ocean common carriers and marine terminal operators (MTOs) serving the U.S. foreign oceanborne trades to ensure that they do not cause substantial increases in transportation costs or decreases in transportation services
• Maintaining and reviewing confidentially filed service contracts and Non-Vessel-Operating Common Carrier (NVOCC) Service Arrangements to guard against detrimental effects to shipping
• Providing a forum for exporters, importers, and other members of the shipping public to obtain relief from ocean shipping practices or disputes that impede the flow of commerce
• Ensuring common carriers’ tariff rates and charges are published in private, automated tariff systems and electronically available
• Monitoring rates, charges, and rules of government-owned or –controlled carriers to ensure they are just and reasonable
• Taking action to address unfavorable conditions caused by foreign government or business practices in U.S. foreign shipping trades

Now the question coming. What does the TM for ocean carrier could achieve in FMC topic?

The parts marked as red which are related to e-system integration. Let's simple define them as "Service Contracts Filing" and "Tariff Publish".

What's service contract and how to filing it?

http://www.fmc.gov/resources/how_to_file_service_contracts.aspx

FMC provide the Contract Management System(CMS) to incorporate the filing of service contracts. So TM could integration with the CMS to automatically filing the service contract.

The draft solution could be like that:

Model the service contract as FWA in TM.

When FWA release for charge calculation, using the PPF function to trigger the integration with CMS.

How to publish the tariff?

The tariff portal/website of ocean carrier should be published in the FMC portal.

https://www2.fmc.gov/FMC1Users/scripts/ExtReports.asp?tariffClass=vocc

The draft solution could be like that:

TM could provide the tariff (FWA) POWL in the FMC portal.

Or ocean carrier could integration the TM with own portal. And then publish the portal to the FMC.

Of course, there are a lot of special requirements about FMC should be implemented or enhanced in the TM.

Best Regards

Clark Huang

SAP Named Market Leader in Transportation Management Systems by ARC Advisory Group:

For the fourth year running, SAP was named leader again in ARC’s annual market research study Transportation Management Systems Global Market Research Study by Chris Cunnane, Steve Banker and Clint Reiser. ARC is one of the leading industry analyst firms covering the Supply Chain Execution space. ARC published their annual Transportation Management Systems Market Study and SAP was ranked #1 in many categories. For further details, read the press release.

Application details & Help Portal

SAP TM 9.3

SAP TM Localization for Russia 1.0

SAP Yard Logistics that integrates with SAP TM & EWM

SAP Transportation Resource Planning 1.0

SAP TM Packaged Solutions - RDS

SAP TM Training & Curriculum

Early Knowledge Transfer for TM 9.2:

Access here

Recordings here

SAP TM Collaboration Portal - Overview

View this presentation here

How to use 'Strategic Freight Procurement'

TM Optimizer - How to Guide

Latest Version

Today we shall discuss the functionality as how tax determination process works when settlement documents are transferred from TM to ECC.

There are two configurations-one at business partner side and other at charge type which enables SAP TM to determine tax code in ERP when the settlement documents are saved and transferred to ERP.There is a tax influencer concept which is transfererd to ERP and this transfer is valid for below enclosed documents:

a) FWSD ( forwarding settlement document ) applicable for LSP scenario

b) FSD applicable for both LSP and shipper scenario

Since in the invoice integration process between TM-ECC, the account detremination and tax calculation always happens in ERP, hence tax code and tax calculation uses the condition type concept to determine the tax value.Although this is a standard procedure in ERP but below enclosed is the process followed for determining taxes:

i) Tax conditions in the pricing procedure of SD/MM module in ERP

ii) Tax conditions via access sequence which enables tax code determination

iii) Access sequence in addition to TM passed parameter helps to determine tax code in ERP

Before we discuss about the configuration and master data required to set up the above process let me highlight the various scenarios where this functionality can be used.

On a LSP scenario once the product/cargo item reaches to customer base don the forwarding agreement, the LSP bills the customer for the entire execution of transportation service. However the customer is also supposed to pay tax on the net amount billed by LSP as per the country and regional laws.

Similarly on the freight settlement side when the carrier sends the invoice to the shipper or LSP for payment of the transportation service rendered by them, the tax amount can also be included on the basis of the net amount charged by carrier. This amount when transferred to ERP the tax influencer parameter will be able to do the tax determination in ERP.

In SAP TM, tax determination occurs at 2 levels a) Charge item level  b) charge line level

Configuration settings

Below enclosed is the configuration to be done so that this functionality can be implemented.

a) Define tax type and tax group per country in SAP TM-Tax types in TM  are condition types in ERP to determine tax and tax groups are classification indicators in SAP ERP.The config node is SPRO-Cross application components-SAP BP-BP-Basic settings-Tax type and tax group ( updated in attachment-Screenshot 1)

b) For forwarding settlement process, we can update in Transaction BP in TM if the specific business partner is to be set up per country and respective tax classification indicator.All this values are maintained under control data tab in Tcode BP in TM.This will help to transfer the payer settings from FWSD to ERP .

c) Define BP tax type and tax groups under SPRO-SAP TM-TM-Settlement-Tax as shown in screenshot 2.

Here the 1st config is to define tax at charge type level for countries-Here we need to activate the country for which tax activation has to be done.

2nd config is to define tax for  charges -Here tax type and tax group define dabove needs to be maintained per charge type per country for which we have activated the tax determination at charge type level.

Based on above setting when FWSD is saved and transferred to ERP, this will trigger SD billing document with each charge line in the FWO represents one billing item.

Similarly when FSD is transferred to ERP, tax group info will be passed for each charge type to service line during PO/service entry sheet creation in ERP.

Always remember the tax type and tax group are transfered from SAP TM to ERP for each charge line.

Similarly in ERP side under SPRO-Integration with other SAP components-TM-Invoice integration-Tax, we need to assign TM tax type and tax group  to ERP tax classification indicator.

Container tracking functionality in SAP TM was never realised in practise until SAP EM was used since SAP TM was mainly used for transportation of products or goods from source to destination location.However with SAP TM 9.2 SAP TM can now be used to transport equipements like containers.In older versions SAP TM assumed that containers has to be loaded before transportation process started but infact we also need to keep in mind that the containers transport journey starts much before it was loaded in shippers site.

Hence for any LSP scenario, if there was no empty container available from shipper then in that case empty container have to be hired/contracted from the carrier or LSP who is responsible for the entire transport execution.In this case the process flow is as follows:

a) Container picked up from container yard

b) Empty container transported to port of loading.

The process a.b is called empty container provisioning

c) Once the container was fully loaded ( FCL scenario) the transport is executed and then the container is unloaded at consignee location

d) Finally the empty container from consignee location comes back to container yard again

Process c,d is called as empty container return.

In order to map the process a-d , we can set up forwarding order and in the item details in the item hierarchy empty provisioning and empty returns indicator has to be set as X.Kindly note that container item has to be maintained in item hierachy.

In the locations/dates time tab of FWO, the source and destination location represents the loading and unloading point of container.However the container yards locations are not maintained in the FWO .

Secondly in the item details of the FWO, when we click on the container item, there is two new tabs called as empty provisioning and empty retuns.

In the tab for for empty provisioning, delivery location of empty container and the delivery dates are always prefilled.However both this data can be changed manually since specially the delivery location can be changed if shipper wants to receive the empty container at a different location.

similarly the empty return container tab is always prefilled with pick up date and pick up location which can be changed manually.

Similarly on the stages tab of FWO, dates and locations for empty provisioning/return can also be defined and maintained and also amended in the same tab.

Empty provisioning/return scenario is not supported for trailers and trailer units.

Its so difficult and long to download nwbc from the SAP market site.  Thus I am posting it here for you to download.

Of course, its free and all rights are reserved with SAP AG in Germany and other countries.

https://cloud.web.de/ngcloud/external?locale=de&guestToken=1BgFiq8YRW2xK1dWiBLqqQ&loginName

On many projects, people do not take time to install it and they use the Gui and type nwbc. Its a shame, please use it. It makes your life easier.

Advantages of nwbc:

-its faster then the GUI browser link

-its more comfortable to move between several tabs

-you can maintain favorites and display FO or FU with one click

-you can type part of the transaction name and it will bring you to the area

-you can move from dev to quality system with one click

Any more advantages ? If I have missed some, please add others.

When working with TM, I find it useful to look at all statuses at one glance, thus I am pasting here a summary power point of the standard statuses and how they are updated by EM. Hope, you find it useful.

The execution status at the header can be used to exclude FOs from the cockpit that have arrived at the final destination.

It allows you to show only freight orders that are "in execution" in a POWL.

The handling execution status on FO item level can be used to check what is the current status of the FU (loaded or unloaded ) but it does not say where.

For example, on the Fo item tab, customers can see which one of the FUs was already loaded. But, it changes to unloaded when its delivered and always shows the latest status.
The handling execution status on the stop level says what the status is AND where.
The cargo receipt status allows seeing if one product on a FU was delivered.

If you use standard EM events UNLOAD_END and LOAD_END to do your loadings and unloadings, these statuses will be updated automatically.

In addition, the logistics execution status on the FO header is updated with the last event which is visible on the FO POWLs.

A complete explanation can be found in the TM application help in the following link:

http://help.sap.com/saphelp_tm81/helpdata/en/62/a8e71895594a63886f30ac3187b6ba/content.htm?frameset=/en/32/a1ab88061a4df19ab2ee4f3688baed/frameset.htm&current_toc=/en/32/a1ab88061a4df19ab2ee4f3688baed/plain.htm&node_id=50&show_children=false

An action is similar to a Function module in ERP that you can use to do stuff for you instead of coding it yourself. But, whereas the FM is generic, an action does a concrete thing and a determination determines something and an association links two nodes. In BOPF, these are all different things. Advantage: you can search for things separately and in a categorized manner. To find one in TM, do the following:

-Use transaction /n/BOBF/CONF_UI
-You get the following screen:

-Double-click on /SCMTMS/TOR
-Open Node elements
-Choose the note to which the action is related
-I am looking for an action that updates the delivery status on the FO root level, thus I choose ROOT
-I am looking for an action, some coding that does something (association is a link between 2 nodes, validation validates something, queries are pre-defined searches, determinations can default data based on other data for example etc  ).

-If I double-click on ACTION, I get all the names of actions that exist for the ROOT node of the FU

-Based on the descriptions, I am able to figure out which one could help me
-I find the action determine delivery status as follows:

This is just an example, it may be smarter to update the cargo receipt status on product level and let the standard update the delivery status on the FU when all products were delivered. But, it shows you how to find an action and that was the purpose.

The below coding shows how you can choose the action to set the cargo receipt status based on an EM event (unloading or proof of delivery for example).

data:
     lo_srvmgr_tor        type ref to /bobf/if_tra_service_manager,
     lo_change            type ref to /bobf/if_tra_change,
     lo_message           type ref to /bobf/if_frw_message,
     lo_tramgr            type ref to /bobf/if_tra_transaction_mgr,
     ls_key               type /bobf/s_frw_key,
     lt_key               type /bobf/t_frw_key,
     lt_stage_k           type /bobf/t_frw_key,
     lt_failed_key        type /bobf/t_frw_key,
     lt_failed_action_key type /bobf/t_frw_key,
     lt_return            type bapiret2_tab,
     lv_rejected          type boole_d.

   field-symbols:
     <ls_key>      like line of lt_key,
     <ls_rp_sydat> type /saptrx/rp_sydat.

   " Init.
   clear e_return_code.
   clear ls_key.
   ls_key-key = /scmtms/cl_tor_helper_root=>return_key_for_torid( iv_torid =  i_eai-event_msg-hdr-trxid ).
   insert ls_key into table lt_key.

   " Declare service manager
   lo_srvmgr_tor = /bobf/cl_tra_serv_mgr_factory=>get_service_manager( /scmtms/if_tor_c=>sc_bo_key ).

   " Set cargo receipt status to delivered
   lo_srvmgr_tor->do_action(
   exporting
       iv_act_key           = /scmtms/if_tor_c=>sc_action-root-set_cargo_receipt_delivered
      it_key               = lt_key
   importing
       eo_change            = lo_change
       eo_message           = lo_message
       et_failed_key        = lt_failed_key
       et_failed_action_key = lt_failed_action_key ).

   if ( lt_failed_key is not initial or lt_failed_action_key is not initial ) and lo_message is bound.
     /scmtms/cl_common_helper=>msg_convert_bopf_2_bapiret2(
     exporting
      iv_severity = 'E'
      io_message  = lo_message
     changing
      ct_bapiret2 = lt_return ).

     delete adjacent duplicates from lt_return.
   else.

     " Save Transaction
     lo_tramgr = /bobf/cl_tra_trans_mgr_factory=>get_transaction_manager( ).
     call method lo_tramgr->save
       importing
         eo_message  = lo_message
         ev_rejected = lv_rejected.

     if lv_rejected is not initial and lo_message is bound.
       /scmtms/cl_common_helper=>msg_convert_bopf_2_bapiret2(
        exporting
         iv_severity = 'E'
         io_message  = lo_message
        changing
         ct_bapiret2 = lt_return ).

       delete adjacent duplicates from lt_return.
     endif.
   endif.

If you want to know more about it, please refer to the enhancement guide from Holger Polch which explains everything very well and has coding examples.

https://scn.sap.com/blogs/SAP_TM_Enhancements

Regards

Petra

Hi Folks,

when learning TM for the 9.0 and 9.1 certification and on projects, I formulated many questions about TM which were coming up on projects and which I was asking myself from the online documentation. I also had many enquiries from others asking me how to prepare for the certification. Thus, I had develop the attached app for iPhone. It has around 250 questions about TM and will give you a percentage score at the end of the 80 random questions that each test is made of (spreading up the questions equally for each area). Of course, this is NOT coming from SAP and these are not the original exam questions. I am not allowed to publish them and I would not want to publish them or help someone cheat. All rights about SAP TM are reserved with SAP. My intention was more to share stuff on TM which is worth knowing, spread TM knowledge and make it easier and more fun to learn TM. These are freely formulated questions which help enhance your knowledge about TM or test your knowledge. Maybe, it can encourage more people to do the certification or to go study more in depth a certain area. It took me a few months to formulate these questions while travelling, on the week-ends and in the evenings and the development of the app was also not free of charge, so I hope its understandable that I did not want to give it out for free.  I have verified each question and tried to make them doubt free. Nevertheless, it may happen that you doubt about one or the other answer. If so, please write to me and let me enhance the catalogue. I am also very open to add more questions that you may want to contribute. There are so many things to know about TM, lets make the catalogue of questions grow together within the community. But, most of all, enjoy the app , I sincerely hope you will like it !

Petra

TM 9.0 Certification App for Iphone

TM 9.1 Certification App for IPhone

How to code a condition call  

This question is Not Answered.(Mark as assumed answered)

Petra Hunger  Jan 27, 2016 10:48 PM 

Currently Being Moderated 

Today, I would like to provide sample coding for a condition call.

In TM, most of the times, BRF+ conditions are used instead of custom tables known from ERP. The great thing about these conditions is that you can just provide the Fo number or FU number or OTR number to it and the code will read the related data and return a result. Where in SD, you had to read the table with the data, you can just input the FO and the method will revert back saying if this FO is relevant or not for this condition in lt_cond_result.

The following code can be used:

  REPORT zphu_cond_call.

DATA: ls_bo_inst_key     TYPE /bobf/s_frw_key,
       lt_bo_inst_key     TYPE /bobf/t_frw_key,
       ls_condition_id    TYPE /scmtms/s_condition_id,

       lt_condition_id    TYPE /scmtms/t_condition_id,
       co_message         TYPE REF TO /bobf/if_frw_message,
       lt_cond_result     TYPE /scmtms/t_boid_cond_result,
       lt_cond_result_all TYPE /scmtms/t_boid_cond_result.

CLEAR: ls_bo_inst_key, ls_bo_inst_key, ls_condition_id, lt_condition_id.

BREAK-POINT.

* specify the key of an example bo instance (here: a trq instance)

ls_bo_inst_key-key = '0050569F57AB1ED4A6989181F34473F6'.

APPEND ls_bo_inst_key TO lt_bo_inst_key.

*specify the condition to be executed
ls_condition_id-condition_id = 'ZTEST_PHU'.
APPEND ls_condition_id TO lt_condition_id.

* call method that reads the condition

CALL METHOD /scmtms/cl_cond_ol=>proc_conditions
   EXPORTING
     it_boinst_key            = lt_bo_inst_key  "<- your TRQ number
     it_cond_id               = lt_condition_id   "<- your condition name
     iv_do_not_return_no_hits = abap_true
   IMPORTING
     et_bokey_cond_result     = lt_cond_result "<- whether or not the condition is ok for this instance
   CHANGING
     co_message               = co_message.

* collect all results from condition for later processing
INSERT LINES OF lt_cond_result INTO TABLE lt_cond_result_all.

BREAK-POINT.

You can find this and other useful hints about TM enhancements in the TM enhancement guide from Holger Polch.

http://scn.sap.com/blogs/SAP_TM_Enhancements