Hello viewers

Welcome to our SAP FICO Q&A Blog

This blog is meant to be a forum for SAP FICO Professionals all over the world to share knowledge and experience, as well as to provide timely suggestions and solutions for the work related issues.

Please provide your valuable suggestions to improve this Blog.

Website counter

Search This Blog for SAP Solutions

Sunday, March 27, 2011

OB52 month end closing issue authorisation group issue

Dear viewers, I had some issues in closing the year earlier this year. I thought it is a good idea to share. In OB52 screen, there are 9 fields after the accounts. PROBLEM1: There were many access issues for many period end transactions all over the company. RESOLUTION: I found out that someone who has access to OB52 had introduced Authorization group 01 for acct type "S", which restricted the access of all the transactions. I made this field(Authorization group) blank as there are only two people who has access to OB52 in the whole company. I found that there is no reason to maintain this field. This field is to be maintained only if you want to segregate the authorization according to "account types". Basis team has to maintain authorization groups assignment in the background. PROBLEM 2: Even after closing the previous period, since the Second period from and to are opened from couple of years back, any user can post in the previous periods. One user posted a journal it in the previous year because of this scenario. Resolution: Second period(from and to) were made restricted to 13 and 16th period of previous year for special period postings only. After few days, business came to me and asked to leave the second (from and to) periods blank. I explained them saying that the first (from and to) periods can be the only one that can be maintained but it is recommended as a best practice to maintain the second(from and to) period as 13 to 16 of previous period.

EXCHANGE RATE TYPE in SAP in OB08 (Foreign currency revaluation issue)

Dear Viewers, Problem: I recently added company codes for swizz, Germany and others. I had to define the exchange rate types in OB08(directly in QAS as this is non transportable), I got a green message saying that "You dont have maintainance authorization" SOLUTION: In order to have exchange rate type to be saved, we have to define the translation ratios in the following config: SPRO-->SAP NETWEAVER-->gen settings-->currencies-->define translation ratio. I defined 1:1 in my case and it worked.

Change in Actual Cost center in Statistical internal order

Dear viewers I got a request from the business asking me to change the Actual cost center field in one of the statistical internal order. I know that the change in the actual cost center field is not recommended. This field will be greyed once you use the internal order on purpose by SAP to avoid the inconsistencies in the internal order postings. Solution: Inorder to change that field in the internal order, we have to implement SAP note: 198036.

R-Block issue in service based POs

Murthy Garu, I would like to share one of the issues I had last week. Problem: In our configuration, tolerance keys PP and PE were defined as 5% or 250% as both the limits. But when we create a SERVICE PO for 1000qty and $1 each, the invoice was not allowing to pay even $1001(not accepting even $1 tolerance also). It was shooting an R-BLOCK in the invoice posting. SOLUTION: In a service based PO, Material field is blank and GR/IR is unchecked in the line item level. In order to resolve this issue, I had put a check mark on Estimated price in the control condition tab in the line item level. If we just check this field(Estimate price), the PO is not going to look at the tolerance keys PP and PE. We have to define PS tolerance key(transaction code OMR6), as the service PO is going to look at PS since we checked Estimated price. Note: PE is defined in the following config: SPRO-->MM-->Purchasing-->Purchase order-->Set tolerance limits for price variance