SAP ABAP Message Class AZ Message Number 000 (Incorrect vendor number was transferred)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CA (Application Component) Cross-Application Components
⤷
NDBS (Package) New Dimension Plug-In: Basis Objects
BBPCRM (Software Component) BBPCRM⤷
CA (Application Component) Cross-Application Components⤷
NDBS (Package) New Dimension Plug-In: Basis Objects 
Attribute
| Message class |  |
AZ | |
| Short Description |  |
Master data messages for external applications | |
| Message Number |  |
000 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
19981030 |
Message Text
Incorrect vendor number was transferred
Help Document
Diagnosis
In parameter INOUT_NEXT_LIFNR, vendor number was transferred as the starting point. This vendor number, however, is not contained in table INOUT_LIFNR_TAB. Normally, this inconsistency should not occur if the values are transferred to INOUT_NEXT_LIFNR and INOUT_LIFNR_TAB in subsequent calls as they were returned in previous calls of the function module.
System Response
Procedure
Find out how an incorrect vendor number was saved in parameter INOUT_NEXT_LIFNR. During the first call, the function module was possibly called without using the initial parameter INOUT_NEXT_LIFNR within a sequence of blocked calls.
Procedure for System Administration
History
| Last changed on/by | |
20131127 | SAP |
| SAP Release Created in |
