Sunday, May 8, 2011

SAP FI Certification paper -1

1. Which of these statements on document principles are correct?
R/3 can assign the document numbers always


A business event triggers only one document within R/3


Each business event creates an accounting document within R/3


R/3 will link related documents in the system

2. In the payment process, automatic options to the users are
select open invoices to be paid/collected, post payment document


post payment documents/print payment media


select open invoices to be paid or collected, post payment document, print payment media

3. Which of the following are true.
any payment block can be removed in payment proposal edit


only line item payment block is removed during the payment proposal


items that cannot be paid are detailed in the exception list

4. Which of these statements on payment program are correct
there are four steps in payment process, viz., parameters, proposal, program, print


once the parameters have been specified, the print program is scheduled to generate payment media

5. Every run of the payment program is identified by two fields
run date


identification

6. Which of the following statements are true
The run date is recommended to be the actual date when the program is executed


The field identification is used to run print program

7. Which of the following statements are correct
the G/L account name for house banks must match the names given to the house bank in the bank directory


the G/L account names for house banks are user definable


the G/L account names for house banks could be the bank name and account number


the G/L account names for house banks are defined in bank directory


at company code level, G/L account names for house banks can be different from those in chart of account

8. Which of the following statements are true in respect to payment program configuration in all codes area
sending company code and paying company code are same always


by specifying the vendor/customer special G/L transaction to be paid, we can process specified special G/L transaction only


by activating payment method supplement, we can print and sort payments





9. Which of the statements are true in respect to configuration of payment program bank determination area
without ranking order, system will not process the payment


bank/payment method combination is must to define ranking order


without maintaining the value date in bank selection, system will not process the payment

10. If we are using check management, which of the statements is true
define check lots in order to print checks


check lots are used only for automatic payments

11. True/false
all company codes in the payment run parameters must be in the same country


a payment method can only be used if it is entered in the account master record


the payment proposal can only be edited, deleted and recreated as often as desired


the exception list is a part of the payment proposal

12. When running the dunning program
we can edit proposal


we cannot delete the proposal


we can recreate the proposal until the dunning clerk is satisfied with the result


after completing the dunning proposal list, dunning data is updated in master records

13. Which of the following statements are true
one time accounts cannot be dunned


we can assign two dunning procedures to customer master records


dunning procedure can process only standard transactions


interest can be posted at the time of dunning

14. The maximum dunning level can be defined in the dunning procedure is
four


six


nine

15. An item whose days in arrears are smaller or identical to the grace periods, dunning program will consider for the dunning notice. TRUE/FALSE

16. Which of the following statements are false
we cannot specify per dunning level that interest is to be calculated


we cannot print a dunning notice in a legal dunning procedure, although no further account movements have occurred


we can set a minimum amount for the dunning charges on each dunning level

17. What information does a dunning run change?
the date of the last dunning run in the customer master record


the dunning level in the customer master record


the dunning level in documents for which dunning notices are created


from (layout set) specifications in the customer master record for the text in the next dunning letter


the dunning procedure in the customer master record for the next dunning run



18. Which of these statements are true
we can calculate interest on G/L accounts under interest on arrears method


each interest id must be assigned on interest calculation type

19. Two steps to define financial statement versions are
enter it in the directory of financial statement version


define hierarchy levels and assign accounts

20. Which of the following statements are true
a financial statement version consist of maximum 9 hierarchy levels


we cannot assign account group according to balance


drill down report is a tool that enables to analyze sub ledger transaction figures only

21. Individual value adjustment for doubtful receivables are possible
through special G/L transactions


through normal transactions


both of the above

22. Foreign currency valuation is possible
only vendor/customer open items


only balance sheet items


both of the above

23. Which of the statements are true
when we are valuating open items without update for reversal of the adjustment posting after key date, user can define another posting date in place of key date +1


when we have regrouped the receivables/vendors, system carries out adjustment postings


allocating costs to financial accounting through external settlement, the G/L is updated online/realtime

24. Depreciation posting can be executed
through batch input session


direct FI postings


any one of the above

25. To set up the financial statement version in your company, maximum limit is 9. TRUE/FALSE





KEY - T (True), F (False)

  1. A-T, B-F, C-F, D-T
  2. A-T, B-T, C-T
  3. A-T, B-T, C-T
  4. A-T, B-F
  5. A-T, B-T
  6. A-T, B-F
  7. A-F, B-T, C-T, D-F, E-F
  8. A-F, B-T, C-T
  9. A-F, B-T, C-F
  10. A-T, B-F
  11. A-T, B-F, C-T, D-T
  12. A-T, B-F, C-T, D-F
  13. A-F, B-F, C-F, D-F
  14. A-F, B-F, C-T
  15. FALSE
  16. A-F, B-F, C-T
  17. A-T, B-T, C-T, D-F, E-F
  18. A-F, B-T
  19. A-T, B-T
  20. A-F, B-T, C-F
  21. A-T, B-F, C-F
  22. A-T, B-T, C-T
  23. A-T, B-T, C-T
  24. A-T, B-T, C-T
  25. FALSE

SAP FI Certification paper - 2

1. Which of the following statements are correct with respect to business area
one business area can be used for many company codes


business areas must be assigned to company code in the IMG


they are used for internal P&L and balance sheets


