Sales and Distiribution Questionaire 1 (1) Doc

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

o Business area. A unit in an enterprise, grouping product and market combinations as
homogeneously as possible for the purpose of developing unified business policy.
o Financial Accounting (FI). A business area is an organizational unit within financial
accounting which represents a separate area of operations or responsibilities within an
organization. Financial accounting transactions can be allocated to a specific business area.
Briefly explain the relationship between sales organizations and company codes.
Many to One.
What is the central organizational element in purchasing?
Purchasing Organization.
Explain the relationship between sales organizations and plants.
Many to Many.
Explain the relationship between sales organizations, plants and company codes.
Many to Many to One.
Can one business area be assigned to several company codes? Which (sub) module of SAP
could make business areas obsolete?
Yes in CO .
What is a credit control area? What relationship exists between credit control areas and
company codes?
Credit control area. Organizational unit in an organization that specifies and checks credit
limits for customers. A credit control area can include one or more company codes. It is not
possible to assign a company code to more than one credit control areas.
Which organizational element is central in shipping? Give a definition of it.
Shipping Point: Organizational unit at a fixed location that carries out shipping activities. A
shipping point could, for example, be a company's mail department or a plant's rail depot. Each
delivery is processed by only one shipping point.
Give a definition of plant (in SAP).
Organizational unit within Logistics, serving to subdivide an enterprise according to production,

procurement, maintenance, and materials planning aspects.
A plant is a place where either materials are produced or goods and services provided.
Classification: Business object
Structure: A plant can assume a variety of roles:
As a maintenance plant, it includes the maintenance objects that are spatially located within this
plant. The maintenance tasks that are to be performed are specified within a maintenance
planning plant.
As a retail or wholesale site, it makes merchandise available for distribution and sale.
As a rule, the plant is the organizational unit for material valuation.
The preferred shipping point for a plant is defined as the default shipping point, which depends
on the shipping condition and the loading condition.
For the placement of materials in storage (stock put-away), a storage location is assigned to a
plant. The storage location depends on the storage condition and the stock placement situation.
The business area that is responsible for a valuation area is determined as a function of the
division. As a rule, a valuation area corresponds to a plant.
Can you assign two different sales organization to the same company code?
Yes.
To what do you assign distribution channels and divisions?

Sales Organizations.
What are the highest organizational units in SD, MM.PP,FI,CO?
SD: Sales Organizations.

M: Plant
PP: Plant
FI: Company Code
CO: Controlling Area
Can you further subdivide a plant? If yes into what?
A plant can be subdivided into storage locations, allowing stocks of materials to be broken
down according to predefined criteria (e.g., location and materials planning aspects).
A plant can be subdivided into locations and operational areas. Subdivision into locations takes
geographical criteria into account, whereas subdivision into operational areas reflects
responsibilities for production.
Can a sales organization sell from a plant belonging to a different company code?
Yes.
How many shipping points can you assign to a plant?

Many.
How many shipping points can you assign to a sales organization?

None.
If you have a warehouse management system active, to what would you assign the
warehouse number?
Plant & Storage Location.
Sales and Distribution - 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 transfers the reported requirements and creates orders or
purchase requisitions from them etc.
For controlling transfer of requirements, you have to carry out the following steps:
1. Each requirement type has to be allocated to one requirement class only.

2. The transfer 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 transfer of requirements to be carried out at document item
level.
OVZG - Requirement class
It specifies the following points:
- whether an availability check and a transfer of requirements is carried out for a transaction (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 transaction SM30 for V_* configuration)

OVZH - Requirements type
V_TVEPZ_V - Assignment of requirement type to Transaction
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.
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 different 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
To temporary block the creation of Sales Order for a certain materials.
Set the material status parameters in transaction SM30, Table Views V_TVMS.
Click Maintain and double click into the Materials Status code.
You can set three types of response for each Sales and Distribution process :-
1. no dialog
2. warning when entering the document
3. error message (that is, the sales and distribution document cannot be entered on
the basis of the material status)
Define Tax Determination Rules
You specify the valid tax types in transaction OVK1. More than one tax type can be defined for
a country by defining the sequence.
The SAP System determines the taxes automatically within pricing.

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
Now, you define the Tax Determination in VK12.
VK12 - Domestic Taxes/Export Taxes
Condition Type MWST

Customer Taxes Material Taxes Rate Taxes
0 0 0%
0 1 0%
1 0 0%
1 1 9%
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.
Link Between SAP SD, MM & FI

The link between SD and MM :-
1. When you create sales order in SD, all the details of the items are copied from Material master
of MM.
2. MRP and availability 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 transact with this material.
There are many such links between SD and MM.
Now the link between SD and FI :-
1. Whenever you create a delivery with reference to a sales order, goods movement takes
place in the background. 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
How to do configuration for Credit Management function?

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 OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
3. Transaction XD02 or VD02

Check which credit control area is assigned to the payer.
Payer:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in
Transaction
OB45, or the credit control area must be entered under the relevant company code in
table
T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be
assigned to a credit account by using Transaction FD32.
10. Transaction OVA8

Here, the individual credit checks for key fields
o credit control area
o risk category
o 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
status must be set (field "Status/block").
11. Transaction FD32

Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the
limit check (static or dynamic credit limit check).
13. Transaction OVA7
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 VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
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 update and credit check. You can find the used pricing procedure of the order
under "Item -> Condition -> Analysis". Pricing procedure: Line with subtotal = 'A':
15. Transaction OB45

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.
Update:
16. Transaction OMO1

Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update.
All other settings will lead to errors.
MRP block for Credit limit attained Customers
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.
You should try and use one of the standard requirements.

See in transaction "VOFM".
Under Requirements / Subsequent Functions / Reqs. Availability.
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:
DATA: W_ZSDCRD TYPE ZSD_CREDITBLCK.
DATA: W_CMGST LIKE VBUK-CMGST.
SELECT SINGLE * INTO W_ZSDCRD

