CDHDR entries for chaning LFA1-LNRZA

[Former Member]

Hi,

If I change any of the main fields of vendor data then there is one entry in CDHDR

Even if I change multiple fields, eg I change name, city and bank data

Then there is only entry in CDHDR and multiple entries in CDPOS for LFA1, LFBK tables etc

but when I change the Atlernate Payee field in general data of vendor, there are multiple entries in CDHDR

there as as many entries in CDHDR as many entries are there for WYT3 table for the vendor

This is very puzzling and it effects as we have defined vendor change event and workflow

this causes multiple change events and multiple workflows for single change

so I need to figure out reason why there are multiple entries for change header for KRED change document for WYT3 table.

kindly provide some inputs

thanks

b

[Former Member]

Hi,

I think what you want is to control the trigerring of workflow for few field changes...

You can use workflow start conditions to control the trigerring of workflow... on inserting theses conditions your workflow will trigger only for relevant fields and will ignore the other...

Search this forum... for workflow start conditions...

Regards

Gautam

Edited by: gautam maini on Aug 17, 2011 2:41 PM

[bhakti2]

hi Rick and gautam

thanks for the response

this issue is not related to workflow or workflow start conditions

because even if we completely remove the workflow from the system

still we will see difference in CDHDR entries

if we change any field eg name, city, postal code, bank...... then there is ONE entry in CDHDR for KRED

even for alternate payee field there is one entry for KRED

but only if there are partner functions mantained for a vendor, i.e. there are entries in WYT3 table, then there are multiple entries

the number of entries is equal to number of partner functions for that vendor in WYT3 table

the tabnam and fname in CDPOS is WYT3 and LIFN2.

Is this standard behavior of KRED change object ?

thanks

b

[Former Member]

Hi,

I think this behaviour is standard behaviour ... if partner functions in vendors are vendors themselves and if the change is affecting them as well they will also be changed side by side so new change documents for them as well.. otherwise you wont be able trace changes in the partners change history...

Regards

Gautam

[bhakti2]

Hi Gautam

If the change events are for the partner vendors then object ID should be different for every change document entry and not the same as it is now.

Thank you very much for your input. It provides lot of clarification.

thanks

bhakti

[former_member185167]

Hello,

"this issue is not related to workflow or workflow start conditions"

Then you would get better and quicker answers in a different SDN forum.

regards

Rick Bakker

hanabi technology

[bhakti2]

hey Rick

the issue is not related to workflow or start conditions means that root cause is not workflow but it effects workflow

so this wud be the right forum because this problem will be encountered / analysed by workflow ppl coz change pointers relate to workflow events, dont you think so?

thanks

b

[former_member185167]

Power failures affect workflow too.

[former_member185167]

Hello,

You'll have to look in the workflow and see how it's making the change. It could be doing a separate change for every field. I don't see why it should but it would explain what you're seeing.

regards

R