Is it possible to maintain a mandatory field in R/3 Support Message?

Hello Experts,
I am implementing Service Desk feature of SOLMAN 7.0 ehp1. Client is expecting to add one field wherein he wants to add some additional information about the message reporter. Since it is an important information, client wants this field to be mandatory.
This information should also be visible to the processors.
Is it possible? IF it si, then how to do it?
Thanks in advance,
Deepak

Hi Deepak,
As you want to create a new custom field, I would suggest you to append a new screen profile to the standard one then you create a transaction variant for that screen which can be assigned to the transaction type.
Also, this is very much possible to achieve using coding. As yop are designing a new screen to incorporate the new filed, you can make it mandatroy by hard coding. Your ABAPer may be able to help you.
Rajeev

Similar Messages

Add new field in the Create Support Message Popup Screen

Hi Experts,
I need to create Project Code Field in the standard popup screen Create Support Message
Suggest me any Badi or FM or Bapi or Enhancement to create a new field and update the field value to the Support Message created.
Please let me know if this is possible or not?
Thank You,
Sowjanya Sreekrishna

Dear Abhijit
Even after doing PGI, there are some fields which are in editable mode in delivery. For example, in VL02N, if you select "Goto --> Header --> Shipment, you can see fields like Bill of Lading are in editable mode.
If you specify what your requirement is, then probably, a better option can be given.
Thanks
G. Lakshmipathi

Regarding mandatory fields, Context Objects and Fault Message Types

Hi All,
1) I am creating a structure with fields "Name", "Street" and "City". While creation i want to make "Name" fields as mandatory. Is it possible. If so how to achieve this.
2) What is the purpose of Context Object and in which situation we will use this.
3) What is the purpose of Fault Message Types and in which situation we will use this.
4) I am doing file to file scenario, at sender side i have set the adapter as file and transport protocol as "FTP" . It is asking for "Server", "PORT" and "Login Details". What is this FTP, for this do i need to take any login details. I am totally not aware of FTP, could please explain more about this.
Kindly look into the above points and respond point by point.
Thanks in advance.
Regards,
Prem.S

Hi prem,
1) I am creating a structure with fields "Name", "Street" and "City". While creation i want to make "Name" fields as mandatory. Is it possible. If so how to achieve this.
give occurence 1..unbounded. for the field name.
2) What is the purpose of Context Object and in which situation we will use this.
If u have multiple receiver system then to determine the reciever u can use context object.....
the alternative of context objetc is X-Path...
Check out these
http://help.sap.com/saphelp_nw2004s/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/content.htm
/people/prasadbabu.nemalikanti3/blog/2006/09/20/receiver-determination-based-on-the-payload-of-input-dataextended-xpathcontext-object
Here is a scenario where context objects were used for BPM
Technical Context Object in ccBPM
Get the details here:
http://help.sap.com/saphelp_nw04/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/frameset.htm
Technical Context Objects :
http://help.sap.com/saphelp_nw04/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/frameset.htm
A list of the Technical Context Objects names can be found here:
http://help.sap.com/saphelp_nw04/helpdata/en/6e/ff0bf75772457b863ef5d99bc92404/content.htm
Difference between context object and x-path:
diff between context object and x path
3) What is the purpose of Fault Message Types and in which situation we will use this
whenever u want to catch some exception u can use fault message types.Just for a example u r sending some data to SAP system.But due to some reason the R/3 system is down.so in this case if u have implemented fault message ..u can get a error message specifying r/3 is down....
Fault message implementation.
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
How to Guide
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40574601-ec97-2910-3cba-a0fdc10f4dce
4) I am doing file to file scenario, at sender side i have set the adapter as file and transport protocol as "FTP" . It is asking for "Server", "PORT" and "Login Details". What is this FTP, for this do i need to take any login details. I am totally not aware of FTP, could please explain more about this.
there are two transport protocol for File adapter
1)FTP(File transfer protocol)
to know abt FTP check here
http://help.sap.com/saphelp_nw04/helpdata/en/43/0e16bfd7b021aee10000000a1553f6/content.htm
2)NFS(Network File System)
in server :Enter the host name or IP address of the FTP server.
in PORT:Specify the port number of the FTP server.
The default is the standard port for the FTP server (21)
check here
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
Regards
BILL
***reward with points if ity helps u!!

