SBL-EAI-04065: Target field '%1' does not exist.

Applies to:

Siebel System Software - Version: 7.5.3.15 SIA [16279] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.15 [16279] NLD Fin Svcs
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Red Hat Linux 3.0

This document was previously published as Siebel SR 38-3469112021.
***Checked for relevance on 28-DEC-2010***

Symptoms

Due to changing requirements it was necessary to move some fields from one integration component to another one.
Changes were made on the BC and IC levels (inactivating the old fields, creating the new ones).

During testing the following errors were observed :
[1][0] Fout tijdens het uitvoeren van subproces YAR Synchronous Inbound/Outbound in stap Send Outbound Message. (SBL-BPR-00183) (0x80eb)
[2][1] Doelveld YAR Repayment Duration bestaat niet. (SBL-EAI-04065) (0x818b)
[3][2] Fout bij oproepen van service EAI Data Transformation Engine, methode Execute in stap Convert Country Codes Policy.(SBL-BPR-00162) (0x80d8)
[4] Objectmanagerfout: ([2] Fout bij oproepen van service EAI Data Transformation Engine, methode Execute in stap Convert Country Codes Policy.(SBL-BPR-00162) (0x80d8))
[5] Fout (null) bij oproepmethode "(null)" voor Business Service "(null)"


(translated)

Target field Repayment Duration does not exist. (SBL-EAI-04065)

Cause

The field had been removed from the underlying Integration Component, but had also been marked Inactive in the Administration - Integration > Data Map Editor view. However, in order for the EAI Data Transformation Engine to load the map, it is required that all fields referenced (marked inactive or not) should exist in the Integration Component.

Solution

Please remove the field from the data map as well.

The Validate option in the Administration - Integration > Data Map Editor should highlight this discrepancy between the run-time client data, and the Integration Component defintion. However, it does not report this problem. Change request 12-1LGMFMO has therefore been logged to address this.

References

BUG:10530636 - VALIDATE BUTTON ON ADMIN - INTEGRATION > DATA MAP EDITOR DOES NOT FIND REMOVED INT COMP FIELDS

Applies to:

Siebel Connector for PeopleSoft Applications - Version: 7.5.3 [16157] and later   [Release: V7 and later ]
Siebel Connector for SAP R/3 - Version: 7.5.3 [16157] and later    [Release: V7 and later]
Siebel Connector for Oracle Applications - Version: 7.5.3 [16157] and later    [Release: V7 and later]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Server SP 2
Database Server OS: HP-UX 11.0

This document was previously published as Siebel SR 38-1216451791.
***Checked for relevance on 01-NOV-2010***

Symptoms

the following error was reported in the SAP Process Transaction log, for Workflow Process 'Product - Receive SAP 4x Material (4x IDOC) – DDTE’)', where the EAI Data Mapping Engine was being called :-

Das Zielfeld 'Dimension 1' ist nicht vorhanden.(SBL-EAI-04065)

(English translation)

Target field 'Dimension 1' does not exist.(SBL-EAI-04065)

The customer was able to provide a sample Siebel Message by temporarily amending the Workflow Process to write the message using the ‘EAI XML Write to File’ service. The error could then be re-created with a Workflow Process which read the saved message, and passed this as input to the EAI Data Mapping Engine service.

Cause

Further investigation showed the cause was the SRF not containing the expected Integration Component definitions,

Solution

Re-compiling the objects to the SRF file resolved this.

Regarding the method of transformation, both the decalrative Data Mapper, and eScript Data Mapping are valid approaches. However, using scripting does allow more flexibility, and is required for more complex transformations. See the bookshelf reference Siebel eBusiness Application Integration Volume IV > Data Mapping Using the Siebel Data Mapper > Siebel Data Mapper Overview for further information.