Skip to main content

SAP Transport Management (TM) Notes

 

SAP TRANSPORTATION MANAGEMENT CAN BE IMPLEMENTED IN FOLLOWING WAYS:-

1.       ECC separate system -----------------------------------------TM separate system

2.       S4(tm)------------------------------------------- completely embedded

3.       ECC-----------------------------------------S4(EWM+TM) this is for our TM and EWM

4.       S4---------------(DRF)------------------S4(tm+ewm+YL+em)

                                    ▪     Business system group(bsg):-

                                           1.    Ecc1—(asia, dubai)     2. Ecc2(rest of the world)

                                                            BSG1                                      BSG2

One TM system

● In the above example the two business systems was connected to one TM system and the system will understand from which system the sales order was triggered with the help of the business system group. This is the use  of a business system group and send the same information to that particular business system. So whenever entries are coming from bsg1 system will send the same to bsg1 and the same will happen to bsg2

1.       What are the variants of TM

2.       What are the versions of TM

3.       Integration between TM and ECC

Release setup

                                          1.   Integration between TM and ECC

●      If we are working in s4 system then there is no integration is required because they are on the same platform and SAP has set up an inbuilt setup called BGRFC with the help of BGRFC system will automatically create the required documents in system

●      But, when we are working in 9.1 to 9.6 sidecar versions we require CIF(core interface framework)

ECC--------------------------------TM  CIF

●      CIF helps you to transfer the data from ECC system to TM system. We can implement it to CRM, GTT, EWM. We have to adopt CIF.And it is not required in embedded.

CIF is used to transfer the master and org data’s

●      To move transactional data we require (IN standalone)

                                                              ▪    QRFC

                                                              ▪    TRFC

                                                              ▪    QUEUE SCHEDULER

                                                              ▪    RFC

                                                              ▪    XI/PI/PO

❖ If we are working on s4 systems we need not take are of qrfc, trfc, etc.,

Implementation of SAP TM

1.      ECC----------------------------------TM(standalone)

2.      S4 TM(embedded)-----presently taking training on this model

3.      ECC---------------------------------s4(TM,EWM)

● in this scenario we use two systems and we need some config touch points.and they are two different systems

4.      S4---------------(DRF)---------------------s4(TM, EWM, YL)

❖ Variants of SAP TM:-

1.  Shipper -----Eg:-nestle,cococola,pepsi------->ECC-----TM

2.  LSP (Logistics service provider)--------FEDEX, ups, bluedart---->TM

3.  FF (Freight forworder)-------------DHL, Gati------------>TM

4.  Retailer---------------------reliance trends, Dmart, Walmart------>ECC----TM

✔   In the above examples the shipper will manufacture the goods.

✔   The LSP will provide the transportation service they will not manufacture any goods they main activities are selling the services

✔   In FF they will act as mediators by supplying their vehicles between the shipper and LSP

✔   Retailers will not manufacture the goods but they will get the goods on consignment basis.

For shipper and retailer we require both ECC and TM systems

For FF and LSP we require only TM system o       There are two costs available

1.      product cost:

It is the cost for your customer. We charge this one from the customer when we do customer billing.

2.      freight cost:(overhead expense)

It is the cost for our carrier. When the carrier transports the goods we have to make a payment to the carrier.

       ▪           In some scenarios the freight costs can be included in the product costs

Eg:In international and express scenarios

▪     Document flow for shipper and retailer scenarios: SO/PO/IBD/OBD---------FU, FO/FB-----charges

------settlement---SES---SPO------MIRO-------------customer billing (Tcode VF01)

       ▪    Document flow for LSP and FF scenarios:

FWO-----FU----FO/FB----charges-----settlement----------billing document

o        Enterprise structure----------------master data-------------------Transactional data

On SD side: We create sales order—so

On MM side:PO/IBD/PR

On FI side: ledger accounts , accounts receivables and account payables

On CO side :we have to setup a controlling area

❖ Enterprise structure: in enterprise structure we have to create

1.      Company

2.      Company code

3.      Plant

4.      Shipping point

5.      Controlling area

6.      Sales organisation

7.      Purchase organisation

8.      Storage location

9.      Distribution channel

10.  Division

o        If we are working for SAP TM we have to activate all the business functions(Tcode---SFW5)

▪    If we don’t activate all the business functions we cant see the transportation management node in integration with other SAP components.

▪    Separately we need not to activate the business functions because in s4 system it comes by default.

▪ In standalone systems we have to activate the business functions and the tcode is SFW5.

       ▪    In Tcode------->SM59 we have to setup the RFC connections

▪    If we are not aware of which version we are working on we have to go to the system tab and click on the status tab, click on product version details and click on installed product versions.

▪    Whenever we are working on a SAP project we have to check whether the optimizer was installed or not. The optimiser is a separate engine and the tcode to check the same is RCCF_VERSION.

       ▪      Number ranges cannot be transported from lower system to higher system.

❖     Define company path: SPRO----enterprise structure---definition---financial accounting--- define company

❖     Company code creation path: SPRO---enterprise structure

-----definition----financial accounting--------copy, delete, check, company code.

▪    The relationship between the company and company code is one to many

▪    As a general practice we have to copy the company code from the existing company code

▪    After copying the company code we have to go to our company code and edit the same

❖     Controlling area path:SPRO---- enterprise structure-------definition-------controlling ---maintain controlling area.

❖     Plant creation path: SPRO----enterprise

structure------definition---------Logistics general--------define, copy, check plant

❖     Division creation path: enterprise structure----- definition ----------logistics general -define, copy, delete, division

▪    If we want to create a storage location firstly we have to define our plant because in plant we have to create a storage location and the storage location is inside  in our plant

❖     Storage location path: enterprise structure-----definition------materials management ------ maintain storage location

❖     Purchase organisation creation path: enterprise structure-----definition------materials management-------maintain purchasing organisation

❖     Shipping point creation path: enterprise structure----definition------logistics execution-------- define ,copy, delete, check shipping point

Assignment of enterprise structure :

❖     Assign company code to company path: enterprise structure -------assignment ----------------financial accounting –assign company code to company path.

●      One company can have multiple company codes

❖     Assign company code to controlling area path: enterprise structure ------- Assignment-------controlling ---assign company code to controlling area path.

●      One company code can have multiple controlling areas

❖     Assign plant to company code path: enterprise structure ------Assignment-----------logistics general-------assign plant to company code

●      One company code can have multiple plants and the relationship is one to many and once you assigned the plant to one company code and the same plant cannot be assigned to the other company code

❖     Assign business area to plant/ valuation area and division path: enterprise structure ------------assignment-----------logistics general-----assign business area to plant/ valuation area and division ❖ Assign sales organisation to company code: enterprise structure -----definition-------assignment--------sales and distribution—assign

sales organisation to company code

●      One company code can have multiple sales organisations and once we assigned the company to one sales organisation we cannot assign the same sales organisation to a different company code.

❖     Assign distribution channel to sales organisation path: enterprise structure ---------definition -----------assignment---------sales and distribution -----------assign distribution channel to sales organisation.

❖     Assign division to sales organisation path: enterprise structure------definition----assignment----------sales and distribution--------assign division to sales organisation

❖     Setup sales area path: enterprise structure----------definition-------assignment------sales and distribution------setup sales area.

