SAP Free Download Center

SAP Free Download Center is available for online resources on SAP Tutorials, SAP Certification and SAP News.


Tips of Certification

I passed my SAP FI certification ECC 6.0 on 21st March 2009. I want to thank each one of them in the group for there support..

People who are going to attend the certification exam kindly concentrate on the TFIN50 and TFIN52

Tips for people who are going to attend the exam:


  • Understand the concepts. Don't memorize.
  • If posible kindly practice the configuration part (Not mandatory)
  • Do the preparation based on the syllabus not based on books. {You will be getting 99% from the syllabus}
  • You have to cover all the chapters.
  • No straight Questions.
  • You will be getting chapter wise questions like AA, Masters, APP, NEW GL and so on.......... ....




“But one thing I can say if you are thorough with syllabus 'U' can easily pass”


Take the certification date only once you finish one round of study of all books

Two types of Questions

Single answer questions {SAQ will be around 10 - 15 questions and remaining will be True/False}

A statement will be given, Based on that 4 to 6 options, You have to select each option is True or False

Subject - No of questions Approx number of questions asked

  1. Asset Accounting - 13 questions 2 questions on depreciation area, 3 questions on asset class, 4 questions on asset transactions and depreciation
  2. Closing Operations in Financial Accounting - 5 1 question on M/E closing, 3 on Balance confirmations
  3. Document and Posting Control - 14 Main questions on cash discount, 1Q on Cross Co.Code, 1Q Doc Reversal, 2Q on Foreign currency, 1Q on authorisation, 1Q on FSG, 1Q on posting period, 1Q on tolerance group, NO questions on TAX.
  4. Evaluation Options in Reporting - 7 2 Q on list viewer and 3 questions on drill down report
  5. Financial Accounting Master Data - 15 3Q on Bank, 4Q on Customer, 3Q on Vendor, 2Q on GL
  6. Payment Program, Dunning Program, Correspondence, Interest Calculation - 6 3 questions on payment program
  7. SAP Overview - 5 2 Questions related to MM, 1 on navigation
  8. SAP Solution Manager - 4 2Q on Roadmap
  9. Special General Ledger Transactions, Document Parking, Validation & Substitution - 6 1Q on Park & Post, 2Q on Splgl, 2Q on Substitution & Validation
  10. The New General Ledger -5 1 on Basics


I think this information will be helpful for all of YOU.

Posted by: Venkat.N(Bangalore)

Useful SAP Site >> mySAP FI Tutorial
Read more

Difference between Parked and Holded document

The ‘Parking of a Document’ in SAP is one of the two preliminary postings (the other being the ‘Holding’ of documents) in the system and refers to the storing of incomplete documents in the system.


These documents can later be called on for completion and posting. While ‘parking’ a document, the system does not carry out the mandatory ‘validity checking.’ The system does not also carry out any automatic postings (such as creating tax line items) or ‘balance checks.’ As a result, the transaction figures (account balances) are not updated. This is true in the case of all financial transactions except in the area of TR-CM (Cash management) where ‘parked’ documents will update the transactions.

The parking of documents can be used to ‘park’ data relating to customers, vendors, or assets (acquisition only). When a cross-Company Code document is ‘parked,’ only one document is created in the initial Company Code; when this ‘parked’ document is posted all other documents relevant for all other Company Codes will also be created. However, it is to be noted that substitution functionality cannot be used with document ‘parking,’ as substitution is activated only on transaction processing.

The added advantage is that a document ‘parked’ by an accounting clerk can be called on for completion by someone else. The ‘parked’ documents can be displayed individually or as a list from where the required document can be selected for completion and posting. The number of the ‘parked’ document is transferred to the posted document. The original ‘parked’ document, if necessary, can be displayed even after it has been posted to.

During a transaction when you do not have a piece of required information, you can ‘Hold the Document’ and complete it later. As in the case of ‘parked’ documents, here also the document does not update the transaction figures.
Read more

Automatic Creation of Primary and Secondary Cost Elements

Part of SAP Controlling module is Cost Element Accounting. It is under this area where you maintain directly master data of cost elements. Just to refresh your mind about cost element.


There are two types of cost elements in Controlling, namely; primary and secondary cost element. Primary cost elements are used to transfer P&L account postings in Financial (FI) to Controlling (CO). It is a requirement that all P&L accounts should have a primary cost elements; otherwise, transactions can not be posted involving P&L accounts in FI. On the other hand, secondary cost elements are use only for allocation and assessment purposes as period-end process.

Some might have created already a cost element. The question now is, how did you create the cost element? You could have created manually for each P&L Account. My dear readers, it’s really a tedious activity to create cost element manually.

Now here is the tip. You can create primary cost elements automatically for all P&L accounts. You just follow this procedure:

1. First, set-up the settings in your Chart of Accounts. Follow this configuration path:

IMG → Financial Accounting (New) →General Ledger Accounting (New) → Master Data → G/L Accounts → Preparations → Edit Chart of Accounts List.

Transaction Code: OB13

The “Change View List of All Chart of Accounts: Details ” screen appears.


Set the Controlling Integration to “2 Automatic creation of cost elements” (see highlighted item), and save your work.

2. Second step, Specify the default cost elements that will be automatically created. Follow this configuration path:

IMG → Controlling → Cost Element Accounting → Master Data → Cost Elements → Automatic Creation of Primary and Secondary Cost Elements → Make Default Settings.

Transaction Code: OKB2

3. Third step, Create Batch Input Session for the automatic creation of cost elements. Follow this configuration path:

IMG → Controlling → Cost Element Accounting → Master Data → Cost Elements → Automatic Creation of Primary and Secondary Cost Elements → Create Batch Input Session.

Transaction Code: OKB3

4. Fourth step, Execute Batch Input Session.

Transaction Code: SM35

Result: The cost elements specified in step 2 will be automatically created.

Writer: sap-knowledge.com
Read more

SAP Documents

SAP is based on the document principle meaning that a document is created out of every business transaction in the system. The Document is the result of a posting in accounting in SAP, and is the connecting link between various business operations. There are two types of documents:

Original Documents: these documents relate to the origin of business transactions such as invoices, receipts, statement of accounts from bank, etc.


Processing Documents: These include accounting documents generated from postings in the system, reference documents, sample documents, etc. The processing documents other than the accounting ones are also known as special documents and they aid in the simplification of document entry in the system.

Every document consists of:

  • A Document Header
  • Two or more Line Items
Before attempting to enter a document, call up the relevant document entry function as the system provides a variety of ready-made document entry templates suited to different transactions such as regular GL entry, customer invoice posting, etc. The details entered in a document can be simulated and displayed before the document is actually posted in the system. You may also choose to park the document and post it later.

Credit: SAPDocs.info
Read more

One-Time Vendor and Customer Table

I’ve searched the internet where I could possibly find One-time Vendor and One-time Customer data in SAP. You know what? I could not find any site telling the best table to find what I am looking.
Most of the sites I visited are mentioning about SAP table name: BSEC, One-Time Account Data Document Segment table.


Well, I’ve checked the table and yes it’s a table for One-time vendor/customer transaction data. However, what if the transactions have originated from PO (MM Module)?

Using BSEC table to get one-time vendor/customer data pose a problem for transactions that originate from PO (MM Module). Because the field that you use to access BSEC is belnr (accounting document number) and gjahr (Fiscal Year). And the belnr that you need is the document number created in accounting not the document number created from PO. To look for the created belnr of a specific PO you need to access table BSEG, and hell it’s cluster table. And worst is, belnr is unknown so it will definitely mess up your program performance because belnr is a key field.

I’d like to share what I’ve just learned as I continue to advance my learning in SAP ERP.

If transactions have originated from FI and SD module, you may use table BSEC. Key fields are satisfied because definitely you know your BELNR and GJAHR you want to access.

Elseif, transactions have originated from PO (MM Module) you can use table RBKP, Document Header: Invoice Receipt table. You can find all the information about the one-time vendor/customer you want to get such; name, address, TIN and etc.

Credit: sap-knowledge.com
Read more

What is the difference between SA38 and SE38?

SAP Transaction Code SA38 and SE38 are both use to execute a SAP program directly.

The difference is, SA38 can be used only to execute or run a SAP program. Whereas, SE38 is use to display an ABAP Editor screen where transaction is not limited only to program execution but also to display or modify the SAP program code.


Furthermore, SA38 is more recommended to use by Functional Consultants/Users of the program e.g. FI/CO.

This will reduce the risk of mistakenly modification or deletion of the program. Especially if no transaction code created for a program. SA38 can be used also by ABAPers to execute the program.
Read more

