Hierarchy
⤷ 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 | WRF_FDG_PO_FASHION |
Short Description | Generation of Vendor Orders (Seasonal) |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
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 | Gen. Seas. |
Medium | 15 | Gen. Seasonal |
Long | 37 | Generation Seasonal Procurement |
Heading | 37 | Generation: Seasonal Procurement |
Documentation
Definition
Defines that the system generates vendor purchase orders using seasonal procurement.
Use
When you set this indicator, the system executes the purchase order split in accordance with the Customizing settings for seasonal procurement.
The merging of vendor purchase order items in Customizing for item categories in the allocation table will not be executed, as otherwise synchronization is no longer possible between the purchase order and the allocation table.
Dependencies
In this case, the system does not take the split criteria for vendor orders in Customizing for the allocation table into account.
If you use the OTB check, the system sets the indicator automatically. You cannot delete it.
When the OTB check is active, the follow-on document generation for vendor orders is only executed synchronously and any input parameters that are filled for parallel processing are ignored. Other document data is processed as before.
If you make allocation-table-relevant changes to purchase orders that you created using Fashion purchase order processing, the system writes the changed data to the relevant allocation table.
Example
History
Last changed by/on | SAP | 20050615 |
SAP Release Created in | 470 |