Custom Fields In Reservation

Hi All,
I Want to add Custom field in MB21/MB22 at item level .
I have searched and tried the BADI MB_RES_BAPI_CREATE1 but couldn't able to find in documentation also how to add the field.
Can any one suggest me how to include the field in Item details screen.
Regards,
Pavan

Hi,
I need to link the Equipment No. Field to the reservation items ,can any one suggest how to add the custom field at item level.
Regards,
Pavan

Similar Messages

Reservations creation with customer fields in ECC from SRM does not work?

Hi,
I have to create reservations into backend system (ECC) from shopping cart creation in SRM 7.0.
Reservation items contiain two customer fields.
RESB is extended by adding an append structure that contains an include with the data structure of the two customer-specific fields.
When reservation is created by BAPI_RESERVATION_CREATE1 function in ECC customer fields are filled.
In SRM I use FILL_RS_INTERFACE1 method of BADI BBP_CREATE_BE_RS_NEW.
When a shopping cart is created in SRM and then approved a reservation is created in ECC but customer fields are empty.
Why?
Thank you for your collaboration.
Best regards.
Al

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90bd6f78-bcce-2a10-17ac-a74187b924ea?quicklink=index&overridelayout=true
Note 885458 - SRM partner maintenance: 'Add to invoicing party' is missing
Note 1034662 - BBP_VENDOR_SYNC: Invoicing Party not getting changed
in classic there may not be any issue since while creating a PO partner function automatically determined correctly int he ECC purchase order .
In SRM , we might pulled only VN vendors.
this could be one of the grey area in SRM Extended classic mode.
check with SAP and update SAP comments / suggection here.
Are PI (invoice party) and VN ( real supplier) vendor number ranges same?
Are many vendor VN and PI different?
Note 1022311 - SRM Integration: Partner at purchase order item level
In Supplier Relationship Management (SRM), you can maintain partners at item level. During the replication into the ECC back end, this partner information is no longer available because there are no partners for the document item in the ECC back end.
Other terms
Business Add-Ins:
ME_BAPI_PO_CUST, ME_PROCESS_PO_CUST, ME_GUI_PO_CUST, MB_MIGO_BADI, MRM_PARTNER_CHECK
let us wait for others reply
Muthu

Unable to update MARA table custom field in Material master

Hi all,
I have added one custom field in MM01,Basic View 2.
For that i have apended that field in MARA table and created one subscreen for that.
This field is visible in MM02/MM01/MM03 in basic data view 2 .
The issue is that we are not able to save values in MARA table which we entered in this field.
I cheked earliar in SDN but couldn't get the proper solution.
i cheked the below available forum discussion link but couldn't get th proper solution.
In material master How to add a new field on Basic data 1 view
Regards,
Amit

Hi,
please trye this :
Please make sure u implemented: methods PUT_DATA_TO_SCREEN and GET_DATA_FROM_SCREEN as they are required for data transport. These methods are called from within the program of the application at PBO or PAI .
See below example code:
PBO:
MODULE initialize OUTPUT.
CLEAR: sflight, ok_code.
IF exit IS INITIAL.
CALL METHOD cl_exithandler=>get_instance
CHANGING
instance = exit.
ENDIF.
CALL METHOD cl_exithandler=>set_instance_for_subscreen
EXPORTING
instance = exit.
ENDMODULE.
The factory method is used to create an instance of the adapter class. You then declare the instance using the public static method SET_INSTANCE_FOR_SUBSCREEN to allow the data for display on the screen to be used in the function group of the user or in the module pool.
MODULE data_for_subscreen OUTPUT.
program = sy-repid.
dynpro = sy-dynnr.
CALL METHOD cl_exithandler=>get_prog_and_dynp_for_subscr
EXPORTING
exit_name = 'BADI_SCREEN'
calling_program = program
calling_dynpro = dynpro
subscreen_area = 'SUB'
IMPORTING
called_program = program
called_dynpro = dynpro.
CALL METHOD exit->put_data_to_screen
EXPORTING
flight = sflight
EXCEPTIONS
reserved = 01.
ENDMODULE.
PAI:
MODULE user_command_0200 INPUT.
CASE save_ok.
WHEN 'BACK'.
SET SCREEN 100.
WHEN 'SAVE'.
PERFORM save_flights.
WHEN '+EXT'.
CALL METHOD exit->get_data_from_screen
IMPORTING
flight = sflight
EXCEPTIONS
reserved = 01.
ENDCASE.
ENDMODULE.
The method GET_PROG_AND_DYNP_FOR_SUBSCR and the input/output parameters specified above are used to determine the name of the customer program and the name of the subscreen. The method PUT_DATA_TO_SCREEN which is called at PBO as well as the method GET_DATA_FROM_SCREEN which is called at PAI are used to transport the data to be displayed.
These methods are implemented by the user:
When you define a screen enhancement, you are strongly recommended to provide sample code for the methods PUT_DATA_TO_SCREEN and GET_DATA_FROM_SCREEN. This code is automatically copied when you create an implementation and can be added to if required. The user of the BAdI definition should not be responsible for the data transport.
regards,
..Pradeep

