New Change pointer for CLFMAS

[Former Member]

Hi all,

I have made my own messagetype Z_CLFMAS to contain extra fields that the standard CLFMAS don't have. For this messagetype I would like to have the changepointer to act the same as for the CLFMAS message type - but I wont!?

I first make a new messagetype as a copy of CLFMAS to contain extra fields for the IDOC.

• Through the BD50 I have activated the Z_CLFMAS for changepointers.

• Through BD52 I have added the same fields:

CLASSIFY ABAUSP ATINN

CLASSIFY ABAUSP ATWRT

CLASSIFY ABAUSP ATZHL

...and so on

and my extra field:

MATERIAL MARA MHDHB

The changepointer creates entries in table BDCPV (changepointer table) for the new message type when I change my own field MARA-MHDHB - but not all the others?

(eg. CLASSIFY ABAUSP ATINN).

What can be wrong??

Info: If I add the field MARA-MHDHB to the standard CLFMAS through BD52 everythings work perfectly! - but I would like to have my own developed messagetype ('cause of upgrade...)

Please Please help me!

[christian_wohlfahrt · Accepted solution]

Hi Lars!

Really strange behavior - who can there be a difference?

But you will find out, just debug function module CLASSIFY_WRITE_DOCUMENT, especially the part where CHANGEDOCUMENT_CLOSE is called and the interesting part starts at the end after "if no_change_pointers is initial."

Check out, where the creation of your Z_CLFMAS fails.

Regards,

Christian

[former_member496069]

Please look at,.

http://www.sapfans.com/forums/viewtopic.php?f=21&t=3184

Maruthi

[Former Member]

Apply the SAP note 698527, which has correction to the program LCLVFF30 and will allow to implement custom message types to the CLFMAS (Change pointer)

Thanks

Vijay

[Former Member]

Hello ,

I am trying to apply sap note 0000698527 but getting the error SAP Note 0000698527 not released.Please help.

Thanks

Rajiv

[Former Member]

Hi Christian,

Thanks for your reply.

I found the problem and a solution.

SAP has hardcoded the Message type CLFMAS into the include LCLVFF30 so it will always give changepointer for this messagetype and not for my new one... I have solved it throught the business transaction event (FBIF) 00004005 - there I create my own changepointer instead - it work perfectly.

[Former Member]

Hi Lars,

I am facing a similar problem as you have faced. I have copied CLFMAS02 into my own Basic type and tried to add a few Material master fields to my Basic Type.

Kindly help me out with triggering the Business transaction event, probably FIBF and how to create your own change pointer.

Thanks!

[Former Member]

Here is my code for the FIBF for creation ofthe changepointer:

FUNCTION ZQM_INTERFACE_00004005.

*"----

---

""Local interface:

*" IMPORTING

*" REFERENCE(I_CLASSTYPE) LIKE KLAH-KLART

*" REFERENCE(I_OBJECT) LIKE KSSK-OBJEK

*" REFERENCE(I_ALLOCTYPE) LIKE KSSK-MAFID

*" EXPORTING

*" REFERENCE(E_DONT_WRITE_POINTER) LIKE RCTMV-MARK

*"----

---

data: lt_ale_stru like bdi_chptr occurs 0 with header line.

data: begin of ale_stru occurs 0.

include structure bdi_chptr.

data: end of ale_stru.

data: l_TBDA2 type TBDA2.

*"----

---

select single * into l_TBDA2 from TBDA2

where mestyp = 'ZCLFMAS'.

if sy-subrc = 0.

ale_stru-tabname = 'MARA'.

concatenate I_ALLOCTYPE

I_CLASSTYPE

I_OBJECT into ale_stru-tabkey.

ale_stru-fldname = '00000000'.

ale_stru-CDOBJCL = 'CLASSIF'.

append ale_stru to lt_ale_stru.

call function 'CHANGE_POINTERS_CREATE_DIRECT'

EXPORTING

message_type = 'ZCLFMAS'

TABLES

t_cp_data = lt_ale_stru

EXCEPTIONS

number_range_problems = 1

others = 2.

if sy-subrc > 0.

message a085(b1).

endif.

endif.

ENDFUNCTION.

[Former Member]

Hi Lars,

It looks quite interesting to me. Can you advise me a bit more.

How it is bypassing the sap standard include which has hard coded the message type?

What is the exact purpose of FIBF?

And how you are integrating this function module with message type in FIBF?

Can you just let me know what are the steps that you went through in configuration for this?

regards,

Shylesh