Sei sulla pagina 1di 53

IS-OIL Industry Solution Oil

Release 4.72

Release Notes

Copyright 2002 SAP AG. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of
Microsoft Corporation.
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.
ORACLE is a registered trademark of ORACLE Corporation.
INFORMIX-OnLine for SAP and Informix Dynamic Server
Incorporated.

TM

are registered trademarks of Informix Software

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other
Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium,
Massachusetts Institute of Technology.
JAVA is a registered trademark of Sun Microsystems, Inc.
JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
implemented by Netscape.
SAP, SAP Logo, R/2, RIVA, R/3, 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.
Design: SAP Communications Media

SAP
System
Table of Contents
SAP AG
______________________________________________________________

1
1.1
1.2
1.2.1
1.2.2
1.2.3
1.2.4
1.3
1.3.1
1.3.2
1.3.2.1
1.3.2.2
1.3.2.3
1.3.3
1.3.3.1
1.3.3.2
1.3.3.3
1.3.4
1.3.4.1
1.3.5
1.3.5.1
1.3.6
1.3.6.1
1.3.6.2
1.3.6.3
1.3.6.4
1.3.6.5
1.3.6.6
1.3.6.7
1.3.7
1.3.7.1
1.3.7.2
1.3.7.3
1.3.8

IS-OIL Industry Solution Oil


Structure Changes in the Industry Solution Oil & Gas IMG
IS-OIL-OLM Remote Logistics M
Offshore Logist
Container List (Enhanced)
Material Tracking Reports (Enhanced)
Rentals (Enhanced)
Vessel Capacity Utilization Report (New)
IS-OIL-DS Downstream
General Switch for Certain Functions (Enhanced)
IS-OIL-DS-EXG Exchanges
BAPI for Invoice Verification (Changed)
Quantity Schedule in Transaction MEPO (New)
SET/GET Parameter OIA_NETCHK (Changed)
IS-OIL-DS-HPM Hydrocarbon Product Management
Quantity Conversion and Excise Duty for Go
(MIGO)
Transaction O582 (Deleted)
Remote Function Call Server (New)
IS-OIL-DS-TAS Interface to Termi
System
Terminal Automation System Interface (Enhanced)
IS-OIL-DS-MAP Marketing, Accounting and Pricing
SAP Term Event Date (Changed)
IS-OIL-DS-SSR Service Station Retailing
Business Add-In for Manipulating Modified
OIRADBT (New)
BAdI for Customizing Availability of Funct
Screen for Payment Card Transactions (New)
Business Add-In to Fill Additional Data Ta
(New)
Business Add-In for Manipulating New Recor
(New)
BAdI to Determine Process ID for Aggregate
(New)
Maintain Complaint Result on Company Code Level (New)
Inventory Management (Enhanced)
IS-OIL-DS-TD Transportation and Distribution
Free-On-Board Shipments of Third-Party Stock (Changed)
Shipment Cost Calculation Before Delivery Confirmation (New)
Shipment Planning Workbench (Enhanced)
IS-OIL-DS-TDP Tariffs, Duties and Permits

1
1
5
5
6
6
8
9
9
9
9
9
10
10
10
11
11
12
12
12
12
13
13
13
13
13
13
14
14
14
14
15
16
16

______________________________________________________________
SAP AG

iii

SAP
System
Table of Contents
SAP AG
______________________________________________________________

1.3.8.1
1.3.8.2
1.3.8.3
1.3.9
1.3.9.1
1.3.9.2
1.3.9.3
1.3.9.4
1.3.9.5
1.3.9.6
1.3.9.7
1.3.9.8
1.3.9.9
1.3.9.10
1.3.9.11
1.3.9.12
1.3.9.13
1.3.9.14
1.4
1.4.1
1.4.2
1.4.3
1.4.4
1.4.4.1
1.4.4.1.1
1.4.5
1.4.5.1
1.4.6
1.4.6.1
1.4.6.2
1.4.6.2.1
1.4.6.2.2
1.4.6.3
1.4.6.3.1
1.4.6.4
1.4.6.4.1

Quantity Conversion and Excise Duty for Go


(MIGO)
Physical Inventory-Based Excise Duty Revaluation (Changed)
User Exits for Default Values and Validation (Enhanced)
IS-OIL-DS-TSW Trader's and Scheduler's Workbench
Batch-Specific Movement Scenarios (New)
Batch-Specific Units of Measure (Changed)
Bunker Consumption in Nominations and Tickets (New)
Influencing Defaulting Logic in Ticket (New)
Selection Screen Defaults in Three-Way Pegging (Changed)
Check of Global Tracking System from Nominations (New)
Mass Change of Nominations (Enhanced)
Event Updates in Nominations (Changed)
Update of Reference Documents Based on Nominations (New)
Consumption of Document Quantities Without
(Changed)
Long-Term Planning and Nomination Breakdown (Changed)
Updating Reference Documents (New)
Additional Reference Documents in Scheduling (Changed)
Ticket Validation (New)
IS-OIL-PRA Production and Revenue Accounting
PRA Archiving (New)
Business Info. Warehouse - Removal of tech
(Deleted)
Removal of Obsolete PRA DDIC Objects and Coding (Deleted)
IS-OIL-PRA-EIA Energy Integration
Upstream Graphics
IS-OIL-PRA-EIA-UG Upstream Graphics
Upstream Graphics Bitmap/Icon Maintenance (Changed)
IS-OIL-PRA-PRD Production
Changed Numbering/Naming of Producing Entity Field (Changed)
IS-OIL-PRA-REP Reporting
Flashform Maintenance (Changed)
IS-OIL-PRA-REP-REG Regulatory Reporting
Texas P1, P1B, P2 and Combined Reports (New)
Multiple Well Statuses for MMS-OGOR Reporting (Changed)
IS-OIL-PRA-REP-TAX Tax Reporting
New Mexico and Wyoming Tax Reporting and T
(New)
IS-OIL-PRA-REP-ROY Royalty Reporting
Base Data Maintenance (Deleted)

16
17
18
18
18
19
20
21
22
22
23
23
24
24
25
26
26
27
28
28
29
29
30
30
30
31
31
31
31
32
32
33
33
33
37
37

______________________________________________________________
SAP AG

iv

SAP
System
Table of Contents
SAP AG
______________________________________________________________

1.4.6.4.2
1.4.6.4.3
1.4.6.4.4
1.4.7
1.4.7.1
1.4.7.2
1.4.7.3
1.4.7.3.1
1.4.7.4
1.4.7.4.1
1.4.7.5
1.4.7.5.1
1.4.7.5.2
1.4.7.5.3
1.4.7.6
1.4.7.6.1
1.4.7.7
1.4.7.7.1
1.4.7.7.2
1.4.7.8
1.4.7.8.1

Royalty Reporting - Old Framework (Deleted)


Oklahoma Royalty Report (Changed)
Royalty Reporting Cross References (New)
IS-OIL-PRA-REV Revenue
Maintain Action Taken Codes (New)
Valuation/Revenue Distribution - Old Version (Deleted)
IS-OIL-PRA-REV-CA Contractual Allocation
CA Division Order Sales - Sales Point Method (New)
IS-OIL-PRA-REV-CP Contracts & Pricing
Oil Industry Pricing Terminology and Key Fields (Enhanced)
IS-OIL-PRA-REV-VAL Valuation
Step Scale and Sliding Scale (Enhanced)
Valuation with Alternative Dual Accounting (New)
Settlement Statement Processing for System
(New)
IS-OIL-PRA-REV-CI Check Input
Check Input Valuation and Posting (Enhanced)
IS-OIL-PRA-REV-CW Check Write
Checkwrite - Old Version (Deleted)
Payment Processing (Changed)
IS-OIL-PRA-REV-JE Journal Entry
Maintain Legend Codes (New)

37
38
39
39
39
40
40
40
40
40
41
41
42
43
43
43
47
47
47
48
48

______________________________________________________________
SAP AG

SAP System
______________________________________________________________

1 IS-OIL

Industry Solution Oil

1.1 Structure Changes in the Industry Solution Oil & Gas IMG
Use
As of SAP Oil & Gas 4.72, the following changes apply to the Industry Solution Oil & Gas
Implementation Guide (IMG). To copy the changes into your Project IMGs, you must regenerate them.
The following IMG activities have been added:
Industry Solution Oil & Gas (Downstream) - Cross-Application Components
o

Under General Settings -> Maintain Business Add-Ins for Meter Reconciliation:
-

Business Add-In to Reconcile Meters with Common Equipment Number

Industry Solution Oil & Gas (Downstream) - HPM (Hydrocarbon Product Management)
o

Under Oil- and Gas-Specific Units of Measurement and Other Stockkeeping Units:
-

Set Oil- and Gas-Specific Units of Measurement

Under Petroleum Measurement Standards -> Quantity Conversion Interface (QCI) Configuration
-> Business Add-Ins:
-

BAdI: Customer-Specific Parameter Handling

Industry Solution Oil & Gas (Downstream) - TD (Transportation and Distribution)


o

Under TD Bulk Shipment -> Intransit Stock:


-

Define Goods Issue at Loading and Proof of Delivery

Convert TD Reason Code to Proof of Delivery Reason Code

Industry Solution Oil & Gas (Downstream) - SSR (Service Station Retailing)
o

Under Document Base Table -> Aggregation Schema -> Maintain Business Add-Ins for
Aggregation Schema Definitions:
-

BAdI: Insert Record into Aggregation Table While Filling DBT

BAdI: Modify Record in Aggregation Table While Filling DBT

Under Payment Card Handling -> Complaint Processing:


-

Maintain Complaint Result on Company Code Level

Under Payment Card Handling -> Maintain Business Add-Ins for Payment Card Handling:
-

BAdI: Determine Process ID for Aggregated Data Upload

BAdI: Exclude Functions for Detail Transaction File

Under Settlement and Invoicing -> Collective Printing -> Maintain Business Add-Ins for Collective
Printing:

______________________________________________________________
SAP AG

SAP System
______________________________________________________________

BAdI: Fill Addition Data Table and Structure

Industry Solution Oil & Gas (Downstream) - TSW (Trader's and Scheduler's Workbench)
o

Under Basic Functions -> Worklist -> Maintain Business Add-Ins for Worklists:
-

Under Nomination -> Basic Settings:


-

Define Reference Document Update

Under Nomination -> Maintain Business Add-Ins for Nomination:


-

BAdI: Reference Document Update

BAdI: Multiple Nominations Validation

BAdI: Nomination Update

BAdI: Publishing to Nomination

Business Add-In to Default the Location for Bunker Consumption

Business Add-In to Generate Nomination Items for Bunker Consumption

Under Tickets:
-

BAdI: Contract Tolerance Check Against Nomination Line Item

Define Validation Groups for Ticketing

Under Tickets -> Maintain Business Add-Ins for Ticket Processing:


-

BAdI: Ticket Header Validation

BAdI: Ticket Item Validation

BAdI: Ticket Event Validation

BAdI: Ticket Validation with Complete Data

BAdI: Ticket Default Settings

BAdI: Ticket Archiving Validation

BAdI: Generating Bunker Consumption Ticket Items

Under Location Balancing -> Maintain Business Add-Ins for Location Balancing:
-

Business Add-In to Check Demand and Supply Schedule Items

Business Add-In for Additional Validations in Location Balancing

Business Add-In for Inventory Calculations in Location Balancing

Under Three-Way Pegging -> Maintain Business Add-Ins for Three-Way Pegging:
-

Business Add-In for Update of Split Items

Business Add-In to Amend Three-Way Pegging Fields

BAdI: 3WP Selection Screen Defaulting

Under Stock Projection -> Maintain Business Add-Ins for Stock Projection:
-

Business Add-In for Rebranding in Stock Projection Worksheet

______________________________________________________________
SAP AG

SAP System
______________________________________________________________

Business Add-In to Schedule Entry Maintenance for Documents

Business Add-In to Schedule Updates of Documents

Business Add-In to Define Breakdown Routines for Schedule Items

Business Add-In to Change the Time Zone

Business Add-In to Consume Sales and Purchase Orders

Industry Solution Oil & Gas (PRA)


o

Under Contracts and Pricing:


-

Under Revenue Accounting -> Valuation:


-

Maintain Alternative Dual Accounting Price Multipliers

Under Revenue Accounting -> Payment Processing:


-

Define Industry Term Values for Pricing

Define Gross Volume States

Under Revenue Accounting:


-

Maintain Legend Codes

Maintain Action Taken Codes

The following IMG activities have been renamed:


Industry Solution Oil & Gas (Remote Logistics Management)
o

All IMG activites that used to come under Offshore Logistics Management are now under the
structure Industry Solution Oil & Gas (RLM - Remote Logistics Management).

Under Global Settings, the following IMG activity has been renamed:
-

Under Shipping -> Containers, the following structure node has been renamed:
-

From Activate Offshore Logistics to Activate Remote Logistics

From OLM Containers to RLM Containers

Under Shipping -> Containers -> RLM Containers, the following IMG activities have been
renamed:
-

From Define OLM Container Categories to Define RLM Container Categories

From Define Container Status for OLM Containers to Define Container Status for RLM
Containers

Under Shipping -> Containers -> RLM Containers -> Define Number Ranges, the following IMG
activity has been renamed:
-

From Define Number Ranges for OLM Containers to Define Number Ranges for RLM
Containers

Industry Solution Oil & Gas (Downstream) - Integration with Customer Relationship Management
o

Under Exise Tax, the following IMG activity has been renamed:

______________________________________________________________
SAP AG

SAP System
______________________________________________________________

From Define Tax Types and Assignment of Product Tax Groups to Define Tax Types and
Product Tax Groups

Industry Solution Oil & Gas (PRA)


o

Under Sales and Balancing, the following IMG activity has been renamed:
-

Under Sales and Balancing -> Balancing Statement, the following IMG activities have been
renamed:
-

From Base Configuration Settings for Balancing to Define Default Smart Form

From Customize Configurable Messages to Define Balancing Message Types

Under Revenue Accounting -> Valuation, the following IMG activity has been renamed:
-

From Additional CA Entitlement Volume Types to Define CA Entitlement Volume Types

From Maintenance of Dialog Process Limit for VL Doc to Maintain the Dialog Process Limit
for VL Doc

Under Revenue Accounting -> Configure Taxes, the following IMG activities have been renamed:
-

From Severance Tax Type to Define Severance Tax Types

From Tax Class to Define Tax Classes

From School Districts to Define School District Codes

Under Production, Tax and Royalty Reporting -> Royalty Reporting -> Royalty Reporting ->
Maintain Reporting Profile Information, the following IMG activities have been renamed:
-

From Profile and smart form links to Define Smart Form Structure

From Profile and field rules to Define Print Values for Smart Form

From Language dependent code text to Define Language for Smart Form Fields

The following IMG activities have been deleted:


Industry Solution Oil & Gas (Downstream) - HPM (Hydrocarbon Product Management)
o

Under Oil- and Gas-Specific Units of Measurement and Other Stockkeeping Units:
-

Check Units of Measurement

Industry Solution Oil & Gas (Downstream) - TDP (Tariffs, Duties and Permits)
o

Under Excise Duty Rates -> Internal Rates:


-

Set/Maintain Internal Rates for Purchasing Condition

Set/Maintain Internal Rates for Sales/Distribution Condition

Industry Solution Oil & Gas (PRA)


o

Under Revenue Accounting:


-

Configure List Viewer Path

Under Production, Tax and Royalty Reporting -> Tax Reporting -> New Tax Reporting Framework:

______________________________________________________________
SAP AG

SAP System
______________________________________________________________

Maintain Field Catalogue

The following IMG activities have been moved:


Industry Solution Oil & Gas (Downstream) - TSW (Trader's and Scheduler's Workbench)
o

The IMG activities that come under Graphical User Interface Settings have been moved to the
Basic Functions section. Previously they came under the Nomination section.

The following IMG activities have been deleted and moved to SAP Menu:
Industry Solution Oil & Gas (Downstream) - BDRP (Bulk Distribution Requirements Planning)
o

Under Site Control Parameters, the following IMG activity has been deleted:
Maintain Plant Site Control Parameters
You can now find this activity in SAP Menu under Logistics -> Sales and Distribution -> Bulk
Replenishment -> Master Data -> Site Control Parameters -> Maintain Plant Parameters.

Under Storage Objekct Characteristics, the following IMG activity has been deleted:
Maintain Segment Data for Storage Object Type
You can now find this activity in SAP Menu under Logistics -> Sales and Distribution -> Bulk
Replenishment -> Master Data -> Storage Objects -> Maintain Segment Data for Storage Object
Type.

Industry Solution Oil & Gas (Downstream) - HPM (Hydrocarbon Product Management)
o

Under Silo/Tank Management -> Master Data, the following IMG activity has been deleted:
Maintain Segment Data for Storage Object Type
You can now find this activity in SAP Menu under Logistics -> Sales and Distribution -> Bulk
Replenishment -> Master Data -> Storage Objects -> Maintain Segment Data for Storage Object
Type.

See also
As of SAP Oil & Gas 4.72, many of the O5* Customizing transactions are no longer available. This
cleanup activity:
o

Affects only transactions that are related to SM30 (view maintenance) and SM34 (view cluster
maintenance)

Does not mean that any functions have been removed, only that the way in which you call some
IMG activities is now different

For detailed information about the cleanup of O5* Customizing transactions, refer to SAP note 642828.

1.2 IS-OIL-OLM

Remote Logistics Management (former

______________________________________________________________
SAP AG

SAP System
______________________________________________________________

Offshore Logist
1.2.1 Container List (Enhanced)
Use
Previously, the Remote Logistics Container List displayed an icon to indicate that a specific container was
in use. As of SAP Oil & Gas 4.72, the list contains additional fields for the following:
o

Number of the shipment to which the container is currently assigned

Loading area

Holding area

1.2.2 Material Tracking Reports (Enhanced)


Use
As of SAP Oil & Gas 4.72, Remote Logistics Management (RLM) provides the following enhancements
to its material tracking capabilities.
Launch Reports from PM Order or PS Network Order
You can launch material tracking reports from a plant maintenance (PM) order for all operations or for a
specific operation. Similarly, you can launch material tracking reports from a project system (PS)
network order for all activities or for a specific activity.
Default Selection Variants
You can store default variants for material tracking selection screens, as you can for SAP RLM packing
screens, using parameter IDs. You can assign your variant to the corresponding parameter ID directly
from the tracking selection screen.
Drill Down to Specific Item
On the material tracking reports, you can select and drill down to any one of the following items to
display or change the specific object types:
o

PM order operation

PM order component

PS network activity

PS network component

1.2.3 Rentals (Enhanced)


Use

______________________________________________________________
SAP AG

SAP System
______________________________________________________________

SAP Remote Logistics Management (RLM) allows you to control the dispatch of rented items to remote
facilities. As of SAP Oil & Gas 4.72, RLM provides a broader solution, including new returns functions
and integration with planning functions.
The Return Rental Item process allows you to track rented items on their return journey from your plant
to the supplier. Additional mobilization data fields are available, including a check box to indicate
whether a specific rented item is a production resource or tool. The functions have been enhanced as
follows:
Additional Mobilization Data Fields
o

Mobilization Status
-

Packages
-

This field indicates the number of packages in which the rentals will arrive at the base. The
number of packages controls the number of mobilization items to be created and supports the
creation of supplementary packages and new mobilization items.

Vendor's Reference
-

The mobilization status field indicates whether or not the rental item is available for use.

The vendor's reference field rovides an external reference for the rental item and is also used
as a selection parameter in the new material tracking report for services.

Production Resource or Tool (PRT)


-

The PRT field flags the rental item as relevant for production planning.

PRT Allocation
If you select the PRT flag under Mobilization Data, PRT allocations to plant maintenance (PM) order
operations and project system (PS) network activities are created at the same time as the mobilization
items. If you do not specify a mobilization material number, PRT items of type miscellaneous are created.
If you specify a material number, the material must contain PRT data.
Returns
On the screen for PM orders and PS network order references, a split-screen view allows you to
distinguish between components and rentals (service lines with mobilization data).
You can pack return deliveries from a returns document and link multiple selection return lines in one
operation. To pack a return delivery, you select the appropriate return lines and choose Pack.
You can customize the system to perform the demobilization process automatically during shipment
receipt. This process updates the mobilization status to demobilized and sets the end date of the
availability for PRT items.
You can indicate the handover of rented material to another remote plant by linking the return document
to a new PM order or a PS network order for this plant.
Material Tracking Report for Services (Rentals)
In this report, the selection screen is based on service lines. A vendor reference is available on the
selection screen, together with all other service line fields and all mobilization data.

______________________________________________________________
SAP AG

SAP System
______________________________________________________________

1.2.4 Vessel Capacity Utilization Report (New)


Use
As of SAP Oil & Gas 4.72, Remote Logistics Management (RLM) allows you to generate even more
detailed information than before on vessel capacity utilization.
When you plan a shipment, you need to know how well the cargo carrier utilizes its capacity. For
example, on a boat the deck space footprint and weight are very important details. Information about
container weight and footprints has long been available in SAP. However, the information has never been
used to provide a report within a standard SAP system.
As of this release, the Vessel Capacity Utilization report includes a BAdI designed to determine the
available footprint and weight capacity on your vessel. You can start the report directly from a voyage or
a shipment, and you can use it to analyze capacity utilization for a complete voyage and for constituent
shipments within the voyage.
The report contains the following information:
o

Total capacity of the voyage, including surface area and weight

Actual load of the voyage, including surface area and weight

Difference between the capacity and the actual load

Within SAP RLM, voyages do not have routes associated with them. However, each shipment has an
associated route. The route of a voyage could span several of these shipment routes, so you can use these
to specify the voyage route when you run the Vessel Capacity Utilization report. If you do not specify a
route, you cannot perform per-leg calculations.

______________________________________________________________
SAP AG

SAP System
______________________________________________________________

The report enables you to plan the utilization of space on deck during return trips. You can also allow for
changes, as when voyages alter their routes due to such factors as adverse weather conditions during
loading at a remote facility.
You can also use this report to compare actual data with the total capacity of the vessel and show possible
capacity bottlenecks during a voyage.

1.3 IS-OIL-DS

Downstream

1.3.1 General Switch for Certain Functions (Enhanced)


Use
As of SAP Oil & Gas 4.72, you can call the following functions in the IMG activity General
Functionality Switch (On/Off):
o

Activate certain functions

Display settings at cross-client level

Activate components or packages at client level

Check component installations

1.3.2 IS-OIL-DS-EXG

Exchanges

1.3.2.1 BAPI for Invoice Verification (Changed)


Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL_470), transaction MR01 is no longer available. This
transaction was used for the invoice verification of incoming invoices. You can no longer use this
transaction to create incoming invoices with batch input processing.
As of SAP Oil & Gas 4.72, you can invoice fee items and use filter types using the enhanced BAPI
BAPI_INCOMINGINVOICE_CREATE.
See also
For more information, see SAP Note 648553.

1.3.2.2 Quantity Schedule in Transaction MEPO (New)


Use

______________________________________________________________
SAP AG

SAP System
______________________________________________________________

As of SAP Oil & Gas 4.72, you can change and display the quantity schedule in a purchase order
(transaction MEPO). The quantity schedule is displayed on a tab page with the same name.

1.3.2.3 SET/GET Parameter OIA_NETCHK (Changed)


Use
As of SAP Oil & Gas 4.72, you can enter the SET/GET parameter OIA_NETCHK in the user profile.
This parameter has replaced the OINETCHK indicator.
However, the system automatically checks if netting is complete for documents that are to be archived.
Documents for which netting is not complete are not archived. You do not need to make any settings in
the user profile for this to take place.
If you want to explicitly switch off the check for documents that are to be archived, you have to create the
above parameter in the user profile and assign it to a value not equal to Y. When you enter this Y, the
system also checks for documents that are to be archived.
Up to and including Release 4.6C, on the initial screen for the write program (SAPF048) of archiving
object FI_DOCUMNT, you could set the indicator OINETCHK, which activated the check for documents
to be archived.

1.3.3 IS-OIL-DS-HPM

Hydrocarbon Product Management

1.3.3.1 Quantity Conversion and Excise Duty for Goods Movements (MIGO)
(Enhanced)
Use
As of SAP Oil & Gas 4.72, the Business Add-In (BAdI) MIGO_BADI contains all the required
enhancements for the Oil & Gas quantity conversion and excise duty determination. This dramatically
reduces the number and extent of modifications.
As of SAP Oil & Gas 4.72, you can use the Oil & Gas quantity conversion and excise duty determination
in transaction MIGO for the following goods movements:
o

