Update copy control?

How can we update a copy controls?
Thanks!

Dear Raghav,
In IMG under
Sales and Distribution -> Sales -> Sales Documents -> Maintain Copy Control for Sales Documents -> Copying Control: Sales Document to Sales Document
or Transaction VTAA
Sales and Distribution -> Sales -> Sales Documents -> Maintain Copy Control for Sales Documents -> Copying Control: Billing Document to Sales Document
or Transaction VTAF
Regards,
Naveen.

Similar Messages

Copy controls from quotation to contract

Hi,
My client want to create contract w.r.t quatation.
I maintained the copy controls for the same but target quantity is not getting updated in contract w.r.t qutation
2)while creating contract without reference order quntity is not getting updated.
Pls suggest what i may missed
Thanks in advance

Hello Dear
This is NOT standard SAP process flow.
But make sure u have copy control at HEADER and ITEM CATEGORY level.
And as your qty is not getting copied that means some thing is wrong with Routines( copy control and data transfer).
Thanks,
Dilip Sadh

COPY CONTROL: SALES ORDER WITH REFERENCE TO QUOTATION

Hi.
We are creating a sales orders with reference to a quotation. When copying, we'd like to be able to include another new position type in the sales orders.
For example:
QUOTATION:
POSITION 10: TYPE ZTAB
SALES ORDERS:
POSITION 10: TYPE ZTAB
POSITION 20: TYPE IRSS.
Where could we place this change?. We suppose when saving the sales orders. Does anybody know how could we make this change?.
Thank you very much!.
Raú

What do you mean by position type?
Please use the language used by SAP so that it could be easily understood.
What is ZTAB & IRSS. Are they materials?
Regarding copying, this is a brief theory
In copy control, you define control data for the document flow of sales documents.
You can specify for a particular sales document type, which document type is to be assigned to copied reference documents, and which item categories or schedule line categories are to be copied.
You must also make specifications for copying requirements and data transfer, as well as quantity and value updates in document flow.
In precise, you are telling the system what data to copy from QT to sales order. It copies data from Quotation order type to Standard order type basing on settings you indicated in copying control.
System won't do anything more than copying from preceding documents and it would transfer data based on copying rules in copy control.

Copy control in contracts

Good afternoon!
I´m having problems regarding copy control between contracts and release orders.
Here´s an example:
Contract 40000019 has an item for 100 pcs.
I input a order which is referenced by this contract, and the system proposes a quantity of 100 pieces. The quantity is changed to 50 pcs manually and is delivered afterwards.
When I input a second order, the system proposes again 100 pieces.
First question: Is there anyway to make the system propose only the un-delivered quantity? i.e. the remaining 50 pieces?
Second question: how do I make the system not to copy rejected items?
Thanks in advance,
Adriano Cardoso

Hi ,
In standard system settings once we take the reference it will copy either whole quantity or nil quantity.We can make the quantity field as empty by making changes in copy controls.If you want to make the balance quantity for delivery ,then need to adda piece of code for your copying requirement for field VBAP.KWMENG and check the quantity already delivered by going in to VBFA table then pick all the subsequent documents for the contract.
It is also important to check the field update document flow tab in copying controls to restrict the quantity.
Hope it helps.
Regards,
Pasapula.

Urgent help on Pricing - Copy controls in SD.

Hi, I am facing issue in SAP while copying the %value of the discount condition type from the sales order to invoice incase BOM material exists in sales order.
"This is happening if the %value of discount modified in the sales order"
- BOM having the item level pricing in sales order. and the discount condition type maintained as "manual entry has priority" (C)
- If discount value modified in sales order sub item(BOM), same value is not copying at the invoice level. but the sub item of invoice document is having same value of the condition record. even after using the "update pricing" in invoice document
- Incase of normal item it is working fine.
- In copy control, item category(ZXXX) of the sub item, "pricing type" maintained as 'c'- Copy manual conditions and re determine others.
As per the technical analysis; BOM (header and item) in the sales order has S.No - 10 and 11, item 11 has pricing maintained(item level). But item 11 is carry forward to Invoice as item 10 (S.NO). when item 10 in the invoice trying to get the discount value from item 10 of the sales order to get the discount amount, since BOM is maintained as item level pricing i.e item11 there is no discount condition type/value finds for the item. system populating the value of the condition record.
How to rectify this issue? please provide the solution if any one knows;Thanks
Let me know if any details required.
Rgds
Siva