Define Posting Keys in SAP

Purpose

In this SAP activity, you define posting keys. During posting of entry, a user is required by the system to specify posting key. It controls how a line item is entered and processed in the system.
For each posting key, you define among other things:


  • which side of an account can be posted to
  • which type of account can be posted to
  • Which fields the system displays on the entry screens and whether an entry has to be made (field status).

Procedure
  1. Access the activity using one of the following navigation option:
    SAP IMG Path: Financial Accounting (NEW) → Financial Accounting Global Settings (New) → Document → Define Posting Key.
  2. Double-click the posting key.
  3. On the next screen choose Maintain Field Status.
  4. On the next screen double-click group Additional account assignments.
  5. On the next screen set the field status for the three above mentioned fields to Opt. Entry.
  6. Then choose Back.
  7. Finally choose Save

Read more

Define Field Status Variant in SAP

Purpose

In this SAP activity, you define and/or edit field status variants and groups. You group several field status groups together in one field status variant.


You assign the field status variants to a company code in the activity Assign Company Code to Field Status Variant. This allows you to work with the same field status groups in any number of company codes.

You can also define and process field status groups. As a requirement, you define a field status group in the company code-specific area of each G/L account. The field status group determines which fields are ready for input, which are required entry fields, and which are hidden during document entry. Just remember that additional account assignments (i.e. cost centers, profit centers or orders) are only possible if data can be entered in the corresponding fields.
Procedure

SAP IMG Path : Financial Accounting (NEW) → Financial Accounting Global Settings (NEW) → Ledger → Fields → Define Field Status Variant.
  • On the Change View “Field status variants”: Overview screen in the left hand frame make a double-click Field status variants.
  • In the right hand frame, choose the line with the field status variant Z001 (Field status for Z001) from the toolbar choose Copy as (F6).
  • On the Change View “Field status variants”: Overview of chosen set screen enter the following data:
    FSTV : Z001
    Field Status Name : Field Status Z001
  • Then choose Enter.
  • On the Specify object to be copied dialog box choose copy all.
  • Then confirm the Information dialog box
    h) Finally, choose Save.

Read more

Effects of Prior Year Postings

One SAP Consultant asked us through email and we quote ”what is the effect of document postings in prior year(s) where carry-forward process have been carried out in those prior year(s)”.


Because of our extensive experiences in SAP implementation and support, we were able to satisfy the SAP Consultant. We would like to share the answer on the query. You may share it also to others through referring this post.

Normally, companies close their books every year end and open a new fiscal year. Part of the closing procedures is to carry-forward balances of G/L accounts.

Case

New fiscal year (current year) is 2009, and the accounting department noted that there are unposted documents which pertain in 2008. The 2008 G/L account balances have been carried forward already in the SAP system.

Explanation

