User exit in VF01 for plant validation while taking the output smartform

Hi Gurus,
I am in a typical situation..
We ahve a scenario where for one specific plant we need to trigger a different output type(smartform) where the billing type is being common for all plants...
example: billing type : A00 ( same for all plants)
              outout type (billing) : B00 ( one smartform)
                                             C00 (another smartform)
For all the plants, Boo triggers as the layout is same for all Except for One specific plant where it should trigger C00 i.e., different smartform i.e., layout...
Any user exit for validating Plant at the time of saving the billing document to trigger a different outout type as above for the same billing type ???
Please help me..
regards
Ravikumar

Dear Ravikumar,
          You can do like this with out using User exit.
-->Take field Plant in to the output condition table
-->Put that condition table in to access sequence
-->Define two condition type as you mentioned B00 and C00
-->Assign access sequence to that condition types.
-->Put those output condition types in the output determination procedure.
-->Assign that output determination procedure to the billing type.
-->Main the condition records for that conditon types with one of the key combination PLANT
I hope it will help you
Regards,
Murali.

Similar Messages

  • User Exit in VF01 for Tax Conditions

    Hello,
    Please inform if any user exit is available for processing Conditions (Tax) in a Sales Order.
    I'm facing a problem that while Invoicing, a certain Tax condition is not being executed.
    Thanks,
    Shalabh Jain

    HI Colleague,
    I will list the available user-exit to be used for Billing Document:
    User Exits For Billing
    USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ)
    The internal number range used in the standard system is specified in the billing type table and can be changed in this user exit. This user exit is only called when the billing documents is created.
    USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
    In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMKCV (header fields).
    USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)
    In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMPCV (item fields).
    USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
    Depending on the number range, table TVFKD is used to set the billing date (country-specific requirments in Italy). USEREXIT_NUMBER_RANGE is automatically deactivated when this user exit is being applied.
    USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)
    This user exit is only called when the billing document is created. It is used to provide the header and the item of the new billing document with deviating or additional data.
    USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB)
    Printing the item line of a billing document can be supplemented or changed.
    USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
    Printing the header line of a billing document can be supplemented or changed.
    User exits in program RV60AFZD
    Short descriptions of the user exits are contained in the program:
    USEREXIT_RELI_XVBPAK_AVBPAK
    USEREXIT_NEWROLE_XVBPAK_AVBPAK
    USEREXIT_NEWROLE_XVBPAP_AVBPAK
    The following user exits are available in report SAPLV60B for transfer to accounting (function group V60B):
    EXIT_SAPLV60B_001: Change the header data in the structure acchd
    You can use this exit to influence the header information of the accounting document. For example, you can change the business transaction, "created on" date and time, the name of the person who created it or the transaction with which the document was created.
    EXIT_SAPLV60B_002: Change the customer line ACCIT
    You can use this exit to change the customer line in the accounting document. This exit is processed once the ACCIT structure is filled in with data from document header VBRK.
    EXIT_SAPLV60B_003: Change the customer line in costing
    The customer line is filled in differently for costing. You can use exit 003 to influence the ACCIT structure.
    EXIT_SAPLV60B_004: Change a GL account item ACCIT You can add information to a GL account item (such as quantity specifications) with this exit.
    EXIT_SAPLV60B_005: User exit for accruals
    Once all relevant data for accruals was entered in the GL account item, you can add to this data with this exit.
    EXIT_SAPLV60B_006: Change the control line ACCIT
    You can use exit 006 to add information to the control line.
    EXIT_SAPLV60B_007: Change the installment plan
    You can use exit 007 to add information to the installment plan
    parameters in the GL account item.
    EXIT_SAPLV60B_008: Change the transfer structure ACCCR, ACCIT and ACCHD
    After the accounting document is filled in with data, you can use exit 008 to change the document once again.
    EXIT_SAPLV60B_010: Item table for customer lines
    You can use exit 10 to influence the contents of customer lines before they are created.
    EXIT_SAPLV60B_0011: Change the parameter for cash account determination or reconciliation account determination
    You can use this exit to change inbound parameters in order to influence account determination.
    I hope that one of them could be helpful.
    Regards
    Ruy Castro

  • User Exit or BADI for Tcode IW31 when saving the Service Order

    Dear ABAPers,
            I would like to add one more line in Service order item when saving the Service order in (IW31).Is there User Exit or BAdI.It is very Urgent Please help me.
    Thanks & Regards,
    Ashok.

    Dear ABAPers,
    These Exits does not meet my requirement.
    These Exits are not called at the time of saving Service Order.
    Thank you for your valuable reply.
    My Requirement is when saving the service Order  i want to add the Line itm at runtime.
    It is very urgent requirement.Please help me.
    Thanks & Regards,
    ashok.

  • User Exit or Badi for MIRO

    Hi
    I need add some validations to data entry in MIRO for send their respective error messages and stop data saving.
    Does somebody knows some User Exit or Badi for make validations in MIRO ?
    Regards
    Frank

    Hi,
    you can use badi MRM_HEADER_CHECK. In order to put error message you can use function module
    PROT_FILL.
    * If there is any error do not allow posting
        DATA: gt_errtab    TYPE TABLE OF mrm_errprot,
              gs_errtab    TYPE mrm_errprot.
        CONSTANTS:     c_errprot(23)   TYPE c VALUE '(SAPLMRMF)TAB_ERRPROT[]'.
        FIELD-SYMBOLS: <fs_errprotj_dt> TYPE table.
        ASSIGN (c_errprot) TO <fs_errprotj_dt>.
        REFRESH gt_errtab[].
        gt_errtab[] = <fs_errprotj_dt>[].
        IF NOT gt_errtab[] IS INITIAL.
          READ TABLE gt_errtab INTO gs_errtab WITH KEY msgty = 'E'.
          IF sy-subrc = 0.
            DATA: c_okqx(17)   TYPE c VALUE '(SAPLMR1M)OK-CODE'.
            FIELD-SYMBOLS: <fs_okqx> TYPE ANY.
            ASSIGN (c_okqx) TO <fs_okqx>.
            CASE <fs_okqx>.
              WHEN 'BU'. "POST
    * This is optional: you can either search for a particular message or
    * do not allow any error message
    * Here search for the message triggered in badi INVOICE UPDATE
                READ TABLE gt_errtab INTO gs_errtab WITH KEY msgty = 'E'
                msgid = 'ZXX' msgno = '030'.
                IF sy-subrc = 0.
                  CLEAR <fs_okqx>.
                  MESSAGE s030(zxx). "While errors exist document will not be posted
                ENDIF.
            ENDCASE.
          ENDIF.
        ENDIF.
    This is used to give error message in case before posting the document.
    KR Jaideep,

  • User Exit or BADi for FB02

    Hi
    Does somebody knows some user exit or BADI for add validations to FB02 when user changes some position data.
    I need to validate some header BKPF (Company, Currency) and detail BSEG (Posting Key, Account Bank)  data when change the position.
    Does somebody knows one user exit or Badi wich i can use to do it  ?
    Thanks
    Frank

    Thanks for your answers.
    I need to make validations for send error messages and i can not use FI Validations and Sustitutions because i send several differents messages  and wuold need N steps (one step for each message).
    The enhancement points called in CHANGE_TO_MODIFY are executed when ok-code is 'CHAE' that is when the user calls FB03 and then change to modify mode for make changes like if he goes to FB02 , but these enhancements are no executed any more when the data changes are made and user press save.
    I already found some enhancement executed just before data saving (it's in FORM belegsummen_pruefen) so i make the validation and send the error message , but when error message appears the screen get protected so the user can not change any screen field for make the data corrections.
    Best Regards
    Frank

  • User Exit or BADI FOR ME59N

    Hi All,
       My requirement is in ME59N if Document Type is ZCD or ZSD it should not consider the Rounding Value (MARC-BSTRF) which is coming from Materrial Master (MRP1 View) and Purchase Info Record (EINE-RDPRF) which is coming from Purchase Info Record(ME12 or ME13), Can any one suggest me the right User Exit or BADI for this, Please go through the requirement.
    Regards,
    Sudhakar .A
    Edited by: Sudhakar Allam on Feb 5, 2010 4:31 AM

    HI Sudhakar ,
                              These are the list of enhancements and Badi's available for ME59N ,
    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
    AMPL0001                                User subscreen for additional data on AMPL
    MRFLB001                                Control Items for Contract Release Order
    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
    MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    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
    The list of Badi are
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
    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_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
    ME_PO_PRICING                           Enhancements to Price Determination: Internal
    ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
    ME_PURCHDOC_POSTED                      Purchasing Document Posted
    SMOD_MRFLB001                           Control Items for Contract Release Order
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
    ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
    ME_REQ_POSTED                           Purchase Requisition Posted
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
    ME_BSART_DET                            Change document type for automatically generated POs
    ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Leve
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKK
    ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN                    Commitment for return item
    ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
    ME_CHECK_OA                             Check BAdI for Contracts
    regards.

  • Need User exit or BAdi for VF01

    Hi.
    I need User exit or Badi for VF01.
    Condtion: After Successful Save of document number in database.
    Please help me.
    To be reward all helpfull answers.
    Regards.
    Jay

    Hi
    The follwing user exits and badis available:
                                                                                    Enhancement                                                                               
    V05N0001                              
    User Exits for Printing Billing Docs. using POR Procedure       
    V05I0001                              
    User exits for billing index                                    
    SDVFX011                              
    Userexit for the komkcv- and kompcv-structures                  
    SDVFX010                             
      User exit item table for the customer lines                     
    SDVFX009                               
    Billing doc. processing KIDONO (payment reference number)       
    SDVFX008                              
    User exit: Processing of transfer structures SD-FI              
    SDVFX007                               
    User exit: Billing plan during transfer to Accounting           
    V61A0001                               
    Customer enhancement: Pricing                                   
    V60P0001                               
    Data provision for additional fields for display in lists       
    V60A0001                               
    Customer functions in the billing document                                                                               
    Business Add-in                                                                                SD_CIN_LV60AU02                       
    BADI for billing                                                
    VOR_WA_FAKTURA                        
    Billing before Goods Issue                                                                               
    If it is helpful rewards points.
                         Regards
                          Pratap.M

  • User exit for SO creation while changing the net price for  item

    Hi folks,
    Is there any user exit or BADI to change the net price in the item label of Sales order??
      My req. is that--- i need to change the net price of sales item if the cond type is 'ZUR1 ?
      how can i achive this?
    Regards
    pabi

    Hi
    The user exits and badis for va01 tcode:
                                                                                    Enhancement/ Business Add-in            Description                                                                               
    Enhancement                                                                               
    V45L0001                             
      SD component supplier processing (customer enhancements)       
    V45E0002                               
    Data transfer in procurement elements (PRreq., assembly)       
    V45E0001                               
    Update the purchase order from the sales order                 
    V45A0004                              
    Copy packing proposal                                          
    V45A0003                               
    Collector for customer function modulpool MV45A                
    V45A0002                              
    Predefine sold-to party in sales document                      
    V45A0001                               
    Determine alternative articles for product selection           
    SDTRM001                              
    Reschedule schedule lines without a new ATP check              
    V60F0001                             
      SD Billing plan (customer enhancement) diff. to billing plan   
    V46H0001                               
    SD Customer functions for resource-related billing             
    V45W0001                             
      SD Service Management: Forward Contract Data to Item           
    V45S0004                              
    Effectivity type in sales order                                
    V45S0003                               
    RP-relevance for incomplete configuration                      
    V45S0001                              
    Update sales document from configuration                       
    V45P0001                               
    SD customer function for cross-company code sales                                                                               
    Business Add-in                                                                               
    BADI_SD_SCH_GETWAGFZ                   
    Scheduling Agreement: Read WAGFZ from S073                     
    BADI_SD_V46H0001                       
    SD Customer functions for resource-related billing             
    If it is helpful rewards points
    Regards
    Pratap.M

  • User exit or BADI for ME22N

    Hi,
    I need a user exit or Badi for defaulting Plant at line item level.
    The scenario goes like this: when ever user tries to change an existing Purchase order and tries to add a new line item in it, I need to trigger USEREXIT or BADI , so that it reads the previous line Plant and updates the current line with the same plant.
    I tried with user exit MM06E005 but it didnt seem to work.
    Can any one please help me?
    I am new to BADI, so I am not sure how to find the BADI and use it. It would be great if anyone can help me i this.
    Thanks
    Ramya

    Hello
    The BAdI ME_PROCESS_PO_CUST is the right one. The method PROCESS_ITEM should be triggered whenever the user changes something in the purchase order at item level and executes any kind of function (e.g. ENTER, CHECK or SAVE).
    However, instead of overwriting the user input via the BAdI you should implement method CHECK ( Closing Check ) where you can validate the user input. If any of your validation fails you can send an error message and set CHANGING parameter CH_FAILED = 'X'. This approach is much more transparent for the user.
    NOTE: In order to "send" an error message you need to add the include mm_messages_mac to your implementing class. For an example see class CL_EXM_IM_ME_PROCESS_PO_CUST (should be available on ERP 6.0):
    METHOD if_ex_me_process_po_cust~process_item .
      DATA: ls_mepoitem TYPE mepoitem,
            ls_customer TYPE mepo_badi_exampl,
            ls_tbsg     TYPE tbsg.
      INCLUDE mm_messages_mac. "useful macros for message handling
    * here we check customers data
      ls_mepoitem = im_item->get_data( ).
      IF ls_mepoitem-loekz EQ 'D'.
    * check field badi_afnam
        IF ls_customer-badi_afnam IS INITIAL.
          mmpur_metafield mmmfd_cust_02.
          mmpur_message_forced 'W' 'ME' '083' text-003 '' '' ''.
        ENDIF.
      ENDIF.
    ENDMETHOD.                    "IF_EX_ME_PROCESS_PO_CUST~PROCESS_ITEM
    Regards
      Uwe

  • User exit or BADI for recruitment

    Hi,
    I am new to HCM, can you give me user exit or badi for recruitment.
    Requirement - i have developed an infotype which i am updating through BSP, while the custom infotype is updated it should simultaneously update some of my Z tables. Hoping for positve replies earliest.
    Thanks in advance:-
    Santosh

    Hi,
    <b>Infotype</b>The data fields of HR master data, time management and recruitment are grouped logically into information types or infotypes for short.
    Examples of infotypes are "Family/Related Person", "Organizational Assignment, "Basic Pay".
    The following naming conventions apply to infotypes:
    Infotypes 0000 to 0999 are used for HR master data
    and sometimes for applicant data
    Infotypes 1000 - 1999 for organizational management
    Infotypes 2000 - 2999 for time data
    Infotypes 4000 - 4999 for applicant data
    Infotypes 9000 - 9999 for customers
    <b>Function character of step</b>
    This controls for which types of processing (create, change and/or delete a data record) a dynamic action should be carried out.
    The processing type is indicated by a two-digit numeric value. These values can be added up; in other words, you can enter several processing types for each infotype, subtype or field. A dynamic action can also be carried out independent of the current processing type.
    00 for Independent of the current function carried out
    02 for Change
    04 for Create
    06 for Change and create
    08 for Delete
    10 for Change and delete
    12 for Create and delete
    Examples
    If you enter 06, an action is carried out if the specified infotype was created or changed.
    If you enter 00, an action is carried out irrespective of whether the specified infotype was created, changed or deleted.
    <b>Variable function part</b>
    The variable function part, which depends on the indicator for step, can have the following meaning:
    <b>P - Plausibility checks</b>
    You can enter values for specific infotype fields. Field names must be entered in full. Literals and constants can serve as comparison values. These must be enclosed by inverted commas. Variables can also be used.
    The old value of a field can be used for comparison; the field name must be preceded by PSAVE-.
    If fields of other infotypes are used for comparison, these must be stored in the module pool of the current infotype.
    The following comparison operators are supported:
    = equal to,
    < less than,
    <= less than or equal to,
    > greater than
    >= greater than or equal to and
    <> not equal to.
    Consecutive checks must be linked by a logical AND. Logical OR links must also be indicated by a /X.
    Note:
    Note that all checks with OR links must have a /X.
    If the result of the comparison operation is not "true", then the following commands (I, F, W etc.) are skipped over until a field is reached or a new comparison operation takes place.
    Examples
    Infotype  Field ..... Ind.   Variable function part
    0007      STAT3       P      P0007-STAT3='0'
    0007      STAT3       P      PSAVE-STAT3='1'
    The step is taken if the value in the P0007-STAT3 field changes from 1 to 0.
    0007                     P      P0013-KLKZ1<>'0'/X
    0007                     P      P0013-ALVKZ<>'0'/X
    0007                     P      P0013-RVKZ1<>'0'/X
    0007                    P      P0013-RVNUM=SPACE
    The first three conditions are linked by an OR; at least one of these conditions must be met. Condition 4 must always be met.
    The step is taken if the following holds true:
    P0013-KVKZ1 not equal to 0 or P0013-ALVKZ not equal to 0 or P0013-RVKZ1 not equal to 0, and P0013-RVNUM empty.
    <b>I - Maintain infotype record</b>
    Enter the step, infotype, subtype, object ID, start and end dates of the record and an indicator which defines whether the step is to be run in the background. The possible actions are INS, COP, MOD, and DEL.
    Use commas to separate selection criteria just like the separator in the matchcode. If an entry is missing, the system inserts a comma.
    Separate the indicator for suppressing dialog from other entries by a slash D (/D).
    Constants, such as those for subtypes, are not enclosed in inverted commas.
    Variable entries are also permitted. Fields containing such values must be put in brackets.
    Examples:
    Infotype  Field ....  Ind.  Variable function part
          ....             I    INS,19,01/D
    Step: Create a Dates record, subtype 01, run in the background
          ....             I    DEL,14,M559
    Step: Delete Rec. Payments/Deds. record with subtype (wage type) M559.
    0007 ....                I    INS,8,,,(P0007-BEGDA),(P0007-ENDDA)
    Step: Create a Basic Pay record (0008) without subtype and object ID. The start and end dates are the same as those in the current Planned Working Time record (0007); specify these two fields only if they are filled because the dynamic action was triggered by this infotype.
    <b>W - Default values for new record</b>
    Literals or variables are used as default values.
    Set the defaults for the infotype, subtype, object ID, start and end dates using an I step and not a W step.
    Do not set defaults for Q fields of an infotype because the values for these fields are derived from the corresponding P fields.
    Examples
    Infotype  Subtype  ..... FC  Ind.  Variable function part
    0021       2              04  I     INS,0015,M430
    0021        2              04  W     P0015-BETRG='10000'
    When a Family/Related Person record (0021) record with subtype 2 (child) is created, an Additional Payments record (0015) with a default amount of 100.00 is created.
    <b>V - Cross-reference to another step</b>
    Here, you can combine fields to groups. The variable function part contains the value in the field which follows the "field" column. Steps which are specified only for the following field are also triggered for each of the other fields.
    Examples
    Infotype  Field  ..... FC  Ind.  Variable function part
    0016       PRBZH        06  V     PRBZT
    0016       PRBZT        06  I     DEL,0019,01/D
    Infotype 0019, subtype 01 is deleted in the background when the field PRBZT or PRBZH in infotype 0016 is changed or created (function code 06).
    The following entries are equivalent:
    0016       PRBZH        06  I     DEL,0019,01/D
    0016       PRBZT        06  I     DEL,0019,01/D
    <b>F - Call a routine</b>
    You can call internal (module pool) as well as external routines.
    If you call external routines, type the program name in brackets after the routine name. Do not specify 'using' parameters. When calling an external routine, all data must be declared in a common part. You can use the fields of structure RP50D to return values from the routine. These are not used in the standard system and can only be populated via the routine and then can be used for defaults (W-Commands).
    This allows customer-specific routines to be formulated with all the above steps.
    Example 1:
    Infotype  Field  .....  Ind.   Var.function part
    0016      PRBZT         F      PROBATION
    0016      PRBZT         I      INS,19,01
    0016      PRBZT         W      P0019-VTRMN=PRBEND
    Module pool MP001600 contains the PROBATION routine. This routine uses the entries in the fields P0016-PRBZT and P0016-PRBEH to determine the end of the probation period which it stores in the field PRBEND.
    The system creates a new 'Dates' record with the reminder date = PRBEND.
    Example 2:
    Infotyp ..... Ind. Var. function part
    0001           F      GET_DATE(ZPUDYN01)
    0001          I      INS,19,01
    0001           W      P0019-VTRMN=RP50D-DATE1
    The GET_DATE routine in program ZPUDYN01 calculates a date and enters this date in the RP50D-DATE1 field via "TABLES RP50D" in ZPUDYN01. This date can be user-defined in GET_DATE: if necessary, user-defined infotypes can be read afterwards.
    <b>M - Send a mail</b>
    Enter the name of the feature which defines the characteristics of the mail.
    Example
    Infotype  Field  .....  Ind.    Var.function part
    0001     SACHP         M       M0001
    A mail is sent when the field SACHP is changed. The characteristics of the mail are defined in feature M0001.
    In the standard system, feature M0001 is provided as a model. The documentation on feature M0001 explains how to define the characteristics of a mail.
    <b>ADDITIONAL HINTS</b>
    If you use a date as a constant, enter it as YYYYMMDD (YYYY=year, MM=month, DD=day).
    The table strings T001P, T503 and PSPAR are filled with the values which are valid on the record start date.
    The old values of the infotype are stored in the field string PSAVE. The structure of this string is the same as the Pnnnn structure (nnnn=infotype). The structure is filled with (valid) values only when the delete, change and create functions are used.
    Please read Create dynamic actions in the Implementation Guide.
    Regards
    Bernd

  • User exit or badi for this functionality

    hi to all experts ,
                          i need user exit or badi for implementing a customized check to ensure appropriate incoterms is being maintained in PO document . they are maintaining two different incoterms maintained for the same vendor depending on the plant.
    thanks in advance

    hi,
    please give the information about
    which transaction??
    which field??
    i think u need only validation, if check is not present u need to throw error or info mess, right..
    regards
    vijay

  • Exit of VF01 for field modification

    Dear All,
    I need to enable field for "Billed Quantity" in line item while doing VF01 so that user can change Quantity. what exit/enhancement will be used?. please help.
    Radsamm

    Hi Sasidhar,
    First of all I wrote my code in the user exit you told me but when I go to VF01 and try to cancel a document, this user exit doesn't work. I'm using the same code, i put a break point and it doesn't stop there...
    data l_kunnr like vbpa-kunnr.
    clear l_kunnr.
    select single kunnr
      from vbpa
        into l_kunnr
          where VBELN = vbak-vbeln
            and POSNR = '000000'
            and PARVW = 'RG'.
      SELECT SINGLE KLIMK
        INTO VBRK-ZKLIMK
          FROM KNKK
            WHERE KUNNR = l_kunnr.
      vbrk-zcarga = 'X'.
    Thanks,
    Maria

  • User Exit or Badi for VF02 Transaction

    Hi Friends,
    I need to do Billing Date validation while chnging the Billing Document. so can u plz provide me some on the user exit which will get triggered for VF02 tran.
    I checked with some of the exit like,
    V61A0001
    V60P0001
    V60A0001
    V05N0001
    V05I0001
    SDVFX011
    SDVFX010
    SDVFX009
    SDVFX008
    SDVFX007
    SDVFX006
    SDVFX005
    SDVFX004
    SDVFX003
    SDVFX002
    SDVFX001 but nothing seems to be triggering for me. Plz help me...

    Hi Please find the below list of userexits.
    Exit Name           Description (VF02)
    J_3RSINV            Export sales
    SDVFX007            User exit: Billing plan during transfer to Accounting
    SDVFX008            User exit: Processing of transfer structures SD-FI
    SDVFX009            Billing doc. processing KIDONO (payment reference number)
    SDVFX010            User exit item table for the customer lines
    SDVFX011            Userexit for the komkcv- and kompcv-structures
    V05I0001            User exits for billing index
    V05N0001            User Exits for Printing Billing Docs. using POR Procedure
    V60A0001            Customer functions in the billing document
    V60P0001            Data provision for additional fields for display in lists
    V61A0001            Customer enhancement: Pricing
    LV60A001            vf

  • Need a Exit or BADI  For Changing Validation Class  (PRUEFKL) during  EL28

    need to change the Validation Class Validation Class  (PRUEFKL)  or send it blank in order to remove all valdition during Meter read uplaod  , Can any one suggest a BADI or user exit or anything where in i can change the Validtion class before validation take place at the time of meter read uplaod .  As validtion class we do not pass in EL28 it usually get filled with 001 ans 002 . 
    Thanks in advance . 
    regards
    rajeev

    Thank for the response however my question was , can we change the Validation Class throght code  any exit or BADI  during el28  not  by config as config will be done for every thing as this we need to do only for a paticlular program .
    So in short i m looking for any enhancement point ( Exit /BADI ) which willl trigger during el28 and i will be able to send emply validation class in initial stage to avoide validation .
    Regards
    Rajeev
    Edited by: rajeevkohli on Aug 3, 2011 2:25 PM

  • User Exit or BADI for Delivery

    Hi,
    I do have a scenario:
    In the order If I do have 3 materials A. B and C for Example.
    If the Stock is not avaliable for materials for A and B, then while creating the deliveries, Delivery will consider materail C.
    Now I want to restrict this, in this sense if the stock is not avaliable for materails A and B the delivery should not be created.
    Could you please help to find out where I can get user exit or copy control or BADI to write the code.
    Thanks in Advance.
    Shravan G.

    hi Brad,
    Please help understand what is Delivery copy control.
    Regards,
    SuryaD.

Maybe you are looking for