第 18 页 / 共 33 页
SAP SD IMP NOTES
example- packing material), for deliveries without reference to an order (Delivery type LO). In
such case the item category determine take place on the basis of customizing setting which is
same as that of sales document item category.
(cid:30) Delivery item category det. - delivery document type + item category group + usages
[DLN (standard item without order) - LO+NORM]
Route determination
• Route determination is carried out in sales order item and depends on:
(cid:214) The departure zone- shipping point (customizing)
(cid:214) Shipping condition-sales document type or sold to party
(cid:214) The transportation zone- ship to party (shipping tab)
(cid:214) The transportation group-material master (general/plant)
• In the order item, you can manually overwrite the route that is determined.
• You can re-determine the route in the outbound delivery based on the weight (weight group).
Whether the route is re-determined depends on the configuration of the delivery type.
Shipment or Delivery scheduling
• Different Times involved in delivery scheduling-
(cid:190) Pick/Pack Time
(cid:190) Loading Time
(cid:190) Transportation Time
(cid:190) Transit Time
• Shipping point calculate: - Pick/Pack Time, Loading Time
• Route calculate: - Transportation Time, Transit Time
Backward scheduling- system confirms the quantity of delivery on the basis of customer request
delivery date.
Forward scheduling- system confirms the quantity on the basis of New Material availability date.
Precise scheduling-the system calculates and displays the results of scheduling down to minute. If you
have maintained the working times of the shipping point, the system performs precise scheduling.
Daily scheduling: - the system uses days, hours, and minutes for calculation, but only displays the
resulting dates.
Route schedule: - the route is used to determine the transportation lead-time and transit time. For
Transportation lead-time precise scheduling uses the working times of the shipping point; daily scheduling
uses the factory calendar of the shipping point. For the transit time both types of scheduling use the
factory calendar of the route to determine when route is used.
(cid:190) You can use the route schedule to organize outbound deliveries from a particular
shipping point to different ship to party.
(cid:190) The route schedule generally contains: Route, Departure date and time, list of ship to party
and itinerary (optional)
(cid:190) You can use route schedules in sales order, stock transfer and outbound deliveries.
(cid:190) In customizing, you define whether a route schedule should be assigned for each shipping
point, order type, purchasing doc. type (Delivering plant) and delivery type.
Abhishek Parihar
SAP SD Certified Consultant
E-Mail: abhishekparihar@rediffmail.com
第 19 页 / 共 33 页
SAP SD IMP NOTES
Picking location / storage location determination: - MALA, RETA, MARE
• MALA: - determination based on the shipping point, the delivering plant, and the storage
location (Material master-plant data/storage 1)
• RETA: - Determination based on the delivering plant, situation, the storage condition.
• MARE: - First MALA then RETA
Options for creating Outbound Deliveries
• Each outbound delivery starts at a shipping point, continues along a route, and has the ship to party
as the destination. These elements are header fields in outbound delivery.
• You can store delivery agreements using the indicators in the customer master record of sold to party
or in the customer material information.
• If the customer allow order to be combined, the R/3 system combines orders when creating the
delivery due list. For this the following characteristics should be same:
• Shipping point, Delivery due date, Ship to party, Incoterm, Route
• You can create an outbound delivery manually with or with out reference to a particular order.
However, if you create a delivery manually, you cannot deliver purchase order or other request.
Delivery due list
• The delivery due list is a work list of all operations requiring deliveries
Shipment
• If you use transportation functions, outbound deliveries are grouped together on the basis of
user-defined criteria in a document called the shipment document.
• Shipment function is optional. You can create a shipment after delivery creation or after PGI.
You can invoice the customer for shipment cost.
Out bound delivery monitor
• The outbound delivery monitor displays all deliveries that are still to be processed or that
have just been processed.
• You can use the outbound delivery monitor to execute important follow-on-functions in collective
processing in the background ( for example-transfer orde creation for picking, or posting of goods
issue).
Transfer order
• A transfer order is an instruction to move material from a source storage bin to a destination
storage bin within a warehouse complex.
• The transfer order include the information like-material number, quantity to be moved, source
and storage bin.
• With WM precise inventory management at the level of the storage bin is possible and used for
warehouse with random storage. This is not possible with lean WM and hence suitable for fixed
bin warehouse.
• You can Group Transfer order based on the warehouse number.
Abhishek Parihar
SAP SD Certified Consultant
E-Mail: abhishekparihar@rediffmail.com
第 20 页 / 共 33 页
SAP SD IMP NOTES
• Automatic or direct creation of transfer order if the systems determine output type WMTA at
the header level of outbound delivery when delivery is being created.
Batch management setting-
• Material master-Plant/storage 1 view and purchasing view- Activate batch management.
• In customizing- delivery item category, sales item categories (automatic batch determination)
when delivering a sales order, this batch is copied to outbound delivery. Then you cannot
change batch in outbound delivery.
• If a batch has not been specified in the sales order, you can enter one in the picking overview
screen of the outbound delivery. You must specify a batch before goods issue.
• Batch split function is used if delivery quantities of an item are to be taken from different
batches. It can be done manually in batch split screen of delivery item or automatically using
automatic batch determination, for this customizing is done in delivery item category.
Serial number
• You can assign a unique serial number to each material. This is allows you to monitor goods
movement for individual materials.
• To use serial numbers, enter serial number profiles in the material master record (general/plant
and Plant data/storage-2).
• Serial number is specified in the delivery item or the order.
• You must specified serial number before posting goods issue.
Shipping related condition
• The outbound delivery can contain shipping-related condition at header level.
• You can use the SD pricing technique.
• Assign the pricing procedure to the delivery type
Delivery split
• When you split a delivery, you create one or more new deliveries, called result and the reminder.
• When you call the delivery split, specify a split profile to determine the type of split. Split profiles are
define in customizing, and assign to delivery type.
(cid:214) Delivery split by warehouse number
(cid:214) Delivery split by partner
Packing
• The packing function is available in –Order (as packing proposal), In the inbound delivery, In the
outbound delivery, In the shipment document.
Packing control-
• You define packaging material type and packaging material group. Assign packaging material
type to packaging material group. Choose material type VERP for material master and maintain the
packaging material group in basic data 1 and sales: general/plant views. However, if this field has
not been maintain in the material master, this material can be packed in any packaging material-
depending on the weight and volume.
Abhishek Parihar
SAP SD Certified Consultant
E-Mail: abhishekparihar@rediffmail.com
第 21 页 / 共 33 页
SAP SD IMP NOTES
• The system can generate a separate item in outbound delivery for each packaging material. For this-
(cid:214) You must set item category determination in customizing. In this context, table entries with
PACK usage are relevant.
(cid:214) The delivering plant must be determined using the plant determination rule in the
packaging material type or must be entered manually.
(cid:214) If you want to bill the customer for packaging material, item category should be determined as
DLN.
(cid:214) If you use returnable packaging material, you must create them in the material master with item
category group LEIH (item category TAL is determined). When goods issue is posted, the
material is transferred to special stock for the customer.
Goods issue
• Posting goods issue involves an interface with FI as stock valuation changes.
• After goods issue has been posted, there is limited scope for changing the outbound delivery.
• The prerequisites for posting goods issue is that picking-relevant item are completely picked (transfer
order is confirmed). This means that the delivery quantity and the picked quantity in the outbound
delivery must be same.
• Goods issue can be posted by changing a single outbound delivery, by collective processing
function to select all deliveries for which goods issue is due to be posted, can also use the outbound
delivery monitor to do this and at the time of transfer order creation (to choosing adobe quantity 2)
• Any errors are logged when, for example, data such as the batch or serial number is missing or
when picking has not been carried out fully for these items. In this case, goods issue is not posted.
• The goods movement is controlled by “Movement type-601” (schedule line)
Effect after goods issue-
(cid:214) Reduce warehouse stock
(cid:214) Post the value change to the stock accounts in inventory accounting
(cid:214) Enter status information in the outbound delivery.
(cid:214) Reduce delivery requirement.
(cid:214) Is store in document flow and update status of preceding document
(cid:214) Create work list for billing.
Cancel goods issue
• If goods issue for an outbound delivery is canceled, the goods issue posting is reset. The system
copies the quantities and value from the original goods issue document and carry out an inventory
posting based on these quantities and values with a reversed +/- sign.
• If the outbound delivery has been fully or partially billed you must first cancel the billing document,
then you cancel goods issue.
• After goods issue has been canceled, the goods movement status of the outbound delivery is reset to
“Not yet started”. This allows you to further process the outbound delivery (Goods issue) as usual.
• For each movement type in inventory management, you must define a reversal movement type
in customizing. No additional settings are required for movement types used for goods issue posting.
Abhishek Parihar
SAP SD Certified Consultant
E-Mail: abhishekparihar@rediffmail.com
第 22 页 / 共 33 页
SAP SD IMP NOTES
Quality management
• You specify in the quality management view of the material master if a quality inspection is to be
carried out for the material. When the outbound delivery is created in SD, QM automatically creates
an inspection lot for the delivery items that are relevant for inspection. The usage decision represents
the completion of a QM inspection. Depending on the customer, or on the customer and the material
together, you can specify if the inspection log must be accepted before goods issue can be posted. You
initiate printing of a certificate of quality from output control of the outbound delivery at item level.
POD settings
• You need to define which delivery item categories are relevant for the POD process. You also need
to define reason for deviation, and in the customer master data (sales area- shipping tab) specify
POD relevance.
• The system creates the billing document based on the correct (verified) quantity. The creation of a
billing document using the billing due list is blocked until proof of delivery has been confirmed.
TAB PAGES IN DELIVERY DOCUMENT
Overview: - Item overview, Picking, Loading, Transport, Status overview, Goods movement data.
VARIOUS COLUMNS IN PRICING PROCEDURE (RVAA01)
Step, Condition counter, Condition type, Description (condition, From, To, Manual, mandatory,
Statistic, Print (X-print of item level), Subtotal (reference level), Requirement, AltCty (Routine),
AltCBV (Routine), Account Key (ERL, ERS), account key- accruals
Step-
Condition counter-
(cid:214) Access number of the conditions within a step in the pricing procedure.
(cid:214) During automatic pricing, the system takes in to account, the sequence specified by the
counter.
PRICING
The term price book refers to a price determination strategy.
Abhishek Parihar
SAP SD Certified Consultant
E-Mail: abhishekparihar@rediffmail.com
第 23 页 / 共 33 页
SAP SD IMP NOTES
Condition records
• Condition records based on key fields (combination of key fields called condition table)
• In pricing condition records you can have a validity period, maintain scale and specify upper and
lower limit for manual changes. Manual changes only in this specified limit.
• You can define unlimited number of levels in a scale.
• You can do mass maintenance of conditions which means that condition records can now be
maintained across all condition type and condition tables.
• New condition records can be created with the reference of existing condition records. Individual
condition records can be maintained manually.
• New price function allows you to maintain multiple condition records simultaneously.
• You can maintain long text in the condition records for pricing and agreements (rebates, sales deals
and promotions)
Pricing report
• To provide an overview of existing condition records. You can generate a list of conditions for
analysis.
• When you creating a new program for pricing report, you first decide in which views you want to
analyze condition records. You do this by selecting specific fields from the existing condition tables.
Depending on which fields are selected, the system will generate a list of tables, which contain at least
one of the selected field catalogues. From this list of tables, select which tables will appear in the
report.
Condition indexes
• You can create and use condition indexes to search for condition records that were created for a
variety of condition type and condition table. Before you can use the indexes that are delivered in
the standard version, you must first activate them in customizing for sales. However, if you create your
own indexes, the system automatically activates each new index when you generate it.
Condition table
• Condition table is a combination of fields, which form key for a condition record.
• Each condition table defines under access sequence.
• All fields, which are to be used for creating a condition table, must be contained in the field catalogue.
It is possible to add additional fields to this catalogue.
Release procedure
• You can allow a release procedure to be used when a condition table is created by selecting the with
release status checkbox. This adds the following fields to the condition table automatically.
(cid:214) KFRST-Release status as last key field
(cid:214) KBSTAT- Processing status as a field of the variable data part (non key field)
• “The release status is set indirectly by defining a processing status in customizing for pricing and
assigning a release status to the processing status”
• Different statuses are
(cid:214) Released
Abhishek Parihar
SAP SD Certified Consultant
E-Mail: abhishekparihar@rediffmail.com
第 24 页 / 共 33 页
SAP SD IMP NOTES
(cid:214) Blocked
(cid:214) Released for price simulation
(cid:214) Released for planning and price simulation.
Access sequence
• An access sequence (search strategy) is defined for each condition type (except header and manual
condition type) in pricing procedure.
• Each access performed during pricing procedure, the access sequence is made using condition table.
• Access sequence is a search key for condition record, which made up of key fields.
Condition type
• The condition type determines the category of a condition and describes how the condition is used.
• The calculation type and scale base type can be controlled for each condition type.
• Conditions: - Price, discount/surcharges, freight, taxes
• Each condition type you can be set as an automatic surcharge, discount or either.
• As well as being determined automatically, condition can also be entered manually in the sales
document. You can prevent one condition type from being changed manually by making setting in
customizing.
Header condition (E.g. HM00, AMIW)
• Header conditions are valid for all items. These are automatically distributed among the items based
on net value. The basis for distributing the header conditions can be changed in the pricing procedure
by selecting the appropriate routine (e.g. weight, volumes) in the AltCBV field (alternative formula for
condition base value)
Special pricing functions
• Group condition:-In customizing you can set a condition type to be a group condition. The condition
base value (e.g. weight) is then calculated as the sum of the individual items within one group. E.g.-
K029
• Group condition with varying keys: -For group conditions with varying keys, item quantities are
accumulated for scale point determination purpose but the rate for each item is calculated from its
individual condition record. E.g.-K005
• Condition update: -Value can be accumulated in the condition records and tested against limits. In this
way, you can set a maximum condition value, condition base value, or number of orders for a
condition. For this you must activate condition update switch in customizing for condition type. [Then
only these fields visible in condition records]
• Condition supplements: -Condition supplements are group of conditions, which are accessed together
during pricing.
• Condition exclusion
(cid:214) Condition exclusion indicator can be set in either the condition type or the condition
records.
(cid:214) Condition types to be compared are first placed in an exclusion group. During pricing, the
conditions which result in the best price (lowest charge or highest discount) are selected from
this group. All others are deactivated.
Abhishek Parihar
SAP SD Certified Consultant
E-Mail: abhishekparihar@rediffmail.com
第 25 页 / 共 33 页
SAP SD IMP NOTES
Special condition type
Manual pricing: - (E.g.-HM00, PN00)
• Header condition type HM00 allows you to enter the order value manually. The new order value is
then distributed proportional the items, taking into account the previous net value. Taxes are
determined again for each item.
• Item condition type PN00 allows you to specify the net price for an item manually. The original
conditions are deactivated.
Minimum price: - (E.g. AMIW, PMIN)
• Header condition type (AMIW): -you may create a minimum value for each order using condition
type AMIW. If the value in the order header is less than this minimum order value during pricing, the
system uses the minimum as the net order value automatically. The minimum order value is a
statistical condition. Condition type AMIW is a group condition and is divided among the different
items according to value.
• Item condition type PMIN: -You can create a minimum price for a material using type PMIN. If the
minimum price is not met during pricing, the system determines the difference using condition type
PMIN
Interval scale (PR02)- Scale pricing
• You can maintain condition records with interval scales if the condition type is set to scale type D in
customizing. Interval scales cannot use for group conditions.
Rounding Diff: -
• You can maintain a rounding unit in table T001R for each company code and currency.
Condition DIFF determines the difference amount. Condition type DIFF is a group condition and is
distributed among the different items according to value.
Customer Hierarchy Pricing
• Customer hierarchy are available in sales order management so that you can create flexible hierarchies
to reflect the structure of customer organization.
• Use Customer hierarchy during sales order processing and billing to determine pricing and running
statistics.
• A Customer hierarchy consists of nodes. Which are only valid for a certain period of time. They also
be moved. If a node is moved, the system automatically reassigns all related nodes and customer
master data.
• Settings-
(cid:214) Create master records for each node
(cid:214) Assign node to each other
(cid:214) Assign the customer master records to the relevant nodes.
• “With customer hierarchies, you can assign price or rebate agreements to a higher level node”
• Customer hierarchy accesses also provide clear and easy master data maintenance because the
different condition records for a condition type can be created together in the quick entry screen for
maintaining condition.
Abhishek Parihar
SAP SD Certified Consultant
E-Mail: abhishekparihar@rediffmail.com
第 26 页 / 共 33 页
SAP SD IMP NOTES
Discount and surcharges
• Pallet discount-KP00, incomplete pallet surcharge KP01, Mixed Pallet Discount KP02, Surcharges for
incomplete mixed pallets KP03
Statistical condition type
• Condition type VPRS-statistical condition used to retrieve the standard cost of the material has
condition category G. it accesses the material valuation segment of material master.
• Condition type SKTO- statistical condition used to retrieve the cash discount rate. It has condition
category E.
Update price
• Update prices on the condition screens is available at header and item level ( in sales order and billing)
: you can choose the pricing time in a dialog box.
Calculation type
• The calculation type for a condition type is defined in customizing. This calculation type determines
how prices or discounts and surcharges are calculated for a condition.
Pricing procedure
• The sequence in which the system accesses the conditions by using condition technique in
business document is determined in the pricing procedure.
• “Requirements, routine and formula provide a method to modify the standard pricing logic to meet
unique user requirement”
Pricing procedure determination-
• Sales Org.+ DC+ Division +Document pricing procedure + Customer pricing procedure
• Pricing determination is carried out using the condition technique.
Requirements (2-Item with pricing, 55- free goods pricing, 59- Free goods)
• You need to determine “how the system should use the conditions type” by specifying the
requirements.
• You are able to make access dependent on requirements to avoid unnecessary access, this reduce the
system load.
Reference level (Subtotal)
• Provides a method to specify a different basis to calculate the condition type and to group condition
for subtotal.
• Pricing procedure can contain any number of subtotals.
Condition type
• Are combined in the require sequence in pricing procedure.
• Mark a condition type in the pricing procedure as being:
(cid:214) A mandatory condition-PR00
Abhishek Parihar
SAP SD Certified Consultant
E-Mail: abhishekparihar@rediffmail.com
第 27 页 / 共 33 页
SAP SD IMP NOTES
(cid:214) A manually condition-HM00, PN00
(cid:214) For statistical purpose only. -VPRS, SKTO
Pricing type
• You can configure the pricing behavior in the pricing type.
• Pricing types are: -
A. Copy pricing elements and update scale
B. Carry out new price
C. Copy manual pricing elements
G. Re-determined taxes
H. Re-determine freight
X, Y Reserved for customer
1-9 Reserved for customer
Tax determination
• The following factor play a role in tax determination
(cid:214) Business transaction- Domestic or export / import
(cid:214) Tax liability of ship to party
(cid:214) Tax liability of material
• You can assign a Rule, BLANK, A, B at the sales organization level to determine tax identification
number in the sales order and billing document.
Sales deal and promotion
• You can define a promotion or general marketing plan for a product line for a certain period of time.
You can then link this promotion with specific sales deals, which themselves linked to special
condition records. These condition records can be used for promotional pricing or discounts.
Rebate processing
Creating rebates agreement: -
• You may define rebates at as many levels as you require, similar to any pricing condition.
• The rebate agreement is created with a specific rebate agreement type. The feature of each
agreement type set in customizing (like condition table and its access sequence).
• Condition records are linked to the rebate agreement specifying the rebate rate and the accrual rate.
Processing rebates
• Rebates are different from other discounts in that they are based on the sales volume generated
by the customer within a specific period and are paid retrospectively.
• A settlement run creates the required credit memo request automatically.
• When the rebate- relevant billing documents are processed, accruals can be determined and posted to
financial accounting automatically, at the same time, the system updates the rebate basis and the
accrual amount on the rebate agreement sales volume screen.
• You can use the rebate credit memo to reverse these accruals. Accrual are cancelled automatically
when a credit memo is created.
• To function properly, rebate processing must be active for: -
Abhishek Parihar
SAP SD Certified Consultant
E-Mail: abhishekparihar@rediffmail.com
第 28 页 / 共 33 页
SAP SD IMP NOTES
(cid:214) Sales organization
(cid:214) The payer master
(cid:214) The billing document
Step rebate processing: -
(cid:206) Rebate processing begins by creating a rebate- relevant billing document.
(cid:206) The valid rebates condition type are determined by the pricing procedure using the rebate basis
subtotal.
(cid:206) Each rebate condition type has an assigned access sequence (set in customizing).
(cid:206) The system uses the access sequence to search for the valid rebate condition records. If valid
condition records are found, the accrual rate is read.
(cid:206) The accrual amount is calculated using the rebate basis.
(cid:206) The system posts an accrual to financial accounting and update accrual in rebate agreement same
time.
Retroactive rebate agreements
• Allow you to take into account billing documents created before the rebate agreement is created.
• The rebate basis for the billing documents created previously is accumulated and recorded in the
rebate agreement. The accrual amount is not automatically updated for billing documents created
previously. This amount must be entered manually.
Requirements
Requirement 24 - In the pricing procedure enforces that the rebate conditions are used only in billing
documents.
Requirement 25 – In the pricing procedure enforces that the rebate conditions are used only in rebate
relevant-billing documents.
BILLING
Billing overview
• A Billing document has two levels-Header and Item
• When you create a billing document in account, the R/3 system carries out a debit posting on the
customer receivables account and a credit posting on the revenue account.
• An important part of billing is the interface to financial accounting. This allows documents to be
creating automatically in financial accounting and controlling when you create billing documents.
• The data, which can be changed before an accounting document created: Billing date, pricing,
account determination, output determination. After posting accounting you can change only
output data.
• You might not want the data to be transferred automatically for certain billing types. In that case you
can set a posting block for the billing type concerned.
• Inter-company billing- a sales organization can also sell products supplied by a plant that is assigned
to a different company code.
Controlling the billing process
Abhishek Parihar
SAP SD Certified Consultant
E-Mail: abhishekparihar@rediffmail.com
第 29 页 / 共 33 页
SAP SD IMP NOTES
Billing type control
• The billing type controls the whole document.
• The billing types are used to cover the full range of business transactions during billing processing.
• In billing type if “Text Delivery” is switched off, the corresponding SD header/item texts are taken
from the order. If the switch is on then it is taken from outbound delivery.
• Having following control.
(cid:214) Cancellation billing type
(cid:214) Number assignment (Internal)
(cid:214) Partners
(cid:214) Rebate
(cid:214) Posting block
(cid:214) Account determination
(cid:214) Invoice list type
(cid:214) Special features of FI interface
(cid:214) Basic function (Text, Output)
• In customizing, for item category (sales doc.), you determine whether billing is to be carried out with
reference to a delivery or an order. The system propose a relevant billing type from the underlying
sales document type. For example, in delivery related billing, a standard order (Order type OR) is
invoiced using billing type F2.
Invoice combination and Invoice split
• It is possible to include both order related and delivery related items in the same billing document.
• If the header partner or data in the header field are not identical, the system will automatically perform
an invoice split.
Invoice list: -
• Each billing type to be included in an invoice list must assign an invoice list type.
• You also need to maintain the following master data:
1. Define a factory calendar, which specifies when invoice list are to be created.
2. Enter this factory calendar in the payer master record (Billing screen, invoice list schedule field).
3. Maintain condition record for condition type RL00 for the payer.
4. Create out put condition records for condition types LR00 and RD01.
Data flow and coping control
• You can automatically fill the reference number and allocation number fields in the accounting
document with numbers from SD documents. The reference number is in header of the accounting
document and is used for clearing. The allocation number is in the customer line item and is
used for sorting line numbers.
• In customizing for copy control in billing, you can define which numbered will be copied as reference
or allocations:
A. Purchase number
B. Sales order number
C. Delivery number
D. External delivery number
Abhishek Parihar
SAP SD Certified Consultant
E-Mail: abhishekparihar@rediffmail.com
第 30 页 / 共 33 页
SAP SD IMP NOTES
E. Billing document number
F. External delivery number if available, other wise delivery number.
• When the invoice list is created, the reference number from the invoice list overwrites the reference
number from the individual billing document.
• Copying requirement are ABAP routines. Before data is copied from the source document to target
document, specific requirements must be satisfied at each level of the document.
Special billing type
Billing type in complaint processing
Cancellation:
• You do not need to make an entry in coping control for billing cancellations.
• When you select cancellations, you branch to an overview screen containing the original billing
document as well as the cancellation. Before updating, you can compare both documents in order to
avoid any discrepancies during cancellation.
Credit and debit memos:
• You can create credit and debit memos either to credit or debit memo request (sales document), or, if
your company does not require a release procedure in case of complaints, directly with reference to a
billing document.
• We can also create credit and debit memo request without reference to a previous business transaction.
• You can control in customizing whether the system is to set a billing block automatically for a
credit or debit memo request.
• The responsible employee can:
(cid:214) Release the credit or debit memo request after review (by removing billing block). The
employee can decide the amount or quantity to be credited or debited.
(cid:214) Reject item in the credit or debit memo request and enter a reason for rejection.
Invoice correction request:
• The invoice correction request represents a combination of credit and debit memo request.
• The invoice correction request must be credited with reference to the corresponding billing document
(no reference to order or inquiry).
• The credit memo item cannot be changed. The corresponding debit memo item, however, can be
updated according to new characteristics (E.g. new pricing, change in quantity)
• You can delete the credit and debit memos in pairs (unchanged pairs of items can be deleted all at once
in this way).
Returns
• Returns are processed in the same way as credit memo request.
Pro forma invoice
• You can create with reference to order or deliveries
• This is generally used for export transaction
• Do not need PGI before creating delivery related Pro forma invoice.
Abhishek Parihar
SAP SD Certified Consultant
E-Mail: abhishekparihar@rediffmail.com
第 31 页 / 共 33 页
SAP SD IMP NOTES
• You can create as many pro forma invoices as required, since the billing status in the reference
document is not updated.
• Data from pro forma invoice is not transfer to accounting
Cash sale
• Order related billing, (BV) the order and delivery are created in one step, although you receive a
document for each other.
• The goods issue is posted at a later time as a separate transaction so the customer does not have to
wait.
• Order type CS is used for cash sales. It has its own output type RD03 which allows you to print an
invoice from the order.
• No output determination, as this has already been carried out in order.
• No new price determination, as the pricing should not differ from the printed invoice.
• Posting in financial accounting is made to a cash settlement account, not to the customer.
• Billing type SV is used for cancellations in cash sales.
Special business transactions
Billing plan-Periodic billing and Milestone Billing
• You can assign billing plan at header level {sales doc. Type} or at item level {sales item category with
billing relevance 1}
• Periodic Billing
(cid:214) Periodic billing is used to spread billing of full amount over several dates within billing plan.
Generally use in rental and in service contract.
• Milestone billing: -
(cid:214) In the SAP R/3 System, milestone is stored in a network along with planned and actual project
data.
(cid:214) Milestone are assigned to the billing plan dates and blocked for billing until the milestone is
confirmed as completed.
(cid:214) The date proposal is used exclusively for milestone billing. It determines a sequence of dates
that are used as the reference for date determination during order processing.
Down payment processing in SD
• Down payments are already created in the sales order. “ At the corresponding due date, a down
payment request (Billing Document) is sent to customer.”
• The down payment agreement can be assigned directly to an item, or it can be defined as valid for all
items in the order.
• As soon as billing date for down payment has been reached the system created a down payment
invoice and sent it to the customer.
• Tax is determined and displayed automatically when the down payment request is created.
• The down payment request (SD) is automatically posted in financial accounting as a down
payment request (Posted as a noted item). The item ha special general ledger (G/L) indicator F,
which insures that posting, is statistical. Posting is made to a different reconciliation account,
Abhishek Parihar
SAP SD Certified Consultant
E-Mail: abhishekparihar@rediffmail.com
第 32 页 / 共 33 页
SAP SD IMP NOTES
which allows you to differentiate down payment requests from other receivables. Billing type FAZ is
used for creating the down payment request.
Installment Payments
• Installment plans allow the customer to pay in installments. Only one billing document is created for
all of the installment payments. The printed invoice is created on the basis of this billing document and
includes a list of individual payment dates and exact amounts. Each installment payment creates an
accounts receivable line posting in FI.
• You must define installment payment terms in customizing (number and amount of the installment
in percentage and payment terms).
Account determination
• Account determination is carried out using the condition technique.
• The slandered account determination procedure is KOFI00, which has the standard condition types as
KOFI and KOFK.
• Criteria for account determination-
(cid:214) Chart of account
(cid:214) Sales organization
(cid:214) Account assignment group for payer
(Customer in to different group, such as domestic and overseas.)
(cid:214) Account assignment group for materials
(cid:214) Account key
(Account keys are assigned to condition types in the pricing procedure, so that conditions such as
freight condition, can be posted to special freight revenue accounts)
SD/FI interface
• Sales organization to company code assignment
• Account determination
• Copy control.
Condition technique is used for
(cid:214) Pricing
(cid:214) Account determination
(cid:214) Material determination
(cid:214) Listing
(cid:214) Exclusion
(cid:214) Free goods determination
(cid:214) Tax determination
(cid:214) Text determination
(cid:214) Output determination
TAB PAGES FOE BILLING DOCUMENT
Abhishek Parihar
SAP SD Certified Consultant
E-Mail: abhishekparihar@rediffmail.com
第 33 页 / 共 33 页
SAP SD IMP NOTES
Header - Header, Header Partner, Conditions, Foreign Trade/customs, Head text, Global trade.
Item – Item detail, Item, Partner, Conditions, Foreign Trade/ customs, Item text, PO date, global
trade.
Abhishek Parihar
SAP SD Certified Consultant
E-Mail: abhishekparihar@rediffmail.com