Workflow - Prefix Number DEV/QUA/PRO

[glauco]

Hi friends,

I'm configuring a wf and I'm transporting it from DEV to QUA. I know that I have to configurate the Prefix Number to tasks. I've created it to DEV and it was transported. But it doesn't work.

Do I need to create a new prefix to use on QUA and after that ... a new to PRO too ?

[ramki_maley]

Hi,

You only need to assign Prefix numbers in DEV. The task number is assigned in DEV only when you create a new task. The new task with the assigned number moves to the systems in the transport path.

Cheers,

Ramki Maley.

Please reward points if the answer is helpful.

For info on awarding points click on this link: https://www.sdn.sap.com/sdn/index.sdn?page=crp_help.htm

[glauco]

Ramki, I know that, but the DEV system says that this prefix number has already been created.

I know too, that it has the key :

Prefix + System (I.E. DEV) + Client

And I tryed to create a new prefix appointing to another client...but it didn't work... coz the R/3 syatem always give me that message..."this prefix has already been created" but doens't exist another prefix for another client yet !

It's so crazy !

Please somebody help me !

[ramki_maley]

Hi,

Tasks and WF templates are client independent therefore you can only assign it once and in the client where you actually create the objects. Also tasks & templates are created with the key Prefix + Serial Number and not Prefix + System (I.E. DEV) + Client.

You do need to configure the WF runtime in each system/client where you want to test your workflows.

Cheers,

Ramki Maley.

[glauco]

OK, my friend,

I've undestood. But why does R/3 ask me for request ?

I think it was to configurate (those prefixes) only on DEV client and transportate those for QUA and PRO.

I.E. all on DEV (wrong way):

On DEV System:Create prefix 990 + DEV + 103

On DEV System:Create prefix 990 + QUA + 303

On DEV System:Create prefix 990 + PRO + 303

But you've said it doesn't work in this way and I have to configurate in each system:

I.E. all in each system (YOUR right way):

On DEV: Create prefix 990 + DEV + 103

On QUA: Create prefix 990 + QUA + 303

On PRO: Create prefix 990 + PRO + 303

waiting for reply... thanks

[ramki_maley]

The Workflow runtime & development configuration (Txn SWU3) is not transportable. Like I said before the Prfix number is attached to a serial number for some of the custom workflow objects. I do not know of an object where instance name and client are attched to an object. I am not sure what prefix you are talking about.

Are you being prompted for a request while saving a new task? That is normal.

I might have misunderstood your question. Please explain step by step what you are trying to do - either by menu path or transaction code and what data you are supplying.

Cheers,

Ramki Maley.

[glauco]

I'm trying to configurate the workflow on QUA 'cause I've already developd and configurated it on DEV, ok ?

so, I'm trying to configurate on QUA on transaction SWU3 witch is saying me that I have to configurate the prefixes for this client. So I'm using OOW4 for this. On OOW4, I'm trying to configure this so the wf system accept and know the tasks I've configurated on DEV on QUA system too.

Problems:

1-I remember now that I've already configurated it on DEV, creating a 990 prefix to tasks, so, I've created all standard tasks (on pftc: this tasks, in a wf, call an object method crteated on swo1) on DEV with this prefix 990...1, 990...2, etc.

2-On QUA System, for these tasks, I have to set the responsables again on QUA too, so I'm not archiving this objective, coz sap say I haven't autorization for this.

3-Each task, I have to set the responsable on QUA now.... but when I enter to set it, it doesn't show the line with yellow color with the description "general task"... too.

an another problem (How to set a user on a background task witch executes a MIGO, so sap system is setting with WF-BATCH on MIGO) I'm post in the forum now.

waiting for reply... thanks.

Glauco

[ramki_maley]

In transaction SWU3, in a non development client (your QUA) you only need to perform the steps under the first activity 'Maintain Runtime Environment'.

Once your WF objects (Tasks, Templates, BO, etc) are transported into the target system, perform a buffer refresh using transaction SWU_OBUF.

The General Task attribute for Task can be set in the display mode (txn PFTC_DIS, display the task then to menu option additional data-> Agent assignment -> Maintain). If you get an authorization error, get the missing authorizations assigned by your Security team.

Cheers,

Ramki Maley.