SAP S/4HANA 2020 FPS1: New features in SAP TM for location types 1040 (store) and 1140 (hub)
Dear users and friends of SAP TM,
Please find here some new features in SAP S/4HANA 2020 FPS1 in regards to locations. To be precise, it’s about locations representing stores (location type 1040) and hubs (location type 1140). I guess those are important especially for the retail industry, but might be for other industries as well.
Let’s go into details of the new features:
- Create locations of type 1140 (hub):
With SAP S/4HANA 2020 FPS1, you are now able to create locations of type 1140 which represent hubs.
In the following example, a plant representing a hub is created in transaction WB03:
Important is to maintain the node type in the supply chain network (field ‘Node Type SCN’) with ‘EW’, representing a Central Warehouse. This indicator, together with plant category ”B’ (for Distribution Center), is used to identify a location as a hub when the location is created.
When you now execute report /SCMTMS/CREATE_LOCATION, a location of type 1140 is created respectively:
Please see also note 2960779
- Replicate locations of type 1040 (store) and 1140 (hub) with DRF (Data Replication Framework):
In SAP S/4HANA 2020 FPS1, we also enhanced the replication capabilities of locations by enabling the replication of stores (location type 1040) and hubs (location type 1140) from one S/4HANA system into another S/4HANA system.
This is shown in the following example with the hub created before:
At first, we replicate the business partner of the hub. We then create the location of the business partner (with location type 1021) in the receiving system with report /SCMTMS/CREATE_LOCATION.
We now start the replication of the hub in transaction DRFOUT. We provide a respective replication model and outbound implementation ‘189_1’, meaning a replication with web service. The hub we want to replicate is mentioned as filter criteria:
We now check the replication in transaction SXMB_MONI (as we used PI in this example). If the replication has been successful, the key mapping is send back in the confirmation message:
And finally we check in transaction /SCMTMS/LOC3 if the hub has been created properly in the receiving system:
For stores (location type 1040) it works pretty much the same, so we don’t need to mention a separate example.
Please see also note 2960779
So, both mentioned points are surely some useful roundups that enable a more accurate transportation planning by considering stores and hubs.
For any questions or feedback, please feel free to comment!
Nice info thanks
Very relevant for Retail-TM scenarios. Thanks !!
Very nice. Tks for Share!
Thanks for sharing this info. Indeed, the location from the report is created as the location type HUB, but when creating a sales order and following FU creation it still follows the shipping point concept (shipping point not used previously - no shipping point location in the TM only HUB location). Is this HUB/Store concept merge somehow with SD/MM integration in embedded TM? If yes, where are some other setups for that?
Thanks for your comment! Sorry that it took a while to reply but I was on vacation.
Might be that I'm not on full steam yet...but I couldn't get your point, quite frankly. What you mean by the shipping point concept? Do you have an example scenario you could describe?
Thanks for your reply. Let me shortly present an example: once you create a sales order with one PRD from plant DC01 (with Plant Cat. B and Note type EW) with assigned shipping point SP01, what should be the standard source location? By now it would always be sth like SP_SP01 (location type 1003) so the question if the introduction of location 1140 should change this behavior?
Ok, now I got it, thanks!
Actually, there's no change in the behavior you describe. It would still be your shipping point SP_SP01.