Approval process - 2 users in stage

Dear all,
Question about the approval process.
I have a stage where 2 users can approve, but only one is required
It works fine when they approve document. As soon as one user approve, the originator user receive alert and can create the document.
However when they want not to approve , the system ask for both user to not approve the request before changing the status of the request from pending to rejected and sending the alert to the user.
If only one say no, the status remains pending, and an action of the second user is required to make the system change the status.
Why to approve, only one is required, and to reject, both are required? is there a way to have the same process in approval than in reject ?
Thank you
Sébastien

Dear Sébastien,
This is in the initial design of this process. We can do nothing about it.
You may post a DRQ here http://forums.sdn.sap.com/forum.jspa?forumID=265 or on Idea Place for this request.
Thanks,
Gordon

Similar Messages

Approval Process by using Sales Stage

Hello all,
I have a requirement and my question iis there any process in OCOD for approval process? i mean if my Sales stage is Initial somebody needs to approve and it keep on moving to Closed/Won or Closed loss by the approval of manager. The highest is the Manager level and the lowest is Sales rep, in between lot of people are involved like BDM, AGM and so on. Could you please suggest on this.
Thanks
Subbu

Bob,
The documents relates to the Service Request object.
We need the same to be done for Opportunities.
The process may include workflow notifications.
I see a couple of fields related to Approver and Approval Status but have not looked into how the same works.
Thanks and Regards.,
Akesh

Question related to Approval Process

Hi All,
I am a new bie to OIM.
I have created a two level approval process.The user will have to select the first level approver while raising the request. We have a approver only field in the DataSet so that the first level approver can select the next level approver.The first level Approver logs in and selects the second level approver and then completes the first level approval.
Once the second level approver approves it the request will be completed.
I have used some common java code by creating a jar(to get the request details) and placing it in the composite instead of writing all the java code in "java embeded code".
The two level approval process was working fine , but I have added loggers in the java code and now when I test the composite both the approvals are executed at a single time.
The first level approval is getting completed by its own with out selecting the second level approver and there is an error in the second level approval. I have tried chaging the Priority of the approval policies also , but still the same issue.
Please help me in resolving this issue. This is very urgent.
Thanks in advance for your help.
Thanks,
PT

Mark the approver only field as required.
find the below link for more detail:
Approval process in OIM 11g
--nayan

Approval Process to Apply to Updated Documents

Hi,
My customer has a problem with certain Sales Orders not going through the Approval Process. Users are circumnavigating the Approval Process in a sneaky way.
Let us say that we have a Sales Order with a value of £1000. On hitting Add, SAP asks the user to submit the Sales Order for approval.
If the user then clicks Cancel they return to the Sales Order entry form. If he then changes the Order value to a figure which does not fire the Approval Process (for example £0) the system allows the Order to be Added.
If the user then amends the Order back to the original £1000, he can Update the Order without firing the Approval Process. I found out how this was happening by looking at the History of a Sales Order and have recreated the issue locally.
I have found SAP Note Number 904373 - Approval Procedure not working on marketing documents. This note states that the above scenario is system behaviour.
Can this be changed so Updated documents will fire the approval process?
Thanks
Greig

