cancel
Showing results for 
Search instead for 
Did you mean: 

Updating QPRS

former_member42743
Active Contributor
0 Kudos

We are using physical samples. There is an addon structure for stability sample for the QPRS structure. The .APPEND structure QSTQPRS0001. It contains the following fields.

PRIMPACK
STABICON
EINGDT
EINLDT
AUSLDT

We are trying to update the fields EINGDT and AUSLDT but are not having any success.

Has anyone done any developments where these fields are being updated by your development?

Is there a secret to it?

Craig

Accepted Solutions (1)

Accepted Solutions (1)

former_member42743
Active Contributor
0 Kudos

The issue was resolved by copying FM

QPRS_QPRS_STORAGE_UPDATE

to a Z program and adding in the desired fields from the add-on fields.

So far so good.

Thanks!

Craig

Answers (4)

Answers (4)

As far as i remember all those fields are updated through a standard BADI Implementation QPRS_ADDON_TAB_06 . Maybe this could be your starting point to see if there is anything missing there. The BADI has a filter on the screen Control Key of your stability sample type..worth to check in case you are using something different than standard.

former_member42743
Active Contributor
0 Kudos

Thanks. I looked at that exit earlier. If I understand it, that is to provide an additional tab in the sample record transactions, (QPR1,2,3).

We are planning on implementing that as well and that's underway.

Thanks!

Craig

Hi Craig,

I had done some tweaks on a similar case but the requirement i had at the time was to place some default params (not on this structure) upon sample Creation. Is it a similar case or you want to update an existing sample?

If upon creation i can share with you some tech details.

S.

former_member42743
Active Contributor
0 Kudos

We do have developments that update fields in the standard QPRS structure. It seems to be an issue with the addon structure fields only. 😞

For instance, one goal is to put the date the sample was "Marked as stored" into the addon field

QPRS-EINLDT "Storage Date of Sample for Storage Condition"

Craig

raymond_giuseppi
Active Contributor

Did you look at BAdI such as QST02_STABILOT_WA, or did you perform some reverse analyzis from update FM QPRS_MASTER_SAMPLE_UPDATE backward?

former_member42743
Active Contributor
0 Kudos

I passed your comment on to our developers to look into.

Thanks!!

Craig

0 Kudos

Sorry..but i am confused. The Badi with the extra Tab + stability study Functions are supposed to be automatically activated when you are using the PLM Addon package. Can you check if you have activated the Business Function EA-PLM in Sfw5? There are a couple of notes on this.

former_member42743
Active Contributor
0 Kudos

sfw5.png

Yes. Its activated.

I believe that just makes it available. That makes the configuration node available in SPRO. It also, appears to add in the additional fields into the QPRS structure as an append structure to the table. You also then get the opportunity to add your own custom fields in a customer append structure.

But from the help screens, it does appear you need to perform some development to interact with the fields. Especially if you are implementing this for samples other than pure stability samples. For instance your custom sample screen can be set up by sample type to have the fields in these addons you want to be able to interact with. Reserves for vendor samples might not use the same fields and hence same tab screen as say samples of manufactured items.

Also, this all deals with interacting with the samples in QPR1/2/3. We were looking at creating some additional transactions. For instance, samples are often collected throughout the day, during the night and over weekends. At some point, those are actually put away into storage, sometimes the next day, sometimes a couple of days later, (i.e. on Monday after the weekend). We don't want to interact with every sample individually in QPR2. So we needed some transactions. For instance, one that would update multiple samples as stored and update the date stored. Otherwise our people would be spending a lot of time in QPR2 updating storage dates.