MSS UWL WebDynproApplication value not found ...

Hello,
I am using MSS and would like to approve recorded times. But when I configure the UWL there is a problem with registering the object tpys:
WebDynproApplication value not found for task TS00700049 in system SAP_ECC_Financials
Portal Component value not found for task TS00700059 in system SAP_ECC_Financials
Could someone tell me please what this could be and how I can fix it?
Thx, Vanessa

Hello Siddharth Rajora,
thanks for your answer. I will try it out in the next days.
Could you tell me which which values I should set for the parameters?
Thanks,
Vanessa

Similar Messages

Value not found in allowed list of options for field...

Hi,
I'm using RIDC on UCM 11g in order to checkin contents.
UCM hosts different projects.
I've the following problem: if somebody (from a different project) insert a new Information Field (e.g. xAnnoPubblicazione) of type Integer - Option List - Select List Validated and it does not make a default value for this field, when I perform checkin using RIDC, it fails with the error:
"oracle.stellent.ridc.protocol.ServiceException: Content item 'UCMRE010132' was not successfully checked in. Value not found in allowed list of options for field 'xAnnoPubblicazione'.
How can I solve this issue? what's the recommended way?
Thank you very much.
Best regards,
S.

In the database language, you have created a NON NULL column and you are trying to insert a record with NULL value to the column. Of course, it cannot work.
There are three options:
- do not declare the field as NON NULL (that is, you option list has to contain 'blank' as a possible value)
- provide the value on insert
- provide the default value

UJK_VALIDATION_EXCEPTION:Property value not found

Hi All
I am getting below error when executing script logic.
UJK_VALIDATION_EXCEPTION:Property value not found.
I got Entity and Intco as properties in my dimensions (entity and intco dim).
*WHEN Z_PARTNERCO
*IS <> PCC_DEF_CC
*REC(FACTOR=1,Z_COSTOBJECT=[Z_PARTNERCO].ENTITY,Z_PARTNERCO= [Z_COSTOBJECT].INTCO,EB_DATASOURCE ="Matching")
*ENDWHEN
Any ideas

Hi Satish,
that a script works on BPC MS, doesn't automatically means it also works on BPC NW.
Since you don't specify the dimension Z_COSTOBJECT nor Z_PARTNERCO in the XDIM_MEMBERSET, the logic will try to fetch the properties for all members of these dimensions. When you don't maintain the properties for all members the logic will not work.
I advice you to make a specification in your XDIM_MEMBERSET for the dimensions Z_COSTOBJECT and Z_PARTNERCO so you know that the properties are maintained for the selection you try to fetch, or you have to maintain the properties for all members of your dimensions Z_COSTOBJECT and Z_PARTNERCO.
But first i would suggest that your try the logic in the logic tester integrated with BW.
Run transaction SE38 in the basic screen of BW and than run UJK_SCRIPT_LOGIC_TESTER.
This will give you a possibility to run your script in a simulation, this way you can test the script first with only one member from which you know the properties are maintained to see if it works.
Harmen

GP Action Task in UWL Error - Page not found or not available

Hi, SDN Fellow.
I have configured the Guide Procedure connector in UWL Administration to display GP task item in UWL.
I created a new process - says XYZ Form Approval Process. I tested the XYZ process in the GP Runtime, every activity screens come out fine. I am able to see all the Guide Procedure task items in the Task console.
But when I launching the activity item from UWL Task console, by clicking on the item line. It was trying to navigate to the page, but it thrown an error message like the following: "Page not found or not available".
Can anyone advise me where should I go to look at the problem?
Thanks,
KC

