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

Similar Messages

CRM Copy control: CRM_COPY_BADI for document relationship

Hello!
I need CRM copy control from an opportunity to another opportunity. The implementation of badi CRM_COPY_BADI should include document relationships: target document should be related to the same documents linked in the source document.
I cannot find a method to do this.
Please, could anyone suggest me a solution?
Thank you.
Kind regards.
Elena

Hello Elena,
Please follow the steps below:
1) Go to transaction CRMV_EVENT
    Click on "Object Function/Callback" button
    Create a new entry with following values:
    Function Module: ZCRM_DOCFLOW_COPY_EC
    Object Function: CRM_DOC_FLOW
2) Go to IMG Path: Customer Relationship Management -> Transactions -> Basic Settings -> Edit Event Handler Table :
Here create a new entry with the following details
Trans. Category       BUS2000111     Opportunity
Execution Time        1                                Immediately
Priority                    99
Object Name            ORDERADM_I                       Administration item
Event                       AFTER_CREATE_WITH_REFERENCE
Attribute                   <*>
Function                  ZCRM_DOCFLOW_COPY_EC
Perform Function for Doc.Header = "Checked"
Perform Function for Document Item = "Checked"
Call Callback = space
3) Create function module ZCRM_DOCFLOW_COPY_EC with the following signature:
*" IMPORTING
*"     REFERENCE(IV_STRVAL_OLD) TYPE ANY OPTIONAL
*"     REFERENCE(IV_STRVAL_NEW) TYPE ANY OPTIONAL
**Code:
DATA:
FIELD-SYMBOLS:
          <ls_orderadm_i_wrk> TYPE crmt_orderadm_i_wrk,
          <lu_orderadm_i_wrk> TYPE crmt_orderadm_i_wrk.
ASSIGN iv_strval_new TO <ls_orderadm_i_wrk>.
ASSIGN iv_strval_old TO <lu_orderadm_i_wrk>.
4) Now in this function module you can read the docflow of old opportunity (<lu_orderadm_i_wrk>) using 'CRM_DOC_FLOW_READ_OB'
Build the new docflow entry for the new opportunity and call 'CRM_DOC_FLOW_MAINTAIN_OW'
Please let me know if any questions.
Thanks,
Sandeep

CRM Billiing document not posted in Accounting

Hi Experts,
Issue:
CRM Billing documents not posting to FI.
We idenfied while debugging in middleware we identified that, Billing document header data doesn't contain value for "Component for RW interface"(COMPO_ACC).
Where we need to maintain/configure value for this field in CRM/ECC, please provide me details.

Is this a case of data migration to new GL.
FAGL_SPLINFO is the table which gets updated for the split information at the time of document posting. If its from migration, please check that the referred RV document is an open item and was migrated correctly.
Thanks and Regards,
Mamta Sarda

Possibility of creation of Master Contract through Copy controls not direct

Hi,
Our requirement is to create a Quantity Contract from opportunity through copy controls. At the same time the system should not allow to create a Quantity contract directly through the transaction code crmd_order.
Is there any way to block the creation directly but allow to create by copy controls.
Thanks in advance,
Venki

hi
what i understood from your requirement is that you do not want to create contract directly,but u desired that its always get created in follow up to the opportunity
then as i told you earlier too,have you did that in customisation of your transaction type
like selecting the option blocked for online mentainance
that way the contract transaction wont be able to get created directly using CRMD_ORDER
but as you wanna create in follow up to the opportunity
so you can select contract as short cut in opportunity transaction type
this way u get ur issue solved
we use BAdi when standard isnt enough to solve the probs,if above customisation doesn solve ur probs then use this BAdi CRM_ORDERADM_H_BADI.
best regards
ashish

COPY CONTROL NOT PRESENT FOR SALES DOCUMENT TYPE DS