Hi Sagar,
I have the same question as TW.
Why does your BOM item not present in the Invoice ? When it is not priced, its presence would not impact anything(not charged and does not flow to accounting) and would also solve your issue.
Thanks,
Deb

Copy controls & Pricing

Right now, in the copy control of delivery to invoice, at item level pricing type is G.
Now,
During SO, at item level , I manually "update" with C. After this, the same price should reflect in the invoice.At invoice, there should be no manual 'update'.
what is the pricing type to be set in SPRO ( so that, no manual update with C is needed at SO header) for this & at what level?
Request an expert to guide me soon, on this, as the actual pricing issue is a bit complicated to explain.
Rgds
Sumanth.G
Edited by: SUMANTH GURURAJ on Nov 3, 2011 10:40 PM

Dear Ram
FOB Price = 'Base Price' - (sum of ' frieght' & 'insurance')
The above logic is in Alt calc Type :12 & is assigned to 'FOB Price' in pric proc.
'Frieght' & 'insurance' are MANUAL HEADER conditions.
Now, with G,
at header level in invoice, when we enter 'frieght' & 'insurance' manually, the 'FOB Price' is NOT getting calculated. ( in 'condition value' column).
With B, the 'FOB Price' is getting calculated' ( as described above)
The problem, is the client does NOT want to use B ( for below mentioned reasons)
with B, only the current billing date is considered.**
The client wants SO PRICING DATE ( which G is fulfiling) ( but G hs limitation, as explained above)
Any other pricng types, which u suggest?
or shall I try to insert a condition category to 'FOB Price' (which is blank now)
The 2 c. types are :
'FOB Price' -
Cond. class B Prices
Calculat.type C Quantity
Cond.category (blank)
Rounding rule Commercial
StrucCond. (blank)
'Frieght' & 'Insurance' (manual hearder conditions) are then added together to a subtotal,& inturn made a single condition type as below.
'Frieght & insurance'
Cond. class A Discount or surcharge
Calculat.type B Fixed amount
Cond.category F Freight
Rounding rule Commercial
StrucCond. (Blank)
Request an expert to kindly guide me on this.
Immediate help would be appreciated.
Rgds
Edited by: SUMANTH GURURAJ on Nov 4, 2011 10:23 AM

Copy control settings for Multilevel variant configuration

Dear All,
I have the following scenario for variant configuration A quotation is created for configurable material with multilevel configurable material
with reference to this quoatation a sales order is created.
My requirement is that the quoatation must get copied to sales order as it is along with the values for subitems also.
In copy control settings there is a field at item level called
configuration :
In this if I maintain value
A: The variant is getting copied but the values for subitems is not getting copied the values for main material is in changable mode.
B: The variant is getting copied but the values for subitems is not getting copied the values for main material are not in changable mode.
C:The variant is getting copied   the values for subitems is getting copied the values for main material are in changable mode but the values for subitems are not in changable mode.
My requiremnt is that
The variant must get copied
the values for subitems must get copied
the main material vlaues must be in changable mode
the subitems vlaues must be in changable mode
How can I fullfill this requiremnt, has any one of you come across this scenario, Pleae provide with solution it is urgent
Informative answers will be provided maximum points.
Deepak

Hai Deepak Mehmi,
please check in T CODE VTAA
In the position check
SalesDocType : Sales order type
SalesDocType : Inquiry type
Double clcik and check
DataT 051 General header data       Copying requirements 002 Header-diff.customer
DataT 101 Header business data
DataT 001 Partner header
And Tick mark for Copy Item Number
For further check:
In Item
                                  Copying requirements 301
DataT 151 General item data                                          Pos./neg. quantity   +
                                                           Copy quantity
DataT 102 Bus.data/item compl.                                     Pricing type         G
DataT 002 Partner item                       2 Update document flow   Cont. item copy mode
                                                    Copy product select.
FPLA 251 Conditions                Configuration
                                                           Campaign Deter.
Regards,
Mani

Copy control for Return Process

HI every one,
I am Doing the Return Cycle Process but i am not sure how to maintain the Copy Control because i am new to return process
Billing Type : ZF2, Item category :ZTAN,Return Order : ZRE, Item category : ZREN, Billing Type : ZG2 (Credit Note)
give me how to maintain the Copy Control in VTFA,VTLA,VTFL
Guideme
Regards,
Anu
Edited by: Anuradha_SD on Sep 14, 2011 12:50 PM

