pim change review board jan berges march 31, 2009
TRANSCRIPT
PIM Change Review Board
Jan Berges
March 31, 2009
Agenda
1. Project Information
2. PIM status
3. Change Request Status
4. Implementation proposal
5. Next Change Review Board
3 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
Project Information1
4 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
Project Information
CT007C – Requirements meeting on Wednesday April 1
Create an interface from SAP-MDM (PR-MDM) to SAP-Blue Planet
Incorporate critical attribute changes that directly impact our ability to feed SAP Blue Planet
Provide a facility to attach BOM information to Logistically Integrated Items (LII)
CT005A – ALMR
Information session on Wednesday April 8, 2009
5 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
PIM status2
6 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
Master Data Status
APR 4.1.25APR 4.1.25 Updates CT007B & SC043Updates CT007B & SC043
CR2254 & CR2255 CR2254 & CR2255
MDM SP05.5.42.103MDM SP05.5.42.103CT007B / SC043 CT007B / SC043
7 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
CORPCZZ002254
(1/2)
Subject:"Where Mastered" and "Origin“ attribute
Description:
APR item update :
If item coming from regular user & and Origin = <empty>,ALC,NOR,ORPand Where Mastered =APR,ENT,APO,ORPThen : Accept update
MDM item update :
If item coming from MDM-APR interface and and Origin = anything and Where Mastered = MDM Then : Accept update
8 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
ORP item creation
If Origin = ORP and Where Mastered = ORPThen : Accept update
MDM new item creation
Where Mastered = MDM and Origin = LUC.
Remember that the origin attribute values ALC, LUC are used in Blue Planet to control the sourcing versus the principle model.
if any PU–APR (item creation) would want to follow the Principle Model, the only way for Blue Planet is to change the origin value to 'LUC‘. which on the other hand will cause conflicts with those rules for items created in APR.
CORPCZZ002254
(2/2)
9 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
Subject:Commodity code for MDM items
Description:Rules only in case the commodity code field in MDM is empty :
If in MDM the Primary category = hardware or other and Part classification = Design or catalog then the commodity code in APR = 30010000
If in MDM the Primary category = software and Part classification = Design or catalogthen the commodity code in APR = 83104010
If in MDM the Primary category = services and Part classification = Design or catalog then the commodity code in APR = 70201000
CORPCZZ002255
10 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
Change Request status3
11 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
Status
Change Document Number
Subject Environment
CT007B improvements
MDM Workflow Improvements between APR and MDM
MDM
CORPCZZ002259 Block OSI (OSS and OSM) from MDM
MDM / APR
CORPCZZ002258 Allow RSB for OEM / MDM items
APR
CORPCZZ002170 Project FM132
Identification of non-tangible items
MDM / APR OpenSee CRB March 10,
2009 and Nov 4, 2008
CORPCZZ002227 ITP Policy: Material Pricing Group
MDM / APR OpenSee CRB March 10,
2009
CORPCZZ002238 Remove Status CI and LA from APR
APR OpenSee CRB March 10,
2009
CORPCZZ002254 New rules between "Where Mastered" and "Origin"
APR
CORPCZZ002255 Commodity code for MDM items
APR
Status
Open
Closed
Closed
Open
Open
12 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
www.alcatel-lucent.comwww.alcatel-lucent.com
CT007B Improvement
13 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
CT007B project went live March 9th, 2009. Part of that go live implemented an EAI interface from APR into MDM. The requirements as drafted were implemented..
1. When APR has a null net weight, the EAI replaces the null with a zero. This is done because of requirements for interfaces other than MDM. When the EAI loads the zero weight, it does not load a unit of weight. When this data is syndicated to MDM, the MDM validations flag the condition of a net weight with a blank unit of weight as an error and locks the record in workflow. The EAI process cannot be changed without causing a large impact to other interface processes. This workflow error expends lots of time and money to resolve manually, including continually looking at individual errors. The request is to have MDM ignore zero weight values with null units of weights on the interface form APR and treat the field like a null value.
CT007B improvement
(1/2)
14 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
2. CT007B requirements specified that reference price should be greater than zero and the validation was built in.
It appears zero is a valid value as a reference price for item types, as LII material types in combination with SLI in APR. When APR syndicates the zero reference price to MDM, the MDM validations flag the condition of a zero reference price as an error and locks the record in workflow.
This workflow error expends lots of time and money to resolve manually, including continually looking at individual errors.
The request is to have MDM allow zero reference prices on materials coming from APR when the “where mastered” equals APR. MDM will continue to disallow zero reference prices on MDM mastered items.
CT007B improvement
(2/2)
15 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
www.alcatel-lucent.comwww.alcatel-lucent.com
CORPCZZ002258
16 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
Subject:Allow RSB for OEM / MDM items
Description:Is the indication that an items is used for regular business or to be used for maintenance phase as
well. Owning and using Business Units have to explicitly specify it via the attribute.
The following business types exist :
Regular Business (RB): Item will be distributed for normal Supply Chain usage. Item will NOT be
distributed for Spare Parts activities.
Spare parts Business (SB): Item will not be distributed for Supply Chain usage. Item will ONLY be
distributed for Spare Parts activities.
Regular & Spare parts Business (RSB): Item will be distributed for normal Supply Chain usage.
Item will also be distributed for Spare Parts activities
OEM/MDM items should have the same rules than for APR/OEM where RSB and RB is allowed
CORPCZZ002258
17 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
www.alcatel-lucent.comwww.alcatel-lucent.com
CORPCZZ002259
18 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
Subject:Block OSI (OSS and OSM) from MDM
Description:Definition :Goods or Services procured to be sold to a customer.Those items are not reusable, not common and can be used only once in customer orders. Those items are non Alcatel-Lucent designed items and have limited lifecycle
Business rules :OSI creation and usage allowed only for Fronting Entities (FE)/ Selling Entities (SeU)OSI creation and management not allowed for PUs/PDs. OSI not allowed to be used in Interhouse Business flows
Creation of OSI must be done in AMR and do not allow OSI from MDM.
CORPCZZ002259
19 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
Proposal4
20 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
Proposal
Change Document Number
Subject Environment
CT007B improvements
MDM Workflow Improvements between APR and MDM
MDM
CORPCZZ002259 Block OSI (OSS and OSM) from MDM
MDM / APR
CORPCZZ002258 Allow RSB for OEM / MDM items
APR
CORPCZZ002170 Project FM132
Identification of non-tangible items
MDM / APR
CORPCZZ002227 ITP Policy: Material Pricing Group
MDM / APR
CORPCZZ002238 Remove Status CI and LA from APR
APR
Open
April 2009
Planning
April 2009
April 2009
April 2009
Open
21 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
Next Change Review Board5
22 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
Calendar PIM Change Review Board / Collaboration meeting
23 | Presentation Title | Month 2009 All Rights Reserved © Alcatel-Lucent 2009, XXXXX
www.alcatel-lucent.comwww.alcatel-lucent.com