ALI type attachment does not execute in UWL

Hi Experts,
We have successfully installed the SAP Office Notifications Inbox Connector (SONIC) for our Enterprise Portal (EP) and it is able to retrieve SAP Office Inbox items under "Notifications" tab of the UWL.
There is just one problem. Some batch jobs defined under transaction code SM36, contains spool list recipients. The recipient will receive a copy of the spool output in their SAP Office Inbox, generated by SM36 after a batch run. The spool output will be in the form of an attachment of "ALI" (ABAP List) type extension sent as a notification to the SAP Office Inbox.
This attachment can be executed successfully when this is accessed via SAPGUI or WEBGUI. However, should the user attempt to access it from UWL in EP, EP is not able to recognize the "ALI" ABAP list. Instead, an operating system pop up window appears requesting the user to select a program to open the "ALI" type file. In fact none of the desktop programs is able to interpret the "ALI" type file which is in binary mode.
My question is, does EP's UWL with SONIC installed have the capibility to recognize an ABAP list type of attachment in a notification or is there some additional configuration that needs to be done. Please advise, any help would be greatly appreciated. Thank you.
Regards,
Lionel

Hi,
You will have to examine the payroll log to see where in the schema the wage type is being dropped by the system. Normall it is just a processing class that is not set correctly.
thanks.
JB

Similar Messages

Attachment Does Not Open in UWL

Hi,
Using a Background Method i have attached a '.PDF' attachment to the workflow. When open in r3 the Attachment works fine and it opens in PDF reader. But when the same thing is tried through portal, it say the file could not be found.
Kindly Help.
Thanks,
Prashant Singhal

Thanks A. Lavorenz
after implement the SAP notes i followed your advice and now I can open attachments.
Goto transaction SICF:
a) goto EXTERN ALIASES
b) add /default_host/sap/bc/contentserver
c )add a user with password
Very important the user must be a type "system"
Claudia Cerulli

Waiting for approval item does not execute attached procedure !

Hi.
Using 3.0.8 on Solaris.
Create one custom item type and associate one on plsql procedure to be run in place when item is listed within its folder.
Go to folder, add item, look for the plsql result : Good it's working !
After that create an item as a create with approval ACL and come back as folder owner, look at the plsql result : NOTHING !!!
My PLSQL procedure is displaying some attributs in order for the folder owner to approve or not the waiting item. So if wainting for approval items does not execute associated plsql function as they are "waiting" (active=0) then I've got some problems!
Any suggestions ?

Hi all,
Thanks very much for your feedback.
In reply to Brian's suggestions
1. I checked to see if WS14500013 was defined as general task; it was not and this has has now been rectified. Went through the other workflows also.
Double checked the contents of the tables:
APPROVAL_TABLE, ITEM_APPROVAL_TABLE, ITEM_APPROVAL_OBJECT.
All appeared OK.
Created a simple one line SC. Invoked approval preview and the message: 'Approval step without ad-hoc capability. No preview possible' was displayed. This is odd since WS14500015 and sub-workflows do not use AD-HOC approval. Or am I not understanding this correctly.
Followed Smitas suggestions but to no effect.
Here are the contents of the said tables which I lifted from the workflow tables:
Again, many thanks for your responses...
**APPROVAL_TABLE****
NAME="APPROVERLIST:ApproverList:" <APPROVAL_INDEX>0000000001</APPROVAL_INDEX>
<APPROVAL_BRANCH>0000000001
<APPROVAL_AGENT>USMGRR11000
<APPROVAL_STATE>0000000002
<INITIAL_AGENT>USMGRR11000
<INITIAL_INDEX>0000000002
**ITEM_APPROVAL_OBJECT***.
NAME="ITEMAPPOBJTABLE:ItemAppObjTable:" - <item>
<SC_GUID>957117374BC6434882B0BFD5462A2724</SC_GUID>
<APP_CRIT_NAME1>COST_CTR</APP_CRIT_NAME1>
<APP_CRIT_NAME2>ORDER_NO</APP_CRIT_NAME2>
<APP_CRIT_NAME3 />
<APP_CRIT_VALUE1>R11000</APP_CRIT_VALUE1>
<APP_CRIT_VALUE2 />
<APP_CRIT_VALUE3 />
<APPROVAL_OBJECT_GUID>9E6EFAC500B681458284BBB60BF99C8A
*****ITEM_APPROVAL_TABLE***,
NAME="APPROVALITEMLIST:ApprovalItemList:"
<item>
<APPROVAL_OBJECT_GUID>9E6EFAC500B681458284BBB60BF99C8A <APPROVAL_ITEM_GUID>1137519335F51C4DB3D2844A8AD484C0