❖     Assign purchasing organisation to company code: enterprise structure------definition----------assignment-------materials management------assign purchasing organisation to company code.

❖     Assign purchasing organisation to plant:enterprise structure

---------definition------assignment------materials management------assign purchasing organisation to plant.

❖     Assign shipping point to plant:enterprise structure

----------definition-------assignment-------logistics execution---------assign shipping point to plant.

❖     Assign sales organisation, distribution channel and plant path:enterprise structure----definition-----assignment------sales and distribution-------assign sales organisation, distribution channel and plant.

❖     Purchasing group creation path: tcode----ome4 Master data:

1.customer master

2.material master

3.vendor master

●      Generally we create a vendor master the tcodes are

XK01,XK02,XK03

●      And for customer master we use the tcodes are xd01,xd02, xd03

●      And for material master we use the tcodes are mm01,mm02,mm03

❖     Traditionally we used these tcodes for creating the master data but in s4 system we cannot use them because they are absolute now

❖     And in s4 there is a concept called business partner roles and while creating the customer as business partner we have to assign the customer roles to that particular BP the same follows to the vendor too.

                                     ▪      BP (business partner) roles for customer are FLCU00, FLCU01

                                     ▪          BP (business partner) roles for vendor are FLVN00, FLVN01

● To check the BP roles in the table the tcode is se16n and the table is but100 and knvv.

Material master data:-

                           ▪    To create material master data the Tcode is MM01

▪    In select views we have to select basic data 1, basic data 2, sales org data 1, sales org data 2, sales/plant general data, purchasing, purchase order test, MRP1, MRP2, MRP3, MRP4, general plant data/ storage 1, general plant data/storage 2, accounting 1, accounting 2.

▪    MARA Is the table which is used to check and the tcode for table is se16n in that table we have to enter the table name as mara

❖      Sales document type creation path(tcode—vov8): spro------sales and distribution----sales ------sales documents -----------sales documents header------define sales document types.

● OR is the standard order type IN SAP which is used for defining sales order types

❖      Creation of a sales order tcode va01

Error message: no pricing procedure could be determined

                              ▪    Goto tcode ovkk

                              ▪  To see the doc.pricing procedure tcode vov8 and it is A

▪    To see the customer pricing procedure the tcode is BP and we have to select our customer there we have to select the customer role as FLCU01 and the pricing procedure is 01

                              ▪    The standard pricing procedure is RVAA01

Error message: control indicators for controlling area xxx does not exist

▪    Controlling area path---spro—controlling-----general controlling-----organisation-----maintain controlling area.

▪    In our controlling area we have to maintain the cctr std.hierarchy maintain H1 there

▪    After maintaining that entry we have to click on activate controlling areas and control indicators and activate all the options and checkboxes.

Error message: ship.condition 01 and loading group 0001 plant xxx stloc not defined

▪    Tcode:OVL2 maintain shipping condition as 01 and and loading group as 0001

Error message: schedule line category CN not defined.

▪    Tcode:vov5 Give item category as TAN and MRP type is PD and maintain CN in MSLCA

❖ To determine the pricing procedure automatically the tcode is VK11 and the condition type is PR00 and select radio button customer/material as with release status

●      Creation of purchase order: tcode ME21N

●      The standard purchase order type is NB ● Error messages while creating purchase order:

1.    Account assignment mandatory for material xxx (enter acc. Ass. Cat) and the tcode is OMS2 and to check the material type the table is mara and the tcode is se16n and our material type is FERT

●      We have to goto quantity and value updating there. We have tick the checkboxes of quantity and value updating.

●      Valuation area is always a plant

●      We have to check mark the info update so that system will automatically update the price

❖   IN ORGANISATON DATA WE HAVE CREATED:

1.      company

2.      company code

3.      plant

4.      shipping point

5.      storage location

6.      distribution channel

7.      division

8.      sales organisation

❖   IN MASTER DATA WE HAVE CREATED :

1.      Customer master

2.      Material master

3.      Vendor master

❖   IN TRANSCATIONAL DATA WE HAVE CREATED:

1.      Sales order

2.      Purchase order

●      THE MASTER DATA WHICH WE HAVE CREATED IN OUR ECC SYSTEM THE SAME DATA

IS APPLICABLE TO OUR TM SYSTEM AND WE HAVE TO TRANSFER THE DATA FROM ECC SYSTEM TO TM SYSTEM

●      WE DON’T TRANSFER  THE PURCHASE ORGANISATION AND THE SALES

ORGANISATION AND COMPANY CODE TO TM SYSTEM

●      IN TM WE SEPERATELY CREATE A SALES ORGANISATION, PURCHASE ORGANISATION

●      THE TRANSCATION DATA WHICH WE CREATED IN ECC SYSTEM WE WILL TRANSFER

THE SAME TO OUR TM SYSTEM (SALES AND PURCHASE ORDERS)

●      WE HAVE TO TRANSFER THE PLANT, SHIPPING POINT, STORAGE LOCATION FROM ECC TO TM SYSTEM

●      WHEN WE CREATE A SALES ORDER GOODS ARE COMING FROM SHIPPING POINT TO OUR CUSTOMER LOCATION AND WHEN WE CREATE A PURCHASE ORDER THE GOODS ARE COMING FROM VENDOR TO OUR PLANT LOCATION.

❖   POSTING A STOCK:-

●      To post a stock tcode is MIGO

●      We have to enter 501 that is receipt w/o purchase order and R10 other and A01 goods receipt

●      ERRORS WHILE POSTING A STOCK:-

1.    Posting only possible in periods xxx and xxx in company code xxx.

we have to goto tcode mmpv.

Firstly we have to goto tcode OMSY there we have to check the period. And after checking the same we have to goto tcode mmpv.

Error 2:check table T159L entry xxx does not exist

● To goto plant parameters the table is SM30 and the table is T159L, clickon customizing------> continue without specifying project------> clickon plant parameters and activate all the checkboxes.

Path: spro------>materials management---------->inventory and physical inventory------>plant parameters

Error 3: material ledger is not active in valuation area xxx

❖   We have to goto omx3 tcode.

❖   We have to goto omx1 tcode to active material ledger account and maintain price determination as 2 checkmark price determination binding.

❖   Goto ckmstart and uncheck the test run-------> and clickon execute------>checkmark start immediately------->give your output device as lp01 and to check the same tcode sm37--------> click on execute

Error 4: correct the customizing settings for ledgers for the universal journal

●      Clickon that particular error and there is a link in that error FIN_CUST_CONS_CHK_P and goto the error message the version 0 of co area xxx is not assigned to any ledger---             click on the question mark to open that error and there we have to click on define ledger for CO version and select any predefined data copy the data from the pre existing ones and from that create a new one

●      And to check whether the stock is posted or not the tcode is

MMBE----click on execute------>click on stock --------->click on material movements

WE HAVE TO TRANSFER CUSTOMER, VENDOR AND MATERIAL MASTERS DATA TO TM

SYSTEM AND WE NEED NOT TRANSFER THE MATERIAL MASTER DATA TO ANY OF THE

SYSTEMS AND THE UNIQUE TRANSCATION IS MM01

Customer is also called as source to party/ship to party

IN TM WE HAVE A CONCEPT CALLED LOCATIONS

Whenever we transfer the customer and vendor masters to TM system. system will create a location with location type.

In TM, the source location is the shipping point and the destination

location is the customer.

●                               TM CONFIGURATION :-

▪    TRANSFER THE CUSTOMER AND VENDOR MASTER DATA’S TO TM SYSTEM.

Go to tcode SE38 and create a program called /sapapo/create_location this is only in s4 system and in standalone system the tcode is NCFM1

●                               There we have to transfer our customer, vendor to check the same path------------>logistics ------->transportation management-------> master data

--------------------->transportation network-------> location----------->/SCMTMS/LOC3 –LOCATION

●                               System will create the location with location types and the location type for customer is 1021 and for the vendor also the location type is 1021 basing on partner roles system will identify who is the customer and  vendor and the roles are FLVN00, FLVN01-----> for vendor and  customer the roles are FLCU00 and FLCU01

●                               Customer roles-----------> FLCU00, FLCU01

●                               Vendor roles--------------> FLVN00, FLVN01

❖   But if we are working in standalone system system will create a location type as

●      For customer -----------> 1010

AND

●      For vendor---------------> 1011

❖   When we transfer the shipping point from ECC to TM system will occupy the prefix as SP_XXX here sp stands for shipping point

TM TRANSACTIONAL CONFIGURATION:-

                                  1.   Creation of control keys: our control key is 0051

Path for creation of control keys: spro ------->transportation

management----->integration---------> logistics integration------> internal TM component integration--->define control keys for document integration

●      As a standard practice we shall not create a control key of our own and should use the standard one which was given by SAP

●      From 0001 to 0020 -------------> external control keys and from 0051 to 0064 they are internal control keys From :

0001 to 0020--------------------> external control keys

0051 to 0064--------------------> internal control keys

❖   Control key is a parameter which will help you to transfer the documents to TM system. They can be a sales or purchase order.

● Goto Define transportation relevance of sales documents and create an entry

❖   Path for creating define transportation relevance of sales documents:spro------------------------------>transportation management------->integration ---------->logistics integration-------------------->internal

TM component integration----define transportation relevance of sales documents

●      If we maintained shipping conditions as 01 then system will only transfer the sales order which are created in that particular shipping conditions  to TM And if we remove the shipping condition and create a sales document integration then irrespective of the shipping condition the documents will move to TM

●      Shipping conditions are at header level because the sold and ship to party is at header level

●      In schedule lines if the confirmed quantity is ZERO. system will not create a freight unit.

●      Any document generated in SAP it shall have a document type Document type will overwrite the shipping conditions if we maintained shipping conditions as 01 in customer master and 02 in sales document type then system will pick the shipping type from our sales document type

●      Tcode for Fiori apps:-/UI2/FLP ----------->SAP Fiori launch pad

✔ To see the freight unit path: Fiori apps ----------> planning --------> edit freight unit

●      Freight unit will be generated with the number series of

41000XXX

●      Freight order will be generated with the number series of

61000XXX

❖   The freight unit is the replica of your sales document (general definition) Or

A freight unit is the smallest object which is ready for transportation process

❖   A freight unit is the s,a

❖   In SAP TM one document type is a default one. If system is unable to pick any document type then it will pick the default document type. And the default document type is 0001

❖   Sales order is not a planned document its just a requirement document and in the same way freight unit is the requirement document

❖   In tm we have default document types. One document type is a default one

●      System is creating a freight unit with the help of LOGISTICS INTEGRATION PROFILE(LIP)

●      In logistics integration profile there is a concept called FREIGHT UNIT BUILDING RULE(FUBR)

❖   FREIGHT UNIT BUILDING RULE(FUBR):

●      Freight unit building rule will help you to determine your freight unit type.

OR

●      Freight unit building rule will help you to determine the respective/required freight unit type

❖   Now we are trying to create a logistics integration profile and in that logistics integration profile(LIP)  we are trying to assign the freight unit building rule (FUBR) and we have assigned this LIP to define transportation relevance of sales documents to TM.

❖   Our business system will overwrite the TM functionality

❖   In order to create a freight order we have to configure the TM MASTER DATA

●      Creation of freight unit type path:- transportation management----------------------->planning------>freight unit-----------> define freight unit types.

●      By using that path we can create our freight unit type

●      TM works on FIORI or NWBC

●      If we create a sales order then the source location is our shipping point and the destination location is our customer and if we create our purchase order then the source location is our vendor and the destination location is our plant.

●      we have to choose the plan on confirmed quantity in logistics integration profile then only system will plan on the confirmed quantities otherwise system will create a freight unit on not confirmed quantity

●      In the logistics integration profile we have to check mark the automatic freight unit building then only the system will create a freight unit. And in sap we cannot create a freight unit manually.

●      To check our list of sales orders the tcode is va05n

●      If we want to create freight unit with our freight unit type then firstly, we have to create  freight unit type, then we have to create a freight unit building rule in that freight unit building rule we have to link our freight unit document type then we have to link the FUBR in our logistics integration profile and this logistics integration profile shall be linked to our sales order relevance to tm documents

●      Creation of freight unit building rule path: FIORI APPS-----> profiles and settings ------> create freight unit building rule

●      We have to give our freight unit document type in document type

●      After creation of our freight unit building rule we have to copy the same from the Fiori apps and paste it on our logistics integration profile.

●      After doing so we can see our document type in freight unit

●      If we don't have /UI2/FLP—SAP FIORI launch pad ---------> goto favorites--------> insert transaction------>/UI2/FLP ● we have to insert that  particular transaction.

●      and after clicking on that particular transaction we have to copy a link and paste it on our google chrome or if it is IE 11 we can work on that particular browser.

●      Creation of transportation request tcode ------->se09------>click on create ------------>click on customizing request----->create our own request.

❖   UNPLANNED DOCUMENTS IN TM:-

1.      Freight unit

2.      Container

3.      Transportation unit

4.      Rail car

5.      Vessel

●      to create a freight unit no master data is required and we required to have master data to create all the documents in TM like FO/FB, CHARGES,

SETTLEMENT, SPO, SES, MIRO, CUSTOMER BILLING

●      In order to create a freight order we have to configure the TM MASTER DATA.

❖   TM MASTER DATA:-

1.      Mode of transport------------------------>road, rail, sea, air

2.      Means of transport----------------------->truck, tractor, bus-->in road scenario

Train.------------>in rail scenario

Ship,cruise------>in sea scenario

Aeroplane, helicopter----->in air scenario

                                                    ▪    In simple terms it can be any vehicle

3.      Resource          ----------------->4 seater car,100 cc truck--->in road scenario

● SUB DIVISIONS OF RESOURCES:-

1.      Vehicle resource

2.      Handling unit resource

3.      Transportation unit resource

4.      Calendar resource

5.      Driver resource

                                                    ▪  Resource will give the actual capacity of the vehicle

4.      Equipment master data

5.      Transportation zone

6.      Transportation lane

❖   TM ORGANISATION DATA:1. Purchase organisation

2.      Purchase group

3.      Sales organisation

4.      Sales group

5.      Sales office

●      Firstly, we have to create a mode of transport.

●      Secondly we have to create means of transport

●      Thirdly  we have to create a resource

●      when we are creating means of transport system will ask for resource, and when we create a means of transport system will ask for mode of transport that is the reason why we have to create mode of transport, means of transport, resource