How to update a custom field of MARC table using BAPI_MATERIAL_SAVEREPLICA

Hi,
I want to update a custom field (Appended field) of MARC table using BAPI_MATERIAL_SAVEREPLICA. Please help me in this issue. I cannot use BAPI_MATERIAL_SAVEDATA as this updated the MARC table record by record. I have to update bulk records at a time.
Thanks
Rahul.

Hi,
Use the Documentation given for struture in BAPI docuemntation...
For loading data into custom fields of MARC use the structure - BAPI_TE_MARC.
First, structures BAPI_TE_<NAME> (<NAME> = MARA, MARC, MARD, MBEW, MLGN, MLGT, MVKE, MARM, MAKT) and the appropriate check structures BAPI_TE_<NAME> (<NAME> = MARAX, for example) have to be extended by the customer to include the required fields. The structures that are delivered as standard only contain the relevant key fields. When new fields are added to this structure, you should ensure that a field has the same name as the field in the database table. Furthermore, the fields in the structures BAPI_TE_<NAME> can only be CHARACTER fields. Data element BAPIUPDATE is to be used for the fields in the check structure (exception to this: key fields.)
Parameters EXTENSIONIN and EXTENSIONINX are used for transferring data to the method. Field STRUCTURE contains the name of the structure (for example, BAPI_TE_MARA or BAPI_TE_MARAX). This names is used to identify the work area (for example, WA_BAPI_TE_MARA or WA_BAPI_TE_MARAX) to which the data is transferred. The remaining fields in parameters EXTENSIONIN or EXTENSIONINX contain data for the key fields (for example, the material number) and the data for customer-specific fields. The number of characters reserved in both parameters for the contents of the customer-specific fields must match the number of characters for the relevant field in the work area. If the number of required characters is less, the remaining characters are left blank. Only when all characters have been filled can the contact for an additional field be transferred. Bear in mind that only data for which an appropriate indicator has been set in the work area can be updated to the database.
Regards,
Bhargava

How to make added custom field Delta mechanism work for LO Cookpit?