Movement type 647 does not currently support serial numbers management

we can't do "shipment start/PGI for DOWN shipment 1178184 DN# 40309339.
Error message " Movement type 647 does not currently support serial numbers management" see also attachment
Error is like that
Stop : Save Shipment
Stop : Shipment 0001178184 :Action for Shipment start
Read Activities profile ZPGI
Main issue
Stop: Movement type 647 does not currentely support serial number management.
Delivery 001114455 in shipment could not be posted GI
Ssome problem with the movement type 647.
what I understand is, its a SD movement which place the material in transit and automatically executes
the 101 movement. If possible please help in this matter.
Pls help what exactly issue and resolution .
Regards
Vicky

Check this thread
[STO with delivery in 1 step (mvt. type 647) with serial numbering |STO with delivery in 1 step (mvt. type 647) with serial numbering]
thanks
G. Lakshmipathi

Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist

Hi there,
same Thread I post in "Portal Developement". Now I try my luck in ths category...
we implement ESS (ERP2004 with WebDynpros) in our testsystem, but we got an error and don´t know what to do...
System Landscape:
- mySAP Enterprise Portal 6.0 SP17
- Java Application Server (excluding from HR)
- mySAP ERP2004 HR-System
The Connections from the portal runs to the Java-App-Server, not direct to the HR-System (HR-System has no Java Installation and our Customer don´t want a installation, because it could be a bad performance)
We implement the Jco´s and fill out the usermapping. If we want to call the firstpage of the new ESS-Role we get this error.
Can anyone help us? Do we need some installations?
Best regards
Christian
Error
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
com.sap.dictionary.runtime.DdException: Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
... 54 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727)
Version
DOM version
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, Build ID: 6.4015.00.0000.20051123162612.0000 (release=630_VAL_REL, buildtime=2005-12-14:21:51:22[UTC], changelist=377533, host=PWDFM026)
J2EE Engine No information available
Java VM Classic VM, version:1.4.2, vendor: IBM Corporation
Operating system AIX, version: 5.2, architecture: ppc64
Other
Session Locale de
Time of Failure Thu Jan 11 16:14:11 GMT+00:00 2007 (Java Time: 1168532051021)
Web Dynpro Code Generation Infos
sap.com/pcui_gp~xssutils
SapDictionaryGenerationCore 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:45[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapDictionaryGenerationTemplates 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:57[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapGenerationFrameworkCore 6.4015.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-11-24:21:18:08[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:14:40[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
SapMetamodelCommon 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:46[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelCore 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:36[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelDictionary 6.4018.00.0000.20060302125547.0000 (release=630_REL, buildtime=2006-09-20:21:00:39[UTC], changelist=392265, host=PWDFM027.wdf.sap.corp)
SapMetamodelWebDynpro 6.4018.00.0000.20060823112248.0000 (release=630_REL, buildtime=2006-09-20:21:09:40[UTC], changelist=415252, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
SapWebDynproGenerationCore 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:15:10[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
sap.com/tcwddispwda
No information available
sap.com/pcui_gp~xssfpm
SapDictionaryGenerationCore 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:45[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapDictionaryGenerationTemplates 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:57[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapGenerationFrameworkCore 6.4015.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-11-24:21:18:08[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:14:40[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
SapMetamodelCommon 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:46[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelCore 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:36[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelDictionary 6.4018.00.0000.20060302125547.0000 (release=630_REL, buildtime=2006-09-20:21:00:39[UTC], changelist=392265, host=PWDFM027.wdf.sap.corp)
SapMetamodelWebDynpro 6.4018.00.0000.20060823112248.0000 (release=630_REL, buildtime=2006-09-20:21:09:40[UTC], changelist=415252, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
SapWebDynproGenerationCore 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:15:10[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
sap.com/tcwdcorecomp
No information available
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.sap.xss.ser.xssmenu.model.types.P_Pernr could not be loaded: com.sap.dictionary.runtime.DdException: Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:314)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:669)
at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:233)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:347)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:855)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:158)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:143)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:135)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createBLCComponentUsage(FPMComponent.java:628)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:773)
at com.sap.xss.ser.xssmenu.vc.header.VcXssMenuHeader.onInit(VcXssMenuHeader.java:196)
at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeader.onInit(InternalVcXssMenuHeader.java:225)
at com.sap.xss.ser.xssmenu.vc.header.VcXssMenuHeaderInterface.onInit(VcXssMenuHeaderInterface.java:162)
at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeaderInterface.onInit(InternalVcXssMenuHeaderInterface.java:144)
at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeaderInterface$External.onInit(InternalVcXssMenuHeaderInterface.java:220)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:466)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:354)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:179)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:347)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
Caused by: com.sap.dictionary.runtime.DdException: Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
... 52 more

Hi,
uhm... good question, long time ago...
Error should be in the JCO-Destinations, where you can choose a targetsystem for each Jco-Destination.
Since them we installed a java on the abap-system, so we have a doublestack.
In the Jco Destiantions must be the ABAP-System.
Application via SAPTicket and MetaData via fix User like DDIC.
Regards
Christian

Selected file cannot be linked because its type (video) does not match the original file's type

I've been using Premiere Elements 9 for a couple of years now, and a few months ago I began having problems importing AVI files created from a BlackMagic Intensity Pro capture card. (These issues were not previously occurring, and since they surfaced, I have exhausted the various settings for the BlackMagic card, used various software such as BlackMagic's own Media Express as well as the freeware VirtualDub, and still have the following problems.)
In addition, these AVI files play just fine, in their entirety, using Windows Media Player and in Quicktime.
The problem (or possibly two, but I suspect they could be related) is that most of the AVI files I attempt to import will either (1) import all video and NO audio, or (2) import ONLY a short segment of audio and video, and the length that Elements imports varies. Usually only in the range of a minute or two. The rest of the file is not imported at all.
After much digging in forums, and testing various settings in trying to figure out the issue, I decided to back up all of my files and completely wipe all hard drives and start over with a fresh installation of Windows and Premiere Elements 9. I haven't installed much else yet, as I wanted to first find out if the reinstallation improved things with Elements.
For the first project I created in Elements after the reinstallation, Elements successfully imported an entire AVI that was nearly 2 hours long, audio and video. This was a file that previously would not import properly into Elements. This suggested that my earlier installation of Elements must have been corrupted somehow. At this point I was very hopeful that all was well.
I proceeded to edit the video as I had wanted, saved the project, and exported it to an MPEG format file. I had originally wanted to export it as an MOV, but I hadn't yet installed Quicktime, so Elements couldn't do that just yet. The MPEG export was successful and plays fine.
However, I then installed Quicktime, and once it was finished, I restarted the PC and reloaded the same project. This time, Elements claimed the media was offline. I double-clicked on a segment of the video, and directed Elements to the raw file, but then an error message popped up: "The selected file cannot be linked because its type (video) does not match the original file's type (audio and video)." This was the same file I had JUST edited and of which I created an MPEG.
I tried creating a new project and the "Get Media" function to import the AVI again, but this time only the video imported with NO audio. (This would explain why the error message said what it did, but not why the audio wasn't imported.)
What in the world is going on with Elements??? I am baffled since the ONLY task I have done on this machine after a complete reinstallation of both Windows and Elements is edit one AVI. I find it very hard to believe that just installing Quicktime caused this.
Some info on my system:
System: Asus P6T w/ Intel i7 920 and 12 GB memory
OS: Windows 7 Ultimate
Video Software: Premiere Elements 9
Capture Card: BlackMagic Intensity Pro (PCI-e)
Capture Software: AVIs recorded with either BlackMagic Media Express or VirtualDub (only prior to the reinstallation, as neither of these programs are currently installed)
I'm getting to the point with Elements that I might need to just abandon it and find something else that is more reliable. Anybody have suggestions to help with this, so I won't have to migrate?

mtnsports
We think that we need to start off with definiting the properties of these .avi files that you are importing into Premiere Elements 9.0/9.0.1 (assumed that you are working for the required 9.0.1 Update).
You say that the "avi" was created from a "BlackMagic Intensity Pro capture card". What are the properties of this .avi that you imported into Premiere Elements? Not all .avi are created equal. What is the video and audio compression, frame size, frame rate, interlaced or progressive, pixel aspect ratio, typical duration?
Based on the properties of the video what have you been setting as the project preset?
Let us start here.
More later.
ATR

Document type ZD does not allow you to assign to object MARA

hi ppl,
I have created a Z document type.but its not allowing me to assign in mm02.what might be the problem..? its throwing an error message Document type ZD does not allow you to assign to object MARA.

You need to enable object linking to mara on your new document type. Go to Tcode DC10, select the document type and then go to the object links area. Create a new object link for your document type.

Source message Message Type: POR does not exist in software component versi

HI All,
I have a .tpz file exported from an SRM 4.0 PI system which i have imported in SRM 7.0 ECC 6.0 PI.
I have imported the .tpz file through the import through "client" option.
I am able to open all the objects but i am not able to open the Message mappings.....
It is throwing the following error:
Source message Message Type: PurchaseOrderRequest does not exist in software component version xx_xx_PO_PROCESSING, 1.0 of xx.com Check whether software component version xx_xx_PO_PROCESSING, 1.0 of xx.com is in the Enterprise Services Repository. Import this or a newer version if necessary.
This needs to resolved very urgently...
Kindly help...
Thanx in advance..
Nandan

Hi,
I'd say you need to import some other SWCV which has all the IDOC typos you use in your scenario
probably this is a prerequisite for importing your SWCV
I don't think this is related to sp level or anything like that
it's just that SWCV is missing
Regards,
Michal Krawczyk

When I touch my iPad screen to execute an app, the screen goes dark then the app icon reappears. The app does not execute.

When I touch my iPad screen to execute an app, then the screen goes dark then the app icon reappears. The app does not execute. Any thoughts?

Try a Reset...
Press and hold the Sleep/Wake button and the Home button at the same time for at least ten seconds, until the Apple logo appears. Release the Buttons.
Basic troubleshooting
From Here
http://www.apple.com/support/ipad/basics/

Oracle ADF refresh as deferred does not execute query on page load

In the oracle ADF page I have two panel boxes. (Oracle ADF 11.1.1.4)
a) Personal information panel box with PanelFormLayout (PersonalInfoViewObj) - ReadOnly View Object
b) Address information panel box with Table (AddressInfoViewObj) - Read Only View Object
For the iterators in a) and b) I have kept refresh condition as deferred and cacheResult=false. Also in b) for af:table, I have kept contentDelivery="immediate"
When page loads it fires SQL query for a) and populate the data in Personal information panel box. However for b) it does not execute the SQL query and the data is not getting populated ( in AddressInformation panel with the tables. Please note data is there in the DATABASE......)
Becasue with the refresh as deferred it was not executing the sql query for Panel b) (panel with Table and table iterator). I have tried refresh as always and refresh ifNeeded/renderModel/prepareModel however in that case it is executing the SQL query two times (twice).
Please let me know the best way to fix this issue.

