RN_OIL_472_EN special edition

8/10/2019 RN_OIL_472_EN special edition

1/53

IS-OIL Industry Solution Oil

Release Notes

Release 4.72


2/53

Copyright 2002SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof 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 Serverare registered trademarks ofMicrosoft Corporation.

IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX, S/390, AS/400, OS/390, and

OS/400are registered trademarks of IBM Corporation.

ORACLEis a registered trademark of ORACLE Corporation.

INFORMIX-OnLine for SAP and InformixDynamic ServerTM

are registered trademarks of Informix Software

Incorporated.

UNIX, X/Open, OSF/1, and Motifare registered trademarks of the Open Group.

Citrix

, the Citrix logo, ICA

, Program Neighborhood

, MetaFrame

, WinFrame

, VideoFrame

, MultiWin

and otherCitrix 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.

JAVAis a registered trademark of Sun Microsystems, Inc.

JAVASCRIPTis a registered trademark of Sun Microsystems, Inc., used under license for technology invented andimplemented 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 AGin 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


3/53


4/53

1.3.8.1 Quantity Conversion and Excise Duty for Go

(MIGO) 16

1.3.8.2 Physical Inventory-Based Excise Duty Revaluation (Changed) 17

1.3.8.3 User Exits for Default Values and Validation (Enhanced) 18

1.3.9 IS-OIL-DS-TSW Trader's and Scheduler's Workbench 18

1.3.9.1 Batch-Specific Movement Scenarios (New) 18

1.3.9.2 Batch-Specific Units of Measure (Changed) 19

1.3.9.3 Bunker Consumption in Nominations and Tickets (New) 20

1.3.9.4 Influencing Defaulting Logic in Ticket (New) 21

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

1.3.9.6 Check of Global Tracking System from Nominations (New) 22

1.3.9.7 Mass Change of Nominations (Enhanced) 23

1.3.9.8 Event Updates in Nominations (Changed) 23

1.3.9.9 Update of Reference Documents Based on Nominations (New) 24

1.3.9.10 Consumption of Document Quantities Without

(Changed) 24

1.3.9.11 Long-Term Planning and Nomination Breakdown (Changed) 25

1.3.9.12 Updating Reference Documents (New) 26

1.3.9.13 Additional Reference Documents in Scheduling (Changed) 26

1.3.9.14 Ticket Validation (New) 27

1.4 IS-OIL-PRA Production and Revenue Accounting 28

1.4.1 PRA Archiving (New) 281.4.2 Business Info. Warehouse - Removal of tech

(Deleted) 29

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

1.4.4 IS-OIL-PRA-EIA Energy Integration

Upstream Graphics 30

1.4.4.1 IS-OIL-PRA-EIA-UG Upstream Graphics 30

1.4.4.1.1 Upstream Graphics Bitmap/Icon Maintenance (Changed) 30

1.4.5 IS-OIL-PRA-PRD Production 31

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

1.4.6 IS-OIL-PRA-REP Reporting 31

1.4.6.1 Flashform Maintenance (Changed) 31

1.4.6.2 IS-OIL-PRA-REP-REG Regulatory Reporting 32

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

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

1.4.6.3 IS-OIL-PRA-REP-TAX Tax Reporting 33

1.4.6.3.1 New Mexico and Wyoming Tax Reporting and T

(New) 33

1.4.6.4 IS-OIL-PRA-REP-ROY Royalty Reporting 37

1.4.6.4.1 Base Data Maintenance (Deleted) 37

______________________________________________________________

SAP AG iv

SAP System Table of Contents SAP AG______________________________________________________________


5/53

1.4.6.4.2 Royalty Reporting - Old Framework (Deleted) 37

1.4.6.4.3 Oklahoma Royalty Report (Changed) 38

1.4.6.4.4 Royalty Reporting Cross References (New) 39

1.4.7 IS-OIL-PRA-REV Revenue 39

1.4.7.1 Maintain Action Taken Codes (New) 39

1.4.7.2 Valuation/Revenue Distribution - Old Version (Deleted) 40

1.4.7.3 IS-OIL-PRA-REV-CA Contractual Allocation 40

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

1.4.7.4 IS-OIL-PRA-REV-CP Contracts & Pricing 40

1.4.7.4.1 Oil Industry Pricing Terminology and Key Fields (Enhanced) 40

1.4.7.5 IS-OIL-PRA-REV-VAL Valuation 41

1.4.7.5.1 Step Scale and Sliding Scale (Enhanced) 41

1.4.7.5.2 Valuation with Alternative Dual Accounting (New) 42

1.4.7.5.3 Settlement Statement Processing for System

(New) 43

1.4.7.6 IS-OIL-PRA-REV-CI Check Input 43

1.4.7.6.1 Check Input Valuation and Posting (Enhanced) 43

1.4.7.7 IS-OIL-PRA-REV-CW Check Write 47

1.4.7.7.1 Checkwrite - Old Version (Deleted) 47

1.4.7.7.2 Payment Processing (Changed) 47

1.4.7.8 IS-OIL-PRA-REV-JE Journal Entry 48

1.4.7.8.1 Maintain Legend Codes (New) 48

______________________________________________________________

SAP AG v

SAP System Table of Contents SAP AG______________________________________________________________


6/53

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

o Under Petroleum Measurement Standards -> Quantity Conversion Interface (QCI) Configuration

-> Business Add-Ins:

- BAdI: Customer-Specific Parameter HandlingIndustry 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 UnderDocument 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

o Under Payment Card Handling -> Complaint Processing:

- Maintain Complaint Result on Company Code Level

o 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

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

Printing:

______________________________________________________________

SAP AG 1

SAP System______________________________________________________________


7/53

- BAdI: Fill Addition Data Table and Structure

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

o UnderBasic Functions -> Worklist -> Maintain Business Add-Ins for Worklists:

- BAdI: Contract Tolerance Check Against Nomination Line Item

o UnderNomination -> Basic Settings:

- Define Reference Document Update

o UnderNomination -> 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

o Under Tickets:

- Define Validation Groups for Ticketing

o 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

o UnderLocation 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

o 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

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

- Business Add-In for Rebranding in Stock Projection Worksheet

______________________________________________________________

SAP AG 2

SAP System______________________________________________________________


8/53

- 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:

- Define Industry Term Values for Pricing

o UnderRevenue Accounting -> Valuation:

- Maintain Alternative Dual Accounting Price Multipliers

o UnderRevenue Accounting -> Payment Processing:

- Define Gross Volume States

o UnderRevenue 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 Managementare now under the

structureIndustry Solution Oil & Gas (RLM - Remote Logistics Management).

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

- FromActivate Offshore LogisticstoActivate Remote Logistics

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

- From OLM Containers to RLM Containers

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

renamed:

- FromDefine OLM Container CategoriestoDefine RLM Container Categories

- FromDefine Container Status for OLM ContainerstoDefine Container Status for RLM

Containers

o Under Shipping -> Containers -> RLM Containers -> Define Number Ranges, the following IMG

activity has been renamed:

- FromDefine Number Ranges for OLM ContainerstoDefine Number Ranges for RLM

Containers

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

o UnderExise Tax, the following IMG activity has been renamed:

______________________________________________________________

SAP AG 3

SAP System______________________________________________________________


9/53

- FromDefine Tax Types and Assignment of Product Tax GroupstoDefine Tax Types and

Product Tax Groups


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

- FromAdditional CA Entitlement Volume TypestoDefine CA Entitlement Volume Types

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

renamed:

- FromBase Configuration Settings for BalancingtoDefine Default Smart Form

- From Customize Configurable MessagestoDefine Balancing Message Types

o UnderRevenue Accounting -> Valuation, the following IMG activity has been renamed:- FromMaintenance of Dialog Process Limit for VL DoctoMaintain the Dialog Process Limit

for VL Doc

o UnderRevenue Accounting -> Configure Taxes, the following IMG activities have been renamed:

- From Severance Tax TypetoDefine Severance Tax Types

- From Tax ClasstoDefine Tax Classes

- From School DistrictstoDefine School District Codes

o 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 linkstoDefine Smart Form Structure- From Profile and field rulestoDefine Print Values for Smart Form

