SD Questions on Corporate Structure

In R/3 you can represent a company's structure by defining and assigning corporate structure elements. What is the purpose of
doing that? Enterprise organization diagram. Chart showing the organizational structure of an enterprise, its organization units and how
they are related. A combined structure can be created from the point of view of accounting, MM, SD. This structure forms a framework in
which all business transactions can be processed.
Which three organizational elements make up a sales area and briefly explain their function?
Sales organization: An organizational unit that sells and distributes products, negotiates terms of sale, and is responsible for these
transactions.
Distribution channel: Channel through which salable materials or services reach customers. Typical distribution channels include
wholesale, retail and direct sales. You can assign a distribution channel to one or more sales organizations.
Division: Product groups can be defined for a wide-ranging spectrum of products. For every division you can make customer-specific
agreements on, for example, partial deliveries, pricing and terms of payment. Within a division you can carry out statistical analyses or set
up separate marketing.
Name the three internal organizational elements within a sales organization and briefly explain their function.
Sales Office. Geographical aspects of the organization in business development and sales are defined using the term sales office. A sales
office can be considered as a subsidiary.
Sales offices are assigned to sales areas. If you enter a sales order for a sales office within a certain sales area, the sales office must be
assigned to that area.
Sales Group. The staff of a sales office may be subdivided into sales groups. For example, sales groups can be defined for individual
divisions.
Salespersons. Individual personnel master records are used to manage data about salespersons. You can assign a sales person to a sales
group in the personnel master record.
What does the term "business area" refer to and how can it be used?
Business Area. The system posts costs and revenue according to the business area. The business area can be equivalent to the:
- sales area (if the accounts are to be posted according to sales)
- plant/division (if the accounts are to be posted according to products)
The business area is defined in Customizing for Sales.
o Business area. A unit in an enterprise, grouping product and market combinations as homogeneously as possible for the purpose of
developing unified business policy.
o Financial Accounting (FI). A business area is an organizational unit within financial accounting which represents a separate area of
operations or responsibilities within an organization. Financial accounting transactions can be allocated to a specific business area.
Briefly explain the relationship between sales organizations and company codes.
Many to One.
What is the central organizational element in purchasing?
Purchasing Organization.
Explain the relationship between sales organizations and plants.
Many to Many.
Explain the relationship between sales organizations, plants and company codes.
Many to Many to One.

Can one business area be assigned to several company codes? Which (sub) module of SAP could make business areas obsolete?
Yes in CO .
What is a credit control area? What relationship exists between credit control areas and company codes?
Credit control area. Organizational unit in an organization that specifies and checks credit limits for customers. A credit control area can
include one or more company codes. It is not possible to assign a company code to more than one credit control areas.
Which organizational element is central in shipping? Give a definition of it.
Shipping Point: Organizational unit at a fixed location that carries out shipping activities. A shipping point could, for example, be a
company's mail department or a plant's rail depot. Each delivery is processed by only one shipping point.
Give a definition of plant (in SAP).
Organizational unit within Logistics, serving to subdivide an enterprise according to production, procurement, maintenance, and materials
planning aspects.
A plant is a place where either materials are produced or goods and services provided.
Classification: Business object
Structure: A plant can assume a variety of roles:
As a maintenance plant, it includes the maintenance objects that are spatially located within this plant. The maintenance tasks that are to be
performed are specified within a maintenance planning plant.
As a retail or wholesale site, it makes merchandise available for distribution and sale.
As a rule, the plant is the organizational unit for material valuation.
The preferred shipping point for a plant is defined as the default shipping point, which depends on the shipping condition and the loading
condition.
For the placement of materials in storage (stock put-away), a storage location is assigned to a plant. The storage location depends on the
storage condition and the stock placement situation.
The business area that is responsible for a valuation area is determined as a function of the division. As a rule, a valuation area corresponds
to a plant.
Can you assign two different sales organization to the same company code?
Yes.
To what do you assign distribution channels and divisions?
Sales Organizations.
What are the highest organizational units in SD, MM.PP,FI,CO?
SD: Sales Organizations.
M: Plant
PP: Plant
FI: Company Code
CO: Controlling Area

Can you further subdivide a plant? If yes into what?

A plant can be subdivided into storage locations, allowing stocks of materials to be broken down according to predefined criteria (e.g.,
location and materials planning aspects).

A plant can be subdivided into locations and operational areas. Subdivision into locations takes geographical criteria into account, whereas
subdivision into operational areas reflects responsibilities for production.
Can a sales organization sell from a plant belonging to a different company code?
Yes.
How many shipping points can you assign to a plant?
Many.
How many shipping points can you assign to a sales organization?
None.
If you have a warehouse management system active, to what would you assign the warehouse number?
Plant & Storage Location.
1. What is the purpose of text determination, account determination, partner determination, output determination,storagelocation
determination
Answer1:
Text determination: For transferring information from material or customer to order/delvery or invoice (and anything inbetween)
Account determination: For transferring financial and costing information to proper financial docs
Partner determination: For determing who is is legally resposible for A/r, who the goods are going to and whatever else you waana drive
through this functionality.
Output determination: What kinda output does a sales/delivery/billing document create and who gets it, where?. For example A partner
might get an EDI notification for a sales order just confirmed, whereas a financial/leasing company gets the invoice!
Answer2:
(a) Text Determination: Any Texts in Masterial Master/Material Determination/Order/Delivery , etc is meant to convey messages to the
subsequent documents for compliance. e.g. "Give Top Priority" message mentioned in Order is meant for Production Dept. (b) Account
Determination:is integration between Finance and SD. The A/P along with Account Keys need to be allocated accordingly with
combination of Account Determination Group for Customer and Material if required. (c) Partner Determination:To identify which type of
Partner it is so that if required for same Customer different Partner Functions may be required e.g Only One Sold To Party per Customer.
More than One Ship to Party/ Bill to Party/ Payer possible. Accordingly different Masters will have to be created. Useful for despatch of
Material in casae of Ship to Party, sending Bill in case of Bill to Party and payment followup/Dunning in case of Payer. (d) Output
Determination: What type of Output (Fax/Mail, etc) is required, where and in what Format(ABAP Customisation may be required in some
cases especially Invoices). (e) Storage Location Determination: depends on Plant, Shipping Point and Storage Conditions
8. What is the purpose of shipping point determination not menu path
So that Shipping Point is determined automatically once the settings for the same are done.

What is the difference between updated project and end to end project. please explain
Answer1:
Some organisations select to implement SAP module by module, thus gets updated as per their convenience / schedule. This is called as
updated project.
Some organisations simply plan all integrated functional modules and decide to go-live with all functional modules and take their entire
operations on SAP. This is called as End to End SAP implementation project.
Answer2:

Upgrade Project is a project where in SAP is already in place and it is the version upgrade from a lower end to a higher version.
End to End project is a project where SAP is implemented for the first time.
12. What is the difference between the Avaialbility check 01 (Daily requirement) and 02 (Individual Requirement) in material
master?
01 and 02 are the checking group. Availability check is carried out with the help of these checking group and checking rule. Checking
group 01 and 02 are maintained on the material master.
01 - Individual requirement -For this system generates transfers the requirement for each order to the MRP .So that MM can either produce
or procure.
02- Collective requirement.-In this all the requirements in aday or in a wek are processed at a time. System stores all req and passes on to
the MRP in MRP run.In this system performance is high however you can not do the backorder processing whereas in other you can do.
What is the difference between business area and profit center?
Answer1:
Business area is where the total business is valuated as a whole
Whereas Profit centre is an area where the company/work place allows the outside agency to use its machinery for external profits (eq: A
CNC machiine which can run 24 hrs a day is utilised in our company for 15 hrs and the balance 9 hrs is let out for addition to the
company's profit) is known as Profit Centre.
Answer2:
Business area is related term to FI module and Profit centre is related to CO module. One business area can have one or more profit
centres.
Answer3:
Business area is gared on external accounting where as profit centers are used for internal accounting purposes
11. What is purpose of maintaining common distribution channels and common divisions
Common Distribution Channel and Common Divison are maintained so that if any master data like customer or material maintained with
respect to one distribution channel can be used in other DCh. It prevents the multiplication of master records.
Eg: A customer is created for say sales area 1000/20/00 then the same customer can be used in sales area 1000/30/00 if we maintain 20 as
common distribution channel. Hence no need for extending the customers...the same for materials also.
4. What is meant by transfer of data from legacy code to sap Legacy Code ?
Answer1:
It should be legacy data to SAP. What it means is you want to transfer all the customer and materials and all other information from Older
(legacy system) to new SAP system. You can do it using many tools, most noticeably MDMs.

Answer2:
Before installation of SAP, Data maintained by Company is called Legacy Data. At the time of instalation, it is required to transfer Data
from Legacy to SAP like Masters (Material/Customer, etc). It can be done in various ways like BDC, LSMW, etc.
What is an Open Item in SAP? How will you find an Open Item in SAP?
you can generate a list of open items from the information systems menu option:
* General Ledger: Information system General ledger reports Line items General ledger line items G/L line items, list for
printing.
* Accounts Receivable: Information system
* Reports for accounts receivable Customer items List of customer open items for printing. Accounts Payable: Information system
Reports for accounts payable Vendor items List of vendor open items for printing.

ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external
systems. When a new enterprise resource planning (ERP) solution such as R/3 is implemented, companies have to interface the ERP
system with legacy systems or other ERP systems. ALE provides intelligent mechanisms whereby clients can achieve integration as well as
distribution of applications and data. ALE technology facilitates rapid application prototyping and application interface development, thus
reducing implementation time. The ALE components are inherently integrated with SAP applications and are robust, leading to a highly
reliable system. ALE comes with application distribution/integration scenarios as well as a set of tools, programs, data definitions, and
methodologies that you can easily configure to get an interface up and running.
Application layer. This layer provides ALE with an interface to R/3 to originate or receive messages containing data to or from external (or
other R/3) systems.
Distribution layer. The distribution layer filters and converts messages containing data based on predefined or custom-defined rule sets.
These conversions may occur to ensure compatibility between different releases of R/3 and R/2.
Communications layer. ALE communications are carried out both synchronously and asynchronously. Synchronous message transmissions
are typically used for the direct reading of control data, while asynchronous message transmissions are used for transmitting or receiving
application data. It is also possible to achieve a pseudo-real-time exchange of application data using transactional Remote Function Calls
(tRFC), which Ill detail later in this article series.
ALE scenarios fall into three categories: master data, transactional data, and control data distribution. Although the underlying principles
are the same for the different categories, there are differences in their functions and configurations. SAP delivers over 200 ALE scenarios;
and by extension there are approximately 200 application areas that can leverage ALE technology for data distribution or communication.
A subset of these scenarios is supported by R/3 for Electronic Data Interchange (EDI).
5. What do you do really in pricing determination, and what are the main deifferences between pricing procedures?
Answer1:
Pricing is determined by combination of Sales Organisation, Distribution Channel, Division, Customer Pricing Procedure and Document
Pricing Procedure.
Answer2:
We determine how the prices are calculated, taking into account sales area(sales org, distribution channel, division), document type and
customer(generally sold-to-party).
The main differences between pricing procedures would be the differences as we mentioned above, from the point of view of field entries.
Coming to the output and the procedure, Suppose the condition types used will be different and hence the following whole procedure. One
pricing procedure determination to the others, which data control these differences .
2. What are the five imp fields to be maintained in account determination
Account Determination: Sales View, Sales Organisation, Distribution Chanel, Chart of Accounts, Account Assignment Group for Customer
and Material and Account Keys.

9. What and where types of copy controls we change

Copy Control: is basically meant so that Data is copied from preceding Document to subsequent one. What subsequent Document is
required is to some extent determined by Customer Requirements as well as Document Types. e.g. In general case of Standard Order, it will
be Copy Control (Order to Delivery) from OR to LF .
We use clocking machine for recording employee clock-in/out ...
Q: We use clocking machine for recording employee clock-in/out . All the data is stored in a 'flat' file which is supposed to be uploaded into
SAP. When tried to open and read the flat file using OPEN DATASET and READ DATASET commands, the Sy-subrc value returned is 8
and the error message 'the specified file not found' is displayed. We checked the path and the file is in the correct location. What is missing?

A: Check the path once again. Check the upper and lower cases. Define you parameter file name like filename-fileextern. Depending on
the place where the flat file resides, the procedure varies. OPEN DATASET is used for upload of file from the host system. If your flat

(text) file is on the PC, you can use the function WS_UPLOAD which will upload your text file into an internal table. This internal table
data can be loaded into SAP. The syntax is as follows:
CALL FUNCTION 'WS_UPLOAD'
EXPORTING
FILENAME = pcfile
IMPORTING
FILELENGTH = fileleng
TABLES
DATA_TAB = internal table name
Please note that you have to specify the pcfile of length 128.
We are in the service industry and have employees working in multiple cities on the same day ....
Q: We are in the service industry and have employees working in multiple cities on the same day. The system seems to allow one taxing
authority per day. But the taxing authority needs to be picked up from the Service Order ideally . Can we achieve this?
A: You can create multiple infotypes 0208 (work tax area) for the same employee and the same day. Use the 'allocation percent' field .
There is no integration however between time management and the work tax area. You may copy infotype 0208 to IT 9208. Infotype 0208
may be used to store the default work tax area and IT 9208 may be used to store the multiple work tax area. Create IT 9208 based on data
from your external time management system.
Explain what are the steps in the SD process at least up to the invoicing stage
Answer1:
1) pre-sales activity -inquiry,quotation
2) sales-order,
3) inventory sourcing,
4) delivery,
5) pgi,
6) invoicing
Answet2:
SD Inquiry-- Quotation---Sales Order---Delivery---Transfer Order----Post Good Issue----Billing---Invoicing.
How do you get the Sales Order (S.O) No. from the Delivery Order?
There are 2 ways through which you can see the reference of the documents.
1) Through Document Flow
2)Enter the delivery-> Go at the item level and select TAB PREDECESSOR DATA tab and you can see the reference order number.

How the Price determination process works in SAP-MM?

Price determination process:
Create a Price schema
Add a condition type if required
Asssign Access sequence to the condition type.
Create a condition table and specify flds required.
Create a cond. rec. The price schema for the particular mat. has a cond type. This pricing will trigger the Price determination process.
Basically the access sequence assigned to the cond type will search the cond table to find the particular cond. rec. and determin the price.
10. How to and where to maintain copy controls
Check for yourself in IMG (Sales Document types and Delivery Document Types)
Condition technique

condition technique means, the combination of

- condition table
- access sequence
- conditon type
- procedure
- determination

RLT is the time taken to produce or bring material from out side.it is based on planned delivery time and inhouse
production time - it will not be implemented but it will there in MRP views in MMR as a part of master data.
this is concept of Production Planning & control Module.
its a part of master data of MMR.
RLT is the sum of
"Purchase Department processing time + Planned delivery time (by vendor) + GR Processing time.
The same concept holds good for the In-house production of a material.

Please choose the correct statements from following SAP SD Certification Sample Questions :

A. By availability check, you can come to know about material availability.

