Create Gate Entry (Transport) CIN SAP

Dear All,
I have activated CIN (country version India) in my system and I am trying to create gate pass using tcode /cvs/gnt01
But system is throwing following error:
Transaction /CVS/GNT01 does not exist
Would you please let me know how you have accessed the Create Gate Entry (Transport) screen?
What is the menu path/tcode for that?
P.S. I am able to access other transactions related to CIN like create excise invoice, list of GRs w/o Gate pass etc.
Regards,
Ali

Dear Ali,
There is no standard process for Gate Entry other than LECI but you can customized as per your requirement, we have developed Gate Entry and Exit process for one of our client and since it is processing smoothly.
1. Gate Entry screen contains 2 radio button and it can be created w.r.t PO and Inbound Delivery.
2. The screen contains Invoice no and date, PO number, IBD number, Vendor, Plant, Location and Transportation details like No of cases, LR number, LR date, Vehicle number, Transporter Name, Mode of transport etc...
3. We have used the following Tables
LIKP, LIPS, EKPO, EKKO,  j_1imovend,  j_1imoddet1
4. Ask your ABAPers to put a) Table control declaration, b) Structure declaration for PO as well as IBD,  c) Internal Table and work area declaration,  d) Constant declaration.
5. Write program with below call function (Choose right one as per the requirement)
     a) CONVERSION_EXIT_ALPHA_OUTPUT.
     b) BAPI_GOODSMVT_CREATE.
     c)  BAPI_TRANSACTION_COMMIT.
     d)  RP_CALC_DATE_IN_INTERVAL.
Hope you clear....
Regards,
Karna J

