Getting Started with JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange

This chapter discusses:

Click to jump to parent topicJD Edwards EnterpriseOne Data Interface for Electronic Data Interchange Overview

Electronic Data Interchange (EDI) is the paperless, computer to computer exchange of business transactions, such as purchase orders and invoices, in a standard format with standard content. As such, it is an important part of an electronic commerce strategy.

Electronic commerce is a means to extend business processes to include suppliers, customers, and employees in a fully integrated supply chain. It can yield shorter cycle times, more efficient inventory management, and better knowledge sharing throughout the extended enterprise. To see these benefits, you need an integrated enterprise application system that you can extend and customize for the supply chain, while still maintaining enterprise information integrity. The JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange system from Oracle includes features for enterprise resource planning that enable you to use electronic commerce for these business interactions:

EDI is a crucial part of business to business commerce. When computers exchange data using EDI, the data is transmitted in EDI Standard format so that it is recognizable by other systems using the same EDI Standard format. Companies who use EDI have their own translator software package to convert the data from the EDI Standard format to their computer system's format. Companies that exchange EDI data are called trading partners.

As an interface between the JD Edwards EnterpriseOne system data and the translator software, the JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange system (code 47) acts as a staging area for moving data in and out of the application systems. In addition to exchanging EDI data, this data interface can be used for general interoperability and electronic commerce needs where a file based interface meets the business requirements.

Some benefits of using the JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange system are:

Click to jump to parent topicJD Edwards EnterpriseOne Data Interface for Electronic Data Interchange System Integration

The JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange system integrates with these JD Edwards EnterpriseOne systems from Oracle:

We discuss integration considerations in the implementation chapters in this implementation guide. Supplemental information about third-party application integrations is located on the Customer Connection website.

JD Edwards EnterpriseOne Sales Order Management

You can enhance customer service by using the JD Edwards EnterpriseOne Sales Order Management system to create order templates and standing or blanket orders. This system also provides additional customer service support through online displays that give:

JD Edwards EnterpriseOne Procurement

The JD Edwards EnterpriseOne Procurement system accommodates a diverse range of purchasing activities for:

Procurement involves order entry through actual payment for the goods and services that you receive.

JD Edwards EnterpriseOne Inventory Management

The JD Edwards EnterpriseOne Inventory Management system defines discreet inventory items, which enables you to manipulate inventory throughout the supply chain. Item identification and processing characteristics are the basic information elements that are specific to individual items across an entire company. This information can be further defined by facility to provide geographic or market flexibility.

JD Edwards EnterpriseOne Accounts Payable

The JD Edwards EnterpriseOne Accounts Payable system enables you to manage supplier relationships and process invoices and payments.

JD Edwards EnterpriseOne Accounts Receivable

The JD Edwards EnterpriseOne Accounts Receivable system helps you to manage cash flow with the flexibility that you need for effective cash management. You can streamline the day to day functions of the entire accounts receivable department. You can simplify and accelerate the process of applying receipts.

JD Edwards EnterpriseOne Demand Scheduling

You use the JD Edwards EnterpriseOne Demand Scheduling system to manage requirements for shipment and production schedules between customers and suppliers. Firm or planned demand requirements enable you to receive, interpret, validate, or forecast net order information for shipments, and to automatically communicate shipment details to the supplier or customer. The system interprets and receives information using Electronic Data Interchange (EDI) documents that are transmitted from customers to suppliers, and then populates the appropriate demand scheduling tables in order to create records, sales orders, and forecasts. You set up the demand scheduling system to manage all of this information.

Click to jump to parent topicJD Edwards EnterpriseOne Data Interface for Electronic Data Interchange Implementation

This section provides an overview of the steps that are required to implement the JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange 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. A complete list of these resources appears in the preface in About This Documentation with information about where to find the most current version of each.

When determining which electronic software updates (ESUs) to install for JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange, 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 8.96 Software Update Guide.

See Also

About This Documentation Preface

Click to jump to top of pageClick to jump to parent topicGlobal Implementation Steps

This table lists the implementation steps for JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange:

Step

Reference

1. Set up global User-defined codes.

See JD Edwards EnterpriseOne Tools 8.96: Foundation Implementation Guide, User Defined Codes.

2. Set up companies, fiscal date patterns, and business units.

See Setting Up Organizations.

3. Set up next numbers.

See JD Edwards EnterpriseOne Tools 8.96: Foundation Implementation Guide, Setting Up Next Numbers.

4. Set up accounts and the chart of accounts.

See Creating the Chart of Accounts.

5. Set up General Accounting constants.

See Setting Up Constants for General Accounting.

6. Set up multicurrency processing, including currency codes and exchange rates.

7. Set up ledger type rules.

See Setting Up Ledger Type Rules for General Accounting.

8. Enter address book records.

See Entering Address Book Records.

9. Set up inventory information, such as branch/plant constants, default locations and printers, manufacturing and distribution AAIs, and document types.

See Setting Up the Inventory Management System.

10. Set up shop floor calendars.

See Setting Up Shop Floor Management.

11. Set up manufacturing constants.

See Setting Up Manufacturing Constants.

Click to jump to top of pageClick to jump to parent topicData Interface for Electronic Data Interchange Implementation Steps

This table lists the implementation steps for the JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange system:

Step

Reference

1. Set up customer billing instructions.

See Setting Up Customer Billing Instructions.

2. Set up EDI information for a supplier.

See Entering EDI Information for Suppliers.

3. Set up item cross references.

See Maintaining Cross-References.

4. Set up EDI tolerance rules.

See Defining EDI Tolerance Rules.

5. Format flat file data.

See Flat File Data.

6. Verify the report output destination in the .ini file. The .ini file contains a UBE section, UBEDBOutputLocation (the ID for the system value is 79), which the system retrieves if a user specifies an invalid output destination for the EDI text files that the system generated. If you do not specify an .ini setting, the current working directory is the default destination for the output.

See JD Edwards EnterpriseOne 8.96 System Administration Implementation Guide, Understanding the Jde.ini File Settings.