SAP ABAP Message Class 6P Message Number 709 (Requirements class should only be changed in exceptional cases)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ PP-MP-DEM (Application Component) Demand Management
⤷ MDPB (Package) Application development R/3 purchasing
⤷ PP-MP-DEM (Application Component) Demand Management
⤷ MDPB (Package) Application development R/3 purchasing
Attribute
Message class | 6P | ||
Short Description | Messages for planned independent requirements (Appl.area 60) | ||
Message Number | 709 | ||
Documentation status | |||
Authorization check Error Message | |||
Changed On |
Message Text
Requirements class should only be changed in exceptional cases
Help Document
Diagnosis
System Response
If requirements have already been created with this requirements type, then these are still treated according to the previous requirements class.
New requirements that are created are consumed according to the new requirements class.
Procedure
To guarantee a clear interpretation of demand management data, proceed as follows:
if requirements already exist with this requirements type, the requirements type should not be changed, but a new requirements type should be created with the new requirements class.
History
Last changed on/by | 20100310 | SAP | |
SAP Release Created in |