Automatic TO creation with WMTA during delivery

Hello,
We are creating TO for ZLF delivery with WMTA output type during the creation of delivery. But after WMTA output type is competed, we are trying to display the Transfer Order information with smartform using the ZMTA output type by triggering it automatically. The problem here is, for the corresponding delivery, the TO number is getting in database table LTAK when the ZMTA gets triggered. Could you please let me know when the TO number will be updated in database table, or how to get the TO number, When does the above values commits to the database table.

Hello,
LTAK and LTAP are the two TO header and item table respectively. This two table gets updated once your TO is created.
Regards,
Kishore

Similar Messages

  • Automatic Po creation With MB01 i am getting Error

    Hi ,
    While doing goods receipt for  Automatic Po creation i am getting error
    MM activated Automatic Po
    VM activated Automatic Po
    101 Mov Type is also activated
    Item 00010 of purchasing document 9999999999 does not exist
    Message no. ME706
    Diagnosis
    Purchase order 00010 with item 9999999999 was not found.
    Procedure
    Enter a different purchase order.
    i given  the Vendor and quantity  after entering error is coming
    Please help
    Manjunath

    HI,
    Pls ceck the points mentioned below.
    Define one of the purchase organizations as Standard Purchase Organization
    Assign your plant to Standard Purchase Organization
    Maintain purchasing information record with price
    Maintain the indicator for movement types 101 & 161
    Define Default Values (MB01) for Document Type
    Now you can enter a goods receipt without entering the purchase order number, a purchase order will be created automatically when you post the goods receipt. All such goods receipt will be valuated at the price maintained in the purchasing information record.
    First you can try this with T. Code MB01 if it is working then try with T. Code MIGO, if you face any error or functionality is not working check with your basis consultant some authorization or some patches may be missing. Ask him to apply all relevant patches.
    Thanks
    Chandru

  • Automatic tag creation with WMP

    A friend of mine told me that WMP 0 can automatically tag your files but I can't get it to work here. Okay he said that I could structure my folders like so:
    artist
    album
    album
    album
    and when i sync the parent folder to my player it would assign that folder name to the artist tag
    then it would assign the 3 album tags to the files contained within each.
    is this how it behaves. if so how do i get it to work this way?

    HI,
    Pls ceck the points mentioned below.
    Define one of the purchase organizations as Standard Purchase Organization
    Assign your plant to Standard Purchase Organization
    Maintain purchasing information record with price
    Maintain the indicator for movement types 101 & 161
    Define Default Values (MB01) for Document Type
    Now you can enter a goods receipt without entering the purchase order number, a purchase order will be created automatically when you post the goods receipt. All such goods receipt will be valuated at the price maintained in the purchasing information record.
    First you can try this with T. Code MB01 if it is working then try with T. Code MIGO, if you face any error or functionality is not working check with your basis consultant some authorization or some patches may be missing. Ask him to apply all relevant patches.
    Thanks
    Chandru

  • Automate BOM creation with script

    Hi all
    I'like to create an Excel macro that would upload a BOM for a specific equipment using SAP Script.
    where i'm struggling right now is on determining the first available position in the ib02 tab
    in the example the first line available for insertion of a new item would be the 53 one.
    When i ran the script recorder i get the following code
    session.findById("wnd[0]/tbar[0]/okcd").text = "/nib02"
    session.findById("wnd[0]").sendVKey 0
    session.findById("wnd[0]").sendVKey 0
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 7
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 14
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 21
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 28
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 35
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 42
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 49
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 56
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 63
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 70
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 76
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 69
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 62
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 61
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 60
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 59
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 58
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 57
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 56
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 55
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 54
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT").verticalScrollbar.position = 53
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT/ctxtRC29P-POSTP[1,2]").setFocus
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT/ctxtRC29P-POSTP[1,2]").caretPosition = 0
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT/ctxtRC29P-POSTP[1,2]").text = "I"
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT/ctxtRC29P-IDNRK[2,2]").text = "TEST_1117"
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT/ctxtRC29P-IDNRK[2,2]").setFocus
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT/ctxtRC29P-IDNRK[2,2]").caretPosition = 9
    session.findById("wnd[0]").sendVKey 0
    session.findById("wnd[0]/usr/subPOS_PHPT:SAPLCSDI:0830/txtRC29P-MENGE").text = "1"
    session.findById("wnd[0]/usr/subPOS_PHPT:SAPLCSDI:0830/txtRC29P-MENGE").caretPosition = 1
    session.findById("wnd[0]").sendVKey 0
    session.findById("wnd[0]/tbar[0]/btn[11]").press
    thanks a lot for your input

    Hi Umur
    Thanks for the tip.
    this is working very well.
    another option is to check is one of the field is empty.
    If no then increment a counter
    if yes then you have reach the first available line and you can use the counter to identify it in the script
    here is an example :
    k = 0
    While session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT/ctxtRC29P-POSTP[1," & CStr(k) & "]").Text <> ""
    k = k + 1
    Wend
    session.findById("wnd[0]/usr/tabsTS_ITOV/tabpTCMA/ssubSUBPAGE:SAPLCSDI:0152/tblSAPLCSDITCMAT/ctxtRC29P-POSTP[1," & CStr(k) & "]").Text = item_type

  • BAPI for automatic Pr creation witth multiple files from excel sheet

    I have written a programm  for automatic PR creation  with the help of bapi , where its picks data from excel sheet and makes PR .It is picking excel files from one folder(Files) for PR creation and moving to another folder(Files sucess).
    now the problem is if Folder (Files) contains one excel sheet ,PR is created fine , but if the Folder(Files) have multiple excel sheet ,its is creating 1st PR right, but next PR's contains all the line item of 1st PR , 2nd PR and so on .can anyone suggest me where is the problem in codes.
    types : begin of x_file ,
            key1(10),
            pur_grp(4),
            maktx(40),
            plant(4) ,
            req(10),
            s_qty(13),
            wbs(24),
            gl(10),
            trackno(10),
            supl(4),
            deladd(255).
    types : end of x_file .
      data : str5 type char10.
      data : mm type char2.
      data : yyyy type char4.
      data : dd type char2.
      data : str9 type char10.
      data : str6 type char10.
      data : month type char2.
      data : year type char4.
      year = sy-datum+0(4).
      month = sy-datum+4(2).
      dd = sy-datum+6(2).
      yyyy = sy-datum+0(4).
      mm = sy-datum+4(2).
      dd = sy-datum+6(2).
      clear str6 .
      clear str5.
      concatenate  dd'.' month '.' year into str5 .
      concatenate  yyyy mm dd into str6 .
    DATA : file type rlgrap-filename .
    data : it_file type table of x_file .
    data : wa_file type x_file .
    data : it_header type table of x_file .
    data : wa_header type x_file .
    *&  Internal Table For Define Row and Coloum Postion
    data: col_start type i value 1 ,
          row_start type i value 2,
          col_end type i value 256 ,
          row_end type i value 65000 .
    *&  Internal Table For Retrieve  Data From Excel
    *data: excel_bdcdata like kcde_cells occurs 0 with header line.
    *data: excel_bdcdata1 like kcde_cells occurs 0 with header line.
    data: excel_bdcdata like ALSMEX_TABLINE occurs 0 with header line.
    data: excel_bdcdata1 like ALSMEX_TABLINE occurs 0 with header line.
    data: it_index type i.
    DATA : IT_INDEX1 TYPE I.
    *&  Define Field Symbol
    field-symbols: <fs> .
    data :   bdcdata like bdcdata    occurs 0 with header line.
    data :   messtab like bdcmsgcoll occurs 0 with header line.
    data : req_items type table of bapiebanc .
    data : wa_req_items type bapiebanc .
    data : req_acc_asg type table of bapiebkn.
    data : wa_req_acc_asg type bapiebkn.
    DATA : RETURN LIKE BAPIRETURN OCCURS 0 WITH HEADER LINE .
    *data : return type table of     bapireturn.
    *data : wa_return type bapireturn .
    data : number type ebeln .
    *****************************MOVE FILES******************************
    data : xsource type string .
    data : xdestin type string .
    data : destin1 type string .
    data : destin2 type string .
    DATA : DEST1 TYPE STRING.
    DATA : DEST11 TYPE STRING.
    DATA : DEST2 TYPE STRING.
    DATA : DEST22 TYPE STRING.
    data : sou_dir_name like SALFILE-LONGNAME.
    data : tar_dir_name like SALFILE-LONGNAME.
    data : tar_dir_name1 like SALFILE-LONGNAME.
    data : sou_filename like EDI_PATH-PTHNAM .
    data : tar_filename like EDI_PATH-PTHNAM .
    data : filename1  type string .
    data : tar_filename1 like EDI_PATH-PTHNAM .
    data : file_itab like SALFLDIR occurs 0 with header line.
    data : wa_file_itab like SALFLDIR.
    data : file_count type i .
    data : dir_count type i.
    data : dir_table like sdokpath occurs 0 with header line.
    data : file_table like SDOKPATH occurs 0 with header line.
    data : wa_file_table like sdokpath.
    data : strr type string ,
           str1 type string ,
           str2 type string ,
           str3 type string .
    DATA : PA_VAL TYPE CHAR1.
    sou_dir_name = 'D:\barcodes\files\'.
    tar_dir_name = 'D:\barcodes\files-success\'.
        "success folder.
    CALL FUNCTION 'TMP_GUI_DIRECTORY_LIST_FILES'
      EXPORTING
        DIRECTORY  = sou_dir_name
        FILTER     = '.'
      IMPORTING
        FILE_COUNT = file_count
        DIR_COUNT  = dir_count
      TABLES
        FILE_TABLE = file_table
        DIR_TABLE  = dir_table
      EXCEPTIONS
        CNTL_ERROR = 1
        OTHERS     = 2.
    IF SY-SUBRC <> 0.
    ENDIF.
    loop at file_table into wa_file_table.
    clear  :  strr , str1 , str2 , str3 .
      strr = wa_file_table-PATHNAME .
      concatenate sou_dir_name strr into str1 .
      concatenate tar_dir_name strr into str2 . " success
      concatenate tar_dir_name1 strr into str3 .         " failed
    FILE = STR1 .
    *start-of-selection.
    *&  Function For Retrieve Data From Excel
    CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
      EXPORTING
        filename                      = FILE
        i_begin_col                   = col_start
        i_begin_row                   = row_start
        i_end_col                     = col_end
        i_end_row                     = row_end
      tables
        intern                        = excel_bdcdata
    EXCEPTIONS
       INCONSISTENT_PARAMETERS       = 1
       UPLOAD_OLE                    = 2
       OTHERS                        = 3.
      IF sy-subrc NE 0.
    WRITE : / 'File Error'.
    EXIT.
    ENDIF.
      loop at excel_bdcdata.
        translate excel_bdcdata to upper case .
        move excel_bdcdata-col to it_index.
        assign component it_index of  structure  wa_file to <fs> .
        move excel_bdcdata-value to <fs>.
        at end of row.
          append wa_file to it_file .
            clear wa_file.
        endat.
      endloop.
    sort it_file by key1. "pur_grp maktx plant  .
    it_header[] = it_file[].
    delete adjacent duplicates from it_header comparing key1 pur_grp maktx
    plant .
    data : h_item(5) type n .
    data : h_pack(10) type n .
    data : line_no(5) type n .
    data : ln_no(5) type n .
    loop at it_header into wa_header .
    ln_no = 1.
    h_item = h_item + 10.
    h_pack = h_pack + 1.
    wa_req_items-preq_item = h_item .
    wa_req_items-doc_type = 'BOM'.
    wa_req_items-pur_group = wa_header-pur_grp .
    wa_req_items-MATERIAL = wa_header-maktx .
    wa_req_items-plant = wa_header-plant .
    wa_req_items-pckg_no =  h_pack .
    wa_req_items-deliv_date = str6 .
    wa_req_items-item_cat = '0'.
    wa_req_items-acctasscat = 'P'.
    *wa_req_items-distrib = '2' .
    **wa_req_items-gr_ind = 'X'.
    wa_req_items-ir_ind = '2'.
    wa_req_items-purch_org = 'TISL' .
    wa_req_items-QUANTITY =  wa_header-s_qty.
    wa_req_items-PREQ_NAME =  wa_header-req.
    wa_req_items-SUPPL_PLNT = wa_header-supl.
    wa_req_items-trackingno = wa_header-trackno.
    append wa_req_items to req_items .
    clear wa_req_items.
    wa_req_acc_asg-preq_item = h_item .
    wa_req_acc_asg-g_l_acct = wa_file-gl .
    WA_req_acc_asg-wbs_elem  = wa_header-wbs .
    append wa_req_acc_asg to req_acc_asg .
    clear wa_req_acc_asg.
    h_pack = h_pack + 1  .
    endloop.
    clear ln_no .
    ***BREAK-POINT.
    *& BAPI FUNCTION
    call function 'BAPI_REQUISITION_CREATE'
    importing
       number                               = number
      tables
        requisition_items                   = req_items
       requisition_account_assignment       = req_acc_asg
       return                               = return .

    Can someone please give me sol........

  • Automating Goods issue during Delivery creation

    Hi all,
    We have a requirement to automate the Goods issue creation for certain type of orders when the Delivery is getting created. The orders that need to be automatically Goods issued during delivery creation are identified based on certain plants. These plants are linked to certain output type and in the output type routine is the standard program RVADEK01 with one additonal code for automating the Goods Issue creation.
    We have a custom table that holds the status of orders and there is a code in user exit userexit_save_document_prepare which changes the status of the order as closed when the goods issue is done.
    But when the delivery is saved, in this case when an automatic goods issue needs to happen, when the flow reaches this user exit, the output type code dosenot get executed and the Goods issue is not done and so the custom table will not be updated with the closed status. So we are in need to findout a place where we can update the status of the order in that table.
    The output type code is not executed even before the other user exit userexit_save_document. The output type code gets executed and goods issue is done after the this userexit_save_document when the COMMIT statement is executed in the subroutine BELEG_SICHEN_POST in the include FV50XF0B_BELEG_SICHERN.
    I need help in finding out if any user exit or badi is called after this commit statement, so that I can add my code to close the status of the order in my custom table. Just after this commit the Goods issue happens and the VBFA table gets updated with the 'R' records for goods issue.
    Please let me know if anyone has any idea on this. The ultimate goal is to find some place after the goods issue is done to update the status of the order as closed in the custom table we have.
    Thanks,
    Packia

    Dear Siva,
    As informed yesterday I changed the language from DE to EN, to match the other shipping points settings in table V_TVST, this did not bring the solution.
    Please let me summarize, I am really desparate here:
    This is only IM related, Not WM.
    Picking lists are not printed for any Shipping Point from this warehouse, this is just a small subsidiary of my customer in Finland.
    Issue is not Aut. PGI.
    VP01SHP has not been configured for any shipping points, still there we do get the PR except for the new shipping point.
    In the deliveries of correct processed shipping points  I do not find any picking output type.
    Item category in new shipping is equal to Item category in already existing shipping points, so no need to config here.
    There is no picking block active.
    PR creation happens once I enter the pick qty in the delivery in VL02N. This is the part that we need to have automated.
    Can you please try to help me out?
    Tnx & regards,
    Chris

  • Help needed in Automatic Batch determination during Delivery

    Hello gurus..
    Can anyone point me in the right direction. I am trying to trigger auto batch determination during delivery creation based on available batches. thank you
    If any can give me the config that goes with it, that'll be great

    Steps to configure Batch Management
    1)  Specify Batch Level
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Specify batch level and activate batch status management Transaction  OMCT
    2)  Batch Number - Activate Internal Number Assignment
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Batch Number Assignment --> Activate internal batch number assignment Transaction  OMCZ
    3)  Batch Creation - for Goods Movements 
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Creation of new batches --> Define batch creation for goods movements
    4) Characteristic Value Assignment -- Update Standard Characteristics 
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Characteristic Value Assignment --> Update Standard Characteristics
    5) Activate Batch Classification for Goods Movements in Inventory Management 
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Characteristic Value Assignment --> Valuation for goods movements --> Activate Batch Classification for goods movements in Inventory Management Transaction  OMCV
    6) Batch Determination – Condition Table(Cross Client)
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Batch Determination & Batch Check --> Condition Tables --> Define production order condition tables Transaction  OPLB
    7)  Batch Determination – Condition Table(Cross Client)
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Batch Determination & Batch Check --> Condition Tables --> Define SD condition Tables Transaction  V/C7
    8) Batch Determination – Access Sequence(Cross Client)
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Batch Determination & Batch Check --> Access Sequences --> Define Production Order Access Sequences Transaction  OPLF
    9) Batch Determination – Access Sequence(Cross Client)
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Batch Determination & Batch Check --> Access Sequences --> Define SD Access Sequences Transaction  V/C2
    10) Batch Determination – Strategy Types
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Batch Determination & Batch Check --> Define Production Order Strategy Types Transaction  OPLE
    11) Batch Determination – Strategy Types
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Batch Determination & Batch Check --> Define SD Strategy Types Transaction  V/C1
    12) Batch Determination – Batch Search Procedure
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Batch Determination & Batch Check --> Define IM   Search Procedure Transaction  OMCY
    13) Batch Determination – Batch Search Procedure
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Batch Determination & Batch Check --> Define Production order Search Procedure Transaction  OPLG
    14) Batch Determination – Batch Search Procedure
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Batch Determination & Batch Check --> Define SD Search Procedure Transaction  V/C3
    15) Batch Determination – Batch Search Procedure Allocation
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Batch Determination & Batch Check --> Allocate IM search procedure/activate check Transaction  OMCG
    16) Batch Determination – Batch Search Procedure Allocation
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Batch Determination & Batch Check --> Assign Search procedure to production order Transaction  OPL8
    17) Batch Determination – Batch Search Procedure Allocation(SD)
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Batch Determination & Batch Check --> Allocate SD Search procedure Transaction  V/C5
    18) Batch Determination – Activate Automatic Batch Determination(SD)
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Batch Determination & Batch Check --> Activate Automatic Batch Determination in SD -->For delivery item categories Transaction  V/CL
    19) Batch Determination – Batch Selection Class
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Batch Determination & Batch Check --> Define Selection Classes Transaction  CL01
    20) Batch Determination – Sort Rule
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Batch Determination & Batch Check --> Define Sort Rules Transaction  CU70
    21) Batch Determination – Make Settings for Batch Where-used list
    Menu Path  Enterprise Structure> Logistics General> Batch Management --> Make Settings for Batch Where-used list Transaction  OMBB
    thanks
    G. Lakshmipathi

  • Error during automatic po creation ME59N

    Dear All,
    Following errors has been shown after automatic po creation by ME59N:-
    Message text Message Class Message Number
    PO could not be created
    PO header data still faulty MEPO 2
    Enter Validity End ME 83
    Enter Latest GR Date ME 83
    Can delivery date be met? ME 40
    Requisition could not be converted
    Please suggest how to solve above .
    with regards,
    Pradeep Bhardwaj

    Hi
    From the messages it seems that system is expecting a Validity end date at PO header & Latest GR date at item level.
    Do you have these two fields as required in the PO??
    If these are required fields then you need to have process to populate them automatically (Programatically) to resolve the error.
    Thanx
    Prasad

  • Error  during automatic PO creation by PR (ME59N)

    Dear All,
    Following errors has been shown after automatic po creation by ME59N:-
    Message text     Message Class  Message Number
    PO could not be created                   
    PO header data still faulty        MEPO               2
    Enter Validity End        ME              83
    Enter Latest GR Date        ME              83
    Can delivery date be met?        ME              40
    Requisition could not be converted     
    Please suggest how to solve above .
    with regards,
    Pradeep Bhardwaj

    Hello,
      to check the errors issued I suggest to try to create the PO converting the PR from transaction ME21N.
    I guess that some fields, mandatory for the PO creation, were not filled in the Purchase Request and could not be determined in any different way. If you can't maintain them on the PR you should set them as optional, if possible, in the customizing for Screen lay-out of transaction ME59N, under "Materials Management --> Purchasing --> Purchase Order --> Define Screen Layout at Document Level".
    Hope to be useful.
    Best regards,
    Andrea

  • Automatic TO creation for delivery

    Dear Experts ,
    We are facing a problem with Automatic TO creation for delivery only in some storage types ( not all the types , some types are working fine )
    The problem happened after we applied a user exit for a specific picking strategy , but even after we have cancelled that user exit still problem remained.
    We have checked the following settings, and everything seems fine:
    1-Warehouse management - Activities u2013 transfers u2013 define Mvt type
    2-Warehouse management u2013 interfaces- Automatic TO creation
    Looking for your help in this issue
    Thanks ,
    Malik

    Hi Malik,
    You mentioned that you have previously implemented the picking user-exit and removed it later. Did you enter the correct picking strategy for the effected storage types after removing the user-exit? This could be one reason.
    What happens when you try to create the TO manually?
    Regards,
    Osman

  • Automatic creation of po during goods receipt

    Dear all,
    po has not been created, but while receiving the material i want automatic generation of po. i have some knowledge about it but it is not working. Can some one send detailed information. with navigation details. Tips that are posted on the sdn is not working.
    Regards

    Hi
    Pl Make sure you have done following settings for the Automatic Creation of PO during GR:
    1) In SPRO ---> Enterprise Structure ---> Assignment -
    >  Material Management ---> Assign Std. Purchase Org. to your Plant...
    2) In Material Master -
    > Purchasing View -
    > Pl. Check. Automatic PO check Box   and  Maintain Purchasing Group....
    3)Create your Vendor for oyur Company Code and  Std. Pur. Org. combination and in that Vendor Master -> Purchasing Data View--- > Pl. Check Auto. PO Check Box...
    4)For your Vendor -Material Master - Plant -Std. Pur. Org combination Maintain valid Info record...
    5)In OLMB --->  Goods Receipt -
    > Automatic Creation of PO ---> for the M.Type:101  pl. check  Auto PO check Box
    6) In OLMB ---> Movement types ---> Copy,Delete, Check M.Types ---> Choose the M.Type:101   and go into Details -
    > Then goto  allowed Fields for M.Types for M.Type:101 --->  there for the M.Type:101   make the field   LIFNR as a Mandatoty field...
    If you have done the above settings properly...then  in  MIGO ---> Choose Transaction GR  and referance as Others
      and do the GR....Make sure you are doing GR with M.Type:101....and yougive the Vendor's name during   GR....
    Now If you save the GR ...automatically PO will be created...
    this you can see it by displaying the MIGO Document..
    Reward if useful
    Regards
    S.baskaran

  • Serial Number validation during Delivery Creation itself(PGI-system checks)

    Process:
    Sales Order PR(Purchase Order) GR( New Serial Numbers are created automatically or manually keyed in)
    Once the Goods Receipt is received, we do the (SO) DELIVERYu2014SERIAL NUMBER ASSIGNMENT Post Goods Issue
    Issue:
    Current Serial Number Profile Management does not do a valid serial number check during DELIVERY CREATION where we do a SERIAL NUMBER ASSIGNMENT.
    Only during POST GOODS ISSUE, the check happens for valid serial numbers; this is too late in the game for business as there is a time lag of 3 days from the DELIVERY CREATION and PGI.
    Reason being--- We donu2019t check the following u201C Existing Stock Checku201D( which does a serial number validation during delivery creation as well)
    SPRO>Plant Maintenance and Customer Service>Master Data in Plant Maintenance and Customer Service>Technical Objects>Serial Number Management>Define Serial Number Profiles
    If we check this option, the business requirement to do a valid serial number check does happen during delivery creation, however we cannot create new serial numbers during Purchase Order- GOODS RECEIPT.
    QUESTION:
    Can we have the system check the valid serial numbers from stock during delivery creation and serial number assignment.
    And Also create new serial numbers during Purchase Order- Goods Receipt.

    Hi
    1.In std SAP its not possible to check the serail number during Delivery creation, through enhancement it can be done.
    2.During GR for PO serial numbers can be created.
    Rgds
    Ramesh

  • Hard Check During Delivery Creation

    Hello Experts,
    Need your advice. I am stuck up in a enhancement issue during delivery creation. i am working for passenger vehicle company.
    Back ground Info.
    the company procures chassis from vendor & builds bus body over it. there are various types of chassis & each is uniquely identified in SAP by Material No. & also mentioned in BOM created for bus. when chassis is received , equipment is created using T-code IE01. After this one more equipment is created for bus which is called BBD Serial No. The equipment for BBD serial no holds chassis serial no. My issue is at the time of creation of delivery using T-code VL01N the user puts the BBD Serial No manually in a dialog box provided, This BBD Serial No is not capturing in the importing structure IT_XLIPS of BADI "LE_SHP_DELIVERY_PROC" Method "Delivery_Final_Check".
    I have to put a check during delivery creation for consumption of Chassis , if the Chassis is consumed during production phase a Mat Doc will be generated with movement Type 261. As such we don't knew the Mat Doc for Chassis Serial no Consumed during prod phase. so to derive chassis no in the BADI against which we have to check for it's consumption. The user provide BBD Serial no in a standard dialog box in VL01N.
    Can we use Field Exit for this or any other BADI Should work.
    Best Regards
    Priyesh Shah

    Hi Priyesh,
    Below steps may help you to get the value of the standard dialog box provided in the screen.
    1. Find the field name of the standard dialog box provided in the the screen for BBD Serial no.
    2. Implement below code in the BAdI "LE_SHP_DELIVERY_PROC" method.
    FIELD-SYMBOLS: <fs> TYPE BBDFIELDTYPE.
    ASSIGN ('(SAPMV50A)BBDFIELDNAME') TO <fs>.
    Now the field symbol <fs> will hold the value passed in the dialog box.
    Please try and let me know if it is working or not.
    Thanks
    Gangadhar

  • New planned goods issue date during delivery creation due to changed route

    Hello All,
    I have defined 2 routes with different values for transit time and transporation lead times. I have configured routes such that in order creation - route A is determined and while delivery creation due to weight group - delivery B is determined.
    Now for Route A i have maintained transit time of 3 days and Transportation lead time of 4 days and for Route B it is 1 day each.
    Delivery scheduling is active for the order type.
    Now when i create the order with a delivery date of say 05/24/2010 then (route A with transit time of 3 days) is determined and the planned goods issue date of 05/21/2010 is in the order.
    Now while creating delivery (Route B which has transit time 1 day) is determined due to the weight group. But the planned goods issue date is still the same 05/21/2010 as in order.
    I am assuming that since the route B has a route of 1 day so the planned goods issue date should be re-determined to 05/23/2010? IS there no scheduling done during delivery creation even though route and subsequently transit time has changed?
    Please let me know the answer to this...
    Thanks
    Shobhit

    Hi ,
    You can use TA - MASS . Enter object type - BUS2032(for sales orders) on initial screen and select sales item data.
    Next screen enter selection fields like sales order no and items. After giving order no and item range , execute and enter all new values for any item data fields. After pressing button "carry out mass change", don't forget to press save button.

  • Budget exceeded error during delivery creation

    Dear All,
    We are facing a problem during delivery creation. Our business scenario is engineered to order and every customer order is created as a Project in PS module. the sales order is linked to the  WBS element. While creating an outbound delivery for the sales order the system gives error message that "Budget exceeded for the WBS." This is for first time such error has occurred during the delivery creation. Logically delivery creation and PGI indicates negative incurrence on the WBS elements so even if the budget is not there or exhausted still then system should allow to create the delivery.
    Please let me know if anybody has face this problem and solved it.
    regards'
    Preetam

    Preetam,
    What you are saying is correct. Delivery creation and PGI indicates negative incurrence on the WBS elements, the system should not check budget of the WBS.
    Just for checking manually, read the details of the error and note the amount. Check budget availability of wbse and compare this amount with available budget.
    Regards,
    Amol Sarode

