Baseline Date - Payment Terms

Hi,
The users have created the Payment Term for the Credit Management purposes and the same has been maintained in the Customer Masters. While creating the Payment Term, the Default for baseline date has been specified as "Document Date". Thus the baseline date is required to be same as the Document Date. In case of all invoices we observe that the baseline date is same as the Document Date, except for few where we notice the Baseline Date has got changed thus impacting the AR Aging.
Could you please advise as to how could the baseline date get changed ? What could be the reasons and how do we check the same ? There were no manual changes made to the Accounting Document. Also what can be done to prevent the same from happening in future ?
Thanks in advance.

Hi,
we faced the same probelm before for Invoices (MIRO).
The USER after filling the details checks that he entered the Invoice date wrong and corrects the invoice date and saves the doc. when he does this the baseline date is not getting updated by the change of invoice date.
here The baseline date is updated only after the reentry of po no. or deleivery no. whatever he is giving the details in MIRO.
we did a lot of investigation with this baseline date problem.
please check with ur user as to he might be changing the invoice date befor saving. if he changes the invoice date he also need to update the delivery no below.
regards
jaya

Similar Messages

Baseline date & Payment terms are not populating for Intercomany vendor

Hi,
When we post intercompany invoice & check the vendor line items in FBL1N,it is expected to have data payment terms & Baseline date from the posted Invoice.this is occuring fime with single company but this data is blank for Intercompany which is creating issues for further steps.
Anybody has faced such issue? What may be the resolution?

Hello,
Why are you directly executing these programs?
You will not expect these program to execute directly by going to SE38.
I would have configured the relevant payment methods in the country with DME structure or classical RFFO* programs, which in turn pick up the inherent programs at the time of running F110.
For example, if you need to generate BACS file for country GB, either you copy the GB_BACS to ZGB_BACS or use GB_BACS directly in FBZP settings.
Make sure that you have maintained OBPM1 / OBPM2 / OBPM3 and OBPM4 settings properly.
The system automatically gives the access to system RFFOAVIS_FPAYM. Prepare a variant against this program in F110. Relevant file gets generated to folder path mentioned in OBPM4 will get generated. The file get generated can be seen in AL11.
Hope this is informative and solves your issue.
Regards,
Ravi

Baseline Date of terms of payment

HI,
I need some help with something, how i can enter the baseline date of term of payment manually? I see in the OBB8, that appear 4 option of baseline date, but not manually.
Is there any configuration in SD that prompts this action?
please give me your answer with detail, i new in this.
Thankz,

Hi Ryan,
in the default for baseline date - select No default.
while creating a sales order you can enter the date on which baseline date should be considered for calculating the payment terms days. this field is avaiable in Billing Tab of Sales order at Header level and Item level.
Please let me know, if you more clarifications.
thanks
rajam

How to see (net due date + payment term's days) in fbl5n as a date

hi experts.
i need some informations about fbl5n fields
i can see net due date and i can see terms of payment fields in the fbl5n but if the invoice has a payment term (30 day additional etc) i want to see (net due date + payment term's extra days) . for example if the net due date is 01.06.2011 and payment term is extra 20 days , how can i see 21.06.2011 in fbl5n or any other sceens?
Edited by: Burak Akdasli on Jun 22, 2011 3:43 PM

Hi
I understand from ur question whats the billing date?
If this is ur question, you can fetch it from sales order>item>billing tab.
The logic u had mentioned is confusing be more specifc as to what scenario u are trying.
Reward if it helped
Chandru

Cutomer master co code data payment terms

hi all,
could pls tell me what is the use of payment terms field in co code data of customer master.Only sales area data payment terms get populated in the sales order.Then why should we maintain the payment terms in co code data
thanks & regards

Hi
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.
best regards,
Thangesh

Fixed Due Date - Payment Term

Hi .... How to get a fixed due date for Vendor / Customer Invoices (without modifying Due Date after posting the Document or Changing Base Line Date for each Invoice at the time of Posting Document)?
For Example, If we post a Vendor / Customer Invoice with in the Dates from 1st Jan to 31st May 2014, default Due Date should be 31st May 2014
(For T Codes FB60 / FB70 / MIRO etc)
Please let me know the alternatives through Payment Term or any other way....
Thanks ..... Ramesh

Hello,
Apart from above suggestions, please check below blog as well where you can calculate dynamic due date for fixed day payment terms.
Fixed day payment terms - The magic behind due date determination!!!
Thanks,
V V

End Date Payment Terms in Oracle Receivables

Hi,
I would like to know if a particular 'Payment Term' can be end dated even if there are invoices with - a) open receivable balance b)Unposted accounting lines..
Thanks,
Madhu

Hi, You can create UDFs for Roles in catalog search.
These UDFs can be made visible in Role similar to Role Owner and different fields which appears in the bottom of catalog search page.
HTH,
~J

FIxed date payment terms

HI All,
we have a requirement where the due date should be a fix date, say 31st march 2007, irrespective of invoice date.
Please let me know if this can be configured & how?

I think it is wise to post this in the FI forum...
If it is not a standard customizing setting then you have to build something for it. My idea is to use an user-exit/badi for it. When calling this user-exit/badi on save read the due date from an own customizing table and modify it with the date available in the workarea.
/Peter

BADI MRM_PAYMENT_TERMS - Baseline date

Hi All,
The requirment I have is to automatically populate the Baseline date based on the GR posting date and Invoice posting date.
While creation of the Invoice in MIRO,
       1) If the GR posting date is greater than the Invoice posting date then the Baseline date should be populated with the GR posting date.
       2) If the Invoice posting date is greater than the GR posting date then the Baseline date date should be populated with the Invoice posting date.
This logic I have implemented in the BADI MRM_PAYMENT_TERMS which works as expected.
But the standard calculation of 'DUE ON' date, Payment terms, Cash discount days are not performing according to the standard functionality and these values do not get displayed.
Why is this getting affected?
Also, please suggest if there is any other way to achieve this requirement without any deviation from the standard functionality.
Below is the code that I have implemented in the BADI.
*----Defining the structure for work area for EKBE table data fetch
TYPES: BEGIN OF TY_EKBE,
          EBELN TYPE EBELN,
          EBELP TYPE EBELP,
          BELNR TYPE MBLNR,
          BEWTP TYPE BEWTP,
          BWART TYPE BWART,
          BUDAT TYPE BUDAT,
         END OF TY_EKBE.
*----Defining the work areas
DATA: WA_EKBE TYPE                   TY_EKBE,          "Work area for History per Purchasing Document table
        WA_DRSEG TYPE LINE OF           MMCR_TDRSEG.      "Work area for Invoice doc items
*----Checking if the Company code is IBTG
IF I_RBKPV-BUKRS = 'IBTG'.
*----Selecting data from EKBE table to fetch the latest GR posting date
    SELECT EBELN
           EBELP
           BELNR
           BEWTP
           BWART
           BUDAT
    INTO WA_EKBE
    FROM EKBE
    FOR ALL ENTRIES IN TI_DRSEG
    WHERE EBELN = TI_DRSEG-EBELN
    AND   BEWTP = 'E'
    AND   BWART = '101'.
    ENDSELECT.
*----Looping at Invoice Doc. Items table into its work area
    LOOP AT TI_DRSEG INTO WA_DRSEG.
      IF WA_EKBE-BUDAT > WA_DRSEG-BUDAT.                 "If GR posting date is greater than invoice date
        E_ZFBDT = WA_EKBE-BUDAT.                         "Assigning the GR date to Baseline date
      ELSEIF WA_EKBE-BUDAT < WA_DRSEG-BUDAT.             "If Invoice date is greater than GR date
        E_ZFBDT = WA_DRSEG-BUDAT.                        "Assigning the Invoice date to Baseline date
      ELSEIF WA_EKBE-BUDAT = WA_DRSEG-BUDAT.             "If Invoice date is Equal to GR date
        E_ZFBDT = WA_DRSEG-BUDAT.                        "Assigning the Invoice date to Baseline date
      ENDIF.
    ENDLOOP.
ENDIF.

Hi,
if you go to se18 and display badi MRM_PAYMENT_TERMS,
in "Interface" tab if you double click on "Example implementation class" CL_EXM_IM_MRM_PAYMENT_TERMS
and then in class interface CL_EXM_IM_MRM_PAYMENT_TERMS, if you display the code of IF_EX_MRM_PAYMENT_TERMS~PAYMENT_TERMS_SET you will find three examples:
METHOD if_ex_mrm_payment_terms~payment_terms_set .
*--- fill all export-parameter ----------------------------------------*
e_zfbdt = i_rbkpv-zfbdt.
e_zbd1t = i_rbkpv-zbd1t.
e_zbd1p = i_rbkpv-zbd1p.
e_zbd2t = i_rbkpv-zbd2t.
e_zbd2p = i_rbkpv-zbd2p.
e_zbd3t = i_rbkpv-zbd3t.
e_zlspr = i_rbkpv-zlspr.
*** Example 1: Setting ZFBDT depending on goods receive
DATA: h_drseg TYPE mmcr_drseg,
        h_budat TYPE mmcr_ekbe-budat.
TYPES: BEGIN OF x_datum ,
           budat LIKE h_budat,
         END OF x_datum.
TYPES: BEGIN OF x_ekbe_gelesen,
           ebeln TYPE ekbe-ebeln,
           ebelp TYPE mmcr_ekbe-ebelp,
         END OF x_ekbe_gelesen.
DATA: h_ekbe_gelesen TYPE STANDARD TABLE OF x_ekbe_gelesen,
        h1_ekbe_gelesen TYPE x_ekbe_gelesen.
DATA: h_datum TYPE STANDARD TABLE OF x_datum,
        h1_datum TYPE x_datum,
        h_ebeln LIKE h_drseg-ebeln,
        h_ebelp LIKE h_drseg-ebelp.
LOOP AT ti_drseg INTO h_drseg WHERE selkz = 'X'.
    SELECT budat FROM ekbe INTO h_budat WHERE
         ebeln = h_drseg-ebeln AND
         ebelp = h_drseg-ebelp AND
         lfbnr = h_drseg-lfbnr AND
         lfgja = h_drseg-lfgja AND
         lfpos = h_drseg-lfpos AND
         vgabe = '1'.
      IF sy-subrc EQ 0.
        MOVE h_budat TO h1_datum-budat.
        APPEND h1_datum TO h_datum.
      ENDIF.
    ENDSELECT.
ENDLOOP.
SORT h_datum DESCENDING.
READ TABLE h_datum INDEX 1 INTO e_zfbdt.
*** Example 2: calculate best payment terms based on manual settings
DATA: h2_drseg TYPE mmcr_drseg,
        h2_zbd1p TYPE mrm_rbkpv-zbd1p,
        h2_zbd1t TYPE mrm_rbkpv-zbd1t,
        h2_zbd2p TYPE mrm_rbkpv-zbd2p,
        h2_zbd2t TYPE mrm_rbkpv-zbd2t,
        h2_zbd3t TYPE mrm_rbkpv-zbd3t,
        h21_zbd1p TYPE mrm_rbkpv-zbd1p,
        h21_zbd1t TYPE mrm_rbkpv-zbd1t,
        h21_zbd2p TYPE mrm_rbkpv-zbd2p,
        h21_zbd2t TYPE mrm_rbkpv-zbd2t,
        h21_zbd3t TYPE mrm_rbkpv-zbd3t.
LOOP AT ti_drseg INTO h2_drseg WHERE selkz = 'X'.
    SELECT zbd1p zbd1t zbd2p zbd2t zbd3t
      FROM ekko
      INTO (h2_zbd1p, h2_zbd1t, h2_zbd2p, h2_zbd2t, h2_zbd3t)
      WHERE ebeln = h2_drseg-ebeln.
      IF sy-subrc EQ 0.
        IF h2_zbd1p GT h21_zbd1p.
          MOVE h2_zbd1p TO h21_zbd1p.
          MOVE h2_zbd1t TO h21_zbd1t.
          MOVE h2_zbd2p TO h21_zbd2p.
          MOVE h2_zbd2t TO h21_zbd2t.
          MOVE h2_zbd3t TO h21_zbd3t.
        ENDIF.
      ENDIF.
    ENDSELECT.
ENDLOOP.
IF h21_zbd1p GT i_rbkpv-zbd1p.
    MOVE h21_zbd1p TO e_zbd1p.
    MOVE h21_zbd1t TO e_zbd1t.
    MOVE h21_zbd2p TO e_zbd2p.
    MOVE h21_zbd2t TO e_zbd2t.
    MOVE h21_zbd3t TO e_zbd3t.
ENDIF.
*** Example 3: Setting ZLSPR depending on currency
CONSTANTS: c_zlspr_r VALUE 'R',
             c_waers_itl TYPE waers VALUE 'ITL'.
IF i_rbkpv-waers = c_waers_itl.
    MOVE c_zlspr_r TO e_zlspr.
ENDIF.
ENDMETHOD.
your case is similar to the first example.
Best regards.

Payment terms - 31 days and payment next

Our customer wants to have a new payment term, with the following condition:
31 days after invoice date, payment next month in the same day. I want to know, if it's possible to have this kind of payment term?
Ex:
invoice date: 02/01
payment next (D+31): 03/02
payment next: 03/03
I did this configuration on OBB8:
Baseline date calculation addition months: 1 (for 1 month); 2 (for two months)..
Default for baseline date: Document date
Payment terms number of days = 1
So, whit this configurations, for months with 30 days the rule is rigth, but for the other months, it isn´t work.
Thank´