Hi,
I think you need a method in an application module to init your data.
In your AM : create a method like :
public void init(){
getViewObject().executeQuery();
}In your adfc-config.xml create a methodCall from this method and a "control flow case" from the methodCall to your page.
and keep refresh as "deferred " in your pageDef.
Clément

Problem with offset value: field type p does not permit subfield access

Hi experts,
In my table am having one field ,
Filed name : planfinish
data type : dec    Length : 15
data store in this field is :    12.05.2010 03:59:00 this format.
i want to remove year 2010 from this above data by using offset.
i have try with code :   lv_year = lv_planfininsh+6(4).      n also declare lv_year as dec 15.
still am getting error. field type p does not permit subfield access
kindly suggest on this.
thx in advance.

a packed decimal field (P) is a numeric field that is always 8 bytes long. The (15) is the DISPLAY or max number of digits characteristic. Like all true numeric types (not 'N'), offset is meaningless and you do NOT have format 12.05.2010 03:59:00 in a P field! You have 15 digits and a sign, and any decimal point is implied by your data declaration.
Look at keyword CONVERT if this is a timestamp field.

Global succession updates are limited to 500 relationships. If more than 500 exist PLM presents a warning message and does not execute the update

Global succession updates are limited to 500 relationships. If more than 500 exist PLM presents a warning message and does not execute the update.
How/Where to increase the relationship count?
The message which I can see :
Warning:
This specification has exceeded the number of parent relationships allowed by Where Used. The Where Used tool only supports up to 500 parent relationships.
Thanks