HI
Let us talk about the Copy control VTAF
I maintained the Copy Control Order Type ZRE,
Target SalesDocTyp ZRE                    Source Bill. Type ZF2
                   Sales Return - JICPL                     Invoice - JICPL
DataT 052 Billing doc.header        Copying requirements 021 Billing header
DataT 103 Bill.bus.header data            Copy item number (TICK)
DataT 003 Bill.header partner
Target SalesDocTyp ZRE                    Source Bill. Type ZF2
                   Sales Return - JICPL                      Invoice - JICPL
ItemCat Proposal   G2N                    Item Category      ZREN
                   Request                                   Return Items -JICPL
                                    Copying requirements 303 Always an item
DataT 153 Item from bill.doc.
                                                           Pos./neg. quantity
DataT 104 Bill.bus.item data                               Pricing type         D
DataT 004 Bill.item partner         X Update document flow
bl.pl 0                                                    Campaign Deter.
Target SalesDocTyp ZRE                   Source Bill. Type ZF2
                   Sales Return - JICPL                     Invoice - JICPL
SchdLneCatProposal DN                    Sched.Line Cat.    CP
                   Return - JICPL                           MRP -JICPL
                                    Copying requirements 303 Always an item
DataT 002 Partner item
Like that i maintained but at the time of Return order with reference to Billing Document its not working means
if i take Second time Same billing Document Number system is showing same qty because i have already refered previously
why system is showing same qty why it is not reduced
guide me
Regards
Anu

Reference order with inquiry through copy control

Hi SD gurus,
We are currently having automatic order creation and then the open inquiry are required to be linked manually to newly created sales order via u2018create with referenceu2019 option inside the order menu.
We want to achieve this below functionalities via copy control (VTAA) for this requirement:
1. Enable creation with reference to an inquiry in change mode of a sales order without repeating the item from inquiry. Only consumption from inquiry.
2. Enable this with different sold-to .
Sales order----
Inquiry
Sold to 1 not equal toSold to 2
Point 2 can be achieved through copying requirement routine 002 at header level but then there is no success for point 1. Both things should work together.
If you have any idea then please suggest.
Thanks in advance.
Regards,
Dheeraj Tolani

What do you mean by position type?
Please use the language used by SAP so that it could be easily understood.
What is ZTAB & IRSS. Are they materials?
Regarding copying, this is a brief theory
In copy control, you define control data for the document flow of sales documents.
You can specify for a particular sales document type, which document type is to be assigned to copied reference documents, and which item categories or schedule line categories are to be copied.
You must also make specifications for copying requirements and data transfer, as well as quantity and value updates in document flow.
In precise, you are telling the system what data to copy from QT to sales order. It copies data from Quotation order type to Standard order type basing on settings you indicated in copying control.
System won't do anything more than copying from preceding documents and it would transfer data based on copying rules in copy control.

Copy control for inbound delivery

Hi All,
I need some help for copy control for inbound delivery. Can any one let me know where is the customization for this?
Is it t.code VTLA.
Path in IMG:Logistics Exectuion-->Shipping>copy control--
>specify copy control for delivery
But I am not sure if the above is the correct customization path.
The reason....
for target document type EL(Inbound delivery) the source document type is DL (order type schduling agreement). Ideally for inbound delivery the source document type should be purchase order. But I can't find the purchase order document types in F4 option.
All documents which are showing are sales order.
Awiting your reply.
Regards,
Sushanta

Specify Copy Control for Deliveries
In this menu option, you define control data for the document flow of deliveries.
You can specify for a particular delivery type, which document type is to be assigned to copied reference documents, and which item categories are to be copied.
You must also make specifications for copying requirements and data transfer, as well as quantity and value updates in document flow. This must be done for each copying procedure at header and item level on a detail screen.
Note
If you define new sales document types, item categories or schedule line categories by copying existing ones, the SAP system automatically copies all specifications for the document flow. You may want to check the copy controls for newly created sales document types, item categories or schedule line categories.
Actions
1. Check the document flow defined in the standard SAP R/3 System.
2. Define to what extent you have to modify its specifications to meet your requirements.
3. Define the document flow for deliveries with reference to sales document types.
Note
Make sure to maintain copy control for the following areas:
Sales documents
Deliveries
Billing documents
If you cannot find an entry, check the copy controls in other chapters.
Complete overview of copy control:
In the chapter on sales, you can find copy controls for:
Sales documment by sales document
Billing document by sales document
In the chapter on deliveries, you can find copy controls for:
Sales document by delivery
In the chapter on billing, you can find copy controls for:
Sales document by billing document
Delivery by billing document
Billing document by billing document

