Problem with BAPI_CLASS_SELECT_OBJECTS part 2

[Former Member]

When I give search criteria for BAPI_CLASS_SELECT_OBJECTS this will only work if I give whole values. somehow values with wildcards are not excepted in this BAPI ??

the function CLSC_SEARCH_OBJECTS which is used in the BAPI works fine with wildcards ??

so when for SELECTIONCRITERIONS I have

NAME_CHAR ZDMS4

CHAR_VALUE 05*

"other values initial "

I don't get any results

with

NAME_CHAR ZDMS4

CHAR_VALUE 05

"other values initial "

I only get results where the value for ZDMS4 is 05

does anybody knows how to search with wildcards in this BAPI ?

Message was edited by:

A. de Smidt

[Former Member]

Hi Smidt,

there are some restrictions in searching using this BAPI as per the documentation

<b>"Restrictions:

- Classes with multiple object types are not supported.

Exception: batches Restriction: only batches are returned

- No returning of classes

- Reference characteristics are not supported

- Interval characteristics are not supported

- No open intervals

- No exclusive search

- No string search

- No display of objects without values

- Objects with locked classification status are not returned"</b>

Regards,

Ravi

[Former Member]

hmmm SAP likes us to programm in BAPI but you can't use them since they can't do what the functions can inside the BAPI ??

CLSC_SEARCH_OBJECTS can handle wildcards and is used in this BAPI ?

is there a workaround for this problem so I can still work with the BAPI and use wildcards ??

[Former Member]

Hi,

Just curious to know why do you still want to use BAPI_CLASS_SELECT_OBJECTS when the FM CLSC_SEARCH_OBJECTS works the way you want ? If you are trying to call the bapi from an external system and being RFC enabled is the only qualification the bapi has, over the FM, create a wrapper bapi around the FM CLSC_SEARCH_OBJECTS and call it from the external program.

Regards,

Ravi

[Former Member]

we are in the middle of a release change from 4.7c to erp2005.

in the Z programm the function CLSC_SEARCH_OBJECTS was used .

in the new release the programm performed 26 times slower (due to this function) than in the old system. I couldn't figure out why since the function didn't change over the release and I couldn't find a difference in the inputparameter for the function.

strange enough the problem was solved when using the BAPI.

when I use the function CLSC_SEARCH_OBJECTS the problem is only when SLCODE = 2 (GE) and not 1 (EQ) as standard in the selectionchararteristics. in the old release it's no problem using SLCODE = 2 ?

we chechek that the function didn't change over the new release ?

anybody got a clue ?

Message was edited by:

A. de Smidt

[Former Member]

to old have to close down