Synchronous Goods Receipt for Kanban: Kanban for in-house production strategies ‘working with production orders’ in S/4 HANA 2020 Embedded EWM

 

Synchronous Goods Receipt for Kanban:-

With this feature,  synchronous goods receipt with the Kanban replenishment strategy In-House can be posted with Production using the control type ”Working with Production Orders for goods receipt from discrete manufacturing directly to the bin of the production supply area (PSA).

Diagram from SAP document to understand synchronous goods movement.

 

Synchronous goods movements are also supported for the following Kanban strategies:

• Summarized JIT call (Kanban) with goods receipt from vendor directly to PSA bin.

• Kanban replenishment strategy In-House Production using the control type Processing with Planned Orders and Cost Collector for goods receipt from repetitive manufacturing directly to the PSA bin

For this blog, Kanban Inhouse ‘0006’ Replenishment strategy has been taken.

 

Step 1:Kanban to empty →creation of production order

System will create a Production order emptying Kanban Card,

Configure all PP production order process for Auto Order release, synchronous goods posting from production scheduling profile and control cycle. Use SAP standard order type for Kanban PPK1 with Forward scheduling.

 

Step 2: Confirmation and GR of prod. order →Kanban to full

On successful Kanban confirmation, Card signal changes from Empty to Full.

System created a material document associated with Production order.

Production Order Completed.

 

Stock Updated.

Warehouse Task created & Confirmed automatically.

 

Customization Involved.

Effects on Existing Data

The system determines the goods receipt bin from the Kanban control cycle.

Effects on Customizing

 Activate synchronous goods receipt in the production scheduling profile assigned to the Kanban material:

• In Customizing for Production under Shop Floor Control  Master Data  Define Production Scheduling Profile for Discrete Manufacturing

• Set up several options for control of ‘Automatic Warehouse Task Creation” at storage type level or WPT level. Also determination of WPT with synchronous posting without document type and Item type

 

Thanks for reading through, I would write more stuff on EWM Manufacturing integration on S/4 HANA 2020 Embedded EWM.

Reference:https://help.sap.com/doc/474a13c5e9964c849c3a14d6c04339b5/100/en-US/363e55b4cd0a400b86f994b282cd4f7f.html

Source: https://blogs.sap.com/2021/04/23/synchronous-goods-receipt-for-kanban-kanban-for-in-house-production-strategies-working-with-production-orders-in-s-4-hana-2020-embedded-ewm/

Direct STO Delivery Creation from EWM- Lesser Known Facts.

 SAP EWM has the capability to create ''Direct STO Delivery'' from EWM and corresponding Stock Transport Orders and Replenishment delivery is automatically generated in S/4 system in 1 step. This business process works both for Intra and Cross Company STO.

The process for stock transfer of a direct outbound delivery is also supported for stock transfers between storage locations, if the goods recipient of the direct outbound delivery is assigned to a storage location as opposed to a plant. In this case, determining the required purchase order data is done from Customizing for the storage locations involved. (STO between Storage location)

1) Directly Ship HU Pallet stock to Sister Plant w/o Picking.

From Maintain Outbound delivery App, Palletized stock can directly shipped to sister plant in 1 step.

On posting GI at HU level, corresponding S4 Replenishment delivery is created. Picking not required.

S/4 Replenishment Delivery with HU, STO PO.

2) Receiving storage location not determined for STO, its empty.

Many customers face this issue during Direct STO delivery creation from EWM, the receiving storage location is blank. No traditional ERP master data settings and config will work here. Customers has to implement SAP note 2911725 - Receiving storage location not determined for STO. This note needs to be implemented prior to S/4 HANA 2020.

In S/4 HANA 2020, the missing code of receiving storage location is already implemented.

3) Direct outbound delivery orders allow shipping of handling units even with blocked stock

Even HU( Palletized Stock) is in block stock type, Direct STO delivery creations allows to ship from blocked state..

This is SAP standard behavior and can be suppressed using Badi /SCWM/EX_DLV_VAL_DIRODO->VALIDATE_ITEM if business wants to forbid HU stock posting from blocked stock type. Reference: SAP KBA 2882517 - Direct outbound delivery orders accept handling units which have blocked stock

