Configuration steps in biw

What are the configeration steps to configure BIW in ECC6.0
The following questions are only relates to ECC6
1) How to define source system?
2) Assign client to logical system?
3) How to setup the BIW menu as easy acces?

hi ramesh,
Technically it is possible to use BIW in an ECC 6.0 instance. You need to install BI_CONT 704 to use SAP contents. Its not recommend to use BW in ECC. SAP recommends different systems for BW and R/3. So better go for different systems.
regards,
raghu.

Similar Messages

OBIEE 11g installation failed multiple times at Distributing Repository Configuration Step

Hi,
I am getting the following error during the Distributing Repository Configuration step in the OBIEE 11g 11.1.1.7 enterprise installation in Windows 8 system.
Severe: Element Type:Domain
Element id: null
Operation result: failed to obtain domain file lock
Detail Message: java.util.concurrent.timeoutException.Timeout;
waiting for lock: Domain config lock;
c:\OBIEE\MIDDLE~1\USER_p~1\domains\EAM_DO~1\config\FMWCON~1\biee-config.lock;[121 secs]
Step Distributing Repository failed
Configuration Action 'Distributing Repository' has failed. Please check logs for details.
Step Distributing repository failed
I checked another blog for this https://forums.oracle.com/thread/2565716 and even there the explanation doesn't convince me.
I tried to look at the Locale of my system where I am installing and I could see it is using Eng-Us by default. One way suggested to check the Unicode format from the web browser and I could check that too to be UTF-8 as suggested by someone on some other blog.
I checked in the logs too as suggested by the Installation dialogue box but it didn't seem much conclusive too.
Here is the snapshot of the log file which I could found.
INFO: Current Inventory:
Oracle Home: OraDb11g_home1
This Oracle Home has not been changed in this session.
Oracle Home: OH1858390736
This Oracle Home has not been changed in this session.
Oracle Home: OH440082373
This Oracle Home has not been changed in this session.
Oracle Home: OH440082374
This Oracle Home has not been changed in this session.
Oracle Home: OH1597391518
This Oracle Home has not been changed in this session.
Oracle Home: OH1285215443
This Oracle Home has not been changed in this session.
INFO: Ending the inventory Session
INFO: Using an existing InstallAreaControl for this Inventory Session with existing access level 1
INFO: Using an existing InstallAreaControl for this Inventory Session with existing access level 1
INFO: Using an existing InstallAreaControl for this Inventory Session with existing access level 1
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
INFO: The ORACLE_CONFIG_HOME env var is set to
Can someone please help me with this since I am stuck with for quite some time now.
Is there any way to check in command prompt to check the locale as required by the system.
What could be the issue here?
Thanks,
Nitin

Hi all,
We are able to resolve the above issue with the below solution.
Root cause of the issue:
You may have a temp directory in the path C:\Documents and Settings\user_name\Local Settings\Temp. You got the above mentioned exception because of the temp directory path having spaces_+ in it.
Solution:
1. Create a new directory called TEMP in a different location for ex: C:\TEMP
2. Now, Right click on My computer --> Properties --> Advanced --> click on Environment Variables.
3. You should be having TEMP and TMP as variables under user variables section pointing to the C:\Documents and Settings\user_name\Local Settings\Temp path.
4. Edit the TEMP and TMP variables and mention C:\TEMP in the variable value.
5. Deinstall and re-install OBIEE 11g.
Happy OBIEE 11g installation!!
Thanks,
Rajesh Gurram

Product costing by sales order configuration steps

hi
plz send me product costing by sales order configuration steps.
sir, i know manufacturing order configuration step but i do not sales order configuration.
in the sales order also is same as manufacturing order like first we have to make planning cost , the planning cost should be updated to material master and next configure the actual cost.
for first step- costing variant -okkn
next -costing variant -opl1
for sales order also same we need to update planning price first- what is costing variant
for actual cost - what is costing variant
plz tell me detail
regards,
sowmya
Moderator: Please, read forum rules before posting

Hi Sashikanth,
Please send me the Configuration document for make to sales order.We are at Blue print stage need some docment for make to sales order.Plese send me the document it will will be very help full for me.
My id is [email protected]
Thanks in advance
Regards,
Nagaraju
Edited by: nagaraju sami on Mar 9, 2008 11:58 AM

Which driver to use in the BPM Configuration Steps?

Hi,
I´m in the BPM configuration steps and we will use BPM on a Weblogic Server, I´m in the step when you need to create to JDBC Data Sources for the Enterprise and Directory Databases, do you know which driver shoul I use? should it be XA o Non-XA?
Thanx in Advanced!
Kind Regards,
Gerardo J

Since there are no drivers, you can create your own, request one, use the Instrument I/O Assistant, or hope someone has one and posts it here. For help on creating one or requesting one, see the main Instrument Driver Network page. As long as you are familiar with the instrument and have the manual, creating a driver is not that hard.

Configuration steps for Extended Classic Scenario

Hi All,
Could you please let me know what are the configuration steps required for extended classic scenario.
Thanks in advance

Hi,
Important Settings that Determine the Extended Classic Scenario
The following settings are required for the extended classic scenario:
u2022 At least one backend materials management system and accounting system is connected to the SAP SRM system and defined in the configuration setting Define Backend Systems.
u2022 Product categories from the backend procurement system are replicated and used in the SAP SRM system.
u2022 The target system for each product category is the backend system in the configuration setting Define Backend Systems for Product Category. Optionally, BADI BBP_DETERMINE_LOGSYS is implemented to determine the backend system.
u2022 The extended classic scenario is activated in the configuration setting Activate Extended Classic Scenario. Alternatively, BAdI BBP_EXTLOCALPO_BADI is implemented to control the extended classic scenario based on customer defined rules.
u2022 If the backend system is an SAP R/3 version lower than 4.6B, you must define local purchasing organizations and purchasing groups.
u2022 If the backend system is an SAP R/3 version 4.6B or higher, you need to map the purchasing group used in the purchase order to the backend purchase group in one of the following ways:
u2022 Use a backend purchasing organization and purchasing group in the shopping cart and purchase order.
u2022 Use BAdI BBP_PGRP_FIND to determine a backend purchasing group in the shopping cart.
u2022 If a local (created in SAP SRM without reference to a backend system) purchasing group and purchasing organization are used, then a valid backend purchasing group is assigned to the RFC user that created the backend purchase order. This assignment is made in the backend system using user parameter EKG in Transaction code SU01.
u2022 Implement the user exit of the BAPIs BAPI_PO_CREATE1 (EXIT_SAPL2012_001 and EXIT_SAPL2012_003), and BAPI_PO_CHANGE (EXIT_SAPL2012_002 and EXIT_SAPL2012_004) to determine the purchasing group with a customer- specific logic.
This is for your additional information.
Hope this helps.
Regards,
Vikas

Configuration steps to create New Special GL

HI,
Can any one please send me configuration steps to create New Special GL. My client required to create new special GL for Rent Advance.
NOTE: hear I am not asking how configuration steps for assigning GL accounts for existing Special GL. I want new Special GL to be Create for rent advance.
Its very urgent
My mail id "[email protected]"
Thank you
mahesh

Hi,
go to transaction code fbzp where you assign GL account to the spl GL indicator.
Go and create a new spl GL indicator there by clicking create new.
Bye

Give me the Configuration steps for intercompany billing and third party s

Hi Gurus,
Give me the Configuration steps for intercompany billing and third party sales and give me a brief description with examples.
Regards,
YSR

Dear YSR
Check the links
[Cross Company Configuration|http://help.sap.com/bp_bblibrary/500/Documentation/J62_BB_ConfigGuide_EN_DE.doc]
[Third Party Without Shipping Notification|http://help.sap.com/bestpractices/BBLibrary/html/J55_ThirdPartyWOSN_EN_US.htm]
Third party order processing is as follows:
Assume three companies X, Y and Z
X - The company,
y - The customer
Z - Vendor
When ever X gets a PO from Y to supply some goods, X has an option of either manufacturing those goods or procuring those goods.
If he is procuring the goods, there are two methods that are generally followed:
Method 1)
After receiving the PO from Y, X creates a sales order against Y.
Now at the same time he also creates a PO to a vendor Z to produce the goods
Z produces the goods and supplies to X
X receives the goods from Z
Then X delivers the same goods to Y.
After that X invoices Y and Z invoices X.
Note : Here there is no direct/ Indirect relation between Z and Y.
This process is known as Trading Process. and the Material here is created with Material type HAWA.
The other method is a Third party order processing method:
Here the glaring difference is that instead of Z supplying the material to X and X in turn supplying the same material to Y.
X authorizes Z to supply the material to Y on his behalf and notify him once the delivery is complete.
Now Z supplies the material to Y and acknowledges the same to X.
Z will send a copy of delivery acknowledgement and invoice to X.
After receiving the delivery confirmation and invoice from Z, X has to verify the invoice and this process is known as invoice verification and is done in SAP through Tcode MIRO.
The next step for X is to create an invoice and submit to Y
Only after the invoice verification document is posted then only X can create an invoice for Y.
This is the business flow that is followed for third party order configuration.
There are few steps that have to be configured to enable the system to function as mentioned above.
Step1)
If you are always followwing a third party process for a material then you have to create the material using item category group BANS.
The procument type should be marked as External procurement (F) in MRP 2 view of the material master record.
if you are not always allowing third party order processing then u can create a material master record with item category group as NORM and the procurement type should be marked as ( X) meaning both types of procurment ( in house manufacturing and external procurement).
Step 2)
the item category in the order should be manually changed as TAS.
For that you need to confugure the item category determination
ord type + item cat grp + usge + Hiv level = Item cat + Manual item cat
OR + NORM + + = TAN . + TAS
OR + BANS + + = TAS
Step 3)
make sure that during the item category configuration for TAS you need to mark relevnat for billing indicator as F
Step 4)
The schedule line cateogry for this type should be CS.
make sure that you mark subsequent type as NB - purchase requisition in this schedule line category as this will trigger the purchase requision order immediately after the creation of the sales order and the PO to vendor is created against this purchase requiesion.
thanks
G. Lakshmipathi

Business partner configuration steps in treasury

Reqiure Business partner configuration steps in treasury.
While creating business partner i get the message :Personal address doesnot exist.
How to rectify this?

No reply.Closed.

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

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.

Configuration Steps for Decentralized Adapter Engine

Hi all,
What all configuration steps are required to make Adapter Engine as
Decentralized AE.
I have made required changes in SLD DataSupplier in Visual Administrator.
what more configurations have to be done? On SAP XI Server and Decentralized
Adapter Engine.
With regards
Prasad

Prasad,
After configuring SLD data supplier in Visual Admin, you need to the following
1) Configure the gateway service for the central integration server on adapter engine host.
2) Perform Initial adapter engine cache refresh
3) Trigger data transfer to SLD
4) Check the connection parameters in exchangeProfile
5) Create HTTP destination pmistore in java environment
you have to go through all these tests for decentralized adapter engine. If you have XI configuration guide, it has all these steps in detail for you to configure
--Archana

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

Cash management(configuration steps need to generate report)

dear guru's
please help to generate cash management reports
please tel me configuration steps and all to generate cash flow and liquidity forecast
thanking u

Hi
Funds management :
Funds Management allows management to set budgets for revenues and expenses within your company as well as track these to the area of responsibility.
http://ot.bloomu.edu/Documents/SAP/Word%20Docs/New/SAPReportsJan2006.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/FIFM/FIFM.pdf
nagesh

Configuration steps for split valuation

Dear Gurus,
I have completed following steps in MM configuration.
A.Defining Enterprise structure
A1. Defining controlling areas
A1. Defining Plants
A3. Defining Storage Locations for Plants
A4. Defining Purchase Organization
A5. Assigning Purchase Organization to Plants
A6. Assigning Plants to company code
A7. Assigning purchasing organisation s to company code
A8. Assigning purchasing organisation s to plant
A9. Creating Purchase Groups
Now I am facing problem in Split evaluation.I am not able to create create valuation class & valuation type.
What is the role of split valuation ?
What are the configuration steps for split valuation?
Can anybody guide me on this/
Thanks & regards,
NB

Hi NB
A fruit company is importing apple from America & Europe. The price of apple imported from America is Rs.10 per Kg. The apple imported from Europe is Rs.15 per Kg. How do they maintain material master for Apple with two prices..?
A chemical factory produces methanol. The cost of methanol produced internally is Rs.20 per liter. But due to high production they purchases methanol from outside at Rs.30 per liter. How do they maintain material master for methanol with two prices..?
Petrol bunks have different varieties of petrol. Hi speed petrol costs Rs.52 and ordinary petrol costs Rs. 47. How do they maintain material master for petrol with two prices..?
If your answer is to maintain two material codes i.e. one for apple-America & one for apple-Europe then you are wrong. If your answer is Split Valuation, then you are right.!
Steps:
We have to activate split valuation if you want to use split valuation. But by default split valuation is Active.To activate the split valuation:
tcode OMW0.
To differentiate between material stocks, you must define valuation category and valuation type.
The valuation category specifies which criterion should be used as the basis for differentiating between the various partial stocks.
The valuation type specifies an individual characteristic of a partial stock.
Go to tcode OMWC, create global types, then global category. assign global types to global categ. and then attach them to valuation area(plant).
regards
Yogesh

Configuration steps for Infotype 0315

Hi ,
My client need to maintain Time sheet data for there employees.for that they need to maintain Infotye 0315.
Pls let me know what is infotype 0315 (Detailed description) & what are the configuration steps for infotype 0315.How to configure that Infotype .What are the pre-requsite steps to configure infotype 0315.Kindly
let me know
<< Moderator message - Everyone's problem is important. But the answers in the forum are provided by volunteers. Please do not ask for help quickly. >>
Edited by: Rob Burbank on Jan 17, 2011 4:22 PM

Dear SC,
Infotype 0315 is to make default values in terms of cost center , profile...etc...which will be picked up when you enter time data in CATS.....you can make the infotype called included in infogroup and get it filled at the time of performing initial action......
Configuration steps are for the CATS profile and other things not for infotype 0315...
regds

Configuration steps in biw

Similar Messages

Maybe you are looking for