- FromLanguage dependent code texttoDefine Language for Smart Form Fields

The following IMG activities have been deleted:


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 UnderExcise Duty Rates -> Internal Rates:

- Set/Maintain Internal Rates for Purchasing Condition

- Set/Maintain Internal Rates for Sales/Distribution Condition


o UnderRevenue Accounting:

- Configure List Viewer Path

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

______________________________________________________________

SAP AG 4

SAP System______________________________________________________________


10/53

- 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 Settingshave been moved to the

Basic Functionssection. Previously they came under theNominationsection.

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 underLogistics -> Sales and Distribution -> Bulk

Replenishment -> Master Data -> Site Control Parameters -> Maintain Plant Parameters.

o Under Storage Objekct Characteristics, the following IMG activity has been deleted:

- Maintain Segment Data for Storage Object Type


Replenishment -> Master Data -> Storage Objects -> Maintain Segment Data for Storage Object

Type.


o Under Silo/Tank Management -> Master Data, the following IMG activity has been deleted:- Maintain Segment Data for Storage Object Type


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)

o 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 5

SAP System______________________________________________________________


11/53

Offshore Logist

1.2.1 Container List (Enhanced)

Use

Previously, theRemote Logistics Container Listdisplayed 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

o Loading area

o 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

o PM order component

o PS network activity

o PS network component

1.2.3 Rentals (Enhanced)

Use

______________________________________________________________

SAP AG 6

SAP System______________________________________________________________


12/53

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.

TheReturn Rental Itemprocess 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

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

o 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.

o Vendor's Reference

- 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.

o 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 7

SAP System______________________________________________________________


13/53

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 Utilizationreport 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

o Actual load of the voyage, including surface area and weight

o 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 Utilizationreport. If you do not specify a

route, you cannot perform per-leg calculations.

______________________________________________________________

SAP AG 8

SAP System______________________________________________________________


14/53

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

o Display settings at cross-client level

o Activate components or packages at client level

o 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 9

SAP System______________________________________________________________


15/53

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

o 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______________________________________________________________


16/53

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

o Goods receipt to transport identification code

o Goods receipt to inbound delivery

o Subsequent adjustment in subcontracting

Effects on Customizing

To use the movement types 857and 858for 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 settingin Customizing for theIndustry 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 thisprogram and connect it to SAP Oil & Gas.

The RFC server program is made up as follows:

o Source code of the C program

o Function module OIB_QCI_RFC_SERVER

o Interface

o Dummy includes of conversion routines from the American Petroleum Institute (API) and American

Gas Association (AGA)

______________________________________________________________

SAP AG 11

SAP System______________________________________________________________


17/53

o Help text

Effects on System Administration

For more information on the installation of the RFC server, see SAP Note 619060.


To use the RFC server, you must make the following setting in Customizing for theIndustry Solution Oil

& Gas (Downstream):

In the IMG activityDefine 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 mustuse 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)

o 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 datereplaces the SAP term base date. The German SAP

termBasisdatumis not affected by this change.

______________________________________________________________

SAP AG 12

SAP System______________________________________________________________


18/53

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 forPayment 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______________________________________________________________


19/53

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 meterreadings.

o 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.

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


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 Dest fld. Doc. key fldSrce struc Srce fld

OIRC_NON_DEST SEQNR (blank)

OIRADBT SEQNR

To do this, chooseDefine document schema.

______________________________________________________________

SAP AG 14

SAP System______________________________________________________________


20/53

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 andthe 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.


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______________________________________________________________


21/53

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


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.Shipmtfield 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

o 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______________________________________________________________


22/53

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

o Goods receipt to transport identification code

o Goods receipt to inbound delivery

o Subsequent adjustment in subcontracting


To use the movement types 857and 858for 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 theIndustry 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

o 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


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______________________________________________________________


23/53

See alsoFor 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)

o 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, thenomination 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 theItem 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______________________________________________________________


24/53

during ticketing, the system creates a new batch (based on the movement scenario).

Alternatively, you enter batch information during ticketing on theNomination Datatab page. You can