●      order management------>planning------>execution and monitoring---->charges and settlement

❖   PLANNING IN SAP TM:-

1.    Mode of transport path:spro----->transportation management----->master data---------->transportation network----->transportation lane--->define transportation mode. ● 01--->road

●      02--->rail

●      03--->sea

●      04--->inland waterway

●      05--->air

●      Note: We shall not assign our means of transport to a particular mode of transport and if we are assigning our means of transport to a particular mode of transport then we are restricting that particular means of transport to that mode of transport.

●      WE CANNOT CREATE A FREIGHT UNIT MANUALLY

●      Means of transport means----> Means of transportation is any of the different kinds of transport facilities used for moving goods and people from one location to the other. ... The means of transportation are bus, train, aeroplane, ship, car, etc while the mode of transportation refers to road, air, sea/ocean, etc.

●      Firstly we have to define our mode of transport and assign it to our means of transport and after define our means of transport and assign it our resource

LEGS OF SHIPMENT DETERMINATION:1.    Pre carriage

2.      Pick up

3.      Main carriage

4.      On carriage

5.      Delivery

Eg:- X customer has ordered for Y product, from A location to F location and we are using multimode of transport system to minimise our freight cost ie.,road, rail, sea, and air.

●      X customer--> Y product----------->A----->road, rail, ocean, air---->G Canada

                                                    ▪    A(hyd)--------------->B Chennai (road)---->pre carriage

                                                    ▪     B(Chennai)--------->C Mumbai (road)--->pickup

                                                    ▪  C(Mumbai)--------->D new York (sea)------>main carriage

                                                    ▪  D(new york)--------->F montreal (air)------->on carriage

                                                    ▪    F(montreal)------->G Ontario (road)------>delivery of goods to cus

●      The longest mode of transportation is main carriage

●      Means of transport is directly proportional to our mode of transport

Means of transport creation path:-transportation management---->master data------------->resources---->means of transport and compartment--->define means of transport

●      we have to create 2 trucks

1.      full truck load

2.      less than truck load

▪    means of transport means-----> Means of transport means----> Means of transportation is any of the different kinds of transport facilities used for moving goods and people from one location to the other. ... The means of transportation are bus, train, aeroplane, ship, car, etc while the mode of transportation refers to road, air, sea/ocean, etc.

resource creation path:- SAP easy access screen------>SAP

menu----->logistics------------------->transportation management----->master data------->resource------------------------->/scmtms/RES01-resource.

▪    resource means-------->You can use resource classes to specify the kind of vehicle that is to be used for your transportation activities. When you enter the means of transport in the resource master data, the system automatically determines the resource class based on the means of transport.

●      While creating your resource master data we shall not give location because by doing so you are restricting that particular resource to that particular location

●      Firstly we have to define mode of transport and assign the same to means of transport.  Then define  means of transport and assign the same to resource master data

●      If you are creating any master data in the system always the best practice Is to give the back dated dates and not to give the front dated dates

●      In resource master data in the ownership tab if we left that blank then system will think that it’s a leased resource.

Transportation zones definition:-

Transportation Zones as grouping element for Locations are used to

define the SAP TM Transportation Network in a more efficient manner by making pure location definitions obsolete.

▪    To reduce huge master data we will create zone and we will assign the locations. From zone it will pick the route determination departure country and zone

▪    In transportation zone we have to maintain plant and shipping point

Transportation zones path:- SAP easy access------->sap

menu------>logistics------------------------------->transportation management-------master data-------->transportation network---------------->transportation

zone------>/scmtms/zone---->transportation zone

▪    Whenever we transfer the shipping point, customer, plant from ECC system automatically zones will also gets transferred

▪    Whenever we are creating our plant, shipping point, and customer we have to assign the zones to them then only we can transfer the same to the TM system and after doing the same we need to goto tcode SE38 there we have to execute a programm /sapapo/create_location. And system will

automatically will create zones

▪    In the same way transfer the customer also while creating customer in BP assign the destination zone in customer master data and goto tcode SE38 there we have to execute a programm /sapapo/create_location and system will

automatically create zones

▪    In intrazone concept we can club multiple zones Eg we can club north and south zones and we can club source and destination zones

o     If we want to search in what locations the shipping point is present then we have to click on open advanced search and give your location in search bar and click on advance search button we can find this open advanced search in define transportation zones.

Transportation zones path in ECC/business system:- logistics

execution----->transportation---->basic transportation functions---->routes------>route determination------>define transportation zones.

●      Org. elements in source zone:

1.      Shipping point

2.      Plant

3.      Vendor

●      Org. elements in destination zone:-

1.      Sometimes plant can also be the destination zone

2.      Customer

Org. data in sap tm:-

1.      Purchase organisation, purchasing group it is for our shipper and retailer industries

2.      Sales organisation,sales office and sales group is for our LSP and FF industries

Note: the org. data which we create in ECC is different and the org data which we create in TM is different. In ecc it is for our vendor and in TM it is for our carrier.

Creating organisational model in sap tm path:- transportation

management--->master data-------->organisational management----->organisational model--->-create organisational model.

●                              Tcodes for creating org. data in sap tm are ppome, ppoce

●                              If you create the same then system will create an internal number range

●                              Business system group is important when we integrate with multiple business systems

●                              We have to maintain a relationship between our tm purchase organisation and ECC purchase organisation by assigning the same purchase org which was created by us in ECC system ie.,BSG.ORG unit in this we have to maintain our ECC purchase organisation by maintain so we have assigned the ECC purchase organisation to our TM purchase organisation if we maintained the relationship between them then system will create SES,SPO,MIRO docs.

●                              If we maintain that relationship then only system will create a SES, SPO, MIRO in ECC system.

●                              We should not maintain any bsg org unit while we are creating our purchasing group in TM why because that there is no specific relationship between our purchase org and purchasing grp.

●                              In our freight unit type we have to maintain our TM purchasing organisation and TM purchasing group

●                              If you want to transport number ranges from one system to another system then we have to maintain the BRF conditions then only we can able to

transfer the same to one system to another system BRF is called as business rules framework

Creating a condition path:- Fiori apps----->profile & settings----->conditions

Creating a condition in NWBC path:- application administration----->general settings -------->conditions

●                              The condition is /SCMTMS/TOR_ORGUNIT this condition is used In order to determine our purchase org. in tm

●                              From the above image we have to maintain our data in the condition by selecting direct value input

●                              There we have to maintain our shipping point

●                              By clicking on direct value input we have to give our purchase organisaton number like in the below image

▪    Before assigning the condition we have to goto our freight unit type and remove our purchasing org. and purchasing grp

       ▪        After doing the same we have to assign the condition in our freight unit type

●                              By removing the purchasing org and purchasing group we are not able to find our purchasing org and group in our freight unit

●                              If you maintain condition in our freight unit type automatically system will pick our purchasing org and purchasing group in our freight unit

▪ Error message:-numbers in number range 01 for object RV_BELEG are almost used up.

Tcode:snro and give RV_BELEG

●                              If you want to check the number range that we are using tcode:vov8 we have to go to  our sales document type and see no.range int.asst

●                              We can move the conditions from one system to another system.

Extractors:- with the help of these extractors we can pull the data and we can update the same data in TM system and with this extractors we can create a freight unit manually from non SAP business systems.

