Subcontracting -Gate Exit

Dear SAP,
Requirement is to have 2 step issue process to the subcontracting
vendor , which should have 1st step issue done at the material store
and 2nd step issue during Gate Exit(when the material is actualy going
out of the premises). so that stock at the vendor location can only be
seen,when the Gate Exit of that material has been compeleted.
Right now the process is followed as follows:-
Step1 : Creation of the Subcontracting PO
Step2 : Transfer Posting of Components from TCode -MB1B ,using Movement
type -541 along with refering the subcontracting PO
Step3 : After this transaction , material can be seen at the
subcontracting Vendor location , irrespective of actual exit of
material from physical location .
Which may cause the data inconsistency , so for avoiding this data
inconsistency,requirement is to follow the 2 -step issue process for
issuing the material to the subcontracting Vendor, basicaly Gate Exit
is required (Extra Transaction at gate),after the Gate Exit only ,
stock can be seen at the subcontracting vendor location.
Thanks & Regards
Nitin Chhabra

Hi,
Still the same problem persists, client wants  stock at subcon vendor location should only be seen when Gate Exit from their location happens, but in the standard scenario , stock keep showing once the Move type 541 happens and on the basis of the material document of the 541 movement subcon chalan got created.
Is it possible on any other document subcon challan can be created and during Gate Exit  541 movment type happens ??? so that stock at Subcon vendor location start existing, only after the gate Exit.
Please suggest as soon as possible.
Thanks & Regards
Nitin Chhabra

