Creation of Customized field for  Pricing Condition tables

Hi Friends
I have a requirement to create a  Pricing condition table with Customized field starts with 'Z'  and
Field length should be more than 80.
After creating New Customized Field, system  is not allowing to create Pricing Condition table and giving error 'Too Many fields selected (larger than 100 bytes)'.
Could you please advice how to over come this error and Maximum field to create Pricing  condition table .
Thanks
Ravi

Hi there,
Table & table attributes are defined by the ABAPers. Not by finctional consultants.
You need to have an access key to define new tables & access sequence.
Check with your ABAPer. He will be able to help you with that.
Regards,
Sivanand

Similar Messages

  • How Update Custom fields for EABL DB table by using BAPI_MTRREADDOC_UPLOAD

    Hi friends,
    How can I Update Custom fields for EABL DB table by using BAPI_MTRREADDOC_UPLOAD
    for the parameter EXTENSIONIN of type BAPIPAREX
    I am passing the Structure as BAPI_TE_EABL
    in that structure MRIDNUMBER as EABL-ABLBELNR field value
    ZMESSAGE some text of 30 char and
    ZSKIPC of 2 char
    but I am not able to update that data for the MRIDNUMBER (ABLBELNR ) in DB table EABL
    I am getting RETURN Structure message type E
    as
    "Upload interim entries: Maintain one table only"
    Can any one provide me solution
    Thanks in Advance
    Ganesh

    Hi,
    Refer the following SAP notes.
    1. Note 485557 - BAPI_REQUISITION_CREATE: 'EXTENSIONIN' customer enhancements
    2. Note 584902 - BAPI_REQUISITION_CHANGE: ExtensionIn not connected
    3. Note 792132 - EBAN, EBKN: user-defined fields are not filled
    Regards,
    Harish

  • Custom Report for Pricing Conditions Master

    Hi Everyone,
    We know that Pricing Conditions Master Data is stored in KONH and KONP. If a condition is populated in a document then transactional data can be obtained from KONV with 'condition record number' as the foreign key.
    The requirement is to design a custom report that lists for order items the pricing conditions (basic price) that are not populated in the sales orders. The pricing is not carried out in these orders as these are not chargeable orders, but the user wishes to know in an existing custom report the price from the conditon master data.
    The idea is that the sales order has no pricing calculated but how much Sales Price the material has as per the price condition master record.This can be known by the custom report.
    Visiting the standard prcing preports like V/LD is laborious for the user and wishes to add a column in an exisitng report of order item list for the price of each order item.
    The challenge here is that in KONH there is no field for material exlusively. It gets stored as a text and hence fetching data from this table for a given material seems difficult. Let us remember that we are not refering to any sales order while accessing data from KONH or KONP.
    Any thoughts / views on how this can be achieved are most welcome.
    Thanks,
    Hemant

    You will have to work on exact condition table in access sequence instead of KONH. For eg: If condition table in access sequence is 601 then you will have fetch the condition number KNUMH from table A601 (prefix A before the condition table number). With the KNUMH you can get the condition value from KONP.
    Regards,
    GSL.

  • 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

  • Adding custom field in pricing condition structure (BADI CRM_COND_COM_BADI)

    Hi,
    I need to add a custom field (ZCITY) to the structure : CRMT_ACS_H_COM and I need to populate this field in the BADI: CRM_COND_COM_BADI in the method : HEADER_COMMUNICATION_STRUCTURE.
    However, my concerns are:
    1. How to add the new field to this pricing structure? Is there any specific procedure to do that?
    2. And once the field is added and populated with the value in BADI, where the pricing calculation takes place based on this custom field?  Do we need to to implement any other BADI's or any pricing routines? I am little confused here.
    Could you please help me on this?
    Bottom line is : A custom field calles ZCITY needs to be added to the pricing structure and freight cost determination should take place based on this new field ZCITY.
    Thanks,
    Sandeep

    Hi Sandeep,
    if the field is used in the condition download from ECC please also check SAP note 514952.
    1. The field is added via the field catalogue maintenance at IMG: Customer Relationship Management -> Basic Functions -> Pricing -> Define Settings for Pricing -> Maintain Field Catalog. As you save or generate the field catalogue the structure will be updated with your field.
    2. Whether you need to implement a JAVA routine for the pricing of this particular condition is defined in the corresponding pricing procedure.
    Best Regards,
    Michael

  • Field Catalog (Output Billing) for new Condition Table

    Dear all,
    I am struggling with new Field Catalog Fields for my Condition Table
    To determine two different printers I have tried to add ERNAM (SAP author of document), and to print or not to print certain documents depending on Customer Number (Proforma and Packing list) I have tried to add KNDNR
    No matter which field I add, the system warns me "Choose the key from the allowed namespace"
    and in the Acces Sequence later on I am getting a red flag.
    So far I have gotten advise that I need to ABAP user exits, create tables and lots of tech stuff.
    I want to configure the system, not program it.
    So: Can I add fields to the Field Catalog without being an ABAPPER or can I not?
    Thanks,
    Nickelodeon

    Hi,
    You can add the field in the OUTPUT COMMUNICATION STRCTURES
    OUTPUT COMMUNICATION AREA for Billing is KOMKBV3 and the Include is KOMKBZ5.
    If you want to add the new field ERNAM then add this field from the VBRK
    Enter the field ZZERNAM in the commnication strctre KOMKBV3  in the include KOMKBZ5 in the data dictionary
    By entering the field in the Include KOMKBZ5 you automatically include it in the commnication structre KOMKBV3
    Next add the field  ZZERNAM in the communication table KOMB
    Now assign the values to the field in the FUNCTION MODULE   KOMKBV3FILL_
    Include the ZZERNAM in the field catalogue for the CONDITION TABLE of Billing documents .
    After doing this you can check the new field in the FIELD CATALOGUE in the CONDITION TABLE for OUTPUT DETERMINATION.
    Please try this for your Application area ( as i gave example for Billing documents) and revert back if you need any more details
    regards,
    santosh

  • 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

  • Mandatory Fields for IDOC ORDERS01 for Pricing Condition EDI1 to trigger

    Hi ,
    I'm Testing an Inbound ORDRSP using we 19  for Pricing Conditions EDI1. What are the Mandatory Fields for IDOC ORDERS01
    Thanks

    hello,
    I think it's better to execute VA01 to create a sales order; in that way you should have an idea of mandatory fields.
    Thanks.

  • Enabling Quote custom field for External Pricing Response

    Hi All,
    Using UI configuration (adaptation) we are able to define new fields and enable them for standard web services. The result is that they are included in the relevant WSDLs and can be mapped using PI/HCI to equivalent fields in an external system such as SAP ECC.
    Looking at Quote's for example, we have defined a new field at Product Item Line level and have the following services we can enable it for.
    Enabling for the CustomerQuoteRequestExternalSalesDocumentDataOut outbound service adds the field to the External Pricing request part of the resulting WSDL, however it is not enabled for the response which is key to our requirement.
    Is it possible through PDI to enable this field for the inbound equivalent for CustomerQuoteRequestExternalSalesDocumentDataOut??? If not, is it possible to create the field through PDI and enable it that way?
    Thanks
    Indi

    Hi Chandan,
    Thanks for the response.
    The External Pricing interface for Quotes is synchronous so has no IDoc as such. We send some parameters to fetch a price from SAP ECC, and the response contains all the pricing information.
    In terms of the response, we're able to pass the value we need from SAP ECC to HCI, however there is no place in the WSDL for us to pass it to the field we have defined in C4C.
    The WSDL for External Pricing contains both the request and response structures, therefore two root nodes. Adaptation only allows us to enable the field for the request (outbound) node. I'm trying to work out how we can enable our custom field for the response (inbound) node within the WSDL structure.
    Thanks
    Indi

  • 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

  • Changing the Sequence of the Access Sequence for Pricing Condition Type

    Hi Friends,
    We have an access sequence to determine the pricing. We have 8 key combinations for the same.
    Customer/Plant/Material/Batch
    Sales Org/ Dist Ch/ Cust Region/Plant/Material/ Batch
    Price List Type/Currency/Plant/Material/ batch
    Plant/Material/ Batch
    1st 4 is with batch. and 2nd 4 is without batch.  At the time of implementation ie., before 8 years the 1st 4 key combinations were used.  But now based on the business need we are not using the 1st 4 key combination rather we are using the 2nd 4 which is without batch.
    My question is that can we change the access sequence so that while the system fetches the price it need not go through the entire ( 91,02,401 ) records.
    If this is possible then
             Will there by any impact during viewing of past data?

    Hi,
    There are two options.
    1)Change the validity dates for those condition records to earlier date.
    2)Usually the sytem checks from top to bottom.If it finds the record in first table then it will return that value and stop searching.
    As your not required things are on the top,remove the condition records for them using VK12 T.Code.And maintain the records for what condition tables you are required.
    Regards,
    Krishna.

  • Function module to change the value for pricing condition type

    Hello experts,
    I want to change the value for pricing condition type for an item in the transaction CRMD_ORDER.
    I used many function modules but none are working.
    Please kindly suggest a function module that will change the value for a condition type .
    I have used the following function module but its not working, please correct the coding if anything needs to be changed or added. Please help me .
    Thank you.
    CLEAR PRCD_COND.
         SELECT SINGLE * FROM PRCD_COND WHERE KPOSN = WA_ORDERADM_I-GUID AND
                                              KSCHL = COND_TY.
      IF SY-SUBRC = 0.
    *    MOVE-CORRESPONDING PRCD_COND TO L_COND_CHG.
    *    CLEAR L_COND_CHG-KBETR.
        L_COND_CHG-STUNR = PRCD_COND-STUNR.
        L_COND_CHG-KBETR = COND_PRC.
    *    L_COND_CHG-KSCHL = COND_TY.
        INSERT L_COND_CHG INTO TABLE T_COND_CHG.
    L_HEAD_GUID = CRMD_ORDERADM_H-GUID.
    L_ITEM_GUID = WA_ORDERADM_I-GUID.
    INSERT L_HEAD_GUID INTO TABLE HEAD_GUID.
    INSERT L_ITEM_GUID INTO TABLE ITEM_GUID.
        CALL FUNCTION 'CRM_ORDER_READ'
         EXPORTING
           IT_HEADER_GUID                    = HEAD_GUID
           IT_ITEM_GUID                      = ITEM_GUID
         IMPORTING
           ET_ORDERADM_H                     = LT_ORDERADM_H
           ET_ORDERADM_I                     = LT_ORDERADM_I
           ET_PRIDOC                         = IT_PRIDOC_RD
           ET_DOC_FLOW                       = T_DOC_FLOW
    *     CHANGING
    *       CV_LOG_HANDLE                     =
    *     EXCEPTIONS
    *       DOCUMENT_NOT_FOUND                = 1
    *       ERROR_OCCURRED                    = 2
    *       DOCUMENT_LOCKED                   = 3
    *       NO_CHANGE_AUTHORITY               = 4
    *       NO_DISPLAY_AUTHORITY              = 5
    *       NO_CHANGE_ALLOWED                 = 6
    *       OTHERS                            = 7
        IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
    MOVE-CORRESPONDING LS_PRIDOC_RD TO L_PRI_COND.
    INSERT L_PRI_COND INTO TABLE PRI_COND.
    LOOP AT IT_PRIDOC_RD INTO LS_PRIDOC_RD.
    MOVE-CORRESPONDING LS_PRIDOC_RD TO L_PRIDOC_CHG.
    L_PRIDOC_CHG-PRIC_COND = PRI_COND.
    L_PRIDOC_CHG-REF_GUID = LS_PRIDOC_RD-GUID.
    L_PRIDOC_CHG-COND_CHANGE = T_COND_CHG.
    INSERT L_PRIDOC_CHG INTO TABLE PRIDOC_CHG.
    ENDLOOP.
    LOOP AT LT_ORDERADM_H INTO LS_ORDERADM_H .
    MOVE-CORRESPONDING LS_ORDERADM_H TO L_HEADER.
    INSERT L_HEADER INTO TABLE HEADER.
    ENDLOOP.
    LOOP AT LT_ORDERADM_I INTO LS_ORDERADM_I.
    MOVE-CORRESPONDING LS_ORDERADM_I TO L_ITEM.
    INSERT L_ITEM INTO TABLE ITEM.
    ENDLOOP.
    L_FIELD-FIELDNAME = 'STUNR'.
    INSERT L_FIELD INTO TABLE FIELD.
    L_FIELD-FIELDNAME = 'KBETR'.
    L_FIELD-CHANGEABLE = 'X'.
    INSERT L_FIELD INTO TABLE FIELD.
    L_INPUT-FIELD_NAMES = FIELD.
    L_INPUT-REF_KIND = 'E'.
    L_INPUT-REF_GUID = LS_PRIDOC_RD-GUID.
    L_INPUT-OBJECTNAME = 'PRIDOC'.
    INSERT L_INPUT INTO TABLE INPUT.
        CALL FUNCTION 'CRM_ORDER_MAINTAIN'
         EXPORTING
           IT_PRIDOC                     = PRIDOC_CHG
         IMPORTING
           ET_EXCEPTION                  = EXCEPT
         CHANGING
           CT_INPUT_FIELDS               = INPUT.
        IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
    REFRESH EXCEPT.
    CALL FUNCTION 'CRM_ORDER_SAVE'
      EXPORTING
        IT_OBJECTS_TO_SAVE         = HEAD_GUID
    *   IV_UPDATE_TASK_LOCAL       = FALSE
    *   IV_SAVE_FRAME_LOG          = FALSE
    *   IV_NO_BDOC_SEND            = FALSE
    *   IT_ACTIVE_SWITCH           =
    IMPORTING
       ET_SAVED_OBJECTS           = SAVED
       ET_EXCEPTION               = EXCEPT
       ET_OBJECTS_NOT_SAVED       = UNSAVED
    * CHANGING
    *   CV_LOG_HANDLE              =
    * EXCEPTIONS
    *   DOCUMENT_NOT_SAVED         = 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.
    COMMIT WORK AND WAIT.

    Hi,,
    To be able to call a function module in an update work process, you must flag it in the Function Builder. When you create the function module, set the Process Type attribute to Update with immediate start
    Alternatively u can use this function module.
    CRM_STATUS_DATA_SAVE_DB
    BAPI_CUSTOMERCRM_CHANGE (If u wish to use a bapi for this).
    Also , Let me know what error you got when implementing other function module.Does the function module didnt return any error but still the value is not changed for pricing condition type?

  • Custom Fields to Contract 'Conditions' Screen

    Hi
    Please share how to add custom fields to Contract 'Conditions' screen just like 'Unit Price'.
    As there is no '_CI' table for conditions table, we are not able to implement the same. We also tried using BDT but to no avail.
    Regards, Sekhar

    Thanks for the reply Bala
    The requirement is to add three more informational fields beside/below the Unit Price. Those fields should hold data, condition wise. i.e. it requires to add 3 more columns in VICNCN table to which I'm afraid there is no custom include available. Also we referred note 690900. Please help how to proceed.
    Thanks, Sekhar

  • Add a custom field for Product Allocation

    Hi experts,
    I have copied S140 to S501 to add a custom field for product allocation.
    I have added the custom field in MCVBAKUSR, so it is visible in MCVBAK.
    However, I don't know whether I can populate data into custom field. I searched in forum, someone said it can be done in SAP enhancement MCS10001. But it can't work. I have tried to place a break-point in the code, and seems that throughout the order creation and product allocation check, it hasn't get into the codings in enhancement MCS10001.
    Can anyone give me some idea on it? Thanks.

    You should have simply extended VBAK table. It would've taken care of extending MCVBAK, etc. Then VBAK field would have to be populated in a user exit USEREXIT_CHECK_VBAK in MV45AFZB, when a document is being created/changed.

  • SD Pricing condition tables.

    Hi,
    I have 3 SD pricing condition tables in ECC that starts with name Axxx. I need to extract the data from these 3 tables thru a generic extractor. Anybody has an idea on how to get the delta from these tables? Any help would be highly appreciated.
    Thanks,
    Rajesh.

    Hi,
    Generic delta can be obtained based of the key field you give in generic delta tab.
    Note make sure that you need to create a view  by joining the relevent tables which contains 3 pricing conditions.
    based on that you can give the key field name for delta etraction. the system will automatically gets the delta.
    santosh

Maybe you are looking for