SAP FICO

SAP RE FX: Contract not called in RERAPP transaction !!!

2011-10-11T08:27:00.001-07:00

Find the list of reasons why contract not processed during the period processing (TCODE: RERAPP):

1. Contract might be not activated - Check the System Status & User Status.

2. Real Estae Object might be not activated - Check the System Status & User Status.

3. Posting Parameters - tab shows the Frequency if you are running out of the frequency check this.

4. Term - tab Check the Contract start date & 1st Posting date

5. In the Terms tab of your contract , check field "Cash flow start date". Based on this date the system generates(plans) cash flow which gets posted by RERAPP.

6. In the RERAPP screen due date field by default shows <= symbol, means any cash flow planned before or on the date given should be posted. I would suggest to select a later "Due Date", for example "Contract End Date" and see if the syste generates any postings for futute period.

7. Authorization failure also an issue for not calling the contract.

SAP FI: Payment Terms Set Up Example

2011-05-26T05:02:00.001-07:00

Payment Terms Issue :

Payment term to be set up as below:

70 days, days of payment 15 and 30

Example:

Date invoice: 01/05/2011 Due date: 15/07/2011
Date invoice: 10/05/2011 Due date: 30/07/2011

SOLUTION:

We have created 3 payment terms with the day limit as 6, 21 and 31.

In the 'payment term' field of OBB8, we have input:

Payment term  Fixed date  Additional months
ZTE6-6            15              2
ZTE6-21          30              2
ZTE6-31          15              3

Required URJENTLY SAP Certified (FICO/SD/MM/PP) or 1 year experience in SAP Implementation / Support

2011-05-10T03:43:00.001-07:00

SAP Hirings only in Bangalore for Bangalore on 14 MAY 2011

Please do not forward candidates who are in other locations - if they are willing to travel on their own and only if they meet the below needs please forward.

so why wait, Start forwarding now !!! Please read the requirement and eligibility criteria below :-

Forward your CV who has about 4 to 8 years of experience in their respective domains and also is a SAP Certified professional OR has Minimum of 1 year experience in SAP implementation/support in the following skills: The fast track batches are open only for SD/MM/PP/HR/FICO.

Please send their resumes to sap.vvr@gmail.com before Friday.

SAP AP: F110 Automatic Payment Run : Tables

2011-03-15T02:22:00.001-07:00

Payment Run relevant tables:
FEDIWF1	FI EDI: Person with signing authority
OPN_J1	Japanese DME Foreign Payment Accounting Data (Open FI)
PNBK	Prenotification: New bank data from master records
PNHD	Prenotification: Files created in ACH format
PYONUMKR	Auxiliary structure for lock object EPYONUMKR
PYORDH	Payment order header data
PYORDP	Payment order item data
REGUA	Change of payment proposals: user and time
REGUH	Settlement data from payment program
REGUHH	REGUH version before the 'n'th change
REGUHM	Payment Data for Cross-Payment Run Payment Medium
REGUHO	REGUH version before the 'n'th change
REGUP	Processed items from payment program
REGUP_CORE	Processed Items from Payment Program
REGUPO	Line item status before the 'n'th change
REGUPW	W/tax information per w/tax type/FI line item in pmnt run
REGUS	Acounts blocked by payment proposal
REGUS_SEPA	SEPA Mandate Lock: Applications To Be Retrieved
REGUT	TemSe - Administration Data
REGUTA	Paying Company Codes for DME Files
REGUV	Control records for the payment program
REGUVM	Payment Data for Cross-Payment Run Payment Medium
SMFIAP	Spec. FI-SL Data in Monitor (See Schedman_specific_fisl)
T004F	Field status definition groups
T012E	EDI-compatible house banks and payment methods
T042	Parameters for payment transactions
T042A	Bank selection for payment program
T042C	Technical Settings For The Payment Program
T042D	Available amounts for payment program
T042FSL	Last additional selections used
T042G	Groups of company codes ( payment program )
T042I	Account determination for payment program
T042J	Bank charges determination
T042JB	Customizing table for Japan Bank Mergers
T042JB1	Customizing table for Japan Bank/Branch Mergers
T042K	Accounts for bank charges
T042L	Bank transaction code names
T042M	User Numbers At The Bank
T042N	Bank transaction codes
T042OFI	Events for MT100 and other DME Formats
T042OFIT	Events for MT100 and other DME Formats
T042P	Bank selection by postal code
T042R	Name of account holder (ref.specifications on bk.details
T042S	Charges/expenses for automatic pmnt transactions
T042U	Block Entries for Debit Customers/Credit Vendors
T042V	Value date for automatic payments
T045T	User ID for bank transactions
T077D	Customer account groups
T077K	Vendor account groups
T078D	Trans.-dependent screen selection for cust.master
T078K	Transaction-dependent screen selection for vendor master
T079D	Company code-dependent screen sel.for cust.master
T079K	Company code-dependent screen sel.for vend.master
T079M	Vendor master data screen selection (purch.org.)
TBACN	Bank EDI file version numbers
TBSL	Posting Key
TFAGS	Definition of FI clearing rules
TFAGT	Texts on FI clearing rules
TZGR	Grouping rules for automatic payments
TZGRT	Name of grouping rules
TBTCO	Job Status Overview Table
TFBUF	Table for FI Data Puffers
TRDIR	Generated Table for View TRDIR
VARID	Variant directory
VARIT	Variant Texts

SAP FI: SWIFT Code details

2011-02-02T22:19:00.001-08:00

SWIFT code is a standard format of Bank Identifier Codes (BIC) and it is unique identification code for a particular bank. These codes are used when transferring money and messages between banks.

The SWIFT code consists of 8 or 11 characters. When 8-digits code is given, it refers to the primary office.
First 4 characters - bank code (only letters)
Next 2 characters - ISO 3166-1 alpha-2 country code (only letters)
Next 2 characters - location code (letters and digits) (passive participant will have "1" in the second character)
Last 3 characters - branch code, optional ('XXX' for primary office) (letters and digits)

source: theswiftcodes.com

SAP Cutover Activities : Master Data Uploading Strategies

2011-01-08T09:14:00.001-08:00

Master Data Uploading Strategies depends upon when we are going live. As per that, you have to give the information to Core Team.

--> If you are going live at the middle of the year then you have to upload the all P&L Account items and B/S Items.
--> If you are going live at the financial year start, you have to upload only the B/S Items.

Activities for Golive:

1.   G/L Master Upload through BDC or LSMW (Upload using the TC: FS00 and extend one company code to another company code using the TC: FS01)
2.   Vendor Master Upload Thru BDC Or LSMW (Will be taken care by MM Consultant, Reconciliation account anc payment terms at company code level will be provided by FI)
3.   Customer Master Upload Thru BDC or LSMW (Will be taken care by SD Consultant, Reconciliation account anc payment terms at company code level will be provided by FI) 4.   Asset Master Upload (TC: AS90)
5.   Cost Element Master Upload (TC: KSH1)
6.   Cost Center Master Upload (TC: KS01)
7.   Profit Center Master Upload (TC: KE53)
8.   G/L Balances (TC: FB01)
9.   Vendor Balances (TC: F-43)
10. Customer Balances (TC: F-22)
11. Customer Advances (TC: F-29)
12. Vendor Advances (TC: F-48)

In case WHT is activated for the specified comapny code the before uploading Vendor Balances you have to take care of WHT(TDS) Information.

SAP - AA : Legacy Asset Data Transfer Configuration Steps

2010-12-28T02:28:00.001-08:00

Transaction Code

SPRO Set Company Code Status

OAYE Specify Sequence of depreciation areas

SPRO Specify Transfer Date / Last Closed Fiscal Year

OAYC Specify Last Period Posted in Prv. System (Transf. During FY)

OAYD Transfer Foreign Currency Values

OAYF Recalculate Depreciation for Previous Years

OAMK Set Reconciliation Accounts (Manually)

Set Company Code Status:

SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Set Company Code Status

You use this indicator to specify the status of the company code from the point of view of Asset Accounting:

Test status - You can change values by transferring asset data from a previous system, or by posting.
Transfer status - You can enter and change values by transferring asset data from a previous system, but posting is not possible.
Production status - The asset data transfer is complete. You can only change values by posting. Before the system goes live, it is essential that you set the system status to "production" (not test).

This rule applies even if you transfer asset data from your previous system in several phases over the course of time. If you do transfer data in this way, you have to temporarily remove the "production" setting of the the company code status.

Company code status is generally set to '2' for conversion purposes. This identifies the company code as being in test with data transfer always allowed. This should be the start-up position for the asset company codes.
In the Production system, this setting should be changed to "0 – Asset data transfer completed" once all data takeover activities are completed for each company code.
Once the SAP company code has had at least one Quarter end reported and verified after go-live, and the assets data is deemed stable, the company code status will be set to '0'.
0 Asset data transfer completed
1 Asset data transfer not yet completed

2 Test company code with data transfer always allowed

3 Company code deactivated - reporting allowed

Specify Sequence of Depreciation Areas:

SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Specify Sequence of Depreciation Areas

In this field you define the order in which you want to update depreciation areas with values during legacy data transfer. You determine this sequence by entering a relative number in this field.
During the transfer of legacy data, the first depreciation area to be transferred is generally the book depreciation area.
In this step, the sequence of the depreciation areas for the data takeover transaction is specified. If there are additional depreciation areas for local / fiscal purposes, the sequence for the depreciation areas may be impacted.

Specify Transfer Date/Last Closed Fiscal Year:

SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Parameters for Data Transfer > Date Specifications > Specify Transfer Date/Last Closed Fiscal Year Status

In this step, the asset transfer date for conversions is specified. This setting is maintained in each client to facilitate test conversion activities.

This configuration is mostly maintained directly in each client. You have to enter this date before starting the asset data transfer. In most cases, the transfer date will be the last day of a fiscal year. All transactions starting in the new fiscal year are then carried out only in SAP Asset Accounting. The values transferred are the cumulative values at the end of the fiscal year.

The transfer date can also be during the fiscal year. When the transfer date is within the fiscal year, the values transferred are the values as they stand at the end of the last closed fiscal year before the transfer date. The transactions since the start of the current fiscal year, however, also have to be transferred. This is necessary in order to create the asset history sheet.

This field is only ready for input if the company code is not yet live. The system uses this date to determine the last closed fiscal year.

Specify Last Period Posted in Prv. System (Transf. During FY):

SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Parameters for Data Transfer > Date Specifications > Specify Last Period Posted in Prv. System (Transf. During FY)

The following step is only necessary if you want to perform an old assets data takeover during the fiscal year. In this case, you must specify the period up to which depreciation was posted in the previous system. This period refers to the posted depreciation that is to be transferred during old assets data takeover.

In this field, the system enters the period, for which depreciation was last posted. If the legacy data transfer is carried out during the fiscal year, you must update this field manually.
This field is not available for input if there is no legacy data transfer during the fiscal year, or if depreciation is not posted in this depreciation area.

If the asset takeover date is during a fiscal year, e.g. 31.03.2006, then the last period in which depreciation postings were made in the legacy system must be specified. This setting is maintained in each client.
This configuration is maintained directly in each client.

Transfer Foreign Currency Areas:

SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Options > Transfer Foreign Currency Areas.

You only need to carry out this step if you manage depreciation areas in foreign currencies.

In this step, you determine that foreign currency areas can receive values during old assets data takeover. Then the depreciation areas are not supplied with values from another area by the system, although they are defined as dependent areas by the Customizing settings. This specification can only be made for areas that are managed in foreign currency.

Using this indicator, you specify that you will provide values for the foreign currency area during the legacy data transfer. The system then does not provide values itself for the area (by taking over values from another area, with no changes allowed) as it normally would.

You can only make an entry in this field for an area which is managed in foreign currency.
For any Depreciation area with foregin currency values fixed at the Group Rate as at the takeover date, the takeover values for this depreciation area is calculated manually/automation tool.

Please note that if any change to depreciation area sequence is undertaken, that the manually input flag will change position and will require updating.

Recalculate Deprecation for Previous Years:

SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Parameters for Data Transfer > Options > Recalculate Depreciation for Previous Years

Set this indicator if you want the system to newly calculate accumulated depreciation from past years during the legacy asset data transfer.

You can recalculate the accumulated depreciation from the past, based on SAP depreciation rules, when a depreciation area is newly entered the values from a depreciation area should be recalculated in the R/3 system.for example, conversion data is not available for this depreciation area for these assets

This recalculation is based on the condition that the acquisition value was acquired completely at the time of capitalization. However, for the book depreciation area, this is only possible in company codes that are still in test mode.
You can also recalculate accumulated past depreciation for individual assets using the transaction "change old assets" (Function: recalculate values) after the takeover of data from your previous system.

Set Reconciliation Accounts (Manually) :

SAP Reference IMG > Financial Accounting > Asset Accounting > Preparing for Production Startup > Set Reconciliation Accounts - TCODE: OAMK (OAK5 - for automatically set)

This step is required for conversion purposes. Carried out directly in client during cutover. By default the relevant GL accounts will have been created as reconciliation accounts. As part of the conversion, the flag is removed from the GL accounts per asset class per company code. After the balances have been loaded, the reconciliation flag is reset. OAMK allows this to be carried out manually. Once they are set as reconciliation accounts, the system will only post to them via Asset Accounting from this point onwards. This is maintainable in each client except production where this step is managed by the cutover strategy.

SAP: HOW TO CHECK THE USER STATUS IN THE TABLE

2010-11-09T04:01:00.001-08:00

Defined User Status details are stored in the Table: ENT5854. You can
see the number of status details for one status profile. These details
may differ from client to client. Also differs from one status profile
to another. Against each status(ENT5854-TXT04) you can see the
technical status(ENT5854-ESTAT) details. Here the technical status
(ENT5854-ESTAT) is the main reference to check details further.

In the Table: VICN01, for every RE-Contract (VICN01- RECNNR) you can
see the Object number (VICN01- RECNOBJNR).

Now, use the same object number in the Table: JEST in the Object
number (JEST- OBJNR) field and execute for the entries. Now you can
see multiple entries in the output. For one object number you can see
multiple entries.

To get the latest status relating to the object (JEST-OBJNR), check
the particular entry, which is with 'active' status (JEST-INACT) and
with the latest 'change number' (JEST-CHGNR).

This status check procedure is same even in case of Rental Object,
Internal Order, WBS Element, etc.,

Always user status starts with 'E0001'and system status starts with
'I0001'. Logic to check the status is also same i.e., active status
having the latest change number.

SAP COPA - KES1 Maintain Charcterstict Values - ABAP Dump

2010-08-09T01:42:00.001-07:00

IF you get abap dump in KES1 –characteristic values.

Run the Program :

1 Goto transaction SE38->Give the program RKEAGENV and execute without test run. Maybe you face problem in KES1.

2 Goto transaction KEA0-> change -> activate and than generate operating concern.

Still not Solved implement OSS Note - 64490 and 942785

If you get an error executing transaction KES1 (V17 installation step Maintain Characteristic Values), install SAP notes 64490 and 942785. After you have executed report RKEAGENV as described in notes mentioned above, reactivate the operating concern (tcode KEA0, Tab Environment, cross-client and client-specific part).

Also check the below links:

Refer to the link - http://help.sap.com/bp_bblibrary/600/Documentation/E00_BB_InstallGuide_EN_DE.doc

Reference:
http://help.sap.com/bp_bblibrary/600/Documentation/BL_QuickGuide_EN_US.doc

SAP: COPA: Defining new characteristics

2010-08-06T05:18:00.001-07:00

You can also manually define new characteristics that you only want to use in Profitability Analysis. Since these characteristics have no table of origin, their values are not automatically derived from other characteristics. You therefore need to define derivation steps for them. The name of new characteristics must begin with "WW" and consist of 4 or 5 characters. Depending on the desired attributes, you must choose one of the following variants:

With own value maintenance - In most cases, you will define new characteristics with their own value maintenance. In this case, the system creates a check table and text table. In the Customizing activity Maintain characteristic values , you can then enter characteristic values and texts for these. Only those values maintained here are permitted values for that characteristic.

Without value maintenance - This option lets you define characteristics with no check table. This means that there is no set of allowed characteristic values and texts. Consequently, no validity check takes place for values of these characteristics. These characteristics cannot be used as receiver characteristics for period-based allocations.

With reference to existing values - This type of characteristic is only required in special cases. Here you assign the characteristic to a data element that already exists in the system. The characteristic takes on the attributes of that data element (texts, length, check table, text table).

source: help.sap

SAP COPA: Deleting Characteristics/ Value Fields from an Operating Concern

2010-08-06T05:12:00.001-07:00

You can delete characteristics and value fields retrospectively from an operating concern that you have already activated. However, you should only use this deletion function for operating concerns that have not yet been used productively. You should also note that some database systems require the operating concern tables to be converted (database conversion) after the deletion has taken place if data had already been posted to the operating concern. Depending on the data volumes involved, the database conversion can take a matter of seconds or indeed several hours. Moreover, you cannot post data or run reports during the conversion. Due to integration, other applications are also affected when data is postedwith an assignment to profitability segments (such as settlement and direct assignment from FI/MM). If the operating concern has been transported to another system (such as the productive system), then the database conversion must also occur in that target system.

To delete characteristics or value fields, perform the following activities:

1. Delete the corresponding characteristics and value fields from Customizing in all clients (this includes forms, reports, planning layouts, and so forth). To locate characteristics and value fields, use the appropriate where-used list in the Customizing Monitor . You can access it by choosing Tools -> Analysis -> Check Customizing Settings. You can jump directly from the where-used list to the relevant Customizing transaction and then delete the appropriate field there.

2. Switch to the screen for maintaining the data structure of an operating concern (Maintain operating concern).

3. If you need to effect other changes to the datastucture for the operating concern before making any deletions, effect those changes and save the data structure.

4. In order to be able to select the fields of the data structure, choose Extras -> Characteristics (or Value fields) -> Unlock.

5. Select the characteristics and value fields to be deleted and remove them from the data structure with the "Reset fields" function.

6. Reactivate the operating concern. The system starts by checking whether the operating concern contains any data and whether the fields to be deleted are still being used in any Customizing settings.

7. If none of the fields are still in use, the system then starts the re-activation. If the operating concern does not contain any data or does not require the database system to be converted, the tables are activated. You are then able to activate the environment for the operating concern. In this case, the following activities no longer apply.

If the operating concern already contains data, a system message tells you that the database needs to be converted. If you proceed, an activation log appears (at the top of the list).

8. Analyze the activation log. If it only contains error messages telling you to convert the tables, proceed with the next activity.

You must otherwise remove the cause of the errors before the tables can be converted. In this case, you should answer "No" to the next prompt, which asks whether the conversion transaction should start.

9. If you still only receive error messages telling you to convert the tables, choose "Back" and start the conversion.

10. Plan a job for the conversion. A list of the tables to be converted is shown for this. If the tables only contain a small amount of data (less than 10 000 records), then all the tables can be converted in one job. In that case, you can select all the tables.

For larger tables, conversion should take place in several jobs. However, you should ensure that table CE4xxxx (where xxxx = operating concern) is the last table to be converted.

Warning. No other changes can be made to the operating concern during the conversion.

A copy of the table is generated during the conversion. The database system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function. You can display the current status of the conversion by selecting the "Refresh" icon. Tables disappear from the list once they have been converted sucessfully. If a conversion is taking a while, it is also possible to leave the transaction. You can then continue the conversion using DB requests -> Mass processing in one of the following ways:

With the job overview. You access this by choosing System -> Services -> Jobs.

Using the database utility transaction. You access this by choosing Utilities -> Database Utility in the ABAP Dictionary menu.

You can use the status function to call up the status of the operating concern during operating concern maintenance. You need to activate all tables after conversion.

11. To analyze errors that have occurred during the conversion, you can use the database utility transaction by choosing Extras -> Logs. The log has the same name as the conversion job: TBATG-date. You can also restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application help while still in the above transaction.

12. Once you have activated all the tables in the operating concern, generate the operating concern environment from within operating concern maintenance.

You can then use the operating concern again.

SAP: COPA :Tables

2010-08-06T05:07:00.001-07:00

When you activate the data structures of your operating concern, the system creates the following objects in the ABAP Dictionary.


Type	Name	Description
Structure	CE0xxxx	logical line item structure
Table	CE1xxxx	actual line item table
Table	CE2xxxx	plan line item table
Table	CE3xxxx	segment level
Table	CE4xxxx	segment table
Table	CE4xxxx_KENC	realignments
Table	CE4xxxx_ACCT	account assignments
Table	CE4xxxx_FLAG	posted characteristics
Structure	CE5xxxx	logical segment level
Structure	CE7xxxx	internal help structure for assessments
Structure	CE8xxxx	internal help structure for assessments

ABAA - AFAR : Unplanned Depreciation - Recalculation of Depreciation

2010-07-21T07:44:00.001-07:00

ABAA - Unplanned Depreciation

There is an unexpected permanent reduction in the worth of the asset that you have to post as unplanned depreciation.

As a rule, the system automatically determines the planned depreciation for the current fiscal year by means of the depreciation keys entered in the master record. If you need to specifically set the amount of depreciation, the system offers a manual unplanned depreciation forecasting option. This means you can manually increase the planned values managed for the asset.The G/L accounts in Financial Accounting are not initially affected by this posting transaction. Asset line items are created, but no FI posting documents. The general ledger accounts are updated and the corresponding FI documents are created by the periodic depreciation posting run. The system then determines the depreciation to be posted up to a specific period, and creates the accompanying posting documents.

Transaction type - 640 : Unplanned depreciation on prior year acquistions

During posting system automatically calcualtes the depreciation in different amounts for different depreciation areas.

After posting you can see the same in AW01N in Planned values section under 'change' column against Unplanned depreciation

AFAR - Recalculation of Depreciation

This might be necessary if:

· You have changed depreciation keys.

· You have made mass changes that you programmed yourself, and these changes affected data relevant to depreciation.

· You want to calculate subsequent revaluation (after the legacy data transfer is closed) using current index figures. In order to correctly calculate replacement values, however, you can only use index series that calculate historically.

This program enables you to recalculate planned annual depreciation using the depreciation terms that are valid at the time that you start the report. You can also run the report in test mode. However, you can only recalculate planned depreciation for fiscal years that are still open. After the system recalculates the planned annual depreciation, it creates a statistical log with the total number of assets processed and the number of assets with errors. You can check the assets with errors using the asset value display transaction.

SAP: Transfer of Legacy Asset Data Methods

2010-07-20T06:23:00.001-07:00

How is depreciation entered during old assets data takeover?

Answer:

Asset Accounting always manages the values related to the fiscal year.

Depreciation values for previous fiscal years are always entered as cumulative values.

Estimated annual depreciation values for the current fiscal year with an old assets data takeover during the fiscal year cannot be entered because they are calculated automatically by the system. Differences from the estimated annual depreciations can therefore only be adjusted as manual value corrections, that is, by entering an asset transaction.

However, if you use a a depreciation key which does not automatically calculate the depreciation, for example depreciation key MANU, the manual depreciation must be entered during the transfer with a 6xx transaction type.

If depreciations have already been posted for the takeover year in the legacy system, these values must also be entered into the SAP System sothat they can be used by the posting program.

Source: OSS 50607

What are the legacy data transfer methods available in Asset Accounting and how are they different?

Answer:

The following is an overview of the legacy data transfer methods with additional information on the transferring legacy assets R/3 library.

1. Manual transfer with Transaction AS91 - This works with Transaction AS01 and is suitable for transferring smaller datasets.

2. RAALTD01 transfer via batch input - This is suitable for the mass processing of larger datasets. The batch input session fills the fields of Transaction AS91 up to and including Release 4.0B or of Transaction AT91 for subsequent R/3 releases. Therefore, only the data fields of these transactions can be filled.

3. RAALTD11 Transfer via direct input - This is suitable for transferring very large datasets. It transfers the same fields as RAALTD01 does, however it only carries out limited field checks. So that you do not receive any incorrect datasets as a result, first test at random the assets to be transferred in AS91 or as of Release 4.5B with Transaction AT91.

Furthermore, bear in mind that value fields are not converted. If, for example you specify a value field for an amount of money in euro in the BALTD-structure, you must consider the format. If, for example the value field has the format ###,## and you only enter 10 as a value, this value is interpreted as 0,10. Therefore you must specify 10,00 as value in BALTD.

To achieve the high performance of RAALTD11, the writing of change documents was also dropped. When you go into the change document display of an asset that was created with this report, the system generates the message "Asset created with Transaction AS02" or " ... AS92" by mistake.

Both RAALTD01 and RAALTD11 have not been enhanced since Release 4.5B.As of Release 4.6B, the legacy data transfer therefore is recommended via BAPI BAPI_FIXEDASSET_OVRTAKE_CREATE since this offers all of the transfer options of the new Transaction AS91 (as of Release 4.5B).

The following methods use this BAPI.

1. Transaction AS100 data transfer with Microsoft Excel - This is suitable for the transfer of smaller datasets (limited by the line count of your Excel version). This transaction is suitable in particular if you have mapped your Asset Accounting prior to R/3 using Microsoft Excel. However, you can create only main asset numbers. More restrictions are described in Note 303710.

2. Transfers via Workbench LSMW or SXDA - BAPI_FIXEDASSET_OVRTAKE_CREATE is used by Business Object Method BUS1022->Create Incl Values, message type FIXEDASSET_CREATEINCLVALUES and IDoc type FIXEDASSET_CREATEINCLVALUES01.You can also call it for the legacy data transfer even from your own program. You can find more information in the documentation of the function module in Transaction BAPI.

IFRS: The Right Next Step for US Business

2010-05-30T23:35:00.000-07:00

Overview

International Financial Reporting Standards (IFRS) is the framework used by most publicly traded companies in the world today to report their financial results. With support from important constituencies, the Securities and Exchange Commission (SEC) and the Financial Accounting Standards Board (FASB) have taken first steps toward a transition to IFRS from the accounting and reporting framework currently in place in the US. Is the US really going to set aside US generally accepted accounting principles (US GAAP)? The answer is almost certainly yes. As this white paper shows, within a few years the SEC is likely to designate a date for mandatory adoption of IFRS by all US public companies.

Read Full Story --> Click HERE

source: sdn. sap. com

Author: pwc

Data Processing Using ABAP code in LSMW

2010-04-21T09:07:00.000-07:00

Data Processing Using ABAP code in LSMW

Before heading towards where and how we can process data using ABAP code I will explain in brief about data migration steps and where LSMW fits in it. Sounds boring, isn't it!!!

But will be helpful to those who are new to data migration and LSMW.

Let's start!!!!

Data Migration

It's a process to transfer data from Legacy System to SAP.

Data Migration Steps

- Analyze the data to be Migrated
- Create field mapping for legacy to SAP fields
- Extract the Legacy data
- Transform the Legacy data to SAP format
- Load Transformed data to SAP
- Validate the Data Loaded.

Read Full Story here

Author:Vijay Sharma
source:sdn. sap. com

SAP : Business Transaction Events (BTE)

2010-04-12T03:04:00.001-07:00

Business transaction events:BTE is Customer Enhancements. It defines the standard interface, how the communication is done to/from external system to SAP.

There are two types of interface available

1. Publish & Subscribe interfaces (also called "informing interfaces")
2. Process interfaces (also referred to as "process" in the following)

Publish & Subscribe interfaces: These will inform you about particular events (such as a document being entered) in the SAP standard application and make the data generated as a result available to the external software.

Examples of such events in the R/3 System are:

- Master record was created, changed, or blocked

- Document was entered, parked, changed, or reversed

- Items were cleared or reset

Process interfaces: Process interfaces are used to submit business processes to a different control which cannot be realized with the standard system, that is process interfaces replace standard processes. It is possible to connect different external developments to the standard R/3 System. The additional developments are generally carried out using the ABAP/4 Development Workbench.

Click here for full story

SAP ECC 6.0: New GL : Cross Company-Code Invoice Posting - Configuration

2010-04-12T02:45:00.001-07:00

Configuration Path: IMG-> Financial accounting (New) -> General ledger accounting new -> Business transactions -> Document splitting -> Extended document splitting

1 Define Document splitting Rule
2. Assign business/transaction Variant to rule

3. Define Business transactions variants

There are two entries in customizing for Company Code Clearing lines.

A) One for the Company Code that does not contain leading item and

B) One for the Company Code that includes leading item.

Click here for the Screens and the posting

Refer OSS Note: 1085921 - Document split

author: Cora Phelan

source: sdn. sap. com

SAP FI: Down Payment - Advance Payment

2010-04-12T02:31:00.001-07:00

1. What is "down payment"?

Down payment is the Received/Paid amount before actual handing over the Goods .

2. The main contents of the down payment:

(1) Down payment is processed when the commodity buying and selling is promised, and the amount received/Paid before the commodity is handed over.

(2) The down payment happens in a debt or Credit side before the commodity is handed over .

(3) after the commodity is handed over, the down payment happened in debt/Credit could be deducted with accounts receivable/Payable.

3. In SAP "special G/L indicator" is used for handling the down payment posting.

What is special G/L indicator? -> For distinguishing the down payment and accounts receivable of the same customer: The "special G/L indicator" is used.

In SAP standard , Special G/L indicator : "A" is used for for Down payment.

Customizing: TCODE:FBKP->special G/L button->example: selecting "Acct Type" : " D " and "SGL Ind." : "A"->Maintain reconciliation account and special G/L account (the reconciliation account will be replaced by special G/L account when "A" is used for posting down payment line items) , by pressing properties button-> "Special G/L transaction types" could be set.

4. standard scenarios for customer down payment in SAP R/3 system for down payment processing:

(1) Down Payment Request (T-cd:F-37) with special G/L indicator : "A" -> it is only a note, a line item.

(2) Create down paymet n in F-29 with special G/L indicator : "A" in T-cd:F-29. Within this step, the down payment could be cleared.

(3) Create account reveivable in T-cd:FB70( customer open line items is posted).

(4) Clear the down payment created in step(2)withinv customer open item created in step(3) in T-cd:F-39.

Normally the partial amount in customer Open items is cleared with down payment( down payment amount <= amount in customer open item)

(5) Clearing the account receivable in F-28(clearing the left part amount in customer open line items)

For example:

(1)For down payment request, no transaction is happened, so no really document with debit/credit lines generated.

(2) creatr down payment : Bank ￥10,000 　/ down payment ￥10,000

(3) create customer open line item : account Reveivable　￥15,000 　/ Revenue ￥15,000

(4) clear down payment : Down payment　￥10,000　/ Receivcable　￥10,000

(5) clear the customer open line item : Bank ￥5,000　/ 　Receivable ￥5,000

SAP :EC-CS Data Upload Methods

2010-04-12T02:27:00.001-07:00

Introduction to Consolidation (EC-CS):

Consolidation (ECCS) is a part of FI sub-module which is used for consolidation of various company codes to extract the final financial position of the companies as a whole.

The consolidation is done mostly at 3 levels:

1.Statutory Consolidation - This is the consolidation carried out based on the company as the primary unit (Consolidation unit)
2.Profit Centre Consolidation - This is the consolidation carried out based on the profit centre as the primary unit (Consolidation unit)
3.Business Area Consolidation - This is the consolidation carried out based on the Business Area as the primary unit (Consolidation unit)
4. User Defined - This is done as per the requirement of the business, where it requires any other consolidation.
Data Collection in Consolidation: The data collection plays a crucial role in the consolidation process, basically consolidation units are grouped in to Consolidation groups depending up on the requirement of reporting to the business. The feed for the reports come from the data that is provided in various forms to consolidation.

Data Collection methods:

The data that is used in consolidation is not directly posted in to ECCS module; the data is extracted based up on the consolidation dimension or method used say statutory consolidation dimension, profit centre consolidation dimension or any other dimension as configured in the system.

The various methods of data collection are:-

1. Online data entry
2. Flexible upload
3. Real time update
4. Periodic extract
5. Rollup
6. Offline data entry

1.Online data Entry : Using the data monitor, you enter financial data online which was reported by those consolidation units for which you specified this data transfer method. You enter the data in data entry layouts. Data entry layouts are used for entering reported financial data both online in the SAP System and offline on the basis of MS ACCESS. You can use various layouts, depending on the type of data to be entered and the level of detail involved.

2.Flexible Upload: Option for importing both the master data (consolidation units and groups, chart of accounts, etc.) and the reported data from a text file.

3.Real time Update: The data entry method that is used in real time update is to update the consolidation with a document, when ever a posting is done in to FI or Sales invoice, i.e., when ever a document is posted in to SAP, the configuration is done in such a way that the document will even generate a consolidation document.

4.Periodic Extract: The data entry method that is used here is a on line data method, we decide in advance what data method we are going to input in to the consolidation unit, say either cumulative or periodically, if we use cumulative method we update the total cumulative postings as one document for a particular posting date and if we use periodically all the totals of a period is uploaded to a consolidation unit.