enter the origin batch, destination batch, and load batch.


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.


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)

o Purchase into Destination based on Purchase Order (06)

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

o Transfer into Location based on Stock Transfer Order (16)

You define movement scenarios in Customizing forIndustry 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 Customizableinbound 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 forIndustry Solution Oil & Gas (Downstream) -> TSW (Trader's and Scheduler's

Workbench) -> Nomination -> Maintain Business Add-Ins for Nominationand 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.


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______________________________________________________________


25/53

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 contentis 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.


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 theMat. 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______________________________________________________________


26/53

codesI13(Generate consumption item) andI14(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.


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 forIndustry 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 forIndustry Solution Oil & Gas

(Downstream) -> TSW (Trader's and Scheduler's Workbench) -> BasicFunctions -> 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 forIndustry

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 forIndustry 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______________________________________________________________


27/53


28/53

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 ofproduct. If the vendor or customer does not pass the check, the system blocks ticket actualization and

thereby the shipment of product.


When you confirm a nomination item, the system automatically sets theHOLD(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 toXGTS(GTS hold flag).

An authorized user manually clears the hold status to allow the system to actualize the ticket by assigning

the statusXHLD(clear HOLD flag for ticket).


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______________________________________________________________


29/53

Effects on CustomizingIn 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 forIndustry 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

o Purchase orders

o Purchase requisitions

o Stock transfer orders

o Stock transfer requisitions

______________________________________________________________

SAP AG 24

SAP System______________________________________________________________


30/53

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.


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.


In Customizing for the stock projection parameters, you can chooseDocsCnsumption 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______________________________________________________________


31/53

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.


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.


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-Upof the Stock Projection Worksheet to nominations (publish with breakdown). You implement the

BAdI in Customizing forIndustry 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 themethod WHATIF_DISAGG_RULE. You implement the BAdI in Customizing forIndustry 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.


If you want the reference documents to be automatically updated, you have to make the following

settings in Customizing for theIndustry Solution Oil & Gas (Downstream). In the IMG activity Specify

TSW control parameters, you have to set theRef. Doc. Updateindicator. 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______________________________________________________________


32/53

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

o Reservations

o 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.


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.


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 forIndustry 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 usingpurchase 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)

o Purchase requisition into location (33)

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

o Stock transport from transport system into location (36)

______________________________________________________________

SAP AG 27

SAP System______________________________________________________________


33/53

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.


To ensure that tickets are validated, you must use one or more of the following Business Add-Ins (BAdIs)

in Customizing for theIndustry Solution Oil & Gas (Downstream)by choosing TSW (Trader's and

Scheduler's Workbench) -> Tickets:

o BAdI: Ticket Header Validation

o BAdI: Ticket Item Validation

o BAdI: Ticket Event Validation

o 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 Archivingcontributes 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 Archivingincludes 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 theRegulatory

Reportingapplication components.

After the system archives well completion volumes, it changes the status of the delivery network to

archivedto prevent the Contractual Allocationand Valuationapplication components from processing

the delivery network. The network can be processed again if well completion volumes are regenerated

______________________________________________________________

SAP AG 28

SAP System______________________________________________________________


34/53

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 Archivingdoes not include data that is needed for prior period adjustment (PPA) purposes.


In theArchiving Objecttransaction AOBJ, you select the archiving object from the overview screen and

then choose Customizing Settingsto specify the maximum file size.

Ownership Customizing for Archiving

In the Owner Request Global Settingsactivity (Industry Solution Oil & Gas (Production and Revenue

Accounting) -> Ownership -> Owner Request -> Owner Request Global Settings), in theRetn. 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______________________________________________________________


35/53


36/53

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 inorder 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 Accessmenu:

- 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______________________________________________________________


37/53

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______________________________________________________________


38/53

Effects on CustomizingThe 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______________________________________________________________


39/53

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, notwith 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)

o Conservation Tax (CN)

o Emergency School Tax (ES)

o 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 Referencestransaction is now available in the SAP Easy Accessmenu

(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______________________________________________________________


40/53

Framework: New

Report ID: 132

File: Downloadable intermediatefile for detail record provi