Hierarchy
⤷ 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_CFMENUOLMBCHNX | Set Up Customer Exits for External Batch Number Assignment |
Transaction Code | S_ALR_87006954 | IMG Activity: SIMG_CFMENUOLMBCHNX |
Created on | 19981222 | |
Customizing Attributes | SIMG_CFMENUOLMBCHNX | Set up customer exits for external batch number assignment |
Customizing Activity | SIMG_CFMENUOLMBCHNX | Set up customer exits for external batch number assignment |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CFMENUOLMBCHNX |
As part of the external batch number assignment, the following two function module exits are available in the SAP enhancement SAPLV1ZE for checking a new batch number that has been entered.
- EXIT_SAPLV01Z_003. Using this exit, you can replace the proposed number range object BATCH_CLT and/or external interval 02 with a number range object and/or external interval you have defined yourself.
You also have the option of suppressing the batch number check, for example, based on the material or plant. - EXIT_SAPLV01Z_004. Using this exit, you can define your own checking rule.
Further notes
In both exits, a communication structure with the application data for each business transaction (for example, plant or material type ) is available. To obtain more information such as the time, user name, or the date, you must use one of the exits.
Example
In the function module exit EXIT_SAPLV01Z_003, an external number range XY is determined, against which the batch numbers are checked.
In the function module exit EXIT_SAPLV01Z_004, the batch number entered is checked against your own rules.
Activities
- Create the enhancement.
Either create a new project or use an existing project.
- Activate the project.
Your enhancement only works after the project has been activated.
Further notes
In contrast to modifications, enhancements are always release-insensitive because they are not included in the SAP original, but in a namespace reserved for the customer.
The general procedure for creating enhancements is contained in the enhancement transaction in the "Utilities - Online manual" menu.
Every enhancement is documented. To access this documentation, choose the "SAP docu" pushbutton in the enhancement transaction.
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
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_CFMENUOLMBCHNX | 0 | HLA0006045 O | |
SIMG | SIMG_CFMENUOLMBCHNX | 1 | HLA0009761 | Batches |
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 |
CMOD | L - Logical transport object | CMOD | LOBM_CHNEU | Customer enhancement projects |
History
Last changed by/on | SAP | 19990129 |
SAP Release Created in |