SAP Helpdesk | SAP Portal | SAP Forum | SAP Support

SAP FINANCE & CONTROLS: A BRIEF INTRODUCTION & OUTLINE

noreply@blogger.com (sapient) — Wed, 05 Oct 2011 05:15:00 +0000

Now, the new SAP GL – integrates many streamlined processes to be unified more closely to further alleviate any duplication of live-time tasks.

This New General Ledger Accounting in mySAP ERP has some dynamic advantages in comparison to the classic General Ledger Accounting (as used in SAP R/3 Enterprise Version) – such as the ability to run real-time reconciliation between Management Accounting (CO) and Financial Accounting (FI) – i.e. – there is a real-time integration with Controlling.

Previously time-consuming reconciliations are hence now rendered obsolete. The new SAP GL further allows the management of multiple ledgers within the General Ledger Accounting Module itself.

This creates the scope for portraying parallel accounting scenarios within the SAP System.
Controlling (CO) is the term by which SAP refers to “Managerial Accounting”.

The Organizational Elements in CO are Operating Concern, Controlling Area, and Cost Centers. Hence, the SAP CO Module helps management by providing reports on cost centers, profit centers, contribution margins, profitability, etc.
It focuses on internal users, in contrast to FI – which focuses on data drawn for
external reporting.

The transactions posted in FI are transferred to CO for cost accounting processing, analytical reporting, and audit-controlling spectrums.
There can be either a one-to-one relationship or there can be one-to-many relationship between
Controlling Areas Verses Company Codes. Hence, CO becomes the governing module that oversees the consolidation of costing data whereby management can derive their perspectives for analysis.

The SAP Controlling (CO) Module’s Components are:
Cost Element Accounting
Cost Controlling
Cost Center Accounting
Internal Orders
Activity-Based Costing
Product Cost Controlling
Profitability Analysis
Profit Center Accounting
Some methodologies that are unique in their structural concepts are – for example – CO PA & PCA. PA refers to Profitability Analysis that derives from how profitable your market-segments are on their external sides. EC-PCA refers to Profit Center Accounting that produces the analysis that portrays how your internal ‘profit centers’ are functioning in terms of their profitability. To further expand the
potential, we also have CO-PC in SAP – which streamlines Product Cost Controlling.

SAP FINANCE & CONTROLS: A BRIEF INTRODUCTION & OUTLINE

noreply@blogger.com (sapient) — Wed, 05 Oct 2011 05:10:00 +0000

SAP FINANCE & CONTROLS: A BRIEF INTRODUCTION & OUTLINE

In today’s world of innovation through Information Technology, SAP is truly a dynamic package by which one can integrate, diversify, and streamline their work-processes with multi-dimensional compatibility.

SAP – “Systems, Applications, and Products in Data Processing” – was founded in 1972 with its headquarters in Walldorf, Germany.For those who are in the Finance/Accounting Profession who wish to delve into a creative and
interactive scenario by which they can apply their hands-on experience & expertise to another level of fantastic intellectual stimulation, SAP FI/CO Implementation & Configuration is truly the ultimate. Their expertise will render them to very swiftly master its technical configuration – for the concepts are all
part of every Finance/Accounting Professional’s innate thought-process – and - the SAP modules follow a thorough schematic pattern by which all functionalities & technicalities are logically laid-out.

SAP Financial Accounting (FI) is an important core module where in live-time, the financial processing
transactions are all captured to provide the basis via which data is drawn for external reporting.

This SAP FI Module is integrated with many parallel modules that enable a company to unify processes that may have needed the utilization of many software packages.
Other Modules of SAP that commonly find a role of integration with FI are (but not limited to) Material Management (MM), Sales & Distribution (SD), Human Resources (HR), Product Planning (PP), Controlling (CO), etc.

Amongst these CO – Controlling is another major focus for those coming from the
Finance/Accounting/Auditing/Budgeting and Financial Reporting/Analysis Backgrounds/Professions.