FROM ZSD_CREDITBLCK
WHERE KKBER = VBAK-KKBER
AND CTLPC = VBAK-CTLPC.
IF SY-SUBRC = 0 AND VBUK-CMGST CA 'B'.
IMPORT VBUK-CMGST TO W_CMGST FROM MEMORY ID 'CREDIT'.
IF W_CMGST = SPACE.
MESSAGE I706(Z1).
EXPORT VBUK-CMGST TO MEMORY ID 'CREDIT'.
ENDIF.
*} REPLACE
*{ INSERT DEVK966908 1
*} INSERT
* Read the subsequent function information for the message
PERFORM FOFUN_TEXT_READ USING GL_FOFUN
CHANGING FOFUN_TEXT.
MESSAGE ID 'V1' TYPE 'E' NUMBER '849'
WITH FOFUN_TEXT
RAISING ERROR.
*{ INSERT DEVK966908 2
*} INSERT
ENDIF.
ENDFORM.
Credit Mgmt Dynamic checking

How I can automatically re-execute a dynamic credit check a few days prior to shipment for
future dated sales orders.
A. Program RVKRED08? Or manually execute function module

SD_ORDER_CREDIT_RECHECK.
We check credit at the time of the delivery (at delivery creation and before picking) and use the
blocked sales doc process/list to release them. This can be set up in customizing under risk
management-> credit management.
SAP SD Credit Limit Problems

Have set credit limits for my customers in transaction FD32. The problem is: so long as the
Receivables figure is lower than the Credit limit figure, the system allows the creation of sales
orders and subsequently, deliveries i.e. Credit exposure goes over 100%. Eventually, when we
invoice these deliveries, we go over the credit limit. Is there a way we can stop this from
happening ? Is there a way we can get the system to look at the Credit exposure figure instead of
the Credit limit figure ? If so, can this setting be done at the Credit Control Area level ?
A. Credit Exposure = (receivables + open deliveries/ sales orders) - special liabilities.
Activate Simple credit Checking or Automatic Checking? Check note number 18613 for
detailed instructions for activating credit management, mostly u have not set the subtotal to Ä
The system should check credit limit against the credit exposure. The credit exposure can be
defined to be what you want. Using static credit check you can include orders, deliveries, bill
docs. In dynamic credit check you can look at the horizon to be included in credit exposure. You
may also want to make sure you are checking credit at time of delivery create. This can be done
with a combo of credit control/risk cat/ status in config. You also may need to make sure you are
running the jobs provided by sap to recheck orders after saved. Do not know job names off
hand.
From the scenario given, I doubt what sort of credit check has been assigned for the
order type. in transaction OVAK check whether u have put D and credit group 1 for the
respective order also in OVA8 check where u have ticked? static or dynamic? If ticked at static
then both --> order and deliveries should be selected.
Sales value field in not getting updated after creating the billing
Are on 4.6b. going for credit management but facing one problem. in fd32- customer credit
management change - the sales value field in not getting updated after creating the billing.
eg. when creating the order - the order value get updated in the sales value in fd32. after
creating the delivery - that value remains same in the field of sales value. but when
going for billing (delivery related), the bill value is appearing in 'receivables' but the amount
in 'sales value' is not getting reduced. because of this the credit exposure is increasing
continuously. Update group for corresponding credit ctrl area is 12. also the item is mark for
credit update.
A. Need to check couple of settings like:
1. Your customer should be assigned the credit control area.
2. In your Item Category Credit should be active.
Customer is assign to concern CCA and item category is mark for credit active
Check the credit update group in the transaction OB45. The credit update group controls
when the values of open sales orders, deliveries and billing documents are updated. It
should be '000012'. Further also refer to the OSS note 18613.
How to do rebate processing (Scenario)

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?
A.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 process. 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.
This is broadly the outline of the rebate process.
Note : I recommend you to study the theory part of why rebate and why not a discount.
This will help you understand better.
May be I can help you with rebate process.(IN -IMG)

1. define a rebate agreement type
2. define a condition type group
3. define a condition type and place this condition
Type in the pricing procedure.(REQUIREMENT=24)

ALSO IN THE PROCEDURE- ACCRUAL KEY = ERU
YOU ALSO HAVE TO DO THE ACCOUNT DETERMINATION FOR REBATES.
Once you have defined all the 3 and assignment starts.

Assign the agreement type to the condition type group
Assign the cond type group to the condition type.
Condition technique is also used in rebates.
REBATE ACTIVATION- IN CUSTOMER MASTER, SALES ORGANISATION AND FOR

THE BILLING DOCUMENT.
After having done this please proceed to maintain the condition record for the rebates
(transaction code-vbo1)
Note: if you maintain the requirement column with the requirement as 24 - the rebate will be
affected in the billing document and if you don’t give the requirement as 24 your rebate will be
affected in the sales order.
The rebate process is completed when you have created a credit memo to the customer.
The document type for the partial settlement is R3.
Please make sure you open two screens SO THAT YOU CAN COMPARE THE NEW
ENTRIES WHAT EVER YOU'RE DEFINING WITH THAT OF THE STANDARDS or first
you try with the standard condition type boo1, boo2 boo3 boo4.
AFTER YOU HAVE FINISHED A COMPLETE SALES CYCLE OF CREATION ORDER ,

DELIVERY AND BILLING.
GO TO THE CONDITION RECORD IN CHANGE MODE (VB02) AND SETTLE THE

ACCOUNT PARTIALLY.
In a simple way,
1. First you need to create a Rebate agreement.
2. Create condition record for rebate giving the rebate rate and accrual rate.
3. when the rebate relevant billing doc is generated, the rebate and accruals are determined and
posted in a separate GL account as a noted item - amount to be settled. Also it gets copied in the
rebate agreement.
4. create settlement run using credit memo request and then credit memo to settle this amount
with the customer.
This is what the link says.
Name two ways to start a transaction.

