The BAM_ACTIVITY_EXTENDED table contains context values that are important to the application. Several fields are automatically included, but the table can be extended with additional fields mentioned previously. The following table contains one record for each entry that is recorded by the BAM activity log driver and can be used as a continuation of the BAM_ACTIVITY table.
Field |
Datatype |
Description |
---|---|---|
RecordKey |
Char(32) |
Primary key for this table and foreign key for RecordKey in BAM_ACTIVITY_CONTEXT and BAM_ACTIVITY tables. This value is a GUID, solely used to uniquely identify an activity record. |
Tstamp |
Datetime |
The time at which this activity record was logged, with precision down to the millisecond if the system supports it. This is identical to the tstamp value in the corresponding BAM_ACTIVITY record. |
BAM_tpm_partnername |
Varchar(128) |
Value of the bam_tpm_partnername special register, when available. |
BAM_edi_ackstatus |
Varchar(5) |
Value of the edi_ackstatus register when available. |
BAM_edi_transactionID |
Varchar(128) |
Value of the edi_transactionID register, when available. |
BAM_edi_version |
Varchar(128) |
Value of the edi_version register, when available. |
BAM_edi_type |
Varchar(128) |
Value of the edi_type register, when available. |
Msgsize |
Varchar(128) |
Size of the message in bytes at this point in processing, when applicable. |
Protocol |
Varchar(128) |
Protocol specific information. This is often the name of the protocol of the channel. |
Extension |
Varchar(128) |
Value of the extension register, when available. |
BAM_tpm_partnerid |
int |
Value of the bam_tpm_partnerid special register, when available. |
BAM_tpm_countryname |
Varchar(2) |
Value of the BAM_TPM_COUNTRYNAME register, when available. |
Text |
Varchar(512) |
The text of the BIZERROR message, for message entry records (recordtype = 151), |
iWay Software |