If the addition CLIENT SPECIFIED is specified, but the client ID in the WHERE condition is not, the SELECT statement bypasses If the client ID is not specified in the WHERE condition, the selection is made across all clients. Input parameter is annotated with the annotation the addition CLIENT SPECIFIED is specified, the client column is handled The addition CLIENT SPECIFIED cannot be used when accessing Statement, an addition entity~clnt must be used to give the field a name that can be used in the current statement. If the client field is accessed explicitly or implicitly in the SELECT Not have a component for the client field, which means that a client column is added to the results If CLIENT SPECIFIED is specified for a client-specificĬDS entity, the client field is read from the database and added to the results set. In the addition ORDER BY, the column can be sorted explicitly according to client identifier. When using the addition CLIENT SPECIFIED, theĬlient column of client-specific data sources can be specified in the WHERE condition to determine the Is possible to identify statically that the data sourcesĭata_source are not client-specific, the addition CLIENT SPECIFIED cannot be specified. Must be inserted after the last addition ON of the join condition. When a join expression is specified, the addition When a single data source is specified, the addition must be insertedĭirectly after the data source in the join condition. | |(clnt_syntax)ġ.Ĭlient handling in Open SQL. SAP NetWeaver AS ABAP Release 750, ©Copyright 2016 SAP AG.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |