SAP FICO Issue-8

Issue No.: 8
The client processed a bank statement and one of the line items in the bank statement overview in transaction
FEBA shows the status as "Complete." However, the client used a wrong posting rule here. How can you change to the correct posting rule and process the transaction again so that the status is changed to "Posted"

There are two ways to handle this situation:

•  With a reverse bank reconciliation posting document.
• By deleting the bank statement from the SAP R/3 system. To delete the bank statement, follow these steps:

1. In T-code SM38, enter RFEBKA95 and execute the program. It will open the posted bank statement.

2. Deselect all and select the statement that is wrongly posted to delete it.
3. Repost the bank statement through T-code FF67.

SAP FICO Issue-7

Issue No.: 7
While creating G/L accounts, some of the G/L accounts were wrongly kept as open item management. Now the
user wants to remove open item management functionality through transaction code FS02, but the system is giving the following error message: "This account does not balance to zero."


System Response:
You cannot switch the open item management specification on or off with this transaction.

Procedure:
If you want to switch this function on retroactively for a certain account, you should create a new account with
the correct setting and use this to make a transfer posting of existing items.

While creating the G/L master, you have to pay utmost attention to the setting of G/L master attributes. The situation here
is changing the attribute of G/L accounts after posting the transaction. For this, you have two options:

 Standard solution:
1. Create a new G/L account.
2. Transfer the account balance from the old G/L account to the new G/L account.
3. Switch off open item management for the old account and retransfer the G/L balance from the new account to the old account.

Without making the account balance zero, you can't switch an open item attribute of a G/L account.

Consulting solution:
As an alternative, the user could try program RFSEPA03, depending on his SAP release. The user may have to copy the program to the "Z" program and remove the piece of code that prevents its use. Before adopting this procedure,make sure the user reads the program documentation and related SAP advice.

SAP FICO Issue-6

Issue No.: 6
There are a few G/L accounts where line item displays are not activated. The client would like to see what
entries are actually hitting these accounts. 

There are two possible solutions regarding this problem. SAP recommends the first solution because only standard means are used. The second solution requires the usage of a correction report and is therefore a consulting solution.

Standard solution:
1. Create a new account and set the options according to your requirements. Be sure to set the line item display indicator (SKB1-XKRES).
2. Transfer the items from the old account to the new account. You can only do this for accounts that you cannot automatically post to. As an alternative, you can transfer the balance completely.
3. Lock the old account for postings.
Consulting solution:
1. Manipulate all documents that were posted in the past. You can use the correction program RFSEPA01
(contained in the standard system as of release 3.0D). Read the document carefully.
2. For releases prior to 3.0D, a corresponding correction program is available on SAPSERV3.
While creating the G/L account, utmost care should be taken with the open item management and line item management attributes of the G/L account.

SAP FICO Issue-5

Issue No.: 5

The user wants to add a trading partner as selection criteria in the F-03 screen. This does not come with the
standard screen.

You are using transaction code F-03 to clear open items for a particular G/L account. While offsetting debit transactions with credits, depending upon business requirements, the user will select one of the selection options provided in that screen. The SAP R/3 system will pull all open items based on the selection criteria. The standard SAP R/3 system comes with very limited selection criteria; however, you can include a new selection field and change the sequence of the selection criteria. To add a new selection field or change the selection criteria sequence, you have to configure the SAP R/3 system through transaction code O7F1.

SAP FICO Issue-4

Issue : 4
How can you add a new column in an open item clearing transaction with T-code F-03? Right now you have a document number, document date, document type, posting key, and amount. You need to add a posting key and amount in the transaction fields in the screen.

1. Go to the Clearing G/L Account Process Open Item screen using T-code F-03 from the menu bar.
2. Select --Settings and Change line layout
3. Select the Create button.
4. Give the line layout a name and description, and press Enter
5. Select the Insert after button to view the available fields.
6. Select the required field by double-clicking on that field. The required field is automatically listed under your own layout.
7. Repeat the process for each field required to create your layout and save.
8. Go back to the Clearing G/L Account Process Open Item screen, and select the Editing option button under the line layout variant for the G/L account clearing transaction.
9. Give your variant a name and save.

SAP FICO Issue-3

Issue No.: 3
My client raised a PO at USD 13 for 50 qty. A goods receipt MIGO transaction was done at that price. Now my client wants to do a MIRO transaction at USD 14 for 50 qty.
 
