|
<< Click to Display Table of Contents >> Navigation: Multi-case Editing > Grid Editor > Grid Editing Prices |
Navigation: Multi-case Editing > Grid Editor >
Use the Grid Editor to modify the pricing or pricing adjustments (escalations, differentials, or energy factors) for more than one case at a time. Refer to the Prices Form for a more in depth understanding of the elements of pricing in PHDwin.
To Open the Prices Table in Grid Editor
1.Go to the list of Forms and double-click on Grid Editor if it is not already open. 2.Select the cases to edit by dragging and dropping them from the Case List into the right section of the Grid Editor window. Select multiple cases by using Click+Shift, Click+CTRL, or by dragging over a grouping of cases set up in the sort order. The number of cases selected is shown with a case count on the top right. To remove one or more cases, hover over the case and click the 3.Under Available Edit Tables, select Prices. 4.Click Edit to open the Grid Editor table 5.Make the appropriate changes and click Save to save the data and exit the Grid Editor. |
These are the standard columns in the Prices table. You can click on the icon on the top left •*Case ID - The ID Code ties each record to a case in PHDwin. New rows should be populated with the proper Case ID. This is a required field when adding new price records and tells the program which case the price or price adjustment will be applied to when the Grid Editor is closed. •Case Name - The Case Name is presented so that users are able to easily identify the case, even though the Case ID is the actual field used by the Grid Editor to link the new price data to a case. The case name is used for reference and is displayed so users can identify the case being edited. If a new price record is added, there is no need to populate the Case Name as this new information is not saved in this table •*Product - The product that the price is applied to. The product is a required field when adjusting or adding new prices lines. The product name has to match one of the available products in the Phase Configuration for the case and can be selected from the drop-down provided. •*Unit- The units for the price per product. For example, when modifying the price for oil, the unit would be bbl because the price for oil is measured in $/bbl. •*Stream - The default stream for prices is Revenue. If there are additional revenue streams in the database it can also be selected. •*Deck Type - The Deck Type is either - Price, Add Escalation, Percent Escalation, Add Differential, Percent Differential, or Energy Factor. Energy Factor decks can only be applied to Gas type products otherwise an error is thrown and the case is not updated. •Model - The name of a model that has already been created. New models cannot be created here. To hard-code a price, set it to Case Specific. The Model column is either say Case Specific or linked to a Model if there is one applied to the case. If a model is applied, it cannot be edited the Grid Editor, no changes to those values will be pulled back. •Sequence - Lists which segment of the deck the value is for. The Sequence column lists the order of the segments of a price deck, if there are multiple segments to model a price that changes over time. For a single segment price deck, the value is 1. For multiple segment price decks, the value is 1 for the first segment, 2 for the second segment, and so on. •*Segment Value - Required - The value of the price segment in the units listed. View the corresponding start date and length of the segment in the next two columns. This can be a positive or negative value. •Pri. Date - Price Date. The date is only required for the first segment of the deck. It can be populated with a hard-coded or linked date when the price begins. The length of each segment is set with the # of Months in the next column. Linked dates have to be formatted specifically. Examples of these are in the next section of this topic. •# of Months - The number of months that the segment lasts. This must be populated for each segment of the deck. To continue until the economic limit, input ECL. For the last value of the segment, this value will automatically be converted to ECL to continue the segment until the economic limit. •Cap Value - The cap value of the price. It is optional and only applicable to Price decks (not escalations or differentials). The cap must be entered on the first segment of the price. It will be ignored on all other segments.
*Required Field |
Entering Multiple Segments for Prices
If a user schedules out multiple segments for something, such as a price or escalation, PHDwin will honor the initial date that is entered and then the offset from that segment to the next. It is important to enter the correct date for the initial segment, and then the correct offsets. All dates after the initial segment will be ignored. Formatting Linked Dates Note: In the latest builds of PHDwin V3 (from build 9), it is now much easier to use linked dates using the provided drop-down menu. This reduces the chances of error. If a price deck or price model changes over time, always begin the price on a hard date. However, if a flat price or escalation is used, link it to some event on the case using Linked Dates. To use the Linked Date field in the Grid Editor, it must be formatted correctly. If not an error occurs and the changes to records with invalid linked dates will not be saved. Say a price has been scheduled to begin at, or be linked to, First Production of Oil. When viewed in the Grid Editor, the Linked Date might look like this: Fprod [Oil]. When adding a price to a handful of cases, it is recommended to set up a sample using one of the cases on the Prices form in PHDwin before making changes to the rest of the cases in the Grid Editor. This makes the right formatting visible. These are the valid options for Price linked dates along with examples of how to enter each one in the Grid Editor:
Important notes about linked dates: •The inputs in brackets [ ] are required. •The input in parenthesis ( ) is optional - this is the offset. The (Offset) is a number of days and can be positive or negative. If no offset is entered, zero is assumed, implying no offset. •The offset for Start Date should always be positive. If a negative offset from the case start date is used, it will not report, because nothing is usually reported before the case start date. |