SAP FAQ

Try Some Interesting Way to Earn Income !!!

2011-07-14T03:15:00.001-07:00

Hi ,

I have something interesting for you - you can easily earn regular income online via PaisaLive.com!

It's really amazing! You get paid to open & read the contents of PaisaLive mails. You also receive special discount coupons, promotions and free passes to various events in your city.

Join now and get Rs. 99 instantly, just for joining. What more, as a special bonus you get paid for inviting your friends also!

Create your PaisaLive Account & refer your friends to earn launch referral bonus on every new registration.

http://www.PaisaLive.com/register.asp?3699120-5247249

PaisaLive - Get Paid to read emails

Try This Some Interesting Way to Earn Income !!!

2011-07-14T02:27:00.001-07:00

Hi ,

I have something interesting for you - you can easily earn regular income online via PaisaLive.com!

It's really amazing! You get paid to open & read the contents of PaisaLive mails. You also receive special discount coupons, promotions and free passes to various events in your city.

Join now and get Rs. 99 instantly, just for joining. What more, as a special bonus you get paid for inviting your friends also!

Create your PaisaLive Account & refer your friends to earn launch referral bonus on every new registration.

http://www.PaisaLive.com/register.asp?3699120-5247249

PaisaLive - Get Paid to read emails

TRIED IT AND WAITING FOR THE RESULT !!! TRY YOURSELF AND LET ME KNOW.....GOOD LUCK FOR THE DAY!!!

Regards

Ramana

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 : Define Substitution

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

Define Substitution:

With Substitution, you can define the correct value in a particular field. This happens in the background. Substitution happens for all the accounting documents for which the said prerequisite statement satisfies. Substitution changes the value in that particular field, if it contains any data. This happens even when you change the document also. So, be cautious while designing the scenario in relation to substitution.

A substitution step contains the following statements:

• Prerequisite statement:

a. The prerequisite statement establishes which conditions must be fulfilled before the substitution can be performed.

i. If the prerequisite statement is false, the transaction is continued without substitution.

ii. If the prerequisite statement is true, the transaction is continued with the substituted values.

• Substitution value(s):

b. The substitution value is a numerical value or a string of letters that replace the value entered.

c. A single substitution process can replace more than one value.

• Substitution exit:

d. You can specify that substitution is to be performed through a substitution exit.

e. The substitution exit number directs the system to an ABAP program defined by the user.

f. Substitution exits enable you to define more complex substitutions and replace more than one value in a substitution.

g. The prerequisite statement used in a substitution can consist of a simple statement or a complex combination of statements composed of logical statements, rules, and sets.

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: ASAP Implementation Check List !!!

2011-01-08T23:31:00.001-08:00

ASAP Implementation check list, gives you the details in brief.

You can find details each phase wise.

Click here for the file.

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: FI-AP: Possible F110 Errors !!!

2010-12-29T04:43:00.000-08:00

Payment proposal & & has not yet been created
Payment proposal & & cannot be changed again
Company codes &/& do not appear in proposal & &; correct
Company code & does not exist; correct
Payment method & is not defined in country &; correct
Enter a payment method for incoming payments
Enter a payment method for outgoing payments
Payment method & is not defined in company code &; correct
Payment run & & has not yet been carried out
& is not a house bank for company code &; correct
No G/L account has been specified for & /& for the bank
Customer/vendor does not have suitable bank details for pmnt method &
No bank has been chosen; use different payment method
Select customer's/vendor's bank details
Payment method & is not defined for this payment run
New allocation only possible if item is unblocked
No items found with the relevant values
Account & is contained in proposal & &; release not possible
Account & & is currently blocked; try again later
Special G/L transaction for exception list; it cannot be changed
Inconsistency after error; changes not saved cancelled
Do not place the cursor on a line with exceptions
Block key & cannot be set in the payment proposal
Bank data for house bank & & has been deleted
Required address data missing; please maintain (see long text)
Address data read from master record
Required address data missing from document; choose another payment meth.
There are still bills/exch. for presentation in unprocessed BI sessions
Doc.currency & and country currency & of presenting country are different
No number range could be found for the payment orders
A number could not be assigned for the payment order
Company code & for & & is blocked by user &
Item in excep. list cannot be changed because belongs to sending CoCde &1
Payment proposal being checked against payment budget....
Account & & is blocked against payment
Only the following accounts can be used: &1
Bank data for country & bank key & has been marked for deletion
Missing authorization in company code & (activity &)
Proposal run &1 / &2 does not exist
Payment run &1 / &2 does not exist
Proposal run &1 / &2 processed: &3 vendor(s)/customer(s) blocked
Changeable payment blocks are not allowed in proposal processing
Payment run &1 &2 is intended for cross-payment run payment media
The payment runs selected cannot be processed together
Error when creating the payment medium run
&3 payments were selected
Payment run is not a payment medium run
Payment medium run was reset
No data records found for these selection criteria
No documents can be displayed for proposal run
Only documents for FI payments can be displayed
You are not authorized to delete this object
You have no authorization for company code &
You have no authorization for FI proposal run
You only have authorization for FI payment run
You have no authorization for HR payment runs
You only have authorization for HR payment runs
You have no authorization for FI payment runs
You have no authorization for FI proposal runs
Function module WS_VOLUME_SET with error &
Payment advice note & already exists
Payment document advice note & does not exist
Error during deletion of the payment document advice note
Processing terminated. No payment advice note created.
This function cannot be executed for payment demands.
IDOC & is being called up for display
Not possible to process IDOC data
Incorrect display of IDOC
Only IDoc data can be processed
Data for payment IDoc & archived.
Internal error archiving data for payment IDoc.
Archiving cannot be completed.
... payment not possible because of reported error
Posting for account type & should be carried out with posting key &
For document type &, account type & is not defined
G/L account & does not exist in company code &
Withhld.tax for cntry & curr. & code & withhld.tax cntry & not defined
G/L acct & in comp.code & is not a reconciliation acct for acct type &
No posting keys have been defined for company code clearing &, &
G/L account & & is a reconciliation account, so cannot be posted to
G/L account & & only allows & as foreign currency but not &
For account & & period & / & has not been opened
For company code & period & / & has not been opened
The posting keys are not specified completely for transaction &
Sp.G/L indic. & is not permitted for bill of payment exchange requests
Special G/L indicator & is only permitted for statistical postings
Company code clearing not possible for comp.code & vendor & customer &
Account & & for cash discounts must not have a tax code
Proposal run & & has already been carried out and edited
Payment run & & has already been carried out
Customer & & is already contained in proposal & &
Exchange rate from & to & not maintained at posting date
Document number & & already assigned (incorrect status in no.range &)
In company code &, document number range & is missing for &
Bank acct cannot be determined for co.code & bank & pmnt method & curr.&
In country & the definitions for pmnt method & were deleted
Fiscal year variant & is not defined for comp.code &
In fiscal year variant & no period is allocated for &
Proposal run & & has already been carried out
Customer & & : Alternative payer & is missing, cannot be processed
...none of the payment methods defined can be used for these items
Customer & & is contained in proposal & &; no editing
Vendor & & is contained in proposal & &; no editing
More than 50 accounts are contained in another payment proposal
Processing will be stopped, no items have been edited
Different trading partners & and & in payment document
Purchase order & (assigned to an account) not permitted
Overlap with payment run & &
Parameters could not be read
Customer & & is blocked, editing not possible
Vendor & & is blocked, editing not possible
Company ID not specified for company code &
Business transaction cannot be processed by consolidation
Tax calculation procedure not defined for company code & in country &
Master data for branch or payee & is missing
Payment amount & falls short of minimum amount of & &
In company code & the definitions for pmnt method & were deleted
Vendor & &: No payment due to delete flag or posting block
Customer & &: No payment due to delete flag or posting block
Synchronous update could not be activated
Selected and as yet unassigned bills of exchange (amnt in &): Total &
Payment amount in &: &
Rate from & to & on & for rate type & is missing in rate table
Vendor & & does not exist for company code clearing
Customer &1 &2 for vendor &3 is blocked
Customer &1 &2 for vendor &3 is blocked by &4
Vendor &1 &2 for customer &3 is blocked
Vendor &1 &2 for customer &3 blocked by &4
Document & & &: payment block changed by BTE 00001820 in &
Document & & &: payment method changed by BTE 00001820 in &
Customer &: no payment in company code & due to balance block
Vendor &: no payment in company code & due to balance block
Payment with currency &1, payment method &2: No valid payment procedure
Different payer (customer &) and clearing not possible concurrently
The payment document is to receive too many items
... the execution of the payment program is terminated
Item is blocked for payment
Account is blocked for payment
Alternative payee is blocked for payment
No valid payment method found
Error in creating the payment document; read job log
Error in editing the document; read job log
Payment method in the document should not be considered in this run
A breakdown of the line items on the payment forms was not possible
Minimum amount for payment has not been reached
Item is blocked for payment, lost cash discount imminent
Account is blocked for payment, lost cash discount imminent
Payee is blocked for payment, lost cash discount imminent
Pmnt methods for this run are not specified in master record or in item
Special G/L transaction which only appears on the exceptions list
Payment request: no payment, original document will be paid
Payment request: no payment, original document is cleared
+/- sign for local/for.curr.balances are different, pmnt not possible
Preliminary payment: no clearing, since original document not paid
Clearing document type for debit side transfer posting is not defined
Clearing document type for credit side transfer posting is not defined
Master data is missing for branch or payee
Due date is too early for the bill of exchange payment method in question
Different payer during clearing is not supported
Inconsistency between payment request and document
Account has been flagged for deletion
Payee flagged for deletion
Unconfirmed change to master record
Unconfirmed change to payee master data
Change to master data refused
Refused master record change for payee

SAP: Validation & Substitution

2010-12-06T08:28:00.001-08:00

Validation, which validates the values entered by the user.

Substitution, which substitutes the correct values by removing the wrong values entered by the user.

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: CO - COPA Document not created

2010-08-31T23:39:00.000-07:00

1. COPA not activated in TCODE:KEKE - with this you can transfer actual postings from SD, FI, CO & MM.

2. From SD
    - if Condition type not assigned to Value field
    - if Condition type not active

3. From MM
    - if Condition type not assigned to Value field
    - if Condition type not active

4. From FI
- Either source or value field not assigned in the PA transfer structure.
- In case of "Default account assignment", if PS is activated and value not flown means then the issue must be in derivation.

5. From CO
- Missing CO Number ranges - TCODE: KEN1

Consolidation SEM BCS Vs EC CS

2010-07-21T06:39:00.001-07:00

1. BCS is Business consolidation and Simulation and EC CS is Consolidation and Simulation in ECC 6.0

2. SEM BCS and ECCS both are consolidation applications of SAP System.
3. ECCS is based on R/3 where as SEM BCS is based on BW.
4. BCS is entirely out side R/3 and EC CS is R/3, here they have included some features in R/3 for consolidation and at the same time BCS is out side R/3 and has more features....while taking the reports then you take help of BW... end of the day you will get the data from R/3 even for BCS also.

SEM-BCS –Functional advantages compared to EC-CS -

- Easier integration to remote SAP systems or non-SAP systems via BI
- Approval workflow for documents **
- Copy function and flexible upload for all posting levels **
- Deferred taxes –balance sheet approach **
- Inter-unit profit elimination in inventory with supply chains
- Inter-unit profit elimination in inventory with equity method
- Inter-unit profit elimination in transferred assets
- Hidden reserves and contingencies
- C/I –read investment data from totals database
- C/I –flexible treatment of goodwill in acquisitions
- C/I –posting of goodwill on subsidiary
- Allocation
- Restatement infrastructure **
- Web-enablement for functionality used by local accountants **

SEM-BCS –Missing functionality compared to EC-CS *

- Mass change of items and consolidation units
- Real-time update from FI
- Sample documents and parked documents **
- Currency translation –method * is no longer available
- C/I –statement of changes in equity
- Encapsulated function modules to be used within custom-defined tasks
- Multi-period consolidation **

* based on ERP 2005
** may be provided via ERP 2005 enhancement package

source: sap service market place

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

Running new GL and traditional GL at the same time

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

Refer to the following OSS Note for all migration queries

1070629 - FAQs: New General Ledger Migration

Read question 23 for "Running new GL and traditional GL at the same time"

23. You want to configure a new company code with the new general ledger. The existing company codes use the classic general ledger. Can company codes use different general ledgers (classic and new) in the same client?

The implementation of a new company code and the transition from the classic general ledger to the new general ledger are two different projects which you must schedule at different times.
You perform the migration from the classic general ledger to the new general ledger at client level and it affects all company codes in this client.

Because the new general ledger is activated at client level, the new general ledger would be active for all company codes, not only for the new company code. This would mean that the new general ledger is active in the old company codes, but there was no migration from the classic general ledger to the new general ledger. This is not possible.

Therefore, it is not possible to start with a new company code in the new general ledger while the classic general ledger is still active in other company codes in the same client.

First implement the new company code. Then set up the project for the transition from the classic general ledger to the new general ledger.

Alternatively: First set up the project for the transition from the classic general ledger to the new general ledger and migrate the data to the new general ledger, then implement the new company code.

Benefits of New General Ledger over the Classic General Ledger

2010-04-23T01:49:00.001-07:00

The new General Ledger in mySAP ERP has the following advantages over the classic General Ledger in R/3 Enterprise:

a) In the new General Ledger, you can display the parallel accounting using parallel accounts (as in R/3) or using parallel ledgers. The FI standard functions and reports are available for all parallel ledgers.

b) The 'Segment' entity and the relevant reporting that are required for segment reporting according to IAS and U.S. GAAP are available in the new General Ledger.

c) In addition, you can enhance the new General Ledger flexibly, that is, you can enter user-defined fields and update the relevant totals. Many standard reports can evaluate the information from the user-defined fields.

d) When you use the new 'Document Splitting' function (online split), you can create financial statements at company code level and, if required, for entities, such as the segment. For each document, the system then creates a zero balance
for the relevant entity, for example, for the segment.

e) As a result, you no longer have to carry out time-consuming reconciliation tasks between FI and CO for the end of period since cross-entity processes are transferred in real-time to the new General Ledger in Controlling. Furthermore, you can, for example, navigate from the financial statements report results or the profit and loss statement report results to the relevant CO report.

f) The new General Ledger uses the same interfaces as the General Ledger in R/3. As a result, users do not require any additional training.

