Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
WAUF (Package) Application development R/3 Purchasing, Allocation table
Basic Data
| Data Element | EKORGABW |
| Short Description | Indicates different purchasing organization |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | EKORGABW | |
| 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 | Diff. POrg |
| Medium | 15 | Diff. pur. org. |
| Long | 20 | Different pur. org. |
| Heading | 2 | DP |
Documentation
Definition
This indicator controls whether or not the plants or distribution centers within an allocation table need to belong to the same purchasing organization (see the allocation table header).
When creating an allocation table, the user must specify a purchasing organization which is transferred to the allocation table header.
Among other things, the purchasing organization is passed on to the follow-on documents. In particular, only plants that are assigned to the same purchasing organization may occur in a purchase order.
If alternative purchasing organizations are not prohibited for a plant or distribution center, the system automatically determines a purchasing organization for each plant or distribution center using the following procedure:
- If the plant or distribution center is assigned to the purchasing organization specified by the user (see the allocation table header), then this purchasing organization is transferred.
- Otherwise, the normal (standard) purchasing organization is transferred from the plant master.
The purchasing organization determined for each plant or distribution center overrides the purchasing organization predefined by the user and is forwarded to the follow-on documents (for example purchase orders).
Regardless of whether alternative purchasing organizations are prohibited or not, the system checks to see if the purchasing organization that is determined or predefined by the user (see the allocation table header) is assigned to the plant or the distribution center. If such an assignment does not exist, then an error message appears in the incompletion log and the allocation table item remains blocked for subsequent processing.
The system then also checks whether the purchasing organization determined for a plant or a distribution center is the same as the purchasing organization predefined by the user (see the allocation table header). Variances appear as warnings in the incompletion log.
Unexpected or unwanted side effects can result due to alternative purchasing organizations:
- Source determination
In the source determination (regardless of whether automatically carried out or manually requested), the purchasing organization is used to determine external vendors for a distribution center and either a distribution center or an external vendor for a plant. The system can then determine a source of supply that is not expected or required by the user in the current situation. In this case, the user needs to make a manual correction.
- Price determination in follow-on documents
The purchasing organization determined in the allocation table is also used for determining prices in follow-on documents (for example purchase orders).
History
| Last changed by/on | SAP | 20010607 |
| SAP Release Created in |