●                              The standard solution is that we have to activate a check mark in the logistics integration profile then only we can create a freight unit in the system

●                              As we can see in the above image there is a tick mark checked in the automatic freight unit building in that way system is able to create a freight unit manually

●                              if you want to create a freight unit manually we have to go to Fiori apps---------------------->transportation-logistics integration----->delivery integration

●                              In this area we can able to see our freight units manually and create delivery for the same freight units which are created manually

●                              Shipping type in freight unit can come from our sales order document and it can also come from our TM document with the help of transportation mode in shipper and retailer scenerios. If we are in LSP & FF it will come from the FWO(forwording order)

●                              If you want to maintain the shipping type we have to goto our sales order tcode-va01 and goto header data----->shipping tab and maintain shipping conditions like in the below image.

●                              If you mainteined the same then the same will be determined in our freight unit

●                              As we can see in the above picture when we defined our shipping type in our sales order in header data we can see our transportation mode determined in our freight unit

       ▪             With the help of Geo cordinates system will help you to determine the exact location

●                              In the above image we can see that geo cordinates and with the help of the same system will able to determine the exact location

Direct shipment options:- it means that we are transporting the goods directly to the customer without doing any planning in TM it is done where the customer needs the urgent requirement of the goods

❖   PLANNING AND EXECUTION:-

●      TOR:- FU, FB, FO------------------->transportation order

●      TRQ:-FWO, OTR, DTR------------->transportation request

▪    /scmtms is for TM system goto table tcode se16n and enter this condition /SCMTMS/D_TORROT this will give you the entire information about your freight units, freight orders, freight booking, service order, transportation unit, freight order copy for tendering

       ▪    In this way we can see the freight units

●      In the above image we can see that we have had all the document types that are to be displayed

●      If you give the table name as /scmtms/D_TRQROT then it will display all the forwording orders.you can see the same in the below image

●      In the above image we have given the /SCMTMS/D_TRQROT then it will give you about forwording orders

●      We can see the list of orders which are displayed in the system

●      We can see that we can choose the orders which are to be displayed

●      In HANA systems we dont have OTR and DTR concepts

●      Presentation layer, application layer, database layer

❖   Unplanned documents in TM:- FU, TU, container, RCU

When we are working in rail car scenerio we have a concept called RCM/OSEM. RCM stands for railcar management and OSEM stands for onsite event management

●      How to plan -----------basing on best route, best vehicle, best price, customer delivarable time

With the help of optimizer system will do automatic planning and in transportation cockpit

●      So, whenever we are working for sap tm project we have to ask the basis guy to install the optimizer engine in SAP TM

❖   To check in which version we are working on we have to goto system------status-----------product version details----goto installed product versions

●      In the above image we can see that at which product version we are working on and we have to see the service pack is installed or not the same can be seen in the below image

●      In order to work that particular functionality we have to check whether all the components have activated or not in the above picture SAP TM is standalone and S4CORE is the embedded system

●      The above are the support packages and we have to check whether all the support packages activated or not

●      And nextly we have to check whether the optimizer is installed or not and the tcode for the same is rccf_verison

●      Here we have to check whether the optimizer is installed or not

●      And there we can see all the versions whether they are installed or not

●      If our client installed basic shipping we cannot do the optimizer planning

▪ And in the below image we can see the differences between basic and advanced shipping.

       ▪    We have to goto tcode SBGRFCMON-bgRFC monitor

       ▪    We have to click on execute on this particular screen

▪    And check whether all the green lights are present or not if there is a red light then there is something absent in the system and the green light indicates whether back and forth communication is happening or not

TRANSPORTATION PLANNING IN SAP TM

There are different kinds of plannings are there

They are:-

1.      Manual planning

2.      Optimizer planning

3.      One step planning

4.      Two step planning

5.      Short cut planning

6.      Back ground and fore ground planning

● Order management----transportation planning---execution and tendering and monitoring---charges and settlement

❖   When we are planning we have to observe how to plan, when to plan and what to plan

PROFILES:-

Profiles will help you to filter your demands ie., freight units in the transportation cockpit.

1.    Selection profile:- it is a profile which will help you to filter your freight units based on time, geographical and additional functions.

● Creation of selection profile:1. Time related attributes

2.        Geographical related attributes

3.        Additional functions

❖   Selection profile will have only three attributes they are listed above

1.           Time related attributes:-                                                                            delivarable dates xx---for   A product-------A location------------------B location-------->28/02/2021

A  product-------A location -----------------B location------->01/03/2021

B   product-------A location------------------Z location-------->01/03/2021

C   product-------A location------------------D location------->10/03/2021

D  product-------A location------------------E location------->18/03/2021

F product-------X location------------------Y location------->23/02/2021

●      Now the planner has to see the visibility of the orders which needs to be delivarable by next 5 days and the todays date is 25th feb and now the planner has to see the visibility of the orders which are to be delivarable in the next 5 days.

●      From 25th the end date is -------->1st march we need to count from 25th the planner will see the visibility of the goods which needs to be delivered in next 5 days and from the above dates he can see 3 orders

●      From the above example system was unable to pick the 23/02/2021 order and it is missing.

❖   Now the planner has a visibility of 5 days future -------offset  days---3 past and from the above example system will pick the orders from 22, 23, 24, 25, 26 and that is the time period we have in our planning area because from 25th system will go 3 days back and the system will consider the orders which are missed in the past and since system is taking 3 days offset dates now system will calculate from 22nd system will calculate 5 days future from 22nd and the latest delivarable date is 26th and the orders will be picked by the system is only one ie., 23/02/2021.if you take 10 days future

and 3 days past then system will pick only 4 orders. And there is a holiday on 26th so system will not consider holidays and system will consider 26th as a holiday and it will extend the delivarable date

10 days (future)---offset days---3

22, 23, 24, 25, 26,27, 28, 1, 2, 3, 4, 5

●      From the above example system will consider 26th as holiday and It will extend the date to 5th and the new delivarable date is 5th of march

●      Transportation cockpit is a place where we can see the visibility of our freight units, freight orders, trucks, trailers or our shipment documents in a single area

❖   We need to create a selection profile in fiori apps

Path for creating selection profile in nwbc is---->application administration------------->profiles----->create selection profiles

❖   Selection profile path in fiori apps----->fiori apps---> profiles and settings--->create selection profile

❖   From the above image we can create a selection profile and in the above image we can see the selection profile inside of the profile

❖   Inside the selection profile it looks as in the above image

PLANNING PROFILE:- planning profile will help you to plan our shipments based on

1.      Capacity selection settings

2.      Optimiser settings

3.      Cost and constraints settings

4.      Carrier selection settings

5.      Incompatability settings

6.      Manual settings

7.      Scheduling settings

8.      Profile settings

9.      Load planning settings

●      Without planning profile we cannot plan our shipments

Planning profile creation path:- fiori apps--->transportation- profiles and settings-------->create planning profile.

●      In the above image we can see the creation of a planning profile

❖   And the planning profile will look like in the above image

❖   The selection profile will help you to filter our freight units basing on the pickup and delivery dates and planning profile will help you to plan our shipments