Copy controls, how to do it

The SOrder type is ZOR1
The deliv doc type is ZLF1
How to set copy controls at the header and item levels???
gone to VTLA....selected both the docs...how to set copy controls between header and item level...please help me...

Dear raghu ram
At Header Level :
Conditions :
Order requirements:::::::::001
Combination requtmt:::::::051
Data Transfer
Header Data:::::::::::::::::::001
At Item Category Level
Order requirements::::::::101
Data Transfer
Item data:::::::::::::::::::::::101
Business Data::::::::::::::::2
Select "Update document flow"
thanks
G. Lakshmipathi

Re: Errors in copy controls

Hai SDN Members
In VL01N AFTER entering shipping point and order nu if i enter
<b>No OF copying ref is missing for table LIPS in ttable TCVPL</b>this error message is displayed.
pl find me ths solution.Points Rewarded
regards
anand

Pl maitain the copy control between the sales order document and delivery at both header level and item level.
Spro->img->logistic execution->shipping->copy control ->specify copy control for deliveries
Order requirement at header -001
check item numeber check box.
At item level
Order REquirement -101.
check update document flow
positive/negative qty - +

Problem Copy control Order to Invoice

Hi All,
I maintained a copy control from order to invoice and in the item category the pricing type is maintained as 'G'(Copy pricing elements unchanged and redetermine taxes). But when I create invoice the condition value for pallet discount is getting recalculated.
There is a requirement for this condition type in the pricing procedure that when the order quantity is greater than the pallet quantity maintained through material master then only the discount should be affected.But when I change the pallet quantity to less than the order quantity,after the order is created and then invoice the order the condition value is going through the requirement and the value is getting changed .
Can anyone tell me why it is recalculating when the invoice is created, it should not reprice the order, but just carry over current pricing to the billing
All useful answers will be rewarded.
Thanks,
Ranjan

