F110 - Payment posting in BSEG towards REGUH information - HBKID and HKTID

Hello,
I am making investigation on the payment program (and includes) linked to the F110 transaction.
I have made a proposal and the payment thanks to the F110 transaction and i have activated in facultative House Bank HBKID and Account ID HKTID on Bank accounts.
I can see on REGUH that the program is able to fill the two data fields (HBKID and HKTID) on the vendor open item.
Yet when i go to BSEG, i only get the HKTID data field populated on both items whereas on the GL item (the transitory bank account) nothing is populated.
Could anyone tell me where is the include or the part of the program in the F110 program where i can understand why is it the case ?
Thank you in advance,
G/L     Vendor     PM     House Bk     BnkT     Profit Ctr     Alt.acct     Acct ID     G/L amount
40110010     442866     T     AXI02          1423     401100     AXI01     10 000,00
51000977                                   AXI01     10 000,00
Best regards

Hi FI Sap,
You can maintain this field in OB32 T code to make the document line item changes. Give Account type as D for customers or K for vendors accordingly. And also select field can be changed option under possibility of changing the field tab.
I hope it helps else revert us with your query.
Thanks & Regards,
Lakshmi S

Similar Messages

  • Copy BSEG SGTEXT in Payment Run (F110) to Payment Posting Document

    Hi,
    Client creates a Vendor Invoice using F-43 and they are entering in Text on each line (BSEG-TEXT).  They then run F110 to produce payment and they wantt the BSEG-TEXT field from the Vendor Invoice Document to be copied to the Payment Posting Document BSEG-TEXT field.
    Is there a user exit in SAPF110V or SAPF110S that can be used or is there some other method?
    Thanks

    Please check by giving sort key 24 - document header text in Bank Gl Account master data

  • Duplicate payments in Payment list of F110 payment run

    Hello all,
    We had run APP trhu F110 payment run was as expected with amount 100000 EUR but when we checked payment list (EDIT- Payment - Payment list) there are duplicate entries and total is showing as 200000 EUR.
    Following are onservations
    1) In SAP posting made correctly to all vendors with a total of 100000 EUR. So no double payments posted in vendor account 
    2) Payment list is showing amounts with a doument numbers. Duplicate payments also having document numbers but which are not exists in SAP
    3) Documents posted with doc type ZP in sap is not in serial i.e 1,2,3,4 Its posted like 1,3,5,7... the document no 2,4 can be seen in the payment list
    4) Also I checked log for the payment run and I found one warning message as "Check whether a duplicate payment medium has been created"
    5) Also status of payment run is "Posting orders: 1,174 generated, 605 completed"
    6) I also checked setting in FBZP which is also correct
    We need to correct the DME file with correect postings
    If anyone has faced issue then please share your inputs
    Thanks & regards

    Dear Rajan,
    the payment document validation works as follows:
    If you select this parameter, a form is only printed if the related
    payment document has already been posted.
    Note that it is not advisable to schedule the payment program and the
    data medium programs to run at the same time, if you want the system to
    be able to carry out validation of the payment documents - because the
    system does not start posting the documents at the same time as the
    program runs, and in order to ensure that the payment program generally
    finishes its run before all the payment documents have been posted, the
    payment medium program (started after the payment program) would display
    in the error list any documents that have not (yet) been found.
    As a result double payments are not possible as no payment media is
    created if the payment document is not posted. The items are still
    open and are selected in the next payment run again.
    If the payment document validation is not used, the payment media is
    created but the open item is not cleared as the payment document is
    not posted. In this case you have to clear the open items manually
    (if a repeat update is not possible) to avoid double payments.
    dear Prashant,
    It is normal that if the automatic payment does not pay all the items, You can find them hanging into sm13.
    However, in general, when this happens you could try to use the edit >
    payments > after termination > draw up again option, if it is
    available.  If there is an entry in SM13, as in Your case, you should process it.
    But sometimes the System does not allow to do it.
    Anyway the only problem I can see is the one reported by the note 545340:
    When the payment program is terminated, it may be the case that not all
    payment documents exist on the updated database while the entries
    already exist in the tables REGUH and REGUP. However, this basic
    procedure has the advantage that the payment media can already be
    created for the purpose of fast forwarding to the bank when for example
    the payment documents update is delayed.
    For this problem please refer to the Note 545340 point [4]
    that answers to it.
    Furthermore please be aware that:
    as I told You in the beginning, If the payment program does not pay
    all the invoices contained into the payment proposal, It will depend on
    the fact that during the payment proposal run time and the payment
    proposal time, something changed respect one of the selected invoices.
    This means that one document number was NOT posted even if It is
    contained in the tables REGUH and REGUP.
    Please be informed payment data tables REGU* are used by only payment
    program and no need to take any corrective action and should not be a
    problem with auditors.
    So You can pay the invoices manually or by the next automatic payment
    run without any problem.
    I hope now the System behaviour is more clear.
    Mauri

  • F110 payment run - Plant wise

    Dear All,
    We have a  scenario where clients is having five plants under one legal entity.
    Client wants F110 payment run  separately for all vendor invoices specific to the plant.
    For all plants , there are separate bank accounts and respective invoice must go to plant specific bank account as this is legal requirement of the country.
    Could you please let me know configuration steps to manage this scenario.
    Also can you let us know, how can we make payment to selected Vendors in F110 ( additional field tab).
    In paramater tab,we have the option to incorporate the selected vendor codes.
    In additional field tab,we have only 3 row with a range of Vendor codes.
    Now i want to make payment to 50 vendors(specific to one plant) the vendor codes are 001,18,58,193,etc......how can we do this  while we run the payment program.
    Do suggest
    Regards

    When you are posting an invoice, some field in the invoice document must have plant information. Based on that you can substitute the House Bank. Lets say for example, You enter the value "Plant1" in the Assignment field of the vendor invoice. and you want to pay Plant1 invoices through house Bank HBK01. Then your should create a substitution rule saying if the value in say assignment field is "Plant1" then substitute House Bank field in the vendor line with value HBK01. If you are using a dedicated vendor number ranges specific to plant, then you can do the house bank substitution based on vendor ID as well, and then you don't have to enter Plant info in the invoice.
    Then all the invoices will have right house bank data. Now to make sure that you are paying to vendor posting specific to a plant in the payment run. You can go to FREE SELECTION tab of payment run(F110) when you enter parameters, and in the drop down under field name double click others option and select the document and enter. and then select and enter the field that you are using to enter plant information. In my example I have used Assignment field to enter plant information. So, I will select BSEG-ZUONR. Then I will go to Values field and enter "Plant1". Then Payment run will pick up only "Plant1" invoices.
    If you already using some rules to enter the house bank in the invoice, then you might not want to use the substitution rule. But find out which field in the vendor invoice has plant infomation, and select that field as i have shown above though FREE SELECTION.
    Thanks
    ROn

  • F110 Payment Run Idoc

    I have the partner profile setup for F110 Payment run.
    I have added the message types : REMADV for the basic type PEXR2002.
    I also have added : PAYEXT for PEXR2002.
    The Payment run generates the Idoc successfully. PAYEXE IDoc is generated.
    I want to actually generate REMADV Idoc as per my functional requirement.
    Question:
    1. Whats the difference if Both are pointing to same Basic Type - PEXR2002 ?
    2. What should I do to generate REMADV and Not PAYEXT?
    3. Any configuration that decides the idoc type?
    FYI - The payment method configured for all this is "E" - BACS Payment.
    Any help would be appretiated.
    Pranali

    Hi ,
    check this blog  http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a00afa41-4254-2d10-74a5-bd560edf74da?quicklink=index&overridelayout=true
    IDOC Configuration steps for EDI
    IDOC Information
    IDOC type: PEXR2002
    Message type: REMADV
    Function Module: IDOC_INPUT_REMADV_CTR
    Process code: REMC
    Process
    When an inbound Payment advice is received, it will create a payment and clearing AR document with the document type set up in the config below.
    Config
     Define posting rule in SPRO->FI->Bank accounting ->Business Transactions ->Payment transactions ->manual bank statement->define posting keys and posting rules
     Assign company code to EDI payments in SPRO->FI->AR and AP ->Bus Transactons->Incoming Payments->Electronic->Payment Advice Notes->Assign company codes for EDI payment advice notes.
     Define Payment advice type 06 in SPRO->FI->AR and AP ->Bus Transactons->Incoming Payments->Electronic->Payment Advice Notes->Define Further processing with account type D.
    Prabhudas

  • Withholding Tax Type for Payment Posting - Customer Accumulation -

    We are using the Withholding Tax Type for Payment Posting for customer with the accumulation per month and checking the minimum/maximum withholding tax base amount to calculate the tax.
    When we run the F110 transaction (Automatic Payment) the system creates a BIll of Exchange as Noted items and keep the accounting document created from the SD opened. After the customer pay the bill, the bank send a file informing the payment, then we clearing the accounting document. 
    But the system updated the WITH_ITEM Table and filled the fields AUGBL(Clearing Document) and AUGDT (Clearing Date) with the number and date of the BIll of Exchange that was created during the F110 running.
    I am confused about this situation because according the Withholding Tax Type for Payment Posting, the system only could updated the table  WITH_ITEM  with an accounting document. Noted items are not an accounting document.
    I would like to konw if the system is working properly, or can have something wrong in our configuracion?
    Thanks and regards
    Augusto

    Hi ,
    In some countries there is requirement that you need to deducted Withholding tax either at time of Invoice or payment which ever is ealier . so if you get Invoice first then you deduct the Withholding tax on Invoice and define the tax type and assign to company . but if you make paymnet first which we called advance or down payment then we configure Withholding tax on payment .
    If a vendor is liable for withholding tax on invoice it may be liable for payment as well if you think you may pay some advances .
    Please let me know if you need more information

  • Reverse one item after F110 payment

    Dear ALL:
    is it possible to reverse one item after F110 payment?
    it seems when I reset and reverse the payment document for this line item, the table REGUH still has this line items record, if I delete the output for this , it will delete all the items, is it possible to delete the output of one item after f110_payment has been posted?
    thanks very much

    Hello,
    The other option is to use FBRA (reset cleared items) transaction.
    You can reverse and reset a payment clearing document with this Tcode.
    Please note, if there was more than one invoice included in the clearing, all those will be reversed.
    Regards,
    Endre

  • F110  Payment Run

    I am having a problem with F110 Payment run. It's showing the error as: 'Item cannot be paid due to inconsistent withholding tax'. I have done the payment run for the same vendor, same company code and it worked well. Later, I deleted one of the WH Tax type in Vendor Master. Has anyone come across this or similar issue?. What can I do to solve this?.

    hi,
      I am not able to see the Deleted WH Tax info. when I run the RFWT0010. I tried to do the payment run after executing RFWT0010, but am not able to resolve the problem. I have run the S_P00_07000134(the 1099 report) a few days back(before posting the new Invoices). Do you think this has anything to do with the existing problem. And I have checked the config. again for the tax type, Tax codes and their assignments to Co.Cd. which everything seems to be correct. I tried to pay using f-53 which is showing the same error.
    As Hein said i tried to look in the Invoice doc. for the WHTax info.(I have the setting to do calculate the WHTax amount @ the Payment level). So, its not possible to delete the Tax code and make the settings in VM.
    As per suresh, I have checked the validity of the tax code its(1/1/2000-12/31/9999). And the tax type, tax code are assigned in the VMR.
    I am not able to resolve this. Has anyone come across the same/similar issue and resolved it?.

  • System shut down during F110 payment run

    During the F110 payment run, the PRD system shut down. There were 259 items in the proposal and according to the status 42 posting orders were generated and completed. What is the process to handle this problem? Can the payment run be re-started?
    It appears that clearing documents were created for some open items before the system shut down but no checks are showing in the check register. Has this happened to anyone before and what steps should be taken to resolve this?

    Is it a matter of...
    1. deleting the output of the payment run,
    2. deleting the proposal
    3. canceling the the payment check by check using FCH8 if any occurred
    4. reseting and reversing the clearing documents created using FBRA before the system shut down
    5. start a new payment run

  • Reference field value in the F110 Payment document

    Dears
    We are running the automatic payment run for the vendor invoices posted.
    In each vendor invoice, we have filled the reference field, text field, etc.  However, while running the payment in F110, the system does not reproduce this reference field value in the payment document.  Hence we are not able to match the items for comparison.
    Have we left out any setting in FBZP or somewhere ?

    Hello,
    Apart from above suggestions, you can check linked invoices to payment document through below option.
    Open payment document in FB03, go to Menu->Environment->Payment usage
    This will list all invoices cleared through that payment document.
    If you are looking for tables, Pass payment document number , company code, year, account type and account to AGKO table and get the clearing date. Pass these details to BSAK and get list of cleared documents.
    AUGDT = Clearing date from AGKO
    AUGBL= Clearing document from AGKO
    and other details passed earlier.
    Hope this helps.
    Thanks,
    V V

  • F110 payment run - split on invoice line item that exceed certain amount

    Dear expert,
    Now i want to ask is there any ways to configure F110 - payment run to auto checking on whenever the amount of one fi document is more than USD100,000 will auto split to second payment item.
    *i have already tick individual pmnt on tcode FK02 - change vendor master data (at automatic payment transactions column). This method will split all fi document under same vendor post with different posting document number.
    I would like to ask is there any way to configure auto split on the fi document (if the document is exceed some amount) for payment run.
    thanks and appreciate

    i have put distribution amount.
    Let say i put distribution amount USD100, after i run payment run, one account payable document will generate one payment document.
    As what i want is- if the ap document is USD 200, then the payment document will generate two payment document.
    Coz my enquiry is if the payment is excedd USD100 we need to assign to another tt payment as the TT is only accept maximum USD100 transfer.
    Expert, please advice on ur view.
    Thanks and appreciate much on ur previous help.
    regards,
    Ng Chong Chuan

  • F110- Payment advices for vendor - SAP standard solution

    Hello all,
    I would like to generate Payment advices via Idoc to the vendor in a standard way ( no ABAP), can I use the program RFFOUS_C ( assigned in Payment method company code ) and generate the idoc payment advices via RFFOAVIS?
    I canu2019t create the payment advices with the above programs, here what I have done so far
    1) Vendor master checked with the EDI flag
    2) FBZP is configured, assigned the RFFOUS_C
    3) Variant setup for RFFOAVIS
    4) Payment posted correctly but in the output its is saying " No row selected"
    We are using classic payment medium.
    Thanks in advance for your help

    Have you created right variant in your parameters in F110. Otherwise, no advice will be created.
    have you checked your FBZP settings, you must allow the generation of payment advice.
    Are you looking into SP02 for payment advice.

  • Run F110 Payment Proposal in Custom Z Report

    Hi Folks,
    I have a requirement to run payment proposal part of the F110 transaction from a Z program without having to create a payment proposal.
    It's a little tricky to explain so I will try to say it in these terms:
    My desired output is the "Display Payment Proposal: Payments" table that can be viewed by clicking Display Proposal button in F110.
    My desired input is Company Code, Pament Methods, Next Payment Date and the list of Vendors (i.e. the values that are entered when creating the payment parameters.)
    So, is this achieve able without going through tons of F110 code to replicate the functionality.
    Many thanks for any help,
    Colm

    I created a function module to do the work. Hopefully somone finds it useful
    FUNCTION z_run_dummy_pay_proposal.
    *"*"Local Interface:
    *"  IMPORTING
    *"     REFERENCE(I_LAUFD) TYPE  F110V-LAUFD
    *"     REFERENCE(I_ZWELS) TYPE  F110V-ZWELS
    *"     REFERENCE(I_NEDAT) TYPE  F110V-NEDAT
    *"     REFERENCE(I_LAUFI) TYPE  F110V-LAUFI
    *"  EXPORTING
    *"     REFERENCE(EXCEPTION) TYPE  CHAR255
    *"  CHANGING
    *"     REFERENCE(T_LIFNR) TYPE  ZTT_LIFNR
    *"     REFERENCE(T_BUKRS) TYPE  ZTT_BUKRS
    *"     REFERENCE(T_REGUH) TYPE  ZTT_REGUH
    *"     REFERENCE(T_REGUP) TYPE  ZTT_REGUP
    *"     REFERENCE(T_BSIK) TYPE  ZTT_BSIK
      DATA: ls_rfdt TYPE rfdt, "Cluster Table that stores the Payment Parameters
            lv_seconds TYPE i, "Seconds used to control the wait time
            ls_lifnr TYPE lifnr,
            ls_bukrs TYPE bukrs.
    *RFTD table is the parameter cluster table  for F110 amoung others
      CONSTANTS: lc_relid TYPE rfdt-relid VALUE 'FB', "CHAR02 data element for SYST from RFDT table
                 lc_parm TYPE c LENGTH 4 VALUE 'PARM', "Constant value to pass into the RFDT table
                 lc_f110 TYPE c LENGTH 4 VALUE 'F110'. "Constant value to pass into the RFDT table
    *The values are needed to store the parameters correctly in the Parameter Cluster Table
      f110v-laufd = i_laufd.
      f110v-laufi = i_laufi.
      f110c-budat = i_laufd.
      f110c-grdat = i_laufd.
      rfdt-mandt = sy-mandt.
      rfdt-relid = lc_relid.
      CONCATENATE lc_f110 i_laufd i_laufi lc_parm INTO rfdt-srtfd.
      f110id-progr = lc_f110.
      f110id-laufd = i_laufd.
      f110id-laufi = i_laufi.
      f110id-objkt = lc_parm.
    *Build up the Vendors that are being stored in the parameters
      LOOP AT t_lifnr INTO ls_lifnr.
        r_lifnr-sign = 'I'.
        r_lifnr-option = 'EQ'.
        r_lifnr-low = ls_lifnr.
        APPEND r_lifnr.
      ENDLOOP.
    *Build up the Company Codes that are being stored in the parameters
      LOOP AT t_bukrs INTO ls_bukrs.
        fkttab-bugrp = sy-tabix.
        fkttab-zwels = i_zwels.
        fkttab-nedat = i_nedat.
        fkttab-bukls = ls_bukrs.
        fkttab-xpruf = 'X'.
    *To match the SAP standard I put in 6 blank lines
        APPEND fkttab.
        CLEAR fkttab.
        APPEND fkttab.
        CLEAR fkttab.
        APPEND fkttab.
        CLEAR fkttab.
        APPEND fkttab.
        CLEAR fkttab.
        APPEND fkttab.
        CLEAR fkttab.
        APPEND fkttab.
        CLEAR fkttab.
        APPEND fkttab.
      ENDLOOP.
      LOOP AT fkttab WHERE bugrp IS NOT INITIAL.
        buktab-bukrs = fkttab-bukls.
        buktab-bugrp = fkttab-bugrp.
        SELECT SINGLE land1
          FROM t001
          INTO buktab-land1
          WHERE bukrs = fkttab-bukls.
        SELECT SINGLE zbukr
          FROM t042
          INTO buktab-zbukr
          WHERE bukrs = fkttab-bukls.
        APPEND buktab.
      ENDLOOP.
    *Use the SAP standard to format the Vendors
      PERFORM selektion_lifnr.
    *Create the Payment Parameters
      PERFORM sichern.
    *Commit the work and wait for the Payment Parameters to be written to the database
      COMMIT WORK AND WAIT.
    *Wait up to 4 minutes for the Payment Parameters to be created, if they aren't after
    *4 minutes raise an exception
      CLEAR lv_seconds.
      DO 240 TIMES.
        SELECT SINGLE *
          FROM rfdt
          INTO ls_rfdt
          WHERE relid = lc_relid
          AND srtfd = rfdt-srtfd.
        IF sy-subrc = 0.
          EXIT.
        ELSE.
          WAIT UP TO 1 SECONDS.
          lv_seconds = lv_seconds + 1.
          IF lv_seconds = 240.
            exception = 'parameter_create_failed'. "Old and new exceptions cannot be used at the same time
            EXIT.
          ENDIF.
        ENDIF.
      ENDDO.
    *Once the payment parameters have been created we can create a payment proposal
      CALL FUNCTION 'SCHEDULE_PAYMENT_PROPOSAL'
        EXPORTING
          i_laufd           = i_laufd
          i_laufi           = i_laufi
          i_xstrf           = 'X' "Create immediatly
        EXCEPTIONS
          startdate_wrong   = 1
          parameters_missed = 2
          lock_failed       = 3
          job_open_failed   = 4
          job_close_failed  = 5
          OTHERS            = 6.
      IF sy-subrc <> 0.
        exception = 'proposal_create_failed'. "Old and new exceptions cannot be used at the same time
      ENDIF.
    *Trigger the Job
      COMMIT WORK AND WAIT.
    *Clear out the tables that are used to store the cluster table
    *values for the parameters
      REFRESH: buktab, fkttab, slktab, sldtab, trctab, usrtab,
               faetab, jobtab.
      CLEAR:   buktab, fkttab, slktab, sldtab, trctab, usrtab,
               faetab, jobtab, f110c,  trcopt, f110versionpar.
    *Import the Payment Parameters Values
      IMPORT buktab fkttab slktab sldtab trctab usrtab
             faetab jobtab f110c  trcopt f110versionpar
             FROM DATABASE rfdt(fb) ID f110id.
    *Check to see has the job finished
      CLEAR lv_seconds.
      DO 240 TIMES.
        READ TABLE jobtab INDEX 1.
        SELECT SINGLE *
          FROM tbtco
          WHERE jobname = jobtab-jobname
          AND jobcount = jobtab-jobcount
          AND status = 'F'.
        IF sy-subrc = 0.
          EXIT.
        ELSE.
          WAIT UP TO 1 SECONDS.
          lv_seconds = lv_seconds + 1.
          IF lv_seconds = 240.
            exception = 'proposal_create_failed'. "Old and new exceptions cannot be used at the same time
            EXIT.
          ENDIF.
        ENDIF.
      ENDDO.
    *Store the Payment Proposal Header Values
      SELECT *
        FROM reguh
        INTO TABLE t_reguh
        WHERE laufd = i_laufd
        AND laufi = i_laufi.
    *Delete the values where no payment will be made
      DELETE t_reguh WHERE vblnr IS INITIAL.
    *Store the Payment Proposal Line Item Values
      SELECT *
        FROM regup
        INTO TABLE t_regup
        FOR ALL ENTRIES IN t_reguh
        WHERE laufd = t_reguh-laufd
      AND laufi = t_reguh-laufi
      AND xvorl = t_reguh-xvorl
      AND zbukr = t_reguh-zbukr
      AND lifnr = t_reguh-lifnr
      AND kunnr = t_reguh-kunnr
      AND empfg = t_reguh-empfg
      AND vblnr = t_reguh-vblnr.
    *Get the relevant Outstanding Payment to Vendors Values
      SELECT *
        FROM bsik
        INTO TABLE t_bsik
        FOR ALL ENTRIES IN t_regup
        WHERE bukrs = t_regup-bukrs
      AND lifnr = t_regup-lifnr
      AND umsks = t_regup-umsks
      AND umskz = t_regup-umskz
      AND zuonr = t_regup-zuonr
      AND gjahr = t_regup-gjahr
      AND belnr = t_regup-belnr
      AND buzei = t_regup-buzei.
    *Delete the Payment Proposal
      CALL FUNCTION 'DELETE_PAYMENT_PROPOSAL'
        EXPORTING
          date                = i_laufd
          identification      = i_laufi
        EXCEPTIONS
          abnormal_end        = 1
          no_delete_authority = 2
          OTHERS              = 3.
      IF sy-subrc <> 0.
        exception = 'proposal_delete_failed'. "Old and new exceptions cannot be used at the same time
      ENDIF.
    *Delete the Payment Parameters
      CALL FUNCTION 'DELETE_PAYMENT_PARAMETERS'
        EXPORTING
          i_laufd           = i_laufd
          i_laufi           = i_laufi
          i_inter           = space
        EXCEPTIONS
          no_authority      = 1
          parameters_missed = 2
          wrong_status      = 3
          OTHERS            = 4.
      IF sy-subrc <> 0.
        exception = 'parameter_delete_failed'. "Old and new exceptions cannot be used at the same time
      ENDIF.
    ENDFUNCTION.
    Edited by: Colm Gavin on Apr 15, 2011 12:22 PM

  • F110 - Payments

    Hi!!
    I would like to see if anyone could provide me with some info regarding the following
    I have a problem when I run outgoing payments through F110.
    I created a new payment method and posted two vendor invoices using this method.
    When I run F110... for outgoing payments, I select one of two pending invoice and generate a payment document.
    If I run F100 again, for the same vendor, the trx  shows the two vendor invoices in the proposal. This is an error
    cause the invoice that has been cleared should not appear in the proposal.
    Thanks,
    Regards.
    Laura

    By any chance can you post your log  on here?
    Once it's cleared running the payment run and not the proposal this should not be happening .. not sure how it would be happening unless it was not actually cleared in the 1st palce.  Are there any errors in any of the invoices?
    Jay Esparza

  • Alternate Payee Number not capture during Manual payment posting (FBZ2)

    Dear Friend,
    Appreciate if anyone can help me with below issue.
    Scenario:
    - Vendor master already been updated with the alternative payee number.
    - I have create a vendor invoice with payee data in the field BSEG-EMPFB.
    Problem:
    When I perform FBZ2 - post outgoing payment and select the invoice created, the payee field was not updated automatically neither based from the original invoice nor vendor master. Furthermore, the field was greyed out during payment posting.
    Pls help how can I cantured the payee number based from the original invoice during post outgoing payment.
    Thx.

    Hi Kiran,
    Here is my answer to your Q.
    1. Have you given alternate payee in vendor master
    - YES, at the genral data->payment transaction and also at alternative payee in doc. I already insert the payee number.
    2. While doing FBZ2 in account give the alternate payee and when you go inside it tells no open items found
    -NOT exactly, coz i dont use the alternate payee number for choosing open item. I use the same vendor code as per invoice.
    3. Click other items and click process open items there you will find the open invoice of the the vendors.
    -NOT applicable as i already select the vendor based from the invoice to be made.
    When I choose open item during FBZ2, entered the main vendor code as per invoice to be made. In the invoice, the alternate payee number is there already. Just during FBZ2 the field is greayed out, hence the payee number from invoice wav not adopted when manual payment was done.
    I notice if i use the FBZ2, the payee field is not open for entry.
    Pls help.
    Thanks.

Maybe you are looking for