❖   Delivery based planning means we have to create a delivery and from that delivery we have to create a freight order and the ownership will be there at our ECC system level and order based planning means we are creating a sales order and freight order and doing all the kind of planning here and sending the final information to our ECC/business system saying that these are the latest dates which are to be delivered to the end customer location

❖   When we do order based planning the entire authority is at our end now and when we do delivery based planning we are committed to our customer

❖   The route which we get in sales order is not actual route its just a proposed route and the route which we get in delivery document is the actual route

Error messages:-

1.      No delivery proposal for FU 41XXX: FU not relavent for delivery integration

2.      1 FU is unsuitable for delivery proposal; removed from scope

3.      1 selected objects is unsuitable for delivery proposal; removed from scope

●      If these error messages popped up then we have to change the control keys or enable to move the sales order to outbound delivery and the same is present in the above image or we have to change the control keys to 0052

If we select outbd.delivery then system will allow the same

TM will do planning in optimizer

●      From the above image we can choose the class and the Goto se24 to enhance the methods /SCMTMS/CL_PC_METHODS from that we can enhance the methods if we double click on the same we cn enhance the same by entering into the programm

       ▪    TRQ-----> FWO, OTR and DTR

       ▪    TOR-----> FU, FO, FB, service order

▪    Any error in the cockpit the tcode for the same is slg1 and we have to enter our user id and click on execute then system will give you the exact error message

▪ From the above image we can see that we have to enter our user id and click on execute

       ▪       And from the above image we can see the exact error in the system

▪    And from the above image we can see whether there are any authorization issues are present or not and the tcode su53

❖   Parallel processing profiles:- These are the profiles which are used to split the servers and allot the space accordingly

●      Some examples of server sizing can be seen in the below image

●      From the above image we can see that it is for sap scm

●      This is the server sizing of sap tm

❖   So, whenever we don’t see the trucks in our cockpit that means that we haven’t maintained the capacity selection settings we have to maintain the capacity selection settings in planning profile and these settings will help us to determine trucks, trailers, schedules etc., in our cockpit

o     We have to maintain the capacity selection settings then only we can see the resources in our transportation cockpit and we can see the same in the above image

● And when we maintained the same we can see our resources in our cockpit

▪    In realtime if something is not displayed we have to retrigger the sales order to do the same we have to goto sales order and enter some notes and in that way we can retrigger the sales order and automatically the sales order gets refreshed and will update in the corrosponding freight unit

Error messages:-

1.      messages for capacity selection settings XXX resource selection using resource attribute.

2.      Choose either trm specific or trm unspecific selection options only

● The meaning of those error messages is when you are maintaining mode of transport relavance maintain mode of transport relavance if you are not maintaining mode of transport relavance don’t assign the same.

From the above images we can see the  error messages

A cash sale is a sale in which immediate delivery is possible in cash sales the control lies on our document type and tcode vov8 and BV is for cash sales for all your cash sales delivery will be automatically

If you maintain “ X “ then system will create  delivery automatically whenever we save our sales order which means that for all of our cash sales delivery will be created automatically and in this scenerio we don’t require a planning because customer will come and he/she themselves will take away the goods

So in TM when we create a sales order with the document type BV then system will create delivery automatically

●      We can see that in above image in cash sales delivery is automatically created, firstly sales order will get saved and then delivery will be created. And it will not move to TM.that is not moved to TM because of our shipping conditions

●      The shipping condition for BV document type is 10 ie., as soon as possible it is for cash sale business. And we don’t require to plan and we don’t require a freight unit in cash sales and if you want to move this sales order to TM system we have to change the document type In sales order relavance to TM as BV

●      In this type of scenerio we have to enter our freight order document type directly in our FUBR(freight unit building rule).

●      Long term planning is nothing but planning your documents with freight units

▪    And from the above example we can see that system has generated a freight order directly and the series of freight order is “61” it starts with “61” and for freight unit it starts with “41” and from here we have to create a delivery to our customer location

▪    In express courier and parcel scenerios If the weight of a product is below 750kgs by default system will create a freight order. It is the standard rule in any industry not only in sap tm system will create a execution document

       ▪    Error messages:-

1.      Optimiser run failed

2.      No transportation lanes passed to the optimizer

3.      No distance and duration calculation possible for stage XXX FO XXX stage 10-XXX

4.      XXX freight unit otc XXX acceptable times for pickup/delivery at XXX at XXX is outside plan horizon the meaning of the error is say for example we have to deliver a good on 7th of march and we are delivering the same at 8th of march that is the reason why the error popped up

5.      None of the transportation demands can be planned

Transportation lanes will combine the transportation zones and we have to assign the transportation lanes to transportation zones

In source zones we have to maintain the shipping point with the prefix sp_ , and in destination zones we have to maintain the customer

Through lanes system will understand through which particular zones we have to travel from source to destination

●      Creation of transportation lanes path:- sap easy access----->logistics------->transportation management---->master data--->transportation network---->transportation zone------>/SCMTMS/TL5-define transportation lanes

Always we have to remember that if you don’t have a proper location we cannot create a transportation lanes between the locations.

●      If we create the lanes between the shipping point and customer location as we can see in the above image we have to create so much of master data and instead of that we can maintain the transportation lanes in between the transportation zones and in those zones we can combine multiple lanes

●      And from the above image we can observe that in the transportation zones we can maintain multiple locations and to create a transportation lane either we require a proper location or transportation zone data

●      In between transportation zones we have to maintain the transportation lanes and with which means of transport we are travelling in those lanes we have to define that particular means of transport also and the same can be seen from the above image

●      We have to assign means of transport and the carrier to the same

●      While we are creating the carrier we can directly assign the transportation zone

▪    Like we can see in the above image we can directly assign the transportation zone while we are creating the career and we have to assign source zone to the carrier

▪    Always we have to remember that when we are creating a career we have to assign the vendor roles first and the we have to assign FLVN01 purchasing, and FLVN00 company code and there after we have to assign the carrier CRM010

▪    if the carrier role was not avaiable we have to goto cross application components-------->sap business partner----->business partner--->basic settings--->business partner roles---> define bp roles

▪    from the above image we can see the path where we have to assign the bp roles and after entering the same we have to goto CRM010 role and we have to change bp view from BPTM00 to BPTM02 (external TM data for carrier)

●      from the above image we can see that bp view as BPTM00 and we have to change the same to BPTM02 (external TM data for carrier)we have to maintain that role

●      if system has planned system will give the above messages as seen in the image

●      if you maintain transportation lanes then only system will plan our freight units

●      system will consider priority and cost is also less for the same that is the reason why in the above example system is considering the Full ton truck

●      because the main theme of sap tm is to minimize our freight cost

❖ load planning settings will be helpful when we do our handling unit, package building. So whenever you want to build or load our truck

●      if we are plannig 100 trucks its very tough to watch all the loads regarding the same and with this 3D load plan we can see the length, height of the package with the help of 3D load plan in sap tm

●      with the help of visual business system will automatically give the dimensions of the truck

●      load planning means how much load we are loading and how much distance it is travelling

●      firstly we have to activate the load plan settings in planning profile and later on we have to work on the resource viewer. 2150 is the standard rule in sap tm load plan settings

❖ Resource viewer activation path:- fiori apps ---->transportation master data---------------->resource viewer

●      We have to select our means of transport then system will display our truck in the resource viewer and the same we can see in the above picture

