Standard field to be used in place of Product Hierarchy

HI,
We are going to have a new material in our system but we do not want to create a new Product Hierarchy for that. Infact we want that if any new material is created, we need not creata any new product hierarchy for that.
Please suggest what standard field can we use instead of Product Hierarchy without impacting the system .
Thanks.
Rudresh

Hi Rudresh,
Product Hierarchy is a informative field and can be used for reporting purpose. For a specified material type, if you dont want to maintain product hierarchy, make that field optional using OMS9.
Regards,
Amol

Similar Messages

  • How to add a standard field to the Product search criteria ?

    Hello all,
    despite my searches on google and sdn, i'm still  confused on how to add a standard field in the search criteria of the Product seach screens (component/view PRD01QR/Search for example) , I mean a standard Product field that is not included in the available fields list in the UI configuration tool.
    I found some explanations for adding a specific Z-Field, this is ok , but I'd like to add a standard field as a search criterion, namely the item category group.
    Could someone give me the needed detailed steps for this?
    thanks
    Ludovic

    Hi
    Chk ths link out :
    http://wiki.sdn.sap.com/wiki/display/CRM/Howtoaddanexistingfieldtoasearchpageofadifferent+component
    Rgds,
    Swati

  • How to map customer field to standard field using BAPI_PO_CREATE1 ?

    Hi,
    i am trying to transfer a customer field from SRM to ECC60 through BAPI_PO_CREATE1;
    In SRM the EAN field does not exist; Thus we have created it.
    While transfering the PO to ECC, we try tu use BBP_PO_INBOUND_BADI to map the SRM field to the EAN11 field in EKPO.
    However, we do not find the EAN11 field in the BAPIPOITEM structure.
    Steps already done :
    BBP_CUFMAP
    How do we map a customer field coming from an external system to an ECC standard field ?
    Kind regards,
    Yann

    interface name is: SalesOrderCreateRequestConfirmation_In
    have a look at this link to get some more details:
    http://help.sap.com/esoa_erp2005/helpdata/en/44/62e384e370311de10000000a155369/frameset.htm
    is that what you need?

  • PC UI Advanced Search - Enhancement by standard fields of transaction table

    Hello,
    we are using CRM 5.0 SP13.
    We are familiar to enhance PC UI applications (BP+transactions) by EEW customer fields and how to use/hide them in the search functionalities etc.
    But now we need to enhance the advanced search for leads by the POSTING_DATE date of table CRMD_ORDERADM_H. Unfortunytely in PC UI advanced search structure for leads CRMT_BSP_LEA_SEARCH_ME the POSTING_DATE is not included like it is in the opportunity advanced search structure CRMT_BSP_OPP_SEARCH, where we were able to enhance the search easily by CRMC_BLUEPRINT_C customizing.
    The idea is to solve the problem to create EEW fields POSTING_DATE_FROM and POSTING_DATE_TO like they are existing in CRMT_BSP_OPP_SEARCH and use them in advanced search. So far no problem in creating and displaying the EEW fileds by CRMC_BLUEPRINT_C.
    But the part we are missing is to link the new EEW fields to the standard database-field POSTING_DATE and implement the search functionality "Searching by select option POSTING_DATE_FROM and POSTING_DATE_TO".
    Anybody any experience to link EEW-fields to standard fields of database tables for advanced search functionality in PC UI.
    Thank you for your help in advance.
    Best regards
    Marco

    Hi Marco,
    The best option here is to create redefination of the query method of the leads search class. Here you can first ensure that the call to the query method of super class takes place and the next would be do mapping between custom fields to local structure and then call the relevant API's to fetch the data.
    Best Regards, Adil

  • Can standard DO can be used as Receiver Generation DO?

    Can standard DO can be used as Receiver Generation DO? and the Std. DO can be mapped to RMM?
    If not, then what are the difference in the features of Standard DO & Receiver Gen DO?

    Hi Romi
    A Standard and RecGen DO are two different DO categories.
    A data object category defines a default flow definition for a data object. When you create a data object, you choose the data object category you want to serve as its template. The newly created data object inherits the flow definition from the selected data object category.
    You cannot use a Standard DO in place of a RecGen DO, coz they have fairly different functionalities.
    Standard DO has the basic functionality of transferring the data between DOE and client and vice versa.
    Where as Receiver generation (RecGen) data objects are used to generate the logical devices for the mobile clients for the purposes of distributing data to the appropriate subscribers. The fields defined in the receiver generation data object define the information to be extracted from the back end for storage in the device inventory. These fields are mapped to receiver meta model fields.
    You can use the following link to clarify more doubts you may have:
    http://help.sap.com/saphelp_nwmobile71/helpdata/en/8f/0b674240449c60e10000000a1550b0/frameset.htm
    Ask for more clarifications if you need any.
    Ankur

  • Implications of changing standard field names

    Hi
    We want to rename some of the fields in IMA11 transaction as the purpose for which the fields are being used by us is different from what the standard field names convey.
    Before changing the names, I would like to know if there will be any adverse implications of making that change including impact on upgrades/service packs etc;
    Appreciate all inputs on this.
    Thanks
    Sriram

    Thanks for the reply. These fields whereever they are appearing in other transactions and reports, we are going to use for same purpose and so if they appear with changed names at all places, it is ok with us.
    We are only changing the Field Label and nothing else.
    Want to know of any side effects from others who might have done such changes.
    Also any impact on upgrades.
    Thanks
    Sriram

  • Standard field for Net explosive mass (NEM) for dg documents

    Hi,
    I have searched standard fields in the material master and dangerous goods master but i can not find a standard field for Net explosive mass (NEM). This value is needed for dangerous goods documents.
    Is there anyone that know if there is a standard field for this or do I have to create one myself?
    Best regards / Gustav

    Hello Gustav
    sometimes SAP is saying that Enh.- Apck need to be activated and if you take a "close" look this it is not the case. It is sufficient to use new SPs.
    Now based on your reseach results:
    Actually the situtation regarding Enh.. Pack is like this:
    a.) to use EHS you need to "switch" (activate) the EA-APPL component; no way back ! possible !
    b.) to use Enh. Pack EHS extensions you need to "switch" (activate) the Enh.PAck => actually: no way back possible ! (SAP has announced that they are planing to change this behaviour; I did not follow this discussion; I believe actually there is no way back and personally I believe this (to go back) does not make sense in EHS environment)
    c.)  OPS_EHS_CI_1 is the Business function in Enh. pack 3
    d.) LOG_EHS_CI_2 is the Business function in Enh. pack 5 (now available to all customers).
    Therefore to my understanding this is the SAP approach: 1.) first activate EA-Appl, then OPS_CHS_CI_1 and then if suitable/necessary LOG_EHS_CI_2
    What are the pros and cons of activation?
    a.) in principal you are dealing with a "release" change (testing required; analysing new customizing activities etc. etc.)
    b.) to our experince there are in most cases "strange" effects at other places; therefore you need take care regarding the activation (example: we lost some EHS functions (which are part of the former release) in release change to ECC 6.0; these functions (yes they still exists but..) are only ! part of EHS after ! an "activation" of Enh. Pack 3)
    c.) at the end you get all  enlargements which are part of Enh. Pack (without a choice!
    In most cases the benefit is higher compared to the "technical" risks of the activation (on long term approach).
    Details of the functionality of OPS_EHS_CI_1 and/or LOG_EHS_CI_2 (what are the changes etc.) are explained on high level in help.sap.com and on detailed level on SAP marketplace; therefore I will not enumerate them.
    On SAP Marketplace you find a number of OSS hints "how to use Enh.Pack" / "How to activate" / Master Insturctions (Set up etc.) etc.
    Personally my impression is: both Enh.PAcks (3 + 5) contain usefullnew functions which could give benefit on mid and long term in using EHS.
    Keep in mind the SAP strategy: new functions  (PS: Enh. Pack 6 will get in Ramp Up this year (to my recent knowledge) and will contains further EHS extensions) will always be part of enh. pack. Only if the function is needed because of legal change a new function is delivered as SP (no activation necessary).
    With best regards
    C.B.
    Edited by: Christoph Bergemann on Apr 9, 2011 8:31 AM
    Edited by: Christoph Bergemann on Apr 9, 2011 8:36 AM
    Edited by: Christoph Bergemann on Apr 9, 2011 8:37 AM
    Edited by: Christoph Bergemann on Apr 9, 2011 8:37 AM
    Edited by: Christoph Bergemann on Apr 9, 2011 8:39 AM

  • Invisible the standard fields..

    Hello Friends,
       How can i disable account assignment fields such as gl account or business area..
       I also want to make appear standard field in basic data frame such vendor part # or catalog item..
      Is there any Badi available if is some sample coding please..
    John.

    Hi,
       To disable the account assignment fields,you will have to modify the template SAPLBBP_PDH_ACC_1000_1 of service BBPACCOUNT.
      To make appear Std fields in the basic data frame,you may have to modify the template SAPLBBP_SC_UI_ITS_300 of service BBPSC01 so that these fields are also displayed.Here,in the structure "GS_SCR_BASIC_I" whcih holds all the values of the fields in the basic data frame has these fields(vendor part /vendor part) so i dont think there will be any problem in modifying the template.You just need to see where you can display these fields in the basic data frame.
      Another approach would be..If you dont need certain fields in the basic data frame,in place of those fields you can display these fields.
    BR,
    Disha.
    Pls reward points for useful answers.

  • Add search help/drop down list to a standard field in MIR7

    Hi All,
    I have a requirement to add  a search help on one of the strandard field in MIR7. This field has no search help in dictionary (SE11). Do you have any idea on how to do this? Is there any exit that i can use to?
    Please help!
    Thanks in advance.

    Hi Akira,
    Please check the below threads.
    [how to create F4 for the standard transaction]
    [F4 HELP for standard field..;
    [http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/daeda0d7-0701-0010-8caa-edc983384237]
    [Re: Adding a field in standard search help;
    Edited by: Prasath Arivazhagan on Apr 13, 2010 5:38 AM

  • Adding a new SAP standard field to complaints result BOL

    Hi Experts,
    There is a requirement to add SAP standard field 'Posting date' to Advance search result BOL of complaints.
    This field already exists in search BOL and visible on WEB UI advanced search.
    The field is added as attribute in result context node of BT120S_CPL/AdvSearchComplRL through wizard.
    But, unable to see the values getting populated. Could you please let us know if any code to be written for getting values populated.
    Regards,
    Santosh

    Hi Santosh ,
    My previous post was based on the fact that you have added a model attribute. Since you have added the field as a value attribute and you want to use it for querying , then you would have to do the following
    a) Extract the value from the value node.
    b) Add the selection param so that 'posting date' is passed to the GENIL. You can use add selection param method in the Advanced query. Use the name of the field in the BOL & the value as yours.
    c) Get the result & show it on the way you want.
    This is same as it would have been when you had a model field. In that case also you would have extracted the value from model node. I see no difference here except that fetching the field. Rest of the steps remain the same if the field is available in BOL for advanced query.
    Yes the difference lies in showing it in the WebUI as now you would have to fill this value node manually. If you had a model node , the framework would have done this for you.
    But don't base your choice of model/value node on the ease of coding but on the business case.
    Regards
    Kavindra

  • Mapping of CRM BP standard field to ECC Standard field

    Hi Experts ,
    We have a requirement in which we need to copy "Identification Type" field (table field BUT01D-TYPE) in "Identification Tab" of Business Partner from CRM into ECC Standard Field 'Corporate Group' in Control Data in XD01 (Table Field KNA1-KONZS).
    Please let me know where I can do the mapping of the CRM field to ECC field for this requirement .
    thanks in advance.
    Anil

    Go to se19 and choose name for the implementaion and click create. Definition is 'CRM_DATAEXCHG_BADI'. Choose description for the implementation and Save your implementation. Next you have to implement method CRM_DATAEXCH_R3D_MBDOC_FILL by doubleclicking on it. Data coming from r3 are witen in table TI_BAPIMTCS. And to write data to crm you can use direct logic or fill structure of CT_BUS_TRANS_MSG.
    For more information about the badi goto SE18 and open badi CRM_DATAEXCHG_BADI and hit Documentation button.

  • MM - Material master data - move standard field to another view

    Hi everyone,
    ÉCC 6.0 - release 7.0.
    I've been adding many custom fields in Material master data MM01/02/03. Now I got a problem because we have to use a standard field in another view.
    The field MARA-HERKL is set up to 'SV'(attribute V_130F-PSTAT):
    Warehouse management = S
    Sales = V
    I want to add 'K - Basic data' in this field's attribute at OSMR Tcode , but this attribute is disactivated. I can not change this value.
    I've check this note 306966 that mention: You cannot create new entries and delete entries in client 000. This client contains only the entries delivered by SAP which are used for distinguishing customer-specific fields and SAP standard during the maintenance of the other clients.
    Is there any problem whether I delete this field and afterwards create it with the new values?
    I'm not in client 000. So, I want to just make sure I will do a legal change.
    thank you in advance,
    Alexandre

    None tips, Closed.

  • Issue in Updating Customer specific fields in WBS using BAPI_BUS2054_CREATE_MULTI

    Hi Experts,
    I am able to create the WBS element using BAPI_BUS2054_CREATE_MULTI.But the issue is i am not able to update customer specific fields even after passing the fields as per specification in Function module documentation. I have also created an implementation of BADI  as per below specification in FM documentation:
    Procedure for Filling Standard Enhancements
    Before you call the BAPI for each object that is to be created or changed,
    for which you want to enter customer-specific table enhancement fields, add a
    data record to the container ExtensionIn:
    STRUCTURE:    Name of the corresponding help structure
    VALUEPART1:   Key of the object + start of the data part
    VALUEPART2-4: If required, the continuation of the data part
    VALUPART1 to VALUPART4 are therefore filled consecutively, first with the
    keys that identify the table rows and then with the values of the
    customer-specific fields. By structuring the container in this way, it is
    possible to transfer its content with one MOVE command to the structure of the
    BAPI table extension.
    Note that when objects are changed, all fields of the enhancements are
    overwritten (as opposed to the standard fields, where only those fields for
    which the respective update indicator is set are changed). Therefore, even if
    you only want to change one field, all the fields that you transfer in
    ExtensionIn must be filled.
    Checks and Further Processing
    Using the methods ...CREATE_EXIT1 or. ...CHANGE_EXIT1 of the BAdI
    BAPIEXT_BUS2001, BAPIEXT_BUS2002, and BAPIEXT_BUS2054, you can check the entered
    values (and/or carry out other checks).
    In the BAdI's second method, you can program that the data transferred to the
    BAPI is processed further (if you only want to transfer the fields of the CI
    includes, no more action is required here).
    But still i am unable to update fields though i am able to create WBS with rest of the fields except  custom fields.
    I am using attached code to achieve this.Do we need to code anything inside method create_exit1 or create_exit2 implementation for BADI or
    Please help on priority

    Hi Rahul,
    First observation from your code is that i could not find the assignment for the field
    GWA_WBS_EXTIN-STRUCTURE. I hope you are not filling this field, that could be one reason for failure. Try to do it and let us know if you still have the problem.
    Br..
    Dwaraka

  • Update user defined fields in MARA using bapi_material_savedata

    Hi,
    I have this problem:
    I am creating materials from a Z table filled by another application (not SAP). I am using the bapi "bapi_material_savedata" to create the materials and it is working fine. But now I need to fill user defined fields in the MARA table from this Z table, and this fields, are not filled after using the bapi.
    I am using the bapi tables "extensionin" and "extensioninx".
    I have modified the BAPI_TE_MARA structure adding the ZZ fields of the MARA and the BAPI_TE_MARAX structure with the same fields but different data elements. So I have this structures/tables:
    BAPI_TE_MARA:
       MATERIAL - MATNR
       ZZDIM1   - ZZCHDIM1
       ZZDIM2   - ZZCHDIM2
       ZZDIM3   - ZZCHDIM3
    BAPI_TE_MARAX:
       MATERIAL - MATNR
       ZZDIM1   - BAPIUPDATE
       ZZDIM2   - BAPIUPDATE
       ZZDIM3   - BAPIUPDATE
    MARA:
    ..(standard fields of the MARA)....
       ZZDIM1   - ZZCHDIM1
       ZZDIM2   - ZZCHDIM2
       ZZDIM3   - ZZCHDIM3
    Here is the code that i'm using to update the extensionin and extensioninx tables:
    DATA x_bapi_te_mara TYPE bapi_te_mara.
      DATA x_bapi_te_marax TYPE bapi_te_marax.
      it_extensionin-structure = 'BAPI_TE_MARA'.
      it_extensioninx-structure = 'BAPI_TE_MARAX'.
    * the internal table it_material contains the data of the
    * ZZ fields
      MOVE-CORRESPONDING it_material TO x_bapi_te_mara.
      x_bapi_te_mara-material = it_material-matnr.
      x_bapi_te_marax-material = it_material-matnr.
      x_bapi_te_marax-zzdim1 = 'X'.
      x_bapi_te_marax-zzdim2 = 'X'.
      x_bapi_te_marax-zzdim3 = 'X'.
      it_extensionin-valuepart1 = x_bapi_te_mara.
      APPEND it_extensionin.
      it_extensioninx-valuepart1 = x_bapi_te_marax.
      APPEND it_extensioninx.
    Also i have an entry in the table T130F that i'm not sure i need.
    Please help me to fill this user defined fields !!
    Regards,
    Jesus

    I'm using both,
    x_bapi_te_mara-material = it_material-matnr.
    x_bapi_te_marax-material = it_material-matnr.
    The first line is from the x_bapi_te_mara structure and the second for the x_bapi_te_maraX.
    Thanks

  • Map a custom SRM field to a standard field in R/3

    Hello All,
    We have created a custom field in SRM and it needs to be transferred to one of R/3's
    standard field. it has to be done in both the classic and extended classic scenario.
    For the extended classic scenario I tried using the BADI BBP_ECS_PO_OUT_BADI
    but this is not getting called in the creation of local purchase order neither
    does it transfer the changes made to r/3
    As for classic scenario I tried using the BADI BBP_CREATE_BE_PO_NEW ~ FILL_PO_INTERFACE1
    but the structure cs_po1_document-IT_POITEM does not get filled up with the item_guid
    which needs to act as a reference field to read the table.
    At the backend i tried using the bbp_po_inbound_badi and tried to change the value in the
    debuggung mode. But it didn't carry the value to the field either.
    Thanks in advance,
    Prasanna

    1. The BADI BBP_CREATE_BE_PO_NEW will only be called in the classic
    scenario wherein the purchase order is directly created in the backend
    R/3 system.
    For extended classic scenario, kindly use the BADI BBP_ECS_PO_OUT_BADI
    instead.
    Please be sure that you have filled  BBP_CREATE_BE_PO_NEW  with these lines:
    CS_CTRL_ATT-BE_DOC_TYPE = 'SRM'.
    CS_CTRL_ATT-BE_STORAGE_CAT = 'DMS_C1_ST'
    Please also check the settings in the customing of the backend (DC10, DC20, DC30).
    2.  Please create test data in BAPI_PO_CREATE1 in backend system according to note 539978 As in the note described, please 
      - set the Parameter FBGENDAT 'X' in the backend system for the
        RFC user of the SRM system
      - execute the report FBGENDAT in the mode 'A'.
        after activating this report, test data will be created by every
        BAPI_PO_CREATE(1) call.
      - once you have a new entry in the SM13 of the backend system,
        please deactivate the generation of test data in report FBGENDAT.
    Please check the Data transfered from SRM.
    3, There are some field with will be cleared during MM processing when
    you run the BAPI_PO_CREATE1 with the data transfered from SRM.
    Examples : 
    Classic scenario.
    In this case you create service purchase order.
    For service purchase orders fields WEMPF and ABLAD(GR_RCPT and UNLOAD_PT in BAPI) are not filled when creating the document. It is absolutely not possible to have this unloading point/ Recepient on item level service documents. The account assignment is entered on service level and it is then used to determine the account assignment on item level.  So even if you were able to pass from SRM the unloading point/Recepient on item level in service documents it would be overwritten from the account assignment of services. This functionality won't be available in standard R/3.
    Please see note 118008 for more information.
    Extended classic scenario.
    As soon as you pass delivery address The system clears field EMLIF (supp_vendor in the BAPI interface). Do not pass delivery address and you will be able to have Vendor in the purchase order. Due to the fact that delivery address exist, a lot of fields in lt_item are cleared, including supp_vendor.
    Call stack:
    8 SAPL2012 FORM PROCESS_ADDR_TABLE
    7 SAPL2012 FORM CREATE_ITEM_ADDR
    6 SAPL2012 FORM PROCESS_NON_INTEGRATED_COMP
    5 SAPL2012 FUNCTION BAPI_PO_CREATE1
    Please see code in subroutine PROCESS_ADDR_TABLE:
                    CLEAR imt_item-kunnr.
                    imt_itemx-kunnr = bapi_yes.
                    CLEAR imt_item-emlif.            !!!!!!!!!!!!!!!!!!!!
                    imt_itemx-emlif = bapi_yes.
                    CLEAR imt_item-lblkz.
    If you have the fields cleared in MM process , it is not a SRM-EBP-POR issue , but a MM-PUR-PO-BAPI  The BADI BBP_CREATE_BE_PO_NEW will only be called in the classic scenario wherein the purchase order is directly created in the backend R/3 system. For extended classic scenario, kindly use the BADI BBP_ECS_PO_OUT_BADI instead.
    I hope this information will help you .
    Summer Wang
    Edited by: Summer Wang on Nov 24, 2009 2:50 AM

Maybe you are looking for