Good issue -error

error
G/L account 400000 does not exist in company code KTV
step by step
help me
ali'

Hi
Go to T.code FS00
Enter the GL account number and company code and then on the menu bar click GL ACCOUNT > go to Create with reference, enter the GL Number and standard company code 1000, check the data in all the tabs and then save.
your required GL will be created
Cheers
Chris
Edited by: CHRIS MM on Dec 28, 2010 4:58 PM

Similar Messages

  • Goods Issue error - batches not defined for delivery item

    Hi,
    We are getting a Goods Issue error  u201CThe batches are not defined for delivery item 000010u201D.   We are only getting this error for a material that is being shipped against a particular third party sales scheduling agreement.  We went live in 2007 and we had no issues, but when we had to create a new Sched Agreement this year, for third party sales, we started to get this error.  However, if we re-activate the old scheduling agreement we do not get the error.  We have a batch job that executes the following steps:
    1.     VL06IG (collective goods receipt)
    2.     VL10 (collective delivery)
    3.     VL06O (collective GI)
    We have compared the 2 scheduling agreements and see no difference.  We are assuming it has something to do with how the scheduling agreement was setup, but are not sure.  Any suggestions on how to correct this problem would be much appreciated.
    Thanks in advance,
    Helen

    Dear Murali,
    The material has not changed at all.  I'm not sure what you mean by maintaining batches while receipt of the material.
    If I re-open the old scheduling agreement, we do not get the error message.  However, as soon as we use the new SD scheduling agreement, we get the error.  We are using the same material master on both scheduling agreements.
    Thanks,
    Helen

  • Post Good Issue Error

    When I Press the Post Goods Issue Button for a delivery in SD the error dump appears.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          10/15/2008 06:38:52
    Short dump has not been completely stored (too big)
    Short text
    The current application triggered a termination with a short dump.
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    Short text of error message:
    No RFC destination is defined for SAP Global Trade Services
    Long text of error message:
    Technical information about the message:
    Message class....... "/SAPSLL/PLUGINR3"
    Number.............. 002
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "MESSAGE_TYPE_X" " "
    "SAPLMBWL" or "LMBWLU21"
    "MB_POST_GOODS_MOVEMENT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    System environment
    SAP-Release 700
    Application server... "biw7sap"
    Network address...... "68.88.249.38"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x Intel 801586"
    Character length.... 16 Bits
    Pointer length....... 32 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "BIW7SAP"
    Database type..... "ORACLE"
    Database name..... "ECS"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Mar 20 2007 00:45:21"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "OCI_10201_SHARE (10.2.0.1.0) "
    Patch level. 102
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    Memory consumption
    Roll.... 8176
    EM...... 26130600
    Heap.... 0
    Page.... 57344
    MM Used. 19070624
    MM Free. 785208
    User and Transaction
    Client.............. 800
    User................ "CUSER14"
    Language key........ "E"
    Transaction......... "VL02N "
    Program............. "SAPLMBWL"
    Screen.............. "SAPMV50A 1000"
    Screen line......... 39
    Information on where terminated
    Termination occurred in the ABAP program "SAPLMBWL" - in
    "MB_POST_GOODS_MOVEMENT".
    The main program was "SAPMV50A ".
    In the source code you have the termination point in line 59
    of the (Include) program "LMBWLU21".
    Source Code Extract
    Line
    SourceCde
    29
       when a goods movement for an inbound or outbound delivery is posted
    30
       directly from VL31N/ VL01N, XBLNR is not yet known when we call
    31
       CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
    32
       BKPF as well. There is no other way to forward XBLNR to FI as not
    33
       every document is posted by MB_CREATE -> a new function module in
    34
       MBWL for transferring the information, called by FI, meant to load
    35
       the complete function group for all MBxx postings when this isn't
    36
       required (Performance). Would be the better way to transport the
    37
       information after switching off MBxx in later release.
    38
       corresponding IMPORT ... FROM MEMORY ... can be found in
    39
       AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
    40
    l_mem_id = 'MKPF-XBLNR'.                                   " 641365
    41
    EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id.             " 641365
    42
    ENDIF.
    43
    IF xmkpf-xabln IS INITIAL.                               "note 434093
    44
    CALL FUNCTION 'MB_XAB_NUMBER_GET'.                   "note 434093
    45
    ENDIF.                                                   "note 434093
    46
    47
    ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
    48
    49
    ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
    50
    CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
    51
    EXCEPTIONS
    52
    error_message = 4.
    53
    As soon as we have started to put things into UPDATE TASK, we must
    54
    ensure that errors definitely terminate the transaction.
    55
    MESSAGE A is not sufficient because it can be catched from
    56
    external callers which COMMIT WORK afterwards, resulting in
    57
    incomplete updates. Read note 385830 for the full story.
    58
    IF NOT sy-subrc IS INITIAL.
    >>>>>
    MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
    60
    sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    61
        MESSAGE A263.
    62
    ENDIF.
    63
    Optische Archivierung
    64
    Spaete Erfassung mit Barcode
    65
    Redesign of barcode handling -> note 780365
    66
    PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
    67
    xmkpf-mjahr
    68
    barcode.
    69
    70
    MOVE-CORRESPONDING xmkpf TO emkpf.
    71
    CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
    72
    EXCEPTIONS
    73
    error_message = 4.
    74
    MOVE-CORRESPONDING xmkpf TO emkpf.
    75
    CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
    76
    EXCEPTIONS
    77
    error_message = 4.
    78
    IF NOT sy-subrc IS INITIAL.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    4
    SY-INDEX
    0
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    6
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    W0
    SY-UCOMM
    WABU_T
    SY-TITLE
    Delivery 80015203 Change: Overview
    SY-MSGTY
    X
    SY-MSGID
    /SAPSLL/PLUGINR3
    SY-MSGNO
    002
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20081015
    SY-UZEIT
    063852
    SY-XPROG
    SAPLBPFC
    SY-XFORM
    CONVERSION_EXIT
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    10 FUNCTION     SAPLMBWL                            LMBWLU21                               59
    MB_POST_GOODS_MOVEMENT
    9 FORM         SAPMV50A                            FV50XF0B_BELEG_SICHERN                769
    BELEG_SICHERN_POST
    8 FORM         SAPMV50A                            FV50XF0B_BELEG_SICHERN                 86
    BELEG_SICHERN_01
    7 FORM         SAPMV50A                            FV50XF0B_BELEG_SICHERN                 16
    BELEG_SICHERN
    6 FORM         SAPMV50A                            MV50AF0F_FCODE_SICH_OHNE_CHECK         10
    FCODE_SICH_OHNE_CHECK
    5 FORM         SAPMV50A                            MV50AF0F_FCODE_WABU                    11
    FCODE_WABU
    4 FORM         SAPLV00F                            LV00FF0F                               92
    FCODE_BEARBEITEN
    3 FUNCTION     SAPLV00F                            LV00FU02                               44
    SCREEN_SEQUENCE_CONTROL
    2 FORM         SAPMV50A                            MV50AF0F_FCODE_BEARBEITEN              62
    FCODE_BEARBEITEN
    1 MODULE (PAI) SAPMV50A                            MV50AI0F                               52
    FCODE_BEARBEITEN
    Chosen variables
    Name
    Val.
    No.      10 Ty.          FUNCTION
    Name  MB_POST_GOODS_MOVEMENT
    XBLNR_SD
    0080015203
    3333333333
    0080015203
    0000000000
    0000000000
    EMKPF
    000000000000000000          ##
    2222222222333333333333333333222222222200222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    XMSSA[]
    Table IT_589[0x196]
    FUNCTION-POOL=MBWLDATA=XMSSA[]
    Table reference: 307
    TABH+  0(20) = 00000000200D869300000000330100004D020000
    TABH+ 20(20) = 00000000C4000000FFFFFFFF04090300E01B0000
    TABH+ 40( 8) = 08000000C1108001
    store        = 0x00000000
    ext1         = 0x200D8693
    shmId        = 0     (0x00000000)
    id           = 307   (0x33010000)
    label        = 589   (0x4D020000)
    fill         = 0     (0x00000000)
    leng         = 196   (0xC4000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000134
    occu         = 8     (0x08000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    collHook     = 0x00000000
    ext2         = 0xD80C8693
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x980C8693
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    RRESWK
    22222222222
    00000000000
    00000000000
    00000000000
    %_SPACE
    2
    0
    0
    0
    L_MEM_ID
    MKPF-XBLNR
    4454254445
    DB06D82CE2
    0000000000
    0000000000
    RSJOBINFO
    00000000000000                                  ##
    2222222222222222222222222222222233333333333333222222222222222222222222222222222200
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    RNAME
    R
    52222
    20000
    00000
    00000
    SCREEN
    BT_UALL
    4555444222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    24F51CC000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    IT_RSTRUCT
    Table[initial]
    XMKPF-XABLN
    2222222222
    0000000000
    0000000000
    0000000000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    SYST-REPID
    SAPLMBWL
    5454445422222222222222222222222222222222
    310CD27C00000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    ODM07M[]
    Table[initial]
    GT_GOCOMP
    000000000000                                             ####              00000000000000
    3333333333332222222222222222222222222222222222222222222220000222222222222223333333333333322222
    000000000000000000000000000000000000000000000000000000000000C000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SY-SUBRC
    4
    0000
    4000
    L_ATPCB
    22222
    00000
    00000
    00000
    XMKPF-MBLNR
    4900035075
    3333333333
    4900035075
    0000000000
    0000000000
    XMKPF-MJAHR
    2008
    3333
    2008
    0000
    0000
    BARCODE
    2222222222222222222222222222222222222222
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    T003
    800WL49AMS                          XX  XXXXXH
    3335433445222222222222222222222222225522555554222222
    8007C491D3000000000000000000000000008800888888000000
    0000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000
    KNVV
    00000000                     000
    2222222222222222222222222222222223333333322222222222222222222233322222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    T064B
    2222222222222222222222
    0000000000000000000000
    0000000000000000000000
    0000000000000000000000
    VGMSEG[]
    Table[initial]
    No.       9 Ty.          FORM
    Name  BELEG_SICHERN_POST
    MAT_AUF_HINWEIS_COPY
    2
    0
    0
    0
    XLIKP[]
    Table IT_392[1x2360]
    PROGRAM=SAPMV50ADATA=XLIKP[]
    Table reference: 197
    TABH+  0(20) = 082D1E94E0C8119300000000C500000088010000
    TABH+ 20(20) = 01000000380900003000000004FC0100D0070000
    TABH+ 40( 8) = 04000000C1108001
    store        = 0x082D1E94
    ext1         = 0xE0C81193
    shmId        = 0     (0x00000000)
    id           = 197   (0xC5000000)
    label        = 392   (0x88010000)
    fill         = 1     (0x01000000)
    leng         = 2360  (0x38090000)
    loop         = 48    (0x30000000)
    xtyp         = TYPE#000027
    occu         = 4     (0x04000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x18081E94
    pgHook       = 0x00000000
    idxPtr       = 0x00000000
    shmTabhSet   = 0x00000000
    id           = 1541  (0x05060000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 4     (0x04000000)
    lineAlloc    = 4     (0x04000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0xA87F1B94
    collHook     = 0x00000000
    ext2         = 0x28940F93
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x70A22B93
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    XLIKP
    8000080015203CUSER14     06580920081014      Z0011000LF   X20081016200810152008101420081017200
    3333333333333455453322222333333333333332222225333333344222533333333333333333333333333333333333
    800008001520335352140000006580920081014000000A0011000C6000820081016200810152008101420081017200
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    <%_L195>
    CVBAP
    8000000012132000020T-AS301           T-AS301                                       0201     Su
    3333333333333333333524533322222222222524533322222222222222222222222222222222222222233332222257
    80000000121320000204D13301000000000004D1330100000000000000000000000000000000000000002010000035
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    MAT_AUF_HINWEIS_GEPRUEFT
    2
    0
    0
    0
    <%_L195>-UPDKZ
    UPDKZ_DELETE
    D
    4
    4
    0
    0
    IVBPA52_PAGIND
    0.0.1.
    000
    00C
    VBUK_KEIN_KREDITCHECK
    2
    0
    0
    0
    XLIPS[]
    Table IT_83[1x3552]
    PROGRAM=SAPMV50ADATA=XLIPS[]
    Table reference: 50
    TABH+  0(20) = E8F54D93F0282893000000003200000053000000
    TABH+ 20(20) = 01000000E00D0000FFFFFFFF0400000080330000
    TABH+ 40( 8) = 04000000C1108401
    store        = 0xE8F54D93
    ext1         = 0xF0282893
    shmId        = 0     (0x00000000)
    id           = 50    (0x32000000)
    label        = 83    (0x53000000)
    fill         = 1     (0x01000000)
    leng         = 3552  (0xE00D0000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000260
    occu         = 4     (0x04000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xD0896993
    pgHook       = 0x00000000
    idxPtr       = 0x00000000
    shmTabhSet   = 0x00000000
    id           = 410   (0x9A010000)
    refCount     = 1     (0x01000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 4     (0x04000000)
    lineAlloc    = 4     (0x04000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 2     (0x02000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0xC8402493
    collHook     = 0x00000000
    ext2         = 0x50E41293
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xC8532493
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    VBUK_KREDIT_NEUAUFBAU
    2
    0
    0
    0
    LT_INB_CIFEXT
    Table IT_2692[1x476]
    PROGRAM=SAPMV50AFORM=BELEG_SICHERN_POSTDATA=LT_INB_CIFEXT
    Table reference: 1104
    TABH+  0(20) = C095F993B8301E940000000050040000840A0000
    TABH+ 20(20) = 01000000DC010000FFFFFFFF0400000090AC0100
    TABH+ 40( 8) = 10000000C1308401
    store        = 0xC095F993
    ext1         = 0xB8301E94
    shmId        = 0     (0x00000000)
    id           = 1104  (0x50040000)
    label        = 2692  (0x840A0000)
    fill         = 1     (0x01000000)
    leng         = 476   (0xDC010000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#002271
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xF077F993
    pgHook       = 0x00000000
    idxPtr       = 0x00000000
    shmTabhSet   = 0x00000000
    id           = 1542  (0x06060000)
    refCount     = 1     (0x01000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x10000000)
    lineAlloc    = 16    (0x10000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 2     (0x02000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    collHook     = 0x00000000
    ext2         = 0x70E43294
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x70041E94
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    V50AGL-DISPLAY_FROM_ARCHIVE
    2
    0
    0
    0
    XLIKP-VBELN
    0080015203
    3333333333
    0080015203
    0000000000
    0000000000
    EMKPF
    4900035075200800000000000000          ##
    3333333333333333333333333333222222222200222222222222222222222222222222222222222222222222222222
    4900035075200800000000000000000000000010000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    VBMUE
    2222222222222222222
    0000000000000000000
    0000000000000000000
    0000000000000000000
    VBSK
    0000000000000000000000####   ####
    2222222222222222222222222233333333333333333333330000222000022222222222222222222222222222222222
    000000000000000000000000000000000000000000000000000C000000C00000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    PACKDATEN_VERBUCHEN
    2
    0
    0
    0
    No.       8 Ty.          FORM
    Name  BELEG_SICHERN_01
    IF_FINAL_CHECK
    2
    0
    0
    0
    LF_ONLY_FINAL
    2
    0
    0
    0
    LF_ONLY_PREPARE
    2
    0
    0
    0
    LF_FLAG_DOCNUM_NEW
    2
    0
    0
    0
    CF_SUBRC
    0
    0000
    0000
    T683V
    22222222222222222222222222222222222
    00000000000000000000000000000000000
    00000000000000000000000000000000000
    00000000000000000000000000000000000
    SY-XPROG
    SAPLBPFC
    5454454422222222222222222222222222222222
    310C206300000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    IF_RENUMBER
    X
    5
    8
    0
    0
    SPACE
    2
    0
    0
    0
    XVBPA_FIRSTIND
    0.0.1.
    000
    00C
    SY-REPID
    SAPMV50A
    5454533422222222222222222222222222222222
    310D650100000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    IF_POST
    X
    5
    8
    0
    0
    SYST-REPID
    SAPMV50A
    5454533422222222222222222222222222222222
    310D650100000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    XVBPA_AKTIND
    0.0.1.
    000
    00C
    No.       7 Ty.          FORM
    Name  BELEG_SICHERN
    %_DUMMY$$
    2222
    0000
    0000
    0000
    IVBPA2KEY
    000000
    22333333
    00000000
    00000000
    00000000
    IV_FINAL_CHECK_DURCHFUEHREN
    2
    0
    0
    0
    CHARX
    X
    5
    8
    0
    0
    LF_SUBRC
    0
    0000
    0000
    No.       6 Ty.          FORM
    Name  FCODE_SICH_OHNE_CHECK
    IVBPA1KEY
    000000
    33333322
    00000000
    00000000
    00000000
    T180-AKTYP
    V
    5
    6
    0
    0
    AKTYP-CREATE
    H
    4
    8
    0
    0
    CVBFA
    000000          000000 ####   ####        00000000000000                        0
    2222222222222333333222222222233333320000222000022222222333333333333332222222222222222222222223
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    000000000000000000000000000000000000000C000000C00000000000000000000000000000000000000000000000
    XSDCTRLFLAG
    22
    00
    00
    00
    SYST
    |    ######################################T#######################################µ#########XP####
    000000000000000000000000000000800000005000000000000000000000000000000000000010B0001000AF550000
    0000100000000000000010601000104000000040006050407000000000000000000000000000C0500010300F800300
    00000000000000000000000000000000000000000000000000000000000000000000000000000000000000AF000000
    00000000000000000000000000000000000000000000000000000000000000000000000000000000000000BF00000C
    GC_FCODE_PODCANC
    ABBR
    4445222222222222222222222222222222222222222222222222222222222222222222
    1222000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    XSDCTRLFLAG-PROTSAVE
    2
    0
    0
    0
    YES
    X
    5
    8
    0
    0
    GC_FCODE_PODQUIT
    PODQ
    5445222222222222222222222222222222222222222222222222222222222222222222
    0F41000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    PROTOCOLCALLER-SDL
    SDL
    5442
    34C0
    0000
    0000
    GC_FCODE_PODSTOR
    PODS
    5445222222222222222222222222222222222222222222222222222222222222222222
    0F43000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    LIKP-VBELN
    0080015203
    3333333333
    0080015203
    0000000000
    0000000000
    LIPS-POSNR
    000010
    333333
    000010
    000000
    000000

    Hi
    As soon as we have started to put things into UPDATE TASK, we must
    54 ensure that errors definitely terminate the transaction.
    55 MESSAGE A is not sufficient because it can be catched from
    56 external callers which COMMIT WORK afterwards, resulting in
    57 incomplete updates. Read note 385830 for the full story.
    From the above message I think u need to read the not 385830 in tcode snote.
    Thx.

  • VL02N:Post Goods Issue Error: PXA_NO_FREE_SPACE

    Hi gurus,
    i am testing post goods issue under vl02n after posting&delivering a sales order with type OR. the ' PXA_NO_FREE_SPACE' error occured after my clicking post good issue.
    PFB the error log, can anyone help to solve it out. TIA.
        No PXA storage space available at the moment.
    What happened?
        The current ABAP/4 program had to be terminated because there
        was no space available to load it.
        Each ABAP/4 program to be executed is stored in a central
        storage area that is divided between all users.
        This area was too small to hold all currently active programs for all
        users.
        Resource bottleneck
        The current program "SAPMV50A" had to be terminated because
        a capacity limit has been reached.
    What can you do?
        Since this could have resulted in a temporary bottleneck, you should
        try to restart the program.
        Ask your system administrator to increase the size of the area (PXA)
        used to store the ABAP/4 programs.
        Note which actions and input led to the error.
        For further help in handling the problem, contact your SAP administrator
        You can use the ABAP dump analysis transaction ST22 to view and manage
        termination messages, in particular for long term reference.
    Error analysis
        Unable to load a program of 1048576 bytes.
        The PXA ('program execution area') was too small to hold all
        currently active programs for all users.
        At present, the size of the PXA is set at 144868 Kbytes.
        The largest contiguous and unlocked memory chunk has 1014784 bytes.
    How to correct the error
        The current size of the PXA was set at 144868 kilobytes.
        You can increase or decrease the PXA in the SAP profile. When
        doing this, please refer to the relevent instructions in the
        installation manual.
        You can use the utility program 'ipclimits' to display the
        available system resources.
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "PXA_NO_FREE_SPACE" " "
        "SAPMV50A" or "FV50XF0B_BELEG_SICHERN"
        "BELEG_SICHERN_POST"
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
        1. The description of the current problem (short dump)
           To save the description, choose "System->List->Save->Local File
        (Unconverted)".
        2. Corresponding system log
           Display the system log by calling transaction SM21.
           Restrict the time interval to 10 minutes before and five minutes
        after the short dump. Then choose "System->List->Save->Local File
        (Unconverted)".
        3. If the problem occurs in a problem of your own or a modified SAP
        program: The source code of the program
           In the editor, choose "Utilities->More
        Utilities->Upload/Download->Download".
        4. Details about the conditions under which the error occurred or which
        actions and input led to the error.
    any reponses will be awarded,
    regards,
    samson

    Check these links where the same issue was discussed
    [PXA_NO_FREE_SPACE|http://www.sapfans.com/forums/viewtopic.php?f=12&t=304020&p=917783]
    [PXA_NO_FREE_SPACE Error|http://sap.ittoolbox.com/groups/technical-functional/sap-basis/pxa_no_free_space-error-858115]
    thanks
    G. Lakshmipathi

  • Post Goods Issue - error : Class type does not exist - Message no. VK662

    Hi,
    I am trying to do Post Goods Issue and getting this error: Class type does not exist
    When double click on the error, it shows it is a message no vk662.
    Any help to resolve it is appreciated. Thanks in advance.
    -Sri

    Sri
    There is a problem in batch determination.
    The batch you assigned to the material does not have a class or if it has a class, that class does not exist.
    Display the batch from the delivery item  using MSC3N and go into the Classification tab. You should have a class of class type 22.  See if that class exists in CL03 and its status in basic data tab. Work on these lines and revert.
    Hope this helps.

  • Unplanned goods issue error

    Hi ,
    How to do unplanned goods issue of those components which are not in the BOM of production order. In migo we can do it by 261 and choosing others.till here its ok but against what document migo will be done. I mean to say there should be some document which the shop floor guy must give to the stores so that he can do the migo( unplanned goods issue) in SAP.
    I thought i can address this problem by creating a reservation and then take a print of that reservation and print out can be the document for the stores.
    So I tried to create a reservation in MB21 , movement type 261, but couldnt create the reservation because of following error:
    "Manual reservation for order category 10 not allowed"
    Please help to resolve..
    Is there any other to create a document without creating a reservation??
    I want to see a report of unplanned goods issue VS planned goods issue.Is it available or has to be developed?
    Regards

    Hi,
    I know thru MB1A or migo 261 i can issue goods to prod order and that will flow as unplanned goods issue. But if the worker  or supervisor  on shop floor goes and tells stores to issue him goods which are not in the Goods issue slip, then will the stores do this above mentioned transaction?? no he will not. he will ask for some hard copy.
    we should think from business point of view also.
    What i am asking is:  the way we have reservation print out or goods issue slip print as a document to enable stores to issue planned goods, what is the document to issue unplanned goods ??
    Please help.
    Regards.

  • Goods issue error at batch level stock

    Hi Experts,
    In MMBE for Material 12121426 Plant 6348 storage location  0001,batch 4065634891 in storage
    location level have stock is 12.000 EA and batch 4065634891 level stock is
    4,164.000 EA
    User is performing Goods issue through MB1A 261 movement type For 4,164.000 EA EA but showing error
    is Deficit of SL Unrestricted-use 4,152 EA : 12121426 6348 0001 4065634891
    Please suggest any one why batch level stock not updated to storage location level and why system not allowing batch level stock in MB1A How to rectify this error
    Regards
    Mohan

    You probably have to contact SAP. There is hot news about inconsistencies between batch stock and storage location stock: 1930161 - Stock inconsistencies in table MCHB for batches
    See as well KBA 1963022 - More details on the stock inconsistencies situation mentioned in Hot News 1930161

  • VL01N Post Goods issue error

    Hi Gurus,
    In ECC 6.0 version in VL01N t.c. when i press "Post Goods Issue" button i confront following error;
    Fld selectn for mvmt type 601 / acct 621000 differs for Settlement period (003)
    Message no. M7093
    Diagnosis
    Comparison of the field selection strings from movement type 601 and G/L account 621000 has revealed that there is an incompatible field selection combination at one or more points.
    Field for which the field selection is different: Settlement period
    Example
    On the movement type screen, a given field is a mandatory-entry field, whereas on the G/L account screen, the same field is suppressed.
    System Response
    You cannot post this transaction, unless you have changed the field selection adequately.
    Procedure
    Contact your system administrator.
    Action to be taken by the system administrator
    Check whether any postings resulting from this movement type are to be made to the G/L account determined automatically. If you find that the G/L account is not correct, check the automatic account determination in the Customizing system for valuation.
    Proceed
    If the G/L account is correct, use the report RM07CUFA to compare the field selection for the movement type with the field selection for the G/L account and change the incorrect settings or the field status group of the G/L account.
    Proceed
    I tried adviced actions but no any solution. Could you please guide me to solve the issue with step by step and reference t.c.
    thanks

    Check these threads where the same topic was discussed
    [Re: Fld selectn for mvmt type 561 / acct 2005999 differs for Ext. GA amount in|Fld selectn for mvmt type 561 / acct 2005999 differs for Ext. GA amount in]
    [Error while adjusting the Consignment Stocks |Re: Error while adjusting the Consignment Stocks]
    thanks
    G. Lakshmipathi

  • Goods Issue Error

    Hi all,
    I have WM and HUM active.
    I'm trying to post a GI to Cost Center using the transaction MIGO and Movement type 201. I get this error during the transaction:
    Data for creating a delivery is incomplete (Vendor)
    Message no. M7279
    Diagnosis
    The system found that the data required to create a delivery via Shipping is not complete.
    System Response
    The system cannot create a delivery.
    Procedure
    Check that the data for Vendor is maintained in your system:
    loading group
    debtor number
    sales organization
    distribution channel
    division
    shipping condition
    shipping point
    It's strange that the error is specific to vendor because this is an inhouse transfer to a cost center. However, I've maintain the listed items in spro.
    There's still something wrong and I'm at a loss. What am I doing wrong? How can I correct it?
    Any suggestions would be appreciated. Thank you.

    Hi,
    If the issueing plant/stro.loc. is HU&WM managed, outbound delivery should be created.
    Please check:
    img -> logistics general -> Hu -> basis -> MM -> IM -> HU requirement for stro.loc. and default value  for deliveries.
    Here you should assign a default customer for this plant/storage location. You also have to define default sales area.
    THen you have to make sure that:
    1. customer and material master all exists in the sales area.
    2. shipping condition, loading group is maintained.
    3. shipping point determination /  item cateogry determination is maintained.

  • Goods Issue Error Message for Stock Transport Scheduling Agreement

    Hello,
    I have set-up an inter-company stock transport scheduling agreement, delivery is created and stock is picked. Upon PGI of the delivery I receive the following message, has anybody and ideas of the root cause?
    Message - E M7 153
    Purchase order XXX does not contain items for a stock transfer
    Thanks.

    Dear,
    Please check vendor
    http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/help-with-config-of-one-step-sto-720045
    Regards,
    Syed Hussain.

  • Error Goods issue by using IW41

    Hi Experts,
    I use IW41 to do Goods Issue. error msg as below.
    please advise why the GI is fail. and how to overcome it.
    Thanks
    Regards
    <
    Confirmation saved (Goods movements: 0, failed: 1)
    Message no. RU110
    Diagnosis
    The confirmation of the operation involved goods movement postings. The system informs the user that 0 goods movements were successfully posted and that 1 goods movements could not be posted due to incorrect or insufficient data.
    Procedure
    You can manually post the goods movements that could not be automatically posted by calling up reprocessing on the initial screen for production orders.
    >

    check Tcode COGI and see error log

  • Work Order Issue - Error Creating Goods Delivery,Goods Issue or GRPO

    We use SAP Business One 2007 A PL:08. We have an add-on for the work orders and While putting the work order from released to completion, a user is getting an error message that says:
    "Error Creating Delivery,Goods Issue or Goods receipt PO- Error Issuing Delivery Note -Item no. is missing [DLN1.Itemcode][Line:3]"
    I do not see any item missing in the work order and all the posting periods are open. I have checked all possible settings!!
    Any idea what this could be?
    Thanks

    Hi,
    Is it your add-on or a 3rd party add-on?
    Thanks,
    Gordon

  • Error Code "-5002" While adding a Goods Issue Document

    Hi,
    While adding a goods issue document for only a specific combination of items I get "Internal Error (-5002) occured" message.
    The scenario is i am adding 5 rows with following specification
    Row1- Serial Managed Item
    Row2- Batch Managed Item
    Row3- Managed by none
    Row4- Batch Managed Item
    Row5- Serial Managed Item

    Hi I had the same Issue,
    What my problem solved was setting the baseline number for each serial and batch number on each specific line to the line number of that specific line.
    like this:
    doc.Lines.SerialNumbers.SetCurrentLine(doc.Lines.SerialNumbers.Count - 1);
    doc.Lines.SerialNumbers.InternalSerialNumber = 2;
    doc.Lines.SerialNumbers.BaseLineNumber = doc.Lines.SerialNumbers.Count - 1;
    Regards

  • Error message while posting goods issue.

    Hi,
    Please help me with the following problem..
    I have created Sales Order, Delivery & also created the Transfer Order number. After creating Transfer ordering, while submitting post goods issue, when I click on PGI, I get
    "Posting only available for period 2002/10 to 2002/11"...
    As a resulf of the above, I am not able to complete Billing for all the sales orders I have created.
    Can somebody please help me with above?
    Regards
    Nadeem

    Use the MMPV transaction to check your current period. Since you have transactions already done you need to do closing for every month.
    If you are on an IDES system for training purposes you can do a fast transaction by removing the plant assignment from the company code. The use the MMPI transaction to set your current period. Remmber April is period 1 if you are are using the indian financial year and fiscal year variant k4.
    Then reassign the plant and now try posting It will allow you. But a word of caution. Never attempt to remove the plant asignment in the development system. It might cause errors. for that there is a separate note.
    regards
    Jude

  • HU error when Reversing the goods issue in STO process

    Hello Gurus,
    I will explain the whole process we follow for STO:
    1. Create sales order ->Based on PR in sales order schedule lines, PO will be created -> outbound delivery -> Pack in HU -> PGI -> based on output type Idoc will be triggered -> this outbound IDOC will create the Inbound IDOC and Inbound delivery -> Here HU will copied from Outbound delivery (Means both in inbound delivery and outbound delivery HU is same)-> then do the Good receipt in Inbound delivery.
    Now when user doing the goods receipt he is getting error MSSA-SATRA exceeded by 1PCE  The reason is someone deleted the item from the sales order.  Hence when user trying to post the GR it is checking for the open sales order item in MSSA table.  Since it has been deleted from the sales order he cant able post GR.
    Now user does not wants to receive this item, hence we wants to reverse the process.
    So we followed the below process:
    1. Unassigned the HU in Inbound delivery and then deleted the Inbound delivery.
    2. Then used VL09 transaction to reverse the goods issue.  But system giving error saying that HU is already assigned to object.
    I cant able to reverse the Goods issue since the HU is same in Inbound delivery and outbound delivery.
    Kindly suggest the reversal process for the above case.  Many thanks for your help in advance.
    Awating for your valuable replies.
    Br,

    Insted of deleting the handling units you should have un assign the handling units from inbound delivery.You have deleted the handling units and the same handling units will not be available in outbound delivery Pack icon.
    Do one thing are you able to enter line item in sales order ?.If yes then create inbound delivery manually and create new handling units for the qty and do GR.
    Currently where is the stock is it transit ?.If yes then above option may work.
    If nothing is possible only an option to write a SAP oss note they will correct your outbound delivery and inbound delivery.

Maybe you are looking for