Hi.
I went to the NW Admin --> Trace & Log, and get the details of the error message:
Full Message Text
Error looking up url: portal_content/com.sap.pct/platform_add_ons/com.sap.caf.eu.gp.folders.gp/com.sap.caf.eu.gp.roles.runtime/com.sap.caf.eu.gp.worksets.runtime/com.sap.caf.eu.gp.pages.procinstance2
[EXCEPTION]
javax.naming.NameNotFoundException: [Xfs] Object not found: com.sap.caf.eu.gp.worksets.runtime/com.sap.caf.eu.gp.pages.procinstance2 at portal_content/com.sap.pct/platform_add_ons/com.sap.caf.eu.gp.folders.gp/com.sap.caf.eu.gp.roles.runtime/com.sap.caf.eu.gp.worksets.runtime [Root exception is javax.naming.NamingException: [Xfs] Object not found: com.sap.caf.eu.gp.worksets.runtime/com.sap.caf.eu.gp.pages.procinstance2 at portal_content/com.sap.pct/platform_add_ons/com.sap.caf.eu.gp.folders.gp/com.sap.caf.eu.gp.roles.runtime/com.sap.caf.eu.gp.worksets.runtime]
at com.sapportals.portal.pcd.gl.PcdFilterContext.filterLookup(PcdFilterContext.java:407)
at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1248)
at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookupLink(PcdProxyContext.java:1353)
at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookup(PcdProxyContext.java:1300)
at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:1067)
at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:68)
at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:1060)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sapportals.portal.pcd.pcm.roles.RoleNavigationConnector.getNodes(RoleNavigationConnector.java:287)
at com.sapportals.portal.pcd.pcm.roles.RoleNavigationConnector.getNode(RoleNavigationConnector.java:161)
at com.sapportals.portal.navigation.cache.connector.CacheNavigationConnector.getOriginalNode(CacheNavigationConnector.java:931)
at com.sapportals.portal.navigation.cache.connector.CacheNavigationConnector.getNode(CacheNavigationConnector.java:779)
at com.sapportals.portal.navigation.NavigationService.getNavNode(NavigationService.java:1524)
at com.sapportals.portal.navigation.NavigationService.getNode(NavigationService.java:543)
at com.sapportals.portal.navigation.cache.CachedNavigationService.getNode(CachedNavigationService.java:164)
at com.sapportals.portal.navigation.NavigationEventsHelperService.getCurrentNavNode(NavigationEventsHelperService.java:493)
at com.sapportals.portal.navigation.NavigationEventsHelperService.getCurrentLaunchNavNode(NavigationEventsHelperService.java:533)
at com.sapportals.portal.navigation.NavigationEventsHelperService.getCurrentLaunchNavNode(NavigationEventsHelperService.java:521)
at com.sapportals.portal.navigation.workAreaiView.doContent(workAreaiView.java:138)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:375)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:388)
at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
at java.lang.Thread.run(Thread.java:534)
Caused by: javax.naming.NamingException: [Xfs] Object not found: com.sap.caf.eu.gp.worksets.runtime/com.sap.caf.eu.gp.pages.procinstance2 at portal_content/com.sap.pct/platform_add_ons/com.sap.caf.eu.gp.folders.gp/com.sap.caf.eu.gp.roles.runtime/com.sap.caf.eu.gp.worksets.runtime
at com.sapportals.portal.pcd.gl.xfs.BasicContext.lookup(BasicContext.java:1066)
at com.sapportals.portal.pcd.gl.PcdPersContext.lookup(PcdPersContext.java:387)
at com.sapportals.portal.pcd.gl.PcdFilterContext.filterLookup(PcdFilterContext.java:403)
... 35 more
Hope that we can get some hints from the message above.
KC

Request failed with SID value not found

Hi Gurus, I have this error message "No SID found for value '15.00' of charateristic 0CURKEY_TC" and similar message with "10.00" and "*0.0" value, when trying to activate data in standard DSO in BI7.0.
This is a Dev system just setup for traning purposes so I do not have any Master data to load. I am only loading transactional data from DataSource 0PU_IS_PS_32
I tried searching for the answer and did the following
1) Transfer Global Settings from the source system (which solved other problems but not this one)
2) In RSRV, I do not see any errors for this InfoObject
3) I am not sure how I can update table T006 and or TCURC with these values?
I also tried following the Note: 619987 and does not know how I can implement this function module "If you nevertheless receive this error message for the initial value, this means that there is an inconsistency in the SID table for the 0UNIT or 0CURRENCY characteristic. You can eliminate this inconsistency by calling the RSDMD_INITIAL_LINE_INSERT function module with I_CHABASNM = 0UNIT or 0CURRENCY"
Is there any help that anybody can extend, it will be greatly appreciated.

Dear,
SID error comes during activation of ODS because the related MD is not available for assigning SIDs.
So as a first step ensure that the related master data is loaded and Attribute change run has been triggered.
Or Load the MD and Activate the MD (Modeling > InfoObject > Search the Infoobject > Right click > Activate Master Data)
Once you perform this you can retrigger the activation. It should work fine.
Else as a workaround you can blank out these particular values and activate.
There is also one more workaround wherein you can create the Master data entries directly in BW itself. But both the above step should be done after consulting Business and considering data volume that needs to be edited/created.
In most case once you perform the loading and activation of MD your activation should work fine when repeated.
There are cases where it failed again with the same error. In that case try this also (ensure that PSA is there).
Delete the request in red.
Go to monitor
Edit > Setting for further update > Packet should be processed in the background.
Edit > Update Reversal > Read everything manually > Yes
Background processing successfully scheduled
Then you can see the Load running again.
Once this is done perform activation again
Hope it helps
Regards
Bala

Urgent - Report Column based on LOV - Value not found in LOV

Hi All,
Recently, we have upgraded to HTMLDB 2.0 from HTMLDB 1.5.
I have a SQL report. One of the columns is based upon LOV - Display as Text (Based on LOV, does not save state).
For the "Ids" of the report, it should display the corresponding "Names" from the LOV.
But, for the cases, where no record exist in LOV for some Id, then it is directly showing the Id instead of "-" (which i have specified in Display Null Text) in the report column attributes.
Before upgrade, it was working fine.
Any idea where is the issue.
Please help.
Thanks in advance,
Monika

Hi,
Can anybody help me in sorting out this issue please.
For your reference, i have made a test case on
http://apex.oracle.com/pls/otn/f?p=20451:4:3519837362944582:::::
Here, there are 2 tables
1. MY_EMP_COUNTRY(emoid, empname, cntry_id)
2. MY_COUNTRY_LOOKUP(id, name,active)
LOV is created on table 2
select name d, id r
from my_country_lookup
where active = 'Y'
And, on the page a SQL report is created
select empname, cntry_id
from my_emp_country
where, cntry_id is based upon the LOV.
Since, in lookup table, cntry_id = 4 is set inactive, it is not picked up by the LOV and hence on the report instead of showing the NULL text it is showing the cntry_id (4).
The attributes of report column cntry id -
Named LOV = CNTRY_LOV
Display Null = YES
NULL text = -
Display Extra Value = YES
Am I missing anything.
thanks,
Monika

Re:md values not found in cube

Hi Gurus
I have a ods and a cube data is going from ods and then from ods it is going in to cube i changes the update rules for a characteritsic from source char to md attr of i ditectly did a reini to cube and i can find values for all the objects expect for the object for which i changed the update rues
Any suggestion
Thanks in advance
pv

Hi
Thanks for the answer
Master is available and active.
I already deleted the data on the cube and did a reinitia from ods
Any Suggestion

Data or Field value not found(ALE/IDoc)

Dear All,
I succesfully sent IDoc to the Destination client.In BD87(Destination) i found Data in IDoc type but it unable to update into database so what could be problem.
plz reply me soon,
RP

Thanks Dear,
Finally i got success.
thanks a lot

ADK Installation root registry not found?

Hi,
I am trying to image some machines in one location and for some reason we aren't able to. Basically it just PXE boots, finds it in the collection and then it is stopped with a command prompt open "x:\sms\bin\x64>" and doesn't do anything after
that.I checked the SMS log and all I see is the following:
ADK installation root registry value not found.
Loaded C:\Windows\system32\wimgapi.dll
Opening image file D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim
Found Image file: D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim
PackageID: LIA0029B
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
Closing image file D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim
Any ideas or anything else I can check? TIA

