Selecting a document field for a field in a condition table/access

Hello
I created a pricing condition table using field WGHIE from the standard field catalog.
Img/SD/Basic Functions/Pricing/Pricing Control/Define Access Seq
I can assign the table to a access, but when I try to do the field assigment it give's me the message "<i>Select a document field for WGHIE</i>"  at the field assignment part.
In the fields display the WGHIE field has nothing listed in the Doc Field and it's grayed out so you cant change it.   Also in the I/0 field its red lighted
Any ideals as to how I can fix this.   
Thanks

Rudy,
For more information, see Transaction SPRO via the path 'Sales and Distribution -> System Modifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing' and OSS Note 21040
REWARD IF U FINDS THIS AS USEFUL...
Regds
MM

Similar Messages

  • SDIMA: Values for field SUPP_EXIST in condition table CNCCRMPRCUS801 differ

    Hi Experts,
    when checking condition records consistency between CRM and ERP via transacation SDIMA we get the following error for one of the conditon records: 'Values for field SUPP_EXIST in condition table CNCCRMPRCUS801 differ'. Can anybody explain to me where this message could come from? To my understanding field 'SUPP_EXIST' only exists in CRM condition tables for technical reason. So no way to compare this against an ERP condition table field, is there?
    And related to this: I found that this error message is triggered from method CL_CND_DIMA_CRM->COMPARE_MBDOC. As the DIMA-Compare is triggered asynchronously and just setting a break-point is no option therefore, I was wondering if anybody knows a way of debugging this method in order to find out what the coding does in detail before the message is thrown.
    Thanks a lot for your help!
    Cheers,
    Jens

    Hi Brian and the other Experts,
    thanks for your help. Unfortunately, I don't have a single record with this problem but a lot more. So it is not possible to correct this manually. Also, I would not know how to correct this anyhow as I don't understand what field in R/3 should map to field SUPP_EXIST in CRM condition tables. Let me explain:
    From my understanding, in CRM (leave aside scales) we have two database tables for each condition table, a central and a supplemental table. A condition record always creates a data record in the central table and nothing is inserted in the supplemental table in case that the fields form the supplemental table are not needed. However, when there are less common condition features involved (e.g. uppler limits), then an additional data record will be created in the supplemental table with the relevant data. And this is when field SUPP_EXIST comes into play as it is an indicator for the system that a data record exists for that condition record also in the supplemental table.
    The condition record data model in R/3 is completely different. For CRM condition table CNCCRMPRCUS801 the following tables in R/3 are involved: A801, KONH and KONP. And there is a data record for each of them for a given condition record. There is no concept of having a supplemental table as far as I understand it so where exactly would I find this SUPP_EXIST in R/3 so that I can make sure it does not deviate from the data in CRM?
    Would be great if someone could give me another hint. What am I getting wrong?
    Cheers,
    Jens

  • Need to add new fields to the condition table

    Hello All,
    The requirement is to create the new condtion table for MM containing the following fields and maintain the entries in this table:
    - client
    - characteristic
    - class
    - internal characteristic.
    THe condition tables are created via tcode M/03 or through the customizing path
    Material Management > Purchasing > Conditions > Define Price Determination Process > Maintain Condition Table.
    The problem which i am facing is as follows :
    -SAP has the standard procedure for the generation of the condition tables . Selected fields are made available by SAP in the field catalog and we can select only from the those available fields. Once we select the required fields the condition table is automatically generated in the background.
    -As the requirement is, we need to have 4 fields in the generated condition table (client, characteristic, class and internal characteristic), but the problem is that none of these fields are available in the field catalog which is provided by SAP (in tcode M/03, M/04 and M/05).
    -Designing of the Z table wonu2019t be useful as we would not be able to use the Z table as the condition table.
    Can you please suggest how can we add the desired field to the existing field catalog in M/03 or is there any other alternate solution to this ?
    Thanks in advance for your help.

    >
    Rinkesh Doshi wrote:
    > Hello,
    >
    > The specific ABAP question which I have is :
    >
    > Is there any way in which we can enhance the existing field catalog in M/03 tcode to include the 4 new fields (client ,characteristic,class,internal characteristic) ?
    >
    > Thanks.
    Please post your code which you developped until now and show us where the problem is. I cant see any ABAP related question.

  • New field creation in Condition Table?

    Hi Gurus
    I want to know whether it is possible to add a new field in field catalogue whle creating a condition table. I want to add Chapter Id of the material.
    Thanks
    Rishi

    Hi Rishi,
    Follow below example-
    Add a Field To New Condition Table in Pricing
    Add a field to a new condition table in Pricing (Condition Technique):-
    I will explain you the process with below example...Please follow steps in below sequence-
    Try to add the filed from the field catalog.  In case the required combination field is not there, you can add the field through the following process to filed catalog and create the condition table.   It is most common that one or other time we need to use this function while configuring multi tasking & complex Pricing Architecture.
    Here I'm giving a simple guide to add fields to the Pricing Field Catalogues:
    For example you want to use field PSTYV ('Sales document item category') that is included in structure KOMP ('Pricing Communication Item') as a key for a condition table.
    When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.
    Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ, KOMKAZ, PSTYV are the other terms which we need to know about, to add Fields.
    Reason and Prerequisites: 
    For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG ('Allowed Fields for Condition Structures').
    Proceed as follows:
    1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short text, you can use, for example, 'ZZ - sales document item category' and as a field label, you can use the field labels of PSTYV.Save, check and activate your entries.
    2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:
    Component Component type:
    ZZPSTYV ZZPSTYV
    Save, check and activate the change you made.
    3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because structure KOMPAZ is included in both structures.
    4. Call up Transaction SPRO. Navigate to 'Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control' and execute 'Define Condition Tables'.
    Choose 'Conditions: Allowed fields' and include ZZPSTYV as a new entry.
    5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.
    6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:
    MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
    In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.
    Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.
    For header fields, use structure KOMKAZ instead of structure KOMPAZ and
    USEREXIT_PRICING_PREPARE_TKOMK instead of
    USEREXIT_PRICING_PREPARE_TKOMP.
    For more information, see Transaction SPRO via the path 'Sales and Distribution -> System Modifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing' and OSS Note 21040.
    Regds
    MM

  • Standard field for Country of Despatch in condition table

    Hello All,
    I want to created a condition table with Despatching Country, Destination Country, Tax Classificatio of Customer and Tax Classification of Material.
    In the allowed fields for selection, I am able to get the field LAND (country of despatch).  I have created the condition table and assigned in the access sequence.  But when I see the analysis in the sales order this field is picking destination country.
    I do not want to include Z field in the KOMK/KOMP struture, I want a standard field.  Can anybody hlep me out............
    Thanks & Regards,
    Sreehari.

    At my end, its absolutely right?
    TKOMK-ALAND is based on delivering/supplying plant.
    If that is not the case, then it is not standard, where TKOMK-ALAND is is not equal to T001W-LAND1.
    Take assistance of ABAPer in your team & check whether  any enhancement (Program MV45AFZZ, Form USEREXIT_PRICING_PREPARE_TKOMK) is done.
    Say, in enhancement sales organization country is used as the country of departure.
    Regards
    JP

  • Adding custom fields to the condition table in CRM

    Hi all,
    Our requirement is to download the sales conditions type from R3 to the CRM system. In one of the condition table we are trying to add shipping point( VSART ) and Special processing indicator (SDABW).
    For that we have added the fields in the structure CND_MAPT_ACS_REM_CUST (Comm. Structure Condition Exchange Customer Exit R/3 Fields) and we have added the fields in the field catelog in transaction ( /SAPCND/CTCT - Maintain Condition Tables). Then we have mapped these fields in the view V_CND_MAP_CNVFLD.
    Finally we run the adapter object of that particular table to download the details from R3, but the condition table in CRM is not getting activated, so the adapter object is giving the error.
    Please help in this.
    Thanks & Regards,
    Raghuram.

    Hello Raghuram,
    I feel that your issue is similar what i have faced, refer to my post:
    Link: [Issue in customer specific price;
    For solving this you can refer to detailed steps in,  Note 514952 - Download of customer-specific tables.
    Also additionaly you may need to run the report /sapcnd/rv12n001, as i also had to do so.
    If not solved then let me know the relevant message in SLG1
    Regards

  • How to select into a field of my internal table?

    Howdy,
    I have an internal table:
    TYPES: BEGIN OF T_OUTPUT,
            EQUIPMENT         TYPE  EQUI-EQUNR,
            DESCRIPTION       TYPE  EQKT-EQKTX,
            EQUIPMENT_CAT     TYPE  EQUI-EQTYP,
            MASTER_WARRANTY    TYPE  BGMKOBJ-MGANR,
            DELIVERY           TYPE  LIKP-VBELN,
    END OF T_OUTPUT.
    DATA: ITAB_DETAILS TYPE STANDARD TABLE OF T_OUTPUT WITH HEADER LINE.
    Now i'd like to do a slect from LIKP into the field ITAB_DETAILS-delivery, but his code doesn't work?
    SELECT VBELN FROM LIKP INTO table ITAB_details-delivery
             WHERE  VBELN IN S_VBELN
             AND VKORG  = P_VKORG
             AND WERKS  = P_WERKS
             AND ERDAT IN S_ERDAT
             AND LFART IN S_LFART.
    Does anyone know what I am doing wrong?
    I need to keep the name of the field as 'delivery' and I don't want to change its order in the internal table - Otherwise I'd ahve used the 'MOVE CORRESPONDING' command.
    Does anyone have any ideas?
    Thanks!

    STEVE,
    Modified Code:
    Get value for Delivery
       SELECT <b>SINGLE</b> VBELN FROM LIKP
           INTO ITAB_details-delivery
             WHERE  VBELN IN S_VBELN
             AND VKORG  = P_VKORG
             AND WERKS  = P_WERKS
             AND ERDAT IN S_ERDAT
             AND LFART IN S_LFART.
    Insert into Internal Table ASSUMING u have values for
    other fields in the Work Area.
    <b>  append ITAB_DELIVERY.</b>
    Thanks
    Kam

  • Lead Selection to be disabled for some of the records in Table

    Hi ,
    I have 5 records in table .User shouldn't be allowed to select four rows thosse four rows should be in disable mode just for display purpose.Only one Row must be allowed to select(lead select).
    How can I Achieve above Functionality.
    Thanks & Regards
        Kiran

    Hi Kiran,
    Probably you might have tried the following.
    Bind OnLeadSelect event to some action.
    And in that action method write the code to fetch selected lead and check if it is 0(first row) else set leadselection to 0
    int selectedRow = wdContext.node<node name>().getLeadSelection();
    if(selectedRow!=0)
        wdContext.node<node name>().setLeadSelection(0);
    With this code the user can not select any of the rows other than first.
    If this is not what u require please let me know
    Regards,
    Santhosh

  • WHAT IS USE OF CHANGE DOCUMENT FIELD?

    HI experts,
    go like this,
      mara->matnr->dataelement of matnr->further charecteristics ->change document
    in this if we select change document field what will be occured , if we deselect   thatfield what will be the changes and where will be reflected that changes.
      thanks,

    Hi,
    It is used as an Indicator for writing change documents
    <b>Use</b>
    This flag is used to create change documents for business objects.
    You can create a change document object for a business object. This change document object contains the tables in which the data of the business object is stored. Function modules that are called in the corresponding application programs and that log the changes at runtime can be generated from the change document object.
    Logging only takes place if the fields whose contents were changed refer to a data element that was flagged as relevant for the change document.
    You can go to the maintenance screen for change documents from the initial screen of the ABAP Workbench with Development -> Other tools -> Change documents.
    Regards,
    Padmam.

  • Cannot find a field for creating a condition table

    Hi all,
    I m trying to create a shipment scenarios which involves shipment cost based on prices,boxes,material....etc. to start with i tried to create a condition table, here the key combination needs to have the filed 'boxes' in it. I am not able to find it even in the master table. Is there any other place whr i can find it or how can i add this into the list?(master table)
    any input is highly appreciated.
    regards/aryan.

    Hi
    Try to ad the filed from the field catalog ,In case the required combination field is not there u can add the field through the following process to filed catalog and create the condition table.
    It is most common that one or other time we need to use this function while configuring multi tasking & complex Pricing Architecture.
    Here Aim giving a simple guide to add fields to the Pricing Field Catalogues:
    For example you want to use field PSTYV ('Sales document item category') that is included in structure KOMP ('Pricing Communication Item') as a key for a condition table.
    When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.
    Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ, KOMKAZ, PSTYV are the other terms which we need to know about, to add Fields.
    Reason and Prerequisites
    For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG ('Allowed Fields for Condition Structures').
    Proceed as follows:
    1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short text, you can use, for example, 'ZZ - sales document item category' and as a field label, you can use the field labels of PSTYV.Save, check and activate your entries.
    2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:
    Component Component type
    ZZPSTYV ZZPSTYV
    Save, check and activate the change you made.
    3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because structure KOMPAZ is included in both structures.
    4. Call up Transaction SPRO. Navigate to 'Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control' and execute 'Define Condition Tables'.
    Choose 'Conditions: Allowed fields' and include ZZPSTYV as a new entry.
    5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.
    6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:
    MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
    In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.
    Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.
    For header fields, use structure KOMKAZ instead of structure KOMPAZ and USEREXIT_PRICING_PREPARE_TKOMK instead of USEREXIT_PRICING_PREPARE_TKOMP.
    For more information, see Transaction SPRO via the path 'Sales and Distribution -> System Modifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing' and OSS Note 21040.

  • Fields in Field Catalog not available when creating condition table

    I  see that field HIEBO01 to HIEBO12 are available in Field Catalog, but I don't see these fields when creating condition table
    Please let me know what I am missing here.
    Any insight on this would be really helpful.  Thanks guys!

    you need to get them added to the pricing structure KOMKAZ or KOMPAZ based on whether you need @ header level or @ item level respectively.
    and then add the logic in the sales order user exit for these added field in the pricing_prepare_TKOMK or pricing_prepare_TKOMP...again based on header level or item level.....
    Then go back to the field catalog and select from the respective structure and add them, Then you can see them when creating cond tables.
    Hope this helps. Hope i havent misunderstood your query.,
    Regards
    Sai

  • Please help me with selecting the right institute for me

    HI All,
    Please help me which institute I should select for my SAP SD training?
    ONE INSTITUTE COVERING THE FOLLOWING TOPICS:
    Sales overview
    Enterprise structure related to SD
    Master data, like Customer master data, material master data, condition master data and Output master data.
    Partner determination
    Sales document types
    Item categories
    Schedule line categories
    Pricing: Condition table, access sequence, Condition type, pricing procedure
    Stock Posting
    Free goods
    Bills of Material
    Material determination
    Material Listing and Exclusion
    Incompletion logs
    Revenue account determination
    Credit management
    Outline agreements like quantity contract, value contract and scheduling agreements
    Shipping process like Shipping point determination, Route determination, Shipping conditions picking ,PGI
    Delivery types
    Delivery item categories
    Invoice process
    Billing types
    Special sales processes like cash sales, rush orders ,consignment process and Third party process
    Return sales process
    Credit memo process
    Debit memo process
    Availability check
    Rebate processing
    Intercompany sales
    Output determination
    Copy control
    Integration with MM,FI
    Technical topics like ABAP tables, user exits and IDOC’s
    Real time scenario’s
                   OR
    OTHER INSTITUTE COVERING THE FOLLOWING TOPICS:
    1. Introduction to Supply chain management
    2. Introduction to SAP ERP package
    3. Introduction to ASAP implementation methodology
    4. Lecture Demo on Basic navigation skills in SAP R/3
    5. SAP landscape. Tips and tricks
    6. Introduction to Enterprise structure in SD
    7. Overview of Material master records
    8. Demo on ROH, HAL and FERT creation
    9. Hands on exercise on creation of material mastesr records in SAP
    10. Introduction to SD master data (Business partners, conditions and outputs)
    11. Introduction to order processing and Demo
    12. Hands on exercises on sales order processing
    13. Introduction to delivery process, picking and post goods issue process
    14. Introduction to stock transport orders and inter-company stock transport Orders
    15. Exercises on delivery with respect to sales orders
    16. Introduction to billing process (Customer billing, Inter-company, Proforma, Credit memo and Debit memo)
    17. Introduction pricing procedure, condition records, condition tables and access sequence.
    18. Configuration on SD sales order types, delivery and billing
    19. Warehouse management overview
    20. Introduction to SAP WM configuration
    21. Demo by instructor on configuration
    22. Develop configuration scripts
    23. Introduction to develop BPP
    24. Hands on exercises to students
    25. Introduction to WM master data
    26. Introduction to transaction data in WM
    27. Hands on exercises on creation of master data elements in WM
    28. Hands on exercises to students on WM transaction data
    29. Introduction to CTS process (SE10, SCC1)
    30. Demo on WM business scenarios and integration points
    31. Introduction to develop integration test scenarios. Develop test scripts
    32. Introduction to OSS notes and SAP Help
    33. Introduction to EAI tools, FID, RF Gun, MDE, SAP console and hand held devices
    34. Introduction to SAP bold on tools (SRM, CRM, BW, SEM, GTS, CIC, FSCM, DP, SNP, PP/DS, GATP, CIF and Plug in)
    35. Introduction to quick reference guides, cheat sheet, FAQ, work instructions, job aides, transaction aides, work instructions and change management
    36.Interface between SD & FI
    37.C forms, H forms
    38.Excise Related Invoices
    39.CIN configuration (taxes)
    40. Debugging with help of ABAP Tool
    41.Excise Returns Process with pricing details
    42.Order, Delivery, Billing, exicise, Output types configuration

    You should talk to various institute.

  • Add a new field to an existing Condition table

    How can I add a new field to an existing condition table?
    I have table 971 and I want to add INCOTERMS (INCO1) to this existing table but do not see how to add it.
    Thanks

    Hi Vicky,
        I dont think you can add new fields to the condition table once you have activated the condition table.
    SAP says you can only make limited changes to the condition table, like changing the description, fast entry screen, header and footer fields, but not able to add new fields to the table, and I think that is the correct approch or else for the same table you will have two sets of condition records.
    Please refer to the below link:
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/de/7a8534c960a134e10000009b38f83b/frameset.htm
    What you can do is create a new condition table with additional field and assign this table before the currently used table in the access sequence.
    Hope this helps.
    Regards
    Raj

  • Condition table field order

    Hello folks,
    Is it important to list the fields in a condition table in the proper order ?
    I do not think so and like to clarify with you pls.
    regards
    Ravi

    Hi
    A condition table defines the combination of fields (the key) that identifies an individual condition record. A condition record is how the system stores the specific condition data that you enter in the system as condition records. For example, when you enter the price for a product or a special discount for a good customer, you create individual condition records.
    Example
    Example of a Condition Table
    A sales department creates condition records for customer-specific material prices. The standard R/3 System includes condition table 005 for this purpose. The key of table 005 includes the following fields:
    Sales organization
    Distribution channel
    Customer
    Material
    The first two fields identify important organizational data and the last two fields express the relationship between customers and specific materials. When the sales department creates a condition record for a material price or discount that is specific to one customer, the system automatically uses condition table 005 to define the key and store the record.
    AS per SAP Help
    regards
    Prashanth

  • Adding SERVICE_ORG_RESP_SHORT field to Condition Table

    Dear Experts!
    We want to use the SERVICE_ORG_RESP_SHORT field in our Condition Table to define product Pricing. The problem is it doesn't exist in a Field Catalog (SPRO -> CRM -> Master Data -> Conditions and Condition Technique -> Condition Technique: Basics -> Create Field Catalog).
    We see two possible ways of dealing with this issue:
    1) Adding SERVICE_ORG_RESP_SHORT field into Global Field Catalog (SPRO -> CRM -> Master Data Conditions and Condition Technique -> Condition Technique: Basics -> System Configuration for Condition Technique -> Set Up Usage -> folders "Global Field Catalog: Fields" and "Global Field Catalog: Data Elements").
    2) Using BAdI (SPRO -> CRM -> Basic Functions -> Pricing -> Define Settings for Pricing -> Adopt User-Defined Fields).
    Please, tell us, which of these ways is correct?
    Kind Regards,
    Alexander Smirnyagin.

    Hi Alexandr,
    the first step mentioned above is required to define the field, so that you can use it to create a conditon table based on it and maintain master data for that condition table. In addition, you should implement the /SAPCND/ROLLNAME BADI for the field.
    The second step described above is required to integrate the field for transaction processing, e.g. in a sales or service order. You need to define which order value should get passed to your pricing attribute.
    Best Regards,
    Michael

Maybe you are looking for

  • Turning off video mirroring

    I have an imac G5, and I just got an apple video adapter so that I can watch DVDs and Quicktime movies and such on my old TV via the composite video connector. Works great, except that when I plug the connector in, my imac automatically reduces the r

  • Best Workflow for Subtitles

    I'm editing footage that is in French and Creole, and I only speak English. Basically, I need a method of editing, where the footage already has the English subtitles on it, and I simply edit that footage in FCP. At the moment, I only have the raw fo

  • How to print specific image size?

    Hi Gang - how do I print a 11x15" image onto 13x19" photo paper?  At first it seems easy, but things aren't making sense. Here's what I did: I exported the photo and used the LR image resize dialog area to 11x15" - easy. I imported the exported image

  • Show serverfarm issue

    Hello Does anybody know how to figure out the reason why I can see a lot of failures in the show serverfarm output sh serverfarm test serverfarm     :test, type: HOST total rservers : 4                                                 ----------connec

  • Edit mp4

    hello to those people that have the mercury play back engine i wonder if you can edit mp4 without rendering and export it to mpeg2 format please try this for me and let me know if it work i would like to buy the card right away thanks guys