SAP ABAP Message Class B1 Message Number 128 (A message type could not be (uniquely) identified)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SALE (Package) Application Link Enabling
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SALE (Package) Application Link Enabling
Attribute
Message class | B1 | ||
Short Description | ALE group messages | ||
Message Number | 128 | ||
Documentation status | |||
Authorization check Error Message | |||
Changed On |
Message Text
A message type could not be (uniquely) identified
Help Document
Diagnosis
In order that IDOCs can be sent in this case with the help of the ALE customer distribution model, the partner profiles for the message control for the application , message type , change message '', partner type 'LS' and partner role ' ' must contain the same message type for all parameter numbers.
In this case, a total of different message types were detected.
System Response
Procedure
You need to maintain the partner profiles for the message control such that the same message type gets used for all partners with the selection criteria listed above.
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in |