Badi: Fagl_3keh_defprctr

Hi friends:
After so lonng time, i am visiting You.
There is a small doubt on Badi which is provided by SAP.
Badi name: Fagl_3keh_defprctr.
The above badi is not workig in SE19 or Se18.
Can you explain me why?
Because i am excuting the intreset calculation for Fixded deposits(f.44).
After excuting the above t.code system will display one accouting entry i,e
Fixed deposits DR
To Intrest received.
For the second line item is cost element so system is picking the profit center.
For the first line item system is not able to pick the profit center. because that is a vendor.
Please explain me the above problem.

Hi,
First of all am sorry as I am not able to provide a solution to ur problem.
Will u plz provide me why BDEs is been used?
And how shall I get the available BDEs in a particular T code.
Thanks & Regards,
Abhi.

Similar Messages

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.

User Exit with call up after document splitting in New GL.

Hello,
I am looking for a user exit which is called up after document splitting and before final posting to FI. We are implementing Ecc 6.0 and wish to change functional area on gl line item based on values in cost center. However, this change/redetermination of functional area also needs to be done on documents which have been split. Splitting is at profit center level.
Regards
Jayesh.

Hi Gordon,
Yes, by a little piece of ABAP.
I have created a Z table and configured by co.code and document type. Add a little bit of code in the badi FAGL_3KEH_DEFPRCTR.
Hope it helps.
Thanks,
Srini

Impact on profit ctr after activation of New GL

Hi,
I would like to know,what is the impact on profit ctr after activation of New GL?
Thanks in advance
Prasad

The following OSS note will be of some help in addition to online help documentation
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.
Header Data
Release Status: Released for Customer
Released on: 10.09.2007 10:54:03
Priority: Recommendations/additional info
Category: Consulting
Primary Component: EC-PCA Profit Center Accounting
Secondary Components: FI-GL General Ledger Accounting
Releases
Release Independant
Related Notes
1087350 - NewGL: Reading partner profit center in reversal
1018065 - NewGL: activating "segmentation" scenario
997925 - Read partner profit center in NewGL
966000 - mySAP new general ledger and Joint Venture Accounting
937872 - NewGL: internal revenues between profit centers
895923 - Active indicator of PCA in CO-PA derivation
853169 - ALLOCATION: Actual cycles can only be executed periodically
820121 - Document splitting does not work for segment
764841 - No profit center derivation for active flexible GL
756146 - mySAP ERP new General Ledger: General information
741821 - Release limitations concerning SAP ERP 2004
217338 - Number of profit centers
Print Selected Notes (PDF)

BADI for changing fields during Creation of BP in CRM

Hello to everyone,
I need to find a BADI (or other way) to default several fields during BP creation in CRM (4.0 SR1 SP9). The fields I will like to set are TAX TYPE, TAX NUMBER, TAX CATEGORY, etc.. I have found the BADI BUPA_TAX_UPDATE but i dont see any suitable parameters (structures) to changes these fields. Please advice and thanks in advance.

Hi
If you use function BUPA_NUMBERS_GET then your BP number will already be buffered and you can avoid a DB read. It may also be that the BP is not in the DB yet anyway.
You can only pass one GUID in at a time - loop through IT_CHANGED_INSTANCES into a variable of type BU_PARTNER_GUID and pass that into the function as input parameter IV_PARTNER_GUID.
Cheers
Dom

Implementing BADI MD_ADD_COL_EZPS for MD04 custom column

