Account Payable - Scheduled Payments

Hello All,
I am working in AP and need to identify any invoices that have a scheduled pay dates in the future. This must have to do with the AP_PAYMENT_SCHEDULES_ALL table. Metalink says almost nothig about these fields.
(1)
Is the "creation_date" the date that the payment is scheduled and is the "due_date" the date that the paymeny has been scheduled for? FUTURE_PAY_DUE_DATE looks to be null or not populated.
(2)
If I am looking for payments scheduled in the future I guess I would be looking for payments with a due_date > sysdate?
Please let me know if you have expertise here,
Thanks, Bradley

Due_date and FUTURE_PAY_DUE_DATE these are 2 field alltogether, nothing can be drived one the basis of these.
Take a note, Due_Date, is calculated by system , the moment you attach payment Term, as part of invoice creation. Where as FUTURE_PAY_DUE_DATE is field get populated once you are making a payment in advance date.
The very similar way, Paybale department give a cheque in the month of Jan 2008 with Cheque Date 8 Feb, means accural would be done in Feb Period month.
This is query which will potentailly bring all the records.
begin
apps.FND_CLIENT_INFO.SET_ORG_CONTEXT(121);
end;
SELECT aiv.vendor_name,
aiv.invoice_num,
aiv.invoice_amount,
aiv.payment_method_lookup_code,
aiv.payment_status_flag,
aiv.pay_group_lookup_code,
aiv.approval_status_lookup_code,
aiv.vendor_hold_flag,
apsa.due_date,
APSA.FUTURE_PAY_DUE_DATE,
apsa.hold_flag
FROM apps.ap_invoices_v aiv,
ap_payment_schedules_all apsa
WHERE aiv.payment_status_flag = 'N' -- CHECK FOR PAYMENT STATUS FLAG Y
AND aiv.holds_count = '0'
AND aiv.invoice_id = apsa.invoice_id
AND apsa.hold_flag = 'N'
AND aiv.approval_status_lookup_code = 'APPROVED'
AND aiv.vendor_hold_flag = 'N'
More over AP_PAYMENT_SCHEDULES_ALL does not make a sense to look for future payment field.
For Future dated you should take a link to
-accrual_posted_flag
-future_pay_posted_flag
of the table ap_invoice_payments_all
Does it helps