5.Rollup : The data entry method we use in Rollup method is to collect the data periodically say monthly by running the data monitor & consolidation monitor and pull the data to consolidation, this method is particularly used in profit centre consolidation, were we use the rollup monthly and once at year end to accumulate the data which is existing in various units (profit centre's) and pull the balances of totals to consolidation process.

6.Offline Data Entry: Decentralized data entry and processing of individual financial data is possible with MS Access. Master data are downloaded from a central R/3 system. After creation of the reported data, it is uploaded with a special method of the flexible upload.

Conclusion: The data entry method plays a crucial role in consolidation, as the data that we process to get final reports at the consolidation are extracted from already posted balances in FI (company code & business area) & Co (profit centre), the data is statistical data which is pulled and accumulated in the sub- ledger where from we configure the system to pull final financial reports.

author: Satish Puram

source: SAP Community Network

SAP ECC 6.0: Asset & NEW GL Integration

2010-04-12T02:22:00.001-07:00

From the AC210 course you will see that the new entities within New general ledger accouning such as the profit center/segment cannot be directly assigned to assets in asset master data. Therefore it has to be derived from cost center or order that is linked to asset. This is maintained in the time-dependent data of the asset.

Click here for full story.

author: Cora Phelan

source: sdn. sap. com

SAP : Using USER EXIT For FI SUBSTITUTION

2010-04-12T02:15:00.001-07:00

Substitutions can be used for validating data at the time of entry in SAP system. This wiki can be used for creating custom user exits so that one can set his validations & conditions. User exits are user defined FORM routines that are used to calculate/replace values with in a substitution .I have shown demo for FI but same steps with some minor modifications can be used for other areas too.

What are substitutions?

Whenever a data is entered in a system, validations are invoked to check its integrity .Once validations are done, one can substitute the entered value with some other value. This gives you the opportunity of having the system validate values that are to be substituted. A substitution value can be numeric or a string. The system first performs some validations and then substitutions.

Transactions used for substitutions are :

GGB1 : Substitutions maintenance.

OBBH : Activation of FI substitutions.

Substitutions can be performed using three ways:

1.Constant values.

2.Field -Field assignment.

3.User exits.

Steps for creating user exits for substitutions....click here for fully story

Author: Rajneesh
Source: sdn. sap. com

SAP : Cash Flow Reports : Direct / Indirect Method Config Settings

2010-04-09T01:09:00.001-07:00

TCODE' for the Cash Flow Reports are as below :

S_ALR_87012271       Cash Flow (Direct Method)
S_ALR_87012272       Cash Flow (Indirect Method) Variant 1
S_ALR_87012273       Cash Flow (Indirect Method) Variant 2

Below are the details of the Form' used in the above reports:

Form 0SAPRATIO-04 Cash flow (Direct Method)
Form 0SAPRATIO-03 Cash flow (Indirect Method) variant 1
Form 0SAPRATIO-01 Cash flow (Indirect Method) variant 2

Use the TCODE: FSI6 to view the above form.

Above given Forms used in the below given reports

Report 0SAPRATIO-04 Cash flow (Direct Method)
Report 0SAPRATIO-03 Cash flow (Indirect Method) variant 1
Report 0SAPRATIO-01 Cash flow (Indirect Method) variant 2

Use the TCODE: FSI3 to view the above reports.

You should know what format you would like to see in the cash flow statement.

You should use the FS items accordingly copy the standard forms and changed according to your format. You should be conversant enough to do basic report painter.

Go to the Form 0SAPRATIO-01

Go to the form menu > click on change.

Go to edit menu, select general data selection / gen.data select .

There you assign your financial statement version (FSV) and confirm.

Then come to the form double click on each row and assign your respective financial statement version item and confirm.

And you change the rows as per your requirements.

Save the form.

Execute the report change the INT to your own Chart of Account.

Also make sure in the form you have assigned the FS items from your Financial Statement Version (OB58).

FS items are nothing but nodes in your FSV.

Use TCODE: FF7A for Cash Position reporting. You must activate Cash Management first, Go to TCODE: FDFD in configuration and activate the company code for cash management.

Understanding Results Analysis for WIP

2010-04-09T00:14:00.001-07:00

Introduction and Configuration Guide

Work in process (WIP) inventory forms a part of the working capital or current assets of a firm appearing in their balance sheet. Work in process or progress are partially completed goods, parts, or subassemblies that are no longer part of the raw materials inventory and not yet part of the finished products inventory. Fundamental Principle of International Accounting Standard 2 states that Inventories are required to be stated at the lower of cost and net realisable value (NRV).

The guidance on measurement of cost of inventories is that, cost should include all:

a)     costs of purchase (including taxes, transport, and handling) net of trade discounts received
b)     costs of conversion (including fixed and variable manufacturing overheads) and
c)     other costs incurred in bringing the inventories to their present location and condition

With SAP, the raw materials gets transferred to finished goods via production orders or process order. In this process, typically, the production order is created to which raw materials are issued, all activities performed in the process are charged along with any overheads that is apporopriate the production order. Production is ongoing, and it is quite natural that at month end, we end up with some open production orders. SAP in its product costing functionality, provides the feature to calculate the value of WIP. This will be derived based on the careful definition of Line IDs in line with the cost components. The WIP shall be the total debits cost in the order as reduced by the credits for goods receipt.

Key elements of WIP Results Analysis Configuration.

Step 1 Define Results Analysis Key OKG1.

Here you just give a name, four letter key with its description.

Step 2 Create cost elements of type 31 the following minimum

Valuated Actual cost, say for eg. 990001.
Calculated Costs, say 990002.
WIP account 990003
WIP Reserve 990004
WIP Reserve 990005

Step 3 Define RA version, OKG9, Enable Transfer to Financial Accounting (checkbox)

Under extended control, you may enable checkboxes relating to

- Generate line items
- Assignment/RAkey
- Update/RAkeyEnter the cutoff period for actual RA/WIP, the effective date before which any WIP data if existed, will not be altered.

Step 4 In OKGC, define the valuation method for WIP.

Here, you specify that WIP calculation mode is one when the order has the staus REL.

The calculated WIP shall be cancelled when the order status changes to DLV or TECO. You maintain this data for CO area, RA version and RA key combination.

Step 5 SPRO>Controlling>Product Cost Controlling>Cost Object Controlling>Product cost by order>Period End Closing>Work in process>Define Line IDs.

The line IDs are similar to cost component, that you create during cost estimates like a) 010 for Material b) 020 for Labor and c) 030 for Overhead to say the least.

Besides these, create one more line ID say 999 for the Settled Cost, which appear as credit when you make a goods receipt.

Create additional WIP type 31 cost elements and their corresponding Reserve account for the above#### WIP Material 990006

WIP Material Reserve 990007
WIP Labor 990008
WIP Labor Reserve 990009
WIP Overhead 990010
WIP Overhead Reserve 990011

Step 6 Now you assign the source cost elements OKGB, that are expected in the production order to various line ID as created above.

You maintain this data for CO area, RA version and RA key combination. You use masking when you mention which cost element to be assigned to various IDs. You can also direct various cost element, if it comes with a combination of particular cost center and activity type to a particular Line ID. If you need to keep it simple, just enter +++++++ for cost centers, activity types and Business processes. Cost elements can be masked as follows; for eg. All cost primray cost elements for materials, if they start from 210001 to 219999, the you can mask them like 00021+++++. Give the line ID in the column Required to Capitailze.

Step 7 Define the update. OKGA You maintain this data for CO area, RA version and RA key combination.

Here you specify which line IDs are to be grouped under which cost elements and their reserve account. You connect the cost elements created in step 5 to the line IDs. The category for the line IDs for material, labor and overhead shall be K, that stand for cost. The line ID 999 settled cost shall be maintained as category A, (settled cost). When you assign A, you won't have to maintain any cost elements for WIP and reserve creation.

Step 8 Define posting rules for WIP calculation OKG8

You do this for Controlling area, company code, RA version. Maintain this for RA category WIPR (WIP cost, Required to be capitalized) and RUCR (Reserve for unrealized cost). You maintain the P& L account (changes to stock) and the balance sheet (WIP)account.These G/L accounts are posted in Financial Accounting.

Step 9 Ensure number range assignment for the WIP transactions under appropriate head OKG6:

KABG Automat. WIP/results analysis
KABM Manual WIP/results analysis
KSWP Prim. Target Cost Calc. (WIP)
KSWS Sec. Target Cost Calc. (WIP)

Period end WIP calculation Process

The process of running WIP is the t-code KKAX for individual order processing and KKAO for collective order processing. The system debits the WIP account and credits Inventory Change account. This entire WIP is reversed and a new entry is passed the following month. When the order is fully delivered no additional WIP entries are passed.

Note: The RA Key shall be entered in the production order, under the control tab. This can be defaulted through order type.

author: Sridhar Vasudevan

source: sdn.sap.com

Surviving a successful SAP GO-LIVE

2010-03-24T00:56:00.001-07:00

I still remember the first time that I was a part of a SAP project that went live. We had toiled for seven months to get the Netherlands operation of a gas manufacturing company from an outdated HP legacy on to SAP. The day before the go-live saw us toil till 04:30 in the morning only to miss the opening address of the general manager over some cakes and beer. Yes the Dutch can drink beer at all hours of the day. The go-live was a rocking success but still we missed out on the free cans of beer that morning. So here is my list of things that enable companies to have a rocking go-live and not miss the beer party:

==> Proper Governance: A lot of resource and money is spent on a SAP implementation. Without a proper governance model there is no accountability and the project would fall apart. Lots of time, the upper management is way too busy in running the business at hand and the implementation takes a backseat. A proper governance ensures that the vision of the management is percolated down to the lower levels and conflict resolutions are easier. Weekly meetings with status reports go a long way in making a success story of any implementation.

==> Scoping: Most SAP projects have time and cost overruns because of improper scoping. A proper blueprinting of the business at hand and mapping the same to the solution available results in knowing the gaps that have to be bridged. Sometimes very little time is given to this whole process resulting in improper estimates and subsequent gaps being found that are critical for the business. As a result the scope keeps on creeping up and leads to an overall delay in the program. Proper documentation should be maintained about the scope and a process should be set up by the governance team about scope creeps. Best managed projects have minimum scope changes.

==> Stakeholder communicaton: Many project disasters can be avoided by setting up proper communication channels. Often there are no clear cut communications from the project management team about the expectations from the business. In turn the business has no clues about what to expect out of SAP. Communication of weekly progress and targets for the next week play a pivotal role Most SAP implementation service providers follow a global-delivery model where custom development (ABAP coding) is done at a different location. As a result there are a lot of bottlenecks in communication. Efforts should be made to ensure that there is proper communication of requirements resulting in near zero errors. During the stage of cutover and go-live effort must be made to have status meetings everyday which go a long way in giving confidence to the stakeholders.

==> Involvement of business at all steps of the project: An SAP implementation is not only an IT software change. It involves a change in the approach of business and lots of processes need to be aligned to this new way of working. As a result, there should be involvement of the business at all steps straight from blueprinting till the go-live. Teams working in silos often face a problem because of unwillingness of the business to look for alternative ways of working at the last moment before the go-live. The involvement of business results in healthy discussions and subsequent realignment of business process becomes easier.

==> Not the onus of IT: Similar to the previous point, there should be a firm communication from the top management that the onus of implementing SAP is not only for the IT team but the whole business. This results in different ideas coming to the table and reduces conflicts during go-live.Business approvals at every stage: No SAP project can be achevied without custom developments. There are local business processes that need ABAP codes to be written for certain add on functionalities. Often the developments related to such gaps go completely untested till the point of user acceptance testing resulting in major defects that can be avoided by taking the business approval from a very early stage of development. The best way is to share unit testing and integration testing results with the business and seek their approvals before hand.

