Simplified Transportation Cockpit in SAP S/4HANA Public Cloud Transportation Management

 

1. Overview

1.1 Purpose and Benefits 

• Streamline daily planning by focusing the Transportation Cockpit on the data and actions you use most. 

• Reduce visual noise, speed up decision-making, and make the cockpit easier to adopt for lightweight logistics. 

1.2 Configuration Tasks

• Custom selection criteria (saved searches) 

• A custom cockpit view (visible columns and order) 

• Saved section views so your layout persists 
  

2. Custom Selection Criteria Configuration

• Open the Transportation Cockpit and set the filters you use most often.
• Collapse criteria that aren’t relevant to your daily planning to keep the filter panel clean. 
• Save the filter set as a custom search so you can reuse it.
  
  

 3. Custom Cockpit View Configuration

• Click the settings icon. If it’s not visible, open the menu behind the three dots and select the settings option. 

• Choose which columns to show and arrange their order to highlight the fields you need for planning. 

• Hide non-essential columns to reduce scrolling and distraction. 

• Save the view by clicking the arrow in each section so the layout is retained 

4. Good Practices 

• Keep filters minimal and name saved searches clearly (for example, by lane, carrier, or plant). 

• Align the column set with your automation approach (e.g., show statuses and fields you use to trigger or monitor automated planning and execution). 

• Review and update the view periodically as your process evolves. 

 

5. Further Information

• Transportation cockpit documentation in SAP Help Portal
  https://help.sap.com/docs/SAP_S4HANA_CLOUD/61e246f4b34c4e1790d8b7651c0b40a8/54deed6bbd8047e28dfa2193...  
  
  
• If you are interested in further automation capabilities in SAP S/4HANA Public Cloud Transportation Management check the complete blog post series:
  https://community.sap.com/t5/blogs/blogworkflowpage/blog-id/scm-blog-sap/article-id/8018 

Source: https://community.sap.com/t5/supply-chain-management-blog-posts-by-sap/simplified-transportation-cockpit-in-sap-s-4hana-public-cloud/ba-p/14306615

Event Driven TM in S/4HANA Public Cloud: Update Delivery Data When a Freight Order is created

 

1. Overview 

If you repeat simple updates in Transportation Management, such as setting general data on every Freight Order, it is time to automate them. When the decision is straightforward and the action is always the same, automation saves time and avoids errors. 

This series shows you how to build a small, event-driven extension in SAP S/4HANA Cloud, public edition. In our example, when a Freight Order is created, a local event handler updates static header data automatically. 

1.1 Why this pattern 

• Cuts manual effort for routine Freight Order updates 
• Uses released cloud APIs (usage type C1) and ABAP logic 
• Upgrade-safe and simple to maintain 

Example we will build 

• Trigger: Freight Order created 
• Action: Update general header data with predefined values 
• Result: Each Freight Order starts with consistent, ready-to-use data 

 1.2. Prerequisites  

• Developer Extensibility (3-system landscape) is enabled 
• The required view or API is released for ABAP Cloud (usage type C1) 
• ABAP Development Tools (ADT) are installed and connected to your system 
• You have a development package in the customer namespace. 
• You have access to create classes your development environment.

 1.3 Links 

• Stability Contract for System-Internal Use (C1): https://help.sap.com/docs/SAP_S4HANA_CLOUD/c0c54048d35849128be8e872df5bea6d/b6fe6846e9c7488e8c7e6d42...
• Local consumption of businees events 
  https://help.sap.com/docs/abap-cloud/abap-rap/business-event-consumption?version=s4hana_cloud&locale...
• CDS Views for Freight Order Management: https://help.sap.com/docs/SAP_S4HANA_CLOUD/c0c54048d35849128be8e872df5bea6d/125ff931b6274419b2164211...

 

 1.4 Alternatives 

There is more than one way to automate routine tasks in Transportation Management. The local event consumption approach is ideal for simple, immediate updates. For more complex needs, consider: 

• Job scheduling: periodic, time based updates or high volume corrections 
• BAdIs: governed logic at standard enhancement points during process steps 

Choose the option that best fits your timing, volume, and control requirements. 

2. Implementation Steps 

2.1 Find relevant event in ADT 

You need the behavior-enabled object for Freight Order, not just a read-only CDS view. The correct BDEF for this example is I_FreightOrderTP. 

Why I_FreightOrderTP? 

