Area Process

Area
Other Consumers Data Type Method Object Name Transaction /
URL
Migration
Required
(In Scope?)
Source
System
Extract /
Create
Method
Transform
Method
Load Method Complexi
ty
Data
Volumes
Extract
Previously
Built?
Transform
Previously
Built?
Load
Previously
Built?
Release
Data
Team
Business Reconcil
e (BU)
Notes
TM General e.g. TM, EWM, EM Configuration SAP Configuration Organisational Structure Y N/A N/A N/A
Business Partners (Customer)
Business Partner - Ordering Parties
Business Partner - Shippers
Business Partner - Consignees
Business Partner - Bill To Parties
Business Partner - Payer
Business Partners (Contact Person)
Business Partner - Account Manager (Aurizon Internal Staff)
Business Partner - Ordering Delegate (Customer's)
Business Partner - Accounts Payable Person (Customer's)
Business Partner - Primary Customer Contact (Customer's)
Business Partners (Vendors)
Business Partner - Freight Forwarders
Business Partner - Carriers
Product Master
Product Master - General View
Product Master - Sales View
Location Master
Location Master - Ports
Location Master - Ship to Party
Location Master - Yards
Location Master - Depot
Location Master - Customer Ship From
Location Master - Terminal
Master Custom Upload Tool Transportation Zones N
Transportation Zones Hierarchy
Configuration Means of Transport
Transportation Lanes
Default Routes
Schedules
Departure Rules
Freight Agreements
Forwarding Agreements
Internal Agreements
Resources
Excel upload
From PM
1 Organisational Structure
2 Business Partners
3 Locations
4 Resources
6 Product / Material
7 Dangerous Goods
8 Warehouse Number
9 Storage Type
10 Storage Section
11 Storage Bin
# Type
12 Transportation Unit (Active \ Passive Resource)
13 Resource (Person / Forklift)
14 Containers
15 Road Determation Rules
Set ID
Consist ID
Common Across all the Streams Yes Yes
Customer to Order No
Yes
Managing Yards and Terminals No
Yes
Transportation Planning No Yes
Customer to Order No
Yes
Customer to Order No Yes
Managing Yards and Terminals Yes Yes
Managing Yards and Terminals Yes Yes
Managing Yards and Terminals Yes Yes
Managing Yards and Terminals Yes
Yes
Owners
Configuration Master Data
(Yes / No)
Standard Object
(Yes / No)
Managing Yards and Terminals No
Yes
Managing Yards and Terminals No Yes
Managing Yards and Terminals / Transportation Planing No No
Managing Yards and Terminals Yes
No
Managing Yards and Terminals No
Yes
Managing Yards and Terminals No No
No Customizing
Yes CIF & Custom Upload Tool Ship to Party
No CIF & Custom Upload Tool Locations relevent to delivery of Goods(i.e.
Ports, Ship to Party Address,Yards, depot etc)
No CIF & Custom Upload Tool All Resources from ERP
No CIF & Custom Upload Tool Complete Material Master Data
No CIF & Custom Upload Tool Complete DG Master Data
No Customizing
No Customizing
No Customizing
No Customizing
Standard Object
Enhanced(Yes & No)
Load Tool EWM
No Custom Upload Tool
No CIF & Custom Upload Tool
New Custom Upload Tool
New Table Maintenance(SM30)
No Custom Upload Tool Set id to be recorded at Wagon/loco (TU)
Master data for the Set IDs linking the wagon
IDs
Set ids can be used only once on a single
service
New
Custom Upload Tool
Consist id to be recorded at Wag-on/loco (TU)
Master data for the Consist IDs link-ing the
wagon IDs
Set ids can be used only once on a single
service
Description
Address Fields (Title, First Name/ Last Name, Street, Country,
Region etc.)
Identification type
Source System
Business Partner type
Business Partner Role
S2C 5.2 Customer Master
Product code
Product Description
Unit of Measurement
Net Weight
Gross Weight
Weight Unit
Volume
Volume Unit
Packaging material Type
Packaging Material Group
Allowed Weight
Allowed Volume
Warehouse process type determination Indicator
Product code
Warehouse data
Storage type data
Put away indicator
Storage section
indicator
Storage bin type
UOM
Stock removal
indicator
Road Name
Storage Type
Length
Capacity
Gauge
Storage Bin Type- Road type (Maintenance Road / Yard
Road/Terminal roads)
Wagon/Loco position for the Roads
From Coordinates
To Coordinates
Required Fields
All the Wagons and Locomotives for the planned Train Service for
the yard and their assignment to the respective train Services
should be created automatically through the TM interface. These
would be repre-sented as TUs (S&R activity object) in the EWM
system.
Following details should be captured for Wagons / Locomotives.
Status - Planned - (Standard) -
- Prep. (to allow creation of WTs prior to
Activation) - (GAP)
- Active - (Standard)
- Unavailable - (GAP)
Custom Status requirements based on
Order Status -
(Empty/Loaded/Ordered/Available)
General Status -D(Defective)/M(Maintenance)/R(Restricted)
/K(condemned)/S (Stow)/P(Commissioned) etc.
Wagon/loco Origin Location - (GAP)
Wagon/loco Destination location - (GAP)
*Number of Container Slot on the wagon / Number of Stacks (not at
wagon level depends on geogrphy)
Higher level Wagon (TU) - (GAP)
Position id of the wagon in the train makeup- (Standard)
Sequence of container on the wagon - (GAP)
Position of Wagon on bin (Road) - (GAP)
*Loco/ Wagon Class or Type (an Inventory item) - (GAP)
Loco Type - Diesel/Electric
Loco Status - Working / Hauled
Loco/Wagon ID (Class & Running Number), Reusable IDs - (GAP)
- Wagon id Check digit (not for QLD)logic on the master data re-
S2C 5.2 Customer Master
1
2
3
4
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
A B C D E F G H
End-to-End Business
Process Description
Aurizon, Australia
Business Processes (Process flows, i.e. selecting & sequencing business processes from the Business Building Blocks of the Process Catalog)
Process
Streams
(Level 0)
Aurizon
Process Flow
ID
Process Area
(Level 1)
Process Group
(Level 2)
Business Process
(Level 3)
Process Step
(Level 4)
Activity - optional
(Level 5)
Activity - optional
(Level 6)
Customer to
Order processing
Master Data
OP1 Create/Maintain Customer Master
Data / Business Partner data
Business Partner Roles in SAP TM
Customer
1. Ordering parties
2. Shippers
3. Consignees
4. Bill-to parties
5. Payer
Contact Person
1. Account Manager(Aurizon Internal Staff)
2. Ordering delegate
3. Accounts receivable person(Customer)
4. Primary customer contact(Customer)
Vendors 1. Freight-forwarders
2. Carriers
Customer master record created in ECC and CIF to TM
Customer name
Customer address
Sales Data
Contact Person/s
Contact email/s and phone number/s
Customer master record already exist in TM
Upload/conversion programs for
further upload of TM specific data in
Master data for Cash sale
One time customer codes created in
ECC to be CIFed to TM and used for
Product Master
Product (Material Master) master record created in ECC and CIF to TM
General Product /Material Master
Sales Data of the Product/Material
Location Master
New Location Masters to be created in TM
Assignment of Transshipment Location
Manually
Via Upload/Conversion Program
Transportation Zones
New Transportation Zones to be created in TM
Manually
Via Upload/Conversion Program
Transportation Lane
New Lanes to be created in TM
Manually
Via Upload/Conversion Program
Default Route
New Default Routes with Stages o be created in TM
Manually
Via Upload/Conversion Program
Dangerous Goods Master data
(created in ECC and CIF to TM)
UN Code
Packaging group
DG class
Sub Risk
Hazardous Chemical Code
Packaging type. E.g. Drums
Contract related roles
Create contract
Change/edit contract
Approve/Release contract
Order related roles
Create order
Confirm order
Change/edit order
Resource
All Aurizon Owned Resource master record created in ECC and CIF to TM
Maintenance Details
Down Time
Avalibility Calender
Upload the TM Specific Data through
upload program
Carrier Profile
New Carrier Profile with be created in TM System
Schedule
New & change of schedule will be done in TM system
243595858.xlsx.ms_office page 11 of 24
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
A B C D E F G H
Rail Carrier Schedule
Intermodal train schedule
Coal train schedule
MTP Schedules
SAP TM Wagons Schedule
Shipping Schedule
Cancel order
RICEF / GAPS
243595858.xlsx.ms_office page 12 of 24
1
2
3
4
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
I J K L M N O
\
Activity - Optional
(Level 7)
Activity - Optional
(Level 8)
Manual process (M) /
Systemrelated process
(S) ?
Scoping Requirement ID GAP ID EM Relevance
S
S
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S
S 1.0 Delta
S
S 1.0 Delta
S
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S 1.0 Delta
S 1.0
S 1.0
S 1.0
S 1.0
S 1.0
S 1.0
S 1.0
S 1.0
243595858.xlsx.ms_office page 13 of 24
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
I J K L M N O
S 1.0
S
243595858.xlsx.ms_office page 14 of 24
TM
1 Organisational Structure Settlement to Cash X
4 Business Partners (Staff) Customer to Order X
8 Trade lanes Transportation Planning X
9 Resources Managing Yards and Terminals X
10 Resources Managing Yards and Terminals X
11 Carriers Customer to Order X
12 Carrier Profile Transportation Planning X
13 Default Routes Transportation Planning X
Type #
System Reference
Owners
15 Departure Calendar Transportation Planning X
a. Forwarding Agreements Customer to Order X
b. Freight Agreements Customer to Order X
c. Internal Agreements Customer to Order X
17 Transportation charge calculation sheets Customer to Order X
18 Rate Tables Customer to Order X
19 Calculation bases Customer to Order X
20 Scales Customer to Order X
22 Dangerous Goods Customer to Order X
23 Warehouse Number Managing Yards and Terminals
24 Storage Type Managing Yards and Terminals
25 Storage Section Managing Yards and Terminals
29 Resource (Person / Forklift) Managing Yards and Terminals
30 Road Determation Rules YT & TPS X
31 ATT (Authority to Travel) Transportation Planning X
32 Containers Managing Yards and Terminals X
33 Containers Customer to Order X
34 TRA(Train Route Acceptance ) Transportation Planning X
35 Load table Transportation Planning X
36 Slot Profile Transportation Planning X
37
Master Index Table Settlement to Cash X
38 Customer Hierarchy Customer to Order X
Forwarding Order
EM EWM
N ?
X Y Y
Y
Y Y
N Y
Y Y
Y
Y
System Reference
Upload Conv'n Req. R3 Source
Y
Y
Y
Y
Y
Y
N
Y
X Y Y
X ?
X Y
X Y
X Y Y
X N
X
Y
-
R3) Employee records should be replicated from ERP
LS) RYCS / FMS WA
LS) RYCS / FMS WA
Source
LS) RYCS / FMS WA
?
?
Resources which are replicated from PM will still need to
have extra data entered when the record arrives in FMT.
Additionally security roles will be needed to ensure only
some internal groups can change certain data.
These records won't come from PM and will need to be
created in FMT Directly. Additionally security roles will be
needed to ensure only some internal groups can change
certain data.
In transportation networks, we may have
many permutation and combination of
paths to reach from source location to
destination location. But we use one best
option or most profitable or fastest way to
reach the destination and we will always like
to use this desirable route for given source
and destination; in SAP TM we call it default
route. There may be numerous possible
paths from one source to one destination.
For many businesses, only a few of these
possible paths are reasonable; often,
business experience or careful analysis of the
network leads an organization to know the
most desirable route for a given source and
destination.
Mapping Provided Description or Comment
You define the departure Calendar similarly
to carrier schedules. The difference is that
you can reference the referenced carrier
schedules departure Calendar by selecting
the created departure Calendar stage,
clicking on the Departure Calendar button,
and selecting the Assign option to select a
departure rule of the referenced carrier
schedule. In a master Train schedule, the
stages of the departure Calendar indicate
whether the underlying Train schedules
departure Calendar has changed.
High level grouping of all Yards & Terminals within a
corridor
CD will be providing the structure for this master data
element
CD will be providing the structure for this master data
element
This will be modeled as a resouce in the TM system.
How will these be modelled in the future?
CD will be providing the structure for this master data
element
CD will be providing the structure for this master data
element
Ability to maintain slot profiles on wagons/wagon classes
w.r.t containers
Ability to maintain slot profiles on container/container
classes w.r.t pallets
This master data for Index Table will come from Australian
Statistically Index . This will be used in charge Calculation .
Mapping Provided
S2C 6.3