Do remember that during carry-forward process, the balance sheet accounts are simply carried forward in the new fiscal year e.g. 2009. On the other side, the profit and loss accounts are carried forward to one or many retained earnings account(s depend on the number of retained earning accounts defined for the company code.

In the above case, any postings in the old fiscal year adjust the relevant carried forward balances automatically. The system adjust the accounts through background processing. There is no need to redo the carry-forward process.
Read more

Configure Default Baseline Date for Payment

This article is a quick reference on how to set the default value of baseline date for payment in SAP.


A baseline date for payment is the date for which the payment terms apply. It’s the basis of the sytem to determine the cash discount taken (from vendor) or cash discount given (to customer). During entry of customer and vendor invoice transactions, the baseline date field is a required field. You can not proceed with the posting of the transaction not unless the said field is filled-up.

In SAP system, you can customize the default baseline date for payment that appears during transaction entry. You may choose as default either the posting date, document date, entry date or no default date. Do remember you can override the default value of baseline date.

To configure the default value of baseline date for payment, here’s a quick and simple guide:

Transaction Code: OBB8

SAP Path: IMG → Financial Accounting → Accounts Receivable and Accounts Payable → Business Transactions → Outgoing Invoices/Credit Memos → Maintain Terms of Payment.

Select the the default value either posting date, value date, document date or no default. Bear in mind that the default baseline date is applicable for each payment term you maintain. You could have different default baseline date for different payment terms.

Credit: SAP-Knowledge.com
Read more

Disable/Enable User Menu and SAP Menu

1. Configure individual specific SAP users

Enter transaction code SM30 (Maintain Table Views) in your SAP command field and maintain USERS_SSM table.


You would notice that no data maintained in this table during initial access.

  • To maintain entries, click ‘New Entries’ button. Enter the individual
    username on the User Name field.
  • To enable user menu and SAP menu, tick the appropriate checkboxes. To
    disable, untick the chekcboxes.

2. Configure all SAP user
Enter transaction code SM30 (Maintain Table Views) in your SAP command field and maintain SSM_CUST table.

    • To enable te user menu for all SAP users set ALL_USER_MENUS_OFF = No.
    • To disable it, set ALL_USER_MENUS_OFF = Yes.
    • To enable the SAP Menu set SAP_MENU_OFF = No
    • To disable it set SAP_MENU_OFF = Yes.

Read more

Batch Data Communication/Batch Input/Inbound-Outbound

When a company decides to implement the SAP R/3 to manage business critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.


In the process of replacing current applications and transferring application data, two situations might occur:

  • The first is when application data to be replaced is transferred at once, and only once.
  • The second situation is to transfer data periodically from external systems to SAP and vice versa.
  • There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called “batch input” or “batch data communication”.
  1. SESSION METHOD
  2. CALL TRANSACTION
  3. DIRECT INPUT

Starting with the concept of data transfer, you will find details steps required for getting data into SAP.

Download Batch Data Communication User Guide

Credit: sapdocs.info
Read more

SAP Extended Withholding Tax Configuration Free Download

This document is a product of sapficoconsultant.com

Introduction

Withholding tax is applicable in few countries. Some of the countries which have withholding tax are United Kingdom, Slovakia, Turkey, Argentina, Brazil, Chile, Colombia, Mexico, India, Philippines , Thailand and South Korea. SAP has given an excellent solution to map the withholding tax scenario.


This material demonstrates how to config extended withholding tax in SAP.

Download here >> SAP Extended Withholding Tax Configuration

Useful SAP Site >> mySAP FI Tutorial
Read more

SAP Certification Questions Free Download

This is useful material for all guys need to prepare themself before take the certification exam.


You can download from SAP Free Download website.

Useful SAP Site SAP Tutorial
Read more

SAP Accounts Receivable & Accounts Payable Core Concept

This document demonstrates core concept of SAP FI Accounts Receivable and Accounts Payable.

The following contents are including in this material.


You can download from SAP Free Download website.

Useful SAP Site >> SAP Tutorial
Read more

SAP GUI 7.1

SAP GUI installations can be downloaded from SAP FTP Web site.

All files distributed in compliance to the Policies outlined at Official FTP Web site ftp://ftp.sap.com


ftp://ftp.sap.com/pub/sapgui/win/710/compilation1/
ftp://ftp.sap.com/pub/sapgui/win/710/patches/
ftp://ftp.sap.com/pub/sapgui/win/640/patches/
ftp://ftp.sap.com/pub/sapgui/win/640/compilation5/

New Features of the Installation Tool

This section describes the new features of NetWeaver SAPSetup (NW SAPSetup):

  • The new multi-product installation tool lets you maintain not only the SAP GUI for Windows 7.10 but almost all Windows-based SAP front-end software on a single installation server.

  • Installation server features, such as Import Product, help integrate additional SAP front-end components into an existing installation server.

  • You can configure packages with multiple SAP front-end components.

  • With NW SAPSetup you can manage multiple SAP front-end components that are deployed on the front ends.

  • If available on the installation server, you can deploy multiple SAP front-end components on the front ends using a command on a single line.

  • NW SAPSetup provides full-featured install, uninstall, update, and patch of SAP frontend components that are available on an installation server or distribution medium such as a DVD.

  • New wizard-driven user interfaces let you manage the installation server more easily.

  • You can install new components, uninstall existing ones, and update the remaining components in one cycle.

  • You can customize the installation of packages by programming events that support Visual Basic (VB) scripting.

  • Local Security Handling (LSH), when configured, lets you deploy SAP components on front ends without requiring administrative privileges on all machines.

You can download from SAP Free Download website.


Useful SAP Site >> SAP Tutorial
Read more

Followers

SCM in ERP

Subscribe via email

Enter your email address:

Delivered by FeedBurner

Recommended Posts