• TP stands for transactional processing. TP interface views are behavior-enabled. 
• Events, actions, validations, and determinations are defined in the RAP behavior definition (BDEF) behind the TP view. 

Plain interface views such as I_TransportationOrder_2 are read-only and do not expose events. 

Finding the BDEF in ADT 

• In ADT, use ABAP Repository Search to open the BDEF entity I_FreightOrderTP. 
  
• In the BDEF, look for ‘use event‘ declarations. 
• You subscribe to the alias. In our exampe ‘Created’ 
  

2.2 Create the Implementation Class 

2.2.1 Global Class 

• Create a new ABAP class in the customer namespace. 
• In the class definition, declare the relevant business event using the FOR EVENTS OF keyword so the class can receive the event. 
• Do not implement business logic in the global class.
  
  

2.2.2 Local Class Implementation 

• Go to the tab ‘Local Types’ tab. 
• Create a local handler that receives the event data and performs the update. 
• Use EML to update the Freight Order entity. Keep the update focused and transactional. 
  
•  

2.2.3 Example: Enrich the Freight Order 

In this example, you update: 

• Purchasing Organization 
• Purchasing Group 
• Carrier 

Use static data to start. This proves the flow endtoend quickly. Once validated, introduce simple business rules. For example: 

• Derive Carrier based on Shipping Point (e.g., map shipping points to preferred carriers). 
• Apply fallback logic if no match is found (e.g., set a default carrier and log a warning). 

2.2.4 What’s Next 

• Next, test the event flow endtoend: trigger the event, verify the updates via EML, and confirm the business outcome in the Freight Order. 

2.2.5 Tips and Pitfalls

• Business events run as separate transaction, asynchronously after the main transaction. It might be necessary to refresh the UI to reflect the changes. If you need to make changes withing the main LUW, consider using BADI instead.
• Consistency: Use correct business terms (“Freight Order,” “Purchasing Organization,” “Purchasing Group,” “Carrier”). 
• Robustness: Validate event payloads, and handle missing or inconsistent data 
• Performance: Keep event processing light; avoid longrunning operations in the handler. 
• Testability: Write unit tests for the local handler logic where possible. 

 

3. Code Snippet: Event Handler to Default Carrier and Purchasing Data 

3.1 What this does 

• Listens to the “Freight Order created” event and defaults carrier, purchasing organization and purchasing group.
• Uses local business event consumption and EML updates against released RAP business objects.

3.2 Before you start 

• This sample is provided asis. Use at your own risk and verify in a test tenant. 
• Adapt constants and namespaces to your customer namespace. 
• Only use C1 released objects. 
• Verify which attributes you can use to differentiate which freight orders should be processed . 

3.3 Global Class

Create a global class in the customer namespace without any method implementations.

CLASS <classname_customer_namespace> DEFINITION PUBLIC ABSTRACT FINAL FOR EVENTS OF I_FreightOrderTP.
   PUBLIC SECTION.
   PROTECTED SECTION.
   PRIVATE SECTION.
ENDCLASS.

CLASS <classname_customer_namespace> IMPLEMENTATION.
ENDCLASS.

 

3.4 Local Class

Open tab local types and create the class implementation. Keep in mind, this is only a template and the coding needs to be adjusted to match your organisations requirements.

CLASS lhe_<classname_customer_namespace> DEFINITION INHERITING FROM cl_abap_behavior_event_handler.

  PRIVATE SECTION.
    METHODS on_created FOR ENTITY EVENT newlycreatedfreightorder FOR freightorder~created.
ENDCLASS.


CLASS lhe_<classname_customer_namespace> IMPLEMENTATION.

  METHOD on_created.
    CONSTANTS lc_purchasing_organization TYPE /scmtms/vdm_pur_org_ext_id VALUE <purchase_org>.
    CONSTANTS lc_purchasing_group TYPE /scmtms/vdm_pur_grp_ext_id VALUE <purchase_group>.
    CONSTANTS lc_carrier_uuid TYPE /scmtms/vdm_carrier_party_key VALUE <carrier_uuid>.

    LOOP AT newlycreatedfreightorder ASSIGNING FIELD-SYMBOL(<singlefreightorder>).
      IF <singlefreightorder>-Carrier IS NOT INITIAL.
        CONTINUE.
      ENDIF.

    MODIFY ENTITY i_freightordertp
      UPDATE FROM VALUE #( ( %key-TransportationOrderUUID = <singlefreightorder>-   TransportationOrderUUID
        TranspPurgOrgExtID = lc_purchasing_organization
        TranspPurgGroupExtID = lc_purchasing_group
        CarrierUUID = lc_carrier_uuid
        %control-TranspPurgOrgExtID = cl_abap_behv=>flag_changed
        %control-TranspPurgGroupExtID = cl_abap_behv=>flag_changed
        %control-CarrierUUID = cl_abap_behv=>flag_changed ) )
      FAILED DATA(ls_create_failed)
      REPORTED DATA(ls_create_reported).
    ENDLOOP.
  ENDMETHOD.