==> Ease of usage tools creation: A lot of SAP processes/ transactions are time consuming and hence business users are unwilling to let go of old processes. In one of our projects, rebate processing was being done through excel sheets. It was very difficult to convince the business users to use the standard SAP functionality to create rebates because of the sheer time required to create one rebate in SAP. Similar was the requirement for having a tool for faster upload of contracts into SAP. We managed to create such tools that have gone a long way towards the acceptance of the solution by the business users. Such tools are easy to create and give the users a confidence and saves their time.

==> Exhaustive training and hand holding pre and post go-live: Usually during any implementation, user trainings are completed in tight schedules. For a novice, learning all the transactions and nuances of SAP is not easy. This can only be acheived through exhaustive trainings and hand holding sessions pre and post go-live. Most of the issues that are encountered during any implementation is caused because of a lack of knowledge. After the go-live there should be a validation of the data going into the system by the implementation team to check for errors in transactions before they become disruptive.

==> Controlling data issues during user acceptance testing: During any user acceptance testing the majority of issues are related to wrong master data. Most of these issues can be avoided by putting in place checks and controls to make the master data proper for the testing. A lot of time and effort can be saved by this step. If this step seems to be very tedious, then a subset of the data should be analsyed for errors and this should be provided to the users for user acceptance testing.

==> Managing changes: Change management is very important to any organisation and especially so when taking a giant step like a SAP implementation. A lot of processes are bound to change and reactions to change are not always positive. To ease changes there should be proper hand holding for the users and giving them the broader picture of why such changes are necessary. Human nature avoids changes and in case of a SAP implementation people are also afraid of their job security. To get the best results the governing body should address change management issues with positive reasons.

==> Motivating and rewarding people: A SAP implementation is a very complex project and people need motivation to go ahead with the work at hand. Rewarding people who have worked towards change, arranging open forums and appreciating people for their committment towards the project goes a long way in making an SAP implementation successful.

==> Managing politics: Politics is one thing that can derail an implementation and hence the governing committee should take every possible action to eliminate the politics. Hidden agendas should be brought out in open through transparent communication.

Author: ainindra

Source: sdn. sap. com

SAP FICO: SPL - Variable field movements in FI

2010-03-24T00:44:00.001-07:00

Sometimes we need to modify standard SAP transactions in FI for field movements . This blog is intended to provide a step by procedure of user exit creation for this field movement to occur instead of modifying standard SAP programs with an example scenario.

Example Business Scenario Company A has created a special purpose ledger (ZZHYP say) would like to populate 4 digit trading partner(VBUND) in the special purpose ledger .The field will only be used for reporting and is only needed in the Special Purpose Ledger. But the available data or the current values are present in 3 digits only. So Company A would like to change the entire 4 digit trading partner populated from FI to 3 digit trading partner in the special purpose ledger.

For this purpose, a standard sap modification has to be done, but SAP allows you to enhance FI/CO features without modifying the standard code which are often collectively referred to as "user exits," SAP Enhancements are used to expand the standard functionality within SAP. Enhancements use function modules and are called from the standard SAP code. Each module in the system has a set of delivered enhancements that help companies expand the standard functionality where they need it. So here we create a Z program to insert our code for changes that has to be done and customize it. Hence when the data flows from FI to SPL, it will pass through the user exit that we have created to get the required result.

To accomplish this requirement, Company A will use the Variable Field Movement User Exit.

Read full story here

Author: Ramya

Source: sdn. sap. com

IFRS Adoption In Consolidated Statements

2010-03-23T22:57:00.001-07:00

This first series of four blogs is dedicated to handling IFRS adoption for consolidated statements. They provide an overview of a new SAP "How-to guide" called "IFRS adoption in consolidated statements using SAP® BusinessObjects^TM Financial Consolidation, starter kit for IFRS". The objective is to bring practical guidance to end-users in order to manage successfully all the issues raised by the adoption of IFRSs and to get the maximum benefit from SAP® BusinessObjects^TM Financial Consolidation.

The blogs will cover:

Blog #1: Approaches in IFRS adoption
Blog #2: Operating issues to deal with in financial reporting systems.
Blog #3: How to face the challenge - The starter kit for IFRS as a starting point - this blog
Blog #4: How to face the challenge - Key implementation templates

In the previous blogs (1 and 2), the retrospective method was described, along with the main issues to handle in financial reporting systems. We will now focus on the solutions proposed by SAP.

Continue here for full story

Author: Jean-Francois Bouillon

Source: sdn.sap.com

Non-Deductible Tax in Procurement

2010-03-23T22:52:00.001-07:00

The detailed explanations regarding Taxes in purchasing are recorded in below SAP notes:

501054 FAQ: Taxes in purchasing
214151 Tax processing in purchasing

Let us review the customizings and have an example of non-deductible tax in procurement process. The simple example is procurement of non-stock material.

Click here for full story

Author: Jimmy Zhnag

Source: sdn.sap.com

TCodes F110 and FBZ0 - Segregation of Duty Fix

2010-03-23T22:47:00.001-07:00

Generally Tcode F110 is a potential SoD risk. F110 combined with FBZ0 creates numerous SoD violations. Let's discuss what is exactly the risks are and how to avoid it.

F110 - Automatic Payment Transactions : Status
FBZ0 - Payment Proposal

Through F110, we can do two activities i.e. Payment Run and Payment Proposals.
(While running payment proposal it asks for FBZ0 access at the background, that is why I have combined both of the transactions while describing it)

Now the risk is that payment run and payment proposals should not be given to the same person who will access F110 because of SoD violation.

To remove this SoD risk, we need to play around some authorization objects i.e. F_REGU_BUK and F_REGU_KOA.

These authorization objects contain some activities which are given as numbers inside the role.

The meaning of those numbers are provided below.

02 Edit parameters
03 Display parameters
11 Execute proposal
12 Edit proposal
13 Display proposal
14 Delete proposal
15 Create payment medium proposal
21 Execute payment run
23 Display payment run
24 Delete payment run payment data
25 Create payment media of payment run
26 Delete payment orders of payment run
31 Print payment medium manually

To make payment run and payment proposal mutually exclusive, we need to restrict the activities accordingly.

So one role should not contain 11, 12, 13, 14 and 15 and the other role should not contain 21, 23, 24, 25, 26 and 31.

Restricting the authorization objects with above activities we can remove the potential SoD risk easily.

Author: Sambit

Source: sdn.sap.com

How to configure valuated project stock?

2010-03-23T22:35:00.001-07:00

Introduction:

Today many industries want to manage project stock in quantity and value basis.In this blog we are going to discuss the attibutes of valuated project stock and the configuration steps

valuated Project stock:

Project stock for which each material in the stock is always managed quantity-based and value-based.Each material quantity is valuated with monetary valuation.All goods movements for the project stock lead to corresponding postings to G/L accounts in Accounting.

Click here for full story

Author: Raja Ramaswamy

Source: sdn.sap.com

Restriction of Maximum 999 FI Document Items During MM transactions

2010-03-23T22:33:00.001-07:00

I guess you might have this experience. While entering a goods receipt (MM-IM) through transaction MIGO, there is the error message: F5727 "Maximum number of items in FI reached".

There is a limit of (999) line items which can be posted per FI document. This is because the line item number (BSEG-BUZEI) field length is defined as (3) numeric positions, i.e., (999) line items.

Click here for full story

Author: Jimmy Zhang

Source: sdn.sap.com

No Subsequent document found in Accounting

2010-03-23T03:35:00.001-07:00

An invoice has been cancelled using MR8M.

While the material document has been generated no accounting has been generated.

The error message is : No Subsequent document found in Accounting (Message No. RW 017)

Solution :

If the invoice is via MIRO, then below notes should be helpful to you.

OSS Note : 382797 - MIRO: Analysis and repair for missing follow-up documents

OSS Note : 781498 - MIR4: Missing follow-on documents

Accounting entries not involving GR/IR directly

2010-03-11T23:34:00.001-08:00

MATERIAL PRICE CHANGE

In SAP, material price can be changed by using the TCODE: MR21. The accounting entries are similar for both V and S price control. Price can either be increased or decreased which is directly affecting the stock account and therefor hitting BSX. The balancing act is done by the account Gain/Loss revaluation which is UMB.

Accounting entry:

Description		Posting Key	Transaction Key	Account Type
Raw material consumptin a/c	DR	99	BSX	M
Revenue Expens a/c.	CR	83	UMB	S

PIPELINE MATERIAL WITHDRAWL

Pipeline material assumed to be availabel all the time. This type of material is not planned, purchased. The material is never stored. The material is withdrawable at any time. Info record should be maintained for the material for Pipeline category.
Accounting entry:

Description		Posting Key	Transaction Key	Account Type
Consump.for internal goods a/c	DR	91	KON	S
Cost Price Differ a/c	CR	81	GBB	S

MATERIAL TO MATERIAL TRANSFER

Inventory from one material can be transferred to another material. The only condition for this is, both the materails should have the same base unit of measure.

Movement type used is 309.

There are four possible cases with this scenario depending on the Price Control of the Material.

From - To
V       - V
V       -   S
S       -   S
S       -   V
As long as the receiving material is maintained at V, there won't be any difference entries. The receiving material with V will always accept the incoming price. If the receiving material is at S, and if the incoming price is different from its Standard price, then there will be price difference entries.

Case 1: S to V

Material-MATS (Price control-S) to Material-MATV (Price contrl-V)

Description		Posting Key	Transaction Key	Account Type	Material
Raw material consumptin a/c	DR	99	BSX	M	MATS
Raw material consumptin a/c	CR	89	BSX	M	MATV

Case 2: V to S

Material-MATV (Price control-V) to Material-MATS (Price contrl-S)

Description		Posting Key	Transaction Key	Account Type	Material
Raw material consumptin a/c	DR	99	BSX	M	MATV
Raw material consumptin a/c	CR	89	BSX	M	MATS
Exp.from St. Transfer a/c	DR	93	AUM	S	MATS

Here the receiving material is at S, and hence the difference amount is posted to a Exp/Rev account with AUM.

PLANT TO PLANT TRANSFER

This is similar to the previous scenario, only difference is different valuation areas, material being the same. Again the same four case (S<->V) are possible.

The entries will also be of the same naterua BSX, BSX and AUM.

Note in case of STO, the accounting entries happen when the material issued from the shipping plant. At the receiving plant when the GR is done, there won't be any accounting entries.

VALIDATION & SUBSTITUTION : Boolean logic

2010-03-11T02:34:00.001-08:00

1. Boolean logic refers to the system of mathematical logic
2. It is used to create logical rules or statements
3. These logical statements are used to analyze, select, and process data
4. Logical statements can be linked using operators
5. An operator links logical statements and defines how the statements should be processed
6. A combined statement is two or more logical statements linked together.

Boolean logic is used in:

Report Writer
Validation
Substitution

TRUE / FALSE : is a logical proposition that is either true or false

AND (conjunction)

Both statements must be true for the combined statement to be true.

(Condition A) AND (Condition B) = In this case if Codition A & Condition B are true then only total statement becomes true to move further on posting.

