Invoice correction - Copy control

Dear experts,
Users want to use SAP standard invoice correction requests.
The only change is on the sign of the item values.
The 1st one copy of G2n should have negative value whereas the second, copy of L2N, should be positive.
I tried to change the copy rules between the invoice F2 and the IC doc: the 1st pricing type which must be E and not F (470 release).
Is there any standard way to change this process?
Thanks in advance for your help
xPlo

Hi,
We finally changed the SD document category for the invoice correction request.
It was iniitally K for credit note request and turned into L for debit memo request.
Then, the copy rules from billing to sales document could be updated as required.

Similar Messages

Invoice To Service Order - Copy Control

Hi All,
I have a business requirement where in as soon as invoice is generated for sold product, a service order should be created for installation and demo. I am using copy control option and for target trnsaction type i have checked the option complete reference without any routine. To copy certain fields i believe i need to write a routine but With options 'Copy Item number' and 'Complet reference' do i get item level details without mentioning in routine program.
Kindly guide how to creae follow from invoice using copy control.
Many Thanks in Advance !!
Regards,
Abhishek Sandhir

Hi Abhishek
I have few queries just to understand the process you are following
1. You are creating your sales order/ invoice in CRM or ECC?
2. Do you want serial number / Component/Ibase information on the service order? If yes then do you have this information on your sales order.
Regards
Naresh

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

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

Billing Copy control-invoice split by material document

Splitting the invoice based on the material Document(ekbe-belnr). Suppose i have 3 material documents for one Purchase order. Based on the 3 material documents, it shpould create 3 invoices. So for this i created a routine. Its for billing document copy control. But my routine is combining all the material document quantities and it creating only one invoice but i required multiple invoices based on no of material document. i wrote code like this. Its urgent..
FORM daten_kopieren_901.
TABLES: kna1.
DATA : v_kunnr TYPE kunag,
         v_katr2 TYPE katr2,
         v_belnr TYPE ekbe-belnr,
         v_bewtp TYPE ekbe-bewtp.
DATA: BEGIN OF it_zuk1,
            modul(3) VALUE '904',
            vtweg LIKE vbak-vtweg,
            spart LIKE vbak-spart,
            belnr LIKE ekbe-belnr,
            vgbel LIKE vbrp-vgbel,
        END OF it_zuk1.
TYPES:BEGIN OF t_ekbe,
           belnr TYPE ekbe-belnr,
           bewtp TYPE ekbe-bewtp,
           flag TYPE c, "Rajiv
        END OF t_ekbe.
TYPES:BEGIN OF t_vbap,
           vbeln TYPE vbap-vbeln,
           posnr TYPE vbap-posnr,
       END OF t_vbap.
TYPES:BEGIN OF t_vbep,
             banfn TYPE vbep-banfn,
          END OF t_vbep.
TYPES:BEGIN OF t_eban,
            ebeln TYPE eban-ebeln,
            ebelp TYPE eban-ebelp,
        END OF t_eban.
STATICS:i_ekbe TYPE STANDARD TABLE OF t_ekbe.
DATA: wa_ekbe TYPE t_ekbe.
DATA: i_vbap TYPE STANDARD TABLE OF t_vbap.
DATA: i_vbep TYPE STANDARD TABLE OF t_vbep.
DATA: i_eban TYPE STANDARD TABLE OF t_eban.
SELECT vbeln posnr FROM vbap INTO TABLE i_vbap
                          WHERE vbeln = vbak-vbeln.
IF sy-subrc = 0.
    SELECT banfn FROM vbep INTO TABLE i_vbep
                    FOR ALL ENTRIES IN i_vbap
                     WHERE vbeln = i_vbap-vbeln
                     AND   posnr = i_vbap-posnr.
ENDIF.
IF sy-subrc = 0.
    SELECT ebeln ebelp FROM eban INTO TABLE i_eban
                    FOR ALL ENTRIES IN i_vbep
                     WHERE banfn = i_vbep-banfn.
ENDIF.
IF sy-subrc = 0.
    SELECT belnr bewtp FROM ekbe INTO TABLE i_ekbe
              FOR ALL ENTRIES IN i_eban
                   WHERE ebeln = i_eban-ebeln
                   AND   ebelp = i_eban-ebelp.
endif.
LOOP AT i_ekbe INTO wa_ekbe WHERE flag NE 'X'.
    IF ( ( wa_ekbe-bewtp = 'E' ) OR ( wa_ekbe-bewtp = 'R' ) OR
                                        ( wa_ekbe-bewtp = 'Q' ) ).
      it_zuk1-vtweg = vbak-vtweg.
      it_zuk1-spart = vbak-spart.
      it_zuk1-belnr = wa_ekbe-belnr.
      it_zuk1-vgbel = vbrp-vgbel.
      wa_ekbe-flag = 'X'.
      MODIFY i_ekbe FROM wa_ekbe TRANSPORTING flag.
      vbrk-zukri = it_zuk1.
      EXIT.
    ENDIF.
ENDLOOP.
REFRESH: i_vbap,i_vbep,i_eban,i_ekbe.
ENDFORM.

Hi Ramana,
I'm afraid this is not possible. Correct me if I'm wrong: You have a TPO scenario in which you create a purchase order for a sales order item. This purchase order may have multiple GR? As billing is based on the sales order position (which is only one) there is no way to split this one position into multiple lines for each GR. This would only work if there is a 1:1 relation between sales order item and GR!
Regards,
John.

No Copy controls between cash OBD to cash Invoice

