1365939_E_20230317 VPRS logic and Customizing settings in SD
目录
- The priority of the possible sources is as follows
- Special characteristics of the condition VPRS
- Various processes
- Order-related billing
- Delivery-related billing
- Third-party business transaction
- Customizing in the third-party business transaction
- Customizing for make-to-order production
- General Customizing settings
- Pricing procedure configuration
- condition checks
- Transfer prices
2023-03-17 1365939
1365939 - VPRS logic and Customizing settings in SD
Version 6 Type SAP Note
Language English Master Language German
Priority Recommendations / Additional Info Category Consulting
Release Status Released for Customer Released On 22.11.2013
Component SD-BIL-IV ( Processing Billing Documents )
Please find the original document at https://launchpad.support.sap.com/#/notes/ 1365939
Symptom
In addition to the automatic condition types whose value is determined using
access sequences and condition records, there are specific condition types whose
value is calculated by the system. In particular, this includes the cost that is
contained in the standard SAP system as condition type VPRS.
The values for VPRS are determined from the valuation segment of the material
master, from the document flow, or from the purchase order history (third-party
business transaction).
Useful note:372772
The priority of the possible sources is as follows
• Invoice receipt
• Goods receipt (valuated)
• Purchase order
• Goods issue
• Valuation segment in the material master.
The first three sources are essential for a pure third-party business
transaction and for individual purchase orders; the last two are for delivery-
related billing and order-related billing.
Useful notes: 117714, 337542, 792547
Special characteristics of the condition VPRS
• The condition type VPRS has the condition category 'G' and should only be
available once in the pricing procedure.
• VPRS should not be used as a basis for further pricing.
• The currency transaction of the condition category (KNTYP) 'G' is subject to
special rules in pricing. Conditions with the KNTYP 'G' are translated with
the exchange rate type 'M' independently of the value that was stored in the
customer master.
• 'B' (value transfer to KOMP-WAVWR) must be assigned to VPRS as the condition
subtotal; otherwise, the cost cannot be determined.
© 2023 SAP SE or an SAP affiliate company. All rights reserved 1 of 5
2023-03-17 1365939
Useful notes: 15462, 24832, 185225
• VPRS can also be flagged as relevant for accruals.
As a result, document lines are also formed in the accounting document for
VPRS when a billing document is transferred to accounting. A relevant
account determination that determines the corresponding accounts and stores
them for accounting document creation is a prerequisite. You can see the
accounts on the detail screen of the (item) condition in the "Account
determination" section. In addition, for this process, the VPRS must be
transferred from goods issue, because only then can the billing document
adopt the value in local currency (KWERT_K) directly from the goods issue
posting and transfer this to accounting. You can determine the origin of the
cost condition from field KONV-KSTEU. Also see SAP Note 547570.
Useful notes: 795068, 611094
Various processes
Order-related billing
Creating the billing document with reference to the sales order.
The source of the cost is the valuation price of the material master (order).
Delivery-related billing
Creating the billing document with reference to the delivery note.
The source of the cost is the goods issue.
If batches or bills of material (BOMs) exist, a cumulation of the subitems in
the main item can be triggered with the relevant Customizing settings.
Transferring VPRS from the subitem when
• the subitem is not relevant for billing
• VPRS should not be determined for the subitem category
• VPRS should not be determined for the main item category.
Useful notes: 352441, 373661, 65908, 70038, 77414
Function module CUMULATE_SUBITEM_VALUES
Third-party business transaction
A material required by the customer cannot be delivered itself by the company.
Therefore, the order is forwarded to an external vendor who sends the goods to
the customer directly and invoices the company.
The third-party order processing is implemented in the SD and MM modules
and the following scenario is represented in the standard system.
• You enter a third-party item (TAS) in a sales order (TA). The schedule line
category CS (third-party) is transferred to the document via the order
category and the item category.
• The item category TAS is created either automatically and then entered
in the item category group of the material 'BANS' or it can be changed
by the user if you want a normal item (TAN) to be processed via a
third-party business transaction. This is an exception.
• The scheduling line category CS ensures that a purchase requisition is
created for the third-party order item in the MM module.
© 2023 SAP SE or an SAP affiliate company. All rights reserved 2 of 5
2023-03-17 1365939
• This is then converted into a purchase order in purchasing.
• The ordered goods are delivered directly to the customer by the vendor. A
goods receipt posting for this purchase order is not required. However, to
document this step in the system, a statistical goods receipt can be posted
in inventory management.
• The subsequent incoming invoice of the vendor is updated with reference to
the purchase order (transaction MIRO in the MM module). Depending on the
settings in Customizing, it forms the basis for the later customer billing
document.
• In SD the billing document for the sales order is created and it depends on
the Customizing settings whether billing occurs on the basis of the order
quantity or on the basis of the invoice receipt quantity. If billing occurs
on the basis of the order quantity, the billing document can be created
immediately after the creation of the sales order. If billing occurs on the
basis of the invoice receipt quantity, the billing document cannot be
created until the vendor invoice has been entered in the invoice receipt
check. In this case, the billing index is set up in SD during the update of
the vendor invoice.
• A vendor invoice may also be posted after the customer billing document. In
this case, the invoice receipt in SD triggers an update of the costs in the
existing customer billing document (function module SD_INVOICE_VPRS_UPDATE).
Note that the system cannot recognize whether a third-party business
transaction is completed and no further incoming invoices are to follow in
SD. Problems occur, for example, if the quantities in MM and in SD do not
correspond. The special correction program SDVPRSUPDATE was created for this
(Note 371844).
• Process
• Incoming invoice is posted in MM (MIRO)
• Costs are channeled to SD
• If no further SD billing documents are expected, all the affected
billing documents must be updated; to do this,
• transfer the costs of the current incoming invoice and all
• existing incoming invoices (quantities and costs)
• distribute the total costs to existing billing documents (scaling)
• statistics update and posting the difference in CO-PA.
• For credit memos in the third-party business transaction, there is no VPRS
because a credit memo does not reduce the cost.
The standard condition 28 sets the VPRS to zero (0.01). VPRS is also never
updated.
Useful notes: 322497, 371844, 372760, 745172
Make-to-order production
In contrast to the pure third-party business transaction, billing occurs here on
the basis of a delivery note. VPRS is not taken from
the goods issue.
If you want to update teh VPRS after a later invoice receipt, the report
SDVPRSUPDATE can be used to correct costs.
© 2023 SAP SE or an SAP affiliate company. All rights reserved 3 of 5
2023-03-17 1365939
As of Release 605, the report SDVPRSUPDATE is no longer required for the
process. Now, the posting of an invoice receipt (transaction MIRO) triggers the
automatic correction of the costs in the SD billing document.
The make-to-order production item in the item category 'TAB' is known.
Useful notes: 93153
Customizing in the third-party business transaction
In the pure third-party business transaction, order-related billing is always
available.
• Item category: TAS
• Billing relevance (FKREL) 'F'
• Copying control: Order -> Customer billing document
• Billing quantity indicator (FKMGK) = E/F
Customizing for make-to-order production
During make-to-order production, a delivery-related process is always available.
• Item category: TAB
• Billing relevance (FKREL) = 'A'
• Copying control: Delivery note -> Customer billing document
• Billing quantity indicator (FKMGK) = E/F
General Customizing settings
Pricing procedure configuration
The condition type VPRS is created as a statistical condition in the pricing
procedure.
Condition 4 should be assigned in the VPRS line in the pricing procedure. This
condition checks
• Whether the company code is the same as the selling company code
• Whether the plant is filled
• Whether the item category is relevant for determining the cost
• That the item is not relevant for down payment clearings.
The condition values should be stored temporarily in the condition subtotal
field 'B'.
Transfer prices
Transfer prices run parallel to VPRS.
The are dealt with in the same way during the goods issue and passed on to
pricing (form routine TRANSFER_PRICE in the includes LV60AA19, LV60AA28, and
LV60AA90).
Other Terms
VPRS, third-party, make-to-order production, Customizing
© 2023 SAP SE or an SAP affiliate company. All rights reserved 4 of 5
...
