Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
GBAS (Package) FI-SL Customizing / integration / Basis
Basic Data
| Data Element | GCOQUAN1 |
| Short Description | Update quantity analog to standard quantity |
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 | 10 | Std qty |
| Medium | 15 | Standard qty |
| Long | 30 | Standard quantity |
| Heading | 0 |
Documentation
Definition
In controlling, a standard unit of measure is defined for each cost element. When a CO document is posted, the system tries to calculate a standard quantity from the document quantity (for example, posting in grams and converting to standard kilograms). If conversion is not possible, the standard quantity is set to zero (for example, posting in pieces, but it is not possible to convert to standard kilograms). The standard quantity is stored in the controlling summary records.
Since the unit of measure is stored in the key of the Special Purpose Ledger databases, it can be advantageous to use the CO standard quantity since fewer summary records will then be created. The disadvantage of this being that the standard quantity cannot be calculated in every case and is then stored with the value zero in the Special Purpose Ledger.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
