topic Regarding Custom message type configured for triggering change pointers in Application Development and Automation Discussions

Regarding Custom message type configured for triggering change pointers

Former Member — Fri, 27 Jun 2008 04:35:43 GMT

Hi All,

A new message type has been created with reference to Standard message type and change pointers has been created and configured.

When a chaaracteristic is being created or changed both customizing message type as well as standard message type are getting triggered,change pointers are created for both BDCP and BDCPS.

The value of field TABKEY in table BDCP is getting updated for standard CHRMAS message type with correct characterstic values where as for customizing message type the value for TABKEY is not correct which is comming as internal numberic value where as for standard messag type its created with correct values.

All the configuration is done correctly.Would request any one to help me if they have faced any situation like this.

Regards,

Sekhar

Re: Regarding Custom message type configured for triggering change pointers

Former Member — Fri, 27 Jun 2008 11:49:21 GMT

Hi,

if the same characteristic is changed only one entry should exist in BDCP for that change with two corresponding entries in BDCPV. So tabkey can not be different.

I see two possible reasons:

1) change pointers of one messagetype only are migrated to BDCP2 (unlikely . but you may check).

2) You have cahnged different characteristics - some tabkeys are longer than defined in BDCP. Theese long tabkeys are stored internally in a different way. You can retrieve the correct tabkey only by using FM CHANGE_POINTERS_READ (recomneded always).

Kind regard,

Re: Regarding Custom message type configured for triggering change pointers

Former Member — Fri, 27 Jun 2008 11:56:16 GMT

you need to use the bdcpv table to get the change pointers like this...

SELECT cpident tabname tabkey fldname cdobjcl cdobjid cdchgno

cdchgid

INTO TABLE i_bdcpv

FROM bdcpv

WHERE mestype = 'ZSDG' AND

tabname = 'DMARC' AND

cretime >= l_change_date AND

cdchgid IN r_change_type.

Re: Regarding Custom message type configured for triggering change pointers

Former Member — Fri, 27 Jun 2008 12:46:48 GMT

Hi ,

Thanks for your reply.

Actually BDCPV table is not being updated by custom message type. In order to get update of BDCPV table do we need to make any settings or configuration.

Please let me know..

Regards,

Sekhar

Re: Regarding Custom message type configured for triggering change pointers

Former Member — Fri, 27 Jun 2008 12:55:12 GMT

Hi,

Sorry the entries are getting created for both custom msg type and standard msg type, but the tab key values and table name are different.

Regards,

Chandra.