Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MB0C (Package) Customizing R/3 inventory management
IMG Activity
| ID | SIMG_CFMENUOLMBOMBS | Record Reason for Goods Movements |
| Transaction Code | S_ALR_87000504 | IMG Activity: SIMG_CFMENUOLMBOMBS |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUOLMBOMBS | Record Reason for Goods Movements |
| Customizing Activity | SIMG_CFMENUOLMBOMBS | Record Reason for Goods Movements |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOLMBOMBS |
In this step, you can carry out the following for each movement type:
- maintain the input status of the Reason field
- store a key that gives a reason for the movement (for example, reason for return delivery) and a corresponding text.
When you enter a goods movement, you can only enter reasons which have been defined for the movement type here.
Example
- You define that specification of a reason in the case of a return delivery is mandatory.
- You specify the reason for return delivery documents
- 0001, if the quality of a delivery is poor
- 0002, if the delivery is not complete
The reason for the movement is stored in the material document. In Inventory Management, you can use a report to evaluate the material documents for which a reason for movement was specified.
From the Inventory Management menu, you can display all material documents which have been posted for a particular reason. To do this, choose Environment -> Display list -> Reason for movement.
Note
It is only worthwhile to maintain the possible reasons for a movement type if the Reason field for the movement type is ready for input.
If you want to use the Reason for movement report to determine the reasons for which materials were returend to the vendor, it is a good idea to maintain a reason for movement for movement types 122 (return delivery to vendor) and 124 (return delivery from GR blocked stock) only.
Default settings
In the standard system, reasons 0001 and 0002 are intended for return deliveries (movement type 122).
Activities
- Enter the following information for every movement type for which you want to store a reason in the document:
- a key number
- a text
- Make sure that the entry of a reason is possible in the menu option "New movement types" (view "Entry control").
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-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 | SIMG_CFMENUOLMBOMBS | 0 | HLA0006045 O HLA0006047 |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_156_G | V - View | OMBS | 9999999999 | Control: Reason for Movement | ||
| V_157D | V - View | OMBS | 01 | Reason for Movement |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