Mandatory field in the People Screen in HR

Hello All,
We have a SIT defined in which there is a mandatory field. Is there any way that we can make sure that the new hire cannot be made possible without entering the mandatory field in the SIT?
Even if its a customization, please advice
Thanks
KK

Hi Madhu,
Since Select options are nothing but ranges, you can use the following code to add two distinct values to the select options by default.
s_ktokd-sign = 'I'.
s_ktokd-option = 'EQ'.
s_ktokd-low = 'Y001'.
append s_ktokd.
s_ktokd-low = 'Y005'.
append s_ktokd.
clear s_ktokd.
However, if you want to mention a range like all the values between these given two values to be considered then u may use,
select-options : s_ktokd for KNA1-KTOKD default 'Y001' to 'Y005'.
or
s_ktokd-sign = 'I'.
s_ktokd-option = 'BT'.
s_ktokd-low = 'Y001'.
s_ktokd-high = 'Y005'.
append s_ktokd.
Reward if helpful.

UDF as Mandatory Fields

Hi!
is it possible to make UDFs mandatory fields in SAP B1?
Thanks
Riza

Hi,
Yes possible. Please check this document:
http://scn.sap.com/docs/DOC-48302
Thanks & Regards,
Nagarajan

How to add new fields in the Create Suppport Message Screen

Hi experts,
I have a requirement which is to add 3 selection fields in the Create Support Message Screen. The 3 fields are Category, Subject and Solution. The value of these 3 fields must aurtomaticallly populate the same fields in the Support Message screen in the Solution Manager for each message sent.
Is this functionallity possible? If yes, please give me some ideas how to do it..
Points will be rewarded for helpful answers.

Hi Eric,
Yes it is possible. Use statements SET and GET parameters in your program.
1. Get parameter ID for the fields Category, Subject and Solution from the data element. or Set parameter ID.
2. Use GET Statement in the PBO of the Support Message screen .
GET PARAMETER ID 'XYZ' FIELD <field-name>.
"XYZ is the parameter ID
"<field-name> - field should have the field . not in quots
3. Use SET statemet in the PAI of the Create Support Message Screen or where the value is available for the 3 fields.
SET PARAMETER ID 'XYZ' FIELD <field-name>.
"XYZ is the parameter ID
"<field-name> - field should have the field . not in quots
4. Parameter ID : Double click on the data element of the specified field->Select Further Characteristics TAB -> u can see the parameter ID or U can set the parameter ID there .
It works. Try it.
Regards,
Venkat.O

How to maintain standard text as a mandatory field

Hi ,
please suggest me How can i maintain a STDTEXT as a mandatory field while creation a production order.
while creating production order using CO01, in operation overview(F5) there is a column called STDTEXT.
so i need to maintain the these field as a mandatory pleas suggest me how can i do this.
Regards,
Sateesh C

Dear
You need to do the following :
1.Create Stnadrad Text Key in CR09
2.Assing this key in Work Centre in Defaultr Values in Standard Text Key filed
3.In routing if you create operation with this Work Centre then it will automatically pop up in operation line -Standrad Text field
4.If you create production Order in CO01 -then this this routing will be selected along with Operation details .Check operation oerview
Hope this helps
Regards
JH

To maintain 'Functional Location Description' field as mandatory field

Hi All,
I am unable to maintain the "Functional Location Description" field as mandatory field (Screen Filed: IFLO-PLTXT).
In IMG settings, I am unable to find this field to change it to "required" field. Could you pls. tell me the way to make this field as mandatory.
Thanks in advance.
JK

hi try t.code oiaj there is a filed of description

Mandatory fields passing to the structure POCOND in BAPI_PO_CREATE1

Hi,
Please help me that what are the mandatory fields passing to the structure POCOND in BAPI_PO_CREATE1. I am using BAPI to create the PO based on certain conditions. But after creating the PO the condition values are not updating properly. Currently i am not passing any values to the structure.
Your solutions should be highgly appreciated. Please help me this issue as early as possible
Regards,
Uday