- Dynamic Menu
- Command Field
Why do you create user-specific parameters?

They supply defaults to R/3 fields. If a field is indicated, the system automatically fills in default
value. Depending on the field definition, the entry can also be replaced with a value entered by
the user. (Concept of PARAMETER ID)
Name the three different kinds of messages in the R/3 system. What is the difference
between them?
A message can have five different types. These message types have the following effects during
list processing:
A (=Abend):
The system displays a message of this message type in a dialog window. After the user confirms
the message using ENTER, the system terminates the entire transaction (for example SE38).
E (=Error) or W (=Warning):
The system displays a message of this message type in the status line. After the user chooses
ENTER, the system acts as follows: -While creating the basic list, the system terminates the
report.
While creating a secondary list, the system terminates the corresponding processing block and
keeps displaying the previous list level.
I (=Information):
The system displays a message of this message type in a dialog window. After the user chooses
ENTER , the system resumes processing at the current program position.
S (=Success):
The system displays a message of this message type on the output screen in the status line of the
currently created list.
What is a data dictionary or repository?

Central catalog that contains the descriptions of an organization's data and provides information
about the relationships between the data and its use in programs and screens.
The data descriptions in a Data Dictionary is also called metadata, i.e., data that describes other
data. The ABAP/4 Dictionary stores system-wide data definitions. When you create a new data
definition, the Dictionary tool does all the processing necessary to create the definition. You can
use the Dictionary tool to look up the "definition" of objects in your R/3 System.
What is a match code?
A.Comparison key. A match code allows you to locate the key of a particular database record
(e.g. account number) by entering any field value contained in the record. The system then
displays a list of records matching the specifications.
If you want an end user to see a specific menu after logging on the R/3 system, how could
you do that?
User maintenance transactions allow the system administrator to create and maintain user master
records. This includes the generation and assignment of authorizations and authorization
profiles.
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 mentioned that nobody change the system configuration, it is very unlikely that the
system will misbehaved 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 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.
Auto proposed all the dates when creating Sales Order
How can I make the system auto create all the Sales Order date during creation?
Each Sales Order can have different date proposal settings.
Follows this step to set the default Sales Order Type proposal date:
- Go to VOV8, double click on sales order type.
- 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.
To change the Materials field Delivery Plant:

Go to 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
You need to receipt the rejected goods through SD Module (VA01 - Sales Order type RE).
The steps are as follows :
1. Create a return request. (Using Sales Order in SD)

2. Create outbound delivery according to return request.
3. If the setting is correct in the outbound delivery screen SAP will automatically switch post
goods issue button into post goods receipt. The setting is in sales order item category and
delivery type.
4. In the standard system the movement type used is 651.
5. After post goods issues receipt is done using outbound delivery, the quantity is placed in
blocked stock without value updating.
6. You will then decide if the return quantity are indeed bad stock or not.
7. Transfer Posting from block stock to unrestricted stock (mvt type 453), this will have
accounting effect (Debit Inventory, Credit COGS)
8. Goods Issue to scrap account how to create new titles which can be used in creating the
"address" view on the Vendor master.{T-Code: XK01}
In config go to Basis Components --> basis services --> Address Management --> Maintain title
texts
How to Know that Sales BOM is working or not? (Scenario)
I have set up a sales BOM. How do I know or test that is is working or not?
Once you enter a material (for which 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.
In my experience BOM’ s work if all maintenance has been done properly.
A number of things to check is:
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 maintained 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 BOM’s are all single-level. You could set it to B if BOM are configured
multi-level.
Release strategy for Sales order
Is it possible to have release strategy for sales order?
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 authorization profiles; what I
mean to say is that the sale order to be kept incomplete by the person who does not have the
required authorization & the person with proper authorization 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.
Consignment Sales Process in SAP

The consignment process in SAP standard consist of four small processes:
Consignment fill up (send materials to customer consignment). Here you have a consignment
fill up order and a consignment fill-up delivery.
Consignment issue (issue materials from customer consignment to the customer). 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).
Consignment pickup (pickup consignment stock and move it to plant stock).

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.
How to perform a consignment order?
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.
1. Consignment fill up:

Sales document type is KB
Item category KBN
schedule line category E1
In this step, you are not invoicing the customer. document flow is sales order ---- delivery item
category. It will not be relevant 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
schedule line category: C0 or C1
Here you are invoicing the customer(because he used the goods). you are assigning the delivery
document 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 type, 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.
Sales document type: KR

Item category: KRN
Schedule line category: D0
You will assign delivery document and billing to sales document. you will create return order,
return delivery, return billing.
Your setting item category relevant for billing, returns, pricing, special stock.
Your setting schedule line item category: 634 movement type, NO availability NO TOR.
4. Consignment Pick up:

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.
Assign return delivery to sales document type.
Sales document: KA
Item category: KAN
schedule line category: F0 & F1
Your setting item category relevant for returns. any schedule line category relevant for 632
movement type, MRP, availability check, delivery.
Now you check your plant stock. Stock will increase.
Issue free goods to selected Customers
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 inconvenienced. How do I set it up?
1.Run trans. VBN2 to first create master record for free goods as follows:
Enter following information in selection screen:
- Free goods type: NA00
- Sales org, distribution channel, customer # and execute.
Now in next screen create the record as follows:

- First select the exclusive button and verify that you are in exclusive view.
(that is if you want exclusive)
- Material#, Min qty - Say 34 cartons. (check in what units you want to manage)
From: 34 cartons
unit of measure:
Free goods: 12 Pcs
Unit of measure: Pcs
Calculation type: 1 or try the other options
Deliver control: Blank or any of the other options suitable to you.
Now save and exit.

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 qtys and see if the free goods qty are
scaling up.
If not adjust the calculation parameters in the master record screen

It should be transaction VBN1. Sorry for the error.
VBN2 is to change the record. VBN1 creates it.
If you want to give free goods to some of the customers than

1. create a customer group say 99 for FREE GOODS
In Free Goods Menu:

2. add a field catalog for CUSTOMER GROUP
3. create a condition table (free goods) say 555 only for customer group
4. create a sequence say FREE with condition table 555
5. create a condition type say FREE with
6. maintain pricing procedure say ZFREE with condition type FREE
Now assign:
7. Active Free goods Determination or Assign with your sales organization this procedure
ZFREE
8. Create free goods determination with transaction code /nvbn1 for FREE with Key Customer
Group 99 for exclusive
Give customer Group say 99 and from 34 to 34 free 12
Suppressing Fields in Sale Order

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)
To make a filed entry enabled or grey (non-entry allowed):

User exits in the program MV45AFZZ-USEREXIT_FIELD_MODIFICATION
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 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed
information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made,
you must make them in this user exit. This FORM routine is called up by the module
FELDAUSWAHL.
Actually suppressing fielding sales orders user-wise is quite easy. We are doing it in our
company. For this we use user-exit FORM USEREXIT_FIELD_MODIFICATION in
MV45AFZZ.
Below is the sample code

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 accessed via this user exit.
Settlement Down payment with Installment payment Term (Scenario)
Scenario :- Problem with Down payment settlement using installment payment term.
1. When we create Sales order, (sales item value = 100) use payment term :
0009 (Installment Payment term, 30%, 40%, 30%). In the Billing Plan, I specify 2 records, 1st
record is Down payment request 30% of Order value, billing type is FAZ . the 2nd record is
Final invoice 100%, billing type is F2.
2. Create Billing type Down payment request , it will document as Noted item in the accounting
document.
3. Receive Down-payment from customer via FI screen , at this stage the accounting document is
created as following
Dr. Cash/Bank 30
Cr. Advance from customer 30
4. When I create Billing document for the sales item, the down payment value will be proposed
for settlement at Billing Creation, I then accept the default value of down payment clearing.
The accounting document is as below
Dr. AR 30 (*split AR by installment payment term)
AR 40
AR 30
Cr. Sales 100
Dr. Advance from customer 30
Cr. AR 9 (DP. 30% * 30)
Cr AR 12 (DP. 30% * 40)
Cr AR 9 (DP. 30% * 30)
It seems SAP settlement Down payment by Installment Payment term. Was wondering that is
there are alternative or an option to setup the Down payment settlement independent of
Installment term. I meant, I don't want to have the last 3 Credit item as above, I want only 1 line
item of credit, the accounting should be
Dr. AR 30 (*split AR by installment payment term)

AR 40
AR 30
Cr. Sales 100
Cr. AR 30 (Not separate by Installment payment term)
Solutions : Suggestions on how I could proceed?
Your problem with Down payment settlement is common. Many users object to the down
payment or security lodgment mechanism. In our case we often park and apply the advance
manually to final invoice.
However, following the above case we sometimes use this with our PS orders:
1. Create Sales order, (sales item value = 100) with billing plan with three steps 30% down
payment,30% std billing on order completion and 70% on delivery. A little different to your
original Billing Plan, but 1st record is Down-payment request 30% of Order value, billing type
is FAZ . the 2nd & 3rd records are std F2 invoices 30% ,70%.
2. Create Billing type Down payment request , it will document as Noted item in the accounting
document.
3. Receive Down-payment from customer via FI screen , at this stage the accounting document is
created as following :-
Dr. Cash/Bank 30
Cr. Security deposit payment 30 ( In many countries this may be subject to TAX laws)
4. Create the First Billing documents , the down payment value will be proposed for settlement at
Billing Creation, then
accept the default value of down payment clearing as these equal each other. The accounting
document is as below
Dr. AR 30
Cr. Sales 30
Cr. AR 30
5. Create the Second Billing document ( down payment value has expired and will not be
proposed) The accounting
document is as below is then standard for the last installment.
Dr. AR 60
Cr. Sales 60
This alternative provides a cleaner option with the Down payment.
SAP FAQ (SD)
Master Data
Q: Some materials have been blocked for procurement and production. Even though deletion
flag is set for a material/plant level, the order can be still entered ( with a warning message). Is
there a way to block such transactions for a material flagged for deletion?
A: Sales Status field in the sales organization view of the material master may be used to block
any transaction for the material.
Q: We can define our own exchange rate types and use them instead of the defaulted types, 'M',
'B' and 'G'. How can we overwrite default types in SD?
A: Exchange rate gets copied from the customer master record. Exchange rate types are to be
maintained for the customer in the sales screen of the customer master record.
Shipping
Q: The PL00 condition is fine in delivery. But when we try to print to either the screen or
printer, an error V1032 occurs. Why?
A: In order to use the Packing list PL00 (packing slip in delivery) you must do 'Packing' in the
delivery note (edit->packing)
Q: we have to enter a shipping point while creating a delivery. Is it possible to create delivery
without shipping points?
A: When you are releasing a sales order, choose Sales document -> Subsequent functions->
Create delivery, then the shipping point will be brought in from the sales order. In all other
scenarios you have to key in the shipping point. The above described scenario will only work if
all items on the sales order are to be shipped from the same shipping point.
Billing
Q: SAP allows a non-inventory item and an inventory item to be in the same document till
delivery but splits at the time of creation of billing document. Can we combine a non-inventory
item with an inventory item in one invoice? Can we treat it as a value item in sales order so that
it is priced and then make it as a text item in delivery documents so that it appears in the same
invoice and does not split?
A1: Make the non-stock material deliverable, but not pickable. Both items will carry into the
delivery, and therefore appear on the same invoice.
A2: Change the copy rule for orders->invoices and deliveries->invoices to specify that invoice
combination is permitted. However note that for system to create combined invoices, PO
number, payment terms, sales organization, and distribution channel must be identical. Else
undesirable combinations may be created by the system.
Pricing Conditions
Q: It is impossible to price at the material level (matnr) , when a material has a pricing reference
(mvke-pmatn) set up against it in the master data. Pricing always look for the pref, even if a price
is set up against the material and not the pref. How can we price by material and pref?
A: The field used to look up at the price is defined in Access sequence. You may find a step with
PMATN as material number. If you insert a step with MATNR then the system will first look for
the material, if not found (use the exclusion tick box) it will look for the pref.
Customizing
Q: We generated a new condition table. Assigned the condition to access sequence. Created a
condition record. Access sequence is assigned to the output type. But when we create a billing
document, output screen comes up blank for the output type. When we look up Determination
Analysis, we get an error "Note 524 Access not made (Initialized Field)". What else is required
to be done?
A: Assign output determination procedure to the header of the document and the output type.
Q: How can we set up to have the VAT# be accepted in the Ship-To Master File Data Control
screen?
A: IMG->Fin. Acct.->AR and AP ->Customer acct->Master Record -> Prepare to Create
Customer-> Define Acct. Group.
Q: We want to explode Bill of Material automatically at time of Order entry and explode an
Equipment BOM in the sales order. What are the setting required?
A: Use an item category that is configured for bills of material for having a sales BOM to
explode automatically.
Standard SAP item categories are :
TAQ - Pricing and inventory control take place at the BOM header level
TAP - Pricing and inventory control take place at the BOM item level
These can be automatically derived using the item category groups ERLA and LUMF,
respectively.
Q: How can we make the Customer Group 1 (or 2, 3, 4, 5) a mandatory field?
A: Logistic General-> Logistics Basic Data: Business Partners -> Customers -> Control ->
Define account groups and field selection for customer
Choose Customer Acct. GR. (double-click). -> Field Status: Sales data (double click) -> sales
(double click) .Check the radio button against Customer Gr as REQ. ENTRY. Save the settings
to make customer GR entry mandatory .
Q: Is there an user exit to copy the data into planning table?

