Copy control transport orders
Hello Gurus:
Quickly question: How we can modify the copy control between transport order and deliveries?
I want add a conditions to copy the values of the field between the transport order and the delivery.
Thanks in advance
javier
Hello Javier,
If you are using SAP version 4.7 or below then you could configure it via OMGN.
or if you are using ECC 6.0 ( I believe even 5.0 ) then you need to manually Browse from SPRO>MM>Purchase Order--> Set Up Stock Transport order.
Here u can setup all the relevant config pertaining to Transport orders.
thanks
Murtuza
Similar Messages
-
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 invoice - order - KDMAT will not be there
Hi Experts!
we create customer orders (in this case credit notes) with reference to an invoice.
the problem is that the field vbap-kdmat is empty in the copy control and so it could not be filled into the new order.
in VTAF we use the copy requirement 153 Item from bill.doc.
in the PO tab of the invoice the customer material is filled (manually)
We don't have set up information in VD51 but we fill the customer material with some information and this should be copied into the returns.
does anyone have an idea how to get the copy control working?
I tried to change the 153 to 151 where the source says:
vbap-kdmat = cvbap-kdmat.
but without the value in vbap (it is empty while executing this code) the field will remain empty.
Thank you in advance
Regards
Daniel Hermannhi
billing level PO tab customer material number comes through order , here table also VBAP, so actually this PO tab all fields are display mode only ,
when enter the sale order item PO tab level enter the customer material number , then pass to same billing level ,
when billing level you enter manually this data fet at VBAP table only ,
so you assign the copy routine 151 then on kdmat copy billing to credit memo order OR we maintain same kdmat in main order its copy to billing then also copy credit memo also
do this
regards
sankar -
Copy control Returns order to invoice or sales order
Hi all,
we are using Sold-to's with a variety of partners and partner types of which all are not being used in the sales order.
Unfortunately when we create a returns order in refernce to either the original sales order or the invoice, we are bing presented with pop ups showing all partners. i.e the original invoice does not have a special partner we use (ZF) but when we create the returns order we are being asked to pick this partner or if there is only one it is populating the partners.
We do not wish this to happen we wish only for the original partners to be copied, i.e. no additions and no requests for us to pick one if there is more than one.
Can anbody advise on copy control settings to manage this we have tried various options but none have worked.Hello Greenbum
1) You can use your own copy routine in the header ( Copying Control: Billing Document to Sales Document) where for Copying requirements for partner data VBPA- the bottommost Data Transfer routine- you may copy and modify routine FV45C001.
If the above does not work
1) Assign a Partner Determination Procedure with only requisite Partner functions to the 'Return' Order.
2) In the procedure, populate the 'Origin' filed for all the partner functions with X, Y or Z and devise user exit for partner determination- EXIT_SAPLV09A_003.
Let me know how it goes. -
Copying Control from Order to Order
Hi Gurus,
I need your help.
I need to copy Order from Order Document Type on Propose Item on Order Update (VA02). When I do this, the manually inputted pricing conditions was not copied. On VTAA, I already change the value of Pricing Type from A->C, then D,E,F,G, and M but seems no help at all. I hope you can help me.
Your help will be highly appreciated.
Thanks,
Mon MagallanesHi,
Maybe I need to state my problem so that you can help me easily.
Our scenario is there are two persons that will transact the Order. One officer (Officer 1) will create the Order, input the quantity of the items and manage the price of every item. Another officer (Officer 2) will modify the order to input the storage location but no capability of modifying the price. Officer 2 has the capability to split the items on the order so that he can manage where storage location will the items be assigned.
Example:
OFFICER 1
Items Quantity Storage Location
Product1 5 __________
Product2 10 __________
OFFICER 2
Items Quantity Storage Location
Product1 2 1100
Product1 3 1150
Product2 4 1100
Product2 5 1150
Product2 1 1170
Officer 1 declare the price and Officer 2 put the storage location without access on the price. What I'm trying to do is to propose item on the same order so that the items will be duplicated. But my problem is in the condition tab per item, the condition type that has manually inputted (mark ups, additional price plus) on price where not copied. Only the prices that is maintained on VK11 is copied. Is there any work around with this problem? I tried to use the batch split in the outbound delivery for the officer 2 but our QM module is inactive.
I hope you can help me with this.
Thanks,
Mon Magallanes
Edited by: Mon Magallanes on Oct 29, 2009 10:33 AM -
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 -
Copying Control: Sales Document to Sales Document delete
hello all,
I want to prevent users to create a sales order refer to another sales order.
They always do that in my company, so we have a big document flow and proces are most of the time false :-(.
I'm a junior in customizing and I htought I can delete the copying control between my sales order type to sames order type.
What do you think about it? what can be the impact?
thanks for your help!Dear Swiercz,
There is no harm in Deleting Copy control between Order type to Order type, provided you are sure that either of the Order type would not be used to create other Order type.
Alternatively, in you copy control settings between Order types, you can delete all the Item Categories that are listed under Item.. This would make sure that no data is copied from one document into other...
Hope this helps...
Give points if useful...
Thanks,
Jignesh Mehta
Mumbai, India
091 98700 10230 -
Hi experts,
I want to copy pricing elements unchanged from order to billing for this I have maintained pricing type " D - copy pricing elements unchanged in copy control from delivery to billing at item level.
Still the system is carrying out new pricing in billing
I have also tried by maintainining copy control from order to billing
Can anyone guide me for these ????Please check whether u have maintained any different document. procedure in billing type screen (VOFA).
Also check at OVKK screen, u maintained a different combination for the different document pricing procedure.
If u maintained any diff doc. procedure in VOFA screen, please remove and see.
do reward points if it is useful -
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 -
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. -
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 -
Copy control for Text in Sales Order
Hi All,
i would like to check with you guys.
I have a scenario where by, we create sales order and maintain item text. This is copied to the delivery. Here the text if modified to enter more text.
But when it comes to invoice, it is copying the text from the sales order instead of the delivery.
How can I configure it to copy from delivery?Hi,
Kindly check the following points:
1) Same text ids are present at Delivery item & Billing Item.
2) It at you want it at Item level text only then try through the ABAP routine at Copying Control between Delivery to Billing.
3)As u must have checked at Delivery --> Billing Document Copying control at item level , I didn't find any control for text.
Similarly for the Header. But by default Header text will overlap the item text as well due to the missing routine. But I have verified it in the past, if you maintain the same text at Delivery Header and it will populate at your billing document Header text as well.
Please try and confirm the same.
Thank You,
RB. -
Copy control routines in Sales Order and Debit Memo Req.
Hi,
I have a scenario wherein, I am creating a Debit Memo Request with reference to a Sales Order. DMR(Debit Memo Request ) & SO (Sales Order)will not be created on the same day. I want to have Pricing date in the DMR (both at item and Header level) as current date and dont want it to be copeid from SO.
Can it be possible with the standard available routines in copy control between SO and DMR? IS there a need for creation of separate routine.
Thanks.Hi,
As per the business requirement it is ok to change the Pricing since based on the pricing date the Exchange rate is calculated.
The exchange rate at the DMR level should be calculated on the date of creation of DMR and so the pricing date from the Sales order should not be copeid.
Any suggestions pls. -
051 routine between sales order and delivery copy control
Hi,
The copy control routine 051 in copy control from sales order to delivery defines four combination criteria.
1) delivery types same in config of sales doc type
2) sales org same of the sales orders
3) delivery indicator same
4) billing type same as defined in sales doc type.
my question is if i have the follwoing copy control defined between sales order and delivery :-
sales del sales deliv bill routine
order type org agreement type in copy ctrl
type
ZOR ZLF 1000 SAME ZF2 051
ZTSD ZLF 1000 SAME ZF2 051
my question is how will the routine combine all the sales doc type into a single delivery. my confusion is since the rotuine is attached to every combination of sales doc type and delivery type in copy control, how will the routine identify that it has to combine the sales doc type ZOR and ZSTD into a single delivery.
one of the statements wriiten in routine 051 is that " check sales org is same for all document ". does this mean that the routine will identify sales orders with doc type ZOR only if the routine is attached in config for copy contol between zor and zlf and i remove the routine for copy control belwteen zstd and zlf.
regards
sachinSales order is the order from your customer and delivery is when you are delivering the item.
Shipping: In general when the item is dispached from the warehouse, we can say the item is shipped,where as delivery is item/product reaching to the end customer.
Hope it helps,
Kiran -
Copy control from Sales Order to Purchase requisition
Can any one guide me how to set this, which fields need to be copied from Sales order to Purchase requisition.
VasuI don't think so sap has provided this kind of control but you can configure certain things as item category level for thirdparty in SD
SPRO-SD-sales-sales document-sales document item-define item categories
here you can check for item category TAS or you can create your own
Maybe you are looking for
-
LabVIEW hangs while writing to unavailable network Drive
Hello, I am trying to write data at the end of my test sequence run to a file and storing it on a network drive. If there is a problem with the network drive (busy or disconnected), then my application hangs for around 10-15 secs before giving out er
-
1680X1050 Resolution for external display is not an option in Lion?
I am using a DVI to mini DVI connection on my MacBook Pro and did not have this problem with Snow Leopard. Is there anyway I can get this resolution as an option?
-
Dear fellows I would like to change color appereance in the 3d picture control as the program runs, how can i do that. As far as i know in 3d picture control you can only change the color and alpha during making the object if you are using primitives
-
Need clarification: SCJP questions
The following code when pasted in eclipse is giving a compilation error but the answers are as given below!! Please explain. Question 1 Given: 11. static classA { 12. void process() throws Exception { throw new Exception(); } 13. } 14. static class B
-
plz tell me how i can get oracle project i.e sample project or demo projects so that i can have an idea............... plz help.................... thanks