E. The availability is checked on the material availability check.
G. During sales order, you CAN overwrite the plant.
H. Delivering plant on the material master is found in Sales : Sales ord. tab.
K. Complete delivery or Partial delivery preferences AFFECT availability check results.
N. The system firstly carries out delivery scheduling (backward) based on the customer's requested delivery date and determines
the material availability date. After this, it runs availability check for this date.
O. Availability check is done at Plant level. You can also at check other plant level.M. Availability check includes current stock,
planned inward movements, Forecast outward movements.
Q. If quantity of an order item is not totally confirmed then an order item is backdated.
R. If the requested delivery date for an order item cannot be kept then an order item is backdated.
V. By selecting appropriate option, you can include storage locations in the availability check.T. MAD date must be determined by
system before carrying out availability check.
Availability check
1. Availability check is an integral part of the business process that determines if the required delivery quantity can be met on a required
delivery date. For this purpose the system takes into account pre-delivery activities such as scheduling for picking or packing times and the
time taken to produce or obtain the material. It also performs several background functions such as
2. Backorder processing, rescheduling and ATP quantities.
Backorder processing: processing of a sales order that has not been fully confirmed or not confirmed at a certain delivery date.
3. Rescheduling: is a proposal of how confirmed quantities already assigned to a sales order can be reassigned to other sales orders that
have a higher priority.
4. Available to promise (ATP): is a process of checking the available quantities of a material. The ATP quantity consists of warehouse stock
+ planned receipts (incoming stock) planned issues (outgoing stock). to examine stock on hand (CO09) proceed to logistics sales &
distribution sales environment availability overview.
5. Replenishment lead time (RLT): is the time taken for the material to become available either internally (in house production) or
externally (from a vendor). The most important things to consider during an external procurement are purchasing and MRP2 (procurement)
views of MMR where the processing time for purchasing, planned delivery time and goods receipt processing time are taken into account.
On the other hand internal procurement is based on in house production time (MRP 2 view) goods receipt processing time or alternatively
RLT time, which is found on MRP 3 view.
6. RLT (Replenishment Lead Time) is the time taken for the material to become available. RLT is only used when doing an ATP check
(Available To Promise). The value of RLT for a material is specified on material master record.

7. There are three types of availability checks

Check on basis of ATP quantities.

Check against product allocation.
Check against planning.
Configuring Availability check through Checking Groups
1. The checking group + checking rule determine how the availability check is to be performed.
2. The checking group determines whether and how the system checks the stock availability and generates requirements for
material planning. The checking group defines what type of requirements will be passed on i.e. summarized requirements
(daily/weekly) or individual requirements for each sales order.
3. The checking rule applies to how the availability check is to be carried out at the transaction level. Note that you must define
checking rules for each individual application such as for production orders for example. In Sales and Distribution, the checking
rule is specified internally within the system and cannot be changed.
4. The checking rule, in conjunction with the checking group, determines the scope of the availability check for every business
operation; that is, which stocks, receipts and issues are to be included in the availability check and whether the check is to be
carried out with or without the replenishment lead time.
5. Briefly explaining the above checking group determines which type of requirement to be passed on to MRP whether it be
individual or summarized and checking rule which is at the transaction level and can be configured independently for each
application module, determines which stocks, receipts and issues to be taken into account. For performing an availability check
checking group has to work in conjunction with checking rule.
6. Advantages of individual processing over summarized processing
Backorder processing is possible.
You can access (MD04) order, line and schedule line individually which gives a greater control on available stock and
requirements placed on stock.
The system automatically uses individual requirements in case of special stock items.
7. Required data for the Availability check to be carried out
The Availability check must be switched on at the requirement class level.
The Availability check must be set at the schedule line level.
A requirements type must exist by which the requirements class can be found.
A plant must be defined in the sales order for each schedule line item (in other words plant must be defined for every material in
MMR).
A checking group must be defined in the material master record in the MRP3 screen in the availability check field.
8. Configuring Availability check and defining Checking Groups
Checking groups are introduced into the sales order based on the setting in the material master record.
SAP standard checking groups are 01 summarized requirements and 02 individual requirements or you can create your own by
copying the standard ones.
Total sales and total deliveries columns are there to configure a checking rule to sum up requirements to post to MRP either
individually or by day or week.
Block quantity required can be set if you want several users to be able to process the material simultaneously in different
transactions without blocking each other.
The no check indicator is CHECKED when you DO NOT want the system to carry out ATP check.
9. Defining material block for other users the block check box is an indicator that enables you to block material master records
of a particular material during the availability check and restrict other users from accessing same master record and reserve the
material. If the block is not set, two users can confirm the same material at the same time for two different orders, not knowing if
the stock is available or not. If you select this field, the material is blocked during the availability check and other users cannot: a)
Make changes in the material master record. b) Create purchase orders for the material. C) Create orders for the material.
10.Defining default values for checking groups - Checking groups are introduced into the sales order based on the setting in the

material master record.

However if there is no entry present in the material master record for the checking group, a default value can be set here,
depending on material type and plant.
This default value will be used by the system depending on the material type mentioned in MMR and plant in sales order.
If an entry exists, this default value is over written by MMR.
11.Controlling Availability Check in this section, you tell the system what stock on hand and what inward and outward
movements of stock it must take into account when performing the availability check in addition to whether or not to consider the
replenishment lead time.
12.These settings are based on the checking group that is assigned to the material master record and the checking rule that is
predefined and assigned to the sales and distribution transaction.
13.These settings carry out control both for sales order and delivery as well. This is due to the fact that you may want to include
specific stock or incoming stock for the sales order, yet at the time of the delivery only include physical stock on hand waiting to
be shipped.
14.It is possible to indicate to the system that you would like the availability check NOT TO CHECK the stock at the storage
location level. This indicator is used to set the scope of the availability check.
15.It is used to switch off the check at storage location level. You create a reservation for a particular storage location. However,
the scope of the availability check is set in such a way as to exclude the storage location. In this case, the system carries out the
check at plant level only and does not take the storage location into account that is specified in the reservation.
16.Should you not want the system to automatically check RLT, you may indicate so here. RLT is the time taken for a material to
become available. It is only used when doing an ATP check and is taken from MMR.
17.defining the elements in the availability check entirely depends on the business needs, but a few tips are given under
When controlling the Availability check at the time of the sales order, a purchase requisition does not necessarily indicate by it is
going to come into the plant.
A shipping notification on the other hand - a confirmed purchase order is a good indicator of receiving stock on a specified date.
It is always recommended not to select the shipping notifications for the delivery requirements type as you may not actually
receive the stock into plant or warehouse for which you are creating a delivery.

SAP Sales and Distribution Frequently Asked Question

Master Data
Q: Some materials have been blocked for procurement and production. Even though deletion flag is set for a material/plant level, the order
can be still entered ( with a warning message). Is there a way to block such transactions for a material flagged for deletion?
A: Sales Status field in the sales organization view of the material master may be used to block any transaction for the material.

Q: We can define our own exchange rate types and use them instead of the defaulted types, 'M', 'B' and 'G'. How can we overwrite default
types in SD?
A: Exchange rate gets copied from the customer master record. Exchange rate types are to be maintained for the customer in the sales
screen of the customer master record.

Shipping
Q: The PL00 condition is fine in delivery. But when we try to print to either the screen or printer, an error V1032 occurs. Why?
A: In order to use the Packing list PL00 (packing slip in delivery) you must do 'Packing' in the delivery note (edit->packing)

Q: we have to enter a shipping point while creating a delivery. Is it possible to create delivery without shipping points?

A: When you are releasing a sales order, choose Sales document -> Subsequent functions-> Create delivery, then the shipping point will be
brought in from the sales order. In all other scenarios you have to key in the shipping point. The above described scenario will only work if
all items on the sales order are to be shipped from the same shipping point.

Billing
Q: SAP allows a non-inventory item and an inventory item to be in the same document till delivery but splits at the time of creation of
billing document. Can we combine a non-inventory item with an inventory item in one invoice? Can we treat it as a value item in sales
order so that it is priced and then make it as a text item in delivery documents so that it appears in the same invoice and does not split?
A1: Make the non-stock material deliverable, but not pickable. Both items will carry into the delivery, and therefore appear on the same
invoice.
A2: Change the copy rule for orders->invoices and deliveries->invoices to specify that invoice combination is permitted. However note
that for system to create combined invoices, PO number, payment terms, sales organization, and distribution channel must be identical.
Else undesirable combinations may be created by the system.

Pricing Conditions
Q: It is impossible to price at the material level (matnr) , when a material has a pricing reference (mvke-pmatn) set up against it in the
master data. Pricing always look for the pref, even if a price is set up against the material and not the pref. How can we price by material
and pref?
A: The field used to look up at the price is defined in Access sequence. You may find a step with PMATN as material number. If you insert
a step with MATNR then the system will first look for the material, if not found (use the exclusion tick box) it will look for the pref.

Customizing
Q: We generated a new condition table. Assigned the condition to access sequence. Created a condition record. Access sequence is
assigned to the output type. But when we create a billing document, output screen comes up blank for the output type. When we look up
Determination Analysis, we get an error "Note 524 Access not made (Initialized Field)". What else is required to be done?
A: Assign output determination procedure to the header of the document and the output type.
Q: How can we set up to have the VAT# be accepted in the Ship-To Master File Data Control screen?
A: IMG->Fin. Acct.->AR and AP ->Customer acct->Master Record -> Prepare to Create Customer-> Define Acct. Group.
Q: We want to explode Bill of Material automatically at time of Order entry and explode an Equipment BOM in the sales order. What are
the setting required?
A: Use an item category that is configured for bills of material for having a sales BOM to explode automatically.
Standard SAP item categories are :
TAQ - Pricing and inventory control take place at the BOM header level
TAP - Pricing and inventory control take place at the BOM item level
These can be automatically derived using the item category groups ERLA and LUMF, respectively.
Q: How can we make the Customer Group 1 (or 2, 3, 4, 5) a mandatory field?
A: Logistic General-> Logistics Basic Data: Business Partners -> Customers -> Control -> Define account groups and field selection for
customer
Choose Customer Acct. GR. (double-click). -> Field Status: Sales data (double click) -> sales (double click) .Check the radio button
against Customer Gr as REQ. ENTRY. Save the settings to make customer GR entry mandatory .
Q: Is there an user exit to copy the data into planning table?
A: Use user exit MCP20001 and include ZXSOPU01.

Others

Q: We get a report screen: "Goods issue: Problem Log" during the delivery process when activating Post Goods Issue button. We want to
include our own error message to this list if the selected batch is not on a customer defined table. What is the best way?
A: Try User exit - USEREXIT_SAVE_DOCUMENT_PREPARE
How can we define Sales Order (VA01) & Scheduling Agreement (VA31)?
to define the sales order go to transaction code vov8 and choose order type (oR) copy it and define ur own same like contracts choose order
type nms or sc
A sales order is defined as a document which contains the details of the customer (address etc) the materials to be delivered its price (along
with discounts applicable) the delivery date the customer has requested the material availability date or the schedule line date
organizational details such as sales org sales office etc. shipping point and inco terms among other details.
A schedule agreement is an agreement/contract between two plants under either the same company code or different company code which
basically contains a delivery schedule to supply an "X" quantitity of materials at specified regular intervals to a certain period.

Business Scenarios Main Elements

Business Scenario: Business-related grouping of business processes localized in a specific organizational area that share some similar
goals in an enterprise, such as purchasing, services, balance sheet preparation, production, personnel administration, and so on.
Organizational Unit: Organizational grouping of enterprise areas which, for legal reasons or for other specific business-related reasons or
purposes, are grouped together. Organizational units include legal company entities, sales offices, and profit centers.
Master Data: Data which is used long-term in the R/3 System for several business processes.
Examples include customers, materials, and vendors.
Transactions: Application programs which execute business processes in the R/3 System such as creating a customer order, posting an
incoming payment, or approving a leave request.
Document: A data record that is generated when a transaction is carried out.
Reports: Program which reads certain data elements and displays them in a list.
Organization levels in Procurement :

Client
Definition :

1. Client is a commercial , organizational unit within the R/3 system , with its own data ,masters records , and set of tables.
2. From a business perspective , the client forms a corporate group .
Some cool facts about the client :
1. Highest hierarchical level in SAP
2. All areas of an organization that are to be integrated into the SAP R/3 production system should be included under one client
3. There is a common set of rules in one client
Common tables
Common master files
Common databases
4. Standardized Data Across the client
A vendor number and name is common across the client
A customer is common across the client
A general ledger number and description is common across the client
A material number and description is common across the client
Company Code
Definition : Its the smallest organizational unit having independent accounting department within external accounting.
Some cool facts about the company code :
1. Balance sheet ,Profit loss statement s require by law are created at company code level.
2. We can create several company codes in one client in order to manage various separate legal entities.
3. To create a company code we can easily copy the standard one and then customized it.

Plant
Definition :
1. It is a logistic organizational unit that divides the enterprise from the perspective of production , procurement , plant maintenance and
material planning.
2. Its a manufacturing facility or branch within a company code.
Some cool facts about a plant :
1. When creating a plant just copy the standard plant which automatically make the entry in the plant table and all others depended tables .

Storage Location
Definition : Its the organizational unit which allows the differentiation of material stocks within a plant
Some cool facts about a storage location:
1. Inventory management at quantity basis in carried out at Storage location level in a plant.
2. A storage location cant exist without a plant.
3. One storage location can be assigned to only one plant.

So is it the end of the basic structure ?

The answer is nooooo . What do you do with a Television without cable connection? How do you see the channels? Till now the television
part is done. Now lets see what the cable part of it is. The cable which links the organizational units with the external word is Purchasing
organization with the help of Purchasing group.

Purchase Organization :
Definition: It is an organizational level which negotiates conditions of purchase with vendors for one or more plants
Some cool facts about a Purchasing Organization:

1. It is responsible for companys purchase requirement.

2. There are three types of Purchasing Organization.
Plant Specific : One Purchasing Organization is responsible for only one Plant.
Company Code specific : One Purchasing organization is responsible for whole the company as well as its all plants .
Cross-company code specific : One purchasing organization is responsible for one or more company codes and all theirs plants.
3. One purchasing organization can be assigned to one or more plants.
4. One plant can be assign to one or more Purchasing organizations.

Purchasing Group :
Definition : Its the key for buyer or group of buyers responsible for certain purchasing activities .
Some cool facts about Purchasing Group :
1. We do not assign a purchasing group to any purchasing organization .It enables us to use any purchasing group for any purchasing
organization .

BLUE PRINT :
The ASAP methodology adheres to a specific road map that addresses the following five general phases:

1. Project Preparation, in which the project team is identified and mobilized, the project standards are defined, and the project work
environment is set up;

2. Blueprint, in which the business processes are defined and the business blueprint document is designed;

3. Realization, in which the system is configured, knowledge transfer occurs, extensive unit testing is completed, and data mappings and
data requirements for migration are defined;

4. Final Preparation, in which final integration testing, stress testing, and conversion testing are conducted, and all end users are trained;
and

5. Go-Live and Support, in which the data is migrated from the legacy systems, the new system is activated, and post-implementation
support is provided.

ASAP incorporates standard design templates and accelerators covering every functional area within the system, as well as supporting all
implementation processes. Complementing the ASAP accelerators, the project manager can create a comprehensive project plan, covering
the overall project, project staffing plan, and each sub-process such as system testing, communication and data migration. Milestones are
set for every work path, and progress is carefully tracked by the project management team.

Effective Communication

Weekly update meetings ensure full communication between the project team, the client project team, and project management. These
meeting are used not only to update on project status, but also to identify any issues or risk areas that may threaten the project. By

identifying these problems early, they are more easily mitigated and resolved, reducing their impact on the project timeline.

Ensuring Quality and Mitigating Risk

Project quality is verified near the completion of each project phase. Using existing ASAP checklists, these quality checks ensure that all
tasks for the phase have been completed properly, that all relevant documentation has been kept, and that all tasks required to commence
the next phase of the project have been completed.

In addition to the specific project team, companies may use Quality Assurance reviews on all of its projects to ensure that experience
gained on other projects has been taken into account and that the optimum system design has been utilized.