a company code can have many business areas

2. Which of the following statements are correct
a plant is assigned to only one company code


a company code must be assigned to one chart of accounts only


a chart of accounts can be assigned to multiple company codes


a plant can be assigned to many company codes

3. What are true with respect to business area
a company code can have many6. business areas


a business area can be across company codes

use of business area is not optional in R/3 system

balance sheets and profit and loss statements can be drawn up for business areas

4. Which of the following statements may be false with respect to a business area
the use of business area is optional


a company code can have many business areas

business area balance sheet will always balance

none of the above

5. The standard delivery clients in a R/3 system are
client 000, 001 and 002


testing client 777 and training client 999

client 001, 000,002 and training client 999

client 000 and 001

client 001, 000 , testing client 777 and training 999

6. What are all the possible meanings of the word ‘client’ that have been used
a customer implementing R/3 system


an individual PC in which batch inputs are done for uploading to SAP at a later date

the highest technical entity in R/3

the data server

the front end presentation PC which interacts with SAP system
7. The three tier in R/3 system is represented by
client, customer and application


data, user and application

user, data base, programs

presentation client, R/3 application and data base

application, data base and customer of R/3


8. The entity in R/3 to provide financial statements and results at the lowest level is
company


company code

controlling area

plant

enterprise controlling

9. Which of the following statements is always false with respect to a company code
a company code can have many plants


a company code can have many companies

a company code can be linked to only one controlling area

a company code need not be linked to an operating concern

a company code can have many sales organizations

10. Which of the following statements are always true
a sales organization can be assigned to only one company code


a company can have many company codes

a company must be linked to a controlling area

a company code must always be assigned to a company

an operating concern can indirectly contain only one company code

11. Which of the following entities are optional to implement the core financial module of R/3
operating concern


controlling area

business area

plant

company code

12. The menu hierarchy in standard R/3 system is
main menu, application menu and task menu


main menu, sub menu, task menu and help menu


system menu, application menu and help menu


main menu, application menu and help menu


client menu, application menu and user menu

13. For a user with two user ids to the same SAP R/3 client, the maximum no. of sessions that could be open are
six


nine


twelve


eighteen


twenty four

14. The order of fields as they appear during the log on to an R/3 system is
client, user id, password


language, client id, password


client, user id, password, language


user id, client, password, language



15. Which of the following is not seen by the user normally in the status bar of the SAP screen
client number/id


session number


data server name/id


user id/name


information, error, and warming messages

16. A user has multiple sessions open and when open of the session is closed by the user
the system does not automatically save the data/information of the session being closed


system always prompts for saving the data in the session being closed


system always automatically saves the data/information of the session being closed without prompting’


system prompts for saving the dta of the session being closed at the time of user log-off from the system

17. Which of the following entities cannot be directly assigned to a company code
company


business area


controlling area


functional area


financial management area

18. ABAP stands for
advances in business applications programming


applications in business and advanced program


advanced business applications programming


advanced business for advanced program


advantage in business applications programming

19. The configuration of the R/3 is done through
the implementation guide


the implementation assistant


business navigator


business engineer


sessions manager

20. The ASAP CD contains
the implementation guide


implementation assistant


concept check tool


business navigator


Q&A Db

21. Which of the following statements are true regarding ASAP – project preparation phase
the business blueprint document must be prepared


enterprise scope area document must e prepared for initial project planning


project plan must be prepared


the project kick off meeting is very essential to involve all the key users and project team members to communicate the objectives and mission of the project


technical requirements planning must be taken up



22. Which of the following are true with respect business blueprint phase
when customer inputs are updated on the Q&A db, there is a direct automatic updation of the IMG for the business processes/components in scope to be customized


when the business processes are identified and updated in the system, a list of activities to be taken up in IMG for customization is generated


the standard reference model of R/3 system cannot be directly accessed from the Q&A db


business blueprint document shall be generated

23. Which of the following statements re true with respect to testing and quality reviews as recommended by SAP
he volume and stress test must be conducted on the same system in which user training is done


testing a tool which avoids retrospective changes and acts as an early warning system to correct the customization of business processes


the power (key) users shall not be involved in the testing process as it would hinder timely completion of the activity


there must be quality control of the first four stages before the ‘go-live’ phase


external consultants must always carry out quality control

24. What are the three data types in SAP
master data, transaction data, and balance data


master data, table data, and user data


master data, table data, and transaction data


table data, user data and transaction data


master data, table data and server data

25. Various company codes access a controlling area should have
same currency


same fiscal year variant


same chart of accounts


same controlling organization structure





KEY

  1. A-T, B-F, C-T, D-T
  2. A-T, B-F, C-T, D-T
  3. A-T, B-T, C-F, D-T
  4. A-F, B-F, C-F, D-F
  5. A-F, B-F, C-F, D-T, E-F
  6. A-F, B-F, C-T, D-F, E-F
  7. A-F, B-F, C-F, D-T, E-F
  8. B
  9. B
  10. B
  11. C,D
  12. A
  13. C
  14. C
  15. .
  16. A
  17. B,D
  18. C
  19. A
  20. B,C,E
  21. B,C,D,E
  22. B,D
  23. B,C,D
  24. C
  25. C

SAP FI Electronic Bank Statement

FI Electronic Bank Statement is an article provided by SAP AG. This SAP FI article is intended for SAP System Administrators, Finance and Controlling (FICO) developer and SAP technology Consultants.
This SAP FI article applies to SAP R/3 systems and it explains FI electronic Bank statement processing in detail. With the help of this SAP FI article you will learn various processing steps of electronic bank statement such as importing data, entering, processing, posting and displaying data. Moreover you will learn to start program and to configure SAP FI system for this use.
Following are the few topics covered in this SAP FICO article.
  • Electronic Bank Statement: Configuration
  • Core Terms and Their Significance for Configuration
  • External Transaction
  • Posting Rules
  • Transaction Type
  • Posting Specifications and Account Determination
  • Account Symbols And Account Allocation
  • Assigning G/L Accounts to Account Symbols
  • Account Allocation for Business Transactions in Foreign Currency
  • Account Allocation Using Function Enhancement: Account Modification
  • Recommended Sequence of Configuration Tasks
  • Creating Transaction Types
  • Allocating Banks
  • Creating Keys For Posting Rules
  • Allocating External Transactions
  • Defining Posting Rules
  • How Does The Automatic Posting Function Work?
  • Information in the Electronic Bank Statement
  • Using the Electronic Bank Statement for Postings and Clearing
  • Electronic Bank Statement: Usage
  • Importing Data
  • Interpreting the Note to Payee Fields
  • Output Data
  • Executing the Program
  • Displaying the Overview
  • Post processing Bank Statements Using the Transaction
  • Post processing Bank Statements with Batch Input Sessions
  • Conversion Programs
  • Functional Enhancements For The Electronic Bank Statement
  • Formats For The Electronic Bank Statement

SAP Cost Center Accounting (CO-OM-CCA)

SAP Cost Center Accounting (CO-OM-CCA) is a document provided by SAP AG. This SAP CO article is intended for SAP System Administrators, Finance and Controlling (FICO) developer and SAP technology Consultants.
This SAP CO article explains Cost center accounting for controlling purposes within your company by helping individual functional areas for decision making. More specifically this SAP CO component cost center accounting help you to analyze overhead costs and records costs with reference to plan values. Moreover you will learn to implement CO-OM-CCA component in R/3 Systems with FI General Ledger component, FI Assets Payable component, FI Assets Receivable Component and CO Overhead Orders.
Following are the few topics covered in this SAP FICO guide.
Cost Center Accounting (CO-OM-CCA)
Master Data in Cost Center Accounting (CO-OM-CCA)
Processing Master Data
Requesting a Master Data Change in the Intranet/Internet (AC)
Enterprise Organization (CO)
Standard Hierarchy
Cost Elements
Cost Centers
Activity Types
Statistical Key Figures
Resources
Cost Center Planning (CO-OM-CCA)
Short-Term Business Planning
Reconciliation of Cost Center Planning With Other Applications
Cost Center Planning Scope
Manual Planning
Utilities
Periodic Allocations in Plan
Manual Actual Postings (CO-OM-CCA)
Editing Manual Actual Postings
Re posting Costs and Revenues Manually
Re posting Line Items
Time Sheets
Direct Activity Allocation
Re posting Internal Activity Allocation
Entering Sender Activities
Manual Actual Price
Manual Cost Allocation
Entering Statistical Key Figures
Actual Postings to Activity Types
Receivers of Manual Actual Postings
Funds Commitment (Cost Centers, Internal Orders, Projects)
Period-End Closing (CO-OM-CCA)
Overview of Period Closing
Schedule Manager (CA)
Periodic Re posting
Accrual Calculation
Transfer of Statistical Key Figures from the Logistics Information System (LIS)
Overheads
Periodic Allocations
Overview of Allocation Methods
Senders and Receivers for Periodic Actual Postings
Defining Periodic Re postings or Periodic Allocations
Example: Periodic Re posting of Telephone Costs
Variance Calculation
Redistribution of Fixed Costs
Actual Price Calculations
Year-End Closing 890
Carrying Forward Commitments
Information System (CO-OM)
Interactive Information System
Period-Based Information System
Important Standard Reports in Cost Center Accounting
Report Definition
Cost Center Summarizations
Cross-Application Topics (CO-OM)
Validation and Substitution
Archiving
Application Link Enabling (ALE)
Changeover to the Euro

Regular Expressions (Regex) and its use in ABAP

Supported as of Release 7.00 Regular Expressions (Regex) are rarely found in ABAP. Have you ever heard something about Regex? We believe so. This article will give you a brief overview and present very good articles from SDN.

Even in ABAP Regular Expressions (Regex) is not a new issue. ABAP supports regular expressions as of Release 7.00, released to customers on Oct 24, 2005. Although not so new its use is rarely found in ABAP. One of reasons is that SAP has already provided other ways to search for patterns e.g. SEARCH txt FOR pattern and IF txt CP pattern.

But what is Regex after all?

Wikipedia

“In computing, a regular expression, also referred to as regex or regexp, provides a concise and flexible means for matching strings of text, such as particular characters, words, or patterns of characters. A regular expression is written in a formal language that can be interpreted by a regular expression processor, a program that either serves as a parser generator or examines text and identifies parts that match the provided specification.”

There is a very good tutorial about Regex at http://www.regular-expressions.info. We will skip the basics of Regex and go directly to its use in ABAP.

Using Regex in ABAP

Regex is more powerful than traditional SAP patterns and is commonly used for searching and validating text. ABAP supports Regex in the statements FIND and REPLACE and via the the classes CL_ABAP_REGEX and CL_ABAP_MATCHER. There is an excellent article at SDN produced by Shaira Madhu with many more details of Regex in ABAP.

Let’s see some examples.
Example 1 – Tests if text starts with Hello (case sensitive)

DATA text TYPE string.
DATA moff TYPE i.
DATA mlen TYPE i.

text = `Hello World example`.

FIND REGEX '^Hello' IN text MATCH OFFSET moff MATCH LENGTH mlen.
IF sy-subrc = 0.
WRITE / text+moff(mlen).
ENDIF.

Example 2 – Removes example from the text only if it is the last word

DATA text TYPE string.

text = `Hello World example`.

REPLACE REGEX 'example$' IN text WITH ''.

IF sy-subrc = 0.
WRITE / text.
ENDIF.

Example 3 – Validates e-mail using the class CL_ABAP_MATCHER

DATA email TYPE string VALUE `webmaster@sapignite`. "missing .com
DATA matcher TYPE REF TO cl_abap_matcher.

matcher = cl_abap_matcher=>create(
pattern = `\w+(\.\w+)*@(\w+\.)+(\w{2,4})`
text = email ).

IF matcher->match( ) IS INITIAL.
MESSAGE 'Invalid e-mail' TYPE 'I' DISPLAY LIKE 'E'.
ENDIF.

Tip: For testing Regex without coding you can use the ABAP program DEMO_REGEX_TOY.

DEMO_REGEX_TOY screenshot

DEMO_REGEX_TOY screenshot

SAP ABAP: Using Field Symbols and References

The SAP® ABAP programming language provides its developers the power to create dynamic and flexible applications. In a previous article in ERPtips titled Saving Customer Time and Budgets via Flexible Programming (June 2004), we introduced some of the techniques that will let you do flexible and dynamic programming and avoid hard-coding values in programs. One important dynamic programming technique used by SAP developers entails a combination of field symbols and data references. In this article, we will see how this is done.
We will start with a brief explanation of Data References and their advantages and uses. The structure of programs that use field symbols and data references will also be discussed. Finally I will present a fully functional program that allows you to read a database table name, and then uses dynamic programming concepts to print its contents. (The user enters the table name and the program prints its contents).
Please note that the field symbols and references concept is vast and a lot of variants exist. However, in this article, we discuss the important forms that may be used in dynamic programming. For a detailed discussion of field symbols and/or data references, refer to the SAP documentation at http://help.sap.com.
These are some of the questions that this article will address:
What are the commands and statements for creating data references in programs?
How are field symbols declared in programs?
What are the steps to create data objects dynamically using reference variables?
How do I combine field symbols and data references for creating dynamic programs?
This article is primarily intended for ABAP developers and consultants. I will assume that the reader is familiar with basic ABAP concepts and has some knowledge of dynamic programming. All the screen images in this article have been taken from ECC 6.0, although the instructions are relevant to other versions of SAP as well.
An Overview of ABAP Data Reference Variables and Data References
Every data object declared within your program has an address in the memory. The address is also known as the reference. SAP ABAP lets you define data reference variables within the program. These variables contain the address (or reference) of data objects, and may be said as pointing to the object in question. A data reference variable may point to single fields, as well as to structures and internal tables.
You may simply define a data reference variable as shown below:
DATA: MYREF TYPE REF TO TYPENAME.
The data reference variable may point to data objects of any type. For example, you may define a data reference that points to a date. The declaration will be like the one shown below:
DATA: MYREF_D TYPE REF TO D.
In the above case, the type that the declaration points to has been fully specified (i.e., date). You may also make a generic declaration. A generic declaration will look like the one shown below:
DATA: MYGENREF TYPE REF TO DATA.
In case this, the type is not specified, but rather we used a generic type, DATA. This may point to a data object of any type. While creating data objects, you need to specify what type of data object the generic reference is to point to (we will see this in the latter part of the article).
When a data reference variable is initially defined, it points to no data object (i.e., it has a NULL reference). If you want to instantiate the data references variable from data variables, you must use a GET REFERENCE statement, as shown below:
GET REFERENCE OF MY_DATE INTO MYREF.
The above statement will populate the reference variable MYREF with the address of the data object MY_DATE.
In order to access the content of the object to which a data reference is pointing, the reference must be de-referenced. You may use the dereferencing operator (->*) for this purpose.
For example, you may have a reference MYREF pointing to a date; by using the dereferencing operator, we can write MYREF->* and the value of the date that is pointed to is printed, as follows:
WRITE: MYREF->*.
You may also use the MOVE statement in order to assign a value to the location the reference is pointing to. An example of this is shown below:
MOVE ’20100101′ to MYREF->*.
After the above statement is run, the MYREF reference variable will point to the date having a value of 01.01.2010.
You may assign the value of a reference variable to another reference variable, such as
MYREF = MYREF2.
Generation of ABAP Data Objects
You may use data references in conjunction with the CREATE DATA statement in order to generate data objects at runtime. You may use the CREATE DATA statement to create single fields structures as well as internal tables.
The generic syntax of this is as follows:
DATA: MYREF TYPE REF TO TYPENAME.
CREATE DATA MYREF.
A simple example for creating a date at runtime is shown below (the “D” indicates date):
DATA : MYREF TYPE REF TO D.
CREATE DATA MYREF.
The above would create a data object having a date type and the MYREF would be a reference to it.
If you declared a generic type reference variable, then you need to specify the type of the data object to be created in the CREATE DATA statement. The generic syntax form of this is shown below:
DATA: MYREF TYPE REF TO DATA.
CREATE DATA MYREF TYPE TYPENAME.
Our date example may be changed as shown below:
DATA : MYREF TYPE REF TO DATA.
CREATE DATA MYREF TYPE D

Free bug tracking software

I just had to take a minute and write about MantisBT, a free bug tracking software application.
I’m big on hosting my own stuff and having free software. Although it’s free, I always donate when I find value in things. It’s just the way I think software should be. Software is good. One person’s work can improve the lives of dozens of people or as many as millions.
MantisBT is a free popular web-based bugtracking system (feature list). It is written in the PHPscripting language and works with MySQL, MS SQL, and PostgreSQL databases and a webserver. MantisBT has been installed on Windows, Linux, Mac OS, OS/2, and others. Almost any web browser should be able to function as a client. It is released under the terms of the GNU General Public License (GPL).
My experience installing it was excellent. I simply uploaded the files to my webserver, created the database through my cPanel, and walked through the installation page. In minutes, I had a robust tracking system at no cost. This thing is powerful enough for an enterprise but simple enough for a small development company.
What’s more, there is a WordPress plugin that allows you to display open tickets on a page!
If you’re looking for some tracking software with plenty of features, but easy-to-use features, then give MantisBT a look.

What is SAP

SAP stands for “System, Applications and Products in Data Processing”. SAP is the largest business software company in the world. SAP is the largest Enterprise Resource Planning (ERP Software) solution software provider. SAP’s main products are SAP ERP (formerly known as SAP R/3) and SAP BusinessObjects software. SAP software has three-tier application architecture: database, application server and client SAPgui (presentation layer). As per the reports there are over 100,600 SAP installations at more than 41,200 companies in more than 120 countries.R/3 architecture was replaced with the introduction of ERP Central Component (ECC ).

SAP's Business Suite contains five enterprise applications. They are SAP ERP , Customer Relationship Management (CRM), Product Lifecycle Management (PLM), Supply Chain Management (SCM), and Supplier Relationship Management (SRM).
Other major business solutions offerings include Advanced Planner and Optimizer (APO),Business Information Warehouse(BW), Business Intelligence ( BI ), Human Resource Management Systems(HRMS), Exchange Infrastructure(XI) , Knowledge Warehouse(KW), SAP Portal (EP), Master Data Management ( MDM ), xApps, Training and Event Management (TEM), Internet Transaction Server (ITS) etc .
ABAP

ABAP stands for Advanced Business Application Programming and it’s a high level programming language used in SAP for the development and other customization processes. Normally a transactioncode is used for executing an ABAP program. For example we can use the transaction code VA01 for creating a sales order.
In this website we are trying to collect SAP Tutorials and arrange different SAP technical and functional materials for professionals seeking for references. Mainly we are trying to collect ABAP tutorials, BAPI, LSMW, IDOC, ALE, ABAP syntax ,ALV, SAPSCRIPTS, Smartforms like technical module topics and NetWeaver, SAP HR, SAP MM, SAP SD, FICO, PP, PM like functional modules. SAP ABAP interview questions and answers, SAP Certification details and software download are also available in the site

HR Certification Questions about TIME MANAGEMENT

TIME MANAGEMENT

1. The prerequisite for planning shifts in Time Management
• Planned Working Time
• Availability Infotype
• Personal Work Schedule
• Requirements Profile
2. If work schedule for salaried and hourly paid employees are not different,then with respect to time management
• 1 grouping is sufficient
• 2 distinct groupings are required
• Insufficient information
• Copy the standard SAP entries
3 A public holiday calendar has the following features
• Is assigned to a personnel subarea
• Can have public holidays with distance to Christmas
• Can have holidays with specific dates and days of the week
• Uses employee subgroup grouping for permissibility for specific employees
4. Day Types are used to define
• Different kinds of holidays in a holiday calendar
• Are used to represent off days
• Are used for determining whether employees have to work on public holidays and whether they are still paid on their days

5. In the SAP R/3 system,Day Off is represented by
• Creating a Daily work Schedule
• Using public holiday class
• Using the zero planned working hours check box
6. Whether or not a day is a day off in the work schedule is based on the following criteria
• Planned Hours
• Day type
• Public Holiday
• Work Schedule Rule
7 Time Management Status 1 represents
• No time evaluation
• No processing in payroll
• Time Evaluation planned
• Integration with Payroll
• Time Evaluation actual
8. Each absence type is assigned to a time constraint Class, so as to reference
• Collision Checks
• The number of records that can be present at any point of time
• Public Holiday Class
• Absence quota types
9. In SAP, inactive days are handled using
• Deduction rules
• Rounding rules
• Absence quotas
• Reduction rules
10. Schema TQTA has the following features
• Automatic accrual of absence entitlements using time evaluation
• Special schema used for accrual of absence quota
• Time Evaluation is a prerequisite to run this schema
• Time Management Status is to be set to 1

