Payment Terms should come from vendor master data

When we create a new contract (ME31K) Z0NQ for the vendor  XYZ by default the payment terms that the contract retrieve is 1131, but in master data (XK03) for vendor XYZ I have payment terms 1011 defined.
I already checked it in Purchase organization and CCode level.
Please advise. Thanks!

It should come from vendor master only butmake sure that you are creating cintract based onthe RFQ or some use exit is avtive for that.

Similar Messages

  • Payment method not defaulting from Vendor master data

    Hi All
    I am running F110 payment run. In the Payment proposal SAP  is not pulling payment method from vendor master data for some invoice. we have like two payment methods , Sap is defaulting payment method for one type of payment method and not defaulting for the other...What could be the possible reasons?( for both the invoices We are not maintaining any payment method)

    Hi
    In F110 if payment methods are different from vendor master data and payment methods mentioned in parameters tab it will take payment methods from parameters tab, so that you have to give both payment methods in parameters tab so that it will consider both.

  • Payment Terms not copied from Vendor Master to PO

    Hello,
    PO was created for a Vendor and Vendor master has the correct payment terms but they did not get copied to the PO. 
    Thanks
    Megha

    Hi Megha,
    Did you maintain the payment terms in the Purchasing area of the vendor?
    SAP says
    Master records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
    Thanks
    Aravind

  • Get PO from vendor master data

    Hi,
    Those any body knows a BAPI or FM that would get the PO that was created in the IDOC from vendor master data?
    Please help...
    thank you...
    regards,
    mae

    Hi Mae,
    hope this may be of some help.
    REPORT zpo_bapi_purchord_tej.
    DATA DECLARATIONS *
    TYPE-POOLS slis.
    TYPES: BEGIN OF ty_table,
    v_legacy(8),
    vendor TYPE bapimepoheader-vendor,
    purch_org TYPE bapimepoheader-purch_org,
    pur_group TYPE bapimepoheader-pur_group,
    material TYPE bapimepoitem-material,
    quantity(13),
    delivery_date TYPE bapimeposchedule-delivery_date,
    net_price(23),
    plant TYPE bapimepoitem-plant,
    END OF ty_table.
    TYPES: BEGIN OF ty_alv,
    v_legs(8),
    success(10),
    v_legf(8),
    END OF ty_alv.
    TYPES: BEGIN OF ty_alv1,
    v_legf1(8),
    v_msg(500),
    END OF ty_alv1.
    *-----Work area declarations.
    DATA: x_table TYPE ty_table,
    x_header TYPE bapimepoheader,
    x_headerx TYPE bapimepoheaderx,
    x_item TYPE bapimepoitem,
    x_itemx TYPE bapimepoitemx,
    x_sched TYPE bapimeposchedule,
    x_schedx TYPE bapimeposchedulx,
    x_commatable(255),
    x_alv TYPE ty_alv,
    x_alv1 TYPE ty_alv1,
    x_alv2 TYPE ty_alv1.
    *-----Internal table declarations.
    DATA: it_table TYPE TABLE OF ty_table,
    it_commatable LIKE TABLE OF x_commatable,
    it_item TYPE TABLE OF bapimepoitem,
    it_itemx TYPE TABLE OF bapimepoitemx,
    it_sched TYPE TABLE OF bapimeposchedule,
    it_schedx TYPE TABLE OF bapimeposchedulx,
    it_alv TYPE TABLE OF ty_alv,
    it_alv1 TYPE TABLE OF ty_alv1,
    it_alv2 TYPE TABLE OF ty_alv1.
    DATA: po_number TYPE bapimepoheader-po_number,
    x_return TYPE bapiret2,
    it_return TYPE TABLE OF bapiret2,
    v_file TYPE string,
    v_temp(8),
    v_succsount TYPE i VALUE 0,
    v_failcount TYPE i VALUE 0,
    v_total TYPE i.
    DATA: v_temp1(5) TYPE n VALUE 0.
    DATA: x_event TYPE slis_t_event,
    x_fieldcat TYPE slis_t_fieldcat_alv,
    x_list_header TYPE slis_t_listheader,
    x_event1 LIKE LINE OF x_event,
    x_layout1 TYPE slis_layout_alv,
    x_variant1 TYPE disvariant,
    x_repid2 LIKE sy-repid.
    DATA : it_fieldcat TYPE TABLE OF slis_t_fieldcat_alv.
    SELECTION-SCREEN *
    SELECTION-SCREEN BEGIN OF BLOCK v_b1 WITH FRAME.
    *-----To fetch the flat file.
    PARAMETERS: p_file TYPE rlgrap-filename.
    SELECTION-SCREEN END OF BLOCK v_b1.
    AT SELECTION-SCREEN *
    AT SELECTION-SCREEN.
    IF p_file IS INITIAL.
    MESSAGE text-001 TYPE 'E'.
    ENDIF.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
    *-----To use F4 help to find file path.
    CALL FUNCTION 'F4_FILENAME'
    EXPORTING
    program_name = syst-cprog
    dynpro_number = syst-dynnr
    IMPORTING
    file_name = p_file.
    v_file = p_file.
    START-OF-SELECTION *
    START-OF-SELECTION.
    PERFORM gui_upload.
    LOOP AT it_table INTO x_table.
    PERFORM header_details.
    v_temp = x_table-v_legacy.
    LOOP AT it_table INTO x_table WHERE v_legacy = v_temp.
    PERFORM lineitem.
    PERFORM schedule.
    ENDLOOP.
    DELETE it_table WHERE v_legacy = v_temp.
    PERFORM bapicall.
    MOVE po_number TO x_alv-success.
    APPEND x_alv TO it_alv.
    CLEAR x_alv.
    *-----To clear the item details in internal table after the operation for a header.
    REFRESH: it_item,
    it_itemx,
    it_sched,
    it_schedx.
    CLEAR: v_temp1.
    ENDLOOP.
    v_total = v_succsount + v_failcount.
    PERFORM display_alv.
    FORM GUI_UPLOAD *
    FORM gui_upload .
    CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
    filename = v_file
    filetype = 'ASC'
    TABLES
    data_tab = it_commatable
    EXCEPTIONS
    file_open_error = 1
    file_read_error = 2
    no_batch = 3
    gui_refuse_filetransfer = 4
    invalid_type = 5
    no_authority = 6
    unknown_error = 7
    bad_data_format = 8
    header_not_allowed = 9
    separator_not_allowed = 10
    header_too_long = 11
    unknown_dp_error = 12
    access_denied = 13
    dp_out_of_memory = 14
    disk_full = 15
    dp_timeout = 16
    OTHERS = 17
    IF sy-subrc = 0.
    *-----To fetch the comma seperated flat file into an internal table.
    LOOP AT it_commatable INTO x_commatable.
    IF x_commatable IS NOT INITIAL.
    SPLIT x_commatable AT ',' INTO
    x_table-v_legacy
    x_table-vendor
    x_table-purch_org
    x_table-pur_group
    x_table-material
    x_table-quantity
    x_table-delivery_date
    x_table-net_price
    x_table-plant.
    APPEND x_table TO it_table.
    ENDIF.
    CLEAR x_table.
    ENDLOOP.
    ENDIF.
    ENDFORM. " gui_upload
    FORM HEADER_DETAILS *
    FORM header_details .
    MOVE 'NB' TO x_header-doc_type.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
    input = x_table-vendor
    IMPORTING
    output = x_table-vendor
    MOVE x_table-vendor TO x_header-vendor.
    MOVE x_table-purch_org TO x_header-purch_org.
    MOVE x_table-pur_group TO x_header-pur_group.
    x_headerx-doc_type = 'X'.
    x_headerx-vendor = 'X'.
    x_headerx-purch_org = 'X'.
    x_headerx-pur_group = 'X'.
    ENDFORM. " header_details
    FORM LINEITEM *
    FORM lineitem .
    v_temp1 = v_temp1 + 10.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
    input = v_temp1
    IMPORTING
    output = v_temp1.
    MOVE v_temp1 TO x_item-po_item.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
    input = x_table-material
    IMPORTING
    output = x_table-material.
    MOVE x_table-material TO x_item-material.
    MOVE x_table-quantity TO x_item-quantity.
    MOVE x_table-net_price TO x_item-net_price.
    MOVE x_table-plant TO x_item-plant.
    x_itemx-po_item = v_temp1.
    x_itemx-material = 'X'.
    x_itemx-quantity = 'X'.
    x_itemx-net_price = 'X'.
    x_itemx-plant = 'X'.
    APPEND x_item TO it_item.
    APPEND x_itemx TO it_itemx.
    CLEAR: x_item, x_itemx.
    ENDFORM. " lineitem1
    FORM SCHEDULE *
    FORM schedule .
    MOVE x_table-delivery_date TO x_sched-delivery_date.
    MOVE v_temp1 TO x_sched-po_item.
    x_schedx-delivery_date = 'X'.
    x_schedx-po_item = v_temp1.
    APPEND x_sched TO it_sched.
    APPEND x_schedx TO it_schedx.
    CLEAR: x_sched, x_schedx.
    ENDFORM. " schedule
    FORM BAPICALL *
    FORM bapicall .
    CALL FUNCTION 'BAPI_PO_CREATE1'
    EXPORTING
    poheader = x_header
    poheaderx = x_headerx
    IMPORTING
    exppurchaseorder = po_number
    TABLES
    return = it_return
    poitem = it_item
    poitemx = it_itemx
    poschedule = it_sched
    poschedulex = it_schedx.
    IF po_number IS NOT INITIAL.
    v_succsount = v_succsount + 1.
    MOVE x_table-v_legacy TO x_alv-v_legs.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    ELSE.
    v_failcount = v_failcount + 1.
    MOVE x_table-v_legacy TO x_alv-v_legf.
    MOVE x_table-v_legacy TO x_alv1-v_legf1.
    LOOP AT it_return INTO x_return.
    IF x_alv1-v_msg IS INITIAL.
    MOVE x_return-message TO x_alv1-v_msg.
    ELSE.
    CONCATENATE x_alv1-v_msg x_return-message INTO x_alv1-v_msg SEPARATED BY space.
    ENDIF.
    ENDLOOP.
    APPEND x_alv1 TO it_alv1.
    CLEAR x_alv1.
    ENDIF.
    ENDFORM. " bapicall
    FORM DISPLAY_ALV *
    FORM display_alv .
    PERFORM x_list_header.
    PERFORM build_fieldcat CHANGING x_fieldcat.
    x_repid2 = sy-repid.
    x_event1-name = 'TOP_OF_PAGE'.
    x_event1-form = 'TOP_OF_PAGE'.
    APPEND x_event1 TO x_event.
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
    i_callback_program = x_repid2
    is_layout = x_layout1
    it_fieldcat = x_fieldcat
    i_callback_user_command = 'USER_COMMAND'
    i_callback_top_of_page = 'TOP_OF_PAGE'
    i_save = 'A'
    is_variant = x_variant1
    it_events = x_event
    TABLES
    t_outtab = it_alv
    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. " display_master_data
    FORM USER_COMMAND *
    FORM user_command USING ucomm LIKE sy-ucomm selfield
    TYPE slis_selfield.
    READ TABLE it_alv INTO x_alv INDEX selfield-tabindex.
    CLEAR : x_alv2,it_alv2[].
    LOOP AT it_alv1 INTO x_alv1 WHERE v_legf1 = x_alv-v_legf.
    x_alv2 = x_alv1.
    APPEND x_alv2 TO it_alv2 .
    ENDLOOP.
    DATA : it_fieldcat TYPE slis_t_fieldcat_alv.
    DATA : x3_fieldcat LIKE LINE OF it_fieldcat.
    CLEAR : x3_fieldcat,it_fieldcat[].
    CLEAR x3_fieldcat.
    x3_fieldcat-col_pos = '1'.
    x3_fieldcat-fieldname = 'V_LEGF1'.
    x3_fieldcat-reptext_ddic = text-111.
    x3_fieldcat-ref_tabname = 'IT_ALV2'.
    APPEND x3_fieldcat TO it_fieldcat.
    CLEAR x3_fieldcat.
    CLEAR x3_fieldcat.
    x3_fieldcat-col_pos = '1'.
    x3_fieldcat-fieldname = 'V_MSG'.
    x3_fieldcat-reptext_ddic = text-112.
    x3_fieldcat-ref_tabname = 'IT_ALV2'.
    APPEND x3_fieldcat TO it_fieldcat.
    CLEAR x3_fieldcat.
    x_layout1-colwidth_optimize = 'X'.
    x_layout1-zebra = 'X'.
    IF it_alv2[] IS NOT INITIAL.
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
    i_callback_program = x_repid2
    is_layout = x_layout1
    it_fieldcat = it_fieldcat
    i_save = 'A'
    i_callback_top_of_page = 'TOP'
    is_variant = x_variant1
    it_events = x_event
    TABLES
    t_outtab = it_alv2
    EXCEPTIONS
    program_error = 1
    OTHERS = 2.
    ENDIF.
    ENDFORM.
    FORM USER_COMMAND *
    FORM top.
    CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
    it_list_commentary = 'Commentry'.
    ENDFORM.
    FORM BUILD_FIELDCAT *
    FORM build_fieldcat CHANGING et_fieldcat TYPE slis_t_fieldcat_alv.
    DATA: x1_fieldcat TYPE slis_fieldcat_alv.
    CLEAR x1_fieldcat.
    x1_fieldcat-col_pos = '1'.
    x1_fieldcat-fieldname = 'V_LEGS'.
    x1_fieldcat-reptext_ddic = text-108.
    x1_fieldcat-ref_tabname = 'IT_ALV'.
    APPEND x1_fieldcat TO et_fieldcat.
    CLEAR x1_fieldcat.
    x1_fieldcat-col_pos = '2'.
    x1_fieldcat-fieldname = 'SUCCESS'.
    x1_fieldcat-key = 'X'.
    x1_fieldcat-reptext_ddic = text-109.
    x1_fieldcat-ref_tabname = 'IT_ALV'.
    APPEND x1_fieldcat TO et_fieldcat.
    CLEAR x1_fieldcat.
    x1_fieldcat-col_pos = '3'.
    x1_fieldcat-fieldname = 'V_LEGF'.
    x1_fieldcat-key = 'X'.
    x1_fieldcat-reptext_ddic = text-110.
    x1_fieldcat-ref_tabname = 'IT_ALV'.
    APPEND x1_fieldcat TO et_fieldcat.
    CLEAR x1_fieldcat.
    ENDFORM. " build_fieldcat
    FORM BUILD_LIST_HEADER *
    FORM x_list_header.
    DATA: x_list_header1 TYPE slis_listheader.
    *-----List Header: type H
    CLEAR x_list_header1 .
    x_list_header1-typ = 'H'.
    x_list_header1-info = text-105.
    APPEND x_list_header1 TO x_list_header.
    *-----List Key: type S
    x_list_header1-typ = 'S'.
    x_list_header1-key = text-106.
    x_list_header1-info = v_total.
    APPEND x_list_header1 TO x_list_header.
    *-----List Key: Type S
    CLEAR x_list_header1 .
    x_list_header1-typ = 'S'.
    x_list_header1-key = text-107.
    x_list_header1-info = v_succsount.
    APPEND x_list_header1 TO x_list_header.
    ENDFORM. " build_list_header
    FORM TOP_OF_PAGE *
    FORM top_of_page.
    CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
    it_list_commentary = x_list_header.
    ENDFORM. " TOP_OF_PAGE
    cheers,
    Hema.

  • Payment done without confirmation of vendor master data

    I have an issue with sensitive fields. A payment was done without confirmation of vendor master data.
    F110 , FK09  transaction is used.
    Without approving the payment, it is cleared. Although it should show Account blocked for payment run.
    Are there any notes which can be applied. This is 46C system?

    check view V_T055F
    and read docu to tcode FK09!
    A.

  • Error while creating money market transaction - payment details not retrieving from BP master data.

    Hello friends
                      I have error while creating financial transaction. Payment details are not retrieving from BP master data to creating financial transaction screen.
    No payment details entered for transaction
    Message no. FTR0030
    Please advise to set off this.
    Thanks & Regards
    Swami

    Dear Swami,
    Please select one payment details in Business partner and use assigned tab from top selection parameter from standing instruction to assigned bank details to product type.
    It will open other window like above example for each product of treasury, then assign bank details to product. Once assigned and save.
    System will pick payment details in deal automatically based on business partner.
    Hope this solve your issue.
    Regards,
    Jain
    Message was edited by: Jain Varghese

  • Vendor payments using bank info from HR master data

    Dear experts,
    We have setup all employees as vendors in FI to make reimbursements.
    Can we use the banking information in HR master data (IT0009) and make the vendor payments in FI. We don't want to maintain bank information in vendor master.
    So, by entering the personnel number of the EE in the vendor master, can SAP integrate and read the banking information from the HR master data?
    Please let me know if this is possible and how.
    regards,
    vishal.

    You have to maintain bank data for vendors and employees separately.  Vendor master cannot access bank data in payroll module.  Use LSMW to populate bank data in XD02 and establish a process to update bank information whenever there are changes in payroll side.

  • Payment terms in PO and vendor master

    PO should be able to override payment terms of the vendor master when a payment term in PO is different from the payment term in vendor master.How do I make it work?
    Regards - SS

    Payment trerm of the PO can not be overwrite the payment temr of the vendor master becuase the vendor master is master data and Po is transaciton data.
    you can over write the payment term of the vendor master defualted in the PO but not other way around.

  • Retrieving text from Vendor Master data

    Hi All,
    Please go through the navigation and query next to that...
    Vendor Master Change/ Display(XK02/XK03) --> Provide any Vendor number already created --->
    select the General Data ---> select Payment Transactions --> press enter to view the data -->
    Goto Menu Extras --> select texts  --> a window will pop up giving 2 rows for entering text as mentioned below.
    Accounting note
    Purchasing memo         
    We can enter the text beside the provision 1st line  else we can double click any one of them so that we will enter into a window to enter the long text or anything necessary.
    Now that in this concern my requirement is that i want to retrieve the text entered under the 1st line  or in the window which comes after double clicking Accounting note or Purchasing memo option basing on Vendor number or any other parameter or if any table where this data gets stored.
    Is there any program required to retrieve this text or any Function Module which retrieves this text or any coding avaliable please do send me as it is a very urgent requirement ....
    regards
    PSNG

    Could you please let me know, How to check through that FM as the parameters are confusing me when i went through them?
    regards
    PSNG

  • Payment Terms on PO Header is not coming automatically from vendor master

    Hi Experts,
    I have two plants maintained as vendors in my system. Both have payment terms maintained in the Vendor master (Purchasing as well as Payment Transaction view) but when I create POs (all with the same document type), for one of the vendors, payment terms is being populated automatically on PO header whereas for the other vendor, it does not pupulate automatically.
    I am wondering if there is any other setting controlling this payment term apart from the Vendor master Payment Term.
    Please guide.
    Thanks.

    These plants are under different companty codes. We have custom document type ZNB for the PO. Do I need to check something in Purchasing Info Record or if any other thing setting controlling it.
    Both the vendor masters have the payment terms maintained exactly the same. But, still I am facing the issue.
    Thanks.

  • Payment terms in Vendor Master data and purchasing info record

    Hi, all, I met one trouble. While I create Purchase Order. In the header item, payment terms is automatically pop up from the data maintaining the vendor master data or purchasing info record if there is difference payment terms between in vendor master data and in purchasing info record. What happend?
    Sometimes, When you create purchase order, payment terms is not automatically pop up even you maintained in the vendor master data or purchasing info record. Why? Is it meaning that I can manually to input payment terms while create each purchase order which can be difference data with vendor master data or purchase info record?
    Thank you very much in advance,

    Hi,
    The payment terms is usually defaulted from either vendor master or purchasing master data record such as contract/outline agreement.  Unless it is set through configuration that the payment terms be set as mandatory, any failure to maintain payment terms won't stop you from posting your PO as this information will only be useful during invoice receipt maintenance.  Having said that if you are setting up your system with discount condition type as part of your PO pricing schema then it is necessary that the payment terms shall be maintained during PO creation.
    Cheers,
    HT

  • Can payment terms on AP invoice always defaults from Vendor Master

    Can payment terms on AP invoice always defaults from Vendor Master

    It defaults from vendor master in the purchase order and that carries forward to invoicing. But you can then change the terms in PO and those terms would be effective for subsequent invoicing.
    Just FYI.. master data payment terms in company code segment defaults to FI invoicing, payment terms in purchasing segment defaults to purchasing based invoice (MIRO).
    Hope it helps.
    Thanks.
    Rahul

  • Payment Terms modified in Vendor master data

    Hi,
    I feel enduser have modified the payment terms in the vendor master data. kindly let me know how to check which user have modified.
    Rdgs

    hi SAPFICO,
    GO to FB03 and Select the document number and Go to the Menu
    ENVOIRNMENT--> Document Changes here you can see who has changed the document and also the date....
    Hope this will helps u...
    Cheers 
    Ranjit

  • Default Payment terms from Vendor Master not from Reference PO

    Hello guys,
    I am creating a PO in reference to another PO and payment terms are copied from the old PO but not updating from Vendor Master. Our payment terms are changed very frequent and our users don't want to create a new PO with too many line items so they just copy an old PO.
    IS there a way to update payment terms form Vendor Master after copying an Old PO? I know this is pretty standard functionality but just trying to see if we can trick the system,
    Thanks
    Ronnie.

    If so then convert this into an error message ensuring that the correct payment term to appear in the message, that the users need not search themselves and find out for updating the payment term
    One thing is that there is no configuration available for you take care of this automatically, there has to be user exit solution.

  • Header data not coming from vendor master when creating SA using BAPI

    Hello,
    I am creating SA using BAPI_SA_CREATE. I am passing the vendor code and other header related data in the header table of the BAPI.
    SA is created successfully with all the data that is passed to the BAPI. Now if the payment term and inco terms data is passed initial to BAPI then this data is not taken from vendor master. This data appears blank in SA.
    Shouldn't this data be picked up from vendor master as they are maintained properly in vendor master?
    I just need confirmation whether BAPI picks or not from vendor master if the data (payment term and inco terms) passed is initial.
    Thanks and Regards,
    Saba

    Hi,
    Are u passing X to corresponding fields of HEADER structure what ever you have populated in HEADER structure .

Maybe you are looking for