Auto UD for Rejected Characteristics

[former_member706977]

Hi,

I know the automatic UD for OK lots and how it works. But I want to do the following:

1. For all lots with origin 08 and rejected characteristics (one MIC only), make an automatic UD (rejected R)
2. Automatic stock posting to scrap

Is there any way to do this? Thanks!

Bilal

[anand_rao3 · Accepted solution]

Not with standard! You may have to develop a custom program. Logic would be as below. Check if works!

1. Inputs for this new program should mostly be same as in QA32.
2. The program should run only for inspection lots with 08 origin.
3. For the given inputs it would fetch required inspection lots and store temporarily in to internal table
4. Pass every inspection lot one by one to BAPI_INSPOPER_GETDETAIL.
5. Check if the inspection lot has any rejected characteristic (consider all the operation the lot has)
6. If found pass the lot to QA12 with default UD as REJ
7. In customizing (QS51) set posting to scrap with UD REJ. This will ensure automatic stock posting in to srap when UD REJ is selected.
8. Schedule this new program in background with correct frequency in SM36.
9. Prior to that you need to set appropriate variant for this program which will take care to fetch appropriate inspection lots for execution.

There could be aperformance issue with this logic as BAPI is going to check each and every MIC for its rejection value. Try to provide maximum inputs as you can to avoid delayed processing. You can also check with good ABAP consultant for its fine tuning.

Anand

[former_member706977 · Accepted solution]

Thanks, Anand.

So, there's absolutely no standard way?

Because the reverse is offered as standard (OK lots and post to unrestricted).

[Former Member · Accepted solution]

Hello,

Anand is absolutely correct, and as far as stdn procedure is concern either UD code = A.Manually or auto via QS51 settings system will post it into UNRES stock. In your case, you need to first identify Rejection at charc. level and based on that UD code as R. so for this custom development required and Anand already provided you the logic of functionality.

Regards