A: Use user exit MCP20001 and include ZXSOPU01.
Others
Q: We get a report screen: "Goods issue: Problem Log" during the delivery process when
activating Post Goods Issue button. We want to include our own error message to this list if the
selected batch is not on a customer defined table. What is the best way?
A: Try User exit - USEREXIT_SAVE_DOCUMENT_PREPARE
Difference between Condition Type
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.
Please note the following points :
1) The condition type must have condition category 'Q' (costing).
2) The condition type must agree with the condition type defined for unit costing in the pricing
procedure.
Q. 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?
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.
Accumulate the amount of condition types in accounting document
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-
(all condition types are shown separately in pricing view)
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.
Determine sales price with shipping point (Scenario)
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.
You'll have to do some settings to reach your goal, it is possible.
Step 1
Append structure KOMP. Do this by changing through SE11 the table KOMPAZ.
This is the include 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.
Basic Process of how Packing Works

Let's say you want to pack a material shirt_jai in test_pack.
Using MM01, create material type=packaging test_pack
[SPRO]
IMG-Logistics Execution-Shipping-Packing-
Define Packaging Material Types
Let's say JPAC. The settings that I chose:
Plant determ. - Plant is entered manually in handling unit
Pack. matl. cat. - Packaging materials
Generate Dlv. Items - blank
Number assignment - Number range interval 'HU_VEKP'
Define material group for packaging material
Let's say JGRP
Define allowed packaging materials
JGRP - JPAC
MM02: Check settings for the materials

First, test_pack
Sales:General/Plant -> Matl. Grp. Pack. Matls: JGRP (Note)

Sales:General/Plant -> Packaging Mat. Type: JPAC (Note)
Basic Data 1 -> Material: JMAT
Then, shirt_jai
Sales:General/Plant -> Matl. Grp. Pack. Matls: JGRP

Sales:General/Plant -> Packaging Mat. Type: -
Basic Data 1 -> Material: JMAT
VL01N Outbound Delivery -> Packing

Enter the materials at top and at bottom
(Select shirt_jai and
Edit - Pack)
This is how the basic process of packing works.
Content Author : Jairam

Author Website : http://www.geocities.com/jairam143/
The "Packing Process" with an Example

Example:
You created a 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
B)these 3 cardboard boxes are put into pallet (PK-095).
Solution:
A)Packing 40 pieces each of material (40 x 3 = 120 pieces)
1)Goto [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.
3)In the upper section, enter the "packing material" (PK-100)
4)In the lower section, change the "partial quantity" to 40 of material R-1160.
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.
B)Packing all 3 cartons in one big carton(PK-095)
1) from above screen, click "pack HUs" (pack shipping unit)

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.
4)selecting both lines, click "pack" icon.
5)Now all the 3 cartons(PK-100 with 40 pieces each of material) are packed in one big carton
(PK-095).
Check: "General overview" icon.
Then "save" the delivery.
Content Author: Smiley

Difference between Condition Type
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.
Please note the following points :
1) The condition type must have condition category 'Q' (costing).
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.
Arvind Rana
Accumulate the amount of condition types in accounting

document
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-
(all condition types are shown separately in pricing view)
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.
Hiding Price Condition Types on a Sales Document

Up to now you, you still cannot exclude certain condition types and subtotal lines from being
processed or displayed in the condition screen by restricting the authorizations.
You have to implement SAP Note No. 105621 - Authorization check for the condition screen
Creating New Pricing Procedure