Yes, see below TIA
<![LOG[Found new image LIA00004]LOG]!><time="13:43:59.968+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:00.046+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:00.077+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00004\boot.LIA00004.wim]LOG]!><time="13:44:00.077+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00004\boot.LIA00004.wim
PackageID: LIA00004
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:00.140+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00004\boot.LIA00004.wim]LOG]!><time="13:44:00.140+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00005]LOG]!><time="13:44:00.951+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:00.951+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:00.951+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00005\boot.LIA00005.wim]LOG]!><time="13:44:00.951+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00005\boot.LIA00005.wim
PackageID: LIA00005
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:00.982+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00005\boot.LIA00005.wim]LOG]!><time="13:44:00.982+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00095]LOG]!><time="13:44:01.980+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:01.980+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:01.980+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00095\boot.LIA00095.wim]LOG]!><time="13:44:01.980+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00095\boot.LIA00095.wim
PackageID: LIA00095
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:02.012+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00095\boot.LIA00095.wim]LOG]!><time="13:44:02.012+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA0016A]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA0016A\boot.LIA0016A.wim]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA0016A\boot.LIA0016A.wim
PackageID: LIA0016A
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA0016A\boot.LIA0016A.wim]LOG]!><time="13:44:02.448+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA001F4]LOG]!><time="13:44:02.948+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:02.948+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:02.948+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA001F4\boot.LIA001F4.wim]LOG]!><time="13:44:02.948+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA001F4\boot.LIA001F4.wim
PackageID: LIA001F4
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:02.963+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA001F4\boot.LIA001F4.wim]LOG]!><time="13:44:02.963+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00231]LOG]!><time="13:44:03.494+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:03.494+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:03.494+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00231\boot.LIA00231.wim]LOG]!><time="13:44:03.494+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00231\boot.LIA00231.wim
PackageID: LIA00231
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:03.509+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00231\boot.LIA00231.wim]LOG]!><time="13:44:03.509+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00269]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00269\boot.LIA00269.wim]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00269\boot.LIA00269.wim
PackageID: LIA00269
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00269\boot.LIA00269.wim]LOG]!><time="13:44:03.977+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00276]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00276\boot.LIA00276.wim]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00276\boot.LIA00276.wim
PackageID: LIA00276
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00276\boot.LIA00276.wim]LOG]!><time="13:44:04.398+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA00288]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA00288\boot.LIA00288.wim]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA00288\boot.LIA00288.wim
PackageID: LIA00288
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA00288\boot.LIA00288.wim]LOG]!><time="13:44:04.835+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Found new image LIA0029B]LOG]!><time="13:44:05.397+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:1123">
< ![LOG[ADK installation root registry value not found.]LOG]!><time="13:44:05.397+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:207">
< ![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:44:05.397+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:344">
< ![LOG[Opening image file D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim]LOG]!><time="13:44:05.397+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:422">
< ![LOG[Found Image file: D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim
PackageID: LIA0029B
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="13:44:05.412+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="bootimagemgr.cpp:925">
< ![LOG[Closing image file D:\RemoteInstall\SMSImages\LIA0029B\boot.LIA0029B.wim]LOG]!><time="13:44:05.412+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="wimfile.cpp:458">
< ![LOG[Begin validation of Certificate [Thumbprint 5FB5F1C55498CB354607662C58BE4C07D293356E] issued to 'f28c724a-201f-4900-91e0-d2f010b670d1']LOG]!><time="13:44:05.865+300" date="02-03-2015" component="SMSPXE" context=""
type="1" thread="6000" file="ccmcert.cpp:1662">
< ![LOG[Completed validation of Certificate [Thumbprint 5FB5F1C55498CB354607662C58BE4C07D293356E] issued to 'f28c724a-201f-4900-91e0-d2f010b670d1']LOG]!><time="13:44:05.865+300" date="02-03-2015" component="SMSPXE"
context="" type="1" thread="6000" file="ccmcert.cpp:1803">
< ![LOG[PXE Provider finished loading.]LOG]!><time="13:44:05.865+300" date="02-03-2015" component="SMSPXE" context="" type="1" thread="6000" file="smspxe.cpp:184">

404 Resource Not Found In UWL for Display Request in Travel Management

Hi Team,
Issue regarding Uwl in Travel Management.In Mss inbox when approver clicks on display form for travel request its throwing error like 404 resource not found.
i have check all uwl iview properties like list actions to be excluded and Xml code etc.
Regards,
Venkat.

Hi Venkat
I hope you are well and many thanks for using the discussion forums .
In relation to the scenario that you have described you mentioned that:
Once a user (via the MSS Inbox) clicks on the display form for travel request you are encountering a 404 resource not found error.
Ok so the first means of analysis is to ensure the UWL Destination Service Configuration is setup and maintained accordingly. Kindly review and consult the documentation below carefully.
SAP Note: 1133821 - UWL Destination Service configuration
After ensuring the destination(s) are setup accordingly and if the issue persists kindly restart the UWL service and clear the UWL cache to see if that resolves the issue.
In the destination configuration kindly ensure there are no discrepancies or misconfigurations.
Now have you navigated to your current connector setup and viewed the status columns to see if there are any exceptions appearing?
Lastly kindly check if the URL being called (at the request page) is correct.
Kindly update me as per your findings.
Kind Regards & All The Best
Troy Cronin - Enterprise Portal Support Engineer

UWL workitem does not open ISRFormApprove application - isr/PCR - MSS BP

We have configured the UWL based on the standard UWL config. guide. The standard itemtypes for MSS which launches the ISRFormApprove application (TS91000075) is part of the xml config. This was working properly when the ABAP stack and Java stack were on the same server (xR2DB1). At that time the ISR webdynpro applications were on the same server (xR2DB1). Now the ISR webdynpro applications are on the portal server (xE2DB1). When we try to open the workitem it looks for the application on xR2DB1 instead of xE2DB1. The error we get is
*********error start
Service cannot be reached
What has happened?
URL http://xr2db1.xx.xx.com:8000/webdynpro/dispatcher/sap.com/pcui_gp~isr/IsrFormApprove call was terminated because the corresponding service is not available.
Note
     The termination occurred in system xR2 with error code 404 and for the reason Not found.
     The selected virtual host was 0 .
What can I do?
     Please select a valid URL.
     If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:xR2DB1_xR2_00-v:0-s:404-r:Notfound
HTTP 404 - Not found
Your SAP Internet Communication Framework Team
*********error end
If we try to use a system in the portal that points to xE2DB1 we get the following error when trying to register this new webflow system in the UWL admin -
System SAP_WebDynpro_XSS: Thu Jul 10 12:18:31 EDT 2008
(Connector) :com.sap.netweaver.bc.uwl.connect.ConnectorException:Thu Jul 10 12:18:31 EDT 2008
(Connector) :com.sap.mw.jco.JCO$Exception:'ashost' is missing
Need help understanding how to make the change in configuration so that when an approval workitem is clicked in the UWL it looks for the ISR applications on the portal server and not on the ECC server.
Version info:-
EP7 SP15, NW04s (server = xE2DB1)
ECC 6.0 (server = xR2DB1)
MSS BP (mySAP ERP 1.0)
Thanks in advance for your help.

We were able to resolve our issue.
On our portal system we had to change the configuration of the system definition for the backend to use the WAS for the portal.
System Configuration > System Landscape
Pick your system definition
Property Category: Web AS
Description, Hostname, Path should be set appropriately for the portal.
Ex:
Desc: Arbitrary
Hostname: portal_host_name:port
Path: /webdynpro/dispatcher

UWL Leave Request Approval and Page Not Found

Hello Everyone,
We are in the process of implementing leave request with EP 70 ECC 6.0 and I am trying to implement the approval portion in the UWL. The workflow is appearing correctly in the UWL; however, when I click on the request in the UWL, I get a pop up with an error message that has "Page Not Found or Not Available." Does anyone know what could be causing this? I have read some of the other messages and transaction SWFVISU has been mentioned, but I am not sure how to set this up or if this would even resolve my problem.
Also, one of the reasons I have decided to go the UWL route is because the Leave Request Approval Web Dynpro has too many steps. Our users will not like having to click Approve, then Review, then Approve Request. If set up correctly, would the UWL have this many steps? I would imagine so if it is calling the same Web Dynpro, but I thought I would ask. Ideally I would like to have our Approvers select the Leave then choose approve and that be all they do.
Please let me know what you think.
Best Regards,
Scott

Dear Scott,
I am having this problem as well.
I did 2 things to fix this problem.
Firstly, please go to SWFVISU and check the visualization parameter for the below task.
TS12300097
TS12300104
TS12300116
Make sure it is package value is sap.com/ess~lea. It is not com.sap. Then re-register your UWL and it should be workin.
Let me know if it still does not and you may need to check your WAS setting.
Rewards point if useful
Regards,
Bryan

UWL ABAPWebdynpro Launch Error - 404 not found

I have a created a Workflow Custom Task and linked it with the ABAP Webdynpro application (no parameters) in SWFVISU.
In the Portal>System Admin>System Config, i have registered item types for all systems.
The problem is When i try to execute the work item , instead of launching the ABAP Webdynpro application, i get the error '404 Not found The Requested resource does not exist'.
This Service is activeted along with other required activations in SICF.
Any ideas about what I might be missing here?
Thanks,
Saurabh

Hi,
1. Check the UWL Config which is in High Priority, within that config check for the Task Item and see if everything is been passed.
If the first option doesn't work, here is an alternative:
2. Create a iView for the Web Dynpro ABAP application in Portal and get the PCD URL of the object created.
Take a backup of the existing config and replace the definition for the task item in discussion.
<ItemType name="uwl.task.webflow.Task Item Number.System Alias" connector="WebFlowConnector" defaultView="com.sap.pct.erp.ess.leaverequest" defaultAction="launchIView" executionMode="pessimistic">
      <ItemTypeCriteria systemId="System Alias" externalType="Task Item Number" connector="WebFlowConnector"/>
      <Actions>
        <Action name="launchIView" groupAction="no" handler="SAPAppLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=no,toolbar=no,menubar=no,location=no,directories=no">
          <Properties>
            <Property name="SAPIntegrator" value=" ROLES:// give the PCD URL which you created***"/>
            </Properties>
        </Action>
      </Actions>
    </ItemType>
And after replacing the content upload the new config to UWL in High Priority.
Hope this helps.
Cheers-
Pramod

XML-22009: (Error) Attribute 'select' not found in 'xsl:value-of'

Hello,
I'm a long-time Siebel developer but novice to BIP, trying to enhance some complex rtf templates that an experienced xdo/bip developer (contractor) designed for us in the past, with a couple of new fields that have been added to the integration object.
All templates and sub-templates receive 'no errors found' when using add-in tool selection of 'Validate Template'. Unfortunately we cannot utilize the 'preview' capability due to the way the sub-templates are called, so only way to test is to upload into server and attempt to run real-time.
This results in UI error of SBL-OMS-00203, which when we dig into the xdo log file turns out to be:
<Line 648, Column 88>: XML-22009: (Error) Attribute 'select' not found in 'xsl:value-of'.
I have exported all templates and sub-templates into XSL-FO Style Sheet and looked at line 648 column 88, and none of them seem to correspond to this line/column combination (in fact most exports do not even go that high in lines).
Googling 'XML-22009' hasn't proven to be of much help, so reaching out to the xdo experts in this forum.
How are the line/column #'s determined in the xdo log output?
I am pretty sure that it must be some issue with my 'Main' template, since none of the sub-templates have been changed (and the current version of the report, without the new fields incorporated, still runs fine from the UI). In the XSL-FO format export of the (modified, with new fields added) 'Main.rtf' file, line 648 places it right in the midst of a bunch of hex which corresponds to an imbedded image (which was also part of the existing template, no change there) and that line only has 65 columns (i.e. doesn't even go up to 88), so I'm questioning how valid the Line/Column information is in the xdo log error message.
Any hints on troubleshooting this one would be greatly appreciated!
Thanks & Regards,
Katrina

Hi,
as I wrote in the inital message, we even left out the output method or used "application/pdf". The result is unfortunately always the same. And I still claim this is not a problem with the stylesheet itself, it has to do something with the mobile's environment.
Something I didn't tell: we have 2 servlets in our application, 1 responsible for output in html and 1 in pdf. The .fo stylesheet passed to the 'html servlet' is parsed correctly (and shows the source code, because it does not know about fo and conversion to pdf), the .xsl stylesheet passed to the 'pdf servlet' raises same exception/same line. You might tell us that there is a problem with the 'pdf servlet', but once again: why in online it is working?
Greetings and thanx very much for your precious time!

Structure field Umskd not found when access team calendar view in MSS.

Hello.
I am keep getting the following error message in my portal when access team calendar view in MSS portal. I am running EP 7.0 with ERP2005 as my back-end system:
com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: DataNodeInfo(FcSelectionList.SelectList.Output.Ex_Request_List): structure field Umskd not found
    at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:299)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
    at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
Since I am new to MSS portal, I don't know what infor I am missing. Please advice.
Best regards,
Phuong.

Hi Vinod Patil,
I just get the problem solved. I may show you the way and hope it help.
First you should apply the SAP note 1058240 (I am in EA-HR 600 level 27 but we still need to apply) into R/3 server. This note is asking you to patch a .SAR (I have no idea on this file) and you may ask your basis to import it. Make should it is imported and the restart the portal server.
This is what we do to solve the problem. Thanks.
Regards,
WaiWeng

MSS UWL WebDynproApplication value not found ...

Similar Messages

Maybe you are looking for