It can happen that the data in JDE and ISPnext is no longer in sync. Order data or master data may be missing in ISPnext, for example.
What causes this?
A possible cause is problems with the scheduled JDE export jobs. Because the interface sends changes only, ISPnext falls behind as soon as an export has not run or has not arrived.
A subsequent regular export does not resolve that. It contains only the changes that arose afterwards, not the changes that were missed earlier.
What to check
- Check in the API logging whether the recent exports have been imported. See JDE export - checking whether the file has been imported.
- Have your JDE administrator check the scheduled export jobs, so that the cause does not recur.
How to resolve it
To bring the data back in line, a full JDE export of the master data and/or order data concerned is needed. You run those export jobs in JDE yourself. The job then produces a BG_FULL file instead of a BG file.
The procedure for the order data is described in JDE export - exporting order data in full (BG_FULL).
When to raise a ticket
Raise a ticket in the Helpcenter when:
- data is still missing after a full export;
- no BG_FULL file appears in the API logging after you have started the export.
State in the ticket which data this concerns, when you started the export and what you saw in the API logging.
More information
How the connection between JDE and ISPnext works is described in JDE connection - introduction.