Similar Messages

  • When materials are returned from customer how to create gate entry ?

    I need to create gate entry for customer return materials before doing PGR. Is there any process available in SAP?
    Pls help
    Jaya

    HI
    you can do one thing
    At the time of doing PGR create a new output type and design smart form / Script based on client requirement and take the print out at the time of PGR
    and also if you want to check the stock for Return material you can track in the system by using MB51 you can find out rather than doing manually because one if you done PGR means you received the Stock
    if i am wrong please correct me
    Regards,
    Prasanna

  • Gate Entry Module In SAP

    Dear Experts,
    We wants to map Gate Entry .
    What are the factors i should consider while devloping the Programe.What is the reference document i should consider and do i need to create any Ztable for the same.
    Can i print the Gate Pass.
    Also any goods movement should i consider.And how to map inward as well as outward and return goods movement.
    Request you to provide me all possible details and logic for the same to map the scenarion in SAP.
    Best Regards,
    SAP MM

    Hi
    There is a module called Yard management.Pl ckeck
    Maganti

  • Creating second InfoView entry point for SAP users in XI 3.1

    Hi All,
    I have BOE XI 3.1 up and running with the Business Objects Integration kit SAP Solutions kit I would like to create a second infoview entry point for SAP users on the same physical box (single server) as regular InfoView. 
    I am trying to mock this up and have detailed the following steps below.  I suspect I am missing a few steps (for example, where do I specify the entry port?).  I am sure step 2 is wrong, as I the desktoplaunch no longer exists in Xi 3.1
    1.  Copy the InfoView.war file to a new directory ( Program Files/Business Objects/ Business Objects Enterprise 12.0/java/applications/sap).  I imagine I would need to rename the war file (say SAPInfoview.war)?
    2.  Create a xml file with the following logic (the part in bold I consider to be wrong...):
    <Context docBase="Program Files\Business Objects\Business Objects Enterprise 12.0\java\applications\sap\SAPInfoview.war" path="/
    businessobjects/enterprise115/desktoplaunch"
    crossContext="false" debug="0" reloadable="false"
    trusted="false"/>
    3.  Save the xml file (what name? does it matter) in Program Files\Business Objects\Tomcat55\conf\Catalina\localhost
    4.  Restart Tomcat
    5.  Change the web.xml to make SAP security the default.  But this should not be the regular infoview web.xml.  I'm not sure where this would reside.
    Thanks,
    Steve
    Edited by: Steve Bickerton on Jan 15, 2009 9:19 PM

    Hi Ingo,
    You've been working with Duncan and Sartaj on this.  The client has two set of users:  non HR which has no BW or R/3 authorization restrictions, and HR, which has authorization restrictions.
    They have deployed SSO using AD for the non HR users.  They also want to leverage InfoView rather than the SAP portal.  For the HR users, we therefore need to capture the SAP id and password at login time to enforce security at the BW and R/3 levels.  We could use the existing Infoview entry point (SSO will fail and they will be prompted for a SAP login).  I do remember that we offered a second InfoView entry point for SAP users in XIR2.  I thought this may be more elegant.
    Thanks,
    Steve

  • Error in Gate Entry

    Hi,
        can any one guide me in soving this issue. The issue is when i executing the gate entry table in se16 in getting dump error "DBIF RSQLSQL_ERROR"
    Runtime Error       DBIF_RSQL_SQL_ERROR
    Except.                CX_SY_OPEN_SQL_DB
    Date and Time      28.04.2008 11:03:32
    ShrtText
    An SQL error occurred when accessing a table.
    What can you do?
    Make a note of the actions and input which caused the error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    How to correct the error
    Database error text........: "Column COMINV not in specified tables. MSGID=
    Job=055461/BDP00/WP00"
    Internal call code.........: "[RSQL/OPEN//CVS/TA_GTHDR ]"
    Please check the entries in the system log (Transaction SM21).
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
    "/1BCDWB/DB/CVS/TA_GTHDR" or "/1BCDWB/DB/CVS/TA_GTHDR"
    "START-OF-SELECTION"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    System environment
    SAP Release.............. "640"
    Application server....... "PRDSAPBD"
    Network address.......... "131.0.0.15"
    Operating system......... "OS400"
    Release.................. "5.3"
    Hardware type............ "0065000655EC"
    Character length......... 8 Bits
    Pointer length........... 64 Bits
    Work process number...... 0
    Short dump setting....... "full"
    Database server.......... "PRDSAPBD"
    Database type............ "DB400"
    Database name............ "BDP"
    Database owner........... "R3BDPDATA"
    Character set............ "en_US.ISO8859-1"
    SAP kernel............... "640"
    Created on............... "Jul 9 2006 22:10:13"
    Created in............... "AIX 1 5 00538A4A4C00 (iSeries)"
    Database version......... "DB4_52"
    Patch level.............. "137"
    Patch text............... " "
    Supported environment....
    Database................. "V5R2, V5R3, V5R4"
    SAP database version..... "640"
    Operating system......... "OS400 2 5, OS400 3 5, OS400 4 5"
    Memory usage.............
    Roll..................... 16128
    EM....................... 12569784
    Heap..................... 0
    Page..................... 49152
    MM Used.................. 1508288
    MM Free.................. 2679120
    SAP Release.............. "640"
    User and Transaction
    Client.............. 009
    User................ "INTBASIS"
    Language key........ "E"
    Transaction......... "SE16 "
    Program............. "/1BCDWB/DB/CVS/TA_GTHDR"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    The termination occurred in the ABAP program "/1BCDWB/DB/CVS/TA_GTHDR" in
    "START-OF-SELECTION".
    The main program was "/1BCDWB/DB/CVS/TA_GTHDR ".
    The termination occurred in line 547 of the source code of the (Include)
    program "/1BCDWB/DB/CVS/TA_GTHDR"
    of the source code of program "/1BCDWB/DB/CVS/TA_GTHDR" (when calling the
    editor 5470).
    Source Code Extract
    Line
    SourceCde
    517
    RSEUMOD-TBMAXSEL = MAX_SEL.
    518
    ELSEIF MAX_SEL = 0.
    519
    CLEAR RSEUMOD-TBMAXSEL.
    520
    ENDIF.
    521
    IMPORT G_DATA_EXIT FROM MEMORY ID MEM_ID.
    522
    IF SY-BATCH IS INITIAL AND G_DATA_EXIT IS INITIAL.
    523
    IMPORT ACTION FROM MEMORY ID MEM_ID.
    524
    ELSE.
    525
    ACTION = 'ANZE'.
    526
    concatenate '/1BCDWB/DB' '/CVS/TA_GTHDR' into g_dbdatakey-eu_name.
    527
    g_dbdatakey-username = c_all.
    528
    import sort_NAME_TAB to %_TAB2_sort
    529
    field_name_tab to %_TAB2_field
    530
    from database dbdata(DB) id g_dbdatakey.
    531
    if sy-subrc = 0.
    532
    delete from dbdata
    533
    where relid    = 'DB' and
    534
    eu_name  = g_dbdatakey-eu_name and
    535
    username = c_all.
    536
    describe table %_tab2_field lines %_l_lines.
    537
    if not %_l_lines is initial.
    538
    %_TAB2[] = %_tab2_field[].
    539
    endif.
    540
    endif.
    541
    ENDIF.
    542
    CASE ACTION.
    543
    WHEN 'ANZE'.
    544
    try.
    545
    SELECT * FROM /CVS/TA_GTHDR                     "client specified
    546
    APPENDING TABLE I/CVS/TA_GTHDR
    >>>>>
    UP TO RSEUMOD-TBMAXSEL ROWS BYPASSING BUFFER
    548
    WHERE GTNUM IN I1
    549
    AND   MJAHR IN I2.
    550
    551
    CATCH CX_SY_DYNAMIC_OSQL_SEMANTICS INTO xref.
    552
    IF xref->kernel_errid = 'SAPSQL_ESCAPE_WITH_POOLTABLE'.
    553
    message i412(mo).
    554
    exit.
    555
    ELSE.
    556
    RAISE EXCEPTION xref.
    557
    ENDif.
    558
    ENDTRY.
    559
    IF NOT G_DATA_EXIT IS INITIAL.
    560
      DATEN NICHT ANZEIGEN, SONDERN NACH AUßEN GEBEN
    561
    CALL FUNCTION G_DATA_EXIT
    562
    EXPORTING
    563
    TABNAME = /CVS/TA_GTHDR
    564
    TABLES
    565
    DATA    = I/CVS/TA_GTHDR.
    566
    LEAVE.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    SY-MSGTY
    I
    SY-MSGID
    SF
    SY-MSGNO
    616
    SY-MSGV1
    /1BCDWB/DB/CVS/TA_GTHDR
    SY-MSGV2
    RE
    SY-MSGV3
    EN
    SY-MSGV4
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    1 EVENT        /1BCDWB/DB/CVS/TA_GTHDR             /1BCDWB/DB/CVS/TA_GTHDR               547
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.       1 Ty.          EVENT
    Name  START-OF-SELECTION
    %_SPACE
    2
    0
    SY-REPID
    /1BCDWB/DB/CVS/TA_GTHDR
    2344454244245525454544522222222222222222
    F123472F42F363F41F7484200000000000000000
    RSEUMOD-TBMAXSEL
    200
    000C
    0008
    /CVS/TA_GTHDR
    0000                       000000000000000000000000000000000000
    2222222222222333322222222222222222222222333333333333333333333333333333333333222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    <%_TABLE_/CVS/TA_GTHDR>
    ENTRIES
    0
    0000
    0000
    SYST-REPID
    /1BCDWB/DB/CVS/TA_GTHDR
    2344454244245525454544522222222222222222
    F123472F42F363F41F7484200000000000000000
    %_DUMMY$$
    2222
    0000
    INPUT_ENTRY
    2
    0
    I1[]
    Table IT_105[0x23]
    PROGRAM=/1BCDWB/DB/CVS/TA_GTHDRDATA=I1[]
    Table reference: 22
    TABH+  0(20) = 0000000000000000000000000000000000000000
    TABH+ 20(20) = 00000016000000690000000000000017FFFFFFFF
    TABH+ 40(16) = 0400000000002830000A249001000000
    store        = 0x0000000000000000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 22    (0x00000016)
    label        = 105   (0x00000069)
    fill         = 0     (0x00000000)
    leng         = 23    (0x00000017)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000174
    occu         = 10    (0x0000000A)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 0
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    store_id     = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    SUBRC
    0
    0000
    0000
    I2[]
    Table IT_107[0x11]
    PROGRAM=/1BCDWB/DB/CVS/TA_GTHDRDATA=I2[]
    Table reference: 24
    TABH+  0(20) = 0000000000000000000000000000000000000000
    TABH+ 20(20) = 000000180000006B000000000000000BFFFFFFFF
    TABH+ 40(16) = 04000000000028D8000A249001000000
    store        = 0x0000000000000000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 24    (0x00000018)
    label        = 107   (0x0000006B)
    fill         = 0     (0x00000000)
    leng         = 11    (0x0000000B)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000177
    occu         = 10    (0x0000000A)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 0
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    store_id     = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    C_ALL
    %_ALL
    254442222222
    5F1CC0000000
    ULINE_LENGTH
    0
    0000
    0000
    I3[]
    Table IT_108[0x23]
    PROGRAM=/1BCDWB/DB/CVS/TA_GTHDRDATA=I3[]
    Table reference: 25
    TABH+  0(20) = 0000000000000000000000000000000000000000
    TABH+ 20(20) = 000000190000006C0000000000000017FFFFFFFF
    TABH+ 40(16) = 0400000000002948000A249001000000
    store        = 0x0000000000000000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 25    (0x00000019)
    label        = 108   (0x0000006C)
    fill         = 0     (0x00000000)
    leng         = 23    (0x00000017)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000179
    occu         = 10    (0x0000000A)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 0
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    store_id     = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    I/CVS/TA_GTHDR[]
    Table IT_124[0x834]
    PROGRAM=/1BCDWB/DB/CVS/TA_GTHDRDATA=I/CVS/TA_GTHDR[]
    Table reference: 44
    TABH+  0(20) = 0000000000000000000000000000000000000000
    TABH+ 20(20) = 0000002C0000007C0000000000000342FFFFFFFF
    TABH+ 40(16) = 04000000000017C8001024C401000000
    store        = 0x0000000000000000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 44    (0x0000002C)
    label        = 124   (0x0000007C)
    fill         = 0     (0x00000000)
    leng         = 834   (0x00000342)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000099
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    store_id     = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    XREF
    F0000000
    F0000000
    XREF->KERNEL_ERRID
    SY-XPROG
    SAPCNVE
    5454454222222222222222222222222222222222
    3103E65000000000000000000000000000000000
    SY-MSGID
    SF
    54222222222222222222
    36000000000000000000
    PAGNO
    0
    0000
    0000
    Internal notes
    The termination occurred in the function "HandleRsqlErrors" of the SAP
    Basis System, specifically in line 759 of the module
    "//bas/640_REL/src/krn/runt/absapsql.c#16".
    The internal operation just processed is "SQLS".
    The internal session was started at 20080428110327.
    Internal call code.........: "[RSQL/OPEN//CVS/TA_GTHDR ]"
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    => 64 bit R/3 Kernel
    => 64 bit OS400 Kernel
    => Heap limit      = unlimited
    => Stack limit     = unlimited
    => Core limit      = unlimited
    => File size limit = unlimited
    => Heap address  = 0x40000000000000009DF46B87C8DACBA0
    => Stack address = 0xfffffffffffb4a0
    => Stack low     =  0xfffffffffffb4a0
    => Stack high    =  0xffffffffffffa10
    => Stack Trace:
         AixStack() at 0x10008ca60
         CTrcStack2() at 0x10008cb58
         rabax_CStackSave__Fv() at 0x100071c74
         ab_rabax() at 0x10006eaa4
         ab_rsqlerr__FPCciT1P11RS_HEADER94T1Pv() at 0x10086d218
         HandleRsqlErrors__F9RsqlError9CloseMode() at 0x100ff8810
         SqlsExecuteCall__FUcP11DynCallInfo() at 0x100ff6fac
         ab_jsqls__Fv() at 0x100ff17dc
         ab_extri__Fv() at 0x10090bb68
         ab_xevent__FPCc() at 0x100928be4
         ab_trigg__Fv() at 0x10092872c
         ab_run() at 0x10108211c
         N_ab_run() at 0x10107539c
         dynpmcal() at 0x1010740e4
         dynppai0() at 0x1010719e4
         dynprctl() at 0x10107b590
         dynpen00() at 0x10022b2c4
         Thdynpen00() at 0x1000a71d0
         TskhLoop() at 0x1000aba14
         tskhstart() at 0x1000c046c
         DpMain() at 0x10174f654
         nlsui_main() at 0x101722dc8
         __start() at 0x100000344
    !!! Invalid stack address encountered: 0x0
    !!! Stack corrupted.
    Mon Apr 28 11:03:32 2008
    Library
    (SRV)PGM
    Module
    Function/Statement No.
    QSYS
    QP2USER
    QP2API
    __Qp2Fork  13
    QSYS
    QP2USER
    QP2API
    runpase_common__FiPvT2  5
    R3640AOPT
    O4PRTLIBC
    AS4STACK
    As4Stack_From_PASE  3
    R3640AOPT
    O4PRTLIBC
    AS4STACK
    As4StackOut  10
    R3640AOPT
    O4PRTLIBC
    AS4STACK
    MATINVS2_8O4_StackFv  8
    List of ABAP programs affected
    Index
    Ty.
    Program
    Group
    Date
    Time
    Size
    Lang.
    0
    Prg
    /1BCDWB/DB/CVS/TA_GTHDR
    0
    25.04.2008
    17:54:15
    114688
    E
    1
    Prg
    SAPMSSY0
    1
    24.01.2007
    03:59:44
    68608
    E
    2
    Prg
    SAPMSSYD
    1
    24.01.2007
    03:59:44
    17408
    E
    3
    Prg
    SAPFSYSCALLS
    1
    06.11.2003
    20:52:59
    6144
    E
    4
    Prg
    RSDBRUNT
    0
    24.01.2007
    03:59:32
    227328
    E
    5
    Typ
    RSSCR
    0
    : m:15
    5120
    6
    Prg
    RSDBSPBL
    0
    06.11.2003
    20:56:48
    59392
    E
    7
    Prg
    SAPDBD$S
    0
    06.11.2003
    20:52:58
    16384
    E
    8
    Typ
    VARID
    0
    12.05.1997
    16:51:30
    4096
    9
    Prg
    %_CSYDB0
    0
    06.11.2003
    20:52:42
    28672
    E
    10
    Prg
    RSDBSPVA
    0
    24.01.2007
    03:38:36
    112640
    E
    11
    Typ
    RSVAMEMKEY
    0
    07.05.1997
    13:07:49
    2048
    12
    Prg
    RSDBSPMC
    0
    24.01.2007
    03:38:36
    66560
    E
    13
    Typ
    DDSHDESCR
    0
    03.09.1997
    03:05:16
    3072
    14
    Typ
    SPPARAMS
    0
    07.05.1997
    13:10:38
    2048
    15
    Typ
    SPPARAMS
    0
    07.05.1997
    13:10:38
    2048
    16
    Prg
    SAPLICON
    16
    12.11.2004
    13:50:21
    23552
    E
    17
    Prg
    %_CICON
    16
    16.03.2004
    20:13:52
    73728
    E
    18
    Prg
    SAPLSABE
    18
    06.11.2003
    20:53:04
    11264
    E
    19
    Prg
    SAPLSECU
    19
    24.01.2007
    03:30:48
    66560
    E
    20
    Typ
    RSSUBINFO
    0
    14.10.1999
    22:01:03
    3072
    21
    Prg
    SAPLSETB
    21
    24.01.2007
    03:51:50
    259072
    E
    22
    Prg
    SAPLSLDB
    22
    31.08.2006
    16:14:51
    70656
    E
    23
    Prg
    SAPLSDIFRUNTIME
    23
    12.11.2004
    13:45:30
    82944
    E
    24
    Typ
    DDFIXVALUE
    0
    27.08.1999
    18:04:56
    2048
    25
    Typ
    X031L
    0
    15.11.2000
    18:03:28
    5120
    26
    Typ
    DFIES
    0
    09.11.2000
    14:07:05
    8192
    27
    Prg
    SAPLSDNT
    27
    31.08.2006
    14:37:01
    201728
    E
    28
    Prg
    SAPLSUGS
    28
    30.08.2006
    19:31:11
    29696
    E
    29
    Typ
    DDFTX
    0
    05.11.1997
    02:52:59
    4096
    30
    Typ
    X031L
    0
    15.11.2000
    18:03:28
    5120
    31
    Typ
    DD03L
    0
    19.11.2001
    15:49:29
    5120
    32
    Prg
    SAPLSDIF
    32
    12.11.2004
    13:45:30
    180224
    E
    33
    Typ
    DD03P
    0
    19.11.2001
    15:46:27
    11264
    34
    Typ
    DD08V
    0
    20.08.1998
    11:35:49
    3072
    35
    Typ
    DD12V
    0
    20.08.1998
    11:35:57
    4096
    36
    Typ
    DD17V
    0
    20.08.1998
    10:50:57
    2048
    37
    Typ
    DD35V
    0
    01.03.2001
    12:21:53
    2048
    38
    Typ
    DD36M
    0
    01.03.2001
    12:38:06
    4096
    39
    Typ
    DD02V
    0
    19.11.2001
    15:50:56
    6144
    40
    Typ
    DD09V
    0
    27.08.1999
    18:04:52
    4096
    41
    Prg
    SAPLSDTB
    41
    31.08.2006
    14:13:30
    386048
    E
    42
    Typ
    DDCACHE
    0
    30.03.1995
    13:12:06
    2048
    43
    Typ
    DCTABDGET
    0
    13.05.1997
    12:49:28
    2048
    44
    Prg
    SAPLSDSG
    44
    12.11.2004
    13:45:30
    112640
    E
    45
    Prg
    RADBTDDO
    44
    12.11.2004
    13:45:30
    34816
    E
    46
    Prg
    RADBTDDF
    44
    12.11.2004
    13:45:30
    237568
    E
    47
    Typ
    DD02L
    0
    19.11.2001
    15:49:25
    6144
    48
    Typ
    DD02T
    0
    05.11.1997
    02:52:47
    2048
    49
    Typ
    DDSTATE
    0
    07.05.1997
    12:49:07
    2048
    50
    Typ
    DD05M
    0
    09.11.2000
    14:06:49
    3072
    51
    Typ
    DD08L
    0
    05.11.1997
    02:52:51
    3072
    52
    Typ
    DD08T
    0
    05.11.1997
    02:52:51
    2048
    53
    Prg
    SAPLSDFK
    53
    06.11.2003
    20:53:04
    23552
    E
    54
    Typ
    DD05S
    0
    05.11.1997
    02:52:51
    3072
    55
    Typ
    DD05V
    0
    05.11.1997
    02:52:51
    2048
    56
    Typ
    DD03K
    0
    09.11.2000
    14:25:24
    2048
    57
    Typ
    DCTABLGET
    0
    04.06.1997
    19:16:24
    2048
    58
    Typ
    DD05Q
    0
    20.08.1998
    11:35:44
    2048
    59
    Typ
    DD05Q
    0
    20.08.1998
    11:35:44
    2048
    60
    Typ
    DD02V
    0
    19.11.2001
    15:50:56
    6144
    61
    Typ
    DD02V
    0
    19.11.2001
    15:50:56
    6144
    62
    Typ
    RSEUMOD
    0
    06.11.2003
    20:36:53
    36864
    63
    Prg
    SAPLALDB
    63
    31.08.2006
    16:20:50
    264192
    E
    64
    Typ
    NODE_STRUC
    0
    10.11.1999
    17:41:51
    2048
    65
    Typ
    TRDIR
    0
    02.11.1998
    09:59:17
    5120
    66
    Typ
    RSEL_PARAS
    0
    05.09.1997
    16:13:02
    2048
    67
    Prg
    SAPLDSYA
    67
    06.11.2003
    20:53:01
    39936
    E
    68
    Prg
    SAPFSDS1
    67
    06.11.2003
    20:53:24
    47104
    E
    69
    Typ
    TDCLD
    0
    02.11.1998
    09:51:35
    5120
    70
    Prg
    SAPLSDOD
    70
    31.08.2006
    16:19:53
    39936
    E
    71
    Typ
    DOKIL
    0
    12.05.1997
    16:46:17
    3072
    72
    Prg
    SAPCNVE
    72
    06.11.2003
    20:52:58
    6144
    E
    73
    Prg
    SAPLLANG
    73
    06.11.2003
    20:53:03
    8192
    E
    74
    Typ
    T002
    0
    14.02.1998
    10:24:58
    2048
    75
    Typ
    RSEXFCODE
    0
    13.08.1997
    12:52:57
    1024
    76
    Prg
    SAPFSPOR
    0
    31.08.2006
    19:27:43
    12288
    E
    77
    Typ
    RSSELINT
    0
    04.04.1995
    16:12:37
    2048
    78
    Prg
    SAPLKGJH
    78
    06.11.2003
    20:53:03
    8192
    E
    79
    Typ
    RSPARINT
    0
    10.04.1995
    09:58:38
    1024
    80
    Prg
    SAPLSCNT
    80
    06.11.2003
    20:53:04
    24576
    E
    81
    Typ
    DYCBOX
    0
    20.08.1998
    11:16:53
    2048
    82
    Prg
    SAPLSVSM
    82
    31.08.2006
    16:12:13
    24576
    E
    83
    Prg
    SAPLSGUI
    83
    12.11.2004
    13:59:56
    61440
    E
    84
    Prg
    SAPLSTTM
    84
    31.08.2006
    14:23:56
    75776
    E
    85
    Prg
    SAPLSBDC
    85
    31.08.2006

    Hi,
    as described in the error message:
    The column COMINV is missing in table /CVS/TA_GTHDR !
    You should check this table in SE11 for consistency of the DB object and the nametab - one of them will be wrong ...
    Regards
    Volker Gueldenpfennig, consolut international ag
    http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

  • *Unable to create Service Entry Sheet.*

    Hi,
    Iu2019m trying to create service entry sheet for a service PO but all the item level fields in ML81N screen are appearing in display mode (non-editable) also I cannot see the u201CService Selectionu201D button. So Iu2019m unable to insert/select the service detail and cannot create the entry sheet. If I use the menu path Edit->Service Selection, still cannot adopt services and system gets busy for a substantial period and eventually timed out.
    Please helpu2026
    Iu2019m using ECC 6.0
    Thanks, Pratap

    Service PO: Intangible good that is the subject of business activity and that can be performed internally or procured externally (outsourced).
    -     Services are regarded as being consumed at the time of their performance. They cannot be stored or transported.
    -     Examples of services include construction work, janitorial/cleaning services, and legal services.
    Steps involved in Service PO:
    1.     Define Organizational Status for Service Categories, in IMG - MM - External Services Management.
    2.     Define Service Category, Enter Service Category, Org. Service Category, External Number Assignment
    Without Validation, Acct. Category Reference & Service Category Description.
    3.     Define Number Ranges for Service Category.
    4.   Create Service Master Record (AC03), SAP Menu u2013 Logistics u2013 MM u2013 Service Master, Enter Service Category,
          Base unit of measure, Mat/srv.grp (007 u2013 Service), Division, Valuation class u2013 3200 & Service type.  
    5.     Create Service PO with Acct. Assignment u2013 Cost Center (K), Item Category u2013 D, Material Short Text, Mat. Group, Plant, Entry for Services in Item Level i.e. Service No., Quantity & Gross Price u2013 Save.
    6.     Maintain Service Entry Sheet u2013 ML81N in SAP Menu u2013 Logistics u2013 MM choose PO in ML81N edit and save.
    7.     Then do MIRO from PO reference u2013 Service Entry sheet.
    8.     Collective Release of Service Entry Sheet u2013 ML85
    Organizational Status for Service Category: The organization status indicates the areas in which service master records are used.
    Service Category: The service category is the most important criterion for structuring service master records. It provides a default value for the valuation classes. Service master records can be assigned to number ranges on the basis of the service category.

  • GRN display through single gate entry number

    Dear Sir,
    I want to develop t-code through which GRN can be displayed against single Gate entry No.

    Hi,
    Where in SAP you are creating the Gate entry no. or is it coming from another system through interface.
    While doing GRn are you refering to such Gate entry number in any field..pls provide the details.
    There are no such SAP standard transaction for gate entry..if its an custom devloped one..kindly provide us the details.
    Thanks
    BR

  • GATE ENTRY PROCEDURE

    I have to set the Gate Entry Procedure for the incoming material.  how do i customize the same and what are the t.codes.
    is Inbound Delivery can be used for Vendor Gate entry.
    regards
    KIM.

    Hi,
    If I understood your question correctly, gate entry is not there in standard SAP.
    You will have to create Z Programme.
    Reagards
    Kedar

  • Gate entry pass

    dear sap guru,
    Service purchase requistion text filed is not coming to related with that gate entry pass. For Example, in PR, we are putting in Header coloumn, about material details, quantity. It is not coming to Gate entry pass.
    How we can get this information in gate entry pass.
    regards,
    babu

    baburaj wrote:
    dear sap guru,
    >
    > Service purchase requistion text filed is not coming to related with that gate entry pass. For Example, in PR, we are putting in Header coloumn, about material details, quantity. It is not coming to Gate entry pass.
    >
    > How we can get this information in gate entry pass.
    >
    > regards,
    > babu
    Which trxn you are creating gate pass?

  • Error when creating files for transport request SAPK-700BGINPLMWUI

    Hello experts,
    We're upgrading our 46c System to ERP 6.0 EHP4.
    In Phase  EHP_INCLUSION we get the following error Message: Disassembling package queue failed, rc = "2", reason = "Error when creating files for transport request SAPK-700BGINPLMWUI"
    We've already checked the SAINT version; Upgrade Fix, SAPCAR version. We've checked our TMS as well and everything seems  O.K.
    Any help would be really appreciated!!!
    Complete Error message:
    EhP component PLMWUI, 700                                                                               
    Looking for SAINT package for 'PLMWUI' ...                                                                               
    R3upReadNewPackages:                                                                               
    patchType='U', langVect='DEC'                                                                               
    RFC Login to: System="X05", Nr="00", GwHost="sxt ", GwService="sapgw00"                                                 
    RFC Login succeeded                                                                               
    Calling function module "spda_read_new_packages" by RFC                                                                     
      ismovesVersion='0'                                                                               
    R3upReadNewPackages: exit: rc=0                                                                               
    ... No matching package found.                                                                               
    R3upReadNewPackages:                                                                               
    patchType='I', langVect='DEC'                                                                               
    RFC Login to: System="X05", Nr="00", GwHost="sxt ", GwService="sapgw00"                                                 
    RFC Login succeeded                                                                               
    Calling function module "spda_read_new_packages" by RFC                                                                     
      ismovesVersion='0'                                                                               
    R3upReadNewPackages: exit: rc=0                                                                               
    Found: name = 'PLMWUI', release = '700', package = 'SAPK-700BGINPLMWUI', type = 'AOI'                                  
    ... Matching package found: 'PLMWUI','700','SAPK-700BGINPLMWUI'                                                             
    (trc) R3upPatchDisassembleQueue: 1 package queue entries                                                                    
    (trc) R3upPatchDisassembleQueue: force=YES                                                                               
    (trc) R3upPatchDisassembleQueue: 1 packages will be disassembled                                                            
    Starting disassembling package queue                                                                               
    Date & Time: 20100319133139                                                                               
    Starting RFC Login to: System = "X05", GwHost = "sxt ", GwService = "sapgw00"                                           
    RFC Login to: System="X05", Nr="00", GwHost="sxt ", GwService="sapgw00"                                                 
    RFC Login succeeded                                                                               
    Calling function module "SPDA_DISASSEMBLE_QUEUE" by RFC                                                                     
    Input table IT_PATQ:                                                                               
    "SAPK-700BGINPLMWUI","000","AOI","PLMWUI","700","SAP PLM Web UI","00"                                                       
    Call of function module "SPDA_DISASSEMBLE_QUEUE" by RFC succeeded                                                           
    Logging off from SAP system                                                                               
    Date & Time: 20100319133139                                                                               
    Disassembling package queue failed, rc = "2", reason = "Error when creating files for transport request SAPK-700BGINPLMWUI"

    Hello Anthes,
    Please Check the things in following sequence :
    1.Use latest SAPehpi, R3trans and tp versions.
    2. users/group authorization issue and/or ownersip limitations (set 777) .Reboot the server to make sure, that the authorisations are updated and there is no lock on a file in the EHPI dir.Repeat the phase.
    Folders where permissions should be 777 are Upgrade directory, Data Directory, Cofile directory and .../EPS/in.
    3. Source file corruption can be ruled out by execution
    R3trans -l /usr/sap/<SID>/..../abap/data/R-700BGINPLMWUI.SAP (The data file corresponding to the Package which is giving error). Check if this ends fine.
    Note 2050
    4. Confirm that your transport tool is 'healthy' by testing it in STMS. In SPAM in client 000 use the function Disassemble package and enter the package <Package name>.
    5. Try to update the kernel if it not helps.
    Best Regards
    Niraj

  • Bex transport  in SAP BW 3.1

    Hello everybody,
    how do you organize Bex transport in SAP BW?
    In our installation, we find it necessary that some queries need to be designed in development system and tested before transport in production. We would like the person who's creating these queries to be able to create and release the transport for his query himself. With just one standard Bex transport this seems difficult to implement:  In our constellation, the standard Bex transport can not be transported to production system, because it may contain test queries, which are not wanted in productive system at all and collects changes of different projects and persons, so it may contain objects that are still in test status, while others need to be transported to production system. Collecting into different requests is only possible if the concerned objects belong to different packages?
    Collecting the needed objects in a transport request manually can't be done without releasing the Bex transport first because otherwise the objects are locked.
    How do you organize Bex transports in your system landscape?
    Thanks for any suggestions, Kathrin!

    Hi Kathrin,
    if you create a query in the development-system, the query will go to the Package $TMP, so no Transport is necessary. If you have a naming-convention, like <InfoProvder>_QU_nnnn or someting else for non-test Queries, it is easy to fetch them in the Transport Connection (Admin Workbench) and transport them in the production-system.
    Hope this helps,
    Regards
    Frank

  • How can i create a new transport request?

    Dear Experts,
    Some colleagues have to modify a master record, but save time, failing to produce a request no., then, how can i create a new transport request?
    Wilson

    Hi,
    Please let us know about the issue when you create the new Transport request .
    In which system you are creating the request . Hope its in Development  .
    If so , check the entries are enabled in SCC4 > Changes without automatic recording
    Changes to repository objects and cross client customizing allowed .
    Protection level 0
    If these entries are enabled, you must be able to create Transport requests.
    Please check and update .
    Regards,
    Nibu

  • Validity period error while creating Service Entry Sheet.

    Hi SAP experts,
    Users are facing below two error messages while creating serivce entry sheet with respect to Standard PO (NB).The PO has RFQ refrence where Validity start and end date is blank. Also PO has Item category 'D' (Services)
    1) "Runtime of entry must fall within Run time of the PO (05.12.2008-05.01.2009)
    2) Entry must be wihin validity period of purchase order (05.12.2008-05.01.2009)
    In the EKKO table system is showing validity start and end date for PO but it is not present in the PO (NB) by ME 22 / 23N.
    Basically standard PO (NB) should not have validity start date and end date but still it is showing in the table EKKO. 
    Kindly provide me related resolution ASAP.
    Thanks
    BR,
    Rahul

    Hi Alex,
    Thanks for the quick reply.
    There is no Validity period maintained in the PO header under "Additional data".
    but still I am getting Validity data in the table EKKO for standard PO (NB).
    BR,
    Rahul

  • Goods receip based on Gate entry.

    Hello experts,
    As per our existing procedure gate entry is done in regiser upon receipt of material from vendor.Then material is moved to store.Based on this gate entry only goods receipt is expected to be done in SAP.How this can be captured in SAP.
    Thanks & Regards
    Atharva G.

    Dear Atharva,
    Please I suggest you to stick with the standard process, as by doing 103 for Gate entry, and 105 to release form GR blocked stock to Unrestricted Stock. Most the time clients want separate entry for Gate Pass to separate it form Quality Inspection stock which normally consultant do by making customize Movt type. i think you want this but i suggest you to go for 103 and 105. if your users keep insisting than just add signing authority to Gate entry output of concern authority.
    Best Regards
    Mohsin Abbasi

  • Creating Service Entry Sheet without using Service Master/Service lines

    We are invoking the BAPI_EntrySheet_Create to create the service entry sheet. We are currently facing this issue...
    1) For assigned PO's, we are getting the PO item and Account assignment information from BAPI_PO_GetDetail. We are using these values to populate the parameters/tables to invoke BAPI_EntrySheet_Create. For population the Entrysheetservices table, we are not using information from Service Master/Service lines but use the information we get from an external system to populate the Service lines(ESLL). We do not provide a Package No/Service information when invoking the BAPI but populate the service lines with short text, quantity, Gross price etc without service information like package no, outline indicator etc. The BAPI creates a service enty sheet successfully(this is without the SES Acceptance indicator not being set) but when we lookup the SES# from ML81n transaction the ESLL details lines are not displayed.
    When displaying the SES using transaction ML81N, the header information is displayed correctly but the lines are not displayed. The Header information is correctly populated in ESSR table and detail is also populated in ESLL table. I think the cross reference information is correctly set in ESLH table to pull up the detail when ML81N as it is missing the package/sub pack information.
    Your expert advise in resolving this issue is very much appreciate. Please advise.

    Hi,
    Creating Service entry sheet using bapi  BAPI_ENTRYSHEET_CREATE
    For creating service entry sheet follow below link and it helps to you.
    http://wiki.sdn.sap.com/wiki/display/ABAP/CreatingServiceEntrySheetusing+BAPI
    Regards,
    Sekhar

Maybe you are looking for