There are others aspects as well like calling ATP check in EWM for the required Item type and generation of packaging material in STP PO.

Disadvantages.

1) No open Stock Transfer Requisition is consumed in planning side, customer has to implement Badi for open STRs consumption.

Thanks for reading. Hope you liked the blog.

Source: https://www.linkedin.com/pulse/direct-sto-delivery-creation-from-ewm-lesser-known-facts-mishra/

How to sizing SAP S/4HANA Conversion

 This Blog was made to help customers prepare the SAP S/4HANA landscape conversion considering the sizing relevant KPI’s for the key performance indicators.

There are many perspectives that we need to consider when doing this planning. The sizing procedure helps customers to determine the correct resources required by an application within customer’s business context.

From the customer perspective, sizing is the translation of business requirements into hardware requirements, but from the development point of view, sizing refers to the creation of a sizing model for the product functionality with a reasonable number of input parameters and assumptions.

Considering this behavior can be changed during project, we cannot forget to re-visit this planning if any change is made on landscape requirements even from customer or development point of view, this can change the actual requirements and impact on overall solution performance.

Also, depending on the scope, this may also include a detailed analysis of the systems to be migrated and/or verification of the sizing assumptions made on-premise or cloud.

What you must know ?

Your business decisions will lead you to the sizing, but it’s not easy to translate it into the sizing forms, and even be sure everything was covered, that’s why you have to understand every business requirement, peak times, user behavior, number of transactions executed by them and most important of all, re-visit this requirements at every decision project step.

All your interpretations and decisions related to the business requirements must be made accordingly.

When you start sizing a conversion to SAP S/4HANA, you must make sure that all relevant actions related to the system housekeeping like, regular jobs, data management and archiving, deletion of unnecessary clients, deletion of unnecessary data (basis tables and application logs), custom code decommissioning, including not in use Z tables, and every item that can help you reduce your actual database size was completed or evaluated in advance.

The blog SAP S/4HANA System Conversion Steps & Details – How to be prepared, contains topics that can help you doing this evaluation.

What are the risks when sizing a project?

Sizing is not the way customer configure the system, actual system configuration is a task performed by the hardware vendor who must ensure the system landscape meets the hardware requirements determined by sizing.

The best sizing is related to the ability to have not only a scalable hardware, but also a scalable application software.

The best evaluation will be confirmed with a good test of system transaction volume, so a stress test must be planned to confirm that all decisions were made in the right way, but if not, the way infrastructure was organized must allows to make it scalable, at this point evaluate the Hyperscalers options:

• Check information provided on blog SAP S/4HANA Deployment on Hyperscalers
• Check the openSAP Course – SAP on Hyperscalers – Strategy, Architecture and Deployment

Those are the main risks you have to mitigate when evaluating data to run the sizing:

Incomplete input data

• Challenge to obtain sufficient usage information as sizing input
• Often caused by communication issues
• Insufficient sizing input is compensated by assumptions, which should be documented

Assumptions are not verified

• While is perfect ok to work with assumption you must ensure that a verification process is included in the project plan

Custom coding @ Special data constellations

• Are very hard to predict, make sure there is a verification process
• Make sizing measurements

Running Sizing Report

This report runs on SAP_BASIS 620 and higher, it is suitable for sizing all business suite products (ERP, CRM, SRM, SCM, etc…), but it’s nor suitable for BW, in this case, please refer to SAP Note 2296290 – New Sizing Report for SAP BW/4HANA

• The report /SDF/HDB_SIZING is described in SAP Note 1872170  – ABAP on HANA sizing report (S/4HANA, Suite on HANA…)

• Used for source ERP 6.0 EhPx, SoH, or S/4HANA Simple Finance 1503
• With ST-PI 2008_1_[700-710] SP 09 or ST-PI 740 SP00 and higher, you install report /SDF/HDB_SIZING’s latest version by implementing Note using SAP Note 2303847

This report will consider the SAP S/4HANA data model changes, also estimates the maximum memory consumption of the database, considers distribution of tables to row and column store, considers differences for secondary indexes, compression of legacy database and data aging for technical objects.

