Export NAVS condition records

I am trying to find out a way to export to csv or excel the NAVS records. Any suggestions would be appreciated.
For example, something that would look like this (these fields):
Country Material group Tax ind f plant Tax ind f acct assg Tax code
US C010 Professional Services 2 1 S7
I know that you can export from the Condition Info area (MEK3->Condition Info->Display condition records) but that export does not include the Tax Code which is what I really need.

Hi Allison,
SAP doesnt make it easy to look at this data for multiple records, as the data is stored across multiple tables.
You can download the data into Excel for each table using SE16 and then use a vlookup to link the data together.
First download the condition records from the table A??? that stores your condition records you can find the table name by looking at the technical information behind the selection parameters in transaction MEK3.
The condition item details (including the tax code) are stored in table KONP and the two tables are linked together by the condition record number field KNUMH. If your system is anything like ours, KONP is huge (9 million records + ), so you will need to us the condition record numbers that you downloaded from table A??? as selection parameters for KONP so that you only get the records that you need. You can copy the column from the spreadsheet and paste it from the clipboard into the selection parameters. Note that the condition record numbers have leading zeros which are stripped out by Excel, so you will need to put them back in before copying the column use the Concatenate function in Excel to do this.
The other alternative is to either write a program or a query to do the same thing, but I think its quicker and easier to use SE16 and Excel.
Hope this makes sense,
Monika

Similar Messages

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

How to create the condition record by ABAP program

Hi Friends,
I want to create/change the condition record of PR00 by ABAP program. It seems that there have no such BAPI/standard function can help on this. Can any one of you point out a way to me?? Thanks in addvance.
Joe GR.

Joe,
Check with below FM..
BAPI_PRICES_CONDITIONS.
Check this link:
Re: Sample code for BAPI_PRICES_CONDITIONS
examples....
http://www.4ap.de/abap/bapi_prices_conditions.php
Two useful threads on Same topic
Re: Sample code for BAPI_PRICES_CONDITIONS
Re: Problem with BAPI_PRICES_CONDITIONS
BAPI_PRICES_CONDITIONS
Please check this sample code from other thread.
wtable1-table_no = '306'.
wtable1-applicatio = 'V'.
wtable1-cond_type = 'ZPR0'.
wtable1-operation = '009'.
wtable1-varkey = '13001001USD 000000000050068946'.
wtable1-valid_to = '99991231'.
wtable1-valid_from = '20051101'.
wtable1-cond_no = '$000000001'.
APPEND wtable1 TO table1.
wtable2-operation = '009'.
wtable2-cond_no = '$000000001'.
wtable2-created_by = sy-uname.
wtable2-creat_date = '20051022'.
wtable2-cond_usage = 'A'.
wtable2-table_no = '110'.
wtable2-applicatio = 'V'.
wtable2-cond_type = 'ZPR0'.
wtable2-varkey = '13001001USD 000000000050068946'.
wtable2-valid_from = '20051101'.
wtable2-valid_to = '99991231'.
APPEND wtable2 TO table2.
wtable3-operation = '009'.
wtable3-cond_no = '$000000001'.
wtable3-cond_count = '01'.
wtable3-applicatio = 'V'.
wtable3-cond_type = 'ZPR0'.
wtable3-scaletype = 'A'.
wtable3-scalebasin = 'C'.
wtable3-scale_qty = '1'.
wtable3-cond_p_unt = '1'.
wtable3-cond_unit = 'EA'.
wtable3-calctypcon = 'C'.
wtable3-cond_value = '454'.
wtable3-condcurr = 'USD'.
APPEND wtable3 TO table3.
CALL FUNCTION 'BAPI_PRICES_CONDITIONS'
EXPORTING
PI_initialmode = 'X'
PI_BLOCKNUMBER =
TABLES
ti_bapicondct = table1
ti_bapicondhd = table2
ti_bapicondit = table3
ti_bapicondqs = table4
ti_bapicondvs = table5
to_bapiret2 = table6
to_bapiknumhs = table7
to_mem_initial = table8
EXCEPTIONS
update_error = 1
OTHERS = 2
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
READ TABLE table6 WITH KEY type = 'E' TRANSPORTING NO FIELDS.
IF sy-subrc = 0.
loop at table6 into ret.
write: / ret-type, ret-message, ret-id, RET-LOG_NO, RET-LOG_MSG_NO,
RET-MESSAGE_V1, RET-MESSAGE_V2, RET-MESSAGE_V3, RET-MESSAGE_V4,
RET-PARAMETER,RET-ROW,RET-FIELD.
endloop.
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
*EXPORTING
WAIT =
IMPORTING
return = ret
ENDIF.
Don't forget to reward if useful....

Different Tax condition records picked on sales order and invoice

Dear Expert,
I have a scenario where the goods supply from plant to different country sales organization customer. it is a n export order.
. sales order has been processed with ship to address in Portugal. We did enter end user VATnumber on the ship to customer. When you look under conditions the MWST is 0.00 which means VAT will not be invoiced.
while creating the order MWST condition calculated correctly by using the export access sequence, but when creating the invoice w r t sales order i am getting the domestic tax access sequence record.
in my case it is wrong, the same sales order MWST condition amount needs to be copied to invoice as well.
after going to condition tab of that billing document, select MWST and click on "Condition Record" I found below different values in sd order conditions and invoice conditions:
invoice:
SD-Order:
Can you kindly help me on this? :-)
Regards,
Yashar

Ideally, you should have a different pricing procedure for domestic and exports and I am not sure, why you have not created one more pricing procedure for exports.
Coming to your query, it seems, the issue is VAT registration number in which case, have a look at the following notes:-
Note 371764 - VAT registration number: Destination country
Note 15244 - Incorrect VAT amount is displayed
Note 148505 - VAT registrtn.no.fr.ship-to & n.fr.sold-to party
G. Lakshmipathi

For NAVS condition

Hi
we have created pricing Procidure but the tax calculation is computing on final amount,
Their are conditions like discount after tax, procidure is not taking into account all that conditions
How can we maintain that
What the use of NAVS condition
How can we mainatain the same
Niti narayan

dear sir.
if the excise is non-deductible . the non-deductible amount will come to NAVS condition type , and it will add to the material cost at the time of MIGO.
example : if you maintain condition record of JMIP -10% and JMX2-100% . it will calculate the tax on base value and that will flow to the NAVS condition type.
CST value will also flow to the NAVS condition.
regards
jrp

Condition records not copied from order to invoice

Hi,
I created an order and it has contion types for Frieght cost and packing cost...for both condition rocrds were found and triggered in order but whn cheked in invoice...records are not copied to invocie level..and when checked in analysis it says "access not made" for both the conditions...
Fields combination for these are shipping point and material frieght group for both condition types...
i checked the validity dates for both conditions and are still in validity dats.
Can anyone advice me is there some thing else i need to check and why condition records are not copied to invoice.
Thanks in advance
Balu

Hi Sumanth,
Copy controls are fine...it is actually delivery related billing scenarios..and in delivery to billing copy contrls in header in determine export dat feild it is set to "B :Redetermine the export data" and at tiem level the pricing type is set to "C:Copy manual pricing elements and redetermine the others"
Kindly let me know if the settings are fine or the problem is woth these settings
Regards
Balaji

Mass Upload of condition records in APO system.

Hi All,
I wanted to mass upload condition records in to the APO system for the transaction /N/SAPCND/AO11 from an external file.
Is there any FM available?
If FM is not available...which one is the best way to do this?
LSMW?? or BDC???
Please guide me..
Thanks,
Babu Kilari

At least the key fields of the conditiontable
(here 800) must be filled in structure ls_komg.
ls_komg-vbeln = '1234567890'. " document number
ls_komg-posnr = '000010'.      " item number
clear wt_komv.
ls_komv-kappl = 'V '.        " Application V = Sales
ls_komv-kschl = lc_kschl.    " Condition type
ls_komv-waers = 'EUR'.       " Currency
ls_komv-kmein = 'ST'.        " Unit of measurement
ls_komv-kpein = '1'.
ls_komv-krech = 'M'.         " calculation type;
                              "M = Quantity - monthy price
ls_komv-kbetr = '1234.56'.   " new condition value
append ls_komv to lt_komv.
call function 'RV_CONDITION_COPY'
exporting
    application              = 'V'
    condition_table          = '800'      " cond. table
    condition_type           = lc_kschl   " cond. type
    date_from                = '20061101' " valid on
    date_to                  = '20061130' " valid to
    enqueue                  = 'X'        " lock entry
    i_komk                   = ls_komk
    i_komp                   = ls_komp
    key_fields               = ls_komg    " key fields
    maintain_mode            = 'A'        " A= create
                                          " B= change,
                                          " C= display
                                          " D= create
with reference
    no_authority_check       = 'X'
    keep_old_records         = 'X'
    overlap_confirmed        = 'X'
    no_db_update             = space
importing
    e_komk                   = ls_komk
    e_komp                   = ls_komp
    new_record               = lv_new_record
tables
    copy_records             = lt_komv
exceptions

Number of Condition Records in Pur. Info Record

