Agent assgnment in PO release

Hi all,
I am using the default rule (Default rule 20000027)for agent assignment . In SPRO 2 release codes are there.
when I am using the default , it is identifed the only 1 user, it is nor identifying the 2 nd person, When I hard coded user, then it is identify. please for this agent assigement.
regards,
Ajay

when I am using the default , it is identifed the only 1 user,
it is nor identifying the 2 nd person, When I hard coded user,
then it is identify. please for this agent assigement
In SPRO settings for the second relaese code maintain Role resolution for workflow as 9 , I think in the rule it is determninig the agents based on the release code , may be you have set the release code as 1 and when realease code is one it always determines only one agent, so maintain the release code as 9 and define the logic to determine all the responsible agents in the user exit
EXIT_SAPLEBNF_005
Please check in the rule for user exit at line number125.

Similar Messages

Where to assign User Id to agent id in PO release strategy work flow

Hi Guys
I have on requirement
Where to assign User Id to agent id in PO release strategy work flow
Thanks in advance
SAP MM

Hi,
Check & follow the path:
SPRO-- > MM ---> Purchasing -> Purchase Order- > Release Procedure for Purchase Orders -
> Define Release Procedure for Purchase Orders -
> Workflow
Here against each release code assign respective User ID's for Release Code
Regards,
Biju K

Agent Determination - PR Item Release

Hi All,
I'm trying to set up standard workflow WS00000038 for purchase requisition release notifications. I'm having a problem with determining the correct agents. I receive the following error in the log when the workflow runs:
Agent determination for step '0000000003' failed
Error in resolution of rule 'AC00000148' for step '0000000003'
I am using standard task TS00007986, and rule 00000148. The configuration for the release procedure is complete and working. I have maintained values for users in T16FW, and set the release codes to '1' for workflow. When I try simulating rule 148 in PFAC, I see that it is pulling from table T161E - and the only release code maintained there is a default 01 in german. I tried creating a custom rule that referenced T16FW, but the simulation failed for it as well.
I am very new to workflow. What do I need to do in order to have this event notify the correct user defined in customizing?
Thanks,
J

Hi,
The entries in table T16FW are made via customizing for the PR release. View V_T16FW is empty... I tried entering manually through SE16 and saving, but it would be blank if I looked at it again.
However, I don't know if that is the problem. I cannot get the rule to determine an agent in PFAC. Currently I have modified rule 00000148 to have the container ReleaseCode look at table T16FW, field FRGCO. It is also still getting requisition from BUS2009. When I simulate in PFAC, I cannot get an agent to be determined.
T16FW contains a link to usernames which are maintained. Why is this rule not determining an agent during simulation?
Thanks

Agent problem in Payment Release Workflow - SPRO

Hi FI PRof's,
I am using the standard workflow WS00400012 for Payment Release.I am using two level approval process.If the invoice amount is less than 20,000 it should goto approver X and if it more than that it should do for X first and then to Y.
I have assigned the agents in SPRO Customizing as follows :
WF Variant - 2000 Approval path - 0001 Level - 1 R.Amt - 10,000 Agent - X
WF Variant - 2000 Approval path - 0001 Level - 2 R.Amt - 999999... Agent - Y
I am using the standard rule 00400125 for agent asssignment.
My Problem for single level release the agent is found(X) and WF is fine.
But while two level release the responsible agent is not found..What could be the problem. Am I missing any thing in Customization.
Rgds

Hi,
You had any response about this problem or able to solve it?
I'm having the same current problems and have not found a solution!
Regards!
Ariel Prebianca

Agent problem in Payment Release Workflow

Hi WF PRof's,
I am using the standard workflow WS00400012 for Payment Release.I am using two level approval process.If the invoice amount is less than 20,000 it should goto approver X and if it more than that it should do for X first and then to Y.
I have assigned the agents in SPRO Customizing as follows :
WF Variant - 2000 Approval path - 0001 Level - 1 R.Amt - 10,000 Agent - X
WF Variant - 2000 Approval path - 0001 Level - 2 R.Amt - 999999... Agent - Y
I am using the standard rule 00400125 for agent asssignment.
My Problem for single level release the agent is found(X) and WF is fine.
But while two level release the responsible agent is not found..What could be the problem. Am I missing any thing in Customization.
Rgds