The sizing report can also be evaluated by running the Readiness Check:

On the SAP S/4HANA Sizing Simulation tab, the initial target SAP S/4HANA size is provided. It is based on the ABAP on SAP HANA sizing report for SAP Business Suite powered by SAP HANA and SAP S/4HANA, which calculates the initial memory requirements for the SAP HANA database based on current data volumes. These requirements were derived from the size of the tables and the compression rate in the source system. With the identified initial target SAP S/4HANA size, you can perform a target system sizing simulation by manually adding additional factors (future database growth, data volume reduction in your SAP ERP system, as well as additional growth arising from new functionalities, mergers, and acquisitions).

On the SAP S/4HANA Sizing tab, your estimated initial target system size is displayed in more detail, providing more information about the estimated memory and disk size requirements by category. In addition, you can see the top 20 database tables of your source system.

On the Data Volume Management tab, the size of your archiving potential in GB and percentage measurements by document type are provided, based on the top database tables in the past 12 and 24 months. In the bar chart view, the chart on the left shows how many gigabytes can be archived for each document type in relation to its total size in your source system. The chart on the right shows the corresponding archiving potential as a percentage for each document type. The bar charts show up to ten document types. To see the analyzed objects, switch to the table view.

How to evaluate the sizing report results ?

The sizing report includes the sizing projections, based on the actual table sizes in the legacy system as well as an estimation of how much the memory footprint can be reduced using functionalities that SAP HANA will enable

• Column store and row store estimations have good enough accuracy (10-20%). Still, do not forget it is an estimation.
• Work Space (temporary memory) estimation uses a simple formula (data size in memory) * 2. Based on experiences, if the work space is bigger than 3TB, it might be oversized.
• Always check the top tables. Very often, you will find basis tables with deletion / archiving potential such as iDoc, workflow, application log tables, etc.
• See SAP Note 706478 – “Preventing Basis tables from increasing considerably” for more details.
• The total estimated memory requirement given by the report should not be considered as the final memory sizing result. Take into account that:
  • Not all the server physical memory will be available to SAP HANA (OS and other processes are run too).
  • There should be enough space left for future data growth or functional extension

The sizing report takes a snapshot, any growth between that date and the go-live date should be considered.

Activities recommended on transition preparation

There are some activities and decisions that might drive you doing the sizing, some transition preparation activities will help. 

Hana Partitioning: Check the sizing report outcome to evaluate the tables with more than 2,000,000,000 records.

According to their tables classification, check the following SAP Notes:

• SAP Note 2289491 – Best Practices for Partitioning of Finance Tables
• SAP Note 2259038 – S/4HANA: Partitioning of table MATDOC

Archive before sizing: Before performing the S/4HANA sizing and executing the conversion, it is important analyse all data that can be archived, or which does not have to be in the business system anymore

• Archived data is still available, typically through additional tooling
• SAP strongly recommends that you archive as much data as possible from the source database before you convert to SAP S/4HANA. This will reduce your conversion and downtime
• There needs to be a housekeeping strategy to deal with data included in technical tables, which has become outdated and unnecessary
• In order to deal with those tables, you can leverage the sizing report attached to SAP Note 1872170 to identify the top technical tables and afterwards SAP Note 2388483 for instructions on how to delete data.

Define UX strategy: Do not forget the end user interface strategy to define the kind of access users will have.

It is necessary to add the resource for Fiori Frontend Server (FES) in addition in case FES is embedded in S/4HANA Backend Server. It can be estimated with Quick Sizer

Tip: Considering total user number is 1000 and half of them (500) login the system in a peak hour (9:00~10:00), you have to add the number of users at peak time, so, add the Input “500” in “No. of concurrent users”. Also adjust the start and end peak time for an accurate evaluation.

Embedded Analytics strategy: When using this feature, It is necessary to add the resource for embedded analytics in addition, which can be estimated with Quick Sizer too.

Tip: At this case the total user number is 1000 and half of them (500) login the system in a peak hour (9:00~10:00), user run and navigate report 5 times in average in the peak hour and they run 50% light query and 50% medium query. Here the input “500” in “No. of concurrent users”.