Similar Messages

  • Requiremnt from client side for generating a report

    My client has requested to generate a report for gate entry and gate exit in that there are various parameters like mode of conveyance, date, signature ,descriptiion of goods ,quantity etc
    how do i go about this
    pls help me sap gurus
    helpful query will be rewarded with points
    Regards
    AMI

    Hi Ahmed,
    Try to gather the transaction codes that the user uses during gate entry and gate exit and the tables that are updated during the process.
    Your delivery documents and shipments should also play a vital role in preparing the report.
    Customer number, Delivery date, Delivery quantity, Shipping point, Route, Mode of transport etc can be retreived from outbound delivery document (VL02N). Tables - LIKP & LIPS.
    Any other shipment data such as Transit route, Forwarding agent can be taken from table KNVS - Customer Master Shipping Data.
    REWARD POINTS IF HELPFUL
    Regards
    Sai

  • User exit / BADI for updating STO when change in subcontracting PO

    Hi
    The requirement is to update the STO (stock transfer order ) when their any change in subcontracting PO at item level. Is there any exit or BADI available where STO quantity and delivery date will be updated after any change in PO at item level ?
    Thanks
    Manas

    Deepak, Exits for MB1B are
    MBCF0002            Customer function exit: Segment text in material doc. item
    MBCF0005            Material document item for goods receipt/issue slip
    MBCF0006            Customer function for WBS element
    MBCF0007            Customer function exit: Updating a reservation
    MBCF0009            Filling the storage location field
    MBCF0010            Customer exit: Create reservation BAPI_RESERVATION_CREATE1
    MBCF0011            Read from RESB and RKPF for print list in  MB26
    MB_CF001            Customer Function Exit in the Case of Updating a Mat. Doc.

  • Which exit for MIGO Subcontracting

    Dear Abaper,
    We were using MB1B t-code for doing subcontracting with reference to PO. We had used a BADI for that.
    Now, we have upgraded our system to EHP6.
    In EHP6 MB1B is obsolete. And as per SAP we have to use MIGO.
    In MIGO we cannot do subcontracting with reference to PO.
    In the transaction MIGO this PO reference functionality is not implemented for movement type 541.
    There are so many exits available in MIGO,
    please tell me which exit to use to do the subcontracting with Movement type 541 for MIGO Transaction.
    Thanks and Regards,
    Arati. 

    Arati, follow this note, it is exactly what you need:
    1915825 - Transfer Posting reference to a Purchase Order in MIGO
    Resolution
    The business function 'LOG_MM_OM_1' must be activated in your system.
    Also, the BADI MB_MIGO_SC_PO_TRANSFER must be activated into the system and then the option 'A08 Transfer Posting' and 'R01 Purchase Order' appears.
    To activate the business function go to tcode SFW5 and mark the function LOG_MM_OM_1 and click on Activate Changes.
    After that you can go to MIGO and check:
    Regards,
    Felipe

  • Exit/BAdI for removing the component from subcontracting

    Hello Friends,
            My client has a very unusual requirement. For a subcontracting PO, they wish that only the finished product GR should be posted in MIGO and the 543 movement type which is happening for the component, shouldn't take place at the same time. Right now this is automatically happening.
              Is there a BADI or exit where we can control this? It's little urgent. Any small help will be appreciated.
    Thanks & Regards,
    Shaheen

    Hello friends,
            I know my question wasn't so straight. But I found a BAdI, where I could make the quantity of the component zero. But in MIGO, when you check the checkbox 'Item_OK', right at the bottom, it selects both the items. That is the finished product and its component. Is there someway that, only Finished product should be selected?
    Awaiting a miracle!
    Regards,
    Shaheen

  • Calculation for subcontracting item of type N (non stock) as it for type L(Stock)

    Hi Gurus,
    I have a Requirement for calculating the cost for Subcontracting  Non stock items N as it is getting calculated in standard functionality for subcontracting items of Type L.
    This will be done in CK11n ( used to calculate the standard cost estimate of the product) for header as well as component materials.
    please suggest the user exit or Badi where i can change.
    Please refer the below logic-
    BOM for the material 2000500 as Header and 1LPL0835298AB as a component and this component has an assembly with 7008508 as a component and this component is an Sub contracted item and this has an assembly with component 1LBA182151-3.
    Price calculation for the material 7008508 (Item Category as N). Since this is sub contracted item the price will picked from field EINE-NETPR.
    In EINA, pass the material (MATNR=7008508) to fetch the list of info records (INFNR) created for that material.
    Then it has to input those info records to EINE table along with Purchasing organization (EINE-EKORG=PT02).
    From the output of EINE table, it should compare the price (EINE-NETPR) of the PIR and should take the least price from those PIR`s.
    If the currency is other than PLN, then it should be converted to PLN based on conversion charges.
    For Material (MATNR=1LBA182151-3), it should pass the material number to table MBEW along with valuation area (BWKEY = WERKS).
    From the output, it should check the Price control (VPRSV) ‘V’ or ‘S’
    If ‘V’ the price will be picked from the field “VERPR”
    If ‘S’ the price will be picked from the field “STPRS”
    Also from the output, it should check the Price unit (PEINH) ‘1’ or other than ‘1’. If it is other than ‘1’ it should divide the VERPR or STPRS by PEINH. Then this is the price of the Material “1LBA182151-3”.
    The material (MATNR=1LBA182151-3) should be passed to table “MARA” and will take the Base unit of measure from that table “MEINS”.
    Br,
    Surya

    Hi Surya,
    Please put breakpoints in any of the below BADI's and check if any of them will trigger for your
    requirement:
    VALUATION_CK                            BAdI for Valuation in Product Costing
    CK_KALAMATCON2_CI                       BAdI for CI Fields for Table KALAMATCON2
    COSTINGRUN_CK                           Edit Costing Run
    COST_APPORTION_CK                       Maint Apportionment Structure Joint Production: Dist Rules
    CO_PROD_COSTING_CK                      Cost Management for Joint Products (Costing, Target Costs)
    DATA_EXTENSION_CK                       For Data Enrichment in Product Costing
    DYNPRO_EXTENSION_CK                     BAdI for Interface Enhancement in Costing
    ORDER_COSTING_CK                        Enables Header Data Changes in Preliminary Order Costing
    QUANTITY_STRUCT_CK                      Enables Quantity/Structure Changes in Costing
    SUR_STOCK_TRANSF_CK                     Overhead on Materials with Stock Transfer Between Plants
    Thanks
    Sri

  • Error in Gate Entry

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

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

  • Goods receipt for subcontracting order! BAPI_GOODSMVT_CREATE

    I wanna use BAPI "BAPI_GOODSMVT_CREATE"  to create goods receipt for subcontracting order.
    But it says that this combination is not possible.  Combination of my movement type and this BAPI.
    What can i do to solve it?
    thanks in advance.

    >
    Julia Nikiforva wrote:
    > I wanna use BAPI "BAPI_GOODSMVT_CREATE"  to create goods receipt for subcontracting order.
    > But it says that this combination is not possible.  Combination of my movement type and this BAPI.
    >
    > What can i do to solve it?
    >
    > thanks in advance.
    Might work
    report zbapi_goodsmovement.
    parameters: p-file like rlgrap-filename default
    'c:\sapdata\TEST.txt'.
    parameters: e-file like rlgrap-filename default
    'c:\sapdata\gdsmvterror.txt'.
    parameters: xpost like sy-datum default sy-datum.
    data: begin of gmhead.
    include structure bapi2017_gm_head_01.
    data: end of gmhead.
    data: begin of gmcode.
    include structure bapi2017_gm_code.
    data: end of gmcode.
    data: begin of mthead.
    include structure bapi2017_gm_head_ret.
    data: end of mthead.
    data: begin of itab occurs 100.
    include structure bapi2017_gm_item_create.
    data: end of itab.
    data: begin of errmsg occurs 10.
    include structure bapiret2.
    data: end of errmsg.
    data: wmenge like iseg-menge,
    errflag.
    data: begin of pcitab occurs 100,
    ext_doc(10), "External Document Number
    mvt_type(3), "Movement Type
    doc_date(8), "Document Date
    post_date(8), "Posting Date
    plant(4), "Plant
    material(18), "Material Number
    qty(13), "Quantity
    recv_loc(4), "Receiving Location
    issue_loc(4), "Issuing Location
    pur_doc(10), "Purchase Document No
    po_item(3), "Purchase Document Item No
    del_no(10), "Delivery Purchase Order Number
    del_item(3), "Delivery Item
    prod_doc(10), "Production Document No
    scrap_reason(10), "Scrap Reason
    upd_sta(1), "Update Status
    end of pcitab.
    call function 'WS_UPLOAD'
    exporting
    filename = p-file
    filetype = 'DAT'
    IMPORTING
    FILELENGTH =
    tables
    data_tab = pcitab
    EXCEPTIONS
    FILE_OPEN_ERROR = 1
    FILE_READ_ERROR = 2
    NO_BATCH = 3
    GUI_REFUSE_FILETRANSFER = 4
    INVALID_TYPE = 5
    OTHERS = 6
    if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
    with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    exit.
    endif.
    gmhead-pstng_date = sy-datum.
    gmhead-doc_date = sy-datum.
    gmhead-pr_uname = sy-uname.
    gmcode-gm_code = '01'. "01 - MB01 - Goods Receipts for Purchase Order
    loop at pcitab.
    itab-move_type = pcitab-mvt_type.
    itab-mvt_ind = 'B'.
    itab-plant = pcitab-plant.
    itab-material = pcitab-material.
    itab-entry_qnt = pcitab-qty.
    itab-move_stloc = pcitab-recv_loc.
    itab-stge_loc = pcitab-issue_loc.
    itab-po_number = pcitab-pur_doc.
    itab-po_item = pcitab-po_item.
    concatenate pcitab-del_no pcitab-del_item into itab-item_text.
    itab-move_reas = pcitab-scrap_reason.
    append itab.
    endloop.
    loop at itab.
    write:/ itab-material, itab-plant, itab-stge_loc,
    itab-move_type, itab-entry_qnt, itab-entry_uom,
    itab-entry_uom_iso, itab-po_number, itab-po_item,
    pcitab-ext_doc.
    endloop.
    call function 'BAPI_GOODSMVT_CREATE'
    exporting
    goodsmvt_header = gmhead
    goodsmvt_code = gmcode
    TESTRUN = ' '
    IMPORTING
    goodsmvt_headret = mthead
    MATERIALDOCUMENT =
    MATDOCUMENTYEAR =
    tables
    goodsmvt_item = itab
    GOODSMVT_SERIALNUMBER =
    return = errmsg
    clear errflag.
    loop at errmsg.
    if errmsg-type eq 'E'.
    write:/'Error in function', errmsg-message.
    errflag = 'X'.
    else.
    write:/ errmsg-message.
    endif.
    endloop.
    if errflag is initial.
    commit work and wait.
    if sy-subrc ne 0.
    write:/ 'Error in updating'.
    exit.
    else.
    write:/ mthead-mat_doc, mthead-doc_year.
    perform upd_sta.
    endif.
    endif.
    FORM UPD_STA *
    form upd_sta.
    loop at pcitab.
    pcitab-upd_sta = 'X'.
    modify pcitab.
    endloop.
    call function 'WS_DOWNLOAD'
    exporting
    filename = p-file
    filetype = 'DAT'
    IMPORTING
    FILELENGTH =
    tables
    data_tab = pcitab
    EXCEPTIONS
    FILE_OPEN_ERROR = 1
    FILE_READ_ERROR = 2
    NO_BATCH = 3
    GUI_REFUSE_FILETRANSFER = 4
    INVALID_TYPE = 5
    OTHERS = 6
    endform.

  • EKET-FIXKZ set after partial goods receipt of subcontract delivery schedule

    Dear all,
    when booking a partial goods receipt (via MIGO) of the finished product of a subcontract delivery schedule the schedule line becomes fixed (EKET-FIXKZ = 'X'), which hinders the next MRP run to modify the delivery schedule according to the new requirements.
    I have tested to change the fixing indicator via SE16 and the next MRP run will then replan the sub contract delivery schedule correctly. But this is no solution.
    Is there a way to modify this setting via an EXIT or BADI in MIGO ?
    Many thanky for your help
    Rabanus Diehl

    Dear all,
    when booking a partial goods receipt (via MIGO) of the finished product of a subcontract delivery schedule the schedule line becomes fixed (EKET-FIXKZ = 'X'), which hinders the next MRP run to modify the delivery schedule according to the new requirements.
    I have tested to change the fixing indicator via SE16 and the next MRP run will then replan the sub contract delivery schedule correctly. But this is no solution.
    Is there a way to modify this setting via an EXIT or BADI in MIGO ?
    Many thanky for your help
    Rabanus Diehl

  • User Exit or Badi for VL01N (before the delivery will be displayed)

    Hello Togheter:
    I have to change the sort order of the delivery items in VL01N before they will be displayed (not at the moment when they'll be stored on the database). Does anybody know any enhancement or user exit or BADI that i can use for this? I've tried with BADI LE_SHP_DELIVERY_PROC, but there is no methode which I can use for reordering the table XLIPS/LIPS before the delivery will be displayed.
    Thanks in advance
    Klaus

    Exits for VL01N ::::::
    V02V0001            Sales area determination for stock transport order                     
    V02V0002            User exit for storage location determination                           
    V02V0003            User exit for gate + matl staging area determination (headr)           
    V02V0004            User Exit for Staging Area Determination (Item)                        
    V50PSTAT            Delivery: Item Status Calculation                                      
    V50Q0001            Delivery Monitor: User Exits for Filling Display Fields                
    V50R0001            Collective processing for delivery creation                            
    V50R0002            Collective processing for delivery creation                            
    V50R0004            Calculation of Stock for POs for Shipping Due Date List                
    V50S0001            User Exits for Delivery Processing                                     
    V53C0001            Rough workload calculation in time per item                            
    V53C0002            W&S: RWE enhancement - shipping material type/time slot                
    V53W0001            User exits for creating picking waves                                  
    VMDE0001            Shipping Interface: Error Handling - Inbound IDoc                      
    VMDE0002            Shipping Interface: Message PICKSD (Picking, Outbound)                 
    VMDE0003            Shipping Interface: Message SDPICK (Picking, Inbound)                  
    VMDE0004            Shipping Interface: Message SDPACK (Packing, Inbound)                  
    Hope they may help a little.
    Regards,
    Jignesh

  • Badi & User Exit for ME21N & ME22N

    Hi,
            My requirement is when a Purchase order is created using ME21n or when a line is added or changed using ME22n, the system should copy the vendors tax jurisdiction to the purchase order line items jurisdiction code. I tried badi (ME_PROCESS_PO_CUST) but could not suceed. Can any one tell me if any badi or user exit available for the same???
    Thanks in Advance.

    hi,
    Enhancement/ Business Add-in            Description
    Enhancement
    MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
    MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
    MM06E001                                User exits for EDI inbound and outbound purchasing documents
    MM06E003                                Number range and document number
    MM06E004                                Control import data screens in purchase order
    MM06E005                                Customer fields in purchasing document
    MM06E007                                Change document for requisitions upon conversion into PO
    MM06E008                                Monitoring of contr. target value in case of release orders
    MM06E009                                Relevant texts for "Texts exist" indicator
    MM06E010                                Field selection for vendor address
    MMAL0001                                ALE source list distribution: Outbound processing
    MMAL0002                                ALE source list distribution: Inbound processing
    MMAL0003                                ALE purcasing info record distribution: Outbound processing
    MMAL0004                                ALE purchasing info record distribution: Inbound processing
    MMDA0001                                Default delivery addresses
    MMFAB001                                User exit for generation of release order
    MRFLB001                                Control Items for Contract Release Order
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    AMPL0001                                User subscreen for additional data on AMPL
    LMEDR001                                Enhancements to print program
    LMELA002                                Adopt batch no. from shipping notification when posting a GR
    LMELA010                                Inbound shipping notification: Transfer item data from IDOC
    LMEQR001                                User exit for source determination
    LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001                                Customer-Specific Source Determination in Retail
    M06B0001                                Role determination for purchase requisition release
    M06B0002                                Changes to comm. structure for purchase requisition release
    MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
    MEETA001                                Define schedule line type (backlog, immed. req., preview)
    ME590001                                Grouping of requsitions for PO split in ME59
    M06E0005                                Role determination for release of purchasing documents
    M06E0004                                Changes to communication structure for release purch. doc.
    M06B0005                                Changes to comm. structure for overall release of requisn.
    M06B0004                                Number range and document number
    M06B0003                                Number range and document number
    Business Add-in
    ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
    ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
    ME_PO_PRICING                           Enhancements to Price Determination: Internal
    ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
    ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
    ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
    SMOD_MRFLB001                           Control Items for Contract Release Order
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
    ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
    ME_REQ_POSTED                           Purchase Requisition Posted
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_PURCHDOC_POSTED                      Purchasing Document Posted
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
    ME_BSART_DET                            Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN                    Commitment for return item
    ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
    ME_CHECK_OA                             Check BAdI for Contracts
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
    No.of Exits:         35
    No.of BADis:         55
    Arunima

  • EXIT or BADI for Post Goods Issue

    Hello Experts,
    I need help in finding a USER EXIT, or BADI to change the contents of MSEG at PGI moment in VL02N.
    I'm using version 4.6c.
    When I click at Post Goods Issue, I need to insert the customer number at MSEG for certain documents that the standard does not use this field.
    Can anyone PLEASE help?
    Will reward points!
    Thanks a lot and regards,
    Fernanda

    Hi
    Enhancement/ Business Add-in            Description                                                                               
    Enhancement                                                                               
    V02V0004                               
    User Exit for Staging Area Determination (Item)                
    V02V0003                              
    User exit for gate + artl 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              
    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                                                                               
    Business Add-in                                                                               
    DELIVERY_PUBLISH                      
    Announcement of delivery data during database update           
    If it is  helpful rewards points
    Regards
    Pratap.M

  • Exit for changing Components in ME21N based on the production Order

    Hi,
          I have a scenerio in which, while creating PO in ME21N for subcontracting(Item category 'L') against a PR, the components for the material should come with my own logic i.e. it will have its production order number, with this production number i will get material of production order. Now i will get the BOM of this material and want to fill the next screen with the same BOM components. So please can anybody help me out how to work out for this problem. I looked for user exit and BADI but was not able to find anything, or is there some other way to do it. Help will be highly appreciated.
    Thanks and regards,
    Pankaj

    Hi,
                 Anybody having any idea. Plz help with your ideas if it is possible to do or not.
    regards,
    Pankaj

  • User exit/BADI for Return PO item delivery Address

    Hi Guyz,
    We have a requirement where in when a PO item is marked as return PO item(In ME21n/ME22n/ME23n We have check box at item level) and click on enter/Check/Save, In delivery address of item details we have to populate Vendor address. By default SAP populates Plant address. If we manually give Vendor number in item details=>Delivery address tab then it populates vendor address. We want to automate this functionality.
    Is there any Exit/BADI which serve this purpose.
    Note: We need this functionality for few doc types(i.e PO doc type should also be available in the exit).
    Any ideas could be really helpfull.
    Thanks,
    Vinod.

    Hi,
    there are some user-exit & enhancements....
    MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
    MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
    MM06E001                                User exits for EDI inbound and outbound purchasing documents
    MM06E003                                Number range and document number
    MM06E004                                Control import data screens in purchase order
    MM06E005                                Customer fields in purchasing document
    MM06E007                                Change document for requisitions upon conversion into PO
    MM06E008                                Monitoring of contr. target value in case of release orders
    MM06E009                                Relevant texts for "Texts exist" indicator
    MM06E010                                Field selection for vendor address
    MMAL0001                                ALE source list distribution: Outbound processing
    MMAL0002                                ALE source list distribution: Inbound processing
    MMAL0003                                ALE purcasing info record distribution: Outbound processing
    MMAL0004                                ALE purchasing info record distribution: Inbound processing
    MMDA0001                                Default delivery addresses
    MMFAB001                                User exit for generation of release order
    MRFLB001                                Control Items for Contract Release Order
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    AMPL0001                                User subscreen for additional data on AMPL
    LMEDR001                                Enhancements to print program
    LMELA002                                Adopt batch no. from shipping notification when posting a GR
    LMELA010                                Inbound shipping notification: Transfer item data from IDOC
    LMEQR001                                User exit for source determination
    LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001                                Customer-Specific Source Determination in Retail
    M06B0001                                Role determination for purchase requisition release
    M06B0002                                Changes to comm. structure for purchase requisition release
    MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
    MEETA001                                Define schedule line type (backlog, immed. req., preview)
    ME590001                                Grouping of requsitions for PO split in ME59
    M06E0005                                Role determination for release of purchasing documents
    M06E0004                                Changes to communication structure for release purch. doc.
    M06B0005                                Changes to comm. structure for overall release of requisn.
    M06B0004                                Number range and document number
    M06B0003                                Number range and document number
    Some BADI s:
    ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
    ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
    ME_PO_PRICING                           Enhancements to Price Determination: Internal
    ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
    ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
    ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
    SMOD_MRFLB001                           Control Items for Contract Release Order
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
    ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
    ME_REQ_POSTED                           Purchase Requisition Posted
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_PURCHDOC_POSTED                      Purchasing Document Posted
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
    ME_BSART_DET                            Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN                    Commitment for return item
    ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
    ME_CHECK_OA                             Check BAdI for Contracts
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
    No.of Exits:         35
    No.of BADis:         55
    Arunima

  • PR to PO conversion in operation subcontracting

    Dear friends,
    We are trying this scenario of operation subcontracting.
    I have a semi - finish material SM01 on which i m carrying 5 operations. The 20th operation is sub contracting. I do not want to maintain a separate material for this operation.  I have done all the necessary settings which are required. I m also getting a PR when a Production order is generated for operation 20.
    Now the problem is when i go to convert this PR to PO in ME58 the system gives me an error, "Not possible to determine any components".
    I do not understand where i have gone wrong.
    The PR document type that is created is NB.
    The PO does not take any material even if I try to maintain one.
    What can be the possible solution.
    Thanking all you for your kind assistance.

    Hi pankaj
    The concept is like that. You need to send a material out with gate pass to the vendor for that particular P.O.
    You might have issued the material from stock for the previous operation so that you will not have a component for that operation. There may be two options.
    Options 1) Create a dummy material with MRP type ND so that the planning will not happen and no plan order. keep stock through a movement type update. Allocate this component to the operation in your routing. If the external operations is pre defined.
    Option 2 )  Create a dummy material with MRP type ND so that the planning will not happen and no plan order. keep stock through a movement type update. Include this component in P.O while converting from PR. If the external operations is not pre  defined.
    The component will now appear in ME 2O
    Hope this is clear
    Regards
    J . Saravan

Maybe you are looking for