Additional characteristics (TKEZU) to existing CO-PA postings

[Former Member]

Hello all,

I have a question considering the data transfer from my SD order to CO-PA. I have the requirement of working with the delivery date (VBAK-VDATU) in CO-PA and derive some characteristics from that date (e.g. the day of week).

However, I've some problems of delivering the date to CO-PA, as date fields can not be directly copied from the order to a CO-PA characteristic. Therefore, I am using a custom text characteristic and an entry in table TKEZU to transfer the value to CO-PA.

This procedure works very well for current postings. However, I'd like to perform derivations my existing CO-PA postings for the purpose of comparison. I could use transaction KEND therefore, however, this transaction only re-performs the derivations and not the data transfer from my SD order to the CO-PA posting.

If I post a reversal (transaction KE4S00) and re-post my SD order (KE4T), my extra field VBAK-VDATU of TKEZU is again not delivered. Even more, I get the warning message 'posting is already existing', although there are reversal postin existing.

I'd appreciate any idea how I could enrich my CO-PA postings with the delivery date field.

Thank you all!

Best regards,
Herb

[Former Member · Accepted solution]

Hi,

thank you for your valuable answers! Regarding your posts:

- COPA0001: This also was my first try. I was implementing EXIT_SAPLKEDRCOPA_001; however, when I'm saving the customer order and the characteristics are transferred to CO-PA, the order is not written to the database yet. Thus, I don't see any possibility of getting VDATU from the order. Am I right?

- KE4T: Here I'm facing a very strange phenomenon: After posting the reversal document for an 'old' CO-PA posting without VDATU, I'm transferring the customer orders again to CO-PA with KE4T. However, my field of TKEZU (VBAK-VDATU is not transferred). When I do the same for a CO-PA posting that is 'new' and has already my field filled with VDATU, I also get VDATU transferred to my posting created with KE4T. Do you have any idea what I'm doing wrong? Maybe this behavior depends on the existing CO-PA postings for which I've created the reversals?

Thanks again for your support!

Best regards,

Herb

[waman_shirwaicar · Accepted solution]

Hi Herb,

    Do you have a table lookup on VBAK-VDATU in KEDR ? If so then if VBAK-VDATU is filled with a value then during KE4T it should be transferred to COPA.

regards

Waman

[Former Member · Accepted solution]

Hi Waman,

thanks for your advice - implementing the table lookup in KEDR now enables also the re-assignment of the value in KEND. However, the 'direct' derivation from VA01 is also still working.

Thank you - it helped me a lot!

Best regards,

Herb

[ajaycwa1981]

Hi

KE4T must work... I dont know why you say it does not...

Or as Piet said, you can use exit COPA0001... But in my opinion, it must work...

br, Ajay M

[Former Member]

Hi,

transaction KEND only re-performs the derivations at segments level CE4XXXX table, it will not effect the CE1XXXX table.

Once KEND transaction performed it has an immediate effect on postings to CO-PA and constantly create new profitability segments, while the corresponding "old" profitability segments become obsolete and can no longer receive postings.

Thanks & Regards

Srinu

[Former Member]

I would rather use the COPA0001 user-exit to perform the derivation. Very flexible in there. You can read exactly wat you need, and perform the exact logic you need.