●      It is not required to activate visual business in s4 systems and when we are working on standalone system it is required

●      In the above image we can see the split deck picture

●      If you want to see the load planning settings in your sap tm cockpit then we have to activate our page layout for the cockpit and remove the standard layout

❖   Page layout creation path:- fiori apps----->transportation-profiles and settings---->page layout for transportation cockpit

❖   The same  path can be seen in the above picture

● If it gets locked by the other user then we have to goto tcode se09

❖   And we have to release the user which he has been locked by him

●      We have to click on new and enter our own page layout for transportation cockpit ● And after entering the same we can the view in the below image

●      From the above image we have to activate explanation load planning

●      From the above picture we can see that we can configure the 4 quadrants in the sap tm cockpit

●      In ewm we have shipping cockpit and in tm we have transportation cockpit

●      From the above image we have to add the quadrants in our cockpit and the same will be reflected in our transportation cockpit

●      We can see the map display in our transportation cockpit and we can map our shipments also

●      This is the picture of a customized transportation cockpit and the same can be seen in the above picture

❖ Yard management is not part of s4 system but, in s4 system we have a concept called yard logistics

●      From the above picture we can see the integration between the EWM, TM, and yard logistics on a single platform all the things which we can do in ewm system the same can be done in yard logistics

●      Carrier selection settings plays an important role in selecting a carrier and if it is one step process system will automatically pick the carrier from step one process VSR_1step

●      Whenever system selects the carrier system will always check for incompatibilites

●      In carrier selection settings we have to maintain a strategy called tsps_Def  and TSPS stands for transportation planning and scheduling

●      While we are doing planning only system has to check whether there are any incompatibilites are present or not then only we have to plan that particular shipment otherwise we have to detach the freight units from the freight order manually and it will assign the same to the compatible truck and we can do the compatible in freight unit and freight order level

●      Dangerous goods check has to complete without errors then only system will plan our shipment documents and we can see the same in the above image

●      Whenever we are working on DIRECT SHIPMENT OPTIONS firstly system will create a freight unit, after system will create a freight order and the system will assign the freight order to a carrier

●      Always we have to remember that carrier selection will happen at freight order level not at freight unit level

●      The carrier selection strategy is CARR_SEL and the service for the same is TOR_CREATE

●      TOR_CREATE is nothing but freight order creation and TOR stands for transportation order

●      freight unit is nothing but our delivery document

●      there is a structure method called service method and strategy in this strategy will assigned to a service---->service is assigned to a method---->method is assigned to a class and then we assign our custom strategy to a service then the service will be assigned to the method.

●      Delivery scheduling concept:- it helps us to determine the delivery dates as per the pickup time, packing time, lead time, loading time, transportation time, transit time here system will consider all these times while delivering the same

o     Example:- today we have created a sales order on 17/03/2021 and the customer will receive the goods on 19/03/2021

1.      for picking 1 day

2.      after packing the goods and load the goods into the truck 1 day

3.      during the transportation from our location to customer location 2 days.

4.      Loading and unloading it will take 1 day

●      So basing on the above example system cannot deliver the goods to the customer on 19/03/2021 and actually it shall be delivered by 22/03/2021 and the customer is expecting the goods to be delivered to him by 19/03/2021 and backward scheduling is always customer requested delivery dates so system will do the backward scheduling first

●      And, whenever system fails to do so then system will do forword scheduling

●      By default system will go for backward scheduling

●      And the same can be seen in the above image

●      Even though If you don’t have a transportation cockpit you can create a freight order and same can be seen in the following Image to do the same we have to goto create road freight order and select our freight order type---->items---->

●      We have to enter our freight unit number starting with the series 41 and we have to assign our means of transport and we have to enter our purchasing organisation and we have to select our carrier.

●      With the help of EDI 210 automatically system will post MIRO document will be posted and once miro document is posted the

information will be passed to the carrier saying that invoice is created

●      Brown field implementation means already implementation was completed on sap platform and we are going to extend for new

dimensional module

●      Green field implementation means fresh implementation to our client business process

●      TM can calculate charges at item level, header level, stage level, product level, package level, container level, handling unit level

●      At header level we will see our pricing procedure and the same can be seen in the below image

●      Whenever we remove action sequence it is called as  header condition and when we don’t see action sequence it is called as header condition and when we see action sequence that is called as item condition and the main difference between header and item condition is header condition is applicable to whole document and whereas in item condition is applicable exclusively only to that particular item only.

TM can be implemented in two releases

Release 1 :-so--->fu--->fo--->tendering--->ecc(shipment)--->shipment cost--->ses---------     spo--->miro--->customer billing Release

2:-so/po/IBD/OBD/------->fu-fo/FB----->tendering------------------------------------------>cha rges/settlement ----->SES------>SPO----->MIRO

●      The difference between these two are we will not create a shipment document in the second release

❖ CHARGES AND SETTLEMENT:-

●      To determine/ see pricing procedure tcode v/08 and the standard pricing procedure is RVAA01. And for MM tcode for the same is M/08. We will see the pricing at header level.

●      V/06 to maintain condition types PR00

●      If we remove action sequence it is called as sequence and the condition type is HB00 there we cant see the action sequence.

●      Freight order is called shipment document in ECC system

●      Templates are predefined document types in SAP TM

●      In condition we have to maintain PR00 to determine price

●      we cannot select a carrier Without optimizer even when you assigned the same carrier to the transportation lanes.

ECC/S4-----------------------------------------------------------------------TM

Condition table                                                                               freight agreement

Access sequence                                                                            calculation sheet

Condition type                                                                                     rate table

Pricing procedure                                                                              charge type

Pricing procedure determination                                               charge category

Condition records                                                                      charge sub category

Scales

Calculation profile

Charges profile

Organisation determination

And always ECC follows                                                   here it is taking top up approach bottom up approach In SD and MM it always starts with bottom up approach.

▪    Error messages while calculating charges:a

The error messages can be seen in the above image

       ▪      We have to assign our freight agreement to our organisation determination

Creation of freight agreement path:- spro--->transportation management--->master data-----> agreements and service products--->define freight agreement types, here we have to select our freight agreement and again in fiori apps we have to create freight agreement and the path is contract management---->create freight agreement

●      The standard freight agreement type is 2000

●      We have to activate multiple parties in freight agreement types so that we can reduce the master data

●      As we can see that we can enter multiple purchase organisations from the above picture

●      We have to maintain our purchase organisation and carrier when we are creating our freight agreement and the same can be seen in the above picture and the same

freight agreement can be used for multiple purchase organisations ● In calculation sheet we have to give our charge type, rate table.

●      Seperately we need not create a calculation sheet we can press add calculation sheet system will automatically create a calculation sheet for us and the same can be seen from the below image

Different charge types in sap TM:-

                      1.    Base price charge (FB00)

●      When we want to move the goods from one location to another location

2.      Stop-off charge

●      When the driver gets exhausted the customer has to pay the charge that is called as stop-off charge

3.      Fuel charge

●      Generally, we have to 1% fuel charge on the base amount

Eg if the base price is 25,000 we have to 1% on that 25,000/-

4.      Detention charge

●      It is a charge where the carrier has arrived to the customer location but the customer hasn’t given the permission to enter into his premises. As a general practice carrier will wait 30 min outside the premises of the customer and from the next min. he will start charging and thereafter the customer has to pay for every minute