11 the following HR infotypes are mandatory for CATS
• Actions,Organisational Assignment,Personal data
• Actions,Personal Data,Planned working time
• Actions,Personal Data,Time sheet Defaults
• Actions,Planned Working Time,Time Sheet Defaults,Planned Working Time
12 In customizing Data Entry Profile, the following are true
• It determines the data entry process for the time data that is entered using the profile
• It determines the layout of the data entry screen
• It controls the target components to which the time data can be transferred
• Specify use of workflow for approval

13. Which of the following are not standard workflow tasks for CATS approval process
• Approver specified by employee
• Approval by superior
• Approval by payroll administrator
• Approval by employer
14 The following infotypes are mandatory if you are working with time Evaluation
• Actions,Organisational Assignment,Planned working time,Personal Data
• Organizational Assignment,Planned working time, Date specifications,Basic Pay
• Organizational Assignment,Planned Working time,Personal Data
• Actions, Planned working time, Date Specifications
15 Which of the following are not tasks of R/3 Time Management
• Processing time events
• Correcting and supplementing time events
• Transferring time events to the interface table CC1TEV
• Checking attendance/absence reasons for particular dates
16.The Personnel Calculation rule can be accessed through the transaction code
• Pe03
• Pe02
• Pe01
• Pe04
17. Which of the following is incorrect as regards the Time Management Pool?
• It is a tool for checking time data
• It is a tool for approving time data
• It is a tool for entering time data
• It is a tool for correcting time data

ABAP

ABAP is one of the many application-specific fourth-generation languages (4GLs) first developed in the 1980s. It was originally the report language for SAP R/2, a platform that enabled large corporations to build mainframe business applications for materials management and financial and management accounting.
ABAP used to be an abbreviation of Allgemeiner Berichtsaufbereitungsprozessor, the German meaning of "generic report preparation processor" , but was later renamed to Advanced Business Application Programming. ABAP was one of the first languages to include the concept of Logical Databases (LDBs), which provides a high level of abstraction from the basic database level(s).
The ABAP programming language was originally used by developers to develop the SAP R/3 platform. It was also intended to be used by SAP customers to enhance SAP applications – customers can develop custom reports and interfaces with ABAP programming. The language is fairly easy to learn for programmers but it is not a tool for direct use by non-programmers. Knowledge of relational database design and preferably also of object-oriented concepts is necessary to create ABAP programs.
ABAP remains the language for creating programs for the client-server R/3 system, which SAP first released in 1992. As computer hardware evolved through the 1990s, more and more of SAP's applications and systems were written in ABAP. By 2001, all but the most basic functions were written in ABAP. In 1999, SAP released an object-oriented extension to ABAP called ABAP Objects, along with R/3 release 4.6.
SAP's current development platform NetWeaver supports both ABAP and Java.

[edit]Where does the ABAP program run?
All ABAP programs reside inside the SAP database. They are not stored in separate external files like Java or C++ programs. In the database all ABAP code exists in two forms: source code, which can be viewed and edited with the ABAP Workbench tools, and generated code, a binary representation somewhat comparable with Java bytecode. ABAP programs execute under the control of the runtime system, which is part of the SAP kernel. The runtime system is responsible for processing ABAP statements, controlling the flow logic of screens and responding to events (such as a user clicking on a screen button); in this respect it can be seen as a Virtual Machine comparable with the Java VM. A key component of the ABAP runtime system is the Database Interface, which turns database-independent ABAP statements ("Open SQL") into statements understood by the underlying DBMS ("Native SQL"). The database interface handles all the communication with the relational database on behalf of ABAP programs; it also contains extra features such as buffering of tables and frequently accessed data in the local memory of the application server.
[edit]SAP Basis
The ABAP language environment, including the syntax checking, code generation and runtime system, is part of the SAP Basis component. SAP Basis is the technological platform that supports the entire range of SAP applications, now typically implemented in the framework of the SAP Web Application Server. In that sense SAP Basis can be seen as the virtual machine on which SAP applications run. Like any operating system, SAP Basis contains both low-level services (for example memory management, database communication or servicing Web requests) and high-level tools for end users and administrators. These tools can be executables ("SAP kernel") running directly on the underlying operating system, transactions developed in ABAP, or Web-based interfaces.
SAP Basis also provides a layer of abstraction between the business applications and the operating system and database. This ensures that applications do not depend directly upon a specific server or database platform and can easily be ported from one platform to another.
SAP Basis currently runs on UNIX (AIX, HP-UX, Solaris, Linux), Microsoft Windows, i5/OS on IBM System i (formerly iSeries, AS/400) and z/OS on IBM System z (formerly zSeries, S/390). Supported databases are IBM DB2, Informix, MaxDB, Oracle and Microsoft SQL Server (support for Informix was discontinued in SAP Basis release 7.00).
[edit]SAP systems and landscapes
All SAP data exists and all SAP software runs in the context of an SAP system. A system consists of a central relational database and one or more application servers ("instances") accessing the data and programs in this database. A SAP system contains at least one instance but may contain more, mostly for reasons of sizing and performance. In a system with multiple instances, load balancing mechanisms ensure that the load is spread evenly over the available application servers.
Installations of the Web Application Server (landscapes) typically consist of three systems: one for development, one for testing and quality assurance, and one for production. The landscape may contain more systems, e.g. separate systems for unit testing and pre-production testing, or it may contain fewer, e.g. only development and production, without separate QA; nevertheless three is the most common configuration. ABAP programs are created and undergo first testing in the development system. Afterwards they are distributed to the other systems in the landscape. These actions take place under control of the Change and Transport System (CTS), which is responsible for concurrency control (e.g. preventing two developers from changing the same code at the same time), version management and deployment of programs on the QA and production systems.
The Web Application Server consists of three layers: the database layer, the application layer and the presentation layer. These layers may run on the same or on different physical machines. The database layer contains the relational database and the database software. The application layer knowledge contains the instance or instances of the system. All application processes, including the business transactions and the ABAP development, run on the application layer. The presentation layer handles the interaction with users of the system. Online access to ABAP application servers can go via a proprietary graphical interface, which is called "SAP GUI", or via a Web browser.
[edit]Authentication into ABAP Systems
There are three common approaches for authentication into ABAP systems:
Usernames and passwords
SAP Logon Ticket
Secure Network Communications
Single Sign-On
[edit]Transactions

