Jabil. Case Study: How Jabil Circuit Integrated Dassian Contract Flow Down functionality in SAP ERP and SAP SNC.

Transcription

1

2 Case Study: How Jabil Circuit Integrated Dassian Contract Flow Down functionality in SAP ERP and SAP SNC. Rocio Timko and Sanaa Wehse, PhD, ASQ SSBB, PMP Jabil SESSION CODE: SC1712

3 LEARNING POINTS Learn how Jabil enhanced SNC Order Management and Schedule Agreements to fit its Government and Military business requirements. See how Jabil determined Dassian was a best fit for managing Contract Flow Down Information. Hear lessons learned from both a project management and technical perspectives.

4 What We ll Cover Jabil: Who we are Why we chose Dassian How we incorporated Dassian Contract Flow Down into our SAP ERP and SNC Systems Roll-out strategy Benefits and lessons learned from our implementation Wrap-up

5 Jabil Overview Founded in Michigan, 1966 World s Third Largest Electronic Manufacturing Services Provider Over 30 Million Square Feet of Manufacturing Space Over 90 Sites on Four Continents Tenured Management Team Over 180,000 Dedicated Employees

6 Global Operations Enable Localized Manufacturing - Over 90 Sites in 23 Countries ASIA 21M Square Feet China India Israel Japan Malaysia Singapore Taiwan Vietnam AMERICAS 6M Square Feet Brazil Mexico United States EUROPE 4M Square Feet Austria Belgium France Germany Hungary Italy Ireland Netherlands Poland Russia Scotland Ukraine

7 Creating Competitive Advantages for our Customers in Every Link in their Value Chain

8 Global Expertise & Intelligent Supply Chains, Engineered for Growth Automotive Digital Home Enterprise & Infrastructure Industrial & Energy Networking & Telecommunications Printing Point of Sale Storage

9 Ingenuity that Helps Customers Thrive on Disruption Consumer Lifestyles & Wearable Tech Defense & Aerospace Mobility

10 What We ll Cover Jabil: Who we are Why we chose Dassian How we incorporated Dassian Contract Flow Down into our SAP ERP and SNC Systems Roll-out strategy Benefits and lessons learned from our implementation Wrap-up

11 Why Dassian? Functionality Dassian satisfies government contracts mandate to flow specific contract Flow Down data (i.e., DFARS and DPAS rating) throughout the supply chain from the customer to the supplier base. Jabil already had an established relationship with SAP Jabil uses SAP ECC 6.0 Jabil uses SAP SNC 7.0 Dassian is a SAP Software Solution and Technology Partner as well as SAP Channel Partner Dassian has solutions certified by SAP Dassian Functionality is an integrated solution within the SAP ERP System Dassian provided built-in user exits to enable custom integration with other SAP systems like SNC. Dassian provides support for their solutions

12 Dassian Contract Flow Down Solution Enables Compliance with government contracting Flow Down requirements. Defense Priorities and Allocations System regulation (15 CFR Part 700) Purchasing System Contract Clause Flow Down Prime Contract CAS clauses (FAR and FAR ) Facilitates the capturing and reporting of customerdefined contract specific data fields without modifications to SAP. Enables querying of contract data fields and Flow Down pegging history to retrieve data for audit purposes.

13 What We ll Cover Jabil: Who we are Why we chose Dassian How we incorporated Dassian Contract Flow Down into our SAP ERP and SNC Systems Roll-out strategy Benefits and lessons learned from our implementation Wrap-up

14 Contract Flow Down in SAP ERP and SNC Release 1 Flow Down Out of the box in SAP ERP for Discrete Purchase Orders (POs) Release 2 Discrete Purchase Orders (POs) in SNC Release 3 Schedule Agreements (SA) in ERP and in SNC

15 Contract Flow Down Available in ERP

16 SAP Landscape Sandbox Practice client A copy of DEV environment was done prior to setting up the sandbox. All transports and development was done first in SBX Transports (export) Change requests DEV Customizing and development client Configuration and development was replicated in DEV. Transports created in DEV. Transports (import) STG PRD User testing, training and approval Configuration and development moved from DEV to STG via transports. User integration test, training documents, and user approval. Production client Validation and go-live support

17 Setting up ERP for Contract Flow Down functionality Workbench Gold client setup A new sales order type New delivery type were created New sales order output is created Dassian Contract Flow Down configuration Excluded fields, Required fields, Receiving objects, Group Objects, Default fields, Pegging configuration, etc. Contract Flow Down buttons on receiving objects. Development to add Flow Down buttons on Sales Order, delivery, purchase requisition and purchase order Changes to purchase order output form Existing purchase order output is updated to include Contract flow down Change purchase order output process Changed from Print Immediately to Print with time dependency, output is processed within a 10 minutes delay SAP User Exit used to call Dassian function module Global Trade System configuration SAP Security roles setup Contract Flow Down functionality is restricted by site (plant), new SAP security roles are created.

18 Dassian Contract Flow Down Configuration Dassian configuration for sales order type, receiving objects, receiving objects for hard pegging, etc., is a simple task

19 Flow Down Data in Discrete POs Directly in PO ME22- ME23 From MRP MD04/MD05

20 Contract Flow Down Available in ERP Purchase Requisitions Item level Delivery Item level Saler Order Header level Saler Order Item level

21 PO Output update PO output form was updated to list contract Flow Down data at PO item level

22 Purchase Order Contract Flow Down Report Selection parameters This report allows users to run and send their purchasing and Flow Down data via to suppliers setup in SNC, EDI Report Layout Excel Format

23 Phase 2 & 3 Flow Down in SNC

24 Flow Down in SNC Flow Down is created in ECC IDoc For SNC IDoc (ORDER, ORDCHG, DELINS) is sent to PI from there a XML message is generated to SNC Flow Down IDoc segments are mapped in PI and translated in SNC

25 Flow Down in ECC IDoc ORDER, ORDCHG New IDoc Structure Example: TEXT IDs for easy identification of Flow Down data in the IDoc structure

26 Flow Down Indicator in SNC PO Worklist Layout FD indicates to supplier that PO Item contains Flow Down data

27 Flow Down in Order Management in SNC Flow Down data details are listed in Notes, from PO Item Details Flow Down indicator in Notes column in PO Details > PO Item

28 Flow Down in Scheduling Agreement Contract Flow Down configuration change Schedule agreement type needs to be setup

29 Flow Down in ECC IDoc DELINS DELINS IDoc Structure Example: Flow Down in DELINS IDoc is included in standard segment

30 Flow Down in ECC Scheduling Agreements From MRP MD04/MD05 It shows Schedule Line Item

31 Proxy Mapping and Setup

32 PI 7.10 Modifications for Flow Down Data Download modified DELINS IDoc Create enhanced data type for DeliveryScheduleNotification_In

33 PI 7.10 Modifications for Flow Down Data Modified the XSLT map to allow Flow Down Data element to be added under ScheduleLine parent

34 Flow Down in SNC Release Summary FD indicates to supplier that PO Item contains Flow Down data If click on FD it links to a popup screen with Flow Down details

35 Purchase Order Contract Flow Down Report Enhancement Schedule line item is a field in the selection parameters to run the report Schedule Line included in Report Layout and Excel Format

36 What We ll Cover Jabil: Who we are Why we chose Dassian How we incorporated Dassian Contract Flow Down into our SAP ERP and SNC Systems Roll-out strategy Benefits and lessons learned from our implementation Wrap-up

37 Roll-Out Strategy

38 Roll-Out Strategy Leveraged a hybrid Agile/Waterfall implementation approach to rollout 3 separate releases and prioritize backlog items Coordinated activities with site subject matter experts (SMEs) and functional managers for Sales and Distribution, Planning, and Purchasing. Communicated to suppliers upcoming functionality Provided easy to follow self-paced demos and training documentation on our portal ahead of go-live along with follow-up Q&A sessions with SMEs as needed

39 Contract Flow Down in SAP ERP and SNC

40 Common Issues 1. PO output for Print Immediate was not available in Phase 1, Dassian provided a solution in Phase 2 2. Layout in MRP Screen can be a problem if there are already other custom buttons in the bar menu 3. Custom text delimiters added in IDoc segment to identify beginning and end of Flow Down data. 4. Customization needed on SNC side to have Flow Down indicator in Worklist layout, PO order details, and Release Summary 5. Dassian tables not sync when updates happened, issue fixed by Dassian 6. Change text field length in ECC, PI and SNC 7. When passing text for IDoc type DELINS text needs to be passed at the Item level, not at the schedule line item

41 What We ll Cover Jabil: Who we are Why we chose Dassian How we incorporated Dassian Contract Flow Down into our SAP ERP and SNC Systems Roll-out strategy Best Practices and lessons learned from our implementation Wrap-up

42 Best Practices and Lessons Learned By involving the users and providing user friendly functionality we obtained better user buy-in of new functionality By releasing functionality in stages we didn t overwhelm users and showed incremental progress and value add The project team worked closely with Dassian consultants to build up the inhouse competencies during the initial release As the Dassian solution is addressed via a series of user exits in standard SAP transactions, the integration is seamless for the end user A train the trainer approach was utilized, and user training was conducted as a group session. The user feedback from training is that the functionality improved their efficiency and effectiveness in processing flow down, and successfully passing audits

43 Best Practices and Lessons Learned We had access to a Purchasing architect who helped mitigate risk and confirm that the team was on the right track Set-up a scrum pit at the customer s location. This made the following processes easier: requirements gathering, standups, Release and Sprint planning, Demos, and Steering committee meetings. Had to change the site s planning strategy to make sales orders drive demand, or manually peg the PIR to a sales order.

44 Best Practices and Lessons Learned Because the creation of fields and groups are configurable and transportable, it is critical that both the business and IT collaborate closely to set-up the fields and values that flow down. From a timeline perspective, the initial barebones implementation (includes software install, configuration within ERP, minor customization, users authorization set-up, and training, reports creation) required 3 months to deploy with support from Dassian, followed by 2 to 3 additional releases to customize schedule agreements and SNC integration.

45 What We ll Cover Jabil: Who we are Why we chose Dassian How we incorporated Dassian Contract Flow Down into our SAP ERP and SNC Systems Roll-out strategy Benefits and lessons learned from our implementation Key Learnings

46 KEY LEARNINGS Keep communication with key stakeholders open through out the project Prioritize development items and release schedule to align with the business needs Test all possible scenarios for sales orders, purchase orders and scheduling agreements. Provide SME training or training of trainers Ensure clear communication with the Dassian team to validate that you are on the right track and have them help as needed

47 STAY INFORMED Follow the ASUGNews team: Tom Chris Craig

48 THANK YOU FOR PARTICIPATING Please provide feedback on this session by completing a short survey via the event mobile application. SESSION CODE: SC1712 For ongoing education on this area of focus, visit