7.1: Error codes in BAPI Wrappers

[Former Member]

this relates to NW Mobile 7.1, SP04

Can anybody point me to some documentation, what kinds of errors should be set in the BAPI Wrapper?

my observations:

If a consistency check in the backend fails, my BAPI Wrapper returns 'E' in the BAPIRETURN2 structure, the change is discarded on the client.

How can I handle that on the client? I vaguely remember that there are some Listeners, but I could not find documentation on that.

Thanks, Andre

[Former Member · Accepted solution]

Hi Andre,

You can ask ur client developers to handle the type E messages.

Means, If the client get any message of type E then they can simply discard those records.. otherwise confirm it...

[Former Member]

Hi Oren,

nothing new so far.

I am using the following code copied from some other BAPI Wrapper. Some documentation would be helpful:

CALL FUNCTION 'BALW_BAPIRETURN_GET2'
  EXPORTING
    TYPE       = 'S'
    CL         = 'BGMSG'
    NUMBER     = '000'
    PAR1       = 'Success'
  IMPORTING
    RETURN     = BAPIRETURN.
APPENDbapireturn to return.

The documentation of the class "Rejection" hints, that you can set names of fields and more. But I do not know how. That's why I was asking.

Cheers, Andre

[Former Member]

Hi ,

Did you find solution for this issue

Oren

[Former Member]

Hi Sagar,

but how do I know that there was a problem?

Thanks, Andre

[Former Member]

Hi Sagar,

thanks, that is what I had hoped for ... I am the client developer too .-)

How do I access these return messages and how do I handle them?

for example:

- E: constistency check not met

- instead of dropping the record, notify user to change the record

Any pointers?

Thanks, Andre

[Former Member]

Hi andre,

Ya you can do one thing, rather dropping those records, you can maintain LOG and ERROR list at client side where you can ask user to change appropriate data and then ask them to SYNC again..