Error at DB downtime configuration step in SAP installation

Hello Gurus,
While installing CRM IDES 5.0 I am stuck at DB downtime configuration (step 9). After shutting down MSSQL server services are not automatically started. In usual case it should be. Its giving "could not start the MSSQLSERVER" service on host. And my MSSQL services are not starting either it is giving Named pipes provider, error:40 - could not open a connection to SQL Server. If any one faced similar kind of problems sugguest on this.
Regards,
Murali

Check your event log why your database is not coming up.
Markus

Similar Messages

Explain withholding tax partial pament configuration steps in sap

Hi,
This ramu .explain withholding tax partial pament configuration steps in sap .

Hi,
Please follow the steps for tds-partial payments
In the following activities you make the settings for withholding tax. (SPRO-F.AC(NEW)-F.AC.GLBSETTINGS-WITHHOLDINGTAX-EXTENDED WITHOLDING TAX.
The SAP R/3 System provides you with two procedures for processing withholding tax:
"Standard" and extended withholding tax.
"Standard" withholding tax is the procedure that has always been supported by the system. It offers you the following features:
Withholding tax for accounts payable
Withholding tax calculation during payment
Withholding tax code per vendor line item
Extended withholding tax provides the following additional features:
Multiple withholding taxes per customer or vendor line item
Withholding tax calculation for partial payments
Enhancements in withholding tax calculation
Withholding tax calculation during invoice entry and during payment
Regards
Sridharshetty

Open to Buy configuration steps in SAP IS Retail

Hi Guru's,
Let me know about open to buy configuration steps in SAP IS Retail.
Thanks in advance.
Regards,
SP

Hello All,
Delete the plant / Site complete details and put in one transport and do the import & export.
Thanks.
Edited by: krishna cherry on Jul 26, 2010 3:28 PM

Steps after SAP Installation

Hi Gurus,
Do you have a document which would list down the steps to be performed after SAP is installed before we start migrating the legacy data.
thanks

Hi Gurus,
Do you have a document which would list down the steps to be performed after SAP is installed before we start migrating the legacy data.
thanks

GC install fails on OMS Configuration step with NodeManager

I'm trying to install OEM Grid Control and I'm having some problems getting past the OMS Configuration step in the installation. I'm not very familiar with Oracle products. I've completed all the configuration steps listed in the documentation and in order to resolve an earlier problem, I deleted the Keynectis and Telesec certificates from the cacerts java keystore. NodeManager is being run as a service, though I think the configuration process is launching a new instance because it can't connect to the service. I've also been unable to connect to the service through the WLST nmConnect function, though it's possible my parameters are incorrect. If the only problem is that GCDomain is not registered in the nodemanager.domains file, I'm not sure what I'm doing wrong, because I put it in the nodemanager.domains file located at C:\Oracle\Middleware\wlserver_10.3\common\nodemanager:
#Domains and directories created by Configuration Wizard
#Fri Apr 22 15:23:16 EDT 2011
wl_server=C\:\\Oracle\\Middleware\\wlserver_10.3\\samples\\domains\\wl_server
medrec-spring=C\:\\Oracle\\Middleware\\wlserver_10.3\\samples\\domains\\medrec-spring
GCDomain=C\:\\Oracle\\gc_inst\\user_projects\\domains\\GCDomain
medrec=C\:\\Oracle\\Middleware\\wlserver_10.3\\samples\\domains\\medrec
note - the file paths are correct and use escaped slashes where appropriate, but this message board system is turning the last double backslash into a line break. I can't find any html solution that works, so just take my word for it
I restarted NodeManager after making the change as well. Any help would be appreciated. Thanks.
Details:
Machine - Windows Server 2008 x64
DB - 11gR2
WLS - 10.3.2
GC - 11.1.0.1
Install Log:
FINE: Connecting to Node Manager ... Apr 22, 2011 3:23:19 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: <Apr 22, 2011 3:23:19 PM EDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.> Apr 22, 2011 3:23:19 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: <Apr 22, 2011 3:23:19 PM EDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.> Apr 22, 2011 3:23:19 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: <Apr 22, 2011 3:23:19 PM EDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.> Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: This Exception occurred at Fri Apr 22 15:23:20 EDT 2011. Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: weblogic.nodemanager.NMConnectException: Connection refused: connect. Could not connect to NodeManager. Check that it is running at win2008x64-2:7,401. Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at java.net.PlainSocketImpl.socketConnect(Native Method) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at java.net.Socket.connect(Socket.java:525) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at weblogic.nodemanager.client.SSLClient.createSocket(SSLClient.java:38) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:227) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:199) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:205) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:52) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:175) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:168) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at java.lang.reflect.Method.invoke(Method.java:597) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.core.PyReflectedFunction.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.core.PyMethod.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.core.PyObject.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.core.PyObject.invoke(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.pycode._pyx2.nmConnect$3(<iostream>:118) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.pycode._pyx2.call_function(<iostream>) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.core.PyTableCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.core.PyTableCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.core.PyFunction.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.core.PyObject.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.pycode._pyx41.startNM$1(C:\Oracle\Middleware\oms11g\sysman\omsca\scripts\wls\start_server.py:20) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.pycode._pyx41.call_function(C:\Oracle\Middleware\oms11g\sysman\omsca\scripts\wls\start_server.py) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.core.PyTableCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.core.PyTableCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.core.PyFunction.__call__(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.pycode._pyx39.f$0(C:\Oracle\Middleware\oms11g\sysman\omsca\scripts\wls\create_em_infra.py:74) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.pycode._pyx39.call_function(C:\Oracle\Middleware\oms11g\sysman\omsca\scripts\wls\create_em_infra.py) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.core.PyTableCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.core.PyCode.call(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.core.Py.runCode(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at org.python.util.PythonInterpreter.execfile(Unknown Source) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at weblogic.management.scripting.WLST.main(WLST.java:131) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at java.lang.reflect.Method.invoke(Method.java:597) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE:      at weblogic.WLST.main(WLST.java:29) Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Fri Apr 22 15:23:20 EDT 2011 Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Node Manager is down starting it Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Not connected to Node Manager Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Launching NodeManager ...
Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Properties: {ListenAddress=win2008x64-2,ListenPort=7401,NodeManagerHome=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239,StartScriptEnabled=true,StartScriptName=startEMServer.cmd,}
Apr 22, 2011 3:23:20 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Command: C:\Oracle\MIDDLE~1\JROCKI~1.5-3\jre\bin\javaw.exe -classpath "C:\Oracle\MIDDLE~1\JROCKI~1.5-3\jre\lib\rt.jar;C:\Oracle\MIDDLE~1\JROCKI~1.5-3\jre\lib\i18n.jar;C:\Oracle\MIDDLE~1\patch_wls1032\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_oepe1032\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JROCKI~1.5-3\lib\tools.jar;C:\Oracle\MIDDLE~1\utils\config\10.3\config-launch.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.2.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.0\lib\ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1\lib\ant-contrib.jar;C:\Oracle\Middleware\oms11g\sysman\jlib\emConfig.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf-api.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\jrf-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.odl_11.1.1\ojdl.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.odl_11.1.1\ojdl2.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.dms_11.1.1\dms.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.dconfig-infra_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.xdk_11.1.0\xml.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.wsm.common_11.1.1\wsm-pmlib.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.wsm.common_11.1.1\wsm-policy-core.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.wsm.common_11.1.1\wsm-secpol.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.wsm.common_11.1.1\wsm-dependencies.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.wsm.policies_11.1.1\wsm-seed-policies.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.webservices_11.1.1\orawsdl.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.webservices_11.1.1\mdds.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.webservices_11.1.1\ws_confmbeans.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\org.apache.commons.digester_1.7.jar;C:\Oracle\MIDDLE~1\ORACLE~1\..\modules\javax.xml.bind_2.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\..\modules\javax.activation_1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\..\modules\javax.xml.stream_1.1.1.0.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.http_client_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jmx_11.1.1\jmxframework.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jmx_11.1.1\jmxspi.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.dconfigbeans_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share.ca_11.1.1\adf-share-base.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share.ca_11.1.1\adf-share-ca.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share_11.1.1\adflogginghandler.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share_11.1.1\adfsharembean.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share_11.1.1\commons-el.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share_11.1.1\jsp-el-api.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.adf.share_11.1.1\oracle-el.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\auditwlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\sslconfigwlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\oamap_help.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\ossoiap_help.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\jps-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.auditprovider_11.1.1\jps-wls-auditprovider.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1\jps-manifest.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1\jps-mbeans.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1\jps-upgrade.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1\jps-patching.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\lib\ADF-SH~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\lib\mdswlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\AUDITW~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jps-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jrf-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAP_~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAUT~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\ossoiap.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OSSOIA~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\SSLCON~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\wsm-wlst.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbembedded57.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbtools57.jar" weblogic.NodeManager "-v"
Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:21 PM> <INFO> <Loading domains file: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains> Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:21 PM weblogic.nodemanager.server.NMServerConfig initDomainsMap Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: INFO: Loading domains file: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:21 PM> <WARNING> <Domains file not found: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains> Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:21 PM weblogic.nodemanager.server.NMServerConfig initDomainsMap Apr 22, 2011 3:23:21 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: WARNING: Domains file not found: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains Apr 22, 2011 3:23:22 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:22 PM> <INFO> <Loading identity key store: FileName=C:/Oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true> Apr 22, 2011 3:23:22 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:22 PM weblogic.nodemanager.server.SSLConfig loadKeyStoreConfig Apr 22, 2011 3:23:22 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: INFO: Loading identity key store: FileName=C:/Oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:23 PM> <WARNING> <Node manager configuration properties file 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.properties' not found. Using default settings.> Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM weblogic.nodemanager.server.NMServer <init> Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: WARNING: Node manager configuration properties file 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.properties' not found. Using default settings. Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:23 PM> <INFO> <Saving node manager configuration properties to 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.properties'> Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM weblogic.nodemanager.server.NMServer <init> Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: INFO: Saving node manager configuration properties to 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.properties' Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Node manager v10.3 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Configuration settings: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: NodeManagerHome=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: ListenAddress=win2008x64-2 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: ListenPort=7401 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: ListenBacklog=50 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: SecureListener=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: AuthenticationEnabled=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: NativeVersionEnabled=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: CrashRecoveryEnabled=false Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: JavaHome=C:\Oracle\MIDDLE~1\JROCKI~1.5-3\jre Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: StartScriptEnabled=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: StopScriptEnabled=false Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: StartScriptName=startEMServer.cmd Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: StopScriptName= Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogFile=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.log Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogLevel=INFO Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogLimit=0 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogCount=1 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogAppend=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogToStderr=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: LogFormatter=weblogic.nodemanager.server.LogFormatter Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: DomainsFile=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: DomainsFileEnabled=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: StateCheckInterval=500 Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: QuitEnabled=true Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Interface= Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: NetMask= Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: UseMACBroadcast=false Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: DomainRegistrationEnabled=false Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Domain name mappings: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:23 PM> <INFO> <Secure socket listener started on port 7,401, host WIN2008x64-2/192.168.182.135> Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: Apr 22, 2011 3:23:23 PM weblogic.nodemanager.server.SSLListener run Apr 22, 2011 3:23:23 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: INFO: Secure socket listener started on port 7,401, host WIN2008x64-2/192.168.182.135 Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Successfully launched the Node Manager. Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: The Node Manager process is running independent of the WLST process. Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Exiting WLST will not stop the Node Manager process. Please refer Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: to the Node Manager logs for more information. Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: The Node Manager logs will be under C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239 Apr 22, 2011 3:23:30 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: Connecting to Node Manager ... Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: <Apr 22, 2011 3:23:41 PM> <WARNING> <Configuration error while reading domain directory> Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess: weblogic.nodemanager.common.ConfigException: The domain 'GCDomain' at 'C:\Oracle\gc_inst\user_projects\domains\GCDomain' was not registered in the nodemanager.domains file and dynamic domain registration is not supported. Please register the domain in the nodemanager.domains file. Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess:      at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:257) Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess:      at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:224) Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess:      at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:108) Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess:      at weblogic.nodemanager.server.Handler.run(Handler.java:70) Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
FINE: NMProcess:      at java.lang.Thread.run(Thread.java:619) Apr 22, 2011 3:23:41 PM oracle.sysman.omsca.util.ProcessOutputReader run
...

I have a JDK already installed, but isn't JRockit being used by NodeManager in this case? Does NodeManager need to run on the JDK?
Regardless, I tried changing JavaHome in the nodemanager.properties file to the JDK/jre directory, but the log file still has the original path. The log seems to indicate that the process thinks that NodeManager is down because it can't connect, so it launches a new instance and uses default configuration parameters, which naturally wouldn't have my changes to the nodemanager.domain or nodemanager.properties files.
Also, the log says it can't connect to NodeManager at win2008x64-2:7,401. I'm not sure why there's a comma in there, but by the time this configuration step fails, there is a javaw.exe process listening on port 7401 and if I retry the step without killing it, the step will fail earlier because the port is already bound.

Okb9 configuration step

< MODERATOR: Message locked. Please read the [Rules of Engagement|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement] before posting next time. try and search first.>
hi guys,
pls send okb9 configuration step in sap r/3 6.0 version.
step by step.
thanks
rohit agrawal

< MODERATOR: Excellent answer. >
Hi,
Actually, there are not so many 'steps'. Just go to OKB9 and define your default CO objects for the G/L accounts.
Regards,
Eli

SAP Netweaver 7.3 PI Configuration Steps

Hi all,
        We have installed SAP Netweaver 7.3 PI in a separate server with server configuration of ,
       Windows 2008 64-BIT Server Enterprise edition.
       MS SQL Server 2008
       SAP Netweaver 7.3 PI
       24 GB RAM & 500 GB HDD.
       I request you to provide us the configuration steps for PI 7.3.
Regards,
Gopinath M.L

Hi Gopinath,
I am not sure if I got the point, but you can perform the post installation automatically by executing templates within NWA. But of course there is also a detailled description available how to do it manually (eg in case of problems). You can find these documentation under:
http://help.sap.com/saphelp_nw73/helpdata/en/48/a9b8c87e28674be10000000a421937/content.htm
Was this what you are searching for?
best regards,
Markus

Configuration steps SAP NW04 - BW 3.5

Hi,
Beside the material found in the SAP NW04 installation master guides, I would like to draw an exhaustive list of the required steps to configure a brand new SAP BW 3.5 system.
Assuming that one has just finished the technical installation, what are the necessary configuration steps and tips?
Any help on that topic would be greatly appreciated and rewarded - needless to say!
Best regards,
LauQ

Hi!
sap* is mostly used for installation steps and not for system copy..
if your system is just newlyinstalled and if you have no clients in your system other then the one delivered by sap like 000 .....then you need to copy 0000 via SCCL and then start doing tasks in this new client with a user who has simmilar authorizations as sap*
so you will maintian profile parameters only after the copy...and then define logical system
<i>"actually these steps are more clearly explained in installation guide for 3.0 than in instguid for 3.5"</i>
hope it helps
with regards
ashwin
Message was edited by: Ashwin Kumar Gadi

Error while configuration step for Oracle Customer MDM base pack

The second step of MDMCustomerBase Import seeddata is failing, in the configuration step of Oracle Customer MDM base pack
please help

Also In oracle AIA 11g configuration wizard the logs are as:
BUILD SUCCESSFUL
Total time: 2 minutes 5 seconds
'choice' is not recognized as an internal or external command,
operable program or batch file.
Step Prepare Properties file ended successfully
Step Prepare Properties file ended successfully
MDMCustomerBase Import Seeddata
Error
Failed to import Seeddata
Step MDMCustomerBase Import Seeddata failed
Failed to import Seeddata
Step MDMCustomerBase Import Seeddata failed
Log
Step MDMCustomerBase Import Seeddata started
Buildfile: AIAPLWImportData.xml
[echo] AIA HOME: E:\\\Middleware\AIAHome11g
[echo] AIA Instance: E:\\\Middleware\AIAHome11g/aia_instances/AIAIns11
[echo] Importing E:\\\Middleware\AIAHome11g\data\MDMCustomerBase\PLWSeedData\MDMCustomerBaseSeed.xml
all:
[echo] Executing /c E:\\\Middleware\AIAHome11g/Infrastructure/LifeCycle/PLWImExport/PLWImport.bat -f E:\\\Middleware\AIAHome11g\data\MDMCustomerBase\PLWSeedData\MDMCustomerBaseSeed.xml
[echo] Shell: cmd.exe
BUILD FAILED
E:\Middleware\AIAHome11g\Infrastructure\Install\AID\AIAPLWImportData.xml:48: exec returned: 1
Total time: 43 seconds
'choice' is not recognized as an internal or external command,
operable program or batch file.
Step MDMCustomerBase Import Seeddata failed
Failed to import Seeddata
Step MDMCustomerBase Import Seeddata failed

SAP DBM Configuration Steps

Hey Experts
Please let me know the basic configuration steps involved in SAP DBM. I'm from SD background and new to DBM.

Hi Hussain,
for needed settings in a DBM system find details in the configuration guide for DBM 8.0 which is the newest DBM version.
In online help DBM you can find more informations as installation master guide, release strategy note and application help and the configuration guide:
SAP Dealer Business Management 8.0 – SAP Help Portal Page
Best regards
Joachim

Step by step complete configuration document for SAP PM module

Can any body send me step by step complete configuration document for SAP PM module. If possible screen shots also. I will be highly obliged.
Indranil Chatterjee
Thanks in Advance.

Indranil,
It is not permitted for forum members to send documents to one another.
It is also expected that members will first perform their own research before asking for help. Did you search through SAP Help?
http://help.sap.com/saphelp_erp60_sp/helpdata/en/b2/4df35d51b811d192fb0000e829fbc6/frameset.htm
Best practices?
http://help.sap.com/bp_bl604/BL_IN/html/Content_Library_BL_EN_IN.htm
Best Regards,
DB49

SAP CIN configuration step - by- step material.

Dear Experts,
could you provide SAP CIN configuration step - by- step material.
thanks & regards,
vijay

Hi,
Please provide the same for me. I m also new in this.
Thanks
Kavita

How to configure oracle to SAP NETWEAVER DEVELOPER STUDIO STEP RAGARDING

hi
can u help me on this
i got problem
regarding configuring oracle to sap NetWeaver developer studio what i have deployed any thing studio
that would reflected to database
bye

Hi,
Check this,
WebDynpro and Oracle Connection
WebDynpro and Oracle Connection
Regards,
Vijayakhanna Raman

Risk Mgmnt COnfiguration steps

Hello Friends
Can anyone please tell me the complete steps to configure "Risk Management " with LoC (Letter of Credit) & what is the necessary data to be collected from the business, for configuring the same.
Regards
Sumanth.Gururaj

Hi,
The configuration steps for risk management
How To Do Configuration For Credit Management
Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.
An organizational unit that represents the area where customer credit is awarded and monitored.   This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
   Check which credit control area is assigned to the company code.
   Company code:
   Credit control area:
2. Transaction OVFL
   Check which credit control area is assigned to the sales area.
   Sales area:
   Credit control area:
3. Transaction XD02 or VD02
   Check which credit control area is assigned to the payer.
   Payer:
   Credit control area:
4. Transaction SE37
   Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
   For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
   Which settings do exist for the sales document type used?
   Sales document:
Check credit:
Credit group:
8. Transaction OVAD
   Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
   Credit management/Change risk category
   Definition of the risk category for each credit control area. This risk category can be assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
    Here, the individual credit checks for key fields
    o credit control area
    o risk category
    o credit group are set. Take these key fields from the above settings and go to the detail screen. In particular, check whether fields "Reaction" and "Status/block" are set correctly. To carry out follow-up actions in case of a credit block, the credit check status must be set (field "Status/block").
11. Transaction FD32
    Credit master data for the payer of the relevant document.
    Credit account:
    Credit limit:
    Risk category:
    Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit check (static or dynamic credit limit check).
13. Transaction OVA7
    Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
    field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
    In the pricing procedure used for pricing, subtotal "A" must be entered in a line for determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
    Which update group (field "Update") do you use in the relevant credit control area? The default setting is "12". If you use another update group, check whether this is fine with you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
    Which kind of update did you choose for structure S066?
     In any case, "Synchronous update (1)" has to be chosen as the kind of update. All other settings will lead to errors.
Credit Management Reports
The following table provides an overview of all the reports that are available for credit management:
Program     Function
RFDKLI10     Customers with Missing Credit Data
Checks whether the data regarding credit limits is complete and issues relevant error lists. These enable you to maintain the relevant definitions either manually or with batch input.
RFDKLI20     Reset Credit Limit for Customers
Resets the credit limit information in the control areas.
RFDKLI30     Credit Limit Overview
Lists the central and control area data for each customer.
RFDKLI40     Credit Overview
Provides a comprehensive overview of the customeru2019s credit situation.
RFDKLI41     Credit Master Sheet
Displays and prints the customer master data for an individual account that is needed for credit management.
RFDKLI42     Early Warning List
Displays and prints customers in Credit Management who have been listed by the credit check as critical.
RFDKLI50     Credit Limit Data Mass Change
Changes all the credit management master data together.
RFDKLIAB     Display Changes to Credit Management
Displays the changes to credit management master data for all accounts.
RVKRED06     Check Blocked Credit Documents
Checks all the documents blocked for credit reasons. The report is started in the background and should run after the incoming payments programs.
RVKRED77     Reorganize SD Credit Data
Reorganizes open credit, delivery and billing values. It can be used in the event of an update error, for example.
RVKRED08     Checking sales documents which reach the credit horizon
Rechecks all sales documents that fall within the credit limit horizon of the dynamic credit limit check. The report is run at regular intervals and should be run at the start of each period. The system uses the current date and the period split for the open order values to propose the u2018next credit check dateu2019.
RVKRED09     Check Credit Documentation Background
Checks released documents whose validity period of the release has been exceeded (number of days).
RVKRED88     Simulating Reorganization of SD Credit Data
To run a report:
1.     Choose System ® Services ® Reporting.
2.     Enter the name of the report.
3.     Choose Program ® Execute.
4.     Enter your selection criteria.
5.     Choose Program ® Execute or Program ® Execute and print.
SAP SD Credit Management Tcodes
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
SM30 - Table/View
u2022     V_TVTW - Define Distribution Channel
u2022     V_TVTA_KKB - Assign sales area to credit control area
u2022     V_T014 - FI - Define Credit Control Area
u2022     T001CM - FI - Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
                  Distribution Channel
                              Division
                  Distribution Channel
                              Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
u2022     Check Credit
o     A - Credit limit check and warning message
o     B - Credit limit check and error message (no sales order can    be created)
o     C - Credit limit check and delivery block (block delivery if hit   credit limit)
     Options B and C -> used for checking open order values (when you create/change the sales order)
o     D - Automatic credit control with open order values
     More control in transaction OVA8 - Automatic credit control
     You check for open orders and deliveries, or just open deliveries.
     or open order values with other options
u2022     Credit group
o     Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents - Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
u2022     whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
u2022     Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D - automatic credit check).
u2022     SAP default credit groups
o     01 - credit group for sales order
o     02 - credit group for delivery
o     03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items
You can have the followings credit limit check :-
u2022     Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
u2022     Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.
Max open items %
The customer balance must not exceed a certain percentage.
u2022     Oldest open items
If you don't want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
Dayu2019s oldest item
No of days allowed for overdue or payment terms.
Use of the credit checks Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be re-blocked again by the system. The system only re-blocks the sales document if the new order quantity is above a certain % amount.
u2022     Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
u2022     Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document date is in April then the credit limit is zero.
You can use the "NextReview date" and "Number of days" fields and combined it with the "Last int.review" field in customer credit master "Status" view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
SIMPLE CREDIT CHECK:
Tr.Code - FD32
It Considers the Doc.Value + Open Items.
Doc.Value: Sales Order has been saved but not delivered
Open Item: Sales Order has been saved, Delivered, Billed & Transferred to FI, but not received the payment from the customer.
Eg: Customer Credit Limit is Rs.1, 00,000/-
Suppose Doc.Value + Open Item Value is Rs.1,10,000/-
Here credit limit exceeds then system reacts.
Options: A) Warning Message
B) Error Message (Sales Order won't be saved)
C) Error Message with Delivery Block
AUTOMATIC CREDIT CHECK: Give extra credit facilities to the particular customer.
STATIC CREDIT LIMIT DETERMINATION: Checking Group + Risk Category + Credit Control Area.
A) Credit Checking Groups: Types of Checking Groups.
01) Sales
02) Deliveries
03) Goods Issue
At all the above 3 levels orders can be blocked.
B) Risk Category: Based on the risk Categories Company decides how much credit has to give to the customer.
HIGH RISK (0001) :      LOW CREDIT
LOW RISK (0002) :      MORE CREDIT
MEDIUM RISK(0003): AVERAGE CREDIT
Static Credit Check it checks all these doc value & check with the credit limit
1) Open Doc.Value / Sales Order Value: Which is save but not delivered
2) Open Delivery Doc.Value: Which is delivered but not billed
3) Open Billing Doc.Value: Which is billed but not posted to FI
4) Open Item: Which is transferred to FI but not received from the customer.
DYNAMIC CREDIT CHECK:
1) Open Doc
2) Open Delivery
3) Open Billing
4) Open Items
5) Horizon Period = Eg.3Months
Here the System will not consider the above 1,2,3& 4 values for the last 3 months
Then assign the Sales Doc & Del Documents.
Sales Doc.Type(OR) + credit Check (0) + Credit Group (01)
Credit Limit Check for Delivery Type : Del.Type (LF) + Del Credit
Group (02) + Goods Issue Credit Group (03)
User Exits For Credit Checks And Risk Management
Credit Check
I hope this will resolve your issue
Thanks
Anil Hooda

