EBatch

Each EDD is assigned a unique ebatch number as it is loaded into the database. Every record created by the EDD contains that ebatch number and can be traced back to the EDD from which it was loaded.

The Features described below were introduced in v5.3.3

Every time data is committed to the database, the ebatch number will automatically increment. So, it is possible to load an EDD, Create, Commit, and then load another EDD (without closing EDP), Create, Commit - the new EDD will automatically be assigned a new ebatch. It is possible to load multiple EDDs within the same session of EDP. Each time EDDs are committed, the ebatch is automatically incremented so the next "Create" step will use a new ebatch number.

In some situations (such as partial submissions), users want to use the same ebatch number for multiple EDD files. Since the ebatch will only automatically increment on "Commit," open and "Create" multiple files and they will share the same ebatch number. Commit them all to the database in one "Commit" and they will use the same ebatch number.

For example, suppose a submission is received as two separate files. Start EDP, load, and then "Create" the first file. The data will be on the Package tab in EDP and will be assigned an ebatch. Before committing, load the second file into EDP. When "Creating" the second file, it will use the same ebatch as the first file. When both files have been loaded, complete the "Commit" step and commit all of the records to the database (and they will all have the same ebatch number).

Note: In some cases an error occurs during the Commit step and some rows are left in EDP. Even though the ebatch is incremented after the commit, it only affects the next "Create" step (it does not affect any rows that have already been created and failed to commit). For example, suppose an EDD is loaded and the"Create" step is completed. 100 rows are assigned an ebatch number of 998. "Commit" and 95 rows are committed without error, but five rows have an error. If clicking the "Finish" button, the 95 rows will be committed to the database, but the five error rows will remain in the package in EDP. These five rows will still have the original ebatch number of 998. Resolve the error in those five rows, then recommit. Since those five rows still have the original ebatch number, they will correctly be associated with the first 95 rows once they are committed to the database.

In some rare situations, the automatic ebatch increment feature explained above may not be sufficient. A new menu option is available on the "Pro" tab of EDP. Click the small box/arrow at the bottom-right corner of the "Package" group and a popup menu appears. On that popup menu is the "Increment ebatch" button. After clicking that button, the ebatch value will be incremented. The next time "Create" is used, the new ebatch number will be used.

Manually incrementing the ebatch will not be necessary for most users, but occasionally a user may want to manually increment the ebatch number for some reason. For example, suppose you want to process two separate EDDs and commit them at the same time, but different ebatch values are desired. Load and "Create" the first EDD, then click the "Increment ebatch" button. Then load and "Create" the second EDD. All of the data will be in the same package, but the records will have different ebatch numbers. Commit all of the data in one step.