The figures to input heavily depends on the analytics scenario, so it is recommended to ask analytics experts to understand each parameter value and set the appropriate values based on the analytic scenario the customer assume.

e.g. Fiori Launchpad for average user has 10 tiles including number and login user in peak hour is 500, at least 5000 (10*500) queries are executed in the peak hour. (if not using cache).

Queries are expected to be tuned enough. The longer the runtime is, more H/W resource is consumed.

Advanced Sizing Service from SAP: Advanced Sizing sharpens the initial sizing performed in the planning phase. Depending on the scope, this may also include a detailed analysis of the systems to be migrated and / or the verification of the sizing assumptions made.

With this service customer will be supported in filling out the sizing questionnaire, some additional questions from the customer can be answered, ask SAP for guidance.

Action to closure

This is not an easy work to run an accurate Sizing project, this can only be done with the participation of all involved parts, from technical to functional team, you can start work running this activities

• Use Readiness Check to help with the initial evaluation
• If necessary, run Advanced Sizing service from SAP
• Start a QuickSizer project for SAP S/4HANA
• Ask technical and functional team to help fill the QuickSizer questionnaire
• Wrap your hardware partner on planning
• Re-visit sizing when a project decision can impact results

Check the document Principles of sizing SAP S/4HANA with the Quicksizer Tool

Sizing Tools

• Official SAP Sizing page: www.sap.com/sizing

Reference Material

• Help Sizing SAP HANA
• Quick Sizer Tool Recommendation
• Quick Sizer for Beginners
• SAP Note 1872170 – Sizing Report for SAP S/4HANA
• SAP Note 1514966 – SAP HANA: Sizing SAP In-Memory Database

Reference Blogs

• SAP S/4HANA 2020 System Conversion Steps & Details – How to be prepared
• SAP S/4HANA Deployment on Hyperscalers

If you enjoyed, click on like button !

Thank you,

Brought to you by the S/4HANA RIG

Source: https://blogs.sap.com/2021/03/31/how-to-sizing-sap-s-4hana-conversion/

How-to guide for the activation of SAP Best Practices for SAP TM in SAP S/4HANA 2020

 

Objective

To enable the use of Transportation Management functionality quite a bit of configuration is required. This effort may seem high, e.g. if you want to have a system to get a first idea of how SAP S/4HANA^® Supply Chain for transportation management works, and it requires a least a certain degree of experience with the solution. This blog post should help to considerably reduce the effort for the setup of a viable transportation management process with SAP S/4HANA 2020 in an on-premise deployment. Some of the information also can be helpful for lower releases, starting from SAP S/4HANA 1809 and is expected to be valid for future releases as well.

The reduction in effort is achieved by providing additional information, hints and screenshots for the activation of SAP Best Practices for S/4HANA Supply Chain for Transportation Management 1909. More precise, for the Outbound Transportation scenario. Additionally, with this post I will demonstrate that SAP Best Practices for TM in SAP S/4HANA 1909 can be activated in a SAP S/4HANA 2020 system without any issue. All information in this blog post was collected during the activation of said SAP Best Practice content in sandbox system used by the SAP S/4HANA Regional Implementation Group (SAP S/4HANA RIG).

 

SAP Best Practices for S/4HANA Supply Chain for Transportation Management

SAP provides Best Practices for Transportation Management in SAP S/4HANA to facilitate the setup of transportation management capabilities. At the release of this article the most current version of these SAP Best Practices is available with SAP Note 2970208. This SAP Note contains references to four further SAP Notes, each of which contains the content required to set up the system for a particular transportation scenario. These scenarios build upon each other and this blog post will be about the first scenario – outbound transportation – described by SAP Note 2969153. The SAP Note already contains a detailed step-by-step guide and this article aims at providing additional information, hints and screenshots to even further decrease the effort of setting up transportation management capabilities in SAP S/4HANA.

The SAP Best Practices for S/4HANA Supply Chain for Transportation Management 1909 can be activated either manually, by following the steps provided in the configuration guides attached to SAP Note 2969153 or automatically via Business Configuration Sets (BC-Sets). The BC-Sets are also available as attachment to SAP Note 2969153. In this post automatic activation via BC-Sets is described.

 

