Copying control problem

Dear All,
When i am creating a debit memo and credit memo with reference to invoice, system pop up a message which is given below
Item 000153: Batch expires on .
Not only item i have around 40 material which is not copied due to this reason.
Kindly advice me where should i check.
Thanks a Lot !
regards
ajit

Hi,
From what Item category of invoice are to trying to create the debit memo request? What is the item category that is being determined in the debit memo request and credit memo request?
My guessing is that the item categories that are getting determined in debit memo request and credit memo request have "Automatic Batch Determination" tick on in General Control of Item category configuration. This needs to be changed.
Two ways that I can think off are
a. Go to copy control for billing documents to sales documents (Tcode: VTAF). Select your source document type (Invoice type) and Destination doc type (Debit/Credit memo type). Go into the item category. Now, select the item category of the invoice from which you are trying to copy. See whether system has to propose it or if there is an item category already there.
If the item category is already there, then, you need to go to item category configuration (sales and distribution > sales > sales documents > sales document items > define item categories) and check if "Automatic Batch Determination" is ticked on in General Control. If yes, then you will have to remove it. Save and transport to your prod system.
If item category is not present, then, you will have to then check item category determination (sales and distribution > sales > sales documents > sales document items > Assign item categories) to see which item category will be determined. Then follow the above said procedure to uncheck the "Automatic Batch Determination".
b. In case a is not true, then, you will have to check what is present in the copy routine. You may also have to check the user exit that may have been used in the sales order while creation. You will have to take ABAPer's help for the same.
Hope this helps
Thanks
Mukund S

Similar Messages

Copy control problem : Delivery to Billing

Hi Guys,
I am facing a strange problem regarding copy control between delivery and billing document. The case is as below:
When I am creating an F2 Invoice from LF Delivery the header texts from the LF Delivery is getting copied into the header taxt of F2 Invoice but this is not working when I am creating a F8 Proforma Invoice from a LF Delivery. The thing is like this LF-F8 copy control was working fine before couple of days and now it's not at all working. I am bit surprised to see this as these document types are Standard SAP document types !!!
Can anyone advice regarding this particular issue?
Hrishi

Hi,
Check your Copy Control Settings for
Taget Doc.: F8
Source Doc.: LF
in T. Code: VTFL
For Header Settings:
Maintain Field: Copying requirement - 009 - (DlvRel.pro forma hdr)
and Check Box: Copy Item Number
For Item Settings:
Select your Item Category (say, TAN - Standard Item)
Maintain Fields:
Copying requirements   010 DlvRel.pro forma itm
Data VBRK/VBRP         000
Billing quantity     D
Pricing type         G
Hope, this may Help.
Best Regards,
Amit.

Copy control problem

When creating a credit memo (sales document) from billing document, we have pricing type set up as N (N = Transfer pricing components unchanged, new cost ) in copy control (tcode VTAF ) .It means when you create a credit memo from billing document it copy pricing from billing document, but in our case it is not copying ,it is redetermining pricing for the credit memo.
Whats step should I check to avoid this?

As already suggested, it should be 'D', as it copies the pricing elements unchanged with automatically determined or manually entered surcharges and discounts from the reference document (scales are not read again). This means that the value remains unchanged even if the billing quantity is different to the order quantity. Also, it does not redetermine the taxes
Regards,
gauravjit.

Hi all , problem in copy control from billing type f2 to debit and credit

hi all,
i have a problem in copy control from billing type f2 to debit and credit memos,
could any body advise me the procedure for this issue ,
thanks ,
sre

Hi sre,
It is better to copy f2 to DR or Credit memo request
for that you have to maintain copy requirement 21
                                           Billing doc.header 52
                                           Bill.bus.header data 103
                                           Bill.header partner 3
and for item you maintain copy requirement 303
from dr. or credit memo request you can able to do Document type G2 and L2
i think this may give some idea
regards
bvdv

Problem Copy control Order to Invoice

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

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

Problems with bill copying control and materials with variant configuration

Hi experts,
I have a problem with a bill copying control and the way that my customer is trying to create and print the Bill (VF01).
Let me explain...They have in a Sales Order a material with variant configuration per position, each one can have many characteristics. This characteristics must be printing on the billing document, creating different bills 'coz the max. lines number is 18, so the bill must change page per material-characteristics.
Example:
Max. Number Lines = 3
Position 10
Material A
     -Characteristic A
     -Characteristic B
     -Characteristic C     (Bill 1)
     -Characteristic D
     -Characteristic E
     -Characteristic F     (Bill 2)
Position 20
Material B
     -Characteristic A     (Bill 3) counting characteristics upside
     -Characteristic B
     -Characteristic C
     -Characteristic D     (Bill 4)
I created on Tx VOFM (Data Transfer-Billing documents) a routine trying to control this jump, but my problem is when I'm creating the Bill document (VF01) this work only by position, the debugging enter per position.. so I don't have any control to tell the program must count the characteristics and create another bill.
So... Somebody can help me..or have any idea to solve this problem.....
Thxs a lot!!!!
Diego Helfer

HI Diego
For our coming assignment, we do have similar sort of situation. Currently we are in Requirements Gathering phase.
Though we do not have Variant Configuration in place, we do have restriction for no..of items to be used for printing in Billing Documents.
Current proposal is that we will restrict at Sales Order Creation. If the number of items are increasing, we will restrict saving the document and loading has to be done again. As itz better to restrict at initial phase.
Our schema is One Sales Order -> One Delivery -> One Billig Document.
   Will post if we can manage to acheive some other way and do request you the same.
