# JD Edwards Import Tool: Excel Upload, Z-Files and Orchestrator Options > Source: https://netray.co/erp-help/jd-edwards-import-tool-z-files-excel-upload > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer JD Edwards has no single import button. For small loads use the grid or Excel paste and import features in an application, for large transactional loads use the Z-file interface (load a Z table, run the processor UBE, fix errors), and for repeatable automated loads use Orchestrator or a custom UBE. Choose by volume and by how much validation you need. ## Kind how-to ## System jd-edwards ## Erp Oracle JD Edwards EnterpriseOne ## Module Data Import / Z-files / Orchestrator ## Query jd edwards import tool ## Alternate Queries - jde import data from excel - jde z file upload - jde load data into jde ## Applies To JD Edwards EnterpriseOne 9.x. Available interfaces vary by application and tools release. ## Steps ### Import data with the Z-file method **Items:** - Identify the interface table for the data type, for example the Z-file for address book, journal entries, sales orders or item master, from the Interoperability documentation for your release. - Prepare the source data in the column layout the Z table expects, with required keys and a batch or transaction identifier. - Load the rows into the Z table with a database load, a flat file import, or an application that writes it. - Run the processor UBE for that interface in proof mode first, if available, then in final mode. - Review the processor report and the error messages for rejected records. - Correct the rows in the Z table or source and reprocess only the failed ones. - Verify the result in the target application and reconcile counts and totals before cleaning up the Z table. ## Sections ### Small loads: grid and Excel features **Body:** Many EnterpriseOne forms support exporting a grid to Excel and importing changes back, and pasting rows into a grid. These use the normal form logic and edits, so they are safe, and they are good for hundreds of rows such as price updates or mass maintenance. They are not a data migration tool. They are slow for thousands of rows and depend on the form behaving well for each row, which is why migration projects use Z-files or specialised tools. ### Z-files and the Universal Batch Engine **Body:** The Z-file interface is the standard inbound method for volume. The Z table acts as a staging area; the processor UBE applies the same business function edits used on-screen and then writes the real tables, so data is validated instead of inserted blindly. Run the processor from Batch Versions (a UBE with a version and processing options) and review the output in the Work with Submitted Jobs screen. Always test processing options in a lower environment, since options such as default dates and mode change results. ### Repeatable and automated imports **Body:** For recurring loads, an Orchestrator flow can read a file or call a service and invoke the same forms or business functions. For heavier transformation, an integration tool or ETL job writes the Z table and triggers the processor. Whatever the route, build in an error queue: someone must own rejected rows. Imports that quietly drop errors are the main source of data quality problems after go-live. ## Pitfalls - Inserting directly into production tables with SQL and bypassing edits, creating inconsistent data. - Skipping proof mode and discovering hundreds of rejected rows in final mode. - Wrong data type or length for key fields, such as item numbers with leading zeros being mangled in Excel. - Reprocessing the whole batch after a partial failure and creating duplicates. - Leaving old rows in the Z table so the next run picks them up. ## Ai Angle An assistant can help before and after an import: checking a source spreadsheet against valid codes and existing keys in JDE read-only, and then reconciling what loaded against what was sent. Netray's private AI layer can do this on-prem, with a person approving any write. ## Faq ### How do I import an Excel file into JD Edwards? **Answer:** For small volumes use the grid import or paste feature on the relevant application form. For larger or transactional data, load the rows into the appropriate Z-file table and run its processor UBE, which validates and writes to the real tables. ### What is a Z-file in JD Edwards? **Answer:** A Z-file is a staging or interface table that holds inbound or outbound transaction data. A processor UBE reads it, applies the standard edits and updates the live tables, so you get validation and an error report. ### Can Orchestrator import data? **Answer:** Yes. An orchestration can accept a payload or file and call JDE forms or business functions to create records. It suits repeatable integration; for large batches Z-files are usually faster. ### How do I fix rows rejected during import? **Answer:** Read the processor report or the error messages for the batch, correct the data in the Z table or source, and reprocess only the failed rows, rather than the full batch, to avoid duplicates. ## Search terms jd edwards import tool, jde import from excel, jde z file, jde universal batch engine import, jde data migration tool, jde load data, jde processor ube, jde grid import, jde batch upload, jde interoperability --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json