Business Transaction event keys.

Hi,
Other than GBB, what are all the other business event keys ( eg. PRD, KON ) for which account modifier is possible. and what is the functionality behind this.
Regards,
RitiG

Hi Ritigo
Offsetting entry for stock posting (GBB)
Offsetting entries for stock postings are used in Inventory Management. They are dependent on the account grouping to which each movement type is assigned. The following account groupings are defined in the standard system:
AUA: for order settlement
AUF: for goods receipts for orders (without account assignment)
and for order settlement if AUA is not maintained
AUI: Subsequent adjustment of actual price from cost center directly
to material (with account assignment)
BSA: for initial entry of stock balances
INV: for expenditure/income from inventory differences
VAX: for goods issues for sales orders without
account assignment object (the account is not a cost element)
VAY: for goods issues for sales orders with
account assignment object (account is a cost element)
VBO: for consumption from stock of material provided to vendor
VBR: for internal goods issues (for example, for cost center)
VKA: for sales order account assignment
(for example, for individual purchase order)
VKP: for project account assignment (for example, for individual PO)
VNG: for scrapping/destruction
VQP: for sample withdrawals without account assignment
VQY: for sample withdrawals with account assignment
ZOB: for goods receipts without purchase orders (mvt type 501)
ZOF: for goods receipts without production orders
(mvt types 521 and 531)
You can also define your own account groupings. If you intend to post goods issues for cost centers (mvt type 201) and goods issues for orders (mvt type 261) to separate consumption accounts, you can assign the account grouping ZZZ to movement type 201 and account grouping YYY to movement type 261.
Other than GBB there many other transaction event keys:
you can go to Tcode OBYC and see there...for eg.purpose i'll tell u the imp. one
Agency business: income (AG1)
This transaction can be used in agency business for income deriving from commission (e.g. del credere commission). The account key is used in the calculation schemas for agency business to determine the associated revenue accounts.
Agency business: turnover (AG2)
This transaction can be used in agency business if turnover (business volume) postings are activated in Customizing for the payment types. The account key is specified in Customizing for the billing type.
Agency business: expense (AG3)
This transaction can be used in agency business for commission expenses. The account key is used in the calculation schemas for agency business to determine the associated expense accounts.
Expense/revenue from consumption of consignment material (AKO)
This transaction is used in Inventory Management in the case of withdrawals from consignment stock or when consignment stock is transferred to own stock if the material is subject to standard price control and the consignment price differs from the standard price.
Expenditure/income from transfer posting (AUM)
This transaction is used for transfer postings from one material to another if the complete value of the issuing material cannot be posted to the value of the receiving material. This applies both to materials with standard price control and to materials with moving average price control. Price differences can arise for materials with moving average price if stock levels are negative and the stock value becomes unrealistic as a result of the posting. Transaction AUM can be used irrespective of whether the transfer posting involves a transfer between plants. The expenditure/income is added to the receiving material.
Supplementary entry for stock (BSD)
This account is posted when closing entries are made for a cumulation run. This account is a supplementary account to the stock account; that is, the stock account is added to it to determine the stock value that was calculated via the cumulation. In the process, the various valuation areas (for example, commercial, tax), that are used in the balance sheet are taxed separately.
Change in stock (BSV)
Changes in stocks are posted in Inventory Management at the time goods receipts are recorded or subsequent adjustments made with regard to subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
Stock posting (BSX)
This transaction is used for all postings to stock accounts. Such postings are effected, for example:
In inventory management in the case of goods receipts to own stock and goods issues from own stock
In invoice verification, if price differences occur in connection with incoming invoices for materials valuated at moving average price and there is adequate stock coverage
In order settlement, if the order is assigned to a material with moving average price and the actual costs at the time of settlement vary from the actual costs at the time of goods receipt
Because this transaction is dependent on the valuation class, it is possible to manage materials with different valuation classes in separate stock accounts.
Price differences (PRD)
Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).
Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.
Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification. If you use account modification, the following modifications are available in the standard system:
None for goods and invoice receipts against purchase orders
PRF for goods receipts against production orders and
order settlement
PRA for goods issues and other movements
PRU for transfer postings (price differences in the case
of external amounts)
Revenue/expense from revaluation (UMB)
This transaction/event key is used both in Inventory Management and in Invoice Verification if the standard price of a material has been changed and a movement or an invoice is posted to the previous period (at the previous price).
Expenditure/income from revaluation (UMD)
This account is the offsetting account for the BSD account. It is posted during the closing entries for the cumulation run of the material ledger and has to be defined for the same valuation areas.
Price differences (PRD)
Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).
Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.
Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification. If you use account modification, the following modifications are available in the standard system:
None for goods and invoice receipts against purchase orders
PRF for goods receipts against production orders and
order settlement
PRA for goods issues and other movements
PRU for transfer postings (price differences in the case
of external amounts)
Regards
Yogesh

