PAI validation

Hi Group,
When I am validating one field(for Mandatory check) in one of my transactions using chain and End chain with throwing error message,its working fine hwne I entered and also when I go for first time save in that tab(by throwing Error),when I go to some other tab( in the same transaction) and I click save it is allowing to save and the data in that particular tab (where Validation check working) erased.
Can any body suggest how to solve this

Hi,
Instead of using PAI validation, try making the field mandatory in attributes.
Path: Screen Layout->Field Attributes(DBL Clk field)-> Attributes frame-> Program-> check Input field -> Finally Select "Required" from drop down for input.
Let me know if you have any questions.
BR
Rakesh

Similar Messages

Editable alv: add custom validation and display "errors" in protocol list

Hi,
What I want to do:
PAI validation of editable alv with displaying error's in the protocol list by adding custom entries to the existing protocol object.
What is my problem:
After registering "data_changed event", the protocol list don't appear.
My understanding is, that the object "er_data_changed" is passed by the event "data_changed"
an so I thought I can add some more entries to the protocol list.
After "de-registering" the "data_changed" event, the protocol appears with the standard errros messages (e.g. "input to numeric" by enter charachters)
One more hint:
By creating a new object "er_data_changed" in the handler method the protocol list works, but I would like to append entries to the object that was passed with the event.
Probably I've misunderstand something, please help !
My coding:
PAI:
trigger event "data_changed" -> calls handler method
CALL METHOD r_myalv->check_changed_data
 IMPORTING
 e_valid = is_valid.
stop processing
IF is_valid NE 'X'.
 MESSAGE 'invalid input' TYPE 'E' .
ENDIF.
handler method:
handle_data_changed FOR EVENT data_changed OF cl_gui_alv_grid IMPORTING e_ucomm
 er_data_changed.
METHOD handle_data_changed.
 data: ls_mod_cell type lvc_s_modi.
 CALL METHOD er_data_changed->add_protocol_entry
 EXPORTING
 i_msgid = 'SU'
 i_msgty = 'E'
 i_msgno = '000'
 i_msgv1 = 'This is a test !'
 i_fieldname = ls_mod_cell-fieldname.
 er_data_changed->refresh_protocol( ).
 er_data_changed->DISPLAY_PROTOCOL( ).
ENDMETHOD. "handle_data_changed

Dear Olaf,
 If understood correctly, you want to Edit an ALV and do some data validations when some data is changed in an ALV. To do this follow the following steps:
1. Before displaying ALV, Register the edit event.
* Set cell modified to trigger data_changed
CALL METHOD go_alv_grid->register_edit_event
EXPORTING
i_event_id = cl_gui_alv_grid=>mc_evt_modified.
2. Register the event DATA_CHANGED of class CL_GUI_ALV_GRID & handle the event.
SET HANDLER lo_event_receiver->handle_data_changed FOR go_alv_grid.
The event DATA_CHANGED of class CL_GUI_ALV_GRID has a parameter ER_DATA_CHANGED which is of type CL_ALV_CHANGED_DATA_PROTOCOL.
This er_data_changed has internal table MT_MOD_CELLS(contains index of records changed ) & MP_MOD_ROWS(contains the changed row), using these update your internal table accordingly.
DATA : wa_mod_cell TYPE lvc_s_modi.
FIELD-SYMBOLS: <fs> TYPE table.
LOOP AT er_data_changed->mt_mod_cells INTO wa_mod_cell.
ASSIGN er_data_changed->mp_mod_rows->* TO <fs>.
READ TABLE <fs> INTO wa_output INDEX wa_mod_cell-tabix.
MODIFY lt_output FROM wa_output INDEX wa_mod_cell-row_id.
ENDLOOP.
3. Here it self you can do the required data validations(No need of any PAI modules) as below.
IF wa_orders-zfstfirmtyp = c_9.
MESSAGE s288(zcsp).
DELETE er_data_changed->mt_mod_cells.
EXIT.
ENDIF.
Regards
Kesava

PAI is not triggered after I choose value in F4

Hello experts,
I fight with the following problem:
On my screen I use input field (ucf_s_coi_afd03_ct-xrproc_param) and I coded the F4 help for it manually
PROCESS ON VALUE-REQUEST.
FIELD ucf_s_coi_afd03_ct-xrproc_param
MODULE req_xrproc_param_2006.
After I press f4 on this field, the values are correctly listed but after I choose one value (double click), I would expect that the PAI is triggered but it is not. I have to press ENTER, only then.
Is there a way how to trigger the PAI after the value is chosen?
I found one way, but I don't want to use it:
If I change the input field into "List box" or "List box with key", then I can assign function code to it and if I do that, then it works - PAI is triggered after value is chosen. However, I don't want to use list box, I need standard input field.
Any ideas?
Regards,
Tomas

