Liquidity Forecast not considering payment term / due date

I have configured liquidity forecast and it is picking up values just fine (ECC 6.0).
My problem is that in FF7B it is not taking "Payment Term" and "Due Date" in to consideration at all. Thus as a result not showing what is due on which date.
What do I need to do to ensure that FF7B (liquidity forecast report) show balances considering "Payment Term" and "Due Date"?
Or is here some functionality missing, or I am facing a program error?
Regards

Hi,
You do not have to give the Days there.
Their functionality is different.
Assign 15 in Payment terms Tab in No of Days, Percentage should be blank.
Then the system will calculate the net due date 15 days from Document Date.

Similar Messages

  • Invoice Reduction Invoice Payment Terms - Due Date

    Hi gurus,
    At the time we apply invoice reduction in MIRO screen, both invoices (regular and reduction) take vendor payemnt terms (for ex Due in 30 dyas). Is it possible to assign the invoice reduction invoice a fix payment term "Due Immediately" via configuration?
    Thanks in advance

    Hi there,
    Im afraid there is no setting that will have the system post different payment terms in the invoice reduction
    than what is in the invoice. In MIRO, if you use PO reference to create the IV document, the payment terms are copied from the PO and not from the vendor master. The business reason is, that the PO represents the contract between vendor and customer including the terms of payment. Also check out note 322430 as this gives a good description of the proposal logic for the terms of payment.
    I hope this helps,
    Best regards,
    Adam.

  • Liquidity forecast - purchase order payment terms

    Dear Experts, I have the following issue,
    We are using liquidity forecast, but we are having a problem because the system does not take into account when a Purchase Order is created with Installment Payment Conditions.  The Liquidity Forecast shows the Planning Date equal to Delivery Date of the Purchase Order, not taking into account the division of the payment term and the days of delay of every partial payment. I would like to know if there is workaround for this issue.
    Best regards.

    Hi Cristobal,
    The splitting of payment commitmentment accrding to the instalment dates are not possible. However it is possible to have the first instalment payment date instead of delivery date. But for this the Payment Term definition should take the baseline date as any of the 3 defaults possible ( Doc date/Posting date/Entry date). That means it should not be "No Default".
    Below reproduction from note 497381:
    "In the installment payment terms, you can enter 'Fixed day' and 'Additional months' for the calculation of a baseline date. In this case, the system updates the entire payment commitment as at the calculated baseline date (fixed day and additional months)."
    Please try this and also share your results with us
    Shony

  • Payment terms / Due date Schedule

    Dear experts, how do the Payment terms definen in FI - FICA, relate to the Due Date Schedule used in Student Lifecycle Management?. Do I define Payment terms for the contract account, or just the Due Date Schedule?
    Best regards.

    Hello:
    The Due Date Schedule (DDS) is used to split fees into payment plans (example 50% at beginning of term, 25% one month later and 25% two months later).  The DDS is maintained in the Academic Calendar. To define the DDS you first need to set up a Time Limit and Time Limit Sequences using the IMG path: SLCM>Master Data in SLCM>Academic Calendars.. Note that at least one DDS is required even if you do not provide payment plans for the students. This DDS will have one payment date.  The DDS can be assigned to the Program, Module, Student Account or Contract Object.
    Each partial payment is an orgianal open item which in turn can be split into an FI-CA installment plan using Transaction FPR1.
    As an alternative to the DDS you can use Transaction FPR1 to set up installment plans. This transaction provides more control over payments including dynamic definitoin of due dates.
    Regards,
    Patricia

  • Payment terms - due date on a particular day of the week say friday?

    Experts is it possible in SAP payment terms to configure a term such that due date is on a particular day of the week?
    I want use payment term to determine due date for weekly billing cycle (sunday to saturday) for the invoice to be due on Friday net 27 days from mid point of the week
    eg 1. if a customer is invoiced any day between October 4th to 10th, the due date should be Friday Nov 6th
    eg 2. if a customer is invoiced and day between October 11th to 17th, the due date should be Friday Nov 13th
    Is this possible?
    Thanks in Advance

    You need custom development for this. Using custom development, Substitution in FI or User exit in SD
    I. FI Substitution -
       Create substitution with exit, for field day1 (BSEG-ZBD1T) and baseline date (BSEG-ZFBDT). In exit, determine number of days for required Friday from baseline date you want to use (say document date). This way, due date will be on Friday.
    For determining Friday, use calendar or Ztables.
    II. Invoices created in SD - If you are gerenating invoices in SD, use exit EXIT_SAPLV60B_008. This exit has table ACCIT which also has same fields Day1 and Baseline date. Follow same logic mentioned above.
    I hope this helps.

  • 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

  • Update AP Invoice Payment Schedule (Due Date)

    Dear All,
    Is there any API for AP Invoice Payment Schedule (Due Date) in Oracle EBS R12.
    Please advice.
    Thanks

    Hi there,
    Im afraid there is no setting that will have the system post different payment terms in the invoice reduction
    than what is in the invoice. In MIRO, if you use PO reference to create the IV document, the payment terms are copied from the PO and not from the vendor master. The business reason is, that the PO represents the contract between vendor and customer including the terms of payment. Also check out note 322430 as this gives a good description of the proposal logic for the terms of payment.
    I hope this helps,
    Best regards,
    Adam.

  • Payment terms transaction data

    Hello,
    Could you please tell me in which table Payment terms transaction data is maintained. I have tried checking in BSEG table, but I am not getting the output, it is going into error or not responding after the execution. (I have given only Cocd, Fiscal year, only one posting date and payment term in the selection criteria) Is there any other table which has the payment terms(ZTERM) field with transaction data?
    Thanks

    Hi ,
    Payment terms table   T052
    Terms of Payment Key  ZTERM
    Regards
    Surya

  • Payment Term Master Data

    Can anyone advice me on how to create master data attribute data source in R/3 for Payment Term :
    Please advice me on which table that i should extract the data from :
    Thank you in advance

    Hello Sarvanan,
    Check out table : TVZBT for payment terms master data.
    Create generic datasource on the table TVZBT
    replicate it into BW
    assign the datasource to the infosource
    map the objects create transfer rule transfer structure.
    CReate infopackage and schedule it.
    Regards
    Nimesh

  • Baseline date, terms of payment, net due date in MIRO Parked document

    Hi all:
    When parking a docuement in MIRO with a PO reference the terms of payment, baseline date, and due date are all determined.
    The problem is when we don't have a PO yet, just the vendor and the amount, is there a way for MIRO to determine the terms, baseline date, and due date from the vendor master?

    Hi,
       Just enter the Vendor in MIro and it should pull the Payment terms from the Vendor master (Company Code Area).
    Baseline Date & Due Date are derived based on the settings in the payment term.
    KInd regards

  • SD down payment invoice due date

    Hi,
    Down payment request invoice is generated in SD ,and its clear that the due date in FI document corresponding to this will show the posting date as Due date.but our client needs that the due in downpayment request should be according to the payment terms .i.e it should show due date according to payment term days in the FI document generated automatically when the invoice is saved.is there any user exit /any modification so that the due date should be calculated in background accoding to payment terms when the invoice is saved.
    warm regards,
    rohit

    Hi Glynn,
    I have gone through the sap note ,but in case if the payment terms day is only 5 days i.e  today i will do the invoice and after 5 days it should be due. how this can be done and also if 40 days is payment terms then how we can map this in SAP.
    Thanks & Regards,
    Rohit

  • Payment Term - Fixed date

    Hello Friends,
    Can any one please explain me how does the field "Fixed date" for the following payment term behaves?
    Best Regards,
    Jeetendar

    Hi,
    Can you do a test on this? I have tested and got 25th March as due date.
    If fixed date is not mentioned, system simply calculates due date based on number of day/months mentioned. If fixed date is mentioned, Due date dayis always fixed to that date. This may behave differently if you mention cash discount percentage in first row. If a % is mentioned, this means, user can get mentioned % of cash discount till the calculated date based on fixed day and additional months. In second row, if you don't mention any %, these settings are used for due date calculation.
    After due date, item becomes overdue.
    In you case say you mention 1% in first row and no % in second row with additional months 1.
    This means,
    You can get 1% cash discount till 25th March and no cash discount between 25th March to 25th April.
    Item is over due after 25th April.
    Hope it is clear. I suggest to play around by changing these settings and posting invoices.
    Thanks,
    V V

  • Payment terms - Baseline date calculation.

    Hi
    In payment terms configuration, we have option "No Default" for determining Base line date.
    If we have payment terms with above configuration.......
    In Fi, Baseline field will be blank while posing Customer Invoice, in which case We can enter baseline date manually. However If Invoice is generated from SD-billing document, we dont have any field "Baseline date" while posting billing doc. In such case how system determines Baseline date. When I checked few billing documents, Baseline date is defaulted with BIlling date even "No default" option is selected.
    Is there any configuration in SD that prompts this action. or is it always billing date is defaulted ?
    Please clarify

    Hi !! Madhu,
    There is a way, but not exactly what u require! You can check while maintaining the condition records in t.code VK12, observe the last two columns available, one is called a 'Fixed Value date' & the other is called 'Add Val Days'.
    If you make any entry in the field 'Fixed Value date' this will be the date from which the payment terms start taking effects. Or if you make an entry in Add Val Days' in this case the payment terms start taking effect from billing date + the no. of days mentioned in this column.
    You cannot make a entry in both 'fixed value date' & 'Add Val date'  fields at one time.
    Give your feedback if this has worked for you.
    Regards,
    PATHIK

  • Vendors Payment Before Due Date

    Dear All,
    We could like to restric the release of Vendor payment before the due date.
    We feel there is a system in SAP by which it should give a Error/ warining message (pop up) if any payment is made before the due date.
    Do suggest.
    Regards,

    SAP will give you message if your posting date for e.g. is in past or in future, but the next posting date in F110 parameter decides if you can pay some not due items today or not. SAP will not give you a warning message even if the next posting date is 10 days ahead of today's date.
    In the F110 parameter please make sure Next posting date is always the very next day of the payment run date or Posting date and in the Additinal log tab, please check the indicator Due date check
    This user procedure will make sure that payment is never released before the due date.
    But if still you want some system message to pop up, then SAP standard setting I think will not be of great help, you need to use the BTE00001830 (functional module SAMPLE_PROCESS_00001830) which will help group all the not due items in a group, and exclude the entire group from payments. Information about the group will be received by FM in structure C_REGUH and its line items in table T_REGUP
    By Setting the field XIGNO in C_REGUH to the value "X" the entire group of not due items can be excluded from payments. Please take your abaper help
    Thanks
    Ron

  • F110 bill of exchange: error FZ731 "...requires payment before due date"

    Hi everybody.
    I'm facing an issue that is driving me crazy <:-)
    I want to configure a payment method of type "bill of exchange" (in Spain, "pagaré"). I have several due invoices (due dates: 30/11/10, 31/12/10...), which have this payment method. Some other items are not yet due (30/1/11).
    When carrying out a payment run thru transaction F110, the system asks for the bill of exchange issue date, which I have populated as 30/11/10. At another tests, I have populated as 10/1/11.
    When running F110, the vendor items are then classified as exceptions, with error FZ731 "Pymt method I in the item requires payment by b./exch. before due date", and also message FZ732 "Item not due in 000 - 000 days".
    I think this problem may be motived because the definition of the payment method "I" (company code data) says: Days until due date: 0. But this field is not updatable.
    I've searched the message numbers in the forums, but found no answer.
    Anybody can help? Kind regards,
    Alvaro

    Never mind, I just had to update the Paying company code, fields Bill of exchange due date... > Earliest-lates due date in...days.
    Regards.

Maybe you are looking for

  • Html:options question?

    Hello, Is it possible to change font (bold) of a collection thats inside html:option like below? <div align="left"> <html:select property="istekli" styleClass="metin"> <html:options collection="istekli" property="key" labelProperty="value" /> </html:

  • ERROR FRM-99999 USING FORMS SERVER

    I'm trying to deploy new applications on the Web using OAS and Developer Server. When I am trying to connect via the browser or via the appletviewer to a simple form in Developer Server I get this error in the Oracle Developer Forms Runtime - Web win

  • Can call prioritization done by call type in ICM8.0?

    Hi, I have two calls coming in with nos. 801 and 802 for sales and support for e.g. Now, I have two scripts scheduled based on caltype of 801(sales) and 802(support). In sales script, I use 'Queue to skill group node' and add sales skill group and as

  • LV8 OPC Server Installer

    I use Shared Variable Engine as an OPC Server with LV8. I build an executable (with library deployement), It works on my developpement station (with LV8 installed). I build an installer (with include Variable Engine and LV8 Runtime Engine). If I inst

  • Can't update to 7.0.4 on my iPad - error on download

    Can't update to 7.0.4 on my iPad - error on download