GRN Date as Baseline Date
Hi ,
Want system should capture GRN Posting Date as Base Line date while doing the MIRO.
( If payment term is 30 Days , then system shoulld calculate the 30 Days from GRN posting date )
Any Badi will serve this purpose ( INVOICE_UPDATE )
Thanks in advance.
Hi,
The BADI : MRM_PAYMENT_TERMS to you used to copy the GRN Posting Date as Base Line date while doing the MIRO
Go to T code : SE24 enter the object type CL_EX_MRM_PAYMENT_TERMS click display.
Copy the code and add the same code in your object for the BADI MRM_PAYMENT_TERMS I will work without any issue.
Thanks.
Similar Messages
-
Posting date as Baseline Date in Residual item
Hello,
While clearing a document with Residual Clearing method through F-28 system is automatically proposing end of the month as Baseline Date for the residual item (newly created item for the balance amount), whereas we want it to be the posting/document date but not the monthend as proposed by the system. Eventhough we have selected the option for default baseline date as posting date/document date in Payment Terms, system is proposing monthend date as baseline date for the residual item. I have set payment terms in customer master record as 0001 (immediate payment).
Because of the settings made for default baseline date in payment terms (SPRO/AR-AP) system is proposing document date as baseline date for new documents being posted, but we are facing problem only in case of residual items (new item created for the balance amount while doing residual clearing).
Please let me know the procedure to change the settings, so that posting/document date will become default baseline date for the newly created open item while doing residual clearing.
Thanks in AdvanceHi,
Try to take a look the setting of the following transaction,
IMG> FA> AR & AP> Business Transactions> Incoming Payments> Manual Incoming Payments> Define Tolerances
See what has been set for payment term for Residual Items.
Regards, -
Invoice verification Invoice date,Posting date and Baseline Date
Hi Sap Gurus
Pls Tell Me in detail what Dates should be entered at MIRO transaction,
Invoice date,Posting date and Baseline Date
i presumed that the date on the Invoice slip will be Invoice date,
But in the Invoice the Date is very long back, say a month Older,
the month of Posting as Posting date, but any posting Date made in MIRO will be Paid after 2 or 3 months so in this case what should be the Posting date.
at Base line date in the present company Senario the Discount on Vendor payment is literally valid for all the time , say
In Invoice if the condition is 10% discount if paid in 30 days is given.
but in actual sense the Vendor is paid 10% less even if he is paid after 4 or 6 months also, so in this case what should be the Entry in Baseline date
another senario is the vendor has sent only one Invoice for 2 POs how can this be accomadated in SAP
Pls suggest its Urgent,
Age may have a Bar, But Points No Bar
Thanks and Regards
SathishHi
LIV is nothing but You are getting Invoice from the Vendor for your PO and GR.....and you are checking the Invoice for Price, Qty,Amount etc. by refering the PO and posting the Invoice...
Invoice Date :
The date of Vendor' Invoice...ie) Date at which the vendor Raised the invoice for his supply against your PO...
Posting Date :
The Date at which you actually Verifying Vendor's Invoice and doing the Posting...
base line date :
Generally the Posting Date...
The Imp. of Baseline date is for eg)
If in the Payment Terms if some conditions are maintained like say
10% Discount for Payment With in 30 days, if
PO created on 01.11.2007.
GR done at 10.11.2007.
Invoice slip Received at 30.11.2007 but having the Date on it as 20.11.2007...
So as per your terms you will get 10% Discount if you make the payment on or 20.12.07....
Here if you keep inv. Date: 20.11.2007 and Posting Date : 30.11.2007 and Baseline Date as 30.11.2007 ( you cannot maintain baseline date earlier than Posting date)....even though as per terms the you are eligible for discount if you make the payment on or before 20.11.2007.....as per the system you are still eligible to get the Discount if you make payment on or 30.12.2007( since you have maintained baseline date as 30.11.2007)...
this way Baseline date is Importane...
Generally we use to maintain always Posting Date as Baseline date....
It is advantageous..
Reward if useful
regards
S.Baskaran -
Invoice posting - set document date as baseline date
Hi Expert!
I have issue regardig invoice posting.
When invoice posting transactions are done, the baseline date in the transaction is changing due to unknown reasons. The baseline date should not change and should be the document date. This in turn is having effects on the culculation of the due date for the payment terms.
In this case, i would like to make the document date as the default baseline date and remove the option of changing the baseline date. Please guide me on how to do it step by step.. Please also advise step by step how can i do that in transaction MIRO, FB60, FV60, FB65 and FV65..
Thanks..prashant,
let say i have 3 company codes but i want to set the document date as the default for baseline date only for 2 company codes, how? If i tick on document date in the path u've given, will it be affected to all of company codes?
Where can i check for the payment terms against company code? Because payment terms in the path u've given seems like different than what is being using in the PO currently..
In the path there are 0001, 0002 and 0003 but payment terms which are being using in the PO are K160, K162....
Please advise.. -
MIRO: How to set GR date as baseline date ?
dear friends,
can we set the GR date as the baseline date in MIRO (either GR doc posting date or Document date )?Hi,
Baseline date is configured based on Payment Terms, that can be possible using customizing, there is no relation with GR date and other dates.
Still if you want set the Baseline date with some other default date or PO date, or GR date, -
IT IS POSSIBLE
by enhancements
directly applying enhancements will not work for you, you just have to work smartly by applying 2 enhancements to get the desired results
I will tell you how to do that, just let me know the version of SAP you are working on..
I tried it on ECC 6, and it is working very fine -
Baseline Date as the Document Date
Hi,
I have a query on Payment Terms which we maintain in the Posting Parameters->Postings Tab page in RE-FX Lease Out Contract.
I maintain a payment term for 10 days in the RE-FX Contract.
I have maintained a Condition which is due on 1st of every month with a monthly frequency.
When i simulate the contract for planned Cash Flow, it shows me the conditions which are due to be posted on 1st of every month. Now, here is a scenario wherein I am unable to post the conditions through Periodic Posting (RERAPP) on 1st and i eventually carry out the Posting on 16th of that month. Hence I maintain Document Date and Posting date in the T Code RERAPP (Periodic Posting) as 16th of that month.
Now when i open the Customer Line Items in FBL5N, i find that the Document Date and Posting date to be 16th whereas the Baseline date to be 1st of that month. This makes the calculation of Due Date totally wrong since the system takes 1st of that month as Baseline Date and adds Payment Term days (10 days) to it and shows 11th of that month as the Net due date (which instead should have been 26th of that month.
I tried changing the definition of Baseline Date in the Payment Terms definition to Document Date but it still did not bring the desired effect.
PankajHi,
I face similar problem but not involving TRM.
I've payment term set-up in OBB8 and stating default baseline date = document date.
But in FBL5N system is always retrieving posting date as baseline date. Is there any other setting prevailing over payment term definition?
Regards,
Baptiste -
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. -
Substitution - Baseline Date to be replaced by the Goods Receipt date
Dear Forum,
We have the payment terms defined in the system, with the baseline date corresponding to the 'Document Date' and the credit terms as 60 Days. The users now desire that the Baseline Date should instead correspond to the Goods Receipt Date. To enable this we need to define the substitution such as the Baseline Date at the time of Invoice Verification gets substituted by the Goods Receipt Date, if the GR Date is earlier than the IV date.
Would appreciate help from the friends as to how to configure this and which feilds to be chosen and replaced.
Thanks!
Regards,Hi
You can make the Baseline Date in Invoice (MIRO) with Goods Receipt Date using BADI.
BADI -->MRM_PAYMENT_TERMS
Tell your ABAP Guy to work on this BADI.
In the BADI, MRM_PAYMENT_TERMS Read the Value in WEBUD of Internal Table TI_DRSEG and Pass it into E_ZFBDT.
Also if the Baseline Date is changed manually, then after posting you can see the Goods Receipt Date in Baseline Date.
This resolves your issue.
regards
venkat -
Baseline date in MIR7 cannot be refreshed
Dear experts,
I've got a question in using MIR7 to park invoice. I found that if I changed the document date, the baseline date cannot be refreshed automatically. It leads a result that the net due date is calculated wrongly.
So I would like to know is there any way to solve this problem?
Regards,
IvyHi,
If u want the baseline date to be the same as the document date, you can go for substitution.
Regards,
sridevi
<i>Please assign points, if useful</i> -
Billing created on date as the baseline date in FBL5N
Hello All,
We have a requirement where the baseline date in FBL5N (BSEG-ZFBDT) should be the Billing document created ( VBRK-ERDAT) and not the accounting document created on date.
I tried changing the Payment terms to "Document date" but it does not work either. The fields in the payment terms for base line date ( Document date, posting date, entry date ) refer to the accounting document and not the Billing document.
Please let me know how to go about this.
Thanks for your help in advance.
Thanks,
NagarajuHi,
I face similar problem but not involving TRM.
I've payment term set-up in OBB8 and stating default baseline date = document date.
But in FBL5N system is always retrieving posting date as baseline date. Is there any other setting prevailing over payment term definition?
Regards,
Baptiste -
Baseline date change after the creation of invoice list
When I create invoice document, the invoice date (vbrk-fkdat) is the end of the month and the invoice list date (VBRK-FKDAT_RL) is the next business day after the invoice date, the baseline date of the accounting document (bseg-zfbdt) is the document creation date and this is what I wanted.
However, when I start to create the invoice list, the baseline date on the accounting document (field bseg-ZFBDT) is changed to the invoice list date. Does anyone know why and how to fix and where to look in the configuration to see how invoice list date (vbrk-fkdat_rl) is populated? It seems to me that the baseline date default back to the invoice list date when invoice list document is created. Thanks for your help. I also posted this question in the ERP Financial thread.Hi Valerie,
do you recall the User Exit?
Thanks -
Baseline date change after creation invoice list
When I create invoice document, the invoice date (vbrk-fkdat) is the end of the month and the invoice list date (VBRK-FKDAT_RL) is the next business day after the invoice date, the baseline date of the accounting document (bseg-zfbdt) is the document creation date and this is what I wanted.
However, when I start to create the invoice list, the baseline date on the accounting document (field bseg-ZFBDT) is changed to the invoice date. Does anyone know why and how to fix and where to look in the configuration to see how invoice list date (vbrk-fkdat_rl) is populated? It seems to me that the baseline date default back to the invoice list date when invoice list document is created. Thanks for your help.Hi
You need to check your payment terms. the baseline date is determined from the payment terms, which is assigned to the vendor. You can use OBB8 to see the config of payment terms.
Regards
Sanil Bhandari -
System captures the baseline date as the document date
Hi All,
User has changed the Baseline date as 05/11/2011 in the parked document 12345644/ 54123456 via t-code FV60, however, when the document was posted, the baseline date u201Cdefaultsu201D to the document date.
Appreciate any one suggest me on this issue
NandhaHi Ravi,
The system is defaults to capture the document date as baseline date, the user wants to change the baseline date which has been captured by the system, then he changed the baseline date while posting the vendor park invoice.
later he is saying that the changed baseline date is not taken again it has taken the document only. why it has happend like this.
one question:- is user can change the baseline date while posting the vendor invoice ? if he can change how the system should be configured for this where the setting should be made to take baseline date as given by the user.
Appreciate any one suggest me on this request.
Thanks
Nandha -
Interest Calculation on posting date and due date
Hi
I want vendor interest calculation on due date as well as posting date. Let me know how to get it. According to me only its possible on the basis of one date only.HEllo!
In the report RFINTITAR, you use the interest indicator customizing:
IMG > Prepare Item Interest Calculation > Ref. Date
(table V_T056UX) > field Ref.
(FI Item Interest Calculation: Reference Date)
You have the possibility to define what You need to be considered as
incoming payment due date, choosing between:
1 Value Date (or Baseline Date for Net Payment)
2 Document Date
3 Posting Date
4 Payment Baseline Date
As you can use one interest indicator per customer/vendor you can use only of the dates is used. But, in this
program you can use the BADI FI_INT_CUS01. Please, check if you can meet your business requirements using the methods
of the BADI.
REgards,
REnan -
Calendar date & net due date (FI) PAYMENT TERMS - OBB8 Vendor Invoice
I read many posts on SDN forum about the topic.
Anyway, I didn't find a simple solution for that.
My aim is is to calculate a net due date based on working days.
So, If I've got a 30 days document days payment term ("Deafult for baseline date" = Document date ; Additional Months = '2'), a Vendor Invoice (document date = 12.05.2011), by standard net due date will be 12.06.2011.
FROM 12.05.2011 to 12.06.2011 =
32 CALENDAR DAYS
22 WORKDAYS (32 minus 10 holyday - 2 weekends)
WORKDAYS PAYMENT TERMS Within 30 workdays Due net
Vendor Invoice document date = 12.05.2011
plus 30 workdays = DUE DATE 22.06.2011 (and not 12.06.2011)
Can I obtain that with a standard functionality?
Edited by: Roberto Buono on Jul 1, 2011 2:29 PMHi,
Sadly this is not available as standard. As per your need the Net due date should be worked out by using a factory calendar; but what this does is it delinks the direct correlation between the number of days in the payment terms with the difference between the due date and baseline date. I hope you are aware that Net Due date is not stored but is a variable calculated during run time in reports.
There are four things you can try:
1. The simplest to do is: As the number of weekends are fixed; and if the intention is to give a 30 working day term, then add on the number of weekends and make the payment term effectively for say 40 days. There will be marginal variations over what you want. Best part here is that config remains standard.
2. All the receivable reports will use a function module (usually the same one) to calculate the net due date; enhance the FM and make it consider a factory calendar for calculating due date.
3. Enhance the accounting interface, and in runtime; modify the days that are coming from the payment term; based on a factory calendar, and update the accounting document. This delinks the days mentioned in the payment term and the accounting document and may not be palatable.
4. Enhance the accounting interface, and in runtime; calculate the due date and update the baseline date with it and make the payment term as "Immediate" yielding the desired due date. Not very elegant. Alternatively add to the baseline date days equivalent to holidays and weekends and keep the days from payment terms constant and update the accounting document. Better...
All four options have somes pros and cons. I do not see any other means of acheiving what you want. Maybe you could restrict users to a custom receivables/due date/ageing report which delivers what you want and lock the standard reports.
Cheers..
Maybe you are looking for
-
Switching boot drive to new internal drive??
I just got a new 150 gb internal drive installed and I've been trying to install the restore software to use it for the new boot drive instead of my old 80 gb. Disk Utility will recognize it but the install software process just shows the old drive.
-
Worse Quality than Deezer! :-(
Hey guys! I am really disapointed! I just compared my Spotify-Premium with Deezer and came to the conlusion, that the same track sounds ways better on Deezer. Could you please tell me why I'm paying the same price for worse quality? Best regards Cami
-
R3trans does work on NetWeaver 7.01 ABAP Trial Version
Hi, I have just installed a NetWeaver 7.01 ABAP Trial Version on my laptop(Windows). I need to run "r3trans" command on this system, but it failed, the error message said "connect failed with DBLI_RC_LOAD_LIB_FAILED". When I executed the "r3trans" co
-
Adobe Shockwave Player version 11.5.0.595
Install Adobe Shockwave Player Adobe Shockwave Player version 11.5.0.595 Windows | English | 3.33 MB http://sdc.shockwave.com/shockwave/download/download.cgi
-
IPhone dock with a message or notification front led
Hello there, is there a chance to get the iPhone dock with a message led in front to signalize whether there are unread messages and mails, lost calls or any other notification, e.g. low battery? All docks I found so far are non-communicative as well