Hi there,
I'm using BADI MD_ADD_COL_EZPS to display 3 new buttons and three new columns in MD04.
For each line item that is displayed, the custom column is filled, after the button is hit -This works fine.
My Question is:
Is there any way to limit the value that is filled into the new column so that it only appears on the FIRST line item/row?
(At the moment it is repeated all the way down the page - the new value is a material characteristic, so doesn't change, will always be the same for each line)
I've looked at all the available structures/tables in the FILL_ADD_COLUMNS method of the BADI, and none seem suitable
to determine the "first" row. (ie. something like the way SY-TABIX or SY-INDEX might be used)
Any help appreciated.
Thanks,
David.

Hi Shubhendu,
in the method 'ACTIVATE_ADD_COLUMNS', you can set the flag EZ1_MODE to '1' to make the first column visible always. (it's been a while, but I think setting it to '2' makes it visible when the button is pressed.)
Same applies to EZ2_MODE for second column, EZ3_MODE for third.
look at the flags/parameters in this method, and also in FILL_ADD_COLUMNS, to fill the data.
here you need to fill structure EMDEZX_USEX1 (for column 1) etc.
The code is hit for each record displayed in MD04
Hopefully this helps you.
Regards,
David

Help Needed Badly | BlackBerry INC000025111306 | BlackBerry PlayBook - Tablet button does not work, almost stuck, copper under screen, seventh repair

I was really Humilitated my RIM on this Ticket whcih i rasied.
1) I bought a new tablet in last november in 2 months i had a Charger issue
2) They said this charger issue we cannot replace with new tablet and gave me a refurbished Tablet to me .
3) Which also had same charging issue and they exchanged 2 more tablets and the last tablet which was given to me by RIM have a safety concern
- 1 Small mesh of wire is poping out from the Tablet
- Power Button is very hard and its not that easy to press,
So i raised the above ticket and was esclated internally with RMA as well and i got an update from the esclation agents that we will reply back in 2 Days i waited almost 3 weeks and called 2 times in this 3 weeks for an Update asking for a new tablet so that atleast once in all i can jeep a good 1 Tablet.
But they never bothered to call me and today i called them again and RIM gave me a call back mentioning we cannot give a new tablet we can again check this tablet repair it and give it back , If we cannot repir then give a replacement new/Old tablet,
I was wondering how can a tablet from RIM can go out without such safety concern ? How a mesh of wire can comeout of tablet so what safety norms RIM is follwoing for customer.
AM i not humilitated? since after taking all these struggle tto get a good tablet i have been considered as bad.
What RIM have to say for this, I am planing to take this to Legal department to follow how i can get a justice for this.

I would have deleted this but can't find a delete?
At any rate. got the Blackberry going again but it reset it and lost all the info, pictures and so forth.. oh well. at least it is still working.
Thanks.

Error message in a BADI getting displayed in a popup instead of status bar

Hello All,
I have implemented a BADI in ECC6 to prevent the change of formula in ERP from transaction O3I8.
The BADI gets called on clicking 'Save' from transaction o3I8.
Within the BADI i am giving an error message using the following command:
Message e000(ZABC) .
However , the message gets displayed in a pop up instead of the status bar .
The same is for information and warning messages.
Any suggestions on how to display them in the status bar ?
TIA
Regards,
Vartika

Hi Brad,
The checkbox to display messages in pop-up is already switched off.
Still themessages are getting displayed in pop-up.
Regards,
Vartika

Error message from a BAD PDF

