EDI1(vendor confirmation price) in PO can set to green light?

I have setup the condition EDI1 for the vendor confirmed price. I set as default, when I create PO, the EDI1 condition will show up in the condition tab with price 0. But I found out that EDI1 condition is in "Red light" in stead of green light. Although there is no problem to save the PO, but I feel irritated to see the red light there.
Is there a way to set it as green light with zero price?
Edited by: janice on Aug 13, 2010 9:56 AM

hi J,
i also have the same business requirement-
1/ to have price confirmation from vendor (from what platform vendor can send confirmation- if it has to be via EDI via mail, ??)
2/ do you maintained new condition type in the pricing schema for the PO , and hou is it triggered once the vendor confirm/ mail the price?
thanks in advance for your assistance as to hou to configured this requirements.
thanks a lot,
Coolio.

Similar Messages

  • Generating Inbound delivery based on Vendor Confirmation for Purchase order

    Is there a way to create Inbound deliveries based on Vendor confirmation for a purchase order.
    Here is the complete scenario.
    Buyer Creates the PO for qty 100 and Date August 29
    Vendor Confirms that he can supply a qty of 50 for August 29 and remaining 50 for Sep15th
    Based on vendor confirmation, Buyer creates 2 vendor confirmations (AB) to match with the data received from Buyer, without modifing the PO.
    Requirement:
    Inbound deliveries should get created based on the vendor confirmation.
    As MRP looks at Inbound delivery for Planning purposes once they are available, Inbound delivery should match with vendor confirmation data.
    Is it possible to get this requirement met with standard config available in SAP.

    could you eventually get the answer from the docu Set Up Confirmation Control

  • Vendor confirmation via EDI treated differently by MRP than Manually enterd

    I have a strange situation with MRP. 
    I have a schedule agreement with the following information.
    Date          Delivery sch            vendor confirmation
    05/03/07          100                         100
    05/10/07          100                         100
    05/17/07          100                         100
    05/24/07          100                         100
    05/31/07          100                         100
    06/07/07          100                         100
    06/14/07          100                         100
    Then I increase my independent requirments on 05/10/07 to 200. 
    If I have input my vendor confirmation manually via ME38, then MRP will add an additional Schedule line on 05/10/07 as I expected.   However if the vendor confirmations were sent in via idocs/edi then the schedule line is not added until the end of the confirmations.   
    Does anyone know why MRP would treat these differently based on if the confirmation were manual versus EDI?

    It should not be treated saperately by MRP if it is posted manually or via EDI
    i can think one thing that
    do you have diff confirmaiton category for EDI and diff for manually than it can happen
    so just make sure that all the confirmation category which you use is check for MRP relevant or not in
    SPRO_MM_Purchasing-conformation-Set Up Confirmation Control-select your EDI confirmation contro key and click on confirmation sequence
    and check here that the conf cat is check for MRP or not
    if not than check than you will see that MEP will pickup that.

  • How to post vendor confirmations

    Hello,
    I am getting vendor confirmations like Change in net price quantity and
    delivery date through ORDERSP IDoc. These confirmations are able to see
    in EKES table also.
    But my client want these vendor confirmation should be directly posted
    into the Purchase order.
    Is there is any exit available for this. Is there any other way by
    which? How can I realize this functionality.
    Thanks and regards
    Murali

    Hi sai kumar,
    Thanks for your reply.
    Can you tell me where I can check confirmation control configuration.
    Can I find it in SPRO
    Regards
    Murali Krishna

  • Vendor Confirmation workflow ( TS00008075 ) issue for IDOCs in Error ( 51 )

    Hi All,
              When IDOCs (Basic type: ORDERS02, Message type : ORDRSP ) goes in error with status 51 & comes to SAP system it calls event  u2018INPUTERROROCCURREDu2019  which is correct but it creates problem when it get re processed as it triggers event u2018INPUTSUCCESSu2019 resulting in firing vendor confirmation workflows to respective user ( this batch job re process each ORDRSP IDOC twice a day & hence 2 workflows per IDOC in error to clientu2019s inbox by triggering event u2018INPUTSUCCESSu2019).
    Could you please tell me why these IDOCs are triggering event u2018INPUTSUCCESSu2019 in case of error ( status 51 ) when they get RE PROCESSED. These kind of Idocs must only trigger u2018INPUTERROROCCURREDu2019  once  and should not create anything when these get reprocessed. Please note that these issues arise after EHP4 upgrade. Please let me know if any setting is there for triggering Vendor COnfirmation workflow ( TS00008075 ) when IDOCs in error get re processed.
    Please help us , thanks.
    Regards,
    Kartikey Rawat.

    Hello Kartikey Rawat !
                        INPUTSUCCESS  event gets fired just because it is configured as terminating event in the task.
                        If you don't want this event to get fired, either you can deactivate it  or delete the bindings related to the event  INPUTSUCCESS(doing so should not affect other two terminating events that may be required for you scenario) .
                        If you want know why it is fired, you can get to know in debug mode or check whether the event is defined through  related function modules configured in WE57,BD51,WE42 AND WE20 transaction codes.
                        In WE05 or WE02 transactions, you will get error description.Based on it too, you can figure out the reason.
    Regards,
    S.Suresh

  • BDC for ME22n vendor confirmation

    i am facing problem while doing BDC for ME22N . i am going for itemwise vendor confirmation.
    for first line item it is happening. but for 2nd line item it is not going.
    any help?
    this is my code. i guess some loop i have to add but where? can any body give idea?
    REPORT  ZMM_VC_UPLOAD.
    TABLES :  t100.
           Internal table declaration                                    *
    DATA : BEGIN OF it_upload OCCURS 0,
                  index(4),      "Index
                  EBELN(10),     "PO number
                 EBELP(5),      "line item PO
                  LIST(1),       "item number
                  BSTAE(4),      "Confirmation control key
                  EBTYP(2),      "Confirmation Category
                 BSTAE(4),      "Confirmation control key
                  LPEIN(1),      "Category of delivery date
                  EEIND(10),     "delivery date
                  MENGE(13),     "QTY Quantity as per vendor confirmation
                  XBLNR(20),     "ext doc
                  ERDAT(10),     "doc date
                  er_message(100),
           END OF it_upload.
    DATA: BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE,
          MSGDATA LIKE BDCMSGCOLL  OCCURS 0 WITH HEADER LINE.
    *Selection Screen
    SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
    PARAMETER: P_FILE LIKE IBIPPARMS-PATH OBLIGATORY.  "to select a file.
    SELECTION-SCREEN END OF BLOCK B1.
    *Initialization
    INITIALIZATION.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE .
      PERFORM GET_FILENAME.
    start-of-selection
    START-OF-SELECTION.
      PERFORM MAKE_FILE_NAME .
      PERFORM UPLOAD_FILE.
        PERFORM BDC_PROCESS.
    perform read_messages.
    *&      Form  UPLOAD_FILE
    FORM UPLOAD_FILE .
      CALL FUNCTION 'WS_UPLOAD'
        EXPORTING
          FILENAME                = P_FILE
          FILETYPE                = 'DAT'
        TABLES
          DATA_TAB                = IT_UPLOAD .
            IF SY-SUBRC <> 0.
      ENDIF.
    ENDFORM.                    " UPLOAD_FILE
    *&      Form  bdc_process
    FORM BDC_PROCESS .
    loop at it_upload.
    LOOP AT IT_header.
    refresh bdcdata.
      perform bdc_dynpro      using 'SAPLMEGUI' '0014'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=MECHOB'.
    perform bdc_field       using 'MEPO_TOPLINE-BSART'
                                  'NB'.
    perform bdc_field       using 'DYN_6000-LIST'
                                  it_upload-list.    "'   1'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'MEPO1319-MATKL'.
    perform bdc_field       using 'MEPO1319-SPINF'
                                  'X'.
    perform bdc_dynpro      using 'SAPLMEGUI' '0002'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=MEOK'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'MEPO_SELECT-EBELN'.
    perform bdc_field       using 'MEPO_SELECT-EBELN'
                                  it_upload-EBELN.              "'4500195517'.
    perform bdc_field       using 'MEPO_SELECT-BSTYP_F'
                                  'X'.
    perform bdc_dynpro      using 'SAPLMEGUI' '0014'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=TABIDT14'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'MEPO_TOPLINE-BSART'.
    perform bdc_field       using 'MEPO_TOPLINE-BSART'
                                  'NB'.
    perform bdc_field       using 'DYN_6000-LIST'
                                  it_upload-list.    "'   1'.
    perform bdc_field       using 'MEPO1319-SPINF'
                                  'X'.
    perform bdc_dynpro      using 'SAPLMEGUI' '0014'.
    perform bdc_field       using 'BDC_OKCODE'             "first time
                                  '/00'.
    perform bdc_field       using 'MEPO_TOPLINE-BSART'
                                  'NB'.
    perform bdc_field       using 'DYN_6000-LIST'
                                 it_upload-list.    " '   1'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'MEPO1334-BSTAE'.
    perform bdc_field       using 'MEPO1334-BSTAE'
                                  it_upload-BSTAE  .                "'0005'.
    perform bdc_dynpro      using 'SAPLMEGUI' '0014'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'MEPO_TOPLINE-BSART'
                                  'NB'.
    *loop at it_item where ebeln = it_upload-ebeln.
    perform bdc_field       using 'BDC_CURSOR'
                                  'DYN_6000-LIST'.
    perform bdc_field       using 'DYN_6000-LIST'
                                  it_upload-list.    "'   1'.
    perform bdc_field       using 'MEPO1334-BSTAE'
                                  it_upload-BSTAE.                 "'0005'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'EKES-ERDAT(01)'.
    perform bdc_field       using 'EKES-EBTYP(01)'
                                  it_upload-EBTYP.                 "'vc'.
    perform bdc_field       using 'RM06E-LPEIN(01)'
                                  it_upload-LPEIN.                 "'D'.
    perform bdc_field       using 'RM06E-EEIND(01)'
                                  it_upload-EEIND.                 "'15.02.2009'.
    perform bdc_field       using 'EKES-MENGE(01)'
                                  it_upload-MENGE.                 "'10'.
    perform bdc_field       using 'EKES-XBLNR(01)'
                                  it_upload-XBLNR.                 "'inv 9'.
    perform bdc_field       using 'EKES-ERDAT(01)'
                                  it_upload-ERDAT.                 "'15.02.2009'.
    perform bdc_dynpro      using 'SAPLMEGUI' '0014'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=MESAVE'.
    CALL TRANSACTION 'ME22N' USING BDCDATA MODE 'A' UPDATE 'A' MESSAGES INTO MSGDATA. 
        CLEAR: BDCDATA,BDCDATA[].
        refresh BDCDATA.
      ENDLOOP.
    ENDFORM.                    " bdc_process
           Start new screen                                              *
    FORM BDC_DYNPRO USING PROGRAM DYNPRO.
      CLEAR BDCDATA.
      BDCDATA-PROGRAM  = PROGRAM.
      BDCDATA-DYNPRO   = DYNPRO.
      BDCDATA-DYNBEGIN = 'X'.
      APPEND BDCDATA.
    ENDFORM.                    "BDC_DYNPRO
           Insert field                                                  *
    FORM BDC_FIELD USING FNAM FVAL.
      IF FVAL <> ''.
        CLEAR BDCDATA.
        BDCDATA-FNAM = FNAM.
        BDCDATA-FVAL = FVAL.
        APPEND BDCDATA.
      ENDIF.
    ENDFORM.                    "BDC_FIELD
    *To get file name                                                      *
    FORM GET_FILENAME .
      CALL FUNCTION 'F4_FILENAME'
        EXPORTING
          PROGRAM_NAME  = SYST-CPROG
          DYNPRO_NUMBER = SYST-DYNNR
        IMPORTING
          FILE_NAME     = P_FILE.
      IF SY-SUBRC NE 0  .
        WRITE : / 'Enter File Name'.
      ENDIF.
    ENDFORM.                    "GET_FILENAME

    Hi Dude,
      When ur looping the item information , in your code ur
    loop at it_item where ebeln = it_upload-ebeln.
    perform bdc_field using 'BDC_CURSOR'
    'DYN_6000-LIST'.
    perform bdc_field using 'DYN_6000-LIST'
    it_upload-list. "' 1'.
    perform bdc_field using 'MEPO1334-BSTAE'
    it_upload-BSTAE. "'0005'.
    perform bdc_field using 'BDC_CURSOR'
    'EKES-ERDAT(01)'.
    perform bdc_field using 'EKES-EBTYP(01)'
    it_upload-EBTYP. "'vc'.
    perform bdc_field using 'RM06E-LPEIN(01)'
    it_upload-LPEIN. "'D'.
    perform bdc_field using 'RM06E-EEIND(01)'
    it_upload-EEIND. "'15.02.2009'.
    perform bdc_field using 'EKES-MENGE(01)'
    it_upload-MENGE. "'10'.
    perform bdc_field using 'EKES-XBLNR(01)'
    it_upload-XBLNR. "'inv 9'.
    perform bdc_field using 'EKES-ERDAT(01)'
    it_upload-ERDAT. "'15.02.2009'.
    perform bdc_dynpro using 'SAPLMEGUI' '0014'.
    perform bdc_field using 'BDC_OKCODE'
    '=MESAVE'.
    ->(01) you have to replace to variable , and every loop pass increment the varialbe value with 1.
    ex : -
    V1 = 1.
    loop at item.
    perform bdc_data using 'xyz(V1)' 
                                   it_upload-variable.
    V1 = V1 + 1.
    endloop.
    This is called as index , the table control fields are differ the field name by index only...

  • Updating Vendor Confirmations in PO

    Hi Friends,
    I am trying to update Vendor Confirmations(TABLE EKES) in PO using FM ME_CONFIRMATION_UPDATE.  Even checking for EKPO-BSTAE.
    But i could not able to update EKES table, its throwing an error 'SYSEM ERROR:ERROR DURING UPDATING TABLE EKES'.
    Any suggestions please
    Regards,
    Sunil
    Message was edited by:
            sunilkumar sankineni

    I'm also trying to update the EKES table using the same function module, but not able to update. Did your problem get solved. Can you give me the code, on how to update the EKES table.
    Message was edited by:
            P K Ch

  • BAPI for Purchase Order Vendor Confirmations

    Can any body suggest me the BAPI for the purchase order vendor confirmations transaction code me22n - Tab<b>-(Confirmations)</b> alone.
    regs,
    Raja

    Dear Asha,
    Pls find the below code, this handles only the BDC part of the program.Updates only the EKES table thru standard confirmation tab on ME22N.
    Kindly clarify any doubts in this reg.
    regs,
    Raja.
    FORM ins_stdtable .
      DATA:var TYPE c LENGTH 30,
      cstr(02) TYPE n value '01'.
      data istr(02) type n value '00'.
      DATA recno TYPE i.
      data: eblc type c length 5,
      ebli type i.
      DATA: kebeln LIKE utab-ebeln.
      DATA: BEGIN OF indx,
             ebelp type ekes-ebelp,
             eindx type i,
            END OF indx.
      DATA : CNT TYPE I value 1.
      DATA: COUNTER(2) TYPE N VALUE '01',
      ROWS TYPE P.
      DATA: w_textout            LIKE t100-text.
      DATA: gd_update TYPE i,
            gd_lines TYPE i.
      data :waek like indx,
      itabek LIKE TABLE OF waek.
    *Used to stores error information from CALL TRANSACTION Function Module
      DATA: BEGIN OF messtab OCCURS 0.
              INCLUDE STRUCTURE bdcmsgcoll.
      DATA: END OF messtab.
      SELECT MAX( ETENS ) FROM ekes INTO zetens WHERE ebeln =
      ekko-ebeln.
      recno = zetens.
      LOOP AT utab.
        SELECT distinct ebelp INTO CORRESPONDING FIELDS OF TABLE
        itabek  FROM eket  WHERE ebeln = ekko-ebeln.
        loop at itabek into waek.
          ebli =  ebli + 1.
          waek-eindx = ebli.
          modify itabek from waek.
        endloop.
        loop at itabek into waek where ebelp = utab-ebelp.
          eblc = waek-eindx.
          condense eblc.
        endloop.
        AT NEW ebeln.
          PERFORM bdc_dynpro      USING 'SAPLMEGUI' '0014'.
          PERFORM bdc_field       USING 'BDC_OKCODE'
                                        '=MECHOB'.
          PERFORM bdc_dynpro      USING 'SAPLMEGUI' '0002'.
          PERFORM bdc_field       USING 'BDC_OKCODE'
                                        '=MEOK'.
          PERFORM bdc_field       USING 'BDC_CURSOR'
                                        'MEPO_SELECT-EBELN'.
          PERFORM bdc_field       USING 'MEPO_SELECT-EBELN'
                                         utab-ebeln.
          AT New EBELP.
            perform bdc_dynpro      using 'SAPLMEGUI' '0014'.
            perform bdc_field       using 'BDC_CURSOR'
                                      'DYN_6000-LIST'.
            perform bdc_field       using 'DYN_6000-LIST'
                                     eblc.
            perform bdc_field       using 'BDC_OKCODE'
                                          '=DDOWN3200'.
            PERFORM bdc_dynpro      USING 'SAPLMEGUI' '0014'.
            PERFORM bdc_field       USING 'BDC_OKCODE'
                                          '=TABIDT15'.
            perform bdc_field       using 'DYN_6000-LIST'
                                    eblc.
            PERFORM bdc_dynpro      USING 'SAPLMEGUI' '0014'.
            PERFORM bdc_field       USING 'BDC_OKCODE'
                                          'PICK'.
          ENDAT.
        ENDAT.
        PERFORM bdc_field       USING 'DYN_6000-LIST'
                                          eblc.
        recno = recno + 1.
        cstr = recno.
        counter = cstr.
    *This is to check whether the scheduled line item exceeding 12 rows. if so, use *page up
        if counter >= 13.
          rows = counter MOD 13.
          istr = ( ( counter - rows ) / 13 ).
          do istr times.
            perform bdc_dynpro      using 'SAPLMEGUI' '0014'.
            perform bdc_field       using 'BDC_OKCODE'
                                    '=EINB_CREATE'.
          enddo.
          DO 2 TIMES.
            perform bdc_dynpro      using 'SAPLMEGUI' '0014'.
            perform bdc_field       using 'BDC_OKCODE'
                                    '=P+'.
          enddo.
          COUNTER = '03'.
          cstr = '03'.
        ENDIF.
        CONCATENATE 'EKES-EBTYP('  cstr  ')' INTO var.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                          var.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '/00'.
        PERFORM bdc_field       USING var
                                    utab-ebtyp.
        CONCATENATE 'RM06E-EEIND('  cstr  ')' INTO var.
        PERFORM bdc_field       USING var
                                       utab-eeind.
        CONCATENATE 'EKES-MENGE('  cstr  ')' INTO var.
        PERFORM bdc_field       USING var
                                       utab-menge.
        CONCATENATE 'J_3ASZDI-J_3ASIZED('  cstr  ')' INTO var.
        PERFORM bdc_field       USING var
                                       utab-j_3asize.
        AT END OF Ebelp.
          PERFORM bdc_dynpro      USING 'SAPLMEGUI' '0014'.
          PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=MESAVE'.
          perform bdc_dynpro      using 'SAPLMEGUI' '0014'.
          perform bdc_field       using 'BDC_OKCODE'
                                    '/00'.
          CALL TRANSACTION 'ME22N' USING bdcdata MODE 'E'.
          IF sy-subrc EQ 0.
            savedone = 'Y'.
            saveflag = 'Y'.
            initflag = 'N'.
            MESSAGE 'SAVED' TYPE 'I'.
          else.
            saveflag = 'N'.
            savedone = 'N'.
            initflag = 'Y'.
            MESSAGE 'Not Saved' Type 'I'.
          endif.
          CLEAR: bdcdata.
          REFRESH bdcdata.
        ENDAT.
      ENDLOOP.
    ENDFORM.
    Hope this will help u

  • Vendor confirmations in purchase order

    Hi friends,
    Iam using the fucntion module ME_CONFIRMATION_UPDATE to update the vendor confirmations table ie : EKES table
    Now iam able to succesfully update and insert new record in this table using the above function module.
    Now when i go to ME23N and give purhcase order number and at the item level in the confirmations tab i should see the updated entries of EKES table . but iam not able to see it..
    when i manually add a new line in the confirmations tab then i can see that entry in the EKES table.. how can i get the reverse process ie : when i add an entry in EKES table using the above function module it should reflect in the confirmation tab at the item level in ME22N.
    How can i do it.
    Regards
    Kumar

    Well, not much more I can say. This is the code I uam using for my specific case, hope that gives you some ideas for your case:
    lstr_item-acknowl_no = p_cnftxt.
      lstr_item-conf_ctrl = '0001'.
      lstr_itemx-acknowl_no = 'X'.
      lstr_itemx-conf_ctrl = 'X'.
      LOOP AT gtab_xekes_tmp INTO gstr_xekes_tmp.
        IF gstr_xekes-ebelp NE lv_ebelp AND sy-tabix > 1.
          lstr_item-po_item = gstr_xekes_tmp-ebelp.
          APPEND lstr_item TO ltab_item.
          lstr_itemx-po_item = gstr_xekes_tmp-ebelp.
          APPEND lstr_itemx TO ltab_itemx.
        ENDIF.
        lv_ebelp = gstr_xekes_tmp-ebelp.
      ENDLOOP.
      lstr_item-po_item = gstr_xekes_tmp-ebelp.
      APPEND lstr_item TO ltab_item.
      lstr_itemx-po_item = gstr_xekes_tmp-ebelp.
      APPEND lstr_itemx TO ltab_itemx.
      CALL FUNCTION 'BAPI_PO_CHANGE'
        EXPORTING
          purchaseorder = p_ebeln
        TABLES
          return        = ltab_bapiret
          poitem        = ltab_item
          poitemx       = ltab_itemx.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    /Leif

  • Purely iterative price in controlling area setting

    Dear Experts,
    Please let me know the use and implication of a tick " Purely iterative price" coming in Version setting of controlling area fiscal year wise (Txn Code OKEQ).
    Thanks in Advance for co operation
    Regards
    Rohit

    HI Waman,
    Thanks for the reply.
    I want to clarify some more doubts as follow:
    1)  How this iterative price is calculated means by which transaction code, Is it calculated at the time of automatic plan price calculation means thru KSS4 & KSPI..
    2) What is formula system uses to calculate this price, like plan price may be calculated based on Planned Cost /Planned Activity.
    3) Where we can see this price means in which Txn Code.
    4) As you have said that this cannot be used for revaluation, then what is the use, Is it only for Analysis purpose.
    5) Is there any other settings we have to do in activity master or any other,  to calculate the same.
    Thanks in advance for your cooperation.
    Regards
    Rohit Goel

  • Vendor Confirmation using BAPI

    Can anyone suggest me how to do vendor confirmation using BAPI

    Hi Asha ,
    ME22N is to change Purchase Order ? tell me what do u want to do ?
    <b>for what one u have to Create a program by using BAPI's to creates POs for a Given Vendor .In SAP these is no such functionality to create MASS PO's at a Time.</b>
    Regards
    prabhu

  • Vendor Evaluation - Price history

    Hi
    In vendor evaluation the score for the subcriteria Price History is not getting calculated.
    The scoring method that I have used is : Automatic Determ. from Purch. Statistics: Price Behavior
    What can be the reason? How it is calculated?
    Regards

    to determine how a vendor's price for a material has changed over the last few years, the material's price history is compared with the market price history.
    The system first checks whether the buyer has maintained the current market price and last year's market price for the material.
    If not, the system uses the price for the material group to which the material belongs.
    If this price is not maintained either, the system uses the effective prices from the previous year and the current year. Prices from standard purchase orders for materials and prices from subcontract orders are dealt with separately.
    The system then calculates the percentage variance between the old and new market prices.
    The vendor's effective price is re-calculated with this percentage variance. The result represents the effective price the vendor should be asking if his price had changed over time in the same way as the market price.
    This calculated effective price is then compared with the actual effective price, and a percentage variance is determined.
    The system then awards the vendor the score you have maintained in Customizing for this percentage variance.
    The system repeats this process for all the materials you procure from the vendor. Each time you start an evaluation, the system calculates the average score for all the materials. The result is the vendor's score for the subcriterion "Price History".

  • Vendor Confirmation fk08

    Hi,
           I am creating some new vendors, but everytime i create them or make some changes in them, then someone else has to confirm the changes by using TCODE FK08  before i can use the vendor in system. I just want to know that, is there any other way so that i can confirm the changes by myself. any report, any programme or any tables which i can use.
    Thanks

    The feature of vendor confirmation is given by SAP to avoid creation of incorrect and unauthorised vendors. which is why there is a maker and cheker rule for vendor master.
    Seems that you dont need this dual check functionality. Go to IMG menu
    FI - AP/AR - vendor account - master data - preparations for creation of master data - define sensitive fields for dual control.
    and remove the fields from here. After this you will not be asked to confirm the vendor
    Regds
    Pooja

  • ALE Vendor Confirmation (CREMAS)

    Hi,
    When a Vendor is created FK01 the ALE is settings done to send the Vendor code to another SAP system. But now it will be Unconfirmed in both the systems.
    (LFA1-CONFS and LFB1-CONFS will be '1')
    When the Confirmation is done using a different User in Sending system using FK08, this data is not ALED to the Receiving system. So we had to do Confirmation seperately in both the systems.
    As the IDOC type for CREMAS does not have a segment field for LFA1-CONFS and LFB1-CONFS (Confirmation status) we can create an Extension IDOC segment and send it.
    But I find that the standard ALE Inbound Function module IDOC_INPUT_CREDITOR does not have an option of Confirming.
    Its does only a XK01 or XK02 but not a FK08.
    Cause a confirmation can only be done using XK08 and that too with not with the user who had created the Vendor.
    Please mail me if any of you have done an ALE Automatic Vendor confirmation in the Receiving system.
    Thanks & Regards,
    Midhun.

    Hi,
    Check this Link for Create an Extension Type and a New Segment.
    http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi.jhtml
    Regards
    Appana

  • Updating Vendor Confirmations

    Hi,
    To update Vendor Confirmations manually in PO we first go for  cancellation of PO release then we will update VCs.
    Is it possible to update VCs without cancellation of PO release? If yes,pls explain the procedure.
    Note that We are not using EDI & IDOC.
    Regds

    hi,
    u can do it.
    u have to change the release iondicator from 1 to 3 or others related indiactor in customizing PO release strtagegy.

Maybe you are looking for