InternalTable fields printing asterisks

[Former Member]

Hi all,

I have developed BAPI upload program. In this, inside the internaltable loop, I am appending some bapi tables with the internal

table field values. After the APPEND statements, when Iam again using the internal table fields, it is printing the

asterisks(*) in debugging. But I need to make use of these internal table fields. Can anybody look into this.

Thanks

Murali

[deepak_dhamat]

hi ,

Can you please tell us What exactly you were Doing ?

show us Code . and what you are expecting to happen

Regards

Deepak.

[Former Member]

Hi Deepak, please consider the code. Refer the bold text inside the code.

  loop at data_tab.

    t_head-doc_type            = 'YQT'.
    t_head-sales_org           = 'SEPL'.
    t_head-distr_chan          = 'PR'.
    t_head-division            = '10'.
    t_partner-partn_role       = 'AG'.
    t_partner-partn_numb       = data_tab-f2.
    t_sold_to_party-sold_to    = data_tab-f2.
    t_head-qt_valid_t          = data_tab-f3.
    t_item-material            = data_tab-f4.
    t_item-req_qty             = data_tab-f5.
    t_item-cond_type           = data_tab-f6.
    t_item-cd_type2            = data_tab-f8.
    t_item-cd_type3            = data_tab-f10.
    t_item-cd_type4            = data_tab-f12.
    t_item-cond_value          = data_tab-f7.
    t_item-cd_value2           = data_tab-f9.
    t_item-cd_value3           = data_tab-f11.
    t_item-cd_value4           = data_tab-f13.
    t_order_items_out-material = data_tab-f4.
    t_order_items_out-req_qty  = data_tab-f5.

    append t_head.
    append t_partner.
    append t_sold_to_party.
    append t_item.
    append t_order_items_out.
    append t_order_cfgs_inst.
    append t_order_cfgs_part_of.
    append t_order_cfgs_ref.
    append t_order_cfgs_value.         *bold* BAPI TABLES ARE APPENDED HERE . After append, the asterisk issue coming*bold*


      call function 'BAPI_QUOTATION_CREATEFROMDATA'
        exporting
          order_header_in     = t_head
          without_commit      = 'X'
          convert_parvw_auart = 'X'
        importing
          salesdocument       = salesdocument
          sold_to_party       = t_sold_to_party
          return              = t_return
        tables
          order_items_in      = t_item
          order_partners      = t_partner
          order_items_out     = t_order_items_out
          order_cfgs_ref      = t_order_cfgs_ref
          order_cfgs_inst     = t_order_cfgs_inst
          order_cfgs_part_of  = t_order_cfgs_part_of
          order_cfgs_value    = t_order_cfgs_value.

      call function 'BAPI_TRANSACTION_COMMIT'
        exporting
          wait = ' '.

      if sy-subrc = 0.
        write :/ 'Quotation ', salesdocument, ' Created'.
      endif.
*bold*  BAPI calling functionality is completed here *bold*


*bold* Here iam using the internal table field  " data_tab-f14 " for some condition. but it is displaying asterisks in debugging *bold*
        select single knumv from vbak into v_knumv
          where vbeln = salesdocument.
        commit work.
        select * from konv into table t_konv
          where knumv = v_knumv.

        read table t_konv with key kschl = data_tab-f14       "Condition Type 5
                                   knumv = v_knumv.

But my problem solved to some extent.

Why this happens.

please suggest me your approach if any.

Thanks and Regards

Murali

[Former Member]

After your select from vbak you have a nonsensical commit work. But, you never check sy-subrc to see if your select statements or read statements were successful. How is t_konv defined? Obsolete usage with a header? I hope so, since you've not defined anything to read into.

[SuhaSaha]

>

> After the APPEND statements, when Iam again using the internal table fields, it is printing the 
> asterisks(*) in debugging. But I need to make use of these internal table fields.

Hello Murali,

I think you're using [loop-control break statements|http://help.sap.com/abapdocu_702/en/abapat_itab.htm] hence you're getting '*' in place of field values.

You've remember while using these statements that only the "left-justified" field values are available, for the right-justified fields you'll get '*' values.

A simple workaround is to copy the workarea content to a another variable & use the latter for your processing inside the control-break block!

Further info(code snippet) is available in the forums.

BR,

Suhas

[Former Member]

Hi Suhas,

Thanks for your reply.

I have done what exactly you told.

Now my Problem solved.

Thanks

Murali