Otc

What is the usage of assortments (transaction code ( WSO1 ) ) in our business?

Assortment modules for value contracts are maintained in the master data for
products. You can define a validity period for each material in the assortment
module. When you create a release order, the system checks the respective
entry date against the validity period.

If you have not made any entries in the document, all the materials defined in
sales can be released unless there are any other restrictions in copying control at
item level
Assortment modules support the assortment strategy you have planned.

Each module contains an assortment which applies to all stores and which only
becomes store-specific after a suitable assignment has been made.

Special form of the traditional module types is the value contract
module.

The value contract module is generally only used to group together materials for
value contracts, but it can be used exactly like a standard module in assortment
functions.

The Procedure:

Enter a module type. Promotion modules cannot be created in this transaction;
they can only be created from within the promotion itself.

Profile modules are created directly during integrated material maintenance and
can only be edited here to a limited extent. If you wish to maintain a local module
for a single plant, enter the plant number in the 'local assortment' field.

An assortment module is a grouping of materials, which make up its items. It is
assigned to assortments. It is valid for a certain period of time and has a
maximum assortment priority. Assortment modules belong to different module
types.

The value contract module is a special form; it can be used not only in
assortment functions but also to group materials into value contracts.

Define Account Assignment Group

How to configure the Sales Account Determination?

Field found in Material Master Sales Organization 2.

To define the General Leger posting :-

IMG -> Sales and Distribution -> Account Assignment/Costing -> Revenue
Account Determination
-> Assign G/L Accounts

With this link, the material that used this account assignment group will be posted
with the desired G/L accounts during Billing.

User will not be able to Release the billing document to Accounting if this is not
setup.

If you happend to assign it via Cust.Grp/MaterialGrp/AcctKey, then you can let
your user use this report to check the material assignment.

* Transaction code VKOA

REPORT ZMATNR_AC_ASSIGN LINE-SIZE 132 NO STANDARD PAGE
HEADING
LINE-COUNT 044(001).

TABLES: MARA,
MVKE, "Sales Data for Material
C001. "Cust.Grp/MaterialGrp/AcctKey

SELECT-OPTIONS: S_MTART FOR MARA-MTART DEFAULT 'DIEN',
S_MATNR FOR MARA-MATNR,
S_VKORG FOR MVKE-VKORG DEFAULT 'ALL'.

SELECT * FROM MARA WHERE MTART IN S_MTART
AND MATNR IN S_MATNR.
CLEAR MVKE.
SELECT SINGLE * FROM MVKE WHERE MATNR = MARA-MATNR
AND VKORG IN S_VKORG.

CLEAR C001.
SELECT SINGLE * FROM C001 WHERE KTGRM = MVKE-KTGRM.

WRITE:/ MVKE-MATNR UNDER 'Material',
C001-KTGRD UNDER 'Cust Grp',
MVKE-KTGRM UNDER 'Matl Grp',
C001-KVSL1 UNDER 'Acct Key',
C001-SAKN1 UNDER 'G/L From',
C001-SAKN2 UNDER 'G/L To '.

ENDSELECT.

TOP-OF-PAGE.

FORMAT COLOR COL_TOTAL.
WRITE: / SY-DATUM, SY-UZEIT, SY-REPID,
050 'Material Sales Account Assignment',
120 SY-UNAME, SY-PAGNO.
SKIP.
WRITE: /001 'Material',
020 'Cust Grp',
030 'Matl Grp',
040 'Acct Key',
050 'G/L From',
060 'G/L To '.

Screens in the Sales Documents

Sales Order

Each sales order item can have multiple deliveries at different date. Multiple
deliveries for each sales item is specify in the Schedule line of the Sales Order.

When the Sales order was created (VA01) the system automatically proposes
data from the relevant master records:

• From the customer master record (VD03) of the sold-to party, the system
proposes sales, shipping, pricing, and billing data. In addition, the system
copies customer-specific master data about texts, partners, and contact
people at the customer site.
• For each material in the sales order, the system automatically proposes
data from the relevant material master records (MM03 - Sales view), such
as data for pricing, delivery plant, availability check, tax determination, and
weight and volume determination.

VD53 - Customer-material info record. When you create the sales order
item, the customer material number will be copy into the item Customer
Material. In the Sales order, click Item -> Purchase Order data.
Sales Document Type

Sales document can have many different document type. Each document type
have its own usage..

Some commonly used document type are:-

• OR - Standard Order
• RE - Returns
• FD - Delivery Free of Charge

Different Sales Document type have different control parameters.

For e.g. Document type ZOWN :-

General control :-
Check Division -
Blank -> no checks
1 -> Dialog to inform user that the division is different from material master
2 -> Error when division is different from material master

Shipping
Immediate Delivery
Blank -> Create delivery separately
1 -> Create delivery immediately when sales order is save
2 -> Create delivery if quantity can be confirmed to day

Maintain Sales Document Type

• Transaction VOV8 - Double click on the document type to check the
configuration.

Some configurations you can specify:-

• Check credit limit
• Define the default Delivery type
• Define the default Billing type
• Block the Document Type from being used etc.
• What the purpose of using sales order type?
• In VOV8 of sales docunment like OR, what is the functionalities of those
options?
• FUNCTIONALITY OF A SALES DOCUMENT TYPE:
• i) Document category:
Specifies a classification for different types of document that we can
process in sales and distribution system. The document category
determine how the system stores, keeps track of document data. Ex: A-
Inquiry, B-Quotation, C-order
• ii) Sales document block:
Specifies whether a sales document is blocked for processing. Note: If a
sales doc type is blocked the user cannot create new sales document of
that type, but sales doc already created before setting the block can be
changed or displayed.
• iii) Number range internal assignment and number range external
assignment:
Specifies the number ranges with the help of which either the system (if it
is internal) or the user (if it is external) can give a number for the sales
doc. Defining number ranges for sales document:

SPRO
Sales and distribution
Sales
Sales documents
Sales document header
Define number ranges for sales document.

iv) Item number increment:
Specifies the value by which the item number are incremented in sales
document “when the system automatically generate item number”
• v) Sub item increment:
Specifies how the sub-item number will be incremented in the sales
document.
Note: If we do not specify any value here the sub-item number increment
as the main item.
• i) Reference mandatory:
Specifies whether a reference document is mandatory to create a sales
document if so the indicator also specifies which type of document should
be used as reference.
• vii) Item division:
If we check this field the division ate item level in the sales document will
be determined from corresponding material master record, otherwise the
division entered at Header level applies for all the items in the sales
document.
• viii) Check division: Specifies whether and how the system reacts if the
divisions at the item level differs from the division at header level during
sales document processing
Ex: we can block some divisions for a customers.
• ix) Read info record:
If we check this field then only the system considers customer material
info record.
• x) Check PO number:
Specifies whether the system checks if the PO number exists for other
sales document.
• xi) Check credit limit: Specifies whether the system carries out credit limit
check for the customers during sales document processing.
• How To Configure New Division/Sales Area/Sales Office
• New Division/Sales Area/Sales Office
• 4.6x
• OVXA - Assign division to sales organization
OVXG - Set up sales area
• OVXM - Assign sales office to sales area
e.g Sales Organization -> Distriubtion Channel -> Division
|
-> Sales Office

• VOR2 - Define Common Divisions
• OVAN - Combine divisions allows you to share sales document type data
between different divisions. You define the sales document types in a
central division and then use it as a reference division.
For e.g.
Sales Organization Division Reference division
ALL 01 01
ALL 02 01
ALL 03 01
• OVKK - Define Pricing Procedure Determination
For e.g.
Sales Organization Distribution Channel Division Document
Procedure Pricing Procedure
ALL 01 01
A 1
• SM30 Table/View :
V_TSPA - Define New Division
V_T134G_WS - Assign Business Area To Plant
V_TVTA_GRE - Define Rules By Sales Area
V_TVTA_KFV - Assign business area by sales area
V_TVAKZ - Assign sales order types permitted for sales areas
•
• SAP SD Questions:
What is the difference between sales organization and sales area?
• When you're talking about a company, based on which thing should we
take? Is it different company codes for different locations or is it based on
the product group?
• Sales Organisation is the organisational unit which responsible for the
selling of the product, movement of goods to the customet,customer right
of recourse
• Sales Area is the combination of the Sales:
Organisation + Distribution Channel + Division.
• Company code of an organisation is the legal entity which have separate
Balansheet and profit & loss A/C required by law for the legal purpose so
whenever an organisational unit have different Balance sheet and P/L A/c
you can define a company
code.
• -- Sanjay yadav
• Organistational Structure broadly refers to the way a company follows a
set path of systems/hierarchies.
Different companies do have different structures and the differences in
structures emanates basically from the strategies. STRUCTURE
FOLLOWS STRATEGY...
• A Company's structure can be mapped in R/3 which would facilitate flow of
information, flow of process and also facilitates work flow in a logical way.
• A Sales Organisations structure is based on the Elements of the

Organisation which are as follows.
• 1. Comapny Code
2. Sales Organisation
3. Distribution Channel
4. Division
5. Plant
6. Shipping POint.
• A Company Code is generally created by finance guys and it broadly
represents the highest point of structure.
• The relation between Sales Org and Company code is Unique. One Sales
Organisation can be assigned to one Comapny code. Think of one
practical situation where in u can Say that Essar is One Group (Client).
Essar Infotech (Company Code), Essar Oil (Company Code).
Essar Oil may have Essar South (Sales Org) and Essar North( Sales Org).
You have to remember that Essar SOuth is only assigned to Essar Oil and
not Essar Infotech right....
• A Combination of Sales Org, Distribution Channel and Division is called a
Sales Area and a Sales Area is assigned to the company thru the Sales
Orgn.
• A plant is assigned to the company code. It is also assigned to the Sales
Org and Dist Channe and this channel is called Delivering Plant.
• Follow the following path to assign the business area to plant, division and
sales area:
• SPRO -> Sales & Distribution -> Basic Function -> Accounting
Assignment/Costing -> Business Area Accounting Assignment -> Define
Rule by Sales Area -> Select your Sales Area and assign a rule.
• If you had select rule 001
SPRO -> Sales & Distribution -> Basic Function -> Accounting
Assignment/Costing -> Business Area Accounting Assignment -> Assign
Business Area to plant and division
business area to sales area.
• Follow the path:
Assignment/Costing -> Business Area Accounting Assignment -> Define
Rule by Sales Area -> Select your Sales Area and assign a rule.
Business Area to plant and division
business area to sales area.

• Here we will be assigning the Business Area to Plant, Division and Sales
Area.
• Check the Transaction Codes OVF0 and OVF1.

Common Distribution Channel and Division

How to configure common distribution channel and division?

You can define common distribution channels and divisions. This is possible for
two areas of SAP, for all master relevant data, and for all condition relevant data.

The path is as follows:
IMG -> Sales and distribution -> Master data -> Define common distribution
channels.
IMG -> Sales and distribution -> Master data -> Define common divisions.

Transaction Code - The code here is [ VOR1 ].

After creating the organizational structure and relevant master records you want
to use as the masters, that is, in the distribution channels and divisions you are
going to use as a reference, you can group distribution channels and divisions
separately for master data (which combines customer master and material
master records), group condition records, or both master data and condition
records.

Let’s say you have a product range that is not different for the four different
distribution channels you have (the channels could be telesales, retail, industry,
and wholesale.) Neither is there a difference in the customers’ details when they
purchase through one or the other. Thus, you will not want to create a multiple of
four views of customer master and material master records. Merely create the
customer master records and material master records in one of the distribution
channels, such as retail. Then assign the other distribution channels you created
in the organizational structure setup to this one.

Don’t forget this means you can only create or change master data in the
distribution channel that is being referenced. In the scenario above, this means
you can only change data for the retail distribution channel. Even if you should
access a customer or material master in change mode, press F4 (possible
entries), and select telesales, industry, or wholesale, you will receive a message
“Sales area is not defined . . . ”

The same is true for the sharing of conditions. If conditions are shared, you need
only create a condition in the distribution channel or division you are using as the
reference. Obviously, this only pertains to conditions that have the distribution
channel and/or division in their key, such as a price based on sales area."

Block Sales Document Type / Delivery / Billing by Customer

When there is a temporarily stop of business with a customer, you can block new
orders to be created for this customer. You can have the options of blocking all
the work flow or let the delivery and billing to continue for any open orders.

VD05 - Block/Unblock Customer

OVAS - Sales Order Type Blocking reasons
OVAL - Blocking reasons links with Sales Order Type

OVZ7 - Delivery Blocking reasons
OVV3 - Billing Blocking reasons

In 4.6x, if you found that your Sales Order Billing Block is not working, it is
because you need to build the Billing Block for the Billing Type.

SM30 - Table/View V_TVFSP

Wrong/duplicate RE Created

• Check Document Flow for RE

Decision:-

 No Goods Issue and No Credit Memo created
 Reject the sales order item
 No Goods Issue and Credit Memo created
 Cancel Credit Memo
 Reject the sales order item
 Goods Issue and Credit Memo created
 Create another OR to offset the credit memo created.
Treat this as a normal OR process. Ensure that
account receivable is informed by typing in the item
text. Please do not send invoice to customer as the
RE is wrongly/duplicate.

Note: When you create another OR, the delivery department may actually
go and delivery the goods to customer. Thus, it is important to inform
them that this OR is for internal adjustment. The process of posting the
goods issue must be done by the delivery side for proper flow.