hi,
Refer to OSS note 24832:
14.05.2008 Page 1 of 10
Note 24832 - Pricing rules / TVCPF
Note Language: English Version: 27 Validity: Valid from 18.05.2004
Summary
Symptom
Depending on the situation, the system should redetermine conditions or
not. For this, a differentiated control is required, for example:
1. When you create sales orders or billing documents, the condition types
are partially redetermined although you want to copy the values from
the reference document.
2. During other transactions, however, you want to redetermine the
condition types instead of copying them.
3. The 'New pricing' function on the item condition screen
redetermines all new conditions, that means it works with pricing
category 'B'. This is undesirable to a certain extent.
4. The same applies to the 'New pricing' function for the entire sales
order.
The following text will explain some examples for the use of the pricing
type implemented for this purpose (KNPRS):
Example 1 **********************************
You want to copy condition type 'VPRS' from the sales order into the
billing document. You are using pricing type 'G'. However, as a consequence
the value of the VPRS condition in the billing document differs from the
value of the goods issue posting.
Example 2 **********************************
You want to copy condition type 'PI01' (price for intercompany billing)
from the sales order into the billing document. You are using pricing type
'G'.
Example 3 **********************************
The costs 'VPRS' are to be redetermined when copying a credit memo request
from a billing document. This is required if you defined the credit memo
item in such a way that no costs are to be determined. Since the pricing
requirements are no longer checked when copying, you have to proceed as
described above to eliminate the VPRS.
Example 4 **********************************
The 'New pricing' function on the item condition screen is to keep the
manual condition, this means the function should behave like pricing
category 'C'.
Example 5 **********************************
The 'New pricing' function for the entire sales order is to keep the
14.05.2008 Page 2 of 10
Note 24832 - Pricing rules / TVCPF
manual conditions, this means the function should behave like pricing
category 'C'.
Example 6 **********************************
Billing is to be carried out using pricing type 'G'. However, condition
types with condition category 'S' and 'T' (standard price or moving costs)
are also to be redetermined. In the standard system this pricing type
copies those condition types from the sales order.
More Terms
KNPRS, TVCPF, TVCPA
Cause and Prerequisites
The pricing type controls which condition types are redetermined or which
are copied unchanged (however, the items are always revaluated). Below,
you will find a description of the pricing type characteris
Note that the specified standard pricing type characteristics
partly do not exist in older releases, or that the standard
pricing type characteristics may be different in the
individual releases. Therefore, the given consulting note
should not be considered to be exhaustive. It merely serves to
explain the principle of how a pricing type is structured and
how its characteristics can be influenced. The exact
characteristic of a pricing type in the release being used can
be seen directly in the source code of Form routine
KONDITIONSVORSTEP in Main program SAPLV61A.
o 'A' (Copy price components and redetermine scales):
No condition types are redetermined. Only the scaled prices are
adapted due to a changed basis.
o 'B' (Complete new pricing):
Completely new pricing (as if you created a new item), manual
conditions are lost.
Restriction: Condition types which are not determined via condition
technique (for example, condition type 'VPRS' or condition types
with KNTYP = 'G' which are determined using formulas) are NOT
redetermined even if you do not change them manually.
o 'C' (Copy manual pricing elements and redetermine the
others):
Completely new pricing, manual ones are copied.
Caution: Here you have to make sure that all condition types that
can possibly be changed manually have T685A-KMANU = 'C' (Manual
entry has priority) in Customizing. Otherwise, it is possible that
the conditions are displayed twice (automatically and manually) and
that both are active.
o 'D' (Copy pricing elements unchanged):
14.05.2008 Page 3 of 10
Note 24832 - Pricing rules / TVCPF
As in pricing type 'A' but the prices are fixed (no scales are
read). Condition base value and value are redetermined.
o 'E' (Adopt price components and fix values):
As in pricing type 'D' but neither condition base value nor value
are redetermined.
o 'F' (Copy pricing elements, turn value and fix):
Only used within the program.
o 'G' (Copy pricing elements unchanged and redetermine
taxes):
a) The following condition types are redetermined:
- Condition class KOAID = 'D' (Taxes)
- Condition class KOAID = 'C' (Volume-based rebate)
- Condition category KNTYP = 'I' (Intercompany billing
conditions)
- Condition category KNTYP = 'R' (Invoice list conditions)
- Condition category KNTYP = 'L' (Always new when copying)
- Condition category KNTYP = 'G' (Cost conditions)
- Condition category KNTYP = 'E' (Cash discount conditions)
All remaining condition types are dealt with like pricing type 'D'.
In particular, with pricing type 'G', the system does not only
redetermine the taxes but also the cost conditions and the
intercompany billing conditions.
o 'H' (Redetermine freight conditions):
The following condition types are redetermined:
- Condition type KNTYP = 'B' (Delivery costs)
- Condition type KNTYP = 'F' (Freight conditions)
- Condition type KNTYP = 'L' (Always new when copying)
o 'I' (Redetermine rebate conditions):
Rebate conditions and scales are redetermined.
o 'J' (Redetermine confirmed purchase net price/value):
Condition types with condition category KNTYP = 'D' (Confirmed
purchase net price/value) are redetermined.
o 'K' (Adopt price components and costs. Redetermine
14.05.2008 Page 4 of 10
Note 24832 - Pricing rules / TVCPF
taxes):
The following condition types are redetermined:
- Condition class KOAID = 'D' (Taxes)
- Condition class KOAID = 'C' (Rebate)
- Condition category KNTYP = 'R' (Invoice list conditions)
- Condition category KNTYP = 'I' (Price for intercompany billing)
- Condition category KNTYP = 'E' (Volume-based rebate)
o 'M' (Copy pricing elements, turn value):
No conditions are redetermined; during copying, the condition
values are multiplied with -1.
o 'N' (Transfer pricing components unchanged, new cost):
Condition types with condition category KNTYP = 'G' (Cost) are
redetermined.
Please note that this pricing type has NO effect on the invoice
since here the goods issue value from the delivery is usually
directly transferred to pricing. Redetermination of the settlement
price by subsequently reading the material valuation segment when
executing pricing type "N" would result in the fact that the goods
issue value information were irretrievably lost.
This standard behavior can be changed by a modification only. If
required, please contact your local consultant or SAP Remote
Consulting.
o 'O' (Redetermine variant conditions):
Condition types with condition category KNTYP = 'O' (Variants) are
redetermined.
o 'P' (Revaluation only):
The system does not redetermine any conditions; only the
revaluation occurs.
o 'Q' (Redetermine calculation conditions):
Condition types with condition category KNTYP = 'Q' (Costing) are
redetermined.
o 'U' (Redetermine precious metal conditions):
Condition types with condition category KNTYP = 'U'
(Discount/surcharge for precious metals) are redetermined.
Solution
There are two options to change the standard behavior:
14.05.2008 Page 5 of 10
Note 24832 - Pricing rules / TVCPF
1. Set up a new pricing type (for example, 'X') and allocate the pricing
type in the document flow (copying control in the IMG, Customizing
depending on the source and target document type via Transactions
VTAA, VTAF, VTLA, VTLF and VTFF).
2. Change the pricing type used in the standard system.
Procedure
For both purposes, USEREXIT_PRICING_RULE is used in Program RV61AFZA. This
is called after the setup of internal table STEU which defines the behavior
of pricing types.
Example 1 ******************************
Picing type 'X' is to be set in a way that condition 'VPRS' (which has
condition category 'G') is not redetermined during the billing. Otherwise
it behaves as pricing type 'G'.
Up to Release 4.0B, USEREXIT_PRICING_RULE can be implemented as follows:
FORM USEREXIT_PRICING_RULE
STEU-KNPRS = 'X'.
STEU-KNTYP = 'LRIE......'.
IF KOMK-KNUMA IS INITIAL.
STEU-KOAID = 'CD........'.
ELSE.
STEU-KOAID = 'D.........'.
ENDIF.
STEU-MAUEB = ' '.
APPEND STEU.
ENDFORM.
In order to ensure that pricing type 'X' acts exactly like pricing type
'G', the FORM routine USEREXIT_PRICING_COPY in Program RV61AFZA is to be
used in releases lower than Release 4.0A (if you create a document with
reference to another document, this is called: copying control; here, the
MODE is the pricing type):
FORM USEREXIT_PRICING_COPY.
IF MODE CA 'X'.
IF KONV-KSTEU NA 'CEF'.
KONV-KSTEU = 'D'.
ENDIF.
ENDIF.
ENDFORM.
In this case, you should note that the billing document contains a special
rule concerning cost condition 'VPRS'. If the goods issue for the delivery
note to be billed is posted, the value of the goods issue is copied into
condition 'VPRS'. This is hard-coded. You can prevent this by setting the
field TKOMP-WAVWR to zero in include LV60AFZZ,
USEREXIT_PRICING_PREPARE_TKOMP.
In higher releases, pricing type 'K' is also available, which copies the
VPRS of the order to the billing document and does not redetermine it
unless there is no goods issue posting (otherwise, the above-mentioned
special rule applies.)
14.05.2008 Page 6 of 10
Note 24832 - Pricing rules / TVCPF
Example 2 *********************************
Pricing type 'Y' is to be set in a way that this works as pricing type 'G'
but without redetermining the intercompany billing conditions 'PI01' and
'PI02'. They have condition category 'I'.
Changes in program RV61AFZA:
FORM USEREXIT_PRICING_RULE.
STEU-KNPRS = 'Y'.
STEU-KNTYP = 'GLRE.......'.
IF KOMK-KNUMA IS INITIAL.
STEU-KOAID = 'CD........'.
ELSE.
STEU-KOAID = 'D.........'.
ENDIF.
APPEND STEU.
ENDFORM.
In order to ensure that pricing type 'Y' acts exactly like pricing type
'G', the FORM routine USEREXIT_PRICING_COPY in Program RV61AFZA is to be
used:
FORM USEREXIT_PRICING_COPY.
IF MODE CA 'Y'.
IF KONV-KSTEU NA 'CEF'.
KONV-KSTEU = 'D'.
ENDIF.
CLEAR: KONV-SAKN1.
ENDIF.
ENDFORM.
EXAMPLE 3 *********************************
Pricing type 'Z' is to be set in the same way as pricing type 'D', but this
time the costs are to be redetermined. Up to Release 4.5B, you can
implement USEREXIT_PRICING_RULE as follows (as of Release 4.6A, pricing
type 'N' is available for this procedure):
FORM USEREXIT_PRICING_RULE.
STEU-KNPRS = 'Z'.
STEU-KNTYP = 'G.........'.
STEU-KOAID = '..........'.
STEU-MAUEB = ' '.
APPEND STEU.
ENDFORM.
In order to ensure that pricing type 'Z' acts exactly like pricing type
'D', the FORM routine USEREXIT_PRICING_COPY in Program RV61AFZA is to be
used:
FORM USEREXIT_PRICING_COPY.
IF MODE CA 'Z'.
IF KONV-KSTEU NA 'CEF'
KONV-KSTEU = 'D'.
ENDIF.
ENDIF.
14.05.2008 Page 7 of 10
Note 24832 - Pricing rules / TVCPF
ENDFORM.
Note: To correct the problem, you should define your own pricing types. In
some cases, it may be required to change existing pricing types. This is
required if you want to influence the reaction to certain field changes in
the sales order (see Note 26115 for this). This also allows you to
influence the 'New pricing' function in the sales order and billing
document. This function uses pricing type 'B'.
EXAMPLE 4 *********************************
The 'New pricing' function is meant to keep the manual changes. By default,
pricing type B' is called. As of Release 4.5A, however, you have the option
to store another pricing type for this purpose in Customizing of the
pricing procedure (Transaction V/08).
In USEREXIT_CHANGE_PRICING_RULE of program MV61AFZA, you can
replace pricing type 'B' with another pricing type, for
example, 'C' up to Release 4.0B.
FORM USEREXIT_CHANGE_PRICING_RULE USING PRICING_RULE.
IF PRICING_RULE = 'B'.
PRICING_RULE = 'C'.
ENDIF.
ENDFORM.
EXAMPLE 5 **********************************
The 'New pricing' function is to be set for the entire sales order in a way
that manual changes are kept. In the standard system, pricing type 'B' is
called. As of Release 4.5A, however, you have the option to store another
pricing type for this purpose in Customizing of the pricing procedure
(Transaction V/08).
Up to Release 4.0B, a solution is only possible by means of a modification
in program MV45AF0F:
FORM FCODE_KONB.
PERFORM PREISFINDUNG_GESAMT USING CHARB. <<<<<<<<<< delete
PERFORM PREISFINDUNG_GESAMT USING CHARC. <<<<<<<<<< insert
ENDFORM.
FV45PF0P has to be changed in the same way:
FORM PREISFINDUNG_NEU.
Aufruf neue Preisfindung
PERFORM PREISFINDUNG USING CHARB. <<<<<<<<<< delete
PERFORM PREISFINDUNG USING CHARC. <<<<<<<<<< insert
geänderte Informationen in Beleg übernehmen
PERFORM VBAP_BEARBEITEN.
PERFORM VBAP_BEARBEITEN_ENDE.
ENDFORM.
14.05.2008 Page 8 of 10
Note 24832 - Pricing rules / TVCPF
EXAMPLE 6 *********************************
Pricing type 'X' is to be set so that it functions like pricing type 'G',
but also redetermines condition categories 'S' and 'T'.
Change in Program RV61AFZA:
FORM USEREXIT_PRICING_RULE
STEU-KNPRS = 'X'.
STEU-KNTYP = 'GLRIEST...'.
IF KOMK-KNUMA IS INITIAL.
STEU-KOAID = 'CD........'.
ELSE.
STEU-KOAID = 'D.........'.
ENDIF.
STEU-MAUEB = ' '.
APPEND STEU.
ENDFORM.
To ensure that pricing type 'X' behaves exactly like pricing type 'G', use
FORM routine USEREXIT_PRICING_COPY in Program RV61AFZA:
FORM USEREXIT_PRICING_COPY.
IF MODE CA 'X'.
IF KONV-KSTEU NA 'CEF'.
KONV-KSTEU = 'D'.
ENDIF.
ENDIF.
ENDFORM.
Additional information ***********************
You can display the standard behavior of the pricing types in FORM routine
KONDITIONSVORSTEP (up to Release 3.1I in Include LV61AF0K, as of Release
4.0A in Include LV61AA12). There, for each pricing type, a line exists in
internal Table STEU. The fields have the following meaning:
o KNPRS
This is the pricing type used.
o KNTYP
This field contains a positive list of the pricing categories (up
to 10 values can be entered).
o KOAID
This field contains a positive list of the condition classes (up to
10 values can be entered).
o MAUEB
This field specifies whether manual changes should be copied.
o STFKZ
This field contains a positive list of the scale indicators (up to
14.05.2008 Page 9 of 10
Note 24832 - Pricing rules / TVCPF
5 values can be entered).
o NOTYP
This field contains a negative list of the condition categories (up
to 5 values can be entered).
o KDUPL
This field contains a positive list of the structure conditions (up
to 3 values can be entered).
o NOKDUPL
This field contains a negative list of the structure conditions (up
to 3 values can be entered).
o KFKIV
This field specifies whether intercompany billings should be
redetermined ('.' or 'X' can be entered).
o KVARC
This field specifies whether variant conditions should be
redetermined ('.' or 'X' can be entered).
o PRSQU
This field specifies whether the price source should be taken into
account ('.' or SPACE can be entered).
Note that most condition attributes (fields of the XKOMV structure) can
also have the value SPACE. To use the above 'CA' or 'NA' statements in the
IF statements also in these cases as required, you can fill the fields of
the STEU line with a corresponding number of '.' characters. These values
are mainly checked in FORM routine XKOMV_AUFBAUEN_PRUEFEN (up to Release
3.1I in Include LV61AF0X, as of Release 4.0A in Include LV61AA65).
Header Data
Release Status: Released for Customer
Released on: 18.05.2004 13:18:36
Priority: Recommendations/additional info
Category: Consulting
Main Component SD-BF-PR Pricing
The note is not release-dependent.
14.05.2008 Page 10 of 10
Note 24832 - Pricing rules / TVCPF
Support Packages
Support Packages Release Package Name
DIMP 471 SAPKIPME06
Related Notes
Number Short Text
1009170 Date of services rendered in the credit memo process
992808 Pricing type 'T': Redetermine tax conditions only
547570 FAQ: VPRS in pricing
410907 Allowed pricing types BAPISDLS-PRICING III
195094 Manual prices during intercompany billing
117347 Pricing type K modified for condition category L
114756 Customer hierarchy determination for pricing
102961 New pricing type for milestone billing plans
45326 No prices for customer-specific pricing type
26115 Conditions not updated during field change
Award opints if useful.
Regards,
Raghu.
Edited by: Raghuram Saripalli on May 14, 2008 11:12 AM