Hi ,
In my current requirement i m using BAPI_PO_CREATE1 to create the PO.
I am passing all the line item detials to the BAPI.
For some of the material rounding value are maintained in MM02 on MRP view.
If the line item material maintains rounding value then instead of taking the PO item quantity, it is taking the rounding value that has maintained in MM02. So to control that i have done the forceful updation using the update statement in one of the exit on BAPI_PO_CREATE1.
Here i m facing one problem. Now i can able to udpate the PO quantity correctly.
But the Condition value maintained in the Condition View still taking the rounding value for calculating.
To control this also i am using update statement on KONV table and the field is KAWRT. But this value is not updating.
Please help any one that in which table the the condition value is going to update and wht are the criteria to update the Condition Value field.
Points should allocate for suitable answer.
Thanks
Uday

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.
raj

Hi,
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 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,
MARKIV

hi ,
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

Mandatory Field in ALV Grid

Hello,
i've a editbale alv grid.
Is it possible to set a field/colum as mandatory field?
Best regards,
TomSd

Hi,
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 fields on the same page with dependent LOVs

Hi,
I am working on an ADF-BC application using JDeveloper 10.1.3.4
I have an ADF Creation form with dependent LOVs and while implementing dependent LOVs we set the autoSubmit property of the selectOneChoiceListBox as true.
If I have some mandatory fields on the same page then because of the autoSubmit property set as true whenever I select a value in the list the page gets submitted and the mandatory fields give an error that the values are required therefore I had to remove the mandatory fields.
I tried using f:subview but even that dint serve the purpose because what I want is something like partialSubmit so that my mandatory fields do no give an error when I select a value in the list.
Can somebody help me on this, how to have a dependent list and mandatory fields on the same page.
P.S: It is very crucial for my application
Thanks,
Raksha

Hello,
This bug has been around since 10.1.3, its even still present in Trinidad and now in 11.
One of the ways to avoid is to make your fields use:
showRequired="true"instead of
required="true"I have not found a decent way to avoid this in general.
My idea was that this shiould be possible with a phaselistener and determine if this is a partial page event instead of a normal submit, but this didnt work.
-Anton

Mandatory fields in the Conditio Records

Hi,
The question is;
When we maintain the condition record for pricing, we find that certain fields are mandatory and certain fields are not mandatory in a key combination.. Where and how is the mandatory setting set to the fields?
Thanks in advance,
Fazal

Hi Fazal,
All the fields of the condition record are mandatory. Once u define the fields in the condition table, they become mandatory in the condition record.
For ex. if my condition record consists of Customer, material, and sales orgn, then i need to maintain all the fields in the condition record with out which the condition record will not be found.
Cheers,
Hi Anil,
Considering your example of a table consisting of fields Customer, material, and sales orgn; when i go to VK12, enter the condition type and select the key combination consisting of the above fields, the sales org would be mandatory or the sales org and the customer would be mandatory fields and material would not be mandatory before execution.
If I give the material details then the specific condition record is the output, but if the sales org is the only mandatory field and i enter that and execute then it gives me a huge list.. Now, my question is how do you make this feild (sales org) mandatory or rather see it a mandatory entry in the VK12 screen???
Regards
Fazal

Mandatory Fields in iView created from SHD0 (sceen variant)

I am experiencing an issue with the Portal display of an (IAC) iView. The iView displays PZ05 and a transaction variant was setup to handle Emergency contact info. I created a screen variant for the second screen of this transaction (screen 0200) in which I made 7 of the fields mandatory in the variant. When this is tested on the R/3 side the mandatory fields are displayed the way they are supposed to be (with the check mark in the box, denoting it as a required field) however when they are displayed in the iView on the Portal the mandatory fields are completely filled up with the "check mark in the box". In other words the "Name" field is 40 character... and there are 52 "check marks in the box" characters filling up the field. The iView works great but this looks ugly. Any suggestions on what I should do to rectify the situation?
We are running Portal 6.0 SP15 with a stand alone ITS on a 4.6c backend and the Business Package is 50.4.

Hi Balaji,
When you create Vendors properly in ECC it should not give such an error. You have to maintain basic data, Accounting data and purchasing data. Rest all are optional.
For replicating vendors from R/3 to SRM you should have a Vendor root org / group in SRM. BBPGETVD is used to replicate vendors to SRM by mentioning the logical system and Vendor Group ID.
Hope this makes you clear. Please explain the error clearly for further help.
Award points for helpful answers.
Rgds,
Teja

Is it possible to maintain a mandatory field in R/3 Support Message?

Similar Messages

Maybe you are looking for