Field Exit in ME21N -PO

Hi all,
This is related to the Tcode ME21N (PO).
I need to put validations on the fields of Purchasing Document and Item in the above Tcode.These are the fields at the item level in the last two columns.For this I have created 2 Field Exits for the Purchasing Document(Data Element-EBELN and Item (Data Element EBELP).
The problem is that there are 2 Item fields (the first column and the Last Column) of the same Data Element EBELP.Now for both these fields the field exit for the Item gets trigerred, once for each (ie first it has the value from the 1st column and next time it has value from last column).Now my validations are required only for the Last Column entry.
So how do I make out in the logic of the field exit that it has been trigerred only for the Last Column Entry.Can I use the Field name in the screen for Last Column in any way for my requirement.
Your Inputs are appreciated and will be rewarded.
Thanks,
Stock.

see u need to get the entries as
Ebeln        EBELP
12000001   0001
12000001   0002
so if i want to validate on ebeln for item 2 then i need to differentiate it in hte select
12000001 0001
<b>12000001 0002</b> "---> on limit the validation of 2
so i need to feed EBELP in the select statement .
select single EBELN EBELP from EKPO
where EBELN  = P_EBELN
  and EBELP =  P_EBELP
To fetch the right entry u need to reach only that value of ebelp .
Pass the code .
regards,
vijay

Similar Messages

  • Field Exit for ME21N & ME22N transactions

    HI Friends,
    I need to make the SAP Standard screen field "Overdeliv. Tol." & "Unlimited" to inactive under the Item level data --> Delivery tab in ME21N & ME22N transaction.
    Can i do ths? If so give me the steps and Screen exit for the same...

    For User Exit's
    goto to tcode->status->program name->double click on that,
    then goto to-> attribute take the package name and
    Goto SMOD tcode ->Utilities->give the package name and F8
    then a list of exits will display for that tcode as well as that package.
    double click on the exit u can see the Fm exit,screen exit,feild exit,include exit. there
    u can check the table MODSAP
    For BADI's,
    1)goto to tcode SE24 give the CL_EXITHANDLER and display and then double click on the GET_INSTANCE
    keep Break point at this location 'call method cl_exithandler=>get_class_name_by_interface'
    then the tcode it will trigger there and we can debugg there we can find badi'for that tcode and then remove the break point.
    2)Goto to tcode->status->program name->double click on that program will display's
    then  press crtl+F then cl_exithandler
    Thank u,
    santhosh

  • ME21n - Purchase order field exit??

    Hi
    Does anybody know what the ME21n (enter purchase order) field exit would be so that I can default a particular G/L account (HKONT) when the account assignment group is 'F' & the purchasing org is a particular value?
    If you can also confirm if that is going to be possible with coding in that field exit I would appreciate it....
    Thanks all for your time...

    Screen Exit
    Please remove the TDS-related input fields on the PO entry screen on the customer data tab  (PO line details).
    - TDS account
    - TDS cost code
    - TDS sub code
    1.     Goto Transaction Code Me21n
    Fill the following fields
    Enter
    Give the input values in following fields from  ORGDATA TAB
    Purchasing org
    Purchasing group
    Company code
    Vendor
    Enter
    Select Customer Data tab like following
    USER EXIT  : MM06E005 (Customer fields in purchasing document )
    &#61664;  Goto  : T.Code : SMOD
    &#61664;     Give the Enhacement Name : MM06E005
    &#61664;     Click on Display
    &#61664;     Click on Components Push Button
    &#61664;     Double click on function module EXIT_SAPMM06E_016( Export Data to Customer Subscreen for Purchasing document item)
    &#61664;     Double click on Include ZXM06O01.
    &#61664;     Insert the following coding in that include
    SET PARAMETER ID 'BUK' FIELD g_ekko-bukrs.
      LOOP AT SCREEN.
        IF screen-name = 'EKPO_CI-ISMSUBTITLE1'.
          screen-input = '0'.
          MODIFY SCREEN.
        ENDIF.
    *>>>>>>>>>>>>>>>>>>>>>> Begin of insert CR336/BG1 >>>>>>>>>>>>>>>>>>>>>>
        IF screen-name = 'G_EAN11'.
          screen-input = '0'.
          MODIFY SCREEN.
        ENDIF.
    *<<<<<<<<<<<<<<<<<<<<<<< End of insert CR336/BG1 <<<<<<<<<<<<<<<<<<<<<<<
    *>>>>>>>>>>>>>>>>>> Begin of Changes for K896570/501411945 <<<<<<<<<<<<<
    IF screen-name = 'EKPO_CI-TDSACCOUNT'.
          screen-input = '0'.
          MODIFY SCREEN.
        ENDIF.
    IF screen-name = 'EKPO_CI-TDSCOST'.
          screen-input = '0'.
          MODIFY SCREEN.
        ENDIF.
    IF screen-name = 'EKPO_CI-TDSSUB'.
          screen-input = '0'.
          MODIFY SCREEN.
        ENDIF.
    *>>>>>>>>>>>>>>>>>> End of Changes for K896570/501411945 <<<<<<<<<<<<<
    *>>>>>>>>>>>>>>>>>>>>>> Begin of insert SM1 >>>>>>>>>>>>>>>>>>>>>>
        IF ( screen-name = 'EKPO_CI-TDSACCOUNT'
          OR screen-name = 'EKPO_CI-TDSCOST'
          OR screen-name = 'EKPO_CI-TDSSUB'
          OR screen-name = 'TDS_TXT_1'
          OR screen-name = 'TDS_TXT_2'
          OR screen-name = 'TDS_TXT_3'
          OR screen-name = 'TDSACCOUNT-DESC'
          OR screen-name = 'TDSCOST-DESC'
          OR screen-name = 'TDSSUB-DESC'  ).
          IF g_ekko-bukrs(2) <> 'U6'.       "not a theatrical company
            screen-invisible = '1'.
            screen-input     = '0'.
          ELSEIF g_flag = 0.                "display only
            screen-invisible = '0'.
            screen-input     = '0'.
          ELSEIF g_flag = 1.                "change
            screen-invisible = '0'.
    *>>>>>>>>>>>>>>>>>> Begin of Changes for K896570/501411945 <<<<<<<<<<<<<
           screen-input     = '1'.       "Fharook Syed
            screen-input     = '0'.        "Fharook Syed
    *>>>>>>>>>>>>>>>>>> End of Changes for K896570/501411945 <<<<<<<<<<<<<
          ENDIF.
          IF screen-name = 'EKPO_CI-TDSACCOUNT'.
            screen-required  = '1'.
          ENDIF.
          MODIFY SCREEN.
        ENDIF.
    *>>>>>>>>>>>>>>>>>>>>>> End of insert SM1 >>>>>>>>>>>>>>>>>>>>>>
    &#61664; save & activate.
    &#61664; Repeat the above process in ME21N to see customer data fileds in CUSTOMER DATA tab
    After the above Modifications CUSTOMER DATA is   displaying like this
    rewars if useful

  • Exit for ME21N

    Hi,
    Need your help for solving an issue related to ME21N ( Purchase Order Creation)
    I am having ZVRL(say) condition type that is mandatory and is defined in pricing schema ZVVA01(say).ZVVA01 is further attached to purchase organisation 4000 (say).
    I am having a document type ZVVN . I want to save the purchase order without ZVRL (Defined as Mandatory condition)  for particular document type ZVVN. But as ZVRL is mandatory condition , So system does not allow me to save the purchase order.
    For solution following option have been ruled out by the client-
    1) Through a separate vendor schema with different purchase organization.
    2) Entering any value like .01 or .002 for the mandatory condition type that is for ZVRL.
    Other than above two, Can anyone please tell me if there is any exit/badi/ or pricing routine available through which we can avoid mandatory ZVRL condtion for particular document type ZVVN at the time of saving and changing the Purchase order.
    Thanks
    Deepak Gupta

    Hi,
    Check all user exit for ME21N
    Transaction Code - ME21N Create Purchase Order
    Exit Name Description
    LMEDR001 Enhancements to print program
    LMELA002 Adopt batch no. from shipping notification when posting a GR
    LMELA010 Inbound shipping notification: Transfer item data from IDOC
    LMEQR001 User exit for source determination
    LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001 Customer-Specific Source Determination in Retail
    M06B0001 Role determination for purchase requisition release
    M06B0002 Changes to comm. structure for purchase requisition release
    M06B0003 Number range and document number
    M06B0004 Number range and document number
    M06B0005 Changes to comm. structure for overall release of requisn.
    M06E0004 Changes to communication structure for release purch. doc.
    M06E0005 Role determination for release of purchasing documents
    ME590001 Grouping of requsitions for PO split in ME59
    MEETA001 Define schedule line type (backlog, immed. req., preview)
    MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
    MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
    MEQUERY1 Enhancement to Document Overview ME21N/ME51N
    MEVME001 WE default quantity calc. and over/ underdelivery tolerance
    MM06E001 User exits for EDI inbound and outbound purchasing documents
    MM06E003 Number range and document number
    MM06E004 Control import data screens in purchase order
    MM06E005 Customer fields in purchasing document
    MM06E007 Change document for requisitions upon conversion into PO
    MM06E008 Monitoring of contr. target value in case of release orders
    MM06E009 Relevant texts for "Texts exist" indicator
    MM06E010 Field selection for vendor address
    MMAL0001 ALE source list distribution: Outbound processing
    MMAL0002 ALE source list distribution: Inbound processing
    MMAL0003 ALE purcasing info record distribution: Outbound processing
    MMAL0004 ALE purchasing info record distribution: Inbound processin
    MMDA0001 Default delivery addresses
    MMFAB001 User exit for generation of release order
    MRFLB001 Control Items for Contract Release Order
    AMPL0001 User subscreen for additional data on AMPL
    See which is suitable for your requirement.

  • User exit - for ME21N, 22N, 23N - at line item level

    Hi,
    I want to add new text field to display the description of the MPM(material) in it.
    That filed I want to add to the Account Assignment tab at item level.
    How to add that field on the screen, I mean any screen exit for this?
    and function module to pass the data to that field.
    If anybody worked on such problem then pls. let me know.
    Thanks in advance.
    -- Umesh

    Hi,
    These are the user exits for me21n.                
    AMPL0001          
    LMEDR001          
    LMELA002          
    LMELA010          
    LMEQR001          
    M06B0001          
    M06B0002          
    M06B0003          
    M06B0004          
    M06B0005          
    M06E0004          
    M06E0005          
    ME590001          
    MEETA001          
    MEFLD004          
    MELAB001          
    MEVME001          
    MM06E001          
    MM06E003          
    MM06E004          
    MM06E005          
    MM06E007          
    MM06E008          
    MM06E009          
    MM06E010          
    MMAL0001          
    MMAL0002          
    MMAL0003          
    MMAL0004          
    MMDA0001          
    MMFAB001     
    Regards
    praveen

  • Field Exit is not working in QA but working in Development Server....

    Hi friends,
                         I have created Field Exit for data element EPOS_LGORT (Storage Location) .Which is using in ME21N transaction of MM. This Field Exit is proper
      working in Development Server but after transport in QA it is not working. I have checked code , it is same as well as exist in development Server. 
                  Abap/fieldexit parameter already has been set as ‘Yes’. But still it is not working.
    Following values has been set for Parameter ‘abap/fieldexit’ for QA .       
    Dflt value                no
    ProfileVal               YES
    Current value          YES
    SAP Release         4.71
                         Any other setting required for  parameter's . Please suggest me.
    Thanks.

    Hi Chandrasekhar,
                           Thanks . Default value of parameter abap/fieldexit is 'yes or no' . Basis person told me that abap/fieldexit either can be set yes or no , so where we have to set 'X'  value for abap/fieldexit parameter.
      After execution of Program RSPARAM , following values found for  QA Server.
    1.1 R/3 C kernel               no
    2.1 file                             no
    3.1 file                             YES
    3.2 program parameters    YES
    3.3 Replace $$ and $(..)    YES
    3.4 Generate file name      YES
    4.4 Value in SharedMemory      YES
          Any other setting's  we needed ?

  • User Exit in ME21N Required

    Hi,
    Is there any user-exit for ME21N, thru which the below 3 values can be changed?
    Goods-Receipt (EKPO-WEPOS)
    Inv.Receipt       (EKPO-REPOS)
    GR-Based IV    (EKPO-WEBRE)
    Any pointers on this would be appreciated. Thanks in advance.
    Rgds,
    Bhargav.

    Hi,
    chk the following userexits..
    AMPL0001  User subscreen for additional data on AMPL            
    LMEDR001  Enhancements to print program                         
    LMELA002  Adopt batch no. from shipping notification when posting
    LMELA010  Inbound shipping notification: Transfer item data from
    LMEQR001  User exit for source determination                    
    LMEXF001  Conditions in Purchasing Documents Without Invoice Rece
    LWSUS001  Customer-Specific Source Determination in Retail      
    M06B0001  Role determination for purchase requisition release   
    M06B0002  Changes to comm. structure for purchase requisition rel
    M06B0003  Number range and document number                      
    M06B0004  Number range and document number                      
    M06B0005  Changes to comm. structure for overall release of requi
    M06E0004  Changes to communication structure for release purch. d
    M06E0005  Role determination for release of purchasing documents
    ME590001  Grouping of requsitions for PO split in ME59          
    MEETA001  Define schedule line type (backlog, immed. req., previe
    MEFLD004  Determine earliest delivery date f. check w. GR (only P
    MELAB001  Gen. forecast delivery schedules: Transfer schedule imp
    MEQUERY1  Enhancement to Document Overview ME21N/ME51N          
    MEVME001  WE default quantity calc. and over/ underdelivery toler
    MM06E001  User exits for EDI inbound and outbound purchasing docu
    MM06E003  Number range and document number                      
    MM06E004  Control import data screens in purchase order         
    MM06E005  Customer fields in purchasing document                
    MM06E007  Change document for requisitions upon conversion into P
    MM06E008  Monitoring of contr. target value in case of release or
    MM06E009  Relevant texts for "Texts exist" indicator             
    MM06E010  Field selection for vendor address                     
    MMAL0001  ALE source list distribution: Outbound processing      
    MMAL0002  ALE source list distribution: Inbound processing       
    MMAL0003  ALE purcasing info record distribution: Outbound proces
    MMAL0004  ALE purchasing info record distribution: Inbound proces
    MMDA0001  Default delivery addresses                             
    MMFAB001  User exit for generation of release order              
    MRFLB001                                                         
    regards,
    nagaraj

  • User Exit for ME21n - Urgent

    HI all,
    I want to add a function module when a Purchase order is saved(ME21n), i want to know how to find user exit for ME21n & which user exit to be changed.
    I want to call a function module when the user saves the purchase order, please help.
    Please also let me know the step to find the user exits.
    Thanxs in advance.

    Hi,
    Please check enhancement MM06E005 (SMOD).
    Here list of User exit and BADI for ME21N .
    Transaction Code - ME21N                    Create Purchase Order
    Enhancement/ Business Add-in            Description                                                    
    USER EXIT                                                                               
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.    
    MEQUERY1                                Enhancement to Document Overview ME21N/ME51N                   
    MEVME001                                WE default quantity calc. and over/ underdelivery tolerance    
    MM06E001                                User exits for EDI inbound and outbound purchasing documents   
    MM06E003                                Number range and document number                               
    MM06E004                                Control import data screens in purchase order                  
    MM06E005                                Customer fields in purchasing document                         
    MM06E007                                Change document for requisitions upon conversion into PO       
    MM06E008                                Monitoring of contr. target value in case of release orders    
    MM06E009                                Relevant texts for "Texts exist" indicator                     
    MM06E010                                Field selection for vendor address                             
    MM06E011                                Activate PReq Block                                            
    MMAL0001                                ALE source list distribution: Outbound processing              
    MMAL0002                                ALE source list distribution: Inbound processing               
    MMAL0003                                ALE purcasing info record distribution: Outbound processing    
    MMAL0004                                ALE purchasing info record distribution: Inbound processing    
    MMDA0001                                Default delivery addresses                                     
    MMFAB001                                User exit for generation of release order                      
    MRFLB001                                Control Items for Contract Release Order                       
    AMPL0001                                User subscreen for additional data on AMPL                     
    LMEDR001                                Enhancements to print program                                  
    LMEKO001                                Extend communications structure KOMK for pricing               
    LMEKO002                                Extend communications structure KOMP for pricing               
    LMELA002                                Adopt batch no. from shipping notification when posting a GR   
    LMELA010                                Inbound shipping notification: Transfer item data from IDOC    
    LMEQR001                                User exit for source determination                             
    LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt     
    LWSUS001                                Customer-Specific Source Determination in Retail               
    M06B0001                                Role determination for purchase requisition release            
    MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)      
    MEETA001                                Define schedule line type (backlog, immed. req., preview)      
    ME590001                                Grouping of requsitions for PO split in ME59                   
    M06E0005                                Role determination for release of purchasing documents         
    M06E0004                                Changes to communication structure for release purch. doc.     
    M06B0005                                Changes to comm. structure for overall release of requisn.     
    M06B0004                                Number range and document number                               
    M06B0003                                Number range and document number                               
    M06B0002                                Changes to comm. structure for purchase requisition release    
      Business Add-in  - BADI                 
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal              
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer     
    ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.      
    ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer   
    ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting                      
    ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation            
    ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order                 
    ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields                     
    ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions         
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions         
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer              
    ME_PURCHDOC_POSTED                      Purchasing Document Posted                                     
    ME_RELEASE_CREATE                       BAdI: Release Creation for Sched. Agreemnts with Rel. Docs     
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions         
    ME_REQ_POSTED                           Purchase Requisition Posted                                    
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address                       
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV               
    MM_EDI_DELFOR_OUT                       Enhancements for IDoc Output of SA Releases: Internal          
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order      
    MM_EDI_ORDERS_OUT                       Enhancements for IDoc Output of Purchase Order: Internal       
    SMOD_MRFLB001                           Control Items for Contract Release Order                       
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders              
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data                  
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI                                  
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level        
    ME_BAPI_PR_CHANGE_01                    BAdI: Enjoy BAPIs for Purchase Requisitions (Method Change)    
    ME_BAPI_PR_CHANGE_02                    BAdI: Enjoy BAPIs for Purchase Requisitions (Method Change)    
    ME_BAPI_PR_CREATE_01                    BAdI: Enjoy BAPIs for Purchase Requisitions                    
    ME_BAPI_PR_CREATE_02                    BAdI: Enjoy BAPIs for Purchase Requisitions (Method Create)    
    ME_BSART_DET                            Change document type for automatically generated POs           
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active                    
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant              
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)    
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation       
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO        
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking             
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges                          
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details                       
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India                  
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control             
    ME_CIP_REF_CHAR                         Facilitates Reference Characteristics in Purchasing            
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active           
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders              
    <b>Reward points</b>
    Regards

  • Field exit and Authorization grp

    Hi All,
    I have the following requirement...
    I Created a field exit for the data element (MATKL-for example)..Is there any chance that we could use that AG as indicator to evaluate in the field exit???
    That is...
    If the material group(MATKL) has the AG(Authorization group) populated with a value (ZRES – for example) ,then that particular Material group is restricted and should not be used in the creation/modification of documents.
    Is there any possiblilty of achieving the above requirement..??
    Please suggest a solution.
    Regards
    Shiva

    My requirement in this scenario is : I need to decide between a authorization group and field exit to restrict the users using some group of material groups which are obsolete.
    Since the field exits are created over a data element in many transactions such as ME21N/22N/23N/..etc the data element for material group is not MATKL so in such cases I need to create field exits for all data elements which the material group uses across various transactions.
    On the other hand, if I could restrict the use of certain material group based on authorization group then use of field exit would not be required…
    But the possible problem with this may be to restrict only certain transactions …but not all the transactions.
    Authorization Object: M_MATE_WGR
    Definition :
    Material group authorization for material master records.
    This object determines whether a user is authorized to maintain the material master record for a specific material group.
    Defined Fields
    Fields
    Possible values :
    ACTVT
    01 User may create data.
    02 User may change data.
    03 User may display data.
    06 User may mark data for deletion.
    BEGRU (Authorization grp-table T023)
    Here you must specify the
    authorization groups from Table T023
    for which the materials concerned may
    be processed.(may be any number of grps)
    Regards
    Shiva

  • Debugging Field Exits

    Hi,
    I am trying to create a field exit on Outline Agreement Field(KONNR) in ME21N. Can anybody plz guide me how I can debug the Function Module at the time of excuting the Transaction.
    Thanks in advance,
    Rinku.

    No.Field exit can not debug. Field exits have to be tested in isolation in the development environment. To analyze problems that occur only in the screen environment, the relevant variables can be written to the file system using TRANSFER... and can be analyzed there.
    Check whether you have assigned a value to the OUTPUT field.
    The following ABAP statements are not allowed in the function modules of field exits:
    BREAK-POINT,
    CALL SCREEN, CALL DIALOG, CALL TRANSACTION, SUBMIT,
    COMMIT WORK, ROLLBACK WORK,
    COMMUNICATION RECEIVE,
    EXIT FROM STEP-LOOP,
    MESSAGE I, MESSAGE W.
    regards
    vinod

  • Warning message in field exit

    Hi All,
    I'd the requirement of giving a warning message for transaction VA01 if user enters some specific order type.
    So I'd created a field exit for AUART for this screen. But i am able to give error message only and found out that warning & info messages can't be given in a field exit.
    Please help me out. Is there any way I can give a warning message in field exit or suggest some other sol. for it.
    Thanks,
    Manu

    Hi,
    Thanks f or your answers, but the issue is that i need to give this message as User enters the details on VA01 screen & presses enters.SO i can't use user exit like move_field_to_Vbak & others.
    Also, using a FM to give pop up message will ultimately make use of statement CALL SCREEN which is not allowed in field exit, i also tried FMs which displays messages normally means not in pop up screen, but again through it also i can only give error messages.
    Please suggets if there is any other option.
    Thanks,
    Manu Parihar

  • Error Message in Field Exit

    Hi All,
    We have a FM which throws an error message. When that is executed in report, it works fine and the error message is displayed.
    We have implemented this FM in FIELD EXIT for PRCTR. But it is not throwing any message. We checked the data, it is fine.
    Can any one know how to solve this??
    Thanks,
    Sreedhar

    Also you need to check whether this is assigned to any program/screen. As you know it will only trigger in the attached program.
    See the documentation of RSMODPRF program.
    Regds
    Manohar

  • Query on Field exits in ECC 6.0

    Hi All,
    We have implemented field exits in SAP R/3 4.6c and now we have upgraded to ECC 6.0.
    I need to know the following information:
    Are field exits obsolete in ECC6.0?
    Can we create new field exits in ECC 6.0 ?
    Going forward, what is the alternative technology/concept to be used - enhancement sports, BADIs etc for field validations(or instead of field exits)?
    Regards
    Shiva

    Hi,
    Though it is obsolete, SAP does not say dont you field exit. You can still use field exit. You can still create field exits.
    Whatever is already existing will definitely work. Creating a field exit is much more simpler and easy than the BADIs or Enhancement points.
    Yes you are right, going forward, you will have to use BADIs or Enhancement points.
    Regards,
    Subramanian

  • How to call an include in a field Exit?

    Hi Guys,
                  i am having a doubt ,How to call an Include in a field Exit function module.
                i wrote as "include zxx_incl." but if i wrote like this in my Field Exit i am getting a Suntax error
    "Recursive INCLUDE nesting in program "ZFLDEXIT_INCL". It contains an
    INCLUDE statement which calls itself or a previously read program
    ("ZFLDEXIT_INCL                           ").
    '                 i am having other doubt while creating an include program does we need to write a 1st statement as include zxx-incl within the same include ZXX_incl? if not i am getting a syntaxt error.
    thanks,
    Gopi.

    Yes, thats the problem.
    Your include is named ZFLDEXIT_INCL and in the first line of that include you probbaly wrote
    include ZFLDEXIT_INCL.
    Delete that, includes don't need a reserved word like programs and reports

  • Field Exit with DYNP_VALUES_UPDATE

    Hello, I am trying to develop a validation in a SAP transaction (XD01) to check some field values and if them are right then fill automatically the rest of the field in the screen, using a Function Modulo and the FM DYNP_VALUES_READ I am able to retrieve the field values correctly, my problem is when a try to fill the rest of the screen's fields with FM  DYNP_VALUES_UPDATE it doesn't work. Does anybody have used this FM? is possible what I am trying to do?
    Thanks in advice for your help.

    Hi Fernando,
    Using Field exit we can't populate multiple fileds, One filed exit is applicable for only one input filed.If you want to implement the
    filed exit for multiple fileds you have to implement the one exit for one filed.
    Regards,
    Mahender Reddy

Maybe you are looking for

  • Boot Camp / Win 7 (64-bit) install hangs at "windows loading files"

    I was hoping I might get some help from the community. I've got the new MBP 15", 2.66/i7 and OS 10.6.3. I launch Boot Camp utility, assign a partition for Windows (76 GB in this case), insert the Win 7 disc (Home Premium 64-bit OEM I just bought) whe

  • Need advice with support

    I have had problems with my iPhone 4 since about day 3. I get the No Sim Card error over and over all day. I have called apple many time and have logged over 12 hours on the phone with support now. My First call to apple I got an Advisor and after cl

  • Startup issue - Process 'Starting Framework'

    Hi I seem to have a startup issue with NM2004s.  I get a Half Green/ Half Yellow icon in the MMC.  The 01 instance is always yellow and never progresses onto green.  I have a process status of 'starting framework'. Anyone else had this issue? Cheers

  • Performance Issues in IS-Retail system

    Hi Idoc Gurus, We are working in IS-Retail environment. As a part of process we are posting sales from POS system in R/3 system. Which than create a billing document in SD.While doing this process,there are performance issues. Issue is that this sale

  • New, Z-Buffer related blending mode

    My suggestion is linked to Photoshop usage in still-image 3D composition. Specifically, it is about new layer blending mode what makes usage of depth channel (Z-buffer) information provided by rendering software. Very often I would like to be capable