BP - Additional Customer Fields

Hi CRM'ers, I want to Add 3 Z-..fields to BUT000, and then add it to BP address information screen on Tcode 'BP'. I have tried adding the field via Tcode EEWB , but do get message DC1101 'BDT-DC is Not Prepared for This Application Object'...can anyone help....is there another way or what does this message tells me...thanks
AJ

Hi AJ,
Check the oss Note 955236. This should solve your problem.
<b>Reward points if it helps!!</b>
Best regards,
Vikash.

Similar Messages

Adding Additional Custom Fields to Alerts

in the Custom Fields tab of the alert properties, there are 10 custom fields. a few questions regarding "custom fields"
is there a way to add addtional custom fields?
can variables be placed in the custom fields so data that changes from alert to alert can be passed?
is there a way to add additional custom fields and give them a more formal name (e.g. MyHomeGrownField)
thanks.

Yes you can put values in these custom fields. but you cannot change the field names to something else.
Values can be put in these fields through OpsMgr PowerShell. Check the links -
https://social.technet.microsoft.com/Forums/systemcenter/en-US/dde47a28-ce70-4144-b7f3-70cb8a3d3cb9/using-custom-fields-in-scom-alerts?forum=operationsmanagergeneral
http://scug.be/dieter/2012/01/23/scom-2012-pass-data-to-custom-fields-with-monitors/
Thanks, S K Agrawal

Additional custom field on mm01/mm02 screen

hi all,
I need to create an additional custom field on mm01/mm02 screen.
value entered in this field will be updated in the database.
Kindly give pointer to the user exit/ screen where i can create the custom field.
thanks in advance