Hi All,
Can we use the Request API to create the request (and then Approval) for other than ADD (object type like Disable, Enable etc) of a user like below
long lRequestKey;
long UserKey=1;
long ObjectKey=201; //testro1
HashMap reqMap = new HashMap();
reqMap.put("Requests.Target Type", "U");
reqMap.put("Requests.Object Request Type", "Disable");
reqMap.put("Requests.Type", "U");
lRequestKey = reqObj.createRequest(reqMap);
System.out.println("Created request and got key :" + lRequestKey);
reqObj.addRequestUser(lRequestKey, UserKey);
System.out.println("Added the request user");
reqObj.addRequestObject(lRequestKey, ObjectKey); // I am not sure if this part is right but without this it is giving me the error.
System.out.println("Added the request object");
reqObj.completeRequestCreation(lRequestKey);
System.out.println(Completed and submitted the request");
I gave it a try but the Resource detail is not getting populated in the request due to which request hang up in "Request Initialized" state. I tried by passing the Process Instance Key also but no luck.
Any chance if anyone crack it before. Please tell me. Thanks

Restart approval process through Thor api in oim 9i

Hi,
   I am using oim 9i.
Scenario:
   For a resource object i have a object form and a child form along with it.
   The user fills the object form along with the child form and submits for approval.
   During the approval process the user(requester) is able to edit the child form even though approval is started and approved by some stakeholders.
   Can we restart the approval process if any changes is made on child form?
   Also i have added entity on POST-Insert on child form.I come to know whenever there is change on the form.
   But on the change in the child form i want to trigger approval back to the 1st approver(restart the approval process).
Could you help me with the api for restarting approval process or any url link which would help.
Regards,
Nirav

okk...thanks for the replies..
I am a newbie and wanted to know how to call this process task adapter as i currently have entity adapter on POST-insert on child form which identifies that there is some update..So does that means through entity adapter i need to call the process task of a approval process?
Also is it possible to get the value of user who updated the child form as soon as it is updated?
On post-insert adapter when i try to get the value of "formupdate by" whenever it is triggered it gives me the previous "update by" and not the current "update by" value?
Does the database get updated later or am i doin somethng wrong,beacuse if it is a post-insert i should get values of "latest update by" on the form?

Approval Process Completion Conditions for different stages

Hi
I have an approval process with 2 stages. The first stage has multiple approvers running in parallel. Only one user needs to approve for it to progress.
In the second stage it needs to be approved by all users.
I can set the completion conditions to complete after one person approves but this will also set it for the second stage.
Is it possible to have different completion conditions for each stage or im i better just having a second approval proccess action?
Hope that makes sense and thanks

Hi,
According to your post, what do you mean “you have an approval process with 2 stages”?
In SharePoint 2013 workflow, a workflow can add many stages into it, and a stage can add many same or different actions into it.
So, each separate action you added in a workflow must be in a stage, will not be in two stages.
If you want to make the workflow complete when one user approved the task process in a stage, I recommend that you can directly set the “Completion Criteria” option to “Wait for specific response” as below in the “Task Option” of the “Start a Task Process”
action.
If you want to make the workflow go to the second task process in the second stage when one user approved the task process in the first stage, I recommend that you can set the “Completion Criteria” option to “Wait for specific response” as below in the “Task
Option” of the “Start a Task Process” action in the first stage.
Then, you can set the “Completion Criteria” option to “Wait for all response” as below in the “Task Option” of the “Start a Task Process” action in the second stage.
And, you can go to “Start Options” to check “Start workflow automatically when an item is created”, publish the workflow and test whether it works in your environment.
The workflow is shown as below:
Best Regards,
Yumi Fu

Approval process in update user workflow

Hi
I have read in the document Administrative Guide that by default, the approval process is set only for user creation. and the same does not work for update and delete operations on user, unless we customize the code.
Does any one of you have any idea as to what customization needs to be done for successful approval process for updates also. I have set approvers for resources.
Thanks
Bushra

1. backup the existing Update user workflow as an xml file
2. Copy paste the same in the BPE.
3. Save the copy as a new object with a different name.
4. Edit the new workflow as follows:
4.1 Create new activity
4.2 In the new activity, add a variable with some name
4.3 create a new action, and let that action be a subprocess. For that subprocess, browse and choose 'Approval' as the action.
4.4 Add a argument as name=approvalForm and value=<name of approval form>
4.5 Include argument user=$(user), etc. (Check the original approval workflow to see what the names of the arguments are)
4.6 For return to=name of the variable declared, from=approved
4.7 Add a 'isTrue' condition for the variable declared.
5. Make the appropriate transitions, and ur ready to go.
Let me know if this helps. I can post some skeleton code tomorrow. I need to work on it. Drop a line at [email protected]

Approval process to disable user

Hi,
I need to have an approval process before disabling the user and the approver not being user's manager.I am not quite sure as how to implement it. Please guide.
Thanks

Hi All,
Can we use the Request API to create the request (and then Approval) for other than ADD (object type like Disable, Enable etc) of a user like below
long lRequestKey;
long UserKey=1;
long ObjectKey=201; //testro1
HashMap reqMap = new HashMap();
reqMap.put("Requests.Target Type", "U");
reqMap.put("Requests.Object Request Type", "Disable");
reqMap.put("Requests.Type", "U");
lRequestKey = reqObj.createRequest(reqMap);
System.out.println("Created request and got key :" + lRequestKey);
reqObj.addRequestUser(lRequestKey, UserKey);
System.out.println("Added the request user");
reqObj.addRequestObject(lRequestKey, ObjectKey); // I am not sure if this part is right but without this it is giving me the error.
System.out.println("Added the request object");
reqObj.completeRequestCreation(lRequestKey);
System.out.println(Completed and submitted the request");
I gave it a try but the Resource detail is not getting populated in the request due to which request hang up in "Request Initialized" state. I tried by passing the Process Instance Key also but no luck.
Any chance if anyone crack it before. Please tell me. Thanks

Approval process is skipping with update user

Hi,
I have approval process before updating a user (the oganization in which the user exists has approvers assigned to it). I am using the default Lighthouse Approval subprocess.
But when i try to update a user, the workflow is going inside the "Lighthouse Approval" subprocess but the "getApprovals" activity (in the approval subprocess) is returning null. So the approval workitem is not being created.
Can anyone help me out in this? Am i missing anything here.
Thanks

I belive the approvals only works for when someone is assigned the role, not when they are updated.
Dana Reed
Senior Identity Management Architect
AegisUSA
Denver, Co

Approved invoices can not be edited - Approval process

Hi Experts -
I have recently raised an incident with SAP about Approval process - the complete message and support reply is as follows - but i believe we need a change in the approval process - if the approval required is only one but you have defined two people (Either or OR) in the approver list - the system should allow the document to be edited if one of the approvers reject it.
please let me know and i believe we need a change in design - unless otherwise a solid reason is given to justify the existing design
10.07.2009 10:32 Description (English) by SRS Manian
     We have created approval procedure for all the invoices which are entered into the system., The
'Accts' user enters the invoice into the system - the invoice comes for approval to 'Manager' user.
When the Manager opens the invoice via Alert window - he/she wants to modify certain information
(lines as well as Sales person) and approve it.
The invoice which gets opened from the alert window - does not allow the user 'Manager' to modify at
all. All the information on the invoice are greyed out.
The system should allow the user 'Manager' to modify the information. Since the manager has full
authorization to the system.
10.07.2009 10:35 Info to Reporter by SAP
     Dear Partner/Customer,
We have received your inquiry and are currently processing it.
You will be contacted with a solution or an update as soon as possible.
For further details regarding the phase your message is in at the
moment please refer to:
http://service.sap.com/%7Esapidb/011000358700000575782007E
Kind regards,
SAP Business One Product Support
10.07.2009 10:59 Reply to Reporter by SAP
     Dear Manian,
Thank you for contacting us.
When the originator sends the document for manager's approval, note that the at that stage, the document is still in the 'Approval Process'. This is because the system is waiting for the 'Manager' to 'Approve or Reject' the document. Hence, looking at the Document, it is still in 'Draft - Pending' Status.
When the document is in 'Draft-Pending' Status, the document is not available for editing, because the system considers that it is still in the waiting process. In your case, the manager cannot edit t he document.
To amend the document, an action is required from the approver either to reject it first. Once rejected, it can be amended and re-sent for approval.
I have checked our knowledge base and noted that there is an article which describes the approval process. Please refer to the Expert on Phone Wiki Article (March 2009) with title: Why a draft documen t in an approval process cannot be modified by the originator?
The link will provide the explanation:
https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=88735894
I have also attached Notes 1321234 and 1111431 for your reference.
Best regards,
Lorna Real
Support Consultant
Product Support for SAP Business One
SAP Ireland
10.07.2009 11:59 Reply to Support Center by SRS Manian
     Thanks for the reply. The scenario is when the Manager receives the
document for approval, he wanted to edit and add it. Your reply (and
documentations) states that it needs to be rejected first before it is
available for editing. When it is gets rejected - the person who
orignated the document gets an alert and he can edit it. Here the
Manager must get an alert so that he can edit the Rejected document.
When the 'manager' rejects the document, and goes back to the alert
window to open the document - it is still greyed out !!
How does the 'manager' reject the document and edits it ?
regards
Manian
10.07.2009 12:11 Reply to Reporter by SAP
     Dear Manian,
If after the Manager rejects it and still the document is not editable (greyed out), it means that the document may still be in the 'Approval Process'. When it is greyed out, what is the status of the document in the header? Does it say 'Rejected' or 'Pending'?
If it is still in 'Pending' mode, please verify the number of 'Approvers' set in the 'Stages' tab of the 'Approval Template - Setup' window. If there is more than one user listed as 'Approver', and o nly 1 approval is required, the system provides an opportunity to other 'Approvers' to approve or reject the document. If in your case, the number of approvers is 2, and manager 'rejected' it, the sys tem still keeps the document in Pending status as it waits for another approver's decision to reject or approve it.
Also, verify the number of 'Approvals' required. If the number of 'Approvers' who have not rendered their decision is greater than or equal to the 'Approvals' required (e.g. approvers - 2, required ap provals - 2) the system keeps the document within the approval process. This is to allow the other 'Approvers' to decide on the document.
I hope this clarifies the behaviour. If you can provide us a step by step screenshot of the issue, this may help us to provide a more accurate response.
Best regards,
Lorna Real
Support Consultant
Product Support for SAP Business One
SAP Ireland
10.07.2009 12:28 Reply to Support Center by SRS Manian
     Hi:
The status of the document in the Header says 'Pending' and the status
below the document number says 'Suspended' - it is not showing as 'Draft'
Regards
Manian
10.07.2009 12:42 Call to Customer / Partner by SAP
     Performed on: 10.07.2009 10:41:59 (UK)
Contact person: SRS Manian
Status of discussion: Customer not reached
Subject:
Called the partner but currently engaged on another line.
Would like to hold a webex.
10.07.2009 12:42 Reply to Reporter by SAP
     Dear Manian,
I'm trying to call you but there was no response on your mobile.
When the header says 'Pending', then it means the document is still within the approval process. Please check the Approval Template and see the number of approvers and the number of approvals require d.
The number of approvals and approvers may be greater than 1. In this case, the system waits for other approvers to approve or reject the document. Once all the approvers have rejected the document, th en the document will be released and available for editing.
Best regards,
Lorna Real
Support Consultant
Product Support for SAP Business One
SAP Ireland
10.07.2009 18:11 Reply to Support Center by SRS Manian
     Hi:
Thanks for the reply - i tried this and found out the following:
1 - In the approval templates - we had mentioned number of approvals
required as '1'.
2 - in the number of approvers - we had mentioned two users
Though the template requires only one approvals (Either or OR) the system
expects both of them to approve or reject -
Can u please let me why is this behaving like this - or is this is the
way it is designed ? - if this is the way it is designed - i beleive it
is wrong - weneed to give a solution to the customer
regards
Manian
11.07.2009 05:52 Reply to Reporter by SAP
     Dear Manian,
Thank you for the information. The behaviour is a current system definition documented as per Note 1321234. I have attached the said Note for your reference. When only 1 approval is required and there are 2 or more persons are allowed to approve the document, the document does not get automatically rejected when 1 person 'rejects' it. The system waits for other approvers to render their decision b ecause a person may still approve or reject the document.
The design is not an application error. If you would like to change this design, please post your requirement in our SAP Business One Product Development Collaboration
forum. You can find the forum in this link:
/community [original link is broken]
The forum is beingmoderated by members of the Solution Management team specialized in certain areas, according to the folder you are in. Partners can impact the design of specific features by posting suggestions and feedback at this forum. Kindly refer to Note 1028874 which describes more on the above process.
As the request will be handled through another process, we kindly request that this support message be closed.
Thank you for your understanding.
Best regards,
Lorna Real
Support Consultant
SAP Product Support for SAP Business One
SAP Ireland
11.07.2009 09:02 Reply to Support Center by SRS Manian
     Hi Thanks for the reply - however, the solution given doesnot address the
problem we are beingfaced with our client
Is there a Development Request we can raise so that this problem is
addressed in future
I am going ahead and confirming this Message though
regards
Manian
11.07.2009 10:04 Reply to Reporter by SAP
     Dear Manian,
Thanks for the information. I understand the customer's requirement. As previously mentioned, please log a development request in this link:
/community [original link is broken] This is from Note 1028874.
Unfortunately,we at the support centre does not have access to the list of development requests. Hence, kindly follow the process in Note 1028874.
I'm sending the message back to your side for confirmation.
Best regards,
Lorna Real
Support Consultant
Product Support for SAP Business One
SAP Ireland
SAP Notes
Number     Short text
0001035200
Issue can be solved via existing documentation
0001111431
Deleting rejected draft documents.
0001167635
Maintenance Policy (L)
0001321234
Status of a document rejected within the Approval Process.

Hi Gordon - thanks for the reply - i am sorry i never realized that the message i raised could be messed up like this - the following is a clear message with some paragraphs:
Hi Experts - I have recently raised an incident with SAP about Approval process - the complete message and support reply is as follows - but i believe we need a change in the approval process - if the approval required is only one but you have defined two people (Either or OR) in the approver list - the system should allow the document to be edited if one of the approvers reject it. please let me know and i believe we need a change in design - unless otherwise a solid reason is given to justify the existing design
SRS Manian We have created approval procedure for all the invoices which are entered into the system., The 'Accts' user enters the invoice into the system - the invoice comes for approval to 'Manager' user. When the Manager opens the invoice via Alert window - he/she wants to modify certain information (lines as well as Sales person) and approve it. The invoice which gets opened from the alert window - does not allow the user 'Manager' to modify at all. All the information on the invoice are greyed out. The system should allow the user 'Manager' to modify the information. Since the manager has full authorization to the system.
Reply to Reporter by SAP Dear Manian,
Thank you for contacting us. When the originator sends the document for manager's approval, note that the at that stage, the document is still in the 'Approval Process'. This is because the system is waiting for the 'Manager' to 'Approve or Reject' the document. Hence, looking at the Document, it is still in 'Draft - Pending' Status. When the document is in 'Draft-Pending' Status, the document is not available for editing, because the system considers that it is still in the waiting process. In your case, the manager cannot edit t he document. To amend the document, an action is required from the approver either to reject it first. Once rejected, it can be amended and re-sent for approval. I have checked our knowledge base and noted that there is an article which describes the approval process. Please refer to the Expert on Phone Wiki Article (March 2009) with title: Why a draft documen t in an approval process cannot be modified by the originator? The link will provide the explanation:
https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=88735894
I have also attached Notes 1321234 and 1111431 for your reference. Best regards, Lorna Real Support Consultant Product Support for SAP Business One SAP Ireland 10.07.2009 11:59
Reply to Support Center by SRS Manian
Thanks for the reply.
The scenario is when the Manager receives the document for approval, he wanted to edit and add it. Your reply (and documentations) states that it needs to be rejected first before it is available for editing. When it is gets rejected - the person who orignated the document gets an alert and he can edit it. Here the Manager must get an alert so that he can edit the Rejected document. When the 'manager' rejects the document, and goes back to the alert window to open the document - it is still greyed out !! How does the 'manager' reject the document and edits it ? regards Manian
Reply to Reporter by SAP
Dear Manian, If after the Manager rejects it and still the document is not editable (greyed out), it means that the document may still be in the 'Approval Process'. When it is greyed out, what is the status of the document in the header? Does it say 'Rejected' or 'Pending'? If it is still in 'Pending' mode, please verify the number of 'Approvers' set in the 'Stages' tab of the 'Approval Template - Setup' window. If there is more than one user listed as 'Approver', and o nly 1 approval is required, the system provides an opportunity to other 'Approvers' to approve or reject the document. If in your case, the number of approvers is 2, and manager 'rejected' it, the sys tem still keeps the document in Pending status as it waits for another approver's decision to reject or approve it. Also, verify the number of 'Approvals' required. If the number of 'Approvers' who have not rendered their decision is greater than or equal to the 'Approvals' required (e.g. approvers - 2, required ap provals - 2) the system keeps the document within the approval process. This is to allow the other 'Approvers' to decide on the document. I hope this clarifies the behaviour. If you can provide us a step by step screenshot of the issue, this may help us to provide a more accurate response.
Best regards,
Lorna Real Support Consultant Product Support for SAP Business One SAP Ireland
Reply to Support Center by SRS Manian
Hi: The status of the document in the Header says 'Pending' and the status below the document number says 'Suspended' - it is not showing as 'Draft'
Regards
Manian 10.07.2009 12:42
Reply to Reporter by SAP
Dear Manian,
I'm trying to call you but there was no response on your mobile. When the header says 'Pending', then it means the document is still within the approval process. Please check the Approval Template and see the number of approvers and the number of approvals require d. The number of approvals and approvers may be greater than 1. In this case, the system waits for other approvers to approve or reject the document. Once all the approvers have rejected the document, th en the document will be released and available for editing.
Best regards,
Lorna Real Support Consultant Product Support for SAP Business One SAP Ireland
Reply to Support Center by SRS Manian
Hi: Thanks for the reply - i tried this and found out the following: 1 - In the approval templates - we had mentioned number of approvals required as '1'. 2 - in the number of approvers - we had mentioned two users Though the template requires only one approvals (Either or OR) the system expects both of them to approve or reject - Can u please let me why is this behaving like this - or is this is the way it is designed ? - if this is the way it is designed - i beleive it is wrong - weneed to give a solution to the customer
regards
Manian
Reply to Reporter by SAP
Dear Manian,
Thank you for the information. The behaviour is a current system definition documented as per Note 1321234. I have attached the said Note for your reference. When only 1 approval is required and there are 2 or more persons are allowed to approve the document, the document does not get automatically rejected when 1 person 'rejects' it. The system waits for other approvers to render their decision because a person may still approve or reject the document.
The design is not an application error. If you would like to change this design, please post your requirement in our SAP Business One Product Development Collaboration forum.
You can find the forum in this link:
/community [original link is broken]
The forum is being moderated by members of the Solution Management team specialized in certain areas, according to the folder you are in. Partners can impact the design of specific features by posting suggestions and feedback at this forum.
Kindly refer to Note 1028874 which describes more on the above process.
As the request will be handled through another process, we kindly request that this support message be closed. Thank you for your understanding.
Best regards,
Lorna Real Support Consultant SAP Product Support for SAP Business One SAP Ireland
Reply to Support Center by SRS Manian
Hi Thanks for the reply - however, the solution given does not address the problem we are being faced with our client Is there a Development Request we can raise so that this problem is addressed in future I am going ahead and confirming this Message though
regards
Manian
Reply to Reporter by SAP Dear Manian,
Thanks for the information. I understand the customer's requirement. As previously mentioned, please log a development request in this link:
/community [original link is broken]
This is from Note 1028874.
Unfortunately, we at the support centre does not have access to the list of development requests. Hence, kindly follow the process in Note 1028874. I'm sending the message back to your side for confirmation.
Best regards,
Lorna Real Support Consultant Product Support for SAP Business One SAP Ireland

How to use a pwa group in CREATE A TASK PROCESS in SPD 2013 for project server workflow approval process

I am working on a Project Server 2013 workflow. I am creating this using Sharepoint Designer 2013. In this workflow I am using approval process at one stage. I have created a security group SalesManagers in PWA. I want to use this group for workflow approval
process. I want all users of this group get approval tasks.
For this I used START A TASK PROCESS activity in the SP Designer. I clicked on
this user and created task process. But here I could not find SalesManager group which I created in PWA. I was only able to find the users. I can also see
Administrators for PWA . But couldnot find SalesManager or any other security group created in pwa.
Can anyone suggest how I can get the security group created in pwa.

NBDevelopment,
I believe SPD only recognizes the SharePoint Groups and not the project server security groups.
The Administrators for PWA, and few other groups like Project Managers for PWA etc., are synced SharePoint Groups with the security groups, which is why they show up in SPD.
You could create a SharePoint Group for the Sales Managers group and use that in SPD.
Cheers,
Prasanna Adavi, Project MVP
Blog:
Podcast:
Twitter:
LinkedIn:

925685 - Approval process is not triggered after documents are added

Hi there,
I was wondering if anyone found already a solution for the following problem.
According to SAP Note: 925685 - Approval process is not triggered after documents are added.
Within our SAP application, we want to approve purchase orders for departments based upon the document total.
I was very astonished that employees are able to add a PO which will not trigger an approval stage and after the document is added, they have the possibility to change the document and at the update moment no approval will be started even if the document meets the approval requirements.
Therefore I really want the flexibility to give users the possibility to change their PO.
Meanwhile, documents which are added under approval, are also locked for changes, although this is another question it is also pretty annoying!
I hope anyone has already found a method or work around for the stated problems above.
(We are using SAP 8.8 PL 20)
Thanks in advance.
Kind regards,
Marcel

Hi Kambadasan,
Thank you for your reply
I'm sorry but I know how the approval templates work and they are configured correctly, however as SAP also mentioned in their own Note, this is due to the lack of SBO that SAP has such behaviour.
Hi Gordon,
Thanks for your reply.
Unfortunately I have not found the post you mentioned...
I will post my issue alson on the topic you mentioned.
Hopefully they found a solution or maybe version 8.81 will solve the problem.
Thanks a lot!!
Kind regards,
Marcel

Approval process (Release strategy of scheduling agreement)

Hi,
Recently we are trying to implement the approval process of scheduling agreements.
Client requirement is when ever there is a change in price irrespective of the following
1. Retrospective price change in any line item
2. Current price change in any line item
3. Future price updation in SA in any line item
4. New addition of line item
the system should trigger the release process (i.e. Approval process).
Our idea is to design the approval process based on document type and net value of SA. Based on which trigger should happened. But when we test it we find the following issues.
1. Trigger is not happening for future date price change or price for new period as the net value of SA is based on validity time.
Becuase the net value change will happen only on that onwards..
Also we are not using any cumulative pallned values in agreements.
Any can suggest the best solution to over come this..or Any user exit is avaliable to handle this issue.
regards,
K.Sundaresan.

Below are the (changed) item fields :
Purchasing Document Item Change Date AEDAT
Item Delivery Date EINDT
Schedule Line is "Fixed "FIXKZ
Below are the (changed) header fields :
Release Indicator: Purchasing Document FRGKE
Release status FRGZU
Purchasing document processing state PROCSTAT
Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on document type level ,I am also confused on this .
Please assist on this

OIM: Error while deploying Custom Approval Process for Self-Register

While deploying the Custom Approval Process for Self-Register, i am getting the following error in scac.log file
Nov 16, 2011 2:48:58 PM oracle.fabric.common.wsdl.SchemaManager isIncrementalBuildSupported
INFO: XMLSchema incremental build enabled.
Nov 16, 2011 2:48:58 PM com.collaxa.cube.CubeLogger info
INFO: validating "ApprovalProcess.bpel" ...
oracle.jrf.UnknownPlatformException: JRF is unable to determine the current application server platform.
     at oracle.jrf.ServerPlatformSupportFactory.getInstance(ServerPlatformSupportFactory.java:79)
     at oracle.integration.platform.blocks.WLSPlatformConfigurationProvider.<clinit>(WLSPlatformConfigurationProvider.java:44)
     at oracle.integration.platform.blocks.FabricConfigManager.<clinit>(FabricConfigManager.java:155)
     at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXpathFunctions(FabricXPathFunctionResolver.java:271)
     at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXPathConfigFile(FabricXPathFunctionResolver.java:153)
     at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.init(FabricXPathFunctionResolver.java:51)
     at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.loadFabricXpathFunctions(BPELXPathFunctionNameResolver.java:57)
     at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<init>(BPELXPathFunctionNameResolver.java:48)
     at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<clinit>(BPELXPathFunctionNameResolver.java:44)
     at com.collaxa.cube.lang.compiler.bpel.XPathExprValidatorVisitor.<init>(XPathExprValidatorVisitor.java:122)
     at com.collaxa.cube.lang.compiler.bpel.AssignValidator.<init>(AssignValidator.java:89)
     at com.collaxa.cube.lang.compiler.bpel.BpelParser.<init>(BpelParser.java:452)
     at com.collaxa.cube.lang.compiler.bpel.BPELValidator.validate(BPELValidator.java:60)
     at com.collaxa.cube.lang.compiler.BPEL1Processor.validate(BPEL1Processor.java:329)
     at com.collaxa.cube.lang.compiler.BPEL1Processor.process(BPEL1Processor.java:153)
     at com.collaxa.cube.lang.compiler.CubeParserHelper.compile(CubeParserHelper.java:47)
     at oracle.fabric.bpel.bpelc.BPELComponentValidator.validate(BPELComponentValidator.java:40)
     at oracle.soa.scac.ValidateComposite.validateComponentTypeServicesReferences(ValidateComposite.java:1117)
     at oracle.soa.scac.ValidateComposite.doValidation(ValidateComposite.java:500)
     at oracle.soa.scac.ValidateComposite.run(ValidateComposite.java:150)
     at oracle.soa.scac.ValidateComposite.main(ValidateComposite.java:135)
Nov 16, 2011 2:49:00 PM CubeProcessGenerator compile
WARNING: classpath is: D:\JDev11g\Middleware\jdeveloper\jdev\extensions\oracle.sca.modeler.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;D:\JDev11g\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.mediator_11.1.1\mediator_client.jar;D:\JDev11g\Middleware\oracle_common\modules\oracle.mds_11.1.1\mdsrt.jar;D:\OIMPS1\Middleware\oracle_common\modules\oracle.jps_11.1.1\jps-manifest.jar;;D:\OIMPS1\Middleware\Oracle_IDM1\server\workflows\new-workflow\process-template\SelfRegistrationApprovalApp\SelfRegistrationApproval\SCA-INF\classes;D:\OIMPS1\Middleware\Oracle_IDM1\server\workflows\new-workflow\process-template\SelfRegistrationApprovalApp\SelfRegistrationApproval\SCA-INF\classes;D:\OIMPS1\Middleware\Oracle_IDM1\server\workflows\new-workflow\process-template\SelfRegistrationApprovalApp\SelfRegistrationApproval\SCA-INF\gen-classes;D:\OIMPS1\Middleware\Oracle_IDM1\server\workflows\new-workflow\process-template\SelfRegistrationApprovalApp\SelfRegistrationApproval\SCA-INF\lib\oimclient.jar;D:\JDev11g\Middleware\oracle_common\modules\commonj.sdo_2.1.0.jar;D:\JDev11g\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;D:\JDev11g\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpel1-1-xbeans.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-common.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpel_coherence_config.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-exts.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\thirdparty.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpm-analytics.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-thirdparty.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\wsif-binding.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-validator.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\monitor-rt-xbean.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\oracle.soa.bpmn.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\user-patch.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.thirdparty.jar;D:\JDev11g\Middleware\jdeveloper\uddi\lib\oracle.soa.uddi.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\bpm-infra.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\testfwk-xbeans.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-ext.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-infra-scheduler.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\xmlunit-1.1.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-infra-tools.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-xpath-exts.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\oracle-soa-client-api.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.wls.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-client.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime-ext-was.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime-ext-wls.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\oracle.soa.fabric.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.workflow_11.1.1\bpm-services.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.ext_11.1.1\classes
In scac_out.xml file following is the error message
<Fault>
<severity>error</severity>
<loc>/ns:composite</loc>
<line/>
<col/>
<file/>
<msg>
<![CDATA[SCAC-50012]]>
</msg>
</Fault>

Hi,
I have run into the same problem with SOA 11.1.1.5 version. In my case after fixing the following two errors it seems to work fine.
If you have followed the guide, there must be some errors:
First the java code if copied then contains an extra enter value:
Instead of:
"try {
System.out.println("Prototype for invoking an OIM API from a SOA Composite");
System.out.println("RTM Usecase: Self Registration Approval by Organization
Administrator");"
Use the following:
"try {
System.out.println("Prototype for invoking an OIM API from a SOA Composite");
System.out.println("RTM Usecase: Self Registration Approval by Organization Administrator");"
The other error is that you should not use <BEAHOME>/oracle_common/modules/oracle.jps_11.1.1/jps-manifest.jar, but the <BEAHOME>/oracle_common/modules/oracle.jps_11.1.1/jps-api.jar in jdeveloper. After these the deployment to the application server works fine for me.

ITEM tab in the Approval Process overview IN srm 7.0 AND EP 7.1

Hi Friends,
I am working in SRM 7.0 with EP 7.1..
1 . I have to remove 'ITEM' tab in the approval process overview screen which is apprearing in Portal. approval process overview screen will be appeared when 'Display / Edit Agents' Button in the Header level of the Shopping cart screen.
2 . Remove Approval Process overview tab in the detail screen of the shopping cart.
Any idea
John.

Hi Masayuki,
Thank you for your quik reply.
can you please explain little bit more on this..
2. tab
Easy way is right click, User Setting -> Hide Tab. or User Setting -> More.. Remove display tab
I tried this option but this is each user setting , Can we make this centerlized?
or
Go to SE80 Webdynpro and change the visible property.
I know the webdynpro for this tab but to change this visible property do I need have access key( Core modification ) or any other way to do such as enhancement spot?
John.
Edited by: John peter on Jul 10, 2009 11:16 AM

Approval process - 2 users in stage

Similar Messages

Maybe you are looking for