What is the transaction 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)
Hope this helps.
Sabir
Reg pricing procedure.
1. Use transaction code v/07 to create a 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.,
(Do assign relevant access sequence)
3. Use transaction code v/08 to define pricing procedure.

4. Assign this to your relevant sales area+ dpp+cupp.
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.
Hope this helps,
Chakravarthy Narasimhn
Re-pricing in a Quotation
How can I, or am I able to find anything on a way of RE-Pricing be done 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 (transaction 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.
Quantity Based Discounts in Bulk Quantities Sales

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.
If the customer orders 10 pieces of part ABC, the price is $50.
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.
That should do it.
Determine sales price with shipping point

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.
You'll have to do some settings to reach your goal, it is possible.
Step 1
Append structure KOMP. Do this by changing through SE11 the table KOMPAZ.
This is the include 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.
Pricing date based on delivery date

Used transaction VOV8.
This configuration is by order type.
There is a field called proposal for pricing date.
There you can select pricing date as requested delivery date.
A - Proposed pricing date based on the requested dlv.date (Header)
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.
( T 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.
SAP Tips by: Sreenivas
Report to Check the Entered Pricing Condition Price

Which is the best transaction 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.
Other Pricing Reports you can tried are these:
---------------------------------------------------------------------------
|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.
Use VA05, select your Orders and on the result screen :-
click Edit- > Mass Change -> New Pricing (menu).
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)
Make Material Master Price of a material as sales price

automatically
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.
This is how it goes :-
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 transaction VOFM) is:
RV64A901
FORM FRM_KONDI_WERT_600.
XKWERT = KOMP-WAVWR.
ENDFORM.
The pricing procedure than looks like that:
Step 1 VPRS statistical, subtotal B, reqt 4

Step 2 PR00 Altcty 600
Customer discounts on effort only

-----Original Message-----
Subject: Customer discounts on effort only
Hi All,
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.
Kindly help,
-----Reply Message-----
Subject: RE: Customer discounts on effort only
Hi,
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.
Hope it helps.
Thanks
Hi
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
Regards
I am in SAP R/3 rel.30F.

We have 2 options to meet your requirement.
1. Using scale in condition type ( tcode V/06 ), choose scale basis
G.Scale based on a formula ( be: your based amount is invoice ). Define
scale formula. You need ABAPER to define it.
2. Using routine in Alt.calc.type ( tcode V/08 , Maintain Pricing
Procedure ). Here, you also need ABAPER to create routine.
hope this help

Steps to Create Commission for Agent
For creating commission agent, you have to follow below steps.
1) Establish Partner Functions for the Commissionee(s)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE
PARTNER FUNCTIONS
Transaction Code: VOPA
2) Assign the Partner Functions to Partner Procedures

PARTNER FUNCTIONS
3) Create a Partner Procedure for the Commissionees

PARTNER FUNCTIONS
4) Create New Customer Account Group(s) for Commission Agents

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; LOGISTICS
GENERAL ->; LOGISTICS BASIC DATA: BUSINESS PARTNERS ->; CUSTOMERS ->;
CONTROL ->; DEFINE ACCOUNT GROUPS AND FIELD SELECTION FOR CUSTOMER
Transaction Code: OVT0
5) Assign the Partner Functions to the Customer Account Group(s)

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)
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
Transaction Code: SE11
9) Edit MV45AFZZ – userexit_pricing_prepare_tkomk (Client Independent)

Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR
10) Edit RV60AFZZ - userexit_pricing_prepare_tkomk (Client Independent)

11) Edit MV45AFZB - userexit_new_pricing_vbkd changing new_pricing (Client Independent)

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)
DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->;
DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES
Transaction Code: OV24
14) Create Condition Tables (Client Independent)

Transaction Code: V/03
15) Create an access sequence containing the new tables (Client Independent)
16) Create a new condition type

DEFINE CONDITION TYPES ->; MAINTAIN CONDITION TYPES
17) Add the Condition Type to the Pricing Procedure

DEFINE AND ASSIGN PRICING PROCEDURES ->; MAINTAIN PRICING PROCEDURES
11) Create Commsission Report ZZCOMMISSION (Client Independent)

Billing cannot be Release to Accounting
This SAP message will appear if the system is unable to find the G/L codes match from the
configuration in transaction VKOA
No account is specified in item 0000001001

Message no. F5 670
Diagnosis
No account was specified for account type "S" in item "0000001001" of the FI/CO document.
System Response
The Financial Accounting program cannot process the document.
Procedure
A system error has probably occurred in the application you called up. Check the data transferred
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
tabstrips - 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 VKOA have been done correctly.
Check whether the sales order (VA03 - Goto - Header - Financial Accounting - Field name:
AcctAssgGr) have been filled in automatically.
Check whether the billing document (VF03 - Goto - Header - Header - Field name: AcctAssgGr)
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 customer, therefore, the
system will not be able to determine the Account Assignment Group manually.
Default Start Variant for VF04

There are two types of variant in VF04.
One is the selection variant before clicking the Display Billing List Button.
You can set the start variant via SE93 using the Change mode.
The second variant is the Billing Layout display variant.

This is after clicking the Display Billing List Button.
After creating your layout display variant, you can set it by clicking :-
Settings ->
Display Variant
-> Administration
Select the layout display variant you want and click :-
Edit ->
Define default settings
Condition Exclusion which will be determined in the billing

document
The system can exclude conditions so that they are not taken into account during pricing.
For example:
Material 4711 costs 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.
Assign the procedure to the pricing schema, and maintain copy control so that pricing is not
copied from Sales Order.
To achieve this, copy the standard pricing to a ZXXXX Pricing.
Define new document pricing procedure in SM30 - V_TVKV for billing.
Assign new document pricing procedures to billing types in SM30 - V_TVFK_PR
Define the Condition Exclusion Groups in OV31.
Assign the Condition type for the Condition Exclusion Groups in OV32.
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.
Steps for creating a new or changing an existing Billing
Document Types
Create/Change your Billing types configuration in VOFA.
Some of the IMG stuff are :-
1) To block automatic transfer of the billing document to accounting, mark the field.
Indicates whether the system blocks automatic transfer of the billing document to
accounting.
During document processing, you can manually transfer blocked billing documents to
accounting by selecting:
Billing -> Change -> Release accounting
2) Account determination procedure
3) Output determination procedure etc. ...
After customizing, use transaction VCHECKVOFA to check your configuration :-
1) Proforma billing types: If it is a proforma billing type, (VBTYP = U), the field must
be blank and the account determination procedure must be empty.
2) Cancellation billing document types: : A check is made to see if the cancellation

billing document type has the right VBTYP. An F2 invoice, for example, (VBTYP 'M')
can only be canceled with billing type S1 with VBTYP 'N' . A billing type with
VBTYP '5' can only be canceled with the VBTYP '6' and vice versa.
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:
Sales documents in VTFA
Target Source
e.g. F1 - Invoice OR - Standard Sales Order
F1 - Invoice ZOR - Your Sales Order
Billing documents in VTFF

e.g. G2 - Debit Memo F1 - Invoice
G2 - Debit Memo F2 - Invoice
Deliveries in VTFL
e.g. F1 - Invoice LF - Delivery
F1 - Invoice ZOR - Your Delivery
Usually for copy control, you let the rest of the settings remains as SAP defaults.
You only assign the new Billing Document Types.
After that use transaction VCHECKTVCPF to check your Copy control customizing.
Billing Block will not worked if you did not assign it

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 worked if you did not assigned it to the desired billing types.
You can auto block by :-
1. sales document type in transaction VOV8, fields Billing Block,
or
2. item categories in SM30 - V_TVAP, by filling the fields Billing Block.
Billing Plan for Milestone Billing

Milestone billing means distributing the total amount to be billed over
multiple billing
dates in the billing plan.
As each milestone is successfully reached, the customer is billed either a

percentage of
the entire project cost or simply a pre-defined amount.
During sales order processing, the system determines from the item category
whether a
billing plan is required and, if so, which type of plan
The type of billing plan that is determined at this point is set up in

Customizing and
cannot be changed in the sales document.
Billing plans for periodic billing and milestone billing plans for project-
related milestone
billing have different overview screens so that you can enter data relevant
to your
processing.
For example, for milestone billing, you must be able to enter data to
identify the
individual milestones.
IMG configuration requires :-
1. Maintain billing plan types for milestone billing in OVBO.
2. Define date description in SM30 - V_TVTB.
3. Maintain Date Category for Billing Plan Type IN OVBJ.
4. Allocate date category in SM30 - V_TFPLA_TY.
5. Maintain date proposal for Billing Plan Type in OVBM.
6. Assign Billing Plan Type to Sales Documents Type in OVBP.
7. Assign Billing Plan Type to Item Categories in OVBR.
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
SAP Billing - Combine Billing for deliveries with different

date
When using transaction VF04 or Billing (background), the date of the billing document (e.g. the
current date) must be entered (In VF04 : settings, default data.)
In VF06 or background: variant with parametrization) to avoid an unwanted split due to the
billing date.
This OSS notes is very helpful :-
11162 - Invoice split criteria in billing document
36832 - Invoice split in fields from the sales order
Billing Spilt by Item Category

Is it possible to split invoice Item category wise. I mean If in sales order there is TAN and
TANN then the invoice should split,is it possible?
Naina
Yes, it is possible. Create a modification of copy control routine for billing and use VBAP-
PSTYV as an additional split criteria there.
Martishev Sabir
Thank you for your reply. Can you please tell me the exact steps what should I add under
that(additional split criteria).
Naina
In trx 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.
* Header data
* VBRK-xxxxx = ............
* Item data
* VBRP-xxxxx = ............
* Additional split criteria
DATA: BEGIN OF ZUK,

MODUL(3) VALUE '001',
VTWEG LIKE VBAK-VTWEG,
SPART LIKE VBAK-SPART,
END OF ZUK.
ZUK-SPART = VBAK-SPART.
ZUK-VTWEG = VBAK-VTWEG.
VBRK-ZUKRI = ZUK.
ENDFORM.
This is how it should look after modification:
* Header data
* VBRK-xxxxx = ............
* Item data
* VBRP-xxxxx = ............
* Additional split criteria
DATA: BEGIN OF ZUK,

MODUL(3) VALUE '001',
VTWEG LIKE VBAK-VTWEG,
SPART LIKE VBAK-SPART,
PSTYV LIKE VBAP-PSTYV, <- New line
END OF ZUK.
ZUK-SPART = VBAK-SPART.
ZUK-VTWEG = VBAK-VTWEG.
ZUK-PSTYV = VBAP-PSTYV. <- New line
VBRK-ZUKRI = ZUK.
ENDFORM.
After this routine is created and activated place it as the default copy control routine instead of
the old ones.
Martishev Sabir
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.
The error is as follows:
Maximum number of items in FI reached Message no. F5 727
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.
Prepaid process possible

-----Original Message-----
Subject: Prepaid process possible
I am looking for information on how we could implement a prepaid process. By "prepaid

