Performance condition records exchange

Maybe this sounds a little rediculous but we need to exchange about 150.000 condition records from R/3 to CRM. It is a relatively simple condition table, which only contains customer and material.
These consition recards get generated in R/3 and need to be downloaded to CRM.
Does anyone have an idea on the performance? How much time would it take to exchange this amount of data? I know that the hardware etc. is of much influence but an idication would already be helpful.
Best regards,
Pascal.

hi
go to st05 and see the time taken by the insert stement
and again if it is slow then plz
refresh <table>
free <table >, statement to free the table from the buffer memory.
u can restrt the server if possible after that definitly the system will take less time.
thanks
rewards if useful
sachhidananda

Similar Messages

Condition Records not to be calculated if base value is negative

Dear all
I have configured a pricing procedure which is being used while performing DP90 with reference to service order. Now the values are getting populated in condition type EK02 and based on this value various other charges like service tax, supervision charges are getting calculated.(condition records have been maintained for condition types related to these charges). Is it possible that these charges do not get calculated if the value in EK02 is negative?????

You can create a routine where you can put the check. And assign it to pricing procedure for all the condition types you don't want negative value for.
Thanks

Condition records in idoc

hi
whenever po is created or changed idoc should get triggered, as it is done already,now the issue is the condition records also be included in idoc whenever po is created or changed.
can anyone explain me how to do that?
and what is idoc view and how it is related to condition records.

IDOC Views are used for IDoc outbound processing where you dont want to send an entire IDOC out when all you need is just some of the segments.
To improve performance when generating IDocs, you can use views to ensure that only the segments relevant to the current business process are filled with data. Views are therefore only important for IDoc outbound processing
chk the sap doc.
http://help.sap.com/saphelp_47x200/helpdata/en/d5/edf160dcdc11d1890c0000e8216438/frameset.htm
Edited by: Mahalakshmi Padmanaban on Feb 16, 2010 3:02 PM

Archive pricing condition record

Hello everybody,
I want to ask about how to archive MM pricing condition record?
I tried with SARA, archive object CND_RECORD or program /SAPCND/CND_RECORD_WRITE but it doesnt work.
Kindly advise,
Thanks,
HN

Hello Jurgen,
We're about to archive tens of millions of SD_COND entries - mainly to reduce the number of change records we have in table CDHDR, of type COND_A (COND_A is the change document object for SD Pricing conditions and we have over 100 million of them! And is now causing a few performance issues).
Understandably this is going to take a long time to process so I was intrigued to read your post that no conditions should be maintained whilst the archiving programs run...
I've tried searching OSS but haven't been able to locate any information about this.
Could it be that you were referring to the old archive programs and not the newer ones such as those described in:
Note 838768 - New archiving programs for condition records
Any help you could offer would be much appreciated!

Pricing condition records should not be picked up

Hi,
I have configured a scenario for Supplementary Invoice for which I created a new sales order type. The requirement is such that this order type should not pick the pricing condition records that have been created in VK11. Please suggest how can this be configured.
Do I have to use any Userexits, if so which one?
Regards,
Abhishek

As mentioned by you, you have created a new Sales Order Type, you can create a new document pricing procedure, based on which you can determine a new pricing procedure.
To configure new Document Pricing Procedure:
IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Define Document Pricing Procedure. (Maintain the new Document Pricing Procedure in new Sales Order Type)
Maintain a new Pricing Procedure, maintaining the Condition Types as manual. Maintain the determination of Pricing Procedure appropriately.
Pricing Procedure Determination:
In SD, Pricing Procedure is determined (T.Code: OVKK) based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
Pricing Procedure Configuration:
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure (T.Code: V/08): It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
Regards,
Rajesh Banka

Read sales Condition records

Hi Experts,
I need to read the condition record from sales order maintenance. I have the following information.
Material Number, Quantity, Plant, sales area, customer, condition type. Is there any standard function module which will give me the condition rate given the above details. It should also consider if scales exists for the condtion records.
Thanks a lot for your help.
Best regards
Satish

Satish,
u can try this code.
if u r using WBS element, this vl be the procedure.
*Conditions
SELECT kappl kozgf kvewe kotabnr kolnr
                            FROM t682i INTO TABLE it_t682i
                            WHERE kappl = c_v AND
                                  kvewe = c_a AND
                                  kozgf IN (c_zpr0,c_zpr1).