Dear Gurus,
I am doing Cash sales.
Sales order: ZOBV
OBD: ZDBV
Invoice: ZBBV
In Delivery copy controls, I could link ZOBV to ZDBV, but in Billing copy controls I am not finding my OBD to Invoice copy controls. So I wanted to copy BV to BV and change it to ZDBV to ZBBV. Since there is no BV to BV copy control existing, I want to copy normal LF to F2 and change it to ZDBV to ZBBV.
Is this OK / correct??
If not how should my copy controls be??
Plz help me out here.
Thanks and regards with rewards.
Venkat - Hyd

In Cash sales the billing is order related billing. Therefore, delivery is immediate and bill happens afterwards, so, it ought to be order related billing. Thats why you would not find any Copying control between Delivery and Billing.
Take care. JP

How to determin the pricing procedure in copy control from invoice to so

Hi,
I have a request to create a sales order reference to a invoice. But in SPRO pricing procedure determination,i config different pricing procedure.
e.g. invoice ---procedure A
sales order-----procedure B
when i create the sales order , the procedure is A which is copied from invoice ,but i hope the procedure is B.
how should i config the copy control. I have tried the B and C in pricing type of copy control.
Thanks

HI
Try to maintain Different Document pricing procedure in Sale Document type and Billing type
and also maintain settings in OVKK and test the cycle
check and revert
Regards,
Prasanna

Copy control from Invoice to Credit Memo request

Hii All
We have a requirement where when we create an credit memo request with reference to the invoice we want that PO number in the invoice should be copied to the credit memo request.
Can this be done through copy control or some user exit needs to be implemented for the same.
Pls do let me know.
Thanks & Regards
Gaurav Manocha

What are the Routines & Copying Requirements being maintained in the Copy Control from Billing Document to Credit memo Sales Document Type.
It should be Billing Document Header "052", Billing Business Header Data "103'. Copying Requirements should be "021".
Kindly check and revert back.
Best regards,
Ankur

Copy control from Invoice to Accouting

Hi All
We have a requirement where when we create an accouting document with reference to the invoice we want that one partner number in the invoice should be copied to the one field in the accouting document..
Can this be done through copy control or some user exit needs to be implemented for the same.
Thanks in Advance,
Regards,
Shaju
Edited by: shaju tv on Jun 16, 2009 5:08 PM

Hi Rajeswari,
Thanks for your reply.
It is not related to bill booking.
I wanted the value in partner function data of the billing document to be flown to accounting document line item field XREF1.
Can you please suggest some idea ?
Thanks for your help.
Regards,
Shaju

Copy Control Invoice - Debit Memo

Dear All,
I have some typical problem when i creating the debit memo request with reference to Invoice.
I have BOM Material in the Invoice i.e. with 2 sub items
M001 TAQ
S001 ZCRD
S002 ZCRD
i set the copy control to from Invoice to Sales document -- Item category
If it is TAQ copy as L2W
And ZCRD as L2W also
But when i try to create the Debit memo request it is copying TAQ as L2w but not ZCRD as L2W it is copying same as ZCRD..
Where ZCRD is is relevant for delivery so i didnu2019t want this item category to be copied can any one suggest why it is doing that???
Thanks
Sundhu

Did you check Item category assignment?
Sub items in BOM have different item category group (in material master record) and it appears you did not properly assign it.

Copy control for invoice list cancellation

Hi Friends,
I wish to maintain the copy control for invoice list cancellation, as the case study as follows
My client maintain invoice list, but due to certain reasons ,one of the invoice from invoice list has to cancel , the error I am getting as "Sales document F2 cannot be invoiced with billing type LRS."
Also , explain as to what fields need to maintain in copy control for the same.
Kindly help me at the earlist
Thanks in advance
Shailesh

Hi
As far as I know, invoice cancellation or invoice list cancellation is not done by copy control. or...that is the one and the only document in SD which can be created without copy control.
I think it is only sufficient if you include the cancellation document type in the invoice list type in the configuration of Billing document types.
I think that alone should solve your problem.
Reward if this helps you.

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

Consolidate Invoice - Copy Control Routine_VF01

Hi All,
Billing type eg: ZZYY is used to create a consolidate invoice, collecting all the shipments of a previous period of time.
The copy control routine (Ex:915) is now set up to copy requirements between delivery type LF and billing type eg: ZZYY.
The consolidation needs to happen for 'Bill To' only.
Every thing else needs to be excluded.
The routine already works for some criteria but it does not exclude yet:
·     Carrier
·     Destination country (of ship to)
·     Region (of ship to)
·     Foreign trade number.
Now I want to consolidate the Invoices based on 'Bill To' only and I want to remove the Cosolidation of invoices for the above mentioned 4 parametes.
Points Assured.
Reagrds,
Viji

Using of Clear statement. this was done.

Copy control - Order to Invoice

User wants a field to copy over from sales order header to the header field of credit memo and debit memo when they are created with reference to an order.
They also want that field to copy over to the invoice irrespective of whether the invoice is created with reference to order or delivery.
I was able to do the first part by making changes in the routine used in copy control of sales order to sales order. However I'm not able to do that 2nd part as this field is not passed on to the delivery doc. Any suggestions?

Hi Carrie
simple now that you have clarified
In the copy control settings for billing, delivery to billing ( LF to F2) select "a" for the refrence number field - this will automtaically move the customer PO number as required by you at the time of billing
please test in develoment once and then move to production
cheers
nandu
note: you may get multiple answers now for this

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 Hermann

hi
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

Invoice correction - Copy control

Similar Messages

Maybe you are looking for