>
Jonathan Coleman wrote:
> Rather than triggering the PBO in order to fill in other fields on the screen from your POV event, the usual approach I've seen is to call the function DYNP_VALUES_UPDATE (which is quite well documented) e.g. you could get a customer number from your F4 dropdown, then retrieve their name and address and populate that data back into the screen all from within the "process on value-request" module logic.
>
> Jonathan
The original problem (or at least my orignal problem) which was solved by the SUPPRESS DIALOG was how to trigger my PAI validation - not the PBO though that of course follows on afterwards - immediately on selecting a value from a search help in order to carry out a further check on the value selected. I've used DYNP_VALUES_UPDATE in other situations, but it was not a suitable solution for me here.

Validation while delimiting IT185

Hi,
When user tries to delimit a particular record in IT185 through PA30, we need to do some validation.
I am trying this while setting a break-point in exit : ZXPADU01 & ZXPADU02. but it doesn't stop there.
Kindly let me know any exit or BADI where in I can add a specific check.
Thanks...

Hi Sam,
You can use both BADI as well as user exit for validation when delimiting the infotype 0185.
BADI : you can use badi HRBAS00INFTY method AFTER_INPUT or BEFORE_UPDATE to validate some thing after input.
User Exit: You can use user exit ZXPADU02 for all the PAI validations, but for this you will need to create a project in SMOD/CMOD and activate it to activate the user exit.
Regards,
Ramnivas

Validity Period for BP relationships

Hello Experts,
We are having a problem with the validity date in BP relationship. Our partner functions get replicated from ECC to CRM. However, if one of the partner function detail changes, the relationship come up with two values for the same partner function which is correct but both show the same validity to and from date.
For eg if we have the payer XYZ for the sold to ABC from validity period 2008 to 2009 and the payer changed to EFG from 2009 to 9999, the relationship tab shows both the payer valid from 01.01.01 to 01.01.9999.
The system then fails to determine the correct payer if an order comes through from MSA and stops with an error in CRM which then has to be processed manually.
How can this problem be resolved so that the validity period comes up with the correct dates and the system can automatically pick up the correct partners?
PT

Hi,
Please go to transaction BUBN and in that one field group would be there called 'Relationship Category/Role Definition Category'.
Select that and go to "Field Group--> Fields" and add the following two fields:
Table                        FieldName
BUS050DFLD           DATE_FROM_STR
BUS050DFLD           DATE_TO_STR
Dont check any of the check boxes like "input field" and "not a required field".
Save it and come out and then again launch BP trx to get the desired result.
This is how i solved my problem in CRM 4.0.
Please let me know if you have problems.
Regards
Sidd

Output error

Hi,
Below is my code : When I execute this it is not displaying any data. Right now I don't want the values to be displayed in ALV just normal report.
*& Report ZTESTING1
REPORT ZTESTING1.
TABLES:
 SSCRFIELDS, " Fields on selection screens
 BSIS, " Accounting: Secondary Index for G/L Accounts
 BSEG, " Accounting Document Segment
 BKPF, " Accounting Document Header
 SKA1, " G/L Account Master (Chart of Accounts)
 T001A, " Add. Local Currencies Ctrl for Company Code
 TCURR. " Exchange Rates
DATA DECLARATIONS
INCLUDE <ICON>.
ALV grid reporting data *
TYPE-POOLS: SLIS.
DATA DECLARATIONS
CONSTANTS: GC_FX_SET TYPE SETNAMENEW VALUE 'ZFI_RP_1241_FXACCT',
 GC_CTA_SET TYPE SETNAMENEW VALUE 'ZFI_RP_1241_CTAACCT',
 GC_ICFX_SET TYPE SETNAMENEW VALUE 'ZFI_RP_1241_ICFXACCT'.
DATA: GV_SET_LINE_COUNTER TYPE I,
 GV_FX_ACCOUNT LIKE BSEG-HKONT,
 GV_CTA_ACCOUNT LIKE BSEG-HKONT,
 GV_ICFX_ACCOUNT LIKE BSEG-HKONT,
 GT_SET_VALUES LIKE RGSBV OCCURS 0 WITH HEADER LINE.