We appended a new custome field into extraction structure of the LO Cookpit datasource 2LIS_02_ITM through RSA6. And then run CMOD to write the exit code to populate the value and it works fine. But after we read Roberto's Weblog:
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it , find the enhancement we did can't make the Delta mechanism works if only this new field gets changed in a record, and the change cannot be reflected on BW.
In order to make the Delta mechansim works, one option is to append the custom field into one of the LIS Communication Structure MCEKKO of 2LIS_02_ITM extraction structure and then write the enhancement code to this LIS Communication Structure. In this way, the custom field can be treated like standard field that whenever it gets changed, the Delta mechanism or the user exit will be triggered. The enhancement for this LIS Communication Struture is LEINS001.
Now we've got two problems when doing the above enhancements of the LIS Communication structure:
1. Maintain extraction structure problem in LBWE:
We added a custom field, e.g., called ZZZ in LIS Communication structure MCEKKO (Purchasing Document Header) by creating a new custom append structure and add the field ZZZ into it, then activate the new append structure, but get warning msg like "Field name DUMMY is reserved (Do not use structure as include in DB table)".
We do find a field called DUMMY in the structure MCEKKO. How to get rid of the warning msg and successfully activate the new custom append structure with the new field ZZZ?
You could say that we can ignore the warning msg, but why the new custom field appended can not be seen from the right side pool of the Maintain Extract Structure in LBWE? We need to make the new custom field shows up in the right side pool and then drag it over to the left side frame and to activate the extraction structure to change it. But now it doesn't show up in the right frame pool!
2. Refer to Sanyam's weblog
/people/sanyam.kapur/blog/2005/04/30/custom-fields-and-bw-extractors-making-a-mixed-marriage-work-part-ii, there is a sample code inside this article which tells us how the sample code looks like to write this LIS Communicaton structure enhancement to make the Delta mechanism works, below is the code we modified to suit our needs, but don't know if it would work?
DATA: i_t_ekko LIKE ekko   OCCURS 1 WITH HEADER LINE.
DATA: ebeln LIKE ekpo-ebeln,
      it_ekko TYPE TABLE OF ekko WITH HEADER LINE,
      old_val(50) TYPE c. "For storing the value from the Field Symbol
FIELD-SYMBOLS <fs> TYPE ANY TABLE.
CASE zeitp.
WHEN 'MA'.                            "When creating a purchase order
    MOVE '(SAPLEINS)T_EKKO[]' TO old_val.
    ASSIGN (old_val) TO <fs>.
    i_t_ekko[] = <fs>.
    LOOP AT xmcekko.
      ebeln = xmcekko-ebeln.
      IF xmcekko-supkz = '1'.            "Old Value ?
        SELECT SINGLE * FROM ekko INTO it_ekko WHERE ebeln = ebeln.
        xmcekko-ZZZ = it_ekko-ZZZ.
      ELSE.                              "New Value ?
        READ TABLE i_t_ekko WITH KEY ebeln = ebeln.
        xmcekko-ZZZ = i_t_ekko-ZZZ.
      ENDIF.
      MODIFY xmcekko.
    ENDLOOP.
EndCase.
Share your ideas and we will give you reward points!

Hello Kevin
We have exactly the same problem. Did you solve it? If you did, could you please tell us how you did it? We neither see our field in LBWE. Our field is a Z field from a Z table.
I hope you could help us. We just have this issue to finish our project.
Thanks a lot in advanced

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

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

Regarding Adding Custom Fields to VTTK and VT01n transaction.

Hi,
We need to add few custom fields to Shipment header table VTTK.
Also, these fields should be reflected in 'Additional Data' tab of transaction VT01n/VT02n for editing and should be available for display in VT03n.
If anyone has done this, please provide the approach.
Thanks,
Arshad

Hi Arshad,
The fields suppl.1 to suppl.4 and Addit.text 1 to Addit.text 4 are the reserve fields available in additional data tab of shipment.
If those fields are not being used already, u can utilise those fields for your purpose. Please check the documentation for the fields ADD01 to ADD04 and TEXT1 to TEXT4 in VTTK table.
The description of the fields can be modified from CMOD transaction.
Regards,
Poornima

Custom field in action

Hi,
My customer wants to capture every action inPa40... against an office order. Can I create custom field or is there any standard reserved field that i may use..pls help..the best way.

hi,
You can try to add fields in infotype 0001. IF you will check the table PA0001 (table of IT0001 structure), structure CI_P0001 is present. Here you can add the field as per your requirement. As 1 of our expert said you have to use TC PM01 to enhance it. Also you need to re-generate/ modify the related objects as well. Please take help of a ABAP-HR expert.
Praveen

Bapi bbp_create_be_rs_new mapping a customer field to standard field