1. Why we are maintaining separate pricing procedure for inter company sales and business processs.
2. What is the different between standard and inter company pricing procedure and what type condition type
we are using in this intercompany.
There are two simple reasons for making any Pricing Procedure in SAP SD Modules.
1) Business Reason. What are the pricing aspects or strategies you want to apply for the client requirement in order to sell their
goods or render services, is all about the reason for various pricing procedures.
Eg: Domestic sales pricing procedure,
- Export Pricing Procedure,
- A rebate pricing procedure or
- A High Discount oriented pricing Procedures.
- A repair pricing procedures.
You have your own conditions intended to few transactions only. Put all this conditions as a set defining your own Procedures. It may even
include special requirements and formulas applied for such Pricing Procedures.
2) A special pricing procedures, in order to facilitate added functionalities of SAP pricing architecture, we must define new
pricing procedure. SAP Standard programmes checks these special Indicators in-order to do some required functions.
As a example 1, you need to have a Pricing procedure for condition supplement inorder to use the condition supplements. The condition
supplement pricing procedure must be given in the condition type definitions (v/06) of the Pricing Condition where you need to
supplement, without which SAP SD Condtion Supplements functionality doesnt work.
As a example 2, you need to have a Pricing procedure for Inter Company Billing Conditions(IV01 & IV02) inorder to be active for Inter
Company Billing specific transactions. Thus make sure that, the procedure wouldnot apply for non-Inter company transactions.
Eg: KA0000 for Condition Supplement for KA00
- PR0000 for Condition Supplement for PR00
- ICAA01 for Inter-Company Billing
Here I would like to remind about a important field in pricing.

In V/08 of defining a new Pricing Procedure, in main screen, you have a field called TSPP (Transaction Specific Pricing Procedure). This
has to be ticked on for Intercompany Billings.
The SAP help reads for this field as Under:
Transaction-specific pricing procedure
Pricing procedure transaction-specific indicator
Before Release 4.0A, no special pricing procedures were used for intercompany billing and rebate credit memos, programs were just set
accordingly to deal with these situations. As of Release 4.0A you are offered greater flexibility in the form of the option to define special
pricing procedures for intercompany billing and rebate credit memos. For reasons of future compatability, you will still be able to use the
old program specifications. For this reason, you must set this indicator if you want to create a special pricing procedure. This is to prevent
the program settings being used.
This indicator is also used as of Release 4.0A to redetermine the condition class and the statistical condition indicator when copying from a
reference document.
Example:
You copy prices from a shipment document to the billing document. The prices should lead to a surcharge in the billing document. This is
guaranteed by the redetermination of the condition class in the pricing procedure.
Same case with Standard Pricing procedure or Inter Company Pricing Procedure.
This configuration is done when user request for new pricing condition type other than the standard ones provided by the system.
Screen to tcode VA01 - Create New Sales Order for customers
- Double Click the Item
- Then Click the Conditions Tabstrips

CAN SALES ORDER AND BILLING HAVE DIFFERENT PRICING :

Yes, can have 2 different pricing procedures
1. One for Sales Order
2. Another at the Billing
Let us take an example:
Generally in the Pharma industry this procedure is adopted becuase all the goods are batch price based.
1. In the Pharma Industry whenever the goods are manufactured it will done in a batch to keep track and price is fixed, I mean there will be
a Batch Master which has a certain price fixed for it. This Batch Master will have certain number of batches . These batches will have the
number series generated wither by internal or external generation depending upon the client requirement
2. So till all the batches are produced as per that particular Batch Master will have the same price. Like that there will n number of batches
will different different prices
3. So when you are preapring Sales Order you be only putting the tenative price for the goods that are sold

4. Then at the time of delivery we will be picking up the goods from different batches basing on the required delivery quantity and finally
we do the PGI.
5. This is called Delivery Based Pricing becuase your price for the goods will be determined at the time of the delivery as the goods picked
up from the different batches which have different prices. ( Mind it there will very less difference in the prices).
6. So at the time of Billing the Pricing Procedure behaves differently depending upon the differnent batches that are picked basing on the
batch determination.
7. So the prices which are detemined from different batches will be the actual prices at which the goods are billed to the customer along
with other condition that are applied as required.

DEFINE CONDITION TYPE :

V/05 - Condition Table for V/07
e.g. a business may no longer wants to have a sales discount based on the sales organization, customer group, and material,
but decided that the discount should be based on the sales organization, customer group and material group.
V/06 - Create new condition types by copying a similar conditions type and changing it according to your needs.

Double click on the condition type to change the control options

V/07 - Access Sequences for condition type

V/08 - Pricing Procedures for condition types.
The pricing procedure is also used in the account determination. This determines the general ledger accounts to which prices,
discounts and taxes must be posted.

Click on the Pricing Procedures e.g. PR0000 - Condition Supplements for PR00

Click Control - e.g. Tick Mdt if you want the condition type to be mandatory

o OV34 - Define account key

o OV35 - Assign account key

Actky - Revenue account

Accrls - Accruals account

OVKK - Determine which Pricing Procedures to use for which Condition Type.

PRICING RELEASE PROCEDURE :

Define Processing Status - SM30 -> V_T686E
You are free to design your own processing status flow.
e.g. from 01 -> 02 or
from 01 -> 02 -> 03

To convert the old Pricing Condition with the release status use program SD_MOVE_A004_TO_A304.
For the standard tables, the following pairs of condition tables are intended to be used:
old <> new VAKEY fields
A004 <> A304 VKORG + VTWEG + MATNR
A005 <> A305 VKORG + VTWEG + KUNNR + MATNR
A006 <> A306 VKORG + VTWEG + PLTYP + WAERK + MATNR
A007 <> A307 VKORG + VTWEG + (SPART) + KUNNR
For example, if you are using A005 > A305, you have to copy the program to ZSD_MOVE_A005_TO_A305 and amend the
program Source and Target table.
First test run by ticking both option. If you confirm that there are no errors, then run by unticking both options.
Be careful while executing the conversion program as it can erase all your existing pricing condition data.
Once the conversion is completed, you can activate the Customer/Material with release status :IMG -> Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control -> Define Access Sequences ->
Maintain Access Sequences
In VK12, you will be able to choose the new Customer/Material with the release status column per material.

For adding field into Field catalog:

I shall give an example. But you should first identify the field for Profit Center (Design ID) and then do as follows:
For example if you want to use field PSTYV (Sales document item category) that is included in structure KOMP (Pricing
Communication Item) as a key for a condition table.
When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.
Prerequisites:
For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG (Allowed Fields for
Condition Structures).
To solve the problem, proceed as follows:
1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short
text, you can use, for example, ZZ - sales document item category and as a field label, you can use the field labels of
PSTYV.Save, check and activate your entries.
2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:
Component Component type
ZZPSTYV ZZPSTYV
Save, check and activate the change you made.

3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because
structure KOMPAZ is included in both structures.
4. Call up Transaction SPRO. Navigate to Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control and execute
Define Condition Tables. Choose Conditions: Allowed fields and include ZZPSTYV as a new entry.
5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.
6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:
MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include
RV60AFZZ.
Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition
table.For header fields, use structure
KOMKAZ instead of structure KOMPAZ and USEREXIT_PRICING_PREPARE_TKOMK instead of
USEREXIT_PRICING_PREPARE_TKOMP.
For more information, see Transaction SPRO via the path Sales and Distribution -> System Modifications -> Create New
Fields (Using Condition
Technique) -> New Fields for Pricing and Note 21040.
For creating a condition Table:
1) There are almost all the regularly used Conditon Table predefined in the system from 001 to 500.
See what best you can use the Standard Tables to avoid further errors.
2) In case you should define the new condtion Table,
a) Goto TCode: V/03
b) Give a Table any number from 501-999
Press execute and reach to next screen.
c) Check up whether the field you are looking is already added in Field catalogue.
d) Double click on the fields you want to make a Table..one by one. Note that the sequence here is important in higher
hierarchical to lower..
Eample : Sales Org, DC, Division, Customer and then Material etc..,
e) After selecting, click on the Techincal View buttin (redone) and reach to next screen.
7) Check which key should be in header and which key should be footer. Use check and uncheck functionalities there..
<!--[if !vml]-->

<!--[endif]-->Once you are through with all the above steps ..click on generate button.

Check the Table is generated or not.

You can check it at V/04 or V/05 or in SE11.

DEFINITION OF FIELD IN PRICING PROCEDURE :

