SAP PI PO 接口消息数据库表介绍 BC_MSG_LOG

SAP PI PO 接口消息数据库表介绍 BC_MSG_LOG 

BC_MSG
BC_MSG_AUDIT
BC_MSG_DUP_CHECK
BC_MSG_LOG
BC_MSG_LOG_STAT
BC_MSG_VERSION

BC_MSG
BC_MSG (XI_AF_MSG for PI 7.0x and lower) is the master table for persistence of messages on the Java side, one record per each persistent asynchronous message. BC_MSG keeps the last (or only) message version created via staging – just for asynchronous messages.

BC_MSG_AUDIT
The entries in table BC_MSG_AUDIT (XI_AF_MSG_AUDIT for 7.0x and lower) are the audit log entries visible in the RWB/PIMON. In 7.1 and higher, per default the audit log is only written to database for error messages and the messaging system does not persist the audit logs of successully processed asynchronous messages.

BC_MSG_DUP_CHECK
For each asynchronous message (EO or EOIO) that enters the PI/PO system, an entry is stored in table BC_MSG_DUP_CHECK and kept for 30 days by default to prevent reprocessing of the same message. This is because the retention period of asynchronous messages is usually too short (1 day by default). And if the same message is re-triggered by the sender, it might get duplicated. The entries in table BC_MSG_DUP_CHECK are not relevant with synchronous messages (BE) even if logging is configured. There are just 3 fields in this table – MSG_ID, DIRECTION and PERSISTED_AT – this is not a version related information, just message identifiers.

BC_MSG_LOG and BC_MSG_LOG_STAT
The entries in table BC_MSG_LOG and BC_MSG_LOG_STAT are created in case message logging was configured. These can be created for both asynchronous and synchronous messages.
BC_MSG_LOG – one record per each logged version.
BC_MSG_LOG_STAT keeps a single record per logged message.

BC_MSG_VERSION
The entries in table BC_MSG_VERSION are the message versions created when message is edited with Message Editor or in case staging was configured. Versions created via staging — these are created only for asynchronous messages and are stored in BC_MSG_VERSION and BC_MSG tables. By default, this version is created after Receiver and Interface determination step (stage MS).

Related Notes:

SAP Note 1314974 – Successful asynchronous messages – audit log persistence
SAP Note 1760915 – FAQ: Staging and Logging in PI 7.3 and higher
SAP Note 1826164 - BC_MSG_AUDIT table growth even with low PI message volume
SAP Note 1872758 – How XI/PI messages are persisted in Adapter Engine
SAP Note 1960448 – Configure message retention period per interface
SAP Note 1982452 – Audit Logs for successful synchronous messages with log versions to be persisted/archived if audit log memory cache is disabled
SAP Note 2137688 – New Feature: Background Job to mass cancel messages
SAP Note 2403587 – Default Delete Job does not work even the custom archive job has been deactivated
SAP Note 2518441 – The tablespace PSAPSR3DB of PI system grows quickly
SAP Note 2538365 – How to enable compression on PI/PO system
SAP Note 2771052 – PI global parameter of retention period for logging messages is not taking effect
SAP Note 2778426 – How to decease the size of table BC_MSG_DUP_CHECK
SAP Note 790226 – Messages in AdapterEngine/PCK database do not get archived
SAP Note 872388 – Troubleshooting Archiving and Deletion in PI