cancel
Showing results for 
Search instead for 
Did you mean: 

PS ACTIVITY CONFIRMATION CJ20N

Former Member
0 Kudos

Hi,

My client requirement is system should not allow user to confirm activity 0020 (int. processing 0020) unless and until user confirm activity 0010 (int. processing 0010).

Next operation confirmation should be restricted by system if previous operation is not confirmed. T_Code - JC20N. For that i am created status name "Confirmation Allowed & Block". But after release of all the activity when i tested to confirm 2nd activity system not block me before confirmed the 1st activity. How to maintain transaction control for user status "Confirmation Allowed & Confirmation block in t_code - OK02.

How can i assign multiple network type with single network profile.

Kindly assist me.

Former Member
0 Kudos

Hi,

Kindly tell how can i restrict confirmation of successor activity. System should not allow user to confirm activity 0020 (int. processing 0020) unless and until user confirms activity 0010 (int. processing 0010). Next operation confirmation should be restricted by system if previous operation is not confirmed.

Example in my Network structure diagram their is only one netwrok and three internal activities and relationship is finish start for all three activity.

1. activity ===>fs===> 2.activity ===>fs ===> 3.activity.

Is there any standard check box available to meet our requirements?

kindly help its urgent

Paulo_Vitoriano
Active Contributor
0 Kudos

Hi,

I think if you are using CATS, you can validate in a user-exit that the predecessor NWA (if exist) has a final confirmation processed. I am not familiar for such logic to be part of the standard system.

Regards,

P.

MTerence
Active Contributor
0 Kudos

Hi,

There is no standard way of doing this. I am not sure whether you have gone through below thread.

https://archive.sap.com/discussions/thread/859168

Regards

Terence

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member198942
Contributor
0 Kudos

Instead of using separate activities, standard way of designing this process will be to use the activity elements under main activity as 0010,0020 etc. This will ensure that activity cannot be full confirmed unless activity elements are confirmed in full. This will prevent any use of user status or exit enhancements.

Former Member
0 Kudos

Hello,

It's not about activity element, requirement is system should be block 2nd activity unless and until confirm the 1st activity. It's a production system, so all the user are block by system to change/edit the user status.

Kindly guide me to do this.