on 09-10-2014 7:20 AM
Dear All,
My Requirement is to hide payment terms field VBKD-ZTERM in sales order.
1. I have tried the same using T Code SHD0 by modifying screen 4440 (Ticked Invisible check box) but unfortunately desired results could not be met. Screen shots attached for reference.
2. Do I need to make a copy of existing transaction variant BUS2032 and apply the new changes?
3. Am I committing any mistake at a basic level?
Appreciate your prompt response on the same.
Regards,
Anirban
Hi
Payment term is there in three screens. Overview, header and item level. You have to make this field invisible in all three screens. Check the screen numbers from sale order screen in System > Status and match these screen numbers where you have marked ZTERM field as invisible.
If you have maintained payment term in customer master and marked this field as invisible in sale order still system will save the payment term in field VBAK-ZTERM. I have not tested this but I believe this is how system should work. Please test and update,
Thank$
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear MoazzaM,
I know that payment term is available in 3 screens. My question is that if I make the field invisible in any of the screen then it should at least perform for that particular screen. Because I tried the same with Std TV BUS2032 and it worked.
Or is it that If apply the changes for all the screens it would take effect in case of Z transaction variant?
But I am surprised why the same is not getting called when I use a Z transaction variant. Also please note that if I refer to the Std TV BUS2032 and make a copy of the same I am still not able to use it as the screens called there are already used at many places in standard SAP?
Please suggest.
Regards,
Anirban
Hi,
Thanks ! Its working after assigning it to an order type. But here I am still left with one weird doubt.
1. To hide a field in sales order (in this case VBKD-ZTERM) we need to assign the TV to the document type.
2. But in case of any other changes in the initial screen (I tried to make sales Office field as mandatory) it worked without even assigning it to the document type.
3. Are there any thumb rules for this?
Regards,
Anirban
Well I don't know any thumb rule but I can share my personal views about it. If we run TCode VA01 we can modify field without assigning variant to order type because it doesn't involve order type at this stage but once you give order type and go to that order type's screen than it becomes mandatory to assign the variant to order type in VOV8.
In short Sale order behaves in different and special way but VA01 external screen behaves just like normal and all other screens.
Thank$
anirban,
What is the business reason for not wanting this field in the sales order?
As you know, this field is in billing document also. What does the client want in billing document?
If a customer has some terms of payment; in the customer master record. Then what is the expectation when sales order and billing document are created?
TW
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear TW,
The client does not want the payment terms VBKD-ZTERM to be modified and displayed for a particular order type in Sales Order only. It should flow from customer master. If the requirement would only have been restricted to modification of the field then I could have used Display check box. But here I need to hide the same. Can you please let me know how is it possible?
Regards,
Anirban
Dear TW,
Client does not want the end user to change and view the payment terms in sales orders for a particular business scenario (identified by an order type) for a specific user group. (This might be an administrative/management decision which client does not want to reveal.)
Billing is carried out by some other user at Branch level wherein Sales order is created at the Warehouse level.
I will obviously get back to client with the impact analysis but before that I need to know the feasibility aspects.
Regards,
Anirban
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.