Sending Contact Data of customer with DEBMAS message type

[Former Member]

Hi there Integrators,

I am working on a test scenario.

Whenever customer contact person list is updated I would like to trigger an Idoc to PI.

In PI the contact list is mapped into CSV file and router further ...

Everytime I am changing customer's 'header' data, like name, a corresponding record is created in BDCP2 table with MESTYPE = DEBMAS and TABNAME = KNA1.

Everytime I am changing contact person list, a corresponding record is created in BDCP2 table with MESTYPE = DEBMAS and TABNAME = KNVK.

The problem is that when in case I create Idoc based on 1st case (KNA1) - only E1KNA1M (header) segment is created in Idoc.

This is causing my mapping program in PI is failed.

So presumably the best option to avoid such errornous messages in PI is to not sending such Idocs with only header data included, but theese which have contact data subsegment (E1KNVKM) included.

How should such filtering be done? I could use user exit or BTE to filter out, but then unprocessed change pointers are still be lingering in BDCP2 table...

How would you suggest to approach this scenario to keep it clean ?

Would appreciate your tips,

Regards,

bob.

[MichalKrawczyk · Accepted solution]

Hi,

>>>>How would you suggest to approach this scenario to keep it clean ?

send all data each time as per my blog - there are ways to do it with debmas too

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/14575

Regards,

Michal Krawczyk

[Former Member · Accepted solution]

Raja Sekhar Reddy T

With your solution SAP is still going to send Idocs and unnecessary communication (SAP - PI) will be triggered, causing dead messages. Thanks anyway.

Michał

Your solution seems perfect for my scenario, thanks a lot!

[rajasekhar_reddy14]

write a condition in receiver determination to flier the same,