TFNRegistry Reporting: Cross Entity Activity Report

Time

Timeframe selected for the report to display.

Control Resp Org

The name of the Resp Org performing the transaction.

If it is not available (e.g. password related transactions), it is set as N/A.

Owner/Acting As Resp Org

The name of the Resp Org that the transaction is being performed for by the Control Resp Org.

Please Note: At the time of the transaction, the Control Resp Org can specify the Resp Org it is Acting As, by setting the ROID parameter.

• If ROID is provided by Control Resp Org, then the Acting As Resp Org is set using the ROID.
• If ROID is not provided, and if resource owner is identified, then the Acting As Resp Org is set using the Resource Owner.
• If ROID is not provided, and the Resource Owner is not identifiable, then set the Acting As Resporg is set as N/A.

ROID Provided

Filter for selecting the transactions where the Acting-As Resp Org is populated (Yes), not populated (No) or All records.

Setting the filter ‘ROID Provided’=Yes, allows the report user to focus on transactions where the Control Resp Org has declared which Resp Org it is Acting As.

Transaction Type

The transactions that can be performed by the Control Resp Org on behalf of the Owner/Acting-As Resp Org. Default = All, but individual transaction types can be selected from the dropdown and displayed on the report.

Also, each Transaction Count (rightmost value) on the report has a tooltip that shows the split up of that Count by Transaction Type.

For Example: When submitting an OCA request, the following APIs are logged: Search and Reserve, OCA with random search, and PR create (per TFN). If we submit an OCA request for 10 TFNs, we will have a transaction count of 10 logged PR create plus one for Search & Reserve and one for a random search; so in total for 10 TFNs, we will have a total of 12 as the transaction count. However, if we submit an OCA request for 100 TFNs, we will have a transaction count of 120 plus an additional count is for bulk as we are invoking bulk API; so in total for 100 TFNs, we will have a total of 121 as the transaction count.

Last Refresh Date/Time

Identifies the date and time the report was last refreshed.