Example : (GL = 900000) AND (cOST CENTER = A001CD1000)

while posting system check whether GL = 900000 AND cOST CENTER = A001CD1000

(10 > 6) AND (2 + 2 = 4) (TRUE)

(2 + 2 = 4) AND (10 < 6) (FALSE)

(10 < 6) AND (2 + 2 = 4) (FALSE)

(2 + 3 = 4) AND (10 < 6) (FALSE)

OR (disjunction)

At least one of the statements must be true for the combined statement to be true.

(Condition A) OR (Condition B) = In this case if Codition A or Condition B are true then only total combined statement becomes true to move further on posting.

Example : (GL = 900000) OR (cOST CENTER = A001CD1000)

while posting system check whether GL = 900000 OR cOST CENTER = A001CD1000

(10 > 6) OR (2 + 2 = 4) (TRUE)

(2 + 2 = 4) AND (10 < 6) (TRUE)

(10 < 6) AND (2 + 2 = 4) (TRUE)

(2 + 3 = 4) AND (10 < 6) (FALSE)

NOT (negation)

Statement that follows the NOT operator must be false for the statement to be true.

NOT (2 + 2 = 4) (FALSE)

NOT (10 < 6) (TRUE)

NAND (NOT AND)

At least one statement must be false for the combined statement to be true.

Example :

(2 + 2 = 4) NAND (10 > 6) (FALSE)

(2 + 2 = 4) NAND (10 < 6) (TRUE)

(10 < 6) NAND (2 + 2 = 4) (TRUE)

(2 + 3 = 4) NAND (10 < 6) (TRUE)

NOR (NOT OR)

Both statements must be false for the combined statement to be true.

Example :

(2 + 2 = 4) NOR (10 > 6) (FALSE)

(2 + 2 = 4) NOR (1 = 2) (FALSE)

(2 + 1 = 4) NOR (2 + 2 = 4) (FALSE)

(2 + 1 = 4) NOR (10 < 6) (TRUE)

--> (implication)

The two statements depend on each other to determine the truth value of the statement, if the second statement is true or the first statement is false, the combined truth value is true.

Example :

(1 = 1) --> (2 + 4 = 6) (TRUE)

(2 + 2 = 4) --> (10 < 6) (FALSE)

(10 < 6) --> (2 + 2 = 4) (TRUE)

(10 < 6) --> (2 + 3 = 4) (TRUE)

<-> (equivalence)

Both statements must be true or both statements must be false for the combined statement to be true.

Example :

(1 = 1) <-> (2 + 2 = 4) (TRUE)

(1 = 1) <-> (10 < 6) (FALSE)

(10 < 6) <-> (1 = 1) (FALSE)

(2 + 3 = 4) <-> (10 < 6) (TRUE)

source: help.sap.com

Useful VIEW TABLES from different modules :

2010-03-04T00:50:00.000-08:00

Sometimes we face difficult to pull the data from one table, put the data in different table to fetch required data. In most of the cases SAP has provided some view table which are the combination of the 2 or more tables. This makes easy for us to fetch the data without much effort. I did some workaround and got some info. Appreciate if you also share the view table information in this relation.

View Table	Tables joined	Description
EKBI	EKKO, EKPO, EKBE	Join via EKKO / EKPO / EKBE for MR11
MARAV	MARA, MAKT	View Table for Logical DB MGM
MARCP	MARA	EC-PCA: View of Table MARC
MARDP	MARA	EC-PCA: Projection View of Table MARD
SWIVOBJECT	SWW_CONTOB, SWWWIHEAD	Join SWW_CONTOB with SWWWIHEAD
SWWVHEARET	SWWWIHEAD, SWWWIRET	Joint view of SWWWIHEAD and SWWWIRET (types B,F,P,W)
TXW_J_WITH	BSAK, WITH_ITEM	Join of BSAK and WITH_ITEM for DART
V_ACEDSASSGMT	ACEDSASSGMT, ACEOBJ	Join ACEDSASSGMT and ACEOBJ
V_ACEDSOH	ACEDSOH, ACEOBJ	Join ACEDSOH and ACEOBJ
V_ACEDSOI	ACEDSOI, ACEOBJ	Join von ACEDSOI und ACEOBJ
V_ACEDSOI_ACCNTS	ACEDSOI_ACCOUNTS, ACEOBJ	Join of ACEDSOI_ACCOUNT and ACEOBJ
V_ACEDSOP	ACEDSOP, ACEOBJ	Join ACEDSOP and ACEOBJ
V_ACEPSOH	ACEOBJ, ACEPSOH	Join ACEOBJ and ACEPSOH
V_ACEPSOI	ACEOBJ, ACEPSOH, ACEPSOI	Join ACEOBJ and ACEPSOI
V_ACEPSOIT	ACEOBJ, ACEPSOIT, ACEPSOH	Join ACEOBJ and ACEPSOIT
V_ADRCADRV	ADRC, ADRV	View of ADRC and ADRV
V_AFAB_1	ANLA, ANLZ and ANLC	View of ANLA, ANLZ and ANLC for dep. posting
V_AFVC_AFKO	AFVC und AFKO	View-Tabelle mit Kombination AFVC und AFKO
V_ANI_AB	ANIA & ANIB	Joint View of ANIA & ANIB
V_ANI_AB	ANIA & ANIB	Joint View of ANIA & ANIB
V_ANLBAZ	ANLB, ANLZ, and ANLA	View of ANLB, ANLZ, and ANLA
V_ANLC_CURR	ANLC	Value Fields of ANLC
V_ANLP_ACC	ANLP	View for Table ANLP with Doc. Number and Accounting Objects
V_ANLSUM_1	ANLA, ANLZ, ANLB and ANLC	View of ANLA, ANLZ, ANLB and ANLC
V_ANLSUM_2	ANLA, ANLZ, ANLB and ANEP	View of ANLA, ANLZ, ANLB and ANEP
V_ANLSUM_3	ANLA, ANLZ, ANLB and ANEP with ANEA	View of ANLA, ANLZ, ANLB and ANEP with ANEA
V_ANLV_UPD	ANLV	View of ANLV for Update of Insurance Values
V_E070TC	E070TC, E070 and E07T	View of E070TC, E070 and E07T
V_EINA	EINA + EINE	Joinview zum Lesen der EINA + EINE
V_EWU_KEKO	KEKO and KEPH	Generated Table for View V_EWU_KEKO
V_KBED	KBED and KBEZ	Database View Using KBED and KBEZV_KEKO_ENQ
V_KEKO_ENQ	KEKO & T001K	View for locking KEKO using company code
V_KNA1ADR3	KNA1-ADRNR, KNA1-LAND1	Projection View for checking KNA1-ADRNR, KNA1-LAND1
V_KNA1ADRC	KNA1 and ADRC	View of KNA1 and ADRC
V_LFA1ADR3	LFA1-ADRNR, LFA1-LAND1	Projection View for Checking LFA1-ADRNR, LFA1-LAND1
V_MARM_T006A	MARM and T006A	View of MARM and T006A
V_MKPF	MSEG and MKPF	View of MSEG and MKPF
V_MMIM_BEW	MBEW	View of Table MBEW
V_MMIM_BS	EKKO & EKPO	View of Purchase Orders
V_PACKIN	PACKKP, PACKPO, PACKKPS	View of tables PACKKP, PACKPO, PACKKPS
V_PACKIN2	PACKKP, PACKPO, PACKKPS	View of tables PACKKP, PACKPO, PACKKPS
V_PTRV_APPR	PTRV_HEAD & PTRV_PERIO	Join to Tables PTRV_HEAD & PTRV_PERIO
V_PTRV_HEAD	PTRV_HEAD & PTRV_SHDR & PTRV_PERIO	Join to Tables PTRV_HEAD & PTRV_SHDR & PTRV_PERIO
V_PTRV_SREC	PTRV_SREC & PTRV_SADD	Join to PTRV_SREC & PTRV_SADD
V_QDQLQEM	QALS, AVFC; QAMV, QASV	View of QALS, AVFC; QAMV, QASV for dyn. mod. hist. (characs)
V_RESBRSADD	RESB and RSADD	View Between RESB and RSADD
V_RPBANF	RESB, RSADD and RSDB	View for RESB, RSADD and RSDB
V_RPBANF_STOCK	RESB, RSADD and RSDBS	View for RESB, RSADD and RSDBS
V_S_FCODE	SE18/19/20	View for internal tables in SE18/19/20
V_TXW_AFRU	COEP/COBK/AFRU	Join COEP/COBK/AFRU

SAP : Investment Management (IM) Overview

2010-03-01T03:35:00.001-08:00

Create an Investment Program : Transaction Code: IM01

The investment program can be used to augment planning and budgeting at the level of the individual measure by offering planning, budgeting and monitoring of a comprehensive budget.

Investment programs are helpful to enterprises that create an investment plan and a budget annually, and wish to monitor the budget as a whole, rather than just at the level of individual measures.
Using investment programs, you can obtain an overview of planning and budgeting processes in complex enterprise structures for all investments and large projects of the group, while at the same time maintaining strict budgetary control.

Create Top Program Position : Transaction Code: IM11

The top program position is the highest level in Investment Management which is company code specific, and it is the highest level that can have a budget.

· Determine the SAP Profit Center prior to creating the investment program.
· Determine the SAP Cost Center relevant for overall project management.

Change Investment Program Structure: Transaction Code: IM22

This change in structure is required to create the individual program positions. These program positions are the equivalent of the line items in the legacy system.

· Determine the SAP Profit Center responsible for the program position prior to changing the program structure.
· Determine the SAP Cost Center relevant for the program position (this can be different from the Cost Center used in the top program position).

Edit Original Budget: Transaction Code: IM35

This transaction will establish the budget in SAP for a given investment program and the relevant program positions. The Top Program Position is the highest level where a budget can be entered – the budgeted amounts are pushed down to the lower levels of management, i.e. the Investment Program Positions and the Internal Orders. This type of budgeting is referred to as "Top-Down" budgeting.

· Know the budgeted amounts for the program prior to executing the transaction.

Change Program Planning: Transaction Code: IM32

The instruction will walk the user through steps required to create a budget Supplement

· Original Budget
· Increased budget is required but original budget needs to remain unchanged

Create an Internal Order: Transaction Code: KO01 / KO02 / KO03

steps required to create an Internal Order.

· Determine the program type and order type prior to creating the internal order
· An internal order already existing can be referenced to minimize data input

Budget Distribution: Transaction Code: IM52

steps required to distribute the budget to measures (Internal Orders)

Create Overall Budget planning for IO: Transaction Code: KO12 / KO13

steps required to plan the budget of an Internal Order.

· Determine the program type and order type prior to creating the internal order
· An internal order already existing can be referenced to minimize data input

Display internal Order Actual Line Item: Transaction Code: KOB1

steps required to display an Internal Order Line Item.

Close Old Approval Year: Transaction Code: IM27_CLOSE

steps required to close an old approval year

· Existing Investment Programs
· A new approval year must have been opened prior to closing the old approval year
· Selection of orders can be filtered based on the order status

Open New Approval Year : Transaction Code: IM27

steps required to open a new approval year

Budget Carry Forward : Transaction Code: KOCF

