Activity logs are permanent archives of comments, system-generated log entries, or trackers assigned to customers, vendors, users, products, EDI transactions, or system activities.
When necessary, the system administrator can purge activity logs.
Every customer, vendor, and user in the system has an activity log, which contains the trackers assigned to that customer, vendor, or user. Every time you create a tracker, you must assign the tracker to a customer, vendor, or user. The system then stores the tracker in the designated entity's activity log.
The system places copies of trackers in the job queues of users on the trackers' forward lists. When users remove their IDs from tracker forward lists, the system removes the tracker copies from the users' queues, but the trackers continue to reside permanently in their activity logs.
Product activity logs record events that affect the quantities and locations of products in your warehouse. The log is a permanent repository for this information and maintenance is not required. To view a product's activity log, use the Log hot key located on various product related screens, such as Inventory Inquiry, Inventory History Ledger, or Product Location Maintenance. When necessary, you can add additional comments using the Product Activity Log Entry screen.
The Remote Activity Log records all the activity associated with remote transactions, such as BCXML, to and from Eclipse. From the activity log, you can drill down to the transaction details, such as the system-generated order for a customer's order submit transaction.
The System Activity Log records events such as program compiles, e-commerce transfers, file saves, system backups, and record purges. It also logs users dialing into and exiting the system. When necessary, Eclipse Support personnel can create system activity log entries.
The EDI Activity Log contains a summary of transmission connection attempts, actual connections, and transaction information, such as whether a document was sent or received. The log is a permanent repository for this information and maintenance is not required. Use the log to monitor the daily activity of EDI programs.
Use the Remote Activity Log to view all the activity associated with remote XML transactions to and from Eclipse. From the activity log, you can drill down to the transaction details, such as the system-generated order for a customer's order submit transaction.
See Also: