Customer specific requirement

[Former Member]

Hello Expert

We have case need to show amont on delivery note for spcific customer only.

Normal customer we don't want to show amount on delivery note.

In order to realize requirement we need speific field on customer master to distinguish normal customer and specific customer.

Do you know appropriate field on the customer master or other way?

We already used customer group and customer ABC  fields.

Best regards,

Ichimura

[deepabalu · Accepted solution]

Hi,

You can check Attribute fields of Customer Master (XD01)

Steps:

Enter TCode - XD03

Enter Customer Details

(Menu) Extras - Additional Data - Attribute Fields.

With this field you can differentiate between Normal and Specific Customers.

Hope this may of any help to you.

Regards,
Deepa

[former_member182378 · Accepted solution]

Deepa, Yoshihito,

I would request for more information about the requirement (question below) before selecting fields "Attribute1" etc.

The reason for this is there fields are in table KNA1.

Yoshihito,

Could there be a scenario where the same customer for a particular sales area be "included"? And the same customer, for a different sales area be "excluded"? (for being printed on the delivery note output)

If yes, then field "Customer group 1" etc.(KNVV-KVGR1)

XD03, Button Sales Area Data, Extra > Additional Data

[Former Member · Accepted solution]

Hi Deepa

Thank you for your information.

It's very helpful.

Hi TW

There is the case sales area is same and sold-to is different.

Some cusotmer request to show net sales amount on the delivery note and some cusotmer don't request to show it.

Basically sold to name, ship-to name company informaion, material and Quantily are required on the delivery note.

Best regards,

Ichimura

[moazzam_ali]

Dear

As suggested by Deepa please go for additional fields and validate this field at the time of output of delivery note. If there are multiple ship to parties for a single sold to party then you have to be careful with partner functions too.

ThankS

[former_member182378]

Moazzam,

Could you please elaborate how multiple SH customers influence this requirement?

If there are multiple ship to parties for a single sold to party then you have to be careful with partner functions too.

[moazzam_ali]

Dear Sir

If there there are more than one ship to party then we must enter pricing group in every ship to party or in logic we will have to for sold to party's group other wise system will not be able to find pricing group in ship to party.

[Former Member]

Dear MoazzaM

Could you explain above part more detail?

We have followoing cases.

Case 1

One sold to party have several ship-to parties and they have specific requirement to show net sales amont on the delivery note. Other customer don't need to show it on the delivery notes.

In that case do we need to use pricing group if we use Attribute Fields?

Case 2

One sold to party have several ship-to parties and some have specific requirement to show net sales amont on the delivery note. Other ship-to paries and other sold to customers don't need to show it on the delivery notes.

In that case do we need to use pricing group?

Best regards,

Ichimura

[former_member182378]

Yoshihito,

It is simple!

The customer (be it Sold to party or Ship to party) for which you need the value of net amount (value of condition type) to populate in the delivery note; ONLY for those customers you need to maintain a value in field Attributes (e.g. Attribute 1 etc.)

Path: XD03 > General Data > Extra > Additional Data

Taking an example:

SP 4500

SH S6001

SH S6002

Suppose you want for customer (SH) S6001 to populate in the delivery note, then go to XD03, give S6001,

General Data > Extra > Additional data, in field Attribute 1 = give value

Thus if a delivery is created for S6002, then the value of net amount would not populate printout (output). Because for S6002, the field Attribute 1 = blank

So, from my understanding, in both case 1 and case 2, the field Attribute 1 can be used.

Additional remark - When could field Customer group be used?

If for the same SH e.g. S6001, for some sales areas you want the value to populate in the delivery note and for some sales areas you do not want the value to populate in the delivery note - in that case Customer group field should be used.

[Former Member]

Hi TW

Thank you for your explanation.

We already used customer group and customer group 1 to 5 so we need other fields to set flag as specific requirement.

Best regards,

Ichimura

[moazzam_ali]

Dear

There are many other fields which you can use. These are in general data and Sales area data. Are you looking for field now? As your scenarios has been explained very well by TW. Now if you are not able to find any field then you can check fields in general data. There are separate additional fields for sale are and general data. Please check them.

Thank$

[former_member182378]

Yoshihito,

To understand your requirement in a clearer manner -

1.

Is it that, for some customers; in the delivery note (printout or...) you want to populate the value of condition type?

And for other customer; you donot want to populate (on the output of the delivery) the value of this condition type?

Do that mean, in the pricing procedure there is no different (that condition type should / can be included). Only in the output of that condition type, it should be only for some customers.

2.

So would this be a requirement where you use output determination functionality?

3.

In CMR, you can explore the possible of using fields "Price group" or "Price list"

In Sales area data > Tab Sales

Side comment - As I understand, you need a logic (for customers; for whom value should populate in the delivery note output) to be incorporated in the requirement; in the output procedure which is assigned to the delivery type, for a particular output condition type.

[former_member204407]

Hi,

Go to SD>Basic Function >Pricing>Pricing control>Define and Assign Pricing procedure>Define customer Pricing procedure>

Create new customer pricing procedure(example:S) for specific customers and assign in customer master sales view.

configure pricing procedure based on new combination in OVKK.

Sales area+ document pricing procedure+ customer pricing procedure(S)

when ever you create sales order for specific customer new pricing will be redetermined.

in this way you can distinguish normal customer and specific customer.

Regards,

Krishna.