Search This Blog

SBL-EAI-04088: Data Transform Error. %1: Invalid Map Function Argument Type: '%2'

Applies to:

Siebel Connector for PeopleSoft Applications - Version: 7.5.2 SIA [15051] and later   [Release: V7 and later ]
Siebel Connector for SAP R/3 - Version: 7.5.2 [15051] to V7   [Release: V7 to ]
Siebel Connector for Oracle Applications - Version: 7.5.2 SIA [15051] to V7   [Release: V7 to ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Professional)
Version: [18353]
Database: Oracle
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Sun Solaris 8

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


Customer was experiencing the following error while processing message received from SAP application through BAPI tRFC Receiver component:

ObjMgrBusServiceLog Error 1 0 2005-08-02 16:11:45 (dtescriptsvc.cpp (103)) SBL-EAI-04088: Data Transform Error. EAIExecuteMap: Invalid Map Function Argument Type: ''

ObjMgrLog Error 1 0 2005-08-02 16:11:45 (stepexec.cpp (768)) SBL-BPR-00162: Error invoking service 'SAP 4x Account - SAP Maps (MO)', method 'Execute' at step '2: Invoke XML'.


The reported error can occur when the DTE business service is not able to determine if the Inputs argument is of type SiebelMessage, MIMEHierarchy or XMLHierarchy. In this scenario, SiebelMessage integration object instance were sending from SAP application to Siebel application but the DTE business service ‘4x Account - SAP Maps (MO)’ was causing the reported errors.

Through further tests, the customer had found the storage type of SiebelMessage input argument for Execute method was set to Property in the DTE business service and this was the cause of the error.


The storage type should be set to Hierarchy instead of Property, as the incoming message was SiebelMessage integration object instance. After changing the storage type from Property to Hierarchy in Siebel Tools and compiling the DTE business service, the reported errors could be resolved.

No comments:

Post a Comment