Initial situation and prerequisites

The system which is used for this post is on SAP S/4HANA 2020 FPS0. I do not expect any differences for an FPS1 system. Please comment below in case you experience deviating behavior due to 2020 FPS1, so everyone can benefit.

In the test system some SAP Best Practices for SAP S/4HANA (on premise) were activated when the system was on the 1909 release. Also see this blog post on how SAP S/4HANA Supply Chain for extended warehouse management functionality was activated. Then the system was upgraded to the 2020 release before starting the activation of the SAP Best Practices for TM.

The content activated before should not have an impact on the TM setup described here except for scope item BD9_US – Sell from Stock. This scope item must be activate before, as mentioned in the configuration guides attached to SAP Note 2969153. The SAP Note also mentions two prerequisite SAP Notes (2632824, 2789609), but none of them is relevant for SAP S/4HANA 2020. I recommend to carefully read through the whole SAP Note first, e.g. to know in which order to activate the BC sets.

 

Upload of BC sets

The following hints can help you during the upload of the BC-Sets.

• Before starting the upload of the BC-Sets you should have a package and a workbench request available to take the objects created from the BC-Sets. I added everything to the same package and transport request.
• For the upload it is helpful to store the downloaded files in a folder on the desktop because one must navigate there for each of the BC sets.
• Use transaction SCPR3 for the upload

Transaction SCPR3 – Upload

• After uploading all files use the button “Save list as favorites” to define all BC-Sets in the list as a favorite.

Save list as favorites

• SAP Note 2969153 mentions BC-Set /SCMTMS/UI_POWL which needs to be uploaded, but it is not part of the content provided in the Note. See the screenshots below for how to find it.

Find /SCMTMS/UI_POWL (1)

Find /SCMTMS/UI_POWL (2)

• Do not use the “Save list as favorites” button to mark /SCMTMS/UI_POWL as a favorite. This will overwrite your existing favorites. You can use the “Define Favorites button”. Selection criteria “User BC sets” will give you the objects uploaded by you.
• In case you wonder where BC-Set Y_TMS4HANA_CUSTOMIZING is coming from, this is uploaded as part of Y_TMS4HANA_GENERAL.

 

Activation of BC-Sets

In the following some screenshots should help you to go through the steps for the activation of the BC-Sets uploaded before and some further information is provided.

• A customizing transport is required for this step. Again, since I do not plan to transport the customizing objects to a different system, I put everything into the same transport request.
• The order of activation of the BC sets is specified in SAP Note 2969153
  • /SCMTMS/UI_POWL
  • Y_TMS4HANA_SCENARIO_DEL_CUST_1909
  • Y_TMS4HANA_GENERAL_1909
  • Y_TMS4HANA_BASICSHIPPING_OT_1909
  • Y_TMS4HANA_CHARGES_DEL_CUST_1909
  • Y_TMS4HANA_CHARGES_1909
• Use transactions SCPR20 to activate the BC-Sets
  • [Optional] Before activation you can use the consistency check. On tab “General Information” you will find the releases for which a particular BC-Set is valid

Consistency check

• • Use the activate button to start activation of a BC-Set.

Activate BC-Set

• The popup mentioned in SAP Note 2969153 is displayed after the selection of the customizing transport. There you need to choose “Expert Mode” and how to handle existing data. I selected “Overwrite All Data” for all BC-Sets.

Activation options

• During the activation of BC-Sets Y_TMS4HANA_BASICSHIPPING_OT_1909 and Y_TMS4HANA_CHARGES_1909, you must define some constants. I recommend selecting the values predefined from the BC set. This helps when you want to compare the system setup to the configuration guide and during executing the test script

Constants (1)

Constants (2)

• Activation of the BC sets in my test system led to the results below. Although there were some warnings and errors the activation was successful as my tests showed.
  • /SCMTMS/UI_POWL à               Successfully completed
  • Y_TMS4HANA_SCENARIO_DEL_CUST_1909 à           Finished with warnings
  • Y_TMS4HANA_GENERAL_1909 à              Finished with warnings
  • Y_TMS4HANA_BASICSHIPPING_OT_1909 à          Successfully completed
  • Y_TMS4HANA_CHARGES_DEL_CUST à Finished with warnings
  • Y_TMS4HANA_CHARGES_1909 à Activation ended with errors
    • Object OMWW could not be activated

 

 

