Hierarchy
ECC-DIMP (Software Component) DIMP⤷
IS-HT-DRM (Application Component) Distributor-Reseller-Management⤷
/SAPHT/DRM14 (Package) DRM Customizing for ES only
IMG Activity
| ID | /SAPHT/DRM_MS48 | Define Validation Types |
| Transaction Code | /SAPHT/36000010 | (empty) |
| Created on | 20000412 | |
| Customizing Attributes | /SAPHT/DRM_MS48 | Define individual validations |
| Customizing Activity | /SAPHT/DRM_MS48 | Define individual validations |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPHT/DRM_SIMGMS46 |
In this IMG activity, you define additional validation types which will take place on records in staging area.
Validation type represents the different validations that may be performed on staging area records.
There are several predefined validation types in the system. Further, you can define your own validation type and code for them in business add-in "SAPHT/IF_EX_DRM_STS_BADI" method "VALIDATIONS".
Being a system level activity, this validation type can be called for both manufacturer/ supplier side and distributor/ reseller side.
While creating the validation type, you assign a bit number to it. This is used internally to store the failed validation in an easily retrievable format.
Example
"Sales Area is missing" is a validation that needs to be done on the staging area record. The system validation type "0005" defines such a validation.
Requirements
Standard settings
Recommendation
It is recommended that your validation type entries begin with the numeral "9" and that you keep the bit numbers in the range 80 to 100. SAP keeps these ranges free in the standard system and protects them from being overwritten during release upgrades.
It is not necessary to create entries in this table to add new validations to items in staging area.
But it is recommended to do so because you can then use them as the search parameter for finding out staging area records which fail the validation. For more information, see user documentation of business add-in "SAPHT/IF_EX_DRM_STS_BADI" method "VALIDATIONS".
Do not use same "bit no" for two validations as it will adversely affect "search by error" capability in staging area.
Activities
If you want to create a new validation type then proceed as follows:
1. Enter an alphanumeric key with maximum of four characters.
2. Fill a unique bitno in the range 80 to 100 for the manually added validations.
Further notes
The bit numbers are also used to find if ship-and-debit claim response IDoc will be sent and what rejection reasons will be sent there. So the bit number assignment becomes necessary.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
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 |
| /SAPHT/DRMVGVAL | V - View | /SAPHT/DRM_C21 |
History
| Last changed by/on | SAP | 20000420 |
| SAP Release Created in |
