Hierarchy
IS-M (Software Component) SAP MEDIA⤷
IS-M (Application Component) SAP Media⤷
JAS (Package) Application development R/3 Publishing Advertising System***
IMG Activity
| ID | ISPSD_PABRBEDING | Define Requirements for Pricing |
| Transaction Code | S_KK4_74002028 | IMG Activity: ISPSD_PABRBEDING |
| Created on | 19990816 | |
| Customizing Attributes | ISPSD_PABRBEDING | Define Requirements for Pricing |
| Customizing Activity | ISPSD_PABRBEDING | Define Requirements for Pricing |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISPSD_PABRBEDING |
In this step, you define the requirements for pricing in order processing/billing and in service settlement (home delivery settlement, commission settlement, postal charge forecast).
Requirements are represented as FORM routines. These FORM routines are used in the condition technique and in statistics.
Requirements are used to check a variety of criteria when carrying out the functions in question. You should enter the requirements to be used along with the functions for the condition technique in the pricing procedure. When you do this, the system displays a list of the requirements available per function.
The following communication tables are available for use in creating requirements for pricing: KOMK, KOMP, T001, T001R.
Note
The following preliminary step was added as fine-tuning for the requirements for pricing:
- The system first checks the fields in KOMK.
- If the result for the requirement is negative at this point, there is no need to check the position fields in KOMP.
Example
In pricing, a requirement is used to check whether or not a condition type is set up in the document. For example, it can define that a condition type is ignored for redirections.
Activities
- Please check first whether you can use the requirements in the standard system.
- Overwrite the existing routines if necessary.
- To create new requirements, please proceed as follows:
- Specify a group number. The group number should be in the number range interval 600 - 699, which is reserved for customer modifications.
- Enter a descriptive text.
- Create the desired requirement using the Editor.
- Activate the requirement.
- Enter a long text describing the meaning of the FORM routine in greater detail.
- Specify the application for which this requirement is to be used exclusively.
- Enter the requirement in the pricing procedure for the function in which you want to use the requirement.
Business Attributes
| ASAP Roadmap ID | 255 | Create Interfaces |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | ISPSD_PABRBEDING | 0 | I170007149 | Settlement |
| SIMG | ISPSD_PABRBEDING | 1 | O I510000066 |
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 |
| TFRM | L - Logical transport object | JY10 | 06 | Formulas and Requirements: Table Entries |
History
| Last changed by/on | SAP | 19990816 |
| SAP Release Created in |