steps required to carry forward budgets

Prerequisites
· An investment program with budget values

IM Reporting : Transaction Code: S_ALR_87012824 & S_ALR_87012813

steps required to run Investment Management Reports. This report is a drill-down report. By double-clicking on any line item it takes the user one level lower.

· Reports can also be executed from within each SAP module.

CO : Secondary Cost Element Categories

2010-03-01T03:20:00.001-08:00

21: Internal Settlement
Used to settle order costs or project costs to objects in Controlling (CO), such as orders, profitability segments, cost centers, and projects.

Cost elements of this category cannot be used for settlement to objects outside of CO (assets, materials, general ledger accounts, and so on). Use primary cost element category 22 for this purpose.

31: Order/Project Results Analysis

Used to store results analysis data from order/project results analysis on the order/project.

41: Overhead
Used to allocate overhead costs from cost centers to orders. This overhead rate can be material, sales, or administrative costs .

42: Assessment

Used to allocate costs during assessment.

43: Internal Activity Allocation

Used to allocate costs during internal activity allocation and for allocating process costs.

50: Incoming Orders: Sales RevenueUsed for sales revenues from sales orders with incoming orders in the current period of the project-related incoming orders.

51: Incoming Orders: Other Revenues

Used for other revenues, such as imputed interest from sales orders with incoming orders in the current period of the project-related incoming orders.

52: Incoming Orders: Costs
Used for the costs arising from sales orders with incoming orders in the current period of the project-related incoming orders.

61: Earned Value
Used for earned values from earned value analysis in the project system.

CO: Primary Cost Element Categories

2010-03-01T03:18:00.001-08:00

01: Primary costs / cost reducing revenues

This Primary Cost Element category can be debited for all primary postings, for example, in Financial Accounting (FI) or in Materials Management (MM).

Cost-reducing revenues are revenues that are to be handled in CO similarly to overhead costs, and which reduce the prices of an activity type or the costs to be assessed. This is the case, for example, with rent revenues, which reduce the room costs to be assessed. Cash discount amounts and exchange rate amounts are also cost-reducing revenues.

Note:
In contrast to revenues of cost element category 11, cost-reducing revenues in the CO module are typically assigned to cost centers. Note that when you use Profitability Analysis (CO-PA, costing-based) these cost-reducing revenues can only be transferred to Profitability Analysis during secondary allocations and not during invoicing.

03: Accrual Calculation Using the Percentage Method

You can only use this cost element category during accrual calculation in Cost Center Accounting (component CO-OM-CCA) when you are using the percentage method. You can post directly from FI to take account of the actual costs incurred. The system also uses cost elements of this category to post the accrual amounts within Cost Center Accounting CO-OM-CCA.

If you do take actual costs into account (say, for additional costs), create cost elements of this category in Controlling (CO) only. The account must be defined in the chart of accounts, but you do not need to create the general ledger account in FI.

04: Accrual Calculation Using the Target=Actual Method

Used in Cost Center Accounting (CO-OM-CCA) only for accrual calculation when you are using the target=actual method. You can post costs directly from FI to register actual costs incurred. At the same time, the R/3 System uses this category of cost element to post accrual cost amounts within Cost Center Accounting CO-OM-CCA.

11: Revenues
Used to post revenues. These revenues are generally posted during make-to-stock-production directly into the operating profit, or with make-to-order-production to the sales order.
In Controlling (CO) revenues are displayed with negative +/- sign. An exception to this is Profitability Accounting (CO-PA, costing-based), in which all values, including revenues, are displayed with a positive +/- sign.

Caution: If you post revenues to cost centers, the values are displayed as statistics only (for information purposes).

This means: You can repost revenues to other cost centers to correct postings, but other allocation is not possible.
Revenues are not taken into account during activity price iteration and are therefore not included in activity allocation prices.
Note: Revenues are generally defined as cost element category 11. This enables the integrated transfer of billing documents to CO-PA. An exception to this rule is cost-effecting revenue. See the section "Primary Costs / Cost Reducing Revenues".

12: Sales Deductions
Used to post deductable items (sales adjustments, sales corrections) such as discounts and rebates. Certain deductable items (freight charged separately in the invoice, surcharges for small quantities, special orders) are not classified as sales deductions, but as revenue elements.

You can use this category in the same manner as revenue elements (category 11). Values on cost centers are displayed as statistical only.

22: External Settlement

Used to settle order costs, project costs, or cost object costs to objects outside of CO. These objects could be assets (Asset Management), materials (Materials Management), or general ledger accounts (Financial Accounting). The R/3 System creates an accounting document when the costs are settled.

Cost elements of this category cannot be used for settlement within CO (cost centers, orders, projects, and so on). Use secondary cost element category 21 for this purpose. The R/3 System does not create an accounting document when costs are settled within CO.

90: Cost Elements for Balance Sheet Accounts in FI

Automatically assigned when you create cost elements in CO whose general ledger accounts in FI are asset reconciliation accounts (special balance sheet accounts), not income statement accounts. You cannot change this category in CO master data maintenance.

FI does not require CO account assignments to cost elements of category 90. However, if you enter an account assignment, it is only recorded statistically for true objects.

Category 90 cost elements enable you to check the budget of an order or project when you acquire fixed assets that can be directly capitalized. To do this, enter the capital investment order or the WBS element in the corresponding field of the asset master data. Asset Management (AM) ensures that the specified order or WBS element is automatically entered in the document during the asset acquisition.

In CO the order or WBS element is debited statistically. This statistical debiting is checked by the system using the budget during availability control.

Deletion of SAP Data - TCODE : OBR1, Program : SAPF020

2010-01-29T03:07:00.001-08:00

This program resets transaction data in a company code, initializes the number ranges, deletes data from test payment and dunning runs, and deletes cross-company code transactions and customer credit control data. The program also includes data from Special Purpose Ledger and Controlling if it is generated by transactions in Financial Accounting.
It deletes the following:

Document header supplement for recurring entries
Document header for Financial Accounting
Document segments

Financial Accounting document segment
one-time data document segment
bill of exchange field document segment
tax data document segment

Change documents
Document long texts
Financial Accounting: Secondary index for customers
Financial Accounting: Secondary index for customers (cleared items)
Financial Accounting: Secondary index for vendors
Financial Accounting: Secondary index for vendors (cleared items)
Financial Accounting: Secondary index for G/L accounts
Financial Accounting: Secondary index for G/L accounts (cleared items)
Secondary index for material documents
Index table for customer bills of exchange used
Customer master record transaction figures
Customer master record special G/L transaction figures
Vendor master record transaction figures
Vendor master record special G/L transaction figures
G/L account master record transaction figures
Cross-company code posting procedures
Customer payment history
Prenumbered checks
Payment medium file
Open item account with changed reconciliation account
Consistent payment run information
Consistent dunning run information
Held documents
Documents for external systems
Parked documents
Data for external tax systems
Information on business area allocation
Reconciliation postings from the company code's reconciliation ledger
Cash management data for the company code

Some fields are initialized for dunning control and customer credit control.

Customer master record (dunning data)
Vendor master record (dunning data)

date of the last dunning notice
dunning level
date of the legal dunning proceedings

Credit management: Control area data

total of the order values for checking the credit limit

total of the receivables for checking the credit limit

relevant special G/L transaction commitments for checking the credit limit

date on which the credit limit was exceeded

the indicator stating that the credit limit has to be reset, is set.

Controlling data which can be allocated to the company code to be deleted (also planning data), is deleted in the program run.

Requirements

Only switch on the "Cluster deletion off" field if you do not want to delete directly in the RFBLG cluster. This only makes sense if you have added your own fields to the BSEG and have defined your own matchcode objects for them, or you have set table logging for tables BSEG, BSET, BSED or BSEC. This is then also necessary to reset your own matchcode information and the log information. Note that the runtime will increase.

Note

You should always run the reset program in background processing since problems can occur during runtime even if you are just deleting or displaying small sets of data. Database changes, however, are made only in production run mode, and when they are made, the system writes a log entry in addition to the documentation.
If the company code you are deleting is found in a payment run and no other company code that is included in this payment run is productive, the program deletes the data of that payment run. The log lists the number of payment runs in which the test company code and a productive company code exist together. To delete these records from the system, you have to run your own programs. The same applies to test dunning runs.
If a primary cost element is in a controlling area that is assigned to a productive company code, the program does not delete any data in Controlling. The log then informs you of this situation, and lists the number of records per table that are not deleted.
In Special Purpose Ledger, the program deletes all standard ledgers in totals table GLT0 and GLT3, including the additional ledger for the respective company code. Furthermore, it deletes all nonstandard additional ledgers and nonadditional ledgers in the other totals tables. The remaining ledgers must be deleted using other, application-specific programs (certain consolidation ledgers).
If an error occurs in the deletion program for Special Purpose Ledger, the log lists the error text. You can display the long text using transaction SE91 by specifying the application area.
The reset program does not delete any documents that are being posted at the time of the program run.

A warning appears for non-productive company codes that are linked by means of the controlling area to the company code you are deleting. You can select "Suppress repetitive warnings" to limit these warnings so that only the first one appears.

SAP COPA : Account Based Vs Costing Based

2010-01-06T23:27:00.001-08:00

In Account based CO-PA:

1. You can't get Cost component break down.
2. No break down of variance categories.
3. Create a Characteristic in KEA5 and add to operating conern in KEA0. KEQ3 is to define segment level characteristics. To improve system performance, you can also restrict the characteristics that make up the profitability segment.
4. When you add a characteristic to operating concern, then by default that characteristic is available at the time of document entry. We use characteristic groups to determine what characteristics appear in which order on the screens for assigning profitability segments in different business transactions. If no characteristic groups are defined, the user can enter values for any characteristic in the operating concern.
5. Account based CO-PA uses the same tables (COEP, COEJ, COSP, COSS etc.,) as used by overhead cost management, whereas costing based COPA has it's own tables. The definitions of profitability segments for both CO-PA sub-modules are stored in the same table, the CE4XXXX table (where XXXX = operating concern).
6. Period account approach, unlike costing based which is cost of sales accounting approach.
7. Account-based CO-PA stores all transaction in three currencies: the transaction currency, the local currency, and the controlling area currency.

Text field in FI Document automatically from MIRO line item

2010-01-05T22:08:00.001-08:00

When a purchase order is created to a cost centre, G/L account and cost centre are entered manually. Often Purchase Order only uses short text field as reference, i.e., Material is not mandatory.

MIRO process is then done for PO after GR, and the PO text (short text) is copied into MIRO.

G/L account line items can be displayed in FBL3N, detailing the document numbers related to the invoice/PO once posted.

The field "Text" is defaulted as blank, even if created with reference to a PO, which contains text. Does anybody know of a way to automate process so that the text field is populated with the text from MIRO?

You can transfer what ever the data from the MIRO to accounting document-using BTE.

Go to SE37 - SAMPLE_PROCESS_00001120 (this is the standard BTE for account document posting). Copy this with ZSAMPLE_PROCESS_00001120.

In this you cannot modify the tables t_bkpf and t_bseg. you can use t_bkpfsub and t_bsegsub.

For this a little bit config is required.

1) Go to t-code FIBF-> settings->Products->... of a customer.

