This chapter contains the following topics:
Section 1.1, "JD Edwards EnterpriseOne Product Data Management Overview"
Section 1.2, "JD Edwards EnterpriseOne Product Data Management Integrations"
Section 1.3, "JD Edwards EnterpriseOne Product Data Management Implementation"
To understand the critical role that product data management plays in the business, you must understand the ways in which product data affects businesses and how businesses can more efficiently define, track, manage, and maintain product data. The JD Edwards EnterpriseOne Product Data Management system from Oracle enables you to define manufacturing specific item information, bills of materials, ingredients lists, work centers, routings, and processes.
With this application you can:
Enter and review bills of material.
Create work centers, and enter costing and accounting information, use routing instructions, and generate lead times.
Set up shift information and kanbans for repetitive manufacturing.
Enter and review processes, operations, ingredients, co-products, and by-products for process manufacturing.
Set up, review, approve, and print engineering change orders.
Send and receive data from external systems.
Set up start dates, manage overlapping and concurrent operations, and calculate lead times.
The JD Edwards EnterpriseOne Product Data Management system integrates with these JD Edwards EnterpriseOne systems from Oracle:
JD Edwards EnterpriseOne Inventory Management.
JD Edwards EnterpriseOne Requirements Planning.
JD Edwards EnterpriseOne Procurement.
JD Edwards EnterpriseOne Product Costing and Manufacturing Accounting.
JD Edwards EnterpriseOne Sales Order Management.
JD Edwards EnterpriseOne Shop Floor Manufacturing.
JD Edwards EnterpriseOne Capacity Planning.
The JD Edwards EnterpriseOne Product Data Management system works with other JD Edwards EnterpriseOne systems to ensure that all product and manufacturing costs are tracked and transacted. We discuss integration considerations in the implementation chapters in this implementation guide. Supplemental information about third-party application integrations is located on My Oracle Support at https://support.oracle.com/.
Supplies the basic information about each component (or ingredient), such as part number, description, unit of measure, stocking type, issue type code, location, and lot control information.
Activates flash messaging to warn of a pending engineering change order (ECO).
Uses JD Edwards EnterpriseOne Product Data Management information to plan finished goods, the raw material, and purchased parts that are required to manufacture them.
Uses sales orders and forecasts to pass demand for items down through the bills of material to the components.
Uses the bills of material to determine component requirements for planned orders and work orders without a parts list.
Master Production Schedule (MPS) uses the effective dates established by ECOs to plan and introduce products.
Activates flash messaging to warn of a pending ECO.
Uses bills of material for kit processing.
Uses bills of material (BOMs), routing instructions, and work center information to calculate total material, labor, machine, and overhead costs for each primary unit of the parent item.
Uses bills of material during a cost roll-up to determine the material cost for the parent.
Uses bills of material and routing instructions to process work orders and schedule work activity within the plant.
This section provides an overview of the steps that are required to implement the JD Edwards EnterpriseOne Product Data Management system.
In the planning phase of the implementation, take advantage of all JD Edwards EnterpriseOne sources of information, including the installation guides and troubleshooting information.
When determining which electronic software updates (ESUs) to install for JD Edwards EnterpriseOne Product Data Management, use the EnterpriseOne and World Change Assistant. EnterpriseOne and World Change Assistant, a Java-based tool, reduces the time required to search and download ESUs by 75 percent or more and enables you to install multiple ESUs at one time.
See JD Edwards EnterpriseOne Tools Software Updates Guide.
For information about the Oracle Business Accelerator solution for implementation of JD Edwards EnterpriseOne Product Data Management, review the documentation available.
See http://docs.oracle.com/cd/E24705_01/index.htm.
This table lists the suggested global implementation steps for the JD Edwards EnterpriseOne Product Data Management system:
Set up global user-defined code (UDC) tables.
See "Working With User Defined Codes" in the JD Edwards EnterpriseOne Tools System Administration Guide.
Set up fiscal date patterns.
Set up companies.
Set up business units.
Set up next numbers.
Set up accounts, and the chart of accounts. (Optional)
Set up the General Accounting Constants.
Set up multicurrency processing, including currency codes and exchange rates.
See JD Edwards EnterpriseOne Applications Multicurrency Processing Implementation Guide.
Set up ledger type rules. (Optional)
Set up address book records.
Set up default location and printers.
Set up branch/plant constants.
Set up Manufacturing/Distribution automatic accounting instructions (AAIs).
Set up document types.
Set up shop floor calendars.
Set up manufacturing constants.
A business interface is a set of components that implementation teams can use to create an integration between JD Edwards EnterpriseOne and an external system. Business interfaces can include one or more of these business interface components:
Business Services
Real-Time Events
Batch Import and Export Programs
For additional information about business interfaces, and the business objects available for this product area, see these topics in the JD Edwards EnterpriseOne Applications Business Interface Reference Guide: