Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
WBON (Package) WWS: Bonus
Basic Data
| Data Element | WERKS_NABBR |
| Short Description | Plant |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | WERKS | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table | T001W |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | WRK | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Plant |
| Medium | 15 | Plant |
| Long | 20 | Plant |
| Heading | 4 | Plnt |
Documentation
Definition
Plant that is used for updating the subsequent settlement if a document item without a plant reference is to be updated in Agency Business.
Use
In Agency Business (settlement requests, but also vendor billing documents), document items may not contain a reference to a plant.
It is not possible to update business volume without a plant.
In particular, cross-company code settlement (settlement at plant level) is not possible, as the company code of the plants involved is used in settlement documents. This is necessary, for example, for a correct breakdown of provision for accrued income.
The business volume is therefore updated using the plant entered here, if no plant reference is given in the item.
Notes
If you work with agency documents (settlement requests, vendor billing documents) without a plant reference, enter a suitable plant for each company code.
History
| Last changed by/on | SAP | 19980525 |
| SAP Release Created in |