' + ' ve & ' - ' ve quantity in copying control

I tried to copy a quote (12 qty) to order(11 qty), but when I went back to the quote again, it still had the open qty remaining as 12.
Steps done (All using standard):
QT= 10 qty doc complete
QT->OR 10 qty doc complete
Check QT- 10 qty
Which one is the open qty:
Line Item qty
Schedule line order qty
Schedule line confirmed qty
Can anyone tell me if I am checking at the wrong place or have missed out any step in between.
Discussion locked.
Reason: Duplicate post - Copy Control: Positive/Negative Qty, Open Qty is still Open in Quotation when an Order is created using quote as refernece
Message was edited by: Jyoti Prakash

Hi,
This controls how the quantity is to be dealt from the source document to the Target document. For example, your are creating a quotation QT; with reference to the quotation you are creating a sales order OR. If the quotation is for 1000 pieces. First you create a sales order for 750 pieces. So what should happen to the quantity given in the source document. This is exactly controlled by this field. In this case it should be 1000- 750=250 is to be updated. So, at item category level (AGN) it is given positive sign.
Take a different example: You are creating a quantity contract CQ; then you are creating a return order with reference to this quantity contract. Let the quantity contract was created 1000 pieces; after so many sales order the remaining quantity is 870 pieces. Now you are creating a return order for 100 pieces with reference to Quantity. What should happen to the source document Quantity contract CQ? This is controlled by the /- field. By logic, in this case the quantity contract should increase to 870100=970. So the quantity contract is eligible for 970 pieces after this transaction. That is why the item category KMN while copying from CQ to RE is shown as negative.
For example, if you change the sign from positive to negative in item category AGN while copying from Quotation QT to Sales order OR, the eligible quantity to be copied to the sales order will increase every time you create a sales order.
Regards,
K Bharathi

Copy control for Questionnaire from Opportunity to activity

Hi All,
I have the Business Requirement to copy updated Questionnaire from Opportunity to follow up activity / Task.
Can anyone suggest if is it possible through Copy control BADI or any other Enhancement.
Thanks & Regards
Amit

Hi,
please implenet this BADI 'CRM_COPY_BADI' and put the break point and do debugging then u will get clear idea..
after that please let me know ur comments..
Regards,
Bixamaiah.

Update copy control?

Similar Messages

Maybe you are looking for