ENDCLASS.

 

3.5 Risk Reduction Checklist for Productive Usage

• Validate before update: Ensure the Freight Order exists and is updatable before issuing EML.
• Handle errors: Catch and log EML failures with clear message categories; surface actionable context.
• Consider BRFR+ tables instead of hard-coding any values
• Keep it light. Consider job processing or BADI implementation for more complex logic.
  
  

4. Conclusion

• Automating routine Freight Order updates via a local event handler in S/4HANA Cloud ensures consistent, upgrade-safe data with minimal manual effort.
• If you are interested in further automation capabilities in SAP S/4HANA Public Cloud Transportation Management check the complete blog post series:
  https://community.sap.com/t5/blogs/blogworkflowpage/blog-id/scm-blog-sap/article-id/8018 

 

Thanks to my co-author @Slava_Aliakseyevets

Source: https://community.sap.com/t5/supply-chain-management-blog-posts-by-sap/event-driven-tm-in-s-4hana-public-cloud-update-delivery-data-when-a-freight/ba-p/14306637

Getting started with the SAP Logistics Management setup

  am sure that by now, as an avid Supply Chain professional,  the announcement of SAP's latest solution to enrich its Digital Supply Chain portfolio has not gone unnoticed. Of course, I am referring to SAP Logistics Management.

Although being a nascent product, I will let you be the judge, but I am sure you will find the SAP Help page provided to aid you in the setup and running of the solution to already be extremely complete and rich. That said, as with any product help, there is a limit to what and how much can go into it. This blog aims to complement, not replace the provided SAP help, with visual aids to hopefully help the new comers to the SAP world as well as provide tips to maybe the more seasoned professionals amongst you. 

This blog will cover some of the key SAP Logistics Management setup tasks - that you do not want to go wrong.

Where appropriate, I will for the sake of continuity reference the relevant SAP help page.

Setting up your Organisational Structure

As with any system, there must be structure in the house (an action or transaction will occur in a structuring company level or a logical combination of many). The logistical levels of your company must be mirrored in your ERP and in SAP Logistics Management (referred to as LGM hence forth). Unless you are embarking on a green field implementation, it is quite likely that you will already have defined some of those elements, such as 'Company Code', 'Sales Area', etc.. The point of this section, will not be to cover all SAP organisational levels, but only those that are critical to be able to execute your logistics processes across your ERP and LGM.

Setting up your Organisational Structure in ERP 

I say ERP, but at the time of writing this blog I mean SAP S/4HANA Cloud Private Edition (aka Cloud ERP Private, S/4HANA PCE..), (Please check this page for minimum release requirements). Note: This blog will not cover the creation of an entire Organisational Structure (company code, shipping point, sales area, etc...) which are all needed. This blog will only focus on the key organisational levels required to create a warehouse in LGM.

This step will essentially entail defining a third party  warehouse. To do so you will need to leverage /create 3 SAP organisational objects:

• A Plant
• A Storage Location
• A Warehouse (number)

Once you have created those organisational elements, you will then need to indicate how they relate to one another and also let your ERP know that the warehouse you have created is managed -externally- to your ERP (your inventory value and quantity will be managed and visible in ERP at the IM -Inventory Management- level, but managed and tracked in quantity down to the warehouse bin level in LGM).

The steps required to define a third party warehouse are detailed here in the LGM SAP Help.

Define a Plant

LGM can be deployed in a green or brown field implementation scenario. Thus it may be that you already have a plant defined in your system that you simply wish to extend to be used with LGM, or you need to create a new one to coincide maybe with the creation of a new warehousing site.

If you need to create one, then go to your ERP implementation guide (transaction SPRO), and then follow the path SAP Customizing Implementation Guide --> Enterprise Structure --> Definition --> Logistics - General --> Define Plant

Enter the Plant details, such as (1) the plant code and name and (2) address details) and save your entries when you are done.

