Other checks on purchase requisition state

1 1 1 1 1 Rating 0% (0 Votes)

Tags: IF_RELEASABLE_MM , IS_REJECTION_ALLOWED , IS_RELEASE_ALLOWED , IS_RESET_REL_ALLOWED

In the previous article I've shown how to check if we can reset the rejection of the purchase requisition. In the same way you can check if rejection is allowed or if release is allowed or if reset of release is allowed. To do that you'll have to replace following piece of code from previous example fo_releasable->is_reset_rej_allowed( )

with one of the following:

fo_releasable->is_rejection_allowed( )
fo_releasable->is_release_allowed( )
fo_releasable->is_reset_rel_allowed( )

In next article I will show you how to reset the rejection of PR .

Add a comment

How to check if for purchase requisition rejection can be reset?

1 1 1 1 1 Rating 0% (0 Votes)

Tags: IF_PURCHASE_REQUISITION , IF_RELEASABLE_MM , MEPO_DOCUMENT , MEREQ_GET_FACTORY , IF_PURCHASE_REQ_FACTORY , IS_RESET_REJ_ALLOWED

Working with Purchase Requisitions in ABAP is quite pleasant job, but sometimes it's not so easy like with other documents types. You cannot easily say if Requisition is rejected and can be reset by checking EBAN table. You have to use OO PR objects to be able to do so. Bellow you can find a method how to check if you can reset the rejection of the requisition done in the WF.

Importing:

I_BANFN TYPE EBAN-BANFN ->Purchase Requisition Number

Exporting:

E_RESETABLE TYPE FLAG -> If rejection can be reset this parameter will be set to 'X'

Changing:

CO_FACTORY TYPE REF TO IF_PURCHASE_REQ_FACTORY -> Purchase requisition factory

Exception:

HEADER_COULDNT_BE_CREATED

Add a comment

Range to search in lower case fields

1 1 1 1 1 Rating 0% (0 Votes)

Tags: LOWER CASE , UPPER CASE , SEARCH , LOOP , SELECT

It may happen that you'll need to do select or loop on a base of the field which is kept in lower case, but you don't know exactly what's the value o field. In such case you may want to build a range of the possible values to be able to fulfill the task. Here is how to do it quite fast by doing FM:

function z_ab_prep_val_for_case_search.
*"--------------------------------------------------------------------
*"*"Local Interface:
*"  IMPORTING
*"     VALUE(I_TEXT) TYPE  CSEQUENCE
*"     VALUE(I_SIGN) TYPE  CHAR1
*"     VALUE(I_OPTION) TYPE  CHAR2
*"  EXPORTING
*"     REFERENCE(ER_RANGE) TYPE  STANDARD TABLE
*"--------------------------------------------------------------------
  field-symbols: <low> type any.
  field-symbols: <sign> type any.
  field-symbols: <opt> type any.
  field-symbols: <line> type any.
  field-symbols: <linenew> type any.
  field-symbols: <lownew> type any.
  field-symbols: <tab> type standard table.
  data: f_times type i.
  data: f_text type string.
  data: f_textnew type string.
  data: f_insidel type i.
  data: f_insidel2 type i.
  data: ft_data type ref to data.

  "create temp table and assign it to FS
  create data ft_data like er_range.
  assign ft_data->* to <tab>.

  f_text = i_text.

  "get lenght
  f_times = strlen( f_text ).
  "translate to upper case so we have always same start
  translate f_text to upper case.

  "append initial line to range and put first value into table
  append initial line to er_range assigning <line>.
  check sy-subrc eq 0.
  assign component 'LOW' of structure <line> to <low>.
  check sy-subrc eq 0.
  <low> = i_text. "all in uppercase
  assign component 'SIGN' of structure <line> to <sign>.
  check sy-subrc eq 0.
  <sign> = i_sign.
  assign component 'OPTION' of structure <line> to <opt>.
  check sy-subrc eq 0.
  <opt> = i_option.
  translate <low> to upper case.

  "create entries for each other combination of cases
  do f_times times.
    f_insidel2 = sy-index - 1.
    loop at er_range assigning <line>.
      assign component 'LOW' of structure <line> to <low>.
      check sy-subrc eq 0.
      if f_text+f_insidel2(1) ca '*+' and ( i_option eq 'CP' or i_option eq 'NP' ).

      else.
        append initial line to <tab> assigning <linenew>.
        check sy-subrc eq 0.
        assign component 'LOW' of structure <linenew> to <lownew>.
        check sy-subrc eq 0.
        assign component 'SIGN' of structure <linenew> to <sign>.
        check sy-subrc eq 0.
        <sign> = i_sign.
        assign component 'OPTION' of structure <linenew> to <opt>.
        check sy-subrc eq 0.
        <opt> = i_option.
        <lownew> = <low>.
        f_textnew = <lownew>+f_insidel2(1).
        translate f_textnew to lower case.
        <lownew>+f_insidel2(1) = f_textnew.
      endif.
    endloop.
    append lines of <tab> to er_range.
    refresh <tab>[].
  enddo.

endfunction.

Add a comment

Characteristic's own input screen - Part 8 - example of use

1 1 1 1 1 Rating 0% (0 Votes)

Attachments:
ZAB_CLASSIFICATIONS_POPUP.nugg
ZCL_ABAPBLOG_COM_CLASSIFIC.nugg

We got all needed functions, so I'll give you an example how to call the methods correctly to get characteristics update window like this:

Program bellow is reading firstly the info about stored values in given characteristic and then throws an update screen. After exiting from the screen it's saving data to database.

Add a comment

Characteristic's own input screen - Part 7 - save characteristic value to database

1 1 1 1 1 Rating 0% (0 Votes)

Attachments:
ZCL_ABAPBLOG_COM_CLASSIFIC.nugg

Tags: BAPI_OBJCL_CHANGE , BAPI_OBJCL_GETDETAIL

Now it's time to save the values entered into database. I will use here previously created method to move data from reference structure to BAPI tables, then I will read values from database to see if something has changed with BAPI_OBJCL_GETDETAIL, then save the values with BAPI_OBJCL_CHANGE. Just one remark, you have to pass all values always to that FM!

Importing:

I_DATA TYPE DATA OPTIONAL
value( I_CHANGE_NUMBER ) TYPE BAPI1003_KEY-CHANGENUMBER OPTIONAL -> Change Number

Exception:

NO_DATA

Add a comment

Characteristic's own input screen - Part 6 - move reference data to bapi structures

1 1 1 1 1 Rating 0% (0 Votes)

Attachments:
ZCL_ABAPBLOG_COM_CLASSIFIC.nugg

Tags: BAPI_CLASS_READ , COC1_FEATURE_CHECK

Our characteristics update screen was displayed, data was changes so we need to read the reference data and put the values into BAPI structures in order to be able to save the values to database.

I will use here BAPI_CLASS_READ to read all possible characteristics and COC1_FEATURE_CHECK to get characteristic details.

Importing:

I_DATA TYPE REF TO DATA

Changing:

CT_OBJVALUESNUM TYPE TT_BAPI1003_ALLOC_VALUES_NUM
CT_OBJVALUESCHAR TYPE TT_BAPI1003_ALLOC_VALUES_CHAR
CT_OBJVALUESCURR TYPE TT_BAPI1003_ALLOC_VALUES_CURR

Exceptions:

NO_DATA_TO_PASS

Add a comment

Characteristic's own input screen - Part 5 - show characteristic's own update screen

1 1 1 1 1 Rating 0% (0 Votes)

Attachments:
ZCL_ABAPBLOG_COM_CLASSIFIC.nugg

Tags: COC1_FEATURE_CHECK , CTMS_DDB_INIT , CTMS_CLASS_DDB , CTMS_DDB_SET_VAL_FROM_OBJECT , CTMS_DDB_SET_VALUE_INTERNAL , CTMS_DDB_SET_VALUE_ONLINE , CTMS_DDB_HAS_VALUES_INTERNAL