Transfer postings

Stock transfers with tracking function


-

Two-step stock transfers without a stock transport order


In transaction MIGO there is new subscreen that displays the data (such as the tracking
number) that you can use to track stock transfers.

Two-step stock transfers with a stock transport order


In transaction MIGO there are two new movement types (857 issue from intransit stock
(adjustment posting) and 858 receipt into intransit stock (adjustment posting)). If you use these
movement type for two-step stock transfers, you can track the goods movements and the
system automatically performs gain and loss postings.

______________________________________________________________
SAP AG

10

SAP System
______________________________________________________________

Restriction
You cannot use the Oil & Gas quantity conversion and excise duty determination in MIGO for the
following types of goods movements:
o

Goods receipt to transport

Goods receipt to transport identification code

Goods receipt to inbound delivery

Subsequent adjustment in subcontracting

Effects on Customizing
To use the movement types 857 and 858 for two-step stock transfers with a stock transport order and to
trigger the system to automatically perform gain and loss postings, you must make the following setting
in Customizing for the Industry Solution Oil & Gas (Downstream):
Activate the tracking function for two-step stock transfers in the IMG activity Maintain Two-Step
Transfer Control.

1.3.3.2 Transaction O582 (Deleted)


Use
As of SAP Oil & Gas 4.72, transaction O582 is no longer available. This transaction was used for
creating default values for the Oil & Gas quantity conversion.
You can, however, still create default values using transactions O3DEFAULTS and O3C1.

1.3.3.3 Remote Function Call Server (New)


Use
As of SAP Oil & Gas 4.72, you can use a new Remote Function Call (RFC) server. This server connects
the Quantity Conversion Interface (QCI) to external programs (C programs) that are provided by third
party software providers.
This solution is based on the C program QCI_SRV. To use the RFC server, you must compile this
program and connect it to SAP Oil & Gas.
The RFC server program is made up as follows:
o

Source code of the C program

Function module OIB_QCI_RFC_SERVER

Interface

Dummy includes of conversion routines from the American Petroleum Institute (API) and American
Gas Association (AGA)

______________________________________________________________
SAP AG

11

SAP System
______________________________________________________________

Help text

Effects on System Administration


For more information on the installation of the RFC server, see SAP Note 619060.
Effects on Customizing
To use the RFC server, you must make the following setting in Customizing for the Industry Solution Oil
& Gas (Downstream):
In the IMG activity Define conversion group and external function module settings, assign the function
module type for RFC to the required conversion group.
Restriction
You cannot use the new RFC server for Production and Revenue Accounting (PRA). Instead, you must
use the CALL SYSTEM technique.
See also
For more information about the RFC server and the CALL SYSTEM technique, see the following SAP
Notes:
o

619060 (QCI: New RFC Server Installation Guide)

619057 (External Function Calls Using CALL SYSTEM)

1.3.4 IS-OIL-DS-TAS

Interface to Terminal Automation System

1.3.4.1 Terminal Automation System Interface (Enhanced)


Use
As of SAP Oil & Gas 4.72, the Terminal Automation System interface allows delivery confirmations to
be created with reference to inbound deliveries when you purchase materials. The Terminal Automation
System of the receiving plant uses IDoc OILLDD to send the actual delivery data of a shipment to SAP
Oil & Gas. SAP Oil & Gas automatically creates the delivery confirmation.

1.3.5 IS-OIL-DS-MAP

Marketing, Accounting and Pricing

1.3.5.1 SAP Term Event Date (Changed)


Use
As of SAP Oil & Gas 4.72, the SAP term event date replaces the SAP term base date. The German SAP
term Basisdatum is not affected by this change.

______________________________________________________________
SAP AG

12

SAP System
______________________________________________________________

1.3.6 IS-OIL-DS-SSR

Service Station Retailing

1.3.6.1 Business Add-In for Manipulating Modified Records for OIRADBT (New)
Use
As of SAP Oil & Gas 4.72, this Business Add-In (BAdI) is called in function module OIRA_FILL_DBT.
You can use it to manipulate data in modified records before the aggregated data is used to fill table
OIRADBT.

1.3.6.2 BAdI for Customizing Availability of Functions on Detail Screen for


Payment Card Transactions (New)
Use
As of SAP Oil & Gas 4.72, you can use this Business Add-In (BAdI) to include your own logic for
determining the functions (such as reverse and change) that are available on the detail screen for payment
card (PC) transactions.
The BAdI is also available as of Release 4.6C Service Pack 2 AOP-SAPKI4C085.

1.3.6.3 Business Add-In to Fill Additional Data Table and Structure (New)
Use
As of SAP Oil & Gas 4.72, you can use this BAdI to determine additional data passed to the function
module GN_INVOICE_CREATE (invoice creation).
For example, if meter readings are used to create material documents and invoices, and you know that the
material documents are created before the invoicing process has started, you can use the BAdI to find the
number of a material document created from these meter readings. The material document numbers can
then be passed to function module GN_INVOICE_CREATE in the table parameter T_OIRI_ADDDATA.

1.3.6.4 Business Add-In for Manipulating New Records for OIRADBT (New)
Use
As of SAP Oil & Gas 4.72, this Business Add-In (BAdI) is called in function module OIRA_FILL_DBT.
You can use it to manipulate data in new aggregated records before the aggregated data is used to fill
table OIRADBT.

______________________________________________________________
SAP AG

13

SAP System
______________________________________________________________

1.3.6.5 BAdI to Determine Process ID for Aggregated Data Upload (New)


Use
As of SAP Oil & Gas 4.72, you can define your own logic for determining the process ID for the upload
of the aggregated clearing house data used for reconciliation.
The BAdI is also available as of Release 4.6C Service Pack 2 AOP-SAPKI4C078.

1.3.6.6 Maintain Complaint Result on Company Code Level (New)


Use
As of SAP Oil & Gas 4.72, you can define company code-specific settings for changing and processing
complaint results.

1.3.6.7 Inventory Management (Enhanced)


Use
As of SAP Oil & Gas 4.72, it is possible for the system to:
o

Determine storage locations at the BOM item material level in material documents based on meter
readings.

Use the correct material in material documents based on meter readings when the material assigned
to the meter is not the actual material. This is the case when, for example, a higher grade fuel is sold
as a lower grade fuel.

Reconcile stock using the dip readings from tanks that are connected.

Effects on Customizing
To enable the system to determine storage locations at the BOM item material level, in the document
definition step of the Implementation Guide (IMG) for the Industry Solution Oil & Gas (Downstream),
you must include:
Dest struc
Srce struc
OIRC_NON_DEST
OIRADBT

Dest fld.
Srce fld
SEQNR
SEQNR

Doc. key fld


(blank)

To do this, choose Define document schema.

______________________________________________________________
SAP AG

14

SAP System
______________________________________________________________

1.3.7 IS-OIL-DS-TD

Transportation and Distribution

1.3.7.1 Free-On-Board Shipments of Third-Party Stock (Changed)


Use
As of SAP Oil & Gas 4.72, you can change the classification parameters of batch materials. The
enhancement to Transportation and Distribution (TD) supports sales processes that involve materials
shipped in batches. The TD enhancements allow you to change the classification parameters at several
stages in the sales process, which results in a more accurate update of the delivery quantities.
The enhancement supports sales scenarios where the posting of goods issues, gains, or losses are
notrelevant to the shipment, as well as sales scenarios where the discharge information is not required and
the shipment is complete at loading confirmation, rather than at delivery confirmation.
Effects on Existing Data
During the shipment of free-on-board materials, the system posts the goods issue at loading confirmation.
Depending on the terms of the contract, the product quantity that the system uses in the invoice to the
customer is based on the discharge quantity or the loaded quantity.
During delivery confirmation, you enter the discharge quantity and other information that is relevant to
the discharge of product. The system uses the discharge quantity as the basis for invoicing or saves the
discharge data for statistical purposes. In either case, the system does not post gains or losses for the
product quantity. In some business scenarios it is not necessary to record discharge information, so a
delivery confirmation is not required. In that case, the enhancement allows you to complete a shipment at
loading confirmation, rather than at delivery confirmation.

1.3.7.2 Shipment Cost Calculation Before Delivery Confirmation (New)


Use
As of SAP Oil & Gas 4.72, you can perform shipment cost processing before a shipment reaches delivery
confirmation (status 6) in Transportation and Distribution (TD). Before this enhancement was available,
you could not create shipment cost documents for shipments where the delivery was not confirmed (a
status less than 6 in TD). Now, you can create shipment cost documents for TD shipments between the
loading and delivery confirmation (status 4 to 6 in TD).
With the Document Item Quantity Assignment in TD, you can allocate discharge-relevant documents to
shipment costs in the shipment cost document. With the enhancement, you can perform the cost
allocation before delivery confirmation.
Effects on Existing Data
During loading confirmation, if a shipment cost document already exists for a shipment, you can neither
make changes to the loading details of the shipment nor reverse the posting resulting from loading. To
perform loading confirmation again for a shipment that already has a shipment cost document, the
following options are possible:
o

If the shipment cost information is already transferred to financial accounting, you can reverse the

______________________________________________________________
SAP AG

15

SAP System
______________________________________________________________

posting data for each item (by cancelling the shipment cost settlement for each item) and delete the
shipment cost document.
o

If the shipment cost information is not yet transferred, you can delete the shipment cost document

Effects on Customizing
In Customizing for the shipment cost type, you define the overall status of shipments based on the
creation of shipment cost documents. You do this in Customizing for Industry Solution Oil & Gas
(Downstream) -> TD (Transportation and Distribution)-> TD Bulk Shipment -> Shipment Costs ->
Shipment Cost Document-> Shipment Cost Types and Item Categories.
In the Customizing activity Shipment Cost Types and Item Categories, you select the detail view of the
shipment cost type and in the Ov.stat.Shipmt field enter the value 4 for the overall status. You do this to
ensure that the system can generate a shipment cost document when the TD shipment is equal to or
greater than this overall status.

1.3.7.3 Shipment Planning Workbench (Enhanced)


Use
As of SAP Oil & Gas 4.72, you can assign reservations and inbound deliveries to a shipment in the
Shipment Planning Workbench.

1.3.8 IS-OIL-DS-TDP

Tariffs, Duties and Permits

1.3.8.1 Quantity Conversion and Excise Duty for Goods Movements (MIGO)
(Enhanced)
Use
As of SAP Oil & Gas 4.72, the Business Add-In (BAdI) MIGO_BADI contains all the required
enhancements for the Oil & Gas quantity conversion and excise duty determination. This dramatically
reduces the number and extent of modifications.
As of SAP Oil & Gas 4.72, you can use the Oil & Gas quantity conversion and excise duty determination
in transaction MIGO for the following goods movements:
o

Transfer postings

Stock transfers with tracking function


-

Two-step stock transfers without a stock transport order


In transaction MIGO there is new subscreen that displays the data (such as the tracking
number) that you can use to track stock transfers.

Two-step stock transfers with a stock transport order


In transaction MIGO there are two new movement types (857 issue from intransit stock
(adjustment posting) and 858 receipt into intransit stock (adjustment posting)). If you use these

______________________________________________________________
SAP AG

16

SAP System
______________________________________________________________

movement type for two-step stock transfers, you can track the goods movements and the
system automatically performs gain and loss postings.
Restriction
You cannot use the Oil & Gas quantity conversion and excise duty determination in MIGO for the
following types of goods movements:
o

Goods receipt to transport

Goods receipt to transport identification code

Goods receipt to inbound delivery

Subsequent adjustment in subcontracting

Effects on Customizing
To use the movement types 857 and 858 for two-step stock transfers with a stock transport order and to
trigger the system to automatically perform gain and loss postings, you must make the following setting
in Customizing for the Industry Solution Oil & Gas (Downstream):
Activate the tracking function for two-step stock transfers in the IMG activity Maintain Two-Step
Transfer Control.

1.3.8.2 Physical Inventory-Based Excise Duty Revaluation (Changed)


Use
As of SAP Oil & Gas 4.72, in order to have one common solution for the excise duty revaluation process,
you can now only revaluate excise duty when it is not based on the physical inventory count (transaction
O4KT).
When an excise duty rate changes, the inventory on which excise duty was levied must be revaluated.
Previously you could revaluate this excise duty inventory as follows:
o

Based on the physical inventory count

Not based on the physical inventory count


You can calculate the new value of the excise duty inventory (that is, the value of the excise duty
inventory after the excise duty has been revaluated) for:
-

A combination of material, plant, and valuation type

The whole plant (collective processing)

The whole excise duty group (collective processing)

In-transit stock

Negative inventory

Effects on Existing Data


When you revaluate the excise duty inventory based on the physical inventory count, the system enters
temporary data in table OIH14. Before you upgrade to IS-Oil 4.7 this table must be empty, which means
that you must have completed all excise duty revaluations that are based on the physical inventory count.

______________________________________________________________
SAP AG

17

SAP System
______________________________________________________________

See also
For more information, see SAP Note 609703.

1.3.8.3 User Exits for Default Values and Validation (Enhanced)


Use
As of SAP Oil & Gas 4.72, you can customize the following tables with user exits for default values and
validation:
o

Table OIH08 (Default values for purchasing)

Table OIH11 (Default values for sales)

1.3.9 IS-OIL-DS-TSW

Trader's and Scheduler's Workbench

1.3.9.1 Batch-Specific Movement Scenarios (New)


Use
As of SAP Oil & Gas 4.72, you can account for changes in product quality during the shipment process.
Trader's and Scheduler's Workbench (TSW) provides enhancements to movement scenarios, the
nomination process, and ticketing that allow the creation of batches during product shipment.
By creating a new batch during the nomination and ticketing processes, you can take into account product
quality changes that occur during shipment. When a shipment is complete, you can use the new batch to
capture measurements at the destination (the customer location for sales and the own company for
purchases).
Product quality changes can occur during shipment until the product is finally discharged at the
destination, such as the delivery location. At this point, the customer measures the product quality. The
TSW enhancement allows you to create a new batch during the shipment process to reflect these quality
changes.
Because the batch is often unknown during scheduling, the enhancement allows you to enter batch
information in tickets. You can also set up the system to automatically create batches during ticketing.
During ticketing in TSW, the movement scenario determines if a batch is a load batch or an origin batch.
The process is more streamlined because you do not have to return to the nomination to enter the batch
data before ticketing.
The enhancement also supports shipment processing where an in-transit plant is not assigned. By
manually or automatically creating a load batch, you can track product quality for each shipment and
vendor combination or shipment and customer combination.
Effects on Data Transfer
You enter batch information during nomination maintenance in the Item Details. You can enter the origin
batch, destination batch, and load batch. For destination and load batches you can select Create, so that

______________________________________________________________
SAP AG

18

SAP System
______________________________________________________________

during ticketing, the system creates a new batch (based on the movement scenario).
Alternatively, you enter batch information during ticketing on the Nomination Data tab page. You can
enter the origin batch, destination batch, and load batch.
Effects on System Administration
You can track batches by customer and delivery to support the processing of customer complaints.
However, managing complaints is a manual process and is not included in the enhancement. You can
create differential invoices to settle discrepancies in the product amount that are created by quality
changes.
Effects on Customizing
Only movement scenarios that are defined in Customizing can be used for scheduling a TSW nomination.
The movement scenarios in TSW are enhanced to allow shipments that involve the tracking of batches.
You can use the following movement scenarios to process shipments involving batches or create your
own movement scenarios (the codes for the movement scenarios are specified in parentheses):
o

Sale into In-Transit Location based on Sales Order (05)

Purchase into Destination based on Purchase Order (06)

Transfer into In-Transit Location based on Stock Transfer Order (15)

Transfer into Location based on Stock Transfer Order (16)

You define movement scenarios in Customizing for Industry Solution Oil & Gas (Downstream) -> TSW
(Trader's and Scheduler's Workbench) -> Nomination -> Basic Settings -> Customize TSW movement
scenarios.
You use the movement scenarios to handle the tracking of batches in combination with a Customizable
inbound process (CIP). The system uses the CIP during Ticketing to trigger document generation for the
tickets according to the movement scenario.
The Business Add-Ins (BAdIs) for nomination validation and ticket validation are enhanced so that the
system can validate nominations and tickets that include load batches. You can implement these BAdIs in
Customizing for Industry Solution Oil & Gas (Downstream) -> TSW (Trader's and Scheduler's
Workbench) -> Nomination -> Maintain Business Add-Ins for Nomination and Industry Solution Oil &
Gas (Downstream) -> TSW (Trader's and Scheduler's Workbench) -> Tickets -> Maintain Business
Add-Ins for Ticket Processing.

1.3.9.2 Batch-Specific Units of Measure (Changed)


Use
As of SAP Oil & Gas 4.72, you can convert the Unit of Measure (UoM) for a batch during scheduling
and stock projection. With the enhancement you can perform stock projection based on a base UoM and
on a batch-specific UoM.
Effects on Existing Data
You can set up the TSW master data and Stock Projection Worksheet (SPW) so that the system performs
UoM conversions based on the characteristics of a batch. For example in the mining industry, the base

______________________________________________________________
SAP AG

19

SAP System
______________________________________________________________

unit of measure (defined in the master data record of the material) is typically measured in wet ton (the
physical weight including moisture). However, sales are made based on the dry ton. The moisture content
is a batch characteristic and the UoM conversion from wet to dry ton uses the batch characteristic for the
UoM calculation.
In the SPW, the system calculates the starting inventory based on the UoM from the batch -specific
conversion. If the UoM that the system uses to calculate the SPW is batch -specific, the system corrects
all relevant document quantities in the SPW. When calculating the SPW, the system converts nomination
quantities, document quantities, and ticket quantities from the batch-specific UoM to the base UoM (and
vice versa), taking into account the characteristics of the specified batch.
The SPW by batch shows the SPW for a location, material, and batch combination. This means that the
system uses the book inventory for the specified batch as the starting inventory in SPW and only planned
or actual movements are shown in the SPW which involve that batch.

1.3.9.3 Bunker Consumption in Nominations and Tickets (New)


Use
As of SAP Oil & Gas 4.72, you can store a percentage value to represent the bunker consumption that
takes place during the transport of gas products. In the gas industry, a percentage of the product is burned
by the pumps used by the pipelines. You enter the percentage value for bunker consumption in freight
contracts along with the transportation fees and other terms and conditions.
In Trader's and Scheduler's Workbench (TSW), you account for bunker consumption in in the master
data records of transport systems, in nominations, and in tickets.
The enhancement supports the scheduling processes by making it possible for you to take bunker
consumption into account in nominations. The enhancement adds more flexibility to the ticketing
process, because the system creates sales orders, deliveries and goods issues for the carrier based on
consumption items. This step ensures the proper adjustment of the inventory and supports various
settlement scenarios with the carrier.
Effects on Existing Data
You can enter a percentage for bunker consumption in the TSW Details screen that you access from the
freight contract. The system captures the percentage for the bunker consumption of the transport system.
During nomination maintenance, the system generates line items to represent bunker consumption. You
can manually add nomination items to balance the demand or supply items against consumption line
items.
In nomination maintenance on the Mat. Balance (material balance) tab page, you can select Cons. Items
to generate line items that represent bunker consumption. When you select Cons. Items, the system
creates consumption lines for all demand items in the nomination header. If consumption line items
already exist, the system updates the consumption lines based on any changes.
You can assign TSW locations to transport systems as consumption-relevant locations.
Additional TSW movement scenarios are available to schedule shipments that involve bunker
consumption.
Using the consumption-relevant data from the freight contract, the TSW Worklist checks the
system-generated consumption items for nominations. In Customizing for the TSW Worklist, the reason

______________________________________________________________
SAP AG

20

SAP System
______________________________________________________________

