Customer field in EKKO - strategy

Hello people,
we are creating a new filed in EKKO, to display in ME21n, but when the user changes it,  I dont want the Purchase order falls in strategy to liberation.
Is it possible?
Thanks!

OK OK

Similar Messages

  • Moving data from custom fields to ekko table

    Hi Experts,
    I added new custom tab into me21n,me22n,me23n header thro me_gui_po_cust and me_process_po_cust.
    If i enter values in my custom fields, transport_from_model this method is not triggering.i have written below code in this method.
    METHOD if_ex_me_gui_po_cust~transport_from_model.
      DATA:     l_header  TYPE REF TO if_purchase_order_mm,
                ls_mepoheader  TYPE mepoheader,
                ls_customer TYPE ci_ekkodb.
      CASE im_name.
        WHEN subscreen.
          mmpur_dynamic_cast l_header im_model.
          CHECK NOT l_header IS INITIAL.
          ls_mepoheader = l_header->get_data( ).
          CALL FUNCTION 'ZMM_GET_DATA'
            EXPORTING
              im_ebeln       = ls_mepoheader-ebeln
    *            im_ebelp       = ls_mepoheader-ebelp
           IMPORTING
             ex_data        = ls_customer .
          MOVE-CORRESPONDING ls_mepoheader TO dynp_data_pbo.
          MOVE ls_customer-ztender TO dynp_data_pbo-ztender.
          MOVE ls_customer-zemdapplicable TO dynp_data_pbo-zemdapplicable.
          MOVE ls_customer-zpbgapplicable TO dynp_data_pbo-zpbgapplicable.
          MOVE ls_customer-zemdamount TO dynp_data_pbo-zemdamount.
          MOVE ls_customer-zemdvalidity TO dynp_data_pbo-zemdvalidity.
        WHEN OTHERS.
      ENDCASE.
    ENDMETHOD.
    i cant move my values entered in custom fields to ekko table.
    please help if u know..
    regards,
    Kavitha
    Edited by: Matt on Mar 23, 2011 10:55 AM added  tags

    Hi,
    check this out.. !!
    Import data from Excel to Oracle Database and
    Added link From Ask Tom.. your requirement you would be satisfied.. I supppose.. !!
    http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:908428873069
    - Pavan Kumar N

  • Update EKKO table for the custom field through BAPI

    Hi Experts,
    I need to create an Custom field in EKKO table through Include Structure.
    Now I have to update that custom field in my program.
    I have gone through the following but could not solve my question.
    Update EKKO table
    User Exit for ME21 PO Creation at the time of saving--Urgent
    I don't need to update when I hit the save button or any thing
    I have the PO's which needs to be updated with that field...
    Any suggestions would be greatly helpful.
    Thanks,
    Chaithanya...
    <removed_by_moderator>
    Edited by: Julius Bussche on Jul 7, 2008 10:47 PM

    Hi Patrick,
    Sorry Patrick you are right.. The structure is at header level.
    I have made the changes still I could not achieve it.
    I have made the following
    In EKKO table I have append the structure with a custom field ZZBUY.
    Now I have also appended BAPI_TE_MEPOHEADER and BAPI_TE_MEPOHEADERX with the custom field
    ZZBUY.
    Here is my program
    Data: wa_bapi_poheader  type BAPIMEPOHEADER,
             wa_bapi_poheaderx type BAPIMEPOHEADERX.
    Data: it1_bapi_poheader  like BAPI_TE_MEPOHEADER,
             it1_bapi_poheaderx like BAPI_TE_MEPOHEADERX.
    CALL FUNCTION 'BAPI_PO_GETDETAIL1'
      EXPORTING
        PURCHASEORDER            = wa_DATA-ebeln
    *   ACCOUNT_ASSIGNMENT       = ' '
    *   ITEM_TEXT                = ' '
    *   HEADER_TEXT              = ' '
    *   DELIVERY_ADDRESS         = ' '
    *   VERSION                  = ' '
    *   SERVICES                 = ' '
      IMPORTING
        POHEADER                 = wa_bapi_poheader
    *    POEXPIMPHEADER           =
      TABLES
        RETURN                   = it_bapireturn
    it1_bapi_poheader-ZZBUY = 'X'.
    it1_bapi_poheaderx-ZZBUY = 'X'.
    it_extensionin-structure = 'BAPI_TE_MEPOHEADER'.
    it_extensionin-valuepart1 = it1_bapi_poheader.
    append it_extensionin.
    Clear  it_extensionin.
    it_extensionin-structure = 'BAPI_TE_MEPOHEADERX'.
    it_extensionin-valuepart1 = it1_bapi_poheaderx.
    append it_extensionin.
    Clear  it_extensionin.
       CALL FUNCTION 'BAPI_PO_CHANGE'
         EXPORTING
           PURCHASEORDER                = wa_data-ebeln
           POHEADER                     = wa_bapi_poheader
           POHEADERX                    = wa_bapi_poheaderx
    *      POADDRVENDOR                 =
    *      TESTRUN                      =
    *      MEMORY_UNCOMPLETE            =
    *      MEMORY_COMPLETE              =
    *      POEXPIMPHEADER               =
    *      POEXPIMPHEADERX              =
    *      VERSIONS                     =
    *      NO_MESSAGING                 =
    *      NO_MESSAGE_REQ               =
    *      NO_AUTHORITY                 =
    *      NO_PRICE_FROM_PO             =
    *    IMPORTING
    *      EXPHEADER                    =
    *      EXPPOEXPIMPHEADER            =
         TABLES
           RETURN                       = it_bapireturn
    *      POITEM                       =
    *      POITEMX                      =
    *      POADDRDELIVERY               =
    *      POSCHEDULE                   =
    *      POSCHEDULEX                  =
    *      POACCOUNT                    =
    *      POACCOUNTPROFITSEGMENT       =
    *      POACCOUNTX                   =
    *      POCONDHEADER                 =
    *      POCONDHEADERX                =
    *      POCOND                       =
    *      POCONDX                      =
    *      POLIMITS                     =
    *      POCONTRACTLIMITS             =
    *      POSERVICES                   =
    *      POSRVACCESSVALUES            =
    *      POSERVICESTEXT               =
           EXTENSIONIN                  = it_extensionin
    *      EXTENSIONOUT                 =
    *      POEXPIMPITEM                 =
    *      POEXPIMPITEMX                =
    *      POTEXTHEADER                 =
    *      POTEXTITEM                   =
    *      ALLVERSIONS                  =
    *      POPARTNER                    =
    *      POCOMPONENTS                 =
    *      POCOMPONENTSX                =
    *      POSHIPPING                   =
    *      POSHIPPINGX                  =
    *      POSHIPPINGEXP                =
    *      POHISTORY                    =
    *      POHISTORY_TOTALS             =
    *      POCONFIRMATION               =
    It gives me messages saying that
    Please also populate interface parameter POHEADERX
    No data changed
    Where am I going wrong..
    Waiting for your replies....
    Thanks,
    Chaitanya

  • 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.

  • Custom field in Purchase Requisition Release

    Hi all,
    I have create a popup with a custom field when the user releases first step of a Requisition Release, via ME54N.
    The system don't save my custom field, I have used this exit:
    EXIT_SAPLMEREQ_005 of the ampliament MEREQ001.
    my code:
       CALL SCREEN 999 STARTING starting at 5 10                 MOVE: eban-zzsubmi       TO ls_item-zzsubmi,
                eban-zzappunto     TO ls_item-zzappunto,
                zzautfor           TO ls_item-zzautfor,
                eban-zzattautor    TO ls_item-zzattautor,
                eban-zzdatattoauto TO ls_item-zzdatattoauto.
       CALL METHOD im_req_item->set_data( ls_item ).
    the ls_item, is ok, with my custom field, but seeing in debug this method, the system don't save my field.
    Maybe we don't have the permission of change custom field on EKKO during Release step?
    Thanks all.
    Reward for all.

    Hi ,
    Try with create new tab in PR item level, add field in custom tab example Final release Tab.
    Try to fetch data from EBAN table when final release happened ( based on status ) the date will update in this table. I hope this is helpful.
    Use user exit to create custom tab and custom field 
    enhancement MEREQ001 : check this enhancement.
    user exit EXIT_SAPLMEREQ_0*
    I hope it is helpful

  • R3 Unicode error when transferring SRM PO with custom fields to R3

    We have an SRM 5.0 system.  We are sending an SRM created PO to R3 (4.7).  This works perfectly if there are no custom fields.  We added 1 custom field of 1 character byte to the SRM PO Header.  When this is done there is a dump in R3 in SAPLBBP_BAPI_PO in "MAPPING_CUSTOMER_FIELDS" saying Data objects in a Unicode program are not convertible.
    This happens at the following statements
    ASSIGN wa_bapi_cf_header TO <l_tmp_fs>.
    l_valuepart = <l_tmp_fs>.
    We think this is related to our custom fields on EKKO on the R3 side where there is a currency field (packed), but we are not sure since we just started working with SRM.  Below is our R3 PO header structure for custom fields.
    wa_bapi_cf_header has the definition of PO header in our R3 system that contains a packed field.
    .INCLUDE     CI_EKKODB          0
    ZZCMPCD     ZCMPCD     CHAR     1
    ZZTDRIND     ZTDRIND     CHAR     1
    ZZACO     ZACO     CHAR     1
    ZZBIDROOM     ZBIDROOM     CHAR     1
    ZZCAS     ZCAS     CHAR     1
    ZZPONEG     ZPONEG     CHAR     1
    ZZWARRPO     ZZWARRPO     CHAR     1
    ZZQUOTETYPE     ZZQUOTETYPE     CHAR     10
    ZZAPRDT     ZZAPRDT     DATS     8
    ZZAPRTIM     ZZAPRTIM     TIMS     6
    ZZMASSIST     ZZMASSIST     CURR     17                 
    ZZPD     ZZPD     CHAR     1
    ZZREASON     ZZREASON     CHAR     2
    The field being sent from SRM is
    ZZACO     ZACO     CHAR     1.
    How can I correct this problem?  
    Thank you for any help you can give.
    Ada Thompson

    Hi,
    See these related threads;
    short dump(UC_OBJECTS_NOT_CONVERTIBLE)
    Data objects in a Unicode program are not convertible?what does this mean?
    Virtual Char error - UC_OBJECTS_NOT_CONVERTIBLE
    /message/1069612#1069612 [original link is broken]
    BR,
    Disha.
    Do reward points for useful answers.

  • Updating custom field in table EKKO within user exit when PO is saved

    I am trying to update a custom field in table EKKO when a PO is saved.  I am using FM EXIT_SAPMM06E_013, within enhancement MM06E005.  Since EKKO is not a table that can be updated with this user exit, I am using a technic that I read about on SDN where I assign a field symbol to the calling program variable and then am able to access data within EKKO table.  But when I pass this data back into the field symbol, for some reason this field is not getting saved when the PO is saved.  In debug mode, it looks like this field is getting updated, but when I look in the table after the PO is saved, it is not there.  My code sample is below.  What I am doing wrong?
    data:
      CHAR(50) VALUE '(SAPLMEPO)EKKO-ZHDRCSTCENTER',
      g_zhdrcstcenter like ekko-zhdrcstcenter,
      FIELD-SYMBOLS <F1> type any.
    if i_ekko-ekorg = '5401'.
      ASSIGN (char) to <F1>.
      g_zhdrcstcenter = <F1>.
      move '0000113322' to g_zhdrcstcenter.
      <F1> = g_zhdrcstcenter.
    endif.
    Thanks!
    Sarah Smyth.

    Firstly, have you investigated using EXIT_SAPMM06E_008 to set any custom fields you have added in the EKKO_CI / CI_EKKODB structure?.. that might work more easily.
    In terms of doing an assign back into a calling program's memory, it can work but it's probably worth setting a break point in your code then stepping through watching the values in EKKO - sometimes you can find subsequent code that re-writes an earlier copy of values back into the structure, thereby preventing you doing your change...  SAP does warn this method is for "internal use".  Also check in your debugger that it's SAPLMEPO and not SAPMM06E you need.

  • Strategy for Custom Fields

    Hi Everyone,
    I've a question related to handling of custom fields during upgrade.
    Scenario:
    9.0 delivered record has a custom field added to it.
    After initial pass, following happened.
    1. 9.0 delivered record was replaced by 9.2 delivered record structure
    2. Custom Field was deleted
    3. Data for the custom field was dropped too..
    Q1 What should be the best strategy to get the data and field back... Here is what I understand.
    Keep 9.2 record
    Add custom field to it.
    Import data for custom field from another 9.0 environment.
    Suggestions welcome.

    during initial move don't drop the custom added fields which are needed.
    This way you will not lose the data

  • Custom field in PO header tab and its editable status

    Hi All,
    I have added an input field in the PO header (Customer Data) tab.
    The same field has been appended in the EKKO table.
    The update as per user's entry in PO is getting done in database table.
    The field will get grayed out for ME23N tcode and will be editable for ME21N and ME22N.
    The logic has been written in the PBO section.
    Now, within the tcode ME23N, user has option to get into change mode by pressing F7.
    Once user clicks F7, the PO gets into change mode, but the custom field will be still in uneditable mode itself.
    There are couple of other custom fields are in the same tab. They get into change mode with F7, but this alone remains un editable.
    How to make it editable in this scenario???
    Regards
    Pavan
    Edited by: Pavan Sanganal on Dec 26, 2011 6:56 PM

    HI Pavan,
    so only one custom field will not update in update mode after clicking f7 , so what happend exactally when user clciks on f7 the field properties are changed in to editable mode, in module pool program we can change field properties using internal table SCREEN , so loop the screen check this input field properties , like
    loop at screen .
    if screen-name = 'custom_field'.
    input = 'x'.
    endif.
    endloop.
    Regards
    Siva

  • 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

  • Customer field in ME22N Purchase Order Transaction

    Hi all,
    I have to add an additional field to Ekko and want to maintain it using the Enjoy Purchase Order Transaction.
    To do so, I added an append to ekko and MEPOHEADER with my z-Field and implemented the Badis:
    ME_PROCESS_PO_CUST  Method PROCESS_HEADER to read the data from vendor and to set the modell using:
    call method lo_obj->set_data
        exporting
          im_data = lw_header.
    In ME_GUI_PO_CUST  Method TRANSPORT_FROM_MODEL I want to read the data using
    data: lo_header       type ref to if_purchase_order_mm,
    lw_header = lo_header->get_data( ).
    my Problem: My Z-Field in structure lw_header is initial; the data is lost!
    Did I forget a step? Is it necessary to add z-fields to CI_EKKODB instead of using own appends?
    Thx

    Hi,
    If you want to add fields in header then append the fields to the standard structure
    'CI_EKKODB' provided in EKKO table and if it is item level then append the fields to the structure
    'CI_EKPODB'.
    Now in 'MM06E005'  make use of the following components for your use.
    1) EXIT_SAPMM06E_006 - Export Data to Customer Subscreen for Purchasing Document Header
    Here, you can export the data to the subscreen by making use of the parameters 'I_EKKO' and 'I_CI_EKKO'
    provided in the import parameters of the exit.
    2) EXIT_SAPMM06E_008 - Import Data from Customer Subscreen for Purchasing Document Header
    You can import the data from screen from 'EKKO_CI' and if you want to update the EKKO table with those values
    then make use of the parameter 'E_CI_EKKO'.
    I hope this will help you.
    If you want anymore help, get back to me.
    Regards,
    Jallu

  • Long text field required in customer field

    HI everybody,
      We are in the implementation of SRM 5.0. Here requirement is using z include structure, the customer fields have to be added.
    In structure, i can add my own fields. But customer wants long text in customer fields.
    If i maintain a field with 300 character means, screen displayed as single field as lengthy one.
    But customer wants long text.Main worry from customer side is, they want to able to copy and paste paragraph into SRM customer field.
    So please suggest me that how can i acheive this issue.
    Txns in advance

    Hi.
    You call read/write this field with FM REAd_TEXT of WRITE_TEXT, check this example:ù
    ztdline       TYPE tline           OCCURS 0   WITH HEADER LINE,
            CALL FUNCTION 'READ_TEXT'
              EXPORTING
                client                  = sy-mandt
                id                      = 'F01'
                language                = 'I'
                name                    = ekko-ebeln
                object                  = 'EKKO'
              TABLES
                lines                   = ztdline
              EXCEPTIONS
                id                      = 1
                language                = 2
                name                    = 3
                not_found               = 4
                object                  = 5
                reference_check         = 6
                wrong_access_to_archive = 7
                OTHERS                  = 8.
            IF sy-subrc <> 0.
         MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
            ENDIF.
    the table ztdline have the long text.

  • Saving customer fields to SAP table (EXIT_SAPMM06E_012)

    Hi All,
    I would like to ask you guys a bit of a help with a user exit that I am working on as of the moment.
    I am coding a user exit for a service purchase order (ekpo-knttp = 'K' and ekpo-pstyp = 'D') this is a service purchase order of cost centre category.
    Since SAP does not allow the goods recipient (ekkn-wempf) to be modified for reasons specified in SAP Note 118008. I have used user exit MM06E005 FMs EXIT_SAPMM06E_017, EXIT_SAPMM06E_016 to the data in PBO and PAI for the transaction.
    Now I tried using the two FMs EXIT_SAPMM06E_018 and EXIT_SAPMM06E_012 to pass this value to the table but it does not seem to get saved in table EKKN.
    Using FM EXIT_SAPMM06E_018  the I have maintained the structure CI_EKPODB to include WEMPF and after debugging passing that user exit area the wempf is being tranfered to global data but this does not get saved in EKKN table (EKKN-WEMPF).
    Although this is outside of the standard best practice of SAP since the account assingment belongs to the limits or the service line for service order but maintaining this recipient field for the PO item does not impact our system processes as the business acknolwedges goods recipient for service PO.
    BADI ME_PROCESS_PO_CUST has also been implemented under method PROCESS_ACCOUNT invoking the interface IF_PURCHASE_ORDER_ACCOUNT_MM but unsucessful in the operation.
    If anyone of you guys has encoutered same scenario or implementation requirement please do give information on this or work-arounds are well appreciated as well.
    Cheers,
    Erwin

    Hi,
    We have worked on a similar requirement ,just check if its useful to you.
    Requirement:
                         You have to add the custom field in SAP standard table EKKO. Then we have to place the field in ME21N screen. When user enters any input into the field it should get updated in the database.
    Note:
                         EKKO table is meant for Purchasing document header, you should add the field in the header level for ME21n screen. There you are provided with customer sub screens where you can add the field in the screen.
    Procedure:
    1You have to create a field in the Custom Include of standard table, after creating activate it.
    2.Double click on the include then you can add your custom field here.
    Find out the Required Enhancements:
    1.Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton u2018Information systemu2019.
    2.Then mention the particular package name of the transaction you need to      enhance. Then you will be shown the list of Enhancement components for that particular package.
    3.Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
    MM06E005 is the Enhancement component we are using here.
    Development
    Creating a Project to include the enhancement:
    1.Go to transaction CMOD and create a project.
    2.Enter a description for the project.
    3.Then, click on the pushbutton u2018Enhancement Assignmentsu2019 in the Application Toolbar.
    4.Click on the components in Application Toolbar.
    5.Here you will be shown the function module exits, screen exits and Include tables.
    6.Click on the custom screen SAPLXMO6 u2013 0101 in which it suits the requirement of adding the custom field to the layout
    7.Click on layout and go to get from dictionary and select the field you need to add and click ok.
    8.Place the field in the layout and activate it.
    9.After that you come back and check the respective function module in which you need to implement the code. So, we need to import the data from sub screen for purchasing document header. Therefore we have chosen  the  EXIT_SAPMM06E_008.
    10. Write code in the Function Exits to synchronize the programs:
                       Now, code has to be written in the function modules EXIT_SAPMM06E_008 so that data flows to and fro between the main SAP program and custom sub screen program. Double clicking on the exit we get the following screen.
    11. Double click on the include and write the required code inside it. Then activate it.
    TABLES:EKKOIF NOT EKKO_ZADD IS INITIAL.
    MOVE EKKO-ZADD  to e_ci_ekko-zadd.
    move corresponding  e_ci_ekko to ekko.
    modiky ekko  from ekko.
    12. Now come back and activate the entire project.
    13. Now go to ME21n transaction and create a purchase order by giving all the mandatory fields including custom field we have created. Here Test is the custom field we have created. After entering the data then press SAVE button, your data will be populated to the respective table.
    14. Go to SE11 or SE16n, check whether the field got updated in the database or  not in EKKO table.
    Thanks,Surya Pydikondala.
          Finally it gets updated in the database.

  • MRP Generated production orders greys out Sales Order and Customer fields

    Hi there,
    The MRP generated production orders greys out the Sales Order and Customer fields for some reasons. These fields are really important as they link the production order to the sales order and the customer's purchase order. Could the SAP team please fix this or advise alternative way of getting the sales order and customer info on production order? Thanks.

    Hello
    MRP only poulated this fields in case the material master has been set up with a strategy group hich is make to order (normally 20). Otherwise MRP summarizes all the requirements from different Customer orders and creates a production order
    Stephan

  • How to replicate customer fields in the  backend system.

    Hi All,
    I need to transfer PO customer fields that were created in the SRM system to backend SAP system.
    I am using Extended Classic Scenario in SRM and SRM Version is 5.0.
    I am able to replicate the data created in SRM system to the backend.
    How ever, I found the following BADI while debugging.
    1. BBP_DOC_SAVE_BADI
    2. BBP_CTR_RELVAL_ICC
    3. BBP_DOC_SAVE_ICC
    4. BBP_F4_SAVE_DB
    5. HRSYNC_P
    Hence, please tell me which BADI, I need to use to send my customer fields to the backend system.
    Regards,
    Venky.

    Hi
    As Disha told, <u>You need to create a customer Implementation of any othe BADIs using SE19 Transaction.
    Say, you create an active customer Implementation of BBP_ECS_PO_OUT_BADI...</u>
    <u><b>See links given in earlier reply for detailed sample code.</b></u>
    <u>Write the following sample code (pls change it as per your business requirement)</u>
    METHOD if_ex_bbp_ecs_po_out_badi~bbp_b46b_po_outbound.
    ** Customer fields
    MOVE 'POHEADER' TO w_customer_fields-refobject.
    *PO approver
    MOVE 'ZZAPPROVER' TO w_customer_fields-fieldname.
    MOVE is_header-zzlastapprover TO w_customer_fields-container.
    APPEND w_customer_fields TO ct_bapi_customer_fields.
    *SC Date
    MOVE 'ZZSCDATE' TO w_customer_fields-fieldname.
    MOVE lv_scheader-created_at TO w_customer_fields-container(15).
    APPEND w_customer_fields TO ct_bapi_customer_fields.
    *Requester Org
    MOVE 'ZZORGA' TO w_customer_fields-fieldname.
    MOVE w_requester_orgunit TO w_customer_fields-container.
    APPEND w_customer_fields TO ct_bapi_customer_fields.
    endmethod.
    <u>BBP_PO_INBOUND_BADI in R/3.</u>
    method IF_EX_BBP_PO_INBOUND_BADI~BBP_MAP_BEFORE_BAPI.
    data wa_customer_fields TYPE BBPS_IF_CUSTOMER_FIELDS.
    data : WA_BAPI_TE_MEPOHEADER type BAPI_TE_MEPOHEADER,
    WA_BAPI_TE_MEPOHEADERX type BAPI_TE_MEPOHEADERX.
    data WA_EXTENSIONIN TYPE BAPIPAREX.
    data txt_960(960) type c.
    *** EKKO Customer fields.
    *PO Number
    move BBP_POHEADER-PO_NUMBER to WA_BAPI_TE_MEPOHEADER-PO_NUMBER.
    move BBP_POHEADER-PO_NUMBER to WA_BAPI_TE_MEPOHEADERX-PO_NUMBER.
    *ZZAPPROVER
    READ TABLE BBP_CUSTOMER_FIELDS INTO wa_customer_fields
    WITH KEY refobject = 'POHEADER'
    fieldname = 'ZZAPPROVER'.
    IF SY-SUBRC EQ 0.
    MOVE wa_customer_fields-container TO WA_BAPI_TE_MEPOHEADER-ZZAPPROVER.
    WA_BAPI_TE_MEPOHEADERX-ZZAPPROVER = 'X'.
    endif.
    *ZZSCDATE
    READ TABLE BBP_CUSTOMER_FIELDS INTO wa_customer_fields
    WITH KEY refobject = 'POHEADER'
    fieldname = 'ZZSCDATE'.
    IF SY-SUBRC EQ 0.
    MOVE wa_customer_fields-container TO WA_BAPI_TE_MEPOHEADER-ZZSCDATE.
    WA_BAPI_TE_MEPOHEADERX-ZZSCDATE = 'X'.
    endif.
    *ZZORGA
    READ TABLE BBP_CUSTOMER_FIELDS INTO wa_customer_fields
    WITH KEY refobject = 'POHEADER'
    fieldname = 'ZZORGA'.
    IF SY-SUBRC EQ 0.
    MOVE wa_customer_fields-container TO WA_BAPI_TE_MEPOHEADER-ZZORGA.
    WA_BAPI_TE_MEPOHEADERX-ZZORGA = 'X'.
    endif.
    CLEAR txt_960.
    CLEAR WA_EXTENSIONIN.
    write WA_BAPI_TE_MEPOHEADER to txt_960 left-justified.
    WA_EXTENSIONIN-STRUCTURE = 'BAPI_TE_MEPOHEADER'.
    WA_EXTENSIONIN-VALUEPART1 = txt_960(240).
    WA_EXTENSIONIN-VALUEPART2 = txt_960+240(240).
    WA_EXTENSIONIN-VALUEPART3 = txt_960+480(240).
    WA_EXTENSIONIN-VALUEPART4 = txt_960+720(240).
    append WA_EXTENSIONIN to BAPI_EXTENSIONIN.
    CLEAR txt_960.
    CLEAR WA_EXTENSIONIN.
    write WA_BAPI_TE_MEPOHEADERX to txt_960 left-justified.
    WA_EXTENSIONIN-STRUCTURE = 'BAPI_TE_MEPOHEADERX'.
    WA_EXTENSIONIN-VALUEPART1 = txt_960(240).
    WA_EXTENSIONIN-VALUEPART2 = txt_960+240(240).
    WA_EXTENSIONIN-VALUEPART3 = txt_960+480(240).
    WA_EXTENSIONIN-VALUEPART4 = txt_960+720(240).
    append WA_EXTENSIONIN to BAPI_EXTENSIONIN.
    endmethod.
    Hope this will help.
    Regards
    - Atul

Maybe you are looking for