Appendix

BCON Fields

SAP FS-CD uses fields with prefix BCON to establish and maintain bidirectional traceability between insurance objects in FS-CD and their corresponding business objects in origin systems (IPM, ICS, etc.). These fields enable FS-CD to identify the source system and reference specific business objects when processing financial transactions or communicating back to origin systems.

Field Overview

The FS-CD Adapter maps three BCON fields in the IS_HEADER structure when calling the SAP function module FSCD_INSOBJECT_MAINTAIN to create or update insurance objects:

SAP Field InsuranceObject Property Description

BCON_ID

reference.referenceNo

The unique identifier of the business object in the origin system (policy number, claim number, receivable ID, etc.)

BCON_BUSSYS

originSystem

The origin system identifier (e.g., IPM, ICS, IPM-HM)

BCON_ITEM_ID

tenant

The tenant identifier in multi-tenant deployments

BCON_ID

The unique identifier of the business object in the origin system.

Mapped from: InsuranceObject.reference.referenceNo

Purpose: Establishes a 1:1 link between the FS-CD insurance object and the corresponding business object in the origin system.

The same value is mapped to both BCON_ID and INSOBJECT fields in IS_HEADER.

BCON_BUSSYS

The origin system identifier that created the insurance object.

Mapped from: InsuranceObject.originSystem

Purpose: Identifies which system created the insurance object, enabling FS-CD to route callbacks and notifications to the correct origin system.

Configuration: Set via the fscd-adapter.origin-system.<system-id> configuration property, where <system-id> is the key used in the configuration map.

Examples:

  • IPM - Generic IPM system

  • ICS - Generic ICS system

  • IPM-FN - IPM Funeral Insurance line of business

  • ICS-FN - ICS Funeral Insurance line of business

Data Type: CHAR60 (SAP data element)

Usage in Integration: The PaymentReturnedEventListener extracts this field from FS-CD Info Containers to determine which ICS instance should be notified about payment failures. See Integration Layer for details.

BCON_ITEM_ID

The tenant identifier in multi-tenant deployments.

Mapped from: InsuranceObject.tenant

Purpose: Distinguishes between insurance objects from different tenants within the same origin system in multi-tenant scenarios.

Examples:

  • C - Convista Group

Data Type: CHAR10 (SAP data element)

UI Display: The web application displays the tenant using the domain value texts with the key tenant.<id>:

tenant.C=Convista Group

Usage Patterns

Create Insurance Objects

When creating an insurance object in FS-CD, the adapter populates all three BCON fields to establish the link to the origin system.

Update Insurance Objects

When updating an insurance object, the BCON fields are marked by default as "no data" fields by setting them to "/" to prevent accidental modification, as they are immutable after creation. See Change No Data Fields on Update.

Payment Return Processing

When FS-CD cannot process a payment (e.g., due to invalid bank account details), it publishes a payment-returned event containing the BCON fields.

The PaymentReturnedEventListener extracts the origin system identifier to determine which ICS system to call for reporting the payment failure.

UI Navigation

The web application uses the originSystem field along with the configured insurance-object-ui-path to construct deep links back to the origin system:

fscd-adapter:
  origin-system:
    ipm:
      insurance-object-ui-path: /ui/policy/%s/%s  (1)
1 Pattern with placeholders for tenant and insurance object number

This allows users to navigate from the FS-CD Adapter UI directly to the corresponding policy or claim in the origin system.