Sales reservation

Sales reservation takes place automatically through availability check

The setting is on the checking group ( OVZ2 - Define Checking Groups ).
You must set the "Accumul." column. Without setting this it will only check
availability but not reserve it!

SAP recommend Accumul. = 3 -> Accumulate the requirements quantity when
creating and accumulate the confirmed quantity when making changes.

For manual reservation, you can used MB21, movement type 251 - Goods Issue
for sales.
To activate the Sales Order number field, do the followings :-
Activate transaction OMBW
double click movement type 251
double click additional acct. assign.
Tick the required/optional button as per your requirement.

The user have to manage the maual reservation using MBVR.

Reserving material without sales order

In Order to reserve the specific materials for a particular customer, use Strategy
50 to plan your MRP with the materials getting reserved for customer when you
make Ind/Collective requirement(1) in MRP4 view of Material Master

or you can create a manual reservation against that particular material and give
the customer name in the Receipent Field so that you can easily identify the
Material which belong to the Customer

Sales Order Stock

Sales Order Stock are stock with Special Stock type E. It can fall into the usual
stock categories such as unrestricted, blocked etc. but "belongs" to a sales
order. For example, you create a sales order for a part and assign a sales item
category that generates an individual requisition, the requirement has an account
assignment linking it to the sales order schedule line, you convert that requisition
to a Purchase Order.

When you receive the Purchase Order, the stock is placed in sales order stock. It
will show against the sales order/sales order line. It can only be delivered against
that sales order line. Any availability check etc for that material on any other
sales order will not take it into account as it is not available except to the sales
order line the stock is assigned to.

Analyze the difference between Forecast and Confirm sales orders

MD73 - Display Total Requirements

Enter theMaterial or MRP controller you want to analyze.

Assignment field options :-
1 - If you with to look at how the planned independent requirements have been
match to the sales order. Sales order which
are over and above that forecasted are not shown.
2 - If you are interested primarily in seeing what sales order are over and above
the sales forecast.
3 - If you are interested in seeing all the sales order with indication of whether or
not they have been anticipated in the forecast.
4 - If you wish to see all the three reports of the above three options together.
- Blank if you with to see a complete list of sales order, without any indication of
whether they have been anticipated
in the forecast.

Backorder Processing

Backorder processing is a functionality in SAP where you can change the
committments and over-ride the blockage of stocks
marked against sales documents/deliveries. For e.g. you receive an order from a
very important customer for material "A" but
the entire quantity of A is committed to another customer "B" via earlier sales
orders and this is where BACKORDER processing helps you to change the
committment and shift stock due for B to A. This is the benefit of this funtionality.

OMIH - Checking rule for updating backorders
OPJL - Define new checking rule
OPJJ - Define scope of check

V_RA - Backorder Processing

Data selection:-
Sold-to-party Customer code Mandatory
Sales Organization Mandatory
Distribution Channel Mandatory
Division Mandatory

Changed confirmed quantity :-
Tick the material you want to changed and click the Backorder button
Confirmed quantity that still can be changed are highlighted.

V.15 - Backorder List
Sales Organization Mandatory
Distribution Channel Mandatory

Division Mandatory

Third Party Order Processing

Third party order processing is as follows:

Assume three companies X, Y and Z
X - The company,
y - The customer
Z - Vendor

When ever X gets a PO from Y to supply some goods, X has an option of either
manufacturing those goods or procuring those goods.

If he is procuring the goods, there are two methods that are generally followed:

Method 1) After receiving the PO from Y, X creates a sales order against Y.
Now at the same time he also creates a PO to a vendor Z to produce the goods
Z produces the goods and supplies to X
X receives the goods from Z
Then X delivers the same goods to Y.
After that X invoices Y and Z invoices X.

Note : Here there is no direct/ Indirect relation between Z and Y.

This process is known as Trading Process. and the Material here is created with
Material type HAWA.

The other method is a Third party order processing method:

Here the glaring difference is that instead of Z supplying the material to X and X
in turn supplying the same material to Y.

X authorizes Z to supply the material to Y on his behalf and notify him once the
delivery is complete.

Now Z supplies the material to Y and acknowledges the same to X.

Z will send a copy of delivery acknowledgement and invoice to X.

After receiving the delivery confirmation and invoice from Z, X has to verify the
invoice and this process is known as invoice verification and is done in SAP
through Tcode MIRO.

The next step for X is to create an invoice and submit to Y

Only after the invoice verification document is posted then only X can create an
invoice for Y.

