Skip to Content
0

User Status profile allowing stck pstg of QM lot with out UD & MIC completion

Jan 04, 2017 at 11:21 AM

150

avatar image
Former Member

Hi All,

The client had the below requirement for 01 inspection lot which had two operations. Both the operations had MIC's

Requirement1: First, results recording to be done for both the operations and the MIC's status to be set to 5 "Processing is completed". There should be no UD and no stock posting without results recording completion.

Requirement 2: Once results recording is completed for both the operations, then only UD should be taken mandatory and then stock posting to be performed finally.

In short there should not be stock posting with out completion of results recording and then the subsequent UD

I had created the user status profile using BS02 and maintained the below settings:

Status No. Status Initial Lowest Highest Position Priority

1 INIT X 1 10 1 1 2 QFIN 2 20 1 1

INIT had below statuses

Business Trans. No Influence Allowed Warning Forbidden No-Action Set Delete

Close Insp.-Complete X X

Complete Insp-Short Term X X

Make UD X X

Record Insp results X

Start inv. pstg bef. UD X X

QFIN had below statuses

Business Trans. No Influence Allowed Warning Forbidden No-Action Set Delete

Inventory Pstg. Required X

Start Inv.Pstg after UD X X

I had assigned the status profile of inspection type 01

My the inspection lot is not getting changed to QFIN status even after I complete the results recording for all the MIC's. When I try to manually change the status from inspection lot, then the system is allowing to post the Goods with out results recording / usage decision which is wrong.

Any suggestions please. Thanks for your support.

Regards,

Sandeep

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

5 Answers

Craig S
Jan 04, 2017 at 05:59 PM
0

Do you not already have usser status QM_L_003 in your system?

Also check this wiki listing:

https://wiki.scn.sap.com/wiki/display/PLM/Set+up+of+a+user+profile+to+avoid+the+UD+prior+to+RR

Craig

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Jan 05, 2017 at 08:53 AM
0

Hi Craig. Thank you very much for your response.

We had the user status QM_L_003 in our system.

I had implemented the suggested settings provided in link by you. Noticed the the business user is able to directly take the UD and perform stock posting from QA11 transaction even though no results were recorded for the inspection lot..which should not happen

Can you further suggest please..

Thanks & Regards

Sandeep Raja

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Are your MIC's short term or long term characteristics?

0
avatar image
Former Member Jan 07, 2017 at 08:47 PM
0

Hi Craig, Both the operations contains short term & long term MIC's with control indicator as "required characteristic".

Also attached the settings made by me to fulfill client requirement Page1.jpg, Page 2.jpg & Page 3.jpg.page-1.pngpage-2.jpgpage-3.png Request you to check and suggest for any modifications.

Thank you very much

Regards,

Sandeep Raja


page-1.png (100.2 kB)
page-2.jpg (46.2 kB)
page-3.png (75.2 kB)
Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Jan 16, 2017 at 05:35 AM
0

Hi All,

Can you provide any suggestions please or suggest any enhancement / user exits.

Thank you.

Regards,

Sandeep Raja

Share
10 |10000 characters needed characters left characters exceeded
Craig S
Jan 18, 2017 at 03:59 PM
0

Use QM_L_003 status profile. Assign this to your inspection types.

You can't make a UD without short-term characteristics completed. So limit who can force close insp. charac. via security. (several threads on this, google it).

Assign only a few senior people the ability to force close characteristics. and then have an SOP around this process.

This should work for you with basically no development.

Craig


pzofz.png (18.0 kB)
Share
10 |10000 characters needed characters left characters exceeded