What is SAP
SAP stands for “System, Applications and Products in Data Processing”. It
is the largest business software company
in the world and also 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 Business Objects software. SAP software has three-tier application architecture: database, application server and client SAP GUI (presentation layer).As per the reports there are over 100,600 SAP installations at more than 41,200 companies in more than 120 countries /3 architecture was replaced with the introduction of ERP Central Component (ECC ).
SAP‟s Business Suite contains
five enterprise applications.
SAP ERP Customer Relationship Management (CRM)
Product Life-cycle Management (PLM)
Supply Chain Management (SCM)
Supplier Relationship Management (SRM).
SAP SD ( Sales and Distribution ) is one the largest functional Module in SAP. It handles all the processes from an Order to delivery. The main operations, this module handles are Customer Sales Orders processing , pricing, Picking, packing , Shipping, billing and risk management etc.
Various Modules in SAP ERP
SAP APO module – Advanced Planner Optimizer
Any organization success is depended
on 4m‟s. They are Machinery, Material, Man Poour,
Money These M‟s are well maintained and coordinated using an ERP
Reasons for preferring only SAP in the companies:-
1) SAP Gives solution
to all departments in enterprise
to gain success.
2)
Tightly integrated product.
(Means if we update something in one department i.e. Mfg. It automatically reflects in relevant departments. No need
to inform other departments.)
3) Data Security.
Future of SAP:-
Most of the Mfg Company‟s around the world already implemented SAP, Career in sap for Next 40- 50 yrs is Brilliant.
SAP will do
continuous process of R&D with up-gradation in
version as per the time i.e.
4.6c 4.7 5.0 ECC6.0… EHP 7(present Version)
Presently SAP is giving support only for ECC 6.0.
Market share of SAP is 65 to 70%
The Architecture of SAP
SAP Landscape: - A landscape is an arrangement of servers. Any client if they want to implement SAP they need to purchase servers.
SAP Suggest to go for minimum 3 Server:-
1) Development Server
2) Quality Server
3) Production Server
Development Server: - will be used to configure the client business
process into SAP. Development server
will be used by consultants
only.
Quality Server: - will be used to test the scenarios. Quality server will be used by consultants and core users.
Core User is the employee of the company who has good experience & exposure in client business process.
Production Server: - It is the
live server, where end user will do
day to day transactions in SAP.
Production server
will be used by end users
and core users.
Consultants will not have access to production
server.
Users will not have access to development server.
Roles & Responsibility of consultant
As a consultant we will be placed into either implementation project , support project, Rollout
Project, Upgrade Project.
Implementation Project
Configuring client business process newly into SAP.
Whenever implementation partner receives the order from client to implement SAP, then they start using ASAP methodology (ASAP stands for accelerated SAP).
ASAP methodology consists of guidelines to implement SAP, that is step by step implementing of SAP.
ASAP Methodology consists
5 Phases:-
1. Project Preparation
2. Business blue print (BBP)
3. Realization
4. Final Preparation
5. Go-Live & Support
Project Preparation Phase: -
Management from Implementation Partner Management from Client
BDM VP- IT
Delivery Head VP- Finance
Technical Expert Project Manager
Project management Technical Head
Project Preparation Phase
Activities:
1)
Project Preparation Phase
1. User Licenses: - Any client if they want to implement SAP they need to purchase user licenses
from SAP. Based
on number of end users they decide
on how many user licenses to be purchased from SAP.
Eg:-
Total no of end users in Galaxy
Pharma is 1000, each user license costs around Rs. 80000/-
The client has to pay this money to SAP and get the user licenses.
1000 user licenses x
Rs. 80000 = Rs. 8 cr.
This is not one time payment to SAP. Every year client has to pay 22% license cost to SAP in the form of AMC .i.e 22% of Rs
8 cr. as AMC (Annual Maintenance cost)
Sharing of licenses can be done in manufacturing plant if they have shift wise work system
2.
Landscape:- A landscape is an arrangement of servers.
Any client if they want to
implement SAP they need to
purchase servers.
SAP Suggest to go for 3 Servers:-
1)
2) Quality Server
3) Production Server
Development
Server:- will be used to configure the client business process into SAP. Development server will be used by consultant.
Quality Server:- will be used to
test the scenario. Quality server
will be used by consultant and core user.
Core User is the employee of the company who has good experience & exposure in client business process.
Production Server:-
It is live server where
end user will do day
to day transaction in SAP.
Production server will be used by end users and
core users. Consultant does not have excess to production server.
User does not have excess to development server.
After deciding how many servers to purchase, then they decide on sizing of the server.
Ex - Hard disk,
RAM etc. On the basis
of number of Pc‟s
Where to purchases the servers? Popular Manufacturers of servers in the market are HP, IBM, HCL, DELL .
3. Infrastructure:-
A). How many new pc‟s to be purchased for implementation
of SAP. Ex. - 1000 licenses means
1000 pc‟s required
Present pc‟s – 400 nos. (Out of 400, 200 pc‟s don‟t support SAP)
Total no. of pc‟s needed
800+200= 1000 nos
B). Server Environment: -
1) Decide where to place the servers.
2) Server room security
3) Temperature requirement
C). VPN connectivity (Virtual
private Network)
4. Implementation Partner: - will list out all the consultants who are going to involve in this implementation Project.
On an average
the team size for implementation of SAP to Domestic or Unknown client is 15. The team
size for implementation of SAP to
foreign client or known client is 60.
Team of Galaxy Pharma will list out all the core users.
They will pick one core user from
each module, and core user will
be in touch with consultant, throughout the implementation project whatever
consultant require, we need to consult only core user.
5. Consultant
Facilities: - If it is domestic project all the
consultants will go to client place for implementing SAP. If it is foreign project, from each module one consultant
will go to client place (On-Site) and rest of
the team will work from Off- shore (it means Implementation Partner office).
If its domestic project
and all consultants are moving to clients place for implementing SAP, then they will decide
responsibilities of each consultant.
Ex- Accommodation, food expenses, travel expenses, work environment etc.
The Average
project tenure for domestic project is 9 months.
For foreign
project 18 months
6. Go-Live Date: - It is a date from which client(Galaxy Pharma)
will start using SAP or the date the client will start entering day to day transactions
in SAP.
7. Scope for the project: - Which is not possible in standard SAP. Also called
as GAP‟s, will not be considered.
After completion of project preparation phase, the implementation partner management will come back to office and conduct kick-off meeting.
Kick-off: - It means starting off. For kick –off meeting they will invite all the consultants across all the modules that
are going to involve in this implementation project.
Kick-off meeting
agenda:-
1) Introduction about client
2) Rules & regulations of client
3) Role & Responsibility's of consultant
4) Core users list.
5) Go live date.
6) Staring date.
After kick –off meeting all the consultants will move to client‟s place for implementing SAP (Domestic). When all the consultants move to client place to implement SAP then we start 2nd phase of ASAP methodology that is Business Blue Print (BBP).
2) Business Blue Print Phase (3 Months)
Generally the 1St day of client visit, we will have introduction with core user and core user will take us for
site visit (Mfg plant visit).
on 2nd day, the first activity
in BBP is
1)
|
Everyday consultant has to go to core user place, ask the questions and whatever core user will explain note it down
as-it is.
Every day after completion of requirement gathering
(time allot 10am to 3pm) consultant has to prepare
a document called
AS-IS document.
AS-IS document consist of the present business process of client, whatever
core user explain as it is we mention in the document.
-
Based on questionnaires provided by the implement
partner we gather requirement from core user.
-
The requirement gathering
activity we do for 2 months.
2) Prepare
BBP document and sign-off: - After completion of requirement gathering
,we need to prepare BBP document.
BBP
document consist of AS-IS
and TO-BE document.
TO-BE document consist of, how the present business
of the client is going to be in SAP.
While preparing TO-BE document we may find some GAP‟s.
GAP: - For client business
process, if there is no solution in standard SAP then we call it
as a GAP.
Whenever we find GAP we will prepare
GAP analysis document.
Gap analysis document consist
of Clear description of client process, which is a GAP in
SAP.
Is there any alternate solution
or not? If yes, then what is the solution
we are going to provide?
Estimated efforts
-
Functional man days – 35 days
-
Technical man days – 30 days
After preparing BBP
document, we will send this
document to core user for sign-off.
Now core user has to go through the BBP document.
If everything is fine then he will send confirmation mail to consultant.
After getting confirmation mail we take the signature
of core user and PM in sign-off form and one copy will be with Implementation Partner and one
copy we will submitted to client.
Without sign off, we are not supposed to move to the next phase
of ASAP methodology.
- BBP preparation documentation and
sign off will take one-one and half
month.
-
The tenure for BBP
phase is 3-1/2 months.
-
We spend more time on BBP phase, BBP phase is most
critical phase because the success of the project is totally depended on
how accurate we gather the requirements from core user.
In BBP phase we prepare
two documents:-
1)
BBP document.
2)
GAP analysis document.
Common Problem‟s we face in BBP phase:-
1) Most of the core users they don‟t support for gathering
requirement, and also they don‟t come on time. (If it happens
continuous then after 4 or 5 days
we need to inform our PM and our PM will inform to
client PM).
2) They don‟t want change.
(They don‟t want to implement SAP, they may have threat
to their job).
3) Core user having knowledge
on SAP configuration (They will join some institute & they will ask some error and check
our knowledge or waste time for gaining
their knowledge).
After receiving BBP sign-off from core user then we move to the next phase of ASAP methodology that is realization.
3. Realization Phase
Realization: - Configuring the client
business process into SAP or mapping TO-BE process in SAP.
In this phase we Login
into development server,
to configure the client business
process into SAP.
We have two types of configurations:-
1. Base Line configuration
2. Final configuration
1.
Base line configuration: - It is the configuration for
which, we don‟t depend on other module consultant (it is a configuration which
is specific to one module).
2. Final
configuration(Integration between Modules): - it is the configuration for which we need to depend on other module
consultants(MM,PP,FI). This configuration we can‟t do on our own. Ex- Credit Management, Third party.
In SAP whenever
we are saving the configuration, we need to save it in a particular TRANSPORT REQUEST NUMBER
Request number will help to transport the configuration from one server
to another server.
Ex. - Transport request number
will help to transfer the configuration from development server
to quality server
for testing purpose.
After completion of base line configuration and final configuration we transport the entire requests
from development server to quality server.
Functional consultant role in transporting request
1. We need to
release the entire request. Each request consist of parent & child, first
release the child request then release
parent request.
2. List out all the request number in excel file along with the description & sequence, and send this excel file to basic consultant, basic consultant will
transport the entire request
from one server to another server.
Transport request is of two types:-
A).
Customizing request(Client Dependent): - Whatever configurations functional consultant will do, that will save in customizing request.
B).
Workbench request (Client In-Dependent): - Whatever
developments technical consultant will do,
that will store in workbench request.
After transporting the request from development server to quality server then we do internal testi
ng in quality server.
I).
Unit testing:
- It is the testing
which is specific
to one module and no need to depend on other module
consultants.
II). Integration testing: - It is the testing for which
we need to depend on other module
consultants.
Before testing we need to prepare test case document
or test scenario document. Based on this test
case we will do unit and integration
testing
|
Test Case |
|
a) What to test b) How to test c) Expected result d) Actual result e) Status f) Tested document number |
After completion of testing,
we prepare user manual document.
User Manual
document:-It is a guideline
to end users, this document consist of step by step process of creating master data and transaction data along with the
screen shots. After preparing user manual document,
we will give it to core user.
Configuration document: -
This document consists of the entire configurations
made for that particular client along
with the screen shots. Configuration
document will be used for KT (knowledge Transfer) purpose. This document will
be given to core users.
Final Preparation
Activities:-
i)
Training to core users (Train-the-Trainer): - We
give training to core user for 15 days. After that core user will give training to (15 days) their end User.
ii)
UAT Sign-off: - After training
we will ask core user
to test the scenarios and confirm.
Core user has to (10 days) test all
the scenarios; if everything is fine he will give UAT sign-off (User acceptance test).
Throughout
the implementation project we take two sign-off‟s from core user. One is BBP sign-off
and 2nd one is UAT
sign-off.
iii)
Quality
to production: - After getting UAT sign-off
we transport all the requests(configurations) from
quality to production Server.
iv)
Cutover activities: - Uploading of master data and
open transactions data from legacy to SAP.
Legacy means Non-SAP.
Consultant role in cutover
activities
a)
We list out what master data and what open
transaction data should be uploaded from legacy to SAP
Master data consist:-
Customer master
Material master
Pricing master
Open transaction data:
- Open Order (The order which created but yet not delivered or pending)
b)
We do recording
and send this recording to ABAPER while doing recording
simultaneously prepare excel
sheet with the same sequence of recording and send this excel sheet
to core user.
V)Cutover
Strategy: - It is the
planning for uploading data from legacy to SAP. During this strategy we decide when exactly to upload the data
from legacy to SAP. Whenever we plan to upload the data from legacy to
SAP, we request the client to stop the business
transactions. The reason is to avoid data inconsistency.
vi) Cutover Period: - Generally we take 2 days to upload the data from legacy to SAP. The 2 days period is called
cutover period.
After cutover period we go to the
next phase of ASAP methodology that is GO-LIVE & Support.
Go-Live: - Handing over SAP to client, from that
date onwards users will start entering
day to day transaction in SAP.
After implementation we provide 3 months of post production
support.
Interview Questions On
IMPLEMENTATATION PROJECT
1.
What is your team size?
2.
Did you ever attend
kickoff meeting?
3.
Where is your client located?
4.
Can you draw the organization structure of your client?
5.
What you did on the first day of your implementation
project?
6.
What is your project tenure?
7.
On what basis you gather
requirements?
8.
From which phase of ASAP methodology
you involved in implementation project?
9.
What are the activities
they do in project preparation
phase?
10. What are the documents you prepared in BBP phase?
11.
Where exactly you will find in
GAP's?
12.
What is GAP?
13.
Did you find any gaps in implementation project?
14. Did you face any gaps in
BBP phase?
15. What is the tenure for BBP?
16.
What is the most critical
phase of ASAP methodology?
17.
Where the servers are located?
18. How many modules you implemented?
19. Did you visit all the
manufacturing plants of our
client?
20. Did you visit depots?
21. How many types of configurations do you have?
22. Do you have clients
in your development server?
23. What are the documents you prepared in realization phase
24) How many types of testing do you have?
25) What is your role in transporting request?
What is the T code for importing request?
4.
What is the T code for releasing request?
5.
What is the T code for transporting
request from one server to
another server?
6.
How many types of requests do we have?
7.
In what scenarios
we‟re getting workbench requests in SD?
8.
What is cross
client?
9.
What happens if we save condition table
in local object?
10. What is the T code to
transport number ranges?
11. What do we have in test case document?
12. What is the purpose of preparing
configuration document?
13. After transporting the request
from one server to another server
how to take it back?
14. After releasing the request
can i use the request
to save further configurations?
15. What is the tenure for realization phase?
16. Out of 15 team size how many
are SD?
17. How many core users
do you have?
18. How many poour users do you have?
19. To whom you will give training?
20. How many days you will give training?
21. How many times you will take signoff
from core user?
22. What is your role in cutover
activities?
51. What is cutover period?
52. How many months we will
support after go-live?
53. What are the issues during 3months of support
period?
54. How many total documents we prepare in implementation
project?
55. After go-live what we will do?
56. On what basis we do
configuration?
57. What is the role of shadow consultant?
58. Explain your total activity in final preparation phase?
51. How many end users?
52. What is the difference between developer user
id's and normal user id's?
53. In which server
we do cutover activities?
54. What happens if you get an error while uploading the data?
55. Did you face any scenario for which we need
to contact sap for configuring client‟s business process?
SAP
SD SUPPORT PROJECT-OVERVIEW
Roles & Responsibility of consultant in Support Project
Whenever a support partner
get a new project, both the client and support
partner will enter into an agreement called
SLA (Service level agreement).
Other information we should know from SLA is change request.
Change Request: - If client is requesting any new change or
a new configuration for which there is no present configuration in the system,
than we treat it as change request.
Whenever we get change request,
we need to prepare change request document.
This document
consists of:-
Issue description (Ticket details).
Expected solution
Approximate efforts
Functional man days 15 days
Technical man days – 10 days
After preparing
change request document
we need to send this document to superior for review, after review we send this document to core user for
approval, after approval we start working on this issues.
Whenever the organization get new support project, management
will conduct kick-off
meeting. They invite all consultants who are going to
involve in support project.
For unknown client the project team size is 12 and out of this SD is 2, and for MNC or well known client the support team size is 50 or more and SD is 10.
Kick-off means – start
off
In kick-off meeting all will discuss about client:-
Introduction of client
Rules & regulation of client
Roles & responsibility of consultant
Share core user list
Agreement period
Starting date
After kick-off meeting all the
consultants will move to client
place for knowledge transfer
which is called KT.
KT process: - When
all the consultants go to client place for KT process. Core users will hand
over the configuration document
to consultant. Consultant has to go through the configuration document
and simultaneously does the system study (development server). After system study consultant has to prepare
understanding document, After understanding document consultant has to
give reverse KT to core users. The tenure for KT process is 15-20 days.
After reverse KT all the consultants will come back to
their office and start supporting the client.
Ticketing tools (Help Desk) available
in the market: - HP-QC,
Citrix, Remedy, JIRA, Peregrine
It will help to track the tickets and its time.
Ticket cycle process:-
In day to day business transactions End users will get the errors.
Whenever he get the error, he will send the mail to help desk where core users will be available. Core user will
try to solve the errors if it is configuration issues then he will log the ticket into ticket tool along with priority
of issues. After placing tickets in ticketing tool mail will be send to support partner co-coordinator. Co-coordinator
will open the ticketing tool and analyze the ticket and allocate the tickets to relevant consultant then the mail will send to consultant.
The basic responsibility of a consultant once he receive the ticket is,
send acknowledgement to core user and end user.
After acknowledgement we will go to pre-production server and try to do
the same what end user is trying to do in
production server then we should also get the same error in pre-production .
Because pre-production server is mirror
image of production server. After getting error we analyze it and we go to
development server and do the necessary configuration and transfer the request from development to quality server and ask the core user to test it and
confirm, after confirmation we transfer the configuration from quality to
production server.
Status of
Tickets:-
When we receive the ticket the status is open, after acknowledgement will
change the status from open to being process.
If We send a mail to user requesting for some more information then we change
status to waiting for information
.once we receive the required information then again we change the status to
being process. After completion we
send a mail to user to test it and confirm, then we change status to waiting
for confirmation, after user confirmation we change the status
to close.
Issues Resolution document: -
After solving the issues
consultant has to prepare Issue Resolution document.
Issues resolution document
consist of:-
|
-Ticket number |
|
|
- Ticket
Date |
|
|
- Ticket description |
Issue resolution document will be used for
future reference. |
|
- Solution description |
|
|
- Core
user description |
|
|
- Consultant description |
|
Consultant role in weekly meeting in support: - List out all the issues which are in pending and discuss on each and every
issue in Weekly meeting.
Escalation in support: - IF The issue is not properly
solved or addressed
by the consultant then core user will
send escalation mail to superior.
Levels of
consultant in support:-
Level 1 – consultant work only in high priority.
Level 2 – Medium & low priority.
Level 3 – work only in change request.
If core user is assigning wrong priority to the ticket, as a consultant we should request
core user to change the priority ,then only we need to accept the issues.
Every client may not have a ticketing tool. If client doesn‟t have
ticketing tool then ticket process will be manual, that is end user will send a mail manually to core user and
core user will send a mail manually to coordinator and co-coordinator will send a mail manually to consultant and
lastly consultant will send a mail(Acknowledgment) manually to core user and end user.
Roll Out Project
1)
Company
code roll out: - If
the client is starting their business in another country then they extend SAP configuration from one company code to
another company code.
2) Plant roll out: - If
the client is introducing new plant into the business
then we have to do configuration
for that plant in SAP, this we call as plant roll out.
3)
Up gradation Project: - Up gradation is upgrading the SAP
system from one version to another
version.
Login into SAP: - Double click on
SAP logon pad on desk
top.
Select IDES (client name).
Click on Log on
Client – 800
Client – 800
Password – india123
Whenever we are entering
to SAP the default
screen system propose is “Easy Access”.
-
End user will work in easy access
screen.
-
Consultant will use “IMG Screen”
IMG (Implementation Guide).
Interview Questions On SUPPORT Project
1. What is your support
team size?
2. How you got KT form the support client?
3. Tell me the process
how we will get ticket from the
client?
4. What is SLA? And what information we should know from SLA?
5. What documents you prepare
in support?
6. Did you worked on any high priority issues?
7.
Did you worked
on any user exit?
8. Did you develop any Z reports?
9. Tell me one critical issue that you solved
for this client?
10. What you did yesterday?
11. What is the pending
issue you are working on now?
12. What is your present
client‟s business process?
13. What is the ticketing tool your client is using?
14. Where is your client located?
15. What is change request?
16. Do you have levels in support
team?
17. What is your role in weekly meeting?
18. If core user is assigning the wrong priority
as consultant what you will do?
19. Did you worked on any
change request?
20. What do you mean by escalation?
21.
What happens if you are not in a position
to solve high priority issue within 4
hrs?
22. We got a ticket
from core user for which there is no solution
from you end?
Navigation to IMG screen
End user
doesn‟t have access to IMG screen.
If we mention /n before T-code
then present screen
will disappear and next screen will appear.
If we want to log off from SAP, in
the menu bar click on system and log off.
Enterprise Structure
Enterprise structure is an organizational structure that is mapped into SAP
Ex. - Corporate office,
Branch office, sales
head office, manufacturing plant, etc
Organizational Units
1.Company code: - Company code is an organizational unit which is responsible for all the external financial transactions which happens in the company.
Example: - Balance sheet and profit
& loss statement.
Every company has to prepare Balance
sheet and profit & loss statement on the name of company code. It is the organizational
unit, which is registered under company‟s act 1956(INDIA).
|
Z |
A |
L |
k |
In our project
we have one company code and the name of company code is Galaxy Pharmaceuticals
Address of company:
- Galaxy Pharmaceuticals
Industrial Estate#14
Hyderabad
The company code is: - ZALK (the company code can
be numeric or alpha numeric or character).
Q. What scenarios
a client will have multiple
company codes?
Ans. Group of company
or sister concern.
Example – Tata group, Reliance
group, etc.
Having operations in multiple
countries. Example – Ranbaxy India and
Ranbaxy US.
1.
Sales Organisation: - It
is an organizational unit which is responsible for all sales & services
happen in the Company.
Or
It is an organizational unit where strategic
decisions related to sales will be taken.
Or
It is organisation unit where we find
director sales and VP sales.
SD consultant
is responsible to define sales organisation in SAP. Sales organisation
is of 4 digit code.
Ans. If client is
having multiple company codes.Bifurcation of sales responsibility region wise.
Domestic and Export
sales.
|
Galaxy Domestic |
Galaxy Export |
|
|
In our project we have two sales
organizations. |
ZDOM |
ZEXP |
SD consultant is responsible to define distribution channel. Distribution channel
is a logical entity.
4.
Division: - Division is a range
of products or product line. Grouping of products which are similar
in nature.
5.
Sales office: - It
is a physical location where group of people work together to perform sale. (We also call
it as branch office).
In our project we have 28 sales offices in India. (Note:
- we have to maintain
only one sales
office). SD consultant is responsible to define sales office.
Sales office is a 4 digit
codes. It is physical location.
The difference between sales office and sales organisation is, in sales
organisation we will take strategic decision
related to sales but in sales office we can‟t take strategic decisions. In a
sales organisation we will find vice president sales and direct sales but in sales office we will
find sales manager, zonal manager.
6.
Sales
Group: - Group
of people within
a sales office working for different activities. Hierarchy of employees in sales office.
Example: - HDFC bank has 5 different sales activities like; CASA, Personal
loan, home loan, Vehicle loan and miscellaneous loan.
There is no relation between two groups.
If they don‟t have group then they follow hierarchy. SD consultant is responsible to define sales group. Sales
group is a 3
digits code.
In our project we have 2 sales groups.
Ex.:- Insulin & Antibiotic in one group and remain
in other group.
Sales group is a logical
entity.
7.
Plant: - “It is a physical
location where we do the process of manufacturing finished
goods.” MM consultant
is responsible to define plant in
Raw material
is a product which is
used to manufacture finished goods and loses
its identity in the process.
Whenever production department plan to manufacture particular X product they will send request to store department.
Store department
will cross check the raw materials. If all raw materials are available then they issue raw materials to production department.
The dispatch
department 1st they plan for delivery
and then they do picking activity and then packing.
After packing they send the goods
to shipping point.
Shipping point: -It is a physical
location where we do the process of loading goods into trucks
,Rail for dispatching it to customers.
Storage location: - It is a physical location
where we store the
goods within plant.
1.
Depot: - Depot is a physical
location where we store finished
goods to easy distribution goods to customer. In SAP depot is also defined as Plant.
2.
C&F: - Carry and forward, It is a physical location
where we store the finished
goods for easy distributing goods to customers. Owned by third party Vendor.
In SAP C&F is also defined
as plant.
In our project we have two manufacturing plants, one in Vapi and one is in Mumbai and 28 depot but for
practice purpose define only 2 manufacturing plants.
1. Vapi 2. Mumbai
10. Storage location: - It
is a physical location where
we store the goods
within a plant.
In our project each manufacturing plant have 5 storage locations
MM consultant is responsible for storage location definition. It is
also 4 digit code.
11. Shipping Point: - It
is a physical location where we do the process of loading the finished
goods into trucks
for dispatching it to customers.
SD consultant is responsible to define shipping point. Shipping point is 4 digits code.
Other units in organizational unit not relevant to SD consultant
Company:
- A company is an organizational unit which will help to group several company
codes into one. Ex. - Tata
Group, Reliance group etc.
FI consultant is responsible
to define company.
Business Area: - Business area is an organizational unit which will help to generate internal
B/S plant wise.
[The Business area concept is not in use from ECC 6.0
version].
FI consultant is
responsible to define Business Area.
Credit
Control Area: - It is an organizational unit which is responsible for credit activities. (Credit department).
Controlling Area: - It is an organizational unit which is responsible for controlling the cost of the product.
CO consultant is responsible
to define controlling Area.
Purchases Organisation: - It is an organizational unit which is responsible for all purchases
happening in the company. MM consultant is responsible to define
purchases organisation.
“The controls in Sales Organisation”
=> The Address text in sales organisation: - Address text in sales organisation will help to determine the address of the sales organisation to print it in relevant output.
The output can be printout or email or fax.
=> Sales Organisation
Calendar: - The calendar
specifies all holidays and working days.
Define Factory calendar: - SPRO SAP Net weaver General setting
maintain calendar public holiday click on change
button (Pencil ICON) go to create floating public holiday year (2014 – month –
day) mention sort criteria (IN) religious (22 Hindu) Short holiday – long
holiday (Gudipadwa) Enter
Go Back
Click on holiday calendar (in holiday calendar we list out all public
holidays – in real time HR consultant create calendar) click on change go to
create calendar ID (P1) (Galaxy Calender) click on assign holiday go to short key
and select all IN (India)
holiday assign holiday
then select all public holiday save it.
Go Back
Select factory calendar click on change click on create factory calendar
ID (P2) (Galaxy Calender) assign holiday calendar select the day Monday to Friday or Saturday and save
it.
After creating the factory
calendar we assign the factory calendar to sales
organisation.
We assign factory calendar for three organizational units 1.
Sales organisation 2. Plant and 3. Shipping point.
Rebate Proc Active: - Rebate is a special kind of discount which is a conditional discount
and will be valid for specific period of time
Example: - The rebate scheme if any customer
purchases 15000 nos. Cartoon from January to December then he will be
eligible for rebate of
15%.
This field is pre requites to process rebate in an organisation i.e. if
we check this then only system
will allow to process
rebates.
ALE: data for purchases
order (ALE – Application linking enabling):- We use this only for third party process and individual
purchases order process.
If we maintain ALE data for PO while creating sales order in third party
process and IPO process, system
automatically generate
purchases order.
Controls in shipping Point
Path line: - go to shipping
point loading time (it is time taken to do the process of loading the goods into trucks
for dispatching to customer.
Pick Pack Time: - It is time taken to pick
the material from storage location
and to pack it.
Loading time and pick pack time will help to perform delivery scheduling
(delivery scheduling is the process
of determining the delivery date and confirm
quantity).
MASTER DATA
It is the data which is stored centrally
and used in day to day transactions. In SAP SD we have 4 types of Master
Data.
1)
Customer Master: - It is the details
of the customer which is stored centrally and used in day to day transaction.
Ex. – Customer Name, address, communication details, payment info, sales info, etc. Master data is a data which is not changed frequently.
The advantages of Master data:-
I.
No need to enter the details
of the customer every time, which will save the time of
end-user.
II.
Master data will avoid manual mistake.
2)
Material Master: - It is the details of the
products which we store centrally and use in day to day transactions. Ex- Specification
of products,weight
3)
Customer material info record (CMIR):- We use CMIR if customer is placing order with
their own material code. By using
CMIR we assign customer material number with our material number then while creating sales order if user enter
customer material number and system automatically determine our material
number.
4) Condition Master: - Condition master is nothing but pricing master. In this master data we maintain pricing data for all the products.
1) Customer Master
End user will
create customer master in SAP Easy Access
Screen
Roll of consultant
As a consultant we have to give training
to core user, so we should have knowledge of customer master
data.
We should know how to create customer
master.
We define new
entries in customer master data fields. The length
of customer number
is max up to 10 digits.
Customer master data will be divided into three screens:-
|
General Data |
Company code Data |
Sales Area Data |
|
SD
– Address |
FI
– Account |
SD – Sales |
|
FI
– Control Data |
FI
– Payment Transaction |
SD - Shipping |
|
FI
– Payment transaction |
FI
– Correspondence |
SD –
Billing |
|
SD –
Marketing |
FI
– Insurance |
SD
– Partner Functions. |
|
SD –
Unloading points |
|
|
|
SD –
Export Data |
|
|
|
SD – Contact Person |
|
|
In real time authorization to create customer master will be given to one
or two users. If we give authorization to two users, First SD User will create customer with sales data and send it to FI user. Then FI user will enter FI related data, the other scenario is,
we give training to one user to maintain both SD and FI data. In that case only one person will be authorized to customer
master record.
|
T.
Code |
Customer Centrally |
Company Code
Data |
Sales Related |
|
CREATE |
XD01 |
FD01 |
VD01 |
|
CHANGE |
XD02 |
FD02 |
VD02 |
|
DISPLAY |
XD03 |
FD03 |
VD03 |
Path for creating customer
Master
click on account
group overview select standard 0001 company code (ZALK) select
org (ZDOM) Dist.
Channel Division
enter (when we are creating
customer for the 1st time with the new sales area we will get the error message
that sales area is not define for customer. (To solve this error).
Go to the path SPRO S&D master data define common distribution
channel go to our sales organisation (ZDOM)
fill D.CH- Common Distribution channel same which mentioned in dist channel and
enter it and save it.
Go back
Define common division go to our sales organisation enter Division and
Common Division same which we mentioned
in division save it.
Copying reconciliation account
from standard company code 1000
SPRO financial
accounting (new) general ledger accounting (new) master data G/L A/ creation and processing alternative methods copy G/L A/c copy company
code.
Before copying
G/L A/C go to the T.code OBY6 and go to our company
code, select it go to details chart of accts
[INT] fiscal year variant (V3)
fiscal year variant specify
the financial year of the company
Maintain fiscal variant as [1000] pstng period variant as [1000]
save it.
Now go to SPRO ....to copy company code in copy from maintain
company code [1000]
uncheck test run execute (F8)
Go back and select the recon account [140000].
TABS in General
Data Screen
TABS
in General Data Screen
1.
Address: - Address TAB consists
of the personal info of the customer.
i.e. his name, address and communication details.
Title (Mr.) name (Apollo
hospital) street – house
no. Postal code country
region
Transportation
Zone: Transportation Zone will help to determine
route into sales document
2.Control Data: - FI user is responsible to maintain control
data. Control data TAB consists
of tax information of the
customer,
3.Payment Transaction: - This TAB consists
of the customer bank details
and cards details.
FI user is responsible .
4. Marketing: - SD user is responsible to maintain marketing TAB.
4. Marketing: - SD user is responsible to maintain marketing TAB.
1.
Nielsen
ID: - Nielsen id will be used to track
the customers who are located in market survey regions. Whenever we are launching new products we do market survey in
specific regions. If the customers are located in market survey regions then we have to maintain
this field.
Define new entries in Nielsen
ID
Shortcut method to define entries in fields Place the Cursor in the field
and press F1 and click on customizing (key symbol)
continue without specifying project.
OR
Take path SPRO S&D master data business partner customer
marketing define Nielsen ID new entries Y1 (GUJ/RAJ), Y2 (TN/KE), Y3(OR/KOL) save it.
Nielsen id (Y1) Customer classification (Y1)
2. Customer
classification: - Classifying the customer based
on their sales turnover.
The purpose
of this field is 1) Helps to offer discounts 2) Helps to
fix credit limits.
Define customer
classification
SPRO S&D master data business partner customer marketing define customer
classification
go to new entry Y1- 8cr to 10 cr, Y2- 5cr to 8cr, Y3-3cr to 5cr, Y4 -1 to 3cr,
Y5 – o to 1cr save it.
1. Industry: - classifying the customer based
on the industry they belong to, the
purpose of this field is
1) Reporting (Analysis) and 2) Helps to offer discounts.
Industry code 1: - its sub classification of industry.
2.
Regional market: - Dividing the customer in local
market into A class or B class or C Class based on the revenue it‟s generate.
The main purpose
of this field is reporting.
3. Hierarchy assign
Customer Hierarchy: - A customer
is having different labels.
6.
Key figure: - Key figure will be used to compare the Last year sales with present year sales. In annual sales
field we maintain last year sales.
7 .Legal
status: - This field controls
whether customer is Pvt Ltd,
or Public Ltd,
5.
Unloading Point: - It is the physical
location where we unload the goods at customer place.
Unloading point will be used to
plan the delivery for customers.
We assign
customer calendar in unloading point. While doing deliver
system will consider
customer calendar.
a.
Goods receiving hours:
- This will specify the time of customer‟s goods receiving hours.
Defining receiving hours
Take Path – SPRO Master Data business partner customer
shipping define goods receiving hours go to new entries
fill the hours.
Q. There is a customer
who will receive the goods only on Saturday. Where we do control? Ans. In goods receiving hours.
4.Export data: - If the customer is located in outside countries then we have to maintain export data TAB.
5.
Contact person: - Contact person is the
employee of customer
who is responsible for various activities.
TABS in Company Code Data Screen
1. Account Management
a.
Reconciliation account: - Reconciliation account
is G/L account which will be used to accumulate total outstanding of the customer.
Whenever we are creating
invoice system will generate accounting
document. i.e. system will post the invoice
values into the accounting and
Accounting entry is:
Customer Account
Debit
To
Revenue Account
Credit
For the customer account
system determine G/L account from reconciliation A/c.
Select reconciliation A/c as 140000
1. Payment Transaction
a.
Terms of Payment: - It is an agreement
between company and customer for the number of days given to make the payment. (We also called it as credit period).
b.
Payment history
record: - If we check this then customer payment
information will be updated into
credit management.
TABS in Sales Area Data Screen
1.
Sales
a. Sales District:- It is a sub-classification of sales office,
for the purpose of generating
sales report.
The main
purpose of sales district is reporting. Defining sales district:-
Path: SPRO S&D Master
Data Business partner Customer Sales Define sales
districts
go to new entries and define
own sales districts.
b. Sales Office: - It is a physical
location where group of people with in the office work together to perform sales. Assign the sales office in which
customer belongs to
c. Sales group:
- Group of people within
a sales office
working for different activity.
d. Customer Group:
- Grouping of customers who will share the same attributes in volumes
Ex-
|
Dealer |
Distributor |
Institution |
|
|
P1- Bulk dealer |
P4 - Bulk
distributor |
P7 |
- Bulk institution |
|
P2 - Medium
dealer |
P5 - Medium
distributor |
P8 - |
Medium institution |
|
P3-Low dealer |
P6 -Low distributor |
P9 -Low institution |
|
The purpose of
customer group is 1. Reporting 2. Pricing The path
is same assales district.
e. ABC Classification: - Customers are classified into A,B,C classification.
Parameters for classification: > Turnover, > Payment history
etc… The purpose of this field is
1. Reporting
2.
Response time to solve the issues or queries raised by customer.
f.Currency: - If the customer is located outside the country then we maintain customer currency.
If the customer currency is different from company code currency then
while doing sales transaction system
will display the values in customer currency but in accounting document system
will display the value in company
code currency.
This conversion will be happened based on exchange rate.
The T-code
to maintain exchange rate is
T.Code OC41.
The Standard exchange rate type
is “M”.
g.Switch off rounding: - If we check this, system
will not perform
rounding while creating
sales order.
Quantity Decimals
h.Order probability: - After placing the order what is
the chance that the customer
will not cancel the order.
i.Item
Proposal: - If customer is regularly placing order for similar items
then instead of entering the items manually
into sales document every time, we prepare a list and call the list while
creating a sales order. The end user
will select the items from the list and copied into sales order which will save
the time of end users.
The T-code
for creating item proposal is T.CodeVA51.
Mention the item proposal as PV
Maintain sales area enter description mention material and Tgt quantity,
UOM, Description and save it. Go
to the item proposal to customer
master and assign the number and save it.
j. Exchange
Rate type: - If we have an
agreement with the customer for fixed exchange rate throughout the month then we maintain exchange rate for
the exchange rate type other then “M” and we assign that exchange rate type in customer master.
If we don‟t assign
exchange rate type then system
consider the standard
rate type “M”
k. PP customer
procedure: - This field will be used for cross
selling concept or product proposal
concept.
Cross selling is selling
additional products along with the main product. For cross selling
maintain B
For Product
proposal maintain A
Product proposal is automatic determination of
item proposal in sales document.
L.Price group: - Grouping of customers who will share the same pricing attributes. The purpose of this field
is to maintain discounts.
Price group field will help to simplify the maintenance of discount
condition records.
Define Price group:-
SPRO S&D basic function pricing
Maintain price relevant
master data field define price group and double click new entries
M.
Customer pricing procedure: - This field is one of parameter
to determine pricing
procedure into sales document.
M. Price list: - Grouping of customers
who will share the same base price.
Price list will be used
to maintain base price. Ex. Dealer pricelist,
Distribute pricelist, institution pricelist
& direct pricelist etc.
N.
Customer statics group: - This field controls whether to update customer sales data into LIS (Logistics information system)
or not and
LIS is reporting system.
a.
Delivery priority: - This field will be used for classifying the customers into high delivery
priority, medium delivery
priority, and low delivery priority.
The purpose of this field is it will help to process Back orders
and rescheduling.
Back
Order processing :- Whenever high delivery priority customer place
order, if stock is not available then
we go back to the open orders of low priority customer and cancel the
confirmation of low delivery priority
and assign to high delivery priority
customer.
Rescheduling: - Doing the back order process automatically by the system.
Define delivery
priority
SPRO S&D Master data business partner customer shipping define delivery
priority
a.
Order combination: - This field is prerequisite to combine multiple orders into single delivery.
If we check this then
only system will allow combine multiple orders into single delivery.
b. Shipping condition:
- This field is one of the parameter to determine shipping
point into sales document.
Delivering Plant: - If we maintain plant here then it will be determine into sales document.
The
criteria for determining plant into sales document
CMIR
Customer
master
Material
master
a.
Relevant for POD (proof of delivery
or acknowledgement):- If we check this, system will not allow to create invoice for the customer until we receive acknowledgement from the customer.
The T-code to receive POD is T.Code VLPOD.
In POD process while creating invoice to customer, system will copy the quantity
from VLPOD.
b.
POD timeframe: - If we mention Number of days here, if customer fails to send the acknowledgement within the number
of days then system will
allow creating invoice for the total delivered quantity.
c.
Complete delivery required by law: - If
we check this field then system will not allow creating partial
deliveries and system will
not allow confirming partial quantities.
d.
Partial
Delivery per item: - This field controls whether
to allow partial
delivery or not and it also controls how many maximum
partial deliveries to be allowed.
If partial delivery is not allowed then maintain C (only complete
delivery allow). If we want
to allow partial delivery then maintain either Blank or D.
If partial delivery per item is blank then we can restrict maximum partial deliveries up to
9. If partial delivery per item
is “D” then there is no limit
to partial deliveries.
Q. How many
maximum numbers of partial deliveries can be allowed for a single order?
Ans. Depends
on Partial Deliveries per item
i. Unlimited Tolerance: - if
we check this then system will allow increasing or decreasing the quantities in delivery document without any limitation.
Under
delivery tolerance:- If we maintain some percentage here then system
will allow to decrease the quantity
in delivery document up to that percentage, if the percentage exceed then
system will give warning
message.
Over
delivery tolerance: - If we maintain some percentage here then system
will allow increasing the quantity in
delivery document up to that percentage, if the percentage exceed system will
give warning message or error massage.
3) Billing Document TAB
a. Rebate: - This field is prerequisite to process rebate
for a customer.
b.
Invoicing Dates: - If the clients requirement is,
invoice to be generated only on specific date of every month for all the dispatches made during
the month then we go for invoicing dates.
Configuration for invoicing dates
SPRO S&D master data business partner customer billing document
define billing schedule factory calendar change
create factory calendar id [P5] invoicing dates holiday calendar remove all working days save it .
Click on special Rules (in same
screen) click on create from date 30.09.15 TO date 30.09.15 for September, SAVE.same to do for each and
every month.
C. Invoicing
List dates: -
Consolidating all invoices raised during a particular month into one and
sending it to payer, it‟s called as invoice list.
Configuration is
same like above (invoicing Dates). The T-code
for invoicing list is [VF21] or [VF24].
D. Incoterms: - It is an international commercial terms which is an agreement between
Consigner and Consignee for the successful completion of deliveries.
This field specifies who is responsible for freight charges,
insurance charges, loading
charges etc. That
is whether customer is responsible or company is
responsible.
Inco terms
is one of the split
criteria for deliveries.
E. Terms of Payment: - It is an agreement
between company and customer for the number of days given to make the payment. It also called it as
credit period.
Defining terms of
payment
SPRO S&D master data business
partner customer billing document
define terms of payment go to new entries
pay terms [PO45 or 45 days]
sales text [45 days or 30
days].
Base line date: - it is the date from which system start calculating payment
terms. Generally base line date is
invoice date.
Fixed
day: - if we mention someday here then every month from that day
onwards system start calculating payment terms irrespective of invoice date.
Additional month: - If we mention number of months here then after creating invoice system will wait up to that months and then system starts
calculating payment terms.
C.Payment guarantee
procedure: - If the customer is liable for
payment guarantee, then system will not allow
creating delivery until we receive payment guarantee from the customer. The
payment guarantee can be bank guarantee or letter of credit.
Generally Overseas
Customers are liable for payment guarantee.
Q. Without
configuring credit management system is blocking
the order for credit, what could be the reason?
Ans. Customer
is liable for payment
guarantee procedure.
D. Account
assignment group: -
This field is one of the parameter to determine the G/L A/C while posting invoice
values into accounting.
E. Tax
Classification: - This field controls
whether customer is liable for TAX or not.
4. Partner Function
TAB
SAP classified the customers into four partner
function
i.
Sold to party (SP)
– He is the customer who will place
an order to company.
ii.
Shift to party (SH) – He is
the customer to whom we
deliver the goods.
iii.
Bill to party (BP) – He is the customer
who will receive
the bill.
iv.
Payer (PY) – He is the customer
who will make the payment. XD04
– Tracking the change log in customer master.
XD05 – Blocking
/ Unblocking the customer master. XD06 – Customer flag for deletion
XD07 – Changing the customer from one account
group to another
A/C group.
Extending the customer
from one sales area to another sales area
Ex. ZDOM + Z1+Z1 ZDOM+Z1+Z2 ZDOM+Z1+Z3........ up to last sales area ZEXP+Z4+Z6
Take path: - XD01 0001 9990000030(Apollo) as customer no. ZALK, Z1, Z2
(New sales area) in reference again
put 9990000030 as customer no company code Z1 Z1 (because it‟s already created
so take as reference division) enter and save it
and see customer‟s sales area.
Creating customers
with multiple partner
functions and assigning to sold to party
Apollo Scunedrabad (SH-BP)
Apollo VIZAG (SH-BP)
XD01 Select 0001 customer
name complete till partner function
and see how many partner function in partner function TAB.
XD01 Select 0002 (for creating ship to party) and
go till partner function XD01 Select 0004(to
create bill to party) and go till
partner function XD02 for change
(assigning) SH and BP to SP.
Q. I don‟t want user to duplicate the customer master data in SAP. I want system
to restrict this. Where is control?
Ans. Maintain
message no 145
SPRO logistics
general business partner
customer control change
message control for customer data in this configuration TAB, mention the message number 145 online (I) batch (I) save it.
Q Which data from customer
master will automatically update in to already created
sales order? If we make changes in customer master.
Ans Address.
Tables in customer Master :Table will help to store the data
KNA1 – General data
KNB1 – Company code data
KNVV – Sales area data
KNVP – Partner data
ADRC – Address data
VBKD - Business Data
The T. Code to see the table
entries – SE16
Common Division
We use common division concept
if the client is having more number of divisions.
Common division
will help to save the time of end-users and also save the space in data base. If we don‟t have concept
of common division then we have to create customer for each and every division.
Ex. - If we have 100 division
then we need to create customer in one division
and extend the customer to other 99 divisions.
Extending the customer will also take same space and time
of data base and end-users.
To overcome this SAP has given a
provision code is COMMON DIVISION.
Ex. – In our scenario division
are Z1, Z2, Z3, Z4,
Z5, and Z6 but instead
of all we take common division
Z0.
Configuration of common division: - Define
one new division is called common division.
Define as same as division
name common division and code Z0.
Assign Common division to
sales org. Setup Sales area with common division
Assign S&D go to new entries fill and save it
Define common
Division
SPRO S&D master data define common
division assign new division with
existing division save it.
Ans.
No, because each customer should
belongs exactly one distribution channel and we don‟t extend the customer
from one distribution channel to another distribution channel, so we don‟t use
common distribution channel.
Fields in Customer A/c group
Account Group: - The standard
account group for sold to party is “0001”, Ship to party is “0002”,
Payer is “0003”
and Bill to Party is “0004”.
Purpose of Account group: -
1)
Account group will help to differentiate the number ranges.
2)
Account group will help to control the fields in customer master. Controlling the fields means making the fields mandatory,optional,suppress,.
3)
Account group will help to control
the partner functions.
In real time we need to define new account groups
based on client‟s requirements.
Configuring the Customer
number ranges
SPRO logistics general business partner customer control define and
assign number ranges define number ranges
for customer master click on change interval click on insert interval mention
some number (Z8) mention From no. and To no. (Press F4) and select
a number.
External
check box : If we check this system will treat it as external number
and while creating customer master
user has to enter the number manually, if we uncheck this then system will
treat it as internal number then
while saving the customer master system automatically propose
the number. save it.
Define Account Group:-
SPRO logistics general business partner customer control define a/c group
and field selection for customer select
the a/c group “0001 (SP) click on copy mention our own A/c group (Q001) and
assign our own number range (Z8) enter save it.
Again do the same for A/c group 0002 (SH) – Q002 Again do the same for A/c group 0003 (PY) – Q003 Again
do the same for A/c group 0004(BP) – Q004
One
Time Account: - We use this only for one time customers. One time
customer is the customer who may not
place order for the next time, for those one time customer we don‟t waste the
space in database by creating customer master
record.
But without customer master system will not allow to create sales order, so we create one common customer for all one time customers without name
and address. (It is like dummy customer). Whenever one time customer
will place order we use
this dummy customer number.
If we check this one time account then
while creating sales order for one time customer system automatically ask for name and address.
The standard A/c group for one time customer is “CPD” (Internal
number) “CPDA” (External number).
Field Status: - Field status will help to control the fields in customer
master i.e. making the fields mandatory, or optional,
or display or suppress.
Text procedure: - Every customer
will have their own specific
text information. This text information we maintain in customer master.
Ex. - Packing instruction, delivery instruction, payment instruction, term & condition etc.
This text information whatever
we maintain in customer master will be copied into sales order and then
delivery and then to invoice and we
also print the text in
relevant outputs.
Ex. - Printout, E-mail, fax etc.
Customer Pricing
Procedure: - If we maintain
customer pricing procedure
here then system will propose it by default
while creating customer master.
Partner
determination Procedure: - It is the procedure which consists of relevant
partner function and which will
help to determine relevant
partner function in customer master.
AG procedure will have four partner functions
that is the reason when create sold to party system will propose 4 partner
function which are SP-SH-BP-PY.
WE procedure will have one partner functions
that is the reason when create ship to party system will propose 1 partner function which is SH.
RE procedure will have one partner functions
that is the reason when create Bill to party system will propose 1 partner function which is BP.
RG procedure will have
one partner functions is PY
Output determination procedure: - The standard output
determination procedure for A/c group is
{DB0001}.
If access to condition
field in output
type determination is unchecked then system will determine the output type into
sales document from customer master with the help of DB0001 procedure.
In customer master document
TAB we maintain output type.
Partner Determination for customer master
This configuration will help to determine partner functions in customer master.
Take path SPRO S&D
basic function partner
determination setup partner
determination setup partner
determination for customer
master.
1st step Define partner
function
|
Partner Function |
Partner Type |
Unique |
|
SP |
KU |
|
|
SH |
KU |
|
|
BP |
KU |
|
|
PY |
KU |
|
If we check unique then system will not allow adding more partner function in customer master.
The standard partner
determination procedure for sold
to party is “AG”.
Double click on
PDP go to new entries define
our own PDP (QAG) (Galaxy
Sold to party ) save it.
Select the PDP and double click on partner
function in procedure and go to new entries.
Place the partner function
SP-SH-BP-PY in PDP.
|
PDP |
PF |
Not |
Mandatory |
If PDP is for sold to party then
we check not
modifiable for SP.
If PDP |
|
Modifiable |
is for ship to party then we check
not modifiable for SH.
If PDP is for |
|||
|
QAG |
SP |
|
|
Bill to party then we check
not modifiable for BP.
If PDP is for
Payer |
|
QAG |
SH |
|
|
then we check not modifiable
for PY. |
|
QAG |
BP |
|
|
If we check not modifiable then system will not allow changing the |
|
QAG |
PY |
|
|
partner function in customer. |
If we check mandatory then if any of the partner function
is missing then system will not allow
saving the customer master.
In this configuration step we
assign partner determination procedure to A/c group
|
A/c Group |
PDP |
|
|
Q001 |
QAG |
In place
of AG, Mention
QAG and Save
it |
|
5th Step |
Double click on A/c group function assignment |
|
In this configuration step,
we assign partner function to account group. go to new
entries fill this and save it.
|
SP |
Q001 |
|
SH |
Q001 |
|
BP |
Q001 |
|
PY |
Q001 |
|
Bill to Party |
|
|
2nd step |
Partner determination procedure |
Double click on
PDP go to new entries define
our own PDP (QWE)
(Galaxy Bill to party) save it.
Select the PDP and double click on partner
function in procedure and go to new entries. Place the partner function SH in PDP.
|
PDP |
PF |
Not |
Mandatory |
|
Modifiable |
|||
|
QWE |
SH |
|
|
In this configuration step we
assign partner determination procedure to A/c group
|
A/c Group |
PDP |
|
|
Q002 |
QWE |
In place
of WE, Mention QWE and Save
it |
|
5th Step |
Double click on A/c group function assignment |
|
In this configuration step,
we assign partner function
to account group go to new entries
fill this and save it.
Note: - Same we need to do for Bill to party
(BP) and Payer (PY).
Q.What are the parameters
we have in Account Group
Interview Questions
on CUSTOMER MASTER
1 what is the purpose
of ALE data for purchase order in sales
organization?
1. Where we maintain pick pack time and loading time? What is
the purpose of it?
2. Where can i maintain
pick pack time other than shipping point?
3. What is the relationship between
plant and shipping
point?
4. How many sales organizations your client is having
and why?
5. What is business area?
6. How many divisions your client is having and what are they?
7. How many distribution channels
your client is having and what are they?
8. How many places we assign
calendar?
9. What is reconsilation account?
10. What is invoicing dates?
11. What is invoicing list dates?
12. What is the t.code
for invoice list?
13. What is sales area and
sales line?
14. What is purpose of
shipping conditions?
15. From which partner
function system considers shipping conditions?
16. What is POD? What happens if i check
POD?
17. How many partial
deliveries we can make?
18. What is the prerequisite to combine
multiple orders into single
delivery?
19. Where we maintain cash discount percentages? And how it determines into sales documents?
20. What is fixed day in payment
terms?
21. How many places we maintain payment terms in customer
master? Consider from payer?
22. Without configuring credit management my order id blocking
for credit what could be the reason?
23. System considers
incorterms from which
partner function?
24. What is the criteria for determining plant into sales document?
25. Without configuring credit management
system is blocking the order
for credit, what could
be the reason?
26. What is the prerequisite to process rebates?
27. What is difference between
price group and price list?
28. What is the purpose of customer
pricing procedure?
29. What is the purpose
of account group?
30. What happens if we check one time account
in account group?
31. Why we assign partner
function to partner
procedure and account group?
32. What is the purpose of status field in number ranges?
33. If user is duplicating customer master record, that is
creating twice the same customer master i want system
to give warning message
where is the control?
34. Where we assign customer
calendar in customer
master?
35. Clients requirement is they want to receive goods only on Saturday how to configure this?
36. What is the prerequisite to process rebates?
37. Which data from customer master will automatically updates into already created
sales order?
38. What happens if we check not modifiable in partner determination procedure?
39. What happens if we check mandatory?
Material Master
The Specifications of the product which is stored centrally
and used in day to day
transactions.
The T-code to create material Master are:-
Material master is integration between
SD+MM+PP+FI+CO+QM. The Length of material master is 18
characters.
Material master
will be further classified into multiple views:-
|
|
Basic data 1 |
|
|
MM |
Basic data
2 |
|
|
|
Sales org data 1 |
PP |
|
|
Sales org
data 2 |
|
|
SD |
Sales general
plan |
|
|
|
Sales text |
MM |
|
MM |
Purchasing |
|
|
|
FI |
|
|
|
Purchasing text |
|
|
|
|
CO |
MM consultant will take active role for Material master.
In real time End-user will create material
master.
Define new
entries in the field. We give
training to core user.
The material code will have option
of both external and internal.
If we mention some code while creating material
master then system will treat it as external number.
If the material code is blank
while creating material
master then system will propose internal number.
Industry Sector: - The field specified the type
of the industry the material
belongs to.
Material Type: - We have Different
material types
1.
A raw material (ROH - Material Type) is the material which
is used to manufacture finished goods.
2. Semi finished
(HALB – Material
type) is the product which is under
the process of manufacturing finished goods.
3. Finished Goods (FERT – Material
Type) is the products which we manufacture and sell to customer.
4. Trading Goods (HAWA – Material type) is the material which we don‟t manufacture but we procure it from
vendors and sell it to
customer.
Mention the plant, storage
location, sales organisation, distribution channel
then click on continue.
Error1.
If we are creating
material for the first time with the new organisation structure then we will get the message
that material is not fully maintain
for company code.
To solve this go to T-code OBY6 select our company code go to details TAB mention chart of A/c [INT] mention
fiscal year variant [V3] maintain field status variant [1000] posting
period variant [1000] save it.
T-code OMSY go to company code and maintain the period (current month as
per V3) and year save it.
In MRP 1 view select MRP type as “ND”.
In Accounting maintain
cost of product
in standard price field.
Sales people are responsibility for
only finished goods and trading goods.
Basic Data 1 view
Base unit of measure: - It is the unit in which we manufacture and store the goods. Example
– Each, one piece, liter, bottle, strips, etc.
Material Group: - Grouping
of materials which will
share same attributes. The purpose of this
field is
1)
Reporting and 2) pricing.
Old material number: - This field will be used if the legacy material number is different
with SAP material number. In this field we maintain legacy material number for reference purpose.
Division: - Whatever
the division we maintain in material master, it will be determine
into sales document
line item.
Product
allocation: - It is a process of reserving the stocks to customer, customer
groups, and distribution channel.
X-Plant material status: - This field will be
used to block the materials across all the plants.
Product Hierarchy: - IF product is having different
labels.
General Item Category
Group: - This field is one of the parameter to determine item category in inbound deliver
process.
Gross Weight: - It is the
weight of the product including packaging.
Net weight: - It is the weight of the product
excluding packaging.
Sales unit:
- It is the unit in which we sell the goods to customers.
If base unit and sales unit is different,
than system will ask for conversion. (if we want to do conversion go to additional data unit of measure there we can see
the conversions).
Sales unit not vary:
- This field controls whether to change the sales unit or not
in sales document. If we check
this then system will not
allow change the sales unit in sales document.
X- Distribution chain status: - This field will be used to block the material for sales across
all distribution channels.
D-Chain specific Status: - Thus field will be used, if we want the block the material
for sales in a particular
distribution channels.
Delivery
Plant: - If we maintain
plant here then it will be determined
into sales document line item. The Criteria for determining plant
into sales document
is: CMIR, Customer
Master, and Material
Master
Cash Discount: - This field
is prerequisite to determine the cash discount
condition type SKTO into sales
document.
If
we check this then only the
cash discount will be determine into sales document.
Tax Classification: - This field controls whether the material is liable for tax or not.
Minimum Order quantity: -
While creating sales order system will check the sales order quantity with minimum order quantity. If sales order
quantity is less then minimum order quantity then system will give warning
message.
Minimum delivery Quantity: -
If we maintain some quantity here then while creating delivery document system will check the delivery quantity
with minimum delivery quantity.
IF The delivery quantity
is less than minimum quantity then
system will give warning or error
message.
Material statics
group: - This field control
whether to update
material sales data into LIS or not.
Material
pricing group: - Grouping of materials which will share the same pricing attributes. This field will be used for group condition concept in pricing.
Volume rebate groups: - We use this field for group rebate concept. Group rebate is announcing the rebate for group materials.
Account Assignment Group: - This field is one of the parameter
to determine revenue
G/L A/c while posting invoice
values into accounting.
Item category group: - This field is one of the parameter to determine item category in sales document.
·
Header item – ERLA
o Header item – LUMF
Pricing Reference material: -
If pricing is same for multiple products then instead of maintaining pricing
for all the products we maintain
pricing for one material and that material we assign it as pricing reference
material for other materials.
No comments:
Post a Comment