Name = RCRAInfoStateCode Value = (StateID) Name Value Pair, two character RCRAInfo state code. MI Yes Required by both RCRAInfo and the CDX processes. Name = NotificationURI Value = (email address) Name/Value pair, indicating where automatic email notifications should be sent when RCRAInfo processing is complete. No This should be used for Node v1.1 submissions only. Node 2.0 submissions should use the NotificationURI construct in the Submit operation to specify email recipients. Payload Operation Attribute Operation to be performed on the payload. Operation|Module Operation Parameter RCRA-Transactional, Module Parameter HD=Handler CE=CME PM=Permitting* CA=Corrective Action* FA=Financial Assurance* GS=GIS* RU=ReportUniv Delimiter: Pipe (|) Example RCRA-Transactional|HD Yes Required by both the CDX processes and RCRAInfo. There is one payload operation per payload. There may be only one payload per submission Payload XML Document The root element of XML instance file contained in the payload must match the root element in one of the following schemas: RCRA_HazardousWasteCMESubmission_v5.6.xsd RCRA_HazardousWasteHandlerSubmission_v5.6.xsd RCRA_HazardousWastePermitSubmission_v5.6.xsd RCRA_FinancialAssuranceSubmission_v5.6.xsd RCRA_GeographicInformaitonSubmission_v5.6.xsd RCRA_HazardousWasteReportUnivSubmission_v5.6.xsd Yes *These modules support ONLY RCRA-Transactional processing.
Perform an Add/Update transaction for each entity (e.g., Enforcement Actions, Penalties) The record should be added or updated to the database. Make modifications to the data in the source system. Regenerate the record(s) and the records The selected record should be updated with the data modifications. This test is necessary to confirm that the State system is correctly generating/referencing RCRAInfo keys. If this is not being done correctly, the record will be identified as a new record and added to RCRAInfo, rather than updating the existing record Perform a deletion of a parent record in the State system The deleted record should be deleted in RCRAInfo. This test is necessary to confirm that the State source system is not sending delete transactions for cascade deleted children records. Modify data element(s) which RCRAInfo considers to be a primary key (e.g., Evaluation Date). The source State system should identify this as a delete transaction for RCRAInfo, as well as an add transaction for the “new” record. This test case is only necessary if the State source system allows editing of data elements which RCRAInfo considers to be primary keys. Perform an add/update transaction on State data that is associated to EPA owned data The State owned data should be added or updated in RCRAInfo. Errors should not be raised by RCRAInfo referencing IOR issues This test may be necessary only for those States that model cross ownership of data in their source system. Delete a join record in a many to many relationship (e.g. Compliance Schedule) The association between items in the many to many relationship, should be removed but the individual entities should remain in RCRAInfo (e.g., Violations and Enforcement Action) This test is necessary to confirm that the XML documents are being structured properly and placing the delete transaction in the correct level of the data hierarchy in the schema Delete a primary element involved in a many to many relationship (e.g., Enforcement) The primary element should be deleted with the associated join record being cascade deleted by RCRAInfo This test is necessary to confirm that the XML documents are being structured properly and placing the delete transaction in the correct level of the data hierarchy in the schema Perform a full load of data Verify key data points are correctly being loaded into the system It is recommended that prior to initiating a full load of data a snapshot of data is obtained from RCRAInfo, to facilitate data verification. Whether the
Appendix B – RCRAInfo Data Access Services Below is the list of RCRAInfo data access service requests that are available over the Exchange Network and/or REST. Service Parameters EN Query EN Solicit REST GetCADataByHandler handlerId changeDate Yes No Yes GetCADataByState state changeDate No Yes No GetCEDataByHandler handlerId state agency changeDate Yes No Yes GetCEDataByState state changeDate No Yes No GetFADataByHandler handlerId changeDate Yes No Yes GetFADataByState state changeDate No Yes No GetGSDataByHandler handlerId changeDate owner sequenceNumber Yes No Yes GetGSDataByState state changeDate No Yes No GetHDDataByHandler handlerId changeDate state sourceType sequenceNumber Yes No Yes GetHDDataByState state changeDate No Yes No GetPMDataByHandler handlerId changeDate Yes No Yes GetPMDataByState changeDate No Yes No GetHDMaxSequence handlerId sourceType stateId Yes No Yes GetCurrentHandlerByID handlerId changeDate Yes No Yes GetCurrentHandlerByState changeDate No Yes No GetCADataByHandler: This service will retrieve corrective action data for the specified handler id. If a change date is provided, the result will only contain data that has been modified/updated since the change date. If a change date is not provided all data for this handler will be returned.