PIM Change Review Board

1. PIM Change Review Board Jan Berges March 31, 2009

2. Agenda • Project Information • PIM status • Change Request Status • Implementation proposal • Next Change Review Board

3. 1 Project Information

4. 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. 2 PIM status

6. Master Data Status APR 4.1.25 Updates CT007B & SC043 CR2254 & CR2255 MDM SP05.5.42.103 CT007B / SC043

7. 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. CORPCZZ002254(2/2) 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.

9. CORPCZZ002255 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 = 30010000If in MDM the Primary category = software and Part classification = Design or catalogthen the commodity code in APR = 83104010If in MDM the Primary category = services and Part classification = Design or catalog then the commodity code in APR = 70201000

10. 3 Change Request status

11. Status

12. www.alcatel-lucent.com CT007B Improvement www.alcatel-lucent.com

13. CT007B improvement(1/2) 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.. • 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.

14. CT007B improvement(2/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.

15. www.alcatel-lucent.com CORPCZZ002258 www.alcatel-lucent.com

16. CORPCZZ002258 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

17. www.alcatel-lucent.com CORPCZZ002259 www.alcatel-lucent.com

18. CORPCZZ002259 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 lifecycleBusiness 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 flowsCreation of OSI must be done in AMR and do not allow OSI from MDM.

19. 4 Proposal

20. Proposal

21. 5 Next Change Review Board

22. Calendar PIM Change Review Board / Collaboration meeting

23. www.alcatel-lucent.com www.alcatel-lucent.com