Updation of MCHB-CLABS value on Post Goods Issue through VL01n

When POsting Goods Issue I need to change  MCHB-CLABS value.
My requirement:
When quantity left in the stock is less than (MCHB-CLABS)  .005  I am adding the remaining quantity left to delivered quantity, but the stock (MCHB-CLABS) is not getting updated. It remains the same quantity less than .005.
Could you tell me any parameter in user exit which I need to modify?

Hi,
VL01N has one BAdi called "DELIVERY_PUBLISH".
Why don't you use User exit for solving your problem?
Following are the user exits availble for the transaction:
V53W0001  User exits for creating picking waves                  
V53C0002  W&S: RWE enhancement - shipping material type/time slot    
V53C0001  Rough workload calculation in time per item                
V50S0001  User Exits for Delivery Processing                         
V50R0004  Calculation of Stock for POs for Shipping Due Date List    
V50R0002  Collective processing for delivery creation                
V50R0001  Collective processing for delivery creation                
V50Q0001  Delivery Monitor: User Exits for Filling Display Fields    
V50PSTAT  Delivery: Item Status Calculation                          
V02V0004  User Exit for Staging Area Determination (Item)            
V02V0003  User exit for gate + matl staging area determination (headr)
V02V0002  User exit for storage location determination               
V02V0001  Sales area determination for stock transport order         
VMDE0004  Shipping Interface: Message SDPACK (Packing, Inbound)      
VMDE0003  Shipping Interface: Message SDPICK (Picking, Inbound)      
VMDE0002  Shipping Interface: Message PICKSD (Picking, Outbound)     
VMDE0001  Shipping Interface: Error Handling - Inbound IDoc          
Regards,
Dharitree

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.

  • Generate DELVRY  Idoc when Post goods issue is done in SAP

    I need to generate an Idoc when post goods issue is done in SAP (outbound to SAP) .I understood that I can do this using the message control .The message type DESADV with the process code DELV will support this.
    But I didn’t understand how to trigger the Idoc.In the current scenario our Company is doing the post goods issue in SAP for the in three different ways.
    1.Manually doing the post goods issue through the transaction VL02N
    2. an Inbound Interface (using Idoc)  which will do Post goods Issue in SAP
    3.Another Interface using BAPI, which will, do post goods issue in SAP
    I have to run my outbound interface when the post goods issue is done by all the above three ways.  Can any one help me out in this?

    You have to configure the output first .
    You can use output type LAVA ( avaialble in Std SAP ) .
    ( Tcode is NACE , Select Application V2 -> Outputtypes ).
    ( Create condition records suitable to generate an output)
    Next is ALE.
    Setup a distribution Model ( for DESADV ) and all other setup for ALE i.e. Distribute Dist. Model / Generate Partner Profile .
    In the Partner profile in WE20 select your partner system. Double CLick on Outbound Message DESADV ( this wd be there after you generate partner profile , if not add it here in outbound ) . On this screen goto tab MESSAGE CONTROL .
    Application - V2
    Message Type - LAVA
    Process Code - DELV.
    Now you are ready to go. The moment a PGI is done in any form an output LAVA would be proposed and processed using process code DELV.
    Cheers.

  • Automatic Billing with Post Goods Issue

    I need Help on How to Make Automatic Billing while Posting Goods Issue, The Process Flow as Below:
    VA01 Make Sales Order ( Normal Sales Order "OR" )
    VL01N ( Picking and Post Goods Issue )
    VF01 ( Make Billing )
    My customer needs when he Posts Goods Issue in VL01N , automatically the Billing document to be Posted and The Invoice Printed, without Going to VF01 to make the Billing.
    We are using SAP ECC 6.0
    Please Note: i need it on how to do it in customization and with out using the Report (RV60SBT1) which makes collective billing in the background using a job
    Thanks for Your Help

    Dear Omar,
    One way is to use background jobs which will create billing documents in the background (VF06).
    Another way is write a BDC program.
    Refer to following links, in which the same has been discussed.
    Automatic billing
    Re: How to set up in SAP to have automatic billing after PGI
    Hope, you may find this informaton useful.
    Best Regards,
    Amit

  • Update was terminated when Post Goods Issue

    Hi all,
    When I post goods issue, I receive a message "Update was terminated".
    Then, I use SM13 to check update requests, I see an error
       900     USERNAME     20.11.2007     10:47:27     VL02N                         
    double click on that line I see error at module
       8     MB_POST_DOCUMENT     V1     Error
    more details:
       Row 13 in report LMBMBU04
       00 671: ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC
    Finally, Error occurr at line:  
       INSERT mkpf FROM TABLE zmkpf.
    Can anyone help me to solve this problem?
    Thanks.

    Hi Nam,
    This probelm is becuase you are trying to enter a record for which primary key already exists in the table.
    The insertion you are doing with a set of values which already exist and sap is getting this error that the "Duplicate record during insertion". try to check your insertion values and through se16 check if they already exist in the table mkpf.
    To rectify the data or else change the table and add one more unique to the primary key.
    Abhishek Purwar
    http://abhishek.purwar.googlepages.com

  • Goods receipt and post goods issue are not updated back from EWM to ECC

    Hi Experts,
    Would anybody able to tell me the setting to be modified / defined to backward flow of information from EWM to ERP i.e. the goods receipt, goods issue are not being updated back in ECC once the goods receipt and  post goods issue are posted in EWM?
    It would be great help if i get the response as early as possible.
    Chakrapani Das

    Hi Chakrapani,
    You might want to try checking the customization on the SCM part following this path:
    SPRO - Extended Warehouse Management - Interfaces - ERP Integration - General Settings
    Pay special attention on the Check of ERP-EWM Configuration transaction.
    After you have checked these you should probably check the outbound queue monitor (tx SMQ1) from EWM to ERP. You can use the SMQ1 - Outbound queue and SMQ2 - Inbound Queue both in ERP and SCM to check the communication betweene these two systems.
    Also you may want to checkt the SLG1 - Analyse application Log in SCM in order to see if any internal bugs exist.
    All the best,
    Claudiu Maxim

  • Post Goods Issue Accounting Entry & Profit Center Updation???

    Dear All,
    At the time of Post Goods issue it generates an accountng entry.
    we are getting an error related to Profit center.
    we maintained profit center in the sales order. and please clarify me can we create cost element for COGS account which hits at this level.
    I am getting the following errror.
    Balancing field "Profit Center" in line item 001 not filled
    Message no. GLT2201
    Diagnosis
    The field Profit Center marked as balancing is not filled with any value in line item 001, even after document splitting.
    System Response
    The document cannot be posted.
    Procedure
    First check your entries.
    Additional causes could be:
    No value can be derived for this field from the current document data.
    You have entered a document type that is not designed for this business purpose.
    Procedure for System Administration
    Customizing
    But we need profit cener wise balance sheet.
    so please guide me.
    regards,
    shashi kanth.

    If you define document splitting criteria based on Profit Center and if your document contains multiple line items with different profit center, this type of error will come.
    To check this, Go to IMG Path -- Financial Accounting (New) --> General Ledger Accounting (New) --> Document Splitting --> Define Document Splitting Characteristics for General Ledger
    There check whether the mandatory check box is selected for profit Center.  So check in your delivery document, whether any line item does not have profit center.
    You can also have a look at any of the following notes
    a)  995055
    b)  1074689
    c)  1079819
    thanks
    G. Lakshmipathi

  • Update termination error when posting goods issue

    Helllo
    I have a strange problem I can not figure out.  We have serial numbers like 12345/345.  When trying to post goods issue I get an update termination error  for invalid character. This only happens if the quantity is more than 1 each.  A quantity of 1 each works fine and receives no update termination when post goods issue...only recieve termination error if the post goods issue is for a qty of 2 each.
    I searched the SAP site found OSS note 40355...applied the note.  The note also mentions the chaging print paramters to include "/ _"  this is all done.
    I tried doing a ABAP Debug in SE38 (for the delivery note print program) and setting the breaking point, but when I go to run the transaction after the setting break point...when I hit post goods issue...SE38 does not return back to its screen.  So not sure if I am running the correct program there...or if this works for the update terminations?
    So strange I do not get this for a qty of one each only when it is greater than that.  I am stumped need help....
    Any advice wiould be GREATLY appreciated....

    Looks like there is an error in the delivery (or material movement ?) print program. Easiest would be to disable these outputs for test purposes. When no dump then the error is somewhere in the print program an could be analysed by triggering the print separately with ABAP RSNAST00.
    regards Jack

  • Posting goods issue using Message type SHPCON and idoc type DELVRY03

    Hi SAP Gurus,
    I am using message type SHPCON and idoc type DELVRY01 with processing code DELV to post goods issue for a delivery note.
    I tried to simulate the inbound entry via WE19. The scenario should be posting goods issue based on the delivery order.
    In some cases, quantity issued is less than the quantity in the DO. For this, I need to change the delv quantity in the DO via VL02N before I select Post goods issue button. This will change at the same time post the goods issue.
    What I have filled up are the fields:
    E1EDL20-VBELN = DO num
    E1EDL20-VSTEL = Plant
    E1EDL18-QUALF = "PGI"
    E1EDTH13-QUALF = "006"
    E1EDTH13-NTANF = date today
    E1EDL24-POSNR = 000010
    E1EDL24-MATNR = material num
    E1EDL24-WERKS = delv plant
    E1EDL24-LGORT = sloc
    E1EDL24-LFIMG = updated quantity
    But everytime I simulate using WE19, the entire quantity in the DO is not changed at all. The goods issue quantity posted is still the original DO quantity.
    May I know how to do this? Thanks.

    Put value in E1EDL24-LGMNG for qty to pgi.

  • No Acc. Doc generated after Post Good Issue - please help!

    Hi All,
    I have problem when I try to post good issue, the accounting doc doesn't generated.
    I have created SO, (Order type - OR, item category - TAB, Schedule Line cat - CB), created PO after the purchase requisition was generated in the SO. processed good receipt and created outbound delivery, everything is fine until post good issue, there is no Acc. Doc created automatically after PGI.
    I have check the following setting
    material type attribute setting - ok (standard price control, val.update, qty update)
    valuation level - ok (valuation area is plant)
    valuation grouping code - ok (activated)
    valuation areas assigned to the valuation grouping code - ok
    valuation class(s) is linked to material type(s) vis acc. cat. ref. - ok
    accout grouping for movement type - ok (leave it as default)
    configure auto posting - ok (I have run the simulation test, and created the missing G/L acc in the company code which under testing)
    The WL Acc Doc type is defined and assigned with number range.
    material and accounting period are open
    In Purchase order, the purchase item assigned with Acc Assignment Category E, Special Stock is E, Consumption Posting set in Acc Assignment Category is E, Acc Modification is VAY, GR non-valuated and GR non-val. binding checkboxes are deselected.
    I know the Acc Assignment Cate will affect the auto acc posting in GR, but I am not sure it will affect PGI in the same way.
    Could anyone tell me which value string will be using for this auto acc posting for PGI? My best guess is
    MvT S val. update, qty update Mvt Cns
    601 E YES YES L ?
    Could anyone tell me what cause the Acc Doc not be generated after PGI?
    Thanks for your time
    Alvin

    thanks for reply.
    Regard to the point 2 suggested by Cathy, the account determination for billing is set, the accouting doc is created after billing.
    my problem is no acc. doc generated after PGI.
    meanwhile I have searched a similar problem in other forums, I found some similar reply as Prasanth did, so I think I may try to run VA88 to see the result.
    Prasanth, could you please explain the pinciple behind of why this happen if what you say is correct.
    Thanks for your time!!!
    Alvin

  • Effects at Post Goods Issue.

    Hi experts,
    can any body tell me which are the 4 effects happen at the time of Post Goods Issue ?
    I know only one i e Inventory A/C gets credited and COGS gets debited.
    Prashant.

    hello, friend.
    you actually cited 2 effects (decrease in inventory value, increase in cost-of-goods sold), and may have cited a third, which is that inventory quantity is updated.    documents related to material movement and FI/accounting are also created.
    another is that by doing PGI, your transaction (delivery) now appears in the billing due list.
    regards.

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

  • 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

  • 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

Maybe you are looking for