PFCG_ORGFIELD_CREATE : post usage issues

Hi,
i used PFCG_ORGFIELD_CREATE to convert one field CO-OM Responsibility area  (RESPAREA) to Org Level. and yes field do show up in USORG table also.
executed, it showed list of roles, which are effected
now when i open roles to generate, it is showing that org field in display mode in 'organization levels' button and when i click on change button in front of it, get error 'Authorization object  is invalid'.
and i have to use /nex in another session to close this session also.
strange.... not sure what to do
please advice
regards,
Surpreet
does it matters if client is open or not
Edited by: Surpreet Singh Bal on Oct 28, 2010 7:32 PM
faced same error even after opening the client in SCC4
Edited by: Surpreet Singh Bal on Oct 28, 2010 7:43 PM
FOUND similar thread
Re: Error KI870 Authorization Object Is Invalid
Edited by: Surpreet Singh Bal on Oct 28, 2010 8:00 PM

Hello,
it's right the solution for CO-OM issue is the above note or the answer given in the other thread.
Additionaly I would urgently suggest to implement note 1502568. Only on that way, you will have change documents for the SU24 and the Activity groups.
Best regards,
Dieter.
Edited by: Dieter Goedel on Nov 3, 2010 6:31 AM

Similar Messages

  • Changing the field content of 'wrbtr' in accounting document during Post Goods Issue in VL02N

    Hi Experts,
         I have requirement ,where I need to  change the 'amount in document currency value (wrbtr)' in line item of a accounting document, which is created as part Post Goods issue through VL02N.
              I have already check BADI's below as follows:-.
    1) LE_SHP_GOODSMOVEMENT- No accounting document information flows in this BADI.
    2) AC_DOCUMENT - Field 'WRBTR' is not available in substitutable fields list.
    3) BTE-1050 - This BTE is not getting triggered while doing PGI.
            Please suggest any other possibilities to make the change.
    Thanks & Regards,
    Suganth.

    Hi Kartik,
                I have checked the enhancement you specified, but it didn't trigger during PGI. Can u please let me know is there any other possibilities to make the change.
    Thanks
    Suganth.

  • Profit Centre Document issue at the time of Post Goods Issue on SD.

    Dear Experts,
    While SD person is posting Post Goods Issue, System is generating Profit Centre Document along with other documents. We are facing an issue with Profit Centre document here and the issue is:
    Some Profit Centre Documents are populating Delivery Order Number on respective field while some are not. Ideally all profit centre line items should show Delivery Order Numbers.
    Please guide any solution to resolve this issue, its urgent.
    Thanks in Advance.
    Regards,
    Zain Bashir

    Hi Zain
    This is a tricky issue
    Are you saying that the PCA document has the Delivery Number (VL01N) updated in some cases and not updated in some cases?
    The Delivery Number is updated in PCA document when you create Delivery from VL01N and do PGI from VL02N
    But, if you do PGI from VL01N itself, then the delivery number is not updated in the PCA document
    SAP recommends to post PGI from VL02N
    Br. Ajay M

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

  • Billing doc while post goods issue

    Hi,
    Is there any Exit to creat a billing doc immediately when we post goods issue.
    Please, if there any other solution. don't hesitate.
    Thanks.

    You can use message condition record in outbound delivery ,as soon as you do PGI ,this message condition will trigger & it will create Billing document Back ground.Take ABAPer help he will guide you.

  • STO - JEX invoice getting created without Post goods issue of delivery

    Dear Experts,
                We have configured the "Stock Transport Purchase Order" process between 2 different plants within same company code. To satify the Indian legal process, after PGI issue we configured the process as "Proforma" invoice creation using Billing type ZJEX (Copy of JEX). And then Excise Invoice creation using J1IIN.
                      Now problem we are facing is, without "Post Goods Issue" of delivery ZNL also system is allowing to create the invoice using ZJEX type. We are using the standard NLN item category only. But our requirement is, without "Post goods issue" system should not allow to create the sales invoice.
    Can anybody give your suggestion on this issue.
    Thank u
    Regards,
    Nag

    Dear Experts,
            Thanks for your feedback. As per your suggestion i modified the copying requirement in to "034". But during invoice creation i am getting the message that "The item is not relevant for billing". So not successful.
    Can you please give suggestion to solve this issue
    Regards,
    Nag

  • Can we Create Post Good Issue Document as Background Job

    Hi SAP Techies,
    My current projects requires me to run Post Good Issue , as Background Job, Is it possible to do it.If yes
    What is the entire process.
    Regards
    Naveen

    Hi
    The answer to this question lies in transaction VL23.
    You can create a variant and schedule it to run; for example at 10:00 pm every night.
    You need to explore this more but this t-code is the main answer.
    Please reward points if you found this helpful.
    Regards
    SDC

  • 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

  • Can not "post goods issue" against Vendor Return PO.

    Hello Friends,
    **I have a problem During the "Vendor Return Through Purchase Order" Process.I crated a PO with return flag set.**
    **Then  1) Created a outbound delivery against purchase order (VL10B)**
              2) Created a Billing (VF01)**
              3) Next is VL02N - While doing the "post goods issue" where i got following error  message "Update control of movement type is incorrect (entry 161 X X _ L)"**
    Its shows setting related to Mvt 161 to update .I check allowed transaction with respect to 161....VL02N is there .....But don't understand what change needed in "Update control /WM movement type is needed.....Pls suggest any solution........Thanx**
    Regards
    Sachin
    *Error Messafe -
    Update control of movement type is incorrect (entry 161 X X _ L)
    Message no. M7226
    Diagnosis
    The system could not find entry 161 X X _ L in any of the movement type control tables.
    Procedure
    Cancel current processing.
    Contact your system administrator.
    Action to be taken by the system administrator
    Check in Customizing for Inventory Management under Copy, Change Movement Types whether the entry is contained in the Update control view for the movement type.
    If the entry is missing, proceed as follows:
    For standard movement types, this means that the given process is not supported using the present data combination. Do not create any entries without prior arrangement with your SAP consultant. Otherwise, incorrect postings may result.
    For customer-defined movement types (beginning with 9, X, Y, or Z), this may mean that they have not been fully defined. Delete the movement type and re-create it by copying a standard movement type.

    Hi Antony,
    Thanx for reply.
    1) I had assign  delivery Type (RL -Returns Purchase order) to my document type. Assingnment of delivery type thru
    spro>MM->purchasing>purchase order->set up stock transport order--->assign delivery type and checking rule....
    2) MvT - 161----If i modify 161 wrt to  GR Returns what modification is needed ? ......
    3) VOV6 - I had checked it ,maintain it, but that is not relavant in my case....
    4) During PGI system pick 161 as defalult MvT.....can we change it t0 122 ? but how...??
    still the problem is there......
    Sachin

  • Goods picking and Post goods issue in VL02N

    Dear All,
    Am hving problem in Picking goods and Post goods issue.
    This is for the Stock Transport Order with Delivery via Shipping
    Supplying plant is 1000(SAP std,sloc 0001) and Receiving plant 1100(sloc 0001).
    Sales org:1000
    Distrbn Chnnl:10
    Division:00
    1.maintained matrial for both the plants.
    2.Creted STO by using DOC type as "UB" and item cat "U".
    3.And getting the Shipping data for the material in the STO.as shipping point is 1000.
    saved the Po.
    4.After that i done the GR w/o PO for the material using Mvt type 501.
    5.Then,VL10B creating Delivery doc.n this is also created.
    6.but when i do the picking and PGI in VL02N there picking field is greyed out bt i have tried to mangae that when i give the picking Qty in the picking qty field system is throwing the following error.
    <b>Item to be picked by WM (picking quantity cannot be entered)
    Message no. VL118
    Diagnosis
    For this item, picking is carried out using warehouse management transfer orders since the material is stored in a warehouse with random storage.
    System Response
    The system does not allow you to enter a picking quantity manually. The picking quantity is copied automatically into the delivery during the creation of the corresponding transfer order.</b>
    is any data missed by me while doing this process?
    pls let me know n help me in this regrds
    Thank you all

    Hi Vijay
    By changing storage location you could do b'coz the new storage location is not maintained with warehouse, hence no need to perform warehouse transactions (TO creation and confirmation) before inventory mgmt transactions (PGI).
    For trying pick up with WH, first u should have enough stocks in approppriate storage bins and u should perform pick up by creation of TO and confirmation.
    warm regards
    sairam akundi

  • Need Bapi Names for Post Goods Reciept and Post Goods issue to STO in MIGO

    Hi All..
    I need to post goods receipt using input data in MIGO. Is there any BAPI that i can use.
    Also once STO (Stock Transport order) is created, i also need to Post goods issue to STO in MIGO transaction. I do need a bapi for this too...
    Appreciate your help and will reward any helpful answers.
    Thanks..

    Hi,
    ata  : gm_header  type bapi2017_gm_head_01.
    data  : gm_code    type bapi2017_gm_code.
    data  : gm_headret type bapi2017_gm_head_ret.
    data  : gm_item    type table of
            bapi2017_gm_item_create with header line.
    data  : gm_return  type bapiret2 occurs 0 with header line.
    data  : gm_retmtd  type bapi2017_gm_head_ret-mat_doc.
    clear : gm_return, gm_retmtd. refresh gm_return.
    gm_code-gm_code      = '03'.
    gm_header-header_txt = firstscreen-bktxt.
        gm_header-pstng_date = sy-datum.
        gm_header-doc_date   = sy-datum.
        gm_header-ver_gr_gi_slip = ' '.  "print
        gm_code-gm_code      = '03'.
      move lineitem1-bwartwa  to gm_item-move_type     .
          move lineitem1-matnr  to gm_item-material.
          move lineitem1-erfmg     to gm_item-entry_qnt.
          move 'EA'    to gm_item-entry_uom.
          move lineitem1-werks  to gm_item-plant.
          move lineitem1-lgort  to gm_item-stge_loc.
          move lineitem1-kostl to gm_item-costcenter.
          while gm_item-costcenter+9(1) = ' '.
            shift gm_item-costcenter right.
          endwhile.
          overlay gm_item-costcenter with '0000000000'.
          append gm_item.
    call function 'BAPI_GOODSMVT_CREATE'
           exporting
                goodsmvt_header  = gm_header
                goodsmvt_code    = gm_code
           importing
                goodsmvt_headret = gm_headret
                materialdocument = gm_retmtd
           tables
                goodsmvt_item    = gm_item
                return           = gm_return.
    Thanks
    venki

  • Idoc to post goods issue against an outbound delivery

    We happened to simulate both the idocs 'WPUWBW01' and 'MBGMCR02' for posting goods issue for an outbound delivery but failed.
    Request you people to help us on this. Is there another idoc that we have to use to post GI... if so please let us know... and if we are using the right one, guess we are not executing it in the right way... in such a case please guide us with the steps...
    Thanks
    Arun
    We got hold of the Idoc type 'DELVRY03 PGI SHPCON' we are able to post the Idoc but we are able to do the packing only or we are able to change the deliveries but the PGI is not happening..
    please help us on this.. is there some condig that updates the delivery with the PGi or is there something else do be done in the Idoc....
    will provide additional details if required.
    Thanks

    Hi Arun,
    There are no configuration settings in this. It is development that your abaper need to carry out.
    Explain to him that this is the func module. And intrun it has to either trigger a BDC or BAPI for creating packing and PGI.
    He should then do the recording of that and will assign the program pertaining to BDC with in the function module.
    One more suggestion is to put the same query in ABAP section too. U will definitely get a positive response.
    Hope this helps.
    Kind Regards
    Chakradhar

  • Need User Exits for Creation of Delivery and for Posting Goods Issue

    Hi,
    I need User Exits for
    Creation of Delivery
    Posting Goods Issue
    I need to make some checks regarding customer license expiration and if checks fail, I need to stop Creation of Delivery and Posting Goods Issue.
    Thanks in advance,
    Will reward,
    Mindaugas

    In the delivery you can use userexit USEREXIT_SAVE_DOCUMENT_PREPARE to make your checks and send an error message to the user in case they fail.
    You can find this user exit (form routine) in include MV50AFZ1.
    Hope that helps,
    Michael

  • Inter Company -Error in Post Goods Issue

    Dear Experts,
    I have developed new intercompany process between selling company & supplying company to customer. I have created sales order and delivery order. After delivery, am able to to PGI. If i check the Post goods issue document number accounting documents, supposed to take 0020 (selling company code) but its taking some different company conde. we never user that company code for intercompany scenarion. Vould you please tell me...why its taking different company code and how its taking wat we have to do. pls suggest me.  and let me know what are the steps involved during PGI (bcoz PGI accounting entries are automatic)
    Thanks & Regards

    Dear Murali,
    I have checked as per ur suggestions, every things is correct but why it is asking different company code. Actualy our intercompany process between 0010 to 0020. 0010 is the supplying company and 0020 is the selling company. i have assigned 0020 s.org to 0020....config side everything is ok ...i never maintain 0315...but when am doing PGI its getting error                                                                               
    No accts maintained for company code clearing between comp.cds 0010 and 0315.
    Menas here for  acoount clearing between 2 company codes its taking another company code istead of 0020. If its take 0020 i wont get help bcoz we maintained account clearing between 2 company codes.
    Please suggest me
    Thanks & regards
    VS

  • How to fetch post goods issue date and sales order creation date

    Hi All,
    How to find out the difference between SD Sales Order Item Creation Date and final Post goods issue Date. I would like to know how to fetch those dates and what is the relationship between the tables from which i will get the dates.
    Please let me know the solution .
    Thanks in advance.

    Hi,
    Sales order creation date is when u raise a sales order in favor of the customer using VA01.......using ATP logic system purposes the material availability date....
    after saving ur sales order...when u raise the Delivery using VL01n  w.r.t to OR...than u have to perform picking ....In the picking Tab...specify the amount to be picked than press Post Good Issue....means the goods left the company premises ..
    You can the fetch the values using tables-  Use T code   SE12  or SE16
    Vbak-----order header
    Vbap-----order item
    Vbek-----order schedule line
    Likp-----Delivery header
    Lips----Delivery item

Maybe you are looking for