This is the business flow that is followed for third party order configuration.

There are few steps that have to be configured to enable the system to function
as mentioned above.

Step1)
If you are always followwing a third party process for a material then you have to
create the material using item category group BANS.

The procument type should be marked as External procurement (F) in MRP 2
view of the material master record.

if you are not always allowing third party order processing then u 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 procurment ( in house
manufacturing and external procurement).

step 2)
the item category in the order should be manually changed as TAS.
For that you need to confugure the item category determination

ord type + item cat grp + usge + Hiv level = Item cat + Manual item cat

OR + NORM + + = TAN . + TAS
OR + BANS + + = TAS

Step 3)
make sure that during the item category configuration for TAS you need to mark
relevnat for billing indicator as F

step 4)
The schedule line cateogry for this type should be CS.
make sure that you mark subsequent type as NB - purchase requisition in this
schedule line category as this will trigger the purchase requision order
immediately after the creation of the sales order and the PO to vendor is created
against this purchase requiesion.

Defining Company and Assigning Sales Organization

Definition of Company Code

1.Transaction Code: SPRO
2. Click Enterprise IMG button

3. Select Enterprise Structure -> Definition -> Financial Accounting -> Define,
Copy, Delete, Check Company Code -> Edit Company Code Data
4. Check the check box and all yes radio buttons. Click Continue button
5. Click New Entries Button and Type your company code and name.

Assignment of Sales Organization to Company Code
1. Transaction Code: SPRO
2. Click Enterprise IMG button
3. Select Enterprise Structure -> Assignment -> Sales and Distribution -> Assign
Sales Organization to Company Code

Joy

The sales organization is an organizational unit within logistics, that structures
the company according to its sales requirements. It represents the selling unit as
a legal entity. It is responsible for product guarantees and other rights to
recourse, for example. Regional subdividing of the market can also be carried out
with the help of sales organizations.

Each business transaction is processed within a sales organization.

Each sales organization is assigned exactly one company code for which you
enter all accounting details of the sales organization.

A distribution chain can be active for several plants and the plants can be
assigned to different company codes. If the sales organization and plant are
assigned to different company codes, an internal billing document is sent
between the company codes before the sales transactions are entered for
accounting purposes.

Schedule Line Categories and Schedule Agreements

What is the meaning of schedule line categories and schedule agreements?

If you take a sales order document, it is divided into three parts:

Header Level information :
This consist of the overall information of the sales document, for example Net
value of the sales order and the like.

Item level information :
This consist of information at item level, like Item 1 has a material with a net price
so and so, item 2 has another material with another net price and so and so.

Schedule line information :
This gives the information of the time a sales order has to be delivered to the

customer, to view this select the item you want to view and to the menu under
item >> Schedule line. This date is actually calculated from the delivery date in
the Sales document.

Schedule line Agreement :
Use the T.code VA31 (and choose Scheduleline agreement) : This agreement
lets you to predetermine scheduling of different materials with in a given period of
time (This is same like the other contracts).

First enter the material with quantity say for example Material 1 Qty: 40, go to
Edit from the menu >> Item >> Schedule line

There select within the time period defined two dates, say for example on 12: 01:
2005 20 quantity and on 13: 01: 2005 another 20 (The qty has to be same as the
one in the sales order) .

Once this is done you have created a schedule line agreement.

Call this agreement in your sales order (with reference) and use them.

Note: You will be able to deliver only 20 qty on the 12th and 20 qty on the 13th,
even though the sales order is for qty 40

How The System Proposes Probability For Each Item

You have to enter probability % in IMG of sales document header.

The probability (expressed as a percentage) of the customer confirming the
inquiry or quotation as part of a sales order.

The system uses the probability and net value of each item to calculate a total
expected order value for the sales document. The expected order value appears
in the double-line entry screen.

The system proposes the probability for each item. You can change the value
manually depending on the sales document category.

For example:

A quotation contains two items: A quotation contains two items:
- Item 1 has a value of $100 and a probability of 100%
- Item 2 has a value of $200 and a probability of 25%

The system calculates the total probability as follows:
($100 x 100% + $200 x 25% ) divided by $300 = 50%

In this case, the probability of this quotation resulting in a sales order is 50%.

You can generate requirements from quotations. The probability of the quotation
items affects how the system passes on requirements. For example, a quotation
for 100 pieces and a probability of 50% will generate requirements for 50 pieces.

Consignment Pickup and Consignment Return Process

Difference between the Consignment Pickup Process and Consignment Return
Process.

The difference between Consignment Pickup and Return are:

1. In Consignment Pickup what ever the goods lying at the customers point as
Consigment stock will be taken back before consignment issue to the said stock.
Which means the Special stock will be converted in to actual stock or
unrestricted stock.

2. In Consignment Return the goods were already sold to the customer by doing
Consigment Issue. And the customer want to return the stock because of some
reason (like Poor quality, Unable to sell, Price changes, Expiry etc). After doing
consignment Return the stock will be once again added to the Special stock but
not to the Unrestricted stock. If we want it to be unrestricted we should once do
the process by using Consigment pick up.

---

Consignment pickup: Process where the consignee (person who stocks the
goods to sell) has not yet sold the goods and has returned them back to the
consigner (company that manufactures the goods) due to damage.

Goods flow :- CONSIGNER ----> CONSIGNEE ---> CONSIGNER

Consignment return: Process where the customer returns d goods to the
consignee and consignee returns the same to the company. here as the
consignee has already sold (& billed) d goods to the customer, the company
has to issue a credit memo to the consignee (AS IN CONSIGNMENT
PROCESS COMPANY PAYS THE CONSIGNEE ONLY WHEN HE SELLS THE
GOODS TO THE CUSTOMER).

Goods flow :- CONSIGNER ----> CONSIGNEE ----> CUSTOMER ---->
CONSIGNEE ----> CONSIGNER.

---

KB - Fill up

You leave the material in customer premise (say 100 items)
Materialis lying in customer 's place but stock is still in your books.

KE - Issue
Your customer consumes (sells to his cutomer if he is in retail / uses up for
production if he is in mfg)
25 items now 25 items have been invoiced on him

KR - Returns
If the material issue (25 items) are defective you will take it back using KR
(returns)

KA - Pickup
75 items not used by your customer, if you want to take back you will be using
KA

What is the transaction for mass updation of sales order and what are the fields it
will affect?

by: Ketan Rathor

There is a Transaction MASS which can be used to carry out mass changes in
the sales order.

In T Code MASS please select Sales Orders and execute.

Then you choose the relevant tables and the fields which you want to change
and then execute it.

Thereafter you enter the document range and also the relevant datas and then
you choose "Selection Field". Add the fields from Pool to Selection Field using
the arrows.

Now you go to Mass Maintenance menu and click on "Enter New Field Values".

Choose the data and then you execute it . Thereafter you will see that the datas
have changed and then you need to save it .

Once it has been saved, the values will change.

You can check the status through sm37.

You can alternatively go to se16 and go the particular table. Then do mass
maintenance and compare the results. If they match then it has been done .

Difference Between Cash Sales and Rush Order

What are the differences between cash sales and rush order?

by: Naveen Gampa

1) Cash sale : in this delivery automatically happen when you save the sales
order. After that you have to give an invoice to the customer.

2) Rush order. Here also delivery automatically happen when you save the sales
order. But the difference is you can send invoice after some time but the delivery
should happen immidately.

If you goto any super market first, you pick up the item and then pay the bill and
then you will get the bill, this process is cash sales.

Cash sales is order related billing whereas RO is delivery related.

Cash sales is not relevant for availability check as you will be picking the goods
whereas RO is relevant for availability check.

Cash sales is also not relevant for credit management whereas RO is relevant
credit management.

Cash sales uses RD03 as output which immediately prints the invoice whereas
RO uses standard output RD00.

Cash sales has one time customer account group where as RO normally doesn't.

For cash sales order type is BV or CS and for RO it is RO

Cash sales triggers petty cash a/c where as in RO customers account is debited.

Delivery and settlement will be done immediately in cash sales where as in RO

only delivery will be done immediatrly.

Rush Order/Cash Sales –

Rush orders and Cash sales are sales document types that are used in the sales
from plant process or when the customer needs to pick their goods immediately
from the warehouse.

In the sales document type, the following changes have to be made for rush
order/cash sales –

a. order type – RO/CS

b. shipping conditions – immediately

c. immediate delivery – X

d. lead time in days – not to be specified

e. delivery type – LF/BV

f. billing type – F2/BV

g. item category – TAN/BVN

h. schedule line category – CP/CP

In case of rush orders and cash sales once the goods have been withdrawn from
the warehouse, picking and posting goods issue can begin.

In case of rush orders, when you create the billing documents the system prints
the invoice papers and sends them to the customer.

But in case of cash sales, an order related billing index is generated
automatically. This updates the billing due list. Billing type BV is created, while
the billing due list is being processed and the system does not print invoices
during billing for a cash sale.

