Getting error in Vehicle Master creation in DBM7.0

Hi,
We are trying to create vehicle master in DBM 7.0 with tcode /dbm/vm. We are getting this error just after we entered tocde /dbm/vm
"Authorizations or Customizing settings for profile are missing
Message no. /DBM/VEHICLE_MASTER013"
SAP user id has SAP_ALL rights.
SAP Env: SAP ECC 6.0 EHP4
                DBM 7.0 SPS02
                SAPKH60402
                SAPKB70103
                SAPKA70103
Please letus know how to resolve this issue.
Thanks
Rehan

Hi Sachin,
Check your customizing settings in DBM:
spro->Logistics execution->DBM->Vehicle->Vehicle Master-> Navigation on Vehicle Master
->Navigation profile determination-> Assign navigation profile
Depending on conditions please assign relevant navigation profile.
The standard settings look like as follow:
DBM/VEHPRO/CTL3                /DBM/VM               INIT
                                                 /DBM/VMN              INIT
                                                 /DBM/VM_LEAN     INITLEAN
DBM/VEHPRO/CTRL              DBM_PASSENGERCAR   01    DBM1
DBM/VEHPRO/CTL2              DBM_PASSENGERCAR DBM1
Please consider also note 1968452.
Regards
Joachim

Similar Messages

Vehicle Master creation

Hi,
I have started to learn DBM, need your help guys.
I am creating a Vehicle master, after entering the data on the vehicle new entry screen it navigates further where i can check different tabs like - data overview, vehicle history, general data etc.
Upon saving it throws an error "No action control found".
Is this a customizing error ? any idea ?
so far i have done the below things,
New end customer Cust100
a/c grp - KUNA
Notification 500000860
Material role assigned
Org role assigned
User assigned
Vehice model (Material Racer_A1)
Model sales code - Racer-minsale
Model service code - Racer-minsrvc
Asign warrany profile
Racer-minsale  WTY001 std warranty
Appreciate your help.
thanks
Kiran

Hi Kiran,
Use transaction VELOS to assign the Primary and secondary Matrices to the Material used in the vehicle model.
U shouldnt be getting the same error.
DBM Requires that individual users (Login ID's) are assigned to certain roles and the vehicle are assigned to certain matrices in order to proceed with creating vehicles and use them for creating orders.
Hope this info helps..
Best regards,
Harsha
PS: Reward suitable points for all responding.

Getting Error while installing Repository Creation Utility (RCU)!!!!!

Hi,
While installing RCU, I was getting the Invalid Username/Password error on Database Connection Details Screen when i give sys userid. on Database Connection Details Screen I was trying to connect with sys user but failed then I used system user and it got connect.
Then on Component screen, I was getting the below error.
RCU-6083:Failed - Check prerequisites requirement for selected component:ORAESS
Please refer to RCU log at /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for details.
Trying to connect as a non SYSDBA user. User should have SYSDBA privileges to successfully load the ESS schema.
RCU-6092:Component Selection validation failed. Please refer to log at /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for details.
I do not know why i am unable to connect with sys user as i am giving the correct password. Now i have changed the sys password but still unable to connect.
Please check the below link.
http://download.oracle.com/docs/cd/E12839_01/doc.1111/e14259/rcu_screens.htm
Please suggest something.
--- Log File Error ------------------------
2009-12-22 16:46:06.904 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: HOSTNAME: cicl-11g
2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: OSINFO: i386 2.6.18-164.6.1.el5 Linux
2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: JREINFO: 1.6.0_14 /u01/app/oracle/rcuHome/jdk/jre
2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: USERNAME: oracle
2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: USERDIR: /u01/app/oracle/rcuHome/bin
2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: User country: US
2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: User language: en
2009-12-22 16:46:06.913 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: Java class path: /u01/app/oracle/rcuHome/jlib/rcu.jar:/u01/app/oracle/rcuHome/jlib/share.jar:/u01/app/oracle/rcuHome/jlib/help-share.jar:/u01/app/oracle/rcuHome/jlib/ohj.jar:/u01/app/oracle/rcuHome/jlib/orai18n-mapping.jar:/u01/app/oracle/rcuHome/lib/xmlparserv2.jar:/u01/app/oracle/rcuHome/jdbc/lib/ojdbc5.jar:/u01/app/oracle/rcuHome/jdbc/lib/ojdbc14.jar:/u01/app/oracle/rcuHome/jlib/jewt4.jar:/u01/app/oracle/rcuHome/jlib/ojdl.jar:/u01/app/oracle/rcuHome/modules/oracle.odl_11.1.1/ojdl.jar:/u01/app/oracle/rcuHome/jlib/SchemaVersion.jar:/u01/app/oracle/rcuHome/jlib/wlsqlserver.jar:/u01/app/oracle/rcuHome/jlib/wlbase.jar:/u01/app/oracle/rcuHome/jlib/wlutil.jar:/u01/app/oracle/rcuHome/jlib/com.bea.core.weblogic.workmanager_1.6.0.0.jar:/u01/app/oracle/rcuHome/jlib/com.bea.core.weblogic.workmanager_1.7.0.0.jar:/u01/app/oracle/rcuHome/jlib/wldb2.jar:/u01/app/oracle/rcuHome/jlib/help-share.jar:/u01/app/oracle/rcuHome/jlib/ohj.jar:/u01/app/oracle/rcuHome/jlib/oracle_ice.jar:/u01/app/oracle/rcuHome/jlib/rcuhelp.jar:/u01/app/oracle/rcuHome/jlib/rcuhelppages.jar:/u01/app/oracle/rcuHome/assistants/opca/jlib/opca.jar:/u01/app/oracle/rcuHome/portal/jlib/ptlshare.jar:/u01/app/oracle/rcuHome/jlib/ldapjclnt11.jar:/u01/app/oracle/rcuHome/jlib/commons-collections-3.1.jar:/u01/app/oracle/rcuHome/jlib/commons-dbcp-1.2.1.jar:/u01/app/oracle/rcuHome/jlib/commons-logging.jar:/u01/app/oracle/rcuHome/jlib/commons-pool-1.2.jar:/u01/app/oracle/rcuHome/jlib/quartz-1.6.0.jar:/u01/app/oracle/rcuHome/jlib/jta.jar:/u01/app/oracle/rcuHome/jlib/xml.jar:/u01/app/oracle/rcuHome/jlib/iam-platform-utils.jar:/u01/app/oracle/rcuHome/jlib/iam-platform-authz-service.jar:/u01/app/oracle/rcuHome/jlib/iam-features-identity.zip:/u01/app/oracle/rcuHome/jlib/iam-features-configservice.zip:/u01/app/oracle/rcuHome/jlib/jps-api.jar:/u01/app/oracle/rcuHome/jlib/jps-common.jar:/u01/app/oracle/rcuHome/jlib/jps-ee.jar:/u01/app/oracle/rcuHome/jlib/jps-internal.jar:/u01/app/oracle/rcuHome/jlib/jps-manifest.jar:/u01/app/oracle/rcuHome/jlib/MicroSM.jar:/u01/app/oracle/rcuHome/jlib/javax.persistence_1.0.0.0_1-0-2.jar:/u01/app/oracle/rcuHome/jlib/org.eclipse.persistence_1.0.0.0_1-1-0.jar:/u01/app/oracle/rcuHome/jlib/identitystore.jar:/u01/app/oracle/rcuHome/jlib/jps-unsupported-api.jar:/u01/app/oracle/rcuHome/jlib/pd-internal.jar
2009-12-22 16:46:06.913 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: Java library path: /u01/app/oracle/rcuHome/jdk/jre/lib/i386/client:/u01/app/oracle/rcuHome/jdk/jre/lib/i386:/u01/app/oracle/rcuHome/jdk/jre/../lib/i386:/u01/app/oracle/rcuHome/lib32:/u01/app/oracle/rcuHome/network/lib32:/u01/app/oracle/rcuHome/lib:/u01/app/oracle/rcuHome/network/lib:/u01/app/oracle/product/11.2.0/network/lib:/u01/app/oracle/product/11.2.0/jdbc/lib:/u01/app/oracle/product/11.2.0/lib:/usr/lib:/usr/local/lib:/usr/java/packages/lib/i386:/lib:/usr/lib
2009-12-22 16:46:06.913 NOTIFICATION rcu: oracle.sysman.assistants.rcu.Rcu::execute: Launching RCU.
2009-12-22 16:46:06.916 NOTIFICATION rcu: oracle.sysman.assistants.rcu.Rcu::execute: Creating InteractiveRCUModel
2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::<init>: Base URL : file:///u01/app/oracle/rcuHome/rcu/config/
2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::<init>: ComponentInfo xml location : /u01/app/oracle/rcuHome/rcu/config/ComponentInfo.xml
2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::<init>: Storage xml location : /u01/app/oracle/rcuHome/rcu/config/Storage.xml
2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::<init>: DTD Validation : true
2009-12-22 16:46:07.891 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.RCUCommandLineParser::process: Processing command line ....
2009-12-22 16:46:39.363 NOTIFICATION rcu: oracle.sysman.assistants.common.dbutil.jdbc.JDBCEngine::connect: Connecting to database: user:system, role:Normal, connectString:(description=(address=(host=cicl-11g)(protocol=tcp)(port=1521))(connect_data=(service_name=DEV11G)(server=dedicated)))
2009-12-22 16:46:40.515 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Initializing repository configuration metadata
2009-12-22 16:46:40.515 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = INIT_META_DATA
2009-12-22 16:46:40.704 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : AS_COMMON
2009-12-22 16:46:40.707 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : MDS
2009-12-22 16:46:40.713 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : MDS
2009-12-22 16:46:40.714 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : MDS
2009-12-22 16:46:40.716 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : IAU
2009-12-22 16:46:40.720 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORAESS
2009-12-22 16:46:40.721 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : IDM
2009-12-22 16:46:40.721 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : OID
2009-12-22 16:46:40.723 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : OIF
2009-12-22 16:46:40.732 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : OWLCS
2009-12-22 16:46:40.733 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPXDMS
2009-12-22 16:46:40.735 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPSDS
2009-12-22 16:46:40.759 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPLS
2009-12-22 16:46:40.760 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : SOA
2009-12-22 16:46:40.761 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : SOAINFRA
2009-12-22 16:46:40.762 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : SOAINFRA
2009-12-22 16:46:40.762 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : SOAINFRA
2009-12-22 16:46:40.763 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : BAM
2009-12-22 16:46:40.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPM
2009-12-22 16:46:40.768 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPM
2009-12-22 16:46:40.769 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : ORASDPM
2009-12-22 16:46:40.770 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WEBCENTER_SUITE
2009-12-22 16:46:40.771 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WEBCENTER
2009-12-22 16:46:40.771 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WEBCENTER
2009-12-22 16:46:40.772 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WEBCENTER
2009-12-22 16:46:40.774 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : PORTLET
2009-12-22 16:46:40.776 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : PORTLET
2009-12-22 16:46:40.777 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : PORTLET
2009-12-22 16:46:40.778 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : CONTENTSERVER
2009-12-22 16:46:40.778 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : CONTENTSERVER
2009-12-22 16:46:40.779 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : CONTENTSERVER
2009-12-22 16:46:40.783 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCUSSIONS
2009-12-22 16:46:40.784 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCUSSIONS
2009-12-22 16:46:40.785 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCUSSIONS
2009-12-22 16:46:40.786 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCUSSIONS_CRAWLER
2009-12-22 16:46:40.791 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCUSSIONS_CRAWLER
2009-12-22 16:46:40.794 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WIKI
2009-12-22 16:46:40.795 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WIKI
2009-12-22 16:46:40.795 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : WIKI
2009-12-22 16:46:40.796 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : PORTAL_BI
2009-12-22 16:46:40.797 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : PORTAL
2009-12-22 16:46:40.800 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing Component : DISCOVERER
2009-12-22 16:46:40.821 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseXmlData: XML Document: /u01/app/oracle/rcuHome/rcu/config/ComponentInfo.xml is valid
2009-12-22 16:46:40.835 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : MDS
2009-12-22 16:46:40.843 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//mds/mds.xml is valid
2009-12-22 16:46:40.852 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : IAU
2009-12-22 16:46:40.857 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration/iau/iau.xml is valid
2009-12-22 16:46:40.864 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : ORAESS
2009-12-22 16:46:40.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//ess/ess.xml is valid
2009-12-22 16:46:40.883 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : OID
2009-12-22 16:46:40.886 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//oid/oid.xml is valid
2009-12-22 16:46:40.891 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : OIF
2009-12-22 16:46:40.898 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//oif/oif.xml is valid
2009-12-22 16:46:40.904 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : ORASDPXDMS
2009-12-22 16:46:40.907 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//commspresence/commspresence.xml is valid
2009-12-22 16:46:40.915 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : ORASDPSDS
2009-12-22 16:46:40.932 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//commssds/commssds.xml is valid
2009-12-22 16:46:40.938 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : ORASDPLS
2009-12-22 16:46:40.939 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//commsls/commsls.xml is valid
2009-12-22 16:46:40.945 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : SOAINFRA
2009-12-22 16:46:40.950 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//soainfra/soainfra.xml is valid
2009-12-22 16:46:40.955 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : BAM
2009-12-22 16:46:40.958 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//bam/bam.xml is valid
2009-12-22 16:46:40.963 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : ORASDPM
2009-12-22 16:46:40.975 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//sdpm/sdpm.xml is valid
2009-12-22 16:46:40.981 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : WEBCENTER
2009-12-22 16:46:40.991 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//webcenter/webcenter.xml is valid
2009-12-22 16:46:40.998 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : PORTLET
2009-12-22 16:46:41.006 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//portlet/portlet.xml is valid
2009-12-22 16:46:41.011 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : CONTENTSERVER
2009-12-22 16:46:41.021 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration/contentserver/contentserver.xml is valid
2009-12-22 16:46:41.024 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : DISCUSSIONS
2009-12-22 16:46:41.030 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//jive/jive.xml is valid
2009-12-22 16:46:41.040 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : DISCUSSIONS_CRAWLER
2009-12-22 16:46:41.048 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//jive-crawler/jive-crawler.xml is valid
2009-12-22 16:46:41.052 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : WIKI
2009-12-22 16:46:41.056 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//wiki/wiki.xml is valid
2009-12-22 16:46:41.063 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : PORTAL
2009-12-22 16:46:41.065 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration/portal/portal.xml is valid
2009-12-22 16:46:41.070 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently Parsing Repository Config data for Component : DISCOVERER
2009-12-22 16:46:41.073 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration/dc/discoverer.xml is valid
2009-12-22 16:46:41.108 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseStorageData: XML Document: /u01/app/oracle/rcuHome/rcu/config/Storage.xml is valid
2009-12-22 16:46:41.452 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Initializing repository configuration metadata : 937 milliseconds
2009-12-22 16:46:41.464 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Obtain properties of the specified database
2009-12-22 16:46:41.464 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = PREREQ_QUERY_DATABASE
2009-12-22 16:46:41.498 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Obtain properties of the specified database : 34 milliseconds
2009-12-22 16:46:41.514 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Check requirement for specified database
2009-12-22 16:46:41.514 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = PREREQ_GLOBAL_CHECK
2009-12-22 16:46:41.557 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Check requirement for specified database : 43 milliseconds
2009-12-22 16:46:41.572 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Execute pre create operations
2009-12-22 16:46:41.573 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.CustomCompManager::getActionList: CustomCompManager.getActionList: CUSTOM_COMP_PRELOAD_SETUP
2009-12-22 16:46:41.579 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.AbstractCompTask::execute: ValidIf result was false. Skipping Action: oracle.ias.version.SchemaVersionUtil:utilCreateRegistryAndCopyData
2009-12-22 16:46:41.582 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.AbstractCompTask::execute: ValidIf result was false. Skipping Action: oracle.ias.version.SchemaVersionUtil:utilCreateRegistryTable
2009-12-22 16:46:41.582 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Execute pre create operations : 9 milliseconds
2009-12-22 16:46:55.687 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Metadata Services
2009-12-22 16:46:55.687 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = MDS
2009-12-22 16:46:55.687 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Starting component prereq check
2009-12-22 16:46:55.722 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Metadata Services : 35 milliseconds
2009-12-22 16:46:55.727 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Audit Services
2009-12-22 16:46:55.727 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = IAU
2009-12-22 16:46:55.727 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Starting component prereq check
2009-12-22 16:46:55.761 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Execution time for Audit Services : 34 milliseconds
2009-12-22 16:46:55.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: Executing Task: Enterprise Scheduler Service
2009-12-22 16:46:55.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = ORAESS
2009-12-22 16:46:55.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Starting component prereq check
2009-12-22 16:46:55.773 ERROR rcu: oracle.sysman.assistants.rcu.backend.task.PrereqTask::execute: Prereq Evaluation Failed
oracle.sysman.assistants.rcu.backend.validation.PrereqException: RCU-6083:Failed - Check prerequisites requirement for selected component:ORAESS
Please refer to RCU log at /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for details.
     at oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator.executePrereqTask(PrereqEvaluator.java:642)
     at oracle.sysman.assistants.rcu.backend.task.PrereqTask.execute(PrereqTask.java:68)
     at oracle.sysman.assistants.rcu.backend.task.ActualTask.run(TaskRunner.java:303)
     at java.lang.Thread.run(Thread.java:619)
2009-12-22 16:46:55.773 ERROR rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: RCU Operation Failed
oracle.sysman.assistants.common.task.TaskExecutionException: RCU-6083:Failed - Check prerequisites requirement for selected component:ORAESS
Please refer to RCU log at /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for details.
Trying to connect as a non SYSDBA user. User should have SYSDBA privileges to successfully load the ESS schema.
     at oracle.sysman.assistants.rcu.backend.task.PrereqTask.execute(PrereqTask.java:76)
     at oracle.sysman.assistants.rcu.backend.task.ActualTask.run(TaskRunner.java:303)
     at java.lang.Thread.run(Thread.java:619)
Edited by: yousufpaya on Dec 22, 2009 7:31 PM

Hi yousuf;
Please follow below and see its helpful for your issue:
http://soadev.blogspot.com/2009_07_01_archive.html ( part:Error in Running Repository Creation Utility (RCU) While Using Oracle XE database )
Also check:
http://forums.tangosol.com/forums/thread.jspa?threadID=930952&tstart=60 (Joaanas post)
Regard
Helios

ERROR IN VENMDOR MASTER CREATION??

Hii experts
In IDES i have configuration for vendor master , and i have created reconciliation account for vendor also.
While creating vendor master after entering all details at last its throwing error like the account 4 is already exists????
How we can rectifiy this error
Thanks

>
MM group wrote:
> hii
>
> I have Recon account all those thing . atlast while saving the vendor master i m getting error like this "Accounts 4 already exists "
>
> ANd then if click on exit , it will go out from the vendor master screen and no vendor number has been given .
>
> Thanks
Seems like the problem is with the recon account. Try creating with a different recon account, and see whether the error is coming. Check the post below for creating recon account.
How to Configure FICO Reconciliation
In Co, we create Recon accts to keep Fi gl in balance with CO. Not all transactions affect FI gls, best example of it is internal order settlements, they use secondary cost elements and does not affect your G/l accts. To update FI side of it we maintain recon accts. These are primarily for cross company, cross functional and cross business area transactions.
The number of recon accts to be defined is dependant on various factors, like how your management wants to see the reports.. whether they want to classify the cost based on CO object class or by Co types etc..
However the basic config you got to follow is:
1. Activate Recon accts (if you have created CO area newly, it would be active).
    use T.code: KALA
2. Assignment of Recon document type to the Controlling area.
    T.code: OKKP
3. Creating clearing accts (that you want to us! e for reconciliation. During FI-Co recon.. inter company clearing accounts will be automatically credited or debited and now you need to create offset acct which will show up in P&l acct).
    Acct determination set up thru T.code: OBYA
4. Maintain accts for Automatic Recon posting.
    T.code OBYB
5. Assign Number ranges to Recon activity.
    Tcode OK13                                                                                *-- Radha Krishna
Without creating of reconciliation account, can you create vendor? What is the use of reconciliation?
Customer and vendor accounts are sub ledger GL's. We will have to create two reconciliation GLs in viz. Reconciliation GL for Customer and Vendor in chart of accounts.
After, while creating customer and vendor master records, we have to mention respective reconciliation GL in their company code segment details. This recon a/c will show you the net balances in GL for customer and vendor a/cs.
Without creating Vendor you can still create individual GL for each customer and vendor , but then
1) Your list of GL's in chart of account will be very lengthy.
2) Duplication of work as SD/ MM people are also required to create their own list.
3) Cross company code consolidation will not be possible as the chart of accounts will be different.
4) Very difficult to keep track of individual customer/ vendor a/cs.
5) Not advisable even in real time accounting system i.e. manual book keeping.

Error in Vendor master creation

Hi Experts,
While creating vendor master , getting error u201CNo entry in table T001 for argumentu201D.
I think some bank details are missing.
Any one know how to rectify the same. and what might be the reason for this error.
Thanks

hi,
please reffer the below link.
Error - no entry in table T001
Thanking you

Error in Asset Master Creation

In Asset Master Creation an error occured that is
CUSTOMIZING INCONSISTENCY MISSING/INCORRECT IN TABLE NO T093B
Waiting for u r early reply
venky
Edited by: venky venky on Jul 11, 2008 2:53 PM

I suppose you need to check your configuration of Low Value Assets for each
depreciation area.
But before that, please tell me which class of Assets you are using ......Is
it the *LVA Class 5000 ( individual management )* or* 5001 ( collective
management)*. Either way, you need to assign a maximum value / maximum value
over quantity, as the case may be. Unless and until you furnish a value cap,
the asset class does not permit you to create asset master records.
Please look into your IMG under the path:
*IMG -> Financial Accounting -> Asset Accounting -> Valuation ->Amount
Specifications(Company Code / Depreciation Area) ->
Specify Maximum Amount for LVA + Asset Classes*
You would see two activities listed.
Under *Activity 1*, you need to select and assign value check (*represented
by number 1*) if you are using *LVA Class 5000* ; alternatively, you need
to select and assign Check Maximum Amount with Quantity (*represented by
number 2*) if you are using *LVA class 5001*.
You need to do this for each depreciation area you wish to apply this value
cap to and save (using the floppy icon and look out for the confirmatory
message at the bottom left of your screen).
Under *Activity 2,* You need to furnish a value cap ( a ceiling in monetary
units, currency-specifically) for each depreciation area ( a column for
document value and another for Purchase order value ( possibly to
accommodate any tax, as applicable). Please make sure that you do it for
your company code and for each depreciation area wherein you want to control
using a value cap.
Save and look for the confirmatory message at the bottom left of the screen.
Regards,
Bharti

ERROR IN CUSTOMER MASTER CREATION -THROUGH IDOC.

We are facing issue while creating customer through idoc. System is giving error "No batch input data for screen SAPLID_TAXNUM 1000 "
On analyzing this error - we are able to find out that someone has enabled some duplicity check or message control on filed of tax number 1.In this filed we are storing some other legacy information which is not unique to each customer so system is poping up some screen which shows that this information already exist for other customers . Due to this customers are not getting created.
We have checked the message control setting bur there was no such message control.
Now we are not able to figure it that who has done this change and how. Further how this can be resolved.
Pls help.
Rgds,
Sudhanshu Dang

Hai Jobi Thottungal,
Since you can create a Customer with Account type 001, please check what is the PARTNER TYPE assigned.
Now, GO TO
IMG Sales and DistributionMaster DataBusiness PartnersCustomersCustomer Hierarchy
Set Up Partner Determination for Customer Master
Partner Determination Procedure Assignment
Assign the Partner procedure to your Account group
So at the time of creation of Customer master with your Account group, the partner function will get created automatically.
Regards,
Mani

Getting error while rebuilding master database in cluster environment

I am testing a disaster recovery scenario in one of our test MS SQL server with 2 node cluster. I am executing below rebuild command using MS SQL server setup.
C:\U_Soft\SW_CD_SQL_Svr_Enterprise_Edtn_2005_64Bit_X64_English_1_x64_MLF_X11-57796>start /wait C:\U_Soft\SW_CD_SQL_Svr_Enterprise_Edtn_2005_64Bit_X64_English_2_x64_MLF_X11-57797\setup.exe /qb VS=DMZSQLTST REINSTALL=SQL_Engine REBUILDDATABASE=1
ADMINPASSWORD=abcd1234$ SAPWD=abcd1234$
I am getting the blow alert / error the during setup execution
“An installation package for the product Microsoft SQL Server 2005 (64-bit) cannot be found. Try the installation again using a valid copy of the installation package ‘SqlRun_SQL.msi’
I have checked the package is available in the setup.

Hello,
Did you copy the setup file from a different place? The issue may occurs if you don't have access to the original media location of where the RTM bits where installed from.
To resolve this issue, please try to use the REINSTALLMODE with option V to re-cache the media from the new location. For example:
C:\U_Soft\SW_CD_SQL_Svr_Enterprise_Edtn_2005_64Bit_X64_English_2_x64_MLF_X11-57797\setup.exe /qb VS=DMZSQLTST REINSTALL=SQL_Engine REINSTALLMODE=v ADMINPASSWORD=abcd1234$ SAPWD=abcd1234$
And then run the normal command to rebuild the database.
Reference:
http://ms-abhay.blogspot.in/2010/11/error-1706-installation-package-for.html
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Error in Asset Master Creation for Low Value assets

Hi,
I am trying to create an asset under the asset class Low value asset. while saving the asset the system delivers the following Error:
01 Book depreciation
E614 Low value asset max.amount exceeded. No posting allowed
02 Special tax depreciation for APC in fin.statement
E614 Low value asset max.amount exceeded. No posting allowed
I am using the standard Depreciation Key "GWG" But when i change the depreciation key the system allows me to save the asset. Please guide me how to fix this and why system is giving this error.
Regards,

I suppose you need to check your configuration of Low Value Assets for each
depreciation area.
But before that, please tell me which class of Assets you are using ......Is
it the *LVA Class 5000 ( individual management )* or* 5001 ( collective
management)*. Either way, you need to assign a maximum value / maximum value
over quantity, as the case may be. Unless and until you furnish a value cap,
the asset class does not permit you to create asset master records.
Please look into your IMG under the path:
*IMG -> Financial Accounting -> Asset Accounting -> Valuation ->Amount
Specifications(Company Code / Depreciation Area) ->
Specify Maximum Amount for LVA + Asset Classes*
You would see two activities listed.
Under *Activity 1*, you need to select and assign value check (*represented
by number 1*) if you are using *LVA Class 5000* ; alternatively, you need
to select and assign Check Maximum Amount with Quantity (*represented by
number 2*) if you are using *LVA class 5001*.
You need to do this for each depreciation area you wish to apply this value
cap to and save (using the floppy icon and look out for the confirmatory
message at the bottom left of your screen).
Under *Activity 2,* You need to furnish a value cap ( a ceiling in monetary
units, currency-specifically) for each depreciation area ( a column for
document value and another for Purchase order value ( possibly to
accommodate any tax, as applicable). Please make sure that you do it for
your company code and for each depreciation area wherein you want to control
using a value cap.
Save and look for the confirmatory message at the bottom left of the screen.
Regards,
Bharti

Error in vendor master creation Tax number 1

Dear All
when i tried to create a vendor master ,where the vendor country is US .in general data under the tax information tax number1 which is mandatory when i entered i got an error that tax code 1 is not valid.what should i do, i wan to make that filed optional
regards
mac

Hi Manu,
If you want put that field optional you can go through t.code OBD3 .
There select the FI Vendors group and slect field status and in company code data you can change that field from required to optional.
If you have any doubt feel free to ask
May be this information is useful to you
Regards
Surya

UOM error in Material master.

Hi
When we log on to Spanish language, we are getting error in material master for Unit of measure, that the unit of measure has not been created in the language ES. But same UOM has configured in EN language and its working fine for material, while in Spanish language it appear as *** with error details,
Could you please suggestu2026
regards
Vanraj

Hi,
Extactly you are right..you got to Logon in Languange ES and create the required UOM in t-code CUNI...
this shuld solve the issue..try and revrt back..
Also,In CUNI on top menu Go to-Translation-UOM here maintain Source lang to Target lan
Reg,
JJ
Edited by: Jagsap on Apr 20, 2010 4:10 PM
Edited by: Jagsap on Apr 20, 2010 4:15 PM

Error as Enter while creation of PO due to this PO is not created in ME21N

Hi All,
I have an issue where one of my user cannot able to create a PO with refernce to Network and he is getting error as ENTER while creation of PO in ME21N and there is no long text for this error.Also user cannot able to create a PO whenever he clicked on save button the only option he got is Hold or Edit or cancel.
I have asked user to provide the same information (inputs while creation of PO in ME21N) to his colleague and check whether he can able to create a PO successfully or not. User confirmed that his colleague can able to create a PO successfully.
Please let me know what was the root cause behind this.
Awaiting for your valauble inputs & quicker reply.
Note: I have crossverified with technical team and they confim all the required roles are in place for my user.
BR // Kumar.S

Hi Jurgen,
Question from you
Just message ENTER is pretty unusual. Even if there is no long text, the message should at least have a message number, can you tell this number? In general there should be the field name next to the message.
Answer from me
As you have said i have cliked on the error ie ENTERand got the message number as below,
Enter
Message no. ME083
Question from you
Is there any userexit which may cause this error?
Answer from me
According to me know because only one user is having a problem other users can able to create a PO sucuessuflly.
Question from you
What happens if a different user enters the PO under the user ID of the user who can only hold the PO?
What happens if the effected user creates the PO under the user ID of a different user (who is usually able to save POs)?
Answer from me
not tried will let u know on this later
Question from you
Have you customized a new process, and this user is testing it?
Answer from me
No
Please let me know whether the above my inputs help you to identify the issue where exactly it was.
BR // Kumar.S

Getting Error in Master Repo creation in ODI 10.1.3.5

Hi All,
I am creating Master repo with MS SQL Server 2000 and using two approches but getting error.
In first approch -
I am using Driver --->>> com.microsoft.sqlserver.jdbc.SQLServerDriver and
URL---->>> jdbc:sqlserver://localhost:1433;selectMethod=cursor;database=Master_ODI;integratedSecurity=false
Master repo starts but in between getting error "*connection closed*" and some time "*Not delete permission for user on SNP_LICENSE.*
Second Approch -
Using Driver -->> sun.jdbc.odbc.JdbcOdbcDriver
Url-->> jdbc:odbc: <DSN name with master database in SQl Server>
in this approch I am able to create Mater repo but in topology I am not able to see Master repo in Repository window.
Please help me out if Iam doing somthing wrong or missed some steps.
Regards,
Vibhav

Just follow the below steps to create master repository in MS SQL Server, you can find these steps in odi installation folder.
Creating Repository Storage Spaces
Create a database db_snpm to host the Master repository and a database db_snpw to host the work repository. Create two logins snpm and snpw which have these databases by default.
Use Enterprise Manager to create the two databases db_snpm and db_snpw (allow about 40 Mb for Data and 20 Mb for Log for each of them)
Use Query Analyzer or I-SQL to launch the following commands:
CREATE LOGIN <mylogin>
        WITH PASSWORD = '<mypass>',
        DEFAULT_DATABASE = <defaultbase>,
        DEFAULT_LANGUAGE = us_english;
USE <defautbase>;
CREATE USER dbo FOR LOGIN <mylogin>;
GO
Where: <mylogin> corresponds to snpm or snpw <mypass> corresponds to a password for these logins <defaultbase> corresponds to db_snpm and db_snpw respectively
Creating the Master Repository
Creating the master repository consists of creating the tables and the automatic importing of definitions for the different technologies.
To create the master repository:
In the Start Menu , select Programs > Oracle Data Integrator > Repository Management > Master Repository Creation , or Launch bin/repcreate.bat or bin/repcreate.sh.
Complete the fields:
Driver : the driver used to access the technology which will host the repository. For more information, refer to the section JDBC URL Sample.
URL : The complete path for the data server to host the repository. For more information, refer to the section JDBC URL Sample.
User : The user id / login of the owner of the tables (previously created under the name snpm).
Password : This user's password.
ID : A specific ID for the new repository, rather than the default 0. This will affect imports and exports between repositories.
Technologies : From the list, select the technology your repository will be based on.
Language: Select the language of your master repository.
Validate by OK.
Creating the dictionary begins. You can follow the procedure on your console. To test your master repository, refer to the section Connecting to the master repository.

Automatic Po creation With MB01 i am getting Error

Hi ,
While doing goods receipt for Automatic Po creation i am getting error
MM activated Automatic Po
VM activated Automatic Po
101 Mov Type is also activated
Item 00010 of purchasing document 9999999999 does not exist
Message no. ME706
Diagnosis
Purchase order 00010 with item 9999999999 was not found.
Procedure
Enter a different purchase order.
i given the Vendor and quantity after entering error is coming
Please help
Manjunath

HI,
Pls ceck the points mentioned below.
Define one of the purchase organizations as Standard Purchase Organization
Assign your plant to Standard Purchase Organization
Maintain purchasing information record with price
Maintain the indicator for movement types 101 & 161
Define Default Values (MB01) for Document Type
Now you can enter a goods receipt without entering the purchase order number, a purchase order will be created automatically when you post the goods receipt. All such goods receipt will be valuated at the price maintained in the purchasing information record.
First you can try this with T. Code MB01 if it is working then try with T. Code MIGO, if you face any error or functionality is not working check with your basis consultant some authorization or some patches may be missing. Ask him to apply all relevant patches.
Thanks
Chandru

Material Master Upload using Bapi getting error "****** not a valid unit of

Hi Gurus,
i am uploading material master using BAPI Material_master_save_data , where the volume and Unit of Volume is Blank, Still i am getting error as "****** not a valid unit of volume ".kindly help me to resolve the issue.Many Thanks In advance.

Jurgen,
I could able to solve the issue for invalid unit Error ....Now i am getting **** unit of measure is not defined , pls check your entry or else i am getting alternate unit of mesure is same as base unit of measure .
I have used below logic for Purchase Order Unit and Base Unit of measure .
      if wa_upload-unmsr EQ wa_upload-ord_uom .
        bapi_mara1-base_uom = wa_upload-unmsr.
        bapi_mara1-po_unit = wa_upload-ord_uom .
      elseif wa_upload-unmsr NE wa_upload-ord_uom.
        wa_upload-ord_uom = wa_upload-alt_uom.
        bapi_mara1-po_unit = wa_upload-ord_uom.
      endif.
Many Thanks for your help.

Getting error in Vehicle Master creation in DBM7.0

Similar Messages

Maybe you are looking for