Make your settings in the following IMG activities:
1. Create accrual types for the RE-FX component in: Define Accrual Types
2. Enter an accounting principle for the RE-FX component in: Define Customer Settings for Components
3. You have to enter a standard accrual method in: Define Standard Settings for Accrual Calculation. Since the accrual objects are created automatically, the accrual method you enter here is adopted.
4. In Customizing for Flexible Real Estate Management, assign the necessary accrual types from the Accrual Engine to the flow types for which accruals/deferrals are posted. Choose:
SAP Customizing Implementation Guide ® Flexible Real Estate Management (Enterprise Extension) --> Conditions and Flows --> Flow Types --> Define Flow Types
5. You created the accrual types for accruals and deferrals for the RE-FX component:
SAP Customizing Implementation Guide-->exible Real Estate Management (Enterprise Extension)-->Accounting -->rual/Deferral -->Accrual/Deferral -->rual/Deferral Posting ---> Account Determination---> Simple Account Determination -->Define Set of Rules
a. Here you entered the document type for each accrual type.
b. You entered the accounts for the given accrual type.
Real Estate Accrual Defferal Configuration
SAP - FI AR BK: Electronic Bank Reconciliation
Each uploaded electronic bank statement will be assigned with a unique no. in SAP and can be printed retrospectively.
1. Electronic Bank Statement file (in SWIFT MT940 format) is extracted from BANK
2. Data (SWIFT MT940 for BANK) is imported into a temporary dataset in SAP
3. Batch input sessions are generated (per bank statement: one session for G/L Accounting and one for Subledgers- AR/ AP). Bank accounting and subledger accounting batch session can be executed separately or jointly
4. Posting rules and account determination are defined in TR-CM customization
5. As an electronic bank statement is being imported, the system identifies the transactions in it and determines how they are posted.
6. The note-to-payee fields in the electronic bank statement contain various information relevant to open item clearing. Note to payee fields can be interpreted by document number or reference document number for the clearing transaction (example: standard algorithm). If the algorithms we deliver are not sufficient, it is possible to program a user exit tailored to your business (e.g. change the posting rule; influence account determination by means of account modification).
7. Post-processing for posting proposals(line items) which cannot be cleared
Note:
Electronic Bank Statement format SWIFT MT940 is compactable with SAP TR-CM. Standard algorithm for clearing documents is available in the predefined form in SAP. Customisation, as stated in point 6 above, will be needed to cope with AAA specific requirements on Bank Reconciliation. The review task will be performed on the Detail Design Phase, detail of which will be incorporated into the respective customisation functional specifications.
Intercompany transactions in SAP AP / AR : Cross Company Code Transaction
Several companies are involved in an intercompany transaction. The system will post a separate document with its own document number in each of the company codes. A common cross-company code number links individual documents together. The system generates line items automatically (receivables and payables arising between company codes) in order to balance the debits and credits in each document.
Company One
Dr. Expense / Balance Sheet account for Company One
Company Two
DR. Intercompany AR
CR. Expenses / Balance Sheet account for Company Two
Each branch will have different general accounts for AP and AR to separately identify there debits and credits.
This transaction will only be finance related. Intercompany posting in Logistics will be posted in the system automatically.
The process for posting intercompany transactions is as follows:
1. The initial entry is parked.
2. Then an email is sent to the other branch to view the document.
3. On approval of the transaction, the parked document is then posted to the g/l in both companies. The company receiving the revenue will be the one responsible to book into system using the US dollar as base currency.
SAP: Inflation accounting for Fixed Assets
Asset Accounting
The method offer by SAP by execute Inflation Accounting or Revaluation of Fixed assets consist in the calculation of the Fixed Asset trough INPC index or any other index defined.
This solution is developed to countries with a high inflation index where is necessary adjusting the Inflation over fixed assets periodically as a part of the close activities.
It can be used the INPC index disclosed or any other index depending of the enterprise necessities , it means apply the values in points or percentages, these can be applied in the same way over all fixed assets.
Update Inflation Indexes
Use
The system includes inflation indexes like model to different version of country.
These indexes can be used, but in this case is necessary modified inflation indexes. This model can be used like a basis to create the new ones.
In the end this procedure consists in update month by month, before execute the process of the revaluation.
This index can be provisional or definitive but always must to be store; in the other hand the system doesn't carry out any calculation.
Is possible to update provisional or definitive value by an index. The update of the provisional values could be optional; it depends of the inflation requisites. In Mexico the index used is INPC ("Indice Nacional de precios al Consumo"). The value for the present month is know at the beginning of the next month, sometimes could be necessary to carry out the revaluation with an estimate index for later do the process with a definitive index.
When an index is created by first time is necessary to indicate the index value of first date and the last one. The system needs this information in order to do the calculation for the net inflation.
SAP : Problem with Material Ledger and ICP
I have a Russia based client where by it is decided to implement actual
costing and material ledger for dual valuations. I am facing a related
problem that I cannot find the answer on.
Situation
Now in Material Ledger, in Russia we have an obligation to valuate all
extra costs on stock. In a cost of goods flow with third parties, it seems
that we have no issues with the material ledger. But in a flow where we
procure goods from our own factories in Europe – the agreement is that the
Russian M&S unit pays the cost price + 5% ICP to the factory.
Problem
It seems that the 5% ICP markup on the cost price doesn't get reflected in
the material ledger – and hence will not be consider when we run the final
closing entry for actual costing which valuates the stock at periodic unit
price. For example, if at GR goods receipt of PO xxxxxxx the system only
posts 5500 RUB which is 55 RUB / EUR * 100 EUR. Whereas I want to post 5500
* 1.05 = 5775 RUB to the material ledger.
I tried to create accruals / condition type ZA13 in the MM calculation
schema to influence the costprice with some success, but that affected the
way the system accrues for ICP. So I want to post the ICP to the material
ledger, whereas at the same time in the goods receipt I want to post the
normal posting schema for US GAAP which is:
| Debit | Credit |
| Stock recon acct - Stock qty * Std | GRIR acct - Net purchase price + ICP |
| price US GAAP | 5% of net purchase price |
| ICP to pay account – 5% of net | Price diff acct - Price difference |
| purchase price | between standard price and net |
| purchase price |
Kindly provide suggestions based on your expertise if some one has exposure
to Material Ledger.
We encountered a similar situation with our client. Ours is a US based
client that procures Slab/Raw Material from its Trading Company in
Brazil . As per the agreement with the Trading Company, Inventory is
supposed to valued at Market Price (Cost + MarkUp) though the Standard
Cost ( SC) should reflect only the Material Cost will remains the fixed
for one financial year.
We created Info Record for the Slab which excludes Mark Up .The PO's
Base Condition (PB00) (copied from Info Record ) includes Markup . Hence
when GR is executed , the difference btw SC and PB00 hit the Price
Difference Account (PD) to be part of ML .As a part Month End Activity,
the PD is considered for Inventory Revaluation and Periodic Price
Calculation-
Below is small example to illustrate the flow:-
Material Management Info Record
PB00 - $ 600
ZMUP -$(150)
Cost Roll Up(CK11N)
SCE - $ 450
PO -XXXX
PB00- $600
Good Receipt Documents
FI
Dr Inventory Ac - $ 450
Dr Price Difference - $150 -This gets captured in ML , considered for Inv Revaluation n Periodic Unit Price Calculation in AC.
Cr GRIR Clearing - $600
New GL with UPGRADE : SAP ECC 6.0
I know SAP recommends that new GL migration and implementation should be done after upgrade and migration on the 1st day of new fiscal year.
If any of you have come across such situation please share your experience with me.
The main risks for a migration project are related to a lack of understanding of the new G/L functionality. Members of the migration project team (client) may continue to think in classic G/L terms which can lead to new functionality such as document splitting for example either being excluded from the migration when it would be beneficial, or the document splitting producing inaccurate results. Also, without a full understanding of the new G/L functionality existing functionality such as special ledgers for example may be set up in the new G/L when they are no longer needed. This can lead to issues with data and decreased performance. Other potential problems that can be caused by a lack of understanding of the new G/L functionality include:
• Unsure what to use for segments
• Confusion about parallel ledgers
• Creating too many nonleading ledgers
• Not fully understanding document splitting (need or not)
Another significant risk is the amount of data cleansing that is required before the existing data can be migrated. For a migration with document splitting, open items on G/L accounts are time consuming to migrate and the more that can be cleared before, the better.
Other risks include the time required to test and also the time required to ensure that existing interfaces still work as expected. Many migration projects underestimate the time required for these, which can lead to problems in meeting project deadlines.
Therefore: Due to the many influencing factor, there is no general answer to the question of how successful & how long a New GL Migration Project should last. Migrating to the new G/L is complex and the data is highly sensitive, so a full project is necessary. Data cleansing is a significant part of G/L migration or conversion. Deleting G/L accounts that are not required, consolidating accounts, and clearing open items on open item managed accounts are all good examples of tasks that can be started well in advance of a future migration.
Migration to ECC 6.0: Data Consistency Check in the Classic General Before Migration Check
Proceed as follows:
1) Program RFINDEX
In the first run, choose "Documents vs Indexes" in the selection screen.
In the second run, choose "Indexes vs Documents" in the selection screen.
2) Program SAPF190
Run program SAPF190 for the fiscal year prior to the migration and for the fiscal year in which the migration takes place.
If you use Asset Accounting, run program RAABST02.
4) Program RCOPCA44
If you use Profit Center Accounting, run the program RCOPCA44 for a ledger comparison. Important: You cannot use the
transaction code SE38 to start the ledger comparison. Instead, you must use KE5T (this is the simplest method).
SAP : Hedge Management
- You can designate hedging relationships in accordance with IAS 39.
- Hedge Management also contains a prospective effectiveness test that simulates the future effectiveness of hedges by using the market data shift method.
- The component responds automatically to transactions in financial position management and, if appropriate, triggers the dissolution of a hedge.
- In the function for the management of hedging relationships in the IAS hedge category fair value hedge, you can create n:m relationships in order to map complete hedges or partial hedges (micro hedges).
- Hedge Management also contains functions for managing macro cash flow hedging relationships, using either the classical or the hypothetical derivative approach, and portfolio fair value hedges.
Legal Change:- WHT India Tax rate Changes from 1/10/2009
Legal Change (Budget July 2009) for India related to Tax Deducted at Source (TDS) - Tax Rate Changes with effect from 1st October, 2009
| Section | Rate Type | Old Rate(%) | New Rate(%) |
| 194A | 1-Standard | 20 | 10 |
| 194A | 7-Custom or Reduced | 20 | 10 |
| 194C | 4-SubContract | 1 | 2 |
| 194D | 1-Standard | 20 | 10 |
| 194I | 7-Custom or Reduced | 15 | 2 |
| 194I | 6-Rent: Land/Buil/Fur | 15 | 2 |
Delete / Supress field "Sample account" when creating a GL account
I would like to hide or deactivate the following field "sample document" that appears in the master record of a GL account. I have been watching the transactions OBC4 and OBD4, but they are not valid in order to do that.
Please delete any sample accounts existing in that particular chart of accounts using transaction FSM5 and save.
Now check sample account filed will be no more appearing in that particular chart of accounts data.
If you once again want to populate the sample account field you can create a sample account using transaction FSM1.
Down Payment Request Reversal
I have created down payment request for 1000$ for one vendor. then when i go to FBL1N and execute it with only noted item selection, it show me credit balance of 1000$ and red dot which i expected, since it is not cleared.
but later on i reversed the down payment request and executed FBL1N with noted item tab and again it shows me 1000$ credit balance with green dot cleared, which i expected but why would it still show me $1000 credit balance.
even though i have reversed it, it is showing me credit balance, rather it should show me zero balance.
Yes, at first look that is weird. But, if you run FK10N, you will see there this amount won't appear. I believe because there it doesn't consider the Noted items.
Also, if you reversed the noted item with FB08, you will see the reverse document is in fact a clearing document without items. As the noted item is not, in fact, an accounting document (because it doesn't have Debits and Credits)
Transfer of Legacy Asset details !!!
| Transactions | |
| Create | AS91, AS94, AS81, AS84 |
| Change | AS92, AS82 |
| Display | AS93, AS83 |
| Delete | AS06 |
| Reports / Programs | |
| Reports on transferred data | RABEST01, RABEST_ALV01 |
| Deletion program for mass data | Reset company code, transaction OABL, deletes all assets in a company code |
| Tables / Databases | |
| Relevant tables | ANLH, ANLA, ANLZ, ANLV, ANLB, ANLC, ANEK, ANEP, ANEA |
Calculation of Depreciation for Tax for India
But if the asset has been acquired on 01/10/2009, still the asset has to be depreciated from 01/04/2009, since the asset has been acquired for less than 180 days into the fiscal year. The system is working fine for asset capitalized on 25/09/2009 and 07/10/2009. But we are not able to map the same if asset is capitalized on 01/10/2009 and 02/10/2009. For these two dates, the depreciation should start from 01/04/2009.
I have checked the period control setting and calender assignments and everything seems to be in place. How can we tackle the issue?
Sending Dunning Letters By E-Mail
Additional documentation on user exit EXIT_SAPF150D_001 can be reviewed via trans CMOD.
Please use the following steps to review:
1) Run trans CMOD.
2) Select Utilities -> SAP enhancements; increase the max. number of hits to 1,000, press execute.
3) Double click on f150d001 (Indiv. customer exits in prog. for printing dunning notices).
4) Click on EXIT_SAPF150D_001 and Goto > Documentation
The following conditions apply to sending dunning notices by e-mail:
1) You cannot usually dun one-time accounts by e-mail (although you can print out the dunning notices for these accounts).
2) You must store an e-mail address in vendor/customer master records.
3) You must use transaction SCOM to configure the dunning program for e-mail.
4) The following fields in structure FINAA (data on the transmission medium for correspondence) must contain the correct entries in the user exit, as detailed below:
a. FINAA-NACHA = 'I' (1 = output on printer, 2 = send by fax, I = send by e-mail)
b. FINAA-INTAD = e-mail address - FINAA-TEXTF = text format (PDF or ASCII)
c. In transaction SCOT: Setting -> Conversion Rules make an entry: RAW to TXT SX_OBJECT_CONVERT_RAW_TXT
5) In addition, please check some notes that you should review below:
a. 455127 E-mail (SMTP) in different SAP releases
b. 171698 SAPconnect: Formats, conversion, device type - Documentation on configuring SAPconnect is contained in the SAP Online Help under: SAP Library > BC - Basis (up to 4.6), or SAP Web Application Server (as of 5.0) > Basis Services / Communication Interfaces (BC-SRV) > Communication Interface (BC-SRV-COM) > SAPconnect (BC-SRV-COM)
c. Note 171698 explains formats & conversion rules.
I suggest that you should configure SAPconnect to handle simple messages from SAPoffice before you consider the faxing & emailing from other applications.
Note 0455127 has some useful general information on email. Technically this falls under consulting. Currently the standard does not support an email output of dunning notices to more than one email address. If you want to send the mail to several recipients, fill the field FINAA-INTAD with the mail addresses and separate each address with a blank character. There are a total of 130 characters available in FINAA-INTAD.
Note 1042992 should guide you throught this.
Variances due to sales and administration costs
But for production purpose, we dont need that kind of costing sheet. If you have that kind of then you will have problems like you said.
The suggested method is,
1. have one costing sheet with admin and selling costs so that you can simulate the costs for managerial decision purpose
2. Have another costing sheet with admin and selling costs for production purpose
CATT: Computer Aided Testing Tool
TCODE-SCAT : Computer Aided Testing Tool
Used to upload the data, test data. This is very easy procedure compare to other upload tools.