New BADI  and classic BADI

Hi,
Could anyone post solution for making out that a classic BADI is preferred or a new BADI.
This's not an interview question. I just want to make it out for my requirement.
Could anyone post  the exact real time differences between a classic BADi and a new BADI.

Hi,
Use new BAdI over classical BAdI, as performance of new BAdI is better.
Incase of new BAdI you have to create an Enhancement Spot and create BAdI definition under it, and subsequently implement the BAdI. In the code use
GET BADI badi_name to generate BAdI handle, and
CALL BADI badi_name->method.... to call BAdI methods.
Incase of Classical BAdIs adapter class are created in the runtime of the application program.
Check the following link:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/ee/6f3b42ea85b26be10000000a155106/frameset.htm
Regards,
George
Edited by: George Biswal on May 26, 2009 3:04 PM

Similar Messages

  • Demo programs of new and classic BADIs - transactions SE18 and SE19

    Does SAP supply any demo examples of the new BADI switch framework and/or classic BADIs.
    I've been trying to learn how to use SE18 and SE19 from examples on the web and articles in Thomas Weiss blogs. But, I'm still confused.
    Thanks
    Ed Baker

    Thank you for replying.
    I did look at that example during my investigations. In fact, I found another page with screen shots for the example at http://www.sapmaterial.com/badi.html
    Unfortunately, I'm on ECC 6.0 and the screen shots don't quite line up.
    What I'm actually referring to is spots like this in SAP supplied code. Here's a typical example in SAPMV45A during transaction VA01 (sales order create).
    How do I get SAP to branch off to user code when it reaches the "ENHANCEMENT-POINT" line.
    *       MODULE XVBAP_LESEN                                            *
    *       Tabelle XVBAP fuer Bildschirmanzeige lesen, es wird die erste *
    *       Einteilung mit Wunschmenge zur Verfügung gestellt             *
    MODULE XVBAP_LESEN OUTPUT.
      PERFORM XVBAP_LESEN(SAPFV45P) USING CHAR1.
    ENHANCEMENT-POINT XVBAP_LESEN_01 SPOTS ES_SAPMV45A.
    *$*$-Start: XVBAP_LESEN_01----------------------------------------------------------------------$*$*
    ENHANCEMENT 59  /SAPHT/SW_LIC_BU_VERS_SAPMV45A.    "active version
    * IS-HT (D45)(D44)
       CALL FUNCTION '/SAPHT/SW_BUMP_ICON_OUTPUT'
          EXPORTING
              i_vbap_posnr       = vbap-posnr
              i_vbap_uepos       = vbap-uepos
              i_vbup_bump        = xvbup-bump
          CHANGING
              c_gg_process_icon  = gg_process_icon.
    ENDENHANCEMENT.
    *$*$-End:   XVBAP_LESEN_01----------------------------------------------------------------------$*$*
    ENDMODULE.

  • Determining which PCA to use between new-GL and classic EC-PCA

    I tried to use 1kek to transfer AR and AP from FI to PCA but failed with message saying "Document Splitting is Activated".
    We are considering using PCA to make B/S and P/L of several business unit in a company. We are using SAP 6.0. After looking for the references, I understood that I can use new-GL or EC-PCA(classic PCA) for Profit Center Accounting. I wonder which way is the best and easiest one to achieve my company's object.
    As I understood if I activate document splitting, it means I use new-GL for PCA, and I should use table FAGLFLEXA of FI instead of GLPCA of EC-PCA.
    I'd like to use new-GL because it's "new" and convenient, hopefully. But I found several problems using new-GL to make financial reports.
    The first problem was that I couldn't make allocation with accounts which cannot be manually input like AA accounts(Building, Machine, etc.), AR/AP or materials. When I operate transaction FAGLGA35, no effect occurs on those accounts.
    And the second problem is that I couldn't find a way to make a report which has accounts list on its first column and profit center list on its first row. It's surely because I'm a newbie in SAP
    I think everybody trying to use new_GL encounter this problem and it's wired because I couldn't find any thread about this.
    And If I decide to use EC-PCA and make allocation on GLPCA, I think I should make some CBO to transfer AR/AP to EC-PCA. Is there any other possible solution?
    I have a lot of things to ask but I'm not even sure what I know and don't.
    Thanks for you guru's great help.

    The following notes will help you in understanding the set up of PCA in New GL with Classic PCA (EC-PCA):  <b>OSS Norte no 826357</b>
    You want to know
    For release SAP ERP, the Profit Center Accounting was integrated into the new G/L accounting. The solution is as follows:
    SAP delivers the 'Profit Center' and the 'Partner Profit Center' as fixed characteristics that are posted on the original FI postings. The data is not updated in another ledger as in the classic Profit Center Accounting.
    As a result of integration of the Profit Center Accounting into the new G/L accounting, new functions such as 'Document Splitting' are available. Using the function 'Document Splitting' (online document split), you can create balance sheets for company codes as well as for other entities such as the profit center. The balance is then set to 0 for each document for the profit center.
    Integrating the G/L accounting and the Profit Center Accounting into the one application also removes the time and effort needed to reconcile G/L accounting and PCA.
    When implementing the new G/L accounting in Release SAP ERP, we recommend that all new customers map the Profit Center within the new G/L accounting by activating the scenario FIN_PCA (profit center update). It is not advisable to activate the classic Profit Center Accounting in parallel and consequently update parallel data volumes.
    Detailed information about setting Profit Center Accounting in the New General Ledger:
    Define the update of the characteristics 'Profit Center' and 'Partner Profit Center' in the ledger by selecting the scenario 'Profit center update' (Customizing: Financial Accounting (New) -> Financial Accounting Basic Settings (New) -> Ledgers -> Ledger -> Assign Scenarios and Customer-Defined Fields to Ledgers).
    If you want to use the document splitting, you can define the field 'Profit center' as a splitting characteristic in the document splitting (Customizing: Financial Accounting (New) -> General Ledger Accounting (New) -> Business Transactions -> Document Splitting -> Define Document Splitting Characteristics for General Ledger Accounting). Set the 'Zero balance' indicator again for the added field 'Profit Center'. You can now create balance sheets on the profit center. You must also activate the Mandatory Field check to ensure that the profit center is set in all postings. If you want to display balance sheet items at profit center level (for example, receivables and payables) but you do not require complete balance sheets, we recommend that you do not set the indicator 'Zero balance' and 'Mandatory Field check'.
    If you already used classic Profit Center Accounting as an SAP R/3 customer but you now want to use Profit Center Accounting in the new general ledger, you can continue to use classic Profit Center Accounting in parallel to the profit center update scenario in the new G/L accounting in the interim. However, we do not recommend you do this on a long-term basis due to the increased data volume and the increased time and effort required.
    However, if the classic Profit Center Accounting continues to play a leading role for you, we recommend that you do not activate the document splitting in the new G/L accounting, and not for other entities such as the segment either. This is because the classic Profit Center Accounting uses certain functions of the classic general ledger that are no longer available with active document splitting (for example, transaction F.5D, Calculate Balance Sheet Adjustment).
    See the following information for details about the differences between the function of PCA in new G/L accounting and in classic PCA and for details about the effects of new G/L accounting on the posting behavior in classic PCA. Even if mapped into new G/L accounting, PCA always occurs within a controlling area. SAP does not support cross-controlling area PCA. The derivation of profit center and partner profit center with the different business processes when you use the new G/L Accounting is identical to the classic Profit Center Accounting. Details about the differences are available in the following.
    1. Set the proposal profit center for additional balance sheet and P&L accounts.
    Release SAP ERP 2004:
               Profit center scenario in the new G/L accounting is active, classic Profit Center Accounting is not active: If you have to set a profit center on balance sheet and P&L accounts, make entries manually, use FI substitution or implement the BADI AC_DOCUMENT. Note that the system calls the BADI AC_DOCUMENT only for postings using the accounting interface (for example, MM and SD postings), but it is not called for FI postings.
               Profit center scenario in new G/L accounting and classic PCA is active: Transactions 3KEH and 3KEI are available in the classic Profit Center Accounting for maintaining a proposal profit center for balance sheet accounts and P&L accounts. Transactions 3KEH and 3KEI also exist in SAP ERP2004 and function in the same way as in R/3: In other words, you can use the settings in transaction 3KEH to control the update in classic Profit Center Accounting, and the transactions set a proposal profit center where necessary. Keep in mind that the profit center information is therefore affected in new G/L accounting by settings in classic Profit Center Accounting.
    Release SAP ERP 2005:
               Transactions 3KEH and 3KEI (from classic Profit Center Accounting) for maintaining proposal profit centers for balance sheet and P&L accounts are no longer used to set the profit center.
               Profit center scenario in the new G/L accounting is active, classic Profit Center Accounting is not active: If you have to set a profit center on balance sheet and P&L accounts, make entries manually, use FI substitution or implement the BADI AC_DOCUMENT. Note that the system calls the BADI AC_DOCUMENT only for postings using the accounting interface (for example, MM and SD postings), but it is not called for FI postings. In addition, the new transaction FAGL3KEH and the BAdI FAGL_3KEH_DEFPRCTR are available for maintaining proposal profit centers. You can use these new functions to determine a proposal profit center depending on the company code and the account. Note that this proposal profit center does not appear on the input screen; it is derived only when you post the document. The proposal profit center is used if the line item does not contain a CO account assignment and if the profit center was not already determined elsewhere.
               Profit center scenario in new G/L accounting and classic Profit Center Accounting are active: The entries of transaction 3KEH control ONLY the transfer of line items to classic Profit Center Accounting. Transaction 3KEI is no longer relevant. To set the profit center, use the options which are available in the new G/L accounting (make entries manually, use FI substitution, or implement the BADI AC_DOCUMENT).
    2. Derivation of the partner profit center
    Release SAP ERP 2004:
               Profit center scenario in the new G/L accounting is active, classic Profit Center Accounting is not active: Transactions 8KER/8KES are no longer available. Notes 997925 and 1087350 provide the functions from transaction OCCL. Alternatively, you can use the BAdI AC_DOCUMENT to set the partner profit center.
               Profit center scenario in new G/L accounting and classic PCA is active: Transactions 8KER/8KES and OCCL (reading purchase order/sales order for affiliated companies) are active.  However, we recommend that you no longer use transaction 8KER or 8KES. Partner profit centers derived using these transactions are available in both classic Profit Center Accounting and in New General Ledger Accounting only if the line is relevant in classic Profit Center Accounting.
    Release SAP ERP 2005:
               Profit center scenario in the new G/L accounting is active, classic Profit Center Accounting is not active: Transactions 8KER/8KES are no longer available. Notes 997925 and 1087350 provide the functions from transaction OCCL. Alternatively, you can use the BAdI AC_DOCUMENT or the new BAdI FAGL_DEFPPRCTR (enhancement spot FAGL_LEDGER_CUST_DEFPRCTR) with the method SET_DEFAULT_PART_PRCTR to set the partner profit center.
               Profit center scenario in new G/L accounting and classic PCA is active: Transactions 8KER/8KES and OCCL are active. However, we recommend that you no longer use transaction 8KER or 8KES because partner profit centers derived using these transactions are available in both classic Profit Center Accounting and in New General Ledger Accounting only if the line is relevant in classic Profit Center Accounting. Instead, if required, you should use the BAdI FAGL_DEFPPRCTR to set the partner profit center. A partner profit center determined in this way is always updated both in new G/L accounting and in classic Profit Center Accounting.
    3. Displaying receivables and payables for each profit center
    Document splitting is active
               The detailed information from the general ledger view about receivables and payables split online from the document splitting is NOT available for classic Profit Center Accounting. In this case, you CANNOT split receivables/payables nor follow-up costs subsequently (Transaction F.5D - report SAPF180A, Transaction F.50 - report SAPF181, Transaction F.05 - report SAPF100). This means that you CANNOT use transaction 1KEK to transfer receivables and payables to classic Profit Center Accounting. Follow-up costs split according to source can be transferred online to the classic Profit Center Accounting because these are already available in the data entry view.
               Read the documentation of the document splitting carefully. Analyze in which cases you have to set default account assignments because the document splitting is sometimes prevented by default account assignments.
    Document splitting is not active
               In this case, you CANNOT display the receivables and payables according to source at profit center level within the new G/L accounting. However, you can use the old split of the receivables and payables within the classic Profit Center Accounting (transaction F.5D) as well as of the follow-up costs (transaction F.50), and you can use the periodic transfer of receivables and payables using transaction 1KEK. However, you can execute the new report for the foreign currency valuation of the open items (report FAGL_FC_VALUATION) with depreciation areas only, which means that the documents are no longer updated (valuation difference not updated in BSEG-BDIFF). As a result, transaction 1KEK copies only the original receivables/payables, independently of transaction 2KEM 'Account Valuation Differences'; in other words, the original data is not corrected by the valuation differences.
               You can use the standard report groups 8A98 and 8A99 to display the open receivables and payables in classic Profit Center Accounting.
    4. Periodic transfers of asset portfolios to classic Profit Center Accounting
                  As of Release 4. 7, it is possible to map a parallel reporting mapped in FI (for example, parallel accounts) for parallel depreciation areas in Asset Accounting by using particular settings (defining an accounting principle). You must stop the execution of transaction 1KEI because it would result in duplicated data in PCA because of postings to the same accounts. You must also stop transaction 1KEI with a 'different company code' or a 'different depreciation area in the different company code' because the data cannot be transferred correctly. Transaction 1KEI terminates with the error message KM 764. As of Release SAP ERP, if the new general ledger accounting is active, the system issues the message FAGL_LEDGER_CUST 076.
    5. Dummy profit center on P&L accounts
                  You use transactions 3KEH and 3KEI to firstly try to determine a proposal profit center in classic Profit Center Accounting for document line items with a P&L account (no cost element) and without a profit center account assignment. If the system does not find a proposal profit center, the dummy profit center is set for some activities (primarily from Logistics). If the new G/L accounting is active AND if at least one of the two characteristics 'Profit Center' and 'Segment' is used in the document splitting, the routine for setting the dummy profit center will no longer run (see Note 820121 and 832776). Otherwise the document splitting would not split a document, or not split it correctly.  The system must then find the profit center that is valid for the process using the document splitting or another derivation. If this is not the case, the document line item will not be updated in the classic Profit Center (document line items with Profit Center initial are not allowed in the classic Profit Center Accounting).
    6. PCA additional rows
                  If you map Profit Center Accounting in new General Ledger Accounting in SAP ERP, you can use consulting note 937872 to update PCA additional lines recognized from classic Profit Center Accounting in new General Ledger Accounting.
                  If you use the transfer price functions, you do not require Note 937872 because the structure of the PCA additional lines are technically "true" and are automatically posted in new General Ledger Accounting when maintained in transaction 0KEK.
    7. Substitution of profit centers in sales orders
                  Transactions 0KEL and 0KEM are available both in the classic Profit Center Accounting and in the new G/L accounting (Customizing: Financial Accounting (New) -> General Ledger Accounting (New) -> Tools -> Validation/Substitution)
    8. Reporting
    Line item reporting within the new G/L accounting
               Release SAP ERP 2004: Even if document splitting is set with the characteristic Profit Center, only one restricted line item reporting to profit centers is available in this release at present. When you use the G/L account line item list of FI, you can limit profit centers for line item settlement G/L accounts that are not relevant for the document splitting. As of Support Package 10, line item reporting to profit centers and segments is available.
               Release SAP ERP 2005: Line item reporting according to profit centers and segments is available.
    Ledger reporting within the new G/L accounting
               Release SAP ERP 2004: Even if the document splitting is set with the characteristic profit center or segment, no current account reporting to profit centers and segments is available up to Support Package 10.  With Support Package 10, current account reporting according to profit centers and segments is available. Also see the detailed explanations for Release SAP ERP 2005.
               Release SAP ERP 2005: Current account reporting according to profit centers and segments is available. It replaces the standard report groups 8A98/8A99 in earlier releases. However, the difference is that the foreign currency valuation correction is no longer displayed for each item because no update of the valuation in items occurs through the foreign currency valuation in the new general ledger (no BDIFF/BDIFF2 update). It is a key date-related valuation (mostly for the period end).
    9. Transfer prices
                  The transfer price functions (multiple valuations) are available for new General Ledger Accounting as of SAP ERP 2005. For SAP ERP 2004, see the release restrictions in Note 741821. In SAP ERP 2004, you can use the transfer price functions or multiple valuation functions only if you have activated the classic General Ledger and classic Profit Center Accounting.
    10. Creating the profit center standard hierarchy
    Release SAP ERP 2004: You must create the highest node of the standard hierarchy in the Customizing of the classic Profit Center Accounting (transaction 0KE5), even if you are not using classic Profit Center Accounting.
    Release SAP ERP 2005: To create the highest node of the standard hierarchy, use transaction SM30 with the maintenance view V_FAGL_PC_STHR.
    11. Creating the dummy profit center
    Classic Profit Center Accounting is active (regardless of whether classic G/L accounting or new G/L accounting is active):
               If the classic Profit Center Accounting is active, you must create a dummy profit center to avoid postings with an initial profit center in the database tables of the classic PCA.
               If the new G/L accounting is also active AND if you are using at least one of the two characteristics 'Profit Center' and 'Segment' in the document splitting, you have to ensure in Release SAP ERP 2004 that Notes 820121 and 832776 are included.  In Release SAP ERP 2005, the changed posting logic is included from the beginning.  Note that the update of document line items in classic Profit Center Accounting is omitted because of this.
    Classic Profit Center Accounting is not active, New G/L Accounting is active and you are using at least one of the two characteristics 'Profit Center' and 'Segment' in the document splitting:
               You do not have to create and use a dummy profit center.  Using the dummy profit center can cause situations you want to avoid: For example, the system splits receivables/payables to the dummy profit center because of the document splitting (you cannot transfer them manually), or a document line item with dummy profit center account assignment is not split by the document splitting.  To ensure that a profit center is assigned in all rows, set the profit center as mandatory field in the Customizing of the document splitting.  However, note that this can also lead to terminations while posting, if a profit center assignment is missing.
    12. Compare G/L Accounts in FI with Profit Center Accounting (Transaction KE5T)
                  In classic Profit Center Accounting, transaction KE5T is used to compare account balances. In this transaction, the ledgers to be compare are fixed. If you use Profit Center Accounting in new General Ledger Accounting, use the general transaction GCAC. You can enter any base ledger and any comparison ledger.

  • Cost center assessment in new GL and classic GL

    HI ALL
    I want to double check one thing. When you run cost center assessments in classic GL, the system will make entries in GLPCT table for PCA with assessment cost element. But when you got migrated into NEW GL then system will not make any entry in FAGLFLEXT table with assessment cost element. These assesments have no effect on PCA module. If I want to reflect the effect of costcenter assesments in PCA in new GL , where can I check for that?....Is there anyway to acheive this without activating both classic and new gl PCA?
    Thanks
    Steve

    Hi,
    If you have defined variant for real time integration and it has "Cross profit center" checked and this variant is assigned to company code, then FI-CO reconcilation posting will be posted in each of the profit center.
    One can have a single account for all reconcilation posting or different FI-CO recon account can be used for each bussiness process / for each assessement cost element using substitution.
    FI-CO reco account is visible in the FAGLFLEXT and hence can be displayed in report.
    Regards
    Chetan.

  • Classic BAdi and New BAdi ...

    Hi all,
    I have a question regarding the new BAdi concept using enhancement spots.
    With the classic BAdi's once we create an implementation it will call up our implementation when the BADI class is been called.
    But with the new concept we have to explicitly call the BAdi we created right ? doesn't this mean modifiying the standard code ( If there's no ehancement section or point )?
    Can someone tell me whether there is another way to call our implementation by using GET BADI and CALL BADI statement without modifying standard code ( by creating an explicit enhancement).
    Cheers,
    D.

    hi,
    Classic and new BAdIs differ in a number of features that are important for migration:
    1. BAdI object
    a. With classic BAdIs, a BAdI object is created by calling a factory method, and referenced via a reference variable of the type of the BAdI interface.
    b. With new BAdIs, a BAdI object is created via the ABAP statement GET BADIas a handle for the calls of BAdI methods, and referenced via a reference variable of the type of the BAdI. A BAdI object is an instance of an internal BAdI class, which otherwise is invisible to the outside.
    2. Passing comparison values for the filter
    a. With the classical BAdIs, the filter values are stored in a structure and passed with the call of the BAdI methods.
    b. With the new BAdIs, the comparison values for the filters used to search for implementations are passed when the BAdI object is created with the GET BADIstatement.
    There is no way of migrating the call of the factory method one-to-one into the ABAP statement, because GET BADI can also return an existing BAdI object, which is not possible with the factory method.
    3. Calling BAdI methods
    Passing comparison values for the filter
    a. A classic BAdI can be called only once and the call positions are registered centrally.
    b. With new BAdIs, multiple calls are possible and the call positions are not registered centrally.
    For the above reasons, an automatic call migration is not possible.
    Have a look at below link.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ee/6f3b42ea85b26be10000000a155106/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/0e/4d3e42fc94aa04e10000000a1550b0/content.htm
    I hope it helps.
    Best Regards,
    Reshma

  • Playlist folders are supported on the new Nano! (and Classic)

    Hi folks,
    You may have noticed that in iTunes 7.4, playlist folders now show up when selecting which playlists to sync to your iPod. Originally, people thought this was just cosmetic on the iTunes side.
    I am here to tell you now that it is not just cosmetic. The same folders that you create on iTunes will be ALSO shown on your new Nano (and Classic I assume). Previously, the navigation was:
    Playlists->Playlist
    Now it is:
    Playlists->Folder->Playlist
    Which also means you can hit Play on the Folder and it will play every playlist within that folder!

    Anyone able to figure out how the ipod sorts playlists within folders?
    On my itunes I have a folder of playlists for audiobooks. Within that, there's another folder for each nano and then playlists for the books on that nano. In ITunes, they appear in alphabetical order by playlist name, but on the Nano, it seems random: Here's a sample:
    Beaton
    Bond
    Brett
    Fletcher
    Lippman
    Robb
    Stout
    Crais?
    Wren
    Truman?
    Any suggestions would be appreciated.

  • Whats is the diff. btw classic badi and new badi

    Hi guy,
    I just found out that there is classic and new badi implementation in SE19, I would like to check out with u guys on what is the diff btw the two?
    thanks.

    <b>Differences Between Classic and New BAdIs</b>
    Classic and new BAdIs differ in a number of features that are important for migration:
    1. BAdI object
    a.      With classic BAdIs, a BAdI object is created by calling a factory method, and referenced via a reference variable of the type of the BAdI interface.
    b.      With new BAdIs, a BAdI object is created via the ABAP statement GET BADIas a handle for the calls of BAdI methods, and referenced via a reference variable of the type of the BAdI. A BAdI object is an instance of an internal BAdI class, which otherwise is invisible to the outside.
    2. Passing comparison values for the filter
    a.      With the classical BAdIs, the filter values are stored in a structure and passed with the call of the BAdI methods.
    b.      With the new BAdIs, the comparison values for the filters used to search for implementations are passed when the BAdI object is created with the GET BADIstatement.
    There is no way of migrating the call of the factory method one-to-one into the ABAP statement, because GET BADI can also return an existing BAdI object, which is not possible with the factory method.
    3. Calling BAdI methods
    Passing comparison values for the filter
    a.      A classic BAdI can be called only once and the call positions are registered centrally.
    b.      With new BAdIs, multiple calls are possible and the call positions are not registered centrally.
    For the above reasons, an automatic call migration is not possible.
    Have a look at below link.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ee/6f3b42ea85b26be10000000a155106/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/0e/4d3e42fc94aa04e10000000a1550b0/content.htm
    I hope it helps.
    Best Regards,
    Vibha
    *Please mark all the helpful answers

  • Since the latest IOS update, my new iPad Air is freezing and glitching badly. Typing is delayed.

    Since the latest IOS update, my new iPad Air is freezing and glitching badly. Typing is delayed.

    iPad running slow? How to speed up a slow iPad
    http://appletoolbox.com/2012/07/ipad-running-slow-how-to-speed-up-a-slow-ipad/
    If You Think iOS 7 Feels Slow Here’s How to Speed It Up
    http://osxdaily.com/2013/09/23/ios-7-slow-speed-it-up/
    You may have many apps open which can possibly cause the slowdown and possibly the loss of wifi. In iOS 4-6 double tap your Home button & at the bottom of the screen you will see the icons of all open apps. Close those you are not using by pressing on an icon until all icons wiggle - then tap the minus sign. For iOS 7 users, there’s an easy way to see which apps are open in order to close them. By double-tapping the home button on your iPhone or iPad, the new multitasking feature in iOS 7 shows full page previews of all your open apps. Simply scroll horizontally to see all your apps, and close the apps with a simple flick towards the top of the screen.
     Cheers, Tom

  • My macbook pro hard drive went bad and i bought a new one and installed it. Now i have the old corrupted hard drive in my hand and i am looking to recover my files from it, any suggestions please? too bad i never backed them up.

    My macbook pro hard drive went bad and i bought a new one and installed it. Now i have the old corrupted hard drive in my hand and i am looking to recover my files from it, any suggestions please? too bad i never backed them up.

    After you have installed the OSX on the new HDD in your MBP, install the old HDD in an enclosure and connect it to your MBP via USB.  Then try to drag and drop  your data to the new HDD. 
    If this proves unsuccessful, you may look for data recovery software on the Internet.  There will be free trails to see if it will work or not.  If the trial suggests that it will work, then you will have to purchase the software.
    The last resort is a professional data recovery service that will offer NO guarantees and charge a lot of money.
    As you now can appreciate, backups eliminate such predicaments.
    Ciao.

  • All of my apps on my new ipad2 are not working. I had this iPad about 4 months and nothing bad has happened before this. I need help on how to make my apps stop crashing. All my built in apps are fine though.

    All of my apps on my new ipad2 are not working. I had this iPad about 4 months and nothing bad has happened before this. I need help on how to make my apps stop crashing. All my built in apps are fine though. WHATBCAN I DO TO MAKE MY APPS STOP CRASHING. I ALREADY TURNED IT OFF THEN ON AGAIN AN IT STILL CRASHES. HELPPP!!!!

    Try a reset. Hold the Sleep and Home button down for about 10 seconds until you see the Apple logo. Ignore the red slider.

  • Migration of Standard Classic Badi to New Badi

    hi,
    Is it mandatory to migrate all standard classic badi's to New badi's in ECC6.0. I have read in the documentation only custom BADi's should be migrated.
    Can we migrate Standard Classic badi's to New badi's, please provide the procedure for this.
    when i am trying to do this in one way it is not allowing me to use the same class as classic badi used, so i have created custom class for this. Is it going to effect.

    Hi Phanindra,
    Calling New badi's is much faster than calling clasic badi's. SAP never recommends to convert all classic Badi's to New Badi's rather you convert your own Badi's to New Badi's. You cant convert SAP classical BADI to New Badi. if you want to convert custom Badi, then please go through this below link
    http://help.sap.com/saphelp_nw70/helpdata/EN/0e/4d3e42fc94aa04e10000000a1550b0/content.htm
    Thanks,
    Bishnu Dash

  • Pc went bad and need to recover items on a new computer

    My itunes were on a pc that suddenly went bad and I need to recover what I had on a new computer.

    Remove the hard drive from your old computer, put it in an external enclosure, plug it into your new computer, and use Windows Explorer to navigate the drive.  Look in Documents and Settings/Users/YourName/Music/iTunes Music, or Library/Music/iTunes Music depending on the OS on your old PC.  You'll likely find most of it is intact, but some files may be corrupted, and unrecoverable.  Now that you have an enclosure, buy a new hard drive to put in it, and make a backup!

  • I need a new iphone and I've found a fully refurbished iphone 5. Is it a bad idea to get this phone seeing as they are no longer in production? Will it still get updates?

    I need a new iphone and I've found a fully refurbished iphone 5 for a competitive price. Is it a bad idea to get this phone seeing as they are no longer in production? Will it still get updates?
    Or is it worth buying the iphone 5c?

    Hi I would buy the iPhone 5s look on EBay make sure the ICloud Lock has been removed Get the 32G one buy one with the box and from someone who has good feedback. Also look at Refurbished IPhones on Apple Website. Cheers Brian

  • I need to create a Classic BADI definition in an ECC 6.0 Environment

    Greetings all,
    Let me start by saying that I work in a corporation with many SAP landscapes at various versions (4.7, ecc 6 etc.)  We have an application developed in an ECC 6.0 environment which needs to be pushed down to some 4.7 environments.  This development needs some BADIs defined to give the receiving systems some flexibility.  Here comes the problem, 4.7 cannot handle New BADIs and ECC 6.0 will not allow me to create Classic BADI definitions.  I've searched through notes to see if there is some kind of quick fix and I have not found any.  So I appeal to you the enhancement forum.  Is there a note?  How else can I create something and give the non original systems the flexibility needed?
    Thank You

    Yes Michelle, you are misunderstanding.  I am the Definer of the BADI, not the implementer.  I am setting up the hook in the program.  One can still implement a classic BADI in SE19 in ECC 6.0.  What we are prevented from doing is defining a new Classic BADI.  We are forced to define new BADIs.
    Try this:  Go to SE18, select BADI name and put in Ztestjunk.  Now hit the create button:
    Here is the error message you will get:
    "Create" operation is possible only for enhancement spots
    Message no. ENHANCEMENT269
    Diagnosis
    You wish to create a BAdI definition on the initial screen of the BAdI Builder.
    System Response
    It is not possible to directly create a BAdI definition. The BAdI definition can only be created as part of an enhancement spot.
    Procedure
    Either create an enhancement spot or process an enhancement spot that already exists. There you can create BAdI definitions as part of the enhancement spot.

  • Classic BADi not being called

    Hello Experts... Your kind and expert advice is deeply appreciated...
    We had implemented a BADi in CRM4.0 and that is being called and working alright.
    We are now upgrading CRM4.0 to CRM7.0. With this change classic BADis is not being called.
    Difference I noticed in calling program is that in CRM 4.0 BADIs were pulled/instantiated by factory method. However in CRM 7.0 it uses "GET BADI" command. But since "GET BADI" does not fetch implemented BADi, it throws BADI not found exception.
    - I searched and learnt that "Get BADI" can fetch classic BADIs and there is no need to migrate classic BADIs to new BADIs ...(if I am not wrong)..
    - Also that I re-activated classic BADi in CRM 7.0 but still "Get BADI" does not pulled/instantiate BADi.
    - Also I search to have report "ENH_BADI_ADD_MIGR_INFO" run to create link between Classic and new BADi. Will this work?
    Kindly advice to call classic BADi in CRM 7.0? Appreciate it. Thanks!
    Warm Regards,
    Kalpit

    Hi,
    Check if this BADI is migrated to enhancement spot (In attributes TAB). If yes, you need create an enhancement implementation for
    this BADI.
    Thanks,
    SKJ

Maybe you are looking for