Show TOC

Converting Addresses Using Header Mapping and NormalizationLocate this document in the navigation structure

Use

The header mapping is made available in the receiver agreement. It is required in the IDoc adapter, for example, because the IDoc adapter does not know any communication parties.

After header mapping, the adapter must also convert the address to an external protocol.

More information: Receiver Agreement , IDoc Adapter

Features

Interface Overview

Characteristic Value

Name

AF header mapping service

Purpose

Sets or replaces address fields in the message header

Type

Service in the facade com.sap.aii.af.svc.facade

Technical name

com.sap.aii.af.service.headermapping

Certification

Optional

Syntax

Javadoc package com.sap.aii.af.service.headermapping

Header Mapping

The following fields can be specified and replaced for outbound processing:

  • Sender party
  • Sender communication component
  • Receiver party
  • Receiver communication component

The example adapter demonstrates how to use header mapping.

Note

Open CCIInteraction.java and search for the character string CS_HDMAP.

Alternative Identifiers

Alternative identifiers are defined in the communication party.

More information: Communication Party under Alternative Identifiers.

The example adapter demonstrates how to set alternative identifiers.

Note

Open CCIInteraction.java and search for the character string CS_HDNORM.

The two examples show the implementation for the receiver adapter. The header mapping is only contained in the receiver agreement.

Address normalization for a sender adapter looks like this:

Note

Open SPIManagedConnectionFactory.java and search for the character string CS_HDNORM2.