Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
WPOS (Package) IS-R: POS interface
Basic Data
| Data Element | POS_PRICES_SITE_INDEP |
| Short Description | POS Outbound: All Prices Maintained Independently of Stores. |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 0 | |
| Medium | 15 | Pr. StoreIndep. |
| Long | 20 | Prices Store Indep. |
| Heading | 0 |
Documentation
Definition
Indicator: prices are valid for all stores (--> Performance)
The article prices of all stores that use this POS outbound profile are valid for all stores. If this indicator is set, the prices can only be stored at client or distribution chain level.
The change function for POS outbound does not calculate new prices for each store if this indicator is set. Instead, the prices that have already been calculated are stored temporarily so that they can be re-used when other stores use the program run to prepare data.
Information from the condition analysis is also stored temporarily and re-used when preparing data for the remaining stores.
This can greatly improve performance.
In order for this process to function correctly, prices cannot be created for specific stores as this could lead to inconsistencies when prerparing data.
Prices that are stored temporarily at price list category level (table A006) or which have been stored temporarily for a promotion (table A954 must be uploaded first, using a Note especially for this purpose) yet which contain store group assignements, can be regarded as being store specific and therefore make it unnecessary to set this indicator.
History
| Last changed by/on | SAP | 20010607 |
| SAP Release Created in | 46C |
