Skip to Content

Hello Readers,

I was asked the question how to enhance the Dependent Object (DO) Transportation Charges.

In general, DOs like Address, TextCollection and Attachment Folder are not extensible. They are reuse DOs not owned by TM and they do not appear in the Enhancement Worbench as objects that you can create an enhancement object for (i.e. BOPF does not support extensions of these kind of DOs).

The DO Transpotation Charges /SCMTMS/TCC_TRNSP_CHRG in turn can be enhanced via the Enhancement Workbench like you may already know it form other TM BOs (e.g. /SCMTMS/TOR or /SCMTMS/TRQ, etc.). This Do is configired and defined to be extensible.

The only thing you have to keep in mind is the following.

  • A DO is reused in different BOs, eventually even multiple times in the same BO.
  • You can not enhance it directly via the Enhancement Object of the BO where the DO is included.
  • Instead you need to start the Enhancement Workbench and create a separate Enhancement Object for DO /SCMTMS/TCC_TRNSP_CHRG.
  • With this separate Enhancement Object you can then create all kinds of enhancements that you might know already from the TM BOs.

But also keep in mind:

  • Any enhancement on the DO /SCMTMS/TCC_TRNSP_CHRG will be visible and (if not caught correctly) executed by each BO that includes the DO.
  • So Field Extensions on this DO will be available in all BOs that reusethe DO, i.e. if the extension is required only in one BO the others nevertheless carry around these fields although not needed there.
  • For BOs that do not require the enhancement this can lead to unwanted executions of enhancement functionality and performance issues if not done correctly. Make sure that your enhancements only get executed where required.
  • This is especially an issue with Determinations and Validations. They must be implemented in a way that they get only executed where really required.

Best regards,

Holger

To report this post you need to login first.

10 Comments

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

  1. Roman Beketov

    Hi!

    Very useful blog! Thanks!

    Could you please tell me how can I do “Translation” functionality for Z’ fields? I think it should be like “TEXT_COLLECTION”

    ?

    (0) 
        1. Holger Polch Post author

          Hi Roman,

          well, this is done via so called OTR texts that you can create with transaction SOTR_EDIT.

          In earlier releses it was e.g. possible to directly enter a Label Text for the new field in the configuration editor. But as per NW 7.31 and higher releases this has changed.

          In the higher NW releases, the Label Text is first of all automatically taken over from the data element used for the definition of the extension field in the backend, i.e. it is pulled from DDIC.

          But you can create your very own specific Label Texts, assign them to your extension fields and even have the chance to get language specific variants of these Label Texts which can be handled with the translation tools available in the backend.

          Just like standard SAP TM development, you can create  OTR Texts via transaction SOTR_EDIT and assign these OTR Texts to extension fields in the FBI View related to the UIBB that you extend.

          In the coming up version of the enhancement guide this will be mentioned with an example too.

          Hope this helped to answer your question.

          Best regards,

          Holger

          (0) 
            1. Holger Polch Post author

              Hi Roman,

              yes, this should work for any kind of text in general, i.e. not only for Labels but for example for tool tips, etc. … every kind of text that shall appear on the UI and is relevant for translation.

              BR,

              Holger

              (0) 
            1. Holger Polch Post author

              Hi Roman,

              as mentioned in a previous post, I’m currently reworking chapter 5 “UI Enhancements”. Once this is finalized, I’m considering a “pre-release” with the content up to chapter 5. For the remainder of the document the release target is January 2014.

              In case of questions in advance, please feel free to post your questions here in the blog.

              BR,

              Holger

              (0) 

Leave a Reply