Manual configuration steps

According to SAP Note 2969153 after BC-Set activation you should check the configuration guides for required manual configuration. Below I list the manual steps which I had to do to complete the test script. Maybe this can help you to save some time, but it’s possible in your case some different steps will be required. And of course, going through the configuration guide will help you to gain insights into the required configuration.

• Run Report /SCMTMS/TRIGGER_SETUP_BGRFC to create the RFC destination and inbound destination TM_BGRFC_INBOUND.
  • Check SAP Note 2641251 – bgRFC concept in TM 9.5 and S/4HANA for details
  • This is required to allow settlement posting
  • Selection field Logon/server group can be left empty
  • If executed in a system where these destinations already exist, the report will issue an information which says so. Therefore, the report can be used to check if the destinations do exist.
• Check the following steps from the configuration guide for Charge Management. These settings are not included in the BC sets.
  • 30 – Define number ranges for service master record
    • Starting from step 4 – Assign Element to Group
  • 33 – Defining Activity types
• In addition, I had to manually define the number ranges for settlement documents. This is step 3.49 in the configuration guide for charge management. The number ranges are part of the BC set but in my case an overlap with an existing number range prevented the automatic creation. Without these number ranges the creation of Cost Distribution Documents after posting the TM Freight Settlement Document will fail.
  • In my case I had to change the “To Number” of the number range from 9999999999 to 99999999 to avoid the overlap.

Define number range for settlement documents

 

Master data creation

For the creation of business partners and transportation network data (i.e. carriers, customers, locations, transportation zones and transportation lanes) I used the scenario builder tool. Please be aware the scenario builder can only be used if you have licensed Advanced Transportation Management. If not, you have to create the master data manually. Using the scenario builder helped me to reduce the effort for master data creation. For each of the aforementioned objects create one entity according to the master data guides attached to SAP Note 2969153. Then download it to Excel via Scenario Builder. In the Excel file complete the data for the other entities and then upload again via Scenario Builder. For more information on the scenario builder itself please check SAP Help and SAP Note 2791970. I am currently evaluating if and how the scenario builder content I have created can be made available. This would help to decrease the effort even further and I will keep you up to date regarding progress in that area.

The scenario builder does not allow to maintain all the fields which are mentioned in the master data guides, but in my tests, I found all the relevant data was there, except for tax classification. Tax classification “1” had to be maintained manually for all customers (role FLCU01 à Sales & Distribution à Billing à Output Tax).

Currently it is not possible to use the scenario builder for all master data. The mapping of locations to incoterm location (MD guide Transportation Network – Outbound), the organizational structure and charges master data must be created manually using the corresponding master data guide. Below you can find some hints and tricks which, based on my experience, could help you to reduce the effort for master data setup with and without scenario builder.

• The master data guides build upon each other. Use them in the order in which they are listed in the text of SAP Note 2969153, not the in the order in the attachment section.
• Field Payment Methods was mandatory for me for carriers, but not mentioned in the master data guide. I suggest you use payment method T – Bank Transfer.
• When mapping locations to incoterm locations the latter are free text. Keep in mind they must exactly match the incoterm locations maintained in the Business Partner. This match is case sensitive!
• Filling the Excel files for master data creation via scenario builder in some cases can be done efficiently be copying from the master data guide PDF into a TXT file – I can recommend Notepad – and then import into Excel from there. This is especially helpful for transportation zones.
• It is not possible to maintain geocoordinates for locations via scenario builder based on the data in the master data guide, since the upload via Excel requires a different format. Therefore, I maintained the coordinates manually in the system. The table below was created by downloading the locations via scenario builder and extracting the coordinates. You can use the coordinates in this format for upload via scenario builder.