DATA : DATUM TYPE SY-DATUM .
ALV Grid structures
DATA: GT_FIELDCAT TYPE LVC_T_FCAT,
 GS_FIELDCAT TYPE LVC_S_FCAT,
 GT_EVENTS TYPE SLIS_T_EVENT,
 GS_EVENTS TYPE SLIS_ALV_EVENT,
 GT_EXTAB TYPE SLIS_T_EXTAB,
 GT_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER,
 GS_LINE TYPE SLIS_LISTHEADER,
 GT_SELFIELD TYPE SLIS_SELFIELD.
DATA: GT_RSPARAMS TYPE TABLE OF RSPARAMS.
Data for ALV variant
DATA GV_REPNAME LIKE SY-REPID.
DATA GV_X_VARIANT LIKE DISVARIANT.
DATA GV_EXIT(1) TYPE C.
DATA GV_SAVE(1) TYPE C.
DATA GV_VARIANT LIKE DISVARIANT.
DATA GV_STATUS TYPE SLIS_FORMNAME VALUE 'F_STANDARD_02'.
Internal table for BSIS data
DATA : BEGIN OF GT_FXENTRIES OCCURS 0,
 HKONT LIKE BSIS-HKONT, " GL Accnt
 BUKRS LIKE BSIS-BUKRS, " Company Code
 MONAT LIKE BSIS-MONAT, " Period
 BLART LIKE BSIS-BLART, " Doc. Type
 WRBTR LIKE BSIS-WRBTR, " Amt. in DC
 WAERS LIKE BSIS-WAERS, " Doc. Currency
 DMBTR LIKE BSIS-DMBTR, " Amt in Local Currency
 DMBE2 LIKE BSIS-DMBE2, " Amt in Global Currency
 PRCTR LIKE BSIS-PRCTR, " Profit Center
 BELNR LIKE BSIS-BELNR, " Doc. Number
 GJAHR LIKE BSIS-GJAHR, " Year
 BUDAT LIKE BSIS-BUDAT, " Posting Date
 VBUND LIKE BSIS-VBUND, " Trading Partner
 PPRCT LIKE BSIS-PPRCT, " Partner Profit Center
 KOSTL LIKE BSIS-KOSTL, " Cost Center
 PROJK LIKE BSIS-PROJK, " WBS Element
 END OF GT_FXENTRIES.
Internal table for SKAT (GL Description)
DATA : BEGIN OF GT_GLTEXT OCCURS 0,
 SAKNR LIKE SKAT-SAKNR, " GL Number
 TXT50 LIKE SKAT-TXT50, " GL Description
 END OF GT_GLTEXT.
Internl table for bseg for Auto Posting
DATA : BEGIN OF GT_BSEG OCCURS 0,
 XAUTO LIKE BSEG-XAUTO, " Auto Post
 END OF GT_BSEG.
*Internal table for BKPF Document header for user name
DATA : BEGIN OF GT_DOCHEADER OCCURS 0,
 USNAM LIKE BKPF-USNAM, " User Name
 END OF GT_DOCHEADER.
*Internal table for Group Currency
DATA : BEGIN OF GT_GRPCURR OCCURS 0,
 MANDT LIKE T000-MANDT, " Client specific
 MWAER LIKE T000-MWAER, " group currency
 END OF GT_GRPCURR.
Final Internal table for display
DATA : BEGIN OF GT_FINALFX OCCURS 0.
 INCLUDE STRUCTURE GT_FXENTRIES.
 INCLUDE STRUCTURE GT_GLTEXT.
 INCLUDE STRUCTURE GT_BSEG.
 INCLUDE STRUCTURE GT_DOCHEADER.
 INCLUDE STRUCTURE GT_GRPCURR.
DATA : END OF GT_FINALFX.
*Selection Screen
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
SELECT-OPTIONS : SO_BUKRS FOR BSIS-BUKRS," Company Code
 SO_GJAHR FOR BSIS-GJAHR DEFAULT SY-DATUM(4). " Fiscal
" Year
PARAMETERS : SP_MONAT LIKE BSIS-MONAT. " Period
SELECTION-SCREEN END OF BLOCK B1.
SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-002.
PARAMETERS : SP_WAERS LIKE BSIS-WAERS, " Amt in Document Currency
 SP_BLART LIKE BSIS-BLART. " Document Type
SELECTION-SCREEN END OF BLOCK B2.
SELECTION-SCREEN BEGIN OF BLOCK B3 WITH FRAME TITLE TEXT-003.
PARAMETERS SP_VBUND LIKE BSIS-VBUND. "Trading Partner
SELECTION-SCREEN END OF BLOCK B3.
SELECTION-SCREEN BEGIN OF BLOCK B4 WITH FRAME TITLE TEXT-004.
SELECT-OPTIONS : SO_HKONT FOR BSIS-HKONT. "G/L Account Number
PARAMETERS : SP_FX RADIOBUTTON GROUP RADI , " Foreign Exchange
 SP_CTA RADIOBUTTON GROUP RADI, " Cummulative Translation
 " Adj
 SP_IC_FX RADIOBUTTON GROUP RADI, " Inter Co. FX
 SP_XAUTO AS CHECKBOX USER-COMMAND FLAG. " Auto Post System
SELECTION-SCREEN END OF BLOCK B4.
INITIALIZATION
INITIALIZATION.
PERFORM F_PRIOR_PERIOD.
EVENT: AT SELECTION-SCREEN.
A T S E L E C T I O N S C R E E N
Process After Input (PAI)
Validating selection screen fields
AT SELECTION-SCREEN.
PERFORM F_VALIDATE_GLACCOUNT.
EVENT: START-OF-SELECTION
START-OF-SELECTION.
*G/L Account validation in the selection screen
IF SP_FX = 'X' AND SP_XAUTO NE 'X'.
 PERFORM F_FX_WITH_AUTOPOST.
ENDIF.
*& Form F_FX_WITH_AUTOPOST
SELECT THE DATA BASING ON THE FOREIGN EXCHANGE AND SYSTEM AUTO
POSTING
FORM F_FX_WITH_AUTOPOST.
SELECT HKONT BUKRS MONAT BLART WRBTR WAERS DMBTR
 WAERS DMBE2 PRCTR BELNR GJAHR
 BUDAT VBUND PPRCT KOSTL PROJK
 FROM BSIS
 INTO CORRESPONDING FIELDS
 OF table GT_FXENTRIES WHERE BUKRS IN SO_BUKRS
 AND GJAHR IN SO_GJAHR
 AND MONAT = SP_MONAT
 AND WAERS = SP_WAERS
 AND BLART = SP_BLART
 AND VBUND = SP_VBUND
 AND HKONT IN SO_HKONT.
LOOP AT GT_FXENTRIES.
 WRITE : / GT_FXENTRIES-HKONT, GT_FXENTRIES-BUKRS.
ENDLOOP.
ENDFORM. "F_FX_WITH_AUTOPOST
Please help me out.
Thanks.
Message was edited by: Pavan Panduru

