This chapter contains the following topics:
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:
Business to business: Planning, processing, and tracking information across the supply chain.
Business to consumer: Connecting the company with the customers.
Business to employee: Exchanging information and automating key business processes.
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, you can use this data interface 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:
Shorter fulfillment cycle.
Reduced errors.
Increased information integrity through reduced manual data entry.
Reduced clerical work for the manual manipulation of documentation.
Increased competitiveness in the marketplace.
Improved delivery of goods and services.
Decreased time in generating payments and invoices.
Decreased time in recording receipts of payment.
The JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange system integrates with these JD Edwards EnterpriseOne systems from Oracle:
Sales Order Management
Procurement
Inventory Management
Accounts Payable
Accounts Receivable
Demand Scheduling Execution
We discuss integration considerations in the implementation chapters in this implementation guide. Supplemental information about third-party application integrations is located on the Oracle Support website.
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:
Pertinent order, inventory, transportation, and financial information.
Net profitability of a product line when promotions, discounts, and allowances are applied.
The JD Edwards EnterpriseOne Procurement system accommodates a diverse range of purchasing activities for:
Replenishing inventory.
Acquiring materials used to complete projects.
Charging purchased goods and services to specific departments, jobs, or cost centers.
Procurement involves order entry through actual payment for the goods and services that you receive.
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.
The JD Edwards EnterpriseOne Accounts Payable system enables you to manage supplier relationships and process invoices and payments.
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.
You use the JD Edwards EnterpriseOne Demand Scheduling Execution 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 Execution tables to create records, sales orders, and forecasts. You set up the Demand Scheduling Execution system to manage all of this information.
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.
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 simultaneously.
See JD Edwards EnterpriseOne Tools Software Updates Guide.
The implementation steps for JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange:
Set up global user-defined codes.
See "Working with User Defined Codes" in the JD Edwards EnterpriseOne Tools System Administration Guide.
Set up companies, fiscal date patterns, and business units.
Set up next numbers.
Set up accounts and the chart of accounts.
Set up General Accounting constants.
Set up multicurrency processing, including currency codes and exchange rates.
Set up ledger type rules.
Enter address book records. If required, you can also enter global location numbers (GLN) for customers, suppliers, carriers, internal business units, and so on.
Set up inventory information, such as branch/plant constants, default locations and printers, manufacturing and distribution AAIs, and document types.
Set up shop floor calendars.
Set up manufacturing constants.
The implementation steps for the JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange system:
Set up customer billing instructions.
Set up EDI information for a supplier.
Set up item cross references.
Set up EDI tolerance rules.
Format flat file data.
See Flat File Data.
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 Tools System Administration Guide