SAP FI: There are many sub-modules that streamline and specialize in each aspect of the Financial
Accounting Processes:
AA – Asset Accounting
AP – Accounts Payable
AR – Accounts Receivable
BL – Bank Accounting
FM – Funds Management
GL – General Ledger Accounting
LC – Legal Consolidations
SL – Special Purpose Ledger
TM – Travel Management
Out of the above, FI-AR, FI-AP, & FI-AA are the three sub-modules that send simultaneous
postings to FI-GL.

Problems in processing batch input sessions

noreply@blogger.com (SAPhelpdesk) — Sun, 02 Oct 2011 15:29:00 +0000

What are the problems in processing batch input sessions How is batch input process different from processing online

i) If the user forgets to opt for keep session then the session will be automatically removed from the session queue(log remains). However if session is processed we may delete it manually.

ii)if session processing fails data will not be transferred to SAP database table.

Creation of a batch input session

noreply@blogger.com (SAPhelpdesk) — Sun, 02 Oct 2011 15:27:00 +0000

An ABAP program creates a batch input session. We need to submit the program and the batch session in back ground. How to do it?

Please go to SM36 and create background job by giving job name,job class and job steps (JOB SCHEDULING)

Call transaction ABAP

noreply@blogger.com (SAPhelpdesk) — Sun, 02 Oct 2011 15:23:00 +0000

What is the alternative to batch input session

Call transaction.

Alternative to batch input session ABAP

noreply@blogger.com (SAPhelpdesk) — Sun, 02 Oct 2011 15:22:00 +0000

What is the alternative to batch input session

Call transaction.

BATCH INPUT SESSION ABAP

noreply@blogger.com (SAPhelpdesk) — Sun, 02 Oct 2011 15:17:00 +0000

What is a batch input session

BATCH INPUT SESSION is an intermediate step between internal table and database table.
Data along with the action is stored in session ie data for screen fields, to which screen it is passed,program name behind it, and how next screen is processed.

Approach for writing a BDC program ABAP

noreply@blogger.com (SAPhelpdesk) — Sun, 02 Oct 2011 15:16:00 +0000

What should be the approach for writing a BDC program

STEP 1:
CONVERTING THE LEGACY SYSTEM DATA TO A FLAT FILE to internal table CALLED "CONVERSION".

STEP 2:
TRANSFERING THE FLAT FILE INTO SAP SYSTEM CALLED "SAP DATA TRANSFER".

STEP 3:
DEPENDING UPON THE BDC TYPE i)call transaction(Write the program explicity)

ii) create sessions (sessions are created and processed.if success data will transfer).

What are field symbols and field groups. ABAP

noreply@blogger.com (SAPhelpdesk) — Sun, 02 Oct 2011 15:13:00 +0000

What are field symbols and field groups Have you used "component idx of structure" clause with field groups

Field symbols
Field groups

ABAP Typical Structure

noreply@blogger.com (SAPhelpdesk) — Sun, 02 Oct 2011 15:11:00 +0000

What is the typical structure of an ABAP/4 program

HEADER
BODY
FOOTER

Pricing Overview

noreply@blogger.com (sapient) — Sun, 02 Oct 2011 07:50:00 +0000

Pricing Overview

Let’s take a typical example of how an item price is determined in a document. When

item information is entered, the system runs a check for appropriate pricing

procedures. The relevant pricing procedure is determined

based on the sales area, customer, and sales document type (these are

entered in the header of a sales document). Once it finds the right pricing

procedure, the system reads the condition type listed in the pricing procedure

sequentially, as maintained in the pricing procedure. Based on this condition type,

it determines the access sequence.

ROLE OF CACHE

noreply@blogger.com (saphelp) — Sat, 01 Oct 2011 19:57:00 +0000

Explain the role of cache in a disk subsystem:

(looking for: posted writes, to allow the OS to continue processing requests, rather than waiting for a write to be physically committed to a disk drive)

DATABASE ARCHITECT OF AN SAP

noreply@blogger.com (saphelp) — Sat, 01 Oct 2011 19:56:00 +0000

Explain how to layout or architect an SAP database server in terms of data, logs, and so on, to achieve the best performance:

(looking for: keep data and logs on separate spindles, RAID 1 or 1+0 best, separate data in discrete data and index volumes, move logs to separate high performance RAID 1 drive pairs, prefer hardware RAID to software/OS RAID)

RESPONSE TIME

noreply@blogger.com (saphelp) — Sat, 01 Oct 2011 19:55:00 +0000

Response time 'seems' to be slow, per a number of users that have called in to the help desk – how do you troubleshoot this?

(looking for: Check app servers for avg response times in DIALOG using ST03, compare to baseline stats; may also ask a user which particular transaction he is running, and then check the history of that transaction via ST03. Ask the user to enable response time checking on his SAPGUI, so that you can check his specific response time between the front-end and the application server. You will also want to ensure no one has changed logon load balancing, check ST04 for cache hit rates, and check ST06 for CPU utilization for users & system)

VERSIONS IN SAP

noreply@blogger.com (saphelp) — Sat, 01 Oct 2011 19:50:00 +0000

Discuss how the different releases of R/3 since version 3.1i differ in terms of hardware requirements:

(looking for the fact that every new release – to 4.0B, 4.5x, 4.6x, 6x – requires additional RAM, processing power, and even basic disk space just to host the same number of users).

UPDATED PROJECT

noreply@blogger.com (saphelp) — Fri, 30 Sep 2011 19:20:00 +0000

What is the difference between updated project and end to end project. explainAnswer1:Some organisations select to implement SAP module by module, thus gets updated as per their convenience / schedule. This is called as updated project.

Some organisations simply plan all integrated functional modules and decide to go-live with all functional modules and take their entire operations on SAP. This is called as End to End SAP implementation project.

Answer2:Upgrade Project is a project where in SAP is already in place and it is the version upgrade from a lower end to a higher version.

End to End project is a project where SAP is implemented for the first time.

LOCKING ACCOUNTS

noreply@blogger.com (saphelp) — Fri, 30 Sep 2011 19:18:00 +0000

When you are Locking/Unlocking accounts what happens behind the scenes?

User accounts can be locked/unlocked via SU01 (User Maintenance.) But, what goes on behind the scenes? What does the system do to actually set this?

The table USR02 gets updated. The field UFLAG determines if the user account is locked or unlocked. The value "64" indicates that the user account is locked. The value "0" that the user account is unlocked. Knowing this, you can then issue an update statement at the database level that locks all users in mass.

Don't lock yourself out, though! Use exceptions for super user accounts in your update statement.Notice that 4.6b and above have made improvements to this kind of task, making the locking/unlocking a bit easier. However, changing at the database level is much faster and it is just one simple query.

LOCKED TRANSACTIONS

noreply@blogger.com (saphelp) — Fri, 30 Sep 2011 19:15:00 +0000

How can you View Locked Transactions?

As you know, you can lock/unlock transaction codes via SM01. But, how do you go about viewing the transactions that are locked in the system? You need to look in field CINFO, table TSTC.

Within SAP, you can use either SE11 or SE16 to browse the table contents. Make sure you enter "A0" as the "HEX01 data element for SYST" starting value and "A9" as the ending value. This will list all the transactions locked in the system.

Note:

The CINFO field description is "HEX01 data element for SYST

