The is R4 E2M AID is located in https://wiki.o-ran-sc.org/display/RICP/E2+Manager+Interface+Design+-+R4+Draft 

Requirements

• Read the Object that the API method Get All NodeB States Request returns.
• After the RIC-247 US (Validation), E2M loops on the target RANs (either all the RANs or the list provided).
• If DB error - error and Exit.
• If the RAN doesn’t exist (This of course occurs only when Client sent list of RANs) – error and continue the loop.
• If RAN isn’t in connected state – continue the loop.
• Here RAN is connected – Read RAN functions (List of objects – ID, Definition & Revision) from DB
• Build Service Query XML Body containing the Functions (See attached for the IE (Information Elements))
• Send RIC SERVICE QUERY message RMR (12060) with the above functions. If error - error and continue the loop
• Call Ran List Handler to update the healthCheckTimesampSent value but don't update Redis.
• At the end of the loop - Call Ran List Handler to update the object of the  List of RANs 

Acceptance

• Test it with 4 RANs - one in Shutdown, One in Disconnect, 2 Connected, each one with different Functions. See 2 RMRs with correct Functions (XML) are sent. See the healthCheckTimestampSent of only these RANs was updated.
• Test it with no E2T - See 2 Logs of RMR Failures.