Hi pavan,
there is no problem with your program. you have to identify your test data properly. for checking purpose i made some changes to your code, it is working fine.
just check this in your system also,...
REPORT ZTEST .
TABLES:
SSCRFIELDS, " Fields on selection screens
BSIS, " Accounting: Secondary Index for G/L Accounts
BSEG, " Accounting Document Segment
BKPF, " Accounting Document Header
SKA1, " G/L Account Master (Chart of Accounts)
T001A, " Add. Local Currencies Ctrl for Company Code
TCURR. " Exchange Rates
* DATA DECLARATIONS
INCLUDE <ICON>.
* ALV grid reporting data *
TYPE-POOLS: SLIS.
* DATA DECLARATIONS
CONSTANTS: GC_FX_SET TYPE SETNAMENEW VALUE 'ZFI_RP_1241_FXACCT',
GC_CTA_SET TYPE SETNAMENEW VALUE 'ZFI_RP_1241_CTAACCT',
GC_ICFX_SET TYPE SETNAMENEW VALUE 'ZFI_RP_1241_ICFXACCT'.
DATA: GV_SET_LINE_COUNTER TYPE I,
GV_FX_ACCOUNT LIKE BSEG-HKONT,
GV_CTA_ACCOUNT LIKE BSEG-HKONT,
GV_ICFX_ACCOUNT LIKE BSEG-HKONT,
GT_SET_VALUES LIKE RGSBV OCCURS 0 WITH HEADER LINE.
DATA : DATUM TYPE SY-DATUM .
* ALV Grid structures
DATA: GT_FIELDCAT TYPE LVC_T_FCAT,
GS_FIELDCAT TYPE LVC_S_FCAT,
GT_EVENTS TYPE SLIS_T_EVENT,
GS_EVENTS TYPE SLIS_ALV_EVENT,
GT_EXTAB TYPE SLIS_T_EXTAB,
GT_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER,
GS_LINE TYPE SLIS_LISTHEADER,
GT_SELFIELD TYPE SLIS_SELFIELD.
DATA: GT_RSPARAMS TYPE TABLE OF RSPARAMS.
* Data for ALV variant
DATA GV_REPNAME LIKE SY-REPID.
DATA GV_X_VARIANT LIKE DISVARIANT.
DATA GV_EXIT(1) TYPE C.
DATA GV_SAVE(1) TYPE C.
DATA GV_VARIANT LIKE DISVARIANT.
DATA GV_STATUS TYPE SLIS_FORMNAME VALUE 'F_STANDARD_02'.
* Internal table for BSIS data
DATA : BEGIN OF GT_FXENTRIES OCCURS 0,
HKONT LIKE BSIS-HKONT, " GL Accnt
BUKRS LIKE BSIS-BUKRS, " Company Code
MONAT LIKE BSIS-MONAT, " Period
BLART LIKE BSIS-BLART, " Doc. Type
WRBTR LIKE BSIS-WRBTR, " Amt. in DC
WAERS LIKE BSIS-WAERS, " Doc. Currency
DMBTR LIKE BSIS-DMBTR, " Amt in Local Currency
DMBE2 LIKE BSIS-DMBE2, " Amt in Global Currency
PRCTR LIKE BSIS-PRCTR, " Profit Center
BELNR LIKE BSIS-BELNR, " Doc. Number
GJAHR LIKE BSIS-GJAHR, " Year
BUDAT LIKE BSIS-BUDAT, " Posting Date
VBUND LIKE BSIS-VBUND, " Trading Partner
PPRCT LIKE BSIS-PPRCT, " Partner Profit Center
KOSTL LIKE BSIS-KOSTL, " Cost Center
PROJK LIKE BSIS-PROJK, " WBS Element
END OF GT_FXENTRIES.
* Internal table for SKAT (GL Description)
DATA : BEGIN OF GT_GLTEXT OCCURS 0,
SAKNR LIKE SKAT-SAKNR, " GL Number
TXT50 LIKE SKAT-TXT50, " GL Description
END OF GT_GLTEXT.
* Internl table for bseg for Auto Posting
DATA : BEGIN OF GT_BSEG OCCURS 0,
XAUTO LIKE BSEG-XAUTO, " Auto Post
END OF GT_BSEG.
*Internal table for BKPF Document header for user name
DATA : BEGIN OF GT_DOCHEADER OCCURS 0,
USNAM LIKE BKPF-USNAM, " User Name
END OF GT_DOCHEADER.
*Internal table for Group Currency
DATA : BEGIN OF GT_GRPCURR OCCURS 0,
MANDT LIKE T000-MANDT, " Client specific
MWAER LIKE T000-MWAER, " group currency
END OF GT_GRPCURR.
* Final Internal table for display
DATA : BEGIN OF GT_FINALFX OCCURS 0.
 INCLUDE STRUCTURE GT_FXENTRIES.
 INCLUDE STRUCTURE GT_GLTEXT.
 INCLUDE STRUCTURE GT_BSEG.
 INCLUDE STRUCTURE GT_DOCHEADER.
 INCLUDE STRUCTURE GT_GRPCURR.
DATA : END OF GT_FINALFX.
*Selection Screen
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
SELECT-OPTIONS : SO_BUKRS FOR BSIS-BUKRS," Company Code
SO_GJAHR FOR BSIS-GJAHR DEFAULT SY-DATUM(4). " Fiscal
" Year
SELECT-OPTIONS : SP_MONAT for BSIS-MONAT no intervals no-extension.
SELECTION-SCREEN END OF BLOCK B1.
SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-002.
SELECT-OPTIONS : SP_WAERS for BSIS-WAERS no intervals no-extension,
" Amt in Document Currency
SP_BLART for BSIS-BLART no intervals no-extension. " Document Type
SELECTION-SCREEN END OF BLOCK B2.
SELECTION-SCREEN BEGIN OF BLOCK B3 WITH FRAME TITLE TEXT-003.
SELECT-OPTIONS SP_VBUND for BSIS-VBUND no intervals no-extension."Trading Partner
SELECTION-SCREEN END OF BLOCK B3.
SELECTION-SCREEN BEGIN OF BLOCK B4 WITH FRAME TITLE TEXT-004.
SELECT-OPTIONS : SO_HKONT FOR BSIS-HKONT. "G/L Account Number
PARAMETERS : SP_FX RADIOBUTTON GROUP RADI , " Foreign Exchange
SP_CTA RADIOBUTTON GROUP RADI, " Cummulative Translation
" Adj
SP_IC_FX RADIOBUTTON GROUP RADI, " Inter Co. FX
SP_XAUTO AS CHECKBOX USER-COMMAND FLAG. " Auto Post System
SELECTION-SCREEN END OF BLOCK B4.
** INITIALIZATION
INITIALIZATION.
* PERFORM F_PRIOR_PERIOD.
* EVENT: AT SELECTION-SCREEN.
* A T S E L E C T I O N S C R E E N
* Process After Input (PAI)
* Validating selection screen fields
AT SELECTION-SCREEN.
* PERFORM F_VALIDATE_GLACCOUNT.
* EVENT: START-OF-SELECTION
START-OF-SELECTION.
*G/L Account validation in the selection screen
* IF SP_FX = 'X' AND SP_XAUTO NE 'X'.
PERFORM F_FX_WITH_AUTOPOST.
* ENDIF.
*& Form F_FX_WITH_AUTOPOST
* SELECT THE DATA BASING ON THE FOREIGN EXCHANGE AND SYSTEM AUTO
* POSTING
FORM F_FX_WITH_AUTOPOST.
SELECT HKONT BUKRS MONAT BLART WRBTR WAERS DMBTR
WAERS DMBE2 PRCTR BELNR GJAHR
BUDAT VBUND PPRCT KOSTL PROJK
FROM BSIS
INTO CORRESPONDING FIELDS
OF TABLE GT_FXENTRIES
WHERE BUKRS IN SO_BUKRS
AND GJAHR IN SO_GJAHR
 AND MONAT in SP_MONAT
AND WAERS in SP_WAERS
AND BLART in SP_BLART
AND VBUND in SP_VBUND
AND HKONT IN SO_HKONT.
LOOP AT GT_FXENTRIES.
 WRITE : / GT_FXENTRIES-HKONT, GT_FXENTRIES-BUKRS.
ENDLOOP.
ENDFORM. "F_FX_WITH_AUTOPOST
Regards
vijay

BADI or Userexit For QM01(Quality Notification)

Dear Experts,
I want to add some extra fields in QM01 .
Is there is any BADI or userexit available for QM01(Quality Notification).
Please give me some solution.
Regards,
Sanket.

Hi,
SPRO-->Quality management >Notification> Overview of notification types-->Select the notification & 90 give the customer specific screen area
this is the process where we will add the screen...
Go to Function group is XQQM in SE80....create the screen which you have added in config...example 0090 ....
No wgo to includes tab you will see one z*TOP include there you declare the fields you want on this custom screen ....
example : dist type char3.
In the PBO and PAI validations you can make for the added fields as we do in normal Module pool.
In the PAI event create a module and pass the values to the structure VIQMEL.
for example if your added field is dist.
Pass as
VIQMEL-dist = dist.
Go to cmod create a project ,give the enhacement QQMA0001.
In the exit EXIT_SAPMIWO0_009
Pass those values to the req structure which needs to be populated.
example :
i_viqmel-dist = dist.
move-corresponding i_viqmel to e_viqmel.
--> Go to standard table where the values need to be updated(qmel) add one append structure with the req fields
Thanks,
Shailaja Ainala.

Bonsoir, j'ai acheté sur Adobe Reader le convertisseur pdf en format word, ça ne marche pas, faut-il attendre que le paiement soit validé pour que ça se mette en route? merci

bonsoir, j'ai acheté sur Adobe Reader le convertisseur pdf en format word, ça ne marche pas, faut-il attendre que le paiement soit validé pour que ça se mette en route? merci

Est-ce qu'il y a ici un technicien de chez Adobe comme on peut le voir su le forum en anglais ?
au moins qu'il me donne une réponse sur la limite du nombre de fichier mémorisés .
j'ai compris un truc :
j'ai beau réglé un fichier à la forme voulu , à un moment il redeveins comme avant ; en fait il suffit que je change
les réglages d'affichage dans x nombres de fichiers PDF pour que ça annule les réglages du fichier .
si je ne veux pas que les fichiers s'ouvrent en grand comme le fichier télé , il faut d'abord cliquer sur un fichier ayant la forme déjà établie à ma façon , ensuite si je clique sur les suivants ça va ....mais si je clique d'abord sur le fichier télé ( je dis télé mais c'est valable aussi avec un fichier déjà établis et que j'ai élargi ) et que je clique sur les suivants Adobe me les modife .
J'ai laissé les fenêtres qui ont été modifiée , j'ai cliqué sur au moins 10 nouveaux fichiers , je reviens sur ceux qui ont été anormalement modifié ils ont repis leur forme .
la seule chose que je n'arrive pas à déterminer c'est pourquoi le fichier téléchargé ( alors que j'en ai des identiques dans ma partion ) se déforme après x clics ailleurs .
et pourquoi , même sur le Bureau et après avoir modfier sa forme , il reprend sa forme initale .au bout d'un moment .
la chose qu'aurait dû inclue Adobe c'est un verrouillage de fenêtre , on garde la même pour tous ( un peu plus grande que le format A4 ou alors un choix par possible ) et ensuite libre de la dimensionné et qu'elle conserve son réglage ( peu importe ce que l'auteur a décidé ) .
Vu que je n'ai pas de réponse, ni personne qui me donne son avis sur le simple fait de tester, je vais me tourner vers un autre lecteur ....qui j'espère sera plus fiable et surout plus cohérent !
Message was edited by: Loyan

