Few SAP Tickets:

FI/CO Cost centre 5010 does not exist on 31.03.2015

From the cost center standard hierarchy it appears that 5010 and 5020 are only
cost center groups below which cost centers are attached.. if these are groups,
you cannot assign them as cost objects.. try giving one of the cost centers
assigned to the cost center
group 5010 and 5020.. Regarding Date, change the date of cost centre creation-
as-31.03.9999

Tax statement item missing for tax code S1 - error message when releasing bill
doc to FI

Make sure you have the “rate maintained” in the tax code at the lowest level of
the tax jurisdiction.

" Posting only possible in periods 2015/02 and 2015/01 in company code XXXX".

Error is related to the MM posting periods (transaction MMPV (to close period) &
MMPI (to open period) and not the FI posting period (transaction OB52).

Go to /NOX18, delete Co. Code assigned to Plant & Save.

Now go to /NOMSY, change posting period and save.

Go to /NOX18, reassign co .code to plant and sve.

F110 error log " In Table T030R, the entry FI04 SKE is missing"

We need to assign a GL account (Cash Discount Received A/c) via transaction

code: OBXU.

SAP Transaction SKE is for cash discount received.

GL Account created in FI and used but in error cost element did not exist in
CO thus causing FI and CO not in Balance.

Reverse the G/L posting, create the cost element, repost the transaction.

While executing F-92, I am getting an Error:

> Auxiliary account assignment to asset not possible, please remove entry

in the account determination for FI-AA.

Go to TCode AO90 and check the accounts set up for retirement postings. One of
them is causing your problem.

Account XXXXXX requires an assignment to a CO object"

This normally means that SAP is trying to make a posting to a G/L account which
has a corresponding cost element in CO and which requires some kind of CO
object assignment. Without further information, the most likely explanation is
that you need to enter a cost center into your posting.

In [MB1C] new stock creation- error- "period 008/2015 is not open for Account
type S and G/L 799999" How to correct this error?

Error is related to the MM posting periods (transaction MMPV & MMPI)

While posting my material (FERT) into Stock via MB1C, I am getting serious
error," Field selection for movement type 561/acct 233000 differ for Ext. GA
amount in LC)(023).

pl check the field status of movt type 561 and GL Account . (SE38, RM07CUFA)
Both should be alike. Any field selection variation would lead to this kind of error.
When we try to make entries in General Ledger using " Enter G/L Account
Document", am unable to save the doc, the message appears "Company code
not assigned to country or country to calculation procedure" having Message
no. FF703.

Messages beginning with FF have to do with FI Tax Check. It sounds like you don't
have the company code assigned to a tax procedure. Try transaction OBBG. You
probably need to make other tax settings so you should check out the menu
Financial accounting>Financial Accounting Global Settings>Taxes on
Sales/Purchases in the IMG.

When I do an FB01 entry for 04/30/2015 I get the following error:

"Posting in prior month 04/30/2014 exceeds your maximum allowance".

Review settings under transaction code OBA4 - FI Tolerance Groups for Users".
There appears to be some security control placed on users by management. Users
can be assigned to "tolerance groups" and within those, posting limits can be set
for maximum posting by line item and document total for a particular company
code (and even by currency within a company code).

How can I get the SAP ECC 6.0 system to generate an error message at the time
of creating a purchase order that a G/L account has been flagged for deletion....
(G/L XXXXXX can not be used here).

That particular Ledger has been marked for deletion and not yet deleted. Better
ask your ERP In-charge to block the ledger.
I am posting GL Acc. 4161000(Utility Expense) with FB50. The error occurred "An
entry in field Cost center is not permitted for account 4161000".

Check the field status group for the account. (Change FSG to G004)

While Using Tcode F-48, when i fulfill the first screen of the transaction, say
date, vendor a/c, spl Gl, bank a/c, amt, Profit center enter.. till the first screen
input it accepts properly but when for the second screen (DP made pstg key
29,A) after putting the Amount and click on the Document overview or aftr
entering.... I'm getting-“ABAP Runtime-Error.”
What could be the possible reason to get such DUMP error?
Earlier it was working properly... what changes in the customization or any
changes in the ABAP programming made to get this Output.
Do we have any workaround to resolve the F-48 Problem... I tried F-02 same
error.

The short answer is you have not given enough information. You need to go to
TCode ST22 and look at the dump analysis. This will tell you what went wrong
with the program and where. You can copy and paste the relevant bits of the
dump analysis here. Better still, go through the analysis with your ABAPer. He can
run the program in debug mode and find out where it falls over and why.

I have created one asset class 1001 for land and 3001 for Vehicles by myself.
(i.e.without-reference)
I have filled all account determination, screen layout, etc.
When i create asset master record for LAND, i enter asset class 1001 (for-land)-
&-it-accepts.
But when i create asset master record for Vehicle, i enter asset class 3001(for-
vehicle).But-it-throws-error.
”Chart of depreciation SEL that was determined is not entered for asset-class-
3001.” How to rectify the problem ?

Go to OAYZ and activate that asset class in that chart of depreciation.

TYPES OF ISSUES AT SUPPORT LEVEL:

L1- Help desk support (need to solve within 2 hours. Basic issues)

L2- Technical support (Solve within 4 hours. To solve this type of issues u need to
take help of ABAP or BASIS Consultant)

L3- Configuration changes or customization ( need 8 hours to solve. Handled by

senior consultants)

L4- SAP AG ( In SAP Software, some standard settings are missing. Will b taken
care by SAP AG.)

Timings to solve issue, depends on Service Level Agreement.

Levels of support are:

1st Level - At the user's location. Involves helping users in basic issues like "How
to" and resolving basic errors.

2nd Level - May be at the user's location or a nearby location. Used to resolve
issues that 1st level cannot resolve. Does not involve config changes
3rd Level - Usually remote or a central location / locations. Involves config
changes and programming.

SAP Support - Usually involves problems in standard programs which require SAP
program changes. Should be done only by SAP AG.

Medium Issues: (Integration)

1. Billing Document not released to accounting / Accounts
determination:
To resolve the error, you can analyze account determination
in the billing document. Process:
Goto T.Code: VF02 & Enter Invoice number
Next (On the top most strip) goto Environment
Next (Select Environment) go to Account determination
Next (In Account Determination) select Revenue Account
Determination (first option)

This will list all the condition types in the Billing

document & analyze each condition & check for which G/L
accounts is not determined.

Possible errors:
VKOA not maintained for required combination
Solution: Maintain the combination in VKOA.

2. Account Key not maintained in Pricing Procedure:

Impact: This may create accounting document, but if
condition type, which are to be posted to account, but do
not have account key maintained in pricing procedure, it
will not be post the relevant condition type to G/L account.

High Priority Issues:

a. Show stopper -- High priority 
The user(s) just not able to do anything at all on the 
system. Technical is GUI not responding. Functional Tcodes 
or navigation
 01.End user still not clear on the usage/ functionality of
SAP T.Codes,

02.Or Could not know how to rectify or correct if any wrong

process is followed

03. or Not clear how the calculations are getting done in SAP.

04.Purely system issues, which require some OSS notes to be

applied or BASIS team needs look into it.

05. Or the Customizing is wrong, may be all the scenarios

are not perceived at the time of Blue print.
etc.. etc..

Examples:

If the currency is the same. There are no delivery costs. Can the GR/IR value
derived from the PO. In PO there are no changes and the price is 1.

Can we by any chance change the value in GR manually?

Answer:

Uncheck GR based invoice Verification in PO.

Do the MIGO and MIRO.

Below few more issues with solutions to enrich your

knowledge in Handling Issues for your reference: