Hierarchy
⤷ SCM-BAS (Application Component) SCM Basis
⤷ CIF (Package) Core Interface
Basic Data
Data Element | CIFCONSUMP |
Short Description | Consumption Data in the Integration Model |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | FLAG | |
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 | Consumptn |
Medium | 15 | Consumptn Data |
Long | 20 | Consumption Data |
Heading | 15 | Consumptn Data |
Documentation
Definition
With the scenario "Consumption Data" you can send consumption data used in MRP from the ERP system to SAP APO. This allows you to carry out a forecast on the basis of MRP consumption data in the function Demand Planning.
Use
The VMI interface is used in SAP APO for updating consumption data. You must create the planning object characteristics manually in SAP APO to update consumption data in InfoCubes.
Only the initial data supply is planned in the scenario. The system transfers the most recently updated data and a number of historical values determined from the number of historical values to be maintained in the material master (logistic view in the material master).
Dependencies
In the ERP system, the fields 'Forecast Model' and 'Number of Historical Values' have to be maintained in the material master.
You can control whether planned or unplanned consumptions are transferred using the Customizing settings for the MRP type.
In the integration model, you can restrict the selection of consumption data to be transferred by entering a forecast model. We recommend that you use the forecast model 'N' (external forecast) for materials for which you want to create a forecast in SAP APO in the future.
Restrictions: This scenario has not been generally released; for more information see note 358022.
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in |