Professional Documents
Culture Documents
1. This flow chart shows a typical manufacturing supply chain work flow detailing which areas of the
business are involved.
2. The sales department identifies a need for a product. The sales departments tell the marketing
department about their idea and provide any supporting information / data.
3. The marketing department use business analysts to support the project and to complete the
research.
4. Data and supporting evidence is passed back to the marketing department for completion of a
business plan.
5. A fully detailed business plan is forwarded to the Business Unit Manager / Directors.
6. This unit comprises of the senior business directors or managers who make a decision on the
project.
7. After approval the plan is passed back to the analysts to prepare and implement the manufacturing
process.
9. Purchasing work with logistics and Transactionport to plan the purchase and delivery of the
materials to the manufacturing plant.
10. Suppliers receive orders for product and then despatch on agreed Transactionport on agreed dates.
11. Carriers approved by the business Transactionport the raw materials and components to the
manufacturing site.
12. Products are received into the warehouse and then moved to manufacturing.
13. Finished products are moved from manufacturing to the finished goods warehouse which might
be situated locally or in a remote location.
14. Finished goods are put into inventory awaiting orders. The company computer system is updated.
Product is now available to sales.
16. Customer Services take orders and input them to the company computer system.
17. The central computer system maintains Transactionaction records and provided visibility of
product for sale.
19. A copy of the order is sent to the export department for completion of export documentation.
20. Export department manages the final despatch of the product and produces any export documents.
21. Documents are sent to the warehouse to meet up with the finished order.
23. The Transactionport company collects the consignment and delivers it to the customer based upon
the INCO terms of carriage.
24. As stock has now been used the computer system generates a request for new stock.
25. The re-order process generates a request to the purchasing department to place new orders with
the suppliers.
Many people have asked me this question. 'What does SAP IMG actually mean?' Infact many of my
readers have also personally asked me the same question. I am posting the answer below. IMG is the
short form for Implementation Guide. SAP IMG Implementation Guide helps users in customizing SAP
R/3. SAP R/3 IMG lists down all the activities for implementing each of the SAP modules such as FI,
CO, SD, MM, PS, QM, PP, etc. It can really simplify the work of a SAP implementation consultant.
Below, I have listed down some of the key features of SAP IMG Implementation Guide.
Answer:
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 Transactionactions 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 Transactionactions.
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.
Sales person. 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)
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
Transactionactions can be allocated to a specific business area.
Briefly explain the relationship between sales organizations and company codes.
Many to One.
Purchasing Organization.
Many to Many.
Explain the relationship between sales organizations, plants and company codes.
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.
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.
A plant is a place where either material is produced or goods and services provided.
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.
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.
Sales Organizations.
What are the highest organizational units in SD, MM.PP,FI,CO?
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.
Many.
None.
If you have a warehouse management system active, to what would you assign the warehouse
number?
Sales Order Cycle constitutes one of the most important components of the SAP SD module. A Sales
Order is an agreement between organizations to sell products / services over a specific period of time in
certain quantities. In SAP SD, a sales order takes information from the customer master record and
material master record. The Sales Order process would look like
In SAP SD Sales and Distribution, one can view the list of Sales orders in two ways in the system.
On the SAP Easy Access screen, from the navigation menu, choose
SAP menu >> Logistics >> Sales and distribution >> Sales >> Information Systems >> Orders >> List
of Sales Orders.
One can simply go to the Command Field and enter Transactionaction Code VA05. Sales orders can be
viewed in SAP by Sold to Party or by material number.
Answer:
In SAP terminology, the acronym ATP stands for Available-to-Promise. ATP is the process of verifying
the available quantities of material. The ATP quantity is equal to warehouse stock plus planned receipts
(incoming stock) minus planned issues (outgoing stock). Thus the available to promise (ATP) takes into
account all movements into and out of the warehouse. The stock examined for ATP could be safety stock,
stock in Transactionfer, stock in quality inspection, or blocked stock, while the planned receipts and
planned issues of the stock associated with ATP could be purchase orders, purchase requisitions, planned
orders, production orders, reservations, dependent reservations, dependent requirements, sales
requirements, or delivery requirements. On the other hand if the business is into manufacturing
specialized stock, the Available to Promise check is done against such specilaized made to order stock.
SAP SD Organizational Data - Organizational data represents the structure of the company. Each area
within the company and business is represented in a hirerachial format. For example, a sales area is
constructed of a sales organization, a distribution channel, and a division. The "Company Code" which is
the highest form of master data is used in the finance module FI. This 'Company Code' is integrated in the
SAP SD Sales and Distribution module through the Sales Organization. If one thinks in SAP terms,
because of these linkages in the company code in SAP FI module and Sales Organization in the SAP SD
module, SAP posts a particular sales Transactionaction in the correct sales organization.
SAP SD Customer and Material Master Data - This represents the data relating to the goods and
services sold by the company. It is important beacuse one needs to know which goods and services are
sold to which parties. Similarly, the business might have a variety of partners which might need to be
tracked. Thus Customer and Material data gets represented in the System accordingly.
SAP SD Document Master Data - Any Transactionaction in SAP SD is stored in the form of a
document. Any entry has a related document number in SAP. The document master data represents all
data which is stored in a systematic way for a particular business Transactionaction.
Answer:
In SAP, a material master record contains all the necessary data required to manage a material. Material
master data includes a description of the material. Description may include things like size, weight,
dimensions etc. Further, this also includes data relating to the control function i.e. industry sector,
material type etc. All the above data can be maintained directly by the user in SAP MM. In addition to
this data can be directly maintained by the user. Further, the material master record also contains some
data which is directly maintained by the SAP system such as stock levels, which are updated on a
continuous basis.
Q5). Define a Sales Organization in SAP SD Sales and Distribution module in SAP?
IMG Enterprise structure >> Maintain structure >> Definition >> Sales and Distribution
In SAP SD terminology, a Sales Organization can be compared to an organizational unit that sells &
distributes goods, can negotiate terms and conditions of sale, and can carry out such related
Transactionactions.
SAP SD allows a user to define and assign a distribution channel to one or more sales organizations.
Thus, a customer can be delivered goods from a variety of distribution channels that have been defined. A
user can view master record by different sales organization and by different distribution channel. This
enables a user to view data according to his needs.
I was discussing the concept of Sales areas and sales documents with one of my colleagues. He wanted
to understand the concept of assigning Sales areas to Sales Documents. Generally, when someone
comes up to me with a query like this, the first thing I do is start the demo version of SAP loaded on my
laptop. The demo version which I have is IDES SAP. It is always better to have the live system in front of
you when one is explaining technical details.
SAP SD provides the facility of assigning sales documents to specific sales areas. For example, a
different sales document might be used depending upon the sales order. For example, there might be two
different sales documents used for sales orders one for domestic sales other for exports.
Alternatively, same can be configured through Transactionaction Code OVAZ. Referencing Sales
Organizations, as well as distribution channels can also be assigned. An easy way to understand the
concept is to note that the referencing done is only used by the system to determine which sales
documents are permitted for which sales areas.
Big4guy Tip: While configuring, in case you require all sales documents for all sales areas, simply leave
the assignment field blank.
Q6). In the SD module, what are the three levels of a sales document?
Answer:
In SAP SD, each sales document has three main levels and each level is represented by a table that holds
the data for that level. The data for the header level of the sales document is stored in table VBAK. Data
for the item level is stored in table VBAP, and data for the schedule line level is stored in table VBEP.
Thus, for a sales document, diiferent levels of data are stored at various levels.
Sales Order
In the initial screen, choose Logistics - Sales and distribution - Sales. Choose Order - Create (VA01).
The values for sales organization, for distribution channel and the division are usually proposed from
user-defined parameters. Entries for the sales office and the sales group are optional.
The sales areas (sales organization, distribution channel, division) are derived from the sold-to or ship-to
parties. This means that you do not have to enter the sales area when you create a sales document.
If you do not specify a sales area in the initial screen, the system uses the sold-to or ship-to parties, which
you entered in the overview screen, to derive the sales area.
If there are several sales areas for that particular sold-to or ship-to party, you can choose the right sales
area in the following dialog box.
The system then copies the selected sales area into the entry screen. Choose Enter.
An error message appears in the status bar to inform you if the system is not able to determine a sold-to
party. If you enter a sold-to party that is also a unique ship-to party, the system automatically copies it as
such and informs you in the status bar.
If, for example, you defined several unloading points or several ship-to parties in the customer master
record of the sold-to party, the system displays the alternatives in a dialog box. The system can display
alternatives for any or all of the following data: –
- Unloading point
- Ship-to party
- Payer
- Bill-to party
Select the valid data from these proposals by positioning the cursor on the line and choosing Choose.
As soon as you have selected this data, the material data that you have entered is displayed.
If the system carries out an availability check and finds that there is insufficient stock for an order item to
be delivered on the requested date, it displays a screen on which you can choose between several delivery
proposals. You can find more information about this in Reactions to the Availability Check in Sales
Documents. If you want to enter further data for the header or items, choose the corresponding menu
entry. If you want to change data for the items, select the items before you choose a menu entry. Enter all
necessary data.
If you are facing a problem with duplicate customer purchase order as your company does not allowed a
same customer purchase order with the same sales order type.
You can activated the check for duplicate purchase order with "VOV8".
In the General Control Section, look for the field Check Purchase Order No and put in "A".
Default First Date is not Today
When end user created a new sales order with VA01, default First Date wasn't today, why?
Note:
1. Before today, default First Date was always today.
2. Nobody change system configuration.
Although you mention that nobody change the system configuration, it is very unlikely that the system
will mis-behaved after one day.
Usually, after checking, you will find that someone have actually change the configuration as it could not
be a software bug since you have been using it for quite sometime without any problems.
The date is control by each Sales Order Type for each Sales Document type whether is it a
- OR - Standard Order,
- RE - Returns etc.
Verify the Sales order type configuration with the following path:
IMG: Sales and Distribution --> Sales --> Sales Docs --> Sales Doc Hdr --> Define Sales Doc Types
(Transactionaction vov8) will let you control this by sales document type.
There is one field (Lead time in days) which "specify the number of days after the current date that the
proposal for the requested delivery date in the sales document should be".
This should be blank if you want the system to propose current day for delivery date.
The reason could be there should be processing times configured in the system like..pick/pack times,
Transactionit time. Please check the shipping point and also the route for different lead times.
First check what the requested delivery date you have put in the order. Next check the lead times, for that
you can go to the schedule line of the item and click on the Procurement tab.
Check in OVLZ ---> In Pick/pack time wrkdys, any value is maintained there. For example, if 5 is given
in this field, even if stock is available on the same day of order creation, system will allow to do PGI only
after 5 days from the date of order created.
Also go to VOV8, select your sale order type and check the Field "Lead Time in Days".
I'm using service material in my sales order and I need the schedule line to confirm the quantity
always in the actual day (not depending on the delivery date).
T. Code: VOV8
In Tab: Shipping,
Check Box: Immediate Delivery (press F1 to read more about this functionality).
Note: There are few more settings that you may check:
1. T. Code: OVLZ
Field: Pick/pack time wrkdys whether you have maintained any value. It should have been blank
2. T. Code: VOV8
Check how many days mentioned in Lead time in Days. If it is mentioned any days, remove it.
3. T. Code: OVZ9
4. Check in material master MRP2 view how many days are maintained for the fields In-House
production and GR Processing Time.
How can I make the system auto create all the Sales Order date during creation?
Follows this step to set the default Sales Order Type proposal date:
- Look and tick the fields Propose delivery date and Propose PO date.
After making the necessary IMG changes, you need to input the Delivery Plant field for each Materials
that you want the system to propose the default date.
Testing:
Now, try creating a new sales order for the material and SAP will auto proposed all the dates in the sales
order.
I am a SAP SD consultant and recently faced with two new terms, mass order change and ALV , I
also need to know about the Transactionaction code.
There is Transactionaction MASS which can be used to carry out mass changes in the sales order and
other objects.
Mass Maintenance: (Use to change multiple fields in multiple documents at the same time). I have done
mass change for customers; and orders should work the same way too.
2) Choose the table or tables for your selection criteria and also for fields you want to change.
Then execute. (suppose your selection criteria fields are from "sales order header data" table and the field
you want to change, is in "item data" table)
3) Put in the sales documents(21000000, 21000001) you want to change and also the items(10) you want
to change.
- click on " choose selection fields" button
- From the Pool, move the fields you want to the "select fields" using arrows.
5)In "sales order item data" tab, you see the new value of the plant you entered at the top and the old
values of item 10 are below.
-click on "change field values" button. you see all the old values are changed to new values.
-save
Note: it will take some time depending on how many records you have.
Check: Go to [SM37] and see the status of the job you are running and once finished, export the spool
file to a spreadsheet.
Before you do mass maintenance, go to the particular table in [se16] and get the results. Then do the
mass maintenance and compare the results with this one. If they match, then you are good to go.
Note: If you have any user exits that affect the results, ask them to deactivate the MODCHECKS still
you are done with mass maintenance & activate them again.
Is there a way to change the billing date on a ton of sales orders with same old billing date to a same
new billing date?
Suggestion is to test this on a few orders in your development system to get a feel on how this works
before applying this to any production data. MASS is a very powerful tool.
I have 100000 sales orders whith an incorrect price and I would like to do a massive condition
update with pricing type "B" (Carry out new pricing). Is there a Transactionaction or program for
this?
Go to VA05 execute the report. Select all sales orders you want to update the price, Go to the Menu EDIT
--> MASS Change ---> New Pricing. System will display all the re-pricing options. Select B. It will re-
price all the sales orders.
You can try for one or two order initially check the results and if it is OK, then you can do for others.
As such SAP standard does not provide release strategy for sales orders similar to purchase orders.
However this requirement of your can be satisfied through authorisation profiles; what I mean to say is
that the sale order to be kept incomplete by the person who does not have the required authorisation & the
person with proper authorisation will complete
it for further processing. This is only one way of meeting your requirement.
In order to emulate a release strategy similar to purchase orders you can use the status profile in sales
documents (BS02). IMG-Sales and distribution-Sales-Sales documents-Define and assign status profile.
Define whether the Material can be used at which Sales and Distribution process
Here you define how the system responds when entering a sales and distribution document
with this material in the differenet Sales and Distribution Process Flow..
You can use the material status, for example, to prevent orders from being entered for
parts to be discontinued.
OR
Set the material status parameters in Transactionaction SM30, Table Views V_TVMS.
Click Maintain and double click into the Materials Status code.
You can set three types of reponse for each Sales and Distribution process :-
1. no dialog
3. error message (that is, the sales and distribution document cannot be entered on
the basis of the material status)
The Cost Center Determination settings is in OVF3 - but there are some cases where the Cost Center
must be exceptionally changed.
If the document category for order type in IMG VOV8 is defined to be "I" which belong to order type FD
- Deliv.Free of Charge, then the field cost center is active for input during Transactionaction VA01.
Alternatively, you can specify an order reason and assign a cost center to an order reason.
However the standard SAP works only at the header level though, so it would not work if cost center is
needed on the line item.
- Free deliveries
- Returns
- Deliveries of advertising materials
You can also make cost center allocation dependent on the order reason, for example:
Both the IMG settings are done in Transactionaction OVF3, either with/without the order reason.
For controlling Transactionfer of requirements, you have to carry out the following steps:
When a sales order is raised, then the system check for availability of goods. If the availability of goods
is not there, then the system creates a TOR for the supply of goods to PP. Then PP can do procure or
produce the goods. This can be configured by creating requirement class and requirement type and in the
corresponding schedule line category requirement had to be checked.
The MRP department is informed about the quantities and deadlines by which incoming orders should be
delivered. The system checks the availability of the goods based on the requested delivery date of the
customer and creates MRP records which contain all necessary information for passing on to planning. It
ensures that the goods are available in time for the delivery.
Materials planning Transactionfers the reported requirements and creates orders or purchase requisitions
from them etc.
The following sections on the Transactionfer of requirements describe how to control the Transactionfer
of requirements.
- requirements type
- requirement class
- check group
The Transactionfer of requirements is controlled globally using the requirements class which is derived
from the requirements type for all sales document types.
For the sales document types, fine tuning is also possible at schedule line level. This fine tuning is
described in the section "Defining the procedure for each schedule line category".
Note that the requirements classes are also used in production so you should coordinate any changes to
the requirements classes with production. The requirements type and, eventually, requirements class are
determined in the strategy group so all changes made there should also be coordinated with production.
For performing Transactionfer of requirements, you have to carry out the following steps:
3. You must define a check group. It is possible to have this check group proposed for the initial creation
of a material master record.
4. Note that a plant must exist for Transactionfer of requirements to be carried out at document item level.
Requirements Transactionferred to planning are further processed in the module MM. You must,
therefore, coordinate the Transactionfer of requirements with the module MM.
You specify the valid tax types in Transactionaction OVK1. More than one tax type can be defined for a
country by defining the sequence.
In the standard SAP R/3 System, the elements of tax calculation are predefined (for example, tax
condition type "MWST" for taxes on sales and purchases).
Assign the plant for Tax Determination in OX10, using the country key, the SAP System recognizes
which tax type is valid for a plant and thus which taxes are relevant when creating an SD document.
Define the Customer Taxes in OVK3, you will maintain the tax code in Customer Master.
Define the Material Taxes in OVK4, which will then be maintain in Material Master.
For example :-
MWST GST 0 Tax Exempt
MWST GST 1 Liable for Taxes
In this example, if both the Customer Master and Material Master Tax code is 1, Tax will be included
when you create the Sales Order.
1) MWST is a tax condition which is applied to customer to whom we are selling. The rate of tax is
depend on various parameteres, whether is fully liable for tax or expemted (in case of Defence Customer)
2) There are few parameteres which we apply tax condition. Whether customer is tax liable? Whether
material is tax exempted?
For example, if you are selling a goods which are free for tax to any customer, put the Tax Indicator (at
MMR as '0'). If your
material is tax liable pur the Tax Indicator (at MMR as 1). If your customer is not liable for tax at all (like
the case of Indian
Defence organisations) put the Tax Indicator (at CMR as 0) or 1 in case fully tax liable.
3) Now, at VK11 you need to mainatain your pricning conditions with all the combinations like:
10
11
01
00
4) While maintaining your Material Master Records or Cusotmer Master Records, you must identify,
which are tax liable and which are tax exempeted.
5) In anycase, as a SAP standard Best Practises, while processing a sales order, you must retrieve a Tax
condition record from SAP database only and not entered Manually. Accordingly, at V/06, the MWST
condition Defintions, the field for 'Manual Entries', it would be marked as - D (Not possible to process
Manually).
Due to this setting, normally, you cannot maintain Condition tax code during sales order processing. And
in Cusotmer Master, you can only maintain Tax Indicator and not Tax Code.
6) In case your client insists for Manual entry of Tax code during Sales Order processing, you can change
the field at point 5) above to C-Manual entry is priority instead of D.
I'm assuming that, the country is India and based on its requirement:
Sales tax is a state government revenue. There are two types of sales taxes, Local sales tax & central sales
tax. Local sales tax is intra state whereas CST is inter state.
Example of LST : Point of sale i.e. delivering plant & ship to party are within the same state. The rates
are defined by the respective state governments.
Example of CST : The Delivering plant & Ship to party geographic locations are 2 different states. At the
point of sales from one state, the ST goes to that state govt. & consignment is despatched to the Ship to
party. Once that consignment is received at the ship to party state, sales tax will be levied once the sales is
registered there. For this case, the LST that is applicable by the Ship to party further will not be applicable
in all probability to be captured in SAP.
Stock Transactionfer : This does not attract any sales tax. The consignment is Transactionferred from one
D plant to another D plant irrespective of inter/intra state sales. The invoice that is accompanied with the
consignment thus shall not have any final value. It's a zero value invoice, but the basic prices needed to be
mentioned.
The selling organisations normally needs to register with the sales tax authority of the respective state to
have a warehouse or D plant to avoid the double taxation for their dealers/distributors.
Now, the pricing procedure that is there in 4.7 is Factory sale with formula-JFACT, in which the CST
condition type is JIN1 & the LST is probably JIN2. There may be surcharge cond types as well which
will calculate the amount on either JIN1 or JIN2.
For config :
1.SPRO > S&D > Basic fn. > Pricing > Pricing control > Define & assign Pric. procedure > Maintain Pric
proc.
2. The tax rates are normally driven from the Tax classification of Customer & Material access. To do
this config, S&D >Basic fn. > Taxes. You need to include the condition type for country IN in 'Define tax
determin rule'.
3. Same path : But go to Tax relevancy of master records where you configure the condition type &
options of rates that will flow to these masters. One needs to understand here properly as u need to have
unique combinations for picking the sales tax rates. I will try to demonstrate the smallest example. Let's
say, the LST rates are 2%,4% & 0%. I will have two options for material master here. 1 for taxable & 2
for not taxable.
For customer master, I will have 1-LST 2%, 2-LST4% & 3-LST0%. When I create master records for
LST thru VK11 for JIN2, I will chose the access where the combinations of customer & material tax
classifications are available. If this access does not exist create it under an access sequence. But normally
this is standard. The condition records will look like,
Cust-Tax classi. Material tax claasi. Rate Tax code
1 1 2% A1
2 1 4% A1
3 1 0% A1
Remember, rates are flown from the tax codes. Tax codes can be created thru T code FTXP. This is
normally a FI job.
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?
(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 quantities. 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 surprise you with a large order qty, where your lead times are 5+ days. The
forecasted quantities 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 quantities are sometimes requested by the customer on ASNs.
Cumulative quantities reset at year end unless you've got a customer calendar or you've modified standard
SAP user exits 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 quantities and entering standard sales orders (with or without multiple schedule lines) to
represent the true firm quantities.
Condition Technique:
Rebates, use the condition technique, but distinguish themselves from pricing in applying to
Transactionactions over time, versus on a Transactionaction basis. Rebates have their wn field catalog
and their own condition table naming convention. So you could have two condition table "001" one for
pricing and one for rebates, which could have different key fields. You need to use the technical names
A001 For pricing and KOTe001 for rebates when you use the query type using Transactionaction SE 16..
Use creates access sequence (AS). Enter 1 in field category for rebate specific. AS after going thru the
right path of maintaining access sequence for rebates.
The big difference between the rebate and the pricing access sequence is that there is no exclusion flag
available for rebate related AS. This means multiple tables for an access sequence can be applied at the
same time.
Rebate related condition types are identified by condition class -C.
After defining and creating condition types for rebated include them in the pricing proceedure. The
requirement should be 24 here which implies that the accruals are calculated on the basis of invoice/bill.
The other fields- alctyp and altcbv does not allow you to manipulate how a rebate is calculated. Also,
remove the requiremnt 24, if u want to see reabtes at order time.
These accurals are based on sales volume and when they are posted billing is created int eh follwoing
manner. Provision for accruals is debited and Sales revenue is credited. When rebate credit memo is
created
Customer account/ is debited and
Accrual provision account is credited.
Also, please note that when rebates are created without dependent ona material but on customer/material
you need to refer to a material for settlement.
What exactly do you wish to know in Rebates? The total outline of the Rebate process or each and every
step in the SAP system?
First of all rebates are more or less discounts which are offered to customers. The rebates are based on the
volume of the business the customer does with you within a specified time. for eg if the customer agrees
for Rs.1 Crore worth of business with u in 1 year, then you activate your rebate porocess. if at the end of
the year the customer DOES achieve the target u offer him say 2/3/4 % whatever is decided. The rebates
are passed on to the customer in the form of Credit notes.
The rebate can be given to the customer at one time or in installments also.
Consider an example..
You decided to give a rebate of 3% to a customer whose sales vol is $1000 for a particular SO
Then the rebate value is $30..
Now when you make the rebate settlement by doing the Credit memo and you decide to pay $27, then the
accounting will be generated saying 27$ paid towards rebate and 3$ is the accrual which you owe to the
customer
Procedure:
Rebate agreement: Transactionaction code: VB01
When you go to VB01, choose agreement type 0002 and then in conditions give
Material rebate
1 20
20 30
Now create a sales order with a material say M-11 for SOrg 1000 12 00 with QTY 6
Now check VB03 and see rebate agreement it will say Accruals 120 and payments 0
since your rebate is not settled still.
Rebate settlement
Go to VB02 enter ur sales deal no, and change the agreement status to B then enter Shift+F12 and enter
the amount to be paid for example u say $80
Then check in rebate payments rebate doc and partial settlement since you have not paid in full.
Then go to VF01 and enter the credit memo reqst no generated...save the doc no and go to VF02 and say
release to accounting
Accruals:120
Accrual reversed:80
Rebate pay:80
Amount payable:40
This is an example how a rebate will be processed with ref to a SO with an example.
How to do a rebate agreement for a specific customers with settings details?
3.Create a Rebate Agreement in VBO1 (It is O = Owl and not zero). No will be generated
choose 003 - Customer rebates, enter the customer code, the validity and check for the status field be in
Open, click on the conditions enter the percentage and accrual amount. You also can have scales in this.
Also you need to maintain the material for the settlement
4. Create a sales order for that customer and check the rebate agreement.
5. You can see the rebate condition in the invoice only.
6. Once you have posted the invoices, then go to rebate agreement no. click on verification and it will
show the order details.
7. For settlement change the status of the rebate to B - release for the settlement.
8. Credit memo request will b generated copy the no. and go to VA02, remove the blocks if any and
create an invoice (credit memo).this will show u the accrual amount.
9. In both the invoice and the credit memo check the posting - accounting document it will show u the
accrual as negative.
10. Again go to rebate aggreement and check the status it will show you D - Final settlement of
agreement already carried out
Note that in consignment fill up and consignment pickup there are no invoices since there is no change of
ownership for the materials.
In consignment orders you are allowing the stock to sit in your customer location. Once he informs that
he used the stock you will invoice him. If he returns the stock you will accept the stock to take it back.
It is defined in 4 steps.
In this step, you are not invoicing the customer. document flow is sales order ---- delivery item category.
It will not be relevent for billing and pricing because you are not charging money for these goods in this
step.
In schedule line category, you will set movement type 631 & set for availability check and TOR.
2. Consignment Issue.
Once the customer informed you that he used all the goods or partial goods then you will create
consignment issue for used goods.
Sales document: KE
Item category: KEN
shedule line category: C0 or C1
Here you are invoicing the customer (because he used the goods). You are assigning the delivery documnt
and billing document to the sales document.
In item category, you are setting relevant for billing, pricing, special stock.
In schedule line category, your setting is 633 movement types, relevant for availability check & TOR.
3. Consignment Return:
Customer found that some goods are damaged or he not able to sold the goods he want to send it back.
That you are creating this document.
You will assign delivery document and billing to sales document. you will create return order, return
delivery, return billing.
Your setting item category relevent for billing, returns, pricing, special stock.
Your setting schedule line item category: 634 movement type, NO availability NO TOR.
Your setting item category relevent for returns. any shedule line category relevent for 632 movement
type, MRP, availability check, delivery.
Client wants to issue free goods to selected customers after the said customer buys a specified
quantity of a good during the festive season starting 02 December to mid January. for example
customer A buys 34 cartons of Corn Ice-cream, we offer him 12 free corns. this should then reflect
as cost in our accounts. the rest of the system is already up and running and should not be
inconvinienced. How do I set it up?
1.Run Transaction. VBN2 to first create master record for free goods as follows:
Now run VA01 for 34 cartons and press enter. The system will automatically propose the free goods
item at no additional charge. Try higher order quantities and see if the free goods qty are scaling up.
Now assign:
7. Active Free goods Determination or Assign with your sales organisation this procedure ZFREE
8. Create free goods determination with Transactionaction code /nvbn1 for FREE with Key Csuomer
Group
99 for exclusive
To make optional / mandatory you can use in IMG - S&D-> Basic > Functions-> Log of incomplete
Procedures => select the fields > from the tables and the system will check for them (OVA2/VUA2)
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together
during a modification in ABAP.
If a field has no field name, it cannot be allocated to a group. The usage of the field groups (modification
group 1-4) is as follows:
Modification group 3: For modifications which depend on check tables or on other fixed information
Actually suppressing fielding sales orders userwise is quite easy. We are doing it in our company. For this
we use userexit FORM USEREXIT_FIELD_MODIFICATION in MV45AFZZ.
IF SCREEN-NAME = 'VBKD-ABSSC'.
AUTHORITY-CHECK OBJECT 'ZMV45AFZZ' ID 'SCRFNAME' FIELD SCREEN-NAME.
IF sy-subrc = 0.
SCREEN-INPUT = 1.
else.
SCREEN-INPUT = 0.
ENDIF.
endif.
You place the authority check object in authorization profile in the role of the users, who should have
access to the field (in this case it is VBKD-ABSSC), and there assign the corresponding fields that are to
be
Batch Determination
On batch determination, the whole process, how it is determined automatically in the order.
A1) Normally we use batch determination at delivery level, because at the time of order material may or
may not be created. for this material should be configured with batch and batch determination should be
checked in sales views of material.
You need to create a class (You might have to create a new class type) which incorporates the
characteristic.
First Create the Characteristic Using Ct04 and then using Cl02 create the Class including this
characteristic.
Then Create a Batch for the particular plant and Stor Loc using MSC1N.Give the value of the
characteristics in this batch.
Then go to SPRO ->Logistics General ->Batch Management and maintain the Condition Technique
(Procedure, Strategy Types and assignment to sales docs etc).
What is the difference between the item proposal and material determination product proposal?
We use VA51 to create the item proposal. Here we get a number.This number is then linked to the
customer master data in the sales view. This is very commonly used.
Material determination is very closely related to item proposal /product proposal and is used to swap one
material for another in the sales order using the condition technique. I have not seen Material
determination procedures used in the projects I have worked.
Item Proposal or Product proposal:
"Item proposal is same as product proposal & SAP uses the two terms interchangeably.
"An item proposal is a list of materials and order quantities that can be copied into the sales order. Items
can also be selected from a list and copied into a sales order."
1) Use Transactionaction [VOV8] to configure the document type ("MS" for product proposal).
2) Use Transactionaction [VA51] to create a proposal.
3) Enter the item proposal on the sales area data (sales tab) of the customer master record.
4) In [VA01] to create a sales order, Select Edit & propose items."
Material determination:
"Material determination uses the condition technique to swap one material for another when certain
conditions apply. Material
determination is triggered by the material entered in the line item of the sales order.
Use Transactionaction [VB11] to create a material determination condition record. And [OV12] for
configuration of material determination.
Material determination is useful when old product is becoming obsolete or a new product is released by
the company at specific date."
Variant configuration is used where you have a configurable material like computer (made up of
components like processor, monitor, keyboard, mouse etc). These components are called as
characteristics in variant config. Again this will be having values like processor can be either P4 or P3,
monitor can be 15" or 17" etc.
Based on the values selected the variant pricing will happen using the condition type VA00.
Possible questions you can expect are:
- What is variant configuration?
- What is characteristic?
- What is value?
- What is class?
- What is configuration profile?
- What is dependency and what are the types?
- What is a variant table?
- And the Transactionaction codes for the above
This is regarding number ranges defining and assigning tips which you can follow as below:
Whenever there is a new Sales Org being created, you will be required to maintain Number Ranges for
Sales Documents which are allowed for your New Sales Area.
Number Ranges can be maintained Internally by the system, however it can be maintained externally also
if you customize it accordingly.
In Standard SAP the Transactionaction code for Maintaiing Number ranges externally is VN01.
Defining - The same can be reached through in IMG as : Sales & Distribution-->Sales-->Sales Document
Header-->Define Number Ranges for Sales Documents.
Number range Key +Start Number range+ End Number Range+Current Number
For Example: If you want to propose the following Number Range
The Current Number field will be kept zero as you are proposing new number range and no sales
documents have been created on it , Obviously..
*1 is a Unique Two digit Alphanumeric Key, while proposing your key, you should ensure that it should
not be there in the system as existing.
If you propose a key that is there in the system or if the Number Range (Start and End Series) is there in
the system already, the system will throw a message that Interval already already exists. So choose a key
that is unique, and which is not there in the system.
Here , by making this , you are assigning a Key to a Number Range Series.
All the symbols can be used along with numbers from 0 to 9 and Alphabets from A to Z and in any order.
For example: !1, ^A, BB,Z*,M2.........
Assigning - In Assigning, you assign the particular Sales Document to the Number Range you have
already proposed as above.
The Two digit Alpha Numeric Key is maintained or Assigned to the respective Sales Document type in
V0V8.
Locate the particular Sales Doc Type, and double click on it to display it configuration. Here you put the
Two Digit Number key in the Field- "Number range External Assignment"
Besides this:
If a new Shipping Point is created then Delivery Number ranges are required to be maintained.
Similarly,
If a new Plant is created then Billing Number Ranges are required to be maintained.
What is Debit note and Credit note? What is the purpose? How we create?
1. A Transactionaction that reduces Amounts Receivable from a customer is a credit memo. For eg. The
customer could return damaged goods. A debit memo is a Transactionaction that reduces Amounts
Payable to a vendor because, you send damaged goods back to your vendor.
2. Credit memo request is a sales document used in complaints processing to request a credit memo for a
customer. If the price calculated for the customer is too high, for example, because the wrong scale prices
were used or a discount was forgotten, you can create a credit memo request. The credit memo request is
blocked for further processing so that it can be checked. If the request is approved, you can remove the
block. The system uses the credit memo request to create a credit memo.
You can use credit memos in Sales and Distribution (SD) for assigning credit memo requests to the open
invoices and in Financial Accounting (FI) for assigning credit memos and payments to the open invoices
and carry out clearing with them. If you use both Financial Accounting (FI) and Sales and Distribution
(SD), there is a 1:1 relationship between the credit memo request and the credit memo item posted in
Financial Accounting (FI). As soon as you bill the credit memo request together with other sales orders,
or distribute the items of one credit memo request to several billing documents, the assignment is no
longer valid and the system will not process it.
For credit memos, credit memo requests, and payments, you have the following assignment options:
- Assignment to a single invoice
- Assignment of a partial amount to an invoice
- Assignment to several invoices
When you post credit memos, the payment programme processes them automatically. If the credit memo
is specifically related to a particular open invoice item, the payment program automatically attempts to
offset the credit memo against the open item. If it is not possible to completely offset the credit memo
against an invoice, you can post a debit memo to the vendor, who is to reimburse the amount. Then you
can apply a multilevel dunning program.
3. Debit memo request is a sales document used in complaints processing to request a debit memo for a
customer. If the prices calculated for the customer were too low, for example, calculated with the wrong
scaled prices, you can create a debit memo request. The debit memo request can be blocked so that it can
be checked. When it has been approved, you can remove the block. It is like a standard order. The system
uses the debit memo request to create a debit memo.
4. As mentioned above, creating a credit or debit memo request enables you to create credit or debit
memos based on a complaint. For this first create a sales document with the order type for a credit or
debit memo request. You can create the debit or credit memo requests in the following ways:
– Without reference to an order
– With reference to an existing order
Here you enter which order the complaint refers to.
– With reference to an invoice
Here you enter which invoice the complaint refers to.
In all cases, you specify the value or quantity that should be in the credit or debit memo
5. You can block the credit or debit memo request from being billed in Customizing. Go to Sales -> Sales
Documents -> Sales document header -> Define sales document type and select the billing block field in
the billing section. This request can later be reviewed along with similar ones, - if necessary, by another
department. The request for a credit or debit memo can then be approved or rejected.
INVOICE
Output type : RD00
Explain STO.
STO is Stock Transactionport order. It is used for inter company Transactionfer of goods. Plant to plant
Transactionfer and even Transactionferring raw material to Third party contractors (Job Work).
The Process is you create a STO do delivery against the STO and create a Billing Document against the
STO.
Internal customer should be assigned to the ordering plant ( MM -> Purchasing -> Purchase Order ->
Setup stock Transactionport order -> assign the internal customer to the ordering plant and assign the
Sales area of the internal customer.
In SAP sales & distribution module, an intercompany sales occurs when the selling organization belongs
to a different company code than the delivering plant. The Transactionaction path for accessing
intercompany sales billing is:
IMG >> Sales and distribution >> Billing >> Intercompany billing
Let us take an example to understand intercompany sales better. Suppose there are two company codes
namely 1000 and 2000. A customer may place an order for goods in sales organization belonging to
company code 3000. However, the goods may be manufactured by a delivering plant belonging the
company code 1000. A sales order is created indicating delivering plant of company code 1000. The sales
organization then invoices the customer for the materials purchased. SAP R/3 automatically creates an
intercompany billing document at the same time as the customer’s billing document is created. This
intercompany invoice is sent from the delivering plant to the selling sales organization.
As a rule of thumb, when dealing with different company codes, one may find a need to Transfer stock
between two different company codes. However, if the stock be transferred within the same company
code, there is no need for an intercompany Transaction. But in case the stock is transferred between
different company codes, a Transfer of value occurs and is an intercompany sale.
In inter- company sales process, no PO will raise.
While creating sales order, if the end user knows there is no stock on their plant, they request for their
sister Concern Company to deliver these ordered goods to the customer directly, after delivery they will
receive intercompany invoice from the delivering company code, that’s the reason you enter delivering
plant while creating sales order.
Check all your settings once again for creating inter-company billing:
- Now Plant - R (Receiving) become the customer of Plant-D. So create a dummy customer in Plant-D's
company code and sales area.
- Assign this customer number to Plant -R's details & its selling sales area.
- Maintain the intercomapny billing type (IV) in ur sales doc type (OR).
- Now create VA01, enter the required fields, in delivering plant -enter Plant-D, @ item level as well as
@ header level, and save,
- Create Billing VF01 (with ref to DEL again)--observe the bill type-IV.
1. Sales Document Type: The sales document types represent the different business Transactionactions,
such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with
reference to similar sales order. If possible use standard sales order.
2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required
Sales Area. This will minimize selection of Sales Order Type as per sales area.
2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document
Type + Item Category Group + Usage + Higher Level Item Category = Item Category
Schedule Line:
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create
new, copy as from standard & maintain New.
2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item
Category + MRP Type / No MRP Type.
Step 2:
IMG > Logistic Execution > Shipping > Deliveries >
1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy
as from standard & maintain New.
2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type.
Incase if required to create new, copy as from standard & maintain New.
Step 3:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as
from standard & maintain New.
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order
to Billing, Deliver to Billing, etc.
The configuration differs from scenario to scenario & requirement of the client.
Where to maintain settings if we want to make storage location appear by default at the time of
creating the sales order?
There is No storage location determination at Sales order level.Only we can enter manually.
System does not determine storage location at sales order level. User has to indicate it at time of creating
sales order. The storage location entered in the order item is copied into the outbound delivery. If no
storage location for picking is specified in the order item, the system determines the storage location
when it creates the outbound delivery and copies it into the delivery item. The system determines the
picking location based on a MALA, RETA, MARA rule defined in the delivery type.
This functionality is not available in the standard SAP. If you want the system to check the stock at a
specific storage location, the storage location has to be entered manually at item level or you have to go
for development so that it will be defaulted under the specific conditions specified. You have to create a
Z-table and maintain the table with data under which that specific storage location has to be determined.
A user exit has to be used so that it will default the appropriate storage location after checking the table.
Storage loction determination in Sales order is only possible via a user exit. You cannot configure storage
location into sales order: you need to use user
exit MV45AFZB USEREXIT_SOURCE_DETERMIN
or
Userexit_save_document_prepare
or
---
Standard SAP can't determine storage location at sales order level. If required to give manually. But at
deliver it'll determine automatic.
If sales order level by default require, then you have to use user EXIT.
An open sales order is where the order has not been delivered (physical goods).
Open Sales order: I will explain taking an example, suppose there is an order for 100 qty and against this
order, only 50 are being delivered till its delivery date . i.e. it is partially delivered. then its status will be
open . Because it is not fully delivered.
You can check the open order status in VA02 in status tab. (double click on item and at item level chk the
status) or check in Transactionaction VA05 all the open orders.
In SAP SD, the document flow will summarize the status of each document. In order, they are:
1. Sales order : once delivery has been created, the status of the order changes from "open" to
"completed".
2. Outbound delivery : when items are picked and posted for goods issue, the status remains at "being
processed"; the status becomes complete only when billing is done.
3. Billing document : when billing document is created and saved, and posted to accounting, the status of
the delivery becomes "complete"; the status of billing becomes "complete" as well; an accounting
document is created and the status is "not cleared".
4. Payments posting affects the status of the accounting document; hence, you look at table BSEG. once
payment is posted with reference to this accounting document, the status becomes "cleared".
How can we know using data in tables whether a sales order is open or not?
Check in Transactionaction VA05 and in table the status filed will tell you the status of open order.
Check table VBAK / VBAP / VBRK / VBRP and VBFA you can chk the document flow.
Can you tell if a sales order can be considered open if delivery has happened but payment has not
been done yet?
Yes, that sales order will be considered as complete order. not open order.
Delivery will be open against which billing is not happened.
Go to Transactionaction VA05, here you can see list of all Sales order open for any particular sales area.
You can either do mass maintenance to close all the open order by giving rejection reason. Or you can
check one by one order & reject the pending item.
Go to VA02, input the sale order and execute. Now select the line item and assign Reason for Rejection
which you will find on the right top side.
If you have not delivered any quantity, then you can delete the sales order from the tcode VA02 - Enter
your doc no- in the menu bar go to sales document-then DELETE.
After entering sales order (va01) screen, system giving default sold to party. How to disable this?
This is due to activation of userexit V45A0002. You need to deactivate this. Take the help from ABAPer
to find the project which is assigned to the userexit and deactivate the same.
or
Can you also check in your SU3 Parameters whether there is any entry with Parameter ID - VAU?
If some value is set for this parameter , it will be copied by default in SOLD-TO-PARTY during creation
of the Sales Document (VA01)
You can also check if there is any Transactionaction Variant associated with your Transactionaction in
SHD0 through which the default sold-to-party can come.
We have the below requirement of changing sold to party after creation of sales order:
Once sales order is created, purchase requisition is created automatically and purchase order is
created with reference to the purchase requisition. So when Goods receipt is done, the respective
stock is getting reserved for that sales order.
After creation of purchase order, sold to party option in sales order is display only.
---
Suppose we are creating the sales order with customer '11' and material 'abc', but before saving the
sales order document we changed the customer and new customer is '21', so after this change which
is redetermined in the sales order.
-->Tax
-->Price
-->Frieght
-->Payment terms
-->Shipping conditions
-->Route.
If the Sold to party is changed from 11 to 21, then the new SP (21) may be valid for some other Sales
Area, may have different SH,PY &BP. So accordingly those data will change.
If different SP, then Price may vary, Shipping condition may vary. So those data may change.
As different SH may be different, then Route may be different, Plant may be different, and as Tax is
mostly Plant dependent, so Tax may change.
If SP is different PY may be different, so Payment Term, Incoterm & Credit limit may be different, so
those data will be changed/redetermined accordingly.
Question:
In sales order we have profit center tab in line item --> account assignment. From where does this
profit center comes here? The source I mean.
Answer:
Sales order takes profit center from material master view Sales: Plant/General data.
Profit center is assigned in (material master record) MMR in sales orgn 2 view. If you assign there
automatically it will trigger in the sales order. In the item data -> account assignment tab .
This profit center is used in MMR because, once you do OR- LF- F2 for that material this material value
has to trigger in the profit center in FI properly.
After doing F2 and when you save a the Invoice i.e., F2, automatically an accounting document gets
generated along with a profit center document also gets generated if you have assigned profit center to
your MMR.
In material master, I was created profit center PBB2K for part A but it is showing different profit
center when sales order created.
Advise why different profit center show in sales order?
Check 0KEM for any sales order substitution for profit center.
In general, the material master profit center defaults to profit center, but at sales order you can change the
profit center otherwise check 0KEM
It seems as though we have a FI setup in our system through which the Profit Center on the Sales
Order is NOT defaulted from the Material master, but is showing up another value, could you
please provide me the steps where I could look that up? What configuration is it from the FI side
that is preventing the standard material PC to be over ridden?
or
Simple,
It is in substitution,
Go to Transactionaction GGB1 and see under the node profit center accounting.
You will see that you can substitute the profit center in the sales order using substitution.
How can I make the Field Profit Center in the line item level of the sales order to mandatory?
Goto tcode SHD0, give t code as VA01. Make a Transactionaction variant and make the fields
mandatory.
or
Please include the Field Profit Center (PRCTR) in incompletion Procedure of Sales Order Item. So
without Profit Center Entry Sales Order will be incomplete.
Goto T.code OVA2 copy the procedure you are now working with and add the field vbap-Prctr.
In VUP2 you can assign your new procedure to your item category.
Path:
SPRO --> IMG --> Logistics-General -->Logistics Information System --> Logistics Data Warehouse -->
Updating --> Updating Control --> Settings: Sales --> Update Group --> Assign Update Group at Header
Level
and
Sales Org:
DstCh:
Division:
Customer Statistic Group: +
Statistics group for sales document type: 2
SPRO --> IMG --> Logistics-General -->Logistics Information System --> Logistics Data Warehouse -->
Updating --> Updating Control --> Settings: Sales --> Update Group --> Assign Update Group at Item
Level
Sales Org:
DstCh:
Division:
Customer Statistic Group: +
Material Statistic Group: 1
Statistics group for sales document type: 1
Statistics group for the item category: 1
and
Sales Org:
DstCh:
Division:
Customer Statistic Group: +
Material Statistic Group: 1
Statistics group for sales document type: 2
Statistics group for the item category: 2
Note: Once, you will maintain Settings for LIS-Update, it will update onwards Transactionactions and
will not update for already done Transactionactions.
For third party order, either you can create the material master with item category group as BANS, so the
system will automatically pick TAS in the sales order for the material or you can change the item
category manually to TAS in the order.
IMG -> Sales and Distribution -> Sales -> Sales Documents -> Sales Document Item -> Define Item
category groups
Defining Item Category -> Sales and Distribution -> Sales -> Sales Documents -> Sales Document Item
-> Define Item Categories
IMG -> Sales and Distribution -> Sales -> Sales Documents -> Sales Document Item -> Assign Item
categories
Creating Material
MM01
1. On the screen Create Material (Initial Screen) enter the material number if External.
2. Choose Select View(s). (Basic View 1&2, Sales Views, Purchasing views and accounting views).
3. Enter the relevant data and save the material. Use material group BANS in the item material group
field.
VK11
XK01
I am doing export sale but while creating billing document system give error that "Missing export
data" hence accounting document has not created.
Once you gave all the data and save, you can check the log as "Document complete".
Solution :
This will resolve the issue for current Invoice; but if the same error is occurring for every Invoice,
maintain default values.
1. IMG --> Sales and Distribution --> Foreign Trade/Customs --> Basic data for foreign trade --> Define
Business Transactionaction Types And Default Value -->
In this step maintain assignments for country/sales org/dist channel / item category / and
Transactionaction type combination.
2. IMG --> Sales and Distribution --> Foreign Trade/Customs --> Basic data for foreign trade --> Define
Procedures and Default Value --> Define procedure default
In this step maintain assignments with the combination of country/sales org/dist channel/division/exp.imp
group/item category/ procedure.
Apart from the above we need to maintain Comm./imp. code no./country of origin and region of origin at
material master
HINT:
Go to VTFL, select your billing type and delivery type and click on blue magnifying lens on top left so
that it will take you to a screen where most probably, you would be maintaining "B" for "Determ.export
data". Maintain blank field there and save. Now system will not throw incomplete error message.
How to setup material exclusion for customer during sales order creation?
If you want specific material to be added or excluded to a customer, you can do it in "Listing and
Exclusion".
Here is a small note on listing and exclusion, it may be helpful.
Consumer to Business
Your customer can enter purchase orders directly into their web server without having to make a
telephone call or send a fax
Using the screen layout that you defined, your customer can enter data quickly and easily
Your customer can find out quickly about the most up-to-date prices and delivery times
Your customer can check the delivery status of the purchase order at any time
You can design the layout of the screen so that the customer can enter data quickly and easily
You receive the sales order online, as soon as it has been entered
You are able to deliver the product rapidly, thanks to the short time span between entering the
order and its arrival at your company
You can ease congestion in sales order entry as peak times will be more dispersed
Prerequisites
To enter an order in the Internet, the customer has to log on with his or her SAP customer number (or
email address) and an initial password that you issued. The customer can replace the initial password with
their own. The system asks for the customer number and password as soon as the customer assigns a
product to shopping basket. New customers can register at this point by entering their information and the
system assigns them an initial password that they can change later.
Authorizations
For customers with use master data in the R/3 System and are logging on for the first time in
the Internet:You can use Transactionaction SU05 to create, change and delete passwords for the
customer.In order to create a unique identification for the customer, enter object category KNA1
next to the customer number.
For new customers who do not have any master data in the R/3 System and are logging on for
the first time in the Internet:
The system creates a customer master record in the R/3 System with the data from the new customer.
Essentially, the user just provides address data and additional information such as data for the company
code and sales area are taken from a reference customer. The reference customer is obligatory and you
enter it as a global customer in the R/3 System with the company code, organizational data, account
group, and internal number assignment data. You store the reference customer as a parameter value for
the parameter CSM in the master record for the global user.
In the VW01.SRVC service file you can use the ~customeridentification customer ID switch to
decide how the customer should log on - either with the customer number or the email address.
The following values are permitted:
sapnumber (standard value) The customer has to enter his or her assigned customer number to
buy products
email The customer can enter his or her email address and the R/3 System then automatically
finds the customer number by determining the customer master record for that address.
Material Group
Authorization group WWW must be saved for the material group that is being offered on the Internet.
You can save it in the material master in Customizing by going to Logistics - General→=Logistics
Basic Data: Material Master →=Material →=Define Material Groups. If you want to offer several
Internet application components in the same client, you can use the user parameter VBG (in combination
with the R/3 user) to control several material groups.
All the authorizations for the Sales/Distribution object class must be maintained for the R/3 user used by
the Internet application component to log on to the R/3 System via the Interaction Transactionaction
Server (ITS9). You must also save certain parameters for this user. A sales order is created in your R/3
System based on the sales order that has been entered in the Internet. The sales order contains certain
mandatory entries that have to be completed when it is being created.This data is taken from the default
parameters for the global user master record. The parameters are as follows:
SPA (division)
If these parameters have not been completed, the system automatically enters the following
values:
SPA (division): 01
Features
Service Name
The service name of this Internet application component is VW01 and you can find all the relevant files
under the service name in SAP@Web Studio.
BAPIs
The following Business Application Programming Interfaces (BAPIs) are used for this Internet
application component:
BAPI_SALESORDER_SIMULATE
BAPI_SALESORDER_CREATEFROMDAT1
If you use the Internet application component for entering the status of your sales orders, the following
process takes place:
1. You offer a range of products to your customer. The customer can enter the product they want in the
shopping basket.
2. The system asks the customer if he or she is new or an existing customer. If the customer is new in the
system, it runs the registration process to record the cusotmer data. It creates a customer master record in
the R/3 System and assigns a customer number and an initial password to the customer. Company code,
sales organization, division and other data are taken from a reference customer master record contained in
the R/3 System. This means that the customer master record is almost complete when the customer logs
on for the first time and he or she only needs to enter address data. They can change their password and
address data at any time. The customer master records are created in real time so that the customer can
order straight away.
3. The customer can create a quotation for the products in the shopping basket, according to the prices
defined for that customer. The system then displays the total price and the delivery date for the selected
prices.
4. If the customer accepts this quotation, the R/3 System creates a sales order that can be processed
immediately. The system displays the sales order number which the customer uses to inquire about the
status of the order. This status inquiry displays exactly where the sales order is in the processing chain,
for example, if the delivery is already on the way. You can either now place the orders created on the
Internet in a work list to be checked, or you can use the orders to create a work list to be processed
immediately in the shipping department.
5. The customer can choose between paying by invoice or credit card. Invoices are managed in the R/3
System in the same way as normal billing documents. If the customer decides to pay by credit card, the
system checks the card, and once it has been authorized, processing can continue.
A company produces PCs and offers them to their customers in various configurations so that the
customer can choose between different memory sizes, country-specific keyboards or different casings.
Once the customer has filled his or her shopping basket, the system creates a quotation with prices and
delivery information specifically for that customer. If the customer accepts the quotation, he or she can
then let the system generate a sales order for that quotation. The system provides the customer with a
number for the order and the customer can use it to check on processing status later. For example, he or
she can then find out if the products are already on their way.
Database testing involves some in depth knowledge of the given application and requires more defined
plan of approach to test the data. Key issues include:
1) Data Integrity
2) Data validity
Tester must be aware of the database design concepts and implementation rules
What is the purpose of table maintenance, (I think it's for authorization purpose) what is meant by
authorization?
UTP: unit test plans in this we test the task by various test case scenarios.
In scripts how to upload logo (it's saved in .bmp file) I am asking procedure?
Example by giving various input values and checking the output Use Transactionaction SE78 to import
graphics to SAP.
In the form painter, you can either include directly to the form using menu Edit->Graphic->Create or
using the INCLUDE statement in a window. To use an INCLUDE statement, goto into the window script
editor and use menu Include->Graphic. The include can look like this for a bitmap:
You run the report RSTXLDMC, give your logo(Saved as .tif file) in the parameter and run the report.
Then Go to Se71 and include the image from the text elements. For this you go to the Page windows.
Press the text elements button and the include the logo(Which actually has been saved as a TEXT) using
Insert->Text-Standard. Choose your LOGO.
Calling SMARTFORMS from your ABAP program. Collecting all the table data in your program, and pass
once or By using &Quot;ssf_function_module_name &Quot; the user can obtain the function module
generated by the Smartform. The input parameter is the SMARTFORM name the output parameter is
the function module generated .It has to be type RS38L_FNAM. After getting the output parameter.
CALL FUNCTION (output parameter name). to SMARTFORMS
Q: We get a report screen: &Quot; Goods issue: Problem Log&Quot; 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?
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 enteblack (with a warning message). Is there a way to
block such Transactionactions 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
Transactionaction 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. Automatic posting could be, posting of accounting documents to FICO once invoice is created which
can also be controlled manually. Automatically determine the freight while pricing in ship doc. and post
to the relevant account to fico. Usually automatic posting is posting of documents to FICO based on
various account keys and account groups.
Q. How many clients we will create in land scape (like in development server, Quality server,
productionserver) if we are creating more than one in each server what is exact use of that client.
- Global environment If you have global implementations at different client locations (eg; Canada, US,
UK) (for testing purposes with actual master data as well)
- Testing environment (For regression testing purposes before moving to production, integration etc.)
The clients could be variable and could be created to a specific environment usually a development
where abap, functional would mess around say:
Q. How we can do invoice split depending on item category in which scenario we will use?
A. You first need to go for copying controls either from sales to billing (invoice) or delivery to billing or
billing to billing use Transactionactions (vtaa,vtaf,vtla,vtfa,vtfl,vtff) all possibilities for copy controls. This
basically is flow of doc to doc. (may it be sales to billing, del to bill, or bill to bill etc.)
-> this is where you see the Item category and you control whether split is possible or not with the
indicator&Quot; B&Quot; eg: representing split in invoice based on item category. The field here
&Quot; data VBRK/VBRP&Quot; (header/item) which actually is used for splits or combining different
deliveries. Create a splitting rule using VOFM (you need access key to get here). Here you define
comparisons for the fields at header table and item tables and the comparison fields say SPART&Quot;
division&Quot;. &Quot;purchase order &Quot;BSTKD Instance: 5 sales orders combined into 2
deliveries and the split at the invoice would be 5 individual billing with respect to fields PO and DIv. of
each sales order would let you create 5 billings. You need to define the exact & Quot; field&Quot; in the
comparisons both at header and item level that could lead to invoice split. The key here is the field that
is different from header to item will cause split at the item level.
Q. Can any one explain how we will configure milestone billing, periodic billing and which
scenario we will use?
A. Form routines for pricing and various other functions can be maintained form routines are
something to-do with ABAP code.
1. Go to (VOFM) where all requirements which are represented by form routines can be
maintained. Requirements are available to be assigned where access sequences are used (for
determination procedures, here pricing).
2. Once the tcode VOFM is accessed you will see requirements and go select &Quotation;
pricing&Quotation; again you need access key to create your own or copy a routine.
Say you want header price not to have affect the item pricing, you need to go to the program
to change abap code to meet the requirement. This specific requirement you created will be
assigned in the pricing proc. determination &Quotation; reQuirements field&Quotation;
Usually with a number beyond 600.
Note: make sure you activate your routine for its effect to take place.
A.
(a) Text Determination: Any Texts in Material Master/Material Determination/Order/Delivery, etc is
meant to convey messages to the subsequent documents for compliance. e.g. &Quot; Give Top
Priority&Quot; 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
needs 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 dispatch of Material in case of Ship to Party, sending Bill in case of Bill to Party and payment
follow-up/Dunning in case of Payer.
(d) Output Determination: What type of Output (Fax/Mail, etc) is required, where and in what Format
(ABAP Customization may be required in some cases especially Invoices). (e) Storage Location
Determination: depends on Plant, Shipping Point and Storage Conditions
Q. What are the five imp fields to be maintained in account determination
A. Account Determination: Sales View, Sales Organization, Distribution Chanel, Chart of Accounts,
Account Assignment Group for Customer and Material and Account Keys.
Q. What is meant by Transactionfer of data from legacy code to sap Legacy Code?
answer1:
It should be legacy data to SAP. What it means is you want to Transactionfer the entire customer and
materials and all other information from Older (legacy system) to new SAP system. You can do it
2. Create Material – Material Type as "Trading Goods". Item category group as "BANS".
3. Assign Item Category TAS to Order type that you are going to use.
4. A sale order is created and when saved a PR is generated at the background
5. With reference to SO a PO is created (ME21N). The company raises PO to the vendor.
6. Vendor delivers the goods and raises bill to company. MM receives the invoice MIRO
9. The item cat TAS or Schedule line cat CS is not relevant for delivery which is evident from the config
and, therefore, there is no delivery process attached in the whole process of Third party sales.
10. Billing
SD - 3rd party sales order View the PR that is created with a third party sales order
VA01
Order Number
Goto Item Overview
Item ->Schedule Item
SD - 3rd party sales order Assign the PR to the vendor and create PO
ME57
Key in the PR number
Toggle the "Assigned Purchase Requisition"
Execute
Check the box next to the material
Assign Automatically button
Click on "Assignments" button
Click on "Process assignment"
The "Process Assignment Create PO" box , enter
Drag the PR and drop in the shopping basket
Save
(1) Cross Selling: How to configure and the menu path details.
(2) While creating individual order I face one error 'Plant not assigned to Controlling Area': How
to configure controlling area and menu path.
(3) Menu of path of subsequent Delivery Free of Charge.
Cross selling is a concept by which the business can improve the sales. By using this concept the business
can offer combination material for ordered material.
Ex: If the customer placed for the order for computer then computer stand can be suggested as a
combination material. It can be mapped by using cross selling concept that uses condition technique.
When the user raises the sales order and specifies ordered material then system automatically pop-up a
box in which system displays suggested material
Configuration settings:
d) Maintain procedure:
Go to new entries and define cross selling profile Ex: CS0001 and assign our condition type C001 that we
define in
the previous step.
Check cross selling ATP indicator: If you check it, systems carry out ATP check for cross selling product.
Go to VA01; raise the sales order with order material check the effect.
Scenario:
2 companies are created in system - India & Singapore Customer places sales order for particular
material on Singapore. Singapore is not able to produce the same. They pass on the order to India
for processing. After processing India ships the material directly to the customer along with
necessary documentation. Invoice copy is passed on to Singapore. Final Commercial Invoice will
be raised by Singapore. How can the above scenario handled?
1) If you are always following a third party process for a material then you have to create the material
using item category group BANS. The procurement type should be marked as external procurement
(F) in MRP 2 view of the material master record.
2) If you are not always allowing third party order processing then you can create a material master record
with item category group as NORM and the procurement type should be marked as (X) meaning
both types of procurement (in house manufacturing and external procurement).
In the item category the billing relevance should be 'F'.
Partner Functions
Explain me how to get partner determination for sales doc header level.
First determine one account group (Transactionaction code OBD2) assign number range for acct group
(Transaction code OBAR).
We can determine partner determination procedure by using the Transactionaction code VOPA.
In the business different people interacts to make a Transactionaction with the business while making
Transactionactions with the business every partner performs certain roles those are called as a partner
functions.
Depending on the partner type every partner fulfills certain mandatory partner functions. SAP
determines relevant partner functions automatically to relevant partner object type.
Flow: Customer master, Sales, Delivery, Billing, Document header and items.
A) Partner Types.
1) Customer (KU)
He performs partner functions like Sp, Sh, Bp, Py.
2) Vendor (LI)
Partner Functions (FA- Forward Agent).
Partner type (KU) and Partner Functions (AA- Sold T party) to release the contracts.
Aw- ship to party to release the contracts and this partner functions assigned to partner determination
procedure (kab).
partner type Pe
Km credit manager pe 09
kb credit represent pe 09
For sales document.
Pricing
Please explain the difference between Ek01 (Actual Cost) and EK02 Calculated Cost.
These are the condition type that will display the results of the unit costing for certain type of sales
document.
EK01 :
If you use this condition type, the result of unit costing is issued to the first position on the conditions
screen for the item. The value can be used as a basis for price determination.
EK02:
If you use this condition type, the result of unit costing is simply a statistical value which you can
compare with the price.
2) The condition type must agree with the condition type defined for unit costing in the pricing
procedure.
I have a customer who is being offered two discounts ie k007 and k005, now I want to exclude k007
for the next 2 orders or so? I have set the exclusion indicator for the condition type, but still the
condition is being accepted when I create a sales order. Am I missing something, how do I do it?
I think u need to change the validity of the condition record for the condition type K007 defining it not
valid for that particular 2 months. And also the settings of the Requirements as it is correct that it
overrules the exclusion.
To accumulate the amount of condition types in accounting document without affecting the pricing
display in billing document.
As an illustration :-
ZPXX 3500
ZDXX 1000-
ZWXX 500-
Journal:
Dr Vendor 2000
Cr Sales 2000 (ZPXX - ZDXX - ZWXX)
One way to do it is :-
Mark the condition types you want to group as statistical and remove the account assignment key.
Create a subtotal in your pricing procedure that will add them together and put in the account assignment
key for it. This way the individual components will still display on your pricing screen but FI will only
get one posting.
You have to implement SAP Note No. 105621 - Authorization check for the condition screen
What is the Transactionaction code for creating new pricing procedure and how to attach it to
specific plant?
You create PP in spro > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define
and Assign Pricing Procedures > Maintain Pricing Procedures
You can't attach PP to specific plant. Pricing Procedure is determined thru transaction OVKK. The
defining parameters for pricing procedure determination are:
1. SalesOrg
2. Distribution Channel
3. Division
4. Document Procedure (defined in Sales doc\Billing doc maintenance)
5. Pricing procedure assigned to customer (defined in customer master)
1. Use Transactionaction code v/07 to create a access sequence and assign tables based on which you
want to carry on
pricing as accesses.
2. Use Transactionaction code v/06 to define condition type. It can be for base price, discount, freight etc.,
While specifying requirement, we can give reqt no.22 which specifies that plant has to be set. This is
generally done for output taxes since output taxes depend upon the delivering plant. But directly there is
no assignment between plant and pricing procedure.
What is "alt cal type" & "alt base value" & "Requirement field" in the Pricing Procedure
Can any one explain exactly what is "alt cal type" & "alt base value" and also " Requirement
field" in the pricing procedure?
The alternate base value is used as the calculation basis only, while the alternate calculation is used to
modify the final value.
For example, imagine you have a condition type ZZ01, with a condition record maintained (master data)
for $100. Now, condition ZZ02 also exists lower in the schema, but with a rate of 10%. The standard
calculation would result in a final value of $110.
The alternate base value could say, "don't use $100 as the basis -- use the original price PR00 only, which
was $90." Then, the final value would be $100 + (10% of $90) = $109.
The alternate calculation routine says, "ignore the 10% altogether. Instead, use an externally calculated
20%." Then, you end up with a final value of $100 + (20% of $100) = $120.
Put them both together, and you could end up with $100 + (20% of $90) = $118.
Normally if you want to calculate a value you have to use a calculation type for determinating the value.
This calculation type is addition, subtraction or multiplication. Similarly SAP also has got a default
calculation type in the control data of the condition type. There you have the options of Qty based, Fixed
Amount Based or Percentage based.
Here what happens is suppose if you define Your condition type that calculates the base price of a
material on Qty based. Then the calculation will be done based on the quantity of the material. If the
customer orders 10 Nos and you have maintained a unit price of 100 Rs for each material then the value
determined is 1000 INR. Similarly if the discount condition type , you maintain the calculation type as %.
This means if you maintain the value of 10 % in the condition record. Then this percentage is taken as
the calculation type and the condition value is determined.
In some cases you have to forego the default calculation types and use the customer specific method for
calculating a value. For ex if you are calculating the Freight charges for a Material . it depends on so
many criteria like, the weight, volume and also the minimum amount etc etc, in those cases, you forego
the default value and then use the alternative calculation type in calculating the condition value against
the particular condition.
If you have to calculate any value then you have to have a base value for it. For ex if you want to
calculate the discount of 10 % for a material then you have to have a base value on which this 10% is
calculated. Normally you take the condition value of the base price of the material to calculate the value.
Now you don't want to take the base value and take other values as base values which are derived on
some formulae. So you create a routine which will do the mathematical operations in the routine and
derive you a value which is now used as the base value for calculating the condition value for a particular
condition type.
Requirement:
A factor in the condition technique that restricts access to a condition table. The system only accesses a
condition table to determine the price if the requirement specified has been met.
Example:
The system uses an access sequence to determine the price of a material. One of the accesses in the
sequence contains the requirement "in foreign currency." The system only uses the table behind this
access if the sales order for which the price must be calculated is in a foreign currency.
Re-pricing in a Quotation
You can always 'Update" pricing manually in a quotation the same way you do in a sales order, either in
create or change modes. Menu path Edit --> New Pricing or press the 'Update pricing' button on the item
conditions tab.
If you are asking how to reprice a quotation when it converts into a sales order, that can be done with the
copy controls of the Item Category. IMG: Sales & Dist --> Sales --> --> Maintain Copy Control for Sales
Docs --> Sales Doc to Sales Doc (Transactionaction vtaa). Just choose the combination of documents and
the respective item category. The field you need to be concerned with is "Pricing type".
However, from a business process perspective it makes absolutely NO sense to reprice a quotation when
converting to a sales order. After all, the entire point of using quotations is to firm up details like pricing
before creating the sales order.
You're looking to implement quantity based discounts in 4.6c. You are trying to sell items in
specific bulk quantities, and only give the discount for specific quantity intervals.
For example, if a customer orders 1 piece, 2 pieces, 3, etc. of part ABC, the price is $100.
However, this is not only a standard minimum quantity discount. If the customer tries to order 11
pieces, 12, 13, etc. it should return $100 again.
The only values for which $50 should apply are 10, 20, 30, etc. - multiples of the bulk quantity 10.
You have discussed changing your part number to reflect a bulk qty of 10, however you have in
house consumption that is allowed to consume only 1 part at a time. You would vastly prefer to
keep one part number that you order from the supplier, consume internally and ship externally.
You are fairly certain there is basic functionality that covers this, but you're just not sure where to
start.
Taking your requirements literally. Standard SAP scale pricing will not do it in that you only want the
reduced price to come into effect when the order quantity is multiple of some bulk factor.
It is agreed with that creating a separate material number is not a good idea.
You can try this:-
1. Define/Select a UOM for selling in bulk (i.e. cas, pallet, box whatever)
2. Maintain UOM conversion between your base UOM and this new UOM
3. Configure you bulk pricing condition type by usual means (it should be a base price rather than
discount).
4. Place this new bulk price behind your normal "PR00" price in the pricing procedure
5. Create a new condition base value routine via VOFM where you check XKWERT to see if it is a whole
number. If it is not then set XKWERT to zero.
6. Assign this new routine to your bulk price condition in your pricing procedure in ALT condition base
value column.
7. Maintain bulk price conditon record in the Bulk UOM.
You are trying to use shipping point as a key field (with sales org. distribution channel and ship-to
party together) to determine the sales price. You created a condition table with the above key
fields, and maintained the relevant setting (access sequence, condition type and pricing procedure).
There is an error message in the sales order pricing analysis ("access not made" in the shipping
point field).
In the access sequence, you found that the shipping point field's document structure is KOMK.
Can you put to item level field in the condition table and access sequence?
Structure KOMK refers to header of the sales order, but shipping point of course is on item level.
Step 1
Append structure KOMP. Do this by changing through SE11 the table KOMPAZ.
This is included for structure KOMP.
Add a component e.g. ZZVSTEL with component type VSTEL.
Save, activate.
If you want to make more points, assign search help H_TVST to the component.
Ask a programmer if you don't understand this part.
Step 2
Change user exit MV45AFZZ. Say there that field ZVSTEL should be filled with information from your
shipping point.
Do this under part FORM USEREXIT_PRICING_PREPARE_TKOMP.
The coding should be like tkomp-zzvstel = vbap-vstel.
Save, generate.
Step 3
Make a new table as you did before, but first maintain your new field in Condition: allowed fields.
When you create your new table you will see you have two shipping points.
With the button technical view you can check which one ZZVSTEL or VSTEL.
Step 4
Finish with the steps you did before. That was ok.
Now, you will see in your sales order that the shipping point is filled with information.
This control is set at the document level as oppose to the condition type level (PR00).
That means your other condition types such as surcharges and discounts are also determined using the
requested delivery date.
If your requirement is for PR00 to alone to be priced at delivery date then this will not work.
How pricing date is determine in the sales order and billing document? Where is the setting?
The pricing date is proposed based on the setting you make in the Sales document configuration.
(Transaction code: VOV8)
You have a field" Prop.f.pricing date” in the Requested delivery date / pricing date / purchase order date
segment.
Then you can choose the follwoing options:
Blank - Indicates the current date as the pricing date
A - Indicates the date based on the requested delivery date
B - Indicates the date based on the order validity start from date
And the pricing in the billing document is copied from thte sales order / Delivery document..
It again depends on the setting u have in the copy control from order - billng or delivery - billing.
In the copy control, in the item settings you have two fields relavant for this.
One is pricing source and the other is pricing type.
The pricing sources are generally the order. But if you want you can change it to other values mentioned
in the drop down,
but this values have no effect if the pricing type is B.
Any other value other than B in the pricing type will take the reference document price mentioned in the
pricing source field.
but for the pricing type B. The new price is determined in the billing order.
Which is the best Transactionaction code to check the Pricing condition price entered in "VK11"?
Other than "VK13", to display the price, you can use V/LD - Execute Pricing Report to check the prices
entered into the Pricing Master.
Normally Pricing Report - "07 Cust.-specific Prices with Scale Display" will do.
---------------------------------------------------------------------------
|LR|Report title
-- ------------------------------------------------------------------------
|01|Comparison of Price Lists Without Scale Display
|02|Comparison of Price Groups Without Scale Display
|03|Incoterms with Scale Display
|04|Incoterms Without Scale Display
|05|Price List Types Without Scale Display
|06|Price List Types with Scale Display
|07|Cust.-specific Prices with Scale Display
|08|Cust.-specific Prices W/out Scale Display
|09|Material List/Material Pricing Group with Scale Display
|10|List Mat./Mat.Pricing Groups Without Scale Display
|11|Price Groups With Scale Display
|14|Taxes
|15|Material Price
|16|Individual Prices
|17|Discounts and Surcharges by Customer
|18|Discounts and Surcharges by Material
|19|Discounts and Surcharges by Price Group
|20|Discounts and Surcharges by Material Group
|21|Discounts and Surcharges by Customer/Material
|22|Discounts and Surcharges by Customer/Material Group
|23|Discounts and Surcharges by Price Group/Material
|24|Discounts and Surcharges by Price Group/Material Group
|25|VAT/ATX1
|26|Canada/USA
|27|I.E.P.S Mexico
|28|Conditions by Customer
|30|Conditions by Customer Hierarchy
|31|Price List with Release Status
|AC| |
|AD| |
---------------------------------------------------------------------------
Mass Update of condition pricing
You can update the condition pricing for a range of sales order.
For e.g. if you create sales order for 15 months or so, and at the beginning of each year, you have to
update the prices for lots of sales orders.
Other than using VA02 and make an Update of the conditions at item level which is a big work because
you will have lots of open sales order after so many months.
or
if you don't want to do that Online, write your own abap report and use Function SD_BULK_CHANGE
(check where-Used at SE37, Trace VA05 on how to fill the parameters, Function MPRF => New
Pricing)
The first method is not to set the pricing condition VPRS as statistical.
Simply remove PR00 and it will work fine if you always use VPRS as your pricing base inside the
pricing procedure.
VPRS will reads both prices based on the price control in the material master.
It is this simple if you do not have any other "Prices" in the price procedure.
However, if you are using one pricing procedure where for some items you price using VPRS and some
others using PR00, then you should use requirement routines to enable the correct price condition type at
the right time.
The second method involves more work as you need to write a formula (VOFM) to get that information.
1. Set VPRS to be the first step in the pricing procedure and to be subtotal B (as standard).
2. Set PR00 with alt. calc. type formula, which sets the value of PR00 to be equal to the subtotal B.
The routine (created with Transactionaction VOFM) is:
RV64A901
FORM FRM_KONDI_WERT_600.
XKWERT = KOMP-WAVWR.
ENDFORM.
We have a requirement of giving a discount to customer based on the total amount invoiced so far (across
financial years). Where do we set this up? We have seen so far the discounts are calculated
based on the value of the current invoice.
The discount should be on a graduated scale basis for example
0 - 100000 No discount
100000 - 200000 5%
200000 - and above 10%
this means that discount would only start after the customer's net sale value crosses 100000.
For example, if the customer has been billed for 99000 and the current invoice is for 3000, a discount of
5% should be given on 2000 i.e. 100. Another complication is that, the discount is not based on the total
amount billed so far, but only on the effort billed and not on reimbursements (like airfares, living
expenses, visa charges, beeper charges etc). The discount applies only to the effort and not to the
reimbursements. In the above example (invoice of 3000) say the effort billed is only 1500, the rest being
reimbursements. The discount is only on the 500. (the rest being taken up by the lower limit for eligibility
of 100000)
For example the customer might have been billed say 150000 so far but actual effort billed might be only
90000, the rest being reimbursements of actual costs and hence the customer is not eligible for the
discount.
The solution for this is Using rebate condition types and suitable condition
records.
Of this to handle your first problem that is the rebate has to be applied only on the "effort" you have to set
up a line in the pricing procedure which gives the rebate basis i.e the value to be used for rebate cond
types. This I believe solves your problem of rebate only on effort.
Your second problem i.e the discount should start getting applied automatically when it reaches the first
scale for which the values span few financial years. This I am not really sure whether it can be made
possible in the invoice itself. But a work around is not giving the discount directly in the invoice but
settling it against the rebate agreements by Credit notes periodically.
Arent we looking at rebate agreeement. That appears to be a straightaway solution to your problem. You
activate the sales organization and the payer for that .
6) Assign the Partner Functions to the Partner Procedure for the Sales Document Header
Menu Path: Tools ->; Business Engineer ->; Customizing ->; Sales and Distribution ->; Basic Functions
->; Partner Determination ->; Define Partner Functions
Transactionaction Code: VOPA
7) Assign the Partner Functions to the Partner Procedure for the Sales Document Item (OPTIONAL)
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER
FUNCTIONS
Transactionaction Code: VOPA
8) Edit the Pricing Communication Structure (KOMKAZ) to Hold the New Functions (Client
Independent)
Menu Path: Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; DICTIONARY
Transactionaction Code: SE11
The following code should be inserted into program MV45AFZZ to allow the system to re-execute
pricing if the user makes a change to the relevant partner function (alteration, addition, deletion).
13) Add the KOMKAZ Fields to the Pricing Field Catalog (Client Independent)
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE
ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES
Transactionaction Code: OV24
15) Create an access sequence containing the new tables (Client Independent)
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE
ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES
Transactionaction Code: V/07
The Most Important Tips in Pricing for SAP SD Module to crack interviews...
Whenever we define our pricing procedures, we remain least interested in creating our own Condition
Types, Condition Tables & Access Sequences. What we do is, we just define our own pricing procedures
by using the existing condition types (i.e: PR00, K004, K007, KA02, KF00 etc.) & then assign that
Pricing Procedure with “Sales Area, Document Pricing Procedure & Customer Pricing Procedure “.
After that we put the values against each Condition Types, mentioned in our Pricing Procedure by using
the T-Code "VK11". But we also need to know about the Condition Tables, Condition Types & Access
Sequence Creation. So for that purpose we have to use the following T-Codes respectively: "V/05",
"V/06" & "V/07". Now it will become easy to create the same.
Also to inform that, using T-Codes is smarter than following paths through IMG screen.
My condition type is PR00 and Access sequence is PR02. And in this access sequence table 304 is
available. Now when I was entering the PR00 in VK31 it shows error Table 304 is not defining for
the condition type PR02. But when I was entering the PR00 at VK11 it is accepting it.
Difference between VK11 and VK31 - if you go through the menu path you will get the vk 31 as
condition record from the tamplets whereas vk11 as simple condition record. In VK11 you can store
condition record for more than one condition type. This means you can have same condition record for
different condition types.This feature is given to enhance the system's performane and not to create the
duplcation of the work for each condition type.
Again system is not allowing to store the record in the vk31 for the condition type pr00 and access
sequence pr02.This is because if you see this ac seq cointains two accessses 20 and 30 having the same
table no.But you see there is the difference between the technical view of it for Transactionfering the data
from document field and condition field, so you can not maintain the data at VK31.
What is the difference between Header condition and Item condition? I know item condition
applies to each item in a sales document. Header condition can only be applied to an entire
document.
Difference between header and item condition - as YOU CORRECTLY SAID HEADER CONDITION
IS APPLICABLE FOR THE WHOLE DOCUMENT where as item is for item.Ex-Say fright is dependent
on the total weight of all the items in the documents then header condition adds on weights of all items
and calculates the record accordingly.
You have two different types of the header conditions.
a) In one you can duplicate the same value throughout the document for each item.Say discount 2% at
header level which is also applicable to all the items
b) Second is the accumulation of the values of all the item at the header level,as earlier explained for the
weight/fright.
These differenes are controlled through the indicator of group condition in the cond.type configuration.
And so obviously header condition can not have the condition record and hence access sequence.
Change condition type ZOBP's plus/minus indicator to "A" which means only positive is allowed
In pricing procedure there are column such as requirement, sub total altclty, altbv, accurals. What
are these and where we calculate all these values which we put.
1. Requirement: Denoted by nos and maintained in VOFM, this is a condition required for a particular
condition type to be executed. Eg. PR00: req 2 ie item relevant for pricing
VPRS/EKO1: req 4 ie cost
Rebate BAO1 Req 24/Req 25 etc
2. Subtotal: this represents where a which table a value is stored, which can be processed for further
calculation.
Eg. for PR00, if this value is to be used for credt check of a customer, we mark the subtotal as A.
3 Alternate Calculation type: this is also denoted by numbers and maintained in VOFM. Eg. Suppose for
45 units , each unit is charged $100 per unit, the order value comes out to be $4500, that is calculation is
done as per unit price, if the client wants calculation type to be based on volume or wieght, alternate
calculation type can be configured.
Eg, if the pricing scale is maintained and pricing for 45 units comes under the scale of $100 per unit., the
base value is 45 units, but if the client wants a standard base value in some casesto be assumed inspite of
maintaining the scale, an alternate base value is confihured, that is the base value based on which the
order value is to be calculated changes.
5. Accruals: Accruals are maintained for rebate agreements, it constitutes the total accumulated value
which customer has earned through rebate, one the rebate for certain amount is settled the amount from
the accruals get deducted.
1. Create the field in the KOMK (header data) and KOMP (item data) tables using the standard
includes provided for this requirement.
2. Write the code in the user exit to read the Transactionaction data and Transactionfer it to the KOM
“x” structures.
Menu Path
The menu path here is IMG, Sales and distribution, System modification, Create new fields (using the
condition technique), new fields for pricing.
Adding the Field to KOMK and KOMP
This process requires some knowledge of the ABAP dictionary and how to use the ABAP dictionary to
create and change fields and tables. You may have to use an ABAP skill to assist you. If the field is from
the header table (for example, the order table VBAK), you’ll need to add it to the include table KOMKAZ
in table KOMK. If the field is from the item table (for example, the order item table VBAP), you’ll need
to add it to the include table KOMPAZ in table KOMP.
Let’s say you need to use the “base material” to define a price and the base material is not in the pricing
field catalog. The base material is a field on the material master basic data screen and is defined as
MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to the
KOMPAZ include table.
Note When you add a field to these tables, it must start with “ZZ.” Therefore, the field you add would
be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table
MARAWRKST.
After adding the field, generate the structure KOMP. This field is not available in the field catalog and
can be used in condition tables.
Writing the ABAP Code
The field in the communications structure will be blank unless the ABAP code Transactionfers the data
from the material master to the field KOMPZZWRKST. Pricing occurs in the order and in the invoice, so
you need to put this code in both places. For the order Transactionaction, write the ABAP code in user
exit USEREXIT_PRICING_PREPARE_TKOMP in include program MV45AFZZ. For the billing
Transactionaction, write the ABAP code in user exit USEREXIT_PRICING_PREPARE_TKOMP in
RV60AFZZ.
Note: The TKOMP is for the item level. If you are writing the code for a field at the header level, you
would use the user exits that end with TKOMK. The ABAP code would select the Base material field
from the material master table using the material from table VBAP/VBRP. It would then Transactionfer
this field to the structure TKOMP from MOVE MARAWRKST to TKOMP-ZZWRKST.
I will explain you the process with below example...Please follow steps in below sequence-
Try to add the filed from the field catalog. In case the required combination field is not there, you can
add the field through the following process to filed catalog and create the condition table. It is most
common that one or other time we need to use this function while configuring multi tasking & complex
Pricing Architecture.
Here I'm giving a simple guide to add fields to the Pricing Field Catalogues:
For example 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 (Transactionaction V/03), however, the system does not propose the
field in the field catalog.
Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ, KOMKAZ, and
PSTYV are the other terms which we need to know about, to add Fields.
For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG
('Allowed Fields for Condition Structures').
Proceed as follows:
1. Call up the ABAP Dictionary (Transactionaction 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 (Transactionaction 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 Transactionaction 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 Transactionaction SPRO via the path 'Sales and Distribution -> System
Modifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing' and OSS
Note 21040.
Header conditions are those which appear in the header level of any sales order. these conditions are to be
entered manually and get distributed automatically and the basis for distribution are taken from the NET
VALUE of items mentioned at item level.
When we go to the conditions section in a sales order, where the details of pricing are mentioned, here we
add these conditions.
Whenever any Header Condition is used, it overrides the PR00 condition type.
Group Condition: You can use this is feature of a condition type to apply price or discount for a material
based on common property.
Header Condition: This is a manual condition which you apply to header (Condition screen) of a sales
document. This amount is applicable to all items.
Usage of this feature is to apply price / discount for a specific group of materials.
1. You maintained a discount based condition record fbased on material group (= 01 for example). You
maintained scales also.
Qty Discount
1 - 10 Rs. 100.00
11 - 50 Rs. 105.00
51 - 150 Rs. 110.00 etc.
2. You are creating a sales order for a customer with five different items with different quantities as below
ITEM 1 - 25 No's
ITEM 2 - 3 No's
ITEM 3 - 12 No's
ITEM 4 - 27 No's
ITEM 5 - 62 No's
3. While calculating the discount, because of this group condition, system add the quantities of items
which have material group = 01. In the above example total quantity is = 109. System apply a discount of
Rs. 110.00 to each item irrespective of the individual quantities.
4. If you have not activated the group condition feature, system determines the discount value based on
individual item quantity which is as below.
Discount
ITEM 1 - 25 No's Rs. 105.00
ITEM 2 - 3 No's Rs. 100.00
ITEM 3 - 12 No's Rs. 105.00
ITEM 4 - 27 No's Rs. 105.00
ITEM 5 - 62 No's Rs. 115.00
5. Is it clear now. Just try a sales order and see the out come
Procedure to Test:
1. Create 3 materials. Maintain Material Group of each item is same.
2. Activate the condition type as a group condition.
3. Create a condition record for this condition type with scales.
4. Process a sales order for a customer with these three material with different quantities.
5. Check the outcome.
It starts with an understanding of the factors that influences the Price. Let’s say it depends on Customer
and Material. With this understanding now we will start with the Table where we will pass the above
parameters. There is a table 5 which already has Customer and Material so we can now copy and rename
it or use the same table in our Pricing Procedure.
Transaction Code VOK0
Step 1. Define/Choose your Table (with the requirement parameters that influence the price)
Step 2. Define your Access Sequence and include the above Table in your Access Sequence
Step 3. Define your Condition Type (There are four Price Types Basic Price, Discount, Freight and Tax)
and include your Access Seq. Its always better to copy the Price Types provided by SAP.
Step 4. Now comes your Pricing Procedure where you include include Condition Types and format.
Step 5. Now comes Procedure Determination where you specify the Document Pricing Procedure and
Customer Pricing Procedure along with Sales Organisation, Distribution Channel.
Step 6. Maintain Condition Records for your Condition Types
I guess you can make it 8 Steps by dividing some of the main steps. Few important things to note is
following..
1. XD01 - Create Customer - Always ensure that you pick the right Customer Pricing Procedure from
here.
2. VA01 - Sales Order - Ensure that you have the right Document Pricing Procedure from here
3. While Creating Access Sequence, check your Fields and ensure that they appear with any warning
(Highlighted in Red)
4. Do not forget to mention your Access Sequence while defining your Condition Type
5. Always remember that your Procedure Determination has only Basic Price as Condition Type
6. Do not forget to mention the Range (From To) while creating your Pricing Procedure.
Common questions:
We are using the Freight in Header Condition. I maintained two line items in the Sales Order. So
the Header freight is splitting irregularly for two line items (in item conditions). How it is
happening? Any formula is there?
Header Conditions - Automatic pricing does not take header conditions into account; you can not create
condition records for them in the standard system.
Header conditions are entered manually in order processing. R/3 includes the following header
conditions:
- Percent discount (HA00)
- Absolute discount (HB00)
- Freight (HD00)
- Order value (HM00)
Header Condition: If this condition is marked as a header condition, it is possible to enter the condition
type in the header condition screen. Checks for changing the condition manually are unaffected by this.
Group Condition: Group conditions are helpful incase of discounts. If group condition is selected then the
discount percentage or quantity is applicable for the total sum of the quantity in the PO for those materials
belonging to the same material group. Suppose if two materials of same matl grp have discounts for 100
qty and above but in PO if the two matls are bieng procured for 50 qty then they cant avail discounts but
if group condition is selected then the sum of the quantity of both matl of same matl group is considered
(50 + 50) and discount can be availed for 100 qty.
Further Group condition: Indicates whether the system calculates the basis for the scale value from more
than one item in the document.
The nature of header condition is that whatever value you are giving in sale order / billing, line item wise,
it will be distributed proportionately.
If you access V/06 and the header condition type, you can see that the condition type
- does not have any access sequence
- field Group condition is selected
Normally Freight Header condition like condition type "HD00" is calculated on the basis of weight. This
is a Manual condition and you have to enter it in the header screen. It will be proportionately distributed
on each item on the basis of weight. If you will uncheck the group condition field, the same freight
amount will be copied to each item, possibly irrespective of different weight which may not be logical.
Based on whether the group condition field is ticked on or off, it will either split the header condition
value to the items on pro-rata basis or it will just duplicate the header value to all the items.
What you are experiencing with Fixed Amount Header conditions is standard behaviour. Please see below
Notes:
- 876617 FAQ: Header conditions / Header condition screen
- 317112 Behavior of conditions w/ calculation rule B changed
- 485740 Conditions with fixed amount in copy activities
To achieve what you wish (absolute amount), solution is in the below Notes:
- 84605 Transactionfer absolute amount condition to billing doc.
- 25020 Value changes during over/underdelivery
- 25144 Freight conditions during milestone billing
Condition Exclusion
The system can exclude conditions so that they are not taken into account during pricing in sales
documents. Material 4711 cost 150 USD. Some customers receive a discount of 10 USD per 100 pieces.
However, a specific customer can buy the material for 100 USD. Since this is a particularly good price,
the customer should not also have a discount of 10 USD per 100 pieces. Therefore, this discount is to be
excluded from pricing.
You must set a condition exclusion indicator for the price. You can do this in two ways: If you want to set
the condition exclusion indicator a follows then you specify it:
- for all condition records of a condition type (e.g. with condition type PR00) when defining a condition
type in SD Customizing
- for an individual condition record (e.g. only for material 4711) in the detail screen of a condition record
(in the Condition exclusion field)
You must set a condition for the discount in the pricing procedure in Customizing for sales. If this
condition is set, the discount is not valid if the condition exclusion indicator is set. Condition 2 is
available in the standard R/3 System.
This means that if a condition record contains condition supplements they will be taken into account
during pricing.
In any normal situation there could be more than one condition type in a pricing procedure offering a
discount to a customer. Should the discounts be automatically determined, there is the risk that the
customer will receive all the relevant discounts and thus purchase the product for a lower price than he
should.
By using ‘condition exclusion groups’ you can ensure that the customer does not receive all the discounts,
but instead only receives the best of the available discount condition types.
Menu path – IMG - Sales & Distribution - Basic functions – pricing – condition exclusion – condition
exclusion for groups of conditions (OV31).
A condition exclusion group is merely a grouping of condition types that are compared to each other
during pricing and result in the exclusion of particular condition types within a group or entire groups. It
is important to note that the condition types you want the system to compare must exist in the pricing
procedure and must have valid condition records created for them.
If for example, a sales order is created using the pricing procedure that the exclusion group is assigned to,
you can see that the condition offering the most favorable discount to the customer is represented in the
pricing procedure.
For instance, condition type K007 has offered a discount of 10% off the sale price or a real value of $30,
while another condition type K005 has offered a real value discount of $10. The system then takes the
best discount for the customer between the two, which is K007 and makes the other discount K005
inactive. This can be seen by double clicking on the condition type K005, where you can find a entry
saying ‘Inactive A condition exclusion item’.
D – exclusive
E – least favorable within the condition type
First step is to define a ‘condition exclusion group’ by using a four character alpha numeric key.
Next step is to assign the relevant condition types to the exclusion groups such as discount condition
types, freight condition types.
After completing the assignment of the condition types to the exclusion group, proceed with assigning the
condition exclusion group to the relevant pricing procedure.
After selecting the pricing procedure for which you want the condition exclusion to be active, select the
folder ‘Exclusion’ where you can assign the relevant condition exclusion procedure to the relevant
condition exclusion group.
When using the condition exclusion group to find the best condition record in a condition type – only use
one condition type per exclusion group. The most important thing to remember here is to “deactivate” the
Exclusive Indicator on the access sequence assigned to that condition type. Otherwise, the system will
merely find the first condition record and stop searching for other records.
Pricing Report:
A Pricing report basically helps to get the list of all the pricing details which we have maintained in the
system. We can get details of all the condition types including the scales. We can get the details as per our
requirement i.e., Sales org/Dc/Division/Plant /material etc wise. The selection criteria would be as per the
Key combination which you select in the IMG screen
1. It informs you about the customer specific price agreements that were made within a certain period
2. From pricing report you can know which condition records exist for freight charges
3. Which condition records exist for customers in a particular region or country.
Also
1. Get information for price (discounts) that existed at previous period (Say June 200X)
Though all the above T Codes and there are many More standard SAP Reports have very high utility, it is
not widely used. Clients prefer customized reports when it comes to pricing reports - all Z programs and
Transactionactions.
These kind of reports are generally required by the Top Management for periodical review // Finance
team for price control // Master data team for record purposes // Process audits by Internal/external
agency // Of late, for every SOX audit done in the company...especially the change records for prices.
Condition Index
Condition index is very useful for searching the condition record for a customer.
It becomes easier and faster to search for condition records for a customer or material just like it become
easier to search a topics in the book with help of index.
You have to mark the "condition index" check box in the condition type and you have to activate the
index in customization.
You can set the discount for fast ten orders through "condition update".
First, in your discount condition type (V/06) activate the "condition update" check box.
Second, in the condition record, in additional data put "maximum number of orders" as 10.
You may also create the condition record for discount through VK31. Now go to change (VK32), scroll to
the right, you will find a column "N". This is maximum number of order field. Here you can put value 10
and save it.
Where does the standard condition base value (Default one) is determined for a Condition type?
First check the Material Master UOM Conversion - Additional Data - Units of Measure.
Condition base value is a concept used in pricing procedure and actual term used is alternate condition
base value. This is a formula assigned to a condition type in order to promote an alternate base value for
the calculation of the value.
If you have to calculate price of a material then you have to have a base value for it. For e.g. if you want
to calculate the discount of 10 % for a material then you have to have a base value on which this 10% is
calculated. Normally you take the condition value of the base price of the material to calculate the value.
Now, you don't want to take the base value and take other value as base value which are derived on some
formula. So you create a routine which will do the mathematical operations in the routine and derive you
a value which is now used as the base value for calculating the condition value for a particular condition
type.
As per my understanding there is Alternative Condition Base Value, It is a routine which is assigned to
the condition type in the pricing procedure.
Go to Transactionaction V/08 here you select pricing procedure then go in to the control data of the
pricing procedure here you can find Alter native Condition
Base Value in the 14th column of the pricing procedure control data.
When a value is derived for a condition type, based on certain calculation this value is taken as base.
2. Conditional value.
For the number of units ordered depending on the condition amount mentioned this value is derived.
3. Conditional amount
This is nothing but the unit list price what you are mentioning for the line item.
1) What is the role of alternative calculation type, condition base value, requirement in pricing
procedure?
2) Where do we define value for alternative condition base value and alternative calculation type so
that system picks up different value, when the value for alternative condition base value and
alternative calculation type is mention in pricing procedure?
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.
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.
Example
An absolute header discount is, for example, distributed in the standard system according to the
cumulative value of the items.
If the system distributes the absolute header discount according to volume based on the Alternative
formula for condition base value , a header discount of $30 results in the following discounts:
1 $1000 2 cbm
2 $500 4 cbm
$20 $10
$10 $20
Alternative formula to the formula in the standard system that determines a condition.
Requirement
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.
In sales order Diff condition type is not coming, when checked in analysis it says requirement 013 is
not fulfilled, but in pricing procedure I've assigned the requirement as 013, alt.cal type-16, alt CBV-
4.
RE LV61A013
Title
Purpose
This is an example of a pricing requirement. This requirement is met if an entry has been made in the
'Unit to be rounded up to' field in Table T001R. Table T001R stores the rounding rules for company code
and currency combinations. This requirement can be assigned to the condition type in the pricing
procedure that is used to calculate the difference when rounding. Using this requirement, the difference is
only calculated when necessary.
Example
A company has the requirement to carry out rounding for certain company code and currency
combinations. This information is stored in Table T001R. In the document pricing procedure, the user has
configured the SAP delivered condition type DIFF to calculate the difference when rounding occurs. The
user also assigns pricing requirement '13' to the condition type DIFF in the pricing procedure so that the
condition is only calculated when a corresponding entry has been maintained in the table T001R.
or try this go to IMG path --> SAP Netweaver --> General Settings --> Currencies --> Define rounding
rules for currencies. Here maintain the rounding unit which will be stored in Table T001R.
Purpose
This is an example of a condition value formula. This type of formula can be used to influence the value
shown for the condition in pricing. A condition value formula is assigned to a condition type or value line
in the pricing procedure.
Formula '16' was delivered along with condition type DIFF to support the rounding unit rules that can be
defined in T001R for company code / currency combinations. Condition type DIFF was delivered to
perform the rounding at the end of the pricing procedure with the total value. Using formula '16', the
system computes the rounded value and assigns the difference to the condition type DIFF.
Purpose
This is an example of a condition value formula. This type of formula can be used to influence the value
shown for the condition in pricing. A condition value formula is assigned to a condition type or value line
in the pricing procedure.
Formula '17' was delivered so that a condition value could be rounded off according to the rounding unit
rules (e.g. plus 5 or 10 or 100 units) that can be defined in T001R for company code / currency
combinations. When formula '17' is assigned to a condition type, the condition value will always be
rounded using T001R.
Where I can do setting of rounding profile for a new created condition type?
Path: Materials --> SPRO Quantity Optimizing and Allowed --> Order Optimizing --> Purchasing -->
Management Unit of Measure Rounding Rules --> Logistics Units of Measure
Here give new rounding rule and % rounding up and down values
2) Create Unit of measure groups
Path: Order Optimizing --> Purchasing --> Materials Management --> SPRO Unit of Measure -->
Quantity Optimizing and Allowed Logistics Units of Measure Groups
Create new group for YD and ROL
Path: Order Optimizing --> Purchasing --> Materials Management --> SPRO Maintain Rounding -->
Quantity Optimizing and Allowed Logistics Units of Measure Profile
Here give Rounding profile name and plant and click on Dynamic to create new profile
In next screen give desc. For rounding profile, rounding off method as 2, and rounding rule which you
have created.
Maintain minimum order qty as 1 Rol and Order unit as ROL in Info record
BOM Implementation
A bill of material (BOM) describes the different components that together create a product. A BOM for a
bicycle, for example, consists of all the parts that make up the bicycle: the frame, the saddle, wheels, and
so on.
Process Flow
When you enter the material number of a bill of materials that is relevant for sales order processing, the
system displays the material that describes the whole bill of materials as a main item. The individual
components are displayed as lower-level items.
There are two ways to process a bill of materials in Sales. Once you have entered a bill of material in a
sales order, the system runs pricing, inventory control, and delivery processing at:
The type of processing used by the system is determined by the item category group that you enter in the
material master record for relevant materials.
I have set up sales BOM. How do I know or test that is is working or not?
Once you enter a material (for whch you have created a BOM thru CS01) in the sales doc another
material pops under the main material line item as a sub-item (s). If it doesn't then your BOM isn't
working.
1. The bom hasn't been defined for the plant used, or you haven't defined the plant in SO.
2. Main item category - has BOM application SD01 been assigned to it?
3. Item categories for main items and sub-items have not been mainteined properly.
4. Sales items maintenance - You should assign item categories for BOM header items and sub-items to a
specific sales doc.
5. Has the BOM itself been configured properly (i.e. right plant, BOM usage '5')?
6. Are you trying it out on an order created after all BOM maintenance was done?
7. Also , what's the 'Structure scope' set as? Anything except C may be useful here? We have that set to
A, since our BOMs are all single-level. You could set it to B if BOM are configured multi-level.
Those are probably main reasons why BOM shouldn't work. Apart from that, just re-check your whole
config - the truth is out there somwhere.
BILL OF MATERIALS
What are the steps of customization to pricing for header level or item level then?
You can create a sales bom, and price it at header level or sub level.
If you want to assemble the products and depending upon the assemblies you want to price. For eg. if the
customer asks for a certain combinationa of Material A, B and C respectively, then you create a Material
Master record Material D with item category group as LUMF. While the Materials A, B and C are
created with standared item category groups NORM only.
Then create a sales BOM using Tcode CS01 and enter the following details:
Material: Material D
Plant : Plant in which you created the material.
BOM Usage: 5 (Sales and Distribution)
then give the Materials A, B, and C and give their respective quantities.
Before you have to create pricing condition records for Materials A, B, and C.
Then configure the item categories (Transaction code : VOV4).
When processing the sales order, just give the Material D and the system will pick up the corresponding
assemblies for that material and populate in the order.
The item category for the header item will be TAP and the item cateory for the items will be TAN.
In this case the Material D is called as the higher level Item, and all the assemblies are called as the sub
items. Here the subitems are relevant for pricing and delivery where as the header item is not relevant for
neither pricing nor delivery. It just acts as a text item.
This type of configaration of BOM is known as pricing at item level. This is used when you dont
know what quantities of assemblies the customer is going to order and if the price of the assembly keeps
varies.
There is another way of configaring BOM which is pricing at header level. The difference is that the
Material Master D has to be confugured using the item category group ERLA.
In Summary:
-->If you want Header price you create Header Materil with ERLA Itemcategory group.
-->If you want pricing at item level you create header material with LUMF Itemcategory group.
-->To create Sales BOM go to the Transactionaction CS01 there you give enter the data
Delivering Plant.
***Then proceed with enter system will take you the BOM detail screen here you maintain the details of
the components (How many components you need to make a Header material)
-->Now you can create sales order with the BOM material
Example:
You created an order for a material(R-1160 - hard disks) for a qty - 120 pieces.
You need to create a delivery and
A) Pack 40 pieces each of the material are grouped together into larger cardboard boxes (PK-100 -
shipping/packing material) and
Solution:
1) Go to [VL02N] to change the delivery, you already created. Or you can do the following steps while
you are creating a delivery also.
2) Go to "pack" icon.
5) Select both the lines of upper section and lower section and click the green ok. It generates a
shipping unit/handling unit number.
6) Now, select both lines of upper & lower section & click the button "per part. qty" (New HU per part
qty of material) Check: click "General Overview" icon to see whether it packed 40 pieces of material in 3
cartons.
2) Enter the packaging material (PK-095) in the upper section and select this line.
3) Select 3 lines of PK-100 in lower section since you want to pack them in PK-095.
5) Now all the 3 cartons (PK-100 with 40 pieces each of material) are packed in one big carton (PK-095).
To accumulate the amount of condition types in accounting document without affecting the pricing
display in billing document.
As an illustration:-
ZPXX 3500
ZDXX 1000
ZWXX 500-
Journal:
Dr Vendor2000
Cr Sales 2000 (ZPXX - ZDXX - ZWXX)
Mark the condition types you want to group as statistical and remove the account assignment key.
Create a subtotal in your pricing procedure that will add them together and put in the account assignment
key for it. This way the individual components will still display on your pricing screen but FI will only
get one posting.
What is the Transactionaction code for creating new pricing procedure and how to attach it to
specific plant?
You create PP in spro > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define
and Assign Pricing Procedures > Maintain Pricing Procedures
You can't attach PP to specific plant. Pricing Procedure is determined thru trx OVKK. The defining
parameters for pricing procedure determination are:
1. SalesOrg
2. Distribution Channel
3. Division
4. Document Procedure (defined in Sales doc\Billing doc maintenance)
5. Pricing procedure assigned to customer (defined in customer master)
1. Use Transaction code v/07 to create an access sequence and assign tables based on which you want to
carry on pricing as accesses.
2. Use Transaction code v/06 to define condition type. It can be for base price, discount, freight etc.,
While specifying requirement, we can give reqt no.22 which specifies that plant has to be set. This is
generally done for output taxes since output taxes depend upon the delivering plant. But directly there is
no assignment between plant and pricing procedure.
What is "alt cal type" & "alt base value" & "Requirement field" in the Pricing Procedure
Can any one explain exactly what is "alt cal type" & "alt base value" and also “Requirement field"
in the pricing procedure?
The alternate base value is used as the calculation basis only, while the alternate calculation is used to
modify the final value.
For example, imagine you have a condition type ZZ01, with a condition record maintained (master data)
for $100. Now, condition ZZ02 also exists lower in the schema, but with a rate of 10%. The standard
calculation would result in a final value of $110.
The alternate base value could say, "don't use $100 as the basis -- use the original price PR00 only, which
was $90." Then, the final value would be $100 + (10% of $90) = $109.
The alternate calculation routine says, "ignore the 10% altogether. Instead, use an externally calculated
20%." Then, you end up with a final value of $100 + (20% of $100) = $120.
Put them both together, and you could end up with $100 + (20% of $90) = $118.
Normally if you want to calculate a value you have to use a calculation type for determinating the value.
This calculation type is either addition, subtraction or multiplication. Similarly SAP also has got a default
calculation type in the control data of the condition type. There you have the options of either Qty based ,
Fixed Amount Based or Percentage based.
Here what happens is suppose if you define Your condition type that calculates the base price of a
material on Qty based. Then the calculation will be done based on the quantity of the material. If the
customer orders 10 Nos and you have maintained a unit price of 100 Rs for each material then the value
determined is 1000 INR. Similarly if the discount condition type , you maintain the calculation type as %.
This means if you maintain the value of 10 % in the condition record. Then this percentage is taken as
the calculation type and the condition value is determined.
In some cases you have to forego the default calculation types and use the customer specific method for
calculating a value. For ex if you are calculating the Freight charges for a Material . it depends on so
many criteria like, the weight, volume and also the minimum amount etc etc, in those cases, you forego
the default value and then use the alternative calculation type in calculating the condition value against
the particular condition.
If you have to calculate any value then you have to have a base value for it. For ex if you want to
calculate the discount of 10 % for a material then you have to have a base value on which this 10% is
calculated. Normally you take the condition value of the base price of the material to calculate the value.
Now you don't want to take the base value and take other values as base value which are derived on some
formulae. So you create a routine which will do the mathematical operations in the routine and derive you
a value which is now used as the base value for calculating the condition value for a particular condition
type.
Requirement:
A factor in the condition technique that restricts access to a condition table. The system only accesses a
condition table to determine the price if the requirement specified has been met.
Example:
The system uses an access sequence to determine the price of a material. One of the accesses in the
sequence contains the requirement "in foreign currency." The system only uses the table behind this
access if the sales order for which the price must be calculated is in a foreign currency.
Re-pricing in a Quotation
You can always 'Update" pricing manually in a quotation the same way you do in a sales order, either in
create or change modes. Menu path Edit --> New Pricing or press the 'Update pricing' button on the item
conditions tab.
If you are asking how to reprice a quotation when it converts into a sales order, that can be done with the
copy controls of the Item Category. IMG: Sales & Dist --> Sales --> --> Maintain Copy Control for Sales
Docs --> Sales Doc to Sales Doc (Transactionaction vtaa). Just choose the combination of documents and
the respective item category. The field you need to be concerned with is "Pricing type".
However, from a business process perspective it makes absolutely NO sense to reprice a quotation when
converting to a sales order. After all, the entire point of using quotations is to firm up details like pricing
before creating the sales order.
You're looking to implement quantity based discounts in 4.6c. You are trying to sell items in
specific bulk quantities, and only give the discount for specific quantity intervals.
For example, if a customer orders 1 piece, 2 pieces, 3, etc. of part ABC, the price is $100.
The only values for which $50 should apply are 10, 20, 30, etc. - multiples of the bulk quantity 10.
You have discussed changing your part number to reflect a bulk qty of 10, however you have in
house consumption that is allowed to consume only 1 part at a time. You would vastly prefer to
keep one part number that you order from the supplier, consume internally and ship externally.
You are fairly certain there is basic functionality that covers this, but you're just not sure where to
start.
Taking your requirements literally. Standard SAP scale pricing will not do it in that you only want the
reduced price to come into effect when the order quantity is multiple of some bulk factor.
It is agreed with that creating a separate material number is not a good idea.
1. Define/Select a UOM for selling in bulk (i.e. cas, pallet, box whatever)
2. Maintain UOM conversion between your base UOM and this new UOM
3. Configure you bulk pricing condition type by usual means (it should be a base price rather than
discount).
4. Place this new bulk price behind your normal "PR00" price in the pricing procedure
5. Create a new condition base value routine via VOFM where you check XKWERT to see if it is a whole
number. If it is not then set XKWERT to zero.
6. Assign this new routine to your bulk price condition in your pricing procedure in ALT condition base
value column.
You can update the condition pricing for a range of sales order.
For e.g. if you create sales order for 15 months or so, and at the beginning of each year, you have to
update the prices for lots of sales orders.
Other than using VA02 and make an Update of the conditions at item level which is a big work because
you will have lots of open sales order after so many months.
The first method is not to set the pricing condition VPRS as statistical.
Simply remove PR00 and it will work fine if you always use VPRS as your pricing base inside the
pricing procedure.
VPRS will reads both prices based on the price control in the material master.
Price control S for standard price. Price control V for moving average price.
It is this simple if you do not have any other "Prices" in the price procedure.
However, if you are using one pricing procedure where for some items you price using VPRS and some
others using PR00, then you should use requirement routines to enable the correct price condition type at
the right time.
The second method involves more work as you need to write a formula (VOFM) to get that information.
1. Set VPRS to be the first step in the pricing procedure and to be subtotal B (as standard).
2. Set PR00 with alt. calc. type formula, which sets the value of PR00 to be equal to the subtotal B.
RV64A901
FORM FRM_KONDI_WERT_600.
XKWERT = KOMP-WAVWR.
ENDFORM.
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER
FUNCTIONS
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER
FUNCTIONS
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER
FUNCTIONS
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; LOGISTICS GENERAL ->;
LOGISTICS BASIC DATA: BUSINESS PARTNERS ->; CUSTOMERS ->; CONTROL ->; DEFINE
ACCOUNT GROUPS AND FIELD SELECTION FOR CUSTOMER
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER
FUNCTIONS ->; GOTO ->; PARTNER FUNCTIONS ->; ENVIRONMENT ->; ACCOUNT GROUP
ASSIGNMENT
6) Assign the Partner Functions to the Partner Procedure for the Sales Document Header
Menu Path: Tools ->; Business Engineer ->; Customizing ->; Sales and Distribution ->; Basic Functions
->; Partner Determination ->; Define Partner Functions
7) Assign the Partner Functions to the Partner Procedure for the Sales Document Item (OPTIONAL)
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER
FUNCTIONS
8) Edit the Pricing Communication Structure (KOMKAZ) to Hold the New Functions (Client
Independent)
Menu Path: Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; DICTIONARY
Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR
Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR
Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR
The following code should be inserted into program MV45AFZZ to allow the system to re-execute
pricing if the user makes a change to the relevant partner function (alteration, addition, deletion).
13) Add the KOMKAZ Fields to the Pricing Field Catalog (Client Independent)
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE
ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE
ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES
15) Create an access sequence containing the new tables (Client Independent)
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE
ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE AND
ASSIGN PRICING PROCEDURES ->; MAINTAIN PRICING PROCEDURES
Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR
Billing
This SAP message will appear if the system is unable to find the G/L codes match from the configuration
in Transaction action VKOA
Diagnosis
No account was specified for account type "S" in item "0000001001" of the FI/CO document.
System Response
Procedure
A system error has probably occurred in the application you called up. Check the data Transaction
referred to item "0000001001" of the FI/CO document.
Assuming that one of the key combination is Account Assignment Group, you will have to check whether
have the Account Assignment Group been input in the Customer Master (Billing tab strips - Accounting
sections - Field name: Acct assgmt group).
The Account Assignment Group will be copied automatically into the sales order.
Check whether the configuration in Transaction action VKOA have been done correctly.
Check whether the sales order (VA03 – Go to - Header - Financial Accounting - Field name:
AcctAssgGr) have been filled in automatically.
Check whether the billing document (VF03 – Go to - Header - Header - Field name: Acct Assg Gr) have
been filled in automatically.
If the customer master have not been maintained and the user have already input the sales order, then the
user will have to maintained the Account Assignment Group manually either in the sales order or the
billing documents.
Take note for One Time Customer, the user have to input the Account Assignment Group manually into
the sales order. One Time Customer can be used by many customers; therefore, the system will not be
able to determine the Account Assignment Group manually.
One is the selection variant before clicking the Display Billing List Button.
You can set the start variant via SE93 using the Change mode.
After creating your layout display variant, you can set it by clicking:-
The system can exclude conditions so that they are not taken into account during pricing.
For example:
Material 4711 cost 150 USD. Some customers receive a discount of 10 USD per 100 pieces.
However, a specific customer can buy the material for 100 USD. Since this is a particularly good price,
the customer should not also have a discount of 10 USD per 100 pieces. Therefore, this discount is to be
excluded from pricing.
To create a condition exclusion procedure which will be determined in the billing document.
1. Assign the procedure to the pricing schema, and maintain copy control so that pricing is not copied
from Sales Order.
6. Assign the Condition type for the Condition Exclusion Groups in OV32.
7. Assign the Billing Pricing Procedure in VOK8 for the Condition Exclusion Groups.
When billing document is being created just enter manually your new price and the pricing program logic
will include only the higher price one, excluding the rest that are lower price.
1) To block automatic Transactionfer of the billing document to accounting, mark the field.
Indicates whether the system blocks automatic Transactionfer of the billing document to
accounting.
During document processing, you can manually Transactionfer blocked billing documents to
accounting by selecting:
3) Cancellation billing document type partner functions A check is made to see if the
cancellation billing document type partner functions are empty or if those that
correspond to the billing type used are empty.
Next, make sure that you maintain the copy control for the Billing Types:
Target Source
Deliveries in VTFL
Define the possible block indicators in SM30 - V_TVFS and allocate them to the billing types concerned
in SM30
V_TVFSP.
Your Billing Block will not work if you did not assign it to the desired billing types.
2. Item categories in SM30 - V_TVAP, by filling the fields Billing Block.
8. Define rules for determining the date in OVBS. Milestone billing is typically used for billing projects,
such as plant engineering and construction projects. Such projects often include a series of milestones that
mark the completion of different stages of the work. In the SAP R/3 System, milestones are defined in a
network along with planned and actual dates for the completion of work. The milestones are also assigned
to the billing dates in the billing plan. Each milestone-related billing date is blocked for processing until
the Project System confirms that the milestone is completed. Delivery-relevant order items for which a
milestone billing plan applies are billed on the basis of the requested delivery quantity and not on the total
of the confirmed quantities. The connection between the project and the sales document item is made in
the individual schedule lines of the item. Each schedule item can be assigned to a network in a project. To
display the project-related data for a schedule line, proceed as follows: In one of the overview screens of
the sales document, select 1. Item -> Schedule lines. 2. Mark the schedule line and select Procurement
details. The following figure shows an example of milestone billing where only the Contract have been
billed : Order Item Turbine 100,000 Billing Plan Billing date Description % Value Billing Block
Milestone Billing Status 01-10-94 Contract 10 10,000 - x x 01-03-95
Assembly 30 30,000 x x 01-04-95 Maintenance 30 30,000 x x 01-05-
95 Acceptance 30 30,000 x x 01-06-95 Final invoice .. .. x Network/Activities
Milestone Estimate Actual Assembly 01-03-95 01-03-95 Maintenance 01-04-95
Acceptance 01-05-95 For each billing date in a milestone billing plan, you can specify whether the
billing date is: 1. fixed 2. always updated with the actual date of the milestone 3. updated with the
actual date of the milestone, if the date is earlier than the planned billing date for the date
In VF06 or background: variant with parametrization) to avoid an unwanted split due to the billing date.
In transaction VTFA (if your billing is sales order based) choose your billing type and SO type, there
select your item categories and there select the field VBRK/VBRP data. In that field you will see the
currently used routine. With the help of your ABAP guy create a copy of that routine under a different
number and add your lines of code. Let's say you use routine 001.
FORM DATEN_KOPIEREN_001.
END OF ZUK.
ZUK-SPART = VBAK-SPART.
ZUK-VTWEG = VBAK-VTWEG.
VBRK-ZUKRI = ZUK.
ENDFORM.
After this routine is created and activated place it as the default copy control routine instead of the old
ones.
Maximum number of items in FI reached Message no. F5 727
If you hit the above erros when you create an invoice in SD, the corresponding accounting document is
not created.
Diagnosis
The maximum number of items for an FI document ('999') has been exceeded.
System response
FI documents have a 3-digit item counter that limits the number of items permitted per document.
Procedure
If the documents with an excessive number of items come from another application area
(e.g. sales, logistics, order accounting), you can configure the system to the effect that
these documents are summarized in FI. "
How could this error be solved as none of your invoices are getting accounted in FI?
To overcome this, the only way was to break the accounting invoices, 1 with 950 items and the other with
the rest.
This is where you can define a maximum number of items allowed for all billing documents within a
given sales organization.
However, maintaining data here is not enough alone to bring about a billing split by number of billing
items.
You must also go to copying control for order/delivery to billing document at item level under "Data
VBRK/VBRP" and maintain routine 006 "individual invoice limited" or a similar routine that accesses the
data maintained here.
Credit Management
Credit and risk management takes place in the credit control area. According to your corporate
requirements, you can implement credit management that is centralized, decentralized, or somewhere in
between.
An organizational unit that represents the area where customer credit is awarded and monitored. This
organizational unit can either be a single or several company codes, if credit control is performed across
several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of
your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit
control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up
credit control areas and other data related to credit management in Customizing for Financial Accounting.
The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial
Accounting and then Maintain credit control area. You assign customers to specific credit control areas
and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into
account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction codeOB38
4. Transaction codeSE37
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction code
OB45 or the credit control area must be entered under the relevant company code in table
Delivery type:
9. Transaction codeOB01
Definition of the risk category for each credit control area. This risk category can be
Credit control area, risk category, credit group are set. Take these key fields from the above settings and
go to the detail screen. In particular, check whether fields "Reaction" and "Status/block" are set correctly.
To carry out follow-up actions in case of a credit block, the credit check
12. Settings for updating the credit values Update of the credit values is required for the limit
Update of the credit value is active for the corresponding item type if the check box is marked. This
field corresponds to field "Active receivable" in Transaction codeVOV7.
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
Determining the credit value (mark the pricing procedure and double click on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this
subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Which update group (field "Update") do you use in the relevant credit control area? The
Default setting is "12". If you use another update group, check whether this is fine with
you. If you open an OSS message, please tell us the alternative update group.
In any case, "Synchronous update (1)" has to be chosen as the kind of update.
How to block the requirement (MD04) generated by the item category in a sales order when the customer
has attained the credit limit? The MRP requirements still appear even though the schedule is zero.
Try using routine 103, you may have to tweak if it doesn't work exactly as you'd like.
For example, you can write a routine 903 because you only wanted this reaction for certain business units.
Irregardless, using a routine similar to this will prevent the requirement from appearing in MD04 for
orders blocked on credit.
Code:
FROM ZSD_CREDITBLCK
IF W_CMGST = SPACE.
MESSAGE I706(Z1).
ENDIF.
*} REPLACE
*{ INSERT DEVK966908 1
*} INSERT
CHANGING FOFUN_TEXT.
WITH FOFUN_TEXT
RAISING ERROR.
*{ INSERT DEVK966908 2
*} INSERT
ENDIF.
ENDFORM.
Explain in detail difference between simple and automatic credit check types. In automatic check,
difference between static and dynamic checks.
Open Item : Sales Order has been saved , Delivered, Billed & Transactionfered to FI, but not received the
payment from the customer.
AUTOMATIC CREDIT CHECK: Give extra credit facilities to the particular customer.
STATIC CREDIT LIMIT DETERMINATION: Checking Group + Risk Catageory + Credit Control
Area.
A) Credit Checking Groups: Types of Checking Groups.
01) Sales
02) Deliveries
03) Goods Issue
At all the above 3 levels orders can be blocked.
B) Risk Catageory: Based on the risk Catageories Company decides how much credit has to give to
the customer.
Static Credit Check it checks all these doc value & check with the credit limit
1) Open Doc.Value / Sales Order Value: Which is save but not delievered
4) Open Item: This is Transactionfered to FI but not received from the customer.
Here the System will not consider the above 1, 2, 3& 4 values for the lost 3 months
Credit Limit Check for Delivery Type: Del.Type (LF) + Del Credit Group (02) + Goods Issue Credit
Group (03)
Action: Define a credit control area and its associated currency. The Update Group should be ‘00012’.
This entry is required so the sales order will calculate the value to authorize
Action: Assign a default credit control area for each company code
Action: For each company code enter every credit control area that can be used
Action: Towards the end of the pricing procedure, after all pricing and tax determination, create a
subtotal line to store the value of the price plus any sales tax. Make the following entries:
Sub to: “A” ; Reqt: “2” ; AltCTy: “4” ; Automatic Credit Checking ; Transaction action: OVA8
Tables: T691F
Action: Select each combination of credit control areas, risk categories and document types for which
credit checking should be bypassed. You need to mark the field “no Credit Check” with the valid number
for sales documents.
Action: R/3 is delivered with form “02” defined for payment cards. Other than the descriptor, the only
other entry should be “3” in the column labeled “PymtGuaCat”
Transaction action:
Tables: T691M/T691O
Forms of Payment Guarantee and make the following entries Sequential Number “1”
Routine Number“0” Routine Number can be used to validate payment card presence.
Transaction action:
Tables: T691P
Create Customer Payment Guarantee = “Payment Card Payment Cards (All Customers can use Payment
Cards)”.
Transaction action:
Tables: T691R
Action: Define the flag that will be associated with sales document types that are relevant for payment
cards
Transaction action:
Tables: TVAK
Action: Assign the document flag type the sales documents types that are relevant for payment cards.
Tables: T691U
Action: Combine the Customer flag and the sales document flag to derive the payment guarantee
procedure
Transaction action:
Tables: TVCIN
Action: Create the different card types plus the routine that validates the card for length and prefix (etc…)
The Routines can be created based on the original routines delivered by SAP.
*****SAP does not deliver a card check for Discover Card. We created our own routine.
Transaction action:
Tables: TVCTY
Action: Define the card category to determine if a payment card is a credit card or a procurement card.
Transaction action:
Tables: TVCTD
Action: For each card category map the account number range to a card category. Multiple ranges are
possible for each card category or a masking technique can be used. Get the card number ranges from
user community. Below is just a sample of what I am aware are the different types of cards.
400000, 405500, 405505, 405549, 405555, 415927, 415929, 424603, 424606, 427532
428800428899
540500540599 555000556999
340000349999 370000379999
601100601199
Transaction action:
Tables: TVAK
Action: Review the listing of Sales Document types and enter “03” in the column labeled “PT” for each
type which can accept a payment card
Tables: TFRM
Action: Define and activate the abap requirement that determines when an authorization is sent. Note that
the following tables are available to be used in the abap requirement (VBAK, VBAP, VBKD, VBUK, and
VBUP).
Transaction action:
Tables: CCPGA
Action: Define a checking group and enter the description. Then follow the below guidelines for the
remaining fields to be filled.
PreAu If checked R/3 will request an authorization for a .01 and the authorization will be flagged as
such. (Insight does not use pre-authorization check).
A horizon This is the days in the future SAP will use to determine the value to authorize
Valid You will get warning message if the payment card is expiring within 30 days of order entry date.
Transaction action:
Tables: TVAK
Action: Assign the checking group to the sales order types relevant for payment cards
Transaction action:
Tables: TVCIN
Action: For each card type enter the authorization validity period in days.
DC Discover card 30
MC Master card 30
VISA Visa7
Configuration for clearing houses
Tables:
Action: Two General Ledger accounts need to be created for each payment card type. One for A/R
reconciliation purposes and one for credit card clearing.
Tables: T685
Action: Define a condition type for account determination and assign it to access sequence “A001”
Action: Define procedure name and select the procedure for control. Enter the condition type defined in
the previous step.
Transaction action:
Tables:
Action: Determine which billing type we are using for payment card process.
Transaction action:
Tables: TCCAA
Action: Define the general ledger accounts for reconciliation and clearing and assign the function
modules for authorization and settlement along with the proper RFC destinations for each.
Transaction action:
Tables: TCCM
Action: Create the merchant id’s that the company uses to process payment cards
Assign merchant id’s
Transaction action:
Tables: TCCAA
1) You have a Customer which you had felt, he is doing good business and supplied material on Credit of
45 days.
2) Since this customer is good as you felt, you have not managed Credit Checks as well. So, he had
comfortably reached to the fullest credit (or even more) which you can afford for any customer.
3) One fine day you got realized that, there is very bad debt with this customer and need to recover from
him and till then, there will be no further supply to the customer.
4) Your company's legal department has laid a policy that, in order to recover any bad debts, like:
b) In case customer doesn’t respond, we will send at least further reminder (dunning notice) may be 9
times (9 reminders) (Dunning level) and what intervals of time (dunning frequency)
c) Still if the customer doesn’t respond for the reminders, you will file a law suit against the customer for
recovering the Payments.
d) Finally, after getting verdict, you may proceed for auction of his property or as per the order for Law.
Now in SAP, the definition of Dunning procedure is a pre-defined procedure specifying how customers or
vendors are dunned.
- Dunning frequency
- Amount limits
In SAP, you will maintain the Dunning Procedure at customer master. Referring to this your SD Team /
FI Team (user team) will affect Dunning
PS: You might remembered the dunning procedure laid by Relaince Mobile, sometime back, sending
street rowdies for recovering the bad debts from users. That is dunning. Remember Reliance, you will not
forget dunning forever.
Sales Order
When end user created a new sales order with VA01, default First Date wasn't today, why?
Note:
Although you mention that nobody change the system configuration, it is very unlikely that the system
will mis-behaved after one day.
Usually, after checking, you will find that someone have actually change the configuration as it could not
be a software bug since you have been using it for quite sometime without any problems.
The date is control by each Sales Order Type for each Sales Document type whether is it a
- OR - Standard Order,
- RE - Returns etc.
Verify the Sales order type configuration with the following path:
IMG: Sales and Distribution --> Sales --> Sales Docs --> Sales Doc Hdr --> Define Sales Doc Types
(Transaction action vov8) will let you control this by sales document type.
There is one field (Lead time in days) which "specify the number of days after the current date that the
proposal for the requested delivery date in the sales document should be".
This should be blank if you want the system to propose current day for delivery date.
How can I make the system auto create all the Sales Order date during creation?
Follows this step to set the default Sales Order Type proposal date:
- Look and tick the fields Propose delivery date and Propose PO date.
After making the necessary IMG changes, you need to input the Delivery Plant field for each Materials
that you want the system to propose the default date.
Goto MM02, Select the View Sales: Sales Org. Data 1 and fill in the Delivery Plant.
Testing:
Now, try creating a new sales order for the material and SAP will auto proposed all the dates in the sales
order.
Define whether the Material can be used at which Sales and Distribution process
Here you define how the system responds when entering a sales and distribution document
with this material in the differenet Sales and Distribution Process Flow..
You can use the material status, for example, to prevent orders from being entered for
Parts to be discontinued.
OR
Set the material status parameters in Transaction action SM30, Table Views V_TVMS.
The Cost Center Determination settings is in OVF3 - but there are some cases where the Cost
Center must be exceptionally changed.
If the document category for order type in IMG VOV8 is defined to be "I" which belong to order
type FD - Deliv.Free of Charge, then the field cost center is active for input during
Transactionaction VA01.
Alternatively, you can specify an order reason and assign a cost center to an order reason.
However the standard SAP works only at the header level though, so it would not work if cost
center is needed on the line item.
The cost center are assign for such business Transactionactions as:
- Free deliveries
- Returns
- Deliveries of advertising materials
You can also make cost center allocation dependent on the order reason, for example:
Both the IMG settings are done in Transaction action OVF3, either with/without the order reason.
Transfer of Requirements
The MRP department is informed about the quantities and deadlines by which incoming orders should be
delivered. The system checks the availability of the goods based on the requested delivery date of the
customer and creates MRP records which contain all necessary information for passing on to planning. It
ensures that the goods are available in time for the delivery. Materials planning Transactionfers the
reported requirements and creates orders or purchase requisitions from them etc.
For controlling Transactionfer of requirements, you have to carry out the following steps:
2. The Transactionfer of requirements must be switched on at requirements class level, the sales
documents at schedule line level.
3. You must define a check group. It is possible to have this check group proposed for the initial
creation of a material master record.
4. Note that a plant must exist for Transactionfer of requirements to be carried out at document item
level. OVZG - Requirement class It specifies the following points: - whether an availability check
and a Transactionfer of requirements is carried out for a Transactionaction (for sales documents, fine
tuning using the schedule line category is possible), - whether the requirements are relevant for MRP, -
the allocation indicator from the sales view which controls the settlement of customer requirements with
requirements - whether an item is to be settled to an auxiliary account assignment, - the settlement
profile, - the results analysis key. (Use Transactionaction SM30 for V_* configuration) OVZH -
Requirements type V_TVEPZ_V - Assignment of requirement type to Transactionaction V_TVEP_V -
Schedule line category OVZ2 - Define Checking Group V_TMVFU - Define the checking group
that the system proposes when you create a new material master record. You can overwrite the
default value for the checking group in the material master record.
You specify the valid tax types in Transactionaction OVK1. More than one tax type can be defined for a
country by defining the sequence.
In the standard SAP R/3 System, the elements of tax calculation are predefined (for example, tax
condition type "MWST" for taxes on sales and purchases).
Assign the plant for Tax Determination in OX10, using the country key, the SAP System recognizes
which tax type is valid for a plant and thus which taxes are relevant when creating an SD document.
Define the Customer Taxes in OVK3; you will maintain the tax code in Customer Master.
Define the Material Taxes in OVK4, which will then be maintaining in Material Master.
For example:-
MWST GST 0 TaxExempt
MWST GST 1 Liable for Taxes
In this example, if both the Customer Master and Material Master Tax code is 1, Tax will be included
when you create the Sales Order.
Define whether the Material can be used at which Sales and Distribution process
How can we maintain the Tax Code (Tax code - which we maintain in MWST Condtion Records) in
Customer Master or in Sales Order?
1) MWST is a tax condition which is applied to customer to whom we are selling. The rate of tax is
depend on various parameteres, whether is fully liable for tax or expemted (in case of Defence Customer)
2) There are few parameteres which we apply tax condition. Whether customer is tax liable? Whether
material is tax exempted?
For example, if you are selling a goods which are free for tax to any customer, put the Tax Indicator (at
MMR as '0'). If your
material is tax liable pur the Tax Indicator (at MMR as 1). If your customer is not liable for tax at all (like
the case of Indian
Defence organisations) put the Tax Indicator (at CMR as 0) or 1 in case fully tax liable.
3) Now, at VK11 you need to mainatain your pricning conditions with all the combinations like:
1 0
1 1
0 1
0 0
4) While maintaining your Material Master Records or Cusotmer Master Records, you must identify,
which are tax liable and which are tax exempeted.
5) In anycase, as a SAP standard Best Practises, while processing a sales order, you must retrieve a Tax
condition record from SAP database only and not entered manually. Accordingly, at V/06, the MWST
condition Defintions, the field for 'Manual Entries', it would be marked as - D (Not possible to process
manually).
Due to this setting, normally, you cannot maintain Condition tax code during sales order processing. And
in Cusotmer Master, you can only maintain Tax Indicator and not Tax Code.
6) In case your client insists for Manual entry of Tax code during Sales Order processing, you can change
the field at point 5) above to C-Manual entry is priority instead of D.
I'm assuming that, the country is India and based on its requirement:
Sales tax is a state government revenue. There are two types of sales taxes, Local sales tax & central sales
tax. Local sales tax is intra state whereas CST is inter state.
Example of LST : Point of sale i.e. delivering plant & ship to party are within the same state. The rates
are defined by the respective state governments.
Example of CST : The Delivering plant & Ship to party geographic locations are 2 different states. At the
point of sales from one state, the ST goes to that state govt. & consignment is despatched to the Ship to
party. Once that consignment is received at the ship to party state, sales tax will be levied once the sales is
registered there. For this case, the LST that is applicable by the Ship to party further will not be applicable
in all probability to be captured in SAP.
Stock Transactionfer : This does not attract any sales tax. The consignment is Transactionferred from one
D plant to another D plant irrespective of inter/intra state sales. The invoice that is accompanied with the
consignment thus shall not have any final value. It's a zero value invoice, but the basic prices needed to be
mentioned.
The selling organisations normally needs to register with the sales tax authority of the respective state to
have a warehouse or D plant to avoid the double taxation for their dealers/distributors.
Now, the pricing procedure that is there in 4.7 is Factory sale with formula-JFACT, in which the CST
condition type is JIN1 & the LST is probably JIN2. There may be surcharge cond types as well which
will calculate the amount on either JIN1 or JIN2.
For config :
1.SPRO > S&D > Basic fn. > Pricing > Pricing control > Define & assign Pric. procedure > Maintain Pric
proc.
2. The tax rates are normally driven from the Tax classification of Customer & Material access. To do
this config, S&D >Basic fn. > Taxes. You need to include the condition type for country IN in 'Define tax
determin rule'.
3. Same path : But go to Tax relevancy of master records where you configure the condition type &
options of rates that will flow to these masters. One needs to understand here properly as u need to have
unique combinations for picking the sales tax rates. I will try to demonstrate the smallest example. Let's
say, the LST rates are 2%,4% & 0%. I will have two options for material master here. 1 for taxable & 2
for not taxable.
For customer master, I will have 1-LST 2%, 2-LST4% & 3-LST0%. When I create master records for
LST thru VK11 for JIN2, I will chose the access where the combinations of customer & material tax
classifications are available. If this access does not exist create it under an access sequence. But normally
this is standard. The condition records will look like,
Cust-Tax classi. Material tax claasi. Rate Tax code
1 1 2% A1
2 1 4% A1
3 1 0% A1
Remember, rates are flown from the tax codes. Tax codes can be created thru T code FTXP. This is
normally a FI job.
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
(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 quantities. 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 quantities 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 quantities are sometimes requested by the customer on ASNs.
Cumulative quantities 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 quantities and entering standard sales orders (with or without multiple schedule lines) to
represent the true firm quantities.
There is Transactionaction MASS which can be used to carry out mass changes in the sales order and
other objects.
Mass Maintenance: (Use to change multiple fields in multiple documents at the same time). I have done
mass change for customers; and orders should work the same way too.
2) Choose the table or tables for your selection criteria and also for fields you want to change.
Then execute. (Suppose your selection criteria fields are from "sales order header data" table and the field
you want to change, is in "item data" table)
3) Put in the sales documents (21000000, 21000001) you want to change and also the items(10) you want
to change.
- click on " choose selection fields" button
- From the Pool, move the fields you want to the "select fields" using arrows.
5) In "sales order item data" tab, you see the new value of the plant you entered at the top and the old
values of item 10 are below.
-click on "change field values" button. you see all the old values are changed to new values.
-save
Note: it will take some time depending on how many records you have.
Check: Go to [SM37] and see the status of the job you are running and once finished, export the spool
file to a spreadsheet.
Before you do mass maintenance, go to the particular table in [se16] and get the results. Then do the
mass maintenance and compare the results with this one. If they match, then you are good to go.
Note: If you have any user exits that affect the results, ask them to deactivate the MODCHECKS still
you are done with mass maintenance & activate them again.
Is there a way to change the billing date on a ton of sales orders with same old billing date to a same
new billing date?
Suggestion is to test this on a few orders in your development system to get a feel on how this works
before applying this to any production data. MASS is a very powerful tool.
I have 100000 sales orders whith an incorrect price and I would like to do a massive condition
update with pricing type "B" (Carry out new pricing). Is there a Transactionaction or program for
this?
Go to VA05 execute the report. Select all sales orders you want to update the price, Go to the Menu EDIT
--> MASS Change ---> New Pricing. System will display all the re-pricing options. Select B. It will re-
price all the sales orders.
You can try for one or two order initially check the results and if it is OK, then you can do for others.
Condition Technique :
Rebates, use the condition technique, but distinguish themselves from pricing in applying to
Transactionactions over time, versus on a Transactionaction basis. Rebates have their wn field catalog
and their own condition table naming convention.So you could have two condition tables "001" one for
pricing and one for rebates, which could have different key fields. You need to use the technical names
A001 For pricing and KOTe001 for rebates when you use the query type using Transactionaction SE 16.
Use create access sequence (AS). Enter 1 in field category for rebate specific. As after going thru the
right path of maintaining access sequence for rebates.
The big difference between the rebate and the pricing access sequence is that there is no exclsuion flag
available for rebate related AS. This means multiple tables for an access sequence can be aplied at the
same time.
Rebate related condition types are identified by codnition class -C.
After defining and creating condition types for rebated include them in the pricing proceedure. The
requirement should be 24 here which imply that the accruals are calculated on the basis of invoice/bill.
The other fields- alctyp and altcbv does not allow you to manipulate how a rebate is calculated. Also,
remove the requiremnt 24, if u wants to see reabtes at order time.
These accurals are based on sales volume and when they are posted billing is created int eh follwoing
manner. Provision for accruals is debited and Sales revenue is credited. When rebate credit memo is
created
Customer account/ is debited and
Accrual provision account is credited.
Rebate agreemnts is based on agreement types.Conditon records which are created like B001 and B002
are linked to the rebate agreeements specifying the rebate rate + the accrual rates.condition records
specify the rebate rate and the accrual rates.
Consider an example.
You decided to give a rebate of 3% to a customer whose sales vol is $1000 for a particular SO
Then the rebate value is $30..
Now when you make the rebate settlement by doiing the Credit memo and you decide to pay $27, then
the accounting will be generated saying 27$ paid towards rebate and 3$ is the accrual which you owe to
the customer
Procedure:
Rebate agreement: Transactionaction code: VB01
When you go to VB01, choose agreement type 0002 and then in conditions give
Material rebate
1 20
2 30
Now create a sales order with a material say M-11 for SOrg 1000 12 00 with QTY 6
Now check VB03 and see rebate agreemtent it will say Accruals 120 and payments 0
since your rebate is not settled still.
Rebate setllement
Go to VB02 enter ur sales deal no, and change the agreemetn status to B then enter Shift+F12 and enter
the amount to be paid for example u say $80
Then check in rebate payments rebate doc and partial setllemetn since you have not paid in full.
Then go to VF01 and enter the credit memo reqst no generated...save the doc no and go to VF02 and say
release to accounting
Accruals: 120; Accrual reversed: 80; Rebate pay: 80; Amount payable: 40
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 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
The following are the T-codes for central creation of customer master.
You need to identify various parameters within each Account group based on which the reco account is
identified within the customer master.
- 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.
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.
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
No
4. Org structure:
Relation between Company - Sales org
One-to-Many
Sales Org - Plants & company vs. Plants
The Existing system on which current system is working, from which the current system will be migrated
to SAP system
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, Transactionaction 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 Transactionaction 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.
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.
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.
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.
System will not go to asscess condition type system will reply through formula.
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.
3. Few client requirements for customer master, material master, Organization and
Transactionactions.
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 client’s 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 Transactionactions are concerned not all the users are allowed to run all the
Transactionactions. Here the user roles are defined as per the BPO's (i.e., the user is given authorization
only to run certain Transactionactions 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 Transactionaction
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
Transactionactions which allow to view reports that are needed daily by the management.
How to restrict users for not changing some fields in T-code va02?
You can very well delete sales order using Transactionaction 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.
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
Here you have a consignment fillup order and a consignment fillup delivery.
Here you have a consignment issue order, consignment issue delivery and a consignment issue invoice.
(the flow is very similar to a normal OR flow, but the materials are issued from the consignment stock
instead of plant stock unrestricted).
Consignment return (return materials from customer ownership to customer consignment).
Here you have a consignment return order, consignment return delivery and a consignment return invoice.
(the flow is very similar to a normal RE flow, but the materials are returned to the consignment stock
instead of plant stock returns).
Here you have a consignment pickup order and a consignment pickup delivery.
Note that in consignment fill up and consignment pickup there are no invoices since there is no change of
ownership for the materials.
In consignment orders you are allowing the stock to sit in your customer location. Once he informs that
he used the stock you will invoice him. If he returns the stock you will accept the stock to take it back.
It is defined in 4 steps.
In this step, you are not invoicing the customer. document flow is sales order ---- delivery item category.
It will not be relevent for billing and pricing because you are not charging money for these goods in this
step.
In schedule line category, you will set movement type 631 & set for availability check and TOR.
2. Consignment Issue.
Once the customer informed you that he used all the goods or partial goods then you will create
consignment issue for used goods.
Sales document: KE
Here you are invoicing the customer (because he used the goods). You are assigning the delivery documnt
and billing document to the sales document.
In item category, you are setting relevent for billing, pricing, special stock.
In schedule line category, your setting is 633 movement type, relevent for availability check & TOR.
3. Consignment Return:
Customer found that some goods are damaged or he not able to sold the goods he want to send it back.
That you are creating this document.
You will assign delivery document and billing to sales document. you will create return order, return
delivery, return billing.
Your setting item category relevent for billing, returns, pricing, special stock.
Your setting schedule line item category: 634 movement type, NO availability NO TOR.
Even if you create the consignment return the goods are not come to direct to your plant. For that you
need to create consignment pick up. Here the owner ship is not changing so you do not need to create
billing.
Sales document: KA
Your setting item category relevent for returns. any shedule line category relevent for 632 movement
type, MRP, availability check, delivery.
This is regarding number ranges defining and assigning tips which you can follow as below:
Whenever there is a new Sales Org being created, you will be required to maintain Number Ranges for
Sales Documents which are allowed for your New Sales Area.
Number Ranges can be maintained Internally by the system, however it can be maintained externally also
if you customize it accordingly.
In Standard SAP the Transactionaction code for Maintaiing Number ranges externally is VN01.
Defining - The same can be reached through in IMG as : Sales & Distribution-->Sales-->Sales Document
Header-->Define Number Ranges for Sales Documents.
Number range Key +Start Number range+ End Number Range+Current Number
The Current Number field will be kept zero as you are proposing new number range and no sales
documents have been created on it , Obviously..
*1 is a Unique Two digit Alphanumeric Key, while proposing your key, you should ensure that it should
not be there in the system as existing.
If you propose a key that is there in the system or if the Number Range (Start and End Series) is there in
the system already, the system will throw a message that Interval already already exists. So choose a key
that is unique, and which is not there in the system.
Here , by making this , you are assigning a Key to a Number Range Series.
All the symbols can be used along with numbers from 0 to 9 and Alphabets from A to Z and in any order.
For example: !1, ^A, BB,Z*,M2.........
Assigning - In Assigning, you assign the particular Sales Document to the Number Range you have
already proposed as above.
The Two digit Alpha Numeric Key is maintained or Assigned to the respective Sales Document type in
V0V8.
Locate the particular Sales Doc Type, and double click on it to display it configuration. Here you put the
Two Digit Number key in the Field- "Number range External Assignment"
Besides this:
If a new Shipping Point is created then Delivery Number ranges are required to be maintained.
Similarly,
If a new Plant is created then Billing Number Ranges are required to be maintained.
What is Debit note and Credit note
What is Debit note and Credit note? What is the purpose? How we create?
1. A Transaction action that reduces Amounts Receivable from a customer is a credit memo. For eg. The
customer could return damaged goods. A debit memo is a Transaction action that reduces Amounts
Payable to a vendor because; you send damaged goods back to your vendor.
2. Credit memo request is a sales document used in complaints processing to request a credit memo for a
customer. If the price calculated for the customer is too high, for example, because the wrong scale prices
were used or a discount was forgotten, you can create a credit memo request. The credit memo request is
blocked for further processing so that it can be checked. If the request is approved, you can remove the
block. The system uses the credit memo request to create a credit memo.
You can use credit memos in Sales and Distribution (SD) for assigning credit memo requests to the open
invoices and in Financial Accounting (FI) for assigning credit memos and payments to the open invoices
and carry out clearing with them. If you use both Financial Accounting (FI) and Sales and Distribution
(SD), there is a 1:1 relationship between the credit memo request and the credit memo item posted in
Financial Accounting (FI). As soon as you bill the credit memo request together with other sales orders,
or distribute the items of one credit memo request to several billing documents, the assignment is no
longer valid and the system will not process it.
For credit memos, credit memo requests, and payments, you have the following assignment options:
When you post credit memos, the payment programme processes them automatically. If the credit memo
is specifically related to a particular open invoice item, the payment program automatically attempts to
offset the credit memo against the open item. If it is not possible to completely offset the credit memo
against an invoice, you can post a debit memo to the vendor, who is to reimburse the amount. Then you
can apply a multilevel dunning program.
3. Debit memo request is a sales document used in complaints processing to request a debit memo for a
customer. If the prices calculated for the customer were too low, for example, calculated with the wrong
scaled prices, you can create a debit memo request. The debit memo request can be blocked so that it can
be checked. When it has been approved, you can remove the block. It is like a standard order. The system
uses the debit memo request to create a debit memo.
4. As mentioned above, creating a credit or debit memo request enables you to create credit or debit
memos based on a complaint. For this first create a sales document with the order type for a credit or
debit memo request. You can create the debit or credit memo requests in the following ways:
In all cases, you specify the value or quantity that should be in the credit or debit memo
5. You can block the credit or debit memo request from being billed in Customizing. Go to Sales -> Sales
Documents -> Sales document header -> Define sales document type and select the billing block field in
the billing section. This request can later be reviewed along with similar ones, - if necessary, by another
department. The request for a credit or debit memo can then be approved or rejected.
Tables/Tcodes in SAP SD
Important Tables for SAP SD Sales and Distribution: Table Description Customers
I raise a sales order and is getting a error stating that "sales area is not defined".
2) At VOPA-->Assign Partner Determination procedure to your Account Group of Customer Master you
are using.
3) At VOPA--> Assign Partner Functions to your Account Group & Partner Determination procedure
Steps to create a Vendor Master Data at the client level and how do we extend it to different
company codes?
a) Purchases A/c
b) S. creditors A/c
a) KA
b) KG
c) KR
d) KZ
Spro --> Production --> Production Planning --> Demand Management --> Planned Independent
Requirements --> Planning Strategy --> Define Strategy Group.
We can see Strategy Group in Material Master Record - MRP 3 - Planning -- Strategy Group.
10 - For Make to Order
20 - For Make to Stock
Spro --> Sales and Distribution --> Sales --> Sales Documents --> Sales Document Item --> Define Item
Category Usage
Item Category Usage: item category usages which control the usage of an item. Item category usage
controls, for example, the system response if during document processing an item does not refer to a
material but to a text item. Item category usage can also be maintained via the item categories
In contracts we are creating quantity contract and value contracts in that we only put the validity period
after validity period that contract will close,but customer want before one month closing the period
system should alert with popup box like this contract is going to close, for this sales manager can follow
up the customer for renual the contract.
Getting a pop-up when the Contract is going to expire is not a Standard SAP thing. For this you need to
do some programming. Instead of this the Std system has a reminder system where in the open Contracts
and Quotaions are popped up when you about to create a sales order.
This setting is in the Sales order header ,
Goto -- VOV8 --- Quotation and Outline agreement messages
If you want to have different number range for different sales area where the settings to be done.
Number Rage are use to define what number to be assign to sales document type. Number range can be
assign Internal or external.
In internal number range system automatically assign a number to sales document according to number
range define in system.
The Logistics Information System (LIS) is made up of the following information systems:
In the standard system, the following information structures are available in the Sales Information
System:
S001 "Customer"
S002 "Sales office"
S003 "Sales organization"
S004 "Material"
S005 "Shipping point"
S006 "Sales employee "
These information structures form the data basis for the respective standard analysis of the same name.
In addition to the above information structures, the standard shipment also includes information structures
that are used internally (S066/67 Credit Management, S060 rebate processing and S009/14 sales support).
I am trying to see the standard analysis for the customer in MCTA Transactionaction.
But it is not showing all the invoices which I done in a day. It shows only a latest created invoice
details.
MCTA is reading data in table S001, which will not give invoice details as this is a summation of data
based on the billing date. T-code MCVV will allow you to simulate how a single invoice would update all
SIS structures.
You would need to create a custom SIS structure and add the invoice as a characteristic. Use S600 - S999
in the customer namespace then MCSI to execute any custom reports.
Run MC22 and re-generate your info-structure (make sure you play with S001).
When I am creating a bill and saving it and then giving issue output to and then header preview,
the system does not respond. Should I maintain condition records? Where and how to maintain?
For getting any output either by print, Fax, or any media you have to do output determination. output
determination is also carried by Condition techniques. The detail procedure for Output Determination is :
OutPut Determintaion:
Output is a form of media from your business to one of its business partners or it can be within the
organization. The output can be sent to any of the partners defined in the document. Outputs are usually
in the form of Order Confirmations, Freight List, Delivery Notes, Invoices & Shipping Notifications.
Determining form of output is output determination.
Types of Output:
Print Output, Fax, Telex, E-Mail & EDI (Electronic Data Interchange)
1) SPRO-> IMG-> Basic Functions-> Output Control-> Output Determination-> Output Determination
using Condition Technique- >Output Determination for Sales Documents (or you can use output
determination for billing documents depending on your requirement).
2) Create Condition Table: select the field Sales Doc Type from field catalog & Save
4) Assign condition table to access sequence. Select Accesses line item and Go To Fields. Fields will
display the fields we have selected in the condition table i.e. sales doc type.
AF00: Inquiry
AN00: Quotation
LD00: Delivery
RD00: Invoice
Select BA00 & Copy & Rename. Give the same 4-digit code as given to access sequence.
Languages of Output
Assign Output Types to Partner Functions: go to new entries & assign your output type to partner
functions.
Maintain Output Determination Procedure: V10000 (Standard Procedure). Go to new entries and create
your own 6-digit code with description. Select the procedure, go to Control Data. Here mention the output
type i.e. condition type and leave requirement and manual only columns as blank.
Create Condition Records: VV11. Select document type and click on Communication. Mention partner
function, medium, time. Output device: LP01, Spool request Name: SD_003, Suffix 2: order_confir &
flag on print immediately.
Once you press enter you will come across 2 key combinations:
Sales organisation/ Customer Number: fill SO, Customer No, Partner Function Abbreviation, Partner to
whom the output should be sent, time, medium, language.
It contains: Sales Orgnisation, Customer, Partner Function (The abbreviated form of the name that
identifies the Partner) (During output determination, the system determines the recipient of the output
from the master record for the specified partner function. In this field, you can explicitly specify a
recipient that will override the standard partner. There must also be a master record for the partner that is
specified explicitly.), Medium, Time & Language.}
Order Type: Document Type, Partner Function (abbreviation), Partner, Medium, Time & Language.
Path For Output Determination For Sales Documents: Logistics -> Sales/distribution -> Master data ->
Output -> Sales Document -> Create (t-code VV11)
Path for Output Determination for Delivery Documents : Logistics -> Sales/distribution -> Master data ->
Output -> shipping -> Create ( t-ode VV21)
Path for Output Determination for Billing Documents : Logistics -> Sales/distribution -> Master data ->
Output -> Billing Document -> Create ( t- code VV31)
Can we get the print if the order /delivery are blocked after static credit limit check?
IMG - Logistics Execution - Shipping - Deliveries - Define Reasons for Blocking in Shipping - Execute
Here select the delivery block that is blocking your order/delivery, and uncheck if the option Print is
checked.
01 Credit limit
02 Political reasons
03 Bottleneck material
04 Export papers missng
06 No printing
07 Quantity Change
08 Kanban Delivery
Indicates whether the system automatically blocks output for sales documents that are blocked for
delivery.
Example : In the case of sales orders that are blocked for delivery because of credit reasons, you may
want to block the printing of order confirmations.
Note:
The particular output that is affected by a delivery block is determined in output control.
PS: If the document is exceeds by the credit limit output type will not determine and as well as we should
not give the output type in sales order. We have to assign the routine 2 to sales order output types and 3
routine to delivery output types to restrict from output if the docuement exceeds by credit limit
Authorization Concept in SAP R/3 - How to define User Roles, Profiles and authorizations in SAP.
SAP R/3 uses a very complex mechanism to assign users access to system. SAP uses Authorization
Objects to assign authorizations to users. An authorization objects works as a template for an
authorization to be defined. One point to note here is that there are a maximum of 10 fields per
authorization object. For users to conduct an activity in SAP, their user profiles should satisfy the
authorization check for each field in the authorization defined on a specific authorization object.
To take an example, if a user wants to create a new company code, the authorization object is
F_SKA1_BUK - G/L Account: Authorization for company codes. User is given authorization to
authorization object
mentioned above with the relevant fields. Authorizations in SAP are classified as General authorizations,
Organizational authorizations or Functional authorizations. In our example above, authorization object
F_SKA1_BUK has been assigned to function for creating a general ledger master records. SAP can be
configured to check authorizartions at the company code level, chart of account level, individual master
record level so as to prevent user access. I will discuss more on SAP authorizations in my future posts.
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 Transactionfers 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. *-- Vishwajit
1. Automatic posting could be, posting of accounting documents to FICO once invoice is created which
can also be controlled manually. Automatiaclly detremine the freight while pricing in ship doc. and post
to the relevant account to fico. usually automatic posting is posting of documents to FICO based on
variuos account keys and account groups.
2. How many clients we will create in land scape (like in development server, quality server,
production server )
if we are creating more than one in each server what is exact use of that client.
3. How we will configure export sales in sd (respect to plants assign and sales process)?
4. How we can do invoice split depending on item category in which scenario we will use?
4. You first need to go for copying controls either from sales to billing (invoice) or delivery to billing or
billing to billing
use Transactionactions (vtaa,vtaf,vtla,vtfa,vtfl,vtff) all possibilities for copy controls. this basicly is flow
of doc to doc. (may it be sales to billing, del to bil, or bil to bil etc..)
-> this is where you see the Item category and you control whether split is possible or not with the
indicator"B". eg: representing split in invoice based on item category. The field here "data
VBRK/VBRP" (headre/item)whcih actually is used for splits or combining different deliveries. create a
splitting rule using VOFM (you need access key to get here). Here you define comparisions for the fields
at header table and item tables and the comparision fields say SPART"division". "purchase order
"BSTKD Instance: 5 sales orders combined into 2 deliveries and the split at the invoice would be 5
individual billing with respect to fields PO and DIv. of each sales order would let you create 5 billings.
You need to define the exact "field" in the comparisions both at header and item level that could lead to
invoice split. the key here is the field that is different
from header to item will cause split at the item level.
5. Can any one explain how we will configure milestone billing , periodic billing and which scenario
we will use?
5. Menu path:
IMG->sales &distr->Billing->billing plans->define billing plan types.
You set the start date and end dates if applicable to the type of billing you are using. What time to be
billed (end of month, start of month etc..)
Milestone is a billing plan type where a customer is billed for the amount distributed between the dates
until total value is reached eg: if the total billing amountis 1000 USD for a year. You will bill the
customer in different amounts say 200, 500, 300 at different intervals as per customer agreement.
On the other hand Periodic billling is billing the customer for the total amount(here 1000 USD) at regular
intervals peridically until the customer agreement is reached. eg: 1000/12 for a 1 year agreement and say
billed at the 1st day of every month.
6. Form routines for prcing and variuos other functions can be maintained form routines are something
todo with ABAP code.
Go to (VOFM) where all requrements whcih are represented by form routines can be maintained.
Requrements are available to be assigned where access sequenses are used (for determination procedures,
here pricing).
Once the tcode VOFM is accessed you will see requrements and go select "pricing" again you need
access key to create your own or copy a routine.
Say you want header price not to have effect the item pricing, you need to go to the program to change
abap code to meet the requirement. this specific requirement you created will be assigned in the pricing
proc. determination "requirements field"
usaully with a number beyond 600. Note: make sure you activate your routine for its effect to take place
1. What is the purpose of text determination, account determination, partner determination, output
determination,storagelocation determination
Answer1:
Text determination: For Transactionferring information from material or customer to order/delvery or
invoice (and anything inbetween)
Account determination: For Transactionferring 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
5. What do you do really in pricing determination, and what are the main deifferences between
pricing procedures?
Answer:
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
7. What are interfaces used generally an indian organisation which is in retail business and and
which is in banking business and oil business.
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.
Following is a real life question asked in the SAP SD Certification Examination. The question is relating
to one of the based concepts of SAP Sales and Distribution SD Module.
Q). What part of the company is responsible for the type of shipping, the neccesary shipping materials
and the means of Transactionport?
Options:
A) Sales Organization
Transactionportation Planning Point
C) Shipping Condition
D) Shipping Point
E) Warehouse
Answer: The correct answer is 'D' Shipping Point. Shipping points in SD represent an independent
organizational unit that is linked to a plant. Shipping points show the point of departure or receipt of
materials. In SAP, a plant may have many shipping points. However, delivery is created from one
shipping point only. The shipping point is the basic requirement for a delivery to happen in SAP SD. No
delivery can be made without a shipping point. The shipping point is determined by the system based on
the shipping conditions.
Each of the modules in SAP has its own internal organizational structure based on which
Transactionactions are processed. Normally the SAP SD Sales and Distribution modules have structure
of Sales area, Sales organization, distribution channel, Sales division, Sales office etc. Similarly, the
organizational structure in SAP FICO consists of client, company code, business area etc. In SAP there
are linkages between SAP SD and SAP FICO.
For example, by assigning sales organization and plants, once can create a link with company codes
which are in SAPFI. A plant in SAP is always linked to one company code. However the same plant can
be assigned to different sales organizations. Taking the same logic, there can be different sales
organizations assigned within the same company code. Transactionactions in SAP can also occur between
various company codes. For such Transactionactions to happen smoothly, it is important to configure
linkages within SAP SD and SAP FICO. Since master data in SAP is accessed by all modules, the way
the top level organizational hierarchy is structured can play a major role in ERP integration.
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 Transactionactions 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
Transactionaction 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.
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.
1. In SAP you will always get integration with other modules. SD will interact with FI, MM will interact
with SD :-
1a. Looking at MM and SD interaction first, take the scenario of a third party order process. This process
uses a purchase order (which is sent to your vendor). Also invoice verification is used further along the
process to check that the invoice you send to your customer is the same material and quantity as that
which the vendor sends to you (but obviously shipped
directly to your customer).
1b. Billing is an SD function. But SAP needs to know, when processing a customer's payment, to which
GL account the payment has to be processed. For instance payment of a UK based material would be
placed in a different GL account to that of a non-UK based material. Furthermore, a UK based customer
may have a different GL account to that of an Export customer. This is configured in Account
Determination.
2. ABAPers are there to essential do some bespoke development. Your integration, or interaction, with
them would be when specifying the tables, fields, input fields, a simple process explanation, data mapping
(if doing an interface from one system to another) etc. *-- Shahee
1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
2. MRP and availibility check related data is also taken from MM although you control this data in SD
also.
3. While you create inbound/outbound delivery with reference to a sales order,the shipping point
determination takes place with the help of the loading group, plant data, shipping conditions etc. This also
refers to Material Master.
4. The material which you are entering in a sales order must be extended to the sales area of your sales
order/customer otherwise you cannot Transactionact with this material.
1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the
bacgground. eg. In case of standard sales order, you create an outbound goods delivery to the customer.
Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some
G/L account in FI. Every such movement of good s hits some G/L account.
2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit
note etc) created in SD. Thus this is a link between SD and FI
3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM
(Sales Order –
•Availability Check - MM
•Credit Check - FI
•Costing - CO/ MM
•Tax Determination - FI
•Availability Check - MM
•Credit Check - FI
•Reduces stock - MM
Billing -
•Updates G/ L - FI/ CO
•Increases Inventory - MM
•Updates G/ L - FI
•Credit Memo - FI
•Adjustment to A/R - FI
•Reduces Revenue - FI
Quotation / QT
Purchase Order PO
Sales Order OR
Delivery LF
Billing MN
To create a sales order we need purchase order number and custmer number. Before that, to create a
purchase order we need to have material no, vendor no.
To create vendor tcode is
Table is kna1.
After creating sales order using this no we can create delivery note tcode is vl01.
Why Do We Assign Division to Sales Organisation
You can use tcode MASS and then select your Object type or there is few specific mass maint. Tcode is
available like for PO = MEMASSPO etc. but you can use MASS also for that you need to select the
object type for PO
Use object type BUS1001 and generate. Then you have to know the tables where the field you want to
modify is. Pick the fields in their folder and generate again. Then in selection pick the materials or use
other selection criteria. Generate again.
In the upper side of the screen insert the data and click the button 'carry out a mass change'.
MASS maintenance means - suppose you want to change prticaulr field of material for all the mateirl of
certian plant or all the plant you can do using mass like wise for certian PO value if you want to cahnge
you can use mass.
There a lot of Transactionactions for specific mass changes. MASS is also one of the Transactionactions
among them.
So now my question is why I can't see serial number in material document? How can able to see
that? what is the configuration required?
Whatever settings you have maintained is correct. I shall share as to what happens in our business
process.
After Transactionfer order there is a Transactionaction used ZL02 where in the delivery number is entered
and on executing, a screen pops up asking for the serial number. Here we enter the serial number
maintained for the material and is got from MMBE. And the serial number is captured for the material.
Pls check for the serial numbers in MMBE and I suppose a program needs to be created by an ABAPer
for the serial number to be fetched and a Transactionaction to be
created and associated with the program.
In outbound delivery, post goods issue failed because of serial number, but this serial number was
not assigned to any other material.
Check the serial number and material with IQ03. Serial number is material specific.
When I looked at the IQ03, for the serial no "#162559019S.", I realized that the status is still
remain as EDEL and ESTO.
Supposingly, the status should only has ESTO. Is there a way to remove the status "EDEL"?
EDEL status shows that it is assigned to a delivery. Change it by going into IQ02 --> Edit --> Sp.Serial
number Functions --> Manual Transactionaction and make it 'to stock'
If the serial number has status EDEL ESTO that means the serial number is assigned to the Delivery,
reversal PGI has not been completely performed.
Please check your SD document flow if all the documents have been reversed.
In which table name address of the sales office (SD ) is stored. Also tell in which table, description
of the sales office is stored.
in table ADRC you will find name, description, address and all other data.
We have a scenario where we need to Assign single sales office to multiple sales organizations in
CRM. When I am trying to assign sales office to more than one sales organization 1st assignment
between Sales office and Sales Org is getting deleted, and only the 2nd assignment is available.
At sales office level in Function tab, it is showing only the assigned sales Organization (only one
sales org), how to assign one more sales org to this sales office here.
The assignments are on the lower node. Which means you will go to Sales office, go to function TAB and
assign multiple sales organizations there.
In the change form click New entry and assign the new sales organization and distribution channela and
division combination.
3. As you know we have 3 Org Units as far as Sales is concerned i.e. Sales Org, Sales Office, Sales
Group.
4. In R/3 there is a standard way to maintain multiple assignments among these org units.
Ex: Sales Group 'X' works (assigned) for 2 Sales Offices 'North' and 'South' simultaneously.
5. But in CRM this assignment is not as common as in R/3 and is not supported thru SBIV.
6. If you would like to have these multiple assignments made in R/3 available in CRM as well you may
want to go thru EBIV.
8. In EBIV divisions and distribution channels can only be assigned to sales units (sales organizations,
sales offices, and sales groups). If they are assigned to any other neutral Org Units (Org Units without any
Org Attributes), those assignments would be deleted once you shift from SBIV to EBIV.