topic Re: Adding Hierarchy Node does not create Change Pointer in ARTMAS in Application Development and Automation Discussions

Adding Hierarchy Node does not create Change Pointer in ARTMAS

suwandi_cahyadi — Tue, 17 Dec 2013 03:17:00 GMT

Dear Experts,

We have activated change pointer for ARTMAS, most things works fine.

Only that when we add a new hierarchy node to an article, it does not create a change pointer. We do not see new entry for that in BDCP2. (TABNAME = WRF_MATGRP_SKU)

When we change an existing hierarchy node of an existing article, it creates a change pointer as we see an entry in BDCP2.

Is there any pre-configuration / enhancement that needs to be done so that when we add a new Hierarchy Node, a change pointer is created?

Thank you,

Suwandi C.

Re: Adding Hierarchy Node does not create Change Pointer in ARTMAS

Former Member — Tue, 17 Dec 2013 04:02:11 GMT

Hi,

Go to BD52 transaction, check the field and table name is added as the change document items for ARTMAS.

Rg,Kiran

Re: Adding Hierarchy Node does not create Change Pointer in ARTMAS

suwandi_cahyadi — Tue, 17 Dec 2013 04:31:18 GMT

Hi,

Thank you for the reply.

Yes, I've checked at BD52, the table name and field is listed already.

Object = WRF_MATGRP_OBJ

Table Name = WRF_MATGRP_SKU

Field Name = NODE

The fact that when I change the Hierarchy Node the pointer is created does prove that the field has been listed in BD52, doesn't it? Please enlighten me, it's only when I add a new Hierarchy Node that the change pointer is not created

Thank you,

Suwandi C.

Re: Adding Hierarchy Node does not create Change Pointer in ARTMAS

Former Member — Tue, 17 Dec 2013 04:33:12 GMT

Hi Suwandi,

You may want to activate Message type WMATGRP . I think this is the IDOC which is used to ALE heirarchy nodes.

For more information refer to the link below :

Import/Export Interface of the Article Hierarchy - Master Data - SAP Library

Thanks

Kumaran

Re: Adding Hierarchy Node does not create Change Pointer in ARTMAS

Former Member — Tue, 17 Dec 2013 04:54:33 GMT

Hi,

Yes you are right, Whenever any changes were happens for the node, it will be updated in the BDCP2 table. If you observe the table field BDCP2-CDCHGID is having the indicator!

I = inserted new record

U = updated the existing record.

Go to transaction BD50 , click on new entries and make entry for the message type - activate

Go to transaction BD52 and define the fields for message type

Goto transaction BD51 - inbound function moduel

Goto transaction BD60 - provide the classificaion of the object.

Re: Adding Hierarchy Node does not create Change Pointer in ARTMAS

suwandi_cahyadi — Tue, 17 Dec 2013 05:08:45 GMT

Hi,

Thank you for the reply.

But, I need to send the hierarchy information along in the ARTMAS IDoc. Currently we are using enhancement to populate the hierarchy node information from to table WRF_MATGRP_SKU to the extension fields available in ARTMAS IDoc.

Thank you,

Suwandi C.

Re: Adding Hierarchy Node does not create Change Pointer in ARTMAS

Former Member — Tue, 17 Dec 2013 10:22:30 GMT

By Default ARTMAS idoc is not configured to capture WRF_MATGRP field changes. I think you would need to activate this message type to capture inserts intable WRF_MATGRP_SKU . The confusing part is that changes are getting captured.

May be you could try to activate change pointers WRF_MATGRP idoc and see if it works.

Also, WRF_MATGRP_OBJ_WRITE_DOCUMENT is the update function module which SAP uses to insert data/update data in BDCP2 table.

Re: Adding Hierarchy Node does not create Change Pointer in ARTMAS

suwandi_cahyadi — Wed, 18 Dec 2013 03:29:15 GMT

Hi Kumaran,

When I try to add WRF_MATGRP message type in BD50, I get the following message 'WRF_MATGRP does not exist in EDMSG'. Should a note be implemented first? or this has something to do with the SAP version?

However, the function module you specified WRF_MATGRP_OBJ_WRITE_DOCUMENT is found in my ECC version.

Thank you,

Suwandi C.

Re: Adding Hierarchy Node does not create Change Pointer in ARTMAS

Former Member — Wed, 18 Dec 2013 04:17:02 GMT

