QNR For SAP SD

1 SD ORG Structures
 What are Legal entities in SAP SD process

 Selling entities (Sales organisation)
 Product line (divisions)
 Medium of sales (distribution channel)
 Number of Sales offices and responsible area of selling
 Grouping of sales employees (sales groups)
 How many manufacturing facilities do you have? (plants)
 Number of dispatching locations (delivering plant/ storage location)
 How many dispatching points in each plant– shipping points
2 Masters
Customer master
 How do you group your customers account wise
 What types of business partners do you have (Ordering

/shipping/payer/billing/sales personnel/ sales employee), If multiple
partners are there then elaborate the scenario
 Do your customers agree for partial delivery? Do you have concept of
delivery priority?
 Do you have POD concept?
 What are the payment terms?
 Do you have credit limit to customers? What type of credit limits
Pricing
 How do you price your product (pricing components involved in pricing the
product)
 Do you maintain pricing records for the products? (customer / material specific)
Material Master
Do you have different UOM for selling and SKU?
Material Types for Finish material
3 Sales process
Pre-Sales activities
What type of pre-sales activities do you have? (Inquiry /Quotation)

Sales activities
 What types of order processing do you have? (domestic/ export)
 Explain in detail order scenario
 Whether order is created with ref to quotation/ inquiry?
 How do you receive order (FAX/Mail/S Rep/Telephone)?
 Do you have multiple ship to party for single order?
 What all information do you capture at SO level? Which are mandatory to
complete the order?
 Do you want to save the incomplete SO?
 What reason would an order or line item be rejected?

Free Goods
 Do you have the concept of free goods (inclusive and exclusive)

Bills of material
 Do you have a products based on components (Laptop and charger/bag etc)
Delivery Processing
 Do you maintain factory calendar for Plant and dispatching point
 Do you have single dispatching points for all plants or plant specific?
Billing and Invoicing
 Do you combine multiple deliveries in single invoice?
 Do you utilize periodic billing by for rental
 Do you utilize milestone billing ?
 How you are processing the incorrect invoices (Cancelling/correction/ cr/dr
memo)
Consignment
 Do you have consignment process?
Rush/ Cash orders

 Do you have scenario of cash / rush sales?
 Are they regular or one time customer?
 Do you want to book the revenue directly to petty cash or cash clearing?

4 Complaint process

Physical Returns
 Explain the return process
7 Third Party
 Do you sell goods that you purchase from a vendor? Are these materials always
purchased or just on certain orders?

8 Inter Company Stock Transfer
 What is the process of stock transfer?
 Do you bill inter company stock transfer?

9 Stock Transfer
 What is the process of stock transfer

10 Reports and forms
Forms
 Quotation
 Proforma invoice
 Sales order acknowledgement
 Delivery note
 Picking/Packing list
 Invoice
Reports
 SO list
 Pending SO’s
 Price report
 Delivery Monitor

Types of Projects:
SAP :
SI : System Integration
*****Greenfield Implementation Project

*****Roll out project (Global template)
*****Upgrade project
AMS:
Support Project.
Phase of ASAP Methodology
ASAP focuses on tools and training, wrapped up in a five-phase process oriented road map
for guiding implementation.
The road map is composed of five well-known consecutive phases

• Phase 1 Project Preparation
• Phase 2 Business Blueprint
• Phase 3 Realization
• Phase 4 Final Preparation
• Phase 5 Go-Live and support
Brief explanation of each phase
ASAP Methodology – Phase 1 : Project Preparation
Phase-1 initiates with a retrieval of information and resources. It is an important time to
assemble the necessary components for the implementation. Some important milestones
that need to be accomplished for phase 1 include
• Obtaining senior-level management/stakeholder support
• Identifying clear project objectives
• Architect an efficient decision-making process
• Creating an environment suitable for change and re-engineering
• Building a qualified and capable project team.
ASAP Methodology – Phase 2- Business Blueprint
SAP has defined a business blueprint phase to help extract pertinent information about your
company that is necessary for implementation. These blueprints are in the form of
questionnaires that are designed to probe for information that uncovers how your company
does business. As such, they also serve to document the implementation.
ASAP Methodology – Phase- 3 – Realization
With the completion of the business in phase 2, “functional” experts are now ready to begin
configuring SAP.
The Realization phase is broken in to two parts.
1) 1) Your SAP consulting team helps you configure your baseline system, called the baseline
configuration.
1) 2) Your implementation project team fine-tunes that system to meet all your business and
process requirements as part of the fine tuning configuration.
Configuration Testing-
With the help of your SAP consulting team, you segregate your business processes into
cycles of related business flows. The cycles serve as independent units that enable you to
test specific parts of the business process. You can also work through configuring the SAP
implementation guide (IMG). A tool used to assist you in configuring your SAP system in a
step by step manner.
Testing :
FUT : Functional unit test
SIT : System Integration testing
UAT : User Acceptance testing
Regression testing
ASAP Methodology – Phase 4 – Final Preparation

Workload testing (including peak volume, daily load, and other forms of stress testing), and
integration or functional testing are conducted to ensure the accuracy of your data and
the stability of your SAP system. Because you should have begun testing back in phase 2,
you do not have too far to go until Go-live.
ASAP Methodology – Phase 5 – Go-live and Support
The Go-live milestone is itself is easy to achieve; a smooth and uneventful Go-live is another
matter altogether..
WRICEF Implementation >>> FSD document created
W-Workflow
R-Report
I -Interface
C-Customization
E-Enhancement
F-FORM
Introduction of functional specification

When approaching software development businesses with a project in hand, it’s a good idea to make a
list of all requirements. Development teams use it to create a rough estimate of the project and then,
once it’s launched for analysis, to identify all needs.
What is a functional specification?
A functional specification is a blueprint that helps the development team understand how an
application will work, and it describes the user experience step-by-step.SAP Development
incorporates a number of WRICEF solutions. In SAP implementation projects, custom developments
are made.
Objective of Functional Specification
Assumptions
Any assumptions made in the preparation of this document that could prove crucial to the success or
failure of the System should be documented. This could include legislative changes, changes in work
practices, changes in technical capabilities for hardware and/or software, etc.
Functional description
Testing scenarios
Input and Out Parameters

QNR For SAP SD

Uploaded by

Copyright:

Available Formats

QNR For SAP SD

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

QNR For SAP SD

Uploaded by

Copyright:

Available Formats

1 SD ORG Structures

 What are Legal entities in SAP SD process

 What types of business partners do you have (Ordering

Rush/ Cash orders

*****Greenfield Implementation Project

The road map is composed of five well-known consecutive phases

ASAP Methodology – Phase 4 – Final Preparation

WRICEF Implementation >>> FSD document created

Introduction of functional specification

What is a functional specification?

Objective of Functional Specification

You might also like