Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-CMM (Application Component) Commodity Management in Logistics⤷
LOG_CMM_IMG (Package) Commodity Management IMG Objects
IMG Activity
| ID | CMM_INDEX_SD | Adjust SD-Specific Index Relevance for Worklist |
| Transaction Code | S_EBJ_98000253 | (empty) |
| Created on | 20130214 | |
| Customizing Attributes | CMM_INDEX_SD | Adjust SD-Specific Index Relevance for Worklist |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | CMM_INDEX_SD |
Use
In this Customizing activity, you are given information about the conditions needed for the system to register delivery items with goods issue in Sales and Distribution (SD) as being relevant for the period-end valuation. You are also given information about how you can modify the index relevance for your worklist for SD-specific tasks.
The index entries of the relevant delivery items with goods issue are processed by report MEV_CREATE_WL (transaction CMM_PEV_CALC, Period-End Valuation: Creation of Worklist) up until the valuation key date. You can then check the results of the valuation in transaction CMM_PEV_WL.
You can use transaction CMM_PEV_CC, Period-End Valuation: Completeness Check, to check whether any open index entries exist that still have to be processed using report MEV_CREATE_WL.
Requirements
In Customizing for Sales and Distribution, you have activated period-end valuation in Customizing activity Define SD-Specific Settings Dependent on Company Codes.
One of the following two preconditions must be met for the system to register a delivery item with goods issue as being relevant for period-end valuation in Sales and Distribution:
- At least one document item must contain a pricing condition with a floating price.
Note: Irrespective of the pricing condition, the system considers the price as a floating price if you have created a billing document with billing type F2D1 (Provisional/Differential) for the sales order item to which the delivery item refers.
- The batch of the document item is not final.
Note: A batch is considered to be not final if its usage decision characteristic does not contain a value, based on material number, batch number and plant. If this characteristic does not exist or does not contain a value, no further changes will be made to the values, meaning the batch is final.
The system behaves in the following way when posting a billing document:
- If you post a provisional billing document for a delivery and no corresponding index entry exists yet, the system creates an index entry for each item of the delivery for which goods issue was posted. If an index entry already exists, the system updates the organizational data.
- If you post a final billing document for a delivery and an index entry already exists, the system sets the posting date as the declaration date. If you reverse the final billing document, the system deletes the declaration date.
Standard settings
Activities
You can change the standard system behavior by implementing method CHECK_RELEVANCE_DLV within BAdI BAdI: Index Relevance and Maintenance for Commodity Management.
Example
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | CMM_INDEX_SD | 0 | HLA0009600 | Sales and Distribution |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20130214 |
| SAP Release Created in | 617 |