A. STEP
This indicates the number of step-in the procedure.
B. COUNTER
This is used to show a second ministep
C. CONDITION TYPE
This is the most important component in the pricing procedure. The rates are picked up from this element, on the basis of the
properties described.
D. DESCRIPTION
This forms the description of the condition type.
E. FROM
This is used to define the progression of the calculation and range of subtotals
F. TO
This is used to define the progression of the calculation and range of subtotals
G. MANUAL
This function enables to allow the condition type to be entered manually also apart from automatic pickup.
H. MANDATORY
This function identifies the conditions that are mandatory in the pricing procedure. The sales price is a mandatory condition
type.
I. STATISTICS
This can be used to represent the cost price of the material sold, generally used for study statistical impacts of price
J. PRINT
The activation of this function will enable the printing of the values and conditions to the document.
K. SUBTOTAL
A key is assigned from the drop down menu; this can be used by the system in other area like Sis for reporting purpose also
L. REQUIRMENT KEY
This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from
accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only
be accessed if the customer has a low risk credit.
M. ALTERNATE CALCULATION TYPE
This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition
technique. this can be used to calculate complex tax structures.
N. ALTERNATE CONDITION BASE VALUE.
The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for
the calculation of a value.
O. ACCOUNTS KEY
The account keys form part of account determination. These keys are used here to define the posting of the revenue

generated to respective account heads& to subsequent assignment to GL accounts.

PR00- ERL
K007/KA00- ERS.
KF00- ERF.& so On.
P. ACCRUAL KEY.
The accrual keys form part of account determination. These keys are used here to define the posting of the revenue generated
to respective account heads& to subsequent assignment to GL accounts and payment to respective parties.

1. What is the difference between customizing request and work bech request?
All the tasks related to Configurations will be under customising request and all the changes and Developments related to
ABAP will be under workbench request.To be more clear a Technical Consultant(ABAPer) will deal with Workbench Req
whereas a Functional Consultant will deal with Customising Requests.
2. How do you release change requests in your module and how often do you release them?
Before transporting a request from Development we will do the testing and then move it to quality to test it extensively.Once
we are sure or the end user is sure of the resultant output is the same as expected output we will move it to Production.There
is no such time frame.
5. Does functional module level configuration come under workbench request or customizing request?
Fucntional module leve configuration comes under Customising Request.
6. What is the landscape you are following? In which one do you prefer to test functional module level changes?
Development-Quality-Production.
Testing will be done in Development and Quality.

?? depends on your system architecture. Generally, you need at least a Development system, a QA
system and PROD. Often you need many more systems, data load, regression, ...etc
7.how will u transport from quality sever to prroduction server.
se09 is the transaction through which we will transport the request from dev to Quality or dev to Production by selecting the
transport request and then clicking on the lorry button to release it.To see the transport logs,select the transport request
number and click on the transport log option in the GO TO in the menu bar.

Rebate Agreement
1. Which agreement type I should consider, is this custmer rebate(0003), material rebate(0002) or Rebate on the basis of sales
volume(0005), because here client is not offering rebate on Sales volume in rupees or dollar. He is only concerned with totat sales in
kiloleter(Quantity). As per rebate agreement concern rebate is offered in percentage. Please guide me for my scenario.
If your distributors are fewer (far less than 900 materials) then you should go for only customer rebate.
2. Guide me for conditions types and scale basis for maintaining condition records.
When creating customer rebates (T:VB01) select customer rebate, there you will see a header tab: Conditions , click it add how many
customers you want. For each customer you can create scale based conditions (under the heading tab :Scales).
3. Is it necesary to maintain condition record for every material and every customer defining the scale? Because in this scennario
client is going for incentives scheme for each material and each customer (distrbutor).
No need to create condition record for every material if you create customer rebate.
Customer Master
How to create the customer master?
The following are the T-codes for central creation of customer master.
XD01
XD02
XD03

Create Customer (Centrally)

Change Customer (Centrally)
Display Customer (Centrally)

XD04
XD05
XD06
XD07
XD99
XDN1

Customer Changes (Centrally)

Block customer (centrally)
Mark customer for deletion (centr.)
Change Customer Account Group
Customer master mass maintenance
Maintain Number Ranges (Customer)

You need to identify various parameters within each Account group based on which the reco account is identified within the customer
master.
Customer master is basically divided into 3 tabs.
- General - General master details, Juristiction codes, Region, Transportation zone, export data, etc.
- Company data - payment terms, account management, reco account, insurance etc.
- Sales data - Sales product attributes, sales office, sales group, customer pricing procedure, Cust. Statistical grp,
- Shipping data
- Billing data
- Partner functions.
You can create a customer based on 3 views:
1. For Account purpose
FD01/FD02/FD03 etc
2. Sales purpose
XD01/XD02/XD03 etc.
3. Centrally
VD01/VD02/VD03 etc.
What is the Function of item category and item category group?
Item Category determines the processing of any Item/material that we enter in a sales order and in this way it also effects the procesing of
any sales doc in which it is used.
Item Category Group is one of the component which along with the Sales Doc Type, The Item Usage and Higher Level Item Category
decide about the Item Category in a sales doc.
1. How can we know whether the customer is one-time or regular?
One can maintain Account Group for One-time customers. By which we can identify one-time customers.
2. What happens when you do not enter a value for a manual and mandatory condition type?
The pricing procedure will reject the conditions in the sales order
3. Do header condition type have an access sequence?
No
4. Org structure:
Relation between Company - Sales org
One-to-Many
Sales Org - Plants & company vs. Plants
Company - sales org - credit control area
What are sales area and its components?
Sales area consists of Sales Organisation, Distribution Channel and Division.
5. What are legacy systems?
The Existing system on which current system is working, from which the current system will be migrated to SAP system
6. What is cut over strategy?

Cutover strategy depends upon how the organizations design their data load strategies. Normally, you decide the sequence of Data loads for
Configuration settings, Master data, Transaction data which follows whom and then you make a copy of the system as a Production
system a day before and after checking the successful data loads, you go-live 100% or partial again depending upon organizational setup
and policies.
Cutover planning is highly site specific. There's no thumb rule. The stock data as on the date of going live should be correctly entered. But
stock being a highly dynamic quantity, the strategy for loading should be crystal clear. Then you have to load all the back dated transaction
on the stock. Some stock comes into your plant/storage location as return and some stock is actually delivered to your customer through
sales orders of various kinds.
7. What are Cumulative Condition Records?
There is a field:- "condition update" during configuration for a condition type (at v/06)... has it anything to do with cumulative condn.
Records?
8. IF you have 3 different access sequences for one condition record then in a pricing procedure in what hierarchy will you
maintain the three accesses?
In Condition Records (T Code VK11), you would be putting values to corresponding Condition Types. Now one Condition Type can be
assigned to one access sequence. In Access Sequence, you can assign whichever tables and fields are required.
So in my opinion, you cannot have one condition record for 3 access sequences.
9. What happens in the access sequence when you put all the ticks in the exclusive field?
When you put tick in exclusive field of all access sequences, in my opinion, it will try to get available data from the first. Only in case, data
is not available, will it move on to the next one.
10. What is meant by delivery group?
Delivery Group is basically grouping all individual deliveries for Billing. It should have the same Ship to Party, Shipping Point, etc.
11. What triggers the automatic creation of PR or PO in case of third party sales?
In item category we can set "automatic PO" so that PO and PR will automatically generate after saving the order.
You never change the item category configuration to "automatic PO". It is the schedule line category type which triggers the automatic PR
creation.
12. What are the steps that are required to include sales person as a partner function in the partner determination?
Partner function sales represenative or person responsible these two we can add through partner funtion in partner procedure.
13. What is z transaction?
We copied standard TC or object and rename it by Z its basically stnd name which will start from Z (User defined)
14. Can you create sales order for 40 items if the quotation is sent for 30 items?
Yes.
15. What is the importance of requirment field in access sequence?
System will not go to asscess condition type system will reply through formula.
16. What makes the immediate delivery in cash sales?
Order type immediate delivery switch on.
1. What is change request and task? What was your task no.? I need an example or a task no. that is being
used in your project to clear few things in my mind?

The Change Request is that request when you do some thing new in customizing or configuration in the system. The system will
automatically pop with the change request pop box , when you can give request name as defined by the system or can give your own
request name with heading of what changes you have made while customization. The system will generate a request number and you save
it. (e.g.:- VEDK-2785467) VEDK- means the Clients System name then followed by the system generated request number.
Now when you want to release the request you have to use the T-code SE10 where you can see the requests under the heading modifiable
or released. Go to the modifiable option. Each request will have again an internal request number. First you have to release the internal
request and then release the external request number. This will in turn released by the basis guys thru the T-code SM64 in a group when all
the requests are pooled from different users.
The task which you have mentioned in your question is nothing but the what task you have performed while customizing the client system
and the heading name which have given it for that task and generated a request for that task.
2. What is your client Number in the project? Like how we have 800 for IDES?
Generally like IDES client, when you are in the project, the client is also given a number called client number. So while implementing a
project The entire implementation is done under phases and in different Client no Servers.
e.g.:-take a company called ABC which is implementing SAP.
So the Client is given a number in the following manner by the SAP Implementers at the site
291- Sand Box server (Initial Testing scenarios Server)
292- Development Sever (With client data of minimum 15 days transactions)
294- Testing Server (the scenarios developed in development server is tested here)
295- Golden Master Server (Quality cum Testing Server) - checked finally before transferring to production server
296- Production Server (where the clients live data is stored and daily business transactions are done)
3. Few client requirements for customer master, material master, Organization and Transactions.
The client requirements may be in the form of customized reports and queries which are supposed to be suited according to their business
process. Generally the requirements would be coming from the BPO's (Business Process Owners) who will deputed for each module e.g.:SD, PP QM FI) by the client as they would be expert in their areas and module who under the business processes as they clients Project
Team members. They are whole and sole responsible to get the implementation done and meet the requirements raised by them and the
other users from the clients side.
Generally before starting the implementation the entire organization structure and the organizational elements are freezed and a skeleton
structure is prepared and then along with BPO's requirements the system is 1st configured and then the customization is started to suit the
Clients specified requirements.
Now as far as the transactions are concerned not all the users are allowed to run all the transactions. Here the user roles are defined as per
the BPO's (i.e., the user is given authorization only to run certain transactions depending on the levels and stages in his area of
specialization like in SD module the entry level user is only allowed to enter the data like creation of Sales orders or delivery and billing
and the next level is give the authorization for changes to be made for that same data that is entered by the entry level users. The next
higher level -Supervisor is given a few more transaction authorization which will be above these mentioned users)
Here the reports are segregated like Higher Management Reports, Middle Management Reports where by again authorization is given those
heads(Head of the Depts. or the Plants heads or GM etc.,) to run certain transactions which allow to view reports that are needed daily by
the management.
4. How to restrict users for not changing some fields in T-code va02?
There are two ways to do this:
- Make a transaction variant thru SHD0 and assign it to your sales doc. While creating the variant you can place non-changeability ticks on
specific fields. Next allow those users only to work with your transaction variant but not with the original transaction.
- You could make use of user-exit FORM USEREXIT_FIELD_MODIFICATION in include MV45AFZZ (via authorization objects, which
you can assign in role customizing).
The latter is more flexible but it is not feasible if you want to place restrictions to a large amount of fields. *-- Sabir
5. How can we delete the Sales Orders?
How can an invoices be cancelled or deleted?

You can very well delete sales order using transaction VA02, but with a constraint that no subsequent document is created against it.
Invoice can be cancelled using T cose VF11 and then you can reverse the Goods Issue using VL09 and making the picking quantity zero in
the deivery document and delete the delivery order using VL02n . You can then delete the sales order then.
*-- Vaibhav
You cannot delete an Invoice. You can only cancel it with (VF11) if the relevant accounting document is not been generated. Ask your FI
guy to reverse the accounting doc. Only after the accounting doc is reversed and/or deleted, you can cancel your invoice. You also need to
check if any TAX documents are generated with your Invoice. You need to reverse/delete those documents also
In a Sap implementation, various methodologies are used. One among them is ASAP methodology which stands for Accelerated SAP.
ASAP methodology consists of the phases in SAP implementation. It starts with 1.Project Preparation then 2. Business blue print 3.
Realisation(Customization and configuration) 4.Final preparation and 5.Going live. All this phases put together are called one
implementation cycle.
end-to-end implemention is nothing but
project reporting
business bule print
realization
finalisation
go live/support
What is the difference between task and change request?
Basically, a change request is a transportable object, usually
containing one or more tasks. Take a look at the tree structure
in SE09, then expand the object list for a task.
Difference between Tcode MB1A, MB1B, MBIC
Can any body let me know what is the difference between all the three...
1. Mb1a - Enter Goods issue..
2. Mb1b - Transfer Posting..
3. Mb1c - Enter other goods receipts...
If I am not wrong these all 3 are used for Non-consumables items...
In what conditions I should be used.....
=== MB1A transaction code is used for goods issue. This is used for posting materials from stock to consumption say to a cost
center (mvt 201) or to a subcontractor(543).
Transaction MB1B is used to perform tranfer postings and stock transfers. Stock transfers refer to physical movement where
as in transfer posting physical movements of goods is not involved.
eg: transfer posting from material to material (309).
transfer posting from stock to stock (321,343,349).
stock transfer from plant to plant (301).
stock transfer from sloc to sloc (311).
In the above postings if the valuation change is involved then an accounting document is generated.
Transaction mb1c is used for other goods receipts. That is say for a goods receipt w/o reference to PO.
Srinivasulu Tallapalli
=== First I would like to say that all three transactions used in goods movement.
MB1A - Goods issue leads to a reduction in Stock.
MB1B - Transfer posting is used when there is a change in Stock ID or stock category of a material. There is no need for the
actual (physical) movement of goods.
MB1C - Other is used in instances where there is no reference document. Alternatively the transaction MIGO, can be used for
all three transaction but when an entry is to be made for the respective movements, specify the transaction and reference in
the respective fields on the initial MIGO screen.
Patrick Kgosana
=== I have used Migo seperately which is for all the transactions but ...if the stock is not consumables I hope we use MB1B
that I am sure..I have used it.. My question is when to use MB1A and MB1C which is again tranfer of Stock..
Mb1b also reduces the stock when you consignment/ Subcontracting to your subcontractor so I need more clarification
Rajeev
=== I was wrong in my earlier mail about the transaction codes.
Use MB1B for transfer posting. Here your material is not consumed, but only stock transformation.
Use MB1A for goods issue, which updates your material consumption. Your material is no more in the stock and it will be
consumed for external requirement.
Priya.
=== I think that:
1. MB1A: GOODS Withdrawal = 1. Sales Order creation - no impact.

2. Goods Receipt - reduce the planned independent requirement during MRP run
For e.g. if PIR is 100, quantity remained as 100 in PIR, however during MRP run, 100 will not be included in the MRP planned
as stock is available.
3. Delivery - minus the quantity for the oldest planned independent in demand management.
For e.g. if PIR is 100 and delivery 90, PIR becomes 10 (withdrawal 90).
- MB1B: Transfer posting = If you are involved with inventory, then you need the GR/IR account (Inventory Account) when the
IR is posted. If you are not involved about inventory, then the system does not need the GR/IR account when the IR is posted,
the system needs a G/L instead of the GR/IR account.
- MB1C: Other Goods receipts = You can add a new material to the material master and set a beginning balance on it by using
transaction MB1C.
Sub Contracting:
(1) You have a material that can be procured externally, and you have maintained BOM with components. Any waste
generated and received during subcontracting process can be maintained as component with negative quantity.
(2) You create a subcontracting PO (PO with Item Category L). You can also maintain Purchase Info Record for Subcontract
category for material and subcontractor.
(3) You make a transfer posting to issue components for SC PO. Material is sent to subcontractor. As material remains under
your ownership, system does not make any value entry. But quantity is shown as "Material Provided to Vendor"
(4) You receive finished material against SC-PO. You also specify components consumed in manufacturing of finished goods.
Additionally, if you have negative components in BOM, now you'll also receive subcontracting by-products. There are three
events, so three accounting entries are generated:
DR FG Stock/ SC By-Product Stock; CR Change in Stock (FG/ SC By-Product )
(for finished goods received)
DR Subcontracting Charges; CR GR/IR Clg
(for moneys payable to Subcontractor)
DR Consumption (Components); CR Change in Stock (FG/ SC By-Product )
(material provided to Vendor is now charged to expense)
(5) You do the IV for SC Invoice, and the process is complete.
I think that you have got some concepts clarification.
What is the difference between task request and change request during sap implementation. In general how many
tasks will generate during a normal company inmplementation by any functional consultant?
Change request and task request are same.But generally change request is generated during newly created objects or reports
that are transported and task request is used when u regenerate the change request by modifying that object again and
transporting it in new change request.
A particular change request may contain multiple number of task request but that number depends upon number of objects u
transfer during generation and transportation.
A schedule agreement contains details of a delivery schedule but a contract just contains quantity and price information and no details of
specific delivery dates
What's the difference between schedulling agreement with normal order?
What's the condition for us to choose schedule line or order?
Both of them contains schedule line, price, quantity.
There are a couple major differences:
(1) - Schedule agreements allow you to have 2 different sets of schedule lines (VBEP-ABART). Standard SAP you should have two sets of
tabs - of schedule lines. One Forecast & the other JIT. Forecast forwards the schedule lines to planning (seen in MD04) and JIT passes
them to shipping (VL10). They can be identical or different. Typically these are used for component supplier customers (namely
Automotive). The customer will provide you 4-10 weekly buckets (usually a
Monday date) of future forecast qtys. Also send you 1-2 weeks of individual FIRM ship dates - which are entered on the JIT. It comes
down to the customer not knowing exactly what they need next week, but they don't want to suprise you with a large order qty, where your
lead times are 5+ days. The forecasted qtys they sent last week should account for this.
(2) Cumulative Quantities are tracked and influence how the schedule agreement passes requirements to both forecasting and shipping.
These qtys are sometimes requested by the customer on ASNs. Cumulative qtys reset at year end unless you've got a customer calendar or
you've modified standard SAP userexits to not reset.
Schedule agreements are very nice when the customer sends EDI data (830s = forecast or 862s = JITs). Outside of that they can really
cause trouble regarding daily maintenance, missing requirements, cum qty corrections, year end processing, etc.
One alternative would be to use customer independent requirements - entering the weekly, monthly forecasting qtys and entering standard
sales orders (with or without multiple schedule lines) to represent the true firm qtys.

ERP Functional Consultant:

Functional Consultants are the experts having understanding of the business processes and data flow on one hand and has the capability to
fit these business requirements in the vendor ERP product, analyzing gaps, if any.
In any ERP Implementation (generally valid for most of the software product development organizations), there are two parties involved,
one are the business users/experts who give the requirements/wish lists and understand how the business processes are conducted at present
and how they want the future system to be. Then there are technical experts who are expert in various technologies and they can write code
to meet those requirements. Functional Consultants take these requirements from business users and translate them to technical people so
that they can understand in technical terms the business requirements. For example in case of any financial management software,
functional experts having domain knowledge of Finance will give inputs on how the software should work.
Functional Consultants are generally domain specific like Finance, HR, Manufacturing, and Procure to Pay etc. They have educational
background and experience in the relevant business process area, for example you will find a Chartered Accountant working as a General
Ledger Domain Expert. They acquire ERP Product knowledge by undergoing a short training on ERP Module they are working in.
A good Functional Consultant will have in-depth understanding of the business processes, product features and ability to propose a solution
for the business requirements.
ERP Technical Consultant:
Technical Consultants are the experts having knowledge of the code, coding standards and implementation life cycle. Technical
Consultants need not be any domain specific like Finance, HR, Manufacturing, and Procure to Pay etc. Their main role is to do
customizations, extensions, modifications, localizations or integrations to the existing product and develop reports. They have educational
background and experience in computer science as IT Experts, Engineers or Software Developers.
People with software development / technology knowledge are considered as Technical Experts and their main responsibility is to design
the software based on the inputs given by functional/business experts.
ERP Techno Functional Consultant:
Over a period of time, by the experience of working on a specific module Technical Experts tend to learn the business requirements and
processes and acquire functional knowledge also and sometimes referred to as techno-functional resources. Similarly a person doing
postproduction support will pick the functionality, which is generally limited to that project/product, and gradually transition towards being
a domain/business/product expert.
Such experts who have the knowledge of the technical side of the ERP like coding, database etc and who also understand some product
specific configurations for some modules by virtue of self-study or experience are sometimes misconstrued as Technofunctional Experts.
But such experts face a hard time when they are entrusted the task of designing solutions for business process, which are not straight, fit
into the ERP System. At such points the functional knowledge of the Domain becomes critical. Most of the ERP Implementation if given in
the hands of skilled professionals can provide good solutions satisfying all business requirements whereas, in the hands of the un-skilled
resources, it can be a very expensive nightmare for the business.
Similarly functional experts have been working in this field for long with-out deep technical knowledge; however it is a well-established
fact that an expert who understands the technical limitations of the specific ERP is less dependent on the Technical Consultants for
solutioning and is able to come with robust and efficient functional designs.
Gaining functional knowledge for a technical expert can be challenging, but very rewarding as demand for professionals who have both
technical expertise and strong foundation of business process expertise is ever increasing in todays globalized economies. In the present
era of globalization and liberalization, to deliver consistently, technical experts are required to reorient their historical approach of
concentration on the technology and code development, and convert their expertise to a professional who is not only technically sound but
who can understand the language business speaks. Similarly it is becoming important for a functional expert to gain technical excellence by
understanding technical capabilities, development standards and controls to recommend good functional design for the business.
Techno functional Professionals are in great demand as they play a vital role in ERP Implementation projects. Companies always prefer
experts who have the ability to understand both technical and functional challenges, as they prove to be more effective and less costly.

What is transfer order?

Definition:
An instruction to move materials from a source storage bin
to a destination storage bin in a warehouse complex at a
specified time.

instruction to move the material from source storage bin to

destination storage bin with in the warehouse complex.
It contains Material No, Material Quantity, source and
Destination storage bin.

A transfer order consists of items that contain the

quantity of the material to move and specifies the source
and destination storage bins.
A transfer order can be created based on a customer
delivery, a transfer requirement, or a posting change
notice.
Source and destination storage bins can be in different
warehouses.
Application:
This is the term of Warehouse Management (LE-WM)and linked
into SD Module, where clients business run through Warehouse
Related Trasaction:
VL01N
LT03
LT09
VL02N

What Happens When a Transfer Order is Created?

When you create a transfer order, the storage bin data and source document, if used, are changed by the system.
What Happens to Storage Bins?
When you create a transfer order, the system determines which storage bins are involved (the source, destination, and return) and updates
them according to the corresponding activity.
What Happens to Source Documents?
The system automatically updates the appropriate fields in the document that was used to create the transfer order, such as the transfer
requirement, the delivery document, or the posting change notice.
When you create a transfer order on the basis of a transfer requirement, the following data is updated automatically in the transfer
requirement:

Transfer order quantity

Transfer order number

Number of the transfer order items

Number of the open transfer order items

Processing status of the transfer order

As soon as you have confirmed the corresponding transfer order, the system updates the field for the open transfer order items in the
transfer requirement.
In order to simplify the analysis of errors when searching for storage bins, it is possible to display a log of the internal processes which take
place between the material master data and the storage bin search function.

To display the storage bin search log, choose Environment Stor.bin search log from the preparation screens or individual item screens
when creating transfer orders for both stock removals and stock placements.
The system displays a log of each step in every attempt the system makes when searching for storage bins in the warehouse.