Valuation type field mandatory for Refurbishment orders

[faisal_khan]

Hi,

When creating Refurbishment Orders, we would like to make both the Valuation type fields mandatory when using tcode IW81.

How to go about it?

Thanks

Faisal

[former_member192897 · Accepted solution]

Not sure. But, give a try with Transaction  / Screen variant. I think it should work.

[jogeswararao_kavala · Accepted solution]

In fact I forgot about this option. This should work.

[faisal_khan · Accepted solution]

Hi,

Can you please elaborate a bit further, i.e. how to go about it?

Thanks

[Former Member · Accepted solution]

Hi Faisal,

For transaction variant, you have to use t-code SHD0.

here you have to provide a T-code e.g. IW31 and click  on Create button. System will show all screen fields wherein you can define particular fields as mandatory.

Regards,

AMol

[jogeswararao_kavala · Accepted solution]

Hello Faisal khan

I just recalled your requirement. In fact I was trying for sometime and left it because things were not working. Let's here from Ashok regarding the Screen variant way.  To me this issue will be in my mind until something comes out from somewhere. (In fact we are also having this screen without these fields as mandatory).

Good luck

KJogeswaraRao

[former_member192897 · Accepted solution]

Please search the forum for Transaction  / Screen Variant and you will get lot of Threads. You can also use google search engine.

There are Two Valuation type fields in IW81 under Header data MCHA-BWTAR and AFPOD-BWTAR. Both are available in Screen / Transaction variant. You can set them to Required using SHD0 and check once again.

[mdgolamrabbani]

Dear Faisal

How to Enable 1st Valuation Type, Please.

Thanks

M.G Rabbani

[jogeswararao_kavala]

Hello Faisal khan,

Here is a document which I consider the best available on this topic, with the help of which I tried this Transaction variant successfully years ago. You need not have a Z transaction to your Transaction variant. Page number 10 here tells how we assign this Transaction variant to the Standard tcode (in our case IW81). This document is a sort of Lost and Found for me.(I just relocated it)

Here it is  Creating Transaction and screen variants

In fact Requirements like making a field mandatory if not possible by customizing, the best option is user-exit. If it is not available then only one should go for Transaction variant.

Clue for you: You will first make Screen variant for program SAPLCOIH and Screen no.1126 > This Screen variant will be used in of Transaction variant and then page10 to have this variant assigned to IW81.

Please go through the document well. It does not only resolve your issue, but also adds value to your profile.

Good luck

KJogeswaraRao

[faisal_khan]

Hi

Thanks to both Ashok Kumar and Jogeswara Rao.

With your inputs I am sure I would be able to achieve the desired objective. Thanks Ashok for giving idea of Transaction/Screen variant and Jogeswara Rao for the document in last message.

Once I apply the changes then will update you and close the thread.

Thanks

Faisal

[faisal_khan]

Hi,

Thanks Ashok and Jogeswara,

Using the Transaction/Screen Variant, I was able to achieve the objective of making the Valuation type fields mandatory.

Thanks again

[Former Member]

Hi Faisal Khan,

In my opinion, you may want to go ahead with implicit enhancement. Please check with ABAP in order to search for a enhancement point. ( PAI event of screen).

Regards,

Amol

[jogeswararao_kavala]

Implicit Enhancement Points fall outside PAI modules where codes will not be accessible. You can throw more light on this.

[jogeswararao_kavala]

Hello Faisal khan,

This is a good and tough question for me. According to me it is not possible through customization and enhancements. Two methods to be explored.

1. Find suitable fm to retrieve Refurbishment data in buffer and use it in user-exit IWO10009.

2. Explore Implicit Enhancement Point in Order program namely SAPLCOIH.

Regards

KJogeswaraRao

[faisal_khan]

Hi Jogeswara Rao,

Your reply makes me a little worried as these methods needs R&D.Is there a way that upon saving system can check that these fields are not null?

Thanks

Faisal

[jogeswararao_kavala]

That is what needed for this. But that is the constraint. BWART field is not a part of any enhancement. So need to intercept Order program at suitable place and write a code in the Implicit Enhancement point. What I suggested was obviously not easy, Had it been so, by now I would have provided the code to you.

Another option is to try Field-symbols method in the above exit to capture run-time values of BWTAR field. (ABAPer will be able to do it.) In fact I tried various options intermittently last few hours, so far I could not get any break-through.