BAdi after the commit of BP

Hi ,
Is there any BAdi whcih gets trigered after the commit has happend during the save of the BP.
R.

BUS7 is the t-code for the events in BP after updateing the data u will get events to trigger.
Create a new function module and attach at the corresponding event it will trigger after save also.
Please Allot points if it helps.
Regards,
Shiv

Similar Messages

  • Take 2 digits after the comma of a number of type float

    Hello everybody,
    I want to take 2 digits after the comma of a number of type 'float'.
    For example I want to get 3,57 instead of  3.5714285714285716E+00
    Thanks & Regards

    Hello,
    Are you getting the value
    3.5714285714285716E+00
    from the program into some variable ??
    If thats the case you can declare the variable as
    DATA: var TYPE p DECIMALS 2
    BR,
    Suhas

  • Limit Data Entry to 2 Digits after the Comma

    Hi
    I've an Form with Matrix and EditText Columns.
    The columns are bound to Userdatasources.
    When changing the type of the userdatasources i'm able to limit the displayed digits to 2 places after the comma. But it's only  a visual representation as it seems because i'm still able to enter more than 2 digits after the comma.
    Any suggestions?
    Thanks

    It's getting even worse. When entering more than 4 digits after the comma Business One crashes hardly (UI Server - Message)
    I'm using an Userform as described before with 2004 PL34
    Will try to reproduce it with an minimalistic sample but maybe somebody has an idea.
    No one?

  • User exit/BADI AFTER the database commit in va01 va02

    Hi All
    I need an user exit/BADI <b>AFTER the database tables are updated</b> when save button is pressed on VA01/VA02, both these user exits are fired before that.
    Regards
    Badari

    Check out all these exits
                                                                                    SDTRM001            Reschedule schedule lines without a new ATP check            
    V45A0001            Determine alternative materials for product selection        
    V45A0002            Predefine sold-to party in sales document                    
    V45A0003            Collector for customer function modulpool MV45A              
    V45A0004            Copy packing proposal                                        
    V45E0001            Update the purchase order from the sales order               
    V45E0002            Data transfer in procurement elements (PRreq., assembly)     
    V45L0001            SD component supplier processing (customer enhancements)     
    V45P0001            SD customer function for cross-company code sales            
    V45S0001            Update sales document from configuration                     
    V45S0003            MRP-relevance for incomplete configuration                   
    V45S0004            Effectivity type in sales order                              
    V45W0001            SD Service Management: Forward Contract Data to Item         
    V46H0001            SD Customer functions for resource-related billing           
    V60F0001            SD Billing plan (customer enhancement) diff. to billing plan 
    SDAPO001            Activating Sourcing Subitem Quantity Propagation

  • User Exit/BADI after database commit in VA01/VA02

    Hi All,
    Can you tell me an user exit/BADI in VA01/VA02 which I can utilize AFTER the database commit but still utilize the tables/structures like xvbap, xvbkd etc? Thanks.
    Best Regards,
    Avimanyu

    Hi Sengupta,
    Usually there are no user-exits after COMMIT.
    What you need to do is register a call which will be executed after COMMIT, from one of the available user-exits.
    To do this, SAP provides 2 methods:
    1. PERFORM xxx ON COMMIT
    2. Function Module with attribute "Update Module"
    Check ABAP keyword help for more information for PERFORM xxx ON COMMIT.
    <a href="http://help.sap.com/saphelp_46c/helpdata/en/34/8e72cc6df74873e10000009b38f9b8/frameset.htm">http://help.sap.com/saphelp_46c/helpdata/en/34/8e72cc6df74873e10000009b38f9b8/frameset.htm</a>
    Hope this helps.
    Regards,
    Sumant.
    PS: Reward points if this is helpful.

  • Comment after the commit statement.

    Hi Everyone,
    Please do have a look at this.
    Commenting on COMMIT: Example The following statement commits the current transaction and associates a comment with it:
    COMMIT COMMENT 'In-doubt transaction Code 36, Call (415) 555-2637';
    Now where can I see that comment? What is the data dictionary, which will have this detail?
    Regards,
    BS2012.

    If you look into the document for the COMMIT statement you will see this.
    COMMENT Clause
    Specify a comment to be associated with the current transaction. The 'text' is a quoted literal of up to 255 bytes that Oracle Database stores in the data dictionary view DBA_2PC_PENDING along with the transaction ID if a distributed transaction becomes in doubt. This comment can help you diagnose the failure of a distributed transaction.

  • Missing BAdI after the changes to InfoSpoke in BI 7.0

    Hi Gurus,
    Recently our BW system was upgraded from BW 3.5 to BI 7.0. And it was a Technical Upgrade.
    And now we are trying to change one InfoSpoke Selection which has a BAdI defined in the Transformations Tab.
    We didnt touch anything on the BAdI it was just the selection change in the Selection tab.
    Aftre activating the InfoSpoke when we come back to Tranformation Tab we dont see the Traget Structure and BAdi Implementation name any more.
    But when the InfoSpoke was executed, we can see the Transformations step in the monitor screen.
    That means even though the BAdI name was not visible in the InfoSpoke definition, transformations was being performed in the
    extraction.
    But this is not true when  the changes(InfoSpoke) were migrated to Quality system.
    There BAdI and Target Structure are not visible in the InfoSpoke and no transformation step is being executed in the Extraction.
    But both BAdI and Target Structure objects are active in the repository. Only link between the InfoSPoke and BAdI is missing.
    This is happening to all the InfoSpokes which are being changed.And this didnt happen before upgrade to BI 7.0.
    Can any body share some inputs on how to solve this issue..
    Thanks in advance....
    Regards,
    Padma.

    Hi,
    May be the following will help you!
    Regards,
    Subha
    API: RSB_API_OHS_SPOKE_GETDETAIL
    This API identifies the InfoSpoke details.
    Parameters:
    Parameter
    Type
    Description
    Import
    INFOSPOKE
    RSINFOSPOKE
    Name of the InfoSpoke
    Export
    RFCOHDEST
    RSOHDEST
    Name of the open hub destination
    RFCUPDATEMETHOD
    RSBUPDMODE
    Extraction Mode for the InfoSpoke
    RFCPROCESSCHAIN
    RSPC_CHAIN
    Process chain
    RFCOHSOURCE
    RSOHSOURCE
    Open hub data source
    RFCTLOGOSRC
    RSTLOGOSRC
    TLOGO type of data source
    RFCMAXPACKSIZE
    RSIDOCSIZE
    Maximum number of records per package
    RETURN
    BAPIRET2
    Tables
    T_MESSAGES
    BAPIRETTAB
    Messages

  • Not able to use Commit after the function module STATUS_OBJECT_CREATE

    I am using function module   STATUS_OBJECT_CREATE
       CALL FUNCTION 'STATUS_OBJECT_CREATE'
              EXPORTING
               CHGKZ         = 'X'
               CLIENT        = SY-MANDT
                OBJNR         = LV_OBJNR3
                OBTYP         = 'IWE'
                STSMA         = 'ZS_RE_01'
              IMPORTING
                OBJNR         = LV_OBJNR3.
                STONR                        = LV_STONR.
            IF SY-SUBRC = 0.
                COMMIT WORK.
            ENDIF.
    i am getting error after the COMMIT WORK .
    I am not getting any issue in the function module .after the function module i am using the COMMIT WORK and i am getting the following error message
    Category               ABAP Programming Error
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Except.                CX_SY_OPEN_SQL_DB
    ABAP Program           SAPLBSVU
    Application Component  CA-GTF-TS-SMT
    Date and Time          03/17/2014 07:01:29
    |Short text                                                                                        |
    |    The ABAP/4 Open SQL array insert results in duplicate database records.                       |
    |What happened?                                                                                    |
    |    Error in the ABAP Application Program                                                         |
    |                                                                                                  |
    |    The current ABAP program "SAPLBSVU" had to be terminated because it has                       |
    |    come across a statement that unfortunately cannot be executed.                                |
    |What can you do?                                                                                  |
    |    Note down which actions and inputs caused the error.                                          |
    |                                                                                                  |
    |                                                                                                  |
    |    To process the problem further, contact you SAP system                                        |
    |    administrator.                                                                                |
    |                                                                                                  |
    |    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |
    |    at and manage termination messages, and you can also                                          |
    |    keep them for a long time.                                                                    |
    |Error analysis                                                                                    |
    |    An exception occurred that is explained in detail below.                                      |
    |    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught                 |
    |     in                                                                                           |
    |    procedure "STATUS_UPDATE" "(FUNCTION)", nor was it propagated by a RAISING                    |
    |     clause.                                                                                      |
    |    Since the caller of the procedure could not have anticipated that the                         |
    |    exception would occur, the current program is terminated.                                     |
    |    The reason for the exception is:                                                              |
    |    If you use an ABAP/4 Open SQL array insert to insert a record in                              |
    |    the database and that record already exists with the same key,                                |
    |    this results in a termination.                                                                |
    |                                                                                                  |
    |    (With an ABAP/4 Open SQL single record insert in the same error                               |
    |    situation, processing does not terminate, but SY-SUBRC is set to 4.)                          |
    |How to correct the error                                                                          |
    |    Use an ABAP/4 Open SQL array insert only if you are sure that none of                         |
    |    the records passed already exists in the database.                                            |
    |                                                                                                  |
    |    If the error occures in a non-modified SAP program, you may be able to                        |
    |    find an interim solution in an SAP Note.                                                      |
    |    If you have access to SAP Notes, carry out a search with the following                        |
    |    keywords:                                                                                     |
    |                                                                                                  |
    |    "SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"                                              |
    |    "SAPLBSVU" or "LBSVUU01"                                                                      |
    |    "STATUS_UPDATE"                                                                               |
    |                                                                                                  |
    |    If you cannot solve the problem yourself and want to send an error                            |
    |    notification to SAP, include the following information:                                       |
    |                                                                                                  |
    |    1. The description of the current problem (short dump)                                        |
    |                                                                                                  |
    |       To save the description, choose "System->List->Save->Local File                            |
    |    (Unconverted)".                                                                               |
    |                                                                                                  |
    |    2. Corresponding system log                                                                   |
    |                                                                                                  |
    |       Display the system log by calling transaction SM21.                                        |
    |       Restrict the time interval to 10 minutes before and five minutes                           |
    |    after the short dump. Then choose "System->List->Save->Local File                             |
    |    (Unconverted)".                                                                               |
    |                                                                                                  |
    |    3. If the problem occurs in a problem of your own or a modified SAP                           |
    |    program: The source code of the program                                                       |
    |       In the editor, choose "Utilities->More                                                     |
    |    Utilities->Upload/Download->Download".                                                        |
    |                                                                                                  |
    |    4. Details about the conditions under which the error occurred or which                       |
    |    actions and input led to the error.                                                           |
    |                                                                                                  |
    |    The exception must either be prevented, caught within proedure                                |
    |    "STATUS_UPDATE" "(FUNCTION)", or its possible occurrence must be declared in                  |
    |     the                                                                                          |
    |    RAISING clause of the procedure.                                                              |
    |    To prevent the exception, note the following:                                                 |
    |System environment                                                                                |
    |    SAP Release..... 702                                                                          |
    |    SAP Basis Level. 0010                                                                         |
    |                                                                                                  |
    |    Application server... "sds6ci"                                                                |
    |    Network address...... "11.224.101.53"                                                         |
    |    Operating system..... "Linux"                                                                 |
    |    Release.............. "2.6.18-194.el5"                                                        |
    |    Hardware type........ "x86_64"                                                                |
    |    Character length.... 16 Bits                                                                  |
    |    Pointer length....... 64 Bits                                                                 |
    |    Work process number.. 17                                                                      |
    |    Shortdump setting.... "full"                                                                  |
    |                                                                                                  |
    |    Database server... "gctsdb01lds.hsi.hugh"                                                     |
    |    Database type..... "ORACLE"                                                                   |
    |    Database name..... "DS6"                                                                      |
    |    Database user ID.. "SAPDS4"                                                                   |
    |                                                                                                  |
    |    Terminal.......... "GCTEMP02VDI"                                                              |
    |                                                                                                  |
    |    Char.set.... "C"                                                                              |
    |                                                                                                  |
    |    SAP kernel....... 720                                                                         |
    |    created (date)... "Sep 14 2013 05:28:14"                                                      |
    |    create on........ "Linux GNU SLES-9 x86_64 cc4.1.2 use-pr130820"                              |
    |    Database version. "OCI_102, 10.2.0.5.0, V2, default"                                          |
    |                                                                                                  |
    |    Patch level. 500                                                                              |
    |    Patch text.. " "                                                                              |
    |                                                                                                  |
    |    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"               |
    |    SAP database version. 720                                                                     |
    |    Operating system..... "Linux 2.6, Linux 3"                                                    |
    |                                                                                                  |
    |    Memory consumption                                                                            |
    |    Roll.... 1317248                                                                              |
    |    EM...... 0                                                                                    |
    |    Heap.... 0                                                                                    |
    |    Page.... 0                                                                                    |
    |    MM Used. 1242912                                                                              |
    |    MM Free. 53400                                                                                |
    |User and Transaction                                                                              |
    |    Client.............. 160                                                                      |
    |    User................ "DV018458"                                                               |
    |    Language key........ "E"                                                                      |
    |    Transaction......... "SE38 "                                                                  |
    |    Transaction ID...... "5323C30FC9364665E10000000BE06533"                                       |
    |                                                                                                  |
    |    EPP Whole Context ID.... "002655EE0F241ED3ABB7D81260A28C44"                                   |
    |    EPP Connection ID....... 00000000000000000000000000000000                                     |
    |    EPP Caller Counter...... 0                                                                    |
    |                                                                                                  |
    |    Program............. "SAPLBSVU"                                                               |
    |    Screen.............. "RSM13000 3000"                                                          |
    |    Screen Line......... 2                                                                        |
    |    Debugger Active..... "none"                                                                   |
    |Information on where terminated                                                                   |
    |    Termination occurred in the ABAP program "SAPLBSVU" - in "STATUS_UPDATE".                     |
    |    The main program was "RSM13000 ".                                                             |
    |                                                                                                  |
    |    In the source code you have the termination point in line 60                                  |
    |    of the (Include) program "LBSVUU01".                                                          |
    |    The program "SAPLBSVU" was started in the update system.                                      |
    |    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in                   |
    |    procedure "STATUS_UPDATE" "(FUNCTION)", but it was neither handled locally nor                |
    |     declared                                                                                     |
    |    in the RAISING clause of its signature.                                                       |
    |                                                                                                  |
    |    The procedure is in program "SAPLBSVU "; its source code begins in line                       |
    |    1 of the (Include program "LBSVUU01 ".                                                        |
    |Source Code Extract                                                                               |
    |Line |SourceCde                                                                                   |
    |   30|  LOOP AT jsto_upd WHERE chgkz = 'X'.                                                       |
    |   31|    CHECK: jsto_upd-chgnr > '000',                                                          |
    |   32|           jsto_upd-stsma NE jsto_upd-stsma_old.                                            |
    |   33|    CLEAR jcdo_tab.                                                                         |
    |   34|    MOVE-CORRESPONDING jsto_upd TO jcdo_tab.                                                |
    |   35|    MOVE-CORRESPONDING chdat    TO jcdo_tab.                                                |
    |   36|    jcdo_tab-stsma_new = jsto_upd-stsma.                                                    |
    |   37|    APPEND jcdo_tab.                                                                        |
    |   38|  ENDLOOP.                                                                                  |
    |   39|* Änderungen zu Einzelstatus (Insert)                                                       |
    |   40|  LOOP AT jest_ins WHERE chgkz = 'X'.                                                       |
    |   41|    CHECK jest_ins-chgnr > '000'.                                                           |
    |   42|    CLEAR jcds_tab.                                                                         |
    |   43|    MOVE-CORRESPONDING jest_ins TO jcds_tab.                                                |
    |   44|    MOVE-CORRESPONDING chdat    TO jcds_tab.                                                |
    |   45|    jcds_tab-chind = 'I'.                                                                   |
    |   46|    APPEND jcds_tab.                                                                        |
    |   47|  ENDLOOP.                                                                                  |
    |   48|* Änderungen zu Einzelstatus (Update)                                                       |
    |   49|  LOOP AT jest_upd WHERE chgkz = 'X'.                                                       |
    |   50|    CHECK jest_upd-chgnr > '000'.                                                           |
    |   51|    CLEAR jcds_tab.                                                                         |
    |   52|    MOVE-CORRESPONDING jest_upd TO jcds_tab.                                                |
    |   53|    MOVE-CORRESPONDING chdat    TO jcds_tab.                                                |
    |   54|    jcds_tab-chind = 'U'.                                                                   |
    |   55|    APPEND jcds_tab.                                                                        |
    |   56|  ENDLOOP.                                                                                  |
    |   57|* Verbuchung Statusobjekte                                                                  |
    |   58|  DESCRIBE TABLE jsto_ins LINES sy-tabix.                                                   |
    |   59|  IF sy-tabix > 0.                                                                          |
    |>>>>>|    INSERT jsto CLIENT SPECIFIED                                                            |
    |   61|                FROM TABLE jsto_ins.                                                        |
    |   62|  ENDIF.                                                                                    |
    |   63|  DESCRIBE TABLE jsto_upd LINES sy-tabix.                                                   |
    |   64|  IF sy-tabix > 0.                                                                          |
    |   65|    field-symbols <fs_jsto_line> like jsto_upd.                                             |
    |   66|    loop at jsto_upd assigning <fs_jsto_line>.                                              |
    |   67|      IF <fs_jsto_line>-chgnr = '000'.                                                      |
    |   68|        <fs_jsto_line>-chgnr = '999'.                                                       |
    |   69|      ENDIF.                                                                                |
    |   70|* on change of status profile delete user status related to old profile                     |
    |   71|      IF <fs_jsto_line>-STSMA NE <fs_jsto_line>-STSMA_OLD.                                  |
    |   72|        DELETE FROM JEST CLIENT SPECIFIED WHERE                                             |
    |   73|               MANDT = <fs_jsto_line>-MANDT AND                                             |
    |   74|               OBJNR = <fs_jsto_line>-OBJNR AND                                             |
    |   75|               STAT  LIKE 'E%'.                                                             |
    |   76|        DELETE FROM JCDS CLIENT SPECIFIED WHERE                                             |
    |   77|               MANDT = <fs_jsto_line>-MANDT AND                                             |
    |   78|               OBJNR = <fs_jsto_line>-OBJNR AND                                             |
    |   79|               STAT  LIKE 'E%'.                                                             |

    i tried with out using commmit but it is not creating Status.
    When i see the function module help and they are trying to COMMIT
    FU STATUS_OBJECT_CREATE
    Short Text
    Create Status Object
    Functionality
    The function module generates a status object.
    Take the object number from the object number management (function modules OBJECT_NUMNBER_GET_xx).
    If no object number is given, the module takes a temporary object number that must be replaced later (function module STATUS_OBJECT_SWITCH_NUMBER).
    Example
    Creating an internal order with number 100123 (object type "ORC") for status profile "STATSCHEM" with final object number
    call function 'OBJECT_NUMBER_GET_OR'
      exporting
        aufnr = '100123'
      importing objnr = objektnummer.
    call function 'STATUS_OBJECT_CREATE'
      exporting
        objnr = objektnummer
        obtyp = 'ORC'
        stsma = 'STATSCHEM'.
    commit work.
    Creating the same order with a temporary object number
    data: objectkey like ionra.
    * TBO00-REFSTRUCT for object type 'OR' is 'IONRA'
    objectkey-aufnr = '100123'.
    call function 'STATUS_OBJECT_CREATE'
      exporting
        i_objectkey = objectkey
        obtyp       = 'ORC'
        stsma       = 'STATSCHEM'.
      importing
        objnr       = objektnummer.
    call function 'OBJECT_NUMBER_GET_OR'
      exporting
        aufnr = '100123'
      importing objnr = objektnummer_neu.
    call function 'STATUS_OBJECT_SWITCH_NUMBER'
      exporting
        objnr_old = objektnummer
        objnr_new = objektnummer_neu.
    commit work.
    Notes

  • MIGO BAdI or User-Exit - After Database Commit

    Hello,
    I'm looking for a BAdI or user-exit after database commit for MIGO posting. I want to create a FI document after MIGO posting.
    I already tried MB_MIGO_BADI BAdI but system gives a short dump. So I have to find a exit or BAdI after database commit.
    Thanks for helping in advance.
    Regards,
    Burak

    Hello,
    This issue solved.
    I used MB_DOCUMENT_BADI / MB_DOCUMENT_UPDATE and it solved my problem.
    FYI.
    Regards,
    Burak

  • Badi AFTER BP create/update

    Hello All,
    Does anyone know of a badi that is triggered AFTER a BP create or change in CRM 2007?  Both PARTNER_UPDATE and BUPA_FURTHER_CHECKS fire before BP create/change.  We are attempting a delta export of changed/created BPs for export to an external system.  So if you know of a programmatic or configuration way to trigger this, it would be greatly appreciated.
    Thank you,
    Derek Winters

    Hi again,
    In case anyone is interested...
    I actually didn't need a BAdI that interacts after the BP has been created/saved - or in other words, that interacts after the COMMIT. All I needed is a function module which I can call in update task and that did the trick.
    So I did use the PARTNER_UPDATE BAdI. I'm calling there my update-function-module which creates a partner function => I'm using BAPI BAPI_BUPA_PFCT_ADDFUNCTION.
    So this is how I've done it in the IF_EX_PARTNER_UPDATE~CHANGE_BEFORE_UPDATE method:
      data: lt_but050_old           type standard table of but050,
            ls_but050_old           type                   but050,
            lt_but050_new           type standard table of but050,
            ls_but050_new           type                   but050,
            ls_rel                  type                   but050,
            ls_rel_old              type                   but050.
    * get relationships ****************************************************
      call function 'BUPA_BUT050_CALLBACK'
        tables
          et_but050_old = lt_but050_old
          et_but050_new = lt_but050_new.
    * try to get relationship "Responsible Employee"... ********************
      read table lt_but050_old into ls_rel_old
           with key reltyp = 'BUR011'. " Responsible Employee
      read table lt_but050_new into ls_rel
           with key reltyp = 'BUR011'. " Responsible Employee
      if ls_rel_old-partner2 ne ls_rel-partner2
        and ls_rel-partner2 is not initial.
    *   ...add partner function "Sales Representative" *********************
        call function 'Z_CRM_BP_FRG0081_SAVE' in update task
          exporting
            iv_partner1      = ls_rel-partner1
            iv_partner2      = ls_rel-partner2
            iv_partner_fct   = '00000012' " Sales Representative
            iv_relnr         = ls_rel-relnr
          exceptions
            invalid_partner1 = 1
            invalid_partner2 = 2
            others           = 3.
      endif.
    Best regards,
    Melanie

  • Remove spaces after a comma

    Hi,
    I have a string that goes like this "abc, abc def, abcd,abc"
    How do I specify that I want to remove only the space (if there is 1) after the comma and not the one in between "abc def"?
    Thanks....

    Try this:
    String s = "abc,   abc def,    abcd,abc";
    // The following method replaces all comma's with one
    // or more spaces, with a single comma.
    s = s.replaceAll(", +", ",");Good luck.

  • User after the save of customer Master

    Hi,
    I am working on the SAP 4.6C.
    I am creating the customers in the XD01.
    I would like to trigger an exit after the save of the customer Doc to create hierarchy.
    This is required as the FM to create the hierarchy needs the customer number.
    Could any one pls let me know the exit to do this?
    Thanks.
    Murgh.

    Thanks for the mail.
    ZXF04U01 is the include where i am trying to create the hierarchy.This is the one which triggers after the save.
    I need to triger hierarchy FM after the commit work has happend.
    How can i call the FM which can triger after the commit work is done.
    Pls advise.

  • BADI after Final Approval in SC

    Hi Guys,
    Please let me know whether there is any BADI after the finl approval step completed in the Shopping cart.. Or I have to use the workflow events to handle???
    regards,
    Prabhu.

    Here are some Badis that will be triggered after approval
    BBP_CREATE_BE_PO_NEW
    BBP_CREATE_BE_RQ_NEW
    BBP_TARGET_OBJTYPE
    BBP_DETERMINE_LOGSYS
    BBP_EXTLOCALPO_BADI
    BBP_SRC_DETERMINE
    Regards,
    Jagadish

  • Is there a BADI after BBP_CREATE_BE_PO_NEW?

    Hello All,
    I would like to some addtional things after the PO is created in the back--end? Is there a BADI that will allow me to do addtional processing?
    Regards, Dean.
    BTW: SRM 5.0 Server 5.5

    Hi Dean,
    There should normally be the following badi after the PO is transferred to the backend :
    BBP_DOC_SAVE_BADI
    Of course the badi must be implemented for object type BUS2201 and activated.
    Best regards,
    Laurent.

  • BADI USER/EXIT for inserting cust. data after the Pruch. Requsitio is SAVED

    Hi all,
    Is there any  BADI or USER EXIT available for the transaction ME51N to save
    some customer data fields in a separta Z table , after the data is saved from the
    Purcahse requistion .
    I  have used the customer exit MEREQ001 for additing the customer filelds with TABLE CONTROL.
    I am not able to save the data from the table control . Any suggestion on this will be apprecitated  .
    Best Regards

    Hi,
      You have  to use 'EXIT_SAPLMEREQ_003' to import data from screen to your tables and use 'EXIT_SAPLMEREQ_001' to send data to screen.use the below code like below:
    EXIT_SAPLMEREQ_001:
    tables : ci_ebandb.
    data : i_mereq_item type mereq_item.
    if im_req_item is initial.
    clear: ci_ebandb.
    else.
    i_mereq_item = im_req_item->get_data( ).
    move-corresponding i_mereq_item to ci_ebandb.
    endif.
    EXIT_SAPLMEREQ_003
    data : i_mereq_item type mereq_item.
    if not im_req_item is initial.
    i_mereq_item = im_req_item->get_data( ).
    move-corresponding ci_ebandb to i_mereq_item .
    call method im_req_item->set_data( i_mereq_item ).
    endif.
    Also set the flag EX_CHANGED = 'X' to transafer the changes to database
    Regards,
    Himanshu

Maybe you are looking for

  • Sun studio 12 installation problem on RHEL5 x86_64

    Whenever I try to execute the batch installer for sun studio 12 I get the following error message: ./batch_installer --accept-sla Exception in thread "Thread-1" java.awt.HeadlessException at java.awt.dnd.DropTarget.<init>(libgcj.so.7rh) at java.awt.d

  • [Acrobat 8.x] PDF Printer not working

    Hi there, I just migrated from Windows XP SP3 to Windows 7. After having installed Acrobat (as part of CS3), I quickly came across the following nasty problem. The PDF Printer worked about once. After that, it became defunct. When starting a print jo

  • Idoc Type ORDERS04  Mapping field for VBAK-LANDTX

    Hi Experts, Can anyone guide me how to find an IDOC field in Idoc Type ORDERS04 related to the field VBAK-LANDTX (Country of departure) in Sales order Header? Thanks in advance. Christina

  • Recent Crash :(

    my macbook just crashed heres the crash log, can some mac guru help me out? Process: DirectoryService [31] Path: /usr/sbin/DirectoryService Identifier: DirectoryService Version: ??? (???) Code Type: X86 (Native) Parent Process: launchd [1] Date/Time:

  • ITunes dont want to synch apps in 3GS

    Two days ago, when performing a synch between iTunes and my 3GS iPhone, I noticed that the apps are in gray and it doesnt allow me to make any changes.  Why is this? How can I synch apps from my Mac to my 3GS ?