codes I13 (Generate consumption item) and I14 (Update consumption item) are available for generating
worklist entries based on consumption lines in nominations.
You can manually change the scheduled quantity for consumption items in the nomination. If you delete
a nomination item, the system automatically deletes the corresponding consumption line item.
During ticket actualization, the system processes consumption lines from nominations. Before the system
performs ticket actualization, a customizable validation concept determines the check logic that the
system uses for consumption lines. A function group is available for ticket actualization. The system uses
the function group during ticketing to post the required SAP R/3 documents for the consumption lines.
Ticket validation, which occurs when you save or actualize a ticket, ensures that the system
simultaneously posts the line items from bunker consumption and their reference lines.
Using the ticket validation settings, you can specify the severity for the errors that result from the
actualization of tickets with references to consumption items.
Effects on Customizing
You define the movement scenarios for bunker consumption in Customizing for Industry Solution Oil &
Gas (Downstream) -> TSW (Trader's and Scheduler's Workbench) -> Nomination -> Basic Settings ->
Customize TSW movement scenarios.
You must assign the defined validation checks to validation groups. You define the validation groups for
tickets involving bunker consumption in Customizing for Industry Solution Oil & Gas (Downstream) ->
TSW (Trader's and Scheduler's Workbench) -> Define Validation Groups for Ticketing.
You define the settings that the system uses to generate worklist entries based on bunker consumption
during ticketing. You define worklist settings in Customizing for Industry Solution Oil & Gas
(Downstream) -> TSW (Trader's and Scheduler's Workbench) -> Basic Functions -> Worklist.
You define settings for ticket processing, including the validation checks for bunker consumption, by
implementing Business Add-Ins (BAdIs). You implement the BAdIs in Customizing for Industry
Solution Oil & Gas (Downstream) -> TSW (Trader's and Scheduler's Workbench) -> Tickets ->
Maintain Business Add-Ins for Ticket Processing.
To to assign a default TSW Location to a nomination item, you implement the BAdI in Customizing for
Industry Solution Oil & Gas (Downstream) -> TSW (Trader's and Scheduler's Workbench) ->
Nomination -> Maintain Business Add-Ins for Nomination -> Business Add-In to default the location for
bunker consumption.
You can implement a BAdI to generate nomination line items to represent bunker consumption during
scheduling in Customizing for Industry Solution Oil & Gas (Downstream) -> TSW (Trader's and
Scheduler's Workbench) -> Nomination -> Maintain Business Add-Ins for Nomination -> Business
Add-In to generate nomination items for bunker consumption.

1.3.9.4 Influencing Defaulting Logic in Ticket (New)


Use
As of SAP Oil & Gas 4.72, you can use a Business Add-In (BAdI) to adjust the defaulting logic in a
ticket. The system uses the data from the nomination or outbound documents as default values in a ticket.
You must add only the date and quantity.

______________________________________________________________
SAP AG

21

SAP System
______________________________________________________________

Effects on Customizing
To influence the defaulting logic in a ticket, in Customizing for the Industry Solution Oil & Gas
(Downstream), choose TSW (Trader's and Scheduler's Workbench) -> Tickets. Here, call the IMG
activity BAdI: Ticket Default Settings.

1.3.9.5 Selection Screen Defaults in Three-Way Pegging (Changed)


Use
As of SAP Oil & Gas 4.72, a new defaulting option is available in the selection screen of
Three-Way-Pegging. With this enhancement you can set up rules that the system uses to default data into
the Three-Way Pegging selection screen, such as to default all real locations assigned to a specified
planning location. You can choose a defaulting rule in the Three-Way Pegging selection screen and start
the defaufling by choosing the default button.
Effects on Existing Data
A filter-dependent Business Add-In (BAdI) is available to implement the defaulting rules. You
implement the filter-dependent BAdI in Customizing for Industry Solution Oil & Gas (Downstream) ->
TSW (Trader's and Scheduler's Workbench) -> Three-Way Pegging -> Maintain Business Add-Ins for
Three-Way Pegging -> BAdI: 3WP Selection Screen Defaulting .
The following defaulting rules are provided:
o

OIJ_DEAULT_BY_FCC: In the selection screen of Three-Way Pegging on the Transportation


Avails tab page, you can enter the document number for a freight contract, the document indicator
for a freight contract, and the document line item for a freight contract. By choosing the
OIJ_DEFAULT_BY_FCC rule, the system defaults material and location data from the TSW details
of the freight contract to the Three-Way Pegging selection screen.

OIJ_DEAULT_SUB_LOC: In the selection screen of Three-Way Pegging on the Demand Items,


Supply Avails, and Transportation Avails tab pages, you can enter planning locations. When you
choose the OIJ_DEFAULT_SUB_LOC rule, the system defaults all locations that correspond to the
planning locations and excludes the planning location itself.

1.3.9.6 Check of Global Tracking System from Nominations (New)


Use
As of SAP Oil & Gas 4.72, you can set up the R/3 System to perform checks during nomination
maintenance based on information from Global Trade Services (GTS). The oil and gas business is
performed on a global scale with products crossing national and international boundaries. As a result,
there are legal requirements within the industry to be able to show proof of the legality of trades that
involve the crossing of boundaries. Companies require this proof before a sale takes place.
When you save a nomination in Trader's and Scheduler's Workbench (TSW), the system checks if the

______________________________________________________________
SAP AG

22

SAP System
______________________________________________________________

customer or vendor in the nomination is part of the Sanctioned Party List (SPL) stored in the GTS server.
As a result, you can ensure that a business partner or customer is a valid partner prior to the sale of
product. If the vendor or customer does not pass the check, the system blocks ticket actualization and
thereby the shipment of product.
Effects on Existing Data
When you confirm a nomination item, the system automatically sets the HOLD (overall hold) status and
you cannot create a ticket for that nomination item until an authorized user clears the hold status.
When you save a nomination, the system checks the GTS status of the partner. When the results of the
GTS check determine that the the nomination item is assigned to a non-valid business partner, the system
automatically sets the status to XGTS (GTS hold flag).
An authorized user manually clears the hold status to allow the system to actualize the ticket by assigning
the status XHLD (clear HOLD flag for ticket).
Effects on Customizing
You activate the GTS check in Customizing for Industry Solution Oil & Gas (Downstream) -> TSW
(Trader's and Scheduler's Workbench) -> Nomination -> Basic Settings -> Specify nomination settings.
To activate the GTS partner check, choose GTS part. check.

1.3.9.7 Mass Change of Nominations (Enhanced)


Use
As of SAP Oil & Gas 4.72, you can process the header and item data of nominations that you previously
selected, in one go. You can also assign one or more events.

1.3.9.8 Event Updates in Nominations (Changed)


Use
As of SAP Oil & Gas 4.72, you can set up the R/3 System to update events in TSW nominations based on
the events in SAP Event Management.
Using the enhancement, you can track events in SAP Event Management that are maintained in TSW
nomination line items, as well as update nomination line items in TSW nominations based on events
reported by SAP Event Management.
You can also report the events through the Internet using the Web communication layer (WCL). For
example, you have created a nomination to schedule a shipment of crude oil by a marine vessel from an
origin location to a destination location. When you create the nomination, you create an event for the
destination line item that represents the estimated time of arrival (ETA). If there is a delay, the carrier
updates the ETA by reporting a new arrival time in SAP Event Management. The system updates the
destination line item in the TSW nomination with the new ETA and updates the schedule date of the line
item. The system then updates the Stock Projection Worksheet according to the new ETA, that is, the
nomination appears in the Stock Projection Worksheet on the changed date.

______________________________________________________________
SAP AG

23

SAP System
______________________________________________________________

Effects on Customizing
In Customizing you can implement a Business Add-In (BAdI) to transfer event data from nominations to
an external event tracking or event management system. You do this in Customizing for Industry Solution
Oil & Gas (Downstream) -> TSW (Trader's and Scheduler's Workbench) -> Nomination -> Maintain
Business Add-Ins for Nomination -> Business Add-In for Event Manager processing.
See also
The following notes provide example templates for the Customizing related to event updates in
nominations:
Note 652749 (SCEM Customizing for IS-OIL)
Note 655670 (Update of Reported Events from SCEM Server to IS-Oil Nomination)
Note 659345 (Update of Reported Events from SCEM WCL to IS-Oil Nomination)

1.3.9.9 Update of Reference Documents Based on Nominations (New)


Use
As of SAP Oil & Gas 4.72, you can ensure that scheduling data is more accurate by eliminating the
discrepancies between the scheduling documents in TSW (nominations) and the reference documents in
SAP Advanced Planner and Optimizer (APO), such as stock transfer orders or stock transfer requisitions.
Effects on Data Transfer
APO takes into account standard documents, such as purchase orders, sales orders, and stock transport
orders. Before the enhancement was available, TSW nominations and the corresponding reference
documents were not always synchronized. For example, the schedule date in the order could be different
from the scheduled shipment date in the nomination. You can also schedule items from one reference
document using multiple nominations or multiple nomination line items with different dates.
With this enhancement, the system updates the referenced documents for the schedule line item or item
level. If you activate the integration model, the system transfers updates, such as the schedule date and
quantity, to APO. As a result, the reference document in APO and the TSW nomination are synchronized.
The system updates the following types of reference documents:
o

Sales orders

Purchase orders

Purchase requisitions

Stock transfer orders

Stock transfer requisitions

______________________________________________________________
SAP AG

24

SAP System
______________________________________________________________

1.3.9.10 Consumption of Document Quantities Without Nominations (Changed)


Use
As of SAP Oil & Gas 4.72, you can make sales orders and purchase orders relevant for the Stock
Projection Worksheet (SPW) by assigning the stock projection relevance to the document type. With the
enhancement, you can make sales and purchase orders relevant for stock projection, even when the
documents are not relevant for scheduling in a nomination. As a result, the system does not use
nominations to consume the quantities from outstanding orders in the SPW. When using the
enhancement, the system does not consume the outstanding order quantities in the SPW. When
calculating the projected inventory, the SPW takes into account the consumption of quantities from sales
and purchase orders based on goods movements for these orders.
Effects on System Administration
When you post goods issues or goods receipts, the system does not perform a real -time update of the
SPW header or inventory column. Rather, the system calculates the consumption of sales and purchase
quantities when generating the SPW.
Effects on Customizing
In Customizing for the stock projection parameters, you can choose DocsCnsumption so that sales orders
and purchase orders are consumed in the SPW by corresponding goods issues or goods receipts. This may
happen in the SPW if the scheduler does not schedule a nomination referencing an order, but instead
books a goods movement directly (outside TSW). If this indicator is not set, orders in the SPW are
consumed only by a nomination. You do this in Customizing for Industry Solution Oil & Gas
(Downstream) -> TSW (Trader's and Scheduler's Workbench) -> Stock Projection -> Specify
parameters for stock projection.
You implement a filter-dependent Business Add-In (BAdI) that determines if the system is to consume
(deduct or add) the quantity of an order item as the result of a goods movement. The filter value of this
BAdI is the stock projection relevance of the order item. You implement the BAdI in Customizing for
Industry Solution Oil & Gas (Downstream) -> TSW (Trader's and Scheduler's Workbench) -> Stock
Projection -> Maintain Business Add-Ins for Stock Projection -> Business Add-In for stock projection
relevance.
The BAdI method OIJ_SPREL_GIGR_CONSUMPT determines if an order item shall be consumed by a
goods movement or not. You implement the BAdI methods OIJ_SPREL_03 (Consumption of SD orders
by goods movements) and OIJ_SPREL_04 (Consumption of MM orders by goods movements) to make
sales orders and purchase orders relevant for the enhancement.

1.3.9.11 Long-Term Planning and Nomination Breakdown (Changed)


Use
As of SAP Oil & Gas 4.72, you can define nominations from a high-level plan to a more precise schedule
of smaller time intervals (nomination breakdown). Often, nominations are initially created for a long-term
plan, such as monthly or daily. The enhancement to Trader's and Scheduler's Workbench (TSW) allows
you to create a more detailed schedule by breaking the nomination down to a more detailed level, such as
a daily or an hourly plan.

______________________________________________________________
SAP AG

25

SAP System
______________________________________________________________

Using the enhancement you can start scheduling using a high-level plan and gradually create a more
precise shipment schedule by splitting nominations into smaller time periods. To do this, you maintain
high-level nominations, which are like forecasts, as simulation figures in the Stock Projection Worksheet
(SPW).
When publishing the simulation (what-if) nominations, the system uses a breakdown rule to divide the
nomination into smaller time periods. The breakdown rule defines how the system breaks down the
simulation nomination.
Effects on Existing Data
When publishing simulation nominations to real nominations, you have the option to perform a
breakdown of the nomination prior to the publishing process. When you choose Publish with breakdown,
a dialog box appears in which you choose a breakdown rule.
Effects on Customizing
In Customizing you define the breakdown rules which are used to divide the simulation nomination items
into smaller time periods. When you publish high-level simulation nominations, the system uses the
breakdown profile.
You implement a filter-dependent Business Add-In (BAdI) to create breakdown routines for schedule
items. The system uses the breakdown routines when you publish scheduled items from the What-If
Pop-Up of the Stock Projection Worksheet to nominations (publish with breakdown). You implement the
BAdI in Customizing for Industry Solution Oil & Gas (Downstream) -> TSW (Trader's and Scheduler's
Workbench) -> Stock Projection -> Maintain Business Add-Ins for Stock Projection -> Business Add-In
to define breakdown routines for schedule items.
You can implement a BAdI to define additional rules for what-if disaggregation. The BAdI provides the
method WHATIF_DISAGG_RULE. You implement the BAdI in Customizing for Industry Solution Oil
& Gas (Downstream) -> TSW (Trader's and Scheduler's Workbench) -> Stock Projection -> Maintain
Business Add-Ins for Stock Projection -> Business Add-In for what-if type disaggregation rule.

1.3.9.12 Updating Reference Documents (New)


Use
As of SAP Oil & Gas 4.72, reference documents that are dependent on a changed nomination are
automatically updated when you change the quantity or date in the nomination items and then save the
nomination.
Effects on Customizing
If you want the reference documents to be automatically updated, you have to make the following
settings in Customizing for the Industry Solution Oil & Gas (Downstream). In the IMG activity Specify
TSW control parameters, you have to set the Ref. Doc. Update indicator. Also, in the IMG activity Define
Reference Document Update , you must define the document types that are to be automatically updated.

______________________________________________________________
SAP AG

26

SAP System
______________________________________________________________

1.3.9.13 Additional Reference Documents in Scheduling (Changed)


Use
As of SAP Oil & Gas 4.72, you can schedule shipments based on the following types of reference
documents:
o

Purchase requisitions

Reservations

Stock transfer requisitions

Regardless of whether you create these documents in SAP Advanced Planner and Optimizer (SAP APO)
or in the SAP R/3 System, the enhancement allows you to schedule shipments based on these document
types by assigning them to nominations in Trader's and Scheduler's Workbench (TSW).
The enhancement also provides a more complete integration with APO by allowing you to schedule
nominations based on purchase requisitions, reservations, and stock transfer requisitions that are
generated in APO.
Effects on Existing Data
In TSW, you use document indicators to differentiate between the document types that you assign to
nominations during scheduling. In Customizing, document indicators and the assigned schedule item
types define a TSW movement scenario.
In Customizing, document indicators are now provided for purchase requisitions and stock transfer
requisitions, as well as movement scenarios based on these document types.
The enhancement also enables you to assign existing reservations, such as reservations generated in APO,
to nominations. Before this enhancement, the system created reservations during the ticketing process,
but you could not assign the reservations to nominations during scheduling.
Effects on Customizing
You must define movement scenarios in Customizing to schedule shipments using TSW nominations.
Among other settings, the values you enter for the schedule item type, reference document indicator, and
book transfer define the movement scenario. You can now select document indicators for purchase
requisitions (document type code Q) and stock transfer requisitions (document type code U). You do this
in Customizing for Industry Solution Oil & Gas (Downstream) -> TSW (Trader's and Scheduler's
Workbench) -> Nomination -> Customize TSW movement scenarios.
You can use the following movement scenarios defined in Customizing to schedule shipments using
purchase requisitions and stock transfer requisitions (the codes for the movement scenarios are specified
in parentheses):
o

Purchase into transport system at location (31 and 32)

Purchase requisition into location (33)

Stock transport from location into transport system (34 and 35)

Stock transport from transport system into location (36)

______________________________________________________________
SAP AG

27

SAP System
______________________________________________________________

1.3.9.14 Ticket Validation (New)


Use
As of SAP Oil & Gas 4.72, when you save a ticket, it is automatically validated at header and item level.
Ticket events and the ticket header are also validated against all items and events.
Effects on Customizing
To ensure that tickets are validated, you must use one or more of the following Business Add-Ins (BAdIs)
in Customizing for the Industry Solution Oil & Gas (Downstream) by choosing TSW (Trader's and
Scheduler's Workbench) -> Tickets:
o

BAdI: Ticket Header Validation

BAdI: Ticket Item Validation

BAdI: Ticket Event Validation

BAdI: Ticket Validation with Complete Data

If you have used one or more BAdIs, you must activate each validation by entering them in a validation
group in the IMG activity Define Validation Groups for Ticketing.

1.4 IS-OIL-PRA

Production and Revenue Accounting

1.4.1 PRA Archiving (New)


Use
As of SAP Oil & Gas 4.72, Production and Revenue Accounting (PRA) includes archiving objects that
allow you to create and store archive files with data from the SAP R/3 System resulting from business
processes that, once complete, no longer require the data.
PRA Archiving contributes to the optimization of system performance by reducing the amount of data
within the system. System administrators can use the archiving objects as frequently as necessary to
manage system performance.
PRA Archiving includes the following archiving objects:
o

Production Object

This allows you to archive data from measurement point volumes and measurement document tables.
In addition, the production object allows you to archive well completion volume data for which the
delivery network is successfully closed and posted, and for which the reports (for a particular delivery
network and sales date combination) are finalized in both the Tax & Royalty and the Regulatory
Reporting application components.
After the system archives well completion volumes, it changes the status of the delivery network to
archived to prevent the Contractual Allocation and Valuation application components from processing
the delivery network. The network can be processed again if well completion volumes are regenerated

______________________________________________________________
SAP AG

28

SAP System
______________________________________________________________

using manually entered measurement point volumes, well completion downtime data, and well test data.
o

Contractual Allocation Object

This allows you to archive measurement point and well completion allocated volumes after the Valuation
application component uses the volumes and the balancing report is finalized.
o

Ownership Object

This allows you to archive ownership transfer documents.


o

Valuation Object

This allows you to archive combined run information, which provides an overview of allocation results,
for a Valuation document. After the system posts a Valuation document successfully, it deletes the
document.
o

Tax Reporting Object, and Royalty Reporting Object

This allows you to archive data in the tax reporting history tables, or the royalty reporting history tables,
for a particular month after the reporting data is finalized for that month.
o

Journal Entry Object

This allows you to archive journal entries posted in the general ledger history table after offsetting entries
are posted and all the records total zero.
Note:
PRA Archiving does not include data that is needed for prior period adjustment (PPA) purposes.

Effects on Customizing
In the Archiving Object transaction AOBJ, you select the archiving object from the overview screen and
then choose Customizing Settings to specify the maximum file size.
Ownership Customizing for Archiving
In the Owner Request Global Settings activity (Industry Solution Oil & Gas (Production and Revenue
Accounting) -> Ownership -> Owner Request -> Owner Request Global Settings), in the Retn. for Arch.
field, you specify the number of days that ownership transfer data should be retained in the system for
archiving.

1.4.2 Business Info. Warehouse - Removal of technical objects (Deleted)


Use
As of SAP Oil & Gas 4.72, all technical references for the Business Information Warehouse (BW
RS_BCT_OI_EP objects) have been removed: extractors, structures, and all other Business Information
Warehouse (BW) objects. These objects were in the PRA system solely as examples. They have been
removed in the development system for SAP Oil & Gas 4.72, and in the Business Information Warehouse
System.

______________________________________________________________
SAP AG

29

SAP System
______________________________________________________________

1.4.3 Removal of Obsolete PRA DDIC Objects and Coding (Deleted)


Use
As of SAP Oil & Gas 4.72, a number of Data Dictionary objects (DDIC objects and tables) have been
removed from Production and Revenue Accounting (PRA), due to the fact that these objects have become
redundant or obsolete, and thus no longer need to be supported in PRA. Removal of the objects improves
database memory, and can improve performance, because tables with large data volumes have been
removed.
Removal of the tables can result in the data being unavailable (however, the data still will exist in the
system, outside of the tables that were deleted).
The following types of objects have been removed:
- Obsolete system tables
- Obsolete application tables
- Obsolete DDIC objects
- Superfluous ABAP objects
In addition, coding changes have been made, to remove coding that had become superfluous.
CSN Note 506871 lists the PRA objects which have been removed.

1.4.4 IS-OIL-PRA-EIA
1.4.4.1 IS-OIL-PRA-EIA-UG

Energy Integration Architecture / Upstream Graphics


Upstream Graphics

1.4.4.1.1 Upstream Graphics Bitmap/Icon Maintenance (Changed)


Use
As of SAP Oil & Gas 4.72, you can use the following transactions to maintain Upstream Graphics icons
and bitmaps:
o

Download Upstream Graphics Icons/Bitmaps

Upload Upstream Graphics Icons/Bitmaps

Maintain Upstream Graphics Icons/Bitmaps

You can access the transactions from the SAP Easy Access menu by choosing Logistics -> Production
and Revenue Accounting -> Tools -> Upstream Graphics Icons/Bitmap Maintenance.
Previously, Upstream Graphics icons and bitmaps were maintained with the Download icons/flash forms
transaction under Logistics -> Production and Revenue Accounting -> Tools. The Download icons/flash
forms transaction is no longer available, and its functions have now been separated into the icon/bitmap
maintenance transactions listed above.

______________________________________________________________
SAP AG

30

SAP System
______________________________________________________________

1.4.5 IS-OIL-PRA-PRD

Production

1.4.5.1 Changed Numbering/Naming of Producing Entity Field (Changed)


Use
As of SAP Oil & Gas 4.72, the producing entity Field no longer has a Revenue Integration limitation on
its numbering / naming. Before this change, the field could only be three bytes long if Revenue
Integration was activated. Now, the field is 10 bytes (characters/digits).
However, if you are upgrading to 4.72 (R/3 Enterprise) with existing PRA installations, you will need to
carry out a manual task. You will have to reconfigure or reassign the number range interval for fields.
You can do this in the IMG. You do that by choosing:
PRA -> Production -> Maintain Number Range Intervals -> Interval Maintenance (General).
You then select the following entries:
Field - Internal Numbering
Field - External Numbering
The old number range intervals have to be reused. After that, you can extend the upper limit of the
number range interval to the 10-character or 10-digit maximum. That way, you will not have duplicates in
your system.
If you have existing PRA installations, and are upgrading to 4.72/R/3E, it is necessary that you do that in
order to create new fields.

1.4.6 IS-OIL-PRA-REP

Reporting

1.4.6.1 Flashform Maintenance (Changed)


Use
As of SAP Oil & Gas 4.72, the flashforms maintenance transaction has been changed. The transaction,
"Download icons/flashforms" has been divided into three separate transactions in the SAP Easy Access
menu:
- Download Reporting Flashforms
- Upload Reporting Flashforms
- Maintain Reporting Flashforms
The flashforms transaction was removed from the Tools section of the SAP Easy Access menu, and
divided into three separate transactions, which were put into the Production, Tax and Royalty Reporting
section of the SAP Easy Access menu.
There is no change in the functionality of the transaction.

______________________________________________________________
SAP AG

31

SAP System
______________________________________________________________

1.4.6.2 IS-OIL-PRA-REP-REG

Regulatory Reporting

1.4.6.2.1 Texas P1, P1B, P2 and Combined Reports (New)


Use
As of SAP Oil & Gas 4.72, you can use the Texas P1, P1B, P2, and the Combined Report (CBN Report)
to report oil and gas volume dispositions to the Texas Railroad Commission (Texas RRC), based on the
reporting month.
The reports use the Production Regulatory Report "Framework" transaction, which is the standard,
centralized PRA Production Regulatory Reporting tool. You can set up the necessary master data
(Regulatory IDs, which represent specific wells) and then process the reports in the Framework.
Current or amended reports can be set up and processed. The basic reporting unit for all the reports is the
well completion. Reporting is carried out per district.
P1 Report
You can use the P1 Report to report oil dispositions and gas dispositions. For oil dispositions, you can
report: pipeline, truck, sedimentation, skim, and scrubber dispositions. For gas, you can report: lease fuel
system, transmission line, processing plant, vented or flared, lift, pressure, and underground store
dispositions. You can also enter general comments for the P1 Report.
P1B Report
You can use the P1B Report to report oil lease volume dispositions, as well as gas dispositions, including
beginning and ending inventories. You can designate the P1-B report as partially unitized, and you can
designate a "special project" that the well completion belongs to for the P1B Report.
P2 report
You can use the P2 Report to report gas volumes (gas dispositions) and condensate volumes
(dispositions), for specific leases. A gas ID number from the Texas RRC is needed for the P2 Report.
Combined Report (CBN)
You can use the Combined Report to report all the Well Completion Regulatory IDs for all three reports.
The report reports on volumes per operator, month, and year. The Combined Report is an aggregation of
Current Finalized versions of all the three reports, or any of the three reports.
For all the reports (other than the Combined Report), you can run the report either in current or amended
mode. For an amended report, the production month and reporting month are not the same, whereas for
the current report, they are the same. The amended report obtains all the reallocated well completions
from table OIUREP_RWC. Then, the reallocated well completions are processed like the current report.
The Texas P-1, P-1B and P-2 reports can be run separately, and viewed. When the Combined Report is
run, all the three processes will be run. Smartforms for Texas P-1, P-1B and P-2 Reports exist to display
the output as hardcopy (on paper).
Tools are available to migrate the Regulatory IDs and to migrate the RWC entries. The resulting reports
can be customized.

______________________________________________________________
SAP AG

32

SAP System
______________________________________________________________

Effects on Customizing
The following fields can be customized:
- Gas RRC ID
- P1B RRC lease
- Partially unitized
To customize these fields, in the IMG, choose: Industry Solution Oil & Gas (PRA) --> Production, Tax
and Royalty Reporting --> Regulatory/Production Reporting --> Regulatory Reporting Master Data
Setup.
The major product code to volume type cross reference can be customized by choosing: Industry Solution
Oil & Gas (PRA) --> Production, Tax and Royalty Reporting --> Regulatory/Production Reporting -->
Regulatory Reporting Major Pd Code / Volume Type Mapping.
The disposition codes for volume types can be customized by choosing: Industry Solution Oil & Gas
(PRA) --> Production, Tax and Royalty Reporting --> Regulatory/Production Reporting --> Regulatory
Reporting Customizing.

1.4.6.2.2 Multiple Well Statuses for MMS-OGOR Reporting (Changed)


Use
As of SAP Oil & Gas 4.72, you can assign more than one status to a well in the PRA system, for
production regulatory reporting.
Previous to this change, it was only possible to have one status per well, although a well could have more
than one actual function, such as producing, down for repair, injecting, and so on. It is a Minerals
Management Service (MMS) requirement to list the status for each function and to print all the statuses.
In the PRA system, you can now have more than one status for a well, based on separate products and
volume types. You can have, for example, one status for oil for a well, and another status for condensate.

1.4.6.3 IS-OIL-PRA-REP-TAX

Tax Reporting

1.4.6.3.1 New Mexico and Wyoming Tax Reporting and Tax Data Migration
(New)
Use
As of SAP Oil & Gas 4.72, Production and Revenue Accounting includes development that migrates New
Mexico and Wyoming tax data into the existing tax reporting framework, based on the last finalization
reporting year and month.
After the required data is migrated, you can carry out reporting in the new framework for all subsequent
months.

______________________________________________________________
SAP AG

33

SAP System
______________________________________________________________

The development provides a means for complying with the legal tax requirements for New Mexico and
Wyoming tax reporting.
Limitations of the New Mexico Tax Data
Data for the New Mexico report is provided only with an intermediate file, not with an EDI/CSV file.
Further, the system supports only the following tax types for New Mexico (the corresponding system tax
type codes are noted in parentheses):
o

Ad Valorem (AV)

Conservation Tax (CN)

Emergency School Tax (ES)

Severance Tax (SV)

Limitations of the Tax Reporting Migration Transactions


The SAP PRA Tax Reporting migration transactions are not designed for data conversions; they are
meant to be used only to move data from the old tax reporting framework to the new tax reporting
framework.
Override Affiliation Codes for New Mexico
The Set Up Agency Specific Cross References transaction is now available in the SAP Easy Access menu
(Logistics -> Production and Revenue Accounting -> Production, Tax and Royalty Reporting -> Tax
Reporting -> New Tax Reporting -> Set Up Agency Specific Cross References) for you to set up override
affiliation codes for New Mexico.
New Mexico and Wyoming Tax Reporting Features
The New Mexico and Wyoming tax reporting features provided with the SAP Oil & Gas 4.72
development replace those used in previous SAP Oil & Gas releases. The following list provides details
about the new New Mexico and Wyoming tax reporting features, and the corresponding features that they
replace.
o

New Mexico Tax Detail by PUN Number

Oil & Gas 4.72


Current as of: October 2003
Framework: New
Report ID: PUN
Previous Oil & Gas Release
Current as of: December 2001
Framework: Old
ABAP Report: TRBT662R
Tape File: TRBT6692
o

New Mexico OGT-2 - Tax Detail by Ownership Agreement and PUN

Oil & Gas 4.72


Current as of: October 2003

______________________________________________________________
SAP AG

34

SAP System
______________________________________________________________

Framework: New
Report ID: 132
File: Downloadable intermediate file for detail record provided
Previous Oil & Gas Release
Current as of: December 2001
Framework: Old
ABAP Report: TRBT663R
o

New Mexico Tax Detail by PUN Number and Ownership Agreement Number

Oil & Gas 4.72


Current as of: October 2003
Framework: New
Report ID: AGR
Previous Oil & Gas Release
Current as of: December 2001
Framework: Old
ABAP Report: TRBT664R
o

New Mexico Oil & Gas Tax Summary Report

Oil & Gas 4.72 (new with Oil & Gas 4.72; not part of a previous release)
Current as of: October 2003
Framework: New
Report ID: 131
o

Wyoming Form 2000 - Severance Tax (Oil)

Oil & Gas 4.72


Current as of: October 2003
Framework: New
Report ID: 200
File: Downloadable file provided
Previous Oil & Gas Release
Current as of: December 2001
Framework: Old
ABAP Report: TRBT592R
Tape File: TRBT592.EDIFILE
o

Wyoming Form 2002 - Severance Tax Incentive (Oil)

______________________________________________________________
SAP AG

35

SAP System
______________________________________________________________

Oil & Gas 4.72


Current as of: October 2003
Framework: New
Report ID: 202
File: Downloadable file provided
Previous Oil & Gas Release
Current as of: December 2001
Framework: Old
ABAP Report: TRBT594R
Tape File: TRBT594.EDIFILE
o

Wyoming Form 3000 - Severance Tax (Gas)

Oil & Gas 4.72


Current as of: October 2003
Framework: New
Report ID: 300
Current as of: December 2001
Previous Oil & Gas Release
File: Downloadable file provided
Framework: Old
ABAP Report: TRBT592R
Tape File: TRBT592.EDIFILE
o

Wyoming Form 3002 - Severance Tax Incentive (Gas)

Oil & Gas 4.72


Current as of: October 2003
Framework: New
Report ID: 302
File: Downloadable file provided
Previous Oil & Gas Release
Current as of: December 2001
Framework: Old
ABAP Report: TRBT594R
Tape File: TRBT594.EDIFILE
o

Wyoming Conservation Tax

______________________________________________________________
SAP AG

36

SAP System
______________________________________________________________

Oil & Gas 4.72


Current as of: October 2003
Framework: New
Report: 001
Previous Oil & Gas Release
Current as of: December 2001
Framework: Old
ABAP Report: TRBT588R
Effects on Existing Data
If there is existing data in the OIUX1_RPT_MSTRL table, before upgrading to SAP Oil & Gas 4.72, you
need to run program ROIUX2_CONVERT_LOG to update the existing data.

1.4.6.4 IS-OIL-PRA-REP-ROY

Royalty Reporting

1.4.6.4.1 Base Data Maintenance (Deleted)


Use
As of SAP Oil & Gas 4.72, the Base Data Maintenance transaction has been deleted from the Royalty
Reporting application component. You must now use the Master Maintenance transaction instead.
The Master Maintenance transaction is available from the SAP Easy Access menu under Logistics ->
Production and Revenue Accounting -> Production, Tax and Royalty Reporting -> Royalty Reporting ->
New Royalty Reporting Framework -> Master Maintenance.
Effects on Data Transfer
A customer-specific program might need to be modified if it is affected by the change from the use of the
Base Data Maintenance transaction to the use of the Master Maintenance transaction.

1.4.6.4.2 Royalty Reporting - Old Framework (Deleted)


Use
As of SAP Oil & Gas 4.72, beginning in January 2004, SAP no longer supports any royalty reports that
are in the old framework. (This announcement was published previously in the Royalty Reporting Data
Migration release note distributed with the SAP Oil & Gas 4.6C Service Pack 2 release.)
The following reports were part of the old framework and are no longer supported:
Generic Royalty Report
o

ABAP Report: TRBT610R

______________________________________________________________
SAP AG

37

SAP System
______________________________________________________________

Louisiana Royalty Reporting (Oil)


o

ABAP Report: TRBT837R

Louisiana Royalty Reporting (Gas)


o

ABAP Report: TRBT836R

New Mexico OGR-2 Oil and Gas Royalty Report by PUN No.
o

ABAP Report: TRBT677.RPT

New Mexico Oil and Gas Royalty Detail Report by Ownership Agreement and PUN No.
o

ABAP Report: TRBT678.RPT

New Mexico Oil and Gas Royalty Report by PUN No. and Ownership Agreement
o

ABAP Report: TRBT679.RPT

Texas GLO1 - Royalty Reporting (Oil) for Texas, A&M, and UT


o

ABAP Report: TRBT635R

Texas GLO1A - Royalty Reporting (Oil) for Texas, A&M, and UT


o

ABAP Report: TRBT640R

Texas GLO2 - Royalty Reporting (Gas) for Texas, A&M, and UT


o

ABAP Report: TRBT645R

Texas GLO2A - Royalty Reporting (Gas) for Texas, A&M, and UT


o

ABAP Report: TRBT650R

Texas GLO3 - Royalty Reporting (Oil) Summary for Texas, A&M, and UT
o

ABAP Report: TRBT625R1

Texas GLO3 - Royalty Reporting (Gas) Summary for Texas, A&M, and UT
o

ABAP Report: TRBT625R2

1.4.6.4.3 Oklahoma Royalty Report (Changed)


Use
As of SAP Oil & Gas 4.72, the Oklahoma Royalty Report for the Commissioners of the Land Office State of Oklahoma has been improved. A second page has been added to the report to display details of
the adjustments included on the first page of the report.
The details are organized by lease and sales month, and provide an overview of the following:
o

Gross net value

Royalty interest

______________________________________________________________
SAP AG

38

SAP System
______________________________________________________________

Royalty volume

Price

Royalty value

1.4.6.4.4 Royalty Reporting Cross References (New)


Use
As of SAP Oil & Gas 4.72, there are two new transactions in the Royalty Reporting application
component that you can use to set up various cross references in order to meet the requirements of
Louisiana and Texas royalty reporting.
With the Set Up Agency Category Code and Code Values transaction, (Logistics -> Production and
Revenue Accounting -> Production, Tax and Royalty Reporting -> Royalty Reporting -> New Royalty
Reporting Framework), you can set up the following cross references:
o

Field code and field name cross references for Louisiana reports

Allow you to display a field name in the report that is different from the field name maintained in the
Production application component.
o

Purchaser tax ID and purchaser number cross references for Texas reports

Allow you to specify the purchaser tax ID for each purchaser; Texas requires that both the ID and the
purchaser number be shown in the report.
Note: After you enter this type of cross reference, you must execute the Extraction and Reporting
transaction in order for the royalty report processing to be successful.
o

Purchaser Tax ID and contract number cross references for Texas reports

With the Set Up Code and Generic Values Dated transaction (Logistics -> Production and Revenue
Accounting -> Production, Tax and Royalty Reporting -> Royalty Reporting -> New Royalty Reporting
Framework), you can enter multiple Railroad Commission (RRC) lease numbers for non-operated
properties. The Texas General Land Office (GLO) report requires that all the RRC numbers for a lease be
shown in the report.

1.4.7 IS-OIL-PRA-REV

Revenue

1.4.7.1 Maintain Action Taken Codes (New)


Use

______________________________________________________________
SAP AG

39

SAP System
______________________________________________________________

As of SAP Oil & Gas 4.72, the IMG ' Maintain Actions Taken Codes' has been added to the IMG in PRA
Revenue. Action taken is the last action taken in order to resolve an outstanding balance. Owner balances
are monitored. For every owner balance to be monitored, you assign an action code to the amount, and
action date, and a follow-up date, if applicable.
The action taken code is the replacement for the PRA Common Table TBLRD023.

1.4.7.2 Valuation/Revenue Distribution - Old Version (Deleted)


Use
As of SAP Oil & Gas 472, SAP no longer supports the old version of Valuation/Revenue Distribution
(which relies on file-based processing). (This announcement was published previously in the
Valuation/RD Performance Improvements release note distributed with the SAP Oil & Gas 4.6C Service
Pack 2 release.)

1.4.7.3 IS-OIL-PRA-REV-CA

Contractual Allocation

1.4.7.3.1 CA Division Order Sales - Sales Point Method (New)


Use
As of SAP Oil & Gas 4.72, Production and Revenue Accounting includes a new allocation method based
on the existing Division Order Sales method for Contractual Allocation (CA). The new method, called
Division Order Sales - Sales Point:
o

Improves performance by allocating volumes only to sales points, and not to all the termination
points as the Division Order Sales method does.

Reduces the amount of data set up required for cross references. For large networks with common
ownership for volumes allocated from a sales point, you can maintain cross references at sales
points and not at termination points.

You use the Division Order Sales - Sales Point allocation method in the Delivery Network Dated
transaction.

1.4.7.4 IS-OIL-PRA-REV-CP

Contracts & Pricing

1.4.7.4.1 Oil Industry Pricing Terminology and Key Fields (Enhanced)

______________________________________________________________
SAP AG

40

SAP System
______________________________________________________________

Use
As of SAP Oil & Gas 4.72, Production Revenue Accounting provides enhancements to Oil Industry
Pricing Terminology and Key Words functions. The enhancements allow you to select an industry term,
such as equal daily quantity (EDQ) or Council of Petroleum Accounting Societies (COPAS), to be used
on the Conditions Display: Formula Terms screen within the Condition Records transaction. It also
involves the addition of key fields and corresponding descriptions to the header of the screen.
The Oil Industry Pricing Terminology and Key Fields development:
o

Reduces data entry by automatically inserting default values into the fields within the Calculation
Rules dialog box after you select an industry term. You can override these entries if required.

Helps you to identify the master data, relevant to the pricing you are maintaining, with master data
fields and corresponding descriptions in the header of the Conditions Display: Formula Terms
screen.

This development also includes the following key fields on the Conditions Display: Formula Terms
screen within the Condition Records transaction:
o

Contract

Well completion

Measurement point

Product

Effective from date

Effective to date

Effects on Customizing
This development includes a new Customizing activity (Industry Solution Oil & Gas (Production and
Revenue Accounting) -> Contracts and Pricing -> Define Industry Term Values for Pricing), which you
can use to specify an industry term and its corresponding default values. The system then inserts these
default values within the Calculation Rules dialog box after you select an industry term.

1.4.7.5 IS-OIL-PRA-REV-VAL

Valuation

1.4.7.5.1 Step Scale and Sliding Scale (Enhanced)


Use
As of SAP Oil & Gas 4.72, enhancements to step scale and sliding scale calculations enable you to use
sliding and step scales according to the Minerals Management Service's (MMS) regulations. They also
allow you to calculate step and sliding scales for residue materials.
The step scales are based on countable wells. For a gas step scale, a well is counted if it produces

______________________________________________________________
SAP AG

41

SAP System
______________________________________________________________

volumes. For oil, a well is counted if there are over 15 days of well production in a month.
An oil well is also considered counted according to the same criteria in an oil sliding scale. (For a gas
sliding scale, the concept of a countable well is not applicable.)
The step and sliding scale functions calculate average production per day, which the system uses as the
basis to arrive at the sliding/step royalty rate from the matrix maintained on the DOI Owner transaction.
The development provides enhanced logic for the Valuation batch jobs that affect the step scale and
sliding scale functions in SAP PRA used to determine royalty interest rates for individual non-working
interest owners.
In addition, you can use the new reserved word COUNTABLEWELLS to set up the number of countable
wells on a lease for a settlement diversity formula. This reserved word is meant to be used to override the
standard system calculation for countable wells.

1.4.7.5.2 Valuation with Alternative Dual Accounting (New)


Use
As of SAP Oil & Gas 4.72, Production and Revenue Accounting includes Valuation with Alternative
Dual Accounting functions, which enable you to use an alternative method for dual accounting by
generating the payments and reports required by the government for Indian ownership royalties.
Valuation with Alternative Dual Accounting:
o

Enables your company to use government-issued Indian index pricing

Allows you to customize data that the system uses when valuing Indian ownership royalties

The alternative method for dual accounting adjusts the price of gas before the valuation process. The
price adjustment depends on the relationship between the owners of the gas processing plant, and it also
depends on the applicable BTU range, based on the current Minerals Management Service (MMS)
pressure base (PSI) standard, which is 14.73 PSI.
Valuation with Alternative Dual Accounting provides the functions necessary for this alternative method
by using the following two new reserved words:
o

ADAPLOWN (Alternative dual accounting plant owners)

This reserved word indicates that the price multiplier represents gas plant interest ownership.
o

ADANONPL (Alternative dual accounting non-plant owner)

This reserved word indicates that the price multiplier does not represent gas plant interest ownership.

Effects on Customizing
Valuation with Alternative Dual Accounting allows you to customize BTU ranges and the corresponding
price multipliers, as well as date ranges and units of measure. For example, you can enter a price
multiplier for a gas plant owner and a price multiplier for a gas plant non-owner, where both price
multipliers correspond to a particular range of BTU values and a unit of measure.

______________________________________________________________
SAP AG

42

SAP System
______________________________________________________________

You enter the Customizing data in the Maintain Alternative Dual Accounting Price Multipliers activity
(Industry Solution Oil & Gas (Production and Revenue Accounting) > Valuation).

1.4.7.5.3 Settlement Statement Processing for System-Valued Properties (New)


Use
As of SAP Oil & Gas 4.72, Production and Revenue Accounting includes Settlement Statement
Processing for System-Valued Properties development that.
o

Allows you to use the system-valued revenue process code to create settlement statement - division
of interest (DOI) cross references, as well as settlement statements for system-valued properties.

Assists you in resolving issues you may encounter when closing your books.

This development provides a system-valued revenue process code among the codes that you can use to
generate the cross references and settlement statements. It also includes an option for you to specify that
the system should calculate taxes. (If you do not select this option, then you must enter the tax data
manually.)
If you enter tax data manually, it is assumed that the data has already been reported, and the system sends
the settlement statement directly to the Revenue Distribution application component.
After a settlement statement document is completed in the system, you can reverse it and thereby prevent
a double-booking.

1.4.7.6 IS-OIL-PRA-REV-CI

Check Input

1.4.7.6.1 Check Input Valuation and Posting (Enhanced)


Use
As of SAP Oil & Gas 4.72, Production and Revenue Accounting (PRA) includes the Check Input
Valuation and Posting enhancement. The enhancement includes transactions with which you can:
o

Process transmission files generated by Check Stub Data Exchange (CDEX)

Process checks and, if applicable, review the Combined Run Report for checks (the Combined Run
Report allows you to verify allocation results before posting them) with at least one Valuation
document that the system has valued successfully

Use a purchaser/property cross-reference to link check detail lines and journal entries that are
produced when the system books account receivable entries

Use a purchaser/property cross-reference to specify to whom incoming funds are distributed

Check Input Valuation and Posting provides the following benefits:

______________________________________________________________
SAP AG

43

SAP System
______________________________________________________________

Allows you to review and correct errors before posting them

Processes check documents concurrently and selectively

Processes each document independently, thereby reducing the possibility that any errors related to
one document will affect other documents

Promotes consistency between the Check Input, Valuation, and Revenue Distribution application
components because it minimizes the possibility that a document posted successfully in Check Input
will encounter errors in Valuation and Revenue Distribution

Includes a scheduling option that allows you to process a large number of checks during
off-peak hours

Includes comprehensive security functions that restrict access to Check Input features

Protects the integrity of a Check Input document with a locking mechanism that prevents concurrent
changes to the same document

Includes a feature to import or export check detail lines

You use the Check Input transactions to set up purchaser/property cross-references and to process check
documents that are relevant for a unique purchaser/property combination. Check Input processes
incoming checks for the following types of properties:
Check Input Property
The company using SAP Production and Revenue Accounting (PRA) is not the operator but has a
working interest ownership in the property, and the operator sends the check to the company for the
company's interest.
System-Valued Property
The company using SAP PRA is the operator and receives a check from the purchaser of the product sold.
Blanchard Property
This applies to operators in Oklahoma, who are required to pay all royalty interest owners irrespective of
burden groups.
Further, Check Input includes a value process as well as a post process. The value process does the
following:
o

Creates a cash batch with corresponding status information.

Creates a Valuation document, if applicable, that the system processes through Revenue Distribution
to produce both journal entries for posting and the Combined Run Report.

Reports system errors and results at the line item level, according to the purchaser/division of
interest cross-reference

The post process updates line item tables and posts journal entries to SAP FI.
The Check Input Valuation and Posting enhancements for SAP Oil & Gas 4.72 include the following
changes to the interface:
o

The CI Batch Control and CI Detail transactions (previously located in the SAP Easy Access menu
under Logistics -> Production and Revenue Accounting -> Revenue Accounting -> Check Input ->
Document Entry) have been removed. The functions from these transactions have been modified and
refined in the following new transactions:

______________________________________________________________
SAP AG

44

SAP System
______________________________________________________________

PRA Payment Posting Desktop transaction (Logistics -> Production and Revenue Accounting
-> Revenue Accounting -> Check Input -> Document Entry)

Processing Checks in Mass transaction (Logistics -> Production and Revenue Accounting ->
Revenue Accounting -> Check Input -> Periodic Processing -> Processing Checks in Mass)

The CI Journal Entry Generation transaction (previously located in the SAP Easy Access menu
under Logistics -> Production and Revenue Accounting -> Revenue Accounting -> Check Input ->
Period Processing) has been removed. The functions from this transaction have been modified and
refined in the PRA Payment Posting Desktop transaction.

The CI Batch Copy/Reverse transaction (previously located in the SAP Easy Access menu under
Logistics -> Production and Revenue Accounting -> Revenue Accounting -> Check Input -> Period
Processing) has been removed.

The Remitter/DOI Cross Reference transaction (previously located in the SAP Easy Access menu
under Logistics -> Production and Revenue Accounting -> Revenue Accounting -> Check Input ->
Master Data -> Remitter/DOI Cross Reference) has been removed and replaced by the Purchaser to
Property/DOI XRef transaction (Logistics -> Production and Revenue Accounting -> Revenue
Accounting -> Check Input -> Master Data -> Purchaser to Property/DOI Xref).
In addition to the features in the Remitter/DOI Cross-Reference transaction, the new Purchaser to
Property/DOI Xref transaction also has fields available to enter special distribution data required
for situations when a company receives multiple remittances that must be distributed according to
different distribution rules within the same division of interest.

The CDEX Workplace transaction (Logistics -> Production and Revenue Accounting -> Revenue
Accounting -> Check Input -> Document Entry -> CDEX Workplace) replaces and refines the
functions from the following transactions, which have been removed:
-

Modify Check Purge transaction (previously located under Logistics -> Production and
Revenue Accounting -> Revenue Accounting -> Check Input -> Master Data)

CI Check Purge transaction, Inbound CDEX Report, and the Inbound CDEX transaction, all
previously located under Logistics -> Production and Revenue Accounting -> Revenue
Accounting -> Check Input -> Periodic Processing

The Incoming Check A/R and Price Variance report and the Suspended Line Items message report
used to be available in the Report Viewer (Logistics -> Production and Revenue Accounting ->
Revenue Accounting), but are now available under Logistics -> Production and Revenue Accounting
-> Revenue Accounting -> Check Input -> Reports.
The Incoming Check A/R and Price Variance report provides a warning to the user that the unit
price or net receivable calculated in Check Input processing is outside of the user-defined tolerance.
(The net receivable tolerance is established in TBLCI016, while the price tolerance is established by
product code in TBLCI002.)
The Suspended Line Items message report provides information about Check Input line items that
cannot be posted or processed successfully.
Note:
There will be no transactions for migrating data from the old Check Input solution to the new Check
Input solution.

______________________________________________________________
SAP AG

45

SAP System
______________________________________________________________

Effects on Existing Data


o

Master data must be migrated from some common tables to new Check Input as follows:
-

Master data from common tables TBLCI007 (CDEX ID/Owner to Remitter Number
Translation) and TBLCI008 (CDEX ID/Owner to Company XRef Translation) must be
migrated to OIUCI_CDEX_REMX.

Master data from common table TBLCI010 (CDEX ID, CDEX Prod, Remitter XRef) must be
migrated to OIUCI_CDEX_PRDX.
Note: Customers must build their own utility program to migrate the data.

Before upgrading to the new Check Input solution, any checks in the old system that are open must
be closed. You cannot transfer existing open checks into the new Check Input solution.

Master data from table OIUH_RV_PDX (Remitter/DOI Cross Reference) will not be automatically
migrated. Customers must write their own utility to migrate data if necessary.

Effects on Data Transfer


Any customer-specific program might need to be modified if such a program involves now-obsolete
transactions CI Batch Control CI Detail, and/or Remitter/DOI Cross Reference.
Effects on System Administration
The authorization object O_OIU_TXN is available for a system administrator to use in order to control
the following activities in the PRA Payment Posting Desktop (the activity codes and descriptions are
listed):
o

01 - Create

02 - Change (applicable for toggling in the transaction between display and edit mode)

03 - Display (applicable for toggling in the transaction between display and edit mode)

06 - Delete

10 - Process

16 - Execute

69 - Write off line item

71 - Booked documents

A5 - Combined Run report

Effects on Customizing
In order to use the Check Input Valuation and Posting Process, there is a new number range for
Valuation documents that must be set up in Customizing under Industry Solution Oil & Gas (PRA) ->
Revenue Accounting -> Valuation -> Maintain Number Range for Valuation Document.
The Check Input application component no longer uses the settlement statement number range to generate
Valuation documents. Instead, the Check Input application component uses the new number range to
generate Valuation documents.

______________________________________________________________
SAP AG

46

SAP System
______________________________________________________________

1.4.7.7 IS-OIL-PRA-REV-CW

Check Write

1.4.7.7.1 Checkwrite - Old Version (Deleted)


Use
As of SAP Oil & Gas 4.72, SAP no longer supports the old version of Checkwrite. (This announcement
was published previously in the Payment Processing, formerly known as Checkwrite release note
distributed with the SAP Oil & Gas 4.6C Service Pack 2 release.)
The Check Write Batch Run transaction, located in previous releases under Logistics -> Production and
Revenue Accounting -> Revenue Accounting -> Check Write, has been removed.

1.4.7.7.2 Payment Processing (Changed)


Use
Reports
As of SAP Oil & Gas 4.72, the following Payment Processing reports are available:
o

Exception Report

Master Payment Control Report

Taxes Withheld Report

Further, as of SAP Oil & Gas 4.72, the following Payment Processing reports are no longer available
since they are obsolete:
o

All error reports (*.errprt) and sysout (*.sysout) reports

Checkwrite Run Activity Report

Checkwrite Validities Report

Default Account Assignment Report

Minimum Suspense Report

Effects on Customizing
There is a new Customizing activity, Define Gross Volume States (Industry Solution Oil & Gas
(Production and Revenue Accounting) -> Revenue Accounting -> Payment Processing), that you can use
to specify by state whether the gross volume should be printed on a Bottomline file.

______________________________________________________________
SAP AG

47

SAP System
______________________________________________________________

1.4.7.8 IS-OIL-PRA-REV-JE

Journal Entry

1.4.7.8.1 Maintain Legend Codes (New)


Use
As of SAP Oil & Gas 4.72, the IMG activity "Maintain Legend Codes" has been added to the
Implementation Guide (IMG) for Journal Entry. Previously, it was part of the PRA Common Table.
The legend code indicates a payment/deduction type or special payment reason other than the usual PRA
payments, such as litigation. The information is passed through the Revenue Distribution (RD)
allocations process and incorporated into the journal entry for check stub information. You use a legend
code to define the reason for a special payment.
The default value is spaces, which represents the majority of the records, but some of the valid reasons
are:
- Lawsuit settlement
- Contract Buy-Out/Buy-Down
- Extraction Tax
The activity replaces the PRA Common Table TBLRV064.

______________________________________________________________
SAP AG

48

Potrebbero piacerti anche