SAP for Higher Education and Research Discussions
Spark conversations about student engagement, research optimization, and administrative efficiency using SAP in higher education and research. Join in!
cancel
Showing results for 
Search instead for 
Did you mean: 

PIQSTM - Restrict related persons information

l_molenaar
Participant
0 Kudos

In transaction PIQSTM we want to restrict the related person with an "End Date". Unfortunately we can not find a method to change this date in transaction PIQSTM.

The restriction of a related person is possible by using transaction PP01 which is not our desired solution. Is there a method to restrict the related person using transaction PIQSTM?

We want this because it happens that a student has an attendant (someone who takes care of the student). Now it happens that that person changes. Therefore it is nessesary we can restrict the related person and add a new one.

Can anyone help me further with this problem?

Kind regards,

Lukas Molenaar

1 ACCEPTED SOLUTION

former_member182585
Contributor
0 Kudos

Dear Lukas,

If i understand it correctly, then you want to restrict an employee(related person) not to use Transaction PIQSTM as he is shifted to other position/place.

In this case you can use structural authorization functionality.

Hobbins, Bach, is it possible to create a position as related person along with some default roles and responsibilities related to required Transactions ? This will help in getting a new person on board and by attaching him to said position, system will automatically transfer the roles.

Hope this will clear your doubts.

Warm Regards

Vinod Kumar

View solution in original post

5 REPLIES 5

michael_hobbins
Active Participant
0 Kudos

Hi Lukas, from the description of the related person you're mentioning, I'd suggest you'd use the Advisor field on the Individual Study data infotype (the latest versions name the infotype Study data ).

The relationship has BEGDA and ENDDA to define the validation period and are modifiable directly from the infotype tab on Tx PIQSTM. The relationship is modelled on HRP1001, where the ST object relates to a person or positon for example (relation A515).

If you decide to use this field, then I suggest you read the following document where you'll find the user interfase for the advisors to manage their advisees

[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9048df93-8c60-2b10-0c8e-df70b3ac5c99]

Regards

Michael

former_member583013
Active Contributor
0 Kudos

Hello Lukas,

the related person validity can only be changed using transaction PP01. It is not possible to change it in transaction PIQSTM, tab Related Persons, on the Business Partner itself as it's an SLCM relationship (Relationship A521). Please follow the menue path" Go To->Enhanced Object Description. It takes you to the object maintenance screen of PP01 where you change the End Date of this relationship.

Regards,

Tina

former_member182585
Contributor
0 Kudos

Dear Lukas,

If i understand it correctly, then you want to restrict an employee(related person) not to use Transaction PIQSTM as he is shifted to other position/place.

In this case you can use structural authorization functionality.

Hobbins, Bach, is it possible to create a position as related person along with some default roles and responsibilities related to required Transactions ? This will help in getting a new person on board and by attaching him to said position, system will automatically transfer the roles.

Hope this will clear your doubts.

Warm Regards

Vinod Kumar

0 Kudos

Hi Vinod, this "related person" you state doesn't seem to have a clearly defined functional role, hence it'll be difficult to create a common position with transactions and roles/profiles assigned. I haven't done any work on this issue, but it doesn't seem logical, maybe Tina or someone else can add some more info.

Regards

Michael

0 Kudos

Hello all,

Thanks for aswering. I was hoping there would be a way in the PIQSTM. It is quite common in the education i work for the related persons change. So i'm really missing that functionality in the PIQSTM.

I hope someone from SAP can take this into concideration and maybe add this functionality to the PIQSTM??

Best regards,

Lukas Molenaar