VK12 -Copy control rule
Dear All,
I'm trying to copy one material in vk12 condition tab,but ut shows one message - "Copying rules for conditions do not contain V 1 940 2 entry".
Kindly help me to resolve this issue.
Harsh
Hi
As per my under standing of the problem, the following link might have the answer.
Please do give it a try.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/93/743346546011d1a7020000e829fd11/content.htm
If the same dosen't fulfil your requirement, you are requested to elaborate the question further.
Thank You
Regards
Vinayak.M.G.
Similar Messages
-
COPY CONTROL NOT PRESENT FOR SALES DOCUMENT TYPE DS
I am new beginner to the module SD, i am stuck on the issue regarding copy control
I have created an Schedule Line Agreement and want to copy it to the sale document OR standard order, once entering the number for the schedule line document , i am getting a message the copy control rule does exist for DS to OR.
I have been to the setting for copy control with T-code VTAA but there are many fields that required to be filled up,
Which fields do i fill in ?
I have filled in the fields for item category for OR (TAN) and for DS (LPN).
If i use the copy control with these settings i am getting an error message "The copying routine number for table VBAP is missing in table TVCPA"
Any Help would really would be helpful
Regards,
SahilSahil,
I suggest you close this question, since this is an MM forum. You are unlikely to get many answers here.
I also suggest that you first perform a search, before re-posting this question elsewhere.
First, search within the forums (search box on the upper right of this screen). I just tried a search on 'copy control' and got over 20,000 hits. Surely one of these posts will be able to help you.
Next, check online help. This help is generic, and not generally specific to a particular industry:
http://help.sap.com ERP SD Help starts at
http://help.sap.com/saphelp_erp60/helpdata/en/8c/df293581dc1f79e10000009b38f889/frameset.htm
Next, look for generic solutions in Best Practices. This main Library is
http://help.sap.com/bp_bl604/BL_IN/html/Content_Library_BL_EN_IN.htm
Next look for industry specific solutions in Best Practices:
http://help.sap.com/content/bestpractices/industry/index.htm
If you are experiencing a problem, or you believe that SAP is not working per the online help, you can then search OSS notes.
http://service.sap.com/notes
Next search in one of the standard online search engines (such as Google).
Only after you have performed all of these searches, and studied all of the online help that is supplied for free by SAP, then consider posting a question to these forums. A good SD forum is
SAP ERP Sales and Distribution (SAP SD)
Best Regards,
DB49 -
VK12 , copying is incomplete
Hi,
In VK12 When im copying from one material to another by clicking on the copy condition button at the bottom.
im getting the following message:
"Copying is incomplete because no rules has been defined."
i have created materials in vk11 and trying to copy condition of one record to another.
Can anybody suggest on how toresolve this.
regards.
Srinivas.Hi dharmaji Srinivasu,
To be able to copy a condition record from one condition to other you need the following general prerequisites:
If the condition tables differ between the source and target condition records, then:
o Only one field may differ between the two condition tables
o The condition tables must contain the same number of fields
If the condition types differ between the source and target condition records, then each condition type must have the same calculation rule, scale type, condition class, and plus/minus indicator.
You are getting the message "Copying is incomplete because no rules has been defined." because you don't have customized the copy routine in sales -> basic functions -> pricing -> condition copy control.
Please check that and try again.
Thanks in advance,
Mariano. -
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. -
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 PMDear 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 -
ChaRM Copy Control for Ibase component
Hi Team,
I have created ZDCR which is copy of SDCR. And i have created ZDHF which is copy of SDHF. I have created the ZDHF as a subsequent document from ZDCR. While ZDHF is created, the Ibase component is not getting copied from ZDCR.
How to copy the ibase component from ZDCR to ZDHF?
Thank you for the input.
Regards
KumarHi
you need to maintain the settings
goto spro change request management->extended configuration->copy control
define mapping rules
here choose your entries and check the IBASE column.
this shd solv u prb
Regards
Prakhar -
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 TolaniWhat 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. -
Mapping Copy Control for Business Partners in 7.1
Hi everybody,
while in 7.0 IMG activity "Define Mapping Rules for Copy Control" in "Copy Control for Change Management" offers 3 options (partners, texts and dates) it offers only texts and dates in 7.1. Can anyone tell me where I can define any kind of mapping to copy a partner for one document to it's successor in 7.1?
Thanks in advance!
Cheers,
AndyHi Andy,
sorry to say but Daniels way doesn't work. In 7.1 ChaRM and Incident the transaction type copy has changed in a way that we invoke the CRM standard Copy Control and have a BadI there only for specific things.
Partner copy runs via CRM standard partner copy. That means:
1.) You have assigned an access sequence in each partner Determination (area Partner Functions in Procedure) for the partner function:
2.) You have customized an access sequence is defined here:
So, please just customize the partner copy as you would in CRM standard.,
Best regards,
Michael -
Cannot display Access Control Rules page --- BUG REPORT
iWS 4.1sp9 on Linux Admin GUI cannot display Access Control Rules page for Netscape browsers 4.7 and 6.2 or for IE 4.
It does work for IE 5.5 (running this in Vmware).
I'm reporting this bug here as I can't see anywhere else to put it.It could be a firmware bug, or it could be something else bugging out. If the router hasn't been factory reset and it's been through a few firmware upgrades, try resetting it to factory defaults. Take note of any custom settings you have, so you can go in and manually re-configure the router. I would avoid importing a backed up config file in case the config turns out to be the problem, but it doesn't hurt to download a copy of your config now.
Give that a try. Others might have some more ideas.
========
The first to bring me 1Gbps Fiber for $30/m wins! -
Hi Guys,
i am having one requirement.
My client is using one condition from so long time, they defined so many condition records for that condition type.
Now the case is, if i am using the other condition type with the resemblence of that condition type(exactly same with key combination) in another pricing procedure(because of some constraints we are not using same condition type). I want all condition records to be copied of that old condition type to this new condition type.
So, in this process i came to know, there is a configuration for copy control of condition. Plz share some config points in this regards.
Regards,
Rajesh.Hi Raj In,
Jacqueline's solution is good for your requirement. The field RefConType is on Master data Box. Bear in mind, if you'll use this solution you should continue loading condition records for the old condition not by the new. If you don't want that, so you need to define condition copy rule for those condition in:
Sales and distribution --> Basic Functions --> Pricing --> Copy control for conditions
Then, to make the copy of the condition records use trx VK32.
Thanks in advance,
Mariano. -
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,
Ranjanhi,
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 -
Basic Condition in copying control
Hi All,
anybody can you tell me what is basic rule in copying control.I know if copying from one doc to another certail thing are not copied.but how can i know.like if i am copying from invoice to return order assassable value is not copied but i have maintain pricing type D in copying control,what is the reason behind this that certain thing are not copied.
regards
ajitHi,
If you maintain D in the PRICING TYPE in COPY CONTROLS then definitley it should copy from the SOURCE to TARGET.
Please check in the Return order ->ITEM CONDITIONS->ANALYSIS and check the Condition type. It will give information on why it was not copied.
regards,
santosh -
Where do we maintain the copy control between sto (PO) to Delivery
Hi all,
Could please provide the info " where do we maintain the copy control between po and delivery "
.we have copy control between sale order & delivery so all so info will copy to delivery . like that where maintain the copy control between PO and delivery.??Hi
I think we don't have any copy control like in sd,but we can maintain relation between delivery and po by po docuement type
see following path
spro-MM-purchasing-Purchase order-set up stock transfer order-assign delivery type and checking rule
and in same path define shipping data for plant
for Doc type NB - delivery type NL
for doc type UB-Delivery type-NLCC
Regards
Kailas Ugale -
What kind of config is needed to make a free goods order type billable (zero dollar billing), Tried adding the billing type into the field Dlv-rel.billing type in VOV8. Doesn't allow to create the invoice.
Hi Arju,
In order to create an invoice for a free goods order, pl. maintain the following:
1) Make the item category relevant for billing
2) Maintain a default dlvy related billing type in customizing for sales document VOV8
3) Maintain copy control between dlvy and billing document.
Thanks
Kapil Sharma -
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.
Maybe you are looking for
-
When i click on item in xsltlistviewwebpart.ribbon get disabled
Hi, I have a scenerio where I need to enable a delete option [in listitem inside a ribbon], on click of an item in a listview webpart. I am administrator of the site but for few records I am unable to see "delete button." Image attached below. So, I
-
Using 2 separate 15" uMBP machines pointing to the same library on a timecapsule. +1st Late 2008+ 15" uMBP 2.4Ghz running Snow Leopard 10.6.2, iTunes 9.0.2 *2nd Mid-2009* 15" uMBP 2.53Ghz running Leopard 10.5.8, iTunes 8 (last/up2date version if iTun
-
Freight Calculation per DISTANCE
Hello All, I am trying to create a freight cost based on the Miles I have on the route. When I create a Shipement Document, the system takes the diatance to the shipment header (VTTK-DISTZ) but when I try to create the ship cost the system does not f
-
We have a horizontal navigation menu in our application. The dropdowns are constructed using a UI LI menu. This used to work in all browsers up until a few days ago. Now the dropdown will not display. Only the top level menu. The user has Mac OS X Se
-
I can't logon onto Telstra Air using My Account details as suggested.
I can't logon onto Telstra Air using My Account details as suggested in a email I received to get access.