Zreports for vendor wise Delivery schedule release

hi ,
Can some one help me with codes for  the reports for the Delivery Schedule Release vendor wise. which shows vendor details , on titles, Schedule agreement Nos and then the material listed with the qty and targetted date.
Kindly help
regards
Kim

How to release directly from ME38 ?
I tried in the path  delivery sche > Edit > generate Forc Sche
but the msg below:
Error generating release against scheduling agreement  (cause 2)
Message no. 06857
Diagnosis
The function module for generating a scheduling agreement release (forecast delivery schedule or JIT delivery schedule) has run up against an error, causing processing to be terminated.
In this case the cause of the error is 2.
*System Response*
The error may involve one of the following situations:
1: The nature of the error cannot be specified precisely.
2: The forecast delivery schedule or the JIT delivery schedule was generated but no message record could be generated.
3: A document type for which the functions "Generate forecast delivery schedule" or "Generate JIT delivery schedule" are not defined may be involved.
4: A material for which the function "Generate JIT delivery schedule" is not defined may be involved.
5: A scheduling agreement that has not yet been released by all persons responsible may be involved.
6: The factory calendar has not been maintained correctly.

Similar Messages

  • Part1 is not Generating for Vendor Subsequent Delivery

    Hi ASAP
    I hope you must be doing great; steps are as follow which Iu2019m following for vendor return and subsequent delivery for Raw / Capital goods.
    1. PO -> MIGO (101) -> Excise capture & Posting using J1IEX -> MIRO.
    For excise, part1 & 2 to relevant register posting has taken placed.
    Now quality dept. has rejected the goods, for which vendor delivery should take place.
    2. For Vendor return Delivery
    MIGO 122 w.r.t GR of 101-> Excise capture & Posting using J1IS&V.
    For Excise, Part1 is getting created using J1IS, J1IV is creating Part 2, in Acct. doc. RG23C BED/ECS/HEC is being Credit and "PLA On Hold" is being Debited for BED/ECS/HEC amount.
    3. For Vendor subsequent delivery, I have done the excise config. for Movt. 123 .
    MIGO 123 w.r.t. GR of 122. 
    While doing GR for 123, system is not generating Excise screen.
    Any way, After GR of 123, I have Capture Excise Invoice after inputting all relevant data, but while Posting, System is generating message that Part1 is does not exist for vendor excise invoice.
    Now I think requirement is visible for your understanding to suggest me some valuable idea.
    If possible can plz drop a test mail to hksiva.manoj at gmail dot com for further clarification?
    Thanks & Regards
    Manoj K Singh

    Hi Rajaram,
    Thanks for your ealiest reply, yes i have done the config. which you suggested,
    Even after this " Specify which mvt type involves excise invoices",  assignment system is not generating Excise screen for Movt. 123 w. r. t. 122.
    Manoj K Singh

  • IDOC for sheduling agreement delivery schedules (without Forecast/JIT)

    There is an outbound IDOC DELINS to trasmit MM scheduling agreement (Doc.type LPA) delivery schedules of type Forecast/JIT using release procedure. But, can I create outbound IDOC DELINS to transmit MM scheduling agreement (Doc.type LP without release procedure) schedule lines (without specifying forecast/JIT shcedule lines)? When this IDOC is transmitted and processed as an inbound IDOC, it should add schedule lines to a Schedule agreement (Doc.type DS) in SD module. Thanks. Satya.

    Hi Anil ,
    Goto Transaction NACE , Select Application EL and then Click on O/p Types.
    Select your o/p and click on Processing routines.
    Make a copy of medium 1 and change it to 5. The program , Form , Form routine would remain the same.
    Maintain condition records with medium 5 in MN10.
    Ensure that email address exists in Vendor Master.
    Check with ur Basis to make sure that the setting are done in Transaction SCOT for sending document via PDF.
    Create a new Agreement and test it.
    Regards
    Ramesh Ch

  • SA delivery schedule release problem

    Hi all,
    I am created a schedule agreement (Type LPA) and created delivery schedule for it.
    When I am trying to release the delilvery schedule using ME84, I am getting the follwing error.
    Msg No 06/857 -> No message record found.
    I created condition record through NACE for Allication area EL, output type LPET. Still the problem persists.
    Require your suggestions.

    How to release directly from ME38 ?
    I tried in the path  delivery sche > Edit > generate Forc Sche
    but the msg below:
    Error generating release against scheduling agreement  (cause 2)
    Message no. 06857
    Diagnosis
    The function module for generating a scheduling agreement release (forecast delivery schedule or JIT delivery schedule) has run up against an error, causing processing to be terminated.
    In this case the cause of the error is 2.
    *System Response*
    The error may involve one of the following situations:
    1: The nature of the error cannot be specified precisely.
    2: The forecast delivery schedule or the JIT delivery schedule was generated but no message record could be generated.
    3: A document type for which the functions "Generate forecast delivery schedule" or "Generate JIT delivery schedule" are not defined may be involved.
    4: A material for which the function "Generate JIT delivery schedule" is not defined may be involved.
    5: A scheduling agreement that has not yet been released by all persons responsible may be involved.
    6: The factory calendar has not been maintained correctly.

  • Report for in time delivery schedules

    Dear all,
    Plz give me information abt in time and out of schedule material received against given schedules in an purchase order.  provide me relevant tables in which sceduled delivery wise grn data is updated.
    regards ,
    prasad.

    Hi,
    Refer Tables EKES
                        EKET
    Thanks,
    Kishore

  • Zreport for vendor customer details.

    Hi ,
    I have to create a report tto display a vendor and customer details. on screen i have customer code and vendor code with company code and fiscal year. when i select the cust. code plant and year it will show the doc.no ,post. and doc. date,doc type ,qty and amount as per customer details.
    after that as per billing doc. of specific customer ,select excise invoice number and match it with reference number (xblnr) of vendor code. and once it is matched select tht vendor doc.no. post. and doc. date amount and qty and display it in report.so how to right a coding for thesame
    let me know as its urgent.
    Rgrs
    Suchita

    please find below coding for your reference.
    *& Report  ZFI_VEND_CUST_DETAILS
    REPORT  ZFI_VEND_CUST_DETAILS
      NO STANDARD PAGE HEADING
              LINE-COUNT 65
              MESSAGE-ID 00.
    TABLES: BSID,BSIK.
    DATA: IT_BSID LIKE BSID OCCURS 0 WITH HEADER LINE.
    DATA: IT_BSIK LIKE BSIK OCCURS 0 WITH HEADER LINE.
    DATA: IT_J_1IEXCHDR LIKE J_1IEXCHDR OCCURS 0 WITH HEADER LINE.
    DATA: BEGIN  OF IT_OUT OCCURS 0,
            BELNR LIKE BSID-BELNR,        " added On 17.04.2007
            BLDAT LIKE BSID-BLDAT,
            BUDAT LIKE BSID-BUDAT,
            BLART LIKE BSID-BLART,
            NAME  LIKE KNA1-NAME1,                           "Name 1
            MATNR LIKE VBRP-MATNR,    "Material Number
            ARKTX LIKE VBRP-ARKTX,          "Material description
            FKIMG LIKE VBRP-FKIMG,          "Quantity mentioned in the excise invoice
            VBELN LIKE BSID-VBELN,          "Billing Document
            BUKRS LIKE BSID-BUKRS,
           NAME1 LIKE LFA1-NAME1,
            KUNNR LIKE BSID-KUNNR,
            WRBTR LIKE BSID-WRBTR,
            DMBTR LIKE BSID-DMBTR,
            ZUONR LIKE BSID-ZUONR,
           XBLNR LIKE BSID-XBLNR,
           MENGE LIKE VBRP-MENGE,
           LIFNR  LIKE BSIK-LIFNR,        "VENDOR CODE
            EXNUM LIKE J_1IEXCHDR-EXNUM,
            BELNR1 LIKE BSIK-BELNR,        " added On 17.04.2007
            BLDAT1 LIKE BSIK-BLDAT,
            BUDAT1 LIKE BSIK-BUDAT,
           BLART LIKE BSID-BLART,
           NAME  LIKE KNA1-NAME1,                           "Name 1
           MATNR LIKE VBRP-MATNR,    "Material Number
           ARKTX LIKE VBRP-ARKTX,          "Material description
           FKIMG1 LIKE VBRP-FKIMG,          "Quantity mentioned in the excise invoice
           VBELN LIKE BSID-VBELN,          "Billing Document
           BUKRS LIKE BSID-BUKRS,
            NAME1 LIKE LFA1-NAME1,
           KUNNR LIKE BSID-KUNNR,
           WRBTR LIKE BSID-WRBTR,
            DMBTR1 LIKE BSIK-DMBTR,
           ZUONR LIKE BSID-ZUONR,
            XBLNR LIKE BSIK-XBLNR,
           MENGE LIKE VBRP-MENGE,
            LIFNR  LIKE BSIK-LIFNR,
            END OF IT_OUT.
    *DATA: IT_OUT1 LIKE IT_OUT OCCURS 0 WITH HEADER LINE.
    *ALV VARIABLES AND INTERNAL TABLES
    TYPE-POOLS: SLIS.
    DATA: IS_LAYOUT     TYPE SLIS_LAYOUT_ALV,
          IT_FIELDCAT   TYPE SLIS_T_FIELDCAT_ALV,
          IT_LISTHEADER TYPE SLIS_T_LISTHEADER,
          IT_EVENTS     TYPE SLIS_T_EVENT,
          IT_PRINT      TYPE SLIS_PRINT_ALV OCCURS 1 WITH HEADER LINE.
    *SELECTION SCREEN DEFINITIONS
    SELECTION-SCREEN BEGIN OF BLOCK B WITH FRAME TITLE TEXT-001.
    SELECT-OPTIONS : SO_KUNNR FOR   BSID-KUNNR,
                     SO_LIFNR FOR   BSIK-LIFNR,
                     SO_BLART FOR   BSID-BLART.
    PARAMETER      : P_BUKRS LIKE   BSID-BUKRS OBLIGATORY,
                     P_GJAHR LIKE   BSID-GJAHR OBLIGATORY.
    SELECTION-SCREEN END OF BLOCK B.
    *START-OF-SELECTION
    START-OF-SELECTION.
      PERFORM GET_DATA.
      PERFORM DISPLAY_DATA.
    *&      Form  GET_DATA
          text
    -->  p1        text
    <--  p2        text
    form GET_DATA .
    SELECT * FROM BSID
    INTO TABLE IT_BSID
    WHERE KUNNR IN SO_KUNNR AND
    BUKRS = P_BUKRS AND
    GJAHR = P_GJAHR.
    LOOP AT IT_BSID.
    IT_OUT-BELNR = IT_BSID-BELNR.
    IT_OUT-BUKRS = IT_BSID-BUKRS.
    IT_OUT-KUNNR = IT_BSID-KUNNR.
    IT_OUT-ZUONR = IT_BSID-ZUONR.
    IT_OUT-DMBTR = IT_BSID-DMBTR.
    IT_OUT-VBELN = IT_BSID-VBELN.
    IT_OUT-XBLNR = IT_BSID-XBLNR.
    IT_OUT-BLART = IT_BSID-BLART.
    IT_OUT-BUDAT = IT_BSID-BUDAT.
    IT_OUT-BLDAT = IT_BSID-BLDAT.
    APPEND IT_OUT.
    ENDLOOP.
    *SELECT * FROM J_1IEXCHDR
    *INTO IT_J_1IEXCHDR
    *WHERE RDOC = IT_OUT-VBELN.
    *LOOP AT IT_J_1IEXCHDR.
    IT_OUT-EXNUM = IT_J_1IEXCHDR-EXNUM.
    **ENDLOOP.
    *SELECT * FROM BSIK
    *INTO TABLE IT_BSIK
    *WHERE XBLNR = IT_OUT-EXNUM AND
    *LIFNR IN SO_LIFNR AND
    *BUKRS = P_BUKRS AND
    *GJAHR = P_GJAHR.
    *LOOP AT IT_BSIK.
    *IT_OUT-BELNR1 = IT_BSIK-BELNR.
    **IT_OUT-BUKRS = IT_BSIK-BUKRS.
    *IT_OUT-LIFNR = IT_BSIK-LIFNR.
    **IT_OUT-ZUONR = IT_BSIK-ZUONR.
    *IT_OUT-DMBTR1 = IT_BSIK-DMBTR.
    *IT_OUT-XBLNR = IT_BSIK-XBLNR.
    **IT_OUT-BLART = IT_BSIK-BLART.
    *IT_OUT-BUDAT1 = IT_BSIK-BUDAT.
    *IT_OUT-BLDAT1 = IT_BSIK-BLDAT.
    *APPEND IT_OUT.
    *ENDLOOP.
    *ENDLOOP.
    *ENDSELECT.
    *SORT IT_OUT BY KUNNR.
    LOOP AT IT_OUT.
    SELECT SINGLE EXNUM FROM J_1IEXCHDR
    INTO IT_OUT-EXNUM
    WHERE RDOC = IT_OUT-VBELN.
    SELECT BELNR LIFNR DMBTR XBLNR BUDAT BLDAT
    FROM BSIK INTO (IT_OUT-BELNR1,IT_OUT-LIFNR,IT_OUT-DMBTR1,IT_OUT-XBLNR,IT_OUT-BUDAT1,IT_OUT-BLDAT1)
    WHERE XBLNR = IT_OUT-EXNUM.
    ENDSELECT.
    SELECT SINGLE NAME1            "NAME OF CUSTOMER
               FROM KNA1
               INTO IT_OUT-NAME
               WHERE KUNNR = IT_OUT-KUNNR.
    SELECT SINGLE NAME1            "NAME OF VENDOR
                   FROM LFA1
                   INTO IT_OUT-NAME1
                   WHERE LIFNR = IT_OUT-LIFNR.
    SELECT MATNR ARKTX FKIMG
               FROM VBRP
               INTO (IT_OUT-MATNR,IT_OUT-ARKTX,IT_OUT-FKIMG)
               WHERE VBELN = IT_OUT-VBELN AND
                     WERKS = P_BUKRS.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
      EXPORTING
        input         = IT_OUT-MATNR
    IMPORTING
       OUTPUT        = IT_OUT-MATNR.
    MODIFY IT_OUT.
    CLEAR IT_OUT.
    ENDSELECT.
    ENDLOOP.
    endform.                    " GET_DATA
    *&      Form  DISPLAY_DATA
          text
    -->  p1        text
    <--  p2        text
    form DISPLAY_DATA .
      PERFORM FILL_LAYOUT_STRUCTURE.
      PERFORM ALV_HEADER USING IT_LISTHEADER.
      PERFORM FILL_FIELDCAT USING :
          'BLDAT'    'DOC Date'             10  'IT_OUT'  SPACE SPACE,
          'BUDAT'    'Post.Date'            10  'IT_OUT'  SPACE SPACE,
          'KUNNR'    'Customer Code'        10  'IT_OUT'  SPACE SPACE,
          'NAME'     'Customer Name'        35  'IT_OUT'  SPACE SPACE,
          'LIFNR'    'VENDOR CODE'          10  'IT_OUT'  SPACE SPACE,
          'NAME1'    'VENDOR DESC'          35  'IT_OUT'  SPACE SPACE,
          'BLART'    'Doc. Type'             2  'IT_OUT'  SPACE SPACE,
          'VBELN'    'BILLING DOC NO.'      10  'IT_OUT'  SPACE SPACE,
          'BELNR'    'Account Doc. No.'     10  'IT_OUT'  SPACE SPACE,
          'DMBTR'    'AMOUNT IN LOCAL'      13  'IT_OUT'  SPACE SPACE,
          'MATNR'    'Material Code'        10  'IT_OUT'  SPACE SPACE,
          'ARKTX'    'Material DESC'        35  'IT_OUT'  SPACE SPACE,
          'FKIMG'    'QTY'                  12  'IT_OUT'  SPACE SPACE,
          'ZUONR'    'ASSIGNNMENT'          18  'IT_OUT'  SPACE SPACE,
          'EXNUM'    'Excise inv no.'       13  'IT_OUT'  SPACE SPACE,
          'BELNR1'   'Account Doc. No.'     10  'IT_OUT'  SPACE SPACE,
          'BLDAT1'   'DOC Date'             10  'IT_OUT'  SPACE SPACE,
          'BUDAT1'   'Post.Date'            10  'IT_OUT'  SPACE SPACE,
          'DMBTR1'   'AMOUNT IN LOCAL'      13  'IT_OUT'  SPACE SPACE,
          'XBLNR'    'REFERENCE DOC'        10  'IT_OUT'  SPACE SPACE.
    PERFORM ALV_EVENTS USING IT_EVENTS.
    PERFORM ALV_PRINT.
      PERFORM ALV_DISPLAY.
    endform.                    " DISPLAY_DATA
    *&      Form  FILL_LAYOUT_STRUCTURE
          text
    -->  p1        text
    <--  p2        text
    form FILL_LAYOUT_STRUCTURE .
    DATA: WA_EVENT       TYPE SLIS_ALV_EVENT,
            WA_LISTHEADER  TYPE SLIS_T_LISTHEADER.
      CLEAR IS_LAYOUT.
      IS_LAYOUT-ZEBRA = 'X'.
         is_layout-F2CODE = '&ETA'.
         is_layout-detail_popup = 'X'.
      IS_LAYOUT-INFO_FIELDNAME = 'COL_LINE'.
    endform.                    " FILL_LAYOUT_STRUCTURE
    *&      Form  FILL_FIELDCAT
          text
         -->P_0606   text
         -->P_0607   text
         -->P_10     text
         -->P_0609   text
         -->P_SPACE  text
         -->P_SPACE  text
    form FILL_FIELDCAT  using    F D O T TO P.
      DATA WA_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
      STATICS POS LIKE SY-INDEX VALUE 1.
      POS = POS + 1.
      CLEAR WA_FIELDCAT.
      MOVE : 1     TO   WA_FIELDCAT-ROW_POS,
             POS   TO   WA_FIELDCAT-COL_POS,
             F     TO   WA_FIELDCAT-FIELDNAME,
             D     TO   WA_FIELDCAT-SELTEXT_L,
             O     TO   WA_FIELDCAT-OUTPUTLEN,
             T     TO   WA_FIELDCAT-TABNAME,
             TO    TO   WA_FIELDCAT-DO_SUM,
             P     TO   WA_FIELDCAT-FIX_COLUMN.
      APPEND WA_FIELDCAT TO IT_FIELDCAT.
    endform.                    " FILL_FIELDCAT
    FORM ALV_EVENTS USING EVENTS TYPE SLIS_T_EVENT.
      DATA : WA_EVENTS TYPE SLIS_ALV_EVENT.
      CLEAR WA_EVENTS.
      WA_EVENTS-NAME = 'TOP_OF_PAGE'(001).
      WA_EVENTS-FORM = 'TOP_OF_PAGE'.
      APPEND WA_EVENTS TO IT_EVENTS.
    ENDFORM.                    "alv_events
    *&      Form  ALV_DISPLAY
          text
    -->  p1        text
    <--  p2        text
    form ALV_DISPLAY .
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
      I_INTERFACE_CHECK                 = ' '
      I_BYPASSING_BUFFER                = ' '
      I_BUFFER_ACTIVE                   = ' '
         I_CALLBACK_PROGRAM                = SY-REPID
      I_CALLBACK_PF_STATUS_SET          = ' '
         I_CALLBACK_USER_COMMAND           = 'CALL_TCODE'
         I_CALLBACK_TOP_OF_PAGE            = 'TOP_OF_PAGE'
      I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
      I_CALLBACK_HTML_END_OF_LIST       = ' '
      I_STRUCTURE_NAME                  =
      I_BACKGROUND_ID                   = ' '
      I_GRID_TITLE                      =
      I_GRID_SETTINGS                   =
         IS_LAYOUT                         = IS_LAYOUT
         IT_FIELDCAT                       = IT_FIELDCAT
      IT_EXCLUDING                      =
      IT_SPECIAL_GROUPS                 =
       IT_SORT                           = i_sort[]
      IT_FILTER                         =
      IS_SEL_HIDE                       =
         I_DEFAULT                         = 'X'
         I_SAVE                            = 'A'
      IS_VARIANT                        =
         IT_EVENTS                         = IT_EVENTS
      IT_EVENT_EXIT                     =
         IS_PRINT                          = IT_PRINT
      IS_REPREP_ID                      =
      I_SCREEN_START_COLUMN             = 0
      I_SCREEN_START_LINE               = 0
      I_SCREEN_END_COLUMN               = 0
      I_SCREEN_END_LINE                 = 0
      I_HTML_HEIGHT_TOP                 = 0
      I_HTML_HEIGHT_END                 = 0
      IT_ALV_GRAPHICS                   =
      IT_HYPERLINK                      =
      IT_ADD_FIELDCAT                   =
      IT_EXCEPT_QINFO                   =
      IR_SALV_FULLSCREEN_ADAPTER        =
    IMPORTING
      E_EXIT_CAUSED_BY_CALLER           =
      ES_EXIT_CAUSED_BY_USER            =
       TABLES
          T_OUTTAB                          = IT_OUT
       EXCEPTIONS
         PROGRAM_ERROR                     = 1
         OTHERS                            = 2
      IF SY-SUBRC <> 0.
        MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    endform.                    " ALV_DISPLAY
    *FORM FOR TOP OF PAGE
    FORM TOP_OF_PAGE.
      CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
        EXPORTING
          IT_LIST_COMMENTARY = IT_LISTHEADER.
    ENDFORM.                    "top_of_page
    *&      Form  alv_header
    FORM alv_header  USING    P_IT_LISTHEADER.
      data : wa_listheader  type slis_listheader.
      data : v_date1(10).
      data : v_date2(10).
      data : v_kunnr1 LIKE bsid-kunnr.
      data : v_kunnr2 LIKE bsid-kunnr.
      data : v_name1 like t001w-name1.
      clear wa_listheader.
      wa_listheader-typ = 'H'.
      move  'DETAILED CUSTOMER VENDOR DETAILS'
      to  wa_listheader-info.
      append wa_listheader to it_listheader.
    select single name1
         from t001w
         into v_name1
         where werks = p_bukrs.
    clear wa_listheader.
    wa_listheader-typ = 'S'.
    wa_listheader-key = 'Plant'.
    move v_name1
    to wa_listheader-info.
    append wa_listheader to it_listheader.
    write so_budat-low  to v_date1  dd/mm/yyyy no-gap.
    write so_budat-high to v_date2  dd/mm/yyyy no-gap.
    if so_budat-low is not initial and so_budat-high is not initial.
       clear wa_listheader.
       wa_listheader-typ = 'S'.
       wa_listheader-key = 'Date '.
       concatenate v_date1 ' To ' v_date2 into
                           wa_listheader-info separated by space.
       wa_listheader-info = wa_listheader-info.
       append wa_listheader to it_listheader.
    elseif  so_budat-low is initial and so_budat-high is initial.
       clear wa_listheader.
       wa_listheader-typ = 'S'.
       wa_listheader-key = 'Date '.
       wa_listheader-info = '*'.
       append wa_listheader to it_listheader.
    elseif so_budat-high is initial.
       clear wa_listheader.
       wa_listheader-typ = 'S'.
       wa_listheader-key = 'Date '.
       wa_listheader-info = v_date1.
       append wa_listheader to it_listheader.
    endif.
    v_kunnr1 = so_kunnr-low.
    v_kunnr2 = so_kunnr-high.
    if so_kunnr-low is not initial and so_kunnr-high is not initial.
       clear wa_listheader.
       wa_listheader-typ = 'S'.
       wa_listheader-key = 'Customer '.
       concatenate v_kunnr1 ' To ' v_kunnr2 into
                           wa_listheader-info separated by space.
       wa_listheader-info = wa_listheader-info.
       append wa_listheader to it_listheader.
    elseif  so_kunnr-low is initial and so_kunnr-high is initial.
       clear wa_listheader.
       wa_listheader-typ = 'S'.
       wa_listheader-key = 'Customer '.
       wa_listheader-info = '*'.
       append wa_listheader to it_listheader.
    elseif so_kunnr-high is initial.
       clear wa_listheader.
       wa_listheader-typ = 'S'.
       wa_listheader-key = 'Customer '.
       wa_listheader-info = v_kunnr1.
       append wa_listheader to it_listheader.
    endif.
    ENDFORM.                    " alv_header.
    waiting for ur reply.
    Thanx
    Suchita

  • Quality inspection for vendor wise

    Hi,
    My client is having a vendor in Hyderabad, he is a properitory vendor then  inspection isn't required while receiving the material.Another vendor is  in Bangalore, for this vendor inspection is required. But the material number is same for both the vendors. How can i proceed this scenerio.Can anybody suggest.
    Regards,
    Krishna

    Hi Krish,
    You can control this scenario through Inspection control in the Insp. Control tab of Q-info record. Maintain Q-info record for the vendor you need to skip inspection through QI01, Enter the Vendor QM system in the Vendor master record (Consult MM Guy), and select the Existing QM system such that it matches the Vendor QM system and select the inspection control as No Inspection. Your problem will be solved.
    Reward if cleared or get back with queries.
    Keerthi

  • Less GR for delivery schedule against Scheduling agreement

    Dear Experts ,
    we created some Scheduling agreement (ME31N) for vendors and created day wise delivery schedule to receive goods . 
    In SAP we can see that there are some open delivery schedules of past date, say total pending schedules  are of 3000 PCS.
    Then we must be able to do GR(103) for 3000 PCS,  But during GR(103)  SAP is showing that we are having only 1700 PCS remaining for GR .
    How can it possible ?  Please help.
    Regards,
    Ashutosh

    Dear SAP Experts,
    We have created some Scheduling agreement (ME31N) for vendors and created day wise delivery schedule to receive goods.
    1)   In SAP we can see that there are some open delivery schedules of past date, say total pending schedules are of 3000 PCS. Then we must be able to do GR(103) for 3000 PCS, But during GR(103) SAP is showing that we are having only 1700 PCS remaining for GR .
    2) same way in some cases if we have 3000 PCS delivery schedule in breakup of,
        1000     on    15.07.2011
        1000     on    16.07.2011
        1000     on    17.07.2011
    Then if we do GR on 15.07.2011  then system must show that we can do GR of max. 1000 PCS
    And on 16.07.2011 , during GR it must show  2000 PCS, but here I am seeing some fix QTY say 5000 PCS irrespective of any date (means for all date I am seeing the same QTY)
    How can it possible  ? 
    Please help.
    Ashutosh

  • Delivery schedule print out and number

    Dear Expert
    Our client need to implement the scheduling agreement in the company , but the requirement as follows their are two dept one is for vendor dealing and our is meant for requirement generation , so scheduling agreement is generated by one dept and delivery schedule will be generated by other , is it possible to  generate different for delivery schedule?/it not how can we configure the system as such when we release the delivery schedule on the basis of FRC release procedure then only print out should be generated for the deliverry schedule and print out should only consider those line item of delivery schedule which are release no other , i.e if for e.g for 1st month the delivery schedule is generated against the PR 's for different line item of Scheduling agreement , then only  those item wil be consider which are release as per the FRC , then for the next delivery schedule only those item to be consider in the print out which are release 2nd time. how can we map this scenario in the system
    Regards
    farhan

    Dear Expert
    can we customize system as such that we cannot  maintained delivery schedule before the  release of the  SA
    Regards
    farhan

  • Scheduling Agreement with Delivery Schedule using Idoc messages

    Hi all,
    Can anybody please explain the importance of the field name "LABKY" in Idoc execution for Forecaste/JIT Delivery Schedule.
    My requirement is that when i send a new Idoc i do not want the old schedule line which are not yet released , to be deleted .
    As per the SAP help the use of the field LABKY is related to this , but when i tried its value as "1" , the previous schedule lines are still getting deleted.
    Can you pls explain how to go about it . ( DELFOR/DELJIT Idocs)
    Thank you
    Regards
    Subha

    Hi ,
    The Field
    LABKY : Delivery schedule key
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 026, Offset : 0393. external length : 000001
    Regards
    Seegal

  • Idoc execution in Scheduling Agreement with Delivery Schedule

    Hi all,
    Can anybody please explain the importance of the field name "LABKY" in Idoc execution for Forecaste/JIT Delivery Schedule.
    My requirement is that when i send a new Idoc i do not want the old schedule line which are not yet released , to be deleted .
    As per the SAP help the use of the field LABKY is related to this , but when i tried its value as "1" , the previous schedule lines are still getting deleted.
    Can you pls explain how to go about it . ( DELFOR/DELJIT Idocs)
    Thank you
    Regards
    Subha

    Hi ,
    The Field
    LABKY : Delivery schedule key
    internal data type : CHAR
    Internal length : 000001 characters
    Position in segment : 026, Offset : 0393. external length : 000001
    Regards
    Seegal

  • Regarding the Delivery schedule item in Production order

    Hi Gurus,
    Kindly can you let me know what are the settings to be done for getting the delivery schedule line number in the production order along with the sales order and item number for a MTO scenario.
    Regards
    Anand

    If you're working with stg. grp 20, it should do what you're looking for.
    If you're not sure, do this in your sandbox -> assign the stg. grp in material master, create a SO for this material, run MRP, convert the planned order to production order & verify the results.
    To know more about this stg. grp you can go thru SAP help or just do a search in this forum or maybe wait for someone to paste the links for you.

  • Part1 is not generating for Vendor Subsequent delivey

    Hi ASAP
    I hope you must be doing great; steps are as follow which Iu2019m following for vendor return and subsequent delivery for Raw / Capital goods.
    1. PO -> MIGO (101) -> Excise capture & Posting using J1IEX -> MIRO.
    For excise, part1 & 2 to relevant register posting has taken placed.
    Now quality dept. has rejected the goods, for which vendor delivery should take place.
    2. For Vendor return Delivery
    MIGO 122 w.r.t GR of 101-> Excise capture & Posting using J1IS&V.
    For Excise, Part1 is getting created using J1IS, J1IV is creating Part 2, in Acct. doc. RG23C BED/ECS/HEC is being Credit and "PLA On Hold" is being Debited for BED/ECS/HEC amount.
    3. For Vendor subsequent delivery, I have done the excise config. for Movt. 123 .
    MIGO 123 w.r.t. GR of 122. 
    While doing GR for 123, system is not generating Excise screen.
    Any way, After GR of 123, I have Capture Excise Invoice after inputting all relevant data, but while Posting, System is generating message that Part1 is does not exist for vendor excise invoice.
    Now I think requirement is visible for your understanding to suggest me some valuable idea.
    If possible can plz drop a test mail to hksiva.manoj at gmail dot com for further clarification?
    Thanks & Regards
    Manoj K Singh

    Hi Rajaram,
    Thanks for your ealiest reply, yes i have done the config. which you suggested,
    Even after this " Specify which mvt type involves excise invoices",  assignment system is not generating Excise screen for Movt. 123 w. r. t. 122.
    Manoj K Singh

  • Importance of Forecast Delivery Schedules in SD scheduling agreements

    Hi ALL,
    I would just like to consult you a scenario that I'm facing.
    When I create a JIT scheduling agreement, even though that schedule lines are maintained for the JIT delivery schedule tab, if the Forecast delivery schedule tab has no schedule lines, the NET value of the document will be zero.
    Can you explain the Logic behind this?
    Also, why am I not allowed to create an outbound delivery and invoice if the Forecast Delivery schedule tab has no schedule lines?
    I know that the document will be incomplete without the net value, but why is it even though schedule lines are created in the JIT tab?
    Please help me with this.
    Thanks in advance guys!

    This is what I found out in an SAP “Knowledge Base Article" (1472965), indicating that there has to be requirements in the forecast delivery schedule in order for the schedujle agreement line item to not be considered incomplete for price.
    https://websmp230.sap-ag.de/sap/support/notes/convert2pdf/002007204200000153012010?sap-language=EN
    Resolution
    l You have to enter schedule lines for the forecast delivery schedule
    l The VBAP-NETWR is calculated based on forecast delivery schedule and not according to the JIT delivery schedule
    Regards,
    Jeff

  • Vendor wise MIC Limit

    Dear Gurs,
    Pls help me for the scenario as mentioned followed.
    I have a one material. for that there is a 3 differenet vendors. for that material Length is a one MIC.but as per vendor limit is different. I don't want to use a 3 different MIC for vendor wise. Requirment is One Material, One MIC but Limit should be come in Inspection plan as per vendor.
    MIC u2013 length
    Vendors u2013 A,B and C
    Vendor Spec for length for the SAME material u2013 10-12cm,10-18cm,10-20cm (A,B and C vendors)
    For GR if vendor is B then for that Inspcection lot limit of the MIC legnth should be reflected as a 10-18 cm.
    Thanks in advance for help.

    Hi Mihir,
    There are two ways to incorporate the requirement.
    1. Create that much number of task list counters for the inspection plans, same as the Vendors you have. I means One Task list group counter 01 will be assigned to Material 'M' Vendor 'A', counter 02 for  Material 'M' Vendor 'B', & counter 03 for  Material 'M' Vendor 'C'.
    2.  Refer the [wiki document|https://wiki.sdn.sap.com/wiki/display/PLM/SameParameters-DifferentSpecifications]
    Regards,
    Shyamal

Maybe you are looking for