Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Change pointer on custom segment for CREMAS

premal_mistry2
Active Participant
0 Likes
2,764

Hi,

I have extended CREMAS as created a custom segment which would contain LFZA-EMPFK (Vendor as alternate Payee) field from the vendor master (XK01).

The change pointer configuration is done for CREMAS, as well as the linkage of extended idoc and CREMAS is done in WE82 and I have specified the extension in Partner profiles too.

Now the problem is, the Change Pointers are getting created (as I can see it in CDHDR/CDPOS) when I change the content in XK02. But when I see the actual contents of the change pointers in CDPOS, the OLD VALUE and NEW VALUE are coming BLANK and hence through BD21(RBDMIDOC) I am not able to generate idocs based upon those change pointers.

Any help regarding this would be appreciated. Thanks.

Message was edited by: Premal Mistry Guys .... any help on this ??

4 REPLIES 4
Read only

Former Member
0 Likes
1,808

Hi Premal,

You have to add this field (LFZA - EMPFK) in BD52 transaction (Change Document items for message type) under the message type CREMAS.

Steps -

  • Execute the transaction BD52
  • Enter CREMAS as the message type.
  • Click the 'New Entries' button.
  • Enter 'KRED' as object, 'LFZA' as table name and 'EMPFK' as Field Name.
  • Press 'Save' button.

Please do and check, it will resolve your issue.

Thanks & Regards,

Ritwik

Read only

0 Likes
1,808

Hi Ritwik,

Thanks for the reply, I have already done that, in-fact as I said the change-pointers are getting generated (which I suppose is due to correct settings). However, when I see those change pointers in table CDPOS .... the VALUE_OLD & VALUE_NEW fields are showing BLANK.

Further debugging in the idoc creation FM for CREMAS, I found that it is not considering the custom segment that I created for field EMPFK. Hence, the idoc is not getting created .... as all other fields in the standard idoc segments are BLANK.

Read only

0 Likes
1,808

Hi,

It seems to me there is some problems about the field LFZA-EMPFK. Because what I have seen in my system, the Alternate Payee (LFA1-LNRZA) is maintained in Accounting View -> Payment Transaction tab. This field is maintained for 'KRED' object under CREMAS Message Type in BD52 and I have also checked in my system the VALUE_OLD & VALUE_NEW fields are updating correctly for this one. Can you please check once yourself and possibly with the respective Functional guy.

Thanks & Regards,

Ritwik

Read only

0 Likes
1,808

Hi Ritwik,

As I mentioned, I have to refer to LFZA-EMPFK field. The field that I am refering is "Permitted Payee", you can see a button just next to the field that you are referring.

However, this might not be an issue anymore as the change-pointer is generated and I can get the latest data from the table LFZA itself to be sent in the IDOC.

The problem now is that if I have multiple chane-pointer created as a result of the multiple times change in the same field (EMPFK), the program RBDMIDOC is picking only the first change-pointer(the earliest un-processed) and generating an IDOC from it. It should basically generate IDOC for all the un-processed change-pointers.

I debugged the FM MASTERIDOC_CREATE_SMD_CREMAS and came to know that if the table mentioned in the change-pointer(BDCP2-TABNAME) is not from the one's mentioned in the standard segment of CREMAS05(in my case it is LFZA), the system will only generated one idoc from  all the un-processed change-pointers in a single execution. Whereas for all the recognized tables (teh one for which standard segment is there) it will collect all the un-procesed change-pointers.

This is a totally wierd behaviour of SAP....