Copying Control (Sales Doc to Billing Doc.)

[Former Member]

Hi,

I'm currently having an issue pulling the net price through from a Debit Memo Request to the Billing Document. The items and quantites ect.. are coming through. However the net price appears as zero, even at the Maintain Billing Due List ( VF04) stage before the billing document is generated.

Note: The net value does appear on the Debit Memo Request:)

Any help troubleshooting this or helpful documentation would be greatly appreciated.

<b>Points awarded for helpful answers as always.</b>

Many Thanks,

Philip Johannesen

[Former Member]

Hi Philip .,

Logic for Pricing Procedure:

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.

In SD, the steps to configure Pricing procedure are as under:

Step 1:

Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).

Step 2:

Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.

Step 3:

Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.

Step 4:

a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.

b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.

5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.

It is assumed that document pricing procedure, customer pricing procedure , ... are in place.

REWARD if helpfull

Thanks & Regards

Narayana

[Former Member]

thanks Narayana the document is very useful.

The pricing conditions appear to look ok. However when I try to display the condition type EK01 in the billing document conditions tab, I get the following message: Condition type EK01 is not determined using condition records.

The DMR is created using DP91 and EK01 is derived manually. The pricing procedure for the DMR -> Billing Document has no condition types against the following fields that are coming through blank:

<b>-Gross Value

-Discount Amount

-Rebate Basis

-Net Value for Item

-Net Value 2

-Net Value 3</b>

Do I need to set these up?

Many Thanks,

Philip Johannesen

[Former Member]

Hi,

First check if there is any routine assigned in copy control.

Secondly when you do VF01 for DMR as you said net value is not coming.Check in condition tab page,pricing procedure analysis button,the condition records are getting captured properly.It should be same as in DMR.

Third thing is check pricing type in copy control.

Do revert back

Regards,

Amrish Purohit

[Former Member]

Thanks for the quick response.

I checked the condition tab Amrish and you were right the costs are not coming through. In the DMR both condition types: EK01 & SKTV have come through, but on the Billing Document there totals are zero. I noticed that the Condition Control of EK01 is set to C (Changed Manually) in the DMR but E (Condition value and basis fixed) on the Billing Document.

Could you possibly give me a quick run through of the steps required to configure the pricing conditions properly or some suitable documentation?

Many Thanks,

Philip Johannesen

[Former Member]

On closer inspection I noticed that EK01 is coming through with the correct value. However under EK01 the following values are coming through as zero:

<b>-Gross Value

-Discount Amount

-Rebate Basis

-Net Value for Item

-Net Value 2

-Net Value 3</b>

These have no condition type associated with them. They have values in the DMR but aren't carried through to the Billing document. Will I have to create my own condition types to carry these through? If so could someone give me a very brief overview of the steps required.

Many Thanks,

Philip Johannesen

[Former Member]

Hi Philip.,

Go to the copy controls in T.code VTFA and in item category Pricing type should be D.,

REWARD if helpfull

Thanks & Regards

Narayana