EEWB Custom fields creation problem

Hi All,
I have scenario in which I have to add 3 custom fields in Service Desk (Solution Manager) , I could able to do this if my project is saved in local($TMP)  but if I am doing it using a project which is saved in package it is giving me error message no TK885 (No Request as sent through the interface ).
Extension Type  : CUSTOMER_H
Please help.

For EEWB the system setup is important in order to create EEWB transports.
First of all via SM30 check the view V_OXT_SYSTAB, assign the proper logical system name and system role should be Development system.
Furthermore read/implement the following SAP Note (especially the included PDF file).
Note 1086848 - EEW enhancements cannot be transported

Similar Messages

  • Dump after custom field creation in SRM shoppinc cart

    I have created a custom field(using a custom data element and a custom domain) and it is displayed in the Item Basic Data screen.
    Then I create a basket assigning a value for this field.
    The dump occurs when I try to view the basket after creation, from the Status Select or from the link in Approval Screen
    Runtime Errors:  GETWA_NOT_ASSIGNED
    Short text: Field symbol has not yet been assigned.
         The current ABAP program "SAPLGCNV" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    Screen: SAPLBBP_PDH_CUF 0100

    <b>Please ensure that the Z structures (Append Structures) created in this case are Activated completely (and should not be in Partially Active or InActive State).</b>
    <u>Since these structures will be used in the BADI Tables (SC Item level / Header level), these must be activated once again, incase you add / modify/ change the structures in the meanwhile.</u>
    If you want to define fields on item level in shopping carts, use structure INCL_EEW_PD_ITEM_CSF_SC. If you want to see the fields defined on item level in the search results for the shopping carts (for example, in the status), use structure INCL_EEW_PD_SEARCH_ITM_CSF_SC.
    If you have defined document-specific fields on header and/or item level, you also have to define them in structures INCL_EEW_PD_HEADER_CSF (for the fields of the header) and INCL_EEW_PD_ITEM_CSF IF THEY HAVE NOT BEEN DEFINED THERE YET. Consequently, these structures contain the combination of header or item fields of all document-specific fields.
    For more details, please refer to OSS note - 672960 (User-Defined Fields 2) Please carefully read the documentation.
    <b>Few other related OSS notes to refer -></b>
    <u>1018714 Change documents: Time stamp of the application server
    1006898 Deleted vendor not displayed in Change hist of Shopping cart
    731037 Converting SUS 1.0 and SUS 2.0 documents to SUS 3.0
    820201 Document changes for attachments does not work
    691880 Changes in tolerances not displayed in purchase order</u>
    Let me know incase you still face any issues.
    - Atul

  • Groupwise Custom Field Creation throws exception

    When I am trying to create a new field definition (String type) using the object API (8.0.1)(gwoapi_800.h), I got the following exception
    System Message #1: "An error occurred in allocating memory.", System Message #2: "Error Message: "Exception occurred.", Source "FieldDefinitions.Object"",
    IGWFieldDefinitionPtr pDIGWFieldDefinitions;
    Is this a known API issue?

    I put a fix to 8.0.3 and the next major release
    or GroupWise. The problem was there is a custom
    field table that gets created. If the user had
    no custom fields, there was a problem creating
    the first custom field.
    You can get around the problem (until the fix
    is available) by first creating a custom field
    using the GW Client.
    >>> On Tuesday, June 15, 2010 at 1:28 PM, Preston
    Stephenson<[email protected]> wrote:
    > I created a bug to investigate the issue.
    > I'll get to it when time permits.
    > Thanks.
    > Preston
    >>>> On Tuesday, June 15, 2010 at 12:46 PM,
    > pranov2001<[email protected]‑> wrote:
    >> Preston
    >> Thanks a lot for your response. Here is the snapshot of the code that I
    >> am trying to achieve.
    >> _COM_SMARTPTR_TYPEDEF(DIGWAddressBooks, DIID_DIGWAddressBooks);
    >> _COM_SMARTPTR_TYPEDEF(IGWAddressBooks2, IID_IGWAddressBooks2);
    >> _COM_SMARTPTR_TYPEDEF(IGWAccount4, IID_IGWAccount4);
    >> _COM_SMARTPTR_TYPEDEF(IGWCAddressBook2, IID_IGWCAddressBook2);
    >> _COM_SMARTPTR_TYPEDEF(DIGWFieldDefinitions,IID_DIG WFieldDefinitions);
    >> _COM_SMARTPTR_TYPEDEF(IGWFieldDefinitions,
    >> IID_IGWFieldDefinitions);
    >> _COM_SMARTPTR_TYPEDEF(DIGWFieldDefinition,
    >> DIID_DIGWFieldDefinition);
    >> DIGWAddressBooksPtr pDIGWAddressBooks;
    >> IGWAddressBooks2Ptr pIGWAddressBooks;
    >> IGWAccount4Ptr pIGWAccount;
    >> LPCTSTR AddrBookName = _T("Test Contacts");
    >> CComVariant vName(AddrBookName);
    >> DIGWCAddressBookPtr pDIGWCAddressBook;
    >> HRESULT hr;
    >> DIGWFieldDefinitionsPtr pDIGWFieldDefinitions;
    >> IGWFieldDefinitionsPtr pIGWFieldDefinitions;
    >> DIGWFieldDefinitionPtr pDIGWFieldDefinition;
    >> IGWCAddressBook2Ptr pIGWCAddressBook;
    >> LPCTSTR FieldName = _T("AliasName");
    >> //Opening an Addressbook
    >> pIGWAccount‑>get_AddressBooks(&pDIGWAddressBooks );
    pDIGWAddressBooks‑>QueryInterface(IID_IGWAddress Books2,((LPVOID*)&pIGWAddr
    > essBo
    >> oks));
    >> hr = pIGWAddressBooks‑>Item(vName, &pDIGWCAddressBook);
    >> if (hr>=0)
    pDIGWCAddressBook‑>QueryInterface(IID_IGWCAddres sBook2,((LPVOID*)&pIGWCAdd
    > ressB
    >> ook));
    >> //Adding the field to the Addressbook
    >> pIGWCAddressBook‑>get_FieldDefinitions(&pDIGWFie ldDefinitions);
    pDIGWFieldDefinitions‑>QueryInterface(IID_IGWFie ldDefinitions,((LPVOID*)&p
    > IGWFi
    >> eldDefinitions));
    >> _bstr_t btFieldName(FieldName);
    >> pIGWFieldDefinitions‑>Add(btFieldName, 1, &pDIGWFieldDefinition);
    >> The interesting fact is, it works in one worstation and not in other,
    >> even if there is no OS or Groupwise client version difference between
    >> those workstations.
    >> Preston Stephenson;1987092 Wrote:
    >>> The error is reporting something missing.
    >>> Can you support more of your code that you
    >>> are trying to use?
    >>> A small test app would be even better.
    >>> Thanks.
    >>> Preston
    >>> >>> On Thursday, June 10, 2010 at 3:26 PM,
    >>> pranov2001<[email protected]‑> wrote:
    >>> > Hi,
    >>> >
    >>> > When I am trying to create a new field definition (String type)
    >>> using
    >>> > the object API (8.0.1)(gwoapi_800.h), I got the following exception
    >>> >
    >>> > System Message #1: "An error occurred in allocating memory.", System
    >>> > Message #2: "Error Message: "Exception occurred.", Source
    >>> > "FieldDefinitions.Object"",
    >>> >
    >>> > IGWFieldDefinitionPtr pDIGWFieldDefinitions;
    >>> > ....
    >>> > pIGWFieldDefinitions‑>Add()
    >>> >
    >>> > Is this a known API issue?
    >>> >
    >>> > Thanks.

  • Custom field creation using ajax in SP 2010

    If anybody create custom field using ajax toolkit, kindly share me the link or steps.

    yes. I have created custom field using Ajax toolkit which one available by default in VS 2010 under Ajax controls menu. do we need any other details on this, let me know.
    I just drag and drop the Ajax update panel in aspx page that used in custom field solution. then i just run the code and see the result on the new form in  the custom list. so i dont think, we need to do more work on this.

  • Idoc extension for eewb custom fields for BUS20001

    I have an almost exact question as , but I still need to ask what I'm supposed to do.
    We've done enhancements in EEW and I can see some append structures in CRMXIF_BUSTRANS (for example). The problem is that when I generate outbound idoc the sturcture E101CRMXIF_BUSTRANS is missing the corresponding append structures.
    Why isn't EEW adding this, or do I have to generate/re-generate something?
    I've tried to Cancel release/release the ALE interface in BDFG, but with no results.
    I think the replications (initial load and delta load) to r/3 has all EEW modifications, but when it comes to idocs, it woun't change.
    Is the only solution to create a new idoc in bdfg and create a z-structure?
    The FM ALE_CRMXIF_ORDER_SAVE_M used for populating the idoc, would work if the structure E101CRMXIF_BUSTRANS was extended with the same appendstructure (since the only thing it does is a move-corresponding...).
    So, the question is if I have to create a new z-idoc, or if it's possible to regenerate the structure used in the idoc segments?
    Regards, Mikael Löwgren

    When you have ignored the inconsistencies, this means the complex structure fields and the corresponding Idoc Segment fields are different in the support package.
    If this is the case, when the Idoc is regenerated in Tx BDFG, you will find the message type will be in
    error when you press F9 to do the syntax check.
    There you will see the segments which are in error as well as the 'Interface is not current and it must be regenerated' error message.
    Check those segments listed in syntax check against the respective complex structure. If there are differences like if some fields are added or the data element is changed, kindly correct the segment fields via Tx IDOC.
    If you need to add fields to the segment, you need to increase the field length of the segment in EDISDEF table, which can be done in Tx IDOC --> Repair segments tab --> Change entries in EDISDEF table.
    There you can change the field length and then change the entries in EDSAPPL table.
    Similarly if you take out all the errors in the segments listed for a particular message type and try to release the Idoc, it will be released without any errors.
    This happens, as far as my understanding goes, mainly because the complex structures might under go some changes from the development side but not the Idocs. Since both are different entities, mostly these types of things happen.
    Do let me know  if this has helped you.

  • UDF field Creation problem ?

    Hi  all,
      I  have install a addon .Addon installation successfully but and all tables are created but all columns are not created .this problem not for all server. where this addon installed there are installed 4/5 addon(is this problem) .please help how to resolved  it .
    thanks in advance
    Surajit kundu

    We need more information.
    Do you get an error message?
    Do you get an exception?
    Can we see some code?

  • Security using custom field in PCUI

    We would like to create a custom field on the header of the business partner to store information that would then be used in the security roles.
    For example, we want to create a branch field on the header of the business partner and then use this field to restrict access to specific accounts within the sytem using a CRM Security role.
    Does anyone know if you can use a custom field in the CRM system to restrict security within the PCUI application?
    If anyone has any information, I would greatly appreciate it as we are on a crunch to get this implemented!

    Hi Darcie,
    If you add custom field and maintain value in it, i'm not sure if you can restrict access by CRM Security role.
    If your users are going to be entirely based only on portal/pcui (i.e. they would not use SAP-GUI log-in) then you can consider the option of tweaking your Accounts advanced search and not letting users see certain accounts (based on the value in EEWB / custom field)
    Hope this helps.

  • Custom fields not visible in the Active Subject Area column

    I have created several custom fields in the Object Service Request. I need to create a report with those fields, but some of them are not visible / displayed.
    Is there any delay between the custom field creation and its availability in Oracle Answer? Because, only the "old" custom fields appears in the list.
    Thanks in advance for your advices.

    it generally takes one day to appear in analytics

  • Custom field in shopping cart

    Hi All,
    I need to add a custom filed in the shopping cart in SRM. I added the field by appending a structure in INCL_EEW_PD_ITEM_CST_SC and INCL_EEW_PD_ITEM_CSF_SC. I also executed the report BBP_DYNPROS_GENERATE by entering the prog name SAPLBBP_PDH_CUF. After doing these things when I go to shopping cart wizard and go to item details where my field should be visible, it gives a short dump "Field symbol has not been assigned yet (GETWA_NOT_ASSIGNED) ".
    Is there anything else I need to do to add a filed in the shopping cart.
    Please help.
    Thanks in advance.

    Hi Neerja,
    Go through the following links:
    Re: Dump after custom field creation in SRM shoppinc cart
    Re: Customer fields
    Adding fields in shopping cart
    And try to follow the steps given in the following blog:
    How to create custom fields in SRM
    Hope this helps

  • Add a custom field in output tab of po header SRM 7.0

    Hello All,
    Please let  me know How to add a custom field in output tab of po header SRM 7.0.

    Hello Neelima,
    Have you already check the note 458591, which help to custom fields creation? I think this note can be relevant for you.
    Best regards,
    Denise Zanuz

  • Customer fields

    Hi experts
    Someone could send me some documentation about how to create customer fields in SRM, specialy in shopping carts.

    if you have defined document-specific fields on header and/or item
    level, you also have to define them in structures INCL_EEW_PD_HEADER_CSF
    (for the fields of the header) and INCL_EEW_PD_ITEM_CSF IF THEY HAVE NOT
    BEEN DEFINED THERE YET. Consequently, these structures contain the
    combination of header or item fields of all document-specific fields.
    Please read note 672960 carefully
    Also see this  thread;
    Re: Dump after custom field creation in SRM shoppinc cart

  • How to fill values  to custom fields created by EEWB

    Hi All,
    I am working in CRM 5.0,We have extended the BP transaction with two new fields using EEWB transaction.
    Here goes my problem , i wanted to update data to the new fields using FM.
    I tried using BUPA_CENTRAL_CHANGE,where i found the structure of the  custom fields .But the FM is working for standard fields but not for Custom fields.
    Following are the FM generated  in EEWB.
    I have tried using the above FM.But didnt work.
    Can you please help me how to proceed  just to fill values using FM.
    Your suggestions  will be highly rewarded.

    Hi Shiva,
    Thanks for your response.
    I have specified the FM that are generated while creating the fields, where i dnt find any update or delete.
    Further can u explain "you can play with screen config in the AREA MENU code BUPT".
    My requirement is to upload data to those fields through pgm for one time.

  • Problem in database fields creation using default class of B1DE Wizard

    Hi Experts
    In an AddOn I am creating database fields in default class "Project_DB'. It does not give any message weather it creates fields or not. My code for database creation is given below
    Namespace FormARE
        Public Class FormARE_Db
            Inherits B1Db
            Public Sub New()
                B1Connections.theAppl.StatusBar.SetText("Please wait. AddOn is updating database", BoMessageTime.bmt_Long, BoStatusBarMessageType.smt_None)
                Columns = New B1DbColumn() {New B1DbColumn("OCRD", "BondNo", "Bond No.", BoFieldTypes.db_Alpha, BoFldSubTypes.st_None, 20, New B1WizardBase.B1DbValidValue(-1) {}, -1), New B1DbColumn("OCRD", "BFrDate", "Bond From Date", BoFieldTypes.db_Date, BoFldSubTypes.st_None, 10, New B1WizardBase.B1DbValidValue(-1) {}, -1), New B1DbColumn("OCRD", "BTDate", "Bond To Date", BoFieldTypes.db_Date, BoFldSubTypes.st_None, 10, New B1WizardBase.B1DbValidValue(-1) {}, -1), New B1DbColumn("OINV", "Cntner_no", "Container No.", BoFieldTypes.db_Alpha, BoFldSubTypes.st_None, 20, New B1WizardBase.B1DbValidValue(-1) {}, -1), New B1DbColumn("OINV", "Cntnr_Seal", "Container Seal No.", BoFieldTypes.db_Alpha, BoFldSubTypes.st_None, 20, New B1WizardBase.B1DbValidValue(-1) {}, -1), New B1DbColumn("OINV", "Cust_Seal", "Custom Seal No.", BoFieldTypes.db_Alpha, BoFldSubTypes.st_None, 20, New B1WizardBase.B1DbValidValue(-1) {}, -1), New B1DbColumn("OINV", "ctryOrgn", "Country of Origin", BoFieldTypes.db_Alpha, BoFldSubTypes.st_None, 20, New B1WizardBase.B1DbValidValue(-1) {}, -1)}
                B1Connections.theAppl.StatusBar.SetText("Successfully updated database", BoMessageTime.bmt_Short, BoStatusBarMessageType.smt_Success)
            End Sub
        End Class
    End Namespace
    It does not give first message. and second message come properly and immediately when I start the AddOn. I checked it makes all fields accuratly. But when I open the related form it gives error message "Data Source not found". I checked fields name are same as used in form and database .What can the reason? Should I use a simple function for creation of database fields which will run when a button is pressed? Is it fine to using default class for database fields creation?
    Best Regards

    I solved the problem.
    Procedure I followed :
    'GLOBAL_NAMES = FALSE' in init.ora file.

  • Runtime error in CRM_DATAEXCHG_BADI after adding customer fields using EEWB

    Hi gurus,
    I've added 3 custom fields in ORDERADM_I structure using EEWB. ( created in ECC also ).
    Now when i create a sales order, its not flowing to ECC as i am getting the below error.
    Error occured while executing below statement
    MOVE <ls_bape> TO ls_bapiparex_wrk+lc_offset.
    <ls_bape> is having all the custom fields i've created using EEWB.
    Error short text i am getting in st22: ' Data objects in Unicode programs cannot be converted.'
    Kindly help.
    Arun N K.

    Hi Robert,
    Thanks for the reply.
    I was not able to use move-corresponding as there was no matching fields in the destination structure.
    Anyway we found out the issue. One of the custom fields generated using EEWB, used INT4 data element. I deleted the field and created it again using character (NUMC) data element, and it worked fine.
    I still don't know the exact problem of using integer data element. Kindly share if anyone find the reason.
    Arun N K.

  • Problem in custom fields in mm02/mm03

    Hi folks,
    i want to add the custom fields in mm01.iam able to add and update database.but iam facing problem in when iam checking the particular material in mm02/mm03.the custom field data is not correctly.for every material the last custom field data is showing. in database it is updating correctly but in mm02/mm03 it is displaying incorrectly.
    By the following code i can able to display the data in mm02/mm03.but my problem is the last created custom field(model) data is showing for all the materials when iam checking in mm02/mm03.
    here my custom field is "MODEL"
    for eg matnr-10 model -xx.
    matnr-20 model-yy.
    if iam checking in mm02/mm03 for matnr-10 model-yy it is database it is updating correctly.
    can u please tell me how can i write a code to select the custom data(model data) for that particular material.
    Module get_data.
    if sy-tcode = 'MM02'.
    select single model into mara-model from mara
    where matnr = mara-matnr.
    elseif sy-tcode = 'MM03'.
    select single model into mara-model from mara
    where matnr = mara-matnr.
    loop at screen.
    if screen-name = 'MARA-MODEL'.
    screen-input = 0.
    modify screen.
    Thanks in advance,

    Just read the OSS note mentioned earlier.
    You want to integrate customer-specific fields in material master maintenance.
    Other terms
    To add customer-specific fields to an existing material master table (such as MARA or MARC) , you can proceed as follows as of Release 3.0C:
          1. Use an append structure to add the fields to the required table in the Dictionary (this is not a modification; for details, see the SAP document "ABAP/4 Dictionary"). In Release 3.x, the length of the field names must be the same as  the standard five character fields. This is necessary because of dynamic assignments. As of Release 4.0A, the lengths of the field names can be longer than five characters. If the changes of the fields should be recorded in the change document and taken into account during ALE distribution, set the 'Change document-relevant' indicator for the corresponding data elements. For table MARA in Release 3.x, you must also enhance the database view MARU because the database changes are carried out using this view. This small modification is no longer necessary as of Release 4.0A because the database view MARU is enhanced automatically when you enhance table MARA or the include EMARA (which is the data part of table MARA).
          2. Enhancing online maintenance in customized material master maintenance:
          Define a subscreen with your customer-specific fields in a customer-specific function group created as a copy of the standard function group MGD1.
          In Customizing, assign this subscreen to a maintenance screen using the "Copy customized material master" function. For details, see the Implementation Guide (IMG). As of Release 4.0A, program COPYMGD1 is available. You can use this program to create customer-specific function groups as required. This program is also incorporated in the Customizing function 'Configure customized material master'. Ensure that each field of the subscreen has a field statement in the flow logic, otherwise the data is not transported correctly. You can use subscreen SAPLMGD1 2002 as an example.
          If you want these fields to be subject to standard field selection, you must add new entries for them to the central field table for material master maintenance (T130F):
          Application examples for standard field selection:
          The field is mandatory and is to be flagged with a "?".
          The field belongs exclusively to the purchasing user department. Purchasing data and MRP data are both contained on one screen. However, the MRP controller is not to see the purchasing data.
          The following data is required for each field:
                a) Field name        (T130F-FNAME)
                b) Field selection group (T130F-FGRUP)
                Here, you should use a standard field group if the customer field is subject to the same field selection as the standard fields of the standard field group. If it is not, use a customer-specific field group.
                You must then check and, if necessary, modify the attribute of the field group using the function "Maintain field selection for data screens" in Customizing under "Logistics Basic Data -> Material Master".
                Field groups 111 through 120 that are not used in the standard system are reserved as customer-specific field groups. As of Release 3.0F, additional customer field groups are available. (For details, see the IMG).
                c) Maintenance status (T130F-PSTAT)
                List of the user departments that may maintain the field. You can display possible values by using the input help for the maintenance status field in the Customizing activity "Configure Material Master" when maintaining logical screens.
                d) Reference        (T130F-KZREF)
                This indicator must be set if the field from the reference material should be proposed during creation with reference.
    Note: You cannot yet use Customizing to enhance table T130F; you can use only transaction SE16 (Data Browser) or transaction SM31. Future releases will include a separate Customizing function for maintaining customer-specific fields. See Note 306966. By implementing this note you can add entries to table T130F within Customizing. This type of maintenance is possible as of Release 4.5B.
    You may change the entries for standard fields only with regard to the reference data and field selection group. Changing other data for standard fields constitutes a modification. Therefore, you cannot use the Customizing function "Assign Fields to Field Groups" to change this data.
    In addition, you must not add new standard fields to table T130F.
          3. If you want to maintain customer-specific fields using data transfer by direct input or via ALE distribution, proceed as follows:
          Add the fields to central field table T130F (see above).
          Add the customer-specific fields to the data structures for the data transfer (for example, BMMH1 for the main data).
          Also, add the customer-specific fields to the tables in which the incorrect data is stored during direct input. These tables have the same name as the corresponding master data table and also have the suffix _TMP.
          For example: If you add customer-specific fields to table MARA, you should add the same fields to table MARA_TMP.
          If you use ALE, you must also add fields to the IDoc. To process enhanced IDocs, you can use enhancement MGV00001 with customer exit EXIT_SAPLMV01_002 for creating the IDocs and customer exit EXIT_SAPLMV02_002 for posting the IDocs.
          Prior to Release 3.0E, enhancing structure BMMH1 constitutes a modification. In this case, you must add the new fields tot the end of the structure before the last field (SENDE = record end indicator).
          As of Release 3.0F, structure BMMH1 contains the customer include CI_MMH1, which is part of the enhancement MGA0001. Here, you must proceed as follows:
                a) Add the customer-specific fields to include CI_MMH1.
                The names of the fields in CI_MMH1 must be identical to those of the corresponding fields in material master tables MARA, MARC and so on.
                Important: The fields must be CHAR type fields. Therefore, create CHAR type data elements whose lengths are identical to the output length of your fields in  table MARA and so on. Use these data elements in include CI_MMH1, but use the field names from table MARA and so on.
                b) Activate include CI_MMH1.
                c) If you have not used customer structure ZMMH1 before, create it as a copy of structure BMMH1 and delete the standard fields that you do not require. You are not permitted to delete field STYPE and include CI_MMH1 when doing this. If you have already used structure ZMMH1, add include CI_MMH1 to it.
                d) Activate structure ZMMH1. This also adds the customer-specific fields to ZMMH1.
    Run program RMDATING. This program generates routines which are supplied to your customer-specific fields from the input file. As of Release 4.5A, you also need to activate the routines/function modules generated by program RMDATING (especially, the MAT_MOVE_BMMH1_XXXX modules). Details about this subject (especially the procedure when using customer structure ZMMH1) are described in the IMG for transferring the material data under item 'Maintain Transfer Structure'. Also, check the declaration of structure WA in program RMMMBIMC to see whether it is declared with sufficient length. If necessary, enhance the declaration (for the time being, this still constitutes a minor modification).
    In addition, lengthen domain DI_DATA with CHAR 5000. As of Release 3.1H, this has already been done.
    Important: When using customer-specific fields, you can use only structure ZMMH1 to transfer the data. Otherwise, after the next SAP upgrade which contains new standard fields in structure BMMH1, the input files no longer match. If you want these new standard fields to be transferred, add them after your customer-specific fields (the order of the fields in structure ZMMH1 does not need to be the same as the order of the fields in BMMH1).
    If you want foreign key dependencies or fixed domain values to be checked, or another check for a customer field, this is possible up to and including Release 3.0D only by modifying the corresponding check function modules. As of Release 3.0E, you can use function exit EXIT_SAPLMGMU_001 (SAP enhancement MGA00001) for these purposes.
    If you want to use engineering change management to schedule future changes for your customer-specific fields or you want to use the 'Display at Key Date' function, execute program GENERATE in addition. This program generates the necessary assignments for interpreting the change documents. With regard to engineering change management, you must read Notes 60281, 60973, and 48962.
    To date, it is not possible to integrate customer-specific tables in material master maintenance without making a modification. However, you can create customer-specific development objects containing the essential additional logic. You can then integrate these development objects in your system as part of only a minor modification.

Maybe you are looking for