Similar Messages

  • Accounts Payables Workflows (Payment Authorisation)

    Good Afternoon,
    Does anyone know if there is a seeded workflow within accounts payable for the authorisation of payments?
    We are currently running 11.5.10 and following a re-structure we have a desire to print cheques, that are signed in the template, with the issue surrounding the security and control of cheque payments.

    Hi,
    There are no seeded workflows in Oracle 11.5.10 for Payment Authorization

  • Account Payables - Down payment request

    Dear all,
    I create a down payment request
    SAP menu: Financial accounting -> Account Payables->Document Entry-> Down payment-> request
    Field name "Trg.sp.G/L.ind ": I input special G/L indicator is A
    And choose Enter
    and I receive message F5053
    Disagnosis
    The specified special G/L indicator is not classified as "down payment" or not listed in the list of the target special G/L indicator  for indicator "F"
    I  created account and assigned the same in the indicator
    Please tell me the reason I met the mistake? How to fix it?
    Thank in advance
    Minh
    Edited by: Tran Binh Minh on Apr 4, 2008 11:51 AM

    Dear Friend,
    Go to transaction code OBYR and check if GL accounts have been assigned to the special GL indicators "A" & "F", by double clicking on them.
    Also double click on "F", click on the properties tab and check if "A" is given in the field "Target special gl indicator".
    If no, then give it and retry the transaction.
    Assign points if useful
    regards
    Venkatesh

  • Account payable with payment block

    how to assign one company code to two different controlling area, where do we define payment block reason ? Thanks

    Hi,
    One company code can be assigned to only one controlling area. However one controlling area can be assigned to multiple company codees. Refer below:-
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/08/513f4b43b511d182b30000e829fbfe/content.htm
    You can define the payment block reasons in transaction OB27 and can define the default values for payment block in OBBC transaction.
    Regards,
    Gaurav

  • AP PAYABLES- Not getting all the DUE DATE's in with split schedule payments

    Hello All,
    We have some issues with AP Data loading's into our DW from EBS 11.5.10 AP - PAYABLES.
    One of our customer is using split schedule and share payment into few payment. Our
    sql is not reading all the due dates for PAYABLES.
    We are using PAYMENT_NUM=1 from ap_payment_schedules_all table as condition to load the Data to avoid duplicate rows coming for Payables.
    Some hints: removing the "PAYMENT_NUM=1" from the where clause gives all the due_dates but then we have duplicate rows for Payables.
    Please help to modify our query so that it will work for split schedule payment.
    select
    inv.invoice_num,
    inv.doc_sequence_value,
    sob.currency_code,
    inv.invoice_date,
    'EH'||inv.vendor_id vendor_id,
    'EH'||inv.vendor_site_id vendor_site_id,
    ael.ae_line_number distribution_line_number,
    inv.invoice_currency_code,
    aeh.accounting_date,
    'EH'||ael.code_combination_id code_combination_id,
    nvl(ael.entered_dr,0)-nvl(ael.entered_cr,0) accounted,
    nvl(ael.accounted_dr,0)-nvl(ael.accounted_cr,0) amount,
    fuser.user_name,
    fuser2.user_name user_name2,
    inv.payment_status_flag,
    'PAYABLES' rowtype,
    inv.discount_amount_taken,
    inv.invoice_type_lookup_code invoice_type,
    inv.exchange_rate,
    inv.exchange_date,
    tax.name,
    inv.source,
    inv.attribute6 eflow_doc_id,
    sysdate transfer_date,
    sch.hold_flag,
    inv.cancelled_date,
    sch.due_date
    from
    ap.ap_invoices_all inv,
    apps.ap_ae_headers_all aeh,
    apps.ap_ae_lines_all ael,
    ap.ap_tax_codes_all tax,
    ap.ap_payment_schedules_all sch,
    gl.gl_sets_of_books sob,
    applsys.fnd_user fuser,
    applsys.fnd_user fuser2
    where
    aeh.ae_header_id=ael.ae_header_id and
    inv.set_of_books_id=sob.set_of_books_id and
    inv.invoice_id=sch.invoice_id and
    sch.payment_num*1=1 and ---------------------------------------------- *
    fuser.user_id=inv.last_updated_by and
    fuser2.user_id=inv.created_by and
    ael.tax_code_id=tax.tax_id(+) and
    ael.ae_line_type_code='LIABILITY' and
    inv.invoice_id=ael.source_id and
    ael.source_table='AP_INVOICES' and
    aeh.gl_transfer_flag='Y'
    Thanks,
    Aman

    Hello All,
    We have some issues with AP Data loading's into our DW from EBS 11.5.10 AP - PAYABLES.
    One of our customer is using split schedule and share payment into few payment. Our
    sql is not reading all the due dates for PAYABLES.
    We are using PAYMENT_NUM=1 from ap_payment_schedules_all table as condition to load the Data to avoid duplicate rows coming for Payables.
    Some hints: removing the "PAYMENT_NUM=1" from the where clause gives all the due_dates but then we have duplicate rows for Payables.
    Please help to modify our query so that it will work for split schedule payment.
    select
    inv.invoice_num,
    inv.doc_sequence_value,
    sob.currency_code,
    inv.invoice_date,
    'EH'||inv.vendor_id vendor_id,
    'EH'||inv.vendor_site_id vendor_site_id,
    ael.ae_line_number distribution_line_number,
    inv.invoice_currency_code,
    aeh.accounting_date,
    'EH'||ael.code_combination_id code_combination_id,
    nvl(ael.entered_dr,0)-nvl(ael.entered_cr,0) accounted,
    nvl(ael.accounted_dr,0)-nvl(ael.accounted_cr,0) amount,
    fuser.user_name,
    fuser2.user_name user_name2,
    inv.payment_status_flag,
    'PAYABLES' rowtype,
    inv.discount_amount_taken,
    inv.invoice_type_lookup_code invoice_type,
    inv.exchange_rate,
    inv.exchange_date,
    tax.name,
    inv.source,
    inv.attribute6 eflow_doc_id,
    sysdate transfer_date,
    sch.hold_flag,
    inv.cancelled_date,
    sch.due_date
    from
    ap.ap_invoices_all inv,
    apps.ap_ae_headers_all aeh,
    apps.ap_ae_lines_all ael,
    ap.ap_tax_codes_all tax,
    ap.ap_payment_schedules_all sch,
    gl.gl_sets_of_books sob,
    applsys.fnd_user fuser,
    applsys.fnd_user fuser2
    where
    aeh.ae_header_id=ael.ae_header_id and
    inv.set_of_books_id=sob.set_of_books_id and
    inv.invoice_id=sch.invoice_id and
    sch.payment_num*1=1 and ---------------------------------------------- *
    fuser.user_id=inv.last_updated_by and
    fuser2.user_id=inv.created_by and
    ael.tax_code_id=tax.tax_id(+) and
    ael.ae_line_type_code='LIABILITY' and
    inv.invoice_id=ael.source_id and
    ael.source_table='AP_INVOICES' and
    aeh.gl_transfer_flag='Y'
    Thanks,
    Aman

  • Possibility of AP and contracts accounts payable payments running parallel

    Hi Gurus,
      My client already has a SAP system and they are planning to implement FICA for contract accounting. Is it possible to have contracts accounts payable and accounts payable systems running in parallel for the payments. Please let me know the solution soon.
    Thanks
    Santosh

    1. Take List of all applied Invoices of the Payment
    2. Check the status of those invoices. Each one of them should be in status 'Accounted'
    3. If not,Identify the problem with the Invoice and Clear that. The problem may be Invoice adjustment(adj to Paid invoices allowed).
    4. Try running Create Accounting again.
    5. If the problem persists still, it conveys us that the Transactions were struck in loop and can be resolved only by using UPDATE command.
    6. Contact Oracle for Data fix
    Regards,
    Sridhar

  • Where can do you link the Account payable (AP) to Automatic Payment Program

    Hi SAP Experts,
    Where can do you link the Account payable (AP) to Automatic Payment Program (APP) what is t - code and what is the table name and Accounts Receivable (AR) to Automatic payment program (APP) what is t - code and what is the table name
    Thanks in Advance.
    Regards.
    Srinivas

    Hi Srinivas,
    The link is created when you enter vendor number in parameters tab of F110 and do the run. Here in Parameters you enter the vendor code for which you need to run APP. Based on vendors provided here in F110 Parameter tab, the F110 program checks for the open items of that vendor which are to be paid and selects them accordingly. Hope this clarifies.
    Ofcourse in Vendor master under Payment transactions Accounting you have to full the necessary fields like Payment methods etc under Automatic Payment Transactions.
    Hope this clarifies
    Kind Regards
    Soumya

  • R12(Payments)--Accounts Payable Trial Balance Report, Need Info.

    Hi All,
    We are trying to use the report Accounts Payable Trial Balance Report.
    This is an XML Report in R12 now and has 4 different RTF Templates.
    Can you please explain me how this report can be used in R12 and how does it selects the RTF template( from 4 different templates present) at run time.?
    Thanks,

    Hi,
    In 11i we use to have a parameter to give the report in Summary or Detail
    In R12 we have 4 options in templates to have Summary by Account, Summary by Supplier, Detail by Account and Detail by Supplier.
    Report will not select the template automatically. The user needs to select the template before submitting the report.
    Hope it helps
    Regards,
    Sridhar

  • Sap report purchasing and accounts payable

    Dear gurus,
    I intend to create a vendor payment report that would create clarity on the operations in purchasing and accounts payable.
    Which tables would be idea to create such report?
    BR,
    Tolu

    (Only some of the most important tables)
    For MM purchasing, check
    - EKKO     Purchasing Document Header
    - EKPO     Purchasing Document Item
    - EKBE     History per Purchasing Document
    - EKKN     Account Assignment in Purchasing Document
    (Also look at logical database BRM, EBM, ECM, EKM, ELM, EMM, ENM, ERM, EWM,MEPOLDB, PSJ   definitions)
    For FI-AP financial account payable
    - BKPF     Accounting Document Header
    - BSEG     Accounting Document Segment
    - BSIK     Accounting: Secondary Index for Vendors
    - BSAK     Accounting: Secondary Index for Vendors (Cleared Items)
    - BSIS     Accounting: Secondary Index for G/L Accounts
    - BSAS     Accounting: Secondary Index for G/L Accounts (Cleared Items)
    - BSIM     Secondary Index, Documents for Material
    (Also look at logical database BMM, BRF, BRM, KDF definitions)
    Regards,
    Raymond

  • AP Invoice Aging Report by GL Date (using: Accounts Payable Trial Balance)

    Hi
    Need some suggestions:
    I need to develop a custom report in (R12).
    Account Payable Trial Balance Report, does have the capability to run as of a particular date but it does not show aging buckets. This custom report is to be developed to meet the requirements from a Payables detail perspective as well as to reconcile.
    The report should show the balance due as of the report date selected. If As of Date = 5/31/11, then when the report is run on 6/15/11, it gives the results as it existed on 5/31/11. If we run it again on 8/31/11 for As of Date = 5/31/11, and again on 1/13/12, we get the EXACT SAME results each and every time except for the following fields: Current Status, Date Paid and Payment Reference Number.
    The end result should be this report ties to the penny to Oracle GL as of the date selected EXCEPT for any JEs posted to the account.
    Thanks
    Pravin

    Hi Pravin,
    For all transactions in Oracle, you will have GL dates (Accounting Dates) associated to it. If you use this date in your query to filter data, then you will get correct aging data as on a given date.
    To tally with GL, you also must check if the selected transaction has been accounted?
    Raajkumar G

  • What is the query for Accounts Payable Trial Balance (APXTRBAL) in 11.5.10?

    Hi Guys,
    What is the query for Accounts Payable Trial Balance (APXTRBAL) in 11.5.10?
    I have to write an AP Invoice Aging Report in Discoverer to show all unpaid invoices that have been transferred into GL... Business wants it to match one-to-one with the AP Trial Balance standard report...
    Business wants to run the report for any date in a past...
    The report has two parameters:
    As Of Date - the same as As of Date for the AP Trial Report
    Trial Balance Run Date - the date when Trial Balance was run...
    Conditions are:
    TRUNC(Invoice Date) <=TRUNC(NVL(TO_DATE(:As Of Date),SYSDATE))
    TRUNC(NVL(Payment Date,'01-JAN-5000')) > TRUNC(NVL(TO_DATE(:As Of Date),SYSDATE))
    TRUNC(Invoice Creation Date) <= TRUNC(NVL(TO_DATE(:Trial Balance Run Date),SYSDATE))
    Distr Accounting Date <= TRUNC(NVL(TO_DATE(:As Of Date),SYSDATE))
    NVL(Distr Creation Date,Invoice Creation Date) <= TRUNC(NVL(TO_DATE(:Trial Balance Run Date),SYSDATE))
    Show_Flag = 'YES', where:
    Show_Flag = CASE WHEN ( NVL(Cancelled Date,'01-JAN-1901') > NVL(:As Of Date,SYSDATE) AND NVL(Inv Amount Aud,0) = 0 ) THEN 'YES' ELSE ( CASE WHEN NVL(Inv Amount Aud,0) = 0 THEN 'NO' ELSE 'YES' END ) END
    There is a difference between the logic of my report, and the logic of AP Trial Balance...
    Could you please advise what I'm missing?
    Thanks,
    Iana

    What is the query for Accounts Payable Trial Balance (APXTRBAL) in 11.5.10? You can get the code by opening the report in Reports Builder and get the query.
    Or, enable trace/debug as per (FAQ: Common Tracing Techniques within the Oracle Applications 11i/R12 [ID 296559.1]).
    Thanks,
    Hussein

  • List of invoices paid in accounts payable with corresponding expense GL

    Hi,
    Need to know whether there ia any standard report in SAP ECC 6.0 version where we can get the list of all invoices paid  in a period  in A/Pwith corresponding expense GL Account. IF we need to build report painter report or query  any idea which tables will contain all these information. If any one is having functional specification document it will be of great help.
    Regards,
    Vipin

    Hi,
    - check in Easy Access->Accounting-> Fin Acctng->Accounts Payable-> Vendors:Items or Payment Transactions (like S_P99_41000099 or S_ALR_87012085 etc.,)
    - relevant tables would be BSAK or BSEG
    Rgds.

  • Accounts payable: Reconciliation field(s)

    Dear all,
    I have posted the same thread in the Materials Management forum as I am not sure where it belongs. As I am not very familiar with vendor payments, I hope you can help me with this question.
    As per our accounts payable department, when they send a check to a vendor, they need to reference the payment with the bill of lading number.
    But the bill of lading is not available in the payments standard transaction: F110. So I was wondering: which field(s) (which are printed on the check) are usually used by vendors for payments reconcialiation?
    Thanks,
    Annabelle

    Hi Annabelle,
       When you enter an invoice with reference to a purchase order, the system suggests data from the purchase order and the goods receipts against the PO (for example, vendor, material, quantity still to be invoiced, expected amount per item, and terms of payment). You can overwrite these default values if the invoice actually submitted by the vendor contains other values. The system checks whether your input is allowed. In doing so, it may issue warning or error messages.
    You can also assign the invoice items to a purchase order using the number of the delivery note or bill of lading, provided that these numbers were entered at the time of goods receipt.
    With Regards
    Srinivas

  • Accounts payable master data

    Hi All
    Cud any one provide sample code how to upload accounts payable master data?
    thnx in advance,
    Pavani.

    Hi
    Account Payables means the amounts that are to be paid to vendor against the purchase we made
    So here the master data menas the VENDOR, MATERIAL data
    see the related BDC programs
    REPORT zmm_mat_master_non_stock
           NO STANDARD PAGE HEADING
           LINE-SIZE 255.
    Standard Include for Selection Screen
    INCLUDE bdcrecx1.
    Internal Table for Upload Data
    DATA: BEGIN OF i_mat OCCURS 0,
           mbrsh(001),            " Industry Sector
           mtart(004),            " Material Type
    Views
    Organization Levels
           werks(004),            " Plant
    Basic Data1 View
            maktx(040),            " Material Description
           meins(003),            " Unit of Measure
            matkl(009),            " Material Group
           MTPOS_MARA(004),       " Gen Item Category
    Purchasing
            ekgrp(003),            " Purchasing Group
          END OF i_mat.
    Data Variables & Constants
    CONSTANTS : c_x             VALUE 'X'. " Flag
    Parameters
    PARAMETERS: p_file LIKE ibipparms-path.  " Filename
    At selection-screen on Value Request for file Name
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
    Get the F4 Values for the File
      CALL FUNCTION 'F4_FILENAME'
        EXPORTING
          program_name  = syst-cprog
          dynpro_number = syst-dynnr
        IMPORTING
          file_name     = p_file.
    Start of Selection
    START-OF-SELECTION.
    Open the BDC Session
      PERFORM open_group.
    Upload the File into internal Table
      CALL FUNCTION 'UPLOAD'
        EXPORTING
          filename                = p_file
          filetype                = 'DAT'
        TABLES
          data_tab                = i_mat
        EXCEPTIONS
          conversion_error        = 1
          invalid_table_width     = 2
          invalid_type            = 3
          no_batch                = 4
          unknown_error           = 5
          gui_refuse_filetransfer = 6
          OTHERS                  = 7.
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    Upload the Data from Internal Table
      LOOP AT i_mat.
    Basic Screen
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '0060'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RMMG1-MATNR'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'RMMG1-MBRSH'
                                      'C'."i_mat-mbrsh.
        PERFORM bdc_field       USING 'RMMG1-MTART'
                                      'NLAG'."i_mat-mtart.
    Views Selection
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '0070'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'MSICHTAUSW-DYTXT(08)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=ENTR'.
        PERFORM bdc_field       USING 'MSICHTAUSW-KZSEL(01)'
                                      c_x."i_mat-kzsel_01.
        PERFORM bdc_field       USING 'MSICHTAUSW-KZSEL(02)'
                                      c_x."i_mat-kzsel_02.
        PERFORM bdc_field       USING 'MSICHTAUSW-KZSEL(08)'
                                      c_x."i_mat-kzsel_08.
    Organization Levels
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '0080'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RMMG1-WERKS'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=ENTR'.
        PERFORM bdc_field       USING 'RMMG1-WERKS'
                                      '2000'."i_mat-werks.
    Basic data1 View
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '4004'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'MAKT-MAKTX'
                                      i_mat-maktx.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'MARA-MTPOS_MARA'.
        PERFORM bdc_field       USING 'MARA-MEINS'
                                      'EA'."i_mat-meins.
        PERFORM bdc_field       USING 'MARA-MATKL'
                                      i_mat-matkl.
        PERFORM bdc_field       USING 'MARA-MTPOS_MARA'
                                      'NLAG'."i_mat-mtpos_mara.
    Basic data2 View
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '4004'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'MAKT-MAKTX'.
    Purchasing View
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '4000'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=BU'.
        PERFORM bdc_field       USING 'MARC-EKGRP'
                                      i_mat-ekgrp.
    Call The Transaction
        PERFORM bdc_transaction USING 'MM01'.
      ENDLOOP.
    Close the BDC Session
      PERFORM close_group.
    REPORT zmm_vendor_master_upload
           NO STANDARD PAGE HEADING
           LINE-SIZE 255.
    ABAP Name   :   ZMM_VENDOR_MASTER_UPLOAD
    Description :   This Program is used to Upload the Vendor Master.
    Standard Include for Selection Screen
    INCLUDE bdcrecx1.
    Internal Table for Upload Data
    DATA: BEGIN OF i_vendor OCCURS 0,
            bukrs(004),             " Company Code
            ekorg(004),             " Purchase Orgn
            ktokk(004),             " Account Group
    Address Screen
            anred(015),             " Title
            name1(035),                                         " Name1
            sortl(010),             " Sort Field
            name2(035),                                         " Name2
            name3(035),             " Contact Person1
            name4(035),             " Contact Person 2
            stras(035),             " Street
            pfach(010),             " PO Box
            ort01(035),             " City
            pstlz(010),             " Postal Code
            land1(003),             " Country
            spras(002),             " Language
            telf1(016),             " Telephone No
            telfx(031),             " Fax Number
            lfurl(132),             " URL-Mail Id
    Material Group Characteristics
           klart(003),             " Class Type '010'
           class(018),             " Class 'Vendor'
           mname_01(030),          " Characteristic
           mname_02(030),          " Characteristic
           mname_03(030),          " Characteristic
            mwert_01(030),          " Charct.Value
            mwert_02(030),          " Charct.Value
            mwert_03(030),          " Charct.Value
    Control Data
            emnfr(010),             " Manufact.Part No
    Bank Details
            banks_01(003),          " Country of Bank1
            banks_02(003),          " Country of Bank2
            bankl_01(015),          " Bank Key of 1
            bankl_02(015),          " Bank Key of 2
            bankn_01(018),          " Account No Bank1
            bankn_02(018),          " Account No Bank2
    Accounting Info
            akont(010),             " Reconcillation Account
            zuawa(003),             " Sort Key
            fdgrv(010),             " Cash Management Group
    Payment Transactions
            zterm(004),             " Payment terms
           reprf(001),             " Check Double Inv.
            zwels(010),             " Payment Method
            hbkid(005),             " House Bank
           xpore(001),             " Individ.Payment
    Correspondence
            mahns(001),             " Dunning Level
            xausz(001),             " Account Statement
    Withholding Tax Details
            qland(003),             " Withholding Tax Country
            witht_01(002),          " WH tax Type
           wt_withcd(002),        " WH Tax Code
           wt_subjct(001),        " Indicator:WH Tax
    Purchasing Data
            waers(005),             " Currency
            zterm1(004),            " Payment Terms
          END OF i_vendor.
    Data Variables & Constants
    CONSTANTS : c_x     VALUE 'X'.  " Flag
    Paramters
    PARAMETERS: p_file LIKE ibipparms-path.  " Filename
    At selection-screen on Value Request for file Name
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
    Get the F4 Values for the File
      CALL FUNCTION 'F4_FILENAME'
        EXPORTING
          program_name  = syst-cprog
          dynpro_number = syst-dynnr
        IMPORTING
          file_name     = p_file.
    Start of Selection
    START-OF-SELECTION.
    Open the BDC Session
      PERFORM open_group.
    Upload the File into internal Table
      CALL FUNCTION 'UPLOAD'
        EXPORTING
          filename                = p_file
          filetype                = 'DAT'
        TABLES
          data_tab                = i_vendor
        EXCEPTIONS
          conversion_error        = 1
          invalid_table_width     = 2
          invalid_type            = 3
          no_batch                = 4
          unknown_error           = 5
          gui_refuse_filetransfer = 6
          OTHERS                  = 7.
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    Upload the Data from Internal Table
      LOOP AT i_vendor.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0100'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RF02K-KTOKK'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'RF02K-BUKRS'
                                      i_vendor-bukrs.
        PERFORM bdc_field       USING 'RF02K-EKORG'
                                      i_vendor-ekorg.
        PERFORM bdc_field       USING 'RF02K-KTOKK'
                                      i_vendor-ktokk.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0110'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFA1-SPRAS'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=KLAS'.
        PERFORM bdc_field       USING 'LFA1-ANRED'
                                      i_vendor-anred.
        PERFORM bdc_field       USING 'LFA1-NAME1'
                                      i_vendor-name1.
        PERFORM bdc_field       USING 'LFA1-SORTL'
                                      i_vendor-sortl.
        PERFORM bdc_field       USING 'LFA1-NAME2'
                                      i_vendor-name2.
        PERFORM bdc_field       USING 'LFA1-NAME3'
                                      i_vendor-name3.
        PERFORM bdc_field       USING 'LFA1-NAME4'
                                      i_vendor-name4.
        PERFORM bdc_field       USING 'LFA1-STRAS'
                                      i_vendor-stras.
        PERFORM bdc_field       USING 'LFA1-PFACH'
                                      i_vendor-pfach.
        PERFORM bdc_field       USING 'LFA1-ORT01'
                                      i_vendor-ort01.
        PERFORM bdc_field       USING 'LFA1-PSTLZ'
                                      i_vendor-pstlz.
        PERFORM bdc_field       USING 'LFA1-LAND1'
                                      i_vendor-land1.
        PERFORM bdc_field       USING 'LFA1-SPRAS'
                                      i_vendor-spras.
        PERFORM bdc_field       USING 'LFA1-TELF1'
                                      i_vendor-telf1.
        PERFORM bdc_field       USING 'LFA1-TELFX'
                                      i_vendor-telfx.
        PERFORM bdc_field       USING 'LFA1-LFURL'
                                      i_vendor-lfurl.
        PERFORM bdc_dynpro      USING 'SAPLCLCA' '0602'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RMCLF-KLART'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=ENTE'.
        PERFORM bdc_field       USING 'RMCLF-KLART'
                                      '010'. "i_vendor-klart.
        PERFORM bdc_dynpro      USING 'SAPLCLFM' '0500'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RMCLF-CLASS(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=AUSW'.
        PERFORM bdc_field       USING 'RMCLF-CLASS(01)'
                                      'Vendor'."i_vendor-class.
        PERFORM bdc_dynpro      USING 'SAPLCTMS' '0109'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RCTMS-MWERT(03)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=BACK'.
        PERFORM bdc_field       USING 'RCTMS-MNAME(01)'
                           'MATERIALGROUP'." i_vendor-mname_01.
        PERFORM bdc_field       USING 'RCTMS-MNAME(02)'
                           'MATERIALGROUP'." i_vendor-mname_02.
        PERFORM bdc_field       USING 'RCTMS-MNAME(03)'
                           'MATERIALGROUP'." i_vendor-mname_03.
        PERFORM bdc_field       USING 'RCTMS-MWERT(01)'
                                      i_vendor-mwert_01.
        PERFORM bdc_field       USING 'RCTMS-MWERT(02)'
                                      i_vendor-mwert_02.
        PERFORM bdc_field       USING 'RCTMS-MWERT(03)'
                                      i_vendor-mwert_03.
        PERFORM bdc_dynpro      USING 'SAPLCLFM' '0500'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RMCLF-CLASS(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=ENDE'.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0110'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFA1-ANRED'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0120'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFA1-EMNFR'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
        PERFORM bdc_field       USING 'LFA1-EMNFR'
                                      i_vendor-emnfr.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0130'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFBK-BANKN(02)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                          '=VW'.
        PERFORM bdc_field       USING 'LFBK-BANKS(01)'
                                      i_vendor-banks_01.
        PERFORM bdc_field       USING 'LFBK-BANKS(02)'
                                      i_vendor-banks_02.
        PERFORM bdc_field       USING 'LFBK-BANKL(01)'
                                      i_vendor-bankl_01.
        PERFORM bdc_field       USING 'LFBK-BANKL(02)'
                                      i_vendor-bankl_02.
        PERFORM bdc_field       USING 'LFBK-BANKN(01)'
                                      i_vendor-bankn_01.
        PERFORM bdc_field       USING 'LFBK-BANKN(02)'
                                      i_vendor-bankn_02.
       PERFORM bdc_dynpro      USING 'SAPMF02K' '0130'.
       PERFORM bdc_field       USING 'BDC_CURSOR'
                                     'LFBK-BANKS(01)'.
       PERFORM bdc_field       USING 'BDC_OKCODE'
                                     '=VW'.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0210'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFB1-FDGRV'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
        PERFORM bdc_field       USING 'LFB1-AKONT'
                                      i_vendor-akont.
        PERFORM bdc_field       USING 'LFB1-ZUAWA'
                                      i_vendor-zuawa.
        PERFORM bdc_field       USING 'LFB1-FDGRV'
                                      i_vendor-fdgrv.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0215'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFB1-XPORE'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
        PERFORM bdc_field       USING 'LFB1-ZTERM'
                                      i_vendor-zterm.
        PERFORM bdc_field       USING 'LFB1-REPRF'
                                      c_x. "i_vendor-reprf.
        PERFORM bdc_field       USING 'LFB1-ZWELS'
                                      i_vendor-zwels.
        PERFORM bdc_field       USING 'LFB1-HBKID'
                                      i_vendor-hbkid.
        PERFORM bdc_field       USING 'LFB1-XPORE'
                                      c_x. "i_vendor-xpore.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0220'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFB5-MAHNS'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
        PERFORM bdc_field       USING 'LFB5-MAHNS'
                                      i_vendor-mahns.
        PERFORM bdc_field       USING 'LFB1-XAUSZ'
                                      i_vendor-xausz.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0610'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFBW-WT_SUBJCT(01)'.
        PERFORM bdc_field       USING 'LFB1-QLAND'
                                      i_vendor-qland.
        PERFORM bdc_field       USING 'LFBW-WITHT(01)'
                                      i_vendor-witht_01.
       PERFORM bdc_field       USING 'LFBW-WT_WITHCD(01)'
                                     i_vendor-wt_withcd.
        PERFORM bdc_field       USING 'LFBW-WT_SUBJCT(01)'
                                       c_x.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0310'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFM1-ZTERM'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
        PERFORM bdc_field       USING 'LFM1-WAERS'
                                      i_vendor-waers.
        PERFORM bdc_field       USING 'LFM1-ZTERM'
                                      i_vendor-zterm1.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0320'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RF02K-LIFNR'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
        PERFORM bdc_dynpro      USING 'SAPLSPO1' '0300'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=YES'.
    Call the Transaction
        PERFORM bdc_transaction USING 'XK01'.
      ENDLOOP.
    Close the BDc Session
      PERFORM close_group.
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Bill of Exchange (Account Payable)

    Hi Experts:
    I was trying to configure Bill of Exchange - For both Account payable as well as account receivable. Account Receivable Succeed. But have some problem in BOE Account Payable.
    Can any one tell me Step by Step Procedure to configure and use (User Manual) for it. (BOE Payable).
    Please help. Thanks in Advance.
    With Regards,
    Devendra Singh Chauhan

    HI
    Please find the below Config steps
    1.Define Alternative Reconcil.Acct for Bills/Exch.Receivableu201D: in OBYN
    2.Define Accounts for Bill of Exchange Transactions in OBYH
    3.Define Bill of Exchange Tax Codes in below path
    SPRO - > Financial Accounting (New) --> bank Accounting --> Business Transactions --> Bill of exchange transactions --> Post bill of exchange receivable --> Define Bill of Exchange Tax Codes
    4.Prepare Bill of Exchange Charges Statementu201D in Below path
    SPRO --> Financial Accounting (New) --> bank Accounting --> Business Transactions --> Bill of exchange transactions --> Post bill of exchange receivable --> Prepare Bill of Exchange Charges Statement
    5.Define Correspondence Types in OB77
    6.Assign Programs for Correspondence Types in OB78
    7.Define Form Names for Correspondence Print in Below path
    SPRO --> Financial Accounting (New) --> bank Accounting --> Business Transactions --> Bill of exchange transactions --> Post bill of exchange receivable --> Make and Check Settings for Correspondence --> Define Form Names for Correspondence Print
    8.Define Sender Details for Correspondence Form in below path
    SPRO --> --> Financial Accounting (New) --> bank Accounting --> Business Transactions --> Bill of exchange transactions --> Post bill of exchange receivable --> Make and Check Settings for Correspondence --> Define Sender Details for Correspondence Form
    9.Configuration Design of u201CDefine Bank Subaccounts in OBYK
    10. Define Bill of exchange types in F.39
    11.Maintain House Bank Details in F.92
    12.u201CDefine DME User IDs in OBBD
    13.Define User-Specific Settings in below path
    Financial Accounting (New) --> bank Accounting --> Business Transactions --> Bill of exchange transactions --> Present Bill of Exchange Receivable at Bank --> Define User-Specific Settings
    14.u201CDefine Sender Details for Form for Bill of Exchange Presentationu201D in blow path
    Financial Accounting (New) --> bank Accounting --> Business Transactions --> Bill of exchange transactions --> Present Bill of Exchange Receivable at Bank --> Define Sender Details for Form for Bill of Exchange Presentation
    15.Define Bill of Exchange Payment Periodu201D in below path
    SAP Customizing Implementation Guide --> Financial Accounting (New) --> bank Accounting --> Business Transactions --> Bill of exchange transactions --> Present Bill of Exchange Receivable at Bank --> Define Bill of Exchange Payment Period
    16.Set Up Paying Company Codes for Payment Transactionsu201D in below path
    SAP Customizing Implementation Guide --> Financial Accounting (New) --> Accounts Receivable and Accounts Payable > Business Transactions> Incoming Payments > Automatic Incoming Payments> Payment Method/Bank Selection for Payment Program-->Set Up Paying Company Codes for Payment Transactions
    17.Set Up Paying Company Codes for Payment Transactionsu201D in below path
    SAP Customizing Implementation Guide --> Financial Accounting (New) --> Accounts Receivable and Accounts Payable > Business Transactions> Incoming Payments > Automatic Incoming Payments> Payment Method/Bank Selection for Payment Program-->Set Up Paying Company Codes for Payment Transactions
    18.Set Up Payment Methods per Country for Payment Transactions in below path
    SAP Customizing Implementation Guide --> Financial Accounting (New) --> Accounts Receivable and Accounts Payable > Business Transactions> Incoming Payments > Automatic Incoming Payments> Payment Method/Bank Selection for Payment Program-->Set Up Payment Methods per Country for Payment Transactions
    19.Set Up Payment Methods per Company Code for Payment Transactu201D in below path
    SAP Customizing Implementation Guide --> Financial Accounting (New) --> Accounts Receivable and Accounts Payable > Business Transactions> Incoming Payments > Automatic Incoming Payments> Payment Method/Bank Selection for Payment Program--> Set Up Payment Methods per Company Code for Payment Transact
    20.Set Up Bank Determination for Payment Transactionsu201D in below path
    SAP Customizing Implementation Guide --> Financial Accounting (New) --> Accounts Receivable and Accounts Payable > Business Transactions> Incoming Payments > Automatic Incoming Payments> Payment Method/Bank Selection for Payment Program--> Set Up Bank Determination for Payment Transactions
    Hope it will be helpful
    Regards
    CA.Prasad

Maybe you are looking for