5.      ADJ charge

TM has a strong engine called transportation charge calculation management(TCCM) With the help of this tccm tm can calculate the charges at stage level, item level,header level and it can calculate the charge at each and every segment level

In delivery based planning we cannot see the TM status tab in our sales order and after creating a delivery only we can see the tm status bar in the sales order

Creation of freight agreement path:-fiori apps------->contract management------------------->create freight agreement.

●      To check our freight agreement we have to navigate to freight agreement worklist which is in fiori apps

       ▪  From the above image we can see the list of freight agreements

▪    To goto ECC pricing condition types we have to goto tcode v/06 and PR00 is the base price basing on the condition clause system knows that it is a base price and in the same way system comes to know that it is a base price by charge category(FB00) and the category is 004.

       ▪    From the below image we can see charge category and charge subcategory

▪

Charge types creation path:- spro----->transportation management------>basic functions----->charge calculation---->basic settings----->define charge types

●      And image can be seen below

Warehouse billing:- since another member is placing there goods in our warehouse we will charge for the space which we lent to him and that is called as warehouse

billing and TM and EWM communicate frequently

And for warehouse billing we need to activate a check mark in our freight agreement type where it will enable us to do warehouse billing. And, the same can be seen In the below image.

▪    Difference between stop and stop-off/dentation charges is that whenever carrier is waiting outside with the delivarable goods at customer location then in sap tm they will trigger an event saying that we have reached the destination location but the customer havent given the permission to enter into their premises but I have reached to the destination location and as a standard practice the carrier will wait for

30 minutes and after that particular period of time the carrier will charge for the same.

▪    Stop/waiting charge is nothing but whenever we are doing multidrop and multipick there is a time lapse between the loading and unloading of the goods. As a general practice the carrier will wait for 10-15 min in the location and beyond that point if the carrier is ideal so the carrier will charge for the same.

Steps to calculate charges in TM:-

1.        we have to create charge types------------>FB00---basic price

2.        Then we have to go to fiori apps and we have to goto our freight agreement types and their in our freight agreement we have to click on insert to insert our charge types. And the same can be seen in the below image

3.        We have to the status of our freight agreement if it is in in progess state we cant use the freight agreement

4.        To use the same freight agreement we have to click on set status------->released and the same can be seen in the below image

5.        And after the same the status will change to released and the same can be seen in the below image

❖   Calculation profile:- calculation profile will help you to determine your charges based on your header, item and stage data.

❖   Calculation profile creation path:- spro----->transportation management------------------->basic functions---->charge calculation------->basic settings------>define calculation profile and the same can be seen in the below image

❖   Charges profile:- charges profile will help you to determine your calculation profile while triggering charges in the freight order.

Charges profile creation path:- spro----->transportation management-----> basic functions---->charge calculation------->basic settings------>define charges profile. And the same can be seen in the below image

6.      In charges profile we will assign the calculation profile and the same can be seen in the below image

7.      What we have done is firstly we have created calculation profile and in charges profile we have assigned our calculation profile.

8.      After the same we have to assign the charges profile in our TM organisation determination and the Tcode for the same is PPOME. We can see the same in the below image.

▪    Firstly system will look for it is compatable for creating charges or not then it will go to carrier because we have assigned our carrier to our TM purchase organisation and the same can be seen in the below image.

And system will look for calculation sheet in that particular freight agreement and for charge types and now finally system will calculate the charges in TM and finally system shall calculate the charges and that can be seen in the below image

And system will show our agreement and the same can be seen in the below image

Everything is found in our freight agreement

And finally system has completed semi calculation of charges in TM

       ▪    Cost distribution in sap TM:-

Eg:- Whenever we are transporting the goods one is having weight of 100 kgs And the other was having the weight of 50 kgs system shall distribute the charges in in sap TM. And the truck is charging Rs.1000/- for 100 kgs and Rs.500/- for 50 kgs now system shall distribute the charges according to their weight.

FLOW CHART OF CALCULATION OF CHARGES IN SAP TM:-

Freight agreement

Calculation sheet

Charge types(FB00-base price, stop, stop-off etc.,)

Calculation profile

                                                                            Assignment of calculation

Charges profile                     profile to charges profile

Organisational determination in TM

Charges profile

❖   In calculation profile level we can determine our charges at header level, item level, stage level.

❖   To do cost distribution we have to goto our freight order type and in that freight order type we have to enable cost distribution

❖   DEFINE COST DISTRIBUTION PROFILES PATH:- SPRO------->transportation management-------->basic functions-------->cost distribution------>define cost distribution profiles

If we are doing shipper scenerio we have to select distribution level as order/delivery item.

If we are doing LSP & FF we have to select forwording order



 

 


Comments

Popular posts from this blog

Finance All Modules Process Flows

  To- Be Process Flow General Ledger Manual Journal Approval Process Flow Journal Management Invoice Process Flow for Equipment Orders Payment Receiving Through Lock Box Process Flow Collections Overview Process Flow Process Flow to Handle Delinquent Customer Collections Process Flow Payable Invoice (PO Matched) workflow process   Payable Invoice (Non PO Matched) Workflow Process Payment Batch Process  IDR Process Flow To-Be Process Flow Bank Reconciliation - Payment Payables to Fixed Assets Flow Process Flow - Transfer Assets Process Flow –Reclassification (Change Category) Process Flow – Retire Asset Process Flow – Reinstate Asset Process Flow – Impairment Process flow- Depreciate Assets CORP Book to Tax Book TO-Be Process Flow – General Ledger Manual Journal Approval Process Flow   Journal Management  

Finance All Modules Process Flows

  To- Be Process Flow General Ledger Manual Journal Approval Process Flow Journal Management Invoice Process Flow for Equipment Orders Payment Receiving Through Lock Box Process Flow Collections Overview Process Flow Process Flow to Handle Delinquent Customer Collections Process Flow Payable Invoice (PO Matched) workflow process   Payable Invoice (Non PO Matched) Workflow Process Payment Batch Process  IDR Process Flow To-Be Process Flow Bank Reconciliation - Payment Payables to Fixed Assets Flow Process Flow - Transfer Assets Process Flow –Reclassification (Change Category) Process Flow – Retire Asset Process Flow – Reinstate Asset Process Flow – Impairment Process flow- Depreciate Assets CORP Book to Tax Book TO-Be Process Flow – General Ledger Manual Journal Approval Process Flow   Journal Management  

Finance All Modules Process Flows

  To- Be Process Flow General Ledger Manual Journal Approval Process Flow Journal Management Invoice Process Flow for Equipment Orders Payment Receiving Through Lock Box Process Flow Collections Overview Process Flow Process Flow to Handle Delinquent Customer Collections Process Flow Payable Invoice (PO Matched) workflow process   Payable Invoice (Non PO Matched) Workflow Process Payment Batch Process  IDR Process Flow To-Be Process Flow Bank Reconciliation - Payment Payables to Fixed Assets Flow Process Flow - Transfer Assets Process Flow –Reclassification (Change Category) Process Flow – Retire Asset Process Flow – Reinstate Asset Process Flow – Impairment Process flow- Depreciate Assets CORP Book to Tax Book TO-Be Process Flow – General Ledger Manual Journal Approval Process Flow   Journal Management