Dear Experts,

I need help to hide the button accept in my portal. We need that only button show is Accept with Changes.

I follow the document:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c090ae93-2605-3210-ffbb-e00c790e810b?QuickLink=index&…

I create the component.js and put this code:

<%-- <%@page language="abap"%> --%>
jQuery.sap.declare("zcoll_portal.Component");
jQuery.sap.require("sap.tl_collaboration_portal.Component");
// new custom component
sap.tl_collaboration_portal.Component.extend("zcoll_portal.Component", {
  metadata : {
customizing : {
//customizing code to be added
  }
  },
  init : function() {
  this._oResourceModel = new sap.ui.model.resource.ResourceModel({bundleName:
  "sap.tl_collaboration_portal.language_bundle.i18nGeneral"});
  }
});
jQuery.sap.declare("zcoll_portal.Component");
jQuery.sap.require("sap.tl_collaboration_portal.Component");
// new custom component
  sap.tl_collaboration_portal.Component.extend("zcoll_portal.Component", {
   metadata : {
     customizing : {
       "sap.ui.viewModifications" : {
        "sap.tl_collaboration_portal.view.requestsForQuotationCasual" : {
        "btnAcceptRfq" : {
        "visible" : false
                          }
                                                                        }
                                    }
                    }
              }
                                                                         });

But the button show us yet.

Someone have more suggestion for me?

Thanks.

BR.

Renato Okamoto

Hello,

As we  know that Parcel FO does not:

1. appear in transportation cockpit (since stages are non-linear and star shaped)

2. Does not have the option to "Insert FUs based on FU ID" (this option is available only in normal truckload FO)

In some of the countries, our Business has to take certain manual decisions based on Gross Weight of Freight Units, HAZ and Non-HAZ materials etc. wherein they require to un-assign the FU from its Parcel FO number "ABC" and re-assign to another Parcel FO number "XYZ" (there are more than one Parcel Freight Orders in the system at any given point of time)

Since options 1 and 2 are not available in Parcel FO, we are not able to achieve this.

"Assign to existing FO or create new FO" option in DSO in FU is not the one that can help us because our manual decisions and system auto-assignment have mismatch.

Can any one suggest here.

Thanking you in anticipation.

Best Regards,

Vikas Chhabra

Hello All,

Trying to understand and implement auth for TM.

For controlling access for Freight Booking in TM

For example  Create Ocean Freight Booking,Display and edit access has been delivered in object /SCMTMS/FRE_BOOK.

Please correct

a.) If i need to controlled and to provide separate access for create/display/edit, i need make copy of /SCM/TMS/FRE_BOOK and make

changes to at Node details by making use of visibility.

b.) For control at Plant level, do i need to make enhancement using BOPF browser by making a copy of standard.

I understand that for webdynpro object or application access has to controlled by making copy from standards and making enhancements according to our requirement.

OR

As standard this kind of control is possible with normal PFCG roles and authorization object.

Regards

KSK

Dear Experts, I have created a custom validation routine for the TRQ.  In this validation I perform a read and validate the values coming from:

IT_ROOT. io_read->retrieve(      

   EXPORTING      iv_node =  /scmtms/if_trq_c=>sc_node-root                                                                    

      it_key  =  it_key      IMPORTING        et_data = lt_root      ).

This process works fine when entering values into my custom field.  However, this is a requirement to default the values on the screen.  To perform this action some custom code has been added to /SCMTMS/CL_UI_VIEWEXIT_TRQ-ROOT_ADAPT_DATA.  The values show on the screen as expected.  However, the validation routine does not pickup defaulted values.  There must be something done to push the UI defaulting to the BOPF model.  Can anyone provide some guidance on this?

Hi Everyone,

There is a Five Lecture Series for Introduction to SAP TM. It looks great for People who have started Working on SAP TM.

Keep Updating the Other Lectures once Available.

Lecture 1 from Mini Series – SAP Transportation Management

Novigos Introduction to SAP Transportation Management - Lecture 1 - YouTube

Lecture 2 from Mini Series – SAP Transportation Management

https://www.youtube.com/watch?v=HO-V_bI09i4&feature=youtu.be

Best regards,

Rohit

Hi Experts,

We have a single transport domain controller which is being used for all landscapes for transport purposes.

Now, we have decided to move/ create transport domain controller dedicated to each landscape.

What would be the best practice for this new configuration.

Thanks

DK

We are planning in TM 9.1 with schedule.

