Formula in copy control
Hi
Hello, I have a doubt, I need to export a value in the copy control of sales document to sales document, in the formula 051 - General header data , the doubt is if it's corret that I ask for the access key of this formula, or the correct way to do my change is create another formula??
Thanks
Regards
Soraya
Hi Soraya,
It's always better to create another copy routine in T-code VOFM and replace the standard one.
Then in case problem occurs, you could test with standard routines to check the normal behaviour.
Thanks and regards,
Smile
Similar Messages
-
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 -
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. -
Copy Control between Sales Orders and Deliveries
Hi Gurus,
please can you tell me why copy control between Sales Order and Delivery doesn't work?
At header level, into copy control, we can set 2 requirement routines, one as general requirement for copying (TVCPL-AUBED) and the other one as requirement for grouping orders into deliveries (TVCPL-AUZUS).
At header level we can also set a routine for data transfer to define how data are passed from Sales Order header to Delivery header (TVCPL-GRUAK).
Then we can set routines at item level, one as requirement (TVCPL-AUBED) and one as data transfer (TVCPL-GRUAP).
When delivery is created with VL10A transaction, at header level only the first general requirement routine is used (FV50B***). Grouping requirement is not used (we also set a break point and the program is not passing into this routine).
Then it is used the requirement routine at item level (FV50B***).
Please can you tel me how we camake working the routine for grouping requirement at header level?
Thank you very much.
Kind Regards
AndreaHi, we used standard routine even if to be sure we run also the generation report you mentioned.
Please any other suggestions?
Thank you very much.
Kind Regards
Andrea -
Complaint wth ref. to invoice in CRM - Copy control not taken into account!
Hi all,
We are facing problems when replicating return orders (business object Complaint) with reference to invoices in ERP.
The copy control in ERP is not taken into account. Does anyone know if it is possible to check the copy control when replicating the complaint to ERP with reference to the invoice?
The return order is being replicated correctly and the link to the invoice is shown (so, the flow is correct).
But:
1.- The manual pricing conditions in the invoice in ERP are not being copied in the return order.
2.- Some data as the 'Incoterms' is being redetermined from the customer master data and is not being copied from the invoice.
3.- Data related to material is also being redetermined when the order is replicated
The copy control is not being taken into account and we can replicate return orders from CRM to ERP with reference to invoices for which the copy control is not maintained in ERP...
Please help...
Thanks in advance!
YolandaTry something like this, in place of ls_input_field_names-fieldname = 'ZZDEP2PVNDPGM'..
ls_input_field_names-objectname = 'ORDERADM_H'.
ls_input_field_names-ref_handle = '100'.
insert ls_input_field_names into table lt_input_field_names.
Edited by: Kevin Alcock on Aug 10, 2009 4:03 PM -
Follow-up transaction copy control for opportunities
Our CRM system is currently configured to permit follow-up opportunity creation. When follow-up transactions are created all product categories are copied to the new opportunity. We would like to stop this. All header and business partner data should be copied as present, however product information should not be copied. (i.e. follow-up transactions currently work, we only want to switch off product data copying)
I am not familiar with follow-up transaction customization, and not sure exactly where to start. Should I be modifying the current BAdI or is there a standard customizing option to switch off copying of product categories?Hi Derek,
Just try this:-
Go to SPRO->IMG->CRM->Transactions->Basic Settings->Copying Control for Business Transactions->Define Copying Control for Transaction Types.
Search for entry Source=oppt and target=oppt.In this entry, uncheck the check box-Copy Item Number and see if it resolves your issue or not?
Thanks and Regards,
Rohit -
Copy Control for Transaction Types
Hi,
Was wondering if someone could help on following topic. We need to specify the possibility of copy control (follow-up) for certain transaction types in CRM 6.0. I've specified the source TT (ZAPP) and the target TT (ZCON) in customizing activity : Define Copying Control for Transaction Types.
ZAPP = Custom Appointment Activity
ZCON = Custom Opportunity
Now, when I want to create a follow-up for ZAPP in the WebUI (via dropdown 'More' and action 'Follow-Up'), I always get an extensive list of transaction types (about 30) rather than only the opportunity that I originally specified. Any ideas?
Thank you,
Sebastiaan.Hi Kai,
Many thanks for your answer. Indeed, the COPY_DOCUMENT is a very good alternative as it also directs the flow for follow-up. However, I have a question in regards to using this method. I can see that there are parameters that need to be provided (like PROCESS_TYPE etc) but apart from that is it also possible to change fields in the copied document.
e.g. Currently the description of the copied document gathers the description of the action definition, but how can you pass the description of the previous document for instance? Is this also done via the actual parameters?
Thank you,
Sebastiaan. -
Repricing the SAP contract generated from follow up doc in copy control
Hi,
I am facing issue with the conditions copy at item categories level at the time of follow up document in copy control.
The challenge is like this:
There is an option for the conditions copy for line item level upon which the corresponding pricing is generated.
D -- Copy all Conditions
C -- Copy manual conditions
The issue here is at config level they will maintain only Copy manual conditions depending upon whether it is a follow-up / Copy it should change the behavior as Copy all Conditions.
I tried to do this with crmv_event(After with reference::50) though but the problem is its triggering after the pricing got generated.
Welcome you ideas to resolve the issue.
Thanks & Regards,
Madhu JHello Ravikanth
With status management it's not possible to prevent the creation of follow-up documents in CRM.
You have to use the badi CRM_COPY_BADI. Here the exception DO_NOT_COPY must be raised. But it's not possible to gray out the path of the follow-up transactions e.g. for 'varian quote'.
I hope this could be helpful.
Best regards,
Maggie -
Hi All,
I have to create folow up transactions automatically when quotation gets approved. My question is when we create a follow up transaction automatically through Action Profile is it required to have copy control settings or not?
Thanks,
Raothe idea of using copy control would be to copy the data as needed from the base transaction so that your follow up transaction data is consistent. You need to check your requirement and find attributes that needs to be copied over before you determine this.
I hope this helps.
Thanks,
Aparna -
Credit Memo Request (Copy Control)
Hi everyone. Can anyone give me a hand, please?
I would like to send an error message if a end-user is trying to create a Credit Memo Request (tr:VA01) with reference to a billing document which has been cancelled (tr: VF11) already. Actually the system let me do that, but the client doesn´t want to support it anymore.
Thanks in advance.You can maintain the Same in the Copy Control between Billing Document to Sales Order in a Routine that if VBELN in VBRK - FKSTO is "X" ,do not allow to maintain / Save the Sales Order.
Best Regards,
Ankur -
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 advanceHello 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 from quotation to sales order
HI ,
Though my quoation is incomplete it can be copied into sales order, kindly suggest me a so;ution where in incomplete quotaion cannot be copied into sales order.Kindly explain me teh setting in TCODE (VTAA) STEP BY STEP.
Regards
Sunainahi,
Copying control for sales documents is in Customizing, under Sales and Distribution - Sales - Maintain Copying Control for Sales Documents.
In this you can change the procedure by not selecting incomplete quotation for sales order, but this can be done only when some of the data in quotation is missing.
like dont give the validity date in quotation and save it before providing the validity date.
Maintaining an Incompleteness Procedure
An automatically-created quotation does not contain a Quotation-valid-to date. The customer's system requires this information for processing; therefore you have to add it to the quotation prior to saving the document, and before generating the message to the customer.
The incompleteness control is set up in such a way that the quotation is incomplete if this date has not been entered. In Customizing for Sales and Distribution, you choose Sales and Distribution - Basic Functions - Incompleteness Control for Sales and Distribution Documents, to assign sales document type QT (quotation) to incompleteness procedure 10, which contains the field for this check.
Message Control
The following message types have been created to Sales and Distribution (SD) in the vendors system:
· Message type AN00 for the quotation
· Message types POST and PNST for status inquiries
· Message types BA01 and BA02 for the order
confirmation and amendment respectively
· Message type LALE for the delivery
· Message type RD00 for the invoice
regards,
Siddharth. -
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. -
How to delete a Item line in a Sales Order during Copy Control
I want to delete a Line item (VBAP ) record for a certain condition during Copying from reference . I am writing the code in the Data Transfer Routine 151 which is called through VOFM Transaction . I cannot delete it as it . it is a work area VBAP . When i Clear it in debugging i am only able to clear the Line items . I want to completely remove the line . Is there a user exit for the same .
Hi,
You should create a new copy requirement routine at item level in order to exclude the unwanted item.
Assign the requirement routine to each item category type in the copy control .
Regards,
Andrea
Maybe you are looking for
-
hello does anyone knows how to re-enter the decimals for the tempo cause i only have a full number and can't enter a decimal number ?
-
Trouble with linking buttons within an mso, to another mso.
Im trying to set up buttons nested in an mso to link to a graphic within another mso. I cant seem to find a work around.. has anyone encountered this problem/ have a work around? Thanks -LK
-
Date sort is broken in the Organizer
The date sort in the Organizer only seems to support the calendar date, not date and time. If there is only photographs from 1 day in the organizer there is no way to sort the pictures earliest to oldest, because the date sort doesn't include time. D
-
Can't upload photos to facebook from phone. Out of no where!!!!
I was posting pictures to facebook with no problems and then about a month ago I tried to upload a photo from my BB Curve after loging on to facebook and facebook told me that "your browser does not support photo uploads" Can someone help please!!!!
-
Target location vs control center
Hi, We installed OWB10gR2. In R2 we have control Center Manager to deploy the objects. We can create different control centers in connection explorer. In project explorer configuration we can set which control center is deafult one. Up to that we did