Professional Documents
Culture Documents
Release 4.72
Release Notes
TM
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
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
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
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
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:
-
Industry Solution Oil & Gas (Downstream) - HPM (Hydrocarbon Product Management)
o
Under Oil- and Gas-Specific Units of Measurement and Other Stockkeeping Units:
-
Under Petroleum Measurement Standards -> Quantity Conversion Interface (QCI) Configuration
-> Business Add-Ins:
-
Industry Solution Oil & Gas (Downstream) - SSR (Service Station Retailing)
o
Under Document Base Table -> Aggregation Schema -> Maintain Business Add-Ins for
Aggregation Schema Definitions:
-
Under Payment Card Handling -> Maintain Business Add-Ins for Payment Card Handling:
-
Under Settlement and Invoicing -> Collective Printing -> Maintain Business Add-Ins for Collective
Printing:
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
Industry Solution Oil & Gas (Downstream) - TSW (Trader's and Scheduler's Workbench)
o
Under Basic Functions -> Worklist -> Maintain Business Add-Ins for Worklists:
-
Under Tickets:
-
Under Location Balancing -> Maintain Business Add-Ins for Location Balancing:
-
Under Three-Way Pegging -> Maintain Business Add-Ins for Three-Way Pegging:
-
Under Stock Projection -> Maintain Business Add-Ins for Stock Projection:
-
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
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:
-
Under Shipping -> Containers -> RLM Containers, the following IMG activities have been
renamed:
-
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
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
Under Revenue Accounting -> Valuation, the following IMG activity has been renamed:
-
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:
-
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
Under Oil- and Gas-Specific Units of Measurement and Other Stockkeeping Units:
-
Industry Solution Oil & Gas (Downstream) - TDP (Tariffs, Duties and Permits)
o
Under Production, Tax and Royalty Reporting -> Tax Reporting -> New Tax Reporting Framework:
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
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
______________________________________________________________
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
Loading area
Holding area
PM order operation
PM order component
PS network activity
PS network component
______________________________________________________________
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.
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
______________________________________________________________
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.2 IS-OIL-DS-EXG
Exchanges
______________________________________________________________
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.3 IS-OIL-DS-HPM
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
______________________________________________________________
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
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.
Interface
Dummy includes of conversion routines from the American Petroleum Institute (API) and American
Gas Association (AGA)
______________________________________________________________
SAP AG
11
SAP System
______________________________________________________________
Help text
1.3.4 IS-OIL-DS-TAS
1.3.5 IS-OIL-DS-MAP
______________________________________________________________
SAP AG
12
SAP System
______________________________________________________________
1.3.6 IS-OIL-DS-SSR
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.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
______________________________________________________________
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
______________________________________________________________
SAP AG
14
SAP System
______________________________________________________________
1.3.7 IS-OIL-DS-TD
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.8 IS-OIL-DS-TDP
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
______________________________________________________________
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
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.
In-transit stock
Negative inventory
______________________________________________________________
SAP AG
17
SAP System
______________________________________________________________
See also
For more information, see SAP Note 609703.
1.3.9 IS-OIL-DS-TSW
______________________________________________________________
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
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.
______________________________________________________________
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.
______________________________________________________________
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.
______________________________________________________________
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.
______________________________________________________________
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.
______________________________________________________________
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)
Sales orders
Purchase orders
Purchase requisitions
______________________________________________________________
SAP AG
24
SAP System
______________________________________________________________
______________________________________________________________
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.
______________________________________________________________
SAP AG
26
SAP System
______________________________________________________________
Purchase requisitions
Reservations
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
Stock transport from location into transport system (34 and 35)
______________________________________________________________
SAP AG
27
SAP System
______________________________________________________________
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 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
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
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
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
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.
______________________________________________________________
SAP AG
29
SAP System
______________________________________________________________
1.4.4 IS-OIL-PRA-EIA
1.4.4.1 IS-OIL-PRA-EIA-UG
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.6 IS-OIL-PRA-REP
Reporting
______________________________________________________________
SAP AG
31
SAP System
______________________________________________________________
1.4.6.2 IS-OIL-PRA-REP-REG
Regulatory Reporting
______________________________________________________________
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.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)
______________________________________________________________
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 (new with Oil & Gas 4.72; not part of a previous release)
Current as of: October 2003
Framework: New
Report ID: 131
o
______________________________________________________________
SAP AG
35
SAP System
______________________________________________________________
______________________________________________________________
SAP AG
36
SAP System
______________________________________________________________
1.4.6.4 IS-OIL-PRA-REP-ROY
Royalty Reporting
______________________________________________________________
SAP AG
37
SAP System
______________________________________________________________
New Mexico OGR-2 Oil and Gas Royalty Report by PUN No.
o
New Mexico Oil and Gas Royalty Detail Report by Ownership Agreement and PUN No.
o
New Mexico Oil and Gas Royalty Report by PUN No. and Ownership Agreement
o
Texas GLO3 - Royalty Reporting (Oil) Summary for Texas, A&M, and UT
o
Texas GLO3 - Royalty Reporting (Gas) Summary for Texas, A&M, and UT
o
Royalty interest
______________________________________________________________
SAP AG
38
SAP System
______________________________________________________________
Royalty volume
Price
Royalty value
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
______________________________________________________________
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.3 IS-OIL-PRA-REV-CA
Contractual Allocation
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
______________________________________________________________
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 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
______________________________________________________________
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.
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
This reserved word indicates that the price multiplier represents gas plant interest ownership.
o
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).
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
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
______________________________________________________________
SAP AG
43
SAP System
______________________________________________________________
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
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 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
______________________________________________________________
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.
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
71 - Booked documents
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
Exception Report
Further, as of SAP Oil & Gas 4.72, the following Payment Processing reports are no longer available
since they are obsolete:
o
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
______________________________________________________________
SAP AG
48