Defining a Plant

I will not show these steps in detail, but also make sure to complete the assignments of your plant to company code (Customizing Implementation Guide --> Enterprise Structure --> Assignment --> Logistics - General --> Assign plant to company code) , the assignment of a shipping point to your plant (Customizing Implementation Guide --> Enterprise Structure --> Assignment --> Logistics Execution  --> Assign shipping point to plant) and the assignment of a purchasing organisation to your plant (Customizing Implementation Guide --> Enterprise Structure --> Assignment --> Materials Management  --> Assign purchasing organization to plant). 

Define a Storage Location

To create a storage location, then go to your ERP implementation guide (transaction SPRO), and then follow the path SAP Customizing Implementation Guide --> Enterprise Structure --> Definition --> Materials Management --> Maintain Storage Location . The storage location is hierarchically below the plant, so before being able to define a storage location, you first have to indicate the plant in which you want to create this storage location. We will use the plant code previously created.

We will then select the 'New Entries' button and add (1) our storage location code and description and then (2) the address of the storage location. Remember that this storage location, will effectively be a warehouse (as I am using a demo system I have given the description 'LGM WHouse L10' for my storage location and referenced a warehouse number L10 even though I have not yet created it, simply to know that it is mirrored in LGM !).

Define a Warehouse Number