Impossible de changer ma CB sur itune car il est ecrit que le mode de paiment n'est pas valide. Or les coordonnes sont bonne, j'e suis passé d'un pc a un mac. C'est pour ça?

Impossible de changer ma CB sur itune car il est ecrit que le mode de paiment n'est pas valide. Or les coordonnes sont bonne, j'e suis passé d'un pc a un mac. C'est pour ça?

Non ça n'a rien à voir. Il se peut que ta banque ne permet pas d'ajouter ta CB, moi j'ai du passer un coup de fil à la mienne pour qu'ils me permettent d'afficher ma carte sur mon compte iTunes. Essaie voir si ça marche?

Validating records into a maintenance view

Hi folks!
I have a simple Z table (say ZTABLE) and a Z view based on it with some related description (say ZVIEW). The ZTABLE has a DEC field (called COEF) with 2 decimals and it should have only numbers between 0 and 1.
I set the valid interval from 0 to 1 but, as help says, it's only checked for CHAR, NUMC, DEC, INT1, INT2 and INT4 data types. Not for DEC.
Then I use an event on ZVIEW. On SE11 I went to "Table maintenance generator" - Environment - Modification - Events. So there I put the 05 event (Creating a new entry) and I programed the check. It works fine for new entries, but if you have a record on table and you want to change the COEF field you can put there any number, even outside the 0-1 range.
I tried with the 01 event (Before saving the data in the database) but it seams to be called only for last record.
Could anybody tell me what can I do?
Thanks!

Hi,
Since it is a Z TABLE..
You can directly modify the flow logic in SE51.
Go to SE51
Give the program name - SAPL + Function group name
Screen number
Press change..
In the flow logic..
Add a module after the FIELD ztable-number, in the PAI event..
Ex..
FIELD ZTABLE-NUMBER MODULE NUMBER_CHECK.
And in the module validate the number..
MODULE NUMBER_CHECK INPUT.
IF ZTABLE-NUMBER <> '0' OR
ZTABLE-NUMBER <> '1'.
MESSAGE E208(00) WITH 'Not a valid number'.
ENDIF.
ENDMODULE.
Thanks,
Naren

Ativação da BadI - Conversão e validação de numeros de cod de barras

Bom dia,
Estou com um problema no qual eu preciso ativar a BadI - Conversão e validação de numeros de cod de barras boleto brasileiro que esta no SPRO ->Contab. financ.-> contab. clien. fornec. -> trans. contab.-> Saida de pag.-> saida de pag. aut.-> meio de pag. -> Config.esp.de pais p/ meio de pag.
Ao clicar nesta badI, vejo que a BOLETO_BARCODE_BR já está implementada, só falta ativar. até consigo ativa-la, quando eu tendo gravar não acontece nada, e é so eu sair da tela e voltar que eu vejo que ela segue desativada.
Analizando o Doc. de ajuda, A SAP me da as seguintes instruções:
Implementar o BAdI ou ativar a implementação fornecida (BOLETO_BARCODE_BR). Para tal, seguir as Instruções correspondentes.
Seguindo as instruções (no caso de Reimplementa-la) no passo 4 - que diz "4. Gravar as entradas e efetuar a atribuição a um pacote."
aparece um pop up pedindo o seguinte: "Executar registro em Online Service system (oss) R/3" e que ao executar esse regitro eu receberei uma chave de acesso.
1- O procedimento que eu estou executando está correto? Pois me parece muito estranho eu ter que reimplatar a BadI para assim eu poder ativa-la.
2- Se for este realmente o procedimento, como é que eu abro esta OSS? o que é preciso? pois eu nunca fiz este procedimento anteriormente.
agradeço desde já.
Paulo

Bom dia Paulo,
A BAdI e esta implementação standard foram liberadas na SAP Note 784748.
Lá tem o passo-a-passo para a criação de tudo e ativação.
Para personalizar, como validações, a SAP recomenda que você crie a própria implementação ao invés de modificar a implementação standard BOLETO_BARCODE_BR, na nota tem estes passos.
Não sei se respondi a pergunta, mas qualquer coisa é só retrucar.
Atenciosamente, Fernando Da Ró

Date validation in ALV Grid output