hey guys , I am trying to create a reservation in ECC and i am trying to map a custom field to a standard field in ecc. In the structure of the reservation in the bapi there field does not exist but it exists in ecc. How do i map one of the values from the item table to a field to ECC when the field does not even exists in the bapi?
The field that i want to map is PRIO_URG in ecc and it does not exists in the bapi bbp_create_be_rs_new. I saw that there is an IT_RS_EXtensionin strucutre but I dont know how to pass a custom field to a standard?
I also want to pas a text id field to ECC too? How should i do that? thank you.

help! I don't understand how to pass my value that i got from a table in SRM to the bapi structure bapiparex?

Applescript to modify contacts custom field?

Hi-
I want to be able to search my address book the way I used to on my palm... by first initial followed by last name. For instance, if I wanted to search for John Smith, I'd enter "jsm". It's a highly efficient way to search, and I miss it dearly.
So, I would like to write an applscript that I could run on a nightly basis that would go through my entire contact list and look at the "Maiden Name" field. If the field is empty, the script would fill it with the first letter of the first name, followed by the entire last name (if a last name exists). Obviously, it would skip businesses where no names existed.
Bonus points would be doing this in a custom field, but I can't figure out how to get Applescript to read custom field labels at all!
Thoughts?
Thanks!

HI,
This may help you to write your script.
tell application "Contacts"
activate
          set the_people to every person
          repeat with tp in the_people
                    try -- lazy way of skipping companies
                              set fn to first name of tp
                              set l_n to last name of tp -- ln is apparently a reserved variable name
                              if l_n is not missing value then -- it's probably a person and not a business
                                        if maiden name of tp is in {"", missing value} then -- this person doesn't already have a maiden name
                                                  set mn to text 1 of fn & l_n
                                                  set maiden name of tp to mn
                                        end if
                              end if
                    end try
          end repeat
save
end tell
If you decide you don't like it, this will remove all maiden names - including real ones.
tell application "Contacts"
set the_people to every person
repeat with tp in the_people
          try
                    set maiden name of tp to ""
          end try
end repeat
save
end tell
I have a vague memory of trying and failing to get anywhere with scripting custom fields. I'll give it a go though.

Error while adding a custom field with Input help via AET

Hi All,
I need to add two custom field under Service orders at Item level in component BT140I_SRVP.
One field is required to have the input search help f4 and autopopulates the second field
I am able to add one field(not requiring help) successfully through AET .
I have created one Zsearch_help in se11 and its successfully running and Autopopulating seocnd field while I am testing it
While adding second field through AET,I need to enter following details as -
field label,search relevant ,serach help etc.
When I type the name of my 'Zsearch_help' against field search help it gives me following error
'Search help is not compatible'.
Secondly,not getting getter and setter methods for the attrributes in BTAdminI.
Last,please tell me if i create zhelp and activate it,would it automatically appear in the list on AETwhile assiging it to input field?
Please help me out.Kindly be detailed as I am new to SAP CRM.
Thanks,
Shivani

The question is answered in CRM 7.0 forum:
Getting error while adding a custom field (with input help) through AET

Error while adding custom fields in ERP quotation

I am trying to add custom fields to ERP quotation. So picked up ERP_H and added view BTCUSTOMER_H/CustomerH to its views. I have added the relevant custom fields to BTCUSTOMER_H/CustomerH. Now when I try displaying this, I get the following error..
Context generation failed in view BTCUSTOMER_H/CustomerH of UI Component ERP_H
An exception has occurred Exception Class CX_BSP_WD_INCORRECT_IMPLEMENT - There is no node text 'BTAdminH' in controller ''.
Method: CL_BSP_WD_CONTROLLER=>DO_CONTEXT_NODE_BINDING
Source Text Row: 39
Initialization of view BTCUSTOMER_H/CustomerH of UI Component ERP_H failed
An exception has occurred Exception Class CX_BSP_WD_INCORRECT_IMPLEMENT - There is no node text 'BTAdminH' in controller ''.
Method: CL_BSP_WD_CONTROLLER=>DO_CONTEXT_NODE_BINDING
Source Text Row: 39
Cannot display view ERP_H/HeaderOverviewpage of UI Component ERP_H
An exception has occurred Exception Class CX_BSP_WD_INCORRECT_IMPLEMENT - There is no node text 'BTAdminH' in controller ''.
Method: CL_BSP_WD_CONTROLLER=>DO_CONTEXT_NODE_BINDING
Source Text Row: 39
Window ERP_H/MainWindow of UI Component ERP_H cannot be displayed
An exception has occurred Exception Class CX_BSP_WD_RUNTIME_ERROR - View BTCUSTOMER_H/CustomerH in component ERP_H could not be bound
Method: CL_BSP_WD_VIEW_CONTROLLER=>BIND_VIEW
Source Text Row: 165
I have no prior experiance in UI development. Could someone explain me this error and how to fix this?
Regards,
Amar.

