Binding Error.
Pemmireddy Ram
Ram.Pemmireddy at sms.siemens.com
Thu Nov 30 11:36:06 EST 2000
Hello!
I am having a trouble with one of the workflow in 46C, which works in 30F.
I am hoping one of you must have come across this problem.
Thanks in advance for your help.
Problem: Here is one of the problems I am having with binding.
_WI_Object_Id &TASK&
_Adhoc_Objects
_Attach_Objects
_WI_Group_Id &TASK.SMNOTIFICATIONOBJ.DIVISION&
_Workitem
Customer &CUSTOMER&
Error:
001 I ***** Binding definition: Direction "<==", element _WI_GROUP_ID *****
001 E Reference types 'D' and 'O' are not compatible (expression
'&TASK.SMNOTIF
Longtext:
Reference types 'D' and 'O' are not compatible (expression '')
Message no. W8 109
Diagnosis
The two partners of the value assignment in the binding must have compatible
references.
If an expression or element is created with a
<sapevent:DOCU_LINK/DS:GLOS.3526B0B8AFAB52B9E10000009B38F974> data type
reference to an ABAP Dictionary table field (data type reference "D") and
the other expression or the other element references an object (data type
reference "O"), a value assignment is not possible.
Constants, or expressions, which do not begin with the characters & or % are
regarded as a data type reference to an ABAP Dictionary field.
Procedure
You should use the F4 input help for the binding definition.
You should only select container elements which F4 input help shows as Data
type identical or data typecompatible . Such elements are highlighted with
colors.
Caution: The color legend only gives information about whether the element
or expression can be used after formal checking. You must ensure that the
allocation is correct yourself.
Note: Container element properties.
Element _WI_Group_Id
Release
Name
Description
Reference table
Reference field
Search help
Search help param.
* Object Type
My understanding is,
Specification of a ABAP Dictionary field reference is not mandatory. If no
field reference is specified, the data type is C(255) (upper and lower
case). Specification of an object type is not mandatory either. If no object
type is specified, the container element can be assigned a reference to an
object of any type.
This is how it works in 3.0F.
Thanks
Ram Pemmireddy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20001130/77f4fedf/attachment.htm
More information about the SAP-WUG
mailing list