Kind Regards
Eswar

Problem with copy control from sales document to billing document

Hi,
I have a copy control from a sales document to a billing document,
which is copying everything from the sales document, except the
conditoin values. Any ideas on why will a copy routine won't copy the
condition values from a source document? I don't even have a document
pricing procedure assigned to my billing document. Any setting, that
we can do to for the conditions to get copied from the sales document
to the billing document...just as they are in the sales document?
Thanks for the help in advance.
Regards,
Vijay

In IMG,
Implementation Guide for R/3 Customizing (IMG)
-->Sales and Distribution
   -->Billing
      -->Billing Documents
         -->Maintain Copying Control For Billing Documents
            -->Copying control: Sales document to billing document
What setting do you have for your source sales document type to target billing document type? Select the row that shows the document type you are interested in and double click on item(on the left pane). Select the item category and do display. What value do you see under the 'Pricing Type' and 'Price Source'?
May be that is where some config setting is missing.
Srinivas

Problems in Copy Control Setting for Collective invoice..

I need the invoice which combines different deliveries provided the sold to party is same and the delivery date is same. Right now I m using standard routine 11 in the copy control which splits if the purchase order is different or the city code is different. So I need another routine which should remove the splitting criteria.
            The required splitting criteria should be
            1 Different Sold to parties
            2- Different Delivery date
            3- Different Plant
Otherwise it should combine the deliveries into one invoice.
Regards,
Subho

Hi Subhasish,
It's not just ZUKRI - it could be any field and since 011 does not form ZUKRI it isn't in your case. What I'd suggest is:
1. Create your own Data Transfer Routine as a copy of 011.
2. Assign it in VTFF.
3. clear fields that create a split
Also check partners, because the city code, must come from a partner which is assigned to the header. In case this is unwanted, assign this partner function to item procedure, rather than the header and you'll avoid the split.
regards,
Stratis

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!
Yolanda

Try 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

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 J

Hello 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

Copy control in contracts

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

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

Does anybody know table for copy controls from Sales document to Delivery

Hi,
Does anybody know table for copy controls from Sales document to Delivery. Especially for item level.
Regards,
Praveen

>
Lakshmipathi wrote:
> Almost all members know copy control from sale order to delivery. What exactly your problem is ?? Please post that and avoid asking questions like this !!!!!!!!!!
>
> thanks
> G. Lakshmipathi
Sorry for my post. I guess you were a wee bit quicker than me in the reposnse

Copying Control Fields are disable in SAP SD

Hi Friends,
I am having problem with copying control in SAP SD. While using T- Code VTAF, VTFF etc for copying control, I found all the standard fields are disable but I am able to do all the sale processing. Therefore me doubt is; when there is not even a single field is available in the copying control then how I am able to run all the activities. If these are hidden and maintained in background then how I can able to see the existing fields in copying control. Please reply as soon as possible and clear my doubt. I shall be great thankful to you for this.
Regards,
Bharat B

Hi Frank,
Thanks for yours kind response to my doubt but the question is still not solved. as i already explain in my question that the available standard fields are disable means they are not in display mode, else these are hidden/invisible, so please try to give me the appropriate answer for that..and one more thing i want to add i.e. standard fields means..the values avialable for source fields and target fields as per the sap standard..as there is no copyning control existing in the system..For instance; copying control from OR to F1, F2 etc, LF to F1, F2 etc are not shown in the system but i am able to process all the sales activities like sales order creation, Delivery Document and Billing Document creation, so i know that stuff that if the copying control is not available then system won't be aloww me to do the single transaction for sales processing..I know this is bit time consuming and cofusing too but i am having faith in YOU. I think now you have understood my problem..so please provide me the solution for that. I shall be great thankful for this.
Thanks and Regards,
Bharat B

Copying Control Fields are disable

Hi Friends,
I am having problem with copying control in SAP SD. While using T- Code VTAF, VTFF etc for copying control, I found all the standard fields are disable but I am able to do all the sale processing. Therefore me doubt is; when there is not even a single field is available in the copying control then how I am able to run all the activities. If these are hidden and maintained in background then how I can able to see the existing fields in copying control. Please reply as soon as possible and clear my doubt. I shall be great thankful to you for this.
Regards,
Bharat B

Hi Friends,
Thanks for yours kind response to my doubt but the question is still not solved. as i already explain in my question that the available standard fields are disable means they are not in display mode, else these are hidden/invisible, so please try to give me the appropriate answer for that..and one more thing i want to add i.e. standard fields means..the values avialable for source fields and target fields as per the sap standard..as there is no copyning control existing in the system..For instance; copying control from OR to F1, F2 etc, LF to F1, F2 etc are not shown in the system but i am able to process all the sales activities like sales order creation, Delivery Document and Billing Document creation, so i know that stuff that if the copying control is not available then system won't be aloww me to do the single transaction for sales processing..I know this is bit time consuming and cofusing too but i am having faith in YOU. I think now you have understood my problem..so please provide me the solution for that. I shall be great thankful for this.
Thanks and Regards,
Bharat B

Copy controls & Pricing

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

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

Copying control problem

Similar Messages

Maybe you are looking for