12c agent install fails with error - The plug-in configuration for the oracle.sysman.oh monitoring plug-in may have failed

Hi,
I am trying to install 12c agent on windows 7 64 bit server by following m.note .
It is failing with Agent Configuration failed, please see below error message.
INFO: length of temp is2
INFO: Return value:C:\/Oracle/12.1.0.3.0_AgentCore_233/core
INFO: ** Agent Port Check completed successfully.**
INFO: ERROR: The Management Agent configuration failed. The plug-in configuration for the oracle.sysman.oh monitoring plug-in may have failed, or this plug-in may not be present in the Management Agent software. Ensure that the Management Agent software has the oracle.sysman.oh monitoring plug-in, if not then retry the operation. If the agent software has the oracle.sysman.oh monitoring plug-in, view the plug-in deployment log C:\Oracle\12.1.0.3.0_AgentCore_233\core\install\logs to check if the plug-in configuration for the oracle.sysman.oh monitoring plug-in failed.
INFO:
INFO: perform - mode finished for action: configure
INFO:
INFO: You can see the log file: C:\Oracle\12.1.0.3.0_AgentCore_233\core\12.1.0.3.0\cfgtoollogs\oui\configActions2014-10-03_08-48-15-AM.log
INFO:
INFO: C:\Oracle\12.1.0.3.0_AgentCore_233>exit /b 3
INFO: Plugin homes:
INFO: Plugin homes:
INFO: C:\Oracle\12.1.0.3.0_AgentCore_233\core\12.1.0.3.0\oui\bin\runConfig.bat ORACLE_HOME=C:\Oracle\12.1.0.3.0_AgentCore_233\core\12.1.0.3.0 RESPONSE_FILE=C:\Oracle\12.1.0.3.0_AgentCore_233\core\12.1.0.3.0\agent.rsp ACTION=configure MODE=perform COMPONENT_XML={oracle.sysman.top.agent.11_1_0_1_0.xml} RERUN=true completed with status=3
SEVERE: ERROR: Agent Configuration Failed
Thanks,

Looks like , J2EE is having a problem connecting to the DB.Pls. chk. the following
-If you have configured the loop-back adapter , if installing on a local system & updated the /etc/host file with your ip address and host name.
or if the system is part of some n/w group and has ip address assigned ?
-Jdk 1.4 version is installed in your system
-Enough free Disk space available in the system
-How much RAM your system has which windows version you are using ?
-Is the DB is coming up properly ? its error related to this. check the logs.
-If the ports used by sap install / run used by other services running on the system ? & user have admin. privileges on the system .
Pls. update with your findings on above same , for the step next ...
Thanks ,
Uppal

Error at DB downtime configuration step in SAP installation

Similar Messages

Maybe you are looking for