g) Due to the new 'multi-dimensional' aspect in the General Ledger, all data that is relevant for the General Ledger is stored in one environment. As a result, reconciliation tasks, for example, between the general ledger and Profit Center Accounting or the consolidation staging ledger, and processing steps that have to be carried out repeatedly in the individual applications (for example, balance carryforward are no longer required. When you use the new General Ledger, you may not have to use the special ledger anymore.

Finding what tables and fields lie behind an SAP transaction

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

The question "what is it doing and why ?" is a pretty standard part of the BASIS person / teams day. It can be in the context of debugging a program or process, or trying to work out what configuration changes are required to make something work. An example of when thius gets escalated to BASIS is when the development or functional team have moved on, leaving someone who knows what to do but not why – usually a user (under pressure from their boss) who just wants to get the system doing what they've been told it should be doing….

However, your BASIS team (or person) has to be a jack of all trades, but also a working knowledge of Networking, Desktop PCs, the Operating System(s) and Databases(s) their SAP systems are running on and so on, as well as being able to answer SAP functional questions.

Read Full Story here...

Author: Martin

Source: sdn. sap. com

SAP: OSS - Finding notes

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

Does needle in a haystack sound familiar? This documentation is meant to give you a starting place. Remember there are many different ways to find OSS notes. Explore your own. If you find one that works well, please add your comment.

Read full story here

Author: Michell Crapo

Source: sdn. sap. com

Billing document to COPA partially transferred !!

2010-03-05T02:58:00.001-08:00

Check the below for possible reasons:

1. Check the whether the Condition type is assigned properly to the value field.

2. Cost elements used in this case must be created with CElem category must be either 11 (Revenue element) or 12 (Sales deduction)

3. Conditions can be statistical or non-statistical, but the cost element defined for the G/L account must be of type '11' or '12'.

4. Tax conditions are not posted in CO-PA

5. All conditions in an item must be active (inactive conditions are not transferred to COPA)

Sample Questionarie : For Functional Upgrade to ECC 6.0 from 4.7

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

For Functional Upgrade to ECC 6.0 from 4.7 below are some of the questions :

1. The list of implemented modules
2. The list of used transactions/proceses
3. The list of modified by customer standard SAP objects
4. The list of own objects
5. The list of add-ons
6. Landsacape map with all iinterfaces

.....

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.

Guidelines for LSMW Data Transfer for PM, MM, and SD Modules

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

This document briefs about general guidelines during master data transfer via LSMW tool in PM, MM and SD modules during implementation stage. Mostly suitable for consultants who are rigorously uploads data through this tool. This will help as a handy dictionary to refer in case any kind of error occurs while data uploading in LSMW.

Click here for the full version....LSMW Data Transfer

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 - FI AR : Configuration of Dunning - Customer / Vendor

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

SAP Dunning, which is mainly used in processing of collecting the customer payments.

Sometimes your business partners may fall behind on payments. You can send them a payment reminder or a dunning notice to remind them of their outstanding debts. The R/3 System allows you to dun business partners automatically. The system duns the open items from business partner accounts in which the overdue items create a debit balance.

The dunning program selects the overdue open items, determines the dunning level of the account in question, and creates a dunning notice. It then saves the dunning data created for the items and accounts affected.

You can use the dunning program to dun both customers and vendors. It may be necessary to dun a vendor if he or she has a debit balance as a result of a credit memo. If a customer is also a vendor, you can offset the account balances against one another.

Click on Dunning for downloading the "Configuration of Dunning - Customer / Vendor"

How to Configure Reconciliation Account Determination

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

The configuration of reconciliation account determination is similar to revenue account determination.

In some cases, a company will want to separately identify customer receivables. A good example is when a customer pre-purchases a credit which it plans to use in the future against specific types of purchases, e.g., prepaid training credit which the customer gets when they purchase a large piece of machinery. In the accounts receivables, a credit will have to be shown, and when the customer purchases a training course, the cost is deducted from the credit, not billed to the customer.

This example shows how to configure reconciliation account determination for invoicing to make the cost and credit go to a separate account, and how to configure a special G/L indicator to allow manual adjustments of this account in FI-AR module.

Click on "Reconciliation account" to download the configuration.

How to enable the cache memory in SAP R/3 ?

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

Hi VVR,

Can you tell me how to enable the cache memory in SAP R/3? In Whole landscape, for some cache is working and for some it is not.

Please let me know the setting I can enable the cache memory.

I am facing a lot of problems like noting down all the documents and field entries i have typed earlier to test.

Good to see the site for more configurations i dont know and good portal to develop the SAP knowledge esp. in configuration.

Thanks & Regards,

Muthuvel Rajan S

Goto the SAP GUI Help :

In that you can see "Adjusting the Local Layout". If you click on that you will get more items in that select the "Local Data Settings". There you can see the options about the History. If it is "Off" you will see blank space with some text in there. In your case may be it is "off". Check with the other systems (Developemnt/Sand box) may be you can see the details. This is normally controlled by the BASIS people.

SAP BAI, BAI2 flat file format?

2009-11-23T03:05:00.001-08:00

This file is used for SAP financial purposes and this does interact mainly with the Banks. Banks have different format like BAI, BAI2 etc. BAI and BAI2 formats differ in their level of information detail. BAI does not separate out the incoming check line items by invoice subtotal reference. Conversely, BAI2 splits the check total into separate invoice references and associated payment amounts. As a result, your hit rate percentage of payment-invoice matching from each transmission is likely to be higher when using BAI2 rather than BAI formats.

Usually how we approach (when we receive the file) is we will read the legacy file with file adapter and then will convert into the BAI file format and drop the converted file on a shared drive. There are standard programs in SAP which picks this file and loads the data in sap. If your client has different structure then the ABAPer may need to change the program accordingly.

The Bai file format you can take a look here:

DOCUMENTATION ON THE FORMAT

Also please look into this help:

Note 86952 - Electronic bank statemt:BAI format (you can see the standard programs here)

NOTES ON BANK STATEMENT

The bottom line is the standard program in SAP expects this format and using PI will make this file from your legacy file

Differences between SAP EC-CS and BCS

2009-11-23T01:44:00.001-08:00

ECCS is R3 based consolidation system while SEM BCS is on top of BI or BW
server. There are following differences in ECCS and BCS.

BCS, integrated into SAP's Business Intelligence (BI) system, is a component of Strategic Enterprise Management (SEM)
Integration of BCS into Business Intelligence, not SAP R3, requires data to be transferred from FI R3 to the FI cube in BI
Data is consolidated in Cube thus it improves performance
The inclusion of BCS into SAP's BI allows a tight integration between Consolidation Processing and Consolidation Reporting
BCS BI Reporting provide a great deal of flexibility, allowing the user to select & analyze data to meet their specific business needs!
Can work with two conso units in one Data Set. Cost accounting values can be stored and can be used for reporting purpose.
BCS includes the following new tasks that were not included in ECCS:

Use of one monitor, including both Data and Consolidation tasks
Period Initialization
FIGL Datastream
LC Trial balance
Allocation
Elimination – IC Operating Lease

What is this darn Internal Order…, many guys keep asking?

2009-11-18T23:03:00.001-08:00

Let me give you an example which will remove this doubt forever.

Lets say in an organization there are various events such as trade fairs, training seminars, which occur during the year. Now lets assume for a second that these Trade fairs are organized by the Marketing cost center of the organization. Therefore in this case marketing cost center is responsible for all the trade fairs costs. All these trade fairs costs are posted to the marketing cost centers. Now if the management wants an analysis of the cost incurred for each of the trade fair organized by the marketing cost center how would the marketing manager get this piece of information across to them?

Now this is where Internal Order steps in .If you go through all cost center reports this information is not readily available since all the costs are posted to the cost center.

SAP, therefore provides the facility of using internal orders which comes in real handy in such situations. In the above scenario the controlling department would then need to create an internal order for each of the trade fair organized. The cost incurred for each of the trade fair will be posted to the internal orders during the month. At the month end, these costs which are collected in the internal order will be settled from these orders to the marketing cost center. Thus the controlling person is now in a position to analyze the cost for each of the trade fair separately.

Click on the below Config on Internal Order for FREE CONFIGURATION NOTES ON INTERNAL ORDER.

Config on Internal Order

SAP FICO Reports : Most Used & Most Important

2009-11-04T01:15:00.001-08:00

Report Name	Transaction Code	Purpose
General Ledger:
Recurring Entry Documents	S_ALR_87012346	You are able to determine which documents: · are carried out in a particular time period · are not carried out · are carried out during the next run of the recurring entry program
G/L Account Statements	S_ALR_87012332	You use this Report to create Statements for Customers / Vendors / G/L Accounts. The primary difference between this report and other item lists for the entry view (line item lists for customers, vendors, and G/L accounts) is that it can be used to produce item lists for G/L accounts without line item display in the entry view.
Financial Statement	S_ALR_87012284	You use this report to create the balance sheet and profit and loss statements for a user-defined reporting period within a fiscal year with absolute and relative comparisons for a comparison period.
Financial Statement: Actual/Actual Comparison	S_PL0_86000028	You use this report to compare actual data within a certain period to reference data from another period.
Compact Document Journal	S_ALR_87012289	You use this report to display the most important data from document headers and items in table form for the selected documents. The list can be used as a journal and for reconciliation with the lists of account balances (accounting reconciliation).
Line Item Journal	S_ALR_87012291	You use this report to create an overview of the selected posting documents.
Advance Return for Tax on Sales/Purchases	S_ALR_87012357	You use this report to create the advance return for tax on sales/purchases. If required, you can also create a batch input session for automatic transfer posting of tax payable or fill out the tax return.
Chart of Accounts	S_ALR_87012326	You use this report to display G/L account master data that is not specific to the company code and print out G/L account lists.

Fixed Assets:
…by cost center	S_ALR_87011979	You use this report to create a fixed asset report by cost center.
…by asset class	S_ALR_87011981	You use this report to create a fixed asset report by asset class.
Asset Balances	S_ALR_87011994	You use this report to create an Asset Balance and display values of fixed assets.
Asset Transactions	S_ALR_87012048	You use this report to display asset transactions. For each document, the report shows: · the change to the acquisition and production costs · the change to the value adjustments · the ordinary and special depreciation planned for this transaction
Asset Acquisitions	S_ALR_87012050	You use this report to display asset acquisitions.The following is displayed for each document: · Acquired APC · Acquired quantity · Planned ordinary and special depreciation for the acquisition
Asset Retirements	S_ALR_87012052	You use this report to display asset retirements.Each document shows the · Retired acquisition and production costs · Retired quantity · Retired proportional depreciation · Earned revenue · Gain/loss · Possible retirement costs

Cost Element Accounting:
Controlling Documents: Actual Costs	KSB5	You use this report to display actual cost documents. The program creates a Document with all actual Costs as required.
Internal Orders: Master Data Report	KOK5	You use this report to display Internal Order Documents.

Cost Center Accounting:
Cost Centers: Actual/Plan/Variance	S_ALR_87013611	You can use the Report/Report-Interface to access the following reports: · Cost Centers: Actual Line Items · Cost Centers: Planning Overview · Cost Centers: Plan Line Items · CCtrs: Period Breakdown Actual/Plan · Activity Types: Period Breakdown · Stat. Key Figs: Period Breakdown · Cost Centers: Breakdown by Partner · Cost Centers: Breakdown by B.Trans. · Area: Actual/Plan 2 Currencies · Display planning long texts
Range: Cost Centers	S_ALR_87013612	You can use the Report/Report-Interface to access the following reports: · Cost Centers: Planning Overview · Cost Centers: Actual/Plan/Variance · Area: Cost Elements · Cost Centers: Breakdown by Partner · Cost Centers: Breakdown by B.Trans
Range: Cost Elements	S_ALR_87013613	You can use the Report/Report-Interface to access the following reports: · Cost Centers: Actual Line Items · Cost Centers: Plan Line Items · CCtrs: Period Breakdown Actual/Plan · Cost Centers: Planning Overview · Cost Centers: Breakdown by Partner
Cost Centers: Planning Overview	KSBL	You use this report to create a planning overview for all cost centers.
Range: Actual/Budget/Commitments	S_ALR_87013648	You use this report to create an overview for each cost center of the · Actual costs · Commitments · Allotted costs · Budget
Cost Centers: Activity Prices	KSBT	You use this report to create a List of Activity Prices by Cost Centers or Cost Center Groups

Internal Orders:
Orders: Actual Line Items	KOB1	You use this program to create a report for Actual Line Items for Orders.
Orders: Commitment Line Items	KOB2	The program creates a Report for Commitment Cost Line Items for Orders as required.
List: Orders	S_ALR_87012995	You use this program to create a List of all Orders by Controlling Area for a Plan/Actual Comparison.
Orders: Actual/Plan/Variance	S_ALR_87012993	You use this program to create an overview of the actual and plan data on internal orders in the reporting time frame for each Cost element, Cost element group and Statistical key figure.
Order: Planning Overview	KABL	You use this program to create a planning overview by Order.
List_ Budget/Actual/Commitments	S_ALR_87013019	You use this program to create a List concerning Budget/Actual/Commitments for Internal Orders.

Profitability Analysis:
Execute Report	KE30	You use this program to create several profitability reports. · Execute Drilldown Report Plan/Actual Sales Detail List · Execute Drilldown Report Plan/Actual Sales Mat. Costs · Execute Drilldown Report Plan/Actual Sales OH Costs · Execute Drilldown Report Reconciliation

Information System:
Costs/Revenues/Expenditures/Receipts	S_ALR_87013531	You use this program to create a Cost/Revenues/Expenditures/Receipts report for projects.
Actual/Costs/Revenues	CJI3	You use this program to display Project Actual Cost Line Items.

Product Costing
Multilevel BOM: Value / Amount / Status	CK86_99	You use this transaction to create a List concerning costed BOMs.
Cost Component	CK80_99	You use this transaction to create a List concerning Cost Components of the Cost Estimate.
Itemization	CK84_99	You use this transaction to create a List concerning Itemization of the Cost Estimate.
Cost Elements	KKBC_MAT	You use this transaction to create a List concerning Cost Elements of the Cost Estimate.
Analyzing/Comparing Material Cost Estimates	S_P99_41000111	You use this transaction to create a List to compare Material Cost Estimate.
Analyzing Product Cost Collector	KKBC_PKO	You use this transaction to create a List to analyze Product Orders.
Analyzing Product Order	KKBC_HOE	You use this transaction to create a List to analyze Product Orders.

Why do we need to DEBUG : BREAK POINT : WATCH POINT

2009-11-03T22:05:00.001-08:00

DEBUG

We write programs to achieve certain functionality and like other actions, we make mistakes while writing the code. If they are not trapped at the right time, problem becomes bigger, and bigger and bigger.

BREAK POINT

The BREAK POINT is a debugging aid. When we run a program normally, it is interrupted at the statement, and the system automatically starts the debugger, allowing you to display the contents of any fields in the program and check how the program continues. If the program is running in the background or in an update task, the system generates a system log message.

SAP - FI AR BK: Electronic Bank Reconciliation

2009-10-13T02:53:00.001-07:00

The EBS is used to automatically assign incoming and outgoing payments to house bank accounts when they relate to items already posted in the system to customer/vendor/clearing accounts and, where appropriate, the clearing of them.
Each uploaded electronic bank statement will be assigned with a unique no. in SAP and can be printed retrospectively.

Steps in Electronic Bank Reconciliation:

1. Electronic Bank Statement file (in SWIFT MT940 format) is extracted from BANK
2. Data (SWIFT MT940 for BANK) is imported into a temporary dataset in SAP
3. Batch input sessions are generated (per bank statement: one session for G/L Accounting and one for Subledgers- AR/ AP). Bank accounting and subledger accounting batch session can be executed separately or jointly
4. Posting rules and account determination are defined in TR-CM customization
5. As an electronic bank statement is being imported, the system identifies the transactions in it and determines how they are posted.
6. The note-to-payee fields in the electronic bank statement contain various information relevant to open item clearing. Note to payee fields can be interpreted by document number or reference document number for the clearing transaction (example: standard algorithm). If the algorithms we deliver are not sufficient, it is possible to program a user exit tailored to your business (e.g. change the posting rule; influence account determination by means of account modification).
7. Post-processing for posting proposals(line items) which cannot be cleared

Note:
Electronic Bank Statement format SWIFT MT940 is compactable with SAP TR-CM. Standard algorithm for clearing documents is available in the predefined form in SAP. Customisation, as stated in point 6 above, will be needed to cope with AAA specific requirements on Bank Reconciliation. The review task will be performed on the Detail Design Phase, detail of which will be incorporated into the respective customisation functional specifications.

Reasons for adopting Costing-Based COPA

2009-10-13T02:50:00.001-07:00

SAP CO-PA was intended for use with a cost-based approach that stores different currencies, quantities and values from SD, FI, MM and PP as PA value fields to manipulate for a variety of reports. This is the recommended path as it allows more variability in collecting data for PA reports (related to details of cost components for variances, etc.)

In case of High-Tech industry companies using SAP CO-PA, the majority of them utilitise Costing-Based COPA to enable more detail level of Cost of Sales analysis.

Costing-Based CO-PA sometimes does not match with legal book values. Such discrepancies can be explained mainly by 3 big factors:

Timing differences: When the Delivery step is performed in SAP SD, but Billing is not, nothing gets booked into COPA, but COGS is already booked in the FI legal book. During the SD Prototype, since Billing Due List (a batch program) will be executed each day, which perform the billing step for Sales Order with Delivery but not yet billed, the COGS and Revenue will be in syn in both FI and COPA for AAA.

Accruals: It is possible that accrued values are posted in COPA (might be triggered by program in Sales Order conditions), without any posting in FI legal book

Rounding differences from Foreign Currency Translations

Note:
Management using/ viewing these COPA reports need to be acknowledged the fact that due to the intended design of the Costing-Base COPA, values not necessarily always tie to FI legal book. Discrepancies to FI might occur, but explainable.s

SAP- CO : Some of the Product Cost Approaches

2009-10-13T02:47:00.001-07:00

§ Finished Goods Inventory in Production Plant AAAA

Valuation at moving average price per batch (FIFO batch valuation)
A new batch number will be generated for each production order (work order) producing the finished product
Each batch will have a unique material cost
The material cost of a batch is calculated from semi-finished goods and raw materials that are directly constituting to the finished product according to the BOM

§ Semi-finished Goods Inventory in Production Plant AAAA

Valuation at standard price updated from standard cost estimates
All inventory of each semi-finished product will be valuated the same (at the defined standard cost)
The standard cost can be updated either: 1) manually, or 2) automatically from the cost roll-up (can be using weighted average) of the lower levels of the BOM and can be selectively updated only for certain semi-finished products.
Re-valuation of existing inventories for semi-finished product will happen whenever the standard cost is updated. The gain or loss will post to the P/L accounts

§ Raw Materials Inventory in Production Plant AAAA

Raw materials will be valuated for each batch of the receipts of purchase using the purchase order price.
The batches of raw materials will be issued to production orders at FIFO.
No re-valuation of raw materials will be required.

§ All Inventory in Branches

Inventory will be valuated for each batch of the receipts of STO using the STO price (transfer prices plus the landed costs).
The batches of goods will be delivered to customers at FIFO.
No re-valuation of inventory will happen.

SAP - CO : Period End Closing Process

2009-10-13T02:44:00.001-07:00

Period end closing process is a monthly activity in CO and it refers to the following areas:

Execution of allocation cycles to apportion cost from common or shared cost centers to final cost centers
Generation of monthly reports

The following tasks have to be executed at every period end closing:

Ensure postings are completed from sub modules and sub modules have closed
Execute all the active allocation cycles
Check key figures to sub modules (i.e. total Cost Center Accounting figures to agree to total G/L expense accounts etc)
Generate monthly reports
Lock current posting period for controlling

SAP - CO : Statistical Key Figures

2009-10-13T02:43:00.001-07:00

Statistical key figures serve as a basis for internal allocations and as references in the key figure analysis framework. Statistical key figures can be used for internal cost allocations, and can be defined as either fixed values or totals values. There are two major types of allocation in SAP:

