EM_MERGE_WASTE fails for manifests with NULL MAN_TRACKING_NUMBER #37
Description
When the MAN_TRACKING_NUM column of the staging database is NULL, it cannot be paired with target database records in ETL_EM_EMANIFEST_VW, as NULL is never "equal to" anything (https://github.com/WindsorSolutions/opennode2-java/blob/f51cb5788c32c335ec48f50417a30bfdc2f29e37/node-plugin/node-plugin-rcra-outbound/src/main/assembly/outer/RCRA_REPORTING_5.12-SQL-DDL.sql#L2527)
Since manifests with a NULL MAN_TRACKING_NUM cannot be paired with records in the target database, the WH_EM_EMANIFEST_ID column of ETL_EM_EMANIFEST_VW will also be NULL for that manifest.
The stored procedure EM_MERGE_WASTE fails to attach waste to manifests with a NULL MAN_TRACKING_NUM because the WH_EM_EMANIFEST_ID is also NULL (https://github.com/WindsorSolutions/opennode2-java/blob/f51cb5788c32c335ec48f50417a30bfdc2f29e37/node-plugin/node-plugin-rcra-outbound/src/main/assembly/outer/RCRA_REPORTING_5.12-SQL-DDL.sql#L9441).