Now we're ready to build the data for screen output, call the update screen and then move the data back from screen to reference data. We will use here:

COC1_FEATURE_CHECK to get characteristic ID
CTMS_DDB_INIT to initialize memory
CTMS_CLASS_DDB to put in memory classification settings
CTMS_DDB_SET_VAL_FROM_OBJECT to set values in update screen from existing object (option)
CTMS_DDB_SET_VALUE_INTERNAL to set values in update screen in case of using reference data structure
CTMS_DDB_SET_VALUE_ONLINE to call the update screen
CTMS_DDB_HAS_VALUES_INTERNAL to check and get the values from the update screen after user action
zcl_abapblog_com_classific=>create_structure_for_class to create reference data structure
zcl_abapblog_com_classific=>move_screen_val_to_ref_data to move screen values to reference data
zcl_abapblog_com_classific=>clear_initial_line_api_vari to delete initial line for multiple values characteristics
zcl_abapblog_com_classific=>move_ref_data_to_screen_val to move reference data to update screen values table

Add a comment

Characteristic's own input screen - Part 4 - Move screen values to reference data

1 1 1 1 1 Rating 0% (0 Votes)

Attachments:
ZCL_ABAPBLOG_COM_CLASSIFIC.nugg

Tags: KKEK_CONVERT_FLOAT_TO_CURR , COC1_FEATURE_CHECK

In previous article I've shown how to move characteristics from reference data to screen values table, this method is doing opposite way from screen values table to reference data structure.

Importing:

IT_VALUES TYPE TT_API_VALI -> screen values table
I_ATNAM TYPE API_VALI-ATNAM -> Characteristic Name

Changing:

C_DATA TYPE REF TO DATA

Exceptions:

NO_DATA_TO_CHANGE

Add a comment

Characteristic's own input screen - Part 3 - Move reference data values to screen

1 1 1 1 1 Rating 0% (0 Votes)

Attachments:
ZCL_ABAPBLOG_COM_CLASSIFIC.nugg

Tags: COC1_FEATURE_CHECK

Before we can call the screen with the characteristic value to change we need to convert data from our reference data structure to table of type TT_API_VALI. Following method shows how to do it.

Importing:

I_ATNAMTYPE API_VALI-ATNAM ->Characteristic Name
I_DATATYPE REF TO DATA-> our reference data

Changing:

CT_VALUES TYPE TT_API_VALI-> Structure for characteristic screen

Exceptions:

NO_DATA_TO_CHANGE

Add a comment

Characteristic's own input screen - Part 2 - Clear Initial Line

1 1 1 1 1 Rating 0% (0 Votes)

Attachments:
ZCL_ABAPBLOG_COM_CLASSIFIC.nugg

Tags: CTMS_DDB_SET_VALUE_ONLINE , CTMS_DDB_SET_VALUE_INTERNAL , CTMS_DDB_HAS_VALUES_INTERNAL , CTMS_DDB_SET_VAL_FROM_OBJECT

We've got method to convert internal value to float, now it's time for next one which I didn't suppose it would be needed but when I was calling CTMS_DDB_SET_VALUE_ONLINE to show input screen with previously filled data by CTMS_DDB_SET_VALUE_INTERNAL then for multiple value characteristic I was always receiving one additional line to these which was passed by me in export parameters. The funny thing was that it wasn't the case when CTMS_DDB_SET_VAL_FROM_OBJECT was used. Of course this line was initial but the values were treated after as imputed by user. So as always I started to debug the code to see why it's happening. Finally I found that internal table WS in the function group CTMS was not refreshed during the call of CTMS_DDB_SET_VALUE_INTERNAL.

As I couldn't refresh it in any call of FM from this function group I had to use old trick with assignment of data from program in memory. But firstly I check with FM CTMS_DDB_HAS_VALUES_INTERNAL if any values are already there.

Importing:

IT_API_CHAR TYPE TT_API_CHAR -> Table type for structure api_char_tab

Add a comment