Download presentation
Presentation is loading. Please wait.
Published byBruce Page Modified over 6 years ago
1
Integration of a new division/entity into an existing JDE environment
Thomas Baertschi August 21, 2018
2
Discussion Context Companies with an existing JDE installation are expanding the JDE footprint to other parts of the organization: Divisional: Some divisions of the organization are on another ERP system, or are on another instance of JDE. Geographical: Other legal entities outside of the U.S. are using another ERP system, or are on another instance of JDE. Strategic: The company made an acquisition.
3
Challenges Business Processes / JDE Configuration Data Conversion
Technical Testing Organizational
4
Integration of new division/entity
Processes / JDE Configuration
5
Processes / JDE Configuration
Are the existing business processes at the new entity/division already configured in JDE or do new modules need to be configured? If a business process is already configured, how similar or different is it between the existing instance and the new instance? If there a business requirement/imperative to define global processes or will the configuration be different by division/entity?
6
Processes / JDE Configuration
Will the introduction of new divisions/entities bring about changes to existing processes/configuration? Transfer Orders Inter-Company Transfer Orders Inter-Company Settlement and reconciliation Centralized Purchasing Will the integration coincide with the centralization of activities and/or the introduction of a shared services center?
7
Integration of new division/entity
Data Conversion
8
Data Conversion Even if the integrated division/entity is on JDE, data transformation will need to take place: Short Account Numbers could overlap Address Book Numbers could overlap Short Item Numbers and/or Item numbers could overlap Etc. As a result of the need for data transformation, data conversion should follow similar approaches and leverage similar tools as a new JDE implementation: Z tables / EDI tables Manual conversion Keep history in legacy system, in a data warehouse or as a data extract
9
Data Conversion The acquiring entity has to determine how much global definition/rationalization should take place: Common Chart of Accounts Supplier Rationalization Customer Rationalization Item Rationalization The more the acquiring entity wants to harmonize, rationalize the data, the more time and effort must be invested upfront in the project.
10
Data Conversion Decision must be made upfront as to how global and standardized the chart of accounts should be, and/or if flexibility should be given to have differences by division or by country. Definition of a new global chart of accounts may impact the existing chart of accounts and as a result, existing transactions and automatic accounting instructions must be analyzed. Need to consider local statutory requirements, if applicable. For example, countries like France and Italy have a government mandated chart of accounts which needs to be maintained in JDE and may require more details.
11
Data Conversion Rationalization of suppliers and customers can be a very cumbersome. In some countries, Postal Codes and/or Tax ids can be leveraged to find common suppliers/customers. Rationalization of items can have impacts in several areas: Bill of Materials Pricing Supplier Catalog Item Restrictions Etc.
12
Integration of new division/entity
Technical
13
Technical Language requirements -> Language packs, special characters and fonts Time zone requirements -> Server date and time stamps Localization requirements -> Localization ESUs
14
Integration of new division/entity
Testing
15
Testing Setup of a new testing environment or use of an existing environment which is also used for production support. Modifications required to support new division/entity made on a production program. Regression testing for existing division/entity is required and needs to be coordinated as part of the project.
16
Integration of new division/entity
Organizational
17
Organizational Having a new division/entity on JDE raises organizational questions. Who will be maintaining UDC tables? Who will be maintaining customers, suppliers, items? The more standardized the data, the more centralized/controlled the process. Clear procedures and organizational responsibilities should be defined upfront.
18
Please complete a session evaluation
Session ID: Contact Info: Tel:
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.