The last organisational object we need to create is a Warehouse Number (that's all it is. A number and a description). To create a warehouse number, then go to your ERP implementation guide (transaction SPRO), and then follow the path SAP Customizing Implementation Guide --> Enterprise Structure --> Definition --> Logistics Execution --> Define Warehouse Number . 

We will then select the 'New Entries' button and add our warehouse number and description.

 Now that we have created all the organisational objects we need, we can now proceed to representing how they relate to another.

Assign Warehouse number to Plant and Storage Location

As said, a warehouse number, on its own is just that. So we need to indicate to ERP, what this warehouse number maps to physically - a combination of a plant and storage location. To do so go to your ERP implementation guide (transaction SPRO), and then follow the path SAP Customizing Implementation Guide --> Enterprise Structure --> Assignment --> Logistics Execution --> Assign Warehouse Number to plant and storage location. 

We will then select the 'New Entries' button, and indicate the three objects we have previously defined, namely (1) the plant code, (2) the storage location code and (3) the warehouse number. We have now mapped our plant/storage location to our warehouse.

 

Defining the warehouse as third party (external) warehouse

The last step on the ERP side, is to define the warehouse as being 'externally to the ERP' managed. This effectively to indicate to ERP, that when we transact in ERP in the plant/storage location that corresponds to a warehouse number, a message must be sent to the warehouse number to advise it to complete a logistical movement at the warehouse level.

To perform this step, go to your ERP (transaction SPRO), and then follow the path SAP Customizing Implementation Guide --> Logistics Execution --> Decentralized WMS Integration --> Central Processing --> Application --> Activate Decentralized WMS.

There, for your warehouse number, follow the instructions from the SAP help and make the settings as below.

 

Other -optional- ERP settings

I am in this section going to share with you other settings that you may need to make, depending on your scenarios. 

It may be, especially early on in your implementation project or as you test the solution that you want to update the stock in LGM, by performing an initial 561 (initial stock entry) or 501 (Receipt w/o PO) goods movement in your ERP to perform an IM (plant/storage location) movement, in order to be able to process a putaway (at warehouse level) in LGM. In order to facilitate this 'handshake' between ERP and LGM, ERP will automatically attempt to create an inbound delivery, upon saving the goods entry in ERP, but it needs some information to do this. Namely it requires a Business Partner representing the plant, acting as the 'Supplier' (moving stock from IM to warehouse level) and it requires certain delivery copy control settings to be in place.

Define Default Values for delivery

Once you have created a business partner to represent your plant as the 'Supplier', then go to your go to your ERP (transaction SPRO), and then follow the path SAP Customizing Implementation Guide --> Logistics Execution --> Decentralized WMS Integration --> Central Processing --> Application --> Inventory Management Interface and Delivery-Relevant Data --> Define Default values for deliveries.

 Then for (1) your warehouse number, indicate (2) the business partner that represents the plant and maintain the (3) logistics execution and (4) sales area information.

Copy Control for Deliveries

Upon processing a 501/561 stock movement you may get an error message saying  'Copy control is missing for: DZL DIG'. If you do, then you need to maintain additional copy control settings for deliveries. To do so go to your ERP (transaction SPRO), and then follow the path SAP Customizing Implementation Guide --> Logistics Execution --> Shipping --> Copying Control --> Specify Copy Control for deliveries . Transaction VTLA will also take you there directly.

Once there, select 'New Entries' and maintain the information as below:

Header level:

 Item Level:

 

Setting up your Organisational Structure in LGM

Now that we have defined our warehouse in ERP, we can pivot to setting it up in LGM. The relevant LGM help page for this is here. What you will notice is that there is no app in LGM that allows you to manually create any organisational object one by one, like you have in ERP or perform some kind of API sync to replicate the organisational structure from ERP. Instead, you have to perform an spreadsheet based import and upload.

NOTE: I would at this point be remiss, as indicated in the SAP help, to not remind you of an important warning before you proceed here. Whilst the 'Import Organizational Model' app performs certain checks during the import of a file, you cannot remove erroneously created organisational objects or relationships once they are created in LGM, nor is there a check against ERP to check that an imported object really exists in ERP (beware of typos! - so make sure the values you use are strictly identical to those from the source ERP system and have a second set of eyes gloss of over your upload file).

The procedure to follow in order to import your organizational structure into LGM is well detailed here. In a nutshell, you need to use the 'Import Organizational Model' app to (1) download a template spreadsheet with some sample data, amend it with your own data, and then (3) import it back into the same app, in order to (4) create your structure in LGM. There is also a dedicated help page that provides you with more details on the information you need to provide in the template for each object (you need to click on an object, then go down to the bottom of the page to see the details!).

You may also consider, as you move your project from Development --> to Test --> to Production,  to use the (2) export/import features in the 'Import Organizational Model' app to move a cleansed organisational structure down the line (rather than re-creating a new file every time).

Once you have imported your structure into LGM, a graphical representation of it is available for viewing in the 'Import Organizational Model' app.

 Handy tips in the 'Import Organizational Model' app

Using the 'Import Organizational Model' app should be fairly straight forward, but I will below highlight a couple of points that may be of use.

formOfAddress

In the 'ShippingPointAddresses' tab of the template, there is a tab named 'ShippingPointAddresses', and within it a (1) field named 'formOfAddress'. The sample file will be populated with the value '0002', and you may be wondering what this value corresponds to, and what other choices there are !

To find out the list of possible codes and their meaning, then you need to open the app (1) 'Display Code Lists' and see (3) possible values for the item (2) 'Forms of Address'.

As a preamble to this step note that your LGM system will initially be devoid of any code lists, nor do you have the ability to enter any manually in LGM. In order to have your LGM system populated with code lists, then you must perform the Code List Replication step which is detailed here in the SAP help. This step replicates these code lists directly from your SAP S/4HANA Cloud Private Edition system, by calling an API thus ensuring that your ERP is the single source of truth (and avoids double maintenance!).

As a sidenote, in order to replicate these code lists, you must choose the replication object 'SAP S/4HANA Customizing Data' during replication.

 

Handling localised texts

There is a reference to this in the SAP help here.

It may be that you are a multi-lingual organisation, and need to maintain texts for organisational objects in different languages. If that is the case, then you can maintain language specifics in the tab named 'LocalizedTexts' of the template, but you need to make sure that you reference the correct object using the correct naming convention. We will take the hypothetical example to localise a company code. 

My starting point is the template, where I have indicated the details below for a company code 1010, that is in ERP defined as being geographically located in Germany (Country_code = DE). The name, in English (my user language) of this company code is (1)  'Company Code 1010'. I have also attracted your attention to the language code (de = German) , only to say that this is the language of the company (it does not mean that 'Company Code 1010' is the German name of the company!). 

 Before I move on from this tab, I note the following information, as I will need it to localise it.

• (2) The object type (the entityName). The template allows me to localise all organisational objects, so I need to be able to indicate what object it is that I am referring to that I want to localise. Every sheet will in the top left have a unique code. In this case it is 'CompanyCodes'.
• (3) The object to localise. I could in my template have provided the data for multiple company codes, so I need to be specific about which company code it is that I want to localise. This is the code in the column named 'displayID'. In this case I refer to company code 1010.
• (4) The term to localise. We have to be specific and be able to tell which of the fields it is that I want to localise. In this case the term I want to localise is the information in the column named 'name'.

So now that I have the information I need, I can move to the sheet named 'LocalizedTexts' and see how we put this together! I have added details for other object types (entityName), but the first highlighted line is the one of interest for our company code.

 In this sheet, we carefully add the values we recorded in the 'CompanyCodes' sheet and add the missing pieces, namely:

• (4) The locale - the 2 digit language code of the localised language (the language for which we are providing a translation)
• (6) The value - the localised text. The translated text.

Once I have imported the template in to LGM and to make sure that my data is correct, we can do a check using the 'Import Organizational Model' app , by connecting in the appropriate language (go into the Fiori Launch Pad 'Me' menu, then choose 'Settings' and 'Language and region'.

Manage Warehouse Layout app

If you are like me, once the setup was done, I was eager to start setting a default warehouse in my user preferences, only to have a moment of panic when I saw, that at this point none could be selected! 

 So to avoid checking and double checking what could have gone wrong, first go to the 'Manage Warehouse Layout' app and make sure you have maintained the 'Manage Warehouse Attributes' of your warehouse! Once this is done, you should be able to see your warehouse appear in the various drop down lists in LGM. The reference to the SAP help for this section is here.

 

Importing Dimensions and Units of Measure

The LGM SAP help for this section can be found here and is quite comprehensive.

At the end of this step, you will have imported into LGM Dimensions and Units of Measure information from your ERP. In order to do this you will need to download some templates from LGM, extract some data via SE16 from your ERP, populate said templates and upload them into LGM. The help link above provides you all the information you need in order to perform this step (which applications to use, which tables to extract data from..) I will in this section merely provide you with some tips to hopefully help you speed up your workflow.

Before you begin, make sure to make note of the caution to not select the 'Respect Conversion Exit' option when you use SE16 in ERP !

Also, to avoid extracting incomplete datasets from ERP, make sure to (1) check how (2) many entries your tables contain and adjust the (3) Maximum number of hits accordingly.

 

Export/Import Dimensions data 

This step entails extracting data from tables T006D and T006T (for the localised texts) in your ERP.

To facilitate and minimise the amount of data massaging you will need to do, I would suggest you adjust the output columns to line up with those available and required by the template. For table T006D, I narrowed down my list of fields to the below - showing how they map to the template (as the templates may change over time, make sure to check in your environment before proceeding - this is your responsibility). I then extracted the SE16 table data set to Excel and copy/pasted the content in the template - making spot checks to make sure everything lined up and was accurate!

Note that I did not maintain any texts here.

 As my LGM system is intended to be used for English and German speakers, I need to extract Dimensions texts in both these languages.

As per the help, I query table T006T for this. Note: As languages tables can be quite voluminous depending on the number of languages maintained in your ERP, make sure to restrict the search to the languages of interest.

 This table will be a little tricky to handle as the columns from the SE16 Extract do not line up exactly like the template, and the language code from the SE16 extract is one character long, but the template requires 2 characters. Things to note are :

• That some (1) texts are fixed and required by the template (make sure every line has this)
• You should have a dimension repeated as many times as you have selected languages
• Use the Search and replace functions of excel to mass search and replace language 'E' for 'en' and 'D' for 'de' in the locale column.

Again make spot checks to make sure the data you will upload is accurate and complete (as the templates may change over time, make sure to check in your environment before proceeding - this is your responsibility)

Export/Import Units of Measure data 

This step entails extracting data from tables T006 and T006A (for the localised texts).

As before I will show you the column layout I selected and how I arranged it so that it mapped with the template file, allowing me to do a copy/paste operation. Again make spot checks to make sure the data you will upload is accurate and complete (as the templates may change over time, make sure to check in your environment before proceeding - this is your responsibility).

The Units of Measure file with the localised texts is probably the trickiest one to handle, so make sure to check your data set before uploading it to LGM. I say tricky because the SE16 extract will be a flat linear data extract that requires to be transposed for the upload template. I have tried to explain this with the diagram below. In other words you will for each 'keyValue' have to maintain the 'commercialCode', 'shortText' and 'longText' on different lines. At the risk of repeating myself,  make spot checks to make sure the data you will upload is accurate and complete (as the templates may change over time, make sure to check in your environment before proceeding - this is your responsibility).

 That's it for this time folks.

Stay tuned for more content on LGM, and don't hesitate to drop requests  for future blogs in the comments whether it pertains to setup or processes!

Source: https://community.sap.com/t5/supply-chain-management-blog-posts-by-sap/getting-started-with-the-sap-logistics-management-setup/ba-p/14328861