Here's an overview of each table in iPayment and a short description of what they contain.
BOY_E0_ADDCCR - Add Credit Card Requests.
Contains requests for the Add Credit Card Link system.
BOY_E0_AUTH_DATAST - Gateway transactions (Auths/Settlements)
Very useful when debugging. Contains information on all transactions performed to the gateway on a document level, with gateway status, amounts etc.
BOY_E0_BPCCL - Old Add Credit Card lnik table [No longer used]
Contains requests used for the Secure Trading add credit card links. When the new generic Add Credit Card system was built, this was replaced.
BOY_E0_BPEXT - Business Partner extended
Contains the 'customer profile' identifier for Authorize.Net and ProPay. Also contains the token of the default credit card for each business partner, if a default has been selected.
BOY_E0_CC_MAPPING - Credit card mapping configuration
Contains information on the credit card mapping between iPayment credit card types and SAP card types. This is also configured on the configuration screen.
BOY_E0_CONFIG - Configuration
Contains data relating to the configuration screen. Most configurations are shared between gateways, but some are exclusive for each gateway.
BOY_E0_CREDITCAEX - Credit card tokens
Very useful when debugging. Contains information on the BP credit cards. Address data, card type, token etc.
BOY_E0_CYB_TOKENR - Cybersource token requests
Contains requests used when adding credit cards on Cybersource.
BOY_E0_DEL_CRE_CAR - Deleted credit cards
Contains the token for deleted credit cards.
BOY_E0_DOC_STATUS - Document status
Sometimes needed for debugging. Contains the status for iPayment status for each document that has been associated with a transaction. The document status shown in the header in SAP is based on this table.
BOY_E0_IMQ - Internal message queue
Contains Internal Messages that have not yet been sent.
BOY_E0_IMR - Internal message recipients
Contains information on which users are configured to receive internal messages.
BOY_E0_LOG - Log table
Contains various logging information from within iPayment. Usually the eventlog is more useful for debugging.
BOY_E0_LOGARCH - Log archive
Contains archived logging data. These entries are moved from the log table to the log archive table when the "Archive log entries" feature inside iPayment is used.
BOY_E0_OTCC - One-Time credit cards
Similar to BOY_E0_CREDITCAEX, except it contains data of one-time cards.
BOY_E0_OTCCL - One-Time credit card links
Contains One-time credit card link requests.
BOY_E0_OTCCP - One-time credit card incoming payments
Contains OTC information for incoming payments using one-time cards.
BOY_E0_OTCINTE - Integration table
Useful when debugging OTC integration issues. Allows the user to do integrations from 3rd party applications to import credit card tokens and authorizations into iPayment for further processing.
BOY_E0_PAYNOWR - Pay-Now link requests
Contains requests for the Pay Now Link system.
BOY_E0_PT_CONFIG - Payment terms configuration
Contains PT configurations. If there's no entry for a given Payment Term that means nothing has been defined, and the default will be used.
BOY_E0_REFUND_ST - Refund status
Contains statuses and details on refund transactions. In case of CFT (direct) refunds, the transaction/document won't be listed in BOY_E0_AUTH_DATAST.
BOY_E0_SCHEDULE - Scheduled actions
Contains all of the scheduled actions configured through the scheduler.
BOY_E0_TEMPLATE - Batch filter templates
Contains batch filter templates, which the batch filter wizards use to save filter configurations.
BOY_E0_TNL - Transaction notification log