Debit Memo Creation should determine new pric proce than referenced invoice pricing procedure

[ali-sd]

Dear all,

I have a requirement.
User will create Debit Note with reference to some invoice (due to short amount billed).

Invoice pricing procedure (all manual pricing except taxes); Pricing Proc - ZINVOICE
ZR00 Basic Price
ZPAC Package Fee-Normal
ZF00 Freight charge
ZINS Transit Insurance
JOSG (it is automatic pricing, gets determined based on scenario)
JOCG (it is automatic pricing, gets determined based on scenario)
JOIG (it is automatic pricing, gets determined based on scenario)
JOUG (it is automatic pricing, gets determined based on scenario)

If by mistake, user charged less base price or forgot package fee or forgot freight charge or forgot transit insurance or etc. Then user wants to create Debit note to adjust this.

But when I am creating Debit note with reference to this invoice, all pricing condition types from this invoice are getting copied to debit note. But user does not want all to be copied rather he wants only the forgotten condition type to add.

What I feel the option I have:
Delete the unwanted condition types and add the missed condition type or edit the condition type wherein short amount billed in previous invoice.

But I am expecting the below functionality
New Pricing proc ZDEBIT with the below condition types (same as above except one new - the last one)

ZR00 Basic Price
ZPAC Package Fee-Normal
ZF00 Freight charge
ZINS Transit Insurance
JOSG (it is automatic pricing, gets determined based on scenario)
JOCG (it is automatic pricing, gets determined based on scenario)
JOIG (it is automatic pricing, gets determined based on scenario)
JOUG (it is automatic pricing, gets determined based on scenario)
ZF01 Other charges (added one)

When I create debit note with reference to invoice, ZDEBIT pricing procedure to be determined. However, it is always getting determined ZINVOICE.

OR (Doc Pric Proc - A) - linked with ZINVOICE
F2 (Doc Pric Proc - A) - linked with ZINVOICE
DR (Doc Pric Proc - B) - linked with ZDEBIT

OVKK:
Sales org - 1000
Dist Ch - 10
Div - 01
Customer Pric Proc - 1
Document Pric Proc - A or B

1000-10-01-1-A (ZINVOICE)
1000-10-01-1-B (ZDEBIT)

Why does system determine ZINVOICE pricing procedure when I am creating Debit note (with sales order type DR)?
DR has doc pric proc - B. And B is linked with ZDEBIT

Could someone help me to meet the requirement?
Debit note creation should determined pricing procedure (ZDEBIT) when creating this debit note with reference to invoice (with pric proc ZINVOICE)

[Former Member]

Hi,

simply create a new transfer data routine where VBAK-KALSM is not filled. It will then be determined, not copied.

Please check oss note 14136 for further details where you´ll find a good example.

Regards,

JM.

[VeselinaPeykova]

It is a bit tricky to create a sales order with reference to a billing and not inherit the pricing procedure from the billing document.

I will try to explain with screenshots the two ways to create with reference. It may help you understand the case, but I seriously doubt that it will be easy to train the users and control the process efficiently.

I have a billing document F2 with pricing procedure ZVAAMA. ZCR is my order type.

If I create manually ZCR for the same customer and sales area as in the billing document the determined pricing procedure is ZVCOP1.

A. This is how most users create with reference:

The result is... you probably guessed already:

But we don't want this!

B. Here is how you can cheat the system to do what you want:

Do not use create with reference yet, you will get to this later.

Press Enter, then add the customer number from the billing document and adjust dates if necessary. Take a look at your pricing procedure - now it is the 'right one':

Now it is time to add the reference:

As a result the items are added to the sales order, you preserve the link to the billing document, but you do not inherit the pricing procedure of the billing document.

The problem is that this process is very prone to user mistakes and it will be really difficult to control. The only benefit of this approach is if you cannot afford and development budget.

You mentioned that the user wants to post only the difference. In this case it makes sense to take a look at the standard invoice correction order type (RK), but first double-check with a legal consultant if this is permitted in the country where the process will be used.

If you can afford some development budget it may be better if you use the same pricing procedure but control the adjustment of condition types in the sales order with authorizations or use separate condition types with pricing requirements.