Hierarchy

⤷

⤷

IMG Activity
ID | REFXTA_REORPDRES1 | Derive Price Based on Price Code and Other Criteria |
Transaction Code | S_AER_95000396 | (empty) |
Created on | 20060724 | |
Customizing Attributes | REFXTA_REORREORPDRES | Derive Price Based on Price Code and Other Criteria |
Customizing Activity | REFXTA_REORPDRES1 | Derive Price Based on Price Code and Other Criteria |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | REFXTA_REORPDRES1 |
Use
In some cases, a price is not entered directly on the reservation object or the service, but is instead stored in the form of a price code. Here you specify how the system determines the price using this price code.
Requirements
Standard settings
Activities
The system derives the price in several steps. Normally you enter a derivation rule for each of these steps.
The system processes the individual steps in the sequence that you specify.
- Create at least one derivation rule. Enter a name for the rule that makes it clear what is being evaluated in this step. If the derivation is a conditional derivation, then name the condition in the text.
- If the derivation specified in this step should only be performed if certain prerequisites are met, then you should specify these prerequisites first. Choose the Condition tab page and enter the prerequisites. Then the system performs this step only if all prerequisites contained in the table are met.
- Then choose the Definition tab page to specify the actual derivation.
In the Source Fields table, you can choose the fields on which the price depends. The following fields are available:DAYS Duration of the appointment in days
HOURS Duration of the appointment in hours
ISALLDAY This is an all day appointment
ISHOLIDAY The appointment falls (wholly or in part) on a public holiday
ISWEEKEND The appointment falls (wholly or in part) on a Sunday
NEIGHBORH1 First location field of reservation object
NEIGHBORH2 Second location field of reservation object
NEIGHBORH2 Second location field of reservation object
PRICECODE Price code
RECURCOUNT Number of appointments (for a recurring appointment)
RSAREA Reservation area
RSOBJID Object key of reservation object
RSOBJTYPE Type of reservation object
RSTYPE Reservation type
TIMEFROM Starting time
TIMETO Ending time
WEEKDAYFROM Weekday (start, 1 = Monday, ..., 7 = Sunday)
WEEKDAYTO Weekday (end, 1 = Monday, ..., 7 = Sunday)
If you want to determine a price for a reservation, then the system specifies the values for these fields from the data currently entered for the reservation. Choose fields in your system that could influence the price of a reservation. Avoid using fields that do not contain relevant information.
For example, if twenty different locations are defined in your system, but only two reservation areas, then specify if there is a different price for each location, or only for each reservation area. If you want to have three different price zones, then you can add a third reservation area, rather then entering the same rule many times for a large number of locations. - Once you have specified the source fields, choose Maintain Rule Values. For each possible combination of source fields that are used in this rule or step, enter the values for the source fields.
For each combination of source fields, enter the values to be derived for the target fields. The fields have the following meanings:FLOWTYPE Flow type that is used for the account determination
PRICE The derived price
CURRKEY Currency for the price
TIMEUNIT Time unit that the price refers to
ISPERMEAS Is the price per measurement?
MEAS Measurement unit
Depending on the value of the ISPERMEAS and TIMEUNIT indicators, the system multiplies the price with the measurement value and/or the duration of the appointment. The price that the system determines in this way is then billed during periodic settlement of costs or posted to an account assignment object in CO.
As soon as the system finds a price for the current reservation in a given step, the process stops there and the system does not make any further derivations.
Example
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
IMGDUMMY | D - Dummy object | REORPDRES1 |
History
Last changed by/on | SAP | 20090114 |
SAP Release Created in | 700 |