Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-MD-PCT (Application Component) Product Catalog⤷
FF (Package) Cash Management
Basic Data
| Data Element | FFDIS_PRIO |
| Short Description | Priority of selection criterion |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CC_NUMC4 | |
| Data Type | NUMC | Character string with only digits |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| 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 | 10 | Priority |
| Medium | 15 | Priority |
| Long | 34 | Priority of selection criterion |
| Heading | 34 | Priority of selection criterion |
Documentation
Definition
You use this indicator to set the priority of a structure. Priority 1 is the highest priority.
Sorting is by priority first. The customer or vendor master records are then checked to ensure they agree with the structures. The record with the highest priority is checked first. The group from the first matching record is copied to the master record; no further structures (those with lower priority) are considered.
To ensure that each master record has a planning grour, there should be one record (with lowest priority) which would be suitable for all the records:
Priority Ctry Tms ofpyt Dunn.type Pyt meths. Group Payt hist.
.. .. .. .. .. .. ..
13 OTHER X
All the master records which do not fit into other structures receive group "OTHER".
History
| Last changed by/on | SAP | 20010607 |
| SAP Release Created in |
