Beruflich Dokumente
Kultur Dokumente
n R/3 System
n Release IS-OIL 4.6C
n Collection 21
n January 2002
n Material number: 50050262
SAP AG 2001
Trademarks:
n Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
n Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered
trademarks of Microsoft Corporation.
n IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®,
AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.
n ORACLE® is a registered trademark of ORACLE Corporation.
n INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of
Informix Software Incorporated.
n UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
n HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide
Web Consortium, Massachusetts Institute of Technology.
n JAVA® is a registered trademark of Sun Microsystems, Inc.
n JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.
n SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow,
SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com
are trademarks or registered trademarks of SAP AG in Germany and in several other countries all
over the world. All other products mentioned are trademarks or registered trademarks of their
respective companies.
Level 2 Level 3
LO510 3 days
Inventory
Management
IOG350 3 days
Service Station
Retailing
SAP AG 2001
l Essential:
n IOG 150 – Oil&Gas Supply Chain
n Good Knowledge of Sales and Purchasing
l Recommended:
n Oil&Gas Business Knowledge
n LO510 – Inventory Management
n LO515 – Invoice Verification
n LO620 – Pricing
SAP AG 2001
l Audience:
n Project team members and leaders responsible for
implementing basic functions in the Exchange Module
l Duration: 2 days
SAP AG 2001
Contents:
l Goals
l Objectives
l Content
l Overview Diagram
SAP AG 2001
SAP AG 2001
SAP AG 2001
Preface
Any exercises and solutions are at the end of the respective unit
SAP AG 2001
Unit 01
Course
Course overview
overview
Business
Business
Conclusion
Conclusion
background
background
Exchange
Exchange agreement
agreement
Other
Other features
features
setup
setup
Exchange
Exchange reports
reports Daily
Daily business
business flow
flow
Split
Split condition
condition
Logical
Logical inventory
inventory
processing
processing
Sub/base
Sub/base
Settlement
Settlement
relationship
relationship
Purchase
Purchase assignment
assignment
SAP AG 2001
Contents:
l Discussion of business reasons for exchange
SAP AG 2001
SAP AG 2001
Course
Course overview
overview
Unit 02
Business
Business
Conclusion
Conclusion
background
background
Exchange
Exchange agreement
agreement
Other
Other features
features
setup
setup
Exchange
Exchange reports
reports Daily
Daily business
business flow
flow
Split
Split condition
condition
Logical
Logical inventory
inventory
processing
processing
Sub/base
Sub/base
Settlement
Settlement
relationship
relationship
Purchase
Purchase assignment
assignment
SAP AG 2001
SAP AG 2001
Co. 1 Co. 2
SAP AG 2001
n In the above illustration, company 1 operates in one region of the country. They are able to produce
the product and easily transport it to their customers in that region.
n Company 2 also markets in the same region as company 1. High transportation costs or restricted
access to transportation (e.g. limited pipeline allocation) are good reasons for company 2 to enter
into an exchange agreement with company1.
n A company may have excess capacity. Not only are they unable to meet the market demands of their
own customers, but also the needs of the exchange partner.
SAP AG 2001
Contents:
SAP AG 2001
SAP AG 2001
CourseOverview
CourseOverview
Business
Business
Conclusion
Conclusion
Background
Background
Unit 03
Exchange
Exchange
Other
Other Features
Features
Agreement
Agreement Setup
Setup
Exchange
Exchange Reports
Reports Daily
Daily Business
Business Flow
Flow
Split
Split Condition
Condition
Logical
Logical Inventory
Inventory
Processing
Processing
Sub/Base
Sub/Base
Settlement
Settlement
Relationship
Relationship
Purchase
Purchase Assignment
Assignment
SAP AG 2001
Exchange
Exchange Agreement
Agreement Header
Header
Receipts
Receipts Deliveries
Deliveries
Balance
Settlement
Settlement
SAP AG 2001
n The basic business process flow for exchange process is shown on this slide:
The exchange agreement header is where the exchange partner is identified and where certain
controls about the exchange type are defined. Sales and purchase contracts are assigned to the
exchange agreement header and define the particulars about which products are exchanged and
which fees apply to each product movement.
Exchange receipts and exchange deliveries represent actual product movements against the
exchange. Exchange receipts are recorded in the Materials Management (MM) module. Exchange
receipts are recorded in the Sales & Distribution (SD) module.
In a borrow/loan exchange, the system tracks the balance of product owed or owing against the
exchange.
Finally, settlement represents the process of paying for fees, taxes and/or product on a periodic
basis, usually monthly.
Exchange
Purchase contracts Agreement Sales contracts
Receipts
Receipts Deliveries
Deliveries
Balance
Settlement
Settlement
SAP AG 2001
n The standard system has been enhanced to provide exchange functionality. The MM module has
been enhanced to record exchange receipts, while the SD module has been enhanced to record
exchange deliveries.
n The MM module utilizes a vendor master record and the SD module utilizes a customer master
record. For exchange purposes, the vendor and customer are the same exchange partner. Therefore,
the vendor master record is cross referenced with the customer master record. And the customer
master record is cross referenced with the vendor master record.
n This link is a one-time set-up and is required for exchange functionality to work.
Control
Control data
data
Administrative
Administrative data
data
Exchange
Exchange header
header
Posting
Posting rules
rules
Sales Fees
Fees
contract
Purchase Quantity
contract Quantity schedule
schedule
Item
Item
Materials
Materials
SAP AG 2001
n The exchange header data is made up of general information for each exchange agreement as well as
the corresponding detailed information.
n You have to choose if you want to use an evergreen type (it determines how quantities are handled in
contracts, e.g.the quantity that you can call off in total, the quantity that you can call off per period,
or unlimited).
n You choose internal or external posting rules: With internal postings and material, taxes and/or fees
are posted to internal accounts. With external posting and material, any taxes and/or fees are charged
to the exchange partner.
n You also enter control data such us sub/base-, quantity schedule- and netting indicators.
l A quantity per
period is defined -
quantity schedule
must be used
SAP AG 2001
n Evergreen is a long term exchange contract without a fixed end date. The agreement is ongoing and
gets renegotiated on a regular basis. The partners then decide if the evergreen is valid for another
period or if the evergreen is closed.
n We distinguish between unlimited and regular evergreens. With unlimited evergreen, there is no
quantity defined. The exchange partners can lift as much product as they require and for any period
of time. Therefore no quantity schedule is used in that case.
n It differs from a regular evergreen because for regular evergreens, a quantity schedule is used to
define the quantity of the product for exchange.
Start date
Copy into sales &
January February
purchase contracts March April
MT WT F S S MT WT F S S MT WT F S S MT WT F S S
Closing date
May June • Copy into contracts
July August
MT WT F S S MT WT F S S •
M T W T FNo
S further
S M call-offs
T WT F S S
Review date • Further movements
Mandatory for regular
end date quantity
schedule
September October November December
MT WT F S S MT WT F S S MT WT F S S MT WT F S S
SAP AG 2001
For both the regular and the unlimited evergreen, you can specify:
n A start date. This marks the start date of the agreement and is copied into the related sales and
purchase contracts.
n A review date. For regular evergreens, this date is copied into the quantity schedules of the related
sales and purchase contracts. Whenever this date is changed, the related quantity schedules are
adjusted automatically.
n A closing date. When filled, this date is copied into the related sales and purchase contracts and
prevents any call-offs or movements being posted under this agreement.
n While the start date is mandatory for both evergreen types, the review date is only required for the
regular evergreens. The closing date is optional.
Period n 1000 L
Quantity
per period
SAP AG 2001
SAP AG 2001
SAP AG 2001
Unit: Exchanges
Topic: Exchange Agreement Setup
3-1-2 Create an exchange agreement (the “regular evergreen type”) with your
partner.
Exchange type: Borrow/Loan regular
Exchange partner no.: VEND02-##
Exchange number: [ ] (internal number range)
Partner reference: []
Unit: Exchanges
Topic: Exchange Agreement Set-up
Contents:
l Exchange deliveries
l Exchange receipts
SAP AG 2001
SAP AG 2001
Course
Course overview
overview
Business
Business
Conclusion
Conclusion
background
background
Exchange
Exchange
Other
Other features
features
agreement
agreement setup
setup
Unit 04
Daily
Daily business
business
Exchange
Exchange reports
reports
flow
flow
Split
Split condition
condition
Logical
Logical inventory
inventory
processing
processing
Sub/base
Sub/base
Settlement
Settlement
relationship
relationship
Purchase
Purchase assignment
assignment
SAP AG 2001
Exchange
Exchange Agreement
Agreement Header
Header
Receipts
Receipts Deliveries
Deliveries
Balance
Settlement
Settlement
SAP AG 2001
n Exchange deliveries are processed within the sales and distribution (SD) module.
n Exchange deliveries are the movement of product from your own inventory to an exchange partner
or an exchange partner’s customer.
Copy/recalculation of
Contract fees
Update of quantities in
QS in contract/call-off
Call-off
Update exchange
balance
Delivery Post accounting
doc.
Goods
issue
Invoice
SAP AG 2001
n You assign sales contracts to the exchange agreement, allowing management of exchange deliveries.
n The customer (exchange partner) fulfills the contract by placing orders from this contract (call-offs
or release orders). When you create a call-off, you make a reference to the corresponding contract
and the system automatically updates the called-off quantity in the contract.
n The breakdown period is to be copied from the quantity schedule to the contract call-off, depending
on the delivery data entered. Fees for the individual items are also copied from the contract to the
call-off.
n A delivery is carried out with reference to a call-off and is thus also linked to the exchange
agreement. The goods issue has to be posted.
n Depending on the type of outline agreement (thus depending on the exchange type) the exchange
partner is only charged for fees and taxes. If netting is provided in the exchange agreement, the
invoice is blocked and offset in subsequent netting.
n The illustration above shows the flow of documents in the R/3 System and indicates the points in the
process where the quantity schedule is updated, fees are repriced, exchange balance updated and
accounting documents recorded.
Purchase contract
Exchange
Exchange Sales contract
Agreement
Agreement
General
General ledger:
ledger: Delivery
Sales call-off
SAP AG 2001
n Accounting documents are recorded automatically at goods movement. Therefore for exchange
deliveries, an accounting document is reported at goods issue, which is then posted to inventory
accounts.
n Since physical inventory is being reduced, it is credited. In a buy/sell exchange, the value of the
product is settled in cash, therefore the offsetting entry is posted to cost of goods sold.
Purchase contract
Exchange
Exchange Sales contract
Agreement
Agreement
General
General ledger:
ledger: Delivery
Sales call-off
Borrow/loan agreement: Delivery
Credit: PHYSICAL INVENTORY ( - ) Goods issue
Debit: LOGICAL INVENTORY (+)
Billing
SAP AG 2001
n Accounting documents are recorded automatically at goods movement. Therefore for exchange
deliveries, an accounting document is recorded at goods issue, which is then posted to inventory
accounts.
n Since physical inventory is being reduced, it is credited. In a borrow/loan exchange, the value of the
product is not settled in cash, therefore the offsetting entry is posted to logical inventory.
Purchase contract
Exchange
Exchange Sales contract
Agreement
Agreement
General
General ledger:
ledger: Delivery
Sales call-off
Buy/sell agreement: Delivery
Credit: REVENUE- Product (-)
Goods issue
Credit: REVENUE- Fees (-)
Billing
Debit: CUSTOMER (+)
SAP AG 2001
n The billing document creates the first accounting entry and records fees and excise taxes. Tax entries
are not shown in the above illustration for simplicity.
n Revenue for product, fees and/or excise taxes are recorded. A corresponding receivable is established
on the exchange customer account number.
Purchase contract
Exchange
Exchange Sales contract
Agreement
Agreement
General
General Ledger:
Ledger: Delivery
Sales call-off
Borrow/Loan agreement:
Delivery
Credit: REVENUE - Fees (-) Goods Issue
Debit: CUSTOMER (+)
Billing
SAP AG 2001
n The accounting entry for a borrow/loan exchange does not include an entry for product value. The
product value is not settled monthly on a borrow/loan exchange. Instead, the product volume and
value is recorded to logical inventory and will be settled at the end of the exchange.
Exchange
Exchange agreement
agreement header
header
Receipts
Receipts Deliveries
Deliveries
Balance
Settlement
Settlement
SAP AG 2001
n Exchange receipts are processed within the materials management (MM) module.
n Exchange receipts are the movement of a productfrom your exchange partner into your own
inventory or that of your customer.
Invoice
verification
SAP AG 2001
n You assign purchase contracts to the exchange agreement, allowing management of exchange
receipts. Call-offs are created with reference to the purchase contract. Some of the data from the
exchange header is copied into the call-off (e.g. number of the exchange agreement, netting-blocking
indicator etc.). As with the purchase contract, this data is displayed on the detail screen for each item.
n There is a quantity schedule for each item; the breakdown is copied from the purchase contract. The
breakdown period in the quantity schedule is based on the delivery date. The fees for the individual
items are also copied from the purchase contract to the call-off..
n When a goods receipt is posted, the system creates a material document and an accounting
document. In the material document, which serves as proof of a goods movement, specific data from
the exchange agreement is copied into the purchase order. Parallel to the material document, the
system creates an accounting document which contains the accruals from the fee postings, among
other things.
n Invoice verification is carried out during invoice receipt on the basis of the data previously created
during the goods receipt. During verification of a goods receipt-related invoice, each single goods
receipt is settled individually. However, open items which still have to be settled may also be
selected with reference to an exchange agreement.
n You can settle goods receipts with ERS (Evaluated Receipt Settlement) within exchange agreements
directly, without having first received an invoice. The evaluated receipt settlement automatically
creates invoice verification documents according to previously-set criteria.
Purchase contract
Exchange
Exchange Sales contract
Agreement
Agreement
General
General ledger:
ledger:
Receipt
Purchase call-off
Buy/sell agreement:
Goods receipt Credit: GR/IR - Product (-)
Debit : PHYSICAL INVENTORY ( + )
Invoice verification Credit: GR/IR - Fees (-)
Debit: EXCHANGE FEES (+)
SAP AG 2001
n An exchange receipt increases your physical stock. The accounting entry is therefore a debit to
physical inventory and a credit to the GR/IR (goods receipt/invoice receipt) account.
n At goods movement, an accounting entry is also made for fees. Remember that fees for exchange
deliveries are posted at billing.
Purchase contract
Exchange
Exchange Sales contract
Agreement
Agreement
General
General ledger:
ledger:
Receipt
Purchase call-off
Borrow/loan agreement:
Goods receipt Credit: LOGICAL INVENTORY ( - )
Debit: PHYSICAL INVENTORY ( + )
Invoice verification Credit: GR/IR - Fees (-)
Debit: EXCHANGE FEES (+)
SAP AG 2001
n In the case of a borrow/loan exchange, the offsetting entry to physical inventory is a posting to
logical inventory. This is because in a borrow/loan exchange, the balance of product owed or owing
is recorded to logical inventory.
Purchase contract
Exchange
Exchange Sales contract
Agreement
Agreement
Receipt General
General ledger:
ledger:
Purchase call-off
Goods receipt
Buy/sell agreement:
SAP AG 2001
n As you can see, the GR/IR (goods receipt/invoice receipt) accounts will clear to zero. They are
simply clearing accounts used to carry the value of fees or product to the invoice verification step.
n The offsetting entry is an accounts payable entry made to the exchange vendor.
Purchase contract
Exchange
Exchange Sales contract
Agreement
Agreement
Receipt General
General ledger:
ledger:
Purchase call-off
Goods receipt
Borrow/loan agreement:
Credit: VENDOR (-)
Invoice verification
Debit: GR/IR Account (+)
SAP AG 2001
n In the case of the borrow/loan exchange, there is no entry for the product value. Again, this is the
case because the value of the product was charged to logical inventory at goods receipt, and not to
the GR/IR account.
SAP AG 2001
SAP AG 2001
Unit: Exchanges
Topic: Business Flow – Receipts & Deliveries
4-3 Due to the fact that the handling condition has changed for your material, it is now
necessary to adjust the valid handling fee rates.
4-3-1 Adjust the sales fee rate for your exchange partner.
Condition type: HAND
Material: REGULAR-##
Plant AP01
Fee rate: 0,12 USD / GAL
4-3-2 Adjust the purchase fee rate for your exchange partner.
Condition type: HAND
Vendor: VEND02-##
Material: REGULAR-##
Fee rate: 0,12 USD / GAL
Unit: Exchanges
Topic: Business Flow – Receipts & Deliveries
Contents:
SAP AG 2001
SAP AG 2001
Course
Course overview
overview
Business
Business
Conclusion
Conclusion
background
background
Exchange
Exchange
Other
Other features
features
agreement
agreement setup
setup
Daily
Daily business
business
Exchange
Exchange reports
reports
flow
flow
Unit 05
Split
Split condition
condition
Logical
Logical inventory
inventory
processing
processing
Sub/base
Sub/base
Settlement
Settlement
relationship
relationship
Purchase
Purchase assignment
assignment
SAP AG 2001
Receipts
Deliveries
Balance
Balance of
of material
material quantities
quantities
owed
owed / owing against a borrow // loan
/ owing against a borrow loan exchange
exchange
SAP AG 2001
n When exchange balances are built up against "pure" exchanges, for financial accounting purposes, it
is usual to value the assets and liabilities associated with the goods movements, as if they were actual
inventory. The reasoning behind this is that the payable or receivable in the case of pure exchanges is
a quantity of product and not a financial amount.
n The system records and tracks the value of the inventory at the prevailing inventory carrying price
when the material movement was created.
n If no own inventory is carried at a location, the receivable and payable volumes can be valued at the
current value at a "reference plant".
Volumetric balance:
Volumetric balance:
Exchange balance
Exchange balance table
table S036
S036
Financial balance:
Financial balance:
Material internal
Material internal payable
payable // receivable
receivable accounts
accounts
Valuation strategy:
Valuation strategy:
Logical inventory
Logical inventory valuation
valuation segment
segment OIA07
OIA07
SAP AG 2001
n The logical inventory reflects the receipts and deliveries that are posted under a borrow and loan
exchange agreement.
n In the system, the logical inventory is represented by:
the volumetric balance, which is stored in the exchange balance table S036
the financial balance, stored in the material internal payable and receivable accounts
n A moving average price for the exchange balance is maintained in table OIA07 and is used to derive
the gain/loss posting when logical inventory is revalued.
Exchange
Exchange Agreement
Agreement Header
Header
Receipts Deliveries
Receipt D Delivery
R
adjustment adjustment
Balance
Negotiated Negotiated
payment:
payable $ payment:
receivable $
Settlement
Settlement
SAP AG 2001
1 Receipt Delivery
BEFORE
11,000 L15 10,000 L15
Delivery
adjustment
1,000 L15
Receipt Delivery
2 AFTER
AFTER 11,000 L15 11,000 L15
SAP AG 2001
n The logical inventory adjustment transaction allows the oil company to adjust the logical inventory
that they have recorded against an exchange partner.
n It is possible to settle the difference (imbalance) between delivered and received material, by means
of a payment. Open quantities can also be moved to another exchange agreement, which results in
items in the first exchange agreement being settled before the exchange agreement can then be
concluded.
n No physical movement is involved, only a logical inventory movement.
n The LIA transaction allows the oil company to record the change of ownership of a specified
quantity of one product to the ownership of a specified quantity of another product. Note that it does
not necessarily have to be a different product.
n When the LIA logical inventory accounts are updated, so too is the exchange balance.
Purchase contract
Exchange
Exchange Sales contract
Agreement
Agreement
General
General ledger:
ledger:
SAP AG 2001
n As you can see, a delivery adjustment does NOT affect physical inventory.
n Delivery/Receipt adjustments should NOT be used to record an actual product movement.
Purchase contract
Exchange
Exchange Sales contract
Agreement
Agreement
General
General ledger:
ledger:
SAP AG 2001
n As you can see, a receipt adjustment does NOT affect physical inventory.
n Delivery/Receipt adjustments should NOT be used to record an actual product movement.
Purchase contract
Exchange
Exchange Sales contract
Agreement
Agreement
Credit: vendor
Debit: exg bal acct.
Payable Receivable
Debit: customer
Credit: exg bal acct.
SAP AG 2001
SAP AG 2001
SAP AG 2001
5-1 Use R/3 reporting tools to examine what happened within your exchange agreement
so far, and adjust the balance.
5-1-1 What does logical inventory mean?
____________________________________________________________
____________________________________________________________
____________________________________________________________
5-1-2 Display the exchange balance report in order to check lifts and receipts and
the resulting exchange balance.
Application: 03 (Inventory controlling)
Evaluation structure: ZFEXCHBL (Exchange balance)
Evaluation: EXGB (Exchange balance report)
Exchange no.: (From 3-1-3)
Make a note of the exchange balance (lift – receipts) for the “Regular”
material:
____________________________________________________________
5-1-3 What options do you have for settling the imbalance between delivered
material and received material?
____________________________________________________________
____________________________________________________________
Contents:
l Movements based netting
l Exchange statement summary
l Exchange statement detail
SAP AG 2001
SAP AG 2001
Course
Course overview
overview
Business
Business
Conclusion
Conclusion
background
background
Exchange
Exchange
Other
Other features
features
agreement
agreement setup
setup
Daily
Daily business
business
Exchange
Exchange reports
reports
flow
flow
Split
Split condition
condition
Logical
Logical inventory
inventory
processing
processing
Sub/base
Sub/base Unit 06
Settlement
Settlement
relationship
relationship
Purchase
Purchase assignment
assignment
SAP AG 2001
Exchange
Exchange Agreement
Agreement Header
Header
Receipts
Receipts Deliveries
Deliveries
Balance
Settlement:
• Netting
• Exchange statement
• Reconciliation
SAP AG 2001
Movements
Financial
database Netting database
selection
Summary Detail
report report
Clear
Clear
Netting Netting Payables
Payables
Document Receivable
BTCI Receivable
SAP AG 2001
n Movement based netting collects receivables and payables in an exchange and offsets them against
each other.
n Goods movements which reference the exchange agreement are used as the selection method for
choosing the documents.
n The system calculates the netting balance as a sum of the receivables and payables. You either bill
the balance to your exchange partner, or your company pays the amount.
n You can create a statement (printout) for the movement based netting document, and you can send it
to your exchange partner. Your exchange partner can then check the statement. If your exchange
partner reports any changes to you, you can still change the movement based netting document, as
long as you have not created a batch-input session. When the batch-input session is run, the accounts
are cleared and difference postings are carried out.
n For the printout it is necessary to maintain an address for your sales organization.
SAP AG 2001
SAP AG 2001
SAP AG 2001
SAP AG 2001
Unit: Exchanges
Topic: Settlement
AOIL does not invoice its exchange partner after each individual
movement, but settles the exchange agreement periodically. AOIL wants
to offset the receivables and payables collected in the exchange
agreements against each other.
AOIL can create a netting statement (printout) for the movements-based
netting document, and can send it to its exchange partner. AOIL' s
exchange partner can then check the statement. If its exchange partner
reports any changes to AOIL, the movements-based netting document can
still be changed, as long as AOIL has not created a batch-input session.
When the batch-input session is run, the accounts are cleared and
difference postings are carried out.
6-1 Create a movements-based netting document, examine the netting proposal and
check the output on the screen.
6-1-1 Create the netting document:
Exchange partner number: VEND02-##
Netting document type: OINF (Movm.Netting - Fees)
Sales area: AESO/A1/A1
Currency: USD
From month: (01, current year)
To month: (Current month, current year)
Select Netting proposal, and examine all the items.
Go back to the selection criteria screen and save the netting document
(choose Save and Create BTCI), and make a note of the document number
and the batch input session.
____________________________________________________________
Unit: Exchanges
Topic: Settlement
Contents:
l Purchase assignment overview
l Price reference plant overview
l Configuration
SAP AG 2001
SAP AG 2001
Course
Course overview
overview
Business
Business
Conclusion
Conclusion
background
background
Exchange
Exchange
Other
Other features
features
agreement
agreement setup
setup
Daily
Daily business
business
Exchange
Exchange reports
reports
flow
flow
Split
Split condition
condition
Logical
Logical inventory
inventory
processing
processing
Sub/base
Sub/base
Settlement
Settlement
relationship
relationship
Unit 07
Purchase
Purchase assignment
assignment
SAP AG 2001
Purchase
contract
WOIL Exchange
Exchange partner
agreement
Order
WOIL customer
SAP AG 2001
n When the product used in a sale is purchased directly from a third party, purchase assignment
functionality automates the recording of these purchase documents when the user records the
customer sale documents in the SAP System.
n Therefore when the product for a customer sale is supplied from an exchange partner’s terminal, you
assign an exchange purchase contract item to the delivery document of the customer sale process.
n In the first step of the process, you record a sales order in the SAP system as shown in the above
slide.
Purchase
contract
WOIL Exchange
Exchange partner
ENNT
T
agreement
ME
NNM
SIIGG
ASSS
SEE A
HAAS
RCCH
PPUUR
Order
WOIL customer
Delivery
SAP AG 2001
n In the second step of the purchase assignment process, a delivery is created and the exchange
purchase contract line item is assigned to the delivery.
n When the delivery is saved, the quantity to be delivered appears as intended quantity in the quantity
schedule of the purchase contract.
Logical
Goods Purchase
Goods receipt
receipt goods flow
contract
WOIL Exchange
Exchange partner
agreement
Physical
goods flow
Order
WOIL customer
Delivery
Goods
Goods issue
issue
SAP AG 2001
n In the third step of the purchase assignment process, the goods issue is posted, which triggers the
system to automatically post the purchase call-off and the exchange related goods receipt.
n Quantity schedule functionality is not required for purchase assignment. However, when quantity
schedules are used, the system updates the quantity schedule in the following way:
n When you create the delivery and assign the quantity to be delivered to an exchange purchase
contract, the quantity to be delivered appears as an intended quantity in the quantity schedule.
n As soon as the goods issue is posted (and the system automatically creates the purchase order and the
following goods receipt), the delivered quantity is listed in the quantity schedule as a goods receipt
quantity.
Purchase
Sales
contract
delivery note
Item
Purchase
Purchase assignment
assignment
•• Exchange
Exchange contract
contract items
items
•• Non-exchange
Non-exchange contract
contract items
items
Purchase
call-off
Goods
issue
Purchase
Purchase assignment
assignment postings
postings Goods
receipt
•• Post
Post purchase
purchase call
call off
off
•• Post goods receipt
Post goods receipt
SAP AG 2001
n It is possible to assign the delivery to either a purchase contract or to a purchase order. As soon as
the goods issue is posted, an automatic goods receipt is created for the purchase order or, if assigned
to a contract, a purchase call-off is posted before the automatic goods receipt is carried out.
n Purchase assignment functionality is also available for non-exchange contracts.
Exchange
plant
Exchange
plant
Reg
$0
00 Stock
Stock
SAP AG 2001
n When posting a goods receipt under a borrow and loan agreement, the system usually takes the price
from the receiving plant in order to valuate the material received.
n For plants which are only used for purchase assignments, there may be no stock existing.
n In the material master, you can assign so-called price reference plants to each plant. When there is no
stock available at the receiving plant, the system will then take the price from the assigned price
reference plant in order to valuate the material received.
n By setting the so-called price reference valuation plant flag in customizing, you can specify that the
system should take the price from the price reference plant, even if there is stock available at the
receiving plant.
n The slide (above) is the first of three slides which represent the recording of an exchange receipt at a
partner’s terminal. This receipt will be followed by a sale to your customer, from this terminal. In
this illustration, your customer has arrived at your exchange partner’s terminal to pull a load of 8,000
UG6 of regular gasoline. In your SAP System, you have defined your exchange partner’s terminal as
a plant. Since none of the physical stock at this terminal is your stock, there is no inventory of
material recorded in your SAP System at this plant.
General
General ledger:
ledger:
Borrow/loan agreement:
Reg Price
$1.00/gal ref. plant Reg
$1.00/gal
8,000
8,000 gal.
gal. Stock
Stock
SAP AG 2001
n The first step is to record the exchange receipt. At SAP, this process involves creating the purchase
order and goods receipt documents. Configuration has been set to value the product on the purchase
order with the value maintained for that same material in the price reference plant. In other words,
the value of Regular at the price reference plant is $1.00. Therefore, the posting of the exchange
receipt of Regular at the exchange plant is valued based on $1.00.
Exchange General
General ledger:
ledger:
plant
Borrow/loan agreement:
00 gal.
gal. stock
stock
SAP AG 2001
n The last step in the process is to record the sale of Regular to your customer. The accounting entry
for the sale to your customer is a credit (decrease) of physical inventory of Regular and a debit
(increase) to a cost of goods sold account. The value (cost) of the Regular being sold to your
customer, you will remember, was derived from the value of Regular at the price reference plant.
n Therefore, the value at the price reference plant not only determines the valuation on exchange
receipt postings, but is also responsible for the value of the posting to the cost of goods sold account
associated with the customer sale, following the exchange receipt.
SAP AG 2001
SAP AG 2001
AOIL "lifts" product from the exchange partner’s location and delivers
that product to its own service station.
7-1 A service station calls you to order a specific quantity of product, which is to be
delivered from your exchange partner’s location. That means that you create an
order and assign the subsequent delivery to the purchase contract that is connected
to an exchange agreement.
Note: This is not a sale from you to your exchange partner, but to your own
customer.
7-1-1 Create a sales order for the service station (no reference to a contract).
Ship-to party: CUST01-##
Order type: OR
Sales area AESO/A1/A1
Material: REGULAR-##
Quantity: 12000 GAL
Plant: AP02
Save the sales order and make a note of the document number.
____________________________________________________________
7-1-2 Create the delivery for the sales order. Assign the purchase contract from
Exercise 3-2-5 to the delivery. Do not post the goods issue yet.
Shipping point: ASH2
Storage location: A2L1
Purchase document number: (Number from 3-2-5)
Item: 10
Assigned quantity: 12000 GAL
Save the delivery (do not post the goods issue yet!) and make a note of the
document number.
____________________________________________________________
7-2 How do you set up the system so that the purchase contract is automatically
assigned during delivery creation?
__________________________________________________________________
__________________________________________________________________
__________________________________________________________________
Contents:
l Sub/base product Overview
l Price reference plant
l Account posting review
SAP AG 2001
SAP AG 2001
Course
Course overview
overview
Business
Business
Conclusion
Conclusion
background
background
Exchange
Exchange
Other
Other features
features
agreement
agreement setup
setup
Daily
Daily business
business
Exchange
Exchange reports
reports
flow
flow
Split
Split condition
condition
Logical
Logical inventory
inventory
processing
processing
Unit 08
Sub/base
Sub/base
Settlement
Settlement
relationship
relationship
Purchase
Purchase assignment
assignment
SAP AG 2001
SAP AG 2001
n Even though there are many differenct products exchanged, it is usually the case that exchange
partners agree to track the exchange balance of a single product. This simplifies accounting for the
exchange balance. The product in which the exchange balance is tracked, is referred to as the base
product. The actual product delivered or received is referred to as the sub product. Differences in
value between the base product and the sub product are usually settled between the exchange
partners by using product differential fees.
n In the above example, the exchange partners are exchanging three products, but tracking the
exchange balance in the base product of ‘regular’ gasoline.
Exchange
plant
Reg Sup
00 stock
stock
SAP AG 2001
n The valuation of inventory postings on exchange movements is configurable in the SAP System and
relies on a feature referred to as the price reference plant. The price reference plant can be an actual
plant where physical stocks are maintained of the various materials exchanged. An example could be
your refinery plant. Or the price reference plant can be a virtual plant (sometimes called a paper
plant) where there are no physical stocks of material maintained.
n The slide (above) is the first of five slides which represent the recording of an exchange receipt at an
exchange partner’s terminal. This receipt will be followed by a sale to your customer from this
terminal.
n In this illustration, your customer has arrived at your exchange partner’s terminal to pull a load of
8,000 UG6 of Super gasoline. In your SAP System, you have defined your exchange partner’s
terminal as a plant. Since none of the physical stock at this terminal is your stock, there is no
inventory of material recorded in your SAP System at this plant. Additionally, for all materials that
are to be exchanged, you have also defined a price reference plant.
Exchange Price
Exchange
plant ref. plant
Plant
Reg Sup
Reg Sup
$1.00/gal $1.25/gal
$1.25/gal
8,000
8,000 gal.
gal. stock
stock >> 00 gal.
gal. stock
stock
SAP AG 2001
n The first step is to record the exchange receipt. This process in the SAP System includes creating the
purchase order and goods receipt documents. Configuration has been set to value each product on the
purchase order with the value maintained for that same material in the price reference plant. In other
words, the value of Super at the price reference plant is $1.25. Therefore, the posting of the exchange
receipt of Super at the exchange plant is valued based on $1.25.
Exchange
plant
Reg Sup
$1.25/gal
00 gal.
gal. stock
stock
SAP AG 2001
n To complete the transaction, when the sale to the customer is posted in the SAP System, the physical
inventory of Super that has just been created is relieved. Following the exchange purchase order and
goods receipt of product from your exchange partner, you must record a sales order, delivery and
goods issue to your customer. This sale of Super is recorded against the same plant and storage
location used for recording the exchange receipt. Therefore, the inventory volume is drawn down to
zero.
Purchase contract
Exchange
Exchange Sales contract
Agreement
Agreement
General
General ledger:
ledger:
Receipt
Purchase call-off
Borrow/loan agreement:
Goods receipt Debit: PHYSICAL INVENTORY $10,000
Credit: LOGICAL INVENTORY $ 8,000
Credit: Sub/Base Gain/Loss $ 2,000
Invoice verification
Price
Price
ref.
ref. plant
plant
Reg Sup
$1.00/gal $1.25/gal
Base Sub
SAP AG 2001
n The accounting entry recorded at goods receipt reflects values from the price reference plant. Since a
product is being added to inventory, a debit (increase) to physical inventory is recorded. Since the
actual product being loaded is Super, the value assigned to this accounting entry is the corresponding
value for Super that is maintained at the price reference plant.
n The offsetting entry to the physical inventory posting is to logical inventory. Remember that the
logical inventory is being tracked in the Base product of Regular. Therefore, the valuation of the
posting to logical inventory is derived from the value of Regular gasoline maintained at the price
reference plant. The value of Regular gasoline at the price reference plant is $1.00 per UG6.
n Differences between the value of the sub product (Super) and the value of the base product (Regular)
are posted to sub/base gain/loss account.
General
General ledger:
ledger:
Customer sale
Sales call-off
Billing
Exchange
x
Price
plant
ref. plant
SAP AG 2001
n The accounting entry for the sale to your customer is a credit (decrease) of physical inventory of
Super and a debit (increase) to a cost of goods sold account. The value (cost) of the Super being sold
to your customer, you will remember, was derived from the value placed on the exchange purchase
order. The value on the exchange purchase order was pulled from the value of Super at the price
reference plant.
n Therefore, the price reference plant value not only controls the valuation on exchange receipt
postings, but is also responsible for the value of the posting to the cost of goods sold account
associated with the customer sale following the exchange receipt.
Physical
IMG plant AP04
Sub product setting
Sup
Plnt Exg. Val. $1.40/gal
AP04 Sub prod
AP05
Reg
$1.09/gal
Base prod Borrow/loan agreement:
Debit: PHYSICAL INVENTORY $1.32
<
Exchange header
Credit: LOGICAL INVENTORY $1.05
Base product setting Price ref.
Credit: sub/base gain/loss $0.27
Control data
plant AP01
Reg
$1.05/gal
Base prod
SAP AG 2001
n Separate settings exist for controlling the valuation of the sub product and the base product.
n It is ONLY with exchange receipts, that you can derive the valuation of the sub product from either
the current physical inventory value (e.g. Plant AP04 = $1.40) or from the value maintained in the
price reference plant (e.g. AP01 = $1.32). When the flag is set in the IMG, the cost is derived from
the price reference plant. When the flag is not set, the cost is derived from the physical plant.
n On exchange receipts, the valuation of the Base Product can also be derived either from the current
physical inventory value (e.g. Plant AP04 = $1.09) or from the value maintained in the price
reference plant (e.g. AP01 = $1.05).
IMG
Physical
Sub product setting plant AP04
Plnt Exg. Val.
AP04 Sup
AP05 $1.40/gal
Reg
Borrow/loan agreement:
$1.09/gal
Debit: PHYSICAL INVENTORY $1.40
Exchange header
Credit: LOGICAL INVENTORY $1.09
base product setting
Credit: sub/base gain/loss $0.31
Price ref.
Control data
plant AP01
S/B prod.ind. Real plant valuatn.
Sup
$1.32/gal
Reg
$1.05/gal
SAP AG 2001
n In the above example, the settings have been changed from the slide on the previous page.
n Valuation for sub- and base product is derived from the physical plant.
IMG
Physical
sub product setting plant AP04
Plnt Exg. Val.
AP04 Sup
AP05 $1.40
Reg
$1.09 Borrow/loan agreement:
Exchange header <Debit: PHYSICAL INVENTORY $1.40
Credit: LOGICAL INVENTORY $1.05
base product setting
Price ref. Credit: sub/base gain/loss $0.35
Control data
plant AP01
S/B prod.ind. Ref. plant valuation
Sup
$1.32
Reg
$1.05
SAP AG 2001
n In the above example, valuation for the sub product is derived from the physical plant and valuation
for the base product is derived from the price reference plant.
Your
terminal
Reg Sup
$.99/gal $1.19/gal
50,000
50,000 gal
gal Stock
Stock -- Sup
Sup
40,000
40,000 gal Stock -- Reg
gal Stock Reg
SAP AG 2001
n Now let’s go to a different scenario - an exchange delivery. In this scenario, your exchange partner’s
customer arrives at your terminal to pull the product. You have two tanks (one each) of Regular and
Super gasoline with the volumes and values indicated above. In this example, you have configured
the system to ALWAYS value exchange related postings with material values derived from the price
reference plant.
22 Exchange delivery
from your terminal
Reg Sup
$.99/gal $1.19/gal Reg Sup
$1.00/gal $1.25/gal
42,000
42,000 gal
gal Stock
Stock -- Sup
Sup >> 00 Stock
Stock -- Sup
Sup
40,000
40,000 gal Stock -- Reg
gal Stock Reg >> 00 Stock
Stock -- Reg
Reg
SAP AG 2001
n Your exchange partner’s customer loads 8,000 gal of Super gasoline. The recordings required in the
SAP system to reflect this event are an exchange related sales order, and a delivery and goods issue.
Purchase contract
Exchange
Exchange Sales contract
Agreement
Agreement
General
General ledger:
ledger: Delivery
Sales call-off
Delivery
Borrow/loan agreement:
Credit: PHYSICAL INVENTORY $9,520 Goods issue
Debit: LOGICAL INVENTORY $8,000
Debit: sub/base gain/loss $1,520 Billing
Exchange Price
plant ref. plant
Reg Sup
$.99/gal Reg Sup
$1.19/gal
$1.00/gal $1.25/gal
SAP AG 2001
n The resulting accounting document reflects a credit (decrease) to physical inventory and a debit
(increase) to logical inventory. The physical inventory is always relieved using the value of the
physical inventory and not the value from the price reference plant. If your company is using a
moving average price to value your inventory, then this value reflects the various purchase and
transportation costs incurred in order to get product into that terminal.
n Instead of the offsetting entry being recorded to a cost of goods sold account as would be done on a
regular sale, the offsetting entry is recorded to logical inventory. Therefore, the value of the logical
inventory account posting is derived from the value of the base product at the price reference plant.
Again, the difference is posted to the sub/base gain/loss account.
n Note, with the configuration set to always value logical inventory from the price reference plant, it is
possible to have a gain/loss posting on exchange deliveries even if the base product and the sub
product are the same product. This is because the moving average price at the physical plant may be
different from the value maintained for the same material at the price reference plant. The price at the
physical plant is constantly changing because it is based on actual purchase prices and transportation
costs incurred to bring the product into inventory. However, the value of the same material at the
price reference plant is revalued periodically according to market prices. Configuration can be set at
the plant level to value the logical inventory at the physical inventory price. In this case, there would
be no gain/loss posting.
SAP AG 2001
SAP AG 2001
8-2
8-2-1 To create the sales call-off:
Choose Logistics → Exchanges → Exchange operations → Exchange
deliveries → Sales call-off → Create sales call-off
Order type: OR
It is important to choose Create with reference.
Select the contract tab on the Create with reference (F8) dialog box. Enter
the contract number from exercise 8-1-2 and choose Copy.
(Note: You can find the contract by selecting 'Sales itm.per Exchange
(Partner/Sorg/ExgT/ExgNo/Mat./Plnt.)' in the search help. Enter exchange
number from exercise 8-1-2.
Select the Ship-To party CUST03-## from the selection window.
Enter call-off quantity (order quantity): 20000 GAL:
Familiarize yourself with the data in the overview screen, and save the call-
off (or choose Sales document → Deliver).
Contents:
l Sales and Distribution
n Split billing overview
n Condition type
n Billing type
l Materials Management
n Split invoice verification overview
n Condition type
n Evaluated receipt settlement
l Netting
SAP AG 2001
SAP AG 2001
Course
Course overview
overview
Business
Business
Conclusion
Conclusion
background
background
Exchange
Exchange
Other
Other features
features
agreement
agreement setup
setup
Daily
Daily business
business
Exchange
Exchange reports
reports
flow
flow
Unit 09
Split
Split condition
condition
Logical
Logical inventory
inventory
processing
processing
Sub/base
Sub/base
Settlement
Settlement
relationship
relationship
Purchase
Purchase assignment
assignment
SAP AG 2001
Invoice
Taxes
ry
Delive ues
r odu ct val Invoice
P
Fees Fees
Taxes
Invoice
Product
values
Up to 9 invoice cycles
Assign invoice cycle to a condition type
Assign invoice cycles to billing type
SAP AG 2001
n Split invoicing can be used for both exchange and non-exchange deliveries.
n With sales split invoice processing, it is possible to create up to nine different invoices for one
exchange delivery, for example for
a tax invoice
an invoice for the related fees
an invoice for the product values for buy/sell exchange deliveries.
Contract
Contract
Customizing
Invoice cycle product
1 1 PR00 Product
Invoice cycle fees 2 2 LOCN Fees
Invoice cycle taxes 33 33 EFET Tax
Call-Off
Call-Off
1 PR00 Product
2 LOCN Fees
33 EFET Tax
SAP AG 2001
Delivery
- PR00 11
- LOCN 22
- EFET 33
Invoice cycles 1 2 3 4 5 6 7 8 9
Summary: x x x x x x x x x
SAP AG 2001
n For each billing type, you specify which invoice cycles the system should process during billing.
n You assign these invoice cycles to the billing types in customizing.
n For each delivery, the system keeps track of the invoice cycles which have been processed.
n The invoicing is complete when the system has processed all nine invoice cycles.
Invoice
Product
rder
ur chase o lue
P ct va
Produ
Invoice
Fees
Fees
e tax
Excis Invoice
Excise
Tax
• Up to 9 invoice cycles
• Assign invoice cycle to a condition type
• Set split invoice indicator on tax condition types
• Assign invoice cycles to invoice verification filter type
SAP AG 2001
n Split invoicing for MM invoice verification can also be used to process both exchange and non-
exchange receipts.
n With split invoice processing, it is possible to create up to nine different invoices for one exchange
receipt, for example for
a tax invoice
an invoice for the related fees
an invoice for the product values of buy/sell exchange receipts
FI Documents
Purchase Order
Tax 33 EFET x
(del cost) Tax EFET
(del cost)
Fees 22 x
LOCN
Fees LOCN
SAP AG 2001
n Tax condition types are marked as split conditions by setting the Split IV indicator.
n The system copies the Split IV indicator into the related documents where it can still be changed.
n Fee and tax condition types have an invoice cycle assigned to them.
SAP AG 2001
n For each invoice filter type, you specify which invoice cycles the system should process during
invoice verification.
n You assign the invoice cycles to the invoice filter types in customizing.
Selection of
configured invoice
filter types
Optional selection
by exchange no.
Access to fee
condition details
SAP AG 2001
Verification is
processed in
background
(RMBABG00)
Unmatched
invoices can be
resolved manually
from work list
SAP AG 2001
n One method of processing invoice verification is to process in background mode. In this process,
only the invoice amount and item references are entered online.
n Invoice verification is processed in the background.
n Users then only have to process invoices which they were unable to post the background processing.
n This method is much faster than the process whereby the processor must enter both the debit and
credit amounts on two screens and ensure they balance before posting. With background processing,
the system is able to post all invoices which balance.
Goods
Goods receipt Goods Additional select options
receipt receipt
• Exchange number
• Exchange items only?
• Invoice filter type (FEE, MAT, TAX)
• Invoice posting date
ERS selection
Invoice generation
• Post invoice for receipts
• Post credit memo for reversals
Invoice • Inclusive product values
Receipt • Incl. split excise taxes as delivery costs
• Inclusive exchange fees
SAP AG 2001
n In the evaluated receipt settlement (ERS), you enter various selection criteria.
n Invoice filter types are also specified. This controls which condition types are processed during
invoice verification. Invoice filter types are maintained in customizing.
n Once invoice cycles have been used to post separate accounting documents for product, fees and
taxes, it is then possible to create separate netting documents as well.
n In the same way as for billing types and invoice verification filters, you assign an invoice cycle
number(s) to the netting document type.
n The system then clears only the selected conditions in the split netting process.
l Split billing
l Split invoice verification
l Split netting
SAP AG 2001
SAP AG 2001
9-1 To make sure that the system is configured correctly for splitting conditions during
billing, review the condition data in the sales contract.
9-1-1 Review the sales contract.
Contract: (Number from 8-1-4)
Which invoice cycles are assigned to the following condition types?
DRC0 (gross price) ____________________________________
QDRM (metropol. ind) ____________________________________
EFET (federal excise tax) ____________________________________
PDFA (differential fee) ____________________________________
Where do you specify the default invoice cycles for the conditions?
____________________________________________________________
____________________________________________________________
9-1-2 Which invoice cycles are billed by the system when the following billing
types are used:
OIFT (invoice - taxes) _________________________________________
OIFF (invoice fees & material) ___________________________________
9-4 You are now going to bill the created goods receipt. As you have agreed with your
partner to do netting, you do not receive any invoice from your partner at this point.
You will therefore use ERS (evaluated receipt settlement) to create the related
accounting documents.
9-4-1 Process ERS for fees and prices.
Exchange agreement number: (Number from 8-1-1, do not leave
blank)
Invoice filter: FEE
Posting date: (Today's date)
Test: run (blank)
9-4-2 Which conditions have been processed during the ERS run?
____________________________________________________________
9-4-3 Process ERS for taxes.
Exchange agreement number: (Number from 8-1-1, do not leave
blank)
Invoice filter: TAX
Posting date: (Today's date)
Test run (blank)
9-4-4 Which conditions have been processed during the ERS run?
____________________________________________________________
Contents:
SAP AG 2001
SAP AG 2001
Course
Course overview
overview
Business
Business
Conclusion
Conclusion
background
background
Exchange
Exchange
Other
Other features
features
agreement
agreement setup
setup
Unit 10
Daily
Daily business
business
Exchange
Exchange reports
reports
flow
flow
Split
Split condition
condition
Logical
Logical inventory
inventory
processing
processing
Sub/base
Sub/base
Settlement
Settlement
relationship
relationship
Purchase
Purchase assignment
assignment
SAP AG 2001
Characteristics
Characteristics Deliveries
Deliveries Exg.
Exg. Receipt
Receipt Bal(Lifts-Recs)
Bal(Lifts-Recs)
******
****** Exg.
Exg. Partner
Partner 12,000.00
12,000.00 L15
L15 11,000.00
11,000.00 L15
L15 1000.00
1000.00 L15
L15
Updated
Updated at:
at: Deliveries
Deliveries Receipts
Receipts Exchange
Exchange balance
balance
SAP AG 2001
n The user is able to report total deliveries, receipts and balances against exchange agreements and to
summarize this information by material, exchange type, exchange partner, exchange number and
location.
n This functionality is used mainly across pure exchange types where it enables the user to track the
logical inventory balance in real-time and on-line.
n All material movements and LIA transactions which are assigned to an exchange agreement and
correspond to the selection criteria can be listed. The list is sorted according to:
- Exchange partner
- Number of the exchange agreement
- Material
- Plant
- Month
n The total amount of material movements and LIA transactions is displayed for each level; the lifts
and receipts are listed in two separate columns and the difference between the two is listed in an
additional column.
n The system only updates the exchange balance when the goods receipts / goods issues are exchange-
related.
Exchange
agreements
Contract
Purchase fees
Sales
contracts contracts
Abstract
Abstract
Exchange header
Sales contract
Purchase contract Repricing
contract fees
Contract display
SAP AG 2001
n The exchange abstract is a report of all the pertinent information about the exchange agreement
header and related sales and purchase contracts.
n A fee pricing date can be specified in the selection screen. All fees displayed in the report are only
those which are effective on the date entered for fee pricing.
n Functionality is provided, allowing the user to reprice contract fees to a new fee repricing date.
Other reports
l Customer balance
l Vendor balance
l Exchange transactions
l Exchange entitlements
l Exchange movements
SAP AG 2001
SAP AG 2001
Contents:
l Logical inventory revaluation overview
l Bill of material
l Archive of exchange data
SAP AG 2001
SAP AG 2001
Course
Course overview
overview
Business
Business
Conclusion
Conclusion
background
background
Unit 11
Exchange
Exchange
Other
Other features
features
agreement
agreement setup
setup
Daily
Daily business
business
Exchange
Exchange reports
reports
flow
flow
Split
Split condition
condition
Logical
Logical inventory
inventory
processing
processing
Sub/base
Sub/base
Settlement
Settlement
relationship
relationship
Purchase
Purchase assignment
assignment
SAP AG 2001
OIA07
LIA
SAP AG 2001
n The system tracks the moving average price of the logical inventory balances at the company, plant
and product level.
n This strategy is illustrated above and ensures that the integrity between the logical inventory quantity
balance and the logical inventory financial balance in the system is always maintained. In other
words, if all of the quantity balance were cleared, then the financial value held in the system would
be zero.
n This strategy ensures that IS-Oil can handle both standard priced and moving average priced
physical inventory valuation strategies.
OIA07 General
General Ledger
Ledger
Qty Value M.A.P.
2,800L $3,062 $1.0936
MR21
$1.00
OIA07
Qty Value M.A.P.
2,800L $2,800 $1.0000
SAP AG 2001
n IS-Oil functionality incorporates an enhanced price change transaction, which can be invoked as
required, in order to post a new inventory carrying price for logical inventory within a particular
plant.
n The effect of posting a revaluation of logical inventory is illustrated above. The logical inventory
carrying price is changed from 1.0936 USD/L to 1.0 USD/L. The difference between the logical
inventory value at the old carrying price and that at the new carrying price is calculated by the
system and posted to a P&L account.
n In this case the difference is:
(Old price X Quantity) - (New price X quantity) = $3,062 - $2,800 = $262.
n This difference is recorded as a loss during the revaluation process.
Exchange
BOM Material - fees, exg data, QS BOM header
sales contract
BOM component
BOM Material - fees, exg data, QS
Call off
Component 1
order
Component 2
SAP AG 2001
n Exchange functionality integrates with bill of material functionality in the SAP System.
n In the exchange related sales contract in the above diagram, the BoM header material is recorded.
n During the call-off, the BoM splits into its component parts. At goods issue, you notice the logical
inventory is updated with the header material while the physical inventory is updated with the
components. For example, when delivering 100 gallons of a mid-grade gasoline which comprises of
60% regular and 40% super, the exchange balance is updated with a delivery of 100 gallons of mid-
grade, while physical inventory for regular and super are reduced by 60 gallons and 40 gallons
respectively.
Configuration
SAP AG 2001
S036
Data
Archive management
(SARA)
Archive
Object
MC_S036 Delete
Reload
SAP AG 2001
n Exchange functionality incorporates an archiving strategy to efficiently manage exchange data. The
number of exchange movements within S036 continues to grow over time.
n After a period of time, it may be prudent to archive a portion of the exchange data.
n Functionality is available to archive a portion of the exchange history and substitute an exchange
balance summary record in its place.
n If necessary, archived records can be reloaded into the system at any time.
SAP AG 2001
SAP AG 2001
In order to adjust the inventory value to the current market price, AOIL
revalues both the physical and the logical inventory.
11-1 Due to changed market prices, you will have to revalue the inventory for
REGULAR-##.
11-1-1 In the accounting view of the material master, check the moving average
price of the base material that you used in unit 8.
Material: REGULAR-##
Plant: AP04
Check that this is the price that the system used for the goods issue posting in
8-2-2.
11-1-2 Adjust the value of both the physical and the logical inventory to the stock
market price.
Material: REGULAR-##
Plant: AP04
New price: 0,54 USD / 1 KG
CIP: 2 (Revalue logical inventory using new phys.
inventory price)
11-1-1 To check the moving average price of the base material that you have used in
unit 8, choose:
Logistics → Materials management → Material master → Material →
Display → Display current
Enter Material REGULAR-##, select Accounting, then enter Plant AP04.
In the field Price control, the value V indicates that the system uses moving
average price valuation for this material in plant AP04. In the field
Mov.avg.price, you can see the current material price, which should be the
same as the system used for the goods issue posting in 8-2-2.
11-1-2 To adjust the value of the physical and the logical inventory to the stock
market price, choose:
Logistics → Exchanges → Exchange operations → Logical inventory
adjustments → Revaluation of logical inventory
Enter:
Posting date: (Today's date)
Company code: AOIL
Plant: AP04
Choose Enter. On the following Price change – Overview screen, enter:
Material: REGULAR-##
New price: 0,54 USD / 1 KG
CIP: 2 (Revalue logical inventory using new phys.
inventory price)
Choose Price change → Save to post the new price.
CourseOverview
CourseOverview
Unit 12 Business
Conclusion Business
Conclusion
Background
Background
Exchange
Exchange
Other
Other Features
Features
Agreement
Agreement Setup
Setup
Daily
Daily Business
Business
Exchange
Exchange Reports
Reports
Flow
Flow
Split
Split Condition
Condition
Logical
Logical Inventory
Inventory
Processing
Processing
Sub/Base
Sub/Base
Settlement
Settlement
Relationship
Relationship
Purchase
Purchase Assignment
Assignment
SAP AG 2001
SAP AG 2001
SAP AG 2001