Mandatory fields in dynpro
Hi!
I have some mandatory fields in my dynpro, but i also have a option to fill data in the dynpro after filling 2 fields and clickin a button.
The problem is that if I click the button, it says that I have to fill the mandatory fields. Is there a way to stop the control-function only for this button-click?
i tried it with exit-commands, but so i don´t get the data from the 2 filled fields, because it only transports the user-command.
thank you in advance!
Andreas
Hii Andreas..
This is the Solution for u..
You are using the Module AT EXIT-COMMAND to avoid the Mandatory field checks. But in this module the Screen fields are not Copied to Program Variables.
Only the OK_CODE(SY-UCOMM) will be copied.
But you can read the Values of the SCREEN FIELDS by Calling the FM
<b>DYNP_VALUES_READ</b>
(This Fm reads the Screen field values even before they are transported to program)
EG:
CALL FUNCTION 'DYNP_VALUES_READ'
EXPORTING
dyname = sy-cprog
dynumb = sy-dynnr
TABLES
dynpfields = h_dynpfields
EXCEPTIONS
OTHERS = 1.
Let me know if there are any issues.
<b>Reward if Helpful</b>
Similar Messages
-
Radio buttons in dynpro with mandatory field
I have two radio buttons in a group and a field that should be mandatory when one (the first one) is checked.
So when the other is checked it should not be mandatory.
The problem is that when I check the second the field is mandatory until I have put something in the field. In that moment, the field is not mandatory. What I want is to make the field not mandatory when the second is checked so the status of the field was changed to not required in that moment not when I put something in it.
Thank youHi Maria,
I think you have two possibility.
One is to check the "mandatory field" by programming and not with the attribute in the dynpro.
The second way is making a loop at screen in the PBO and depend on with radio button is checked modify the required field of screen table for the field of your interest .
I hope this can help you.
bye
enzo -
Mandatory Fields displaying in the table
Hi
In my create Page , fields are present with input fields and DROP DOWN BY KEY AND rADIO GROUP.
In that some of the fields are mandatory.
If i enter values in that create page, it has to show fields in the table.
But iam having only mandatory fields should come in the table.
Our Abapers created table for the Mandatory fields only.
Iam having doubt how the remaining fields(not showing in the table) will connect to the database.
Will any one explain me on this.
Please help me.
Regards
SushmaIam trying to connect my web dynpro application to R3 Database.
Iam having list screen consistts of Create and Export buttons and table.
Table Fields :
Allowance Code , sub code ,Type , Level , expense Type , amount
After clicking Create button ,
the screen consists of save and Cancel buttons.
Allowance Code -- (Input Field)
Sub Code -- (Input Field)
Period Type -
(Dropdown by key)
Type -
(Radio button Group)
Level --- (Dropdown by key)
Expense Type -(Dropdown by key)
Trip - (Dropdown by key)
Currency - (Dropdown by key)
Amount --(Input Field)
In the Create screen all these fields are present. But in the table in the List Screen it is taking only mandatory Fields.
For this our Abapers created
Fun Mod : Zup_Allowance_Input
Table : ZMSTR_ALLOW
Iam getting error in this code under IdataType in this "Save Button ".
Can any one help me where i went wrong in this code.or else please provide the Code for this.
public void onActionSave(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
//@@begin onActionSave(ServerEvent)
try{
String str1=wdContext.currentStdAllowanceElement().getAllowanceCode();
String str2=wdContext.currentStdAllowanceElement().getSubCode();
IDataType dataType = wdContext.nodeStdAllowance().getNodeInfo().getAttribute("PeriodType").getDataType();
String index=wdContext.currentStdAllowanceElement().getPeriodType();
String str3=wdThis.getTextFromSimpleType(dataType,index);
wdComponentAPI.getMessageManager().reportSuccess("wetreer "+str3);
String arr[]={"Fixed","Actual"};
for(int i=0;i<arr.length;i++)
IPrivateEtrecStdCreateView.ICheckElement e=wdContext.nodeCheck().createCheckElement();
wdContext.nodeCheck().addElement(e);
e.setType(arr);
IDataType dataType = wdContext.nodeStdAllowance().getNodeInfo().getAttribute("").getDataType();
String index=wdContext.currentStdAllowanceElement().getLevel();
String str5=wdThis.getTextFromSimpleType(dataType,index);
wdComponentAPI.getMessageManager().reportSuccess("wetreer "+str5);
IDataType dataType = wdContext.nodeStdAllowance().getNodeInfo().getAttribute("ExpenseType").getDataType();
String index=wdContext.currentStdAllowanceElement().getExpenseType();
String str6=wdThis.getTextFromSimpleType(dataType,index);
wdComponentAPI.getMessageManager().reportSuccess("wetreer "+str6);
IDataType dataType = wdContext.nodeStdAllowance().getNodeInfo().getAttribute("Trip").getDataType();
String index=wdContext.currentStdAllowanceElement().getTrip();
String str7=wdThis.getTextFromSimpleType(dataType,index);
wdComponentAPI.getMessageManager().reportSuccess("wetreer "+str7);
IDataType datatype = wdContext.nodeStdAllowance().getNodeInfo().getAttribute("Currency").getDataType();
String index=wdContext.currentStdAllowanceElement().getCurrency();
String str8=wdThis.getTextFromSimpleType(dataType,index);
wdComponentAPI.getMessageManager().reportSuccess("wetreer "+str8);
String str9=wdContext.currentStdAllowanceElement().getAmount();
Zup_Allowance_Input input=new Zup_Allowance_Input();
input.setAllow_Opt("C");
input.setAllowance_Code(str1);
input.setSubcode(str2);
input.setType1(str3);
input.setLevel1(str5);
input.setExpense(str6);
input.setCurr_Key(str8);
wdContext.nodeZup_Allowance_Input().bind(input);
wdContext.currentZup_Allowance_InputElement().modelObject().execute();
String str10=wdContext.currentOutputElement().get();
if(str10.equalsIgnoreCase("3"))
String errorMessage = "Inserted Successfully !";
IWDEventHandlerInfo windowHandler = wdControllerAPI.getViewInfo().getViewController().findInEventHandlers("OK");
IWDConfirmationDialog windowDialog = wdComponentAPI.getWindowManager().createConfirmationWindow(errorMessage, windowHandler, "OK");
windowDialog.open();
windowDialog.setWindowPosition(300,250);
}if(str10.equalsIgnoreCase("2"))
String errorMessage = "Duplicate Value !";
IWDEventHandlerInfo windowHandler = wdControllerAPI.getViewInfo().getViewController().findInEventHandlers("OK");
IWDConfirmationDialog windowDialog = wdComponentAPI.getWindowManager().createConfirmationWindow(errorMessage, windowHandler, "OK");
windowDialog.open();
windowDialog.setWindowPosition(300,250);
}catch(Exception e)
wdComponentAPI.getMessageManager().reportSuccess(e.toString());
//@@end
//@@begin javadoc:onPlugFromEtrecStdView(ServerEvent)
/** Declared validating event handler. */
//@@end
public void onPlugFromEtrecStdView(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
//@@begin onPlugFromEtrecStdView(ServerEvent)
wdContext.currentStdAllowanceElement().setAllowanceCode("");
wdContext.currentStdAllowanceElement().setAmount("");
wdContext.currentStdAllowanceElement().setSubCode("");
//@@end -
Check mandatory fields before saving
Hello,
In my Z-program, how can I check all mandatory fields in a dynpro before saving?
Is there any function to do that?
Thanks!!!Hi alberto,
1. If the fields are mandatory (as set in the field attributes while designing the screen),
2. then we don't have to write any additional logic for the same.
The system will AUTOMATICALLY check for it, and issue appropriate message.
regards,
amit m. -
Default Back Button ( F3 ) with mandatory fields ( module pool program )
Guys,
I'm editing another persons dialog program and as mentioned in the subject line, there are mandatory fields. WIthout them being filled, I cannot use the back button to exit the program as it prompts me to first fill the mandatory fields.
How can I get past this?
I did a /h for debug mode and pressed Back but it did not even show the debugger.
Regards,
Kevin<b>Use AT exit-command.</b>
MODULE mod [ AT {EXIT-COMMAND|CURSOR-SELECTION} ]
[ ON {CHAIN-INPUT|CHAIN-REQUEST} ]
[ SWITCH switch ].
Extras:
1. ... AT EXIT-COMMAND
Effect
The statement MODULE of the dynpro flow logic calls the dialog module mod of the ABAP program. You can use MODULE either as a keyword or as an addition of statement FIELD. When using it as an addition, the call of the dialog module depends on conditions for the screen fields.
As a keyword, the statement calls the dialog module mod of the respective ABAP program. At the event PAI, you can use the additions AT and ON to specify conditions for the call of the dialog module.
At the event PBO, you can call any dialog module defined in the ABAP program with the addition OUTPUT. At the events PAI, POH and POV, you can call any dialog module defined with the addition INPUT or without any addition. If the dialog module mod does not exist in the ABAP program, an untreatable exception is triggered. After processing a dialog module in the ABAP program, processing of the dynpro flow logic is resumed after the position of the call, unless the screen processing is completed within the dialog module.
You can use MODULE as a keyword only at the events PBO and PAI. At the events POH and POV, you can use MODULE only as an addition to the FIELD statement.
Note
Do not mix up the MODULE statement of the dynpro flow logic with the identically called statement MODULE for defining dialog modules in the ABAP program.
Addition 1
... AT EXIT-COMMAND
Effect
Addition AT EXIT-COMMAND at the event PAI causes module mod to be called exactly if:
The function used to trigger event PAI has function type "E"
Into the input field of the standard toolbar, the user entered a character string starting with "E" and confirmed it using ENTER.
The dialog module is called before the automatic input checks defined in the system or in the ABAP Dictionary and independent of its position in the event block. The only screen field transported to the ABAP program is the OK field. If the function that triggered the PAI event does not fulfill any of the above prerequisites, the MODULE statement is not executed.
If several MODULE statements have the AT EXIT COMMAND addition, only the first one is executed. If no MODULE statement has the addition AT EXIT COMMAND, a normal PAI processing is executed: The predefined input checks are executed and then the PAI event block is processed sequentially. Provided the screen processing is not terminated in the dialog module mod, after the return from the dialog module, the complete PAI processing is executed. You must not use the addition AT EXIT COMMAND in connection with the statement FIELD.
Note
The function type of a function is determined in the Screen Painter or Menu Painter. Usually those functions of the user interface are defined with function type "E" that are assigned to the icons Back, Exit and Cancel in the standard toolbar of the GUI status. Therefore, the called dialog module should terminate the screen processing and allow security checks, if required. -
ESS Address Required Field Web Dynpro
Hi,
Trying to make a field on the ESS Address screen mandatory. Viewed the Web Dynpro Java Code and updated the label to required - which put the * next to the label on the screen, however I cannot see where the validation check exists.
Do I have to validate the code in web dynpro and if so where or is it a ABAP issue?
Have read in other postings (e.g. Re: ESS Web dynpro for portugal) that the required fields can be updating in the table V_T588MFPROPC. I'm unsure if this is correct as a required field 'City' does not exist in this table, which is a mandatory field. Also what values should I enter and how is the error message format created?
Thanks
BrianHi,
Setting the attribute of field as required will only add a * mark in front of it.
If you want to make it mandatory in WebDynpro code then please go through the <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/wd%20java/wd%20tutorials/a%20simple%20input%20form%20with%20message%20and%20error%20service%20support.pdf">following link</a>.
As said by you many of the HR screens field attributes can be configured in SPRO.
SPRO - Personal management - Personal Administration - Customizing UI - Change Screen Modifications.
Hope this helps you.
We can do that setting in backend then thats fine else you can do that in WebDynpro.
Regards,
Nagaraju Donikena.
Regards,
Nagaraju Donikena -
What are the mandatory fields while creation of material master in differen
what are the mandatory fields while creation of material master in different views?
Hi Gopi,
This is purely depends on the function configuration, which would be done MM consultants. Kindly check with them.
thanks & regards
Kishore Kumar Maram -
Dynamic mandatory field error message is not getting displayed in webui
Hi,
In Appointment if the importance is HIGH i made Location as mandatory.For this i enhanced BT126H_APPT/ApptDetails. In the get_p_location() method of BTACTIVITYYH i have written the code.
Now the problem is Error message for this dynamic mandatory field is not getting displayed in webui.
I debugged in DO_FINISH_INPUT error message is getting generated but it is not getting displayed in ui.
Can anybody tell where the problem is?
Thanks,
Hari.Hi Hari,
Really sorry do not know how to convert this nug file to text
How ever quick solution for your problem would be just keep your validation in 'DO_VALIDATE_INPUT' method of the view controller.
Means even if the User clicks on SAVE , Since it fails here , it would not allow you to go further.
Thanks,
Rajesh P -
Mandatory fields while using Group chart of accounts
Hi,
Which are the mandatory fields while maintaining GL accounts in FS00 if i am using Group chart of accounts.
And how attached these group chart of accounts gl to the operational chart of account GL.
rajHi,
the assignment from operational chart of accounts to group chart of accounts is done in OB13. Follow the steps in Customizing IMG FIn. Acc. (new) / Consolidation preparation (new) / General specifications / G/L and FS Charts of accounts...
Best regards, Christian -
What are all the mandatory fields of the BAPI_PO_GETDETAIL?
Hi friends,
I am new to XI. I am using the "BAPI_PO_GETDETAIL1" in my scenario to get details of a particular Purchase Order. Can you tell me the mandatory fields of this BAPI?
Where should i look to identify the mandatory fields of a BAPI?
Thanks.
Senthil Nathan.Hi you can see this in SE37 under the Import Tab. Here you see that the only mandatory input field is PURCHASEORDER. So if you provide the purchaseorder number you get alle the details for that.
Kind regards
Mikkel -
What are the Mandatory fields????
Hi.... Experts...
Please spend your valueble time for me.... I can get back to you with 10 points....
Here I got a requirement to create contract with VA41 transaction...
But I am in confusion with feilds which should be must record...
Please guide me on mandatory fields of VA41 transaction....
Thanks,
Naveen.IHi,
When ever you want to know the required fields for any transaction just try to run the Transaction In SHDB in forgroud mode with a recording name.
You will easily get to know the required fields to be entered for a given transaction.
Sometimes when we run this VA41, eventhough some fields are not mandatory we dont pass them but we willnt b able to create the document eventhough some fields are not mandatory to fill> To have the clear idea abt the manadotry fields try to run in SHDB.
for this VA41, ther mandatory fields are-
contract type (VBAK-AUART)
Sales Area is a combintaiotn of SAles Org, SAles divnsion, Distirbution channel hende all 3 are required to be filled.
1st screen-
Sales Area(VBAK-VKORG)
Division(VBAK-SPART)
D.Channel(VBAK-VTWEG),
2nd screen-
Customer code(kunnr),
Contract validity,
material code(matnr),
quantity
plant(werks).
Best Wishes,
Chandralekha
Edited by: Craig Cmehil on Jun 30, 2008 11:24 AM -
What are the Mandatory Fields in Transaction ME51
Hello Seniors,
I have a requirement about purchase order creation. In this process, I am using the BAPI named " BAPI_PO_CREATE1 ". I have passed all the fields but when I debug and look into the internal tables, I couldn't find certain records. I even debugged " bapiret2" and I see an error which reads "" All mandatory fields are missing"". I have even created a PO in ME51 and found out the mandatory fields but in vain. BAPIRET2 still says, there are some more mandatory fields missing. I need to know what are all the mandatory fields to create a Purchase order using TCODE - ME51.
Your reply is most awaited and rewarded.
Thanks and Regards,
MARKIVhi ,
Functionality
Function module BAPI_PO_CREATE1 enables you to create purchase orders. The BAPI uses the technology behind the Enjoy purchase order transaction ( ME21N).
Alternatively, the IDoc type PORDCR1 is available. The data from this IDoc automatically populates the interface parameters of the function module BAPI_PO_CREATE1.
Functionality in Detail
Authorization
The following authorization objects are checked when an Enjoy purchase order is created (activity 01):
M_BEST_BSA (document type in PO)
M_BEST_EKG (purchasing group in PO)
M_BEST_EKO (purchasing organization in PO)
M_BEST_WRK (plant in PO)
Controlling adoption of field values via X bar
For most tables, you can determine via your own parameters in the associated X bar in each case (e.g. PoItemX) whether fields are to be set initial, values inserted via the interface, or default values adopted (e.g. from Customizing or master records) (for example, it is not mandatory to adopt the material group from an underlying purchase requisition - you can change it with the BAPI).
Transfer
Header data
The header data of the Enjoy purchase order is transferred in the table PoHeader.
Item data
The item data of the Enjoy purchase order is stored in the table PoItem (general item data). The delivery schedule lines are stored in the table PoSchedule.
Use the table PoAccount to specify the account assignment information. If account assignments have been specified for services and limits, you show the relevant account assignment line in PoAccount in the table PoSrvAccessValues via the package number of the service or the limit.
Services and limits
Services, free limits and limits with contract reference can be specified in the tables PoServices, PoLimits, and PoContractLimits.
Conditions
Conditions are transferred in the table PoCond; header conditions in the table PoCondHeader. Price determination is reinitiated via the parameter CALCTYPE in the table PoItem.
Vendor and delivery address
The vendor's address can be specified individually in the table PoAddrVendor; the delivery address in the table PoAddrDelivery. If you do not make any individual specification, the fields will be populated via the central address managementfacility.
Note
In this method, the following restrictions apply with regard to addresses:
Addresses can only be created with this method - they cannot be changed. You can only change address data with the method BAPI_ADDRESSORG_CHANGE.
When you create addresses, they are not checked by the method. An Enjoy purchase order may therefore contain faulty address data.
Partner roles
The partners can be maintained individually via the table PoPartner (with the exception of the partner role "vendor").
Import/export data
Import/Export data can be specified per item in the table PoExpImpItem. Foreign trade data can only be transferred as default data for new items.
Texts
Header and item texts can be transferred in the tables PoTextHeader and PoTextItem. Texts for services are imported in the table PoServicesText.
Version Management
You can make use of the Version Management facility via the table AllVersions.
Return
The PO number is returned in the parameter ExpPurchaseOrder. In addition, all information except the service and export/import tables is placed in the output structures.
Return messages
Messages are returned in the parameter Return. This also contains information as to whether interface data has been wrongly or probably wrongly (heuristical interface check) populated. If a PO has been successfully created, the PO number is also placed in the return table with the appropriate message.
Example
Example of population of BAPI interface in the Function Builder
Parameter: POHEADER
COMP_CODE = 1000
DOC_TYPE = NB
ITEM_INTVL = 00001
VENDOR = 0000001000
PMNTTRMS = 0001
PURCH_ORG = 1000
PUR_GROUP = 001
CURRENCY = EUR
Parameter: POHEADERX
COMP_CODE = X
DOC_TYPE = X
ITEM_INTVL = X
VENDOR = X
PMNTTRMS = X
PURCH_ORG = X
PUR_GROUP = X
Parameter: POITEM
PO_ITEM = 00001
MATERIAL = 100-100
PLANT = 1000
STGE_LOC = 0001
QUANTITY = 15.000
TAX_CODE = V0
ITEM_CAT = 0
ACCTASSCAT = K
Parameter: POITEMX
PO_ITEM = 00001
MATERIAL = X
PLANT = X
STGE_LOC = X
QUANTITY = X
TAX_CODE = X
ITEM_CAT = X
ACCTASSCAT = X
Parameter: POSCHEDULE
PO_ITEM = 00001
SCHED_LINE = 0001
DELIVERY_DATE = 02.12.2002
QUANTITY = 6.000
PO_ITEM = 00001
SCHED_LINE = 0002
DELIVERY_DATE = 03.12.2002
QUANTITY = 5.000
PO_ITEM = 00001
SCHED_LINE = 0003
DELIVERY_DATE = 04.12.2002
QUANTITY = 4.000
Parameter: POSCHEDULEX
PO_ITEM = 00001
SCHED_LINE = 0001
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0002
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0003
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
Parameter: POACCOUNT
PO_ITEM = 00001
SERIAL_NO = 01
QUANTITY = 15.000
GL_ACCOUNT = 0000400000
COSTCENTER = 0000001000
CO_AREA = 1000
Parameter: POACCOUNTX
PO_ITEM = 00001
SERIAL_NO = 01
QUANTITY = X
GL_ACCOUNT = X
COSTCENTER = X
CO_AREA = X
Parameter: POCOND
ITM_NUMBER = 000001
COND_ST_NO = 001
COND_TYPE = PB00
COND_VALUE = 79.900000000
CURRENCY = EUR
CURRENCY_ISO = EUR
COND_UNIT = KG
COND_P_UNT = 1
CHANGE_ID = U
Parameter: POCONDX
ITM_NUMBER = 000001
COND_ST_NO = 000
ITM_NUMBERX = X
COND_TYPE = X
COND_VALUE = X
CURRENCY = X
CHANGE_ID = X
Parameter: POPARTNER
PARTNERDESC = OA
LANGU = EN
BUSPARTNO = 0000001100
PARTNERDESC = GS
LANGU = EN
BUSPARTNO = 0000001200
PARTNERDESC = PI
LANGU = EN
BUSPARTNO = 0000001000
Help in the Case of Problems
1. Note 197958 lists answers to frequently asked questions (FAQs). (Note 499626 contains answers to FAQs relating to External Services Management.)
2. If you have detected an error in the function of a BAPI, kindly create a reproducible example in the test data directory in the Function Builder (transaction code SE37). Note 375886 tells you how to do this.
3. If the problem persists, please create a Customer Problem Message for the componente MM-PUR-PO-BAPI, and document the reproducible example where necessary.
Customer Enhancements
The following user exits (function modules) are available for the BAPI BAPI_PO_CREATE1:
EXIT_SAPL2012_001 (at start of BAPI)
EXIT_SAPL2012_003 (at end of BAPI)
The following user exits (function modules) are available for the BAPI BAPI BAPI_PO_CHANGE:
EXIT_SAPL2012_002 (at start of BAPI)
EXIT_SAPL2012_004 (at end of BAPI)
These exits belong to the enhancement SAPL2012 (see also transaction codes SMOD and CMOD).
There is also the option of populating customer-specific fields for header, item, or account assignment data via the parameter EXTENSIONIN.
Further information
1. Note 197958 contains up-to-date information on the purchase order BAPIs.
2. If you test the BAPIs BAPI_PO_CREATE1 or BAPI_PO_CHANGE in the Function Builder (transaction code SE37), no database updates will be carried out. If you need this function, please take a look at Note 420646.
3. The BAPI BAPI_PO_GETDETAIL serves to read the details of a purchase order. The BAPI cannot read all details (e.g. conditions). However, you can use the BAPI BAPI_PO_CHANGE for this purpose if only the document number is populated and the initiator has change authorizations for purchase orders.
4. Frequently used BAPIs for purchase orders are BAPI_PO_CREATE, BAPI_PO_CREATE1, BAPI_PO_CHANGE, BAPI_PO_GETDETAIL, BAPI_PO_GETITEMS, BAPI_PO_GETITEMSREL, and BAPI_PO_GETRELINFO.
5. For more information on purchase orders, refer to the SAP library (under MM Purchasing -> Purchase Orders) or the Help for the Enjoy Purchase Order, or choose the path Tools -> ABAP Workbench -> Overview -> BAPI Explorer from the SAP menu.
regards
reena -
Hello,
i've a editbale alv grid.
Is it possible to set a field/colum as mandatory field?
Best regards,
TomSdHi,
Have a look at the report BCALV_EDIT_03.
In this report the program logic is such that if the user enters an incorrect value an error is displayed.
Instead you can check if the field of your ALV filelds are null and validate them accordingly.
Regards,
Sandeep -
Mandatory field validation on Page links.
We have created a Portal application where we included different applications as taskflows. We have also created a tabbed interface which helps us to communicate from one task flow to another taskflow. When we are in one page of taskflow and try to move to another page of different taskflow using tabbed interface we receive mandatory field validation error which prevents us to move to any other page until we fill all the mandatory fields. We need to move to different page of taskflow by using the tabbed interface even without filling all the necessary mandatory fields. Can anyone help us to resolve this issue as this is very important for our project.
<b>Layout</b>
<%@page language="abap" %>
<%@extension name="htmlb" prefix="htmlb" %>
<htmlb:content design="design2003" >
<htmlb:page title="Check Pernr " >
<htmlb:form>
<htmlb:textView text = "Personnel No."
design = "EMPHASIZED" />
<htmlb:inputField id = "pernr"
value = "<%= lv_pernr %>" />
<%
if lv_no_pernr = 'X'.
%>
<script language="Javascript">
alert ("Personnel no. is not Valid")
</script>
<%endif.%>
</htmlb:form>
</htmlb:page>
</htmlb:content>
<b>ONINPUTPROCESSING</b>
DATA: l_pernr TYPE persno.
DATA: data TYPE REF TO cl_htmlb_inputfield.
data ?= cl_htmlb_manager=>get_data( request = runtime->server->request
name = 'inputField'
id = 'pernr' ).
IF data IS NOT INITIAL.
l_pernr = data->value.
ENDIF.
CLEAR lv_no_pernr.
SELECT SINGLE pernr FROM pa0000 INTO l_pernr WHERE pernr EQ lv_pernr.
IF sy-subrc NE 0.
lv_no_pernr = 'X'.
ENDIF.
<b>PAGE ATTRIBUTES</b>
lv_no_pernr TYPE FLAG
lv_pernr TYPE PERSNO
hope this helps.
A -
How to put Sales employee (Splcode) Mandatory Field, when adding A/R invoice
Hi,
Kindly solve, How to put Sales employee (Splcode) Mandatory Field, when adding A/R invoice.
Regards,
Rajeev.Follow this step..
1. In SQL Server, go to the SAP B1 Database you're using.
2. then on the Object Explorer , go to Database Folder, explode the SAP DB->Programmability->Stored Procedures->SBO_SP_TransactionNotification * the only Stored Procedure that is allowed to be edited. Just right click and modify
3. Try to paste this -> and click F5
If
@object_type ='13' and @transaction_type in ('A','U')
Begin
If EXISTS
select DocEntry from ONIV
Where DocEntry = @list_of_cols_val_tab_del
and SlpCode<>'-1'
Begin
set @error_message = 'Please select the Sales Employee'
set @error = 1
END
END
Regards
Kennedy
Maybe you are looking for
-
When I copy a CD onto my macbook pro I sometimes get several songs that are "out" of the album. How do I get them all together in one album? Any help will be much appreciated as I cannot seem to find the solution to this problem in the troubleshoot
-
Possible max no. of events in alv
Hi is there any maximum no of events possible in ALV reporting. i.e. what is the maximum no of events of alv possible in one program.
-
Ms office key for mac ????
hello,, i bought a 3 users ms office cd and i have downloaded it on my mac and entered the key then i formated my mac and the ms office is gone i have downloaded it again and it is asking me for the key if i enter the key one more user will be gone o
-
How do I turn off the main display when using external monitor or tv, or can you? Thanks Arthur
-
Texting issues between Iphone and IPAD
I set up my young daughter's IPAD using my Apple ID. Quickly we realized that she was getting the texts that I was sending from my Iphone (to other people) on her Ipad. She was reading things she shouldn't have been....so I need to change this. I