on 01-27-2011 11:04 AM
HI Guys,
i need your advise.
when a Migo against Process order is done, it is created the next inspection date. now if the migo is done 2 days after the Process order this date is different.
what we want is to have the next inspection date equal to the production date. i found in that in migo code:
IF ls_mcha_buffer-qndat IS INITIAL
AND NOT ls_classification-prfrq IS INITIAL.
ls_mcha_buffer-qndat = ls_mcha_buffer-lwedt +
ls_classification-prfrq.
mcha is the i batch table, and qndat is next inspection date.
if we create a ZMIGO with an if for qndat that says for example " if migo date is different then production date, enter production date" it is ok?
thanks
C.
I thinks you should explore User exit
QEVA0003 -->Calculate "Next inspection date" for batch Provided that you are talking abt Recurring Inspections............
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
While it looks like your idea will work, I would suggest you look at using a user exit tied to the posting being done in the migo. I'm sure there is probably a user exit or enhancement point available when the migo is done. Let the system calculate the next inspection date as it normally does,then use the exit to check the inspection date and modify as you need to.
The problem with using custom transactions is that when SAP puts in changes via hot packs or regular upgrades, you'll have to update your z program for your z transaction constantly. Otherwise after a few years you have a woefully antique version of MIGO. If you place the check and change in a regular enhancement or user exit, you shouldn't have to worry about updates in the future. SAP has to honor the use of the exits.
FF
User | Count |
---|---|
98 | |
12 | |
10 | |
6 | |
6 | |
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.