Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Urgent help required for holding characteristic value in MIGO TCode

Former Member
0 Kudos

Hi Experts,

We need your help regarding the following,

Our requirement is that user will create batch along with characteristic at the time posting GR. Now we need to write some validation based upon the provide classification data before saving the GR.

We have checked BADI, (MB_MIGO_BADI) as created batch is not committed so cannot retrieve the characteristic value by using standard FM, have tried exit,

EXIT_SAPLV01Z_013 ,EXIT_SAPMM07M_004,EXIT_SAPLV01Z_014 but its' not stopping over there.

can you please provide your valuable feedback regarding the same ?

Thanks in advance.


10 REPLIES 10

matt
Active Contributor

You do know that what is urgent for you is urgent for practically no-one else on the planet? See point 3 here https://www.forbes.com/sites/travisbradberry/2015/05/05/5-rude-emails-you-send-every-day/#747ba67444...

pokrakam
Active Contributor

I always thought 'Urgent' means that the question is not directed at people who answer in their free time.

matt
Active Contributor
0 Kudos

Or does it refer to Gilgamesh who was definitely an Ur Gent...

I'm sorry, I seem to have walked into sapfans.com circa 2001.

pokrakam
Active Contributor

2006 🙂

matt
Active Contributor
0 Kudos

I stand, somewhat nostalgicly corrected.

Jelena
Active Contributor
0 Kudos

Not sure what to say... What's the deal with "create batch along with characteristic"? Is this standard or did you add that as well?

In general, before data is written to DB it resides in memory, so that's the only thing we can operate with. If that "batch" is supposed to be part of the same transaction (=committed with the GR document itself) then no BADI or user exit will offer you anything different. What's your design here? I'm confused...

Former Member
0 Kudos

Hi Jelena,

Thanks for your comments.

Let me explain bit more, we need to deal with a particular field in characteristic value,for exp, length.

Now once we provide the length and then return MIGO screen then we can have a batch number in BADI (MB_MIGO_BADI) but we will not be able to retrieve the value of length characteristic of that created Batch as that was not updated in DB. My requirement is to check that length characteristic value and based upon that error message will be thrown to stop creating material document.

Now problem is that , we are not getting how can we retrieve that characteristic value in that BADI / user exit in MIGO.

we can have the batch no over there (by using (SAPLMIGO)GOITEM ) but not getting how to get that characteristic value ,

can you please help us regarding retrieving that value ?

It will help us a lot.

Jelena
Active Contributor
0 Kudos

Again - is this batch/characteristic business standard functionality or not? I'm not a expert on MIGO and we don't use batches, so I wouldn't know. If you want an error to be triggered by some characteristic then it'd make more sense to trigger an error right there instead of waiting till later. Or even just not make this characteristic available to begin with.

Also again - the data will be in memory before it's written into DB. Have you tried retrieving it from memory?

Former Member
0 Kudos

Hi,

As I was trying to explain, my error will be thrown based upon the provided characteristic value, i can see its' in table parameter which is within standard sub screen but we do not have any enhancement point or BADI over there to export that value, also we can use field symbol to retrieve the value as its' taking to different screen.

Creating batch characteristic is standard functionality..

Jelena
Active Contributor
0 Kudos

It would be helpful if all this information was in the original post.

If there are no options to pass the value from one part to another then I'm not sure what answer is expected... Explain to the functional specialist that such validation is not technically feasible and then they'll need to design a different process that works within the enhancement limits that SAP allows us.