Hi,
Define Fixed day = 3, and Additional months = 1.
rgds

FB60 - Credit Note: Baseline Date Determination

Hi Experts
At present I have an AP function who use FB60 to post manual Invoices and Credits to Vendors. The issue is that when a Credit is selected (Doc Type: KG) the baseline date and the subsequent due date are not being determined and have to be entered manually. The system will not let the user proceed until the data has been entered.
If FB65 credit (Doc Type: KG) is processed using the same data (Vendor, Date, Payment Terms etc) as used in FB60 the system determines the baseline date and due date.
I have also compared back to the legacy SAP 4.6 System and this functions correctly, the baseline and due dates are determined automatically.
I have worked through all of the standard configuration: Doc Types, Screen Layouts, Transaction Variants, Posting Keys, Default Values, Field Status Groups etc and cannot find the issue.
Please advise if you have any ideas or have experienced the same. My next step is to request one of the programmers to take a look.
Thanks. RS

Hello,
This is intended design from SAP.
See below OSS note:
https://service.sap.com/sap/support/notes/1446873
Because a credit memo is usually considered to be "due immediately", there is no indication which date the system should propose as a baseline date for payment (document/posting/CPU/other date?) if the terms of payment key (field ZTERM initial) is missing. For this reason, the user must set the required baseline date for payment manually.
To avoid this inconvenience, you have the following options:
1. Instead of the procedure described above, you use transaction FB65 (FB75) that is provided for this business transaction, because this is configured accordingly.
2. In the business partner master data, you define a terms of payment key for credit memos (field LFB1-GUZTE or KNB1-GUZTE). This can be used to give the program a default value for the baseline date for payment.
3. In your processing options (in FB60 You will find a button called EDITING OPTION in the top left), you set the #Always Use Payment Base Deadline# indicator (field RFOPTE-XZFBO='X').
Hope this helps.
Regards,
Karthik

Payment terms in downpayment request

After sales order we are creating down payment via VF01. Payment terms in billing document comes from the master data. However when the financial noted item i.e. request is created it ignores it and picks up the net due date i.e. posting date.
For example - Billing document and master data has payment terms as 4 days due net. This means that it is due 4 days from today i.e. 15 March. But the FI noted item (request) when it is created today it picks up due date as today's i.e. 11 March.
Has anyone come across the same issue.

Hi,
As you mentioned you above the down payment made will not through VF01, down payment will be through F-48.
VF01 is for creating billing Invoice docuemnt.
Payment terms will function when you assign the same at the time sales order creation( if customer master is not maintined with payment terms).
Please check your payment terms default for base line date is mantained as posting date or docuemnt date.
payments terms will work accordingly above said.
Regards,
Rama Mohan

Different payment terms !

Hi,
I created a standard flow of sales order, delivery and invoice where in the payment terms are automatically determined as say NL83.
But when i created a credit memo with reference to the standard invoice type ZF2 , paymant terms determined automatically are different say NL30.
Since payment terms are normally determined from the customer master (it is NL83 only)
Please let me know the reason behind having 2 different payment terms ?
Thanks in advance !

Hi,
The payment terms are available in customer master in company code data and sales area data billing tab.
the company code data payment terms are applicable when any transaction relevant to the company say credit management.
the sales area data payment terms are applicable when we do the sales direct transactions.
when credit memo and debit memo are created the payments are taken from the company code.
Please see the payment terms maintained in the company code data.
thanks
Kuntla

Payment term in customer master

Gurus,
XD02 - Change Customer Master
Payment term is maintained in
=> Company code data -> Payment Transactions -> Payment Data-> Payment term
=> Sales Area Data -> Billing Documents-> Delivery ad payment terms-> Terms of payment
In sales order, system propose payment term from Sales area data.
Please explain importance of these field.
Regards,
Ashish
Edited by: Ashish Desai on May 4, 2009 2:57 AM

Hi
In addition to all the suggestions given by all friends
If the invoicing is done thro SD route that is VF01 then the terms of payment maintained in sales area data will get preference
If the invoicing is done thro FI route that is FB70 then the terms of payment maintained in company code data will get preference
If the credit management is active then the terms of payement maintained in company code will take the control
For easy understanding as long as credit management is not active the terms of payment in sales area data will have the control as we are not going to touch FB70 at all mostly
As said by all others terms of payement is taken from payer
Regards
Raja

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

Baseline Date - Payment Terms

Similar Messages

Maybe you are looking for