closing this unresolved

How to populate a custom field of a Std. SAP Tx with BAPI usage 2 Load data

Hi Experts,
For instance, I created a custom field (say, custom_field_1) on a screen of standard SAP tx(say, ME21N) by using screen exit. And in order to populate the data into it (custom_field_1), will use the Function user exits of this Tx(ME23N).
1) In next step, Where Where I have to add this field, apart from appending the same custom field in EKKO/EKPO table or any other related table; Extending the corresponding IDOC or creating a new Custom ÍDOC type? like What about BAPI?
2) If I got a text file with the data (including the data for this custom_field_1 too) and I have been asked to load it into SAP, then, I decided to use BAPI (say, BAPI_PO_CREATE or CREATE1) to create the data, So, How to handle this custom field, I mean, In which BAPI structure I have to pass this custom_field_1 data? ( Iguess, for some BAPIs EXTENSIONIN structures are provided, sorry if am wrong!)
Thank you.
Edited by: SAP ABAPer on Feb 21, 2009 7:40 PM

for example if you added field in the VBAP table then you can pass the custome field values like below
     move 'BAPE_VBAP' to lwa_extension-structure.
      lwa_bape_vbap-vbeln = lwa_final-vbeln.
      lwa_bape_vbap-posnr = lv_posnr.
      move lwa_final-yyslotid to lwa_bape_vbap-new custome field.
      move lwa_bape_vbap to lwa_extension-valuepart1.
      append lwa_extension to lt_extension.
      clear lwa_extension.
      move 'BAPE_VBAPX' to lwa_extension-structure.
      lwa_bape_vbapx-vbeln = lwa_final-vbeln.
      lwa_bape_vbapx-posnr = lv_posnr.
      move 'X' to lwa_bape_vbapx--new custome field.
      move lwa_bape_vbapx to lwa_extension-valuepart1.
      append lwa_extension to lt_extension.
      clear lwa_extension.
call function 'BAPI_SALESORDER_CHANGE'
        exporting
          salesdocument    = strcture
          order_header_inx = strcture
        tables
          order_item_in    =strcture
          order_item_inx   = strcture
          schedule_lines   = strcture
          schedule_linesx = strcture
          extensionin      = lt_extension.

ABAP query using logical database KDF is not populating custom fields

Hi Experts ,
I created two following queries
1.       VENDORCATKDF – uses KDF logical database
2.       VENDORCATLFA1 – uses table = LFA1
I’m pulling the same information in both queries:
·         Vendor Number
·         Country
·         Vendor Name
·         Vendor Category (custom fields added to LFA1)
The results for the query that uses the logical database KDF is incorrect. It doesn’t pull in the flag on the custom field LFA1-ZMRO.   Even though the logical database KDF is made up of the table LFA1 and has these fields.
Is there something that can be done – so that all of these “custom” category fields under LFA1 (such as LFA1-ZZMRO) – get pulled into queries – when we use the logical database KDF ?

Hi,
I have got the error removed by ensuring that fields from one table are a part of one line ( taking help of ruler) only. But the underlying problem remains, the output is not ALV but List output.
I do not think having additional fields in the query is reason for this.
Is it bcoz iI am adjusting the output length of columns to ensure no hierarchical error ?
Can we not have a query using LDB which is shown as SAP List?
Regards,
Garima.

Custom Fields In Reservation

Similar Messages

Maybe you are looking for