This really brings up a larger topic around change management.
The questions you should start with is
1. What kind of change is happening to the raw material?
2. Will this change affect anything upstream inside or outside of PLM4P? (Will this change affect nutrition, compliance, the ingredient statement, the label etc?)
3. Who needs to approve this change?
If they are non-material changes (changes that don't affect theoretical calculations, the ingredient statement, labeling, upstream systems that need to be notified etc) then you should be using get latest revision instead of global succession. Get Latest Revision will automatically switch out the material with the latest approved version. This logic is also configurable in case you need to add additional guard conditions. We can also provide guidance around locking the get latest revision lock once a specification has reached the retired/obsolete state so changes won't occur for specifications in those statuses.
If the changes to the raw material are material changes (changes that affect calculations, labeling etc) then the change should be reflected with a copy of the specification. Dependent specifications then need to be re-issued so calculations can be performed and the appropriate workflow reviews can occur. Smart Issue allows for filtering based on status and should let you re-issue in smaller blocks.
Let me know more about your change management strategy, how often large material changes happen and maybe example causes for those mass changes. We can also schedule a change management training session for everyone where we can share our vision and tools available for change management. This topic is quite large and generally requires a lot of business process discussion beyond just the tools available.
Thanks
Kelly

User exit code does not execute

I'm having a problem with User exit code that does not execute yet seems to be set up correctly.
The User exit is implemented as FM "EXIT_SAPLIPW1_001" in function group XQSM.
I've tried everything I know of with the CMOD and SMOD transactions, and I suspect some sort of transport error.
The only clue I can find in comparing the development system (which works) with the test system (which does not work) is that running "Extended Check" in SE80 on function group XQSM fails with the following error:
"The namespace of program SAPLXQSM has the setting "C" and cannot be tested."
Has anyone any idea what could have happened?

Let us try to retrace the steps.
1. You created a Z project in CMOD and assigned the enhancement IQSM0001 and the component EXIT_SAPLIPW1_001 and activated the same. This is there in the transport.
2. You double clicked on the include in the user exit and created it. You activated the code and included it in the same transport.
If you did the above steps, then your user exit should be active in your test system.
Can you please go to SE10, and list out the objects in your transport? You should see entries in there like below(not necessarily a complete list)
R3TR CMOD <your project name>
R3TR PROG ZXQSMU01
See if you created any of the objects as local objects.
Srinivas

Basic type CREMAS03 does not exist

Hi all.
We have SRM 7 Classic Scenario with ECC 6.4
My problem is in scenario MM-SUS. When we try to replicate a vendor data from MM to SUS the idoc MM is processed correctly, but in (SUS) has an error in trx WE05: Basic type CREMAS03 does not exist.
I review the settings and I can not find the cause.
any idea about that?
Regards

Hi,
I am not clear with your issue. Why are you checking for idoc status in SUS system?
IDOC is sent from the ERP system and check what the status of IDOC is in ERP. Next check whats the xml status in PI system and if its successful in PI then check xml in SUS system/. You can check xml status using tcode: sxi_monitor.
Regards
Sam

Production scheduling profile for production order type 10 does not exist – SAP Message No.10085

When i tried to make confirmation for Production Order through CO15 transaction , i receive the following error message “ Production scheduling profile for production order type 10 does not exist – SAP Message No.10085 “
In Work Scheduling view, Production Scheduling Profile is maintained as per OPKP only.
How to check whether production scheduling profile is maintained for relevant order type 10.
To do this , i went to OPKP & KOT2_OPA transactions but i don’t know how to check. I guide me through with a screen shot.
Also, pls explain about “Order Type 10” and how it is linked with material and order execution.
Looking for a detailed explanation with screen shots , since i am new to SAP.
Thanks With Regards,
Dinesh Kumar V.

Hello Dinesh,
Please check the order type dependent parameter in OPL8 here you will get the Substitute Scheduler
Then go to OPCH and check valid production scheduling profile assign here as per OPKP to your production scheduler for your plant.
Production order have Order category as 10 Process Order 40 in standard SAP you can check this in OPJH.
Best Regards,
R.Brahmankar

ALI type attachment does not execute in UWL

Similar Messages

Maybe you are looking for