Converting Addresses Using Header Mapping and Normalization 

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.

Features

Interface Overview

Characteristic	Value
Name	AF header mapping service
Purpose	Sets or replaces address fields in the message header
Type	J2EE service
Technical name	com.sap.aii.af.service.headermapping
Certification	Optional
Syntax	See also: JavaDoc (.\index.html) package com.sap.aii.af.service.headermapping

 

Header Mapping

The following fields can be specified and replaced for outbound processing (Receiver Agreement):

·        Sender party

·        Sender service

·        Receiver party

·        Receiver service

The example adapter demonstrates how to use header mapping.

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

Alternative Identifiers

Alternative identifiers are defined in the communication party. See also: Communication Party under Alternative Identifiers.

The example adapter demonstrates how to set alternative identifiers.

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:

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