LOC_ID	LONGITUDE	LATITUDE
Data Type CHAR_20	Data Type FLTP_16_16	Data Type FLTP_16_16
0017186001	-1.2158166666666666E+02	3.7004722222222220E+01
0017186003	-9.7325000000000003E+01	3.2739166666666662E+01
0017186004	-1.2206000000000000E+02	3.6980555555555547E+01
0017186005	-1.2139638888888889E+02	3.6847777777777772E+01
0017186006	-1.2234805555555555E+02	3.7155000000000001E+01
0017186007	-1.2241944444444445E+02	3.7774722222222223E+01
0017186008	-1.2159416666666667E+02	3.8685555555555553E+01
0017186009	-1.2131777777777778E+02	3.8035833333333322E+01
0017186010	-1.1845916666666668E+02	3.4031388888888891E+01
0017186011	-1.1845916666666668E+02	3.3949444444444431E+01
0017186012	-1.1721138888888889E+02	3.2724166666666662E+01
0017186002	-9.7123055555555553E+01	3.2706388888888881E+01

• The master data guide for the organizational structure is currently missing in SAP Note 2969153. You can find it in SAP Note 2970146 The assignment of users to organizational units, which is described in that guide, is relevant for organizational unit determination.
• In my test system the Business System Group had been maintained before the activation of TM. Check the name of the business system group which is maintained and assigned to the relevant client in your system. In the master data guide for organizational structure it is assumed the name is “BSG”. If this is different in your system you need to replace the name when setting up the organizational units. Otherwise Freight Settlement will fail

Business system group customizing

• The master data guide for charge management is a bit inconsistent regarding which carrier calculates rates based on which scale base. Just go with what is described in the procedures instead of what is described in the purpose section before. I.e. create zip zone à zip zone rates for carriers 1 -3. This worked fine for me.
• You can speed up creation of charge management master data by copying calculation sheets and freight agreements after creating the first entity according to the master data guide. Only a few fields need to be adapted after copying.
  • Calculation Sheet
    • Description
    • Rate Tables
  • Freight Agreement
    • Freight Agreement ID
    • Description
    • Carrier
    • Calculation Sheet
  • Do not forget to set the status for rate tables and freight agreements to “Released” and then save the document.
  • The master data guide for charge management also contains data on objects which are only relevant for later scenarios, e.g. shipping point SP_1720 for the stock transfer scenario. This shipping point will only be created when activating the BC set for that scenario, therefore no charges master data with reference to this shipping point can be created before that. You can skip the corresponding steps for charge management master data and revisit them later.

 

Test script execution

For testing the configuration follow the steps described in the test script attached to SAP Note 2969153. The information below may help to avoid confusion during test script execution.

• Several steps of the test script are about checking the document preview in the output management tab. This is only possible if your system is connected to an Adobe Documents Service Server. If this is not the case, just skip these steps.
• Some steps refer to SAP Best Practice scope item BD9 – Sell from stock for detailed information. With this link you can access the scope item.
• In step 15 Invoice Verification the “TM Ref.” tab is required. To display this tab you must set user parameter TM_INVOICE_CLERK for your user (System à User Profile à User Data à Tab Parameters). The parameter value can remain blank.

 

Conclusion

Please find below my most important findings after activating and testing the SAP Best Practices for S/4HANA Supply Chain for Transportation Management – Outbound Transportation Scenario 1909.

• The activation of the 1909 SAP Best Practice for outbound transportation with Transportation Management is possible in a SAP S/4HANA 2020 system.
• Master data creation is the most time-consuming step during the activation. If the scenario builder tool can be used (license for Advanced Transportation Management, see above) this effort can be reduced significantly.
• The steps required for the activation are described well in SAP Note 2969153. With the additional information from this blog post the activation can be done without too much effort.

I hope this article will help you with the activation of transportation management capability in your SAP S/4HANA system. Good luck with your efforts and enjoy testing the functionality!

 

Helpful links

• See all questions and answers about SAP Transportation Management
• Follow SAP Transportation Management for more blogs and updates
• Ask a Question about SAP Transportation Management
• Visit your community topic page for SAP Transportation Management

 

Brought to you by the SAP S/4HANA RIG and Customer Care team.

Source: https://blogs.sap.com/2021/03/16/how-to-guide-for-the-activation-of-sap-best-practices-for-sap-tm-in-sap-s-4hana-2020/