| SMW_BDM462 |
The segment field '&1' is a primary key |
| SMW_BDM463 |
The segment field '&1' is a parent key |
| SMW_BDM464 |
There should be no update maps for a read only BDoc type |
| SMW_BDM465 |
The parent segment with name '&1' could not be found |
| SMW_BDM466 |
Invalid table name '&1' for segment '&2'. Only SMO_MEMO00 can be mapped |
| SMW_BDM467 |
BDoc type '&1' can't be a read BDoc,it has update maps assigned to it |
| SMW_BDM468 |
BDoc type '&1' cannot be a write BDoc,it has more than one update map |
| SMW_BDM469 |
The BDoc type short name cannot have more than 14 characters |
| SMW_BDM470 |
No object selected |
| SMW_BDM471 |
Action aborted |
| SMW_BDM472 |
Error: customer version '&' in this SAP system |
| SMW_BDM473 |
Invalid namespace for '&1' and '&2' |
| SMW_BDM474 |
Error while modifying database table & |
| SMW_BDM475 |
Can't delete '&1'. Is not modifiable |
| SMW_BDM476 |
Invalid characters in '&1' |
| SMW_BDM477 |
The updatable map '&1' does not have a primary key |
| SMW_BDM478 |
An update map requires a primary key |
| SMW_BDM479 |
The field mapping information is incomplete |
| SMW_BDM480 |
On saving all where clauses will be changed to mandatory for Std. BDoc |
| SMW_BDM481 |
No log found |
| SMW_BDM482 |
No unreleased task found for object & |
| SMW_BDM483 |
&1 &2 &3 &4 |
| SMW_BDM484 |
Segment deleted successfully |
| SMW_BDM485 |
SAP BDoc type '&1' cant be deleted in a Customer System |
| SMW_BDM486 |
Data Element '&1' does not have the same domain as the parent |
| SMW_BDM487 |
Segment Field '&1' should be GUID, to be a primary key |
| SMW_BDM488 |
The table SMO_MEMO00 can be mapped only if the segment name is SMOMEMO |
| SMW_BDM489 |
For BDoc type '&' an inactive version exists. Releasing not possible |
| SMW_BDM490 |
Segment Name and Parent Segment Name Cannot be the same |
| SMW_BDM491 |
Error during determining the namespace |
| SMW_BDM492 |
BDoc type '&1' is used in a replication. BDoc Class-&2 cannot be changed |
| SMW_BDM493 |
BDoc Short Name '&' is already being used |
| SMW_BDM494 |
Messaging BDoc type cannot have segment with the name 'SMOMEMO' |
| SMW_BDM495 |
Messaging BDoc type cannot map to system fields |
| SMW_BDM496 |
&1 is not a valid Site Tyie ID |
| SMW_BDM497 |
Messaging BDoc type should't contain the Alias name and Table field name |
| SMW_BDM498 |
The datatype, length and decimals are differing from parents attributes |
| SMW_BDM499 |
The BDoc type '&1' has changed from the last time it was mapped |
| SMW_BDM500 |
An unexpected error occurred in function module '&' |
| SMW_BDM501 |
The BDoc type '&' is currently locked by user '&' |
| SMW_BDM502 |
For BDoc type '&' neither an active nor an inactive version was found |
| SMW_BDM503 |
For BDoc type '&' there is already an inactive version |
| SMW_BDM504 |
Messaging BDoc type cannot have segment with the name 'ZSMOMEMO' |
| SMW_BDM505 |
Error when creating an instance for '&' |
| SMW_BDM506 |
Error when determining a transport request for '&' |
| SMW_BDM507 |
Error when adding entries to transport request for '&' |
| SMW_BDM508 |
Cant delete &1.This Msg BDoc type is map'd to one or more Act. Sync BDocs |
| SMW_BDM509 |
&1 is not a valid Messaging BDoc type |
| SMW_BDM510 |
Messaging BDoc types can be mapped only for Synchronization BDoc types |
| SMW_BDM511 |
A database table '&' could not be found |
| SMW_BDM512 |
Table & contains a field (&) without data element |
| SMW_BDM513 |
Table & contains a data element (&) without domain |
| SMW_BDM514 |
A database element '&' could not be found |
| SMW_BDM515 |
Data element '&' is defined without domain |
| SMW_BDM516 |
Structure name '&1' is not valid |
| SMW_BDM517 |
Either Data Element or (Data Type and Length) Should be Entered &1 &2 |
| SMW_BDM518 |
Segment Field '&1' has no Data Element Mapped |
| SMW_BDM519 |
Segment 'SMOMEMO' cannot be Renamed |
| SMW_BDM520 |
Parent Segment should not be specified for Header segment 1& |
| SMW_BDM521 |
Invalid hierarchy for segment '&1' |
| SMW_BDM522 |
Invalid parent-child relationship for segment '&1' |
| SMW_BDM523 |
Parameter '&1' used in where Clause( order = &2) doesnot exist |
| SMW_BDM524 |
segment '&1' should have one and only one primary key |
| SMW_BDM525 |
No parent key defined for Child segment '&1' |
| SMW_BDM526 |
Child segment '&1' should have one and only one parent key |
| SMW_BDM527 |
For Header Segment '&1', No Parent Key should be Defined |
| SMW_BDM528 |
No table Field is mapped for segment Field '&1' of Segment '&2' |
| SMW_BDM529 |
No table is mapped for segment Field '&1' of Segment '&2' |
| SMW_BDM530 |
For System field '&1' of Segm '&2', Segment field should also be the same |
| SMW_BDM531 |
Table '&1' mapped to Segment Field '&2' of Segment '&3' is Invalid |
| SMW_BDM532 |
System field '&1' of Segment '&2', Cannot be mapped to Messaging BDoc |
| SMW_BDM533 |
For Table field '&1' of Segm '&2', segment field should also be the same |
| SMW_BDM534 |
The table '&1' does not have the field '&2' ( for Where Order '&3' ) |
| SMW_BDM535 |
Segment Field '&1' should be GUID, to be a parent key |
| SMW_BDM536 |
Table '&1' Mapped to segment '&2' does contain All System Fields |
| SMW_BDM537 |
BDoc type '&1' has No Segments.BDoc should at least have one segment |
| SMW_BDM538 |
Field name '&1' of Segment '&2' is a reserved name. Give some other name |
| SMW_BDM539 |
Segment Field '&1' should be CHAR32 or CHAR34 GUID, to be a primary key |
| SMW_BDM540 |
Segment Field '&1' should be CHAR32 or CHAR34 GUID, to be a parent key |
| SMW_BDM541 |
Only Automatically created BDoc Names can start with '&1*' |
| SMW_BDM542 |
Only Automatically created BDoc Short Names can start with 'CNB*' |
| SMW_BDM543 |
Sort order for Segment Fields in segment & is not unique |
| SMW_BDM544 |
Post Process cannot be Performed in Productive System |
| SMW_BDM545 |
Post Process cannot be Performed in Test\Quality System |
| SMW_BDM546 |
Field '&1' of segment '&2' Cannot be a Primary Key and also a Parent Key |
| SMW_BDM547 |
Automatically created BDoc type Name should start with '&1*' |
| SMW_BDM548 |
Automatically created BDoc type Short Name should start with 'CNB*' |
| SMW_BDM549 |
Field '&1' of segment '&2' Cannot be a Primary Key and also an R/3 Key |
| SMW_BDM550 |
Field '&1' of segment '&2' Cannot be a Primary Key and also an R/3 Fld |
| SMW_BDM551 |
Field '&1' of segment '&2' Cannot be a Parent Key and also an R/3 Key |
| SMW_BDM552 |
Field '&1' of segment '&2' Cannot be a Parent Key and also an R/3 Field |
| SMW_BDM553 |
The Segment SMOMEMO cannot be a root segment |
| SMW_BDM554 |
The fields for the segment 'SMOMEMO' should not have any namespace |
| SMW_BDM555 |
The primary key of seg & should be mapd to the key fld of update table |
| SMW_BDM556 |
The parent key of seg & should be mapd to the key fld of update table |
| SMW_BDM557 |
The Segment SMOMEMO cannot be copied |
| SMW_BDM558 |
The table '&1' cannot be mapped to segments |
| SMW_BDM559 |
Field '&1' has data type '&2'. '&2' type cant be used for Segment fields. |
| SMW_BDM560 |
Messaging BDoc type '&1' Field name '&2' can't have the data element '&3' |
| SMW_BDM561 |
Field '&1 is a memo field. Segment '&2' has more than one memo field. |