Condition Types used in a particular country

Hi Experts,
I am trying to pull a report of changes made to the condition types using VK13. Before doing this, I would like to know what are the condition types used for a particular country. How can I find out the condition types used for a particular country. Please advise.

Hi Murukan,
As above said we will not maintain condition record for country,until we select the country in our access sequence.
You know the changes made to condition type by the table CDHDR and CDPOS
go to SE16N give the table CDHDR there in TCODE filed give VK12 you will get all changed information regarding that and get the
value in filed CDHDR - OBJECTID pass the same into CDOPS - OBJECTID you can get specific record information.
Check and revert
Regards
Ram

Similar Messages

  • Condition types used in cin

    i have some confusion on cin
    what are condition types used in cin with details
    and where will assign  TAXINJ and TAX INN  please give me full details with example if any documents available please send to [email protected]
    advanced thanks

    <b>TAXINN:</b>
    JEXP IN: A/R BED %
    JEXQ IN A/R BED
    JEAP IN A/R AED %
    JEAQ IN A/R AED Qty
    JESP IN A/R SED %
    JESQ IN A/R SED Qty
    JASS IN A/R Assessable Va
    JIN1 IN A/R CST
    JIN2 IN A/R LST
    JLST IN A/R LST
    JMAN IN Manual excise
    JMOD IN A/R BED ..............................
    Regards,
    Rajesh Banka
    Reward points if helpful.

  • Condition type used for invoice list

    Hello Gurus,
            following condition type used for invoice list, why do they exit in invoice list:
             RL00    MW15.  LR00    RD01

    Hi,
    Please go through the below document
    When you work with invoice lists, you need to be familiar with the following concepts:
    Prerequisites for invoice lists
    Relationship to Pricing
    Structure of an Invoice List
    Changing header and item data
    Integration with financial accounting (FI)
    Prerequisites
    You can only process invoice lists if the following prerequisite data is defined by your system administrator in Customizing for Sales:
    Condition type RL00 (factoring discount) must be maintained and, if required, also the condition type MW15.
    An invoice list type must be assigned to each billing type that you want to process in invoice lists. The standard version of the SAP R/3 System includes two types of invoice lists: LR for invoices and debit memos, LG for credit memos.
    Copying requirements must be defined (for example, the payer, terms of payment and other fields that must be identical in the documents to be included in the invoice list)
    In addition, before you process an invoice list, you must maintain the following master data:
    A customer calendar must be defined, specifying the time intervals or dates on which invoice lists are to be processed.
    The customer calendar must be entered in the Billing Sales Area view of the customer master record.
    Pricing condition records for the condition type RL00 and, if necessary, (e.g. in Germany) the condition type MW15 must be maintained.
    Output condition records for condition types LR00 and RD01 must be created.
    Relationship to Pricing
    The system processes factoring discounts in invoice lists in exactly the same way as other kinds of pricing elements. The data for the factoring discount is stored in condition records. Controlling during document processing is carried out via condition types, pricing procedures and access sequences. This control data is defined in Customizing for Sales by your system administrator.
    For further information, see  Conditions and Pricing.
    Structure of an Invoice List
    An invoice list represents an individual billing document. It consists of a document header and document items. Each item represents a billing document that you have included in the invoice list. The header contains an overview of summary information, such as the net value of all documents in the invoice list, the value of the factoring discount, details of taxes, and so on. It also contains information on partners and output.
    Changing Header and Item Data
    You can change some of the header data - for example, the billing date - when you process the invoice list. You can change an item - either an individual or collective invoice - and display document details. However, you cannot change any data in individual billing documents once they are part of an invoice list.
    It is possible, however, to make certain global changes to output in all items in an invoice list.
    For further information on output, see  Communication in Sales and Distribution Processing.
    Integration With Financial Accounting (FI)
    The documents that you want to combine within an invoice list must already have been billed and forwarded to Financial Accounting. Here the billing documents intended for an invoice list are blocked for normal dunning transactions.
    The dunning block on FI documents is lifted as soon as you create an invoice list and transfer it to FI . The system then calculates the new dunning date for the invoice on the basis of the invoice list date.
    In addition, the system enters invoice list numbers in the FI documents as reference numbers. Invoice list numbers can then be entered for incoming payments.
    When you save the invoice list, the system automatically creates an accounting document for the factoring discount and possible taxes and posts it to the corresponding G/L account in FI.
    Regards,
    Murthy

  • Same condition type used in MM , error?

    Hi ,
    I am (SD) using the same condition type which is used by MM and maintained different condition records in VK11. when I created STO , MM condition value is posting right , But with relevant to STO and Del , I create billing document , here The condition records what I maintained in vk11 are missing. I have check each and every step. where could be the error exists? cant we use the same condition type used by MM , though we maintained different acceess seq and condition records in VK11?
    Thank you,
    Kanna Palle.

    Hi,
    I copied the condition type and changed the name , but its already used by MM. Its a STO process .STO to DEL to IV Billing.I maintained condition records in vk11.In the combination of plant and material , I find different field name for material (but its still named as material and the data element is different from what MM material field). Its confusing I think.
    Precisely , I created access seq for plant and material , they field names are z123 and zabc. when I maintained condition records in vk11 ,  condition record saved in ZAAA and ZBBB fields. now at the time of Billing document , system throws an error saying, * condition record is missing *  The system checks z123 and zabc for condition records , which are not there becos they are in the fields ZAAA and ZBBB.
    At the time of Acc Seq creation , I tried to pick the same field which it shows in billing document.but that is not available in SD , its available only in ALLOWED FIELDS in MM. Pls Throw some light on this.
    Thanks,
    Kanna Palle.
    Any updates on this Pls?

  • To change vendor no for condition types using BAPI_PO_CHANGE

    Hii,
    how to change vendor no for certain condition types using BAPI_PO_CHANGE.
    Is it possible .
    Any parameter is there.
    Plz help urgent
    Title edited by: Alvaro Tejada Galindo on Jun 12, 2008 5:23 PM

    Hi,
       It is possible.
    wa_pocond-vendor_no = wa_konv-lifnr.
    wa_pocondx-vendor_no = 'X'.
       wa_pocond-condition_no = wa_konv-knumv.
        wa_pocond-itm_number = wa_konv-kposn.
        wa_pocond-cond_type = wa_konv-kschl.
        wa_pocondx-condition_no = wa_konv-knumv.
        wa_pocondx-itm_number = wa_konv-kposn.
        wa_pocondx-cond_type = 'X'.
        wa_pocondx-change_id = 'U'.
        APPEND wa_pocondx TO it_pocondx.
        CALL FUNCTION 'BAPI_PO_CHANGE'
          EXPORTING
            purchaseorder                = wa_konv-ebeln
          POHEADER                     =
          POHEADERX                    =
          POADDRVENDOR                 =
          TESTRUN                      =
          MEMORY_UNCOMPLETE            =
          MEMORY_COMPLETE              =
          POEXPIMPHEADER               =
          POEXPIMPHEADERX              =
          VERSIONS                     =
          NO_MESSAGING                 =
          NO_MESSAGE_REQ               =
          NO_AUTHORITY                 =
          NO_PRICE_FROM_PO             =
        IMPORTING
          EXPHEADER                    =
          EXPPOEXPIMPHEADER            =
         TABLES
           return                       = it_return
           poitem                       = it_poitem
           poitemx                      = it_poitemx
          POADDRDELIVERY               =
          POSCHEDULE                   =
          POSCHEDULEX                  =
          POACCOUNT                    =
          POACCOUNTPROFITSEGMENT       =
          POACCOUNTX                   =
          POCONDHEADER                 =
          POCONDHEADERX                =
           pocond                       = it_pocond
           pocondx                      = it_pocondx
          POLIMITS                     =
          POCONTRACTLIMITS             =
          POSERVICES                   =
          POSRVACCESSVALUES            =
          POSERVICESTEXT               =
          EXTENSIONIN                  =
          EXTENSIONOUT                 =
          POEXPIMPITEM                 =
          POEXPIMPITEMX                =
          POTEXTHEADER                 =
          POTEXTITEM                   =
          ALLVERSIONS                  =
          POPARTNER                    =
          POCOMPONENTS                 =
          POCOMPONENTSX                =
          POSHIPPING                   =
          POSHIPPINGX                  =
          POSHIPPINGEXP                =
          POHISTORY                    =
          POHISTORY_TOTALS             =
          POCONFIRMATION               =
        COMMIT WORK AND WAIT.

  • Monthly purchase value,depending on condition type used.

    Can we search for PO,depending on condition type used in the PO.eg. we are using a condition ZENT for entry tax and
    the requirement is to search the po containing that ZENT condition.In dynamic selection mode there is condition group in
    purchase order detail,but it is not selecting the required PO.please guide.

    Hi,
    This requirement is not possible in std SAP Report.
    You need to develop a Z report with the help of ABAPers.
    Give proper logic for them for creating this req.
    Regards,
    Rahul

  • Standard Condition type used for Manual freight at item level

    Hello Gurus
    Can you please tell me the standard condition type used for entering freight manually at header as well as item level.
    Warm Regards
    Prashant Joshi.

    Prashanth,
    The freight Conditions that we use in Sales are two types
    HD00 - Header Level, wherein we have no access sequence
    KF00 - Item level, Wherein we have access sequence  KF00 - Freight
    But you want the condition types to be maintained manually, then you need item details screen of the respective condition type HD00/KF00 using Tcode V/06.
    Inside that Manual entry as "C". Similarly you need to maintain or activate "Manual" Indicator in pricing procedure. Then you can enter the freight Manually.
    Note:
    The difference In applying at the header level and item level is if you enter freight value at the header level it is applicable to all items in the item level. But if you want to apply freight  we can give freight to each item or selective item.
    Regards
    Sathya

  • Condition type used for scrap

    hi,
    what is the condition type used for scrap in Standard SAP.?Assured points
    Best regards,
    R.Srinivasan

    Dear Srinivasan
    Follow the below process:-
    1)  Go to V/06, either copy the standard or create a new by naming ZTCS and maintain the following:-
    -  Cond. class::::::::::A
    -  Calculat.type::::::::A
    -  Access seq.::::::::::K004
    -  Manual entries:::::::D
    -  Item Condition:::::::X
    -  Text DetPrc::::::::::04
    2)  Again in V/06, create one more condition type (say ZECT) for Edu.Cess on TCS for which the same values can be maintained as like ZTCS
    3)  Go to OV34, create an Account key for TCS, say ZTC and ZET for Edu.Cess
    4)  Go to VK11, input the condition type ZTCS and maintain the required TCS percentage (the combination which you can maintain is for Sales Org / Dis.Channel / Material or as per the requirement demands you).   Similarly, you have to maintain the required percentage for Edu.Cess also in VK11
    5)  Now go to V/08, create a new pricing procedure exclusively for scrap sales and maintain these two condition types there with respective Account Keys
    thanks
    G. Lakshmipathi

  • Find condition type (kschl) for a particular material document no (mblnr)

    hiiiiii
    How to find condition type (kschl) for a particular material document no (mblnr).

    Hello,
    <b>Check the table A017 and KONV.</b>
    Vasanth

  • How can I download a list of import condition types used in POs (STP)

    Hi Experts,
    Do any of you know how can I download such a list from SAP? I'm enclosing images of what I need, it'd be great if I could have for instance an excel report of what condition types I have per material for all purchase orders in a determinated period of time.
    Thanks,
    Dersu

    In addition to ticking stuff off as you go along have a play with edit > find. I've not looked at this in any great depth, but it seems you can search for used/unused media. Might be worth a look at.

  • Need to add new condition type using   BAPI_SALESORDER_CHANGE

    Hi all,
    I am using BAPI_SALESORDER_CHANGE to add new condition type for an order item.
    I am able to add it, but problem here is, that i want that condition type to be manually changable. Here, in BAPI, after execution, condition type field becomes disable.
    My code is as follows:
                    MOVE 'B' TO wa_logic-pricing.
                      MOVE 'X' TO wa_logic-cond_handl.
                      wa_cond-itm_number = wa_vbap-posnr.
    *                  wa_cond-cond_st_no = it_konv1-stunr.
    *                  wa_cond-cond_count = it_konv1-zaehk.
                      wa_cond-cond_type =  it_discount-kschl.
                      wa_cond-CONDORIGIN = 'C'.
                      APPEND wa_cond TO i_cond.
                      CLEAR: wa_cond.
                      wa_condx-itm_number = wa_vbap-posnr.
    *                  wa_condx-cond_st_no = it_konv1-stunr.
    *                  wa_condx-cond_count = it_konv1-zaehk.
                      wa_condx-cond_type =  it_discount-kschl.
                      wa_condx-updateflag = 'I'.
                      wa_condx-COND_VALUE = 'X'.
                      APPEND wa_condx TO i_condx.
                      CLEAR: wa_condx.
    FORM f_update_order .
      CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
        EXPORTING
          salesdocument    = salesdocument
          order_header_in  = wa_headerdata
          order_header_inx = wa_headerdatax
          logic_switch     = wa_logic
        TABLES
          return           = it_return
          order_item_in    = i_itemdata
          order_item_inx   = i_itemdatax
          conditions_in    = i_cond
          conditions_inx   = i_condx.
      IF NOT it_return[] IS INITIAL.
        PERFORM f_commit_or_rollback.
      ENDIF.
    ENDFORM.
    Please let me know, if it could be achievable.
    Best regards,
    Meena
    Moderator Message: Corrected the code tags. You need to use flower brackets.
    Edited by: kishan P on Aug 25, 2010 6:04 PM

    Hi,
    This is the demo code i am writing:
    Even Change manual entry field in BAPI did not helped me.
    [code]REPORT  ZTESTM1.
    data: l_knumv type knumv.
    DATA: it_return        TYPE STANDARD TABLE OF bapiret2,         "Internal table for t_txt_ret
           wa_return        type  bapiret2.
    data: begin of it_konv occurs 0.
           include structure konv.
           data: end of it_konv.
    data: logic_switch type standard table of    BAPISDLS,
          wa_logic type BAPISDLS.
    data:itemdata type STANDARD TABLE OF BAPISDITM,
          wa_item type   BAPISDITM.
    data : salesorder type BAPIVBELN-VBELN.
    data:itemdatax type STANDARD TABLE OF BAPISDITMx,
          wa_itemx type   BAPISDITMx.
    data: wa_header type BAPISDH1,
          wa_headerx type BAPISDH1X.
    data: i_cond type STANDARD TABLE OF BAPICOND,
          wa_cond type BAPICOND.
    data: i_condx type STANDARD TABLE OF BAPICONDX,
          wa_condx type BAPICONDX.
    move '0060008601' to salesorder.
    move '000010'  TO wa_item-itm_number.
    append wa_item to itemdata.
    move ' '  to wa_header-BILL_BLOCK.
    move   'U'  to wa_headerx-UPDATEFLAG.
    move  'X' to wa_headerx-BILL_BLOCK.
    MOVE: 'U'  to wa_itemx-UPDATEFLAG,
         '000010'  TO wa_itemx-itm_number.
         append wa_itemx to itemdatax.
    move 'B' to wa_logic-PRICING.
    move 'X' to wa_logic-COND_HANDL.
    select single knumv from vbak into l_knumv where vbeln = '0060008601'  .
    select * from konv into table it_konv where knumv = l_knumv  and kposn = '000010'.
          wa_cond-ITM_NUMBER = it_konv-kposn.
          wa_cond-cond_type = 'Z550'.
          wa_cond-CONDCHAMAN = 'X'.
           append wa_cond to i_cond.
           clear: wa_cond.
    wa_condx-ITM_NUMBER = it_konv-kposn.
    wa_condx-COND_TYPE = 'Z550'.
    wa_condx-UPDATEFLAG = 'L'.
    append wa_condx to i_condx.
    clear: wa_condx.
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
      EXPORTING
        salesdocument               = salesorder
       ORDER_HEADER_IN             = wa_header
        order_header_inx            = wa_headerx
       LOGIC_SWITCH                = wa_logic
      tables
        return                      = it_return
       ORDER_ITEM_IN               = itemdata
       ORDER_ITEM_INX              = itemdatax
       CONDITIONS_IN               =   i_cond
       CONDITIONS_INX              =   i_condx
      EXTENSIONIN                 =
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.[code]
    Thank you.
    Meena

  • Rebates - incorrect condition type used

    I have one rebate agreement (promotion) that has two conditions types attached, one is for Customer Hierarchy/material and the other is Customer/material, both are a fixed amount but going to different accounts.
    The promotion payment has been partially paid but the user paid against the customer /material condition instead of the customer hierarchy /material condition. How would I correct this in accounting and how would one prevent this from happening in the future?

    Hi,
    1) Normally there is a rebate reversal document type set up in the system.
    You should use this document type to reverse the entry. You need to close the rebate.
    2) Fix the setting or configuration. The posting to the account must be done automatically.
    3) Create new rebate.
    4) Run retroactive rebate processing.
    Regards

  • NAVM / NAVS condition type Use

    Hi Experts,
    If i am using NAVM/ NAVS condition type in Purchase Pricing Procedure.
    While creating PO with these condition typeu2019s price is not added to net price.
    But when I post Goods receipt for PO, condition type value hits the inventory.
    Can any one tell me what is happening in the background, so that it is not included in net price but it hits inventory during GR.
    Any Input is highly appreciated.
    Thanks and Regards,
    Selvakumar.M

    Hi
    Actually the Coindition types should get added to the net price, Please check the calculation of net price in your pricing Procedure.
    If the Net price is calculated before the Application of taxes then these may be getting added as the effective price but not to the net price.Please check the same
    The Functionality of NAVM/ NAVS is working, as per required.
    Thanks & Regards
    Kishore

  • Making condition type mandatory for a particular po document type

    I have 2 po document type namely local po and international po. i want a particular condition type ZLCS to be picked automatically as soon as the user picks the po document type.

    Hi,
       You may check the condition technique through a new condition table with PO document type. You may proceed as below:
       You may append the standard MM condition structure to include the PO document type field (in structure KOMPAZ), with the help of abapers . Add the field to condition catalogue in the path: OLME - Conditions - Define Price Determination Process - Extend Field Catalog for Condition Tables.
        Now, you can create condition table with document type field in M/03. Maintain the condition table in the access sequence in M/07. Assign the access sequence to condition type in M/06. Include the condition type in pricing procedure. Maintain condition record for the condition type with required document type in MEK1.
        Check the procedure and revert back in case of any doubts.
    Regards,
    AKPT

  • Checking for the condition types using case statement

    hi folks,
    I have a lot of condition types that I have to check for and I am using case statement to do that. The code goes like this.
    case wac-kschl.
            when 'ZRAT' OR 'ZAGR' OR 'ZRCR' OR
                  'Y098' OR 'Y007' OR 'ZREW' OR 'Y106'        OR 'ZTSR' OR 'Y127' OR 'Y125' OR 'Y126' OR 'Y124' OR 'Y157' OR 'Y092' OR 'Y085' OR 'Y090' OR 'ZMZD'
    OR 'Y215' OR 'Y214' OR 'Y111' OR 'ZC$D' OR 'ZAUD'.
    up till here it is working on errors and when I add few more condition types to the case statement it is throwing the error.
    I have to check for all the condition types out here.
    How can I correct it? Is there a better way to do it?
    thanks
    Santhosh

    Hi Santhosh,
    I think that your CASE statement has a flaw. The line length of one of the lines is too large. You need to insert a carriage-return to shorten it (or press the button 'Pretty Printer').
    The code would look nicer like this:[code]  CASE wac-kschl.
        WHEN 'ZRAT' OR 'ZAGR' OR 'ZRCR' OR 'Y098' OR 'Y007' OR 'ZREW'
          OR 'Y106' OR 'ZTSR' OR 'Y127' OR 'Y125' OR 'Y126' OR 'Y124'
          OR 'Y157' OR 'Y092' OR 'Y085' OR 'Y090' OR 'ZMZD' OR 'Y215'
          OR 'Y214' OR 'Y111' OR 'ZC$D' OR 'ZAUD' OR 'Z001' OR 'Z002'
          OR 'Z003' OR 'Z004' OR 'Z005' OR 'Z006' OR 'Z007' OR 'Z008'
          OR 'Z009' OR 'Z010' OR 'Z011' OR 'Z012' OR 'Z013' OR 'Z014'.
        Do your thing here
          WRITE: / 'OK'.
        WHEN OTHERS.
          WRITE: / 'NOT OK'.
      ENDCASE.[/code]If this will not work for you, you could try a different approach:[code]* Local definition
      DATA:
        var_list(1024).
    Build variable string for checking
      CONCATENATE 'ZRAT ZAGR ZRCR Y098'
                  'Y007 ZREW Y106 ZTSR'
                  'Y127 Y125 Y126 Y124'
                  'Y157 Y092 Y085 Y090'
                  'ZMZD Y215 Y214 Y111'
                  'ZC$D ZAUD'
             INTO var_list
        SEPARATED BY space.
    Check if the correct value is supplied
      IF var_list CS wac-kschl.
      Do your thing here
        WRITE: / 'OK'.
      ENDIF.[/code]Hope this helps you a bit.
    Regards,
    Rob.

Maybe you are looking for