I am new beginner to the module SD, i am stuck on the issue regarding copy control
I have created an Schedule Line Agreement and want to copy it to the sale document OR standard order, once entering the number for the schedule line document , i am getting a message the copy control rule does exist for DS to OR.
I have been to the setting for copy control with T-code VTAA but there are many fields that required to be filled up,
Which fields do i fill in ?
I have filled in the fields for item category for OR (TAN) and for DS (LPN).
If i use the copy control with these settings i am getting an error message "The copying routine number for table VBAP is missing in table TVCPA"
Any Help would really would be helpful
Regards,
Sahil

Sahil,
I suggest you close this question, since this is an MM forum. You are unlikely to get many answers here.
I also suggest that you first perform a search, before re-posting this question elsewhere.
First, search within the forums (search box on the upper right of this screen). I just tried a search on 'copy control' and got over 20,000 hits. Surely one of these posts will be able to help you.
Next, check online help. This help is generic, and not generally specific to a particular industry:
http://help.sap.com ERP SD Help starts at
http://help.sap.com/saphelp_erp60/helpdata/en/8c/df293581dc1f79e10000009b38f889/frameset.htm
Next, look for generic solutions in Best Practices. This main Library is
http://help.sap.com/bp_bl604/BL_IN/html/Content_Library_BL_EN_IN.htm
Next look for industry specific solutions in Best Practices:
http://help.sap.com/content/bestpractices/industry/index.htm
If you are experiencing a problem, or you believe that SAP is not working per the online help, you can then search OSS notes.
http://service.sap.com/notes
Next search in one of the standard online search engines (such as Google).
Only after you have performed all of these searches, and studied all of the online help that is supplied for free by SAP, then consider posting a question to these forums. A good SD forum is
SAP ERP Sales and Distribution (SAP SD)
Best Regards,
DB49

New field in CRM datasouce is not replicated into BW datasource

Hello Everyone
I am hoping you will be able to help me. We have created a new field on our CRM Activities datasource CRM_SALES_ACT_1. This datasouce is currently active and we are using a delta update to our BW system. We have added a new custom field to this datasource which is being populated in CRM (I have checked this using RSA7). However, when this datasouce is being replicated in BW it is not bringing across the new field into the datasouce. We replicted the datasources when the delta queue had been cleared down.
Please can anyone suggest what else I can try, Do I have to delete the current initialisations, and then recreate them using initialisation without datatransfer?
We are using BW3.5
Many thanks
Gareth

Hi Gareth,
I am currenlt involved BI 7.o implementation for CRM analytics (CRM 2007). I am working on a UK council project. I am first time working with CRM.
Mainly we have to provide reports on,
service tickets,
Activities,
Survey
ERMS etc..
Can you please provide some design documentation if you have?. Please can you also let me what all masterdata required....
Thanks,
Sudha

Sales doc copy control not working with price condition

Here's the situation.
For OR sales document I have Procedure ZSALES and price conditions Z001
For a QT Sales document I have Procedure ZQUOTE which does not have a Z001 condition in that procedure.
If I create an OR (with the proper customer / matieral) the Z001 populates, based on it's defined record.
If I then create another OR with reference to the original OR, the Z001 populates with no problem.
Up to now everything's fine, now here's the probem......
If I create an OR with reference to a QT, the Z001 does not populate in the OR order.I know there is no Z001 in the QT for it to copy from, but if I do [New Pricing] in the order it still does not come in.(I've tried [new Pricing] with Pricing type A..G)
I have found OSS Note 413066, but this is in reference to 46c systems. we are on ECC 6.0
any ideas ?

Hi Bill,
If PP assigned for both are different it's not going to populate field even if you are redertermining price, since it would be following the PP of Quotation (ZQUOTE), not Sales Order (ZSALES) because it's gonna copy the elements of that PP in order. Are your PP assigned are same or different?
Hope this will answer your query
Regards
SD

Instruction key in an invoice not taken

Hello!
I have a question concerning the instruction key.
I didnt define an instruction key in the vendor master data nor in the house bank.
And i dont want to define this instruction key in the master data, otherwise, it will come each time in the payment run.
Sometimes, we have to use the instruction key and sometimes not, that's why i dont want to define it in the master data.
But i define an instruction key in the invoice document for the vendor.
when i do the payment run, the instruction key of the invoice is not taken into account.
What should i do in order the system takes the insctuction key completed in the invoice document?
Thanks!
Kind regards,
Chiachen

Hi,
We have maintained the Instruction key in to vendor master and while downloading the by using the ACH for Canada, instruction key is missing.
Value is there in REGUH and not there in REGUP, how to get the same in to download file.
Help me on this issue.
Regards,
Satyam

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

Copy control from opportunity to task

Hello,
I want a task to be created with reference to the opportunity, i have maintained the copy control, but yet the account and the employee responsible dont get copied to the task....what can be the possible reason.

You can not use copy control rutines for partner determination. For that you have to use partner determination procedures under spro>crm>basic settings>partner processing. You have to define in your partner determination procedure for account and employee responsible the correct access sequence "1000 - Preceding Document". This is a standard access sequence that copies partner function from preceding document. You can use also some more complex access sequence if you want.
Regards.

PO : Invoice value in ME23N is not matching with 2LIS_02_SCL field BWGEO

Hi Expert,
              1) Invoice value in ME23N tcode is not matching with datasource 2LIS_02_SCL field BWGEO in item level
for few item BWGEO field contain the data with tax but for few item the value is not coming correctly.
2) The value is not matching for that particular item which has same material document in other Item level.
eg. PO(eg 60000XXXXX) if item 1 has invoice value with tax is 1300+52 and its material doc is XXXX1234. if same material doc XXXX1234 is present in
item 2 for another invoice of same material invoice value with tax is 1200+48. In that case the value which is coming in
BWGEO field is 1300 only.
I am working in 7.0 system for AFS specific. My whole transaction is in INR.
Thanks and Regards
Lalit Kumar

Please review the information below from one of our deverlopers
- it may explain the behaviour you are seeing on your system:
When posting a GOODS RECEIPT for a DELTA UPLOAD process you only will
have the information regarding the GOODS RECEIPT values (XMCEKET-WEMNG
and XMCEKET-WEWRT) and not the invoice values (XMCEKET-REMNG and
XMCEKET-REWRT).
When posting an INVOICE for a DELTA UPLOAD process you only will
have the information regarding the INVOICE values (XMCEKET-REMNG
and XMCEKET-REWRT) and not the GOODS RECEIPT values (XMCEKET-WEMNG and
XMCEKET-WEWRT).
The DELTA INIT process is different, because for this process, all
information about posted documents against a purchasing order need to
processed again and this means that all documents related to an order
(invoices, goods receipt, deliver costs, goods issue, etc)
are read from database and rebuild one by one in the same process, and
of course this information in available.
When posting an invoice, the goods receipt information is not
available because of the following reasons:
1 - System standard fields.
In datasource 2LIS_02_SCL, there is only
fields BWMNG - that represents quantity, BWGEO and BWGEO that
represent values. The information under these fields are dependent
from the information of field BWVORG (BW transaction key). This field
determines whether these values are from a purchasing order, goods
receipt or an invoice. You never have a missing information, but when
you want to get goods receipt values, you need to check where the
BWVORG correspond to goods receipt process and not invoice.
2 - Performance
There are documents as purchasing orders and schedule agreements that
are opened for years in some customer system (it may not be your case),
where goods receipt and invoices have been posted during all this time.
Every time that a new document is posted in order to built the
cancellation sentence (ROCANCEL = X) and in order to add the new
value in the old, system need to process all previous posted documents,
and this means processing time. For this reason when posting invoices
only previous documents that are invoices are taken into account and
not goods receipt.
The delta fields, DBWMNG and DBWGEO, are the difference between the
purchasing order quantity and values and the goods receipt quantity
and values, then is natural that this information is only available
when processing a goods receipt and not when processing an invoice.
I'm sorry if this is not the system behavior that you are expecting,
but this is the normal standard behavior and this is really necessary
because of the system performance when dealing with documents that
have a long order history.
Hope this information is useful for you
Best Regards
Barry

Item Pricing date from ref. Invoice not copied into Credit memo request

Hi SAP experts,
If a reference invoice includes several pricing dates on item level
only the first pricing date will be copied into the credit memo request.
Example: Invoice includes three items. First item has pricing date
2007-03-01 and item 20/30 have pricing date 2007-03-03. When creating
a credit memo request with reference to this invoice,
Pricing date 2007-03-01 will be copied to VBKD-PRSDT field
on header/item level.
When the customer has a foreign currency in use, the exchange rate
in the credit memo request will be from 2007-03-01 and not from
2007-03-03 for items 20/30. This is wrong.
Can you help in finding a solution? Copying routines?

Hi,
Yes data transfer routine is the solution for this.You can create and assign a new routine in the copy control at item level for Invoice to Credit memo request.Here you can write the code as to transfer the data of pricing date field form billing document to credit memo request.
This should work.
Reward points if useful.
Regards,
Amrish Purohit

How to remove the Option "Only Refer Excise Invoice "from MIGO

Hello,
We are using the ECC 6.0. while suppose material is excisable then there are Four options will come in MIGO --Excise Invoice tab
1)Only Cature Excise Invoice
2)Only Refer excise Invoice
3)Only Part1
4)No excise Entry
As per my client requirement then only need two options in MIGO.
1)Only Part1
2)No excise Entry
Bcz they want to Capture and Post excise Invoice in J1IEX only...
I have tried from Tax on goods movementIndia-Basic settings--Excise Grp settings..... Here in MIGO settings we can remove the Click from "EI Capture"....Then we will not find the Capture excise Invoice in MIGO. Next How to remove the "Only refer Excise Invoice from MIGO..
Regards
sapman

Hi,
You can capture Excise Invoice w.r.t. PO in J1IEX and then refer it during MIGO (Note: - You are not capturing Excise Invoice again, only referring it) and then Post it in J1IEX.
And in case of Stock Transport Orders, you need to refer the Excise Invoice No at the time of GR in receiving plant which is posted in the Supplying Plant (via J1IIN) so that system will copy all the duties same as of that invoice and user need not to do any manual intervention.
Also in case of Imports, first you capture Bill of Entry w.r.t. PO in J1IEX and then refer it during MIGO and finally post it in J1IEX.

Credit memo -- with ref to invoice

Hello All,
This is my scenario:
1 Invoice with value 100.
2 Credit memo whith value 100 with ref. to invoice.
3 The system let me create more credit memos for the same invoice exceeding de invoice original value. (it just informes me that there are other credit memos) How can I prevent this ?
I checked copy control and Pos./neg. quantity--i put as "+" and in Item Category TAN- Completion Rule mark as "A".
Regards,
Ashu

Hi Ashutosh singh
Credit Memo and the invoice are different and the two r used in different scenarioes
Credit Memo is the Billing document raised for compensating the customer and the the document is raised with reference to the the Credit Memo request
The scenarios is that the customer places an order with the company and the company delivers the fgoods to the customer in which some of thm are dmaged and the customer then claims for the compensation , so the company asks the customer to return the goods to the company and simultaneously they will pay the compensation
process flow is as
Created the standard order OR
then do the deliver LF
then billing document F2
and then raise the credit memo request for the goods G2
thenBilling which is the credit memo
G2
This is the special process where the goods are received and the customer does not want the replacement of the dmaged goods and instead he wants the amout to be credited
so we have to raise the credit meemo request with reference to the standard illing document and then the credit memo request and then billing document G@
but in the standsrd invoice we havae to creatae the created the standsrd and then the delivery and then the invoice
Invoice
order (VA01)>Delivery(VL01N)>Change Delivery(VL02N)&PGI>INVOICE
EX:
Order type:OR
credit memo:
for the return material or discount is missing for the material,we create credit memo request.credit memo has sent to customer
order (VA01)>CREDIT MEMO(VF01).
NO DELIVERY PROCESS.WITH REF. to BILLING DOCUMENT,we create credit memo request.
EX:
Order type:G2.
The below link will help u
http://able.harvard.edu/ar/wi/create-credit-memo.pdf
http://web.mit.edu/sapr3/windocs/fopcs06f.htm
Reward if useful to u

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!

Similar Messages

Maybe you are looking for