Field "Reason for change" mindatroy in PO under "Version" tabe ?

Hello Exp.,
Is there any EXIT or BADI available to make "Reason for change" mandatory while changing PO in ME22N tcode.
In SPRO, is there any standard location where we can make this field mandatory? .
Input and suggestion is highly appreciable.
Regards
Sanjay

Dear sir,
go to SPRO-IMG-Materials Management-Purchasing-Version Management-Set Up Version Management for External Purchasing Documents.
select your document type for which you want to make the required entry reason for change. and click details indicator(CtrlshiftF2). and in field selection Reason field make the Required entry.
then when u r changing PO the system will ask required entry for reason for change.
regards
jrp

Similar Messages

Keyword.url field bloked for changes in a firefox about:config tab (firefox with yandex)

keyword.url field bloked for changes in a firefox about:config tab (firefox with yandex)

Start Firefox in <u>[[Safe Mode]]</u> to check if one of the extensions or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
*Don't make any changes on the Safe mode start window.
*https://support.mozilla.com/kb/Safe+Mode
*https://support.mozilla.com/kb/Troubleshooting+extensions+and+themes

Purpose of Reason for Change on Timesheets

We are using PWA 2010 for time reporting. There is a field on the timesheet called "Reason for Change". The only value I believe I've ever seen in this field is "Not Delayed", however, other possible values (from a Lookup
table) are "Under Estimated", "Access to Resources", "Assigned to higher priority work", "Technical issue", "Other".
To my knowledge there is nothing anyone does at my company that changes/sets the value of this field. Can someone help me understand how it is used? how it is set? its purpose? I've been looking online but cannot find anything that
talks about it.
Thank you

What you are seeing is a custom field, created by your Project Server administrator, or perhaps by a consultant who might have set up your Project Server 2010 system. I can assure you that this field is NOT a default field. So, I would suggest
that you talk to your Project Server administrator to see if he/she set up this field. And if not, then I would suggest you talk to your consultant. And if nobody knows where this field came from, I would recommend that your Project Server administrator
remove it from the Timesheet-related views in PWA and then that the field be deleted. Just a thought. Hope this helps.
Dale A. Howard [MVP]

Reason for change of Infotype Based on Company Code

Hi Experts,
I have a requirement where I need to restrict the F4 HELP in
PA30 Transaction for the infotype 15 based on company code for the field reason for chagne.
I know that reason for change of infotype are maintained in the table T530E.
But can this be restricited through SPRO configuration.
Thanks in Advance.
Regards,
IFF

Hi.
It's possible to change the search helps with a search help exit.
Take a look in SE11 for search help H_T530E.
Search help exit
A search help exit is a function module for making the input help process described by the search help more flexible than possible with the standard version.
This function module must have the same interface as function module F4IF_SHLP_EXIT_EXAMPLE. The search help exit may also have further optional parameters (in particular any EXPORTING parameters).
A search help exit is called at certain timepoints in the input help process.
Note: The source text and long documentation of the above-specified function module (including the long documentation about the parameters) contain information about using search help exits.
Function modules are provided in the function library for operations that are frequently executed in search help exits. The names of these function modules begin with the prefix F4UT_. These function modules can either be used directly as search help exits or used within other search help exits. You can find precise instructions for use in the long documentation for the corresponding function module.
Regards.

How to enable field "reason for rejection" of view "status" in CRMD_ORDER

Hello Everyone
I need to activate/enable field "Reason for Rejection" in view "Status" of transaction CRMD_ORDER though a delivery document is created for the sales order.
Can some one pls let me know where do I need to code to make field "Reason for Rejection" enabled.
FYI, the same logic was applied for VA02 as well and the logic is written in userexit "USEREXIT_FIELD_MODIFICATION" which is working fine.
Apprecriate your quick response.
Thanks
Dharma

Hi Raj,
Usually we use function module CRM_STATUS_UPDATE to
change user status in document. But if you want to
trigger next process or change from certain user status to next status interactively by the system, you can
use Badi CRM_ORDER_STATUS (here you have after and before
method).
Hope this could help.
Rgds,
Gun.

Reason for Change in Contract

Dear SAP Gurus
I have a requirement that I want to configure, when someone changes Contract via VA42 and while saving the document the system should ask a reason for change somewhere and then only allow to save that document...plz help me..

Hi Ashish,
You can do this with thelp of user exit. Take help of an ABAPer.
I think you can use exit - USEREXIT_SAVE_DOCUMENT. Please have your ABAPer to checvk this exit.
Let us know.
Regards,
SB

Reason for Change LOV

Hi
Anyone know where the LOV is configured for the Reason for Change when an administrator updates an enrollment status? I'm sure I've done this before, but have a complete blank on it now!
Regards
Tim

As they say in the Simpsons "Dooh!!". Of course, thanks very much.
Regards
Tim

Mandatory field 'Reason for Delay" required in VKM3 Tcode application

Hi to all
We use tcode VKM3 to release the sales order for which credit limit check does not required.
Our requirement is to add a mandatory field 'Reason for delay" so that we can write in that field what's the reason to releasing it through VKM3.
Please guide me how to fullfill that requirement.
Thanks & Regards
Anubhav Gupta

Hi Anubhav,
Refer to the following very useful link:
Re: Add new fields to VKM3 transaction
Hope it helps.

Options under versioning tab

Hi,
What is the difference between the options available under "Versioning" tab
"Commit" and "Commit Design", "Update", "Update Design "
Thanks and Regards
Sugirtha

Hi Sugirtha,
"Commit" and "Update" should work on a selection in Pending Changes, while "Commit All" and "Update All" should respectively commit and update all changes regardless of selection.
I see that there is a bug and the "Commit" and "Commit All" have one and the same behavior, and "Update" and "Update All" have the same too.
I will log a bug for that.
Thanks and best regards,
Ivaylo

Process Order API -Reason for change either not provided ...

I'm calling Process Order API to update shipped_quantity for a RMA receipt. Nothing has changed about this code but now I am getting :
"The reason for this change is either not provided or invalid. (OBJECT=ORDER) "
We installed a patch last weekend to speed up Ship Confirms I wonder if we went backwards in OM. Any suggestions ???
Process Order code snipet:
l_header_rec.header_id := p_header_id;
l_header_rec.operation := oe_globals.g_opr_update;
l_line_tbl(1) := OE_ORDER_PUB.G_MISS_LINE_REC;
l_line_tbl(1).line_id := p_line_id;
l_line_tbl(1).shipped_quantity := p_rec_qty;
l_line_tbl(1).shipping_quantity_uom := 'EA';
l_line_tbl(1).flow_status_code := 'RETURNED';
l_line_tbl(1).operation := oe_globals.g_opr_update;
Call Process_Order
OE_Order_pub.Process_Order(
p_api_version_number => 1
.

Please review the documentation about process order API as there are several things you might want to revisit about this call to process order:
Following are my observations:
- you are updating shipped quantity. I think this field shoud not be updated using the API. As it shoudl be updated by a process(shipping process)
-You are also trying to update the flow_status_code. This field is also not supposed to be updated.
My suggestion is that you try to follow the same process step by step that one should follow to update the shipped_quantity on RMA order. (e.g. receiving the item against the order using inventory api's or probably shipping the order line using the shipping api's). I am afraid, using the given code you might create data discrepancy.
Hope this helps,
Nitin Darji

Sales Order Reason for change

Hello All
I have a requirement where we need to add order reason as a warning message whenever users makes following changes in the sales Order using VA02:
1. Change the Order Quantity
2. Change the delivery date for an item or items
3. Delete a particular line item
4. Add a particular line item
I know it can be handled via VA02 user exit. I have listed following user exits will be helpful:
USEREXIT_CHANGE_SALES_ORDER
USEREXIT_CHECK_VBAK
USEREXIT_CHECK_VBAP
USEREXIT_CHECK_VBEP
USEREXIT_CHECK_XVBAP_FOR_DELET
Can you please let me know out of these which one are apt for my requirement and also if let say user makes a change once in the sales order and maintains the order reason before saving it, but how will it be taken care for changes done by the user on some other time. Basically how multiple changes will be controlled?
Looking forward to your response.
Cheers
Ravi

If you keep this order reason in imcompletion log, it will work.
But here the issue is sytem has to validate the order reason field if any of the above mentioned fields has been changed(as suggested, system will give warning in standard except for 1 & 4 options)
Here you can take the report from all the sales orders and differentiate the orders with the above
4-changes with order reason changes into a Z-table with your Abaper.(RVSCD100 program)
But here instead of going for enhancement you can very well control this with user discipline.
system is just an instrument who can help us but cannot think always the way we presume.
Suppose if a user has changed the order qty then he has to keep X as order reason--due to his ignorance he kept Y as order reason.Now system feels that data has been maintained no error in In-Completion log.
Still if you are so keen then you can very well maintain Z-Table with the expected Order reason and you can write a code in USEREXIT_SALESORDER_SAVE(Sorry i am not with SAP now) with your Abaper.
Hope this works and let us know if any.
Regards
Phanikumar

Confirmation Fields Open for Change

We are currently on SRM 5.0 - Extended Classic Scenario and our business process rules allow users to only change the quantity field on confirmations. However after recently applying support packs (now on SP 15), we have found that all of the fields are open for change. Please guide me in modifying the configuration to make all fields to be non-editable except for quantity.

Hi Mitch,
You can achieve this by implementing the Badi BBP_UI_CONTROL_BADI and then for the confirmation implement method: BBP_CONF_UI_CTRL
Based on the fieldname in the ITS template you can mark the parameters: CV_INVISIBLE and CV_INPUT_READY.
You can get the field names from the SRM Web GUI, by going through the source code of the respective screen.
You will need some programming skills, but itu2019s not that hard to achieve. Other method would be the creation of screen variants (tcode SHD0). But I would advise to use the Badi.
Kind Regards,
Skander

Get ZTABLE Old - New Field Values for Change Document History Log

I have done all necessary log configuration for ZTABLE and able to see change document log via SCU3. My problem is that I have to write FM which returns Log History for a specific period. As I have gone throught the Report RSVTPROT. But not able to get how the log data is displayed.

Hi,
Try checking the FMs..Sorry I am not sure which one gives the log....These are the FMs called in the program RSVTPROT.
DBLOG_READ
DBLOG_READ_WITH_STATISTIC
Thanks,
Naren

Reason for change name

hi, what is the reason behind HTMLDB had change it name to Applicaiton Express? thanks.

a good point. does oracle ships out the product
bearing it's new name instead of HTMLDB?Don't know yet. As far as I can tell there's not a lot of 'shipping' going on these days, given the free downloadable world we live in.
I assume some progress has been made on repackaging the download but haven't checked that lately.
Just go to the OTN download or AppEx Studio home pages and try it out. Then you'll know firsthand.
Earl

Reasons for not supporting JDeveloper 3.1 version

Please mention the details reasoning of why JDeveloper 3.1 version is now no longer supported.
Are there Database querying related problems ?

because it is so old, that it's of interest to archeologists only anymore ;-)
there are 2 generations of jdeveloper, the pre-9i and the 9i. jdev 9i is completely new in comparison to the pre-9i versions. the last pre-9i version was jdev 3.2.3, so you may imagine, why 3.1 is no more supported.
trevi

Field "Reason for change" mindatroy in PO under "Version" tabe ?

Similar Messages

Maybe you are looking for