Symptoms

• Active credit cards in IBY_CREDITCARD have a NULL ADDRESSID (also referred to as address_id).
• Credit card-related processing or validation fails because the billing address is not associated with the credit card instrument record.
• The credit card owner's party record exists in the Trading Community Architecture (TCA) tables but the BILL_TO party site use is not linked to the credit card.

Root Cause

Active credit card instrument records in IBY_CREDITCARD were created or migrated without populating the ADDRESSID column. The correct billing address reference should be the PARTY_SITE_USE_ID from HZ_PARTY_SITE_USES for the card owner's active BILL_TO site. A data migration, import, or program error left this column NULL for a subset of active credit cards.

Resolution

Run data_fix.sql. The script creates:

• A backup table (rsi_iby_creditcard_81079) capturing INSTRID and CARD_OWNER_ID for processed records.
• An error table (RSI_DATAFIX_81079_ERRORS) to capture credit cards that could not be updated (e.g., card owner has multiple BILL_TO addresses requiring manual resolution).

The script iterates through active credit cards with a NULL address_id (limited to a configurable batch size). For each card, it updates IBY_CREDITCARD.ADDRESSID by looking up the PARTY_SITE_USE_ID for the card owner's active BILL_TO site from HZ_PARTY_SITE_USES, HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_PARTIES.

If a card owner has more than one active BILL_TO address, the update raises a TOO_MANY_ROWS exception. These records are logged to the error table with an appropriate message. They must be manually resolved by selecting the correct BILL_TO address for the credit card.

The script commits after each successfully processed card. After completion, it prints a summary of successful and failed records and queries the error table. Review the error table and manually correct any remaining records with multiple BILL_TO addresses.

Script Inventory

Key Tables Affected