Hierarchy
SAP_AP (Software Component) SAP Application Platform⤷
AP-PRC-CON (Application Component) Condition Technique⤷
/SAPCND/CUSTOMIZING (Package) Customizing Objects for Condition Technique
Basic Data
| Data Element | /SAPCND/APPLICATION |
| Short Description | Application as Condition Technique |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | /SAPCND/APPLICATION | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table | /SAPCND/T681A |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | /SAPCND/KAP | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Appl. |
| Medium | 20 | Application |
| Long | 20 | Application |
| Heading | 16 | Application |
Documentation
Definition
An application is an entity that uses a usage. An application can use more than one usage to achieve the required results.
The only aim of an application (as regards condition technique) is to specify which search criteria should be used when determining condition records. Each application must be registered within condition technique. Applications are not a part of the condition technique.
An example of an application within mySAP CRM could be "Sales/Service".
Supplementary Documentation - /SAPCND/APPLICATION0001
Use
Processing conditions in product master data depends on the application you wish to use; Purchasing (BBP Scenario) or Sales (CRM Scenario). This decides which condition types should be accessed, for example, to assign a price, discount or surcharge to a material, service or product category.
First choose the required application; Purchasing or Sales and use the input help to enter a condition type in the field for input (in the item area). A line then appears where you enter the price-related data.
Dependencies
To assign a price, for example, to a condition type, you must first make the following settings in Customizing for the condition technique:
- Condition tables must exist and be generated with the necessary fields for product processing (for example, product or business partner and product).
- A condition type must exist (for example, a copy of an existing condition type such as 0PR0). The above-mentioned tables must be assigned to this condition type in an access sequence (in Customizing under CRM -> Master Data -> Condition Technique -> Access Sequence)
- Then you must assign the condition types required for product processing to a new condition maintenance group (in Customizing under -> CRM -> Master Data -> Condition Technique -> Condition Group), as the condition group PRODUCTCRM delivered by SAP should not be modified.
- You must ensure that the condition groups are assigned to the sales and purchasing applications so that the settings of the condition maintenance group apply to the product master data (in Customizing under CRM -> Master Data -> Product -> Special Settings for Sales Transactions and under Enterprise Buyer professional edition -> Master Data -> Products -> Special Settings for Purchasing Transactions).
Example
Condition table SAP004 contains amongst other things the fields 'business partner' and 'product'. A copy of the R/3 condition type PR00 with the name ZPR0 is created. When assigning the condition type to the new condition group ZPRODUCTCRM, condition type ZPR0 is assigned to condition table SAP004. You must then assign the new condition group ZPRODUCTCRM to the sales application.
History
| Last changed by/on | SAP | 20050131 |
| SAP Release Created in |