Similar Messages

  • Different GL for Transaction/Event Key FRL

    Hi expert,
    I hv an issue for subcontract processing.. as defined in SAP the GL for Subcontract is :
    Dr. [FRL] External Service Fee
    Cr. [WRX] GR/IR
    Dr. [GBB-VBO] Inventory
    Cr. [BSV] SP components for refurbishment
    but at the other requirement, the GL for subcontract need to define as the following :
    Dr. [FRL] External Service Material
    Cr. [WRX] GR/IR
    Dr. [GBB-VBO] Inventory
    Cr. [BSV] SP components for refurbishment
    So, how can i define the differences. As i know, SAP just give one transaction/key FRL with one GL account.
    Is there any solutions for this issue?
    i think that it can be changed by defining a new mov.type copy from 101 to combine with new transaction/event key to differ the GL account, but the matter is i can't find any acc.modification FRL assign in this mov.type so i can't change it with new transaction/event key on it....
    please help mee...
    Regards,
    AJ

    Dear Kumar,
    i ll explain it more details..
    the material is the same.. the business process is that the material can be repaired and can be buy by using procedure exchange parts program.
    when it is repaired.. the requirement for the GL is :
    Dr. FRL External Service Fee
    Cr. WRX GR/IR
    Dr. GBB-VBO Inventory
    Cr. BSV SP components for refurbishment
    and when it is exchanging parts program the GL is :
    Dr. FRL External Service Material
    Cr. WRX GR/IR
    Dr. GBB-VBO Inventory
    Cr. BSV SP components for refurbishment
    and certainly, the material can only be assigned with one valuation class.. logically one valuation class can't be assigned with more than one GL account in one trans/event key especially FRL..
    So how it can be solved? or is there any solution by creating a new movement type for Godds Receipt to move the GL to another one.. thanks

  • BTE : Business Transaction Event

    What is the procedure to impliment this concept , please anyone tell me this step by step in detail by taking any example.
    Point will be rewarded for helpfull ans.
    regards
    Sonal

    hello once again ...
    http://help.sap.com/saphelp_erp2005/helpdata/en/3b/7f3e8be57c11d1951f0000e82dec10/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/ad/fc5a4064b4ef6fe10000000a1550b0/frameset.htm
    Example
    http://fuller.mit.edu/user_exits/business_transaction_event.htm
    Example Business Scenario for Business Transaction Events
    Company A would like to copy the group key field from the vendor master into the allocation field on all the line items within a vendor invoice and payments, including the vendor lines. This requirement assumes only one vendor is posted to in a document.
    To accomplish this requirement, Company A will use the Business Transaction Event 1130, Post Document: SAP Internal Field Substitution.
    1. IMG Menu Path: Financial Accounting Financial Accounting Global Settings Use Business Transaction Events Environment Infosystem (Processes).
    2. Find the correct Business Event. You are updating a field, so you select the Processes Info System instead of the Publish and Subscribe Info System.
    3. Execute the search with the defaults.
    4. Find the correct interface for updating a document: Post Document: SAP- Internal Field Substitution
    5. Put your cursor on the event and click on the Sample Function Module button.
    6. You are now in transaction SE37 – Function Builder. This is the function module (sample_process_00001130) you will need to copy into a "Z" name function module for your coding
    7. Click on the Copy button.
    8. Enter the "Z" function module name in the To Function Module field
    9. Enter a Function Group. If you need to create a "Z" function group, go to transaction code SE37 and follow menu path: Go to Function Groups Create Group. A function group is a logical grouping of function modules, and the ABAP code is generated for function groups. You will be prompted for a development class and transport when creating the function group.
    10. In Function Builder (transaction SE37), enter the new "Z" function module. Click on the Change button.
    11. The system will default into the source code screen where you may enter your ABAP code.
    12. Notice the tables available for the code. Additional tables may be declared if necessary.
    13. Enter the following source code
    tables: lfa1.
    data: z_groupkey like lfa1-konzs.
    z_groupkey = ' '.
    loop at t_bseg.
    check for vendor lines. If one is found, read the vendor master and
    retrieve the group key field.
    if t_bseg-koart eq 'K'.
    select single konzs from lfa1 into z_groupkey
    where lifnr = t_bseg-lifnr.
    endif.
    Move the group key field into all line items allocation field.
    loop at t_bsegsub.
    t_bsegsub-zuonr = z_groupkey.
    modify t_bsegsub index sy-tabix.
    endloop. "t_bsegsub
    endloop. "t_bseg
    14. Save the function module.
    15. Back out to the main Function Builder screen by clicking on the green arrow button.
    16. Activate the function module by clicking on the Activate button
    17. Assign the function module to the event in the IMG: Financial Accounting Financial Accounting Global Settings Business Transaction Events Settings Process Function Modules of an SAP Appl.
    18. Hit enter past the warning messages that this is SAP data.
    19. Click on the New Entries button.
    20. Enter the process for your interface. In your example it is 00001130.
    21. Enter the country the interface is valid for. If it is valid for all countries, leave this field blank.
    22. Enter the application the interface should be called for. If it should be called for all applications, leave this field blank. Please note that not all integrated transactions are programmed to go through these interfaces! You will need to test to find out!
    23. Enter the new "Z" function module
    24. Save the settings. At this point you will be prompted for a CTS number for the configuration change.
    25. The Business Transaction Event is complete! You are ready for testing.
    <b>sonal  assiegn point   in privious  question also...</b>

  • Transaction event key and posting key

    Dear All,
              To create a new Transaction event key/posting key.Whats the T.code

    Hi,
    Follow the Path
    SPRO-Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Transaction/Event Keys
    SPRO-Financial Accounting (New)-Accounts Receivable and Accounts Payable-Business Transactions-Internal Transfer Posting-Make and Check Document Settings-Define Posting Keys
    Hope this finds useful.
    Regards,
    Vengat

  • Production planning Business Transaction Events

    Hi All,
    Plz provide me with a list of Production Planning related Business Transaction Events.
    Thanks & Regards,
    Sudheer.

    Hi,
    The following is the basic flow for production planning.
    Step 1: Material Master
    Logistics > Production > Master Data > Material Master > Material > Create General > Immediately
    MM01
    Step 2: BOM creation
    Logistics > Production > Master Data > Bills of Material > Bills of Material > Material BOM > Create
    CS01
    Step 3: Work Center creation
    Logistics > Production > Master Data > Work Center > ( New Screen ) Work Center > Create
    CR01
    Step 4: Route creation
    Logistics > Production > Master Data > Routings > Routings > Routing > Create
    CA01
    Step 5: PIR Generation
    Logistics> Production>production planning>demand management>PIR>CREATE
    MD61
    Step 6: MRP Run
    Logistics>Materials Management>Material planning>MRP>MRP>Total Planning>Online
    MD01 or
    Logistics > Production > MRP > MRP > Sng-Item, Multi-Level
    MD02
    Step 7: Evaluation through MRP list and Stock requirement list
    Logistics>Materials Management>Materials Planning>MRP>Evaluations>MRP List>Individual Display
    MD05
    Logistics>Materials Management>Materials Planning>MRP>Evaluations>Stock Requirements List
    MD04
    Step 8: Conversion of Planned order to Production order
    Logistics > Production > Production control > Order > Create > With a planned order
    CO40
    OR
    Logistics >Production > Production control >Order > Create >With material
    CO01(For creating production order Without planned order)
    Step 9: Order management
    Logistics >Production > Production control >Order > Change >With material
    CO02
    Step10: Goods issue
    1. Logistics >Production >Production Control >Environment >Goods Movement >Goods Issue
    2. Logistics >Materials Management >Inventory Management >Goods Movement >Goods Issue
    MB1A--261Movement type
    Step11: Confirmations.
    Logistics >Production >Production control >Confirmation >Enter >For order
    CO15
    or
    Logistics >Production >Production control >Confirmation >Enter >For Operation >For time ticket
    CO11N
    Step12: Goods receipt
    Logistics > Production > Production Order > Environment > Material Movement > Post Mat to Stock
    OR
    Logistics > Materials Management > Inventory Management > Goods Movement > Good Receipt > For Order
    MB31
    Step13: Techo Or Close Order.
    This can be done from Prd. Order Header menue.
    Complete transaction codes you will get in http://www.sap-img.com/sap-pp.htm
    Apart from the listed these are also used in spro
    1. Subject: Re: list of SPRO t-codes
    2. Message: Define Resource Categroy OP40
    3. Define Status Profiles BS02
    4. Define Field Selection OPFA
    5. Define Task List Usage OP45
    6. Define Parameters OP7B
    7. Define Standard Value Key OP19
    8. Define Person Responsible SPRO
    9. Define Sub Systems SPRO
    Define Default Resource OP42
    Define Transition Matrix OPG6
    Define Control Keys OP00
    Define Setup Type SPRO
    Define Wage Group SPRO
    Define Suitability SPRO
    Define Shift Sequence OP4A
    Define Period Pattern Key OP11
    Regards,
    R.brahmankar

  • Activating/Using Business Transaction Event (BTE) PM000030

    Hello everybody !
    I need to implement BTE PM000030.
    I tried to follow the howto provided by sap & in the forums , but I must be missing a step since this is not working.
    I have created a custom product in transaction FIBF and now I want to assign my own function module to this event & product.
    I entered FIBF->Settings->Of a customer.
    Now when I attempt to select the PM000030 Proccess which im interested in, It is not there, to be exact - most of the proccessing are not there.
    From this step, I found no availible SAP documentation on dealing with this situation.
    I tried to manually enter PM000030 in the field and was rejected saying "entry does not exist in TSP01, when trying to create an entry manually in TSP01, I get an error saying I should first create a data element for it.
    I dont really know what procedure I should follow from here.
    I would highly appreciate any help, Thanks!
    Udi.
    Edited by: Udi Dekel on Mar 16, 2010 5:13 PM

    Hi,
    Please refer to following link :
    [Business Transaction Events (BTE) |http://wiki.sdn.sap.com/wiki/display/Snippets/BusinessTransactionEvents+%28BTE%29]
    [Business Transaction Events - Process Interface - Event 00001040 - customer implementation for dunning notice via email |http://wiki.sdn.sap.com/wiki/display/BPX/BusinessTransactionEvents-ProcessInterface-Event00001040-customerimplementationfordunningnoticeviaemail]
    Hope this helps.
    Regards,
    Chandravadan

  • ISU FICA generic DS  - business transaction events

    Hi All,
    I have created an ISU - FICA generic delta DS but delta is not working for this DS. I have specified one date field as delta specific field. I tried all possible combinations for this field like calday ,timestamp but delta is not working properly. with timestamp option it extract data but for that particular day where as it should extract data between init date & delta date.
    Is anybody having idea about "generic DS delta queue using business transaction event"? when this method is applicable & what is the procedure to make delta working?
    If there is any other option for generic delta plz let me know.
    Regards
    Sonal

    Hi Neel
    Pseudo delta is not generic delta. What I had advised is you can create pseudo delta if you are not able to find date field for generic delta mechanism. 
    1.Add both date fields to generic datasource alongwith all other fields.
    2.You have  to assign this datasource to infosource in BW and map the transfer rules.
    3. Create 2 infopackages for this -one for CREATED ON - will load new records created yesterday & other for CHANGED ON - will load changed records yesterday.
    4. schedule both these infopackages to load daily.
    Also want to re-iterate the fact that this approach is not recommended over creating a delta enabled generic datasource. But in abscence of date field for generic delta mechanism.
    Hope this helps
    Regards
    Pradip

  • How to trigger Business Transaction Event "WEIGH" in WM?

    How to trigger the Business Transaction Event "WEIGH" in WM from a user program?
    This "WEIGH" Business Transaction Event is supposed to modify the status in "status Management System" of SAP.
    Appreciate some feedback.

    Hi Ashutosh, if you are trying to raise a custom event you first must define the event within your business object, using TC SWO1.  If you like you can extend an existing business object or create a new one.  Once your business object is activated and your event is released you should be able to trigger it with the FM 'SWE_EVENT_CREATE'.
    P.S  If you are extending an existing business object, for example BUS2105 and your extended name is ZMBUS2105, refer to the original name, i.e. BUS2105 for the objtype field in the call to 'SWE_EVENT_CREATE'.
    Hope that helps,
    Kevin

  • Business Transaction Event - for bank details

    Hi
    In tcode BP (Business Partner) - tab "Payment Transactions" there is a field for Bank Account.
    In tcdoe FK02 (Change Vendor) - "Payment Transactions" in area "general data" there is a field Bank Account.
    For BP the field Bank Account may be initial, but for Vendor (FK02) it is not allowed to be initial.
    I have found out, that BTE (Business Transaction Event) could be a solution, but I don't know how to proceed with that.
    In tcode FINF (BTE) there is an event with number 00003000 (Bank Detalis Check Routine: Alternative Check), but I don't know how I can use it, and/or how I implement the changes.
    Has anybody an idea how to solve the issue?
    Thanks.

    Hi,
    Assign your new function module in FIBF via Menu path Settings --> P/S function modules (or Process function modules, depending on the BTE you are using) --> ...of a customer. Enter the BTE number and the name of your new function module. Country and application should remain blank, unless the BTE you are using offers those feature
    Check the link http://wiki.sdn.sap.com/wiki/display/Snippets/BusinessTransactionEvents+(BTE).
    Thanks & Regards,
    Neela
    Edited by: Neela M B on Sep 2, 2010 4:03 PM

  • What is business add-ins and business transaction events

    Dear All,
    Would you mind tell me what it sht business add-ins and business transaction events ?
    i still not understand about this after i read the training material
    Regards
    Luke

    Hi LukeWong ,
    BAdi:
    SAP Business Add-Ins (BAdIs) are one of the most important technologies used to adapt SAP software to specific requirements. BAdIs were introduced with Release 4.6 and replace function module exits. This technology is not limited to SAP applications. BAdI calls can be integrated in customer applications. These can then be enhanced by other customer applications. In the various SAP applications, BAdI calls are implemented at places where enhancements are appropriate.Business add-ins are enhancements to the standard version of the system. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
    As with customer exits, two different views are available:
    · In the definition view, an application programmer defines exit points in a source that allow specific industry sectors, partners, and customers to attach additional coding to standard SAP source code, without having to modify the original object.
    · In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard solution, if one is available.
    In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, country-specific versions, industry solutions, partner, customer, and so on). You can create definitions and implementations of Business Add-Ins at any level of the system landscape.SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
    The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to differentiate between Add-In implementations using the filter Country or other criteria.
    The enhancement technique is set up in such a way that it is possible to define interfaces for ABAP soure code, screens, GUI interfaces, and tables. These allow customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
    BADI is just an object-oriented version of user-exit. Instead of entering program code into some function module (as in customer-exit), you define some class which has to implement predefined methods and those methods are fired at predefined points just like an old user-exit. Some BADI can have multiple independent implementations which is much better for software deployment as several developers can implement the same BADI independently. BADI/UserExists are used to enhance R/3 For customer Needs.
    Actually there is no transaction to find when and where the BADI
    is called.
    1. You can see the BADI description to find why it is called.
    2. Once you implemented and activated the BADI, put some break points
    in the BADI and see "where else used" option to check in what all
    programs this BADI is called. In the ITS debug, when you are doing
    the operation what exactly the BADI description tells, it will take
    to the break points and you have to do manually debug the whole thing.
    I know its bit difficult to do manual debug the whole thing, it
    takes lot of time, but you have to be very patience when you are
    dealing with BADI's.
    Transaction SE18 is the BADI equivalent of transaction SMOD
    Transaction SE19 is the BADI equivalent of transaction CMOD .
    To find the BADI to be implemented and then implement this via SE19.
    These steps should enable you to find any BADI related to any transaction in a matter of minutes.
    Procedure 1:
    1) Go to the transaction SE37 to find your function module.
    2) Locate the function SXV_GET_CLIF_BY_NAME.
    3) Put a breakpoint there.
    4) Now open a new session.
    5) Go to your transaction. 6) At that time, it will stop this function.
    7) Double click on the function field EXIT_NAME.
    8) That will give you name of the BADI that is provided in your transaction.
    Business Add-Ins
    Procedure 2:
    1) Goto se24 (Display class cl_exithandler)
    2) Double click on the method GET_INSTANCE.
    3) Put a break point at Line no.25 (CASE sy-subrc).
    4) Now Execute SAP standard transaction
    5) Press the required button for which you need to write an exit logic, the execution will stop at the break point.
    6) Check the values of variable 'exit_name', it will give you the BADI name called at that time.
    7) This way you will find all the BADIs called on click of any button in any transaction
    Check this blogs 2 find a BADI:
    How To Define a New BAdI Within the Enhancement Framework (Some Basics About the BAdI,BAdI Commands in ABAP,
    When to Use a BAdI?)
    /people/thomas.weiss/blog/2006/04/03/how-to-define-a-new-badi-within-the-enhancement-framework--part-3-of-the-series
    How to implement a BAdI And How to Use a Filter
    /people/thomas.weiss/blog/2006/04/18/how-to-implement-a-badi-and-how-to-use-a-filter--part-4-of-the-series-on-the-new-enhancement-framework
    Introducing Business Add-Ins
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f3202186-0601-0010-6591-b832b1a0d0de
    How to implement BAdi in Enhancement Framework
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0456c54-0901-0010-f0b3-cd765fb99702
    Business Add-Ins
    http://help.sap.com/saphelp_47x200/helpdata/en/ee/a1d548892b11d295d60000e82de14a/frameset.htm
    BAdI: Customer-Defined Functions in the Formula Builder
    http://help.sap.com/saphelp_nw04/helpdata/en/04/f3683c05ea4464e10000000a114084/content.htm
    Difference Between BADI and User Exits
    http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm
    To Use BADI - Business Add In you need to Understand ABAP OO Interface Concept
    http://www.sap-img.com/abap/business-add-in-you-need-to-understand-abap-oo-interface-concept.htm
    Business Transaction Events
    Business Transaction Events (Open FI) The Open FI enhancement technique was developed in the Financial Accounting component. Open FI is based upon the following principles: Application developers must define their interface in a function module, an assignment table is read in the accompanying (generated) code, and the customer modules assigned are called dynamically. This technique differentiates between enhancements that are only allowed to have one implementation and enhancements that can call multiple implementations in any sequence desired. Both industry-specific and country-specific enhancements may be defined.
    SAP business transaction events are one type of customer enhancements provided by SAP! We can access the business transaction events using FIBF.Next we have to find the process interface for duplicate invoice check!
    check this blog for details on SAP business transaction events
    Business Transaction Events
    http://fuller.mit.edu/user_exits/business_transaction_event.htm
    FI Enhancement Technique – How-To-Guide on the Usage of Business Transaction Events (BTE)
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/207835fb-0a01-0010-34b4-fef1240ba9b7
    Creation of Events via Business Transaction Events
    http://help.sap.com/saphelp_nw04/helpdata/en/3b/7f3e8be57c11d1951f0000e82dec10/content.htm
    In SAP R/3 you must activate the business transaction events (BTEs) for Availability Check Using SAP R/3. To set this indicator in SAP R/3:........
    http://help.sap.com/saphelp_crm40/helpdata/en/b6/de3efc6bbcdc4b948d466857a10323/content.htm
    cheers!
    gyanaraj
    ****Pls reward points if u find this helpful

  • Separate Transaction event key and Document type

    Hello Gurus,
    Need suggestion and process how to have separate transaction event key and Document types sued in Material document creation with a different number range for the movement types used for SD processes.
    Example: 601/602/651 movement types have the Transaction event key as WL
                   561 has the Transaction event as WA
                   701/702 movement types have the Transaction event as WI
    the transaction event keys of WA WH WI WL WQ WR WS WZ have the same number range.
    I am looking for solution and suggestion as how do we maintain transaction event key and document type for SD dispatches, cancellation, returns movement types separately.
    Thanks and Regards

    Hi,
       U can create new document type in  OBF4  copy the existing on ee.g WA make new document type and in number range assign the FI  number range which u want to assign,  MM number  range can be create in T. code OMBT and FI number range in FBN1.  Documen ttype assignment to t. code is done in OMBA
    regards,
      zafar
    Edited by: zafar_karnalkar on Aug 13, 2010 12:23 PM

  • Menu path to create new transaction event key

    Dear Experts,
    Please give me the menu path and Transaction code to create New transaction event key for
    Materials Management postings.
    Thanks in Advance

    Hi,
    SPRO - Materials Management - Purchasing - Conditions - Define Price determination process - Define transaction/Event Keys.
    For MM transaction key T Code OMGH
    and for FI tarnsaction key T Code is OBCN
    GO to SM30 enter the table T030A and then click on display
    Please note the group as well as transaction code
    May Help U !
    Regards,
    Pardeep Malik

  • Business transaction event in MM

    What is the T-Code for Business Transaction event in MM like we have FIBF in FI

    Hi,
    [Re: Business Transaction Events;
    regards,
    MRao

  • Business Transaction Events

    Hi,
    we use in our system User-Exits and Business Add-In.
    Now i found in customizing "Business Transaction Events".
    Are these to use like User-Exits or Business Transaction Events?
    How can i use this, has anyone some doku?
    Thanks for help.
    Regards, Dieter

    Hi,
    The BTEs are user-exits of accounting module and allow to connect additional components (SAP, custom development, or not SAP) to the main processes of accounting in SAP. But it can often use them to insert controls of accounting documents or master data.
    For example I often use them to know the document number while it's being created, or to change the data in the reports to display FI items, or to use a smartforms instead of sapscript.
    So you can use them in several situations, but if you use them to check the document, you'd use them if you can't to do those controls by validation.
    BTEs are kind of enhancements ( Earlier it was in FI only but has since been extended to some of other areas ).
    All Functions starting with OPEN_FI_PERFORM* are sample of BTE which you can leverage in your custom function.
    see this link
    check this,
    http://help.sap.com/saphelp_nw04/helpdata/en/3b/7f3e8be57c11d1951f0000e82dec10/content.htm
    http://fuller.mit.edu/user_exits/business_transaction_event.htm
    Refer to this blog..
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/207835fb-0a01-0010-34b4-fef1240ba9b7
    Thanks.

  • About transaction /event keys

    hi
    mm gurus
    for what type of transactions we will use GBB Transaction/event key and can u explain about the use of this
    thanks
    subbu

    Hi
    Offsetting entry for stock posting (GBB)
    Offsetting entries for stock postings are used in Inventory Management. They are dependent on the account grouping to which each movement type is assigned. The following account groupings are defined in the standard system:
    AUA: for order settlement
    AUF: for goods receipts for orders (without account assignment)
    and for order settlement if AUA is not maintained
    AUI: Subsequent adjustment of actual price from cost center directly
    to material (with account assignment)
    BSA: for initial entry of stock balances
    INV: for expenditure/income from inventory differences
    VAX: for goods issues for sales orders without
    account assignment object (the account is not a cost element)
    VAY: for goods issues for sales orders with
    account assignment object (account is a cost element)
    VBO: for consumption from stock of material provided to vendor
    VBR: for internal goods issues (for example, for cost center)
    VKA: for sales order account assignment
    (for example, for individual purchase order)
    VKP: for project account assignment (for example, for individual PO)
    VNG: for scrapping/destruction
    VQP: for sample withdrawals without account assignment
    VQY: for sample withdrawals with account assignment
    ZOB: for goods receipts without purchase orders (mvt type 501)
    ZOF: for goods receipts without production orders
    (mvt types 521 and 531)
    regards
    Srinivas

Maybe you are looking for

  • No sender agreement configured in the XI Integration Directory

    Hi, I am using MPA(MML) message format in XI scenario. My scenarios are R3->XI->Marketplace and Marketplace->XI->R3. The first scenario works fine with no problems where as when i try to post MML message from marketplace to XI system, i am seeing the

  • TOSlink optical cable for a Ma Pro? How does it work?

    Not sure if this is the place for this question or not, but I am trying to find out more information about the optical audio in/out section of the Mac Pro. On Apple's description page it claims that a regular TOSlink optical cable will work in those

  • Full screen slide show?

    How do I display photos full screen on a photo page created in iweb and published to .mac? No matter how I size the photos in iphoto they display too small in a web browser after clicking on "start slideshow" on the created web page.

  • Help: dynamic converter

    hi, expert stellent users, im new to oracle ucm, i already installed content server 10gr3 on windows 2003 and i want to test the functionality of dynamic converter component. i already enabled the component and restarting content server and web serve

  • DMEE: name of node in SAPscript form

    Hi, i´m using the DMEE for creating an outgoing XML-File with the Formatree SEPA_CT. For a Node you can define in the Formattree by your own a SAPscript name. I create a form Accompanying Letter for the XML-File with SAPscript. In SAPscript i have fu