In cash sales when you save the order, the system automatically generates a
cash receipt that can be given to the customer as an invoice and the goods are
picked up from the warehouse immediately by the customer. You control the
output with output type RD03, contained in the output determination procedure
for order type CS.

How To Configure Product Hierarchy

SAP Configuration ==> SAP Sales and Distribution

Product Hierarchy:

Product hierarchies are the domain of materials management. A product
hierarchy is assigned to the material master record. This hierarchy is broken
down into specific levels, each level containing its own characteristics. A product
hierarchy is recorded by the sequence of digits within a hierarchy number. This
hierarchy number may have a maximum of 18 digits with a maximum of 9 levels.
The custom Product hierarchies can be maintained in V/76.

Product Hierarchy Number of chars at Various level

In the standard system, the product hierarchy consists of up to 3 levels. The first
and second levels have 5 digits and the third level has 8. The maximum number
of digits is 18 and the maximum number of levels is 9.

You can define hierarchy nodes at the individual levels of the product hierarchy.

The product hierarchy can be structured via DDIC structure PRODHS. In the
standard system, a product hierarchy can be created with up to three levels. The
individual levels can contain the following number of digits:

Level number of allowed digits

15
25
38

This can be changed as of Release 3.0, where it is possible to extend the
maximum number of levels to 9.

If you want to change the standard setting of PRODHS, e.g. you want to change
the number of levels, proceed as follows:

1. Create an appropriate domain in the Data Dictionary (type CHAR with the
required length).

2. Assign these domains to the standard data elements PRODH1, PRODH2, ...,
PRODH9.
Please note that you should use these standard data elements.

3. Change the structure PRODHS by creating or deleting fields with reference to
the data elements.
Choose ZZPRODHN as field name, where n is the position of the field in the
structure PRODHS.

You want to change the structure of the product hierarchy from 5/5/8 digits to
5/5/5/3. Proceed as follows:

Create the following domains:

ZPRODH3 with length 5, category CHAR,

ZPRODH4 with length 3, category CHAR,

Change structure PRODHS:

Structure PRODHS in the standard system:

Structure Fields Data element Category Length

PRODHS ->

PRODH1 PRODH1 CHAR 5



Changes according to example:

Structure Fields Data element Category Length

PRODHS ->




ZZPRODH4 PRODH4 CHAR 3

please take help of ABAPER in extending the levels of Product hierarchy

Configure for Product hierarchy at

SPRO -> IMG -> Logistics - General -> Material Master -> Settings for Key Fields
-> Data Relevant to Sales and Distribution -> Define Product Hierarchies

Explain in detail the configuration steps involved in Customer Hierarchy and how
can we validate the Customer Hierarchy in Sales Order Processing.

Follow the steps for customer hierarchy:

spro -> s&d -> master data -> business partner -> customer -> customer
hierarchy.

(1) define hierarchy types (OVH1) (optional) (you can use the standard type A)
(2) set up partner determination for cust hierarchy

a) Partner functions
1a ku 1b A (see the step 1)
1b ku 1c A
1c ku 1d A
1d ku -- A

b) A/C group functions assignment
sold to a/c gr 1A, 1b, 1c, 1d
bill to -do- 1A
ship to -do- 1A
payer -do- 1A

3) Assign a/c groups OVH2
standard a/c gr your a/c gr( as example)
0012 sold to
sold to ship to
ship to bill to
(do it as per your requirement)

4) Assign sales areas. OVH3
New entries
higher level to lower level
(what ever the discounts you maintain for the higher level it will be passed to
lower level)

5) Assign hierarchy types for pricing by sales document types OVH4

6) Create nodes V-12 (condition record)
use the standard account group 0012(see the 3rd step)

7) Condition record for maintaining customers in hierarchy levels.
VDH1N. use the standard type A and use the node number that you have
created in above step.
click on create
Heir level customer node number
lower level customer XXXXXXXXXX ( from the sales area and a/c groups used
above steps for assignments)

**First time using the node in the higher level is must
see the chart 0012-----
--------XXXXXXX
-------YYYYYYY
--------ZZZZZZZ
---------kkkkkkk

All the X Y and Z customers are assigned to node directly but customer k is
assigned to cust Z meaning : the discount given to node 0012 will be passed on
to all But cust k will only get the discount that assigned to cust z.

** Maintain hierarchy discount types HI01 or HI02 in pricing procedure.
** Maintain discount on the above condition types in VK11 by node or customer.

Please do the following for partner determination:

First determine one account group ( Trans code OBD2 ) assign number range for
acct group ( Trans code OBAR ).

Path:

SPRO --> Sales and Distribution --> Basic Functions --> Partner determination --
> Setup partner determination --> Select setup partner determination for
customer master

Step 1 : Defining the Partner Functions:

Here we must not define any partner function.

Go to partner functions.

While defining the partner functions if we check the field “Unique” that partner
faction has to be unique in the customer master i.e. we cannot have multiple
partners of that function in a customer master.

Step 2 : Assigning the partner functions to the Account group:

Go to account group’s function assignment.

Go to new entries and assign the required partner functions to the required
account group and save it.

Step 3 : Defining the partner determination procedure

Go to partner determination procedures

Go to new entries and define and save it

NOTE: Procedure contains all the required partner functions.

Step 4 : Placing the required partner functions in the procedure:

Select the defined procedure and go to partner functions in procedure.

Go to new entries and place the partner functions

If we check the field “Not Modifiable” for a partner function it cannot change in the
customer master.

If we check the field “Mandatory Function” it becomes a mandatory in the
customer master and save it.

Step 5 : Assigning the procedure to the Account Group:

Go to partner determination procedure assignment.

Assign the procedure to the account group and save it.

Your partner determination is now done.

Company's Order To Cash Process

What is meant by "Order to Cash"?

Customer Order:

A customer orders some items from your company by creating a sales order.

Tcodes: VA01, VA02, VA03

Tables: VBAK, VBAP etc.

Deliveries:

Your company decides to deliver the items ordered by the customer. This is
recorded by creating a outbound delivery document.

TCodes: VL01N, VL02N, VL03N

Tables: LIKP, LIPS etc.

Once the items are available for sending to the customer, you post goods issue
which reduces your inventory and puts the delivery in transit.

This will create a material document. You will post goods issue using VL02N but
the material document created will be stored in tables MKPF, MSEG.

You will then create shipment document to actually ship the items. (Tcodes:
VT01N, VT02N, VT03N, Tables: VTTK, VTTP etc).

Billing:

You finally create a sales billing document. (TCodes: VF01, VF02, VF03, Tables:
VBRK, VBRP etc).

This will have a corresponding accounting document created that will be in BKPF,
BSEG tables.

When customer pays to your invoice, it will directly hit your AR account in FI.

You will have to remember that these are not a required sequence. Some times,
you may configure your system to create a SD invoice as soon as you create a
sales order or you may not create a shipping document at all.

This is the position where Functional Consultant would come into picture and
study the company's order to cash process and configure the SAP system to do
so.

How free goods is configured?
How to configure according to material?

Free goods are configured by condition technique and pricing procedure. This
small note on this will help you.

Maintaining records for inclusive free goods

Logistics
Master data
Conditions
Free goods
VBN1 create

Specify the free goods discount type NA00
Select the required key combination

Material : Specifies the material for which free goods are given.

Minimum quantity: Specifies the minimum quantity of the maeterial that has to be
ordered in order to get free goods.

From: Specifies the quantity from which free goods starts.

Unit of measure: Unit of measure of material.

Are free goods: Specifies the quantity of free goods given to the customer.

Calculation rule: Specifies the rule for calculating the quantity of free goods.

Free goods: Specifies whether the records are maintained for inclusive or
exclusive free goods.

Free goods delivery control: Specifies whether free goods are to be delivered
regardless of the main item or in conjunction with the main item.

Save the condition record.

Maintaining records for exclusive free goods:

Logistics
Master data
Conditions
Free goods
VBN1 create

Specify the discount type for free goods NA00
Select the required key combination
Select the button exclusive.

Additional free goods: Equal to “are free goods” in inclusive

For : Equal to “From” in inclusive.

Free goods : inclusive/exclusive.

Additional material free goods: Specify the material which is given as free of
charge item.

Free goods delivery control:

Note:
1. Inclusive free goods takes 10 as 9+1.
Exclusive free goods takes 10 as 10+1.
2. In exclusive free goods if required we can give the same material as free of
charge item.
3 *Free goods concept is based on condition technique.

SPRO
Basic functions
Free goods
Condition technique for free goods
Maintain condition tables
(After defining condition tables you have to place in Access sequence)
Maintain Access sequence
Maintain condition type.
Go to New entries and define the condition type to which assign the access
sequence.
Maintain Pricing procedure
Activate free goods determination.
We need to assign the free goods procedure to the combination of sales area,
doc pri pro, and cust pri pro.

To make the value of free of charge item as ‘0’, in the main pricing procedure, we
have to take the condition type R100.

Otc

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a Otc

Similar a Otc (20)

Último

Último (20)

Otc