on 07-17-2014 7:39 AM
Hello Friends,
We are in NW Gateway 7.4 and when I logged as User and trying to access Approve Purchase Requisition, I am getting error "Unable to start app". When I looked at error log and in Network element found the below errors. Am I missing something and what I don't understand is the error in Gateway log shows this
1. "No service found for namespace , name sra001_pcapproval, version 0001"
2. Back-end error occurred "T100 Info:GBAPP_APV_MSG-013"
Network Element error:
Gateway error:
Regards,
S.Srikanth
Tags edited by: Michael Appleby
Hi Srikanth,
You have mixed up 3 scenarios.
You tested "Approve Purchase Requisition" but the error message is about "Approve Purchase Contract" and screenshots are about "Approve Purchase Order".
Please follow the troubleshooting steps.
SAP Fiori LL11 - Consultants should know about OData troubleshooting
Regards, Masa
SAP Customer Experience Group - CEG
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Masa,
When I gone through the error log for Approve Purchase Requisition, I am getting error "Backend error occured. T100 Info:GBAPP_APV_MSG-013".
When, I checked with URL http://xxx:8000/sap/opu/odata/sap/gbapp_prapproval;mo/LaunchPageCollection from network element in NW Gateway client, getting below error
<?xml version="1.0" encoding="utf-8" ?>
</Error_Resolution>
But, when I checked in NW gateway client with the below URL, I am able to see the PR for approval in user inbox.
http://xxx/sap/opu/odata/sap/GBAPP_PRAPPROVAL/WorkflowTaskCollection?$filter=TaskType eq'TS00007986'
Regards,
Srikanth
Hi Masa,
Please find below the odata URL for PR Approval and we dont see any error.
http://xxxx:8000/sap/opu/odata/sap/GBAPP_PRAPPROVAL/?$format=xml
But, when we check it in LPD_CUST, we see different URL for PR approval.
/sap/bc/ui5_ui5/sap/mm_pr_apv.
Please let me know if you need further information.
Regards,
Srikanth
Hi Srikanth,
Please copy & past the OData URI from network tab in inspect element. We need check the OData URI has correct filter option or not.
SAP Fiori LL11 - Consultants should know about OData troubleshooting
Regards, Masa
SAP Customer Experience Group - CEG
Hi Masa,
I already pasted the network element URL in my earlier post and thought you are asking for the xml URL. No issues, please find below URL from Network element.
When I gone through the error log for Approve Purchase Requisition, I am getting error "Backend error occured. T100 Info:GBAPP_APV_MSG-013".
When, I checked with URL http://xxx:8000/sap/opu/odata/sap/gbapp_prapproval;mo/LaunchPageCollection from network element in NW Gateway client, getting below error
<?xml version="1.0" encoding="utf-8" ?>
- <error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
</Error_Resolution>
- <errordetails>
</errordetail>
________________________________________________________________________________________________
Regards,
S.Srikanth
Hi Srikanth,
It is strange.
You said OData URI was LaunchPageCollection http://xxx:8000/sap/opu/odata/sap/gbapp_prapproval;mo/LaunchPageCollection.
The LaunchPageCollection does not handle any task type filter but error message said about task type filter.
Please double check the OData URI again. It must be related with WorkflowTaskCollection.
We need to verify that the app passes task ID to backend or not. If the app passes task ID, root cause is in backend side.
Regards, Masa
SAP Customer Experience Group - CEG
Hi Srikanth,
Let's check basics. Have you done everything?
+ UIX01EAP SP02
+ GBAPP002 SP05
+ Note: 1937868 - Installation Information for Approve Requisitions
+ Configuration: App Implementation: Approve Requisitions - SAP Fiori Apps - SAP Library
If above settings are OK, please set external breakpoints in backend.
SAP Fiori LL11 - Consultants should know about OData troubleshooting
Regards, Masa
SAP Customer Experience Group - CEG
Hi Olga,
Can you please let me know which app you are getting error. Please check the following.
1. Check you have latest UI addon & ECC addon
2. Check the services are activated and assigned the system aliases
3. Check the roles are provided to the user.
4. Check all notes are implemented.
5. Check the services from MOD, by clicking on Gateway Client in TCode - "IWFND/MAINT_SERVICE and see whether you are getting Status code - 200
6. Check the services are active in SICF.
Please let me know if you need further information.
Regards,
S.Srikanth
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.