Generating change pointers for custom master data

[Former Member]

Hello,

I'm trying to expand our ALE set-up to encompass our custom master data tables but am having difficulty getting change pointers generated for ALE. So far I've done the following:-

- created a change document and generated associated

function modules etc

- built custom maintenance transaction that calls the CD

function modules

- created a custom IDoc/message type for the data and

activated change pointers for the new message type

I've debugged the code and found that whilst the change documents are being generated correctly the code for change pointers decides that no action is necessary (look like the data on TBD62 and the change document is inconsistent).

Nuggets of wisdom gratefully received...

Brett

[christian_wohlfahrt]

Hi Brett,

maybe just one step is missing: transaction BD52 - assign relevant fields to your message type.

I hope, you speak about Z-data (not customer like XD01). Otherwise you can skip first parts and start with own change pointer - they will be created by standard change documents, too.

But your own maintenance transaction will have some other reasons, too.

Regards,

Christian

[Former Member]

Hi Christian,

Thanks for the reply. Yes I am talking about Z-data (I've been using standard message types for GL accounts etc).

Tried BD52 but it doesn't seem to have made any difference. IDo you think it could be the way that I am passing data across to the cahnge document FM ?

Rgds

Brett

[christian_wohlfahrt]

Hi Brett,

you can split your analysis into two parts:

- creation of change documents (CD),

- creation of change pointers (CP).

First to the documents: are they looking all right, are fields like user, transaction code... filled? Is in CDPOS table name, field name table key filled?

If not, you have to look at your CD creation:

- are you using the includes provided by the change document creation transaction? Have a look at a standard filling (e.g. where used FM DEBI_WRITE_DOCUMENT)

- Do you need to fill some more fields? Some header values have to be set, normally xtable ytable with old / new values will trigger correct handling of fields.

When CDs are correct, try a test with function module CHANGE_POINTERS_CREATE. You can fill in CD and rest of standard CP creation is executed. Here you can check, if some customizing settings are missing.

- global activation of CP

- activiation of CP for specific message type (client dependent!)

- Relevant field assignment to message type

- flag in data element of DB table (further characteristics): change document is set

That's all to get nice BDCP / BDCPS entries

I'm sure, you will get this running soon.

Regards,

Christian

[Former Member]

Hi Christian,

I've dug a bit deeper and eventually got some change pointers coming through !!! The problem seems to be that I didn't include the pseudo field "KEY" in BD52. I'm still having few issues with the change document population but should be able to sort that.

Thanks for your input.

Brett

[Former Member]

Hi Christian ,

I have a similar problem but with respect to Purchase Orders .

can u plz see what i have missed out in my configuration ..

Here are the steps i followed .

1) created a logical custom message us we81 .

2) created custom idoc using we 30

3) Linked custom mesage and idoc using we 82

4) Activated my custom message using bd50 .

5) Assigned fields to message using bd52 ie

Einkbeleg EKKO waers , EKPO-netpr ..etc

6) Assigned cutom message and custom function module

(z...smd_custommsg) via bd60

7) tried to execute the message using BD21 ..

The problem is thet the tables bdcp / bdcps do not have

any data for EKKO and EKPO after i make any changes to

the PO .But the changes records are available in CDPOS but not in BDCP/S . Is there some missing link ??

DO i have to attach my message to the PO ?? Can u plz tell me waht is wrong ?

Regds

AArti

[christian_wohlfahrt]

Hi Aarti!

Is global activaion of CP missing?

Otherwise, take an existing CDHDR/CDPOS entry as example value, go to SE37 and test with function modules

CHANGE_POINTERS_CREATE_DIRECT

CHANGE_POINTERS_CREATE

They will test the customizing, are pretty small and could easily be debugged -> you see missing settings.

Afterwards you should get change pointers to change documents.

Regards,

Christian

[Former Member]

Thanx Christian ,

I tested with the above FM but all my configurations are in place .

To overcome the situation i will use create_pointers using my custom message in my z..FM . This will populate

the BDCP tables , from here onwards i will process the records as in the standard "MasterIdoc_create_smd_xx"

Thanx for the help ,

Aarti

[Former Member]

hey brett,

look at this weblog i've posted.