Function documentation Valuations in Procurement and Sales Locate the document in its SAP Library structure

Use

To use transfer prices, you must transfer values using multiple valuation approaches between the individual companies in your organization.

It is usually not desirable to have to edit or even create multiple valuation approaches by hand. Consequently, the system uses automatic data interfaces to ensure that parallel values are transferred for all purchasing and sales transactions. The following section describes what settings you need to make to set up these parallel value flows.

Integration

A typical example would be the following process:

1.       A stock transport order is entered in group company A.

2.       From this stock transport order, group company B creates a delivery and a goods issue posting. No sales order is created for this transaction.

3.       When group company B writes the subsequent outgoing invoice to the purchasing company, the values for this invoice are automatically transferred using the IDOC interface. This transfer includes the legal valuation approach as well as the group and profit center approaches.

4.       After posting the goods receipt, group company A posts the invoice receipt, which copies the legal, group, and profit center values from this interface.

Features

In order to ensure that all value flows are updated automatically and consistently throughout the system, the following documents need to be transferred automatically between company codes in the group:

·         Purchase order - transferred to company code B (seller) when the stock transport order is created.

·         Outgoing invoice - transferred to invoice verification in company code A.

You need to use the IDOC interface and thus also the ALE functions. This is also the case when both company codes are in the same system. Consequently, you have to carry out the following steps to set up the transfer of multiple valuation methods:

·         Initial Steps in SD

·         Setup of the ALE Functions

·         Settings for the Data Transfer to Invoice Verification

Initial Steps in SD

Prerequisite for transferring parallel values between company codes is that you include the necessary conditions (group value or profit center value) in your pricing procedure. You can use the standard SD pricing procedure RVAA01 as a model.

When choosing the condition types, observe the following:

·         The condition types for transferring group values must belong to condition category b.

·         The condition types for transferring profit center values must belong to condition category c.

·         Both condition types must be defined as statistical in the price determination schema. The print flag must also be set for both of them.

Setup of the ALE Functions

To transfer the values automatically to the purchasing company code, you need to define the same settings you normally define in Customizing for ALE (see ALE - Consultant's Guide).

Settings for the Data Transfer to Invoice Verification

Prerequisite for posting the invoice in the purchasing company code is that the purchase order number and the purchase order item be transferred as reference information.

In addition, you can predefine the document types and program parameters in Customizing under Materials Management ® Invoice Verification ® Conventional Invoice Verification ® EDI. Typically, the keys and the value-added-tax indicator and the company code are converted for this transfer.

Once you have made these settings, every incoming invoice from a vendor that is defined as an affiliated company in its master record (VBUND indicator) will be posted using parallel valuation methods.

 

 

Leaving content frame