This situation can be handled in two different ways: (1) price difference or (2) reversing MIGO and repost MIGO with correct price.

1. At the time of the MIRO transaction, you have an option to post a price difference. In the MIRO transaction, enter the G/L account for price difference and amount (i.e., $1).

2. Reverse the MIGO entry, make changes in the PO, then once again do the MIGO and MIRO transactions.

SAP FICO Issue-2

GENERAL LEDGER (G/L) ACCOUNTING
Issue No.: 2
The user is not getting the drop-down list of G/L accounts that he defined through FS00 while posting through transaction code FB50/F-02.
While entering a transaction, the user usually presses F4 to select a G/L account from the chart of account (COA). The SAP R/3 system displays all available accounts that are created for the desired company code and COA in question. If the user is not getting the G/L account in the drop-down list, try one of the following:

1. Check if the G/L accounts have been created in the company code you are posting.
2. Make sure you have selected the correct company code in T-code FB50.
3. The drop-down has a personal list and a global list. If you are in the personal list, switch to the global list.

SAP FICO Issue-1

Issue No.: 1
The user is trying to create a vendor for a particular company code. In the initial screen for the customer, the company code was set to the default and the user is trying to create another company code. 

 

For rapid data entry, some important parameters such as company code and controlling area are set as the default while setting the user profile. If the security role allows, the user can reset or define his own parameters through transaction code SU01. In transaction code SU01, you will find a Parameter tab; this is where you make all default settings. Check the default value for parameter ID BUK. If you don't want any default values, remove them.

SAP FICO Issues Overview

Issues and Resolutions

OVERVIEW

A ticket is a generic name for claims made by the end user to technical support. At the very least, the end user has to send

an email with a description of the issue, the transaction code, and the program or report name. There are some

applications available to manage these jobs, such as Quality Center from HP, ClarifyCRM , and Manage Now , among

others. The tickets usually have a priority scale: T1 (meaning the issue must be handled the same day, T2, T3, etc. The

person in charge of each module for analysis and resolution handles those tickets. If it involves configuration, when you

have missing e.g. cost center, currency or customized reports discrepancy or for third part as ABAP developers for debug

or include functionality. Depending on the nature of the ticket and resolution, necessary code changes will be done in the

development server. Once the SAP team is satisfied with unit testing, changes will be promoted to the quality environment

for user testing acceptance. Once changes are approved by the user, the SAP team deploys the changes in the production

environment.

This chapter presents issues that may arise while using SAP solutions and discusses ways to resolve those issues.

SAP BI ABAP Course content

1	Introduction to SAP	Introduction to BI ABAP Overview of  BI ABAP
2	ABAP Data Types	Character Integer Numeric Character Floating Point Packed Decimals Time Date, Strings
3	Loops & Branches	Do, Do n times, While If, If Else, if Ladder, Case Small Programs Factorial program Indentation Code Inspector Extended Program Check Debugging
4	Structures & Internal Tables	Over View of Structures Similar Structures creation Different Structures Different structures with Extra Fields Over View of Internal Tables Similar Internal tables creation Different Internal tables Different Internal tables with Extra Fields Modify Operation on Internal Table Delete Operation on Internal Tables Sorting Of internal tables ( Sort) Searching Techniques Of internal Table
5	Landscape & SAP R/3 Architecture	Landscape Model Overview of R/3
6	Normalization & Select Statements	Over view of Normalization Select Statements Logical operators Select Single & Up to 1 rows Nested Select queries For all Entries Join Statements Inner join & Left Outer Join
7	Modularization Techniques	Over view of Modularization Macros Includes Subroutines Function Modules Extraction Using function modules
8	Selection Screen Design	Over View of Selection Screen Selection Screen elements Message Class How to upload files from front end  How to upload files from app server
9	Data Dictionary	Creation of Data Base Table Creation of Domains Creation of Data types Creation of Views Creation of Structures Creation of Type pools Creation of Search Help Creation of Lock objects Creation of table maintenance
10		User Exists Over view  Data Source enhancement Bex query exits
	Cross Applications
11	RFC	Over view of CA Creation of RFC Fetching Data Using RFC ARFC & TRFC
12	ALE/IDOCS	Over view of ALE/ IDOcs Creation of RFC Destinations Creation of Ports Creation of  Partner Profile Creation of Distributed sys  Transfer the data Btw sys
13	Routines	Start routine End Routine Expert routine Field Routine
14	Performance Tuning