I can't check it since I don't have access to a SAP system here, but don't you have to define the first-level approvers separately for the two scenarios? Perhaps my memory is incorrect, but I seem to remember that you can have one first-level approver for the low amounts, and a different first-level approver for the high amounts.
This is mostly a chore that just requires additional maintenance since it seems "everyone" is using the same first-level approver independent of amount, but flexibility is highly regarded in SAP...

Agent determination in PO release

HI all,
In my work flow 2 agents are there. I usng the standard rule ( 20000027)to identifying the agents. This is identifying the 1 st agent , not working for 2nd agent . to find out the agents I find the below code from SDN and wrote it .. Still it is not finding the 2nd agent.
DATA:
      releasecode type t16fs-frgc1,
      frggr type ekko-frggr,
      frgsx type ekko-frgsx,
      frgzu type ekko-frgzu.
select single FRGGR FRGSX FRGZU from ekko into (FRGGR,FRGSX,FRGZU) where
ebeln = object-key-PurchaseOrder.
CALL FUNCTION 'ZPO_REL_CODE'
EXPORTING
    PURCHASEORDER = object-key-PurchaseOrder
    RELEASEGROUP = FRGGR
    RELEASESTATUS = FRGZU
    RELEASESTRATEGY = FRGSX
IMPORTING
    RELEASECODE = releasecode
EXCEPTIONS
    OTHERS = 01.
CASE SY-SUBRC.
WHEN 0.            " OK
WHEN OTHERS.       " to be implemented
ENDCASE.
swc_set_element container 'releasecode' releasecode.
END_METHOD.
Code inside ZPO_REL_CODE is as below :
FUNCTION ZPO_REL_CODE.
""Local Interface:
*" IMPORTING
*"     REFERENCE(PURCHASEORDER) TYPE EKKO-EBELN
*"     REFERENCE(RELEASEGROUP) TYPE EKKO-FRGGR
*"     REFERENCE(RELEASESTATUS) TYPE EKKO-FRGZU
*"     REFERENCE(RELEASESTRATEGY) TYPE EKKO-FRGSX
*" EXPORTING
*"     REFERENCE(RELEASECODE) TYPE FRGCO
data: itab type STANDARD TABLE OF T16FS,
      wa_itab LIKE LINE OF itab.
select single * from t16fs into wa_itab where
frggr = RELEASEGROUP and
frgsx = RELEASESTRATEGY.
if RELEASESTATUS is INITIAL.
    RELEASECODE = wa_itab-frgc1.
    ELSEIF RELEASESTATUS = 'X'.
    RELEASECODE = wa_itab-frgc2.
    ELSEIF RELEASESTATUS = 'XX'.
    RELEASECODE = wa_itab-frgc3.
    ELSEIF RELEASESTATUS = 'XXX'.
    RELEASECODE = wa_itab-frgc4.
    ELSEIF RELEASESTATUS = 'XXXX'.
    RELEASECODE = wa_itab-frgc5.
    ELSEIF RELEASESTATUS = 'XXXXX'.
    RELEASECODE = wa_itab-frgc6.
    ELSEIF RELEASESTATUS = 'XXXXXX'.
    RELEASECODE = wa_itab-frgc7.
    ELSEIF RELEASESTATUS = 'XXXXXXX'.
    RELEASECODE = wa_itab-frgc8.
    ENDIF.
ENDFUNCTION.
Please help me to solve the issue.
regards,
Ajay reddy

Hi,
You can acheive your requirement using deadline. substitution is nto required.
1)Specify the 2days time in the latest end tab
2) select the modelled deadline in the options below.
3) in outcomes tab, activate the processing obsolete line
4) now u can c 3 lines from the task for release
     1) normal flow whn executed
     2) Will check the deadline. Once it is reached it will progress with the steps in processing obsolete branch.
     3) Processing obsolete branch. In this branch,
           a) place the 'PRocess Control' step to remove the workitem from the preovious user
           b) Include the workitem step to send it to the next person who shld release the PO.
Hope this helps you.
Regards,
Sivagami R

Document Parking Workflow Responsible Agent for Two level release

Respected Members,
I have done all the configuration for document parking workflow.
i had said if the amount is greater than one lakh it should go two-level amount release.
My organisation hierarchy includes two positions,
SUB_HEAD with user xyz
HEAD with user ABC.
i have assigned the position HEAD with two level release workflow in spro.
When i am creating a parking document above one lakh, the work items are generating and it is coming
in the inbox for the both users ie xyz and abc.
MY requirement is that when xyz user execute the work item then only it should go to abc user inbox.
it should not go to abc inbox as soon as document is created.
Please give me the answer as soon as possible,
Thanks a lot.
Manish

Hi,
Have you checked out SAP help file for this workflow?
[http://help.sap.com/erp2005_ehp_04/helpdata/EN/0e/0e3b00b84111d3b5b2006094192bbb/frameset.htm]
Regards,
Lim...

FI Payment Release Workflow Agent assignment and SPRO settings.

Hi Experts,
I am working on Payment release workflow for 2 stages. So for this i have activated the main workflow WS00400012 and for First level release WS00400011 and for second level release WS00400021.
Now where should i assign the agent for First level release and second level release ? and what setting should i do in SPRO as FI settings.
Any of you suggestions will be of great help me to resolve this issue.
Regards,
Hari

Hi,
Thank you for your reply.Should i mention the main workflow number in SPRO or
just the subworkflows alone ?.
Assign main workflow number
Can i assign users directly in workflow itself insteas of assigning position in SPRO.
Don't assign users inside the workflow, if the user id you want to change then again you have to change the workflow.
Regards,
Surjith

How to assign agent assigment in release strategy WS20000075?

I have copied the standard workflow WS20000075 and then created Workflow template and in trigering events tab of the wf template, I have binded the event RELEASESTEPCREATED.I have also done the SPRO settings for release strategy,i.e,that is I have assigned the users for each release code in table T16FW and mentioned the role resolution in the as 1 in the table T16FC.
The workflow is working fine but I am a bit confused with the agent assigment in the tasks TS20000166 and TS20000168.I have noticed one thing that in the task TS20000166 a default rule 20000027 - Person responsible for PO release,but it does not seem to work.The TS20000168 does not has any default rule for agent.
Can anyone guide me how i can do the agent assignment for this workflow.
Message was edited by:
Babar Haroon

There is no requirement for default rules.
Agent for task TS20000168 is assigned in the workflow where it is used.
If the default rule for task TS20000166 does not seem to work you should first of all check all the obvious potential problems, and secondly (if you haven't found out what the problem is) tell us <u>why</u> you have concluded that it does not work.
Check:
1) that the task has either been defined as general task or has possible agents assigned
2) that your customizing for the release code has "1" as workflow configuration and that there is a valid agent assignment for the code - alternatively "9" as config and the user exit is implemented
3) that there is overlap between agent assignment for the release code and possible agents for the task

CTI OS desktop client freezes after release of transferred call

Using CTI OS desktop v7.5(9), UCCE 7.5(9), Endpoint is CIPC 8.6.3 on CUCM 7.1.3
ACD call received by Agent 1 on ext 1111
Agent 1 transfers to 1112
Agent 2 answers transferred call on 1112 using answer call button.
Agent 2 disconnects using Release Call button on CTI OS desktop
Call disconnects but stays in grid with status 'Talking' and buttons on CTI OS desktop become unresponsive. CIPC is fully usable independently.
Agent 2 can reset by killing the CTIOS Desktop process and restarting.
This condition ONLY occurs as the result of an inbound transfer to Agent 2. It does not appear to happen when a call is transferred to Agent 1 in a similar scenario (Agent 1 is on a 7942)
Any thoughts as to why this occurs?
Thanks so much for any assistance!

Hi,
looks like for some reason the CIPC does not informs the CUCM about the call released event. Or it does, it's only the JTAPI gateway that misses it.
Did you try upgrading/downgrading the firmware of the CUPC?
Also, I am not quite sure that CIPC 8.x is supported. It might be, but it certainly is not on the list:
http://docwiki.cisco.com/wiki/Unified_CCE_Software_Compatibility_Matrix_for_ALL_7.x_Releases
G.

Purchase requisition workflow - reset release via BSP and BAPI

Hello,
We have a small workflow to release purchase requisition.
A mail is send to the approver. The approver opens an BSP application to release or refuse the PR.
The approval works well.
The rejection doesn't work well.
I use the BAPI_REQUISITION_RESET_REL_GEN to reset the first release of the PR (00 release key)
We have 00, 01, 02 as release key, and all the release have to pass to release completely the PR.
00 is the requester level.
My problem is :
for example I am the 01 level. I received the mail from 00 level, I refuse the PR via the BSP. In ME53N, the current release key is now 00 but when I look at the workflow, the following agent (corresponding to 02 release key) is determined. Normally nothing has to happen.
Someone has an idea to stop the workflow ?
thanks
Véronique

Hi Martin,
When I checked the contain of container in the workflow (in the log), I saw that the release key is 02.
I don't know why but the WF received the event RELEASESTEPCREATED instead of normaly it is finished.
When I reset the release via ME54N, the WF ends correctly and no new event is received.
How can't I see why the event is started in the BAPI.
In fact it is very strange, if I used the BAPI alone, all works, no new event is started.
But if I used the BAPI in my BSP, a new event is started.
Thanks
Véronique

The task TS20000166 in PO release workflow( WS20000075 ) is not terminating

Dear Experts ,
The task TS20000166 in PO release workflow( WS20000075 ) is not terminating after release the PO .
In the WS20000075 ,the event RELEASESTEPCREATED is triggeing and move to the next step.The next step is 'Release of purchase order' , the task TS20000166 is not terminating after release of PO .So Workflow is not move to next step i.e TS20000168.
I have noted TS20000166 is having three terminating event ( RELEASED,RESET,SIGNIFICANTLYCHANGED ) but still it is not terminating.
Is it Clear.If you want more details please let me know .Please help me.
Thanks and Regards
Rajesh

Dear Raj,
Please check agent assignment. And also check graphical mode error and check how many events fire one after one. Because for rejecting there is one more workflow u have to activate but i dont think so u have to activate it after realease . In agent assign ment check workflow with normal agent assignment dont use release stretargy then check it again if it is working fine then it must be problem of agent assignment step.
Reagrds,
Gurprit Bhatia

Positive Release of Materials in SAP QM

Hi
We are currently activating the Quality Management Module in SAP (We have already implemented PP, MM, SD, FI, COPA modules).
We have a typical requirement. Under normal circumstances materials which are not cleared by Quality, cannot be despatched. But we want to despatch materials only upto Consignment Agents point (Although Quality release is not done). The Consignment Agents are configured as Plants in our system.
However, the Consignment Agent should not be able to sell the stock until it is cleared by QA. In other words, system should permit Stock Transfers of such stock but not allow Sale of such stock.
Is there any way such a scenario can be handled in SAP? We are on version 4.7.
Regards
Shobhana.

Have a look at the config. under:
LE/WM/Activities/Transfers/Define stock transfers and Replenishment Control
in combination with one of the RLLNACH* programs SAP help text for RLLNACH4 below >>
You can use this report to control replenishment within the warehouse for storage types with random storage bin management. The system calculates the replenishment quantity on the basis of the current stock situation in the storage type and the replenishment quantity defined in the material master record. The system then creates transfer requirements (TRs) for the calculated replenishment quantities.
You'll need a new movement type and a new Reference Storage Type search record.

Hide Processor ID in PO release code

Dear Experts,
I have requirement to hide processor ID in PO release code. I have maintained user id as agent ID in PO release code workflow.
And apparently, processor ID displayed in PO release strategy tab.
I need to hide processor ID from release strategy tab while agent ID still maintained.
Do you have any suggestion? Please advice
Thanks in advance

Hi,
Field 'processor' is displayed if the release strategy used in PR/PO is subject to workflow. If workflow is not used in the release strategy then this field is not shown.
To hide this field even in case of workflow used, can be done only through modification to standard system.
I have found that you can change the name by using the following user - exit EXIT_SAPLEBNF_005.
br G

Dbsnmp agent not running

STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 8.1.5.0.0 -
Production
Start Date 14-SEP-99 19:06:21
Uptime 0 days 16 hr. 9 min. 20 sec
Trace Level off
Security OFF
SNMP OFF !!!!!!!!!!!
SNMP-Status is OFF.
I am using Oracle 8.1.5.0 and Red Hat 6.0/i386 .
What am i missing?
Thanks all in advance.
null

Yuri (guest) wrote:
: Awgustow (guest) wrote:
: : LSNRCTL> dbsnmp_start
: : LSNRCTL> dbsnmp_status
: : The db subagent is not started.
: : LSNRCTL> status
: : Uptime 0 days
: : Trace Level off
: : Security OFF
: : SNMP OFF
: : Awgustow
: Agent works as follows: it starts up, looks in /etc/oratab for
: databases to manage, tries to establish connection to all of
: them, starts to listen for incoming requests on port 1748. The
: problem can be on any of these steps.
: Try to check with ps -ef | grep dbsnmp if agent processes are
: running (there should be 2 with same name - dbsnmp).
: If yes, try netstat -an | grep 1748 to check if they're
listening
: on TCP port. If they're listening, tracing the agent may help
you
: , though most likely you've hit some bug or config problem -
add
: nmi.trace_level = <level> (0 - off, 16 - maximum)
: nmi.trace_directory = <your directory for trace files>
: nmi.trace_file = <trace file name, e.g. agent
: and then kill agent with killall dbsnmp, start it again and try
: lsnrctl dbsnmp_status. It should generate trace file (but
: startup only trace on 16 level is >50K :-).
: If agent processes are running, but not listening on TCP port,
: most probably agent is not able to connect to one of your
: databases. (BTW, tracing will be of little use in this
situation
: - too cryptic to decipher. You probably will be able to get
: what database is causing problems, by looking at packet dump
: generated at 16th level). Make sure /etc/oratab is OK (lists
only
: valid SID) and that tnsnames.ora has entries for all databases
: mentioned in /etc/oratab.
: On Linux 8.1.5 agent cannot connect to 8.0.5 databases on same
: machine (generally, none of 8.1.5 tools like sqlplus can
connect
: to 8.0.5 on Linux DB). If you have both 8.0.5 and 8.1.5, you
: should comment out 8.0.5 entries in /etc/oratab in order to
start
: the agent. Not very useful, ehe? This is a bug, but no patch is
: yet available.
: If agent processes are not running after dbsnmp_start, again
: tracing should help locate the problem, together with log files
: in $ORACLE_HOME/network/log.
: Write what are your results.
: Yuri
Hi.
The problem was new version of TCL (8.0.4).
Problem solution is use from TCL 7.5.
Regards
Awgustow
Oracle Intelligent Agent
The Oracle Intelligent Agent requires TCL package,
release 7.5.
Follow these instructions to build Oracle
Intelligent Agent
executables.
1. Download the TCL 7.5 sources(tcl7.5.tar.Z)
from:
ftp://ftp.scriptics/com/pub/tcl/tcl7_5/
2. Extract the source in a separate directory and
configure:
$ mkdir tcl
$ cd tcl
$ compress -d tcl7.5.tar.Z
$ tar xvf tcl7.5.tar
$ cd tcl7.5/unix
$ ./configure --enable-gcc
3. Edit the source file tclPosixStr.c:
$ cd ../generic
$ mv tclPosixStr.c tclPosixStr.c.ORIG
cp tclPosixStr.c.ORIG tclPosixStr.c
by commenting the following set of lines:
120 through 122
327 through 329
566 through 568
774 through 776
4. Build the TCL 7.5 library:
$ cd ../unix
$ gmake
5. Install TCL 7.5 in /usr/local, make sure
/usr/local exists and
is writable:
$ su
# gmake install
# exit
6. Set the environment variable ORALE_HOME to the
location where
Oracle8i was installed:
$ export
ORACLE_HOME=<location_where_8i_was_installed>
7. Copy the new TCL library to ORACLE_HOME and
build the
executables:
$ cp libtcl7.5.a $ORACLE_HOME/network/lib
$ cd $ORACLE_HOME/network/lib
$ ln -s libtcl7.5.a libtcl.a
$ gmake -f ins_oemagent.mk agent
null

Agent assgnment in PO release

Similar Messages

Maybe you are looking for