KEDR: Question on Charateristic derivation.

[Former Member]

Hi all,

I would like to have question on the KEDR: characteristic derivation.

Screenshot: http://docs.google.com/View?id=ddhfd9x3_151hfshbtff

Could anyone explain some of the "elements" available in the KEDR?

1a) Customer Hierarchy

• I read here we can have a lot source fields and target fields, what actually these fields are doing?

1b) Move. What actually move mean?

• Condition tab of move, we have some COPA fields

1c) Table lookup

Should you have any steps by steps or explanation on how to make KEDR, kindly advise me with the reference.

Thanks.

[former_member222075]

Hi

Customer hierachy

In this step a field which represents your customer hiearchy is splitted into different characteristics in CO-PA. In your case the customer hierarchy out of the SD invoice is split into the parts HIE01, HIE02 and HIE03. Each of the fields will contain a part of the original field.

Move

In your case the characteristic Ship-to-party is filled with the customer number if ith the ship-to-party field is empty. So it's not really a move but a field copy.

Table lookup

It looks up the field country out of the table KNA1 and writes it to the characteristic WWCST.

Hope I could help.

Jean Daniel

[Former Member]

Thanks Jean,

I have the following questions in order for me to better understand the basic KEDR:

Question 1:

For the customer hierarchy, I have extracted the mapping, as follows

Source fields:

CO-PA VKORG Sales Organization

CO-PA VTWEG Distribution Channel

CO-PA SPART Division

CO-PA KNDNR Customer

CO-PA HIE03 Customer hierarchy Level 3

CO-PA HIE02 Customer hierarchy Level 2

CO-PA HIE01 Customer hierarchy Level 1

Target fields:

CO-PA HIE03 Customer hierarchy Level 3

CO-PA HIE02 Customer hierarchy Level 2

CO-PA HIE01 Customer hierarchy Level 1

Could you advise how does the system split the customer hierarchy to respective target fields, as there is no settings in the condition tab?

Question 2: KEDR: Move

As per screenshot: http://docs.google.com/View?id=ddhfd9x3_157fsc7v7d7

What does the constant <PAL> mean?

To me the <move> sounds like: if condition:Material Group = 003 (Bulb), constant <PAL> move to target field: COPA-VVSTU_ME (base unit measure)

Thanks in advance.

Kindly advise.

[Former Member]

Hi,

Could anyone advise on my previous question.

Thanks in advance.

Regards.

[Former Member]

Hi,

Sorry, I would like to bump ....

Could anyone advise on my previous question.

Thanks in advance.

Regards.

[Former Member]

Hi,

Question 1:

For the customer hierarchy, I have extracted the mapping, as follows

Source fields:

CO-PA VKORG Sales Organization

CO-PA VTWEG Distribution Channel

CO-PA SPART Division

CO-PA KNDNR Customer

CO-PA HIE03 Customer hierarchy Level 3

CO-PA HIE02 Customer hierarchy Level 2

CO-PA HIE01 Customer hierarchy Level 1

Target fields:

CO-PA HIE03 Customer hierarchy Level 3

CO-PA HIE02 Customer hierarchy Level 2

CO-PA HIE01 Customer hierarchy Level 1

Could you advise how does the system split the customer hierarchy to respective target fields, as there is no settings in the condition tab?

Explanation: is u r requirement is to derive the cutomer heirarchy from Customer and SD objects? then in source fields u can maintain only customer and Sales data.. .u need not maintain Customer Hierarchy levels in Source Fields. It is enough if u define them as target fields. If these hierarchies are interdependent then better to create a separte derivation step.

Question 2: KEDR: Move

As per screenshot: http://docs.google.com/View?id=ddhfd9x3_157fsc7v7d7

What does the constant <PAL> mean?

To me the <move> sounds like: if condition:Material Group = 003 (Bulb), constant <PAL> move to target field: COPA-VVSTU_ME (base unit measure)

Explanation: Move functionality in copa enables to fill a particular field on satisfaction of conditions mentioned.

Regars

Sudhakar Reddy