process" I mean:
- Customer sends to us his order
- If customer is set as "prepaid", we produce an invoice for him to pay
- Once we have received his payment, we release the sales order for delivery
- no further billing document is produced.
I found information in online documentation about "down payments" (I imagine that our
prepaid process could be a 100% required down payment) but it does not seem that it
would work. From what I understood it looks like the billing plan is handled based upon the
item category, which implies the processing is "material" specific not "customer" specific.
What we do now:
- We have defined a risk category "prepaid" which is assigned to our prepaid customer.
This risk category automatically block the sales order for delivery.
- We receive the sales orders and produce a Pro Forma invoice from it, and send it to
customer
- Once we receive the payment, we release the sales order for delivery and produce the
invoices.
- We post the payment we received earlier against this last invoice.
As you see, this requires a lot of manual work and a lot of time is wasted to match all
documents together. There most be a more efficient way to handle this, anybody have any
hints?
Subject: RE: Prepaid process possible
Hi again!
You are right! However, if you create a new item category for the prepaid scenario, you can
select what item category (and process) to use at order entry. It is also possible to code a
user exit so that only certain customers will get the prepaid process. This can be done also
with item category groups (can be used to determine what default item category that
should appear). This would mean that you either have different materialnumbers for the
different processes or use different distribution channels in the sales order. DC 10 could be
the normal process and DC 20 the prepaid process. Then you need to create the sales
views in material master for DC 20 for all materials that should be possible to run in the
prepaid scenario, and enter the "prepaid item category group in the sales item category
group field in material master.
Here is a proposal of customizing activities to achieve this:

1. Create a new item category as a copy of the normal item category used for non-prepaid
sales. (Change the billing in the item category to order related billing with no billing plan)
2. Create a new item category group "ZXXX" or something of your choice with the
description "Prepaid" or something like that.
3. In item category assignment, add or check entries so that you have the order type used,
and item category group defaulting the new item category.
4. Check copy control from sales document to billing document for the new item category.
Also delivery copy control could be good to check.
5. Create a new distribution channel and assign it to the company structure (plant, sales
org etc)
6. Extend your material(s) with views for the new distribution channel and enter the "ZXXX"
item category group in the field for sales item category group (I think it is on sales 2 screen
but I am not sure, can't access a system right now).
Now you should be able to create a sales order with the new distribution channel where
the new item category is defaulted. Check that the sales order is completed when both
billing and goods issue for the delivery is posted. If not check the completion rule in the
new item category.
Good luck
-----End of Message
Sending a billing document by e-mail
First, your SAP system must be configure by the basis people in order for you to send an external
mail.
Whether it can send pdf or other file format will depends on the Mail Server you are using.
The basis people must also maintain the conversion parameters so that SAP knows how to
convert the billing documents to be send as a pdf file or other desired format specified by your
company.
Finally, you have define the IMG in Maintain Output Determination for Billing Documents
(Output type MAIL)
SAP Customizing Picking Output

From Release 4.5A, the system does no longer display the actions for SD picking in the
implementation guide.
If you want to use the picking list according to the "old" procedure, you can maintain the list as
follows:
o Carry out Transaction V/38 to maintain the output types.
o Carry out Transaction OVLT to assign the picking list types to the
shipping points.
o Carry out Transaction V/53 to assign the picking lists to own

forms and programs.

Sales and Distiribution Questionaire 1 (1) Doc

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sales and Distiribution Questionaire 1 (1) Doc

Uploaded by

Copyright:

Available Formats

SAP SD Corporate Structure Question

The business area is defined in Customizing for Sales.

What is the central organizational element in purchasing?

Explain the relationship between sales organizations and plants.

Many to Many to One.

Which organizational element is central in shipping? Give a definition of it.

Give a definition of plant (in SAP).

Organizational unit within Logistics, serving to subdivide an enterprise according to production,

To what do you assign distribution channels and divisions?

What are the highest organizational units in SD, MM.PP,FI,CO?

SD: Sales Organizations.

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

How many shipping points can you assign to a plant?

How many shipping points can you assign to a sales organization?

Sales and Distribution - Transfer of Requirements

1. Each requirement type has to be allocated to one requirement class only.

OVZG - Requirement class

It specifies the following points:

(Use transaction SM30 for V_* configuration)

To temporary block the creation of Sales Order for a certain materials.

2. warning when entering the document

Define Tax Determination Rules

The SAP System determines the taxes automatically within pricing.

MWST GST 0 Tax Exempt

Condition Type MWST

Link Between SAP SD, MM & FI

There are many such links between SD and MM.

Now the link between SD and FI :-

3. Tax determination: In case of a tax determination also, there is a direct link

How to do configuration for Credit Management function?

3. Transaction XD02 or VD02

6. Settings for the credit checks

10. Transaction OVA8

11. Transaction FD32

14. Transaction V/08, Pricing

15. Transaction OB45

16. Transaction OMO1

MRP block for Credit limit attained Customers

You should try and use one of the standard requirements.

SELECT SINGLE * INTO W_ZSDCRD

IF SY-SUBRC = 0 AND VBUK-CMGST CA 'B'.

IMPORT VBUK-CMGST TO W_CMGST FROM MEMORY ID 'CREDIT'.

Credit Mgmt Dynamic checking

A. Program RVKRED08? Or manually execute function module

SAP SD Credit Limit Problems

A. Credit Exposure = (receivables + open deliveries/ sales orders) - special liabilities.

A. Need to check couple of settings like:

1. Your customer should be assigned the credit control area.

2. In your Item Category Credit should be active.

How to do rebate processing (Scenario)

This is broadly the outline of the rebate process.

May be I can help you with rebate process.(IN -IMG)

Type in the pricing procedure.(REQUIREMENT=24)

YOU ALSO HAVE TO DO THE ACCOUNT DETERMINATION FOR REBATES.

Once you have defined all the 3 and assignment starts.

REBATE ACTIVATION- IN CUSTOMER MASTER, SALES ORGANISATION AND FOR

AFTER YOU HAVE FINISHED A COMPLETE SALES CYCLE OF CREATION ORDER ,

GO TO THE CONDITION RECORD IN CHANGE MODE (VB02) AND SETTLE THE

This is what the link says.

Name two ways to start a transaction.

Why do you create user-specific parameters?

What is a data dictionary or repository?