A transaction in SAP terminology is the execution of a program. The normal way of executing ABAP code in the SAP system is by entering a transaction code (for instance, VA01 is the transaction code for "Create Sales Order"). Transactions can be called via system-defined or user-specific, role-based menus. They can also be started by entering the transaction code directly into a command field, which is present in every SAP screen. Transactions can also be invoked programmatically by means of the ABAP statements CALL TRANSACTION and LEAVE TO TRANSACTION.
The term "transaction" must not be misunderstood here; in the context just described, a transaction simply means calling and executing an ABAP program. In application programming, "transaction" often refers to an indivisible operation on data, which is either committed as a whole or undone (rolled back) as a whole. This concept exists in SAP and is called as a LUW (Logical Unit of Work). In the course of one transaction (program execution), there can be different LUWs.
[edit]Types of ABAP programs

As in other programming languages, an ABAP program is either an executable unit or a library, which provides reusable code to other programs and is not independently executable.
ABAP distinguishes two types of executable programs:
Report
Module pools
Reports follow a relatively simple programming model whereby a user optionally enters a set of parameters (e.g. a selection over a subset of data) and the program then uses the input parameters to produce a report in the form of an interactive list. The term "report" can be somewhat misleading in that reports can also be designed to modify data; the reason why these programs are called reports is the "list-oriented" nature of the output they produce.
Module pools define more complex patterns of user interaction using a collection of screens. The term “screen” refers to the actual, physical image that the user sees. Each screen also has a “flow logic”, which refers to the ABAP code implicitly invoked by the screens. Each screen has its own flow logic, which is divided into a "PBO" (Process Before Output) and "PAI" (Process After Input) section. In SAP documentation the term “dynpro” (dynamic program) refers to the combination of the screen and its flow logic.
The non-executable program types are:
INCLUDE modules
Subroutine pools
Function groups
Object classes
Interfaces
Type pools
An INCLUDE module gets included at generation time into the calling unit; it is often used to subdivide very large programs. Subroutine pools contain ABAP subroutines (blocks of code enclosed by FORM/ENDFORM statements and invoked with PERFORM). Function groups are libraries of self-contained function modules (enclosed by FUNCTION/ENDFUNCTION and invoked with CALL FUNCTION). Object classes and interfaces are similar to Java classes and interfaces; the first define a set of methods and attributes, the second contain "empty" method definitions, for which any class implementing the interface must provide explicit code. Type pools define collections of data types and constants.
[edit]ABAP Workbench

The ABAP Workbench contains different tools for editing programs. The most important of these are (transaction codes are shown in parentheses):
ABAP Editor for writing and editing reports, module pools, includes and subroutine pools (SE38)
ABAP Dictionary for processing database table definitions and retrieving global types (SE11)
Menu Painter for designing the user interface (menu bar, standard toolbar, application toolbar, function key assignment) (SE41)
Screen Painter for designing screens and flow logic (SE51)
Function Builder for function modules (SE37)
Class Builder for ABAP Objects classes and interfaces (SE24)
The ABAP Workbench (transaction SE80) provides a single integrated interface into these various tools.
[edit]ABAP Dictionary