I am trying to get the number of condition records in a purchase info record.
using ME_GET_INFORECORD_CONDITIONS and also ME_GET_INFORECORD_CONDITIONS_1.
ME_GET_INFORECORD_CONDITIONS_1 gives me the correct values when I try to test the FM.
What is the diff between these 2 FMs.
But when I use ME_GET_INFORECORD_CONDITIONS_1 in a report, it is not giving a correct value.
Following is the code:
DATA: IT_KONP TYPE KONP OCCURS 0 WITH HEADER LINE,
      WA_KONP TYPE KONP.
DATA: coun TYPE i VALUE 0.
"Get the number of condition record - should be useful in BDC call.
CALL FUNCTION 'ME_GET_INFORECORD_CONDITIONS_1'
EXPORTING
I_EKORG       = 'U001'
I_ESOKZ       = '0'
I_INFNR       = '5300000320'
I_LIFNR       = '200524'
I_MATKL       = '001'
I_MATNR       = '80141300'
I_WERKS       = 'L001'
*     I_VABME       =
*     I_BSTME       =
TABLES
TKONP         = IT_KONP.
LOOP AT IT_KONP.
ADD 1 to coun.
ENDLOOP.
WRITE: / coun.
The variable coun is always Zero.
Reg

The LIFNR in the input parameters should be L-Padded with zeros. In SE37 it does it by itself.
reg

Default tax code in PO from Condition record :::::::

Hello experts
If a condition record for a plant vendor material combination is maintained for a particular tax code , is it possible to default the tax code maintained in PO from the condition record??
Pls give ur valuable inputs
Regards
Anis

from Note 214151 - Tax processing in purchasing
. Determination of the tax code
The tax code is defaulted from the purchasing info record in the purchase order item, however, it can also be determined via the conditions. During the determination via the condition technique an access sequence is assigned in the standard system of condition NAVS. With the latter, different tax codes can be stored via the normal condition maintenance depending on tax indicators (material, plant, account assignment, origin). Basically this access sequence can also be assigned to other condition types. The tax code is only transferred to the purchase order if class "D" (taxes) is the condition type. If several condition types of this type exist in the purchase order item, the first one that contains a tax code is transferred.

FM to upload condition records into inforecord (ME12).

Hai experts,
Can any one let me know if there is a FM or BAPI which can be used to update/upload condition records into inforecord (Transaction ME12). I need to know it to write a program for mass change/adding of conditions for huge number of inforecords.
A sample program would be more helpful for me.
Thanks in advance.
Matt.

Hi,
Please try given below code.
    CALL FUNCTION 'ME_INITIALIZE_INFORECORD'.
    CALL FUNCTION 'ME_DIRECT_INPUT_INFORECORD'
      EXPORTING
        activity         = 'V'
        i_eina           = ls_eina
        i_eine           = ls_eine
        i_no_suppose     = ' '
        i_vorga          = 'A'
      IMPORTING
        e_eina           = ls_eina_new
        e_eine           = ls_eine_new
      TABLES
        t_head           = lt_head
        t_line           = lt_line
      EXCEPTIONS
        textname_invalid = 1
        OTHERS           = 2.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
              WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ELSE.
      CALL FUNCTION 'ME_POST_INFORECORD'
        EXPORTING
          i_matnr = ls_eina-matnr
          o_matnr = ls_eina-matnr
        TABLES
          t_eina_i = lt_eina.
      IF sy-subrc IS INITIAL.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            wait = 'X'.
Regards,
Narendra

Find condition record for outline agreement

I want to know how I can find the condition record for an outline agreement. The condition number is not stored in EKKO and within the ME33K transaction I can view the condition by drilling into the item level (EKPO), but I canot find anyway of linking the agreemtn to the condition table KONP.
The reason for the qeustion is we want to outpu all agreements that have a certain condition. Any ideas.

try this code
REPORT zpwtest .
TABLES : ekko , ekpo , lfa1 , komk , komp , t001 , t001w , komv .
DATA : tkomv TYPE TABLE OF komv .
PARAMETER : p_ebeln TYPE ekpo-ebeln ,
            p_ebelp TYPE ekpo-ebelp .
SELECT SINGLE *
FROM ekko
WHERE ebeln = p_ebeln .
SELECT SINGLE *
FROM ekpo
WHERE ebeln = p_ebeln
AND ebelp = p_ebelp.
SELECT SINGLE *
FROM lfa1
WHERE lifnr = ekko-lifnr .
SELECT SINGLE *
FROM t001
WHERE bukrs = ekko-bukrs .
SELECT SINGLE *
FROM t001w
WHERE werks = ekpo-werks .
CALL FUNCTION 'ME_FILL_KOMK_PO'
EXPORTING
    i_ekko = ekko
    i_ekpo = ekpo
    i_lfa1 = lfa1
    i_t001w = t001w
    i_t001 = t001
    i_kalsm = ekko-kalsm
    i_kappl = 'M'
    i_kvorg = '02'             "Preissimulation