Distribution
Assessment

Distribution is the process of cost allocation used to allocate primary costs of cost center using the original primary cost elements. In this method, the costs being allocated will be retained into the original cost elements. On the other hand allocation by assessment could be applied to both primary and secondary costs using a secondary assessment cost element which is different from the original cost elements. In this case, the costs being allocated will be posted to a secondary assessment cost element.

Statistical key figures are defined for assessment purpose:

The statistical key figures used are:

Employees
Man-hours
Floor space
Quantity by Finish Goods

Points for ECC 6.0 FI Certification - NEW GL

2009-10-13T02:27:00.001-07:00

1. Possibilities with New GL:

· Legal and Management Reporting

· Extensibility (extended data structure by default - with customer fields)

· Account Balancing with Any characteristics

· Simple Mapping of Parallel Valuation (possible to manage multiple "books" (->ledgers)

· Reduction of TCO

· Transparency and Uniformity

· Segment Reporting (with online document split in real time)

· Real-Time Integration CO=>FI (time consuming recon activities omitted)

2. Above possibilities not available in Classic GL

3. Do I have to use the new GL

· Optional: for existing SAP customers – during upgrade Classic GL (GLT0) remains active at first

· For initial installations New GL Ledger is active by default in mySAP ERP

4. Activating the NGL Accounting:

· Automatic in initial installation

· It is at client level – applicable across all CC'

· TCODE: FAGL_ACTIVATION

· Result in system-wide changes to the easy access menu and screen and customizing paths

· Conventional Financial Accounting paths will initially remain available – can hide with program RFAGL_SWAP_IMG_OLD

5. Ledger Definition:

· SAP provides leading ledger "0L" and summary table – FAGLFLEXT with the standard system

· Leading ledger gets many of its control parameters from the CC – automatically comes to LL

· LL manages additional local currencies & FYV & PPV which are assigned to CC

· There is exactly only one leading ledger

· Only the values from LL are posted on to CO in standard system

· Addition to LL, you can define other non-leading ledger

· You can assign different alternate currencies &/ FYV, PPV to NLL

6. Summary / Total Table:

· Every reporting is from this table only

· It has extended database

· New GL Total Table (FAGLFLEXT) updates more char/data than the Classic GL Total Table (GLT0)

· New standard fields included:

i. CC

ii. PC

iii. Segment

· It can extended with additional fields – both predefine SAP fields and entirely new fields

· To add this – have to add to account assignment block

· Extending the block will lock out all other transactions

7. Scenarios – Definition and Assignment:

· Scenario defines which fields are updated in the ledgers (in GL view) during a posting (from other application component)

· Scenario provided by SAP:

i. Cost center update - FIN_CCA - sender & receiver CC

ii. Preparation for consolidation - FIN_CONS - consolidation transaction type & trading partner

iii. Business area - FIN_GSBER - sender & receiver BA

iv. Profit center update - FIN_PCA - PC & Partner PC

v. Segmentation - FIN_SEGM - segment, partner segment & PC fields

vi. COS accounting - FIN_UKV - sender & receiver FA

· Scenarios should be associated with the types of Ledgers (LL, NLL (N1), NLL (N2))

· Scenarios available in customizing - provided scenarios assigned to ledgers in customizing

· A ledger (LL) can be assigned one or more scenarios, or even all six at once

· Can not define your own scenarios

· Scenarios do not have to be assigned to non-leading ledgers

· You do not need one ledger for each scenario

· Multiple/non-leading ledgers are useful for modeling different accounting rules

· Values recorded in non-leading ledgers not record in CO module

· If you don't assign scenarios to a ledger (or to multiple ledgers) - segment B/S will not be possible

8. Entry View and GL View:

· When NGL active Financial accounting document always has two views

· You can also see the document in NLL in GL view

· Entry: view of how a document also appears in the sub ledger views / sub ledgers (AR/AP/AA/Taxes)

· General: view of how a document only appears in GL - only for GL and not for sub ledgers

9. S – A & F' I:

· In general, nothing has changed regarding the entry of the documents

· Dependencies have also remained:

i. Expense account is defined as primary cost element in CO and therefore requires a CO relevant account assignment during entry

ii. CO object is used to derive PC and FA

iii. Now new with ERP: A segment can now be derived from PC

10. S – A & F' II:

· If corresponding scenario not assigned – no entities are inherited to GL (neither LL / NLL)

· Effects of missing scenario will be like – if you call up B/S you can see the amount in exp account – but the same not allocated to scenarios – so segment B/S not possible

11. S – A & F' II:

· Scenario assignment is not capable of creating a "zero balance position" for any given entity – because all the terms not passed to all the line items so segment B/S not possible – this function can be possible using the document splitting with active inheritance

12. Use of segment entity:

· Segment field is one of the standard account assignment objects available in mySAP ERP to run analyses for "objects" below CC Level.

· Objective is to give a detail look at the various business activities- segment reporting - IAS14

· BA / PC can be used as alternatives – segment is in addition to BA & PC

13. Deriving a segment:

· Segment assigned in the PC Master record

· Segment posted automatically when PC posted

· There is no "dummy segment posting"

· If the PC does not have a segment, there is no segment account assignment either

· Default is derive segment from profit center – using BAdI , customer can develop their own derivation solutions

· BAdI : FAGL_DERIVE_SEGMENT

14. To post, analyze, and display document segments in NGL you have to perform below activities:

· Definition of the segment

· Derivation of the segment - from PC

· Maintain the FSV & FSG of corresponding FI doc - make 'segment' field to 'optional entry'

· Maintain the field status of the posting key - " "

· Display the segment field using layout in the document display

· Define the scenarios : scenarios has to be defined for LL - if not segment will only be visible in entry view

15. Document Splitting:

· Motivation: to create segment financial statements

· Assumption:

i. Operative process (of document entry) must not be disturbed (changed) by the online split

ii. When a vendor line item list is called, of course, there should still be only one open item for the invoice.

· Splitting doesn't happen in sub ledgers – happens only in GL account level

16. Steps involved in DS:

· Passive split

· Active (rule-based) split

· Clearing line/zero balance formation by document

17. Passive split:

· During clearing the account assignments of the items to clear are inherited to clearing line items

· Cannot be customized

18. Active split: (rule – based)

· System splits document due to splitting rules (provided or custom define)

· Can be configured

19. Clearing lines / zero balance formation by document:

· System creates new clearing line automatically to achieve a split

· Can control this process with the "zero balance flag"

20. Splitting procedure:

· Is the total of all splitting rules of all business transactions.

· Defines how and under which circumstances split will be performed

· Means, each procedure defines how each item category will be handled in the individual business transactions

i. Business transaction: is a general breakdown of actual business process that SAP provides and that is assigned a wide variety of item categories

ii. Business transaction variant: is a specific version of the predefined business transaction provided by SAP and (technical) modeling of a real business process for document splitting.

iii. Item category: is (technical) map of the posted line items – describes the items that appear within a document – derived from among other things, GL account categories – semantic description of document split.

iv. An individual splitting rule defines which item categories can be split and at the same time defines which foundation can be used

· Every GL has to be categorized into one of the item category

· GL account is associated with the item category

21. Splitting rule TCODE: GSP_RD

22. Splitting rules are not for CC – it is defined at client level

23. Document splitting characteristics:

· After defining how you want to split – now define which characteristics to use for splitting in GL accounting

· System proposes logical document splitting characteristics based on the assigned scenarios

· If you elect to use additional splitting chars, you should manage these chars in at least one Ledger

· Activate:

i. Zero balance flag – if you plan to use char to create FS. Balance of the involved entities is then always 0 for every posting, ensuring "entity balancing"

ii. Mandatory flag – has the two meanings:

1. It is an extension of the field status for accounts in which the char can not be entered during doc entry and for accounts that cannot be controlled through the field status.

2. It is a check as to whether a business process-equivalent business transaction variant was selected (which determines whether a splitting rule can be found)

24. Activating document splitting and inheritance:

· Splitting is first activated client-wide in customizing

· In a further step you can activate/deactivate splitting in each CC

· Inheritance: means when you create customer invoice from a revenue line – entities (such as BA / segment) are projected to the customer and tax lines in the GL View

· Default account assignment can be used to replace all account assignments that could not be derived from the posting with a constant "value"

25. Splitting procedure 0000000012 is the defaulted procedure provided by SAP

26. There is no reason why you shouldn't activate inheritance when splitting is active.

· If you didn't use inheritance, you'd have to define "rules" for the business processes to ensure that the account assignment are inherited – to achieve a zero balance in order to post the item

· Activation of inheritance is a first practical step to enable documents with active splitting, without any other customizing activities.

· Inheritance is performed online and at the line item level.

Need to stop depreciation posting on some assets

2009-10-06T04:53:00.001-07:00

Our client want to stop depreciation posting on some particualr assetsbecause these assets are not in use & need to be disposed in future.

What to do to stop depreciation posting on some assets ?

Set the shutdown indicator for these assets and assure that shutdown is considered by the assigned depreciation key.

I have tried this option already but the result is that it is reversing all the depreciation posted in previous month of current year.

My issue resolved. I used shut down option.

Calculation of Depreciation for Tax for India

2009-10-06T04:45:00.001-07:00

In India, there is a requirement that the Depreciation for Income Tax should be calculated based on the date of Acquisition. If an asset has been acquired before or on completion of 180 days of a Financial Year, than the calculation of Depreciation is allowed for full year. If the asset has been acquired after 180 days , depreciation is allowed only for 180 days. Hence for an asset acquired on 25/09/2009, system should allow calculation of depreciation from 01/04/2009, assuming that the fiscal year starts from 01/04/2009 and ends on 31/03/2009. However, if the asset is acquired on 07/10/2009, the system should allow depreciation from 01/10/2009. Sap has delivered standard depreciation keys for the same in reference chart of depreciation for India 0IN.

But if the asset has been acquired on 01/10/2009, still the asset has to be depreciated from 01/04/2009, since the asset has been acquired for less than 180 days into the fiscal year. The system is working fine for asset capitalized on 25/09/2009 and 07/10/2009. But we are not able to map the same if asset is capitalized on 01/10/2009 and 02/10/2009. For these two dates, the depreciation should start from 01/04/2009.

I have checked the period control setting and calender assignments and everything seems to be in place. How can we tackle the issue?

The same has been resolved.I Created a new assignment in Period Control IT for my fiscal year variant. For month 10, i added a new line item with no of days as 2 in addition to no of days as 31 for month 10.

Accounting Entries for MM, FI related

2009-09-08T04:17:00.001-07:00

What should be my accounting entry in procurement?

For Domestic Procurement of Raw Material

During GR

Material Stock Dr.

GR/IR clearing Cr.

During Excise Invoice Credit

Cenvat Account Dr.

Cenvat Clearing Cr.

During Invoice Verification

Cenvat Clearing Dr.

GR/IR Clearing Dr.

Vendor Payable Cr.

For Domestic procurement of Capital Goods

During GR

Material Stock Dr.

GR/IR clearing Cr.

During Excise Invoice Credit

Cenvat Account Dr. (50%)

Cenvat On-hold Dr. (50%)

Cenvat Clearing Cr.

During Invoice Verification

Cenvat Clearing Dr.

GR/IR Clearing Dr.

Vendor Payable Cr

Subsequent of Capital Goods

Cenvat Account Dr. (50%)

Cenvat On-hold Cr. (50%)

For Import Procurement of Raw Material

During Customs Duty Clearing invoice

Custom Clearing Dr.

Custom Payable Cr.

During GR

Material Stock Dr.

GR/IR clearing Cr.

During Excise Invoice Credit

Cenvat Account Dr.

Custom Clearing Cr.

During Invoice Verification

GR/IR Clearing Dr.

Vendor Payable Cr.

For Excise Duty Credit of Raw Material without PO

Cenvat Account Dr.

Cenvat Clearing Cr.

For Excise Duty Reversal through Excise JV

Cenvat Clearing Dr.

Cenvat Account Cr.

What should be my accounting entry when the goods are issued through MM and excise invoice is created (J1IS & J1IV)?

During Excise Invoice Creation

Cenvat Suspense Account Dr.

Cenvat payable Cr.

For TR6C Challan

PLA Account Dr.

PLA on hold Account Cr.

During Fortnightly Utilization

Cenvat payable Dr.

Cenvat Account Cr.

PLA Account Cr.

Note: Cenvat Suspense Account should be cleared appropriately using FI JV's.

What should be my accounting entry in subcontracting reversal / Recredit?

For Subcontracting Challan Reversal

Cenvat Reversal Dr.

Cenvat Account Cr.

For Subcontracting Challan Recredit

Cenvat Account Dr.

Cenvat Reversal Cr.

What should be my accounting entry in SD ?

For Factory Sale

During Billing Document

Customer Account Dr.

Sales Account Cr.

Cenvat Suspense Account Cr.

During Excise Invoice Creation

Cenvat Suspense Account Dr.

Cenvat payable Cr.

For TR6C Challan

PLA Account Dr.

PLA on hold Account Cr.

During Fortnightly Utilization

Cenvat payable Dr.

Cenvat Account Cr.

PLA Account Cr.

For Stock Transfer through SD

No Accounting entries for Performa Billing Document

During Excise Invoice Creation

Cenvat Suspense Account Dr.

Cenvat payable Cr.

For TR6C Challan

PLA Account Dr.

PLA on hold Account Cr.

During Fortnightly Utilization

Cenvat payable Dr.

Cenvat Account Cr.

PLA Account Cr.

Note: Cenvat Suspense Account should be cleared appropriately using FI JV's.

Product Costing scenario in NUT SHELL :

2009-09-01T03:45:00.001-07:00

Let us assume that the company is manufacturing finished product ZZZ for which we need raw materials XXX and semi finished materials YYY.
The Production Order consist of BOM consisting of the above three components and the routing which has the operations to be performed.
The production is carried out through a Machine what we say as a Work Center.
The production order has to be carried out in the work center.
The operations are going to be processed through various activities like power, water, labour etc.
The prices of these activities are being defined for a cost center through KP26.
The planned and actual quantities of the raw materials and other activities are done in the production orders.
The work centers carries the activities and the actual activity performed will be confirmed during production process.
We have a costing sheet to calculate the raw material, packing material consumed along with other overheads.
This costing sheet is assigned in the Valuation Variant of a Plant.
The Valuation Variant also carries the cost component structure defined in OKTZ.
The planned and actual valuation variant for the plant is assigned to the costing variant.
During creation of Production order CO01, we assign these costing variants.
We also assign the settlement rule to the order type.
Whenever the Production Order is created, the costing variant planned captures the values through the cost component structure the materials consumed and the planned activity prices and the costing analysis of the production order shows the planned values of all the costs.
After settlement of Production Order, it shows the actual values.
If you run cost estimate through CK11N or CK40N for the finished product ZZZ, it will capture all the cost through cost component structure and gives you the cost of the material as per the lot size defined by you.
The example referred holds for manufacturing orders and the actual costs are captured based on the settlement of production orders at any point of time.
Whereas in product costing by period, the costs are captured in Product cost collectors and settled based on period settings in settlement rule.
On activation of the material ledger, the material price analysis can be done for the actual cost postings.

Key points while PCA configuration:

2009-08-26T00:45:00.001-07:00

Profit Center Accounting (EC‑PCA) is being used to determine profits and losses by profit center using period accounting approach.

Set Controlling area – OKKS
Maintain Controlling area settings - 0KE5

o In this IMG activity you define the general control parameters for the controlling area.

o The first step you need to take is to enter the name of the standard hierarchy of profit center master data. The system creates the standard hierarchy automatically when you save.

o The dummy profit center receives all the postings in your system to objects, which are not assigned to a profit center. This ensures that your data will be complete in Profit Center Accounting. This field is displayed here for informational purposes only. You create the dummy profit center under Master data -> Dummy center.

o The checkbox Elimination of internal business volume for Profit Center Accounting is ticked for the controlling area OP01

o Currencies:

o Profit Center Local Currency Type = Controlling area currency

o Profit Center Local Currency = USD (as this is the group reporting currency)

o Store Transaction currency: Yes

o Valuation view = Legal valuation

o ALE Distribution method: No distribution to other systems

o Currency Type changed to 30. This is as per OSS Note 119428.This note recommends keeping the PCA currency type to 30 if the currency type for the controlling area is 30 since the currency type in Controlling area settings is 30 the PCA Currency type is changed to 30.

Activate Average Balance Ledger – 0KE6: The average balance ledger is not being used hence the 8Z ledgers have been kept as deactivated.
PCA –Allow balance C/F: In PCA the balances have been configured to allow carry forward. The Pre requisite are that retained earnings accounts have been maintained.
Set Control Parameters for Actual Data -1KEF: As soon as Financial Accounting entries are been made the PCA – 8A Ledgers will be updated simultaneously.
Maintain Document Types: GCBX -> Document type maintained is A0. The three check boxes are for:

The transaction currency,
Local/company code currency and
Third currency determines which currencies are stored for this document type has been used.

SL: Maintain additional document type. This needs to be used when correction documents, (to rectify data posted from Finance and other modules) are posted during the test phases for the period end scenario. This process will be used only during the test phases and hence this document type will not be transported to Production.

7. Maintain Number ranges for local documents - GB02: The number assignment is dependent on the company code

8. Maintain Automatic account assignment – OKB9

9. Choose Accounts: 3KEH: In this activity, you define which accounts or account intervals you want to transfer to Profit Centre Accounting. If no profit center is specified in a posting, the system uses the default profit center for the account or account interval.

BS readjustment: The balance readjustment program read all AR, AP and TAX postings (posted without or with profit center DUMMY). It allocates the correct profit center to AR/AP and TAX and creates postings in FI and In the period end-closing schedule we also run the PCA AR/AP update where all open items (AR/AP) are updated in total in PCA per profit center. The offset postings are updated real time. This means we have double counting in PCA in the AR/AP area. To solve this the readjustment accounts are removed from 3KEH.

10. Derivation Rules for Finding the Profit Center: 3KEI: 3KEH configuration is used for determining default profit centres for all Balance Sheet accounts, other than reconciliation accounts, where the COB cannot be determined. These accounts are therefore, assigned to Corporate or Financing. Certain Balance Sheet accounts are defaulted to DUMMY because the COB cannot be determined at time of posting, and should not be reported against any particular COB from a 'day to day' perspective. They are, however, dealt with during the period end and eventually are allocated to the COB's guidelines.

11. Adding fields to PCA distribution /assessments: Transaction GCA6: View/Table: V_T811I

12. Assignment of Profit Centres to Co codes: In this activity the profit centres are assigned to company codes. This can be done while changing the Profit center or can be done collectively. Transaction KE52, KE56

13. Perform Account Control for Valuation Differences: When payables and receivables are transferred to Profit Center Accounting, the system adjusts valuation differences arising from foreign currency revaluation. In this activity, you decide which account these adjustments through foreign currency revaluation are to be posted to. There are two possibilities here:

§ Posting to the General Ledger account for payables/receivables

§ Posting to the balance sheet adjustment account of the general ledger account for payables/receivables

Currency Type for Controlling Area:

2009-08-25T02:54:00.001-07:00

The controlling area currency type determines which currency is allowed as controlling area currency and whether the CO area currency can differ from the currency of the assigned company codes. CO area currency is either set by the user or derived from other organizational units.

The assignment control indicator, together with the currency type, determines the controlling area currency and whether to activate or deactivate the other company code currency indicator.
You can select currency type 10 only if all company codes assigned to the controlling area use the same currency.
If you select 1 as the assignment control, the R/3 System uses the default setting 10 as the currency type.
If you select currency type 40 or 50, the company codes must either be in the same country, or the countries must use the same index-based currency or hard currency.
If you select currency type 60, the company codes must belong to the same company, or the companies must use the same currency.
If you select currency type 20, specify the currency. With currency types 40, 50, and 60, specify the currency only as long as no company codes have been assigned. If company codes have been assigned, the R/3 System defaults the currency automatically

Difference between Unplanned depreciation and Manual depreciation

2009-08-24T04:13:00.001-07:00

First of all an asset will have depreciation keys.

These depreciation keys have the control for calculating the automatic depreciation.

If you maintain a normal depreciation key, this will automatically forecast the depreciation for the open FYs.

Apart from the above planned ordinary depreciation, you can post unplanned depreciation also, if any unforeseen conditions happen.

Example:

On 31.08.2009 your asset's NBV is 5000$ (after august depreciation run also), but if you feel that (client) this asset's value is further down according to the current market value, you can pass a unplanned depreciation (ABAA) for an amount of 100$. So with this transaction your asset's NBV as on 31.08.2009 will become 4900$.

By passing ABAA, system will not post any accounting doc, since it creates an AA internal document. So you need to do a repeat depreciation run for the august period, then the system will check the asset for any unposted planned/unplanned depreciations to it. So at this point system will pass that amount to accounting.

But where as manual depreciation is concerned...

You cannot post any unplanned depreciation to an asset, which is having depreciation key that does not forecast planned depreciation values for the open FY.

Depreciation key MANU is the standard depreciation key, which will not forecast any planned depreciation to it.

Accounting Entries related to MM transactions...

2009-08-21T20:24:00.000-07:00

Initial stock entry:

Movement type - 561(Receipt per initial entry of stock balances into unrestricted-use)

TCODE - MB1C

FI Document Type - WA

89	Raw material	BSX		S
91	Initial Stock entry	GBB	BSA	H

Physical inventory differences:

Movement type – 702 (Goods Issue – Physical Inventory difference) this is triggered because of the movement type 102, which is given while calculating the difference – INV: for expenditure/income from inventory differences

TCODE - MI07 (MI01 & MI04)

FI Document Type - WI

81	Inventory differences – G/L	GBB	INV	S
99	Raw material	BSX		H

Goods Issue to Production Order:

Movement type - 261 (Consumption for order from warehouse) – VBR: for internal goods issues (for example, for cost center)

TCODE - MB1A

FI Document Type - WA: Goods Issue

81	Raw material Consumption	GBB	VBR	S
99	Raw material	BSX		H

In case Movement type given is 201(Consumption for cost center from warehouse), at the time of MB1A system asks for the COST CENTER & GENERAL LEDGER. Here, the account determination happens directly from MB1A and not from the OBYC. Accounting entry will be same as above except the 'Raw material Consumption'; it triggers whatever the GL given.

Goods Issue / Delivery: SD

Movement type - 601 (Customer delivery) – VAX: for goods issues for sales orders without account assignment object (the account is not a cost element)

TCODE - VL02

FI Document Type - WL: Goods Issue/Delivery

81	Mater. consumed/trading goods without cost element COGS	GBB	VAX	S
99	Finished Goods	BSX		H

Goods Receipt: FG PP

Movement type - 101 (Goods Receipt) – GBB-AUF: for goods receipts for orders (without account assignment) and for order settlement if AUA is not maintained

TCODE - MB31 Goods Receipt for Production Order

FI Document Type - WE: Goods Receipt

89	Finished Goods	BSX		S
91	Inventory change – factory output COGP	GBB	AUF	H

Goods Receipt: RM MM

Movement type - 101 (Goods Receipt)

TCODE - MIGO Goods Receipt for Purchase Order

FI Document Type - WE: Goods Receipt

89	Raw Material	BSX		S
96	GR / IR Clearing account	WRX		H

Invoice Receipt: RM MM

Movement type - 101 (Goods Receipt)

TCODE - MIGO Goods Receipt for Purchase Order

FI Document Type - WE: Goods Receipt

86	GR / IR Clearing account	WRX		S
31	Vendor account	KBS		H

KBS – is without any account determination and posting keys are 81 & 91. It triggers when there is no material is assigned in the PO at that time.

WRX – In case of any posting required without material, account determination should be without valuation class.

If price changed at the time of IR, then based on the difference in the material price system posts amounts to particular material account and not to the price difference account (this is related to the materials with price control – V).

Material Valuation: MM

Movement type -

TCODE - MR22 Dr/Cr Material – material valuation (below given calculation) & MR21: Price Change (Difference amount posts to the material account and calculation is ((New price – Old price) * Quantity)

FI Document Type - PR: Price change – Below entry in case of price increase

89	Raw material	BSX		S
93	Material Valuation	UMB		H

Calculation - {Current Stock Value + (Amount given in MR22 / Quantity given in MR22 * Cr. Quantity)}

Billing Document: SD

TCODE - VF01 Billing - VF11 Cancel Billing

FI Document Type - RV: Billing document transfer - RW: Reversal of billing

01	Customer account	BSX		S
50	Sales Revenue account	UMB		H

TCODE: KANK Maintain Number Ranges for Controlling Documents

2009-08-21T01:27:00.001-07:00

In this IMG activity you create number ranges for business transactions in Controlling or change existing settings.

For every posting in CO the SAP System generates a numbered document.
The document numbers are unique to each controlling area, since each number is assigned only once.
In CO, there are no legal requirements for a continuous assignment of document numbers.
To improve performance, after each restart of an application server, a maximum of 100 document numbers for each number range are not assigned.
Every transaction that you carry out on the controlling area level has to be assigned to a number range group.
A number range group, in turn, includes two document number intervals:

An internal interval for all documents to which the user did not explicitly assign a document number;
An external interval for all documents where the user assigned the document numbers, or which are brought into the SAP system from a non-SAP system (for example, through batch input) and the original document numbers are to be retained. If no external document number is given during posting, the SAP system uses the next open number from the internal number interval of the transaction it belongs to.

Requirements you have system authorization for maintaining number ranges. (Authorization object S_NUMBER).
Note you define the document number range in CO independently from the fiscal year.

Recommendation

SAP recommends that you create separate document number ranges for plan and actual cost transactions so that, when reorganization programs run separately for plan and actual data, the number ranges can also be reset separately.
For transactions seldom used, such as reposting at period-end closing, you should not create individual number range groups. Otherwise, note that no more than 100 document numbers are assigned for system performance reasons on each day that such a transaction is started.
If you work with several controlling areas, which are to use the same number range intervals, it is easiest to carry out the definition for one controlling area only. Choose Copy to transfer your settings to other controlling areas.

Activities

Check whether the standard settings for controlling area satisfy your requirements. If you are not going to work with controlling area, you can transfer the number ranges to your controlling area by choosing Copy.
If necessary, create new number range groups.
Maintain the respective number intervals for the number range groups you created. Ensure that the number intervals do not overlap with those of other groups.

Assign the business transactions that you wish to use to the respective number range groups. For settlement documents you have different TCODE for number ranges.

Step By Step Configuration : Material Ledger

2009-08-20T04:26:00.001-07:00

The below links are for compleate configs of materail :

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSMAT/PSMAT.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAARCMM/CAARCMM.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_MM.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOMDMM/LOMDMM.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PPMRP/PPMRP.pdf

Step-by-Step Procedure for Customizing an Electronic Bank Reconciliation Statement

2009-08-20T04:24:00.001-07:00

Create House Bank and Account ID (FI12)
Setup EDI Partner Profile for FINSTA Message Type (WE20)
Configure Global Settings for EBS (IMG)
- Create Account Symbols
- Assign Accounts to Account Symbols
- Create Keys for Posting Rules
- Define Posting Rules
- Create Transaction Types
- Assign External Transaction Types to Posting Rules
- Assign Bank Accounts to Transaction Types
Define Search String for EBS(Optional)
- Search String Definition
- Search String Use
Define Program and Variant Selection

Additional information is also available in the SAP Library under:

Financial Accounting > Bank Accounting (FI-BL) > Electronic Bank Statement >
Electronic Account Statement Customizing

FI Document Types:

2009-08-18T03:07:00.001-07:00

FI-MM related Document Types:

'PR' – Price Change

Postings on Inventory Revaluation from MM (transaction MR21). 'Price Change' refers to the change in Standard Price of the material, not the price difference between PO and Invoice that is booked at the time of invoicing. Note this type of transaction does not have Reversal FI Document Type. If the price changed need to be adjusted, a new transaction is posted, rather than reverse the original posting.

'RE' – Invoice Receipt

Postings on Invoice Receipt transactions from MM (transactions MIRO/ MRRL)

'RI' – Invoice Receipt-Interco.

Postings on Invoice Receipt transactions for Invoice Verification triggered from Intercompany Sales. The Invoice Verification step for intercompany sales are triggered by SAP in form of a batch generated automatically.

'WA' – Goods Issue

Postings on Goods Issues or MM Transfer Postings.

'WE' – Goods Receipts

Postings on Goods Receipts with reference to Purchase Order or Production Orders.

'WI' – Inventory Document

Postings on Physical Inventory Differences.

'WL' – Goods Issue/ Delivery

Postings on Goods Issues with reference to SD Delivery.

FI-SD related Document Types:

'RV' – SD Invoice

Postings of Sales Invoice from SD transactions. A Sales Order and delivery need to be completed before Sales Invoice is created in SD.

'RW' – SD Invoice-Interco.

Postings of Intercompany Invoice from SD transactions. A Stock Transport Order (STO) and delivery need to be completed before Sales Invoice is created in SD.

'RC' – SD Credit Memo

Postings of Credit Memo from SD transactions. A Credit Memo Request (a special Sales Order Type) need to be raised before Credit Memo is created in SD.

'RD' – SD Debit Memo

Postings of Debit Memo from SD transactions. A Debit Memo Request (a special Sales Order Type) need to be raised before Debit Memo is created in SD.

'RR' – SD Credit for Return

Postings of Credit Memo from SD transactions as arose from Return. A Return Order (a special Sales Order Type) and return delivery need to be completed before Credit Memo for Return is created in SD.

'RS' – SD Rebate Credit Memo

Postings of Rebate Credit Memo from SD transactions. A Credit Memo Request (a special Sales Order Type) need to be raised before Rebate Credit Memo is created in SD.

Difference between Cash Sales & Rush Order

2009-08-13T04:46:00.003-07:00

Cash sales are order related billing whereas Rush Order is delivery related.

Cash sales are not relevant for availability check, as you will be picking the goods whereas Rush Order is relevant for availability check.

Cash sales are also not relevant for credit management whereas Rush Order is relevant credit management.

Cash sales uses RD03 as output, which immediately prints the invoice whereas Rush Order uses standard output RD00.

Cash sales have one time customer account group where as RO normally doesn't.

For Cash sales order type is BV or CS and for Rush Order it is RO

Cash sales triggers petty Cash a/c where as in Rush Order customers account is debited.

Delivery and settlement will be done immediately in Cash sales where as in Rush Order only delivery will be done immediately.

Difference between VF04 & VF06

2009-08-13T04:46:00.001-07:00

VF04 is used to MAINTAIN BILLING DUE LIST based on the Delivery date as default, Means the Delivery documents which has the same date and for which the Billing has to create on a particular date uses this Transaction

VF06 is used to create the Billing for all the Deliveries irrespective of Date,

You have to give the Billing data for VF04 and it is not required for VF06 (in summary).

In VF06, you can also schedule the invoice printing with required date and time. Once the system date and time reaches this, it will run in background.

Difference between PICKLIST & PUTAWAY LIST

2009-08-13T04:45:00.000-07:00

The PICKLIST is used at the time of doing PGI -outbound delivery, it helps us to identify what materials what quantity are to be picked from which storage location for purposes of executing delivery and subsequent Goods issue.

Whereas PUTAWAY list is being at the time of PGR- inbound delivery, goods return. This PUTAWAY list will let us know that what material, what quantity is returned with reference to which particular SO and delivery. The goods returned are isolated and put in separate storage location from your normal one and PUTAWAY helps there.

In short PICKLIST is for removing goods from your storage location while PUTAWAY is for placing goods back.

How to reduce finished goods stock without sales ?

2009-07-22T00:43:00.001-07:00

Iam having a problem regarding the following business scenario.

We are doing make to contract scenario

We created the sales order in reference to sales contract

After the production process we find there are some goods which is more than the sales order quantity, but we cant do any over delivery shipment through SAP.

We have tried with the option in over delivery tolerance and it any how shown that overdelivery tolerance is not applicable in make to contract scenario. So now we are in helpless situation to deliver the goods through SAP and it is stoppe.

Now my finished goods inventory is increasing as the stock is not reducing through sales.

My question is can you suggest any work around solution so that my inventory can be reduced without affecting others I mean not through 562 movt.

If you know the answer, please reply back at sap.vvr@gmail.com