QM certificates vs. DMS
Hi
SAP recommends to use the Archivelink functionality to store In-coming QM certificates. However, these business documents cannot be linked to other SAP objects, like for instance an Equipment (tools). An alternative solution could be to use the Document Management System, but this is not integrated into the transactions QC51/QC55. Is there anyone outthere which has experience with alternative solutions, e.g. how to integrate the DMS solution to the QM certificate.
Br.
Anders
Hi Anders,
regarding the linkage of SAP objects to document info records, you can see
all the available SAP standard objects in function group CV130 under "Screens" in transaction SE80.
I'm not sure about the behaviour in transaction QC51/QC52 but if you can link
document to QM certificates, it should be possible to see some document overview. Maybe there is some entry in the menu bar, which shows the linked documents.
Hope this information is usefull.
Best regards,
Christoph
Similar Messages
-
hello
i'm planning to install a 3rd party certificate on DMS 5.3. I've had a look at the following documentation:
http://www.cisco.com/en/US/docs/video/digital_media_systems/5_x/5_3/dms/aai/administration/guide/certs.html#wp1173018
there doesn't seem to be an option to set the public key size - our certicate provider has specified 2048 bit as a minimum. The default self signed certificate on the DMS is 1024 bit. Does DMS only support 1024 bit and can i use openssl to generate the csr and 2048 bit key and import these into DMS?
Thanks
AndyHi Andy,
DMM officially supports only the import of certificates obtained from a CSR request done on the DMM itself, so you could not import cert and keys obtained externally via the AAI.
I would recommend you to contact your Cisco Account Team for further information regarding the use case you are trying to achieve.
Regards,
Marco -
Defining Date range and using the same range to search the documents.
Hi Sap Gurus,
in our business there are some documents which do have Validity period, like say Inspection certificates and valid for say 10 months, ex.. JAN 25th 2009 to Oct 24th 2009
we store this certificate in DMS and link to some SAP object say an Asset,
we have a requirement to list all the documents based on the expiry date range. say to get a list of documents which are about to expire in 15 days, or the list of documents which have already expired
I tried to define a characteristic in date format, but it is a single value field, and search is only supported on that specific value only.
like we cannot serch the DIR falling in between this Date Ranges.
also report of Documents which are to expire in 15 days could not be got.
is there a way to meet this requirement , if it is through a development also please tell me how the logic could be built
Thanks and regards
Priya SHi SAP Gurus,
Thanks much Thomas for your Promt reply.
The solution provided by Thomas really works but the same thing is not possible in EDMS,
in Easy DMS we cannot manually give any value in the date characteristics field, the system will ask to fill from the date window format.
so we cannot enter < or > <> value in characteristics, hope there is any note or other procedure to get the same funtionality.
please if any one worked on the same with EDMS let me know
Thanks and kind regards
Priya S -
NSU tells you v11 not available for your 5800.. Po...
I have a Blue 5800 bought directly from Nokia's online shop in mid Dec 2008:
http://tienda.nokia.es/nokia-es/product.aspx?sku=3889897&culture=es-ES
It was released very early in Spain (around start Dec 2008)
It is an unbranded handset with product code 0575384 and type RM-356 and firmware v10.0.010
Looking around on the internet, this product code seems uncommon and occasionally listed as USA region?
When I try to upgrade the firmware using Nokia Software Update, it tells me there is no version available. Everyone else seems to be able to update so WHY can't this generic handset be updated yet?
What is the delay in releasing the version of the firmware for this generic, unbranded, non-network-tied phone?
Who else can't upgrade their phone via NSU to version 11?Ahhhh, ok there you go.. its available now! Wasn't earlier..
Things look a little better though I think the display is slightly sluggish now.. And there is a problem with certificates.. "Check for updates" under "Phone Management" reports that the SSL certificate for dms.update.nokia.com has expired yet it is valid until dec this year.. Hmmm Nokia Q/A and testing department doing their job well, again!
grrr
Not changing my 7710 for this phone until I can select multiple items in lists in a way more intuitive than select with tap, options, scroll down, mark/unmark, mark..
On the 7710 you click and drag to start highlighting, then tap to select more items.. FAAAAR easier..
The browser has no context sensative menu.. I can't "open link in new window"
This platform has a long way to go -
QM certificate object can be link with DMS?
Hello guys!
I have the requirement to have the quality certificates available in DMS.
I am looking the DMS customizing, but I cannot find any standard object link for that purpose.
I was trying to create my own object link, I defined my own screen in SE51 but now I don't know how to implement it like subscreen of SAPLCV130 Screen1500.
Any one can tell me if there is an standard object or how I can link my screen to the program SAPLCV130?
Thanks in advance for your helpHi Ravindra,
Thanks for your question, this clarify part of my problem.
Now I am trying to link it myself creating an objectlink and a screen in abap.
I know 3 part have to be implemented:
1. Create the object
2. Create the subscreen
3. Develop the Badi.
The 1st and the 3rd are already done....but I don't how how to create the subscreen and the link it to SAPLCV130.
If I create a subscreen 9001 with program SAPLCV130 a reparing code is needed, so I don't know if this is the correct way or if there is another way to do it without touching the standard program.
Thanks and Best Regards -
Certificate error while calling a webservices from application deployed in
Hi,
When we are trying to invoke a web service from a client application which was deployed in weblogic server we are getting the certificate error. We are using go daddy certificate. Here is the log file
Anyone Please advice.
FileName
weblogic.log
FileComment
<Apr 25, 2011 1:51:15 PM EDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=*.wvu.edu,OU=Domain Control Validated,O=*.wvu.edu". The loading of the trusted certificate list raised a certificate parsing exception Could not set value for ASN.1 string object..>
<Apr 25, 2011 1:51:15 PM EDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=*.wvu.edu,OU=Domain Control Validated,O=*.wvu.edu". The loading of the trusted certificate list raised a certificate parsing exception Could not set value for ASN.1 string object..>
javax.xml.ws.WebServiceException: weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- javax.net.ssl.SSLKeyException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:322)
at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
at javax.xml.ws.Service.<init>(Service.java:56)
at wvudatacollection.wsproxy.scheduler.TimeClockScheduler_Service.<init>(TimeClockScheduler_Service.java:71)
at wvudatacollection.wsproxy.scheduler.TimeClockSchedulerServiceWrapper.getStatus(TimeClockSchedulerServiceWrapper.java:96)
at wvudatacollection.wsproxy.scheduler.GetSchedulerStatusWrapper.getStatusCode(GetSchedulerStatusWrapper.java:10)
at sun.reflect.GeneratedMethodAccessor185.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.adf.model.binding.DCInvokeMethod.invokeMethod(DCInvokeMethod.java:561)
at oracle.adf.model.binding.DCDataControl.invokeMethod(DCDataControl.java:2113)
at oracle.adf.model.bc4j.DCJboDataControl.invokeMethod(DCJboDataControl.java:3009)
at oracle.adf.model.bean.DCBeanDataControl.invokeMethod(DCBeanDataControl.java:436)
at oracle.adf.model.binding.DCInvokeMethod.callMethod(DCInvokeMethod.java:256)
at oracle.jbo.uicli.binding.JUCtrlActionBinding.doIt(JUCtrlActionBinding.java:1437)
at oracle.adf.model.binding.DCDataControl.invokeOperation(DCDataControl.java:2120)
at oracle.adf.model.bean.DCBeanDataControl.invokeOperation(DCBeanDataControl.java:464)
at oracle.adf.model.adapter.AdapterDCService.invokeOperation(AdapterDCService.java:307)
at oracle.jbo.uicli.binding.JUCtrlActionBinding.invoke(JUCtrlActionBinding.java:693)
at oracle.adf.model.binding.DCInvokeAction.refreshInternal(DCInvokeAction.java:47)
at oracle.adf.model.binding.DCInvokeAction.refresh(DCInvokeAction.java:33)
at oracle.adf.model.binding.DCBindingContainer.internalRefreshControl(DCBindingContainer.java:3107)
at oracle.adf.model.binding.DCBindingContainer.refresh(DCBindingContainer.java:2759)
at oracle.adf.controller.internal.binding.TaskFlowRegionController.refreshRegion(TaskFlowRegionController.java:145)
at oracle.adf.model.binding.DCBindingContainer.internalRefreshControl(DCBindingContainer.java:3038)
at oracle.adf.model.binding.DCBindingContainer.refresh(DCBindingContainer.java:2759)
at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.prepareRender(PageLifecycleImpl.java:548)
at oracle.adf.controller.v2.lifecycle.Lifecycle$9.execute(Lifecycle.java:224)
at oracle.adfinternal.controller.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:192)
at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener.mav$executePhase(ADFPhaseListener.java:21)
at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener$5.before(ADFPhaseListener.java:395)
at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener.beforePhase(ADFPhaseListener.java:60)
at oracle.adfinternal.controller.faces.lifecycle.ADFLifecyclePhaseListener.beforePhase(ADFLifecyclePhaseListener.java:44)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:246)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:193)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:85)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:54)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.wls.JpsWlsFilter$1.run(JpsWlsFilter.java:96)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.wls.util.JpsWlsUtil.runJaasMode(JpsWlsUtil.java:146)
at oracle.security.jps.wls.JpsWlsFilter.doFilter(JpsWlsFilter.java:140)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3588)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- javax.net.ssl.SSLKeyException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:313)
at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:312)
... 70 more
Caused by: javax.net.ssl.SSLKeyException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:103)
at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
... 72 more
Thanks,
Sajja
Edited by: user13514455 on Jun 13, 2011 8:35 AMWe resolved this problem for the same version of JDeveloper in the WebLogic Console. In the Domain Structure / Evironment / Servers / Settings for Default Server, click the Configuration and SSL tabs. Then change Hostname Verification to None and check the Use JSSE SSL box at the bottom.
-
Moving documents stored in NW04 internal DMS to external content server ...
Hi all !
is it possible to move documents, stored in NW04s databse (DMS) to an external content server;
we want to swap all documents to an content server;
thanks
oliverHi,
We have to do the following post install activities to connect to Content server from DMS.
On SAP Systems (ECC) using CSADMIN t-code we have done the following post installation steps to check whether Content Server is reachable from SAP system.
When use hit CSADMIN option on the screen
Here we need to uncheck the Check Signature check box as we are not using certificates.
Here we need to give HTTP server (Content Server ) info like host name and the port number service is(1090) running.
2. Using OAC0 t-code create Repository on SAP system (ECC)
Then from here Hit CS ADMIN to create rep on Content Server.
Thnaks,
Tanuj -
Hello,
We want to implement digital signatures in SAP DMS, but we're not sure on how to accomplish it. We have the following scenario:
1. All the users have a digital certificate which is part of the Portuguese ID card;
2. Currently we're all using this certificate to digitally sign e-mails (they use their laptops integrated card reader), for example;
3. We also want to use this certificate to sign DMS documents.
Do you think the above mentioned scenario is possible without licensing additional software? If so, can you guide me through the customization steps?
Thanks in advance.
Kind regards,
RicardoHi Ricardo,
It is quite possible to achieve your requirements using the digital signature strategy available in SAP DMS. I have previoulsy answered the steps involved [here|Digital Signature on Original File; and you may additionally look up [Wiki|http://wiki.sdn.sap.com/wiki/display/PLM/Digitalsignaturein+DMS] and [SAP Help|http://help.sap.com/saphelp_470/helpdata/en/9f/857f3a1c7b11d294d200a0c92f024a/frameset.htm] as well.
In your case,more specifically,you need to adopt the signature method during customization as 'User signature with external security product with/without verification' for which your I-Card reader would also be required.
Regards,
Pradeepkumar Haragoldavar -
OIF with external IdP (Shibboleth) - certificate issue
Hi,
We are in the process of setting up Oracle Identify Federation(as SP) with an external IdP (shibboleth) for SSO,
We got the meta data from the IdP and setup the Identify Provider in OIF with IdP meta data,
The IdP got self sign certificate,
When we try to test the connection, it redirects to the IdP but it fails in the end with below bad certificate error,
Can someone shed some light into this and this is a road block for us? Is Self certificate a issue? please advice any steps to be followed and how
<Error> <oracle.security.fed.controller.library.api.FedEngineInstance> <FEDSTS-12079> <ResponseHandlerException: {0}
oracle.security.fed.controller.frontend.action.exceptions.ResponseHandlerException: oracle.security.fed.util.soap.SOAPException: javax.net.ssl.SSLHandshakeException: Received fatal alert: <b>bad_certificate
at oracle.security.fed.frontend.fed.responsehandler.profiles.sp.SendSoapRequestSSOResponseHandler.perform(SendSoapRequestSSOResponseHandler.java:119)
at oracle.security.fed.controller.library.api.FedEngineInstance.processCall(FedEngineInstance.java:279)
at oracle.security.fed.controller.library.api.FedEngineInstance.processCall(FedEngineInstance.java:164)
at oracle.security.fed.controller.library.api.FedEngineSPInstance.validateAndMapAssertion(FedEngineSPInstance.java:166)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.security.am.engine.authn.internal.plugin.FedUserAuthenticationPlugin.invokeValidateAndMapAssertion(FedUserAuthenticationPlugin.java:284)
at oracle.security.am.engine.authn.internal.plugin.FedUserAuthenticationPlugin.process(FedUserAuthenticationPlugin.java:162)
at oracle.security.am.engine.authn.internal.executor.PlugInExecutor.execute(PlugInExecutor.java:197)
at oracle.security.am.engine.authn.internal.executor.AuthenticationSchemeExecutor.execute(AuthenticationSchemeExecutor.java:101)
at oracle.security.am.engine.authn.internal.controller.AuthenticationEngineControllerImpl.validateUser(AuthenticationEngineControllerImpl.java:265)
at oracle.security.am.engines.enginecontroller.AuthnEngineController.authenticateUser(AuthnEngineController.java:698)
at oracle.security.am.engines.enginecontroller.AuthnEngineController.processEvent(AuthnEngineController.java:299)
at oracle.security.am.controller.MasterController.processEvent(MasterController.java:570)
at oracle.security.am.controller.MasterController.processRequest(MasterController.java:759)
at oracle.security.am.controller.MasterController.process(MasterController.java:682)
at oracle.security.am.pbl.PBLFlowManager.delegateToMasterController(PBLFlowManager.java:209)
at oracle.security.am.pbl.PBLFlowManager.handleBaseEvent(PBLFlowManager.java:147)
at oracle.security.am.pbl.PBLFlowManager.processRequest(PBLFlowManager.java:107)
at oracle.security.am.pbl.transport.http.AMServlet.handleRequest(AMServlet.java:177)
at oracle.security.am.pbl.transport.http.AMServlet.doPost(AMServlet.java:136)
at oracle.security.am.pbl.transport.http.AMServlet.doGet(AMServlet.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61)
at oracle.security.am.agent.wls.filters.OAMServletAuthenticationFilter.doFilter(OAMServletAuthenticationFilter.java:264)
at oracle.security.am.agent.wls.filters.OAMValidationSystemFilter.doFilter(OAMValidationSystemFilter.java:134)
at oracle.security.wls.oamagent.OAMAgentWrapperFilter.doFilter(OAMAgentWrapperFilter.java:120)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3738)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3704)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2281)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1491)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.security.am.engine.authn.internal.plugin.FedUserAuthenticationPlugin.invokeValidateAndMapAssertion(FedUserAuthenticationPlugin.java:284)
at oracle.security.am.engine.authn.internal.plugin.FedUserAuthenticationPlugin.process(FedUserAuthenticationPlugin.java:162)
at oracle.security.am.engine.authn.internal.executor.PlugInExecutor.execute(PlugInExecutor.java:197)
at oracle.security.am.engine.authn.internal.executor.AuthenticationSchemeExecutor.execute(AuthenticationSchemeExecutor.java:101)
at oracle.security.am.engine.authn.internal.controller.AuthenticationEngineControllerImpl.validateUser(AuthenticationEngineControllerImpl.java:265)
at oracle.security.am.engines.enginecontroller.AuthnEngineController.authenticateUser(AuthnEngineController.java:698)
at oracle.security.am.engines.enginecontroller.AuthnEngineController.processEvent(AuthnEngineController.java:299)
at oracle.security.am.controller.MasterController.processEvent(MasterController.java:570)
at oracle.security.am.controller.MasterController.processRequest(MasterController.java:759)
at oracle.security.am.controller.MasterController.process(MasterController.java:682)
at oracle.security.am.pbl.PBLFlowManager.delegateToMasterController(PBLFlowManager.java:209)
at oracle.security.am.pbl.PBLFlowManager.handleBaseEvent(PBLFlowManager.java:147)
at oracle.security.am.pbl.PBLFlowManager.processRequest(PBLFlowManager.java:107)
at oracle.security.am.pbl.transport.http.AMServlet.handleRequest(AMServlet.java:177)
at oracle.security.am.pbl.transport.http.AMServlet.doPost(AMServlet.java:136)
at oracle.security.am.pbl.transport.http.AMServlet.doGet(AMServlet.java:697)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at oracle.security.am.agent.wls.filters.OAMServletAuthenticationFilter.doFilter(OAMServletAuthenticationFilter.java:264)
at oracle.security.am.agent.wls.filters.OAMValidationSystemFilter.doFilter(OAMValidationSystemFilter.java:133)
at oracle.security.wls.oamagent.OAMAgentWrapperFilter.doFilter(OAMAgentWrapperFilter.java:120)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3738)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3704)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2281)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1491)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: java.lang.RuntimeException: oracle.security.fed.controller.frontend.action.exceptions.ResponseHandlerException: oracle.security.fed.util.soap.SOAPException: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate
at oracle.security.fed.controller.library.api.FedEngineInstance.processCall(FedEngineInstance.java:395)
at oracle.security.fed.controller.library.api.FedEngineInstance.processCall(FedEngineInstance.java:164)
at oracle.security.fed.controller.library.api.FedEngineSPInstance.validateAndMapAssertion(FedEngineSPInstance.java:166)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.security.am.engine.authn.internal.plugin.FedUserAuthenticationPlugin.invokeValidateAndMapAssertion(FedUserAuthenticationPlugin.java:284)
at oracle.security.am.engine.authn.internal.plugin.FedUserAuthenticationPlugin.process(FedUserAuthenticationPlugin.java:162)
at oracle.security.am.engine.authn.internal.executor.PlugInExecutor.execute(PlugInExecutor.java:197)
at oracle.security.am.engine.authn.internal.executor.AuthenticationSchemeExecutor.execute(AuthenticationSchemeExecutor.java:101)
at oracle.security.am.engine.authn.internal.controller.AuthenticationEngineControllerImpl.validateUser(AuthenticationEngineControllerImpl.java:265)
at oracle.security.am.engines.enginecontroller.AuthnEngineController.authenticateUser(AuthnEngineController.java:698)
at oracle.security.am.engines.enginecontroller.AuthnEngineController.processEvent(AuthnEngineController.java:299)
at oracle.security.am.controller.MasterController.processEvent(MasterController.java:570)
at oracle.security.am.controller.MasterController.processRequest(MasterController.java:759)
at oracle.security.am.controller.MasterController.process(MasterController.java:682)
at oracle.security.am.pbl.PBLFlowManager.delegateToMasterController(PBLFlowManager.java:209)
at oracle.security.am.pbl.PBLFlowManager.handleBaseEvent(PBLFlowManager.java:147)
at oracle.security.am.pbl.PBLFlowManager.processRequest(PBLFlowManager.java:107)
at oracle.security.am.pbl.transport.http.AMServlet.handleRequest(AMServlet.java:177)
at oracle.security.am.pbl.transport.http.AMServlet.doPost(AMServlet.java:136)
at oracle.security.am.pbl.transport.http.AMServlet.doGet(AMServlet.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61)
at oracle.security.am.agent.wls.filters.OAMServletAuthenticationFilter.doFilter(OAMServletAuthenticationFilter.java:264)
at oracle.security.am.agent.wls.filters.OAMValidationSystemFilter.doFilter(OAMValidationSystemFilter.java:134)
at oracle.security.wls.oamagent.OAMAgentWrapperFilter.doFilter(OAMAgentWrapperFilter.java:120)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61)
... 9 more
Caused by: oracle.security.fed.controller.frontend.action.exceptions.ResponseHandlerException: oracle.security.fed.util.soap.SOAPException: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate
at oracle.security.fed.frontend.fed.responsehandler.profiles.sp.SendSoapRequestSSOResponseHandler.perform(SendSoapRequestSSOResponseHandler.java:119)
at oracle.security.fed.controller.library.api.FedEngineInstance.processCall(FedEngineInstance.java:279)
... 51 more
<Mar 21, 2013 3:50:16 PM EST> <Error> <oracle.oam.binding> <OAM-00002> <Error occurred while handling the request.
java.lang.NullPointerException
at oracle.security.am.pbl.protocol.plugin.credcollect.DefaultRedirectionStrategy.getTargetUrl(DefaultRedirectionStrategy.java:403)
at oracle.security.am.pbl.protocol.plugin.credcollect.DefaultRedirectionStrategy.getRedirectUrl(DefaultRedirectionStrategy.java:314)
at oracle.security.am.pbl.protocol.plugin.credcollect.DefaultCredCollectResponseExecutor.process(DefaultCredCollectResponseExecutor.java:121)
at oracle.security.am.pbl.protocol.plugin.credcollect.CredentialCollectionResponseHandler.process(CredentialCollectionResponseHandler.java:99)
at oracle.security.am.pbl.PBLFlowManager.handleBaseEvent(PBLFlowManager.java:175)
at oracle.security.am.pbl.PBLFlowManager.processRequest(PBLFlowManager.java:107)
at oracle.security.am.pbl.transport.http.AMServlet.handleRequest(AMServlet.java:177)
at oracle.security.am.pbl.transport.http.AMServlet.doPost(AMServlet.java:136)
at oracle.security.am.pbl.transport.http.AMServlet.doGet(AMServlet.java:697)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)extract the certificate for your https site and add this to your trusted store.
if you are using the default trust, it should be located under WLSERV~1.3\server\lib\DemoTrust.jks.
you can either use keytool or a tool like portecle for the same. -
B2B-51075 Missing signer certificate receiving AS2 through reverse proxy
We are setting up AS2 communication through B2B on 11.1.1.6.7, Our reverse proxy configuration in the DMZ looks as shown:
<Location /b2b/httpReceiver>
WebLogicHost internalsoa.domain
WebLogicPort 8001
WLLogFile /dmz/logs/wl-proxy.log
SetHandler weblogic-handler
</Location>
https://externaledi.domain/b2b/httpReceiver
-Dhttp.proxySet=true -Dhttp.proxyHost=externaledi.domain -Dhttp.proxyPort=443
When I go to the externally available URL, I receive the B2B Server is ready to accept HTTP messages from the Trading Partner message.
In the TRACE:32 logging, I see:
[2014-01-10T09:20:30.551-08:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.engine] [tid: [ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: c8ec097869f74d35:75fef00f:14379dde17a:-8000-0000000000080c34,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] Utility:getAllCertsFromWallet:Loaded Certs 5
[2014-01-10T09:20:30.553-08:00] [soa_server1] [ERROR] [] [oracle.soa.b2b.engine] [tid: [ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: c8ec097869f74d35:75fef00f:14379dde17a:-8000-0000000000080c34,0] [APP: soa-infra] java.lang.NullPointerException[[
at oracle.tip.b2b.packaging.SmimeSecureMessaging.verify(SmimeSecureMessaging.java:834)
at oracle.tip.b2b.packaging.mime.MimePackaging.processSignedMultipartMessage(MimePackaging.java:1080)
at oracle.tip.b2b.packaging.mime.MimePackaging.processMultipartMessage(MimePackaging.java:908)
at oracle.tip.b2b.packaging.mime.MimePackaging.processMessageContent(MimePackaging.java:865)
at oracle.tip.b2b.packaging.mime.MimePackaging.doUnpack(MimePackaging.java:780)
at oracle.tip.b2b.packaging.mime.MimePackaging.unpack(MimePackaging.java:670)
at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:1888)
at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1654)
at oracle.tip.b2b.transport.InterfaceListener.onMessageLocal(InterfaceListener.java:412)
at oracle.tip.b2b.transport.InterfaceListener.onMessage(InterfaceListener.java:220)
at oracle.tip.b2b.transport.basic.TransportServlet.doPost(TransportServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
java.lang.NullPointerException
at oracle.tip.b2b.packaging.SmimeSecureMessaging.verify(SmimeSecureMessaging.java:834)
at oracle.tip.b2b.packaging.mime.MimePackaging.processSignedMultipartMessage(MimePackaging.java:1080)
at oracle.tip.b2b.packaging.mime.MimePackaging.processMultipartMessage(MimePackaging.java:908)
at oracle.tip.b2b.packaging.mime.MimePackaging.processMessageContent(MimePackaging.java:865)
at oracle.tip.b2b.packaging.mime.MimePackaging.doUnpack(MimePackaging.java:780)
at oracle.tip.b2b.packaging.mime.MimePackaging.unpack(MimePackaging.java:670)
at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:1888)
at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1654)
at oracle.tip.b2b.transport.InterfaceListener.onMessageLocal(InterfaceListener.java:412)
at oracle.tip.b2b.transport.InterfaceListener.onMessage(InterfaceListener.java:220)
at oracle.tip.b2b.transport.basic.TransportServlet.doPost(TransportServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
[2014-01-10T09:20:30.553-08:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.engine] [tid: [ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: c8ec097869f74d35:75fef00f:14379dde17a:-8000-0000000000080c34,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] MimePackaging:processSignedMultipartMessage:Signature Verification failed
[2014-01-10T09:20:30.585-08:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.engine] [tid: [ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: c8ec097869f74d35:75fef00f:14379dde17a:-8000-0000000000080c34,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] Notification: notifyApp: payload = <Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">[[
<correlationId>null</correlationId>
<b2bMessageId>0A0A117A1437D2B5D520000017198417</b2bMessageId>
<errorCode>B2B-51075</errorCode>
<errorText>
<![CDATA[Missing signer certificate.
]]>
We used the following notes to guide the configuration:
http://blog.darwin-it.nl/2012/11/b2b11g-with-apache-20-as-forward-proxy.html
http://anuj-dwivedi.blogspot.sg/2010/10/enabling-ssl-on-oracle-b2b-11g.html
Has anyone gotten AS2 communication to work through a reverse proxy? We are not picking up any agreements or senders in the B2BConsole reports.
Thanks,
-MichaelIt turns out the trading partner provided the incorrect certificate. Once they sent a new certificate (must be the one they use for signing), everything worked.
-
Storage System in Data Management System (DMS)
Hi Gurus,
I am working with defining storage system where I have named the content respository as DMS_C2 , storage type as R/3 database, Version as 0045.
I would like to know if this storage system would be used to save my documents let say my CAD files in DMS. If yes how can I store and access my documents there in DMS_C2?
Help!!
Thanks,
PaddyIf you intend using an external server and want to experiment, I would actually advise using a cheap desktop machine (any machine with 512MB RAM with windows 2000 or 2003 server would suffice) and playing with that rather, because most of the issues you are likely to encounter would be around the connectivity of the two machines and making a copy of the internal database configuration is unlikely to resolve this or replicate the problems you will encounter. copying the configuration won't replicate the database, it will just create a different logical storage point in the database and I've encountered problems with setting this up before. Alternatively, use your production server and experiment with it before reinstalling before go live.
At least with the separate server you can test HTTP connections, use secure certificates etc. When you use the database you will find yourself unable to check a lot of these because its not on a different server.
Words of warning on problems you will be likely to encounter if installing on windows 2003 server, make sure you have network admin and local machine admin or the install will seem to be successful but you will never get the system up and running properly until you reinstall with these rights. You will receive a HTTP 401 error if that happens. This type of issue will not happen with the database which is why I suggest you get used to using an external server. You also need to test backup's and restores to ensure they are working properly. I've seen many clients not test this and find out their backup software is not compatible with the SAP DB used on the KPRO server, which is generally about the time you find out you've lost a lot of information. -
Storing of HR documents with archive link in DMS?
hi experts,
how to store HR documents with archive link in DMS?
i found somewhere it is possible with tr. code OAWD,OAAD
is helpful..or is there any other way for storing HR documents
becz i am not able to do it..
if any one guide me it will be very helpful to me.
thx..pts will be awarded be sure..hi sam ra,
SAP ArchiveLink - Scenarios in
Applications (BC-SRV-ARL)
SAP ArchiveLink® is one of the SAP Basis cross-application communication interfaces between
the SAP System and external components. External components may be general desktop
applications or external storage systems. The integration of SAP ArchiveLink in the various SAP
applications enables the storage scenarios explained in this cross-application documentation.
The documentation is structured as follows:
An Introductory Section (Seite 10) containing general information about storing using SAP
ArchiveLink and about the following documentation
An application-specific section for each SAP application component (for example, FI, SD,
HR) with the relevant storage scenarios
For information on related areas, see the following documentation:
SAP ArchiveLink (Extern)
SAP Business Workflow (Extern)
Archiving and Deleting Application Data (Extern)
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
SAP ArchiveLink - Introduction
April 2001 9
SAP ArchiveLink - Introduction
The following sections contain general information about this scenarios documentation.
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
SAP ArchiveLink and Application Scenarios
10 April 2001
SAP ArchiveLink and Application Scenarios
SAP ArchiveLink® is one of the integrated interfaces in the SAP Basis System that can be used
to store all kinds of documents in external content servers.
SAP ArchiveLink therefore complements the existing range of SAP application software. For a
detailed description of SAP ArchiveLink, see Introduction to SAP ArchiveLink (Extern).
The SAP application components, for example, SD, FI, HR and MM, support storing using SAP
ArchiveLink by providing various application scenarios. Inbound documents, outbound
documents, print lists, archive files, desktop files and binary files are supported.
How the inbound documents are entered in the system and forwarded for processing and storing
depends on the storage scenario used. For information about the possible Storage Strategies
(Extern) , see the documentation SAP ArchiveLink (Extern).
This documentation describes the storage scenarios that are integrated in the SAP applications,
for example, how Sales and Distribution (SD) documents can be stored in external storage
systems using SAP ArchiveLink.
Archiving in databases using the ADK (Archive Development Kit) is not the same as
storing using SAP ArchiveLink.
For informationen about data archiving using the ADK archiving transaction, see the
documentation Archiving and Deleting Application Data (Extern).
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
SAP ArchiveLink: Overview
April 2001 11
SAP ArchiveLink: Overview
Background
There is a growing trend nowadays to transfer stored data from paper/microfiche to external
content servers (for example, archives). Companies are obliged by law and/or internal
standards to keep documents for a certain length of time. Traditionally, paper archives or
microfilms have been used, but these methods are very expensive, either due to copying costs or
the large amount of space required by such archives. By contrast, electronic storing methods are
a much cheaper option and represent an important part of the paperless office concept.
SAPs R/3 System supports a variety of business processes, which can involve documents both
in paper form and in electronic form. The documents either serve to trigger all kinds of processing
steps in FI, SD, HR and so on, or they are documents relating to processes in one of these
application areas.
When linked to SAP applications, content servers and the SAP ArchiveLink interface allow
flexible access to all document searches available in the SAP System and can therefore lead to
considerable time savings. In addition, a combination of the SAP System and SAP ArchiveLink
allows users multiple access (parallel and direct) to stored documents from their work center
without the need for time-consuming searches, which guarantees faster access to documents.
The subsequent sections of this documentation describe the integration of SAP ArchiveLink in
the functions of various application components within the SAP System.
Concept
SAP ArchiveLink provides the following interfaces:
User interface
Application Interface
This interface consists of function modules, which must be integrated in the SAP
applications, if SAP ArchiveLink functions are to be used.
Business objects are linked to stored documents and object methods are available that
allow storing using SAP ArchiveLink to be integrated flexibly in SAP Business Workflow.
Interface between SAP and external components and general desktop applications
External components may be HTTP content servers, for example. General desktop
applications may be MS Word and MS Excel, for example.
Positioning SAP ArchiveLink
SAP ArchiveLink enables
Incoming documents to be stored in the SAP System
Information from the SAP System (for example, outgoing documents and print lists) to be
stored
Direct access from SAP application components to stored documents
Integration of external content servers with the SAP System
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
SAP ArchiveLink: Overview
The SAP ArchiveLink-specific Terms (Extern) document, technical document class, document
type, object type and synchronous storing and asynchronous storing are explained in the
SAP ArchiveLink documentation, which also contains information on the Administration Concept
(Extern) (content servers, links and link tables).
Technical Basis
Links from documents to business objects are created by the generation of a link table entry,
which contains both a unique identification for each business object using the object type and
object key and a reference to a stored document using the content server ID and a unique key for
each document stored in this content server. It is therefore possible to create a link between a
business object and any number of documents using a simple 1:n relationship in a table. No
entry is required in the application tables in which the business objects are managed. If the link
table entry for an stored document is deleted, all references in the SAP System to this stored
document are also deleted. This technique allows the options for accessing stored documents to
be integrated flexibly into the SAP System.
Application Interface
The interface to the SAP applications contains the following functions:
Linking business objects with stored documents
This function is used to display, retrieve or store stored documents directly from the
business object. An example of this is the link between an F1 business object invoice
and original invoices that have been scanned into the system.
Linking business objects with stored outgoing documents
This function is used to store documents generated using SAPscript and link them with
the relevant business objects. Examples of documents are outbound quotations, order
confirmations, purchase orders and invoices.
Storing print lists
The process for storing print lists is the same as for outgoing documents.
As of R/3 Release 4.6C, application objects archived in data archiving (ADK) are not
stored using SAP ArchiveLink, but rather using the Content Management Service
(Extern) of the SAP Knowledge Provider (Extern) (KPro).
Integration Status
Many applications in the SAP System are linked directly or indirectly with SAP ArchiveLink:
Direct link
FI
MM
SD
Indirect link
Via the DMS (document management system): MM, PP,...
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
SAP ArchiveLink: Overview
April 2001 13
SAP ArchiveLink is centrally integrated in the DMS and all applications with object
links to the DMS are therefore linked to SAP ArchiveLink.
Via MC (Message Control): MM, SD,...
The integration of SAP ArchiveLink in message control allows outgoing documents to
be stored.
Via SAPconnect and the Business Workplace: Faxes
Inbound faxes can be processed directly in the Business Workplace, stored and
linked with business objects without having to be printed first.
Generic Object Services
For R/3 Release 4.0A, generic object services are provided for four SAP ArchiveLink
functions via the system menu for all SAP applications.
From the business objects implemented in the SAP applications, four SAP ArchiveLink functions
can be executed in all applications and independently of which application is involved:
You can display the hit list of stored documents
You can assign stored documents subsequently to a business object.
You can store documents in dialog
You can create a bar code for a business object
These functions are integrated into all SAP applications via object services. There is no need for
special function modules to be integrated in the applications. For more information, see Generic
Object Services (Extern).
For these functions to work smoothly, object orientation in the SAP application and
support of object services are important.
For more information, see Business Context Facilities and Generic Object
Relationships (Extern).
Business Applications
MM
The following documents relating to purchasing in MM can be stored:
Outgoing purchasing documents
Requests for quotation
Purchase orders
Scheduling agreements
Forecast delivery schedules
Contracts
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
SAP ArchiveLink: Overview
14 April 2001
Incoming purchasing documents
Quotations
Order confirmations
Incoming invoices and credit memos
Incoming delivery notes
Print lists
For more information about storing in MM, see SAP ArchiveLink - Storage Scenarios in MM
(Seite 74).
SD/WS
The following are examples of sales documents that can be stored:
Incoming customer inquiries and customer inquiry changes
Outgoing customer quotations
Incoming purchase orders and purchase order changes
Outgoing order confirmations
For more information about storing in SD, see SAP ArchiveLink - Storage Scenarios in SD [Seite
50].
PA
The following personnel administration and payroll documents can be stored:
Incoming HR master data documents
Incoming recruitment documents
Incoming travel management documents
For more information about storing in PA, see SAP ArchiveLink - Storage Scenarios in PA [Seite
204].
QM
The following QM documents can be stored:
Incoming documents for quality notifications (for example, customer complaints)
Outgoing documents for quality notifications (for example, letter of complaint to vendor)
Outgoing quality certificates
For more information about storing in QM, see SAP ArchiveLink - Storage Scenarios in QM
(Seite 93).
The DMS and Applications Connected with the DMS
In the DMS and in applications that are connected with the DMS (often MM and PP), the
following documents can be stored:
Incoming documents
Originals managed in the DMS (PC files)
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
SAP ArchiveLink: Overview
April 2001 15
For more information about storing in the DMS, see Storing in Document Management (CADMS)
(Seite 24).
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Customizing
16 April 2001
Customizing
Customizing is divided into three areas:
General Customizing for SAP ArchiveLink
Customizing for SAP Business Workflow
Application-specific Customizing for individual SAP ArchiveLink scenarios
General Customizing for SAP ArchiveLink
To make these settings, proceed as follows:
Use the Implementation Guide (IMG):
Basis Basis Services SAP ArchiveLink
For further information, see the Customizing (Extern) section in the documentation SAP
ArchiveLink.
Customizing for SAP Business Workflow
For the storage scenarios that use SAP Business Workflow:
Storing for Subsequent Entry (Extern)
Storing for Subsequent Assignment (Extern)
Storing and Entering (Extern)
Storing and Assigning (Extern)
you must make Workflow Customizing settings.
For further information, see the section Specific Customizing (Extern) in the documentation SAP
ArchiveLink and the IMG (Basis Basis Services SAP ArchiveLink).
Application-Specific Customizing
In the individual application scenarios, further customizing settings are required. The
application-specific customizing for each SAP application component is described in the following
sections of this documentation.
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Aim of this Documentation
April 2001 17
Aim of this Documentation
This documentation describes the SAP ArchiveLink scenarios that are delivered as part of the
standard system by SAP. There is a section for each storage scenario. The documentation
describes the standard software.
Each storage scenario description is assigned to one of the big application components in the
SAP System. Storage scenarios in the following application components are currently described:
BC (Basis)
CA (Cross-Application Components)
FI (Financial Accounting)
SD (Sales and Distribution)
MM (Materials Management)
IS-RE (Real Estate Management)
QM (Quality Management)
PP (Production Planning and Control)
PM (Plant Maintenance and Service Management)
PA (Human Resource Management)
PY-DE (Payroll Germany)
The individual storage scenarios are structured as function descriptions and generally contain the
following sections:
Section Description
Use Business background
(this section is sometimes separate from the pure function description).
You learn which application scenarios SAP ArchiveLink supports, which
employees are involved and the advantages and simplifications offered by SAP
ArchiveLink.
This information is enough to give you a first overview of the storage scenarios.
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Aim of this Documentation
18 April 2001
Prerequisites Technical implementation
You become familiar with the document types and the corresponding technical
document classes that form the basis of the scenario. You discover which object
types and link tables are used.
This information is particularly useful if you are planning to enhance or change
the scenario.
Preparation and Customizing
The settings that are necessary to adapt the scenario to the specific
requirements of your corporate structure are described.
The settings described are scenario-specific and usually complement the SAP
application component Customizing.
Activities This section describes the technical and business connection of the scenario to
the R/3 application and how the corresponding application functions are called.
This documentation is not intended to replace the SAP ArchiveLink
documentation and should only be seen as a central reference point for
documentation relating to the implementation of SAP ArchiveLink in the individual
SAP applications.
To find out more about using SAP ArchiveLink and make full use of the functions for
enhancements and in-house developments, see the SAP ArchiveLink (Extern)
documentation.
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
SAP ArchiveLink - Storage Scenarios (BC)
April 2001 19
SAP ArchiveLink - Storage Scenarios (BC)
Ablegen von Listen mit SAP ArchiveLink (Extern)
The following sections describe storage scenarios in R/3 Basis (BC):
Storing Lists in the Report Tree
Storing Print Lists
Storing SAPoffice Documents
See also:
General Introduction (Seite 10) to this scenario documentation
SAP ArchiveLink (Extern) documentation
General Report Selection (Extern) documentation
BC - ABAP Programming (Extern) documentation
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Storing Lists in the Report Tree (BC)
20 April 2001
Storing Lists in the Report Tree (BC)
Use
This section describes the storing of lists generated by executing reports in report trees. The
process is not application-specific and is usually possible for any list unless storing is specifically
prohibited in the program.
Users can access reports that they require in the hierarchical structure of the report tree easily
from all applications, via general report selection in the SAP information system.
The SAP standard report tree contains several standard reports for all applications. To access
reports from a particular application, you must expand the structure until you reach a list of
reports on the lowest level. Here you select and execute the required report. You can display the
result on the screen or print it via the spool system.
Companies can configure the standard report tree to suit their requirements. For example, you
can add your own reports or pre-generated lists and even change the entire structure.
Prerequisites
Technical Implementation (BC)
Object type
SREPOTREE
Document type
ABAP
Link table
TOA01
For further information on executing reports and displaying pre-generated lists in report trees,
see General Report Selection (Extern).
Technical Implementation (BC)
Although storing lists generated in the report tree is similar for all applications, the report tree
available to you may vary from the SAP standard, since your company can adjust the SAP
standard report tree to suit its requirements.
For further information on Customizing the report tree, see the Implementation Guide (IMG).
Choose
Tools Business Engineer Customizing
Implementation projects Display SAP Reference IMG
and then Basis Reporting - Report tree.
Activities
Storing lists
When you have executed a report in the report tree, you can save the result list there and store it
simultaneously.
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Storing Lists in the Report Tree (BC)
April 2001 21
To save your list and store at the same time:
1. Choose System List Save Report tree.
2. Select Store in the dialog box displayed and specify where the list should be stored in the
report tree. Specify the values for Report tree and Nodes.
3. Choose Save.
You have now saved your list in the report tree and the process is complete.
Displaying information on storing lists
You can check whether a list has been stored in the report tree:
To check whether a list has been stored:
1. Position the cursor on the relevant list.
2. Choose Utilities List information.
The System displays a dialog box. The check boxes indicate whether the list has been
stored.
Displaying stored lists
To display a stored list in the report tree, choose the relevant list by double-clicking.
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Storing Business Workplace Documents
22 April 2001
Storing Business Workplace Documents
Use
Documents stored in the Business Workplace (Extern) are usually stored in the R/3 database (PC
documents and binary documents can also be stored in an HTTP content server). To save
memory space in the database, you can store documents in an external storage system using
SAP ArchiveLink. The content of the documents that you have stored using SAP ArchiveLink is
then deleted from the database.
You can only retrieve Workplace documents stored using SAP ArchiveLink from the
external storage system, from within the R/3 System. Direct access within the
storage system is not possible.
Prerequisites
Technical Implementation
Object type
SOFM
Link table
TOA01
Document class
BIN
Document type
SOAARCHIVE Description: Office data object
Preparation and Customizing
To store documents from the Business Workplace, a content server must be maintained for the
object type SOFM and the object class SOAARCHIVE in Customizing (Extern) for SAP
ArchiveLink.
To perform mass archiving of Workplace documents, you need authorization (Extern) for
Workplace administration. This authorization is contained in the role SAP_BPT_USER.
Activities
Proceed as described in Mass Archiving (Extern).
The procedure for displaying and changing documents stored in the archive is no different for the
user than the procedure for documents stored in the R/3 database. Calling documents from the
archive usually takes longer, however.
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
SAP ArchiveLink - Storage Scenarios (CA)
April 2001 23
SAP ArchiveLink - Storage Scenarios (CA)
The following sections describe the storage scenarios in the R/3 application component CA
(Cross-Application):
Document Management System (CA-DMS)
Data Achiving (CA-ARC)
See also:
General Introduction (Seite 10) to the scenario documentation
SAP ArchiveLink (Extern)
Application Data Archiving (Extern)
Document Management System (Extern)
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Optical Archiving in Document Management (CA-DMS)
24 April 2001
Optical Archiving in Document Management (CA-DMS)
eingehende Dokumente (Seite 30)
You can use SAP ArchiveLink® to archive documents from the document management system
(DMS) in optical archiving systems.
Documents Input when Processed (CA-DMS) (Seite 30)
Checking a Document into an Archive (CA-DMS) (Seite 31)
Displaying an Archived Document (CA-DMS) (Seite 32)
Copying an Archived Document to a Document Info Record (CA-DMS) (Seite 33)
Digital Original Application Files (CA-DMS) (Seite 25)
Archiving an Original Application File (CA-DMS) (Seite 26)
Creating a New Version (CA-DMS) (Seite 27)
Changing an Original Application File for an Existing Version (CA-DMS) (Seite 28)
Displaying an Archived Original Application File (CA-DMS) (Seite 29)
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Digital Original Application Files (CA-DMS)
April 2001 25
Digital Original Application Files (CA-DMS)
For each document info record, you can maintain and archive two original application files.
Each original application file can be linked to a maximum of 99 additional files. These are
archived automatically when you archive the original application file.
Functions
You process original application files with the following menu option of the document info record:
Extras Originals File 1(2)
The following functions for archiving and processing archived original application files are
available:
Archiving an Original Application File (CA-DMS) (Seite 26)
Creating a New Version (CA-DMS) (Seite 27)
Changing an Original Application File for an Existing Version (CA-DMS) (Seite 28)
Displaying an Archived Original Application File (CA-DMS) (Seite 29)
Notes on archiving original application files
The system checks the application that is used to process the original application file (for
example, WinWord 7.0).
In the IMG for the Document Management System in the activity Define workstation
applications, you define the archives for the various applications (for example, archive A2
for the application WinWord 7.0).
The system does not log the archiving of original application files. However, in the IMG for
the Document Management System, you can define in the activity Define document types
that all field changes are to be logged (Indicator: Create change documents).
If you have archived an original application file with the function Check in archive, you
can track any changes to the storage data (fields Data carrier and Original) in the change
documents.
Notes on processing archived original application files
You have two options for processing an archived original application file:
Creating a New Version (CA-DMS) (Seite 27)
Changing an Original Application File for an Existing Version (CA-DMS) (Seite 28)
See also:
Figure: Changing an Archived Original Application File (Extern)
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Archiving an Original Application File (CA-DMS)
26 April 2001
Archiving an Original Application File (CA-DMS)
You archive an original application file if you want to save the current processing status for
documentation purposes.
See also:
Figure: Archiving Original Application Files (Extern)
To archive an original application file:
1. Process the document in change mode (Basic data screen).
2. Choose Extras Originals File 1(2) Check in archive.
The system saves the original application file to the optical disk defined in Customizing.
You see a dialog box with the following message:
Document archived successfully
3. You can check which archive the document was saved to.
To do this, display the data carrier and path for the original application data by choosing
Storage data.
The data carrier and the path where the original application file was stored before being
checked in the archive is no longer displayed. The system has overwritten this data with
the archive data.
If the document type is defined such that all field changes are logged, you can still
display the previous storage place (Goto Display changes).
4. Save your document info record.
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Creating a New Version (CA-DMS)
April 2001 27
Creating a New Version (CA-DMS)
This means that you keep the old version (for example, 00) containing the archived original
application file and create a new version (for example, 01) directly from the old version. For the
new version, you then change the original application file.
To process the archived original application file (new version):
1. On the Basic data screen, choose Document New version.
The system copies the data of the existing version (for example, 00), including the archived
original application data.
2. In the new version (for example, 01), the original application file is still archived.
3. Choose Extras File 1(2) Change.
The system automatically creates a copy of the checked in original application file.
Enter the target for the copy. This path identifies the place where the original
application file for the new version (for example, 01) is stored.
If the system accepts your entries, you see a dialog box with the following message:
Data copied from archive
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Changing an Original Application File for an Existing Version (CA-DMS)
28 April 2001
Changing an Original Application File for an Existing
Version (CA-DMS)
This means that you change the version whose original application file has been archived. There
is only one version in this case.
You can display the processing status that the original application file had in the archive from the
status log if the following applies:
When checking the original application file into the archive, you set a status for which the
Indicator: Audit function is selected. This indicator causes original application files that are
checked into the SAP database, a vault, or an archive with this status to be stored automatically.
To change the archived original application file (existing version):
1. Choose Extras Originals File 1(2) Change.
The system automatically creates a copy of the archived original application file.
2. You see a dialog box, where you can enter the target for the copy. As a default value, you
see the path where the file was stored before being archived.
To accept the default value, choose Continue.
If you want the file to be copied elsewhere, enter the required data (data carrier,
path, and file name) in the dialog box. This path identifies the place where the
original application file for the same version is stored. The system overwrites the
previous archive data.
If the system accepts your entries, you see a dialog box with the following message:
Data copied from archive
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Displaying an Archived Original Application File (CA-DMS)
April 2001 29
Displaying an Archived Original Application File (CADMS)
To display an original application file, you always use the following function, whether the data is
stored on a server or in an archive:
Extras Originals File 1 (2) Display.
The system automatically determines the path in the computer network. If the original application
file is stored in an archive, you see a dialog box with the following message:
Data copied from archive
You can display archived data only from computers that have SAP ArchiveLink
software installed.
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Documents Input when Processed (CA-DMS)
30 April 2001
Documents Input when Processed (CA-DMS)
You process documents input when processed in the Archive menu of the document info record.
The following functions are available:
Checking a Document into an Archive (CA-DMS) (Seite 31)
Displaying an Archived Document (CA-DMS) (Seite 32)
Copying an Archived Document to a Document Info Record (CA-DMS) (Seite 33)
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Checking a Document into an Archive (CA-DMS)
April 2001 31
Checking a Document into an Archive (CA-DMS)
You use this function to check a scanned-in document (image) into an optical archive.
See also:
Scenario: Checking a Document into an Archive (Extern)
To check a document into an archive:
1. Two windows are active on your computer screen:
a scan window with a scanned-in document
a window for the R/3 document management system
2. In the document management window, choose the function you require (Document
Create or Change).
Enter the required data on the initial screen and choose ENTER. You see the Basic data
screen.
3. Choose Archive Check into archive.
The system checks whether a status network that supports a status of status type A
(archived) is defined for the chosen document type.
Archiving is possible in the following cases:
if the status network does not support a status of status type A
if the status network supports a status of status type A at the current processing
stage.
The system automatically sets the status of status type A and records the status
change in the status log.
The system automatically determines the archive that is defined in the IMG
functionOptical Archive.
When the data has been archived, you see a dialog box with the following message:
Document archived successfully
4. Save your document info record.
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Displaying an Archived Document (CA-DMS)
32 April 2001
Displaying an Archived Document (CA-DMS)
You use this function you to display documents that were either scanned in when processed,
then archived, or copied from the archive from the document info record.
This function is only active it at least one document has been archived for the chosen
document info record.
To display a document from the archive:
1. Choose menu option Archive Display from archive.
2. What you do next depends on the situation:
If only one archived document exists for the document info record, the system goes
directly to the display program (viewer) and displays the document.
If more than one archived documents exist for the document info record, you first
see a dialog box listing the archived objects with the date on which they were
archived.
On the list, select the archived objects you want to display in the viewer.
Choose the Choose pushbutton.
The system goes to the first selected object.
In the viewer, you can switch between the objects you selected by choosing the
appropriate function (Object + or Object -) from the Goto menu.
3. To exit the display function for archived objects, close the viewer with Document Exit.
You can now continue processing the document info record.
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Copying an Archived Document to a Document Info Record (CA-DMS)
April 2001 33
Copying an Archived Document to a Document Info
Record (CA-DMS)
This function allows you to copy a document that has been archived by another application (for
example, SAPoffice) to a document info record.
See also:
Scenario: Copying an Archived Document to a Document Info Record (Extern)
Figure: Copying an Archived Document to a Document Info Record (Extern)
To copy a document from an archive:
1. Two windows are active on your screen:
a window showing the document in the display program (viewer) of the archive
a window for the R/3 document management system
2. In the document management window, choose the function you require (Document
Create or Change).
3. Place the cursor on the viewer window again.
Choose Edit Select
This selects the scanned-in document for processing in the document management
system.
4. Place the cursor on the document management window.
Choose Archive Copy from archive.
The system makes the same status checks as described in Checking a Document into
an Archive (CA-DMS) (Seite 31).
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
SAP ArchiveLink and Application Data Archiving (CA-ARC)
34 April 2001
SAP ArchiveLink and Application Data Archiving (CAARC)
Use
You can use the Archive Development Kit data archiving transaction and SAP ArchiveLink to
store archive files in external archives. For more information see: Technical Background (CAARC)
(Extern).
Prerequisites
You must enter the following settings in customizing in order to use the SAP ArchiveLink
interface to archive application data:
Platform-independent filename
Document type
Automatic transfer of archive files
Activities
Checking Storage Status of Archive Files (CA-ARC) (Seite 38)
Storing Archive Files Manually (CA-ARC) (Seite 39)
See also:
Setting Platform-independent Filenames for SAP ArchiveLink (CA-ARC) (Seite 35)
Setting Archive File Document Type (CA-ARC) (Seite 36)
Storing Archive Files Automatically (CA-ARC) (Seite 37)
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Setting Platform-independent Filenames (CA-ARC)
April 2001 35
Setting Platform-independent Filenames (CA-ARC)
1. Call the Archive Management.
2. Enter the name of the archiving object and press Enter.
3. Choose the Customizing function.
4. In archiving object-specific customizing choose Technical Settings.
5. In the logical filename field enter a filename that refers to the exchange directory of the
attached SAP ArchiveLink archive system. For example, the logical filename
ARCHIVE_DATA_FILE_WITH_ARCHIVE_LINK. The system delivers the following standard
defined filename:
, if you use this runtime variable in the specification of the
physical path. For example, the physical path could be:
ARCHIVE_GLOBAL_PATH_WITH_ARCHIVE_LINK. See the FILE transaction
documentation for further information.
See also:
Setting Archive File Document Type (CA-ARC) (Seite 36)
Storing Completed Archive Files in the Archive System Automatically (CA-ARC) (Seite 37)
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Setting Archive File Document Type (CA-ARC)
36 April 2001
Setting Archive File Document Type (CA-ARC)
1. Call the Archive Management.
2. Enter the name of the archiving object and press Enter.
3. Choose the Customizing function.
4. Choose Technical Settings in archiving object-specific customizing.
5. Choose the document type Archive in the group box Archive System Link.
See also:
Setting Platform-independent Filenames for SAP ArchiveLink (CA-ARC) (Seite 35)
Storing Completed Archive Files in the Archive System Automatically (CA-ARC) (Seite 37)
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Storing Completed Archive Files in the Archive System Automatically (CA-ARC)
April 2001 37
Storing Completed Archive Files in the Archive System
Automatically (CA-ARC)
1. Call the Archive Management.
2. Enter the name of the archiving object and press Enter.
3. Choose the Customizing function.
4. Choose Technical Settings in archiving object-specific customizing.
5. Mark the checkbox Exec. automat. in the group box Archive System Link.
See also:
Setting Platform-independent Filenames (CA-ARC) (Seite 35)
Setting Archive File Document Type (CA-ARC) (Seite 36)
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Determining Whether an Archive File is Stored in the Optical Archive (CA-ARC)
38 April 2001
Determining Whether an Archive File is Stored in the
Optical Archive (CA-ARC)
1. Call the Archive Management.
2. Enter the name of the archiving object and press Enter.
3. Choose the Management function.
4. Set the cursor on the file whose archive residence you want to know, and double-click.
The Archive Management: Archiving File Detail popup appears. Read the Storage option
status text.
See also:
Storing Completed Archive Files in the Archive System Manually (CA-ARC) (Seite 39)
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Storing Completed Archive Files in the Archive System Manually (CA-ARC)
April 2001 39
Storing Completed Archive Files in the Archive System
Manually (CA-ARC)
Only archive files whose data objects have been deleted in the database can be
stored in an external archive system.
1. Call the Archive Management.
2. Enter the name of the archiving object and press Enter.
3. Choose the Management function.
4. Set the cursor on the file which you want to store in the external archive system.
If you want to store all the files in a session, set the cursor on the session number.
5. Choose the Store function.
The Archive Management: Store via ArchiveLink popup appears.
6. Choose the Store Files function.
The file is passed to the external archive system.
See also:
Determining Whether an Archive File is Stored in the External Archive (CA-ARC) (Seite 38)
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
SAP ArchiveLink - Storage Scenarios (FI)
40 April 2001
SAP ArchiveLink - Storage Scenarios (FI)
The following sections describe storage scenarios in the Financial Accounting (FI) application
component.
See also
The general introduction (Seite 10) to this scenario documentation
SAP ArchiveLink (Extern)dokumentation
Financial Accounting documentation
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Storing Print Lists (FI)
April 2001 41
Storing Print Lists (FI)
Use
In the FI application component, you can use SAP ArchiveLink to transfer the following print
lists to an external storage system:
Compact document journal (RFBELJ00)
Line item journal (RFEPOJ00)
Open item account balance audit trail (RFKKBU00)
Accumulated account balance audit trail (RFKLBU10)
Storage using SAP ArchiveLink has the following advantages:
Reduced burden on online system
Safer storage
Faster, easier access
Prerequisites
Technical Realization (FI)
Following improvements to the print reports, the print lists are now provided with an index when
they are stored, enabling you to access objects (including sub-objects) at a later date.
A particular account in the account balance audit trail.
The system also generates a link to any stored documents that might exist, enabling you to
display the corresponding stored document from the stored print list.
For a detailed description of how to store print lists, refer to Print Lists (Extern) in the SAP
ArchiveLink documentation.
There are no plans for enhancements.
Preparation and Customizing (FI)
No special Customizing settings are required to be able to store print lists in FI. For
information on the Customizing settings for SAP ArchiveLink, see Customizing (Seite 16).
Special authorizations are not required.
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Storing Print Lists (FI)
42 April 2001
Activities
For notes on using these functions (in particular displaying stored print lists) see
Searching for, Displaying and Printing Print Lists (Extern) in the SAP ArchiveLink
documentation.
To store print lists in the FI application component, proceed as follows:
1. Run the appropriate program and enter your selection criteria.
2. On the selection screen, choose Optical archiving and enter the following information in
the dialog box that is now displayed:
Object class: DRAW (document)
Object type: D01 (print list)
Identification: XXX (three figure alphanumeric code of your choice)
Text: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (up to 30 characters
long).
3. Now choose Execute in background or Execute + Print.
To view the stored list, from the R/3 System initial screen, choose
Office Business Documents Find lists. Enter the name of the report program and
any additional selection criteria. Choose Enter. From the list that is now displayed you
can select a print list and display its contents.
When displaying the list, you can also display the incoming and outgoing documents
(provided these were also stored). You do this via hyperlinks which are recognizable
as such by being underlined.
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Storing Incoming Documents (FI)
April 2001 43
Storing Incoming Documents (FI)
Use
In the FI application component, you can transfer incoming documents (invoices, credit memos)
to an external archive system using SAP ArchiveLink. Data can be stored in different ways:
Store for subsequent entry
Store and enter, and
Late storing with bar codes
Assign, then store
For detailed information on the ways in which you can store documents, see Storage
Strategies (Extern) in the SAP ArchiveLink documentation.
The procedure Store for entry later with document parking is different to other storage
methods. Under this procedure, processing is even more automated than it would otherwise be.
The accounting clerk responsible for parking documents receives an incoming document (an
invoice for example) via SAP Business Workflow. In the entry transaction to which the invoice
is subject, the clerk can park this document using the existing incoming document. He or she can
then send the parked invoice together with the incoming document for further processing
(approval or additional investigation) to the relevant colleague. This colleague can then complete
processing and post the invoice.
Prerequisites
Technical Realization (FI)
Object type
BKPF (financial accounting document)
Link table
TOA01
Document class
FAX
Document type
In the standard system, the following document types are supplied for the R/3 FI application
component.
FI document Document type
Incoming invoice without invoice verification FIIINVOICE
Incoming credit memos without invoice verification FICREDIT
Incoming invoice parking FIIINVPREL
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Storing Incoming Documents (FI)
44 April 2001
Fast invoice entry FIIPAYMEN2
Incoming payment FIIPAYMENT
Enhancements
You can define your own document types under
Tools Business Documents
Document types Global document types and
Tools Business Documents
Document types WFL document types.
You can define your own transaction links under
Tools Business Documents
Document types Workflow parameters.
Further information
For basic technical information on adding SAP ArchiveLink functions to the R/3 application
components, refer to the section Incoming Documents (Extern) in the SAP ArchiveLink
documentation.
Preparation and Customizing (FI)
The basic preliminary settings that you must make in SAP ArchiveLink are described in
Customizing (Seite 16)
You need to make settings in Customizing for Financial Accounting only for the activity Late
storing with bar codes. For more information, see the documentation for the activities Specify
Control Parameters for Bar Code Entry and Maintain Document Types for Bar Code Entry
located in Customizing for Financial Accounting under Financial Accounting Global Settings
Document Document Header.
Activities
Scenario: Assignment and Storage in FI
For information on this procedure, see the following sections of the SAP ArchiveLink
documentation:
Scenario: Late Storage with Bar Codes in FI
For information on this topic, see:
Process: Late Storing with Bar Codes (Extern)
Concept: Storing with Bar Codes (Extern)
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Storing Incoming Documents (FI)
April 2001 45
Scenario: Store for Subsequent Entry in FI
For information on this topic, see:
Concept: Store for Subsequent Entry (Extern)
Process: Store for Subsequent Entry (Extern)
Store for Subsequent Entry (Extern)
Scenario: Entry and Storage in FI
For information on this topic, see:
Concept: Store and Enter (Extern)
Process: Store and Enter (Extern)
Store and Enter (Extern)
Document Processing Functions
In certain document processing transactions in FI you have direct access to the functions
available under SAP ArchiveLink. These transactions include:
Changing documents (FB02)
Displaying documents (FB03)
Changing parked documents (FBV2)
Displaying parked documents (FBV3)
When carrying out these transactions, you can use the following functions:
Subsequently assign a stored document from the external content server (see Assign
Stored Documents Subsequently (Extern))
Display the stored document for an FI document from the external content server (see
Searching for Incoming Documents (Extern))
The assignment and display functions might typically be accessed as follows:
1. From the General Ledger menu, choose Document Display.
2. Enter the document number and the company code in which it was posted. Choose
ENTER.
The system now displays the R/3 document.
3. To display the stored document for this R/3 document, choose Environment Object
links
To assign this document to a document already stored, choose Environment Assign
original.
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Storing Incoming Documents (FI)
46 April 2001
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Storing Outgoing Documents (FI)
April 2001 47
Storing Outgoing Documents (FI)
Use
You can store documents transferred from the General Ledger (FI-GL), Accounts Receivable (FIAR)
and Accounts Payable (FI-AP) application components using SAP ArchiveLink. Documents
that you created using SAPscript are stored in an external storage system and linked to the
documents or accounts from which they are derived. You can store the following outgoing
financial accounting documents:
Payment advice notes
Checks
Correspondence like payment notifications and bank statements
Dunning notices
Storage using SAP ArchiveLink takes place using Business Transaction Events, to which end
SAP supplies sample function modules that you can activate by making the appropriate
Customizing settings.
If you already use your own programs (user exits) or Business Transaction Events to
manage printing, faxing, email or dispatching, check whether you need to replace
these developments with a function module enhanced to perform these functions.
IMPORTANT: Ensure that no data is overwritten.
Prerequisites
Technical Realization (FI)
Object type
BKPF (financial accounting document)
BUS3007 (customer account)
BUS3008 (vendor account)
Link table
TOA01
Document class
PDF
Document type
The following document types exist in the standard system:
FI document Document type Function module
Payment advice note FIOPAYAVIS FI_OPT_ARCHIVE_PAYMENT_ADVICE
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Storing Outgoing Documents (FI)
48 April 2001
Check FIOPAYMENT FI_OPT_ARCHIVE_ PAYMENT
Correspondence:
Payment notification
Bank statement
FIOPAYCONF
FIOACCSTAT
FI_OPT_ARCHIVE_CORRESPONDENCE
Dunning notice FIODUNNING FI_OPT_ARCHIVE_DUNNING_NOTICE
If you make changes in Customizing to the object types and document types, you will need to
adapt the corresponding function modules in each case.
Enhancements
There are no restrictions to the way in which sample function modules in the standard system
can be enhanced. They can also be duplicated for additional document types and object types as
many times as necessary.
You can define your own document types in the Basis Implementation Guide under
Basis Services SAP ArchiveLink System Settings Maintain Document Types.
To define you our own object types, on the SAP R/3 screen, choose
Tools Business Framework BAPI development Business Object Builder.
The sample function module FI_OPT_ARCHIVE_CORRESPONDENCE contains the
correspondence types SAP01 (payment notificiation) and SAP08 (account statement).
Additional correspondence types can be added to this function module. You can define
correspondence types in Customizing for Financial Accounting under the
Implementation Guide under
Financial Accounting Global Settings Correspondence Define Correspondence
Types.
Preparation and Customizing (FI)
To activate storage for financial accounting documents using SAP ArchiveLink, make the
following settings in Customizing:
1. If you want to make changes to the function modules (changing the document type
defined in the standard system for example) copy the sample function modules to your
name range. You should then make these changes in the source text.
For a detailed description of the procedure for copying sample function modules to your
name range, see the IMG documentation for the activity Use Business Transaction
Events (located under Financial Accounting Global Settings.)
2. Define the storage method in the function modules. Enter the setting in source text for
the parameter c_itcpo-tdarmod. The following settings are possible:
2 Store only
3 Print and store
3. Create a product with which all function modules that you want to activate can be
summarized at a later date.
To do this, choose the activity Use Business Transaction Events, located in Customizing
for Financial Accounting under Financial Accounting Global Settings. On the SAP
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Storing Outgoing Documents (FI)
April 2001 49
Business Framework: Business Transaction Events screen, choose Settings Products
... of a customer. Mark this product as active by selecting the Active indicator.
4. Assign the function modules to processes (Events).
To do this, choose the activity Use Business Transaction Events, located in Customizing
for Financial Accounting under Financial Accounting Global Settings. On the Business
Framework: Business Transaction Events screen, choose Settings P/S function
modules ... of a customer. In the table that is now displayed, enter the names of the
function modules that you want to activate, together with the Events or products required.
Enter also the name of the product already created.
The names of the processes defined in the standard system are as follows:
Function module Process
FI_OPT_ARCHIVE_PAYMENT_ADVICE 00002050
FI_OPT_ARCHIVE_ PAYMENT 00002060
FI_OPT_ARCHIVE_CORRESPONDENCE 00002310
FI_OPT_ARCHIVE_DUNNING_NOTICE 00001040
Activities
Storing outgoing documents (FI)
Outgoing documents are stored automatically if you have carried out the above-mentioned
settings in Customizing.
Displaying stored documents
Stored documents can be displayed as follows:
On the SAP R/3 screen, by choosing Office Business Documents Documents
Find lists
From the Accounts Receivable or Accounts Payable menu by choosing Master records
Display.
Enter the customer or vendor you wish to display, select one of the indicators under
Company code data and choose ENTER.
On the screen that is now displayed, choose System Display relationships Stored
documents.
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
SAP ArchiveLink - Archiving Scenarios (SD)
50 April 2001
SAP ArchiveLink - Archiving Scenarios (SD)
The following sections describe the archiving scenarios in the R/3 application component SD
(Sales and Distribution):
General sales and distribution (SD)
Sales support (SD-CAS)
See also
General Introduction (Seite 10) to this scenario documentation
SAP ArchiveLink (Extern)documentation
Sales and distribution (Extern) documentation
Sales support (Extern) documentation
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Optical Archiving of Incoming Original Documents (SD)
April 2001 51
Optical Archiving of Incoming Original Documents (SD)
Betriebswirtschaftlicher Hintergrund (SD) (Seite 52)
Weitere Voreinstellungen (Extern)
Spezial-Customizing (Extern)
Ablegen für spätere Erfassung (Extern)
Zuordnen und Ablegen (Extern)
Spät ablegen mit Barcode (Extern)
Ablegen und Erfassen (Extern)
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Business Background (SD)
52 April 2001
Business Background (SD)
The Sales and Distribution application component contains an SAP ArchiveLink function that
provides sales personnel with a quick and efficient means of optically archiving and processing a
wide range of incoming documents including inquiries, purchase orders, contracts, and
complaints. SAP ArchiveLink offers easy online access to these archived documents during the
planning, processing, and analyzing of business transactions in Sales and Distribution.
The SAP ArchiveLink interface supports the following archiving scenarios for incoming
documents in SD:
Early archiving
Late archiving
Late archiving using bar codes
Simultaneous archiving
Early Archiving
In the early archiving scenario, incoming paper documents are archived in the R/3 System before
an SD document is created.
In early archiving, the archiving process usually begins in a central mailroom where a designated
person opens, presorts, prepares, and records (scans) the incoming mail. Once an incoming
document is scanned and an incoming document type is assigned to it, the system triggers the
SAP Business Workflow to notify the authorized employee(s) that an incoming document has
been received and is due to be processed. When the employee accesses the archived
document, the system automatically calls up the relevant business transaction, such as Create
sales order, according to the incoming document type. After the employee creates and saves the
SD document, the system automatically assigns the archived document to it.
For a detailed description of early archiving, see Early Archiving (SD) (Seite 54).
Late Archiving
In the late archiving scenario, incoming paper documents are archived in the R/3 System and
assigned to existing Sales and Distribution documents.
In late archiving, an employee processes an original document directly from paper or carries out
a sales activity before receiving an original document. At a later point in time, the original
document is scanned into the system and archived as a facsimile. It is then assigned to the
existing SD document by:
The person at the archiving station who scans the original documents
The person responsible for processing the SD document
As in the scenario for early archiving, the archiving process usually takes place in a central
location at the company.
For a detailed description of late archiving, see Late Archiving (SD) (Seite 55).
Late Archiving Using Bar Codes
Late archiving using bar codes is a special form of late archiving. In this case, however, a bar
code is attached to the incoming document either in the mail room or at the time of processing.
SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
Business Background (SD)
April 2001 53
An SD document is created from the original document whose bar code ID is linked to the SD
document number. Later, the original document is scanned into the system which recognizes the
bar code ID and automatically makes the proper assignment to the SD document.
For a detailed description of late archiving using bar codes, see Late Archiving Using Bar Codes
(SD) (Seite 56).
Simultaneous Archiving
Simultaneous archiving is a special form of early archiving in which the incoming document is
scanned into the system, optically archived and, at the same time in another window, the
corresponding SD document is created or changed. The system does not activate SAP
Business Workflow in this case; no mail is sent.
For a detailed description of simultaneous archiving, see Simultaneous Archiving (SD) (Seite 57).
SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
Early Archiving (SD)
54 April 2001
Early Archiving (SD)
The following steps describe a typical scenario in which incoming paper documents are archived
before a Sales and Distribution document is created:
1. A clerk in the central mail room of a company receives a letter from a customer who wishes
to buy several products.
2. The clerk scans the letter into a scanning system.
The system displays the letter in the scan dialog window.
3. Using the SAP ArchiveLink interface in the R/3 System, the clerk or another designated
employee selects the function for early archiving and chooses an appropriate incoming
document type for the scanned document, for example, the general description Customer
response to a sales activity, SDIACTRESP.
4. The clerk confirms the assignment of the incoming document type.
This triggers a workflow in which a mail is sent to the employee who is responsible for
creating sales documents, in this case Mr. Jones in the Sales department.
All employees who are to be notified by SAP Business Workflow must first be listed
in the companys organizational structure (see Customizing for SAP Business
Workflow).
5. Mr. Jones receives the work item in his integrated inbox. When he calls up the work item for
processing, a dialog box appears in which Mr. Jones can confirm or overwrite th -
Dms content repository not running
Hey friends,
While creating content repository i went oac0 gave the clicked in create gave the details selected dms as document area, storage type as 04 http content server. Gave version 0046, port number as 1090, server name and server script as details given by basis. clicked on send certificate. Went to CS admin and saw that server status is running with green light in over view section.
a) But when i come back and click on test connection it says content repository doesnt exists what may be the issue.
b) also in details tab repository status shows only defined should it be running or defined?
regards,
satishHello Pradeep,
Again thanks a lot for the help.
Server log trace means are you pointing to running of report to get RFC error by running the report PCMRVC if so then below find the below.
HTTP interface test using function group SCMS_HTTP
23.12.2011 16:35:00
serverInfo:
contRep ZTEST1
contRepDescription client docs storage
serverStatus running
serverVendor Copyright SAP AG, All rights reserved 1998, 2001
serverVersion 6400
serverBuild 201
serverTime 110500
serverDate 23.12.2011
serverStatusDescription
pVersion 0046
contRepStatus defined
contRepStatusDescription
ok 8,659
create(1): new doc (frontend)
check_subrc: subrc 2 instead 0
check_subrc: HTTP error: 500 (Internal Server Error) "ContRep ZTEST1 or Storage entry not defined"
create(1): new doc (frontend) error
create(2): new doc (back end)
check_subrc: subrc 1 instead 0
check_subrc: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456#Timeout during connection setu p (check that partner exists
create(2): new doc (back end) error
delete(1): unknown doc
check_subrc: subrc 2 instead 1
check_subrc: HTTP error: 500 (Internal Server Error) "Internal error: rc=0, ContRep ZTEST1 or Storage entry not defined "
delete(1): unknown doc error
putCert: ok 11,662
3 errors -
Invalid certificate: No Active Certificate for Content Repository
Hello,
I am trying to store DMS documents in Documentum. We have already performed the exercise in a sandbox environment. We moved to a development system on the SAP side and we are trying to use the same repository on the Documentum side. We have performed the prerequisite ArchiveLink configuration. When we execute the program RSHTTP80, we get an error stating that the certificate is invalid. (Output from SLG1 is attached.)
We have resent the certificates and CSADMIN shows that we have an Active certificate. The problem persists.
Any suggestions are welcome.
Thanks.
JRHI JR,
check the date/time settings in your SAP system and on the content server too. Please don't forget the correct timezone settings.
In the URL expiration time is 20140530063005
But from the test the date, time is 30 May 2014, 04:30:05
So my first thought is that the URL is expired.
Best regards,
Janos -
Hi,
We are trying to check-in the originals ( document) within the PLM WebUI DMS, we get a "Read or write error C:\Users\xxxx\.
Could someone help us understand what the reason could be? The Whitelist has been prepared and certificate has been installed.
thanks.Hi Subramanian,
As per screen shot please provide read/write permission to the showing file path .Please check any path defined in Dc 20 and validate it.
Reg,
Chandu.
Maybe you are looking for
-
Can you share your photos in iPhoto with other users on Mac and if so How?
I am trying to share photos in iPhoto from one user to another user on my Mac computer. Can this be done and how do you do it?
-
How do I merge my photo's from my external hard drive into my iPhoto on my hard drive
I have 12,000 photos on my external hard drive, and i have about 1200 on my Mac Mini Hard Drive, these 1200 would be duplicates if i merge them, how do I merge into my Mini without Duplicating photo's
-
Trouble with loading external mp3 files
I apologize for the length of the post. I hope this is clear of what I am trying to explain. My problem deals with getting "undefined" when I press a button to load an external mp3 files. The following is what my XML childNode looks like: <option pho
-
I have a image file (src.ras) and I want to read it and convert it into Binary image. I am reading it and then I want to find the height and width of it using int w = image.getWidth(); int h = image.getHeight(); then I am getting error Exception in t
-
Adobe Flash Player not automatically!
Adobe Flash Player doesn't work automatically in Opera. I updated it a few days ago trying to solve it but nothing. Can anyone help me, please?