I am using Adobe Reader to render PDF documents as a part of a process and then convert it into TIFF. Some of the documents that come in are corrupt PDF documents and cannot render itself in the reader and hence cannot be converted. This is the error that the reader throws:
ADobe reader could not open "test.PDF" because it is either not a supported file type or because the file has been damaged(for example, it was sent as an email attachment and wasn't correctly decoded)
Now, the process is automated with no human intervention. with the advent of this error message, since there is a modal dialog box waiting for a response from the user, the process is interrupted and needs human intervention.
My question is simply this. Is there an API i could use where i can figure out beforehand if the PDF is bad so i can reject such files early on? research shows that using the adobe forms server which has the PDF utility services, there is a query "Is a PDF document" that is available. I do not want to use a server product.
Is there any other ADOBE product that exposes something similar?

I guess i forgot to add that piece of information. WE do not create the PDFs. We receive PDFs from external sources over which we have absolutely no control and that explains why we get such corrupt documents in the first place. I was just wondering if there was a simple API event/method/means attached to any ADOBE product which is compatible with .net that tells me if the PDF is corrupt UPFRONT.

Error while transporting infospoke with BADI in BW7.0

Hi:
We have an infospoke with Transformation ( ie with BADI) in BI7.0.
While transporting to Quality box it gives error.
"Transfer structure /BIC/CZZTXXXXX3 could not be generated
Error when activating InfoSpoke ZTXXXXX3.
Message no. RSOH010 "
Could you please help in rectifying the error.
PS: we tried transporting BADI first and then the infosoke but still its failing.
Regards!
Saniya

Hi
Check the forum link below
Transport Problems with Spokes that have BADIs
Thanks

IPod can no longer sync or charge, bad pin connectors?

I've got an iPod touch thats a year old now that suddenly no longer will charge/sync to anything. I'm thinking maybe the pins are bad?
I've had difficulty inserting chargers into it since I got it, I've been careful to not handle it too roughly but it does take a strong push to get the charger in there. Of all the ipods I've had (and i had the first gen iPod touch before this too) over the years, never had that problem.
Before I get a bunch of "just reset it" kinds of replies, it is functioning properly other then that. Last night I did have it hooked up and synced to my Mac so it fully charged, but just now I went to connect it and now it refuses to connect at all. I've tried 2 cords, and with the same cords I plugged my iPhone in as well and it all worked fine, so it's definitely not my other hardware. iPod software is also up to date as well.
I haven't had a real issue of it not syncing with my computer before today, but in the past month it's had issues staying properly synced to my car radio (play it through USB). It would sometimes drop off or glitch up and not want to work correctly, though in the past week it started working more normally again.
I listen to my ipod as much as humanly possibly, so I'm wondering if this something I can take to the Apple Store and see if its fixable or replaceable. I've been looking for a great excuse to get the new red ipod touch but I've been unemployed since August.. Of course it has to break before I get a new job
Has anyone else had the issue of having difficulty getting the sync cords into their ipod touches/problems where the pins just die?
EDIT: Nevermind. My imac suddenly wont sync my iphone either but I plugged the ipod into the iphone charger and it synced immediately. It's something on my computer's end.
Message was edited by: Arei

*all the songs are there, but there are shown in light grey and not able to be high lighted.*
*I'm also not able to play from my ipod list, only from my itunes??*
Grey text when you look at the content and a lock symbol at the bottom of the screen just indicates that the iPod is set to sync automatically with iTunes. If you want to play the iPod songs through iTunes, delete songs from the iPod, drag songs from iTunes, add playlists to the iPod etc. you need to change the update setting to "manually manage songs and videos" as per the link above. The text will change from grey to black and everything will be directly accessible through iTunes
*I have seen a friend plug his ipod into some one elses computer and the same thing happened, it showed all the content but he was not able to access it, or modify it.*
Again that's most likely because the iPod was set to auto-sync with his home library. If you want to connect and use an iPod on more than one computer or with more than one library you need to change the update preference in the iPod Summary tab to "Manually manage music and videos" and click Apply. The content of iTunes and the iPod are not syncronised in this mode so the two can be different. You can directly access the content of the iPod and play it through iTunes and you can drag and drop whatever you want to the iPod from either library:
Using iPod with Multiple computers
*Before I backed up my itunes libary from my external hard drive, and itunes was empty, it would not allow itunes to be copyied from my ipod?*
iTunes will only give you the option to copy your iTunes Store purchases directly from an iPod to the computer, you'll find details in this article: Copying iTunes Store purchases from your iPod or iPhone to a computer
For everything else (music from CDs, other downloads etc) there are third party utilities that you can use to retrieve the music files and playlists from your iPod.

IPod Touch 5.1.1 no longer sync'ing w/ iTunes 11.1.3(8). . . .Bad Battery ???

Three day ago my iPod began acting up in a major way. The battery charging symbol within the battery indicator is no longer showing the iPod being charged when plug in to my MacBook Pro 5.1 via one of my two USB ports. A new Apple iPod cable was purchased thinking it was a bad wire or pin not making the proper contact with this device. The same conditions are happening with this new cable. I have several other peripheral devices and those devices are working and are connecting to my MBP's USB port without any issues. I have noticed for the past six months my iPod Touch 3rd Gen has been showing signs in needing longer charging times and seems to drain quicker than it used too. The iPod for the past two nights have been charging for more than eight-hours each night and is sporadic as if it deciding "I'm I fully or 30% charged?" Although subtle, It seems to jump within the sliding battery scale when the device is powered off for a while. Sometime showing 80% charged when used for a few hours to 30% charged when used for ten minutes. My iPod is now over three-years old and I think it is time for a new battery!
But, in all honesty, not sync'ing with iTunes is it more than just have a new battery professionally installed? Or are there other electronical problems/components going bad with these devices? What else can be wrong other than a new battery or will a new battery fix all what is mentioned above? Please be very honest and technical if needed, Thanks!

Apple will exchange your iPod for a refurbished one with a new battery for $79. They do not fix yours.
Apple - iPod Repair price
A third-party place like the following will replace the bttery for less. Google for more.
iPhone Repair, Service & Parts: iPod Touch, iPad, MacBook Pro Screens
Replace the battery yourself if you are up to it. You can purchase a replacement battery for about $10
iPod Touch Repair – iFixit

Reg. Exit/BADI for changing item data of PO in ME22N

Hi all,
My requirement is to update the field LABNR (Order Ack.) of few specific line items of a PO, in the Transaction ME22N, using Exit/BADI.
I have tried the BADI ME_PROCESS_PO_CUST. But the PROCESS_ITEM method of this BADI processes only the line item which has been changed/inserted in ME22N transaction. But my requirement is to update line items irrespective of whether that line item was "changed/not changed" during the process in ME22N screen.
Could you please suggest me some suitable Exit/BADI for this requirement.
Regards,
Anbarasan K

Thanks Martin.
Problem solved by implementing the method Process_Header.
1. Get the items from Header                              - im_header->get_items
2. Loop the item list and get the line item record   - re_item-item->get_data
3. <- Logic to Update the line item - >.
4. Update the line item                                       - re_item-item->set_data
Thank you very much.. Martin.
Regards,
Anbarasan K

User Exit/ Badi for Changing Quant parameters during TO Creation

Hi Gurus,
Could you please guide me to advice the User Exit/Badi which can be used for changing Quant Data during TO Creation.
User Requirement: Using "Recepient Field" in MIGO as a Key Value for FIFO in WM during goods issue. Receipient is copied into TR and TO (Standard SAP Functionality). For the purpose of Stock Removal based on Receipient Value, we need to copy this value into Quant Data field named Certificate Number ("LQUA-ZEUGN").
I will highly appreciate reply from Gurus.
Regards,
Gupta M

Hi manish,
Use the Exit MWMTO001 for this purpose and modify the table accordingly. This will solve your problem.
Thanks,
Shibashis

FM Call in BADI during replication of BP from R/3 to CRM causes problem

Hello all;
I am trying to change the BPKIND of the partner in CRM which is created in R/3 with the PARTNER_UPDATE BADI. But the FM called in the BADI causes the BP hang in SMW01 with intermediate state. May you please advice me somthing about this?
METHOD if_ex_partner_update~change_before_update.
DATA: lt_but000_old           TYPE STANDARD TABLE OF but000,
         lt_but000_new           TYPE STANDARD TABLE OF but000,
         ls_but000_new           TYPE LINE OF bup_but000_t,
         lv_objnr                TYPE crmt_object_guid.
CHECK sy-uname = 'ERP_RFC'.
CALL FUNCTION 'BUPA_GENERAL_CALLBACK'
    TABLES
      et_but000_old = lt_but000_old
      et_but000_new = lt_but000_new
    EXCEPTIONS
      OTHERS        = 0.
READ TABLE lt_but000_new INTO ls_but000_new INDEX 1.
ls_but000_new-bpkind = '0001'.
REFRESH lt_but000_new.
APPEND ls_but000_new TO lt_but000_new.
INSERT but000 FROM TABLE lt_but000_new.
* CALL FUNCTION 'ZBBP_BUP_UPDATE'
**    TABLES
**      t_but000 = partner_attrib.
ENDMETHOD.

Kindly check the partner function whether that partner function of customer in ECC, is defined in CRM. If it is not defined then it will not copy to IBase while data transfer.
Reward points if helpful.

Badi: Fagl_3keh_defprctr

Similar Messages

Maybe you are looking for