IMPORTING
    e_komk = komk.
IF komk-prsdt EQ 0.
komk-prsdt = sy-datlo.
ENDIF.
komk-fbuda = sy-datlo.
CALL FUNCTION 'ME_FILL_KOMP_PO'
     EXPORTING
          i_ekpo = ekpo
          i_t001w = t001w
          i_ekko = ekko
          i_komk = komk
*              I_MT06E = MT06E
*              I_EINA = EINA           "hier nicht gefüllt
     IMPORTING
          e_komp = komp.
CALL FUNCTION 'PRICING'
EXPORTING
    calculation_type = 'B'
    comm_head_i      = komk
    comm_item_i      = komp
IMPORTING
    comm_head_e      = komk
    comm_item_e      = komp
TABLES
    tkomv            = tkomv.
LOOP AT tkomv INTO komv .
WRITE : / komv-kschl , komv-kbetr CURRENCY komv-waers , komv-waers .
ENDLOOP.

Tax Condition record automatically created after Excise Invoice creation

Hello,
Excise Document for the export has been created in the J1iin then in the back ground the condition record for the ja1x has been created with key combination reference doc( Delivery no)/ item no.
Please help to know, which configuration setting causes this condition record creation and can we avoid this..
regards
SB

Moved from SAP ERP Sales and Distribution (SAP SD) to Internationalization and Unicode. Please post all your CIN related queries here.
Coming to the issue, in normal circumstances, this will never happen unless some exit is triggering. Check whether J_1I7_USEREXIT_EXCISE_BEF_SAVE is validating like that
G. Lakshmipathi

Attachment in Pricing condition records ?

Hi experts,
Do we have ability to attach documents to pricing condition records in SAP 4.7 ? Or any easy way to achieve this ?
Thanks !
Pricing, Condition, VV11, VV12

Ron
You can't attach documents but can't you use' Internal comment' in the Details screen of a condition record, where you can load the text from a file and you can also export it to a local file.

Condition record exists (removed manually)

Hi
I have created one RFQ w.r.t PR. In ME47 transaction am not getting one condition type (ZNVS)automatically, though it is selected as "automatic display has high priority" in condition type.When analysis is selected system is showing the message "condition record exists (removed manually)
I have maintained condition record in MEK1 for ZNVS.ZNVS is negative value of NAVS (Non deductable condition type)
So that I can deduct the value from JEXS and only excise will be displayed.
how can I get that ZNVS condition type in RFQ conditions Automatically.
Need Help.

What the pricing analysis is saying is that a condition record has been found but it has been removed manually. It can happen in the following cases
1. If a user manually deleted it from the pricing screen, this seems unlikely in your case
2. There is a requirement on condition type K007 level or its access sequence K007 level in the pricing procedure, which removes the retrieved condition record. Check this in the pricing procedure-condition type assignment and access sequence definition
3. There is a formula (alternative calculation type) where there is some code written to remove the retrieve condition type
4. A user-exit is used during condition access and which removes specific condition records from the set retrieved for the pricing procedure
IMG Path : Sales & Distribution -> Basic functions -> Pricing -> Pricing control -> Define and assign pricing procedures (use this to check requirements and formulas at condition type K007 level)
IMG Path : Sales & Distribution -> Basic functions -> Pricing -> Pricing control -> Define access sequences (use this to check if there is any requirement at access sequence K007 level)

BAPI_PO_CREATE1 -- Condition Record filling

Hi,
In this BAPI how to insert the Condition records to be filled ...
    CALL FUNCTION 'BAPI_PO_CREATE1'
         EXPORTING
              POHEADER         = G_BAPIMEPOHEADER
              POHEADERX        = G_BAPIMEPOHEADERX
         IMPORTING
              EXPPURCHASEORDER = G_EBELN
              EXPHEADER        = GSTEST
         TABLES
              RETURN           = G_BAPIRET2
              POITEM           = G_BAPIMEPOITEM
              POITEMX          = G_POITEMX
              POSCHEDULE       = G_BAPIMEPOSCHEDULE
              POSCHEDULEX      = G_POSCHEDULEX
              POCOND           = G_BAPIMEPOCOND
              POCONDX          = G_BAPIMEPOCONDX.
what are the mandatory fields,..
Any helpful inputs on this will be rewarded points
Rgs
Lakshmiraj.A

Pls help,
Any useful inputs on this will be rewarded points.

Export NAVS condition records

Similar Messages

Maybe you are looking for