Click new entries -> product name- ZPRODUCT, text - any text, RFC dest - ZSAMPLE_PROCESS_00001120, A - enable check box -> save.

2) Go back -> settings -> P/S Modules -> ... of a customer.

Click new entries -> event - 00001120, Product - ZPRODUCT, Ctr - Country key, Appl - FI-FI, Function module - ZSAMPLE_PROCESS_00001120 -> save.

3) Go back -> settings -> Process Modules -> ... of a customer.

Click new entries ->Process - 00001120, Ctr - Country key, Appl - FI-FI, Function module - ZSAMPLE_PROCESS_00001120, Product - ZPRODUCT -> save.

Now go to SE37->ZSAMPLE_PROCESS_00001120 logic.

loop at t_bkpf.

loop at t_bkpfsub.

move 'your value' to t_bkpfsub-value.

modify t_bkpfsub index sy-tabix.

endloop.

loop at t_bseg.

loop at t_bsegsub.

move 'your value' to t_bsegsub-value.

modify t_bsegsub index sy-tabix.

endloop.

''Your value' is imported value.

No need to worry about modified values. After execution of BTE it will go to standard program and copy the values of t_bkpfsub] and t_bsegsub to SAP tables. So please be perfect with code. SAP wouldn't allow change the values in t_bkpf and t_bseg values. you can add your own fields in bkpf_subst and bseg_subst.

But make sure that; please write the code in FM with conditions like company code doc type etc. because this BTE is very important. It will execute before acc doc is posted. If you do not specify any conditions it will execute for all co codes in acc doc. it will affect business. You can debug this BTE. Put a break point in FM and see the values while post the MIRO.

Once import the values free memory id and clear the variables whatever you used in BTE.

Problem in spool requests from printing jobs in SAP

2010-01-05T00:01:00.001-08:00

Recently SAP has detected a problem in the spool area which affects all customers in the world regardless of the SAP release and any support package level. As soon as the retention time of a spool request exceeds 2009/12/31, a wrong date 2100/01/01 is entered during creation of the spool request. As a consequence these spool requests will not be deleted anymore from the spool reorg jobs. Using the default retention period this affects all spool requests on each SAP system in the world created since 2009/12/23.

Please refer the SAP note 1422843 for further details. The SAP note 1422843 is to be implemented immediately in all the SAP systems. There is a ABAP report attached in this note 1422843 for the SAP Basis releases 46C to 7xx releases. This report is to be imported in all the SAP systems in the transaction SE38 schedule a periodic job, with a period analogous to the spool reorg job with the report as step, before the real spool reorg job.

Business Transaction Events (BTE) Guide : FI Enhancement Technique

2009-12-18T01:17:00.001-08:00

This article provides a step-by-step guide on the usage of Business Transaction Events, as an Enhancement technique in the Financial Accounting Module of the SAP R/3 system. The Open FI enhancement technique was developed in the Financial Accounting component.

It can be used as Validation, Substitution, Processing point, etc. It works based on the event like FI document simulation, before saving the FI document, after saving the FI document,

Click here for the full version of the document....BTE

SAP Tables for Technical Consultants & also for Function Consultants !!!

2009-12-18T01:09:00.001-08:00

Tables on below topics :

Authorisation, objects, Batch input map's, Batch jobs,Correction & transport, Countries, Currency, Data elements, Development classes, Domains, Dynpro areas, Filenames, Function modules, Function groups, Icons, Logical databases, Matchcodes, Messages, Programs, Repository objects, Purchase Requisition, SAPscript, Spool, Status (menu), Switch objects, Tables and views, Texts, Transactions, User parameters, Variants, Accounting, Accounting documents, Bill Of Material, Classification, Classification characteristics, Configurator, Cost elements, centers, activities, Customer,Equipment, Equipment status, Function location, Customising tables, General ledger accounts, Goods movement, Customising, Inventory document, Maintenance Order, Material, Material document, Notifications, Orders,Personel, Production resource tools, Customising tables, Project, Purchase Requisition, Purchasing document, Purchasing info record, Reservation, Sales Document, Sales requirements, Storage locations and stocks, Tasklist, Transfer requirement, User data, Vendor master, WM transfer, Other tables, Useful Transactions, Function modules, Standard data transfer, Helpful reports.

Click on SAP Tables for the document.

SAP Technical Upgrade – Tips and Tricks

2009-12-16T03:29:00.001-08:00

Overview

This article describes SAP upgrade projects: What steps to follow in an upgrade, what points to be taken care of, what are various prerequisites, etc. The SAP technical upgrade scores for a short duration project ? 20 days to around 3 months duration. In technical upgrades, we aim to get the same or better SAP functionalities in the new system (SAP ECC 6.0) as in the old system (SAP 4.6).

Click here for the full version.....Technical Upgrade

SAP CIN: Uploading of Excise Balances - during Cut Over

2009-11-27T09:21:00.001-08:00

Check the below master & config data in the system before the upload of balances.

GL Accounts, Tax codes and Withholding tax codes, Cost Elements, Cost Centres, Material master, Vendor & Customer Master, CIN Masters, User Profiles

Quantity Balance : TCODE: J1I5

RG23A Part1 -: Stocks of all raw materials - movement type 561.

RG23C Part1 -: Assets (as a non-valuated material) - movement type 561

RG1/DSR - :J1I5 : Stocks of all finished goods - the movement type 561.

GL and Register balance:

RG23A Part2 & RG23C Part2 - pass an Excise JV – The credit account has to be changed to the initial GL balance upload account.

Transferring of balance credit to RG23C Part2 - Posting a normal FI-JV shall transfer the balances of the CENVAT-On-Hold account during the GL balance upload. However, the subsequent credits to RG23C Part2 on account of these purchases is to be posted using an Excise JV- Additional Excise and the credit entry should go to the CENVAT-On-Hold account.

PLA - FI-JV is posted to debit the PLA-On-Hold account for the initial balance.

Number ranges:

Number Range Object	Description
J_1I57FC	57AC5 Number Range
J_1IEXCEXP	Export Excise Invoice Number
J_1IEXCLOC	Local Excise Invoice number
J_1IINTNUM	Internal document number
J_1IPLA2	PLA part2 serial number
J_1IRG1	RG1 number Range
J_1IRG23A1	RG23A Part1 serial number
J_1IRG23A2	RG23A Part2 serial number
J_1IRG23C1	RG23C Part1 serial number
J_1IRG23C2	RG23C Part2 serial number
J_1IINTPR2	Despatch Register serial number

RG23A, RG23C Part I, RG1 Balances required to be uploaded (material wise, Plant wise) after proper reconciliation with the production records. For this the respective Plants are requested to reconcile the same before upload.

Reconciliation of balances
Please ensure that proper reconciliation process/measures are in place. All excise balances are required to be signed off before allowing business transactions.

SAP-FICO: Overview of EC-CS Consolidations

2009-11-23T00:38:00.001-08:00

Consolidating multiple companies into a unified, consolidated set of financial statements is an art form. In SAP, two common ways of producing consolidated financials are EC-CS (Enterprise Controlling – Consolidation System) and through reporting in BW (Business Warehouse). This post deals primarily with EC-CS.

EC-CS gives you a means of rolling up multiple company codes into a unified set of books. If you use multiple charts of accounts, the best option is to create Group Chart of Accounts and map your other charts to it. Your Group Chart of Accounts can then feed into your Consolidation Chart of Accounts.

Features of EC-CS

Consolidate multiple company codes
Import data from the General Ledger to cons units
Manual and automatic eliminations between Consolidation Units (cons units are tied to a Company, which is tied to a Company Code(s))
Eliminations within a cons unit
Reclassifications
Database viewer to view imported records, elimination/reclass records, and manual journal entry records
Upload data from Non-SAP systems (set up this feature in: CXCC). I'm not familiar with the capabilities of this function
Report Painter reporting (GR55)

You can report your consolidated financials either through BW or through Report Painter reports (T-code: GR55). For Report Painter, you will need to create a reporting Library (T-code: GR21), utilizing table FIMC. You'll also need to specify your consolidations ledger while building your reports in GRR1 (or GR52).

Basic T-codes for EC-CS

CX16 – Consolidation Chart of Accounts – Hierarchy Change - allows you to build your Consolidation Chart of Accounts within a hierarchy

CXCD – Data Montior - allows you transfer financial data from the SAP General Ledger into the consolidations ledger

Database Listing of Records - In CXCD, click Goto/Database Listing of Records. This allows you to view the items imported from the General Ledger as well as manually posted items. You can limit by Posting Level which indicates the type of record being viewed.

CX20 – Consolidation Monitor - The Consolidation Monitor allows you to:

Eliminate inter-unit payables and receivables
Eliminate inter-unit sales
Eliminate investment income
Perform manual eliminations
Consolidate investment income
Perform manual reclassifications
Validate consolidated data

Number Ranges entry DELETION !!!

2009-11-18T22:04:00.001-08:00

In case of number range intervals for a specific document type for the years like 2009 & 9999. Some times client may ask to maintain only interval for all the years, in such case number ranges already available for that specific range should delete.

Fallow the below procedure :

For deleting the interval, you must first reset the status of that number range to zero, that means put the zero in the current number.

e.g. Current number is 70885200

Reset the current number status in every year for which you want delete.

Once the status becomes zero, delete the interval.

Create the interval agian for 9999 year only.

Set the current number in 9999 year to the previous value (i.e., 70885200).

COPA Char / Value fields : Description change

2009-11-09T01:30:00.001-08:00

If you want to change the description of a characteristic or value field you must change the descriptions of the related data element.

Therefore you need to perform the following steps:

In KEA5 / KEA6, type in the name of the characteristic/
value field and click on the create / change button
On the next screen, double click on the data element of your
characteristic/value field
On the 'Display Data Element' screen, click on the tab strip
"Field label". You can see the four field lables short, medium, long
and heading. You should change all four field labels and then
regenerate the data element. After having done this you may have to
to regenerate the characteristic/value field and the operating
concern.

Leading ledger & Non-leading ledgers

2009-11-08T22:25:00.001-08:00

Leading ledger

It is a base ledger, which updates the cost center and consolidation.
You can define only one ledger as the leading ledger – SAP provides the leading ledger "0L".
The currency of the leading ledger is always used as the first currency.
The leading ledger is integrated with all subsidiary ledgers.
Only the values from the leading ledger are sent to CO.
The leading area in Asset Accounting (depreciation area 01) must be posted to the leading ledger.
Leading ledger uses the (additional) local currencies assigned to the company code.
Leading ledger uses the GL Total Table: FAGLFLEXT.

Non-leading ledgers

Non-leading ledgers are activated by company code.
You can define additional currencies that deviate from those used by the leading ledger.
As a second and third currency of a non-leading ledger, you may only use currency types that you have already assigned to the relevant company code for the leading ledger.
You can define a fiscal year variant that differs from the leading ledger. If you don't specify a FYV, the FYV of the company code is automatically used.
You can also define a posting period variant that differs from the leading ledger.
Separate document types and number ranges can be defined for non-leading ledgers by users, to ensure continuity in ledger numbering.
Non-leading ledger updates the profit center, segment.
The non-leading ledgers are used as parallel ledger together with the leading ledger. This can be used to apply different accounting standards, such as IAS/IFRS or US-GAAP