Importing memos (step by step)

I have a laptop, loaded with windows xp and iTunes. I need, step by step instruction, on how to convert files to a format, my 40 gb, third generation ipod, can recognise and display.

Hey Molugu,
you shouldn't have to install the client certificates on KeyStorage Service, for receiver adapters. The server's public certificate is sent just in the SSL handshaking. What you should have is the certificate authorization tree in your Trusted ACs Service (if the issuer of your client's certificate is not already there).
You need to install client certificates in sender adapters, when your client uses authentication through certificate. Then you need to install that authentication certificate for the authorized users.
Check the following link for SSL on J2EE: http://help.sap.com/saphelp_nw2004s/helpdata/en/f1/2de3be0382df45a398d3f9fb86a36a/frameset.htm
Regards,
Henrique.

Similar Messages

Error in import abap step while importing system copy.

Hi All,
My colleague had taken System copy of development server, few days back. it was completed successfully,
now we want to restore that system copy, as hardware failed. But when we start the import of system copy,
all ABAP jobs are failing in import abap step, Some DDL statement problem. can u pls help wht to do.
I found in some forums, SMIGR_create_DDL report need to be generated prior to taking system copy, but he
didnt taken tht.
OS: Windows 2003
DB: DB2
Pls find sapinst.log
INFO 2009-10-27 10:43:06.890
Output of C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING 2009-10-27 10:53:37.125
Execution of the command "C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_13-b06, mixed mode)
Import Monitor jobs: running 1, waiting 63, completed 0, failed 0, total 64.
Import Monitor jobs: running 2, waiting 62, completed 0, failed 0, total 64.
Import Monitor jobs: running 3, waiting 61, completed 0, failed 0, total 64.
Loading of 'DOKCLU' import package: ERROR
Import Monitor jobs: running 2, waiting 61, completed 0, failed 1, total 64.
Loading of 'D010TAB' import package: ERROR
Import Monitor jobs: running 1, waiting 61, completed 0, failed 2, total 64.
Loading of 'REPOSRC' import package: ERROR
Import Monitor jobs: running 0, waiting 61, completed 0, failed 3, total 64.
Import Monitor jobs: running 1, waiting 60, completed 0, failed 3, total 64.
Import Monitor jobs: running 2, waiting 59, completed 0, failed 3, total 64.
Import Monitor jobs: running 3, waiting 58, completed 0, failed 3, total 64.
Loading of 'DYNPSOURCE' import package: ERROR
Import Monitor jobs: running 2, waiting 58, completed 0, failed 4, total 64.
Loading of 'SAPAPPL1_4' import package: ERROR
Import Monitor jobs: running 1, waiting 58, completed 0, failed 5, total 64.
Loading of 'SAPAPPL2_2' import package: ERROR
Import Monitor jobs: running 0, waiting 58, completed 0, failed 6, total 64.
Import Monitor jobs: running 1, waiting 57, completed 0, failed 6, total 64.
Import Monitor jobs: running 2, waiting 56, completed 0, failed 6, total 64.
Import Monitor jobs: running 3, waiting 55, completed 0, failed 6, total 64.
Loading of 'SAPNTAB' import package: ERROR
Import Monitor jobs: running 2, waiting 55, completed 0, failed 7, total 64.
Loading of 'SAPSSEXC_9' import package: ERROR
Import Monitor jobs: running 1, waiting 55, completed 0, failed 8, total 64.
Loading of 'SAPSSEXC_8' import package: ERROR
Import Monitor jobs: running 0, waiting 55, completed 0, failed 9, total 64.
Import Monitor jobs: running 1, waiting 54, completed 0, failed 9, total 64.
Import Monitor jobs: running 2, waiting 53, completed 0, failed 9, total 64.
Import Monitor jobs: running 3, waiting 52, completed 0, failed 9, total 64.
Loading of 'SAPAPPL2_6' import package: ERROR
Import Monitor jobs: running 2, waiting 52, completed 0, failed 10, total 64.
Loading of 'SAPAPPL1_3' import package: ERROR
Import Monitor jobs: running 1, waiting 52, completed 0, failed 11, total 64.
Loading of 'SAPAPPL2_5' import package: ERROR
Import Monitor jobs: running 0, waiting 52, completed 0, failed 12, total 64.
Import Monitor jobs: running 1, waiting 51, completed 0, failed 12, total 64.
Import Monitor jobs: running 2, waiting 50, completed 0, failed 12, total 64.
Import Monitor jobs: running 3, waiting 49, completed 0, failed 12, total 64.
Loading of 'D010INC' import package: ERROR
Import Monitor jobs: running 2, waiting 49, completed 0, failed 13, total 64.
Loading of 'SAPAPPL1_2' import package: ERROR
Import Monitor jobs: running 1, waiting 49, completed 0, failed 14, total 64.
Loading of 'SAPAPPL1_7' import package: ERROR
Import Monitor jobs: running 0, waiting 49, completed 0, failed 15, total 64.
Import Monitor jobs: running 1, waiting 48, completed 0, failed 15, total 64.
Import Monitor jobs: running 2, waiting 47, completed 0, failed 15, total 64.
Import Monitor jobs: running 3, waiting 46, completed 0, failed 15, total 64.
Loading of 'SAPSSEXC_2' import package: ERROR
Import Monitor jobs: running 2, waiting 46, completed 0, failed 16, total 64.
Loading of 'DYNPLOAD' import package: ERROR
Import Monitor jobs: running 1, waiting 46, completed 0, failed 17, total 64.
Loading of 'SAPSSEXC_5' import package: ERROR
Import Monitor jobs: running 0, waiting 46, completed 0, failed 18, total 64.
Import Monitor jobs: running 1, waiting 45, completed 0, failed 18, total 64.
Import Monitor jobs: running 2, waiting 44, completed 0, failed 18, total 64.
Import Monitor jobs: running 3, waiting 43, completed 0, failed 18, total 64.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 2, waiting 43, completed 0, failed 19, total 64.
Loading of 'SAPAPPL2_14' import package: ERROR
Import Monitor jobs: running 1, waiting 43, completed 0, failed 20, total 64.
Loading of 'SAPAPPL0_2' import package: ERROR
Import Monitor jobs: running 0, waiting 43, completed 0, failed 21, total 64.
Import Monitor jobs: running 1, waiting 42, completed 0, failed 21, total 64.
Import Monitor jobs: running 2, waiting 41, completed 0, failed 21, total 64.
Import Monitor jobs: running 3, waiting 40, completed 0, failed 21, total 64.
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 2, waiting 40, completed 0, failed 22, total 64.
Loading of 'SAPSSEXC_4' import package: ERROR
Import Monitor jobs: running 1, waiting 40, completed 0, failed 23, total 64.
Loading of 'SAPAPPL2_10' import package: ERROR
Import Monitor jobs: running 0, waiting 40, completed 0, failed 24, total 64.
Import Monitor jobs: running 1, waiting 39, completed 0, failed 24, total 64.
Import Monitor jobs: running 2, waiting 38, completed 0, failed 24, total 64.
Import Monitor jobs: running 3, waiting 37, completed 0, failed 24, total 64.
Loading of 'SAPSSEXC_7' import package: ERROR
Import Monitor jobs: running 2, waiting 37, completed 0, failed 25, total 64.
Loading of 'SAPAPPL0_7' import package: ERROR
Import Monitor jobs: running 1, waiting 37, completed 0, failed 26, total 64.
Loading of 'SAPAPPL0_1' import package: ERROR
Import Monitor jobs: running 0, waiting 37, completed 0, failed 27, total 64.
Import Monitor jobs: running 1, waiting 36, completed 0, failed 27, total 64.
Import Monitor jobs: running 2, waiting 35, completed 0, failed 27, total 64.
Import Monitor jobs: running 3, waiting 34, completed 0, failed 27, total 64.
Loading of 'SAPAPPL2_7' import package: ERROR
Import Monitor jobs: running 2, waiting 34, completed 0, failed 28, total 64.
Loading of 'SAPAPPL2_4' import package: ERROR
Import Monitor jobs: running 1, waiting 34, completed 0, failed 29, total 64.
Loading of 'SAPAPPL1_6' import package: ERROR
Import Monitor jobs: running 0, waiting 34, completed 0, failed 30, total 64.
Import Monitor jobs: running 1, waiting 33, completed 0, failed 30, total 64.
Import Monitor jobs: running 2, waiting 32, completed 0, failed 30, total 64.
Import Monitor jobs: running 3, waiting 31, completed 0, failed 30, total 64.
Loading of 'SAPAPPL0_3' import package: ERROR
Import Monitor jobs: running 2, waiting 31, completed 0, failed 31, total 64.
Loading of 'SAPCLUST' import package: ERROR
Import Monitor jobs: running 1, waiting 31, completed 0, failed 32, total 64.
Loading of 'SAPAPPL0_8' import package: ERROR
Import Monitor jobs: running 0, waiting 31, completed 0, failed 33, total 64.
Import Monitor jobs: running 1, waiting 30, completed 0, failed 33, total 64.
Import Monitor jobs: running 2, waiting 29, completed 0, failed 33, total 64.
Import Monitor jobs: running 3, waiting 28, completed 0, failed 33, total 64.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 2, waiting 28, completed 0, failed 34, total 64.
Loading of 'ENHOBJCONTRACT' import package: ERROR
Import Monitor jobs: running 1, waiting 28, completed 0, failed 35, total 64.
Loading of 'SAPAPPL0_4' import package: ERROR
Import Monitor jobs: running 0, waiting 28, completed 0, failed 36, total 64.
Import Monitor jobs: running 1, waiting 27, completed 0, failed 36, total 64.
Import Monitor jobs: running 2, waiting 26, completed 0, failed 36, total 64.
Import Monitor jobs: running 3, waiting 25, completed 0, failed 36, total 64.
Loading of 'SAPSSEXC_1' import package: ERROR
Import Monitor jobs: running 2, waiting 25, completed 0, failed 37, total 64.
Loading of 'SAPSSEXC_6' import package: ERROR
Import Monitor jobs: running 1, waiting 25, completed 0, failed 38, total 64.
Loading of 'SAPAPPL2_8' import package: ERROR
Import Monitor jobs: running 0, waiting 25, completed 0, failed 39, total 64.
Import Monitor jobs: running 1, waiting 24, completed 0, failed 39, total 64.
Import Monitor jobs: running 2, waiting 23, completed 0, failed 39, total 64.
Import Monitor jobs: running 3, waiting 22, completed 0, failed 39, total 64.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 0, failed 40, total 64.
Loading of 'SAPAPPL2_1' import package: ERROR
Import Monitor jobs: running 1, waiting 22, completed 0, failed 41, total 64.
Loading of 'SAPAPPL1_5' import package: ERROR
Import Monitor jobs: running 0, waiting 22, completed 0, failed 42, total 64.
Import Monitor jobs: running 1, waiting 21, completed 0, failed 42, total 64.
Import Monitor jobs: running 2, waiting 20, completed 0, failed 42, total 64.
Import Monitor jobs: running 3, waiting 19, completed 0, failed 42, total 64.
Loading of 'REPOTEXT' import package: ERROR
Import Monitor jobs: running 2, waiting 19, completed 0, failed 43, total 64.
Loading of 'SAPAPPL0_5' import package: ERROR
Import Monitor jobs: running 1, waiting 19, completed 0, failed 44, total 64.
Loading of 'SAPAPPL2_9' import package: ERROR
Import Monitor jobs: running 0, waiting 19, completed 0, failed 45, total 64.
Import Monitor jobs: running 1, waiting 18, completed 0, failed 45, total 64.
Import Monitor jobs: running 2, waiting 17, completed 0, failed 45, total 64.
Import Monitor jobs: running 3, waiting 16, completed 0, failed 45, total 64.
Loading of 'SAPSSEXC_10' import package: ERROR
Import Monitor jobs: running 2, waiting 16, completed 0, failed 46, total 64.
Loading of 'SAPAPPL2_3' import package: ERROR
Import Monitor jobs: running 1, waiting 16, completed 0, failed 47, total 64.
Loading of 'SAPAPPL0_6' import package: ERROR
Import Monitor jobs: running 0, waiting 16, completed 0, failed 48, total 64.
Import Monitor jobs: running 1, waiting 15, completed 0, failed 48, total 64.
Import Monitor jobs: running 2, waiting 14, completed 0, failed 48, total 64.
Import Monitor jobs: running 3, waiting 13, completed 0, failed 48, total 64.
Loading of 'SAPSLEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 13, completed 0, failed 49, total 64.
Loading of 'SAPAPPL0_9' import package: ERROR
Import Monitor jobs: running 1, waiting 13, completed 0, failed 50, total 64.
Loading of 'SAPAPPL2_11' import package: ERROR
Import Monitor jobs: running 0, waiting 13, completed 0, failed 51, total 64.
Import Monitor jobs: running 1, waiting 12, completed 0, failed 51, total 64.
Import Monitor jobs: running 2, waiting 11, completed 0, failed 51, total 64.
Import Monitor jobs: running 3, waiting 10, completed 0, failed 51, total 64.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 2, waiting 10, completed 0, failed 52, total 64.
Loading of 'SAPAPPL2_13' import package: ERROR
Import Monitor jobs: running 1, waiting 10, completed 0, failed 53, total 64.
Loading of 'SAPAPPL2_12' import package: ERROR
Import Monitor jobs: running 0, waiting 10, completed 0, failed 54, total 64.
Import Monitor jobs: running 1, waiting 9, completed 0, failed 54, total 64.
Import Monitor jobs: running 2, waiting 8, completed 0, failed 54, total 64.
Import Monitor jobs: running 3, waiting 7, completed 0, failed 54, total 64.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 2, waiting 7, completed 0, failed 55, total 64.
Loading of 'SAPSDOCU' import package: ERROR
Import Monitor jobs: running 1, waiting 7, completed 0, failed 56, total 64.
Loading of 'SAPAPPL1_1' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 0, failed 57, total 64.
Import Monitor jobs: running 1, waiting 6, completed 0, failed 57, total 64.
Import Monitor jobs: running 2, waiting 5, completed 0, failed 57, total 64.
Import Monitor jobs: running 3, waiting 4, completed 0, failed 57, total 64.
Loading of 'SAPDDIM' import package: ERROR
Import Monitor jobs: running 2, waiting 4, completed 0, failed 58, total 64.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 1, waiting 4, completed 0, failed 59, total 64.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 0, waiting 4, completed 0, failed 60, total 64.
Import Monitor jobs: running 1, waiting 3, completed 0, failed 60, total 64.
Import Monitor jobs: running 2, waiting 2, completed 0, failed 60, total 64.
Import Monitor jobs: running 3, waiting 1, completed 0, failed 60, total 64.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 0, failed 61, total 64.
Loading of 'SAPUSER1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 0, failed 62, total 64.
Loading of 'SAP0000' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 0, failed 63, total 64.
ERROR 2009-10-27 10:53:37.125
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2009-10-27 10:53:37.140
FCO-00011 The step runMigrationMonitor with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
Thanks.

i checked the DOKCLU log, pls find the log below:
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20091027104307
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#20 $ SAP
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Aug 23 2009 23:42:38
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe -i DOKCLU.cmd -dbcodepage 4103 -k 1gage5M50Dp01eqte1]x3Qa5 -l DOKCLU.log -stop_on_error -loadprocedure fast LOAD
(DB) INFO: connected to DB
(GSI) INFO: dbname   = "ATD                                                                                "
(GSI) INFO: vname    = "DB6                             "
(GSI) INFO: hostname = "UNKNOWN                                                         "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "SERVER"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 23 Step 7)"
(DB) ERROR: DDL statement failed
( DROP TABLE "DOKCLU" )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
( CREATE TABLE "DOKCLU" ( "ID" SAPDB6CHAR(2) DEFAULT ' ' NOT NULL , "OBJECT" SAPDB6CHAR(60) DEFAULT ' ' NOT NULL , "LANGU" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "TYP" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "DOKVERSION" SAPDB6FIXCHAR(4) DEFAULT '0000' NOT NULL , "PAGENO" SMALLINT DEFAULT 0 NOT NULL , "TIMESTMP" SAPDB6CHAR(46) DEFAULT ' ' NOT NULL , "PAGELG" SMALLINT DEFAULT 0 NOT NULL , "VARDATA" VARCHAR(3800) FOR BIT DATA ) IN ATD#ES700D INDEX IN ATD#ES700I LONG IN ATD#ES700D )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(DB) INFO: disconnected from DB
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20091027104307
Thanks

Error in Import Abap step for MI 7.1on AIX oracle

hi guys,
i am installing sap MI 7.1 on AIX on oracle.while installing i am getting the following error in the import abap step
INFO: 2011-01-28 04:15:08
Data codepage 1100 is determined using TOC file '/oracle/MIP/oraarch/51033237/DATA_UNITS/EXPORT_1/DATA/REPOSRC.TOC' for package 'REPOSRC'.
TRACE: 2011-01-28 04:15:09 com.sap.inst.migmon.LoadTask run
Loading of 'DOKCLU' import package is started.
TRACE: 2011-01-28 04:15:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'DOKCLU' import package into database:
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load -i DOKCLU.cmd -dbcodepage 4102 -l DOKCLU.log -stop_on_error -loadprocedure fast
ERROR: 2011-01-28 04:15:11 com.sap.inst.migmon.LoadTask run
Loading of 'DOKCLU' import package is interrupted with R3load error.
Process '/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load -i DOKCLU.cmd -dbcodepage 4102 -l DOKCLU.log -stop_on_error -loadprocedure fast' exited with return code 2.
For mode details see 'DOKCLU.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2011-01-28 04:15:38
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2011-01-28 04:15:38
1 error(s) during processing of packages.
INFO: 2011-01-28 04:15:38
Import Monitor is stopped.
this is the log for DOKCLU
myCluster (127.18.Imp): 650: error when retrieving table description for physical table DOKCLU.
myCluster (127.18.Imp): 651: return code received from nametab is 2
myCluster (127.18.Imp): 294: error when retrieving physical nametab for table DOKCLU.
(CNV) ERROR: data conversion failed. rc = 2
(DB) INFO: disconnected from DB
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20110128090816
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load: START OF LOG: 20110128094510
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load: sccsid @(#) $Id: //bas/710_REL/src/R3ld/R3load/R3ldmain.c#10 $ SAP
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load: version R7.20/V1.4 [UNICODE]
Compiled Oct 25 2007 20:54:47
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load -i DOKCLU.cmd -dbcodepage 4102 -l DOKCLU.log -stop_on_error -loadprocedure fast
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(RTF) ########## WARNING ###########
Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
(DB) INFO: DOKCLU deleted/truncated #20110128094511
myCluster (127.18.Imp): 650: error when retrieving table description for physical table DOKCLU.
myCluster (127.18.Imp): 651: return code received from nametab is 2
myCluster (127.18.Imp): 294: error when retrieving physical nametab for table DOKCLU.
(CNV) ERROR: data conversion failed. rc = 2
(DB) INFO: disconnected from DB
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load: job finished with 1 error(s)
/usr/sap/MIP/SYS/exe/uc/rs6000_64/R3load: END OF LOG: 20110128094511

Hi,
Te problem seems to be a connection to Oracle.
Check the below note :
Note 400241 - Problems with ops$ or sapr3 connect to Oracle
Regards,
Nirmal.k

Inplace unicode conversion - error during import in step 2

Hi,
We are having problems when running the unicode conversion import in step 2: Load Kernel Library. The problem occurs when SAPINST runs the FIXR3OWNS program. We can run FIXR3OWNS manually when logged in with QSECOFR.
From the sapinst_dev.log file:
TRACE      [iaxxco4sys.cpp:57]
           iastring COS4SystemConnect::executeCommand(args_t const& _args)
OS4Trace: Executing remote iSeries command: FIXR3OWNS LIB(SAP700UNEW) OBJ(*ALL).
TRACE      [iaxxejsbas.hpp:451]
           EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception
TRACE      [iaxxcwalker.cpp:301]
           CDomWalker::processStep()
From the job log:
   R3ADMAUTL.
Authority given to user *PUBLIC for object R3DIR in SAP700UNEW object type
   *MENU.
Object authority granted.
Object R3KERNEL in SAP700UNEW type *MENU not secured by authorization list
   R3ADMAUTL.
Authority given to user *PUBLIC for object R3KERNEL in SAP700UNEW object
   type *MENU.
Object authority granted.
Object R3MAIN in SAP700UNEW type *MENU not secured by authorization list
   R3ADMAUTL.
Not able to allocate object R3MAIN in SAP700UNEW type *MENU.
error: call_AS400_command: "CPF2211" caught after "FIXR3OWNS
   LIB(SAP700UNEW) OBJ(*ALL)"
What could be wrong? It is our SIDOFR user?
Best regards
Henrik Hviid

Hi Volker,
Thank you very much. Stupid error :-).
I also did step 2 with fixr3owns yesterday with SAPINST and then it worked. I got to step 3 "iSeries Installation Step", but got an error in SAPINST when "Creating infrastructure for SAP system BND". I logged off SAPINST, patched CRTR3SYS and started SAPINST again and then got the error in step 2 wirh fixr3owns.
I´m now past step 2 and in step 3 "iSeries Installation Step". And I get the same error as I got yesterday...
From the job log:
TMKSVR request processor: request was successful
Processing request from client 10.96.220.5:4350.
EXECUTE CRTR3SYS SID(BND) GLOBALHOST('SAP002') FORCEPROF(*NO)
ADBHOST('SAP002') 1 N
Keyword GLOBALHOST not valid for this command.
Keyword FORCEPROF not valid for this command.
Keyword ADBHOST not valid for this command.
Error found on CRTR3SYS command.
Errors occurred in command.
error: call_AS400_command: "CPF0006" caught after "CRTR3SYS SID(BND)
GLOBALHOST('SAP002') FORCEPROF(*NO) ADBHOST('SAP002')"
I can run "CRTR3SYS SID(BND) GLOBALHOST('SAP002') FORCEPROF(*NO)" manually.
Do you have any ideas?
Best regards
Henrik Hviid

Really slow "importing photos" step when syncing

Every time I sync my Iphone5 to ITunes, the "importing photos" step (step 7 of 8) takes AT LEAST 5 minutes even though I'm not importing any new photos.

Reboot iTunes with your cable to iPhone connected.

Getting Error while installing abap Netweaver 7.02 trial, import Abap step

INFO       2011-12-25 18:15:04.687
           CJSlibModule::writeInfo_impl()
Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING    2011-12-25 18:15:36.932
           CJSlibModule::writeWarning_impl()
Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 2, completed 34, failed 0, total 37.
Import Monitor jobs: running 2, waiting 1, completed 34, failed 0, total 37.
Loading of 'SAPSSEXC_1' import package: ERROR
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 34, failed 2, total 37.
Import Monitor jobs: running 0, waiting 1, completed 34, failed 2, total 37.
ERROR      2011-12-25 18:15:36.932
           CJSlibModule::writeError_impl()
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR      2011-12-25 18:15:36.948 [sixxcstepexecute.cpp:988]
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
INFO       2011-12-25 18:15:37.244 [synxcpath.cpp:815]
           CSyPath::createFile() lib=syslib module=syslib
Creating file C:\Program Files\sapinst_instdir\NW702\AS-ABAP\ADA\CENTRAL\__instana_tmp.xml.
WARNING    2011-12-25 18:15:37.603 [iaxxejshlp.cpp:150]
Could not get property IDs of the JavaScript object.
ERROR      2011-12-25 18:15:37.603 [iaxxejsctl.cpp:492]
FJS-00010 Could not get value for property .
INFO       2011-12-25 18:19:54.317 [sixxcstepexecute.cpp:1073]
An error occured and the user decided to retry the current step: "|NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".
INFO       2011-12-25 18:19:54.317 [synxccuren.cpp:1016]
           CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(const CSyPath & C:/Program Files/sapinst_instdir/NW702/AS-ABAP/ADA/CENTRAL)
           lib=syslib module=syslib
Working directory changed to C:/Program Files/sapinst_instdir/NW702/AS-ABAP/ADA/CENTRAL.
INFO       2011-12-25 18:19:54.520 [synxccuren.cpp:775]
           CSyCurrentProcessEnvironmentImpl::setUser() lib=syslib module=syslib
Switched to user: Benazir\nspadm.
INFO       2011-12-25 18:19:54.660 [synxcpath.cpp:815]
           CSyPath::createFile() lib=syslib module=syslib
Creating file C:\Program Files\sapinst_instdir\NW702\AS-ABAP\ADA\CENTRAL\import_monitor.java.log.
INFO       2011-12-25 18:19:54.676 [synxccuren.cpp:775]
           CSyCurrentProcessEnvironmentImpl::setUser() lib=syslib module=syslib
Switched to user: Benazir\nspadm.
INFO       2011-12-25 18:19:54.707
           CJSlibModule::writeInfo_impl()
Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING    2011-12-25 18:20:25.080
           CJSlibModule::writeWarning_impl()
Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 2, completed 34, failed 0, total 37.
Import Monitor jobs: running 2, waiting 1, completed 34, failed 0, total 37.
Loading of 'SAPSSEXC_1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 34, failed 1, total 37.
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 34, failed 2, total 37.
ERROR      2011-12-25 18:20:25.080
           CJSlibModule::writeError_impl()
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR      2011-12-25 18:20:25.111 [sixxcstepexecute.cpp:988]
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
INFO       2011-12-25 18:20:25.408 [synxcpath.cpp:815]
           CSyPath::createFile() lib=syslib module=syslib
Creating file C:\Program Files\sapinst_instdir\NW702\AS-ABAP\ADA\CENTRAL\__instana_tmp.xml.
WARNING    2011-12-25 18:20:25.767 [iaxxejshlp.cpp:150]
Could not get property IDs of the JavaScript object.
ERROR      2011-12-25 18:20:25.782 [iaxxejsctl.cpp:492]
FJS-00010 Could not get value for property .
INFO       2011-12-25 18:21:19.431 [sixxcstepexecute.cpp:1073]
An error occured and the user decided to retry the current step: "|NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".
INFO       2011-12-25 18:21:19.431 [synxccuren.cpp:1016]
           CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(const CSyPath & C:/Program Files/sapinst_instdir/NW702/AS-ABAP/ADA/CENTRAL)
           lib=syslib module=syslib
Working directory changed to C:/Program Files/sapinst_instdir/NW702/AS-ABAP/ADA/CENTRAL.
INFO       2011-12-25 18:21:19.633 [synxccuren.cpp:775]
           CSyCurrentProcessEnvironmentImpl::setUser() lib=syslib module=syslib
Switched to user: Benazir\nspadm.
INFO       2011-12-25 18:21:19.867 [synxcpath.cpp:815]
           CSyPath::createFile() lib=syslib module=syslib
Creating file C:\Program Files\sapinst_instdir\NW702\AS-ABAP\ADA\CENTRAL\import_monitor.java.log.
INFO       2011-12-25 18:21:19.883 [synxccuren.cpp:775]
           CSyCurrentProcessEnvironmentImpl::setUser() lib=syslib module=syslib
Switched to user: Benazir\nspadm.
INFO       2011-12-25 18:21:19.930
           CJSlibModule::writeInfo_impl()
Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING    2011-12-25 18:21:50.240
           CJSlibModule::writeWarning_impl()
Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 2, completed 34, failed 0, total 37.
Import Monitor jobs: running 2, waiting 1, completed 34, failed 0, total 37.
Loading of 'SAPSSEXC_1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 34, failed 1, total 37.
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 34, failed 2, total 37.
ERROR      2011-12-25 18:21:50.256
           CJSlibModule::writeError_impl()
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR      2011-12-25 18:21:50.287 [sixxcstepexecute.cpp:988]
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
INFO       2011-12-25 18:21:50.599 [synxcpath.cpp:815]
           CSyPath::createFile() lib=syslib module=syslib
Creating file C:\Program Files\sapinst_instdir\NW702\AS-ABAP\ADA\CENTRAL\__instana_tmp.xml.
WARNING    2011-12-25 18:21:50.973 [iaxxejshlp.cpp:150]
Could not get property IDs of the JavaScript object.
ERROR      2011-12-25 18:21:50.973 [iaxxejsctl.cpp:492]
FJS-00010 Could not get value for property .
INFO       2011-12-25 18:21:55.154 [sixxcstepexecute.cpp:1081]
An error occured and the user decided to stop.\n Current step "|NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".
INFO       2011-12-25 18:22:06.995 [synxccuren.cpp:1016]
           CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(const CSyPath & C:/Program Files/sapinst_instdir/NW702/AS-ABAP/ADA/CENTRAL)
           lib=syslib module=syslib
Working directory changed to C:/Program Files/sapinst_instdir/NW702/AS-ABAP/ADA/CENTRAL.
Abort execution because of
controller.userDecideToStop
INFO       2011-12-25 18:22:07.73 [synxcpath.cpp:815]
           CSyPath::createFile() lib=syslib module=syslib
Creating file C:\Program Files\sapinst_instdir\.lastInstallationLocation.
CGuiProxy::receive(): receive error on socket 616
Dec 25, 2011 6:22:07 PM [Info]: >> Closed input stream
Dec 25, 2011 6:22:07 PM [Info]: >> Closed input stream
Dec 25, 2011 6:22:07 PM [Info]: GUI stopped.
Exit status of child: 2

HI,
CONFIG: 2011-12-25 12:51:20
List of packages with table structure: 'SAP0000'.
CONFIG: 2011-12-25 12:51:20
List of packages with views: 'SAPVIEW'.
TRACE: 2011-12-25 12:51:20 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\NW702\AS-ABAP\ADA\CENTRAL\DDLADA.TPL' template file is started.
INFO: 2011-12-25 12:51:20 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\NW702\AS-ABAP\ADA\CENTRAL\DDLADA.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2011-12-25 12:51:20
Data codepage 4103 is determined using TOC file 'D:\NWABAPTRIAL70206_64\NWABAPTRIAL70206_64_EXPORT\NWABAPTRIAL70206_64\SAP_NetWeaver_702e_Export\DATA_UNITS\EXP1\DATA\ATAB.TOC' for package 'ATAB'.
TRACE: 2011-12-25 12:51:20 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_1' import package is started.
TRACE: 2011-12-25 12:51:20 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_3' import package is started.
TRACE: 2011-12-25 12:51:20 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_1' import package into database:
C:\usr\sap\NSP\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_1.cmd -dbcodepage 4103 -l SAPSSEXC_1.log -nolog -c 50000 -force_repeat -loadprocedure dbsl
TRACE: 2011-12-25 12:51:20 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_3' import package into database:
C:\usr\sap\NSP\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_3.cmd -dbcodepage 4103 -l SAPSSEXC_3.log -nolog -c 50000 -force_repeat -loadprocedure dbsl
ERROR: 2011-12-25 12:51:20 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_1' import package is interrupted with R3load error.
Process 'C:\usr\sap\NSP\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_1.cmd -dbcodepage 4103 -l SAPSSEXC_1.log -nolog -c 50000 -force_repeat -loadprocedure dbsl' exited with return code 2.
For mode details see 'SAPSSEXC_1.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2011-12-25 12:51:20 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_3' import package is interrupted with R3load error.
Process 'C:\usr\sap\NSP\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_3.cmd -dbcodepage 4103 -l SAPSSEXC_3.log -nolog -c 50000 -force_repeat -loadprocedure dbsl' exited with return code 2.
For mode details see 'SAPSSEXC_3.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2011-12-25 12:51:50
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2011-12-25 12:51:50
2 error(s) during processing of packages.
INFO: 2011-12-25 12:51:50
Import Monitor is stopped.
THANKS

When syncing with iTunes what does the "importing photo" step do? I don't see my photos imported?

When I sync my iphone 4s I see "importing photos" as one of the steps it is going through in syncing. However, I don't see the iphone photos in iphoto or elsewhere. I turned off the photo stream feature for various reasons. Is that why I see no import? Is there some other setting I need to check?
Thanks.

No one? I still havent figured this out.

Import "RAW files only" also imports JPEGS (+ steps to reproduce)

I filed this bug report to Apple:
Summary:
When importing "RAW files only" the accompanying JPEGs are also imported when the files are stacked (cmd-K) in the import screen.
Steps to reproduce:
1. Create a new library
2. Insert a card from a camera (checked with Canon G9, Lumix DMC-LX3) which holds RAW files and their accompanying JPEG files (same filename, different extension)
3. Cmd-I to import, if the import screen does not open by itself.
4. Make sure "RAW files only" is selected
5. Select "Uncheck All"
6. Select a few RAW files (for example 4) (click first, shift-click last, click checkbox, all 4 are selected at once)
7. Cmd-K to put them in a stack.
Above the "Import Checked" button the number of files to be imported is shown, 4 in this case.
8. Click "Import Checked"
Wherever the images are imported, not only the 4 RAW files will be imported, but also the accompanying JPEG files. This is also the case when only JPEGs are requested, in that case the RAW files will be imported as well.
Is is essential that the images to be imported are stacked in the import screen. If this is omitted, only the requested files (either RAW of JPEG) are imported (4 in this example).
Koen

Hi again
Sorry the delay in getting back to my post but I've been a tad busy.
Well, after a bit of testing I can confirm that the problem does seem to be an issue with Vista (32bit and 34 bit) as Jeff states.
I tried importing the raw files into Vista 32-bit, Vista 64-bit and XP 32-bit and whilst all operating systems allowed the import of JPEG files, I was only able to import the raw files into XP.
I havent got a card reader so am unable to test this at the moment.
Stephen

SAPINST stopped at IMPORT ABAP step

Please help if you can
sapinst showing the following error:
An error occurred while processing option SAP ERP 6.0 EHP4 Ready - Support Release 1 > SAP Application Server ABAP > Oracle > Central System > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
in import_monitor_java.log , i get the following:
Loading of 'SAPAPPL0' import package: ERROR
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.
at the end 26 were imported successfully, 1 with error i.e. SAPAPPL0 and other one is waiting
In SAPAPPL0.log I get the following:
(RFF) ERROR: invalid checksum in data file "/media/sap/install/nw701/51036902/DATA_UNITS/EXPORT_5/DATA/SAPAPPL0.001"
current table was "SMIMPHIO"
(DB) INFO: disconnected from DB
/usr/sap/HRD/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/HRD/SYS/exe/run/R3load: END OF LOG: 20111006080022

Hi,
yes, damaged file definitely.
I think you should copy fully the installation files from DVD/CD (Make sure the installation media is downloaded fully) into local disk, and run the installation locally.
You can compare the checksums (you may use a freeware tool such as 'md5sum')
and compare both checksums from source and targetfile
Regards,
Vincent

Import procedure -step by step

Dear all,
can anybody explain total import procedure along with miro and migo with total account postings of excise n customs duty?
Full points assured..
thanks in advance.

Import scenario
To map Import procedure into SAP , follow the following steps :
1.Create material master of import goods.
2.Create vendor master record of import vendor and Customs clearing vendor.
3.Maintain CIN settings.
4.Maintain J1id.
5.Maintain Pricing procedure SAP standard JIMPOR..,maintain required conditions..JCDB,JCV1...
6.Assign the schema to respective import vendor in Purchasing view of VMR.
Process
Create import PO ,check in conditions of JCDB, JCV1 the customs clearing vendor(Indian vendor) and percentage is assigned..This can be done by In condition tab select condtion then click on display,then enter.
Save the PO.
MIRO --Capture Bill Of Entry.(Commercial Invoice No.,).Customs clearing first .Here CVD will b converted to BED.
Capture Excisse invoice--j1iex.
MIGO.
Post Excise Invoice.
MIRO...Payment to vendor(import vendor)
IMPORT ENTRIES
Find the fin. acct, entry genrated by system with end of every transaction and Import Business Process.
1. Create PO, in contion tab of PO , maintaint all possible Bill of entry coponent and assigned it with custom vendor.
2. Create MIRO for custom vendor ( Planned delivery cost)
FI Entry of Import (Planned Delivery Cost)
1 K 2001000 customs                            60,592.36- INR
2 S 2027100 CVD Clearing                           336.07INR
3 S 2025000Customs Provision                  9,845.38INR
4 S 2025000Customs Provision                   985.38INR
5 S 2027100CVD Clearing                       33,606.65INR
6 S 2027100CVD Clearing                            672.13INR
7 S 2025000Customs Provision                    492.69INR
8 S 2025000Customs Provision1               4,654.06 INR
3. Create GR for Excisable /non-excisable mat.
for Material
1 89 4002100 RM:coal                                   221,365.01 INR
2 96 2021000 Provisional Liab-GR                  195,387.50- INR
3 50 2025000 Customs Provision                     14,654.06- INR
4 50 2025000 Customs Provision                         985.38- INR
5 50 2025000 Customs Provision                          492.69- INR
6 50 2025000 Customs Provision                      9,845.38- INR
for Excise
1 40 4610410 RG 23A-Higher Ed Ces                   336.07 INR V0
2 40 4610100 RG 23A-BED                            33,606.65 INR V0
3 40 4610400 RG 23A-Ed Cess                           672.13 INR V0
4 50 2027100 CVD Clearing                           34,614.85- INR V0
4. create MIRO for importer liab.
FI for Vendor( Importer)
1 K 2001000 test /                                       195,387.50- INR
2 S 2021000 Provisional Liab                         195,387.50 INR
refer following doc for customization and procedure
http://help.sap.com/bp_bblibrary/500/html/J83_ProImportedMat_EN_IN.htm
regards
kunal

How to Query/Lookup Data Target HFM Application in FDMEE Import / Validation Step

Hi Experts,
We are using FDMEE 11.1.2.3.500 to load 2 sets of Flat Files - ICP Trial Balances and Non-ICP Trial Balances. The ICP Trial Balances will be loaded to Target HFM Application first using FDMEE and then the remaining Non-ICP Trial balances Load would follow
We have a complex business requirement wherin we want to check if the Non-ICP Trial Balances for a given ENTITY, ACCOUNT, [ICP None] combination in the Trial Balance File matches the already loaded ICP Trial Balances for ENTITY, ACCOUNT, [ICP Total]. If it matches then this record has to be skipped from our data load else it has to be loaded. To elaborate with an example:
                                                              Entity    Account     ICP              Amount
File 1 (ICS_TB.csv) - Record 1 ->          E1          A1           P1                  100
File 1 (ICB_TB.csv) - Record 2 ->          E1          A1           P2                  300
Above File Gets Loaded First
File 2 (Non_ICP_TB) - Record 1->          E1          A1          [ICP None]      400    (Record to be skipped - It matches the above already loaded File)
Is it possible to validate this during Import or Validate Step in FDMEE? if yes, can you please throw some light on how this can be done?
Thanks!

As far as I am aware there is no seperate Java API reference manual for FDMEE, you are limited to the information available in the Admin Guide for now. If you feel that it is not comprehensive enough perhaps you could raise a ticket or enhancement request via Oracle Support.
The sysntax for the statement should be dmAPI.executeDML(String query,Object[] parameters) according to the AG, I wouldn't put 100% trust in that as it can often be incorrect, but give it a try. Ensure the 2nd parameter is a Jython list.
I don't think the method supports passing a Stored Procedure and there doesn't appear to be another native API method listed that would do that. You could initiate the connection using standard Python or Java libraries and then use a cursor and prepared statements to execute the sql or the callproc method of the Python DB API

Importing memos help

my computer crashed. had to do a recovery of the software. had many voice memos that were not imported into itunes yet. since my ipod software is not loaded back on, what can i do in order not to lose these. i need them loaded. i do not have a burner. if i lose these memos, i will lose my job.
20 gb click wheel Windows XP

Put the iPod into Disk Mode, and then drag the items from the Recordings folder on the iPod to your computer's hard disk. More information is available in this article.
(13762)

Error by Step 'Import ABAP' (SolMng 7.01 MaxDB/Linux 64bit)

Hello
I'm Installing the Solution Manager on Red Hat 5 (Linux x86_64) with MaxDB 7.7.
The installation stops by the step "Import ABAP".
Using the User <sid>adm I get:
hostname:sm0adm 14> /usr/sap/SM0/SYS/exe/run/R3load -testconnect
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
/usr/sap/SM0/SYS/exe/run/R3load: START OF LOG: 20110108224646
/usr/sap/SM0/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/SM0/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
Compiled Sep 20 2010 21:57:57
/usr/sap/SM0/SYS/exe/run/R3load -testconnect
(DB) ERROR: DbSlControl(DBSL_CMD_IMP_FUNS_SET) rc = 20
(DB) ERROR: DbSlErrorMsg rc = 20
/usr/sap/SM0/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/SM0/SYS/exe/run/R3load: END OF LOG: 20110108224646
This is exactly the same error as in the installation protocol.
The error is similar to
ECC6 Install Error at "Import ABAP" step
but on Linux and not on Windows.
I also installed the latest R3load, but I get the same error.
Any hint would be appreciated.
Regards
T.C.

Solved.
/usr/sap/SM0/SYS/exe/run/R3load -testconnect
/usr/sap/SM0/SYS/exe/run/R3trans -d
less trans.log
https://service.sap.com/sap/support/notes/1193243
rpm --install --force /mnt/data/libstdc++-3.2.3-60.x86_64.rpm

Workflow for MM purchase Requisition steps required

Dear all,
        I am trying to configure purchase requisition Workflow.
        I am working with Work flow, WS 00000038
        I have assigned agents to TS 20000162
        Now how to proceed further, do i need to maintain some more settings
        or i should try to test system.
        Regards,
        Gaurav sood

Under the assumption that things have not changed much since 4.70, here's quick introduction:
The workflow is started only when a relevant release strategy is found, so customizing of release strategies is a very important (first) step here.
In the Implementation Guide you find the customizing in the following path:
Materials Management
-- Purchasing
-- -- Purchase Requisition
-- -- -- Release Procedure
-- -- -- -- Procedure with Classification
Only the procedures with classification are relevant if you want to use workflow to notify about requisitions waiting for release.
First you must set up a classification class if that has not already been done. Derive your characteristics from the structure CEBAN. The online help is not too bad, I had never set up classifications before and managed to get it working.
If you need data that are not available in CEBAN, or you want to modify them for the purpose of determining the release strategy there is an enhancement you can implement, and there are customer fields you can use. The enhancement definition's name is M06B0002.
As an example of what you can do, I have used it to set the company code in one of the customer fields, and to change the account assignment type. However, whether you need this enhancement or not depends strongly on what data you use to determine your release procedures (a step in customizing you will get to later).
When that is done you define release groups and release codes. Release codes are defined within each release group. Whether you should use one group or several groups is often a matter of choice.
I myself prefer using several groups even if I don't have to, so long as it doesn't lead to having to define duplicate release strategies (which you will soon get to). So, if there is some characteristic that clearly separates your release strategies, e.g. the highest amount that does NOT require release etc, you can define one group for each value (group) of this characteristic.
For instance, if some company codes require release for everything worth more than 100EUR while the default is to require release from 10.000EUR you could create to release groups. None of your release strategies will be duplicates since the value from which release is required will be different and you thus need to have that as a characteristic.
You then check that the set-up of release indicators is OK, and then you are ready to start defining the strategies. Release stragies are defined within each release group, and use one or more release codes (two or more release indicators).
It is fairly self-explanatory once you get into the screens. The thing to be observant about is to not define overlapping strategies, as this will prevent the solution from working.
When you are done, and have tested the solution in DEV it is time to transport it to the QA system. That's when I got a rather unpleasant surprise. The classification data are not transported, so both the characteristics and class, as well as the classification data in each release strategy had to be redefined. And in roughly two hours I have to do it again in production.
It is possible to transport classification information, it is described in SAP OSS Notes (different solutions for different versions).

Supplier Network Collaboration : Implementation pre-Steps

Hi All,
I am looking for some important pre-steps/Knowledge , which i need to understand for implementing the SAP SNC at customer end.
I have got a theoretical knowlege of all the business process in sap SNC and also i have gone thru the SAP SNC Config guide.
Please suggest!.
Thanking in Advance.
Regards,
Shashi

Resolved

Importing memos (step by step)

Similar Messages

Maybe you are looking for