Transaction code SM01 -- Lock/Unlock Transactions -- cannot be configured for display-only authority and is not easily used for that purpose anyway. Check your SAP system for the SAP report RSAUDITC or RSAUDITC_BCE (they both contain

DISABLING MULTIPLE LOGONS

noreply@blogger.com (saphelp) — Fri, 30 Sep 2011 19:11:00 +0000

How do you Disable Multiple Logins in the Same Client?

To disable multiple user logins within the same client implement this parameter in the instance profile:

login/disable_multi_gui_login = 1

If you do not use this parameter in your system, users have the ability to ignore the warning window at the time they try to login to the same client. Activating this parameter in your system will make you look good if you get audited!

How about exceptional logins?

In case you're wondering how to allow multiple logins for certain key users you can implement parameter login/multi_login_users. You can list the user IDs that should be ignored if the parameter above is active in your system.

CLIENT COPY VS CLIENT REFRESH

noreply@blogger.com (saphelp) — Fri, 30 Sep 2011 19:06:00 +0000

What is the difference between a client

copy and client refresh?

Some times these are the same, For

example, if you are performing a copy to an

existing client for the express purpose of

updating the data, then it is called Client

Refresh.

If you are copying to a newly created client

then it is more appropriate to say “client

copy.”

Another way of thinking about this is that a

client copy from production to a QA server

or from production to DEV server is really a

client refresh

Some times these are the same, For example, if you are performing a copy to an existing client for the express purpose of updating the data, then it is called Client Refresh.

If you are copying to a newly created client then it is more appropriate to say “client copy.”

Another way of thinking about this is that a client copy from production to a QA server or from production to DEV server is really a client refresh.

ADDING NEW INSTANCE

noreply@blogger.com (saphelp) — Fri, 30 Sep 2011 19:01:00 +0000

We want to install another new instance on same

development box. Is this possible? What are some

of the important considerations?

Yes, it is possible to have more than one

instance on a single box. The key is to use a

different SID and a different system number.

It is also important to note that for a 64 bit

SAP kernel, SAP recommends a 20 GB swap

space for 1st instance and 10 GB per each

additional instance.

DISABLE IMPORT ALL IN STMS

noreply@blogger.com (saphelp) — Fri, 30 Sep 2011 18:56:00 +0000

How can one disable the "Import All" button on

STMS for the queues?

Controller. Run STMS->Overview->System.

Choose the System you want to disable

import all. Go to Transport Tool tab.

Add/Create Parameter "NO_IMPORT_ALL"

set its value to 1.

So Importing the Transport Requests is the critical. Sometimes by mistake if one click on the button Import All in the production environment all the Transport Request which is in released status or already Imported to Production can be directly Imported to the production environment (Which may not be required in the Production). This will create great impact in the production Server.To avoid such situation, IMPORT ALL Icon should be disabled in STMS.Procedure to Disable IMPROT_ALL Icon in STMS:-1) Go to STMS Tcode

2) Go to Menu Option Overview

3) Select System4) Choose SAP SYSTEM

5) Go to Transport Tool Tab

6) Create Parameter "NO_IMPORT_ALL" with value 1 (True)

7) Save it.

OK CODE IN BASIS

noreply@blogger.com (saphelp) — Fri, 30 Sep 2011 18:51:00 +0000

What is an OK code?

An OK Code is used by a program to

execute a function for example after a

pushbutton has been clicked

ok_code acts just as a temporary variable that stores the value of sy-ucomm.

When user interacts with the screen elements, the function code that you have assigned is filled in the sy-ucomm field which is turn gets reflected in OK_CODE.

In your ABAP programs, you should work with the OK_CODE field instead of SY-UCOMM. There are two reasons for this: Firstly, the ABAP program has full control over fields declared within it, and secondly, you should never change the value of an ABAP system field. However, you should also always initialize the OK_CODE field in an ABAP program for the following reason:

In the same way that the OK_CODE field in the ABAP program and the system field SY-UCOMM receive the contents of the corresponding screen fields in the PAI event, their contents are also assigned to the OK_CODE screen field and system field SYST-UCOMM in the PBO event. Therefore, you must clear the OK_CODE field in the ABAP program to ensure that the function code of a screen is not already filled in the PBO event with an unwanted value. This is particularly important when the next PAI event can be triggered with an empty function code (for example, using ENTER). Empty function codes do not affect SY-UCOMM or the OK_CODE field, and consequently, the old field contents are transported.

DIFFERENCE BETWEEN SAP MEMORY AND ABAP MEMORY

noreply@blogger.com (saphelp) — Fri, 30 Sep 2011 15:41:00 +0000

