User exit or BADI while billing doc is transferred to accounting.

Hello All,
I've searched SDN for an issue for which I could not find any psbl help.
While billing document is saved, according to the config of the billing type automatic posting to accounting happens and I need a user exit while/after this accounting doc is being created. I hv tried the following exits by inserting break-points but none of them work.
SDVFX001  User exit header line in delivery to accounting
SDVFX002  User exit for A/R line (transfer to accounting)
SDVFX003  User exit: Cash clearing (transfer to accounting)
SDVFX004  User exit: G/L line (transfer to accounting)
SDVFX005  User exit: Reserves (transfer to accounting)
SDVFX006  User exit: Tax line (transfer to accounting)
SDVFX007  User exit: Billing plan during transfer to Accounting
SDVFX008  User exit: Processing of transfer structures SD-FI
My purpose is to get some fields from the billing document and update them in the FI document item text.
Please help.
Thanks in advance.
Regards,
Amit

Hi,
In background is triggers this exit, pass your required text here to field "E_SGTXT" and it will appear in accounting item text.
Insert your text based on the billing transaction else it should not disturb the field, since this exit is used in all place where inventory triggers
use this user exit
MBCF0002 - Customer function exit: Segment text in material doc. item
hope this will help you. all the best

Similar Messages

  • User Exit or BADI while posting GRs.

    HI all,
    I am looking for a User Exit or BADI while posting Goods Receipts for Purchase Orders.
    I need to change the <b>POSTING DATE</b> on the receipt for certain document types.
    i found a user exit : MB_CF001, but this is not allowing me to change the posting date on the material document.
    Thanks for your help in advance.

    Hi Ravi,
                      This is ULitity program which takes Tcode or program name as a input and gives the BADI existing in the program. Please Allocate me the point if it is usefully to you
    REPORT ZBADI_CHECK .
    TABLES : TSTC,
    TADIR,
    MODSAPT,
    MODACT,
    TRDIR,
    TFDIR,
    ENLFDIR,
    SXS_ATTRT ,
    TSTCT.
    DATA : JTAB LIKE TADIR OCCURS 0 WITH HEADER LINE.
    DATA : FIELD1(30).
    DATA : V_DEVCLASS LIKE TADIR-DEVCLASS.
    PARAMETERS : P_TCODE LIKE TSTC-TCODE,
    P_PGMNA LIKE TSTC-PGMNA .
    DATA wa_tadir type tadir.
    START-OF-SELECTION.
    IF NOT P_TCODE IS INITIAL.
    SELECT SINGLE * FROM TSTC WHERE TCODE EQ P_TCODE.
    ELSEIF NOT P_PGMNA IS INITIAL.
    TSTC-PGMNA = P_PGMNA.
    ENDIF.
    IF SY-SUBRC EQ 0.
    SELECT SINGLE * FROM TADIR
    WHERE PGMID = 'R3TR'
    AND OBJECT = 'PROG'
    AND OBJ_NAME = TSTC-PGMNA.
    MOVE : TADIR-DEVCLASS TO V_DEVCLASS.
    IF SY-SUBRC NE 0.
    SELECT SINGLE * FROM TRDIR
    WHERE NAME = TSTC-PGMNA.
    IF TRDIR-SUBC EQ 'F'.
    SELECT SINGLE * FROM TFDIR
    WHERE PNAME = TSTC-PGMNA.
    SELECT SINGLE * FROM ENLFDIR
    WHERE FUNCNAME = TFDIR-FUNCNAME.
    SELECT SINGLE * FROM TADIR
    WHERE PGMID = 'R3TR'
    AND OBJECT = 'FUGR'
    AND OBJ_NAME EQ ENLFDIR-AREA.
    MOVE : TADIR-DEVCLASS TO V_DEVCLASS.
    ENDIF.
    ENDIF.
    SELECT * FROM TADIR INTO TABLE JTAB
    WHERE PGMID = 'R3TR'
    AND OBJECT in ('SMOD', 'SXSD')
    AND DEVCLASS = V_DEVCLASS.
    SELECT SINGLE * FROM TSTCT
    WHERE SPRSL EQ SY-LANGU
    AND TCODE EQ P_TCODE.
    FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
    WRITE:/(19) 'Transaction Code - ',
    20(20) P_TCODE,
    45(50) TSTCT-TTEXT.
    SKIP.
    IF NOT JTAB[] IS INITIAL.
    WRITE:/(105) SY-ULINE.
    FORMAT COLOR COL_HEADING INTENSIFIED ON.
    Sorting the internal Table
    sort jtab by OBJECT.
    data : wf_txt(60) type c,
    wf_smod type i ,
    wf_badi type i ,
    wf_object2(30) type C.
    clear : wf_smod, wf_badi , wf_object2.
    Get the total SMOD.
    LOOP AT JTAB into wa_tadir.
    at first.
    FORMAT COLOR COL_HEADING INTENSIFIED ON.
    WRITE:/1 SY-VLINE,
    2 'Enhancement/ Business Add-in',
    41 SY-VLINE ,
    42 'Description',
    105 SY-VLINE.
    WRITE:/(105) SY-ULINE.
    endat.
    clear wf_txt.
    at new object.
    if wa_tadir-object = 'SMOD'.
    wf_object2 = 'Enhancement' .
    elseif wa_tadir-object = 'SXSD'.
    wf_object2 = ' Business Add-in'.
    endif.
    FORMAT COLOR COL_GROUP INTENSIFIED ON.
    WRITE:/1 SY-VLINE,
    2 wf_object2,
    105 SY-VLINE.
    endat.
    case wa_tadir-object.
    when 'SMOD'.
    wf_smod = wf_smod + 1.
    SELECT SINGLE MODTEXT into wf_txt
    FROM MODSAPT
    WHERE SPRSL = SY-LANGU
    AND NAME = wa_tadir-OBJ_NAME.
    FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
    when 'SXSD'.
    For BADis
    wf_badi = wf_badi + 1 .
    select single TEXT into wf_txt
    from SXS_ATTRT
    where sprsl = sy-langu
    and EXIT_NAME = wa_tadir-OBJ_NAME.
    FORMAT COLOR COL_NORMAL INTENSIFIED ON.
    endcase.
    WRITE:/1 SY-VLINE,
    2 wa_tadir-OBJ_NAME hotspot on,
    41 SY-VLINE ,
    42 wf_txt,
    105 SY-VLINE.
    AT END OF object.
    write : /(105) sy-ULINE.
    ENDAT.
    ENDLOOP.
    WRITE:/(105) SY-ULINE.
    SKIP.
    FORMAT COLOR COL_TOTAL INTENSIFIED ON.
    WRITE:/ 'No.of Exits:' , wf_smod.
    WRITE:/ 'No.of BADis:' , wf_badi.
    ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(105) 'No userexits or BADis exist'.
    ENDIF.
    ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(105) 'Transaction does not exist'.
    ENDIF.
    AT LINE-SELECTION.
    data : wf_object type tadir-object.
    clear wf_object.
    GET CURSOR FIELD FIELD1.
    CHECK FIELD1(8) EQ 'WA_TADIR'.
    read table jtab with key obj_name = sy-lisel+1(20).
    move jtab-object to wf_object.
    case wf_object.
    when 'SMOD'.
    SET PARAMETER ID 'MON' FIELD SY-LISEL+1(10).
    CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
    when 'SXSD'.
    SET PARAMETER ID 'EXN' FIELD SY-LISEL+1(20).
    CALL TRANSACTION 'SE18' AND SKIP FIRST SCREEN.
    endcase.

  • User exit or BADI while saving purchase order

    Hello,
    I want to use an user exit or BADI while saving of purchase order. The objective is to check the material group of the line item while saving. We don´t want to allow to save purchase orders for one material group.
    Can you please guide me.
    Thanks
    Srinivasan

    Hi
    The Business Add-In (BAdI) ME_PROCESS_PO_CUST enables you to extend the business logic of the Enjoy purchase order on an individual basis.
    You can thus influence the dialog transactions ME21N, ME22N, ME23N, and ME29N, and the BAPIs BAPI_PO_CREATE1 and BAPI_PO_CHANGE.
    Typical applications for this BAdI include:
    Processing of own objects
    Processing of additional data on standard objects
    Implementation of additional checks and derivationsChange of data in standard fields
    Change in field selection
    you can use this BADI for checking the material group
    Thanks & Regards
    Kishore

  • Exit to prevent Billing doc to post to accounting for Condition type

    Hi all,
    I have a requirement as below :
    A Sales order Y is created refererring to another Sales Order say X. Sales order X has one condition type which in the process has been removed. When Sales order Y created all the data from X is copied including the condition type( Now one of the condition type is not present in the system which is also copied to the Order Y). Now, when I genreate Billing document and then post to accounting doc, even though the particular condition type that is copied from 'X' is not present in the system, it is getting posted.
    Can you please help me if there is any exit to prvent the Billing doc to post to accounting based on the condition type.
    Regards,
    Uma Chandra Sekhar

    Hi,
    Use the user exit "RV60AFZC", form-routine : USEREXIT_FILL_VBRK_VBRP.  Set the value of structure field VBRK-RFBSK to 'A' to block the creation of accounting document.
    Regards
    Vinod

  • User Exit or BADI in APO to change sales order relevant data while CIF

    Hi Everyone,
    I require User exit or BADI at APO side to change customer field kunnr of sales order after it enters APO through CIF.
    My requirement is to replace KUNNR field with KDGRP field of sales order.
    The data will pass through CIF in APO.
    Is there any user exit or BADI for the same?
    Sample code will be of great help.
    Regards,
    Kashyap.

    Hi ,
    Resolved myself.
    customer exit APOCF010
    Regards,
    Kashyap

  • 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

  • Suitable User-Exit or BAdi for transaction VF01

    Hi
    Is there any User-Exit or BAdi available for Transaction VF01, in which following fields are available.
    Invoice Number -> BELNR
    FI Doc. Type -> BLART
    Inv Date -> BLDAT
    Year -> GJAHR
    Thanks

    the following program are the user exit for billing.
    we often use RV60AFZC and RV60AFZZ.
    RV60AFZA
    RV60AFZB
    RV60AFZC
    RV60AFZD
    RV60AFZZ
    RV60BFZA
    For Sales order
    Pricing, item addtion deletion
    MV45AFZZ
    First, I did not find documentation for the BADI either. But at the first glance the process of implementing it looks quite straightforward. I assume you run R/3 Enterprise (4.7). So, you should implement BADI 'BADI_SD_SALES' - this must be done in transaction SE19. In particular for the purpose of adding some additional items into sales document I would implement method SAVE_DOCUMENT_PREPARE. This method has changing table parameter FXVBAP of type VA_VBAPVB_T - it holds all the sales document items. Just add items of yours to it. Certainly, you have to fill all the appropriate fields carefully.
    Hope this helps somehow.
    In that case you should use USEREXIT_DOCUMENT_SAVE_PREPARE subroutine (form). As far as I remember it has no parameters. To add items to the sales document you should modify internal table XVBAP.
    regards
    vinod

  • User exit or Badi for VF11

    Hi,
    Can anybody suggest me
    Any User-exit or Badi name for VF11 tcode (Billing cancellation)
    Moderator Message: Search before you post and ask your questions in the right forum.
    Edited by: kishan P on Feb 11, 2011 3:11 PM

    Hi
    Exit
    SDVFX001 User exit header line in delivery to accounting
    SDVFX002 User exit for A/R line in transfer to accounting
    SDVFX003 User exit cash clearing in transfer to accounting
    SDVFX004 User exit G/L line in transfer to accounting
    SDVFX005 User exit reserves in transfer to accounting
    SDVFX006 User exit tax line in transfer to accounting
    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
    J_3RSINV 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
    BADI
    BADI_SD_SALES_BASIC
    BADI_SD_TO_FM
    BADI_SD_BILLING
    Ranga

  • User Exit or Badi in Migo

    hi,
    While we post in transaction MIGO with movement type 101, the GR quantity(say 5.00)  gets multiplied with the condition type value(say GAU2 -- 4.00). this total value(say 20.00) is displayed in the amount column of the FI document created.
    Now my reuirement is to not only multiply (5.00 * 4.00) but also with the specification value set by quality(say 2%) so now amount would be ( ( 5.00 * 4.00) * (2/100) ).
    So this needs to be done before the FI document is created.
    Is this possible through any user exit or badi.
    Plz help.

    exits related to MIGO tcode
    MBCF0002  Customer function exit: Segment text in material doc. i
    MBCF0005  Material document item for goods receipt/issue slip
    MBCF0006  Customer function for WBS element
    MBCF0007  Customer function exit: Updating a reservation
    MBCF0009  Filling the storage location field
    MBCF0010  Customer exit: Create reservation BAPI_RESERVATION_CREA
    MBCF0011  Read From RESB and RKPF For Print List in  MB26
    MBCFC003  Maintenance of batch master data for goods movements
    MBCFC004  Maintenance of batch specifications for goods movements

  • SD: Exits or BADIs for Billing

    Tcode VF01
    I am creating a billing document. When the user presses save button i want to:
    1) Check my Z table (which conatins the invoicing limit for the user currently creating bill)
    2) If the condition fails i want to issue a E type message so that creation of billing can be stopped.
    Which user exit or BAdi can be used.
    Regards
    Anik

    These are the Exits Available for Package VF
    J_3RSINV
    SDVFX001  User exit header line in delivery to accounting
    SDVFX002  User exit for A/R line in transfer to accounting
    SDVFX003  User exit cash clearing in transfer to accounting
    SDVFX004  User exit G/L line in transfer to accounting
    SDVFX005  User exit reserves in transfer to accounting
    SDVFX006  User exit tax line in transfer to accounting
    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 numbe
    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 Procedu
    V60A0001  Customer functions in the billing document
    V60P0001  Data provision for additional fields for display in lis
    V61A0001  Customer enhancement: Pricing
    Similarly
    The Badi Availabel for VF package
    SD_CIN_LV60AU02                                               BADI for billing
    VOR_WA_FAKTURA                                                Billing before Goods Issue
    Award Points if Useful.
    Regards,
    Mithun

  • User-Exit or BADI for MB51

    Dear all,
    In MB51 report, sale order value is not showing values even though it actually has.
    What could be the reason?
    If the answer is User-exits or BADI, can u suggest me the correct user-exit or BADI.
    I have already tried the following user-exits by placing BREAK-POINT in the includes. But no where the execution is breaking.
    MBCF0002            Customer function exit: Segment text in material doc. ite
    MBCF0005            Material document item for goods receipt/issue slip
    MBCF0006            Customer function for WBS element
    MBCF0007            Customer function exit: Updating a reservation
    MBCF0009            Filling the storage location field
    MBCF0010            Customer exit: Create reservation BAPI_RESERVATION_CREATE
    MBCF0011            Read from RESB and RKPF for print list in  MB26
    MB_CF001            Customer Function Exit in the Case of Updating a Mat. Doc
    Plz give some suggestions.
    Regards,
    Prem

    Hi ,
    U need to change the layout of MB51 in order to get the SO no.
    goto MB51---> give some inputs ---> in the o/p screen ->click on the variant button-> on the pop screen u, top of it u will get 2 options
    1.Header
    2.Position
    click Position Button ---> here u will get all Fields avail. for this Report O/P , so u can add SO field and save the variant.
    regards
    Prabhu

  • 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 COR1/COR2

    Dear Experts,
    Can you please tell me if we have any user-exit or BADI for chaning the value of the technical completion date field
    i.e. AUFK-IDAT2 while saving the Process Order in COR1 or COR2?
    Thanks,
    Praveen

    Hi Praveen,
    Implement the customer exit EXIT_SAPLCOKO_006 in enhancement
    PPCO0020  Process order: Display/change order header data
    This is only importing one field I_AUFNR.
    but try the logic below.
    data: lv_fnam type char16 value '(SAPLCOKO)caufvd'.
    field-symbols : <fs_caufvd> type caufvd.
    your checks for changing the field IDAT2 (Technical completion date).
    Try to change <fs_caufvd>-IDAT2 field value.
    Regards,
    Dwarakanath.S

  • User Exit Or Badi for Framework Release PO

    Anyone could tell me about any user exit or BADI for storing the calculated value in Frameork order.
    Since it is storing the GNETW in CEKKO and that is used in releasing procedure.
    First of all i want to calculate the total price according to srat date and end date and then only for framework order put that value in CEKKO-KTWRT field.
    Please Help and suggest some thing about this.
    Thanks & Regards,
    Nitin Malhotra

    Hi,
    Check the following PDF .
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9cd334f3-0a01-0010-d884-f56120039915
    May be useful to you.
    Regards
    Sachin

  • User Exit or BADI for Blocking process orders from R/3 to APO?

    Dear Experts,
    I am looking for a user exit or badi to block the process orders from R/3 to APO. As per standard it is not transferring orders which are clsd(closed status). Means that it is not updating live cache but its reading from R3.
    We are facing some problems in cif queues which are not correctly maintained in R3 side. We dont want to touch those orders bcoz its very old data which is not required for planning.
    There will be huge data which needs to be deleted while transferring through cif.
    Please give any user exit (outbound intial transfer) from R/3.
    Or any sugg. I apprecite your inputs...
    Thanks
    Cris

    Hi Cris,
    You can use user exit APOCF004 - Inbound Processing: Production Order/Planned Order in APO to prevent orders coming to APO by deleting orders which are not intended to goto APO from internal tables IT_ORD and IT_OUT.
    Hope this helps.
    Best Regards,
    Ramesh M

Maybe you are looking for