Purchase Req HR Org Structure

[Maue, Thomas X.]

Alon,
 
Rob gave some great solutions for applications areas that are not set up for
Organization
assignments.
 
There are configuration tables set up for Purchase Reqs already.  Another
solution here is -
 
Configure the position or Org Unit in OMGQ (Workflow button) just as you
would normally.
This is the logical place even though you have the configuration (release
code button) set to '9'.
 
Then retrieve the object type and number in the user exit code.  No
hard-coding is necessary.
Here is some sample code:
 
*----------------------------------------------------------------------*
*   INCLUDE ZXM06U12
*----------------------------------------------------------------------*
  DATA: I_TASK LIKE ACTOR_TAB.
 
* Get the task associated with the release group, code and plant - OMGQ.
 SELECT SINGLE * FROM T16FW WHERE FRGGR = I_EBAN-FRGGR
                              AND FRGCO = I_FRGCO
                              AND WERKS = I_EBAN-WERKS.
 IF SY-SUBRC = 0.
  I_TASK-OTYPE = T16FW-OTYPE.
  I_TASK-OBJID = T16FW-OBJID.
 
 
If you don't want/need entries down to the plant level then just add one
entry in OMGQ and change
above select statement to reflect.  Just depends on your requirements.
 
Regards,
 
Thomas Maue
Workflow Consultant
 
 
> -----Original Message-----
>> From: Robert Bates <Rob.Bates at itnet.co.uk>@LYONDELL
> Sent: Monday, June 25, 2001 5:46 PM
> To:   SAP-WUG at MITVMA.MIT.EDU
> Subject:      Re: Purchase Req HR Org Structure
>
>
> Alon,
>
> I have had the same requirement myself on several occasions. My usual
> solution
> is to create a custom table, with a parameter id column as the key and a
> data
> field. Then I create an entry on the table with my chosen key identifier
> (e.g.
> PREQ_APPR) and the organisational object identifier (e.g. S 500000001). In
> the
> user exit you can then code a select from this table with the key of your
> chosen
> name and retrieve the organisational object assigned. If the
> organisational
> object changes in the future, you can simply change the entry on the table
> and
> you won't have to touch your user exit code. If you generate a table
> maintenance
> dialogue for your custom table, the responsibility for maintaining this
> can be
> passed to "less skilled" people!
>
> If you want a more flexible solution, you could do what I do - create a
> generic
> custom table with key columns of ID and Sequence Number, and other
> columns: Sign
> (data type RALDB_SIGN), Option (data type RALDB_OPTI), Low Parameter and
> Hgh
> Parameter. The sequence number in the key allows you to create many
> entries with
> the same ID. For simple single parameters, create an entry on the table
> with
> your chosen name in the ID field and the required value in the Low
> Parameter
> field, then code a SELECT SINGLE low FROM parameter table WHERE ID = your
> chosen
> name to retrieve the parameter. For more sophisticated parameters you can
> create
> a range of entries in the table using the Sign (Include or Exclude) and
> Option
> (Equals, Greater Than, Between etc.) fields - then you can code a SELECT *
> FROM
> parameter table INTO TABLE internal table WHERE ID = your chosen name,
> then load
> that internal table into a declared RANGE, then you can compare against
> the
> parameter by coding, for example, IF container element IN declared range
> THEN
> result = 1 ELSE result = 2. I use this a lot - it makes it very easy to
> change
> the workflow process to reflect business process change without having to
> change, test and transport the workflow.
>
> Hope this helps,
> Rob Bates,
> eBusiness & Workflow Consultant
> ITNET plc SAP Division, UK
>
> To:       SAP-WUG at MITVMA.MIT.EDU
> cc:        (bcc: Rob Bates/ITnet)
>> From:     "Raskin, Alon (Soliance)" <ARaskin at cps-satx.com>
> Date:     06/25/2001 08:10:01 PM
> Subject:  Purchase Req HR Org Structure
>
>
>
> Hi All,
>
> When using the user-exit to determine the approvers for the Purchase Req.
> workflow, there may be a need to refer to a particular org object or
> position in the code. My problem with this is that it means I have to
> hard-code the object ID in the code. If this is ever deleted in the future
> all the code would need to be re-written and re-tested. Does anyone have
> any
> ideas how to refer to a particular position/org object without
> 'hard-coding'
> the ID in the code.
>
> Regards,
> Alon Raskin
>
>
>
>
>
> **************************************************************************
> *********
> http://www.itnet.co.uk
> http://www.itnet.co.uk/eb  -  Click here to see ITNET's ebusiness
> capabilities
>
> Any opinions expressed in this email are those of the individual and
> not necessarily those of ITNET plc and/or its subsidiaries. This email
> and any files transmitted with it, including replies and forwarded
> copies (which may contain alterations) subsequently transmitted from
> ITNET plc and/or its subsidiaries, are confidential and solely for the
> use of the intended recipient. If you are not the intended recipient
> or the person responsible for delivering to the intended recipient, be
> advised that  you have received this email in error and that any use
> is strictly prohibited.
>
> If you have received this email in error please notify ITNET Customer
> Service
> Centre by telephone on +44 (0)121 683 4043 or via email to
> csccom at itnet.co.uk, including a copy of this message.
> Please then delete this email and destroy any copies of it.
> **************************************************************************
> *********