If we are planning with schedule it will not be updated with loading date and time. rather gets what is maintained what is maintained in the schedule.

Is it possible to maintain the loading date and time while we use a schedule.

regards,

Sayantan

This document describes how Text Schema customizing needs to be maintained to be able to propagate texts from TRQ to TOR on item level.

In this example we would like to copy text type NOTE from a FWO item to the assigned FU item.

As the text should appear on item level and not on the header, the text schema do not have to assigned to the FWO/FU type (in customizing) but to the Business Object /SCMTMS/TOR Node ITEM_TR. Therefore the following new Business Entity should be defined (IMG -> Cross-Application Components -> Proccesses and Tools for Enterprise Applications -> Reusable Objects and Functions for BOPF Environment -> General Settings -> Maintain Business Entities).

Business Entitiy: ZTOR_ITEM (e.g.)

Business Object name: /SCMTMS/TOR

Node name: ITEM_TR

Now let's see which settings should be maintained in Text Schema customizing (IMG -> Cross-Application Components -> Proccesses and Tools for Enterprise Applications -> Reusable Objects and Functions for BOPF Environment -> Dependent Object Text Collection -> Maintain Text Schema).

The following Access IDs are defined:

(We have defined two Access IDs because the propagation from OTR to FU and from DTR to FU works on a different way. We suggest to implement both of them to avoid later the errors.)

Access ID: ZA

Access Type: Associtaion Navigation

Text Type: NOTE

Source Business Entity: ZTOR_ITEM

Target Business Entity: /SCMTMS/TRQ

Access ID: ZB

Access Type: Association Navigation

Teyt Type: NOTE

Source Business Entity: ZTOR_ITEM

Target Business Entity: /SCMTMS/TRQ

The Details of the Access IDs:

Access ID: ZA

Sequence No.     Association Name

10                         BO_TRQ_ITEM_ALL

20                         PARENT_ITEM

30                         ITEMTEXTCOLLECTION

Access ID: ZB

Sequence No.     Association Name

10                         BO_TRQ_ITEM_ALL

20                         ITEMTEXTCOLLECTION

These Access IDs have to be assigned to the same Access Sequence (ZS). ZA is the first and ZB is the second.

Text Schema is defined and it contains text type NOTE with Access Sequence ZS.

The last steps is to assign the Text schema to the BO (Assign Text Schema to BO and Node):

Business Object Name: /SCMTMS/TOR

BO Node Name: ITEM_TR

Txt Schema: ZSG_FUITE

Greetings,

We are using Business Content extractor 0SCM_TM_TRAZONE_HIER to retrieve the transportation zones hierarchy from TM.

There are some discrepancies between the extractor results and what can be displayed in the transportation zones hierarchies’ transactions. Hence, we end up with inconsistencies in the hierarchy.

Below are the steps to reproduce the issue in our system

Launch transaction RSA3 Extractor checker

• In the data source field, enter 0SCM_TM_TRAZONE_HIER
• Execute the transaction
• For segment Node, we apply some filters to retrieve the hierarchy for node name GAMMA

We can see that GAMMA belongs to 2 path

• GAMMA > LAMDA > DELTA (NEW PATH )
• GAMMA > BETA > ALPHA (OLD PATH)

This is not allowed in our design and causes some errors in the hierarchy extraction to BI because this is a duplicate entry.

After investigation with the TM analyst, we find out that the path GAMMA > BETA > ALPHA is obsolete and was deleted and then it was replaced by GAMMA > LAMDA > DELTA.

Let’s check the setup in TM:

Launch transaction /SCTM/ZONE_LOCATIONS

• Choose Directly included locations
• For transportation zone LAMDA, we can see customer GAMMA
• For transportation zone BETA, we do not see GAMMA

Launch transaction /SCTM/ZONE

• Choose Directly included locations
• For transportation zone LAMDA, we can see customer GAMMA
• For transportation zone BETA, we do not see GAMMA

Why is the extractor retrieving the old and new paths? Is there anything missing to set the old path to obsolete so that the extractor no longer extract it?

The class used during extraction is /SCMTMS/CL_EXTR_TZONE_HIER_SRV. I believe there is an error in the methods being called to build the hierarchy structure, but before raising an OSS I would like to check with the gurus if there is any other place where we would need to delete our OLD PATH, or if we can run any consistency checks to get rid of the old path.

Thanks for your help, best regards

Good day!

I have a doubt. We did some enhancement (new fields ZZ*)  into 0SCM_TM_TOR the issue is: When some field ZZ* is changed into the table TORROT is not créated a new register into the delta queue some body can helpme please? I dont know why the new change is not updated in Delta queue.

Thanks

The SAP TM geo-map component can be used to display master data and business documents. Sometime the requirement exists in custom development projects to add custom objects to the map. This MKS describes how this can be done with minimal effort.

First of all an enhancement spot implementation class (for example ZCL_MAP_ENHANCE) is needed. This class must implement interface /SCMTMS/IF_EX_MAP_ENHANCE_VB21. Then the enhancement spot implementation can be setup under path IMG -> SAP Transportation Management -> Business Add-Ins (BAdIs) for Transportation Management -> Geographical Map -> Enhancement for Geographical Map -> BAdI: Enhancement for Geographical Map.

To add the custom object, an implementation in enhancement interface method ADJUST_NEW_OBJECTS can be done. This method is called whenever an object is added to the map. It is possible to adjust those spot and link like objects, but also to remove them or add totally new objects.

Example: You want to add an additional spot for each Freight Order representing the resource. The FO is added to the map and supplied to the enhancement method in table CT_LINK_OBJECTS. The FO stage key is the GUID. Adding the new spot needs structure if_vbi_service_provider=>spot_entry containing the following important fields:

GUID                   - Key (usually object key or stage key)

ID                        - Name

TYPE                   - Spot or Link

ROLES                - a table of roles indicating what kind of object it is -> determines for example the icon

DESCRIPTION    - a table of descriptions for tooltip, label, details

FLY_TO               - shall the map zoom to this object

SHOW_LABEL     - shall the label be displayed by default

POSITION           - Longitude and Latitude of spot

With the following code already a spot should be displayed:

METHOD /scmtms/if_map_enhance_vb21~adjust_new_objects.

     DATA: ls_spot        LIKE LINE OF ct_spot_objects,

               lv_role        TYPE vbi_object_role,

               ls_description TYPE vbi_s_object_descr_entry.

     ls_spot-guid = /sctm/cl_guid_convert=>get_guid_x16( ).

     ls_spot-id   = 'MY_TRUCK'.

     ls_spot-position-xpos = '2'.

     ls_spot-position-ypos = '3'.

     lv_role = if_vbi_geomap_const=>gc_object_role-truck.

     INSERT lv_role INTO TABLE ls_spot-roles.

*Add a description

     CLEAR ls_description.

     ls_description-category   = if_vbi_const=>gc_descr_category-tooltip.

     ls_description-field_name = 'Vehicle'.

     ls_description-value      = ls_spot-id.

     APPEND ls_description TO ls_spot-description.

     INSERT ls_spot INTO TABLE ct_spot_objects.

ENDMETHOD.

Map with custom truck spot (of course this can have a more realistic position)

Challenges:

• Depending on the map component the enhancement shall be active, it can be a challenge to keep the object consistently on the map or remove it at the right point in time. This might require some internal object handling in the custom class.
• Different icons: When not using the standard roles determining standard icons, it might be required to set the icon in /SCMTMS/IF_MAP_ENHANCE_VB21~ADJUST_SPOT_ICONS.
• Adding object to the map without others: method ADJUST_NEW_OBJECTS is only called when new objects are added. If you want to show objects without this pre-requisite, either a roundtrip with a new object must be triggered that will be removed immediately and replaced by the custom objects, or a modification is required. (As soon as this comes up I might enhance the enhancement spot...)

A lot more to tell about the options to enhance the map...

This question is real time scenario i need help on this, it would probably answerable by experienced person.

Hi Gurus,

How to delete the reported event in Execution tab of the Freight order?

For Ex:

After capturing POD, if i want to delete it, i cant find any option to delete it.

Thanks,

Michael.

Hi Experts,

I am correctly understand that in SAP TM 9.3 there is no possibility for automate train planning (one active locomotive (with defined number of max railcars can handle) and floating number of passive railcars) via VSR optimizer (Transportation Cockpit)?

Thanks in advance,

Peter

Hello All,

Can anyone help me how to Update/Modify the PPF document created under the attachment folder for given FO.

As per current process we are currently creating a new Document for every changes at FO level , doing this we are facing lot issues with performance as the Each FO would have atleast 10 documents created.

Can some one help me to update the document which is already generated.

Current logic for creation is below .

METHOD attach_file.

*

    CHECK i_keys IS NOT INITIAL.

*

    CHECK i_ppf_out IS NOT INITIAL.

    DATA: lo_srv_mgr TYPE REF TO /bobf/if_tra_service_manager.

*-----------------------------------------------------------------------

*       Local Internal Tables(lt_*)

*-----------------------------------------------------------------------

    DATA: lt_tor_root      TYPE /scmtms/t_tor_root_k,

          lt_tor_items     TYPE /scmtms/t_tor_item_tr_k,

          lt_tor_items_pkg TYPE /scmtms/t_tor_item_tr_k,

          lt_split_info    TYPE ztmst_fu_split_data,

          lo_txn_mgr       TYPE REF TO /bobf/if_tra_transaction_mgr,

          lv_changes       TYPE char1,

          lr_att_root_bo   TYPE REF TO /bobf/s_atf_root_k,

          lv_do_root_key   TYPE        /bobf/conf_key,

          lv_do_doc        TYPE        /bobf/conf_key,

          lt_doc           TYPE        /bobf/t_atf_document_k,

          lt_target_key    TYPE        /bobf/t_frw_key,

          lo_change TYPE REF TO /bobf/if_tra_change  ,

          lt_failed_key    TYPE        /bobf/t_frw_key,

          lv_do_action_key TYPE        /bobf/conf_key,

          lv_updatedoc_key TYPE        /bobf/conf_key,

          lr_action_param  TYPE REF TO /bobf/s_atf_a_create_file,

          lt_doc_manifest  TYPE        /bobf/t_atf_document_k,

          ls_doc_man_last  TYPE        /bobf/s_atf_document_k,

          ls_modification  TYPE        /bobf/s_frw_modification,

          lt_modification  TYPE        /bobf/t_frw_modification,

          lo_message       TYPE REF TO /bobf/if_frw_message,

          lt_key           TYPE /bobf/t_frw_key,

          lv_name_old      TYPE         string,

          lv_name_new      TYPE         string,

          lv_name_first    TYPE         string,

          lv_name_version  TYPE         string,

          lv_full_name     TYPE         string,

          lv_version       TYPE         i,

          lv_versions      TYPE         i.

    DATA: lv_rejected.

*-----------------------------------------------------------------------

*       Local Work Areas(ls_*)

*-----------------------------------------------------------------------

    DATA: ls_key                TYPE /bobf/s_frw_key.

*-----------------------------------------------------------------------

*       Local Variables(lv_*)

*-----------------------------------------------------------------------

*       Field Symbols(<*>

*-----------------------------------------------------------------------

    FIELD-SYMBOLS: <fs_tor_root>  TYPE /scmtms/s_tor_root_k.

    CONSTANTS: lc_underscore(2)       TYPE         c VALUE '_V'.

*-----------------------------------------------------------------------

* Get the required service manager instances

*-----------------------------------------------------------------------

    lo_srv_mgr = /bobf/cl_tra_serv_mgr_factory=>get_service_manager( /scmtms/if_tor_c=>sc_bo_key ).

    lo_txn_mgr      = /bobf/cl_tra_trans_mgr_factory=>get_transaction_manager( ).

*-----------------------------------------------------------------------

*-----------------------------------------------------------------------

    lt_key = i_keys.

    lo_srv_mgr->retrieve(

      EXPORTING

        iv_node_key             = /scmtms/if_tor_c=>sc_node-root

        it_key                  = lt_key

        iv_edit_mode            = 2

        iv_fill_data            = abap_true

      IMPORTING

        et_data                 = lt_tor_root    ).

    CLEAR: lv_changes.

    LOOP AT lt_tor_root ASSIGNING <fs_tor_root> .

*-----------------------------------------------------------------------

*-----------------------------------------------------------------------

      CLEAR: ls_key, lt_key.

      ls_key-key = <fs_tor_root>-key.

      INSERT ls_key INTO TABLE lt_key.

        /scmtms/cl_common_helper=>get_do_keys_4_rba( EXPORTING  iv_host_bo_key      = /scmtms/if_tor_c=>sc_bo_key

                                                                iv_host_do_node_key = /scmtms/if_tor_c=>sc_node-attachmentfolder

                                                                iv_do_node_key      = /bobf/if_attachment_folder_c=>sc_node-root

                                                                iv_do_assoc_key     = /bobf/if_attachment_folder_c=>sc_association-root-document

                                                      IMPORTING ev_node_key         = lv_do_root_key

                                                                ev_assoc_key        = lv_do_doc ).

        /scmtms/cl_common_helper=>get_do_keys_4_action( EXPORTING iv_host_bo_key      = /scmtms/if_tor_c=>sc_bo_key

                                                                  iv_host_do_node_key = /scmtms/if_tor_c=>sc_node-attachmentfolder

                                                                  iv_do_action_key    = /bobf/if_attachment_folder_c=>sc_action-root-create_file

                                                        IMPORTING ev_action_key       = lv_do_action_key ).

*----------------------------------------------------------------------

        CREATE DATA lr_att_root_bo.

        lr_att_root_bo->key           = /bobf/cl_frw_factory=>get_new_key( ).

        lr_att_root_bo->host_bo_key   = /scmtms/if_tor_c=>sc_bo_key.

        lr_att_root_bo->host_node_key = /scmtms/if_tor_c=>sc_node-attachmentfolder.

        lr_att_root_bo->host_key      = ls_key-key.

        lr_att_root_bo->att_schema    = 'DEFAULT'.

        ls_modification-key           = lr_att_root_bo->key.

        ls_modification-change_mode   = /bobf/if_frw_c=>sc_modify_create.

        ls_modification-node          = lv_do_root_key.

        ls_modification-data          = lr_att_root_bo.

        ls_modification-association   = /scmtms/if_tor_c=>sc_association-root-attachmentfolder.

        ls_modification-source_node   = /scmtms/if_tor_c=>sc_node-root.

        ls_modification-source_key    = ls_key-key.

        APPEND ls_modification TO lt_modification.

*

        lo_srv_mgr->modify(

          EXPORTING

            it_modification = lt_modification

          IMPORTING

            eo_message      = lo_message

        ).

        CLEAR lt_modification.

        lo_srv_mgr->retrieve_by_association(

           EXPORTING

             iv_node_key   = /scmtms/if_tor_c=>sc_node-root

             it_key        = lt_key

             iv_association = /scmtms/if_tor_c=>sc_association-root-attachmentfolder

           IMPORTING

             eo_message    = lo_message

             et_target_key = lt_target_key

             ).

        lo_srv_mgr->retrieve_by_association(

           EXPORTING

             iv_node_key    = /scmtms/if_tor_c=>sc_node-attachmentfolder

             it_key         = lt_target_key

             iv_fill_data   = abap_true

             iv_association = lv_do_doc

           IMPORTING

             eo_message     = lo_message

             et_data        = lt_doc

             ).

        CREATE DATA lr_action_param.

*----------------------------------------------------------------------

*       Logic for document versioning

*----------------------------------------------------------------------

        CLEAR : lv_name_old, lv_name_new, lv_name_first, lv_name_version, lv_full_name, lv_version.

        IF lt_doc IS NOT INITIAL.

          lt_doc_manifest = lt_doc.

          DELETE lt_doc_manifest WHERE attachment_type <> text-003.

          SORT lt_doc_manifest BY datetime_cr DESCENDING.

          READ TABLE lt_doc_manifest INTO ls_doc_man_last INDEX 1.

          lv_name_old = ls_doc_man_last-name.

          SPLIT lv_name_old AT lc_underscore INTO lv_name_first lv_name_version.

          lv_version = lv_name_version.

          lv_version = lv_version + 1.

        ELSE.

          lv_name_first = text-001.

          lv_version = 1.

        ENDIF.

        lv_name_new = lv_event_code && lc_underscore && lv_version .

        lv_full_name = lv_name_new && text-002.

        lr_action_param->name                      = lv_name_new.

        lr_action_param->description_language_code = ycl_tms_fo_attachment=>i_ppf_out-langu.

        lr_action_param->attachment_type           = text-003.

        lr_action_param->description_content       = lv_name_new.

        lr_action_param->alternative_name          = lv_full_name.

        lr_action_param->mime_code                 = text-004.

        lr_action_param->file_name                 = lv_full_name.

        IF i_ppf_out-pdf IS NOT INITIAL.

          lr_action_param->content = i_ppf_out-pdf.

        ENDIF.

        IF lv_versions <= 2.

          lr_action_param->visibility_type = 'X'.

        ENDIF.

        CLEAR lt_key.

        ls_key-key = lr_att_root_bo->key.

        APPEND ls_key TO lt_key.

*----------------------------------------------------------------------

*       Do Action Create a file

*----------------------------------------------------------------------

        lo_srv_mgr->do_action(

        EXPORTING

          iv_act_key           = lv_do_action_key

          it_key               = lt_key

          is_parameters        = lr_action_param

        IMPORTING

          eo_change            = lo_change

          eo_message           = lo_message

          et_failed_key        = lt_failed_key

        ).

    ENDLOOP.

  ENDMETHOD.

Regards

Kiran Kumar P.

Hi Exports,

This is Kishore,

Could anyone please let me know what is Transport of copies(ToC) and Relocation in Transport request.

what is difference between workbench Request and TOC.

What is the use of TOC and Relocation.

Thanks&Regards,

kishore.

Hi there,

I work for CP and perform Master Data maintenance in SAP TM. I think we just got version 9.2.

We are trying to plan an FWO/FU and get a too long list of transportation proposals for the business user to try and find the correct one.

We would like to limit the amount of proposals that are returned.

Is it possible to define an incompatibility so that the optimizer only considers certain transshipment locations.

Is there any way for me to achieve this with only master data access?

Unfortunately, I do not have access to configuration. I have access to conditions, planning settings, TCM and network master data.

Any ideas/help would be greatly appreciated.

Thank you,

Adrian

Hi All,

I am trying to fetch the Freight Units which are not planned based on locations , but I am getting only Freight units which are already to some FO/FB.

   IF s_fu_loc IS NOT INITIAL.
REFRESH lt_selpar.

ls_selpar-attribute_name = /scmtms/if_tor_c=>sc_query_attribute-stop-query_by_attributes-log_locid.
ls_selpar-option = s_fu_loc-option.
ls_selpar-sign = s_fu_loc-sign.
ls_selpar-low = s_fu_loc-low.
ls_selpar-high = s_fu_loc-high.
APPEND ls_selpar TO lt_selpar.
CLEAR : ls_selpar.

* Use method QUERY of the service manager to start the query
lo_srv_mgr->query( EXPORTING iv_query_key = /scmtms/if_tor_c=>sc_query-stop-query_by_attributes
  it_selection_parameters = lt_selpar
IMPORTING eo_message = lo_msg
  es_query_info = ls_query_inf
et_key = lt_key_root ).

lo_srv_mgr->retrieve(
EXPORTING
iv_node_key   = /scmtms/if_tor_c=>sc_node-stop
it_key        = lt_key_root
iv_edit_mode  = /bobf/if_conf_c=>sc_edit_read_only
iv_fill_data  = abap_true
IMPORTING
eo_message    = lo_msg
et_data       = lt_stop_fu ).


DELETE lt_stop_fu WHERE stop_seq_pos NE 'F'.
lt_key_stop[] = lt_stop_fu[].

REFRESH lt_key_root.

CALL METHOD lo_srv_mgr->retrieve_by_association
EXPORTING
iv_node_key    = /scmtms/if_tor_c=>sc_node-stop
it_key         = lt_key_stop
iv_association = /scmtms/if_tor_c=>sc_association-stop-assigned_capa_tor_root
iv_fill_data   = abap_true
iv_edit_mode   = /bobf/if_conf_c=>sc_edit_read_only
IMPORTING
et_data        = lt_root
et_target_key  = lt_key_root.

CALL METHOD lo_srv_mgr->retrieve_by_association
EXPORTING
iv_node_key    = /scmtms/if_tor_c=>sc_node-root
it_key         = lt_key_root
iv_association = /scmtms/if_tor_c=>sc_association-root-assigned_fus
iv_fill_data   = abap_true
IMPORTING
eo_message     = lo_msg
et_data        = lt_root_fu.
*      et_target_key  = lt_key_root.
REFRESH lt_key_root.
lt_key_root[] = lt_root_fu[].
IF lt_key_root IS NOT INITIAL.
APPEND LINES OF lt_key_root TO lt_key_root_fu.
ENDIF.

ENDIF.

please help me out how to fetch the FU's which are not in planned state

Thanks,

Arun

Dear Expert,

We are working on the LSP scenario and have question on how cost allocation happens in ECC when the revenue and cost data is moved from SAP TM. Understanding is that Revenue data is moved through Forwarding settlement document and Cost data is moved through Freight Settlement document. Is this understanding correct. If yes, then what is the basis and how cost allocation will happens in ECC.

Thanks in advance

Thanks & Regards

Punit

Hi,

I have created a 2 stage FWO type, which will have 2 legs of transportation.

Location A -> Location B & Location B -> Location C.

Location A & C can be anything, whereas Location B will always be the Warehouse.

How can we default Location B alone to a particular location.

SAP TM 9.0

Thanks in advance,

Deepan Mahendran.