Hi Manish,
Do the following process step by step as specified in the following link.[http://www.****************/Tutorials/ExitsBADIs/MM/MM01.htm]
But in this link while you are at the 11th step
select your required view.
and do the rest as usual.
This is at the configuration level u can add your customer fields.
I dont think there are any exits available that can fulfill your requirement as the same requirement is fulfilled at the customization level.
Thanks.

Introduction of additional customer fields in productive system

Dear experts,
in the SAP help and OSS-notes (SAP Note 891144) it is strongly recommended NOT to introduce additonal customer fields for the new General Ledger Accounting in already productive systems. I would like to know if this because of technical reasons , e.g. field creation or assignment is technically not possible because transaction data is already in the system, or because of the problemsfor the reporting when the fields are not correctly filled .
Thanks a lot.

Hello,
In my opinion, the purpose of this OSS note 891144 is to inform about the risk when you Define Document Splitting Characteristics for General Ledger. In that customizing point, the 2 fields zero balance and mandatory field must be ticked in order to avoid any consistancies related mainly to document posting without profit center, Bus Area or Segment ...
If document splitting is activated, means document must be posted with profit center (or Bus Area or Segment if they are activated) information in order to have correct info and correct reports
But please contact SAP directly if you have problems regarding this
Best regards
Tarek
Edited by: Tarek AYACHI on Sep 2, 2011 5:47 PM

Additional custom field on the assignments tab KO01

Hi Geeks ,
I have a requirement to add a new custom field to the assignments tab of the tcode KO01. This new field is not available in the structure CI_AUFK . Is it achievable via enhancement COOPA003 ? If yes , then how ? . A <removed by moderator> response would really be appreciated.
Thanks,
Preetinder singh.
Edited by: Thomas Zloch on Nov 4, 2011 11:28 PM

Proceed as follows:
    You can use the CMOD transaction to create an enhancement project for the COOPA003 enhancement.
    You can use the SE11 transaction to create the CI_AUFK structure as described above. Transfer three fields into this structure and activate it:
Field name Data element
ZZMATNR MATNR (Material nummer)
ZZKUNNR KUNNR (Debitor)
ZZTEXT30 TEXT30 (30-character text)
It is recommended that you reactivate the COAS and AUFKV views separately.
    Copy the following objcts from the KOXM function group to the XAUF function group, using the SE80 transaction (Workbench Organizer). There, display the KOXM function group, position
the cursor on the source object, and copy it to the corresponding target object.
Caution
When you copy, the target objects are overwritten. If the target objects already exist, then insert the source code for the source object into the target object.
Object type Source Target
Screen SAPLKOXM 0100 to SAPLXAUF 0100
Include (Top include) LKOXMTOP to ZXAUFTOP
Include (PBO) LKOXMF04 to ZXAUFU04
Include (PAI) LKOXMF05 to ZXAUFU05
    The ZXAUFTOP still requires changes to the source code. Use the SE38 transaction (ABAP Editor) to process this include. Detailed instructions are contained in the source code as
comments.
    Activate the enhancement project. The fields should now be available in the master data maintenance, and should be saved.
    Function/Program:
        EXIT_SAPMKAUF_002: Function callup for customer fields: PBO data SAP -> Customer
        EXIT_SAPMKAUF_003: Function callup for customer fields: PAI data customer -> SAP
Include ZXAUFU04 (part of EXIT_SAPMKAUF_002)
*& Include           ZXAUFU04
write imported data in global structures
MOVE-CORRESPONDING I_AUFK TO GLOBAL_AUFK.
MOVE-CORRESPONDING I_KAUF TO GLOBAL_KAUF.
decide wich subscreen is to be displayed
IF ( GLOBAL_KAUF-PAR_LAYOU <> 'ABCD' ) AND
     ( GLOBAL_AUFK-AUART <> '1234' ).
    SUBSCREEN = '0100'.
ELSE.
    SUBSCREEN = SPACE.
ENDIF.
*& Include           ZXAUFU04
This include is part of the example programm for
customer exit COOPA003.
To activate the example, copy it to the include ZXAUFF05.
Remove the asteriks indicating a comment line in the first column.
Make sure ZXAUFF05 doesn't exist yet! Use cut-and-paste instead.
INCLUDE LKOXMF05                                                   *
give only customer fields back to SAP-Programm
*C_USER_CI_AUFK-ZZMATNR    = GLOBAL_AUFK-ZZMATNR.
*C_USER_CI_AUFK-ZZKUNNR    = GLOBAL_AUFK-ZZKUNNR.
*C_USER_CI_AUFK-ZZTEXT30   = GLOBAL_AUFK-ZZTEXT30.
Edited by: ZAHID HAMEED on Nov 5, 2011 12:37 PM

BAPI_SHIPMENT_CREATE - Additional Custom Fields

Hello BAPI Guru's,
I use the BAPI_SHIPMENT_CREATE to create Shipments. All normal requirements are working good. I need your expertise for the following situation:
- I have extended table VTTK with couple of fields to store information about (License plate, Driver information, Vessel Info, Seal No....)
- Using this BAPI when I create the shipment I would like to update the above fields/information also.
- By default this BAPI will not update these new custom fields as these new fields are not existing in the BAPI interface (structure BAPISHIPMENTHEADER).
Can you pls share your views/ideas on how to achieve something like this?
Thanks a lot !
Regards,
Hitesh

Hi,
Hope the following threads will help you regarding your problem.
Re: Creating Contract from Quotation
Thanks.
Nitesh

Additional Customer Fields in Trans. OVA8 Define Automatic Credit Control

Hi,
I must add a customer field in the transaction OVA8 for the credit control but I don't want to make a standard modification.
There are some alternative possibility ?
Best regards.

Many Thanks for your suggestion but with smod i don't find a screen exit for my transaction.. I am mistaking something?
Thanks

Search on the custom field in Product doesn't work

Hello everyone!
Lately I was configuring additional custom field for product header and succeed. Then I wanted to add this field as a search criteria for product search and I followed help on help.sap.com and note 1026956. Here are the steps I did:
1. I've extended structures CRMT_PRIL_QUERY_ADVSEARCH_PROD and CRMT_PRIL_QUERY_ADVSEARCH_IOBJ with my custom attribute.
2. I went to Master Data->Products-> Basic Settings ->Add Attributes to Search Structure and added my custom attribute there.
3. Then I found out that it's not enough and I should perform additional steps not included in note and help. I did these steps suggested by Shanthala Kudva in thread [Can't enable the extendable set type attributes in product search UI|Can't enable the extendable set type attributes in product search UI;.
After that I was able to configure UI and see the search criteria, but when I try to search using custom field I get error message: "Search criteria PRODUCT_ANKER.ZCAT_NUMBER in scenario CL_CRM_PRSEARCHSCENARIO_GETLST not included in tool/filter"
How to find out the reason of this behavior? Did I miss something in configuration?
P.S. Set type called ZPRODUCT, attribute ZCATNUMBER. In structures appended component called ZCAT_NUMBER with component type ZCATNUMBER. In table CRMC_PRSEA_ATTR the record has the attributename ZCAT_NUMBER, attribute_id ZCATNUMBER. Maybe I messed up with that?
Regards,
Alex.

Hi Alexander,
I know this is an old post, but currently i am facing the same issue of not being able to see my custom fields in the BSP Component Workbench.
I tried to follow all steps maintained in SAP Note # 10269656 & 1541480, but no luck.
Can you please tell me what do you mean by "Should not add the extended attributes directly to Search Structure, as SAP expects the attributes to be in APPEND structure"? Can you please let me know how the values are to be maintained in the Search structure table "CRMC_PRSEA_ATTR", which is also accessed using the IMG Meanu path "Master Data --> Products --> Basic Settings --> Add Attributes to Search Structure"
Appreciate your help.
Suresh Karri

Custom fields on Purchase order screen in SRM are missing.

Hi ALL,
SRM 5.0 R/3 4.6c
We have custom fields which appear on the create PO in SRM, the criteria for these fields to appear is if the item is of service type.So if its service item there will be additional/ custom fields for input purchase order screen in SRM,
But at this these fields dont show up for service item PO's . this is happening in Q and P environments while it is working fine in D and S. No changes were made to the system.
Also if I look in to bbp_pd info for the previous service PO, the data shows up in bbp_pd but the data or the custom fields are missing on the web.
We tried deactivating/activating the custom class in Q , but that did not help us!
Consider this as urgernt!
Can anyone please throw some light on this!
Thanks
Krishna

Have you implementated the BADI: BBP_CUF_BADI_2
if yes, then keep a break point there and see if you are missing any thing there...

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 displaying.in 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.
ENDIF.
endloop.
endmodule.
Thanks in advance,
Neelu.

Just read the OSS note mentioned earlier.
Symptom
You want to integrate customer-specific fields in material master maintenance.
Other terms
SAPLMGMM, RMDATIND, ALE, CI_MMH1, EXIT_SAPLMGMU_001
Solution
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.
Regards

Using custom fields of Infoset as Selection Criteria in Query Reporting

Hi Experts,
I have created one Infoset based on LDB PNPCE and added some custom fields to it. Coding has been done for the custom fields.
But these additional custom fields are not available as selection criteria while creating the query.
Can you please tell me how to use the custom fields as selection criteria?
Reply soon
Thanks in Advance.
Raveesh

Hello Guys,
I just noticed that it is possible to select custom fields as selection criteria in case of SAP Query,
but NOT is case of Infoset(Adhoc) query.
Can anyone tell me the whether it is possible to select the custom fields as Selection Criteria in case of Infoset Query?
Thanks in Advance,
Raveesh

Addition of field in list editing for notification - IW28

Hi Group,
As per the client requirement, we are adding a additional field on the notification header using the user exit QQMA0001.
Now i want to sort the notifications using the standard SAP list edit functionality i.e. IW28 but using my additional custom field.
What i need to do to reflect this adiitional field there in list edit?
Thanks

Raghunandan Iyer,
There is no user-exit required to append a structure, you just need an developer key.
Appending the structure will not affect the standard system.
Any appends will show up on the SPAU list. It is part of the upgrade process to review this SPAU list so it should be captured.
Try it in a test/sandbox system...
PeteA

Add a custom-field in the table MARC and manage it in MM01/MM02/MM03

Good day to all of you!
I have this task: To add a custom-field to the table MARC. This custom-field will be managed through the MM01/MM02/MM03 transaction as follows:
In the Basic Data 1 or Basic Data 2 the custom-field data will be added. Let's say the field is MATNR OBSOLETE.
I have searched and implemented the things in customizing: Made a copy of function group MGD1, added the field on the screen.
MY PROBLEM! How to manage it??? When the user enters MM01/MM02/MM03 and update this field, the field should be updated in MARC.
1. I am not sure that this custom-field should be on Basic Data1 or Basic Data2.They want it at plant level.
2. How to manage the data transfer from SAP Standard Program and my Custom Function Group.
PLs: Do not paste me link to sap technical site with that example, because there takes the custom fields and UPDATE a CUSTOM TABLE. I need to update MARC!
All the documentations i have read until now tell you how to add the field, ONLY the first part of the SOLUTION.
Any help, pls?
Good day and thank you!

Hi Alex,
In which way you are trying to update that custom filed. Have you written any logic in EXITS/BADIS?
http://pavelgk.pbworks.com/f/6729224-Implement-Screen-Exit-for-MM01-Adding-New-Fields-in-Screen.pdf
and
Just read the OSS note mentioned earlier.
Symptom
You want to integrate customer-specific fields in material master maintenance.
Other terms
SAPLMGMM, RMDATIND, ALE, CI_MMH1, EXIT_SAPLMGMU_001
Solution
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.
check this link. It may helps you to solve your issue.
Thanks
Sravan

What is "Customer Fields" Tab in the CHaRM

Hi All,
can any one explain what is the "Customer Filelds" tab in the Change Request for?
It is found under the Transaction Data button of the Change request ticket.
Thanks in advance.
Regards,
Pradeep L

Pradeep ,
This tab is used for creating additional customer fields
note
Note 816456 - Customer enhancements for CRM business object types
Regards
Prakhar

Is doing configuration for FB60 using customer field a core mod?

Hello,
For our project, a customer field 'ZZAPPROVER' was added in FB60 transaction code.
It is possible through configuration through the following path:-
SPRO --> Financial Accounting (New) --> Financial Accounting Global Settings (New) --> Ledgers --> Fields --> Customer Fields --> Edit Coding Block --> Customer-Defined Account Assignments --> Customer Include Structure
This basically added the customer field 'ZZAPPROVER' to the include structure CI_COBL.
The important point to note here is that it adds to BSEG table too.
Now the business is asking whether this is considered as a core modification to SAP.
Can anyone update where it is a core mod or not, and if there is any documentation to prove this?
Your comments are highly appreciated!
Regards,
Sanjiv Janardhanan

Hi,
The adding of additional Customer field is available from ECC 6.0 onwards. This is a standard functionlity to enable the customer to add their own fields for better reporting. But SAP cautions that it is better to take backup before doing this addtioin. No posting transactions shall be performed while you are including the customer field. SAP recommends using the u201Clightu201D mode. For this, you only need to make the following entries so that all necessary changes to the dictionary and to the tables are performed automatically in the background:
●      Collection (package)
●      Field name
●      Field description
●      Data type
Character field (CHAR)
Character field with digits only (NUMC)
Trust this helps much!
Cheers!

BP - Additional Customer Fields

Similar Messages

Maybe you are looking for