Does ASCP net against approved requisitions

Hi All,
I released a few approved Requistions using ASCP Workbench tool. After that I reran my data collection process & launched ASCP plan to review fresh recommendations. However, I still see ASCP asking me to release new requisitions though I have released in my last run. I haven't changed Forecasts nor have I added new sales order demand. Does ASCP net against approved requisitions ?
Thanks for the help.
Sandeep

Hello Sandeep,
first check if you can see the PO/PR in collected data (collections workbench).
If you can't see it then it's likely a problem with the planning manager not updating MTL_SUPPLY. Check the MPS% columns in MTL_SUPPLY whether these are populated for the PO/PR in question.
If they aren't verify that the planning manager is running fine (MRP - setup - planning manager).
If it's running then and the MPS% columns are null then make a small change to the PO/PR and reapprove. Wait until the planning manager has done at least one cycle. MTL_SUPPLY should be updated then.
Afterwards recollect PO's/PR's
hope it helps
Geert

Similar Messages

Creating user defined pay items in a complex PO which will be created from an Approved requisition

Hi,
We want to create user defined pay items in a complex PO which will be created from an Approved Requisition.
User will select the approved Req. through WebADI and update the pay Items which will be uploaded and a complex PO will be created with user defined Pay Items.
Approach 1:
The API po_interface_s.create_documents is running good but there is one issue with this API as below.
When we add user defined pay items to the po_lines_locations interface table against a line they are also getting added to the complex PO correctly.
But the issue is coming when the API is creating default shipment lines and distribution which we dont want.
Is there any way to stop creating the default pay items and distributions?
We only want the shipments we have entered in the po_lines_locations interface.
We can delete the lines from the PO_line_locations and po_distributions base tables for the default lines but that will be the last option to do delete on base tables.
Approach 2:
We can also do the same with the open PO import interface but it is not linking the complex PO to the approved requisition from which it is created.
Oracle mentioned that this is a future enhancement and this functionality is not available in standard PO import prog.
We are trying for Approach 1 so any suggestions/solutions are appreciated to achieve the requirement.
Regards,
Sanket

UDT cannot be created in sbo-common. You may create new db and work with table in this db (but it will be not UDT, but standard sql table), or create new company db only for this purposes and create UDT there.

Error in Approve Requisitions Fiori App

Hi All,
I am configuring the fiori app "Approve Requisitions", and when clicking the tile in the launchpad, I am getting the error: "Could not start the app due to a configuration problem".
The strange thing is that I have configured the app "Approve Travel Request" without problems, and it's working great. I can approve and reject the travels.
I think that the error I am getting with the "Approve Requisitions" app, is due to the workflow is a custom one, and the approval task is different from the one that the standard workflow for approve requisitions have.
Does anyone have any idea which is the reason of the error?
Thanks in advance,
Emanuel

Finally, the error was due to a lack of configuration.
I was missing the activation of some services in transaction SICF.
Front-End Server: Activate SAP UI5 Application
Component
Technical Name
SAP UI5 Application
MM_PO_APV
Best Regards,
Emanuel

Error Workflow System:error on approving Requisition

Hi,
DB:11.1.0.7
R12.1.1
OS:Linux 86x64 Red Hat Linux
We are receiving Error Workflow System:error on approving Requisition?
Could anyone please share the resolution on it if faced before?
Thanks for your time!
Regards,

Hi
I see the below error in log.
     Abort          Resolved          Retry          Reassign          Request Information
To          SYSADMIN
Sent          20-Apr-2011 13:15:54
ID          5008
     An Error occurred in the following Workflow.
Item Type = POAPPRV
Item Key = 104-108
User Key =9
Error Name = WFENG_ITEM_ATTR
Error Message = 3103: Attribute 'DOCUMENT_ID' does not exist for item 'POAPPRV/104-108'.
Error Stack =
PO_REQAPPROVAL_ACTION.ReserveAutonomous(010)
PO_REQAPPROVAL_ACTION.ReserveDoc(ReserveDoc 020: Doc Header Id = 104)
PO_REQAPPROVAL_ACTION.Reserve_Doc(POAPPRV, 104-108, PO_REQAPPROVAL_ACTION.Reserve_Doc: 01)
Wf_Engine.GetItemAttrNumber(POAPPRV, 104-108, DOCUMENT_ID)
Wf_Engine_Util.Function_Call(PO_REQAPPROVAL_ACTION.RESERVE_DOC, POAPPRV, 104-108, 229749, RUN)
Activity Id = 229749
Activity Label = DOC_RESERVE_PROCESS:RESERVE_DOCUMENT
Result Code = #EXCEPTION
Anybody have any idea on this.
Thanks and Regards,

ME57 / Filter for Approved Requisitions Only

BASIS Guy here doing some fill-in, so short, easy replies are appreciated!
When our purchasing agents go into ME57, they see all requisitions, regardless of whether or not they have been approved. Is there a way to filter this, so that they only see approved requisitions?

Hi Dan,
If you look at the selection screen in the middle of teh screen, you'll see some check box.
One of them is Released requisitions only...
Cheers!

Automatic PO creation from Imported Approved Requisition

Hi,
Is there any setup to allow automatic PO creation from Imported Approved Requisition.
1. Run Requisition Import to import approved Requisition with no workflow fired.
2. Can we kick off automatic PO creation workflow without kicking off Requisition approval workflow?
Any suggestion will be helpful.

Hi,
pl.review the MOS doc.
How to Create and Approve a Standard PO Automatically From an Approved Requisition Sourced to Standard Quotations [ID 308470.1]
HTH
Sanjay

Problem in Approving Requisition Request in MSS UWL

Hi,
I'm facing problem in approving requisition request sent through Manager in MSS UWL.
We have configured standard process HR_MSSRCF_REQUISITION with ISR scenario is SRQ3. Workflow is WS45600028
Case: When I successfully Check & Send Requisition Request form from MSS Recruitment, it is coming in Manager UWL.
But, when i open the workitem for approval it is not coming as a PDF form with Approve Button in the bottom (Standard). Instead, it opening as per the below screen.
Please help to resolve this issue.
Regards

You should be giving the process reference number or workitem ID in transaction hrasr_test_process.
Which release you are on , what is the SP level of component EA-HRGXX?
Further as per note 972322 - HR Administrator: Migration WD4A - the start process application has been migrated to WDA.
Check the UWL XML configuration to see if the config is as below for the approval task...
APPLICATION     ASR_PROCESS_EXECUTE(For EhP4, otherwise application depends on the level of EA-HRGXX )
      DYNPARAM     WI_ID=${item.externalId}
      NAMESPACE     sap
      SYSTEM_ALIAS     <use your system alias>
A sample XML is available with note - 1371626 - UWL Configuration for HR Administrator BP version 1.51.
This appears to me to be a XML configuration issue. Collaborate with your portal and UWL config consultant.
Hope this helps.
Regards,
Sahir.

ERROR: "info.plist does not validate against DTD"

Hi! I got this error if anyone has it solved Please HELP.
I am trying to package a WRT widget using Nokia WRT extension for Adobe Dreamweaver. This is the place for info on the extension: http://www.forum.nokia.com/Tools_Docs_and_Code/Tools/Runtimes/Web_Runtime/
I figure developer from here who use DW to develop mobile content might know the error.
When come to the step of 'Package Nokia WRT Widget' I got this error: info.plist does not validate against DTD
and a page of error info shown like this:
DTD validated at: Wed Jun 17 2009 19:03:00 GMT+0800 (Malay Peninsula Standard Time)
DTD used for validation: http://www.nokia.com/DTDs/plist-1.0.dtd
Line
Column
Message
Explanation
Source
2
95
DTD did not contain element declaration for document type name
3
16
Attribute "version" exists, but can not be used for this element.
3
21
element "plist" undefined. Did you mean "applet" or "strike"?
4
7
element "dict" undefined. Did you mean "strike" or "input"?
5
7
element "key" undefined. Did you mean "strike" or "blockquote"?
6
10
element "string" undefined. Did you mean "strong" or "strike"?
7
7
element "key" undefined. Did you mean "strike" or "blockquote"?
8
10
element "string" undefined. Did you mean "strong" or "strike"?
9
7
element "key" undefined. Did you mean "strike" or "blockquote"?
10
10
element "string" undefined. Did you mean "strong" or "strike"?
11
7
element "key" undefined. Did you mean "strike" or "blockquote"?
12
10
element "string" undefined. Did you mean "strong" or "strike"?
13
7
element "key" undefined. Did you mean "strike" or "blockquote"?
14
9
element "true" undefined. Did you mean "textarea" or "tr"?
Can anyone knows what this means and how i can solve it?
Please help. Thankyou.
note: I am new here and knows that keep asking quesion without giving back is not good but I have a deadline here and wanted to finish the job. I will read some other post and try to help in return when I am able to do so.

Hi pziecina,
Thanks for your reply,
I suspect my problem is the installation or setup of my system or software. as the result i tested is not by doing any scripting at all. All I did is following one of their example exactly (http://www.forum.nokia.com/Tools_Docs_and_Code/Tools/Runtimes/Web_Runtime/Dreamweaver_Exte nsion/QuickStart.xhtml) and package strightaway without modifying the code. because I want to make sure i got the extension install correctly. even so by packaging one of their ready make example already yield this error.

Hi,When I submit the budget for approval, it is approved and base lined when we submit it for approval. It does not go in approval hierarchy. We want it to flow through approval hierarchy.

Hi,When I submit the budget for approval, it is approved and base lined when we submit it for approval. It does not go in approval hierarchy. We want it to flow through approval hierarchy.

Hi Amit,
if I understand correctly, you just need for a particular object a tooltip to be showed.
There is no such functionality hence you used the trick of using a hyperlink, which if clicked generates undesired behavior.
Hyperlinks don't allow themselves to be disabled, therefore if you are using that workaround you must cope with that.
I would suggest to create an Idea at [https://ideas.sap.com] for having in the properties of an object a tooltip, then post the link to the idea here and other users will vote if they like the idea.
Thanks and regards,
Simone

Fiori Approve Requisitions error - unable to start app

Hello Experts,
We have implemented the UIX01EAP (SAPK-10002INUIX01EAP) Fiori component. I have followed the link Approve Requisitions.
I have activated the OData Service GBAPP_PRAPPROVAL, activated the UI5 application MM_PR_APV, assigned the Business Role SAP_MM_BCR_Buyer_X1, Technical Role SAP_MM_TCR_T_X1 in the Front-end Server and the authorization role SAP_MM_PR_APV_APP in the Back-end server to the relevant User ID.
I have also followed the Configuration Tasks given in the above link including maintaining the Workflow Task under Customizing for Materials Management under Purchasing Purchase Requisition Approve Requisitions App Specify Workflow Task IDs for Approve Requisitions App.
After this when I login to the launchpad URL using the approver user, I am able to see the Buyer (MM) group on the home page and also the Approve Requisitions tile with the correct number of pending workitems.
But when I click on the Approve Requisitions tile to open the app, I get an error popup saying Failure - Unable to start App and get the below error in Chrome console.
Can this be due to some missing role/authorization? Or can this be an issue with the Approve Requisitions app itself?
Regards,
Saurabh

Thanks for your response Masa.
I am getting the below response when I run the service /sap/opu/odata/UI2/INTEROP/ResolveLink service:
Regards,
Saurabh

Task.toXML() creates xml that does not validate against WorklistTask.xsd

I am using the worklist API and I am using the toXML() function provided in the Task object to serialize my Task info to XML. It produces XML that looks alot like a "task" Element. But, it does not validate against the WorkflowTask.xsd schema. What is even more odd is that XML looks different than the xml I see when I look at the data in the BPEL Console.
For example, the first XML document below is from Task.toXML. notice that it's first child element is taskId. According to the xsd, that is not valid. The second xml document in this post is from the console. it appears to be valid.
Am I doing something wrong or should I just not expect the worklist api to produce valid xml? (correction: should I not expect the worklist api to xml that validates?)
<task xmlns="http://xmlns.oracle.com/pcbpel/taskservice/task"><taskId>0D7B97F1B138EE21E04017AC2B194357</taskId><title>Payment not posted by payee</title><isGroup>true</isGroup><acquiredBy/><owner>bpeladmin</owner><conclusion/><state>ASSIGNED</state><subState>ASSIGNED</subState><processId>ResearchRequestWorkflow</processId><processName>ResearchRequestWorkflow</processName><versionNumber>1</versionNumber><notm>1</notm><taskGroupId/><taskType>http://blade-11.payveris.com:9700/orabpel/default/ResearchRequestWorkflow/1.0/taskConfigResearchRequest.xml</taskType><identificationKey>PAULA MERRILL, 2069</identificationKey><priority>3</priority><creator>bpeladmin</creator><creationDate>2006-02-23T14:53:08.000-05:00</creationDate><updatedBy>bpeladmin</updatedBy><modifyDate>2006-02-23T14:53:08.000-05:00</modifyDate><flexString1>1140724383057</flexString1><flexString2>PAULA MERRILL</flexString2><flexString3>PAULA MERRILL</flexString3><flexString4>PaymentId3489</flexString4><flexLong1>0</flexLong1><flexLong2>0</flexLong2><flexDouble1>0.0</flexDouble1><flexDouble2>0.0</flexDouble2><processVersion>1.0</processVersion><instanceId>2304</instanceId><domainId>default</domainId><approvers/><hasSubTasks>false</hasSubTasks><processOwner>bpeladmin</processOwner><pattern>SINGLE_APPROVAL</pattern><taskNumber>10240</taskNumber><systemString1/><systemString2/><systemString3/><versionReason>Task Created</versionReason><assigneeGroups>ResearchManager</assigneeGroups><payload confirmation_number="1140724383057" due_date="2006-02-22-05:00" reason="Payment not posted by payee"><requester xmlns="http://www.pp.com/schema"><first>PAULA MERRILL</first><last>PAULA MERRILL</last><tax_id/></requester><payment_type xmlns="http://www.pp.com/schema" number="">insuranceauto</payment_type><record_info xmlns="http://www.pp.com/schema"><creation app="EU" by="282950" date="2006-02-23T14:53:03.056-05:00"/><updation app="EU" by="282950" date="2006-02-23T14:53:03.056-05:00"/></record_info><payment xmlns="http://www.pp.com/schema" id="3489"><bank_info bank_id="2" funds_model="RISK"/><payment_info><confirmation_number>5428</confirmation_number><amount formattedValue="77.00" value="77"/><payment_date>2006-01-06-05:00</payment_date><check_number>5851</check_number><funded>false</funded><merged>false</merged><network id="3" status="ACTIVE" type="C">MOORE</network><alert_on_completion>false</alert_on_completion><alert_number_days_before>0</alert_number_days_before><scheduled_info id="2278"><scheduled_for_date formatted="01/06/2006">2006-01-06-05:00</scheduled_for_date><scheduled_on_date formatted="01/06/2006">2006-01-06-05:00</scheduled_on_date><created_user_id>282950</created_user_id><updated_user_id>0</updated_user_id></scheduled_info></payment_info><payee_info id="24958" relationship_id="6004"><payee_account_number>JUNIT123</payee_account_number><nick_name>blahblah</nick_name><name>complexpayeenameforatest</name><address1>123 main street</address1><address2>c/o anybody</address2><city>Dark Cityrandomizer</city><state>CT</state><zip>06512</zip><network id="3" status="ACTIVE" type="C">MOORE</network></payee_info><customer_info id="2069"><name>PAULA MERRILL</name><customer_account_id>8</customer_account_id><customer_account_number>213</customer_account_number><customer_routing_number>111111111</customer_routing_number><address1>Ernest Hemingway Drive</address1><city>Springfield</city><state>IL</state><zip>62703</zip></customer_info><state_info><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>958</network_batch_id><state_date>2006-10-24-05:00</state_date><state formatted="Check Cashed by Payee" id="2">Cleared</state><trace_number>211170100000003</trace_number></state_info><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>0</money_batch_id><good_funds_batch_id>0</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="6">Created</state><record_info><creation app="BPEL" by="0" date="2006-01-06T11:14:33-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>0</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="6">Created</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T11:14:35-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>0</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="22">Waiting for Decision</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T11:14:36-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="12">Ready for Funding</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:40:01-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="9">Funded</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:40:01-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>0</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="12">Ready for Funding</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:40:03-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>958</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="9">Funded</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:43:56-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>958</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="Mailed" id="11">Payment Sent</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:43:59-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>958</network_batch_id><state_date>2006-10-24-05:00</state_date><state formatted="Check Cashed by Payee" id="2">Cleared</state><trace_number>211170100000003</trace_number><record_info><creation app="EU" by="9999999" date="2006-02-03T12:38:08-05:00"/></record_info></state_history><record_info><creation app="BPEL" by="0" date="2006-01-06T11:14:33-05:00"/><updation app="EU" by="9999999" date="2006-02-03T12:38:08-05:00"/></record_info><research_request>false</research_request></payment></payload></task>
When Im look at the same task in the BPELConsole, the task looks like:
<task>
<title>Payment not posted by payee</title>
<assigneeUsers/>
<assigneeGroups>ResearchManager</assigneeGroups>
<acquiredBy/>
<owner>bpeladmin</owner>
<payload confirmation_number="1140724383057" due_date="2006-02-22-05:00" reason="Payment not posted by payee" >
<requester>
<first>PAULA MERRILL</first>
<last>PAULA MERRILL</last>
<tax_id/>
</requester>
<payment_type number="" >insuranceauto</payment_type>
<record_info>
<creation app="EU" by="282950" date="2006-02-23T14:53:03.056-05:00" />
<updation app="EU" by="282950" date="2006-02-23T14:53:03.056-05:00" />
</record_info>
<payment id="3489" >
<bank_info bank_id="2" funds_model="RISK" />
<payment_info>
<confirmation_number>5428</confirmation_number>
<amount formattedValue="77.00" value="77" />
<payment_date>2006-01-06-05:00</payment_date>
<check_number>5851</check_number>
<funded>false</funded>
<merged>false</merged>
<network id="3" status="ACTIVE" type="C" >MOORE</network>
<alert_on_completion>false</alert_on_completion>
<alert_number_days_before>0</alert_number_days_before>
<scheduled_info id="2278" >
<scheduled_for_date formatted="01/06/2006" >2006-01-06-05:00</scheduled_for_date>
<scheduled_on_date formatted="01/06/2006" >2006-01-06-05:00</scheduled_on_date>
<created_user_id>282950</created_user_id>
<updated_user_id>0</updated_user_id>
</scheduled_info>
</payment_info>
<payee_info id="24958" relationship_id="6004" >
<payee_account_number>JUNIT123</payee_account_number>
<nick_name>blahblah</nick_name>
<name>complexpayeenameforatest</name>
<address1>123 main street</address1>
<address2>c/o anybody</address2>
<city>Dark Cityrandomizer</city>
<state>CT</state>
<zip>06512</zip>
<network id="3" status="ACTIVE" type="C" >MOORE</network>
</payee_info>
<customer_info id="2069" >
<name>PAULA MERRILL</name>
<customer_account_id>8</customer_account_id>
<customer_account_number>213</customer_account_number>
<customer_routing_number>111111111</customer_routing_number>
<address1>Ernest Hemingway Drive</address1>
<city>Springfield</city>
<state>IL</state>
<zip>62703</zip>
</customer_info>
<state_info>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>958</network_batch_id>
<state_date>2006-10-24-05:00</state_date>
<state formatted="Check Cashed by Payee" id="2" >Cleared</state>
<trace_number>211170100000003</trace_number>
</state_info>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>0</money_batch_id>
<good_funds_batch_id>0</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="6" >Created</state>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T11:14:33-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>0</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="6" >Created</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T11:14:35-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>0</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="22" >Waiting for Decision</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T11:14:36-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="12" >Ready for Funding</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:40:01-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="9" >Funded</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:40:01-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>0</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="12" >Ready for Funding</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:40:03-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>958</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="9" >Funded</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:43:56-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>958</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="Mailed" id="11" >Payment Sent</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:43:59-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>958</network_batch_id>
<state_date>2006-10-24-05:00</state_date>
<state formatted="Check Cashed by Payee" id="2" >Cleared</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="EU" by="9999999" date="2006-02-03T12:38:08-05:00" />
</record_info>
</state_history>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T11:14:33-05:00" />
<updation app="EU" by="9999999" date="2006-02-03T12:38:08-05:00" />
</record_info>
<research_request>false</research_request>
</payment>
</payload>
<conclusion/>
<state>ASSIGNED</state>
<subState>ASSIGNED</subState>
<processId>ResearchRequestWorkflow</processId>
<processName>ResearchRequestWorkflow</processName>
<processVersion>1.0</processVersion>
<instanceId>2304</instanceId>
<domainId>default</domainId>
<processOwner>bpeladmin</processOwner>
<taskId>0D7B97F1B138EE21E04017AC2B194357</taskId>
<versionReason>Task Created</versionReason>
<taskGroupId/>
<taskType>http://blade-11.payveris.com:9700/orabpel/default/ResearchRequestWorkflow/1.0/taskConfigResearchRequest.xml</taskType>
<identificationKey>PAULA MERRILL, 2069</identificationKey>
<comments/>
<priority>3</priority>
<creator>bpeladmin</creator>
<updatedBy>bpeladmin</updatedBy>
<hasSubTasks>false</hasSubTasks>
<approvers/>
<pattern>SINGLE_APPROVAL</pattern>
<flexString1>1140724383057</flexString1>
<flexString2>PAULA MERRILL</flexString2>
<flexString3>PAULA MERRILL</flexString3>
<flexString4>PaymentId3489</flexString4>
<flexDouble1/>
<flexDouble2/>
<flexLong1/>
<flexLong2/>
<flexDate1/>
<flexDate2/>
<flexDate3/>
<attachment/>
<taskNumber>10240</taskNumber>
<creationDate>2006-02-23T14:53:08.955-05:00</creationDate>
<modifyDate>2006-02-23T14:53:08.955-05:00</modifyDate>
<isGroup>true</isGroup>
<versionNumber>1</versionNumber>
<notm>1</notm>
<expirationDate/>
<expirationDuration/>
</task>
Message was edited by:
gjacobi

I am using oracle.tip.pc.services.hw.task.impl.Task
that object has a toXML method.
To get that object, I am using the RemoteWorklistServiceClient.getWorlistTaskById method.
A word of caution. Not only am I still having the issue above (I had to hack my own WorkflowTask.xsd to make it validate) but I have noticed that the toXML() method actually returns different results when you think it would not. For example, I have something similar to the following code:
task.toXML()
task.toElement()
task.getPayload()
task.toXML()
The first and last toXML methods produce strings that do not match (it adds some empty elements to the end of the document). Weird. Very Weird.
Greg

SAP Fiori Approve requisition

Hi All
I have recently cofgured SAP Fiori approve requisition (Purchase requisition) using custom workflow. Attached is the error I get when rejecting or approving a purchase requisition.
Please note that the error only Occurs in QA and works fine in Dev

Please check troubleshooting steps @ SAP Fiori - Configuration
http://scn.sap.com/community/mobile/blog/2013/11/13/sap-fiori-ll11--consultants-should-know-about-odata-troubleshooting
Pls put break point in backend ECC and check where the errors are coming from. You can also see /iwfnd/error_log txn in SAP GW to inspect the errors in GW side. On backend you can check in ST22 or put breakpoint and troubleshoot.
First check general troubleshooting using oData in link above and see where the error is coming from.
thanks
Ashish

Approve Requisitions Fiori application issue

Hi,
We have configured a standard "Approve Requisitions" application on the Fiori launchapad.
The application workflow is working fine from Portal end for first two scenarios, but the workflow status doesn't get changed in R/3 for Scenario3 and 4 as explained below.
Scenario1- User clicks on "Approve", the status gets updated at backend properly.
Scenario2- User clicks on "Reject", the status gets updated at backend properly.
Scenario3- User clicks on "Claim", the status at backend doesn't get changed to "Reserved"
Scenario4- User clicks on "Release", the status at backend doesn't get changed to "Released"
Could you please check on this and advise. Thanks in advance.
Regards,
Yuvraj

Hi Yuvraj,
Check the status of work item in transaction SBWP and compare with the below screen,which gives the information in which state Reserve and Claim will work:
Regards,
Trilochan

Sending Pics does that go against Data

Does sending pics with these smart phones count as data everytime you send one? I noticed when sending a pic on task bar it changes to 3g and some colored arrows are displayed next to it showing it's sending

If you are sharing it via an app or email, then yes it goes against a data allowance.
If you are sending it via a text message, then it does not go against a data allowance, but does go against a texting allowance.

Fiori Approve requisition (Header) can't fetch item data

Hi,
I am trying to implement approve requisition (approval by header level).
I can see the number of PR I need to approve in the tile,
But when I click, it is HTTP error, and there is dump at the backend (CL_GBAPP_APV_PR_API)
this is because the item number is 00000.
system is new, notes are implemented.
any idea?

Hi Masayuki,
We have the same issue here and our SP level are the following:
GBAPP002 SP07
UIX01EAP SP04
Error in the frontend: {"error":{"code":"/IWFND/CM_BEC/026","message":{"lang":"pt","value":"Erro RFC: Access via 'NULL' object reference not possible."},"innererror":{"transactionid":"5486B3C840FD1830E10000000A5A0C07","timestamp":"20141210160652.9077510","Error_Resolution":{"SAP_Transaction":"Run transaction /IWFND/ERROR_LOG on SAP NW Gateway hub system and search for entries with the timestamp above for more details","SAP_Note":"See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)"},"errordetails":[]}}}
Dump in the backend:

Does ASCP net against approved requisitions

Similar Messages

Maybe you are looking for