Hi,

The IDoc message types are stored in table EDMSG.

Defining the message type can be done from the transaction WE81.

After define in WE81, just go to BD50 and activate the change pointers

Re: Adding Hierarchy Node does not create Change Pointer in ARTMAS

Former Member — Wed, 18 Dec 2013 04:58:24 GMT

Hi Suwandi,

Can you please check message type WMATGRP ? I think this is the message type used to ALE article heirarchy.

Thanks,

Kumaran

Re: Adding Hierarchy Node does not create Change Pointer in ARTMAS

suwandi_cahyadi — Wed, 18 Dec 2013 09:34:46 GMT

Hi Experts,

I've configured and activated for the following 3 types: ARTMAS, WRF_MATGRP, WMATGRP

in BD52 I've configured the following fields:

WRF_MATGRP_OBJ	WRF_MATGRP_SKU	DATE_FROM
WRF_MATGRP_OBJ	WRF_MATGRP_SKU	DATE_TO
WRF_MATGRP_OBJ	WRF_MATGRP_SKU	HIER_ID
WRF_MATGRP_OBJ	WRF_MATGRP_SKU	MAINFLG
WRF_MATGRP_OBJ	WRF_MATGRP_SKU	MATNR
WRF_MATGRP_OBJ	WRF_MATGRP_SKU	NODE
WRF_MATGRP_OBJ	WRF_MATGRP_SKU	STRATEGY

After observing further, I found the following facts:

- Adding a new hierarchy assignment to an article in WMATGRP02 does not create change pointer in BDCP2. But the FM WRF_MATGRP_OBJ_WRITE_DOCUMENT is called with UPD_WRF_MATGRP_SKU = 'I' and YWRF_MATGRP_SKU empty and XWRF_MATGRP_SKU is filled with the new entry

- Changing a hierarchy assignment of an article to a new hierarchy in WMATGRP02 create BDCP2 entry for both 3 message type (ARTMAS, WRF_MATGRP, WMATGRP) calls FM WRF_MATGRP_OBJ_WRITE_DOCUMENT with UPD_WRF_MATGRP_SKU = 'U' and YWRF_MATGRP_SKU has 1 entry and XWRF_MATGRP_SKU has 1 entry with the DATE_TO

field is different with the YWRF_MATGRP_SKU.

- The entries that is created in BDCP2 for WRF_MATGRP_SKU is for the DATE_TO field.

The question is then, why is only DATE_TO fields change pointer created while actualy therer are other fields configured in BD52?

Why is the 'I' insert indicator does not create change pointer?

Thank you,

Suwandi C.

Re: Adding Hierarchy Node does not create Change Pointer in ARTMAS

Former Member — Wed, 18 Dec 2013 14:55:22 GMT

Hi Suwandi,

Please check the below SAP note. It looks relevant to the issue you are facing.

1122598 - MM41/42: Writing change docs only if BW indicator is set

595707 - ALE: Data enhancement during evaluation of change pointers

Regards,

Kumaran

Re: Adding Hierarchy Node does not create Change Pointer in ARTMAS

Former Member — Wed, 29 Oct 2014 11:06:15 GMT

Hi,

I am having the asme requirement and stuck in the same place.

Configurations done;

1. BD52 - WRF_MATGR_SKU added to ARTMAS

2. ARTMAS have its stnd FM assignment in BD60

3. Defined Distribution model with ARTMAS (CLONE) in BD64

4. Defined RFC port & Partner profile.

When the change is made in the article master (art hierarchy node - sales view), ARTMAS change pointers are created, but these change pointers are not creating Idocs.

In case the requirement as described earlier is succefully implemented, then lease share the details.

Re: Adding Hierarchy Node does not create Change Pointer in ARTMAS

suwandi_cahyadi — Fri, 14 Nov 2014 04:50:43 GMT

Dear Nimo,

if i'm not mistaken (this has been quite some time ago) for my case, it was the creating a new hierarchy that didn't create any change pointer, but for changing an existing hierarchy it worked just fine.

For the create hierarchy problem, I created an enhancement to alter the change indicator from 'I' to 'U'.

For your case, in case the change pointer has been created but no IDoc is issued, maybe you want to try to create a custom program to manually process the BDCP entries and generate the IDoc. There are an FM available for that: CHANGE_POINTERS_STATUS_WRITE.

Thank you,

Suwandi C.