Maybe you are looking for

  • Cancel the Release for PO & PR

    Hi Once PR or PO released and follow on documents are processed then release can not be cancelled . If PR is released  and Po has created  , the PR release can not be reversed . Similarly If PO released and GR has taken for that PO then release can n

  • How to add attribute to Group in opensso

    I want to add a new attribute in opensso group as UsageControl. Presently while we create a group, we only get option to give id of the group. How to add an entry in that page? I want to give the value of Usagecontrol while creating a group, also I w

  • How to email reports in 9i

    Hi, Could someone please direct me to what I need to do. I would like to email my reports using the clients Outlook program from 9i on the web. Is this possible? If not are there any alternatives. Sorry but I've read so much I don't know where to sta

  • Entourage Sent Items on Blackberry

    Hello all...very strange issue. I am hoping to get totally off of my PC (XP). I am using Entourage for mail with corp exchange. But when I send mail from Entourage I do not see it on my blackberry as a sent item. Yet when I send from outlook, I see i

  • OAM 11.1.6 integration with Ebusiness 12.1.3 throws error on login

    I have integrated the OAM 11.1.6 SSO with E-business 12.1.3 instance.If I login to E-business it will redirect to the the error "There was an error processing your request. The Login/Portal Server Installation may be incomplete. Please contact your S