If you’re doing a clean installation, it is highly recommended that before
- Login to the deployment server or a development client, login to JD Edwards DV Environment and start OMW. Follow below steps to access all the .par files in order to restore them to multiple OMW projects.
- Restore the Generic Objects .par files
- Extract the file Q460051.zip:
- Restore the Generic Objects .par files

-
- Restore the Document Repository .par files
- Extract the file Q46DR52.zip:
- Restore the Document Repository .par files

Follow the readFirst file instructions
-
-
- Import the .par file into an OMW Project and import the .zip file into an OMW Web project and check in all objects.
-
-
- Restore the XMapper .par files
- Extract the file Q46XM14.zip:
- Restore the XMapper .par files

-
-
- Import the .par files into OMW projects and check in the objects.
-
-
- Restore the Dynamic Table Access .par files
- Extract the file Q46TU.zip:
- Restore the Dynamic Table Access .par files

-
-
- Import the .par file into an OMW project and check in the objects.
-
-
- Restore the eInvoicing Outbound .par files
- Extract the file Q46EI10.zip and the eInvoicing Automation Outbound 1.0.zi subfolder:
- Restore the eInvoicing Outbound .par files

-
-
- Import the .par files into an OMW project and check in the objects.
-
-
- Extract the Q46SV462.zip, and restore all the .par files in it:

To validate all objects make sure you successfully checked in all the objects.
- Add R09110Z to one of the projects
- Check out R09110Z
- open in design R09110Z
- click properties, advanced, click generate header
- save
- check in
- Open NN/P0002
- Create System Code Q46 next numbering

Create Shared Drive to be accessed via the Orchestrator and or other processes to record the supplier invoices.
- Add R09110Z to one of the projects
- \\…..\eInvoicing\
- \\…..\eInvoicing\Inbound\
- \\…..\eInvoicing\Inbound\New
- \\…..\eInvoicing\Inbound\Processed
- \\…..\eInvoicing\Inbound\Error
- It is recommended that the file share is available in every environment specific to that environment.
- The file share must be accessible via any batch host server in JD Edwards infrastructure.
- On the Deployment Server, Build/Deploy a full Package in DV
In case any errors are encountered reach Steltix Product Team
- Once concluded the package deployment successfully, from JDV920 we recommend to do some checks:
- From web start BV, R9698711, check all tables and fix missing tables or columns
- hint run BV, R98403G, do not overwrite, generate tables in systemcode Q46
- hint run BV, R9698713 to fix missing indexes
- Process Validation
- Download the Tech Check Samples on the Q46SV461 file:

-
- Upload them to the assigned folder \\…..\eInvoicing\Inbound\New
- On the web environment, open PQ46000 and filter for the same path like: \\…..\eInvoicing\Inbound\New

Once you press find you should visualize the uploaded files. Being successful this means JD Edwards will be to access the file share
- As a final test, import the first invoices as a final test. Run RQ46XM01I to import the files.
- Make sure the Processing Options are filled in with the correct paths.
- Run the report, and you should be able to inquire the transaction using PQ46SV00|ZQ460001.

This above step is possible if the installation has been done using Change Assistant. This installation process is not ready by the time the document has been concluded.