Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dump prone MESSAGE statement #15

Closed
dycsi-gabrielbaca opened this issue Sep 29, 2017 · 3 comments
Closed

Dump prone MESSAGE statement #15

dycsi-gabrielbaca opened this issue Sep 29, 2017 · 3 comments

Comments

@dycsi-gabrielbaca
Copy link

In method EXPORT_TO_TABLE of class ZCL_LOGGER, there is a MESSAGE statement in line 29 that generates a short dump whenever a message with no reference to a message class was used. Therefore, the method is not useful for any case no message classes are used.

I performed a manual correction in my system just like this:

    IF message-msgty IS NOT INITIAL.
      MESSAGE ID message-msgid
                      TYPE message-msgty
                      NUMBER message-msgno
                      INTO bapiret2-message
                      WITH message-msgv1 message-msgv2 message-msgv3 message-msgv4.
    ENDIF.
@epeterson320
Copy link
Collaborator

Hey, thanks so much for finding this. That's definitely a problem. Would you mind submitting your fix in a PR?

@alpex8
Copy link
Contributor

alpex8 commented Oct 11, 2017

@dycsi-gabrielbaca could you please clarify what lead to the error on your side, as I tried to reproduce it.
What I did was as follows:

DATA(logger) = /bitgrp/cl_bal_logger=>new( object = 'MYOBJECT' subobject = 'MYSUB' ).
logger->s( 'foo' ).
data(table) = logger->export_to_table( ).

This was working and the message class of my message was set to BL, number was 1. The content of this message in the class is & & & &

@dycsi-gabrielbaca
Copy link
Author

dycsi-gabrielbaca commented Oct 11, 2017 via email

@andkopp andkopp closed this as completed Apr 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants