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]

Similar Messages

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.

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

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

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

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

BAdI or USEREXIT for changing data of purchase order header - ME21N

hello all,
I would like to ask you any way to change the field "reason for change" of the Purchase Order header.
I tried implementing the method PROCESS_HEADER of IF_EX_ME_PROCESS_PO_CUST
or changing reason_code of structure ekko in user exits EXIT_SAPMM06E_006 and EXIT_SAPMM06E_006
but it seems not to work.
How can i do?..
sap. v. ecc 6.0

>
Shiva Kumar wrote:
> Use the user exit : EXIT_SAPMM06E_012: This is triggered on saving of a PO...and user can add validations etc in the exit...
> Cheers
It doesn't work...
>
Martin Voros wrote:
> you get reference to object IM_HEADER in method PROCESS_HEADER of BADI ME_PROCESS_PO_CUST. On this object you can call two methods - GET_DATA and SET_DATA. GET_DATA returns structure with type MEPOHEADER. You can change your field here and then call method SET_DATA with your modified structure. This should work.
> Cheers
..same thing for this solution...
the field that i want to change is RSCOD inside structure EREVGRID...it seems to have also get_data and set_data methods ( IF_REVISION_ITEM_DCM ),
but I don't know which BAdI to implement that has a object type ref to EREVGRID...
Edited by: E_M on May 13, 2008 11:08 AM

CC01 Change type is in hide mode for Change master

Dear All,
Our requirement is to get the list of Change type in the CC01 T-code when we click the change master. When we select ECR then we are getting the change list of change type. But, when we select the change master as type, then change type is coming as grey field. So we want the list of change type in change master
Please suggest
Regards
Honyal

Hello Honeyl,
Try to understand the logic of ECR (engineering change request).
*Change Type*
    This key defines the change type for the ECR (engineering change request).
*Dependencies*
    If you change objects with reference to an ECR, you control the change process using the following statuses:
    o   System status
    o   User status, if the change type has a status profile assigned to it
        in the IMG
    The system performs workflow tasks if defined.
    Note:
    You can only replace the change type with another change type if the
    following data is identical in both change types:
Status profile
Workflow task
Signature network
You can replace a change type without a signature network by a
change type with a signature network.
It means when you are intended to use the ECM with Statuses like CHKD ECRA ECOP And wish to maintain the controls like ECR to ECO creation and approval then the ECR and statues are required and supported also. the change type decides the different Statuses for the ECR. Hence the change type will be not available with Change Master, where these all status management are skiphence the change type decides the different Statuses for the ECRed and designed for simple change request for which the simple Change master are quite enough.
Kindly go through the Glossary help for them both.
Change Master:-
Data record which contains all the information required for managing a change.
It contains descriptive data (such as reason for change) and data with control functions (such as valid-from date and indicators for object types). In addition to this data, which you can maintain directly, there is also data which the system updates automatically (such as administrative data).
ECR:-
Change master record created with reference to a change type, which defines a specific procedure for the change.
You cannot process change objects with reference to an engineering request (ECR). The person responsible must approve the ECR and convert the ECR to an engineering change order (ECO).
Regards,
Shyamal

Change System Status of SO item dynamically based on Reason for Rejection

Hi ppl,
Our SAP user has raised a requirement as described below:
In sales order (in creation mode (VA01) or change mode (VA02)), if at the item level, the reason for rejection is mentioned, then the system status for that item should be automatically set to Technically Complete SET (TECO); and if the user removes the reason for rejection for the item, then the system status Technically Complete should be RESET automatically.
We are looking for any user-exit or BADI available which would be allow this dynamic change of system status based on the reason for rejection field. (No manual interaction for setting or resetting the system status).
Technically, the functionality is based on the below fields:
Reason for Rejection: VBAP-ABGRU
System Status: JEST-STAT
Please provide suitable inputs.
Thanks,
Dawood
Edited by: Dawood.S.Ghasletwala on Jun 29, 2009 3:14 PM

program: SAPMV45A
User exit: USEREXIT_SAVE_DOCUMENT_PREPARE.
loop at xvbap where updkz NE 'D'.
if not xvbap-abgru is initital.
"set your system state here.
else.
"reset your system state here.
endif.
endloop.
hmmm you can as well try if you got all you need to know already in userexit: USEREXIT_CHECK_VBAP.
Edited by: Florian Kemmer on Jun 29, 2009 11:53 AM

Changing the status of the sales order item based on reason for rejection

Hi All,
When a Sales order item is rejected then the status at the item level is changed as 'TECO'.When the reason for rejection is removed the status 'Teco' is reset.This status change can be achieved using the user exit 'MV45AFZZ'.But the exit does not allow re-atp calculation whenver a blocked item is release.I have use the exit 'MV45AFZB' ,through this the status change as well as re-atp calculation takes place.But the status changed(Based on reason of rejection) does not appear in the same screen.The change gets reflected only when the sakes order is saved and i open it again.
I want the status change to appear in the same screen.I am doing my code in the form 'userexit_check_vbap' of the exit 'MV45AFZB'. Please let me know if there are any user exits or BADI's available for the same(Changing the status of the sales order item based on reason for rejection ).
Regards,
S.Subasree

Hi subburamaiah
If you want the report you can create a separate SIS report . In that take the input field as a Reason for rejection.. and ask for the output the list of sales orders .Now when you check this user defined report you will give the reason for rejection and check what all orders got rejected on that reason for rejection.
Regards
Srinath

Need to disable availability check while changing 'Reason For Order' Field in Retail Tab

While change of STO (Me22n) I want the availability check to be disabled when a change to 'Reason for Oder' is made in the Retail Tab in the item detail.
Let me know if there is any BADI/ User exit or enhancement available where i can do this customization.

Hi Reddy,
Try Transaction Variant, you can customize the screen using this tool.
Basically, you customize the screen (hide, make it required, visible etc) then
save it as screen variant and define a new transaction code to it.
So for your user, just give them this new transaction code (instead of SAP standard).
Detail about transaction variant can be checked on :
http://help.sap.com/saphelp_crm50/helpdata/en/7d/f63a0a015111d396480000e82de14a/frameset.htm
Hope this helps,
Gun.

Reason for rejection not changed in transaction MASS

Hi everybody,
I'm trying to update a sales order item with a reason for rejection (field VBAP-ABGRU) in transaction MASS but it doesn't work. I took a look in SAP notes and found similar problems but these notes (specially note 390105) don't apply to our version (4.7 support package 22). Before opening a note in SAP I would like to have someone's opinion about the issue.
Thanks,
Paulo

Paul, it doesn't work because the field is not updated despite success message issued when the transaction is finished (I tried to change the field content from blank to other value). The field is available in transaction MASS and I have successfully tested it in another system (release 6.00). But now I found a note (regarding to the same problem in another field - MASSSDPOSVBKD-KURRF) that can be helpful. It's note 777746 and it applies to our release. So, I'm waiting for the basis team to implement it to see what happens.
Thank you,
Paulo

Mass change with Reason for Rejection.

Dear Gurus,
Pl tell me the process to close all the open orders at one go. I have tried with the t.code MASS, but I was unable to do that.
Pl give the step by step process.
Regds,
Sreehari

Hari,
MASS transaction is useful, If you know what fields to change and in what documents/customers/vendors/.
In your case what fields is pretty clear (VBAP-ABGRU or MASSVBAP-ABGRU )
But what documents is not clear.
Points to consider.
     You can the documents that are open by just writing some query or even you can get it from SE16 using VBAP table
        and you can use these document numbers and enter in the MASS T.Code.
It looks simple but the main hurdle is not all of the items in these orders are open, right...so you can't enter the reason for rejection in an item which was already delivered, or scheduled to deliver.
So Unless you know that all the items of an order are open, its not feasible to use MASS T.code.
         So my suggestion is to write an ABAP program that check whether the item in an order is open or not and then change the reason for rejection using BDC code.
                Thats my suggestion. I hope you understood the reason for going to an ABAP program.
Regards,
Ajai.
Reward points if helpful.

Purpose of Reason for Change on Timesheets

Similar Messages

Maybe you are looking for