Introduction
Material Master Data is the comprehensive set of materials, services, and products that a company sells, procures, and thus also invoices, and reports. Materials are essential links across the company value chain.
End Vision (to be refined further):
- Centralized and Single golden source of Material Master Data at enterprise level in alignment with master data standards definition and taxonomy.
- Link Material Master to corresponding applicable Products so that at Organizational level we have centralized Product to Material flow.
Challenges (WIP):
| Tactical Current Challenges | Proposed Outcomes | |
|---|---|---|
| 1 | Manual e2e Process flow TAT more than 2 weeks for charge code creation and the same to reflect in other consuming applications. | Operational Efficiency |
| 2 | Delayed invoicing leading to late P&L booking | ProductivityRevenue Recognition |
| 3 | Weak governance - Incomplete visibility on Charge code to Material codes mapping. As well, sometimes Charge codes to Product mapping. | Operational Efficiency |
| 4 | Localization - Each upstream manages their charge codes database and may not be fully mapped to SAP Material codes, there by resulting into duplicates | Operational EfficiencyProductivity |
| 5 | Surcharges and Contractual charges manually applied for the selected products as compared to get charges automatically | Operational Efficiency |
| 6 | when service delivery team executes the service, they need to know what is charge code to be applied and system should be able auto fetch the same based on product to price linkage | Productivity |
| 7 | Lack of control on existing Material codes including Inactivation of the codes | Operational Efficiency |
| 8 | Multiple locations for creation/ amendments/ deactivation | Operational EfficiencyProductivity |
| 9 | Today charge code creation process and product definition process are not in sync - without even defining the service, Charge code requests are getting created. | Operational EfficiencyRevenue Recognition |
Existing Process Flow:
PEX Metrics (TBC)
Current Phase:
- Analysis / Alignment with consumers “in Progress” to capture existing challenges
- Few of the Consumers right point of contacts are to be identified.
- Requested Material data extracts from NFTP team and Pricing team for further analysis as part of Architecture Analysis
- Draft PRFAQ - In Progress
Architecture Definition (WIP):
Product - Maersk Polaris - Confluence
Existing Process in Ocean, LnS
- Charge code creation is initiate by manually raising request whenever there is need for new surcharge for Business.
- LnS - mostly executed by BPOs and for Ocean this could be through BPOs who will align with Centre ocean charge owners
- They need to ensure these charges are in line with authorization to sell or is part of OIPC product offering definition.
- Post raise of request if its shared charge code, an discussion needs to happen on split up and in line with OIPC product specifications. This is done through SNOW ticket.
- Post SNOW ticket for Ocean ADS will update in S4 system. For SAP ECC another team will be executing the same and in parallel capture FACT MDG material code into S4.
- Post creation the same would be extended to all in SAP
- Once extended further manual updates to be carried out in other applications like Kwill, Telicos, CW1
Proposed End State
· This golden source of material/charge codes data will be readily available for consumption across platforms and products, providing data consistency, data linkage, and data accuracy across Maersk.
· The single source of Material Master Data allows for mapping against Maersk’s One Integrated Product Catalogue (OIPC) which can be used for control and governance in LtA/OtC processes.
· The single source of Material Master Data allows for mapping of the same Ocean and LnS services together to enable Integrator Strategy combined value propositions without impacting on Tax/ATR assigned attributes.
· The single source of Material Master Data allows for mapping to approved Core PNL Product Family(ies) to enable accurate PnL reporting impacting FIN teams.
As-Is process