What are the differences between SAP memory and ABAP memory

ABAP Memory is a memory area in the internal session (roll area) of an ABAP program. Data within this area is retained within a sequence of program calls, allowing you to pass data between programs that call one another. It is also possible to pass data between sessions using SAP Memory.

SAP Memory is a memory area to which all sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session (as with ABAP memory) or to pass data from one session to another

SAP memory is a memory area to which all main sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session, or to pass data from one session to another. Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters).

These parameters can be set either for a particular user or for a particular program using the SET PARAMETER statement. Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement. The most frequent use of SPA/GPA parameters is to fill input fields on screens ABAP/4 Memory ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements.

Data within this area remains intact during a whole sequence of program calls. To pass data to a program which you are calling, the data needs to be placed in ABAP memory before the call is made. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory. If control is then returned to the program which made the initial call, the same process operates in reverse.

The SAP memory, otherwise known as the global memory, is available to a user during the entire duration of a terminal session. Its contents are retained across transaction boundaries as well as external and internal sessions. The SET PARAMETER and GET PARAMETER statements allow you to write to, or read from, the SAP memory. ABAP/4 memory The contents of the ABAP/4 memory are retained only during the lifetime of an external session (see also Organization of Modularization Units).

You can retain or pass data across internal sessions. The EXPORT TO MEMORY and IMPORT FROM MEMORY statements allow you to write data to, or read data from, the ABAP memory. This code is from which program you want to export to the ABAP memory: export ist_resb to memory id 'ZPPC0122_FD'. where ist_resb is the internal table name & ZPPC0122_FD is the include name of my program ZPPC0122.

This code is from which program you want to import from the ABAP memory import *ist_resb *= ist_resb from memory id 'ZPPC0122_FD'. where ist_resb This internal table is the importing program internal table. ist_resb This internal table is the exporting program internal table. But remember in both the program you have defined the same internal table with same structure Nowadays Export & Import statement is OBSOLETE it gives SLIN CHECK ERROR in SAP 6.0 Version

TYPES OF LUW's IN ABAP

noreply@blogger.com (saphelp) — Fri, 30 Sep 2011 15:37:00 +0000

Different types of LUWs. What r they?

Two types of LUW are:

DB LUW

A database LUW is the mechanism used by the database to ensure that its data is always

consistent. A database LUW is an inseparable sequence of database operations that ends with a database

commit. The database LUW is either fully executed by the database system or not at all. Once a database

LUW has been successfully executed, the database will be in a consistent state. If an error occurs within a

database LUW, all of the database changes since the beginning of the database LUW are reversed. This

leaves the database in the state it had before the transaction started.

SAP LUW

A logical unit consisting of dialog steps, whose changes are written to the database in a single

database LUW is called an SAP LUW. Unlike a database LUW, an SAP LUW can span several dialog steps, and

be executed using a series of different work processes.

Database Logical Unit of Work (LUW)

From the point of view of database programming, a database LUW is an inseparable sequence of database operations that ends with a database commit. The database LUW is either fully executed by the database system or not at all. Once a database LUW has been successfully executed, the database will be in a consistent state. If an error occurs within a database LUW, all of the database changes since the beginning of the database LUW are reversed. This leaves the database in the state it was in before the transaction started.

The database changes that occur within a database LUW are not actually written to the database until after the database commit. Until this happens, you can use a database rollback to reverse the changes. In the R/3 System, database commits and rollbacks can be triggered either implicitly or using explicit commands.

Implicit Database Commits in the R/3 System

A work process can only execute a single database LUW. The consequence of this is that a work process must always end a database LUW when it finishes its work for a user or an external call. Work processes trigger an implicit database commit in the following situations:

· When a dialog step is completed Control changes from the work process back to the SAP GUI.

· When a function module is called in another work process (RFC). Control passes to the other work process.

· When the called function module (RFC) in the other work process ends. Control returns to the calling work process.

· When a WAIT statement interrupts the work process.