Parameter como listbox, datos fijos

Me solicitaron mostrar por un parámetro de entrada, unos valores fijos (30, 60, 90, 120), así que tomé un Parameter, y con una función (VRM_SET_VALUES) cargamos los datos que queremos que seleccione el usuario.

*TOP:
PARAMETERS P_FXDT AS LISTBOX   LENGTH 3  VISIBLE LENGTH 10 OBLIGATORY .

AT SELECTION-SCREEN OUTPUT.

  DATA:
    lv_name  TYPE vrm_id,
    lt_list  TYPE vrm_values,
    lv_value TYPE vrm_value.

  lv_name = 'P_FXDT'. " Respetar mayúsculas
  lv_value-key = '30'.
  lv_value-text = 'Días'.
  APPEND lv_value TO lt_list.

  lv_value-key = '60'.
  APPEND lv_value TO lt_list.

  lv_value-key = '90'.
  APPEND lv_value TO lt_list.

  lv_value-key = '120'.
  APPEND lv_value TO lt_list.

  CALL FUNCTION 'VRM_SET_VALUES'
    EXPORTING
      id              = lv_name
      values          = lt_list
    EXCEPTIONS
      id_illegal_name = 0
      OTHERS          = 0.

"Fuente: https://answers.sap.com/questions/3608701/parameter-as-list-box.html

Comentarios

Entradas más populares de este blog

How to add custom field in Additional B Tab for SAP Sales Order In this article we want to explain step by step how to add custom field in SAP Sales Order transaction VA01/VA02/VA03. This time Mr ABAPGurus will give the tutorial of enhancement to add custom field in SAP Sales order. In this sample we will add new custom field for comments and customer satisfaction, this data will save into separate table from SAP Standard table ( VBAK / VBAP ). SAP provided us with ADDITIONAL TAB in the sales order transaction ( VA01/VA02/VA03 ) which allow customer to add custom fields. T he different between ADDITIONAL A and ADDITIONAL B is the ADDITIONAL A for field which already predefine in Sales Order Header ( VBAK ) fields and ADDITIONAL B is for field that freely define. This sample we will use ADDITIONAL B because we will store data from customer satisfaction into Z database table. 1. Create one Z table using SE11 SAP Transaction code. 2.Using SE38 Transactio...

A to Z of OLE Excel in ABAP 7.4

SAP users, both business and end users always need to download the output of a report to spreadsheet and do their analytics. The standard excel output from a report is very simple process but it is old fashioned and the spreadsheet looks quite boring. There is no default formatting and the users have to do all the hard work of changing the fonts, coloring the texts, marking the borders etc. Updated 16th Aug 2019 – If you are working in non-ABAP 7.4 (below), there is complete reference program for you too. Go to the end of this article. Thank you Legxis ( LeonievonK ) for the share. I acknowledge, whatever I mentioned above can be achieved in many ways programmatically. We can do it in the old traditional ABAP way but providing multiple tabs in the spreadsheet and formatting is quite tricky with non OLE method. OLE = Object Linking and Embedding The high level agenda of this article is to be the G.O.A.T. (ple...

BADI ME_PROCESS_PO_CUST para pedidos de compra

En este post vamos a ver una de las BADI´s mas utilizadas dentro de SAP. No es otro que la BADI ME_PROCESS_PO_CUST que se utiliza para incluir funcionalidad dentro de los pedidos de compra ( ME21N , ME22N , ME23N ) a través de los diferentes métodos que pone a nuestra disposición. Para los que no tengáis claro que es una BADI os dejo el siguiente link del blog donde ya hablamos sobre ellas: http://sapuniverse.blogspot.com.es/2014/05/badis-en-sap.html El primer paso si queremos utilizar esta BADI sería implementarla y activarla. Para ello debemos utilizar la transacción SE19. Aquí introduciremos el nombre de la BADI y pulsaremos sobre el botón " IMPLEMENTAR " como se ve en la siguiente imagen: Tras esto el sistema nos pedirá que asignemos un nombre a nuestra implementación. Tras aceptar el sistema nos mostrará la implementación que se va a crear. Podremos ver todos los métodos que están disponibles y en los que vamos a poder introducir código. A...

ABAP y SAP

Buscar este blog