The highest entity in the FI
organization is Company, followed by Company Code. Company represents an entity
that consists of one or more Company Codes below
it. Company Code represents the smallest entity for which you are preparing a
financial statement of account for external reporting purposes.The important
organizational structure of controlling includes:
Operating concern the top-most reporting level for
profitability analysis and sales and marketing controlling).
Controlling area central
organization in ‘controlling,’ structuring internal accounting operations).
Cost
Centers (lower-most organizational units where costs are incurred and
transferred).
The
major Organizational Elements of MM include:
Purchasing
Organization
Plant
Storage
Location
The important Organizational
Elements in SAP Sales & Distribution include:
Sales
organization
Distribution
channel
Division
Sales
area
Sales
group
Sales
person
Company Code is a legal
entity for which financial statements like Profit and Loss and Balance Sheets
are generated. Plants are assigned to the company code, Purchasing organization
is assigned to the company code, and Sales organization is assigned to the
company code.
Ans)friends this is a very tricky
question to identify particular person is real experienced or fake. Most of the
fake guys will think of transaction codes. Generally companies will use
importing tools like LSMW, BDC & BAPI. In BDC we will provide field
specifications to abapers and they will
create Z transaction
code for it.
Z transaction code : are
user defined transaction codes starting with 'Z'.
Ans)For Currency their are two case
are there:
Case I :-
if CoCode =
Coarea then Currency of Cocode is equal to Controlling Area.
Case II :-
If Company Code is not Equl to
Coarea then it is called as cross company code. in this
case u can assign one or more
currency .
Coarea currency may be
different than in cocode currency
At the time of Maintain
controling area we give company code currencey 10
Inthe currency field we
give 10 all basic setting comes automatically
Both are the same
In the maintain
controlling area we shoulg be give the
company code currency
Tax codes can be defined
at country level not client level
Ans)Customers with whom
you transact business have to pay their dues eventually. Generally the due date
on which the customers have to settle the dues is stipulated in the terms of
payment agreed into with them.
Now one of the three
logical events can happen:
1) Customers pay on the
due date specified:
They pay the entire
value of money for which you have supplied materials and / rendered services.
Not a bad situation at all..... you can meet your financial commitments as
planned since you have received prompt
payment ....
2) Customers pay ahead
of the due date specified:
This is a better situation for you..... Your
money comes ahead of your original plan and you can be safe about meeting your
financial commitments as
planned ......Therefore,
You waive off a small part of the dues owed by your customers since your
working capital is not hampered.
3)What a mess things are
in this business world !. You had promised money to your creditors assuming
that your customers would pay promptly and that is not happening.
This is a Domino effect
commencing with your customers which you are forced to pass on to your
vendors..... That is not one bit good !!!!. You must do something to prevent
recurrence of such an uncomfortable situation !
What are the corrective
measures which you intend to take?
SAP calls it as DUNNING.
As a first step, you
need to identify which of your customers have not paid their dues promptly .
You need to remind each one of such customers about the non-payment and insist
that the dues are settled immediately. This is done through letter
correspondences ( indicating break up of dues owed by the customers). Some deaf
customers who do not heed your letters need to be reminded often ( that is
periodically , each time the letter sounding a little sterner than the earlier
one.
The second optional step
would be to levy penal charges for the defaulted payment in the following
manner:
1. Levy of interest for
nonpayment / belated payment
2. Levy of incidental
charges incurred with regard to dunning ( the process of dunning is going to cost
you by way of follow up,dunning and printing costs, maintenance of additonal
records,additional labor incurred by way of wages to dunning clerks etc...)
Customers who are tone
deaf even after repeated reminders would be handled through a legal process.
This is the process of
dunning.
Generally, each time you
dun a customer you are crossing one level of dunning. Though you can dun upto a
maximum of nine times , you would normally resort to legal help after dunning
three or four times, at the most. The number of dunning levels you need can be
configured and theoretically it ranges from 0 to 9 levels ( 0 if your company
is run by an inefficient management which does not bother to collect money on
time and 9 if your management is too
liberal with your customers !).
FI MM settings are
maintained in transaction code OBYC. Within these there are various
transaction keys to be maintained like BSX, WRX, GBB, PRD etc. In each of
these transaction keys you specify the GL accounts which gets
automatically passed at the time of entry.
Few examples could be:
BSX- Stands for Inventory Posting Debit
GBB-Standsfor Goods
Issue/Scrapping/delivery of goods etc
PRD- Stands for Price
Differences
FI-MM Integration is based on the following:
Movement
Types
Valuation
Class
Transaction
Keys
Material
Type
The Movement Type is the ‘classification key’
indicating the type of material movement (for example, goods receipt, goods
issue, physical stock transfer). The movement type enables the system to find
pre-defined posting rules determining how the accounts in FI (stock and
consumption accounts) are to be posted and how the stock fields in the material
master record are to be updated.
The Valuation Class refers to the assignment of a
material to a group of GL accounts. Along with other factors, the valuation
class determines the GL accounts that are updated as a result of a
valuation-relevant transaction or event, such as a goods movement. The
valuation class makes it possible to:
Post the
stock values of materials of the same material type
to different GL accounts.
Post the
stock values of materials of different material types to
the same GL account.
The Transaction Key (also known as the ‘Event Key or Process Key’) allows users to
differentiate between various transactions and events (such as physical inventory
transactions and goods movements) that occur within the area of inventory
management. The transaction/event type controls the filing/storage of documents
and the assignment of document numbers.
The Material Type groups together materials with the
same basic attributes, for example, raw materials, semi-finished products, or
finished products. When creating a material master record, you must assign the
material to a material type. The material type determines:
Whether
the material is intended for a specific purpose, for example, as a Configurable
Material or Process Material.
Whether
the material number can be assigned internally or externally.
The Number Range from
which the material number is drawn.
Which
screens appear and in what sequence.
Which
user department data you may enter.
What
Procurement Type the material has; that is, whether it is manufactured in-house
or procured externally, or both.
Together with the plant, the material type determines the material’s inventory management requirement, that is:
Together with the plant, the material type determines the material’s inventory management requirement, that is:
Whether
changes in quantity are updated in the material master record.
Whether changes in value
are also updated in the stock accounts in financial accounting.
FI-SD Integration
The FI-SD account
determination happens through an access sequence. The system goes about
finding accounts from more specific criteria to less specific criteria.
This is the sequence it
would follow:
1) It will first access
and look for the combination of Customer accounts assignment grp/ Material
account assignment grp/Account key.
2) If it does not find the
accounts for the first combination it will look for Customer account assignment
grp and account key combination.
3) Furthermore, if it does
not find accounts for the first 2 criteria’s then it will look for
Material account assignment grp/Account key.
4) If it does not find
accounts for the all earlier criteria’s then finally it will look for Account
key and assign the GL code.
Thus posting of Sales
Invoices into FI are effected on the basis of a combination of Sales
organization, Account type, or Customer and Material Account assignment groups
and following are the options available.
a. Customer AAG/Material
AAG/Account type
b. Material AAG/Account
type
c. Customer AAG/Account
type
For each of this option
you can define a Gl account. Thus the system
uses this gl account to
automatically pass the entries.
A)There is no hard and
fast rules on the tools. Generally RPM(Rational Portfolio
Manager)/Solution Manager/Ascendent(IBM tool) will be used in
Implementation. Support tools are so many. In my project for
incidents we use Impact(IBM Tool). Some other projects using
perigreen/clarify etc.,
A)
ECC=ERP Central Component
Differences:
New GL Concept
PCA comes under New GL
Real time Integration with
New Gl
Tickets
Handling tickets is called
Issue Tracking system. The errors or bugs forwarded by the end user to the
support team are prioritized under three seviority High, Medium and Low. Each and
every seviority as got its time limits before that we have to fix the error.
The main job of the supporting
consultant is to provide assistance on line to the customer or the organisation
where SAP is already implemented for which the person should be very strong in
the subject and the process which are
implemented in SAP at the
client side to understand,to analyse,to actuate and to give the right solution
in right time.This is the job of the support consultant.
The issues or the
tickets(problems) which are arised is taken care of on priority basis by the
support team consultants.
The work process in support
projects are given below for your reference.
1. The customer or the end
user logs a call through any tool or by mail (RADIX). (please see the below
Question)
2. Each one of the support
team is a part of support group.
3. Whenever a customer
logs a call he /she has to mention to which work group (by name).
4. Once the calls came to
the work group the support consultant or the team need to send an IR (Initial
Response) to the user depending upon the priority of the calls.
(Top,High,Med,Low,None)
5. Then the error is
fixed, debugged by the support consultant or the team. Then after testing
properly by generating TR(Transport Request through the basis admin)
6. Then it is
informed to the end user/customer/super user about the changes which have moved
to the production server by CTS process.
These are the
process. In summary, what I understand is that if any configuration or
customization is required to solve the issue, then the consultant have to work
on DEV Client, then the end user will test it in the QA client and after
approval the BASIS consultant has to transport it to
the PRODUCTION client.
An example:
Tickets in SD can be
considered as the problems which the end user or the employee in the company
face while working on R/3. Tickets usually occur during the
implementation or after theimplementation of the project. There can be numerous
problem which can occur in the production support and a person who is working
in the support has to resolve those tickets in the limited duration, every
ticket has the particular deadline alert so your responsibility is to finish it
before that deadline. To begin with , we should give "TICKET" to you
for not knowing it.
Here is an eg of a ticket
raised:
End user is not able
to
1. Create Sales order for
a customer from a New plant, since shipping point determination is not happened
. (Without Shipping point the document becomes INCOMPLETE and he will not be
able to proceed further like DELIVERY,
BILLING).
He raises a ticket and the
priority is set in one of the below:
1. Low 2.
Medium 3. High.
Now you need to solve this
ticket. You would analyze the problem and identify that the SD configuration
has to be done for the new plant. You would request a transport for DEV CLIENT
to BASIS. You do the change and Request one more Transport to BASIS for QA client.
The End user will test the same by creating a sales order for the new plant and
approve it. Finally, you request a transport to move the changes to PRODUCTION.
Once the change is deployed in production the TICKET is closed. What I
have given is a small example. You
would get some real issues
with severity HIGH in your day-day support
No comments:
Post a Comment