Hi Experts,
I have created an OOP ALV output. There are a couple of date fields on the report output which are editable. I have referred the standard DATS type and hence I ma getting F4 help for date on the report output.
Now, If the user enters an invalid date manually (without F4), the CHECK_CHANGED_DATA method of the CL_GUI_ALV_GRID does not read this invalid value and hence I am not able to validate the date.
I do not want to create a custom search help for date.
Please suggest how to validate the date in this case.
Thanks.
Regards,
Rudresh

Hi Rudresh,
In PBO module, set handler for event 'DATA_CAHNGED'
In PAI module always call 'check_changed_data( )' after a custom button click like below.
Inside handler method of event 'DATA_CAHNGED' do validation for date.
*PBO
module status_0100 output.
*Setting handler for event data_changed
        set handler g_o_main->data_changed for g_o_grid.
endmodule.
*PAI
module user_command_0100 input.
clear: ok_code.
ok_code = sy-ucomm.
case ok_code.
    when 'SAVE'. " Function code of ur custom button
      g_o_grid->check_changed_data( ). " Raises event 'DATA_CAHNGED'
endmodule.
*Class method
method data_changed. " Handler method
" Use table        er_data_changed->mt_good_cells[] or er_data_changed->mt_mod_cells to get entered date
endmethod.
Thanks
Edited by: Sap Fan on Sep 29, 2009 8:51 AM
Edited by: Sap Fan on Sep 29, 2009 9:46 AM

A business agreement must be entered for Payer

Hi
While creating sales order showing floowing error message
A business agreement must be entered for Payer xxxxxx
if i go in Details it is showing following messge:
Diagnosis
The field "FI-CA active" is selected for Payer xxxxx in the business partner record, that is, the payment transactions are processed via the R/3 component. A business agreement must be entered for this process.
Procedure
Enter a valid business agreement.
I am not getting where i need to main these settings.currently i am working on CRM 7.0
Can u please help me out to solve this issue
Thanks & Regards
Kishore Kumar

One simple way if you want to get rid of this error (mostly for testing purposes/may not be relevant for production system) is
go to CRM SPRO->MASTER DATA->BUSINESS PARTNER->BUSINESS AGREEMENT->DEFINE BASIC SETTINGS-> (HERE DE-ACTIVATE THE FI-CA INDICATOR).

Urgent: Table control validation of defaulted values

Hi All,
I have 5 fields in my table control. I have provided a button on the screen, if the user clicks that button, one of the fields( checkbox) is set as 'X'.
Now , I want to validate the value in this field.
The issue I have is that it is not going into the CHAIN ENCHAIN module logic to do the validation, if the value is updated through the button, but it performs validation if I update the field manually.
Please advice.
Thanks.
K K

Try this in the PAI process of screen:
LOOP AT itab.
    CHAIN.
        FIELD: ...
        MODULE CHECK_MODIFIED ON CHAIN-INPUT.
    ENDCHAIN.
ENDLOOP.
Oherwise,you can add the check logic into the flow logic of the button,if the value is not valid,block it.
Edited by: Liang Zhang on May 28, 2008 4:34 AM

AIST0002-User Exit - Validation of user defined field

I have implemented the enhancement aist0002. I added a user defined field in a user defined subcreen and added it to the leasing tabstrip. I would like to validate this field against a another field in sap's leasing subscreen. In the pai of the user defined subsrceen the field of the other subscreen does not get filled. Is there a way to access the field of the other subscreen on the leasing tabstrip from the pai module of the user defined subscreen?
Thank you
Tom

Thank you for your response but I am not sure where the import occurs?
This is the pai of the user subscreen 9000 for AS01.
form edit_input .
data: itab type lfza.
if anlu-zzempfk is not initial.
 select * from lfza into itab
 where empfk = anlu-zzempfk and
 lifnr = anla-leafi.
 endselect.
 if sy-subrc <> 0.
 set cursor field 'ANLU-ZZEMPFK'.
 message e007(zvalid).
 endif.
endif.
endform.
Function exit EXIT_SAPLAIST_002 include zxaisu03
looks like this:
anlu = i_anlu.
anla = i_anla.
Data gets moved to anlu or anla if it was already built. They are empty when it is a create transaction(as01).
Function exit exit_saplaist_003. include zxaisu04
looks like this:
e_anlu = anlu.
After the subscreen is processed it exports the data to global variable.
The problem is the pai module for the user subscreen 9000, the field anla-leafi is not filled. This field is located in sap's subsceen 1403. It has data in the screen field. My assumption is that it would be accessible as global data that could be used by my user defined subscreen once I began the validation in the pai of subscreen 9000.
Could you provide more insight on how I would access the field from the other subscreen?

PAI validation

Similar Messages

Maybe you are looking for