Exception in CRM system after creating post goods issue in ECC

Hi Folks,
We are facing an issue in CRM system. I will tell the scenario in details so that it would be helpful to understand,
We are creating sales order in CRM system and it got replicated to ECC correctly. We have maintained action definition to trigger email to the customer.
Then we will be creating delivery and then post goods issue(PGI) for items replicated to ECC systems. After PGI system will update the status in CRM sales order and here configured an action definition to trigger an email to customer.
We have created custom badi implementations for action definition execute badi to send email. Emails are triggering correctly but after PGI creation while replicating the changes from ECC to CRM we are getting an exception in standard code because PPFTTRIGG table does not have entry. We have failed entry in CRM inbound queue and then did some debug and come to know the place of issue. Help me out with some inputs here.
Best Regards,
Dharmakasi.

Hi,
I have identified one thing here, if the action definition does not have start condition system is not updating that entry in PPFTTRIGG table. Here i got 2 questions my mind
1. Why system is not updating the table with all the action definitions available in action profile
2. Why system is looking for the entry which was not updated in PPFTTRIGG table?
I do not understand problem with updating table or with action profile itself. Please give some input here. If we deactivate all the definitions which does not have start condition then there is no error.
Best Regards,
Dharmakasi.

Similar Messages

  • 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

  • How to create post goods issue using sapgui.

    hi,
    can u pls tell how to create pgi for delivery .pls tell  spep by step procedure
    regards
    Guru

    Hi,
    Goto VL02N -> give the delivery number..Then press enter..
    In the resulting screen..There will be a button for called "Post goods issue"..Then press that..The goods issue will be posted automatically..
    Thanks,
    Naren

  • User exit to triger after PGI (Post Goods Issue)..

    Hi,
    Can any one help me on this........... Plz .. Urjent...
    I want to make some operation after PGI and I want to find out the user exit to triger after PGI... I dont know How to find out that exact .. Can any one help me on this ...
    I want the User exit that triger after PGI...
    Regards,
    Raghunath.S

    Hello Sudha,
    Once the PGI ( Post Goods Issues ) over then I want to do some operation .. for that I want to find out the user exit where I can write some logic and process after the PGI...
    Can you help me on this Plzzzzzzzzzzzzz....

  • EDI/ALE output Post Goods Issue from ME2O

    Dear experts,
    I have to create an outbound IDoc (I assume MBGMCR03) of a Goods issue done with ME2O (mvt type 541).
    So far I have read through:
    http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=88113280
    http://scn.sap.com/thread/3146742
    http://scn.sap.com/thread/2056081
    but they all talk about printing the message - I need to create an IDoc.
    In NACE:
    - Application "ME"
    - but which condition record can I choose?
    - output types are all set up with print parameters - no EDI/ALE as far as I can see. Do I have to create new ones?
    Can you please help on how to set this up in NACE?
    Next step would be MN21 for the output condition record I assume,
    WE20 to define output for logical system.
    Thank you for your help.
    Best regards,
    Peter

    Dear experts,
    I am a little further now.
    I used output condition WA01 which is already set up in NACE and in MN23 I set up:
    In SP01 I can see the created Spool entries after creating the Good issue with ME2O. So the print out would work. But I need an EDI output....
    I created a new output condition ZWA1 in NACE and set "Processing routines" to EDI.
    I set "Partner functions" to EDI and LS - logical system.
    In MN23 I have:
    I set Event Type to "WA" because when I look at a material document in MB03 it also shows WA:
    In WE20 I have my LS - logicals system and set up the output for MBGMCR03:
    What confuses me is: I have to send the EDI output to a LS - logical system. But in MN23 I can't set the LS - it gives error: "You cannot enter a partner function for output ZWA1"
    No IDoc is created so far - please help. Thank you.
    Best regarsd,
    Peter

  • Help on IDOC -POST GOODS ISSUE

    Hi Folks,
               I have requirement with me, but I don’t know where to start could you please help me regarding that..
    Here is the scenario....
    Requirement Specification:
    XYZ Company Mexico operations  uses third party systems Foursite) for their inventory process.
    The communication between Foursite and SAP is thru EDI/IDOC.
    In the case of goods customer return to Mexico warehouse, using the following steps the process will be mapped in to SAP.
    Customer calls the account specialist.
    Account specialist creates a ZO order in SAP and conveys a RA to customer.
    Account specialist creates a delivery. The delivery information conveyed to Mexico warehouse thru Inbound receipt IDOC.
    Customer physically returns the goods to Mexico warehouse.
    Mexico warehouse receive the goods with reference to delivery number in Inbound receipt IDOC.
    Once the goods are received, Mexico warehouse send a conformation (Receipt confirmation IDOC) to SAP, which triggers PGI and credit memo.
    Functional Specifications:
    Create POST GOODS ISSUE in SAP for the material and quantity for the delivery mentioned in Receipt conformation EDI.
    Receipt confirmation from Foursite
    Data fields received in the EDI
    Delivery number:LIKP-VBELN
    Material number::LIPS-MATNR
    Quantity:LIPS-LFIMG
    Unit LIPS-MEINS
    Plant :DMEX
    Status  :RS
    Possible IDOC:  SDPICK
    Trigger:
    This IDOC should trigger a Post good issue, for the possible values.
    Transaction: Post good issue.
    Please give ur input /suggestion , What steps I should take to get it complete .
    Thanks in Advance..
    Bye and have a good one .

    Somnath,
    If I understand the right, it is like a integration using EDI formats. Do you have a middleware in place to do the mapping transformation? If yes, the message in EDI format will be recieved by the middleware and will be transformed into IDOC format.
    Then you do the normal settings for an IDOC to be recieved into a SAP system (Partner Profiles, Inbound Messages etc).
    Is this what you were looking for?
    Regards,
    Ravi
    Note : Please reward the posts that help 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

  • Accounting Document not generated after Post goods issue in delivery order.

    Dear Experts
    Greeting of the daays,
    Need your help on below issue.
    After making the post goods issue ,the system is not making the accounting document.
    The error given by the system is as follows:
    Material document 12365 does not include an accounting document
    Diagnosis
    The system cannot find an accounting document for the material document 12365.
    Possible reasons for this are:
    The goods movement has no relevance to accounting. Therefore, the system did not generate an accounting document for the material document.
    The material document is a document that was posted before Release 2.1. Such documents must be converted so that the system can find the relevant accounting document.
    The procedure for the subsequent calculation of value is not active in your system. For further information, refer to the documentation on the program for valuating goods movements: RM07MWBU.
    __Solution what I tried to solve this issue ,but not successful.__
    __Solution 1- maintain OMS2__
    __Solution 2 - maintain OMJJ- movement type 601 - PRCTR is required entry.__
    __Solution 3 - price maintain is material master.__
    __Solution 4 - OBYC - BSX - 7920 - GLA/c  and GBB- VAX and VAY - 7920 GLA/c.__
    __Pls let me know if there is any confirgation is missing.__

    Hi
    Do this checks:
    In tcode OBYC check if you have the proper entries.
    Go to tcode OKB9 and do the settings for the G/L acc. that you have in OBYC.
    To populate PRCTR you can use OKB9 and you can check if you have values in MARC-PRCTR.
    I hope this helps you
    Regards
    Eduardo

  • Special stock partner data problem in ERP system during "Post Goods issue"

    Hi all,
    I have a (probably) customizing issue in an ERP 6.0 EhP4 test system which not occurs in the ERP 6.0 test system. There is a difference but no one could tell me, what causes the problem in this scenario:
    I have two customers, C1 and C2. C2 is the special stock partner (SB) of C1.
    I've created a Consignment Fill-up order, then a delivery document based on the order and posted it with "Post Goods Issue". During the update process, a function module (SD_PARTNER_UPDATE) receives partner data in an internal table which contains the sold-to, ship-to and special partner data.
    When we tried the same process in the ERP 6.0 EhP4 test system then special-partner data did not occur in the parameter table (I've used the same customers and materials). The special stock partner is probably not taken into consideration due to some customizing settings.
    My question is what should I change in the customization to run the process the same way as in the ERP 6.0 system? As far as I know there are no new modifications which have effect on this area, and the used test customers and materials are almost the same - there are no noticable differences.
    Thanks in advance.
    Akos

    I tried setting that field in the sale order this morning.  By defaulting it to "C"; I was able to get warning message for TAE line.  I was able to post goods with TAE and TAQ, being different quantities.  I need the check to determine if TAE and TAQ delivery quantity are different.  Using this fields seems to be line specific.  Thanks for the suggestion.  I now know what that field does to the delivery.
    I rewarded points.
    Thanks,
    Tony

  • Post Goods issue after clicking on Load Starting push button

    Hi All,
    Post goods issue for deliveries, suppose if the shipment document is created for XXXX country do the post goods issue after clicking the push button loading start on. and if the shipment is created other than the XXXX Country do the post goods issue after clicking the shipment start button(Done by Standard SAP).
    There will be validation table in background to identify which shipping point to allow Post Goods Issue before shipment completion. This will require enhancement of Delivery User Exit to incorporate above check based on below mentioned Z Table.
    Z-Table
    - Shipping Point.
    - Delivery Type
    Any body please suggest the user exit or any function module and how to start code for this particular requirement.
    Thanks & Regards,
    Narasimha

    Hi,
    You can write your own vaalidation on click of loading start button.
    Go to include MV56AI_IS_ENHANCEMENT of program SAPMV56A.
    Click on the circular button(Enhance).
    Then Edit --> Enhancement Operation --> Create.
    Create your enhancement giving it a Z name.
    Then in this enhancement you can write your code.
    For loading start you can write your code in the following fashion.
    IF fcode = 'MM_ST03'.
          business logic.....
    ENDIF.
    Regards,
    Firoz.

  • 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

  • Accepted change after post goods issue

    when i made delivery and post goods issue in sap then if any body change the quantity of order in va02 the system accept ?
    how can i change this

    Hi,
    yes..it will accept...but it will show a warning message as per standard.
    Example: " Delivery of 1 EA has already been made for item 10" message no V4096
    if you want to show as an error message try to change the category " W" to "E" in OVAH
    so that it will not allow you to change the order quantity.
    Note: Order quantity will be grayed out after creation of Billing only.
    Hope it helps.
    Thanks,
    Krishna.

  • Post Goods Issue Not creating COPA document

    Hi,
    When I post goods issue, it is generating accounting document, and Profit center document, but no profitability analysis document. I do not have COGS as a cost element. Could this be the issue?
    Thanks,
    Ram

    Hi Siva,
    Thank you. We are using costing based COPA, and COGS is getting posting during billing document creation.
    Another question. Is it required to create COGS as a cost element?
    Thanks,
    Ram
    Message was edited by:
            Ram R

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

  • 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

Maybe you are looking for

  • Photoshop CC keeps asking for me to register and supply my license

    I am a Creative Cloud subscriber, Photoshop/Lightroom only limited edition, and have been for a year or more, running of a Windows 8.1 platform with lots of RAM, etc.  Lately - on occasion - when launching PS, a dialogue will come up with a alternate

  • My podcast artwork is not showing in the iTunes store or in the Podcasts app

    My podcast, the Legal Seagull, was recently posted to iTunes. The problem is that the artwork is not showing in the iTunes store or on the iPhone's Podcasts app. Once you actually download the episodes, the image does appear. I verified that my image

  • Internet sharing in a small coffee house

    I have a friend who has a small coffee house. The place is equiped with a DSL modem and a BEFW11S4 wireless router. Currently the router is wide open and anyone can use the connection. We would like to change things so that the wireless connection ca

  • Japanese Siri is broken

    Just loaded IOS5.1 on iPhone 4s, then switched Siri to Japanese. It recognizes what my Japanese wife says to it (it types out her questions in Japanese, accurately), but then says there is some kind of error (in Japanese, but my wife says it's too te

  • HP 1000 inkjet printer: how to lighten or darken?

    Does the HP 1000 inkjet printer driver allow the user to lighten or darken the image being printed? I have read through the user's guide, and I don't see a way. Thanks for any suggestions.