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

Similar Messages

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

SAP HR Configuration Steps

Hey Guys, I am an ABAPer trying to get into HR Functional. I got trained on OM,PA, TM and Payroll, obviously the documentation I received is not good enough. Could anyone please send me the step-by-step configuration of the HR modules to my email Id [email protected]
Thanks in advance and appreciate all the good work.... Jennifer

Hello,
Few useful links...
http://www.sap-img.com/sap-hr.htm
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci1030179,00.html
http://help.sap.com/saphelp_erp2005/helpdata/en/74/df293581dc1f79e10000009b38f889/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/80/ea89395eb58c4f9d0c3e837cf0909d/frameset.htm

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

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

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

Step by step SAP EDI Configuration

Hi,
Can you please shar step by step SAP EDI Configuration deatils.
Regards,
Nitin Patil

Hi
Seeburger EDI Adapter leverages SAP XI's Adapter Framework. This Adapter is used to perform conversion between EDI and XML format. It also provides some canned EDI layouts and the ability to build your own. It is used to transfer the EDI message via HTTP or AS2 protocols.
The most direct way of using the Seeburger adapters is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to do the following:
1. define or import the inbound message metadefinition in various formats ( edifact, xml,...)
2. using a mapping create an xml variant as the output metadefinition or edifact in the other direction.
3. create a one to one mapping between input en output.
4. export the metadata in xsd or sda format for import in XI
5. generate an SDA which can be deployed in XI and used as a module.
Please go through the following links which clearly explains what you want and it also helps you in understanding the same in depth:
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Integrating XI with SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
Thoughts on EDI in an SAP XI Environment
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a
regards,
Kishore

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

Steps of learning SAP MM configuration

Dear gurus,
I have some questions,
For learning SAP-MM configuration :-
1) What is the sequence of configuration so that u can use system for further application ( Pl. note this is only learning & not standard configuration for any client)
2) What care /precautions should I take to go ahead?
Please forward the related material to following ID
[email protected]
Thanks in advance,
NB

Link: http://help.sap.com/
Path: SAP Best Practices --> Baseline Packages --> Based on SAP ECC 5.00 --> Select Country: for eg, Localized for India --> Technical Information --> Building Blocks --> Select Country for eg, India --> List of Basic Configuration & scenarios will be listed.
<b>J05: Materials Management</b>
Select the required basic configuration / scenario. These will consist of overview, configuration guide, business process, master data &so on ...........
Regards,
Rajesh Banka
Reward suitable points.
How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

SAP ME 15 Installation error in CTC SAP ME Configuration

Hi,
We are doing an SAP ME 15 installation and are getting an error during CTC
for "SAP ME Configuration for installation" during step 6 of 7 "Create or update Global site".
All the JDBC Datasources for VMJDBC are green and working.
From the default trace log I can see this:
#2.0 #2014 10 07 12:36:47:020#+0200#Error#com.sap.tc.lm.ctc.cul.serviceimpl.process.InvokeServiceControllerDefault#
#BC-INS-CTC#tc~lm~ctc~cul~core_sda#C000AC117450002A00000013000002F4#7447350000000004#sap.com/tc~lm~itsam~ui~mainframe~wd#com.sap.tc.lm.ctc.cul.serviceimpl.process.InvokeServiceControllerDefault#Administrator#1##693380984E0C11E49BBF00000071A336#290bfa2c4e0811e4c25d0050569c1b6e#290bfa2c4e0811e4c25d0050569c1b6e#0#Thread[Thread-49,5,Dedicated_Application_Thread]#Plain##
Service execution error; invocation target error when calling method createAndUpdateGlobalSite in class com.sap.me.ctc.services.idat.GlobalSiteConfiguration of component sap.com/xapps~me~ctc~ear (error message = com.sap.me.frame.domain.BusinessRuntimeException: java.lang.NullPointerException: while trying to invoke the method java.util.List.clear() of a null object loaded from field com.sap.sql.jdbc.vendor.VendorPooledConnection.openStatements of an object loaded from local variable 'this')
[EXCEPTION]
com.sap.tc.lm.ctc.cul.api.CULServiceException: Service execution error; invocation target error when calling method createAndUpdateGlobalSite in class com.sap.me.ctc.services.idat.GlobalSiteConfiguration of component sap.com/xapps~me~ctc~ear (error message = com.sap.me.frame.domain.BusinessRuntimeException: java.lang.NullPointerException: while trying to invoke the method java.util.List.clear() of a null object loaded from field com.sap.sql.jdbc.vendor.VendorPooledConnection.openStatements of an object loaded from local variable 'this')
at com.sap.tc.lm.ctc.cul.broker.BrokerServiceExecuter.executeService(BrokerServiceExecuter.java:61)
at com.sap.tc.lm.ctc.cul.serviceimpl.executor.CULServiceExecutor.executeService(CULServiceExecutor.java:36)
at com.sap.tc.lm.ctc.cul.serviceimpl.process.InvokeServiceControllerDefault.execute(InvokeServiceControllerDefault.java:133)
at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.remoteOrLocalExecution(ProcessControllerImpl.java:741)
at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:286)
at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessExecuter.run(ProcessExecuter.java:156)
at java.lang.Thread.run(Thread.java:763)
Caused by: com.sap.tc.lm.ctc.provider.javaServiceProvider.exceptions.CPIServiceExecutionException: Service execution error; invocation target error when calling method createAndUpdateGlobalSite in class com.sap.me.ctc.services.idat.GlobalSiteConfiguration of component sap.com/xapps~me~ctc~ear (error message = com.sap.me.frame.domain.BusinessRuntimeException: java.lang.NullPointerException: while trying to invoke the method java.util.List.clear() of a null object loaded from field com.sap.sql.jdbc.vendor.VendorPooledConnection.openStatements of an object loaded from local variable 'this')
at com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaMethodExecuter.invoke(JavaMethodExecuter.java:291)
at com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaServiceExecuter.executeService(JavaServiceExecuter.java:86)
at com.sap.tc.lm.ctc.cul.broker.BrokerServiceExecuter.executeService(BrokerServiceExecuter.java:59)
... 6 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaMethodExecuter.invoke(JavaMethodExecuter.java:259)
... 8 more
Caused by: com.visiprise.frame.service.ext.ExtensionExecutionException: com.sap.me.frame.domain.BusinessRuntimeException: java.lang.NullPointerException: while trying to invoke the method java.util.List.clear() of a null object loaded from field com.sap.sql.jdbc.vendor.VendorPooledConnection.openStatements of an object loaded from local variable 'this'
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.handleExtensionException(GenericServiceExecutionProcess.java:174)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeExtension(GenericServiceExecutionProcess.java:158)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeExtensions(GenericServiceExecutionProcess.java:125)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.execute(GenericServiceExecutionProcess.java:97)
at com.visiprise.frame.service.ext.TransactionDecoratorSupport.execute(TransactionDecoratorSupport.java:86)
at com.sap.me.frame.service.BaseTransactionExecutionProcess.execute(BaseTransactionExecutionProcess.java:95)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)
at com.sun.proxy.$Proxy916.execute(Unknown Source)
at com.visiprise.frame.service.ext.ServiceExecutionInterceptor.intercept(ServiceExecutionInterceptor.java:44)
at com.sap.me.frame.service.BusinessServiceExecutionInterceptor.intercept(BusinessServiceExecutionInterceptor.java:57)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.GenericSOProxy.invoke(GenericSOProxy.java:81)
at com.sun.proxy.$Proxy1546.loadInitialData(Unknown Source)
at com.sap.me.plant.impl.SiteConfigurationService.createGlobalSite(SiteConfigurationService.java:397)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.visiprise.frame.proxy.DefaultInterceptor.intercept(DefaultInterceptor.java:31)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.ProxyContext.process(ProxyContext.java:67)
at com.visiprise.frame.service.ext.MethodInvocationActivity.execute(MethodInvocationActivity.java:34)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeActivity(GenericServiceExecutionProcess.java:202)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeService(GenericServiceExecutionProcess.java:136)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.execute(GenericServiceExecutionProcess.java:94)
at com.visiprise.frame.service.ext.TransactionDecoratorSupport.execute(TransactionDecoratorSupport.java:86)
at com.sap.me.frame.service.BaseTransactionExecutionProcess.execute(BaseTransactionExecutionProcess.java:95)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)
at com.sun.proxy.$Proxy916.execute(Unknown Source)
at com.visiprise.frame.service.ext.ServiceExecutionInterceptor.intercept(ServiceExecutionInterceptor.java:44)
at com.sap.me.frame.service.BusinessServiceExecutionInterceptor.intercept(BusinessServiceExecutionInterceptor.java:57)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.GenericSOProxy.invoke(GenericSOProxy.java:81)
at com.sun.proxy.$Proxy1546.createGlobalSite(Unknown Source)
at com.sap.me.ctc.services.idat.GlobalSiteConfiguration.createAndUpdateGlobalSite(GlobalSiteConfiguration.java:191)
... 13 more
Caused by: com.sap.me.frame.domain.BusinessRuntimeException: java.lang.NullPointerException: while trying to invoke the method java.util.List.clear() of a null object loaded from field com.sap.sql.jdbc.vendor.VendorPooledConnection.openStatements of an object loaded from local variable 'this'
at com.sap.me.common.impl.DynamicInvocationService.invoke(DynamicInvocationService.java:76)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.visiprise.frame.proxy.DefaultInterceptor.intercept(DefaultInterceptor.java:31)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.ProxyContext.process(ProxyContext.java:67)
at com.visiprise.frame.service.ext.MethodInvocationActivity.execute(MethodInvocationActivity.java:34)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeActivity(GenericServiceExecutionProcess.java:202)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeService(GenericServiceExecutionProcess.java:136)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.execute(GenericServiceExecutionProcess.java:94)
at com.visiprise.frame.service.ext.TransactionDecoratorSupport.execute(TransactionDecoratorSupport.java:86)
at com.sap.me.frame.service.BaseTransactionExecutionProcess.execute(BaseTransactionExecutionProcess.java:95)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)
at com.sun.proxy.$Proxy916.execute(Unknown Source)
at com.visiprise.frame.service.ext.ServiceExecutionInterceptor.intercept(ServiceExecutionInterceptor.java:44)
at com.sap.me.frame.service.BusinessServiceExecutionInterceptor.intercept(BusinessServiceExecutionInterceptor.java:57)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.GenericSOProxy.invoke(GenericSOProxy.java:81)
at com.sun.proxy.$Proxy1578.invoke(Unknown Source)
at com.sap.me.common.impl.XmlInvocationService.invokeConfigLoad(XmlInvocationService.java:695)
at com.sap.me.common.impl.XmlInvocationService.loadApplicationConfiguration(XmlInvocationService.java:174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.visiprise.frame.proxy.DefaultInterceptor.intercept(DefaultInterceptor.java:31)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.ProxyContext.process(ProxyContext.java:67)
at com.visiprise.frame.service.ext.MethodInvocationActivity.execute(MethodInvocationActivity.java:34)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeActivity(GenericServiceExecutionProcess.java:202)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeService(GenericServiceExecutionProcess.java:136)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.execute(GenericServiceExecutionProcess.java:94)
at com.visiprise.frame.service.ext.TransactionDecoratorSupport.execute(TransactionDecoratorSupport.java:86)
at com.sap.me.frame.service.BaseTransactionExecutionProcess.execute(BaseTransactionExecutionProcess.java:95)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)
at com.sun.proxy.$Proxy916.execute(Unknown Source)
at com.visiprise.frame.service.ext.ServiceExecutionInterceptor.intercept(ServiceExecutionInterceptor.java:44)
at com.sap.me.frame.service.BusinessServiceExecutionInterceptor.intercept(BusinessServiceExecutionInterceptor.java:57)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.GenericSOProxy.invoke(GenericSOProxy.java:81)
at com.sun.proxy.$Proxy1535.loadApplicationConfiguration(Unknown Source)
at com.sap.me.plant.impl.ConfigDataLoader.execute(ConfigDataLoader.java:103)
at com.sap.me.plant.impl.ConfigDataLoader.execute(ConfigDataLoader.java:77)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeActivity(GenericServiceExecutionProcess.java:202)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeExtension(GenericServiceExecutionProcess.java:153)
... 94 more
Caused by: java.lang.NullPointerException: while trying to invoke the method java.util.List.clear() of a null object loaded from field com.sap.sql.jdbc.vendor.VendorPooledConnection.openStatements of an object loaded from local variable 'this'
at com.sap.sql.jdbc.vendor.VendorPooledConnection.invalidate(VendorPooledConnection.java:352)
at com.sap.sql.jdbc.vendor.VendorPooledConnection.destroyConnection(VendorPooledConnection.java:317)
at com.sap.sql.connect.datasource.DBDataSourceImpl.closePooledConnection(DBDataSourceImpl.java:737)
at com.sap.sql.connect.datasource.DBDataSourceImpl.destroy(DBDataSourceImpl.java:1043)
at com.sap.sql.connect.datasource.DBDataSourceImpl.destroy(DBDataSourceImpl.java:45)
at com.sap.sql.connect.pool.CreatedObjectsPool.destroy(CreatedObjectsPool.java:140)
at com.sap.sql.connect.pool.Pool.release(Pool.java:558)
at com.sap.sql.connect.datasource.DBDataSourceImpl.releasePooledConnection(DBDataSourceImpl.java:914)
at com.sap.sql.connect.datasource.PooledConnectionHandle.close(PooledConnectionHandle.java:59)
at com.sap.engine.services.dbpool.spi.XAManagedConnectionImpl.destroy(XAManagedConnectionImpl.java:70)
at com.sap.engine.services.connector.jca.ConnectionHashSet.destroy(ConnectionHashSet.java:450)
at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:359)
at com.sap.engine.services.connector.jca.ShareableConnectionManager.allocateConnection(ShareableConnectionManager.java:54)
at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:52)
at com.sap.me.frame.AbstractDataSource.getDBConnection(AbstractDataSource.java:413)
at com.sap.me.frame.AbstractDataSource.executeQuery(AbstractDataSource.java:142)
at com.sap.me.frame.BaseDataSource.executeQuery(BaseDataSource.java:197)
at com.sap.me.frame.BaseDataSource.recordExists(BaseDataSource.java:830)
at com.sap.me.frame.AuditLogHandler.createAL(AuditLogHandler.java:129)
at com.sap.me.frame.AuditLogHandler.performAuditLogWork(AuditLogHandler.java:953)
at com.sap.me.frame.dao.AuditLogListener.performAuditLog(AuditLogListener.java:62)
at com.sap.me.frame.dao.AuditLogListener.afterCreate(AuditLogListener.java:29)
at com.sap.me.frame.dao.CompositeLifeCycleListener.afterCreate(CompositeLifeCycleListener.java:83)
at com.sap.me.frame.dao.ProductionDataAccessService.create(ProductionDataAccessService.java:193)
at com.sap.me.frame.dao.DomainDataAccessService.create(DomainDataAccessService.java:65)
at com.sap.me.frame.dao.DomainDataAccessService.create(DomainDataAccessService.java:30)
at com.sap.me.frame.domain.DefaultDomainService.create(DefaultDomainService.java:96)
at com.sap.me.activity.impl.ExtensionConfigurationService.createExtensionPoint(ExtensionConfigurationService.java:243)
at com.sap.me.activity.impl.ExtensionConfigurationService.createExtensionLocal(ExtensionConfigurationService.java:962)
at com.sap.me.activity.impl.ExtensionConfigurationService.createExtensionByCreateExtensionRequest(ExtensionConfigurationService.java:230)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.visiprise.frame.proxy.DefaultInterceptor.intercept(DefaultInterceptor.java:31)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.ProxyContext.process(ProxyContext.java:67)
at com.visiprise.frame.service.ext.MethodInvocationActivity.execute(MethodInvocationActivity.java:34)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeActivity(GenericServiceExecutionProcess.java:202)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.executeService(GenericServiceExecutionProcess.java:136)
at com.visiprise.frame.service.ext.GenericServiceExecutionProcess.execute(GenericServiceExecutionProcess.java:94)
at com.visiprise.frame.service.ext.TransactionDecoratorSupport.execute(TransactionDecoratorSupport.java:86)
at com.sap.me.frame.service.BaseTransactionExecutionProcess.execute(BaseTransactionExecutionProcess.java:95)
at sun.reflect.GeneratedMethodAccessor454.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)
at com.sun.proxy.$Proxy916.execute(Unknown Source)
at com.visiprise.frame.service.ext.ServiceExecutionInterceptor.intercept(ServiceExecutionInterceptor.java:44)
at com.sap.me.frame.service.BusinessServiceExecutionInterceptor.intercept(BusinessServiceExecutionInterceptor.java:57)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.GenericSOProxy.invoke(GenericSOProxy.java:81)
at com.sun.proxy.$Proxy1581.createExtensionByCreateExtensionRequest(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:57)
at sun.reflect.GeneratedMethodAccessor47.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:260)
at java.beans.Statement.invokeInternal(Statement.java:239)
at java.beans.Statement.access$000(Statement.java:39)
at java.beans.Statement$2.run(Statement.java:140)
at java.security.AccessController.doPrivileged(Native Method)
at java.beans.Statement.invoke(Statement.java:137)
at java.beans.Expression.getValue(Expression.java:98)
at com.sap.me.common.impl.DynamicInvocationService.invoke(DynamicInvocationService.java:64)
... 188 more
Best regards,
Johan

Hi Chandrababu,
Unfortunately I don't know any more than this. I have only done one SAP ME 15 installation so far
and this was the solution to our error situation.
If you don't get it working then you should log a support ticket to SAP.
Best regards,
Johan

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

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

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

SAP DBM Configuration Steps

Similar Messages

Maybe you are looking for