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

Similar Messages

  • Import Procedure Customization and Steps in Import Cycle

    Dear SAP experts,
    My client wants to map the Import purchase in SAP.
    I would like to know the import procedure process in purchasing and what are the various documents involved in the whole cycle.
    And how to map the same in SAP.
    1. Customization steps needed to map this scenario in SAP. - Including Pricing procedure, condition types, schema, tax code to be created, account keys, any account determination steps needed.
    2. Steps involved in the import procedure.Including the creation of Vendor. ( customs office ? how to create the same and use
    the same.)
                   How to do the GR in import procedure.Also what are the steps to be followed in Invoice verifications of import .
    Also mention the various accounts posted in the whole process.
    If anyone can send me the links where details along with screenshots can be found.
    Best Regards,
    MM

    Hi,
    In case of Import PO, Excise Duties don't come from Tax Procedure, These come from MM Pricing. Here you have to use a Zero % Tax Code.
    First of all create following condition types in M/06, as suggested below method;
    JCDB IN:Basic Custom Duty
    JCV1 IN : CVD
    JECV IN : Ed Cess on CVD
    J1CV IN : H&SECess on CVD
    JEDB IN : Ed Cess on BCD
    JSDB IN : H&SECess on BCD
    JADC Addnl Duty of Custom
    JCV1, JECV, J1CV and JADC will go to Excise MODVAT Accounts and JCDB, JEDB and JSDB will get loaded on inventory.
    In M/06, for all above conditions, keep following controls;
    Cond. class A (Discount or surcharge) Plus/minus A (Positive)
    Calculat.type A (Percentage)
    Cond.category B (Delivery costs)
    Activate "Currency Conversion" and "Accrual"
    Vendor in GR 2 (Entry always possible)
    Then assign the above condition types in Imort Pricing in M/08
    Also check following;
    SPRO > Logistics - General > Tax on Goods Movements > India > Basic Settings > Determination of Excise Duty > Maintain Excise Defaults > Here assign following for Tax Procedure;
    CVD cond. - CV1
    ECS cond. - JECV
    ADC cond. - JADC
    And J1CV need not be assigned since it is hard-coded in SAP Standard program.
    Also do account determination in OBYC as your have already done for MIRO of Customs Invoice.
    Also check in SPRO > Logistics - General > Tax on Goods Movements > India > Basic Settings > Maintain Company Code Settings > Here Assign CVD Clearing A/c in your Company Code.
    In case of Import Purcase;
    1. First you create Import PO and input all the Import duties in PO.
    2.Then you do LIV for Customs Office (Here you enter all the Import duties as per Bill of Entry) and following A/c entry get generated;
    Customs Office A/c - Cr (Vendor Recon A/c)
    Customs Duty Clearing A/c - Dr (OBYC - ZCC)
    CVD Clearing A/c - Dr (OBYC - ZCV)
    3. Then Capture Bill of Entry in J1IEX.
    4. Then you do GR w.r.t. Import PO (MIGO), Accounting Entry will come as following;
    Stock A/c - Dr (OBYC - BSX)
    GR/IR Clearing A/c - Cr (OBYC - WRX)
    Customs Clearing A/c - Cr (OBYC - ZCC)
    5. Post Bill of Entry in J1IEX, and Accounting Entry will come as following;
    CENVAT Receivable A/c (BED, ECS, SECess and ADC) - Dr (From Account Detmn of GRPO with Sub Trans Type - IP)
    CVD Clearing A/c - Cr (From Compnay Code Settings of Excise)
    6. MIRO - For Import Vendor
    Import Vendor - Cr (Recon A/c)
    GR/IR Clearing A/c - Dr (WRX)
    7. MIRO - For Clearing Agent
    Out of following conditions;
    JCDB IN:Basic Custom Duty
    JCV1 IN : CVD
    JECV IN : Ed Cess on CVD
    J1CV IN : H&SECess on CVD
    JEDB IN : Ed Cess on BCD
    JSDB IN : H&SECess on BCD
    JADC Addnl Duty of Custom
    JCDB, JEDB, JSDB will get loaded to Stock and JCV1, JECV, J1CV and JADC will get posted to CENVAT Receivable A/c
    In M/08, assign A/c Key ZCC to JCDB, JEDB, JSDB conditions and Customs Clearing A/c in OBYC and A/c Key ZCV to JCV1, JECV, J1CV and JADC conditions and CVD Clearing in OBYC.
    Note: - Here you don't have to use Tax Procedure Accounting (OB40) in case of Imports. Only maintain a Zero % Tax Code in Import PO.

  • 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

  • Passing parameters into ODI procedure step which has an OS command

    Folks,
    I have an ODI procedure step which does a directory listing for a specific directory. The command I am using is
    cmd /C dir d:\local_dir /b > D:\dir_list.txt
    I have put on the 'Command on Target' tab. This works fine
    I want to remove the hardcoding for the directory references. I have tried the command
    cmd /C dir '#src_dir' /b > D:\dir_list.txt
    but when this executes it generates an ODI error 'Wrong process return code'
    any suggestions?

    I've figured it out. The issue was with using quotes in the value being passed into the variable. Once removed, it worked fine. Thanks for the assistance.
    Regards.
    Edited by: user810644 on 17-May-2010 01:59

  • How to run dynamic SQL from an ODI procedure step

    I am on ODI 11.1.1.6.4. From within an ODI IKM step I have no problem running a procedure step like the following which calls a pl/sql procedure to get SQL text then later runs that code. Is there anyway to do the same from within an ODI procedure? I've tried a couple of variations and can not seem to get the parsing levels to resolve within a procedure like they resolve from within a KM step.
    <@
    /* Setup Java variables */
    String out_SQL = "";
    try
    java.sql.Connection sourceConnection = odiRef.getJDBCConnection("SRC");
    String sqltxt = "{call set_sql(?)}";
    java.sql.CallableStatement pstmt = sourceConnection.prepareCall(sqltxt);
         try
         pstmt.registerOutParameter( 1, java.sql.Types.VARCHAR);
         pstmt.execute();
    out_SQL = pstmt.getString(1);
         catch(java.sql.SQLException ex)
              errMessage = ex.getMessage();
              errMessage = errMessage.replace("'","");
         finally
              pstmt.close();
    catch(java.lang.Exception e)
         errMessage = e.getMessage();
         errMessage = errMessage.replace("'","");
    @>
    BEGIN
    -- The SQL that I want to run
    <@
    out.println(out_SQL);
    @>
    -- Error handling
    <@ if ( out_SQL.length() ==0 ) { @>
         raise_application_error(-20101, '<@=errMessage@>');
    <@ } else { @>
         dbms_output.put_line('Successful.');
    <@ } @>     
    END;
    ------

    Please understand that I know that I can do this all within PL/SQL -- I am explicitly doing it the way I have outlined because I want to better understand the parsing levels/behavior within ODI procedures and I want to understand why KMs steps behave differently.
    Another observation -- putting this all within a pl/sql block prevents ODI from properly capturing insert/update/delete row counts like it would if it were running a SQL statement.
    So the question remains -- is there a way to run a dynamic SQL statement in an ODI procedure where the SQL statement is generated from within an Oracle procedure call and then run as SQL within an ODI procedure step? Best would be if there is an example of how this can be done.

  • HT4356 AirPrint Support in the Printer Side (Request for Official Procedure/Steps)

    *I selected the iPhone community (but this is for Apple's AirPrint Support in general)
    We are currently considering to add support for AirPrint
    in our printer-side development.
    Does anyone know how can receive official information from Apple regarding
    the required procedure/steps to correctly support
    AirPrint in the printer side?
    We are expecting that such steps would also contain details
    on how our printers can become listed later on
    in the following Apple page containing the official AirPrint printers:
    http://support.apple.com/kb/HT4356
    We understand that Apple may need to conduct
    some conformance tests in order to consider
    that our printer has already officially supported AirPrint,
    so we may need to consider such also in our schedule.

    Aliel2-
    The round button at the bottom of the iPad's front is your Home button.  The Sleep button is on the top edge near the right corner.
    Normally the Sleep button just puts the iPad to sleep but does not acgtually turn it off.  If you used the "Slide to power off" arrow and turned it off, you will need to hold the Sleep button for several seconds until the Apple logo appears, in order to turn the iPad back on.
    I wonder if you did the reset the right way, but just did not hold both buttons long enough for the Apple logo to appear?  I just tried it on my iPad 2, and it took 17 seconds before the Apple logo appeared.  It took another couple of minutes for it to restart to the "slide to unlock" screen.
    Fred

  • AirPrint Support (Request for Official Procedure/Steps)

    *I selected the iPad community as category (but this is for Apple's AirPrint Support in general)
    We are currently considering to add support for AirPrint in our printer-side development.
    Does anyone know how can receive official information from Apple regarding
    the required procedure/steps to correctly support AirPrint in the printer side?
    We are expecting that such steps would also contain details
    on how our printers can become listed later on
    in the following Apple page containing the official AirPrint printers:
    http://support.apple.com/kb/HT4356
    We understand that Apple may need to conduct
    some conformance tests in order to consider
    that our printer has already officially supported AirPrint,
    so we may need to consider such also in our schedule.
    Any information will be helpful.
    Thanks!

    arch is growing that fast, it is hard to keep an overview. but as long as i, as an "afternoon linux user", can get any information, it is fine with me.

  • 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.

  • HT5312 How do I reset the security questions ? I followed the procedure step by step and I had no " reset info security email " option!

    How do I reset the security questions ? I followed the procedure step by step and I had no " reset info security email " option!

    Welcome to the Apple Community.
    Start here (change country if necessary) and navigate to 'Password and Security', reset your security questions using the link provided, you will receive an email to your rescue address, use the link in the email and reset your security questions.
    If that doesn't help, you don't receive a reset email or you don't have a rescue address, you should contact AppleCare who will initially try to assist you with a reset email or if unsuccessful will pass you to the security team to reset your security questions for you.
    If you are in a region that doesn't have international telephone support try contacting Apple through iTunes Store Support.

  • Mandatory field Export/Import Procedure for Foreign Trade

    Hello all!
    Is there any possibilty to define the field Export/Import Procedure for Foreign Trade
    within the infoset as a mandatory field?
    Table T162 doesn't show me this field.
    Kind regards,
    Barbara

    Hello,
      in customizing under "Materials Management --> Purchasing --> Foreign Trade/Customs --> Control Foreign Trade Data in MM and SD Documents --> Incompleteness Schemas for Foreign Trade Data" you can create an incompletion procedure defininig the documents fields assigning a control type. Then in the subsequent customizing step "Foreign Trade Data in MM and SD Documents" you can assign the Incompleteness schema to each country code, choosing import or export.
    Hope to be useful.
    Best regards,
    Andrea

  • Import procedure in PO??

    Hi All,
    How can I get import procedure determined automatically in an import PO?
    I have maintained the configuration still its not there.....what could I be missing?
    Regards,
    V S

    Hi,
    Please refer below link 
    http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm
    Regards,
    Vinay

  • Foreign trade data: import procedure determination in PO

    Hi,
    The import procedure field in my PO is sometimes filled in sometimes not. When I use PO-Type ZFA I get my import procedure automaticaly filled. When I use PO-Type ZRP i do not get it filled in. Although the Article, supplier and plant are exactly the same. Where can I give in the default value for import procedure for each PO-type?

    hi,
    please check this
    Sales and Distribution -- Foreign Trade/Customs -- Basic Data for Foreign Trade -- Define Business Transaction Types And Default Value

  • Pricing , freight conditon type, import procedure in pricing , taxes

    I understood the pricing , but what with some exercises from where get this?
    How many conditon type will be used in MM ?
    <b>pricing , freight conditon type, import procedure in pricing , taxes</b>
    which conditon types used ? what make the settings in freight conditons ?

    Hi PV
    You can go for Alt calc type ,there we can write, the requirement what we need and that has to be put in the subtotal table
    Reward if useful
    Regards
    Srianth

Maybe you are looking for