The ABAP Dictionary contains all metadata about the data in the SAP system. It is closely linked with the ABAP Workbench in that any reference to data (e.g. a table, view, data type, etc.) will be obtained from the dictionary. Developers use the ABAP Dictionary transactions (directly or through the SE80 ABAP Workbench) to display and maintain this metadata.
When a dictionary object is changed, a program that references the changed object will automatically reference the new version the next time the program runs. Because ABAP is interpreted, it is not necessary to recompile programs that reference changed dictionary objects.
A brief description of the most important types of dictionary objects follows:
Tables are data containers that exist in the underlying relational database. In the majority of cases there is a 1-to-1 relationship between the definition of a table in the ABAP Dictionary and the definition of that same table in the database (same name, same columns). These tables are known as "transparent". There are two types of non-transparent tables: "pooled" tables exist as independent entities in the ABAP Dictionary but they are grouped together in large physical tables ("pools") at the database level. Pooled tables are often small tables holding for example configuration data. "Clustered" tables are physically grouped in "clusters" based on their primary keys; for instance, assume that a clustered table H contains "header" data about sales invoices, whereas another clustered table D holds the invoice line items. Each row of H would then be physically grouped with the related rows from D inside a "cluster table" in the database. This type of clustering, which is designed to improve performance, also exists as native functionality in some, though not all, relational database systems.
Indexes provide accelerated access to table data for often used selection conditions. Every SAP table has a "primary index", which is created implicitly along with the table and is used to enforce primary key uniqueness. Additional indexes (unique or non-unique) may be defined; these are called "secondary indexes".
Views have the same purpose as in the underlying database: they define subsets of columns (and/or rows) from one or - using a join condition - several tables.
Structures are complex data types consisting of multiple fields (comparable to struct in C/C++).
Data elements provide the semantic content for a table or structure field. For example, dozens of tables and structures might contain a field giving the price (of a finished product, raw material, resource, ...). All these fields could have the same data element "PRICE".
Domains define the structural characteristics of a data element. For example, the data element PRICE could have an assigned domain that defines the price as a numeric field with two decimals. Domains can also carry semantic content in providing a list of possible values. For example, a domain "BOOLEAN" could define a field of type "character" with length 1 and case-insensitive, but would also restrict the possible values to "T" (true) or "F" (false).
Search helps (successors to the now obsolete "matchcodes") provide advanced search strategies when a user wants to see the possible values for a data field. The ABAP runtime provides implicit assistance (by listing all values for the field, e.g. all existing customer numbers) but search helps can be used to refine this functionality, e.g. by providing customer searches by geographical location, credit rating, etc.
Lock objects implement application-level locking when changing data.
[edit]ABAP syntax

This brief description of the ABAP syntax begins inevitably with the ubiquitous "Hello World" program.
[edit]"Helloworld"
REPORT TEST.
WRITE 'Hello World'.
This example contains two statements: REPORT and WRITE. The program displays a list on the screen. In this case, the list consists of the single line "Hello World". The REPORT statement indicates that this program is a report. An alternative statement, PROGRAM, would be used for a module pool.
[edit]Formatting rules
The basic formatting rules of ABAP are simple:
Every ABAP statement must end in a period
Tokens within a statement must be separated by at least one space
An end of line is equivalent to a space
Statements and keywords are not case-sensitive
The "Hello World" program could be legally rewritten as follows:
REPORT tESt. WRITE
'Hello World' .
To ensure that code is readable, the ABAP editor provides a "Pretty Printer" function, which takes care of proper indentation. The Pretty Printer also offers a choice between several models of case standardization (all upper case, all lower case, upper case for statements/keywords, upper case for variable names).
If a text literal in an ABAP statement extends across more than one line, then a ‘&’ character must be used to combine a succession of text literals into a single one. Example:
USERPROMPT = 'Please double-click on a line in the output list ' &
'to see the complete details of the transaction.'.
The rule that tokens must be separated by at least one space extends even to operators, parentheses and other symbols. For example the following code is incorrect:
X=(A+B)-(C+1).
The variable names (X, A, B, C), the numeric constant 1, the operators "=", "+" and "-" and the parentheses must all be white-space delimited. The correct code is:
X = ( A + B ) - ( C + 1 ).
[edit]Chained statements
Consecutive statements with an identical first (leftmost) part can be combined into a "chained" statement using the chain operator ":" (colon). The common part of the statements is written to the left of the colon, the differing parts are written to the right of the colon and separated by commas. The colon operator is attached directly to the preceding token, without a space (the same applies to the commas in the token list on the right, as can be seen in the examples below).
Chaining is very often used in WRITE statements. WRITE accepts just one argument, so if for instance you wanted to display three fields from a structure called FLIGHTINFO, you would have to code:
WRITE FLIGHTINFO-CITYFROM.
WRITE FLIGHTINFO-CITYTO.
WRITE FLIGHTINFO-AIRPTO.
Chaining the statements results in a more readable and more intuitive form:
WRITE: FLIGHTINFO-CITYFROM, FLIGHTINFO-CITYTO, FLIGHTINFO-AIRPTO.
In a chain statement, the first part (before the colon) is not limited to the statement name alone. The entire common part of the consecutive statements can be placed before the colon. Example:
REPLACE 'A' WITH 'B' INTO LASTNAME.
REPLACE 'A' WITH 'B' INTO FIRSTNAME.
REPLACE 'A' WITH 'B' INTO CITYNAME.
could be rewritten in chained form as:
REPLACE 'A' WITH 'B' INTO: LASTNAME, FIRSTNAME, CITYNAME.
[edit]Comments
ABAP has 2 ways of defining text as a comment:
An asterisk (*) in the leftmost column of a line makes the entire line a comment
A double quotation mark (") anywhere on a line makes the rest of that line a comment
Example:
***************************************
** Program: BOOKINGS **
** Author: Joe Byte, 07-Jul-2007 **
***************************************

REPORT BOOKINGS.

* Read flight bookings from the database
SELECT * FROM FLIGHTINFO
WHERE CLASS = 'Y' "Y = economy
OR CLASS = 'C'. "C = business
(...)