Petrotranz Oil Shipper Split (.XML)
Back to Import or Export Back to Market Master
- 1 Introduction
- 1.1 Menu Option
- 1.2 Security
- 1.3 Output
- 1.4 Generate a Shipper Split
- 1.5 Exceptions
- 1.6 Override Split Carrier
- 1.7 Appendix 1
Introduction
Metrix clients that use Petrotranz upload the existing Petrinex Pipeline Split (.XML) generated by Metrix onto Petrotranz as the Shipper Split.
Petrotranz requested a new file format so Metrix was enhanced to create a Petrotranz-specific Shipper Split file (.XML format only ).
Note: At this time, the Petrotranz Shipper Split is generated for Product OIL only.
Menu Option
To generate the Petrotranz Shipper Split, the following menu option should be used. The menu option will be available to all users:
Import/Export > Petrotranz > Shipper Split
Security
The security component ShipperSplitExport is available with all Roles that have the Security Component PipelineSplitFileGeneration (for Petrinex Pipeline Split) using the same permissions.
The permission for the above security component (ShipperSplitExport) should be changed to No Access to prevent a user from creating a Petrotranz Shipper Split.
Output
All Petrotranz Shipper Split Outputs will be generated in the following Destination Directory . If the Directory path for the Shipper Split Export Directory Type is blank, it must be filled in to allow for a Petrotranz Shipper Split to be created.
The Petrotranz Shipper will only be created in .XML format. The name of the file will be OILSHIPPERSPLIT + Production Date + Control Group and will be created in the location specified above.
See the Appendix below which shows an XML file example.
Generate a Shipper Split
Batteries that need a Shipper Split must be at step 2. A Shipper Split is requested at the Control Group and will generate data for all batteries that are at Step 2 within the Control Group.
The data contained in an Oil Shipper Split will be all Oil Sales from the Battery to a Delivery System with a Purchaser specified. The user can exclude certain sales records through the use of a “Pseudo Facility” flag on the Delivery System Master. See the Exceptions section for more details. The data is reported by Working Interest Owner (called a "Carrier" for our purposes to avoid confusion with the real WIO and other partners) within Shipper on the Petrotranz Oil Shipper Split. By default, non-TIK partners (Receive Revenue = Yes) use the Producing Battery Operator as the Carrier instead of each individual owner being reported as their own Carrier. For TIK partners (Receive Revenue = No) the default is that each TIK owner will be reported as their own Carrier. The user can modify the default behavior through the use of an “Override Split Carrier” on the Market Master Purchaser. See the Override Split Carrier section for more details.
If you do not have access to the Security Component ShipperSplitExport mentioned above, the following message will be displayed:
Selecting Submit will submit a job to create the Petrotranz output (.XML) in the location specified in section 3. See Appendix 1 for an example.
Exceptions
The ability to identify a Delivery system as a Pseudo Facility has been added to the Delivery System Maintenance screen. All existing Delivery Systems will be defaulted to No. This option helps to not create duplicate dispositions on the Shipper Split when selling the volume at one Control Group and receiving the volume from an Outside Receipt at the second Control Group. If true Control Group to Control Group Transfers are used, a pseudo facility is not needed.
Note: This option (the ability to deem a Delivery System as a Pseudo Facility) is used for Petrotranz Shipper Split processing only.
Override Split Carrier
In the Market Master Purchaser screen - for Oil dispositions only - there is a field called "Override Split Carrier". This field can be used to override the default behaviour mentioned above. For instance, if the user encounters a situation where one TIK owner is the Carrier for another TIK owner, they can use this field to specify a different owner as the Carrier. Rather than each TIK owner being reported as their own Carrier, Metrix will group them together.
In another case, if the producing battery operator is not reflective of the actual Carrier for non-TIK partners, this field can be used to override the Carrier and group partners within the Oil Shipper Split.
Appendix 1
Copyright© 2024 IFS AB. Copying prohibited. All rights reserved.