IF it_t682i[] IS NOT INITIAL.
    SORT it_t682i DESCENDING BY kozgf.
    DELETE it_data WHERE vbeln IS INITIAL.
    DATA: c_val TYPE i VALUE '3600'.
    DATA: BEGIN OF t_t006,
            msehi TYPE t006-msehi,
            zaehl TYPE t006-zaehl,
            nennr TYPE t006-nennr,
          END OF t_t006.
    DATA : it_t006 LIKE STANDARD TABLE OF t_t006.
    SELECT msehi zaehl nennr FROM t006 INTO TABLE it_t006
                             WHERE dimid = 'TIME'.
    LOOP AT it_data ASSIGNING <fs_data>.
      DO.
        READ TABLE it_t682i INTO t_t682i INDEX sy-index.
        IF sy-subrc IS NOT INITIAL.
          EXIT.
        ELSE.
          CONCATENATE c_a t_t682i-kotabnr INTO l_table.
          CLEAR where_clause.
          PERFORM convert_wbs_element USING <fs_data>-objid
                                      CHANGING l_posid.
          PERFORM get_sales_data_of_wbs USING l_posid
                                        CHANGING st_sales.
          IF st_sales IS INITIAL.
            EXIT.
          ENDIF.
          CASE l_table.
When the table is A901, pass the WBS Element
            WHEN c_a901.
              CONCATENATE 'ZZPROJK = ''' <fs_data>-objid '''' INTO where_clause.
When the table is A902, pass the Price List
            WHEN c_a902.
              CONCATENATE 'PLTYP = ''' st_sales-pltyp '''' INTO where_clause.
          ENDCASE.
*Read Condition Rec.No., and Condition type
          SELECT knumh kschl
                INTO TABLE l_gt_konp
                FROM (l_table)
                 WHERE   kappl EQ c_v
                   AND   kschl IN (c_zpr0,c_zpr1)
                   AND   vkorg EQ st_sales-vkorg
                   AND   vtweg EQ st_sales-vtweg
                   AND   kunnr EQ st_sales-kunnr
                   AND (where_clause)
                   AND   matnr EQ <fs_data>-inv_mat
                   AND   datbi GE st_sales-prsdt
                   AND   datab LE st_sales-prsdt.
          IF sy-subrc = 0.
Read the rate, currency and UOM
            SELECT kschl kbetr konwa kmein
              INTO TABLE l_gt_rate
              FROM konp
               FOR ALL ENTRIES IN l_gt_konp
             WHERE knumh    = l_gt_konp-knumh
               AND loevm_ko EQ space.
            IF sy-subrc = 0.
select the data in an internal table and then reading the record
              SORT l_gt_rate DESCENDING BY kschl.
              READ TABLE l_gt_rate INDEX 1.
              <fs_data>-meinh = l_gt_rate-kmein.
              IF l_gt_rate-kschl EQ c_zpr0.
                READ TABLE it_t006 INTO t_t006 WITH KEY msehi = l_gt_rate-kmein.
                IF sy-subrc IS INITIAL.
                  <fs_data>-netwr = ( l_gt_rate-kbetr * <fs_data>-op_megbtr ) / ( ( t_t006-zaehl / t_t006-nennr ) / c_val ) .
                 <fs_data>-netwr = l_gt_rate-kbetr * <fs_data>-op_megbtr.
                ENDIF.
              ELSEIF l_gt_rate-kschl EQ c_zpr1.
                l_gt_rate-kbetr = l_gt_rate-kbetr / 10.
                <fs_data>-netwr = ( l_gt_rate-kbetr / 100 ) * <fs_data>-op_wkgbtr.
              ENDIF.
            ENDIF.
          ENDIF.
        ENDIF.
      ENDDO.
    ENDLOOP.
ENDIF.
Regards,
Sujatha.
Message was edited by:
        Sujatha Reddy

Parallel processing of condition records in SAP

Hi,
I have a particular scenario, wherein XI sends 30000 idocs for pricing condition records of message type COND_A to SAP, and SAP has to process all the idocs within 15 minutes. Is it possible, and what kind of parallel processing techniques can be used to achieve this?
Regards,
Vijay
Edited by: Vijay Iyengar on Feb 21, 2008 2:05 PM

Hi
We had a similar performance issue to load conditions of sales deal.
We did not use IDOC.
Initially we did the BDC and it was loading 19 records per second and than later we developed a direct input program, which loaded close to 900 records per second.
What we did was, we wrote a direct input pogram and called the function module
CALL FUNCTION 'RV_KONDITION_SICHERN_V13A' IN UPDATE TASK
But Pls note - We took approval from SAP before using it.
Regards
Madhan
Edited by: Madhan Doraikannan on Oct 20, 2008 11:40 AM

Error in creation of a condition record

Hi to all, I've this error when I try to create a condition record :
Implementation of Method FIELD_CHECK/DEFAULT_VALUE_SUGGESTION for BAdI /SAPCND/ROLLNAME for filter ZIUSERSTATUS is missing
Message no. /SAPCND/MAINTENANCE719
Diagnosis
Implementation of BADI /SAPCND/ROLLNAME or method FIELD_CHECK/DEFAULT_VALUE_SUGGESTION is missing for the filter characteristic ZIUSERSTATUS.
If, however, the implementation is correct (see BADI Interface Documentation) and active, there is an error in the condition maintenance layer.
System Response
An exception or error occurred because condition maintenance cannot check, convert or lock/unlock the fields of a condition record.
Procedure
Contact the department responsible for carrying out the missing implementation in the case of application fields in the customer namespace. SAP is responsible for SAP fields which are set in the field catalog (/SAPCND/CTFC) and delivered, and if the field is supported as a possible field in a condition table. SAP is also responsible for the implementation of usage fields for SAP applications, just as with condition technique fields.
In cases where SAP is responsible, contact your responsible support organization.
Could someone help me please ?

Hi I just put the coding:
e_was_executed = 'X'.
into every method and however it worked.
Best Regards

How to Delete the condition record in CRM

HI,
Can you please help me how to delete the condition record from condition table in CRM.
Please explain the usage of FM CRMXIF_CONDITION_SEL_DELETE with examples.
I have also read the documention of the function module. How to use this FM for custom defined condition table.
(this is the code given in Documentation)
DATA-OBJECT_REPRESENTATION         = 'E'
DATA-SEL_OPT-CT_APPLICATION              = 'CRM'
DATA-SEL_OPT-OBJECT_TASK                    = 'D'
DATA-SEL_OPT-RANGE-FIELDNAME        = 'PRODUCT_ID'
DATA-SEL_OPT-RANGE-R_SIGN                  = 'I'    (Including)
DATA-SEL_OPT-RANGE-R_OPTION           = 'EQ'
DATA-SEL_OPT-RANGE-R_VALUE_LOW = 'PROD_1'
Thanks
Shankar

Hi Shankar,
I am using the same CRMXIF_CONDITION_SEL_DELETE function module to delete condition record present in CRM.
But it is giving me below error in the return table of the FM after i run the program. Can you please correct me if I am doing any thing wrong?
Error in lt_return: SMW3     CND_MAST_SEL_DEL_EXT_VALIDATE     CND_M_SD
code:
ls_range-fieldname = 'PRODUCT_ID''.
ls_range-R_SIGN = 'I'.
ls_range-R_OPTION = 'EQ'.
ls_range-R_VALUE_LOW = '123456'.
APPEND ls_range TO lt_range.
MOVE lt_range TO ls_entry-SEL_OPT-range.
ls_data-SEL_OPT-object_task = 'D'.
ls_data-SEL_OPT-ct_application = 'CRM'.
ls_data-object_representation = 'E'.
CALL FUNCTION 'CRMXIF_CONDITION_SEL_DELETE'
EXPORTING
    DATA          = ls_date
IMPORTING
   RETURN        = lt_return
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
IMPORTING
    return = lt_ret.
Edited by: Saravanaprasad Nadar on Jul 7, 2010 1:27 AM

Free goods condition records - Usage in Sales Order

HI,
I have so many condition records in various KOTN9xx tables, which are for issuing free goods. If I see a sales order item, that is a free good, how do I know, on what basis (based on which condition record, in which condition table) that free good was issued?
Technically speaking: Similar to KONV table for storing transaction data on pricing, is there a table for storing transaction data on free goods?
Thanks,
Juwin

Find the table number of the key combination of customer / material . & you can extract free goods condition records from this table.
Search in SE11 with the table number.

Regarding Condition record in CRM using field MATKL (Material Group)

Hi All
Currently we are working in SAP CRM 5.2 and it has been connected with backend ECC 6.0.
This scenario is about Pricing which has been maintained in ECC and inturn flows to CRM with few filters in place.
There are few customized Condition Tables in ECC with combination of Sales org./ material group for which discount has been maintained. A proper condition record is also available for this Condition table and it has been assigned to a access sequence and inturn assigned to a condition type.
All these procedures, condition types, access sequence has flown from ECC to CRM. And all the condition tables are active in IMG (Basic Functions / Pricing / Define Settings for Pricing / Create Condition Tables)
When i check in
(SAP menu / Master Data / Prices and Conditions / SAPCND/GCM - Maintain Conditions )
Application - CRM,
Maintenance group - PRODDISCOU,
Maintenance context - GCM
Here for the above mentioned combination when i select the Key Combination (Condition Table) and enter the customized table number (Sales org. / Material Group) iam getting a dump which says the following.
Error analysis
Short text of error message:
Implementation of Method ATTRIBUTE_CONVERSION for BAdI /SAPCND/ROLLNAME for filter MATKL is missing
Program............. "/SAPCND/CL_MNT_COND_MAINT_UI==CP"
Screen.............. "/SAPCND/SAPLCOND_MAINTAIN 0100"
Screen line......... 8
Information on where terminated
Termination occurred in the ABAP Program "/SAPCND/CL_MNT_COND_MAINT_UI==CP" -
in "ON_FCODE_SELECT".
The main program was "/SAPCND/GENERAL_COND_MAINT ".
In the source code you have the termination point in line 622
of the (Include) program "/SAPCND/CL_MNT_COND_MAINT_UI==CM005".
Please let me know the solution, Request you to do the needful aSAP.
Regards
*Ramesh*

Hi Ramesh,
Have you checked the following note?
Note 441083 - Transferring conditions for material group MATKL to CRM
Kind regards,
Johan Wigert

Condition records found but do not show up in the pricing - 208

Hi,
A) In some scenario though the CR is found, access is complete, message is 208, there is not exclusion etc, simple scales..yet the value of CR is not shown / included in the pricing procedure calculation.
B) Also in another situation, always the first scale value being read though the scale value being the next higher one, i.e. it should pick up the next condition record based on the order value but it remains at the first scale, which means the scale somehow always being read is the first one irrespective of the order value.
What could be possible reason for these, debug process?
Thanks much for the help!!

Check the following setting is the Price condition Type, I am assuming u are using simple scales.
in T.Code: V/06 go to the price condition type and double click it.
Check the entries:
Scale Basis: C
Check Value: A
Scale Type: Blank (This value can e maintained in the condition record for price condition type).
If further queries do post them.
Regards
AK
Please Award points if helpful

How can i get the tax code from Condition record number

Hi all,
i have the Condition record number from which i have to get the tax code as i looked inthe KNOP that Condition record number there but no tax code is maintained there.
so is there any other way to find the tax code for particular Condition record number
Regards
suresh

hi suresh,
can u tell me the field name for condition record number and in which table it is stored.
because i knew one condition number which is stored in table EKKO and the field name is
KNUMV- Number of the document condition.
from ekko take relevant details and look for ekpo where u find the tax code
filed name of the tax code id MWSKZ- Tax on sales/purchases code

Accruals Condition Record posted late in COPA along with the Settlement

Hi Gurus,
Accruals condition record for 1 item in an Invoice is posted along with the Settlement Credit Note in COPA. While condition records of the other items from the same invoice were posted on the Billing Date itself.
For eg:
Invoice 111       Date 01.03.2011
Items     Condition   value
1              Z1            100
2              Z1             200
3              Z1             300
COPA Doc No.        Value Field        Date
     001                         200             01.03.2011
     002                         300             01.03.2011
     003                         100             30.05.2011
30.05.2011 is the date of Rebate Credit Note for the Invoice # 111
I also got that if Posting of Accrual is not done for an Item, Retroactive rebate settlement automatically posts a new document for accrual.
So the question is why the posting of accrual was not done on the Invoice date in the first place?
Edited by: Parth Kulkarni on Jul 1, 2011 4:31 PM

Hi Suraj,
i too have the same problem, the condition types for Values and quantity in COPA are assigned. The system updates the quantity for the first billing document but not for the subsequent billing documents.
Cost of goods sold and revenue gets updated.
Regards,
Prateek

Report on Change in Condition Record effects which all Sales Orders

Hello Gurus,
Thanks in advance. My customer requires a report which gives him list of Sales Orders effected due to Change in Condition Record.
Proper input to this will be greatly rewarded.
Regards,
Vishvesh Kamdar

hi,
whenever u change the condition record it will fall under the validility date, ie.,
<b>example:</b>
Condition record for cond type PR00 is
<b>valid from 01/05/2007 to 31/99/9999 is Rs.1000</b>
but suddenly when u change prices on 01/10/2007 then system will display has below
<b>vaild from 01/05/2007 to 31/09/2007 is Rs.1000
vaild from 01/10/2007 to 31/99/999 is Rs.1500</b>
hence u take all the sale orders & billing document which are created from 01/10/2007, this will slove ur purpose
SE16-->vbak--->enter -
> here u will find created on enter the date & execute
hope this heklps u
regards,
Arunprasad

Performance condition records exchange

Similar Messages

Maybe you are looking for