Recurring document - FBD1 with incorrect due-date calculation for AP
Hi Gurus,
in our ECC 6.0 system we are creating with F.14 FI-documents (SAPF120) based on recurring documents (created with FBD1) for various purposes (e.g. Recurring entries for IC-business).
Therefore it's important that the system provides in the final processing of the recurring documents the correct net-due-date in the AP-document based on the document date and the payment term included in the AP-masterdata (LFB1-ZTERM).
Problem:
The processed FI-document contains the correct payment term but the calculated net-due-date with regards to the document date (BKPF-BLDAT) isn't correct. A Dummy-Update of the FI-document with FB02 on field BSEG-ZTERM provides finally the correct net due date but this a not recommended solution.
Any ideas how to solve that issue???
Thanks for replies.
BR, Bernd
Hi Vishnu,
the defined payment term is
fix day: 15
additional month: 1.
Default for baseline date is posting date
Therefore the expectation is that net due date is calculated for posting date
e.g. : 01.02.2012 to 15.03.2012.
The line item after processing in FI-document shows :
Posting Date : 01.02.2012
Bline Date: 01.02.2012
Days/percent: 35
Net due date: 07.03.2012 (dd.mm.yyyy)
That's wrong according to my understanding of the payment term definition.
BR, Bernd
Similar Messages
-
Due date calculation for the credit memo with invoice reference.
Hi,
When we create the credit memo with reference to invoice, the due date for the credit memo is getting copied from Invoice. In this case if the invoice is due on 31.12.2008 and the credit memo is created on 10.09.2009, then the credit memo due date is appearing as 31.12.2008. It should be 10.09.2009 as per the setting in VOFA billing type customisation in "Credit Memo w/vldt".
I would like to know how to customise the below requirement.
If the reference invoice is due after the credit memo creation, the the credit memo should due as per the invoice date.
If the invoice due is past & then the credit memo due date should be Immediate i.e. Due Immediately.
Thanks in advance for help.
Regards,
NithinI doubt there is such option. From the past projects I do remember that we made a change in the form to print the document date as 'Due Date' for credit memos. Credit memos were paid at once when they were processed and I think that payment term was copied from the original invoice, which made their due date far in future.
-
Hi SAP B1 experts:
When the user is going to create a AP Invoice does not matter what payment term appears in the document the due date is the same (03012010) format DDMMAAAA. It is like the system seems not to take this configuration in order to calculate the due date neither if you change the posting date to differents days.
At the moment to create e AR invoice the due date is calculated correctly, so is strange taking that the payment terms are the same for all the BP`s.
I do not know any configuration related with this, so I will appreciate whatever information.
Thanks in advance,
Manuel BarreroHi Manuel,
the due date calculation is influenced by a few factors.
Please have a look in the EES 'Dates in SAP Business One 2005A Sp01'. You'll find it in the archives of the psd calendar.
https://psd.sap-ag.de/PEC/calendar/
In that session most date calculations are explained in detail, including the due date. If you are an end customer, please contact your partner to make the presentation available to you.
All the best,
Kerstin -
Due Date Calculation on A/R Invoice
The Due date calculation on an Invoice for a customer with a payment condition of 30 days is wrong on the system:
Invoice DocDate: 11.05.17
Invoice DueDate: 11.07.01
On the BP Master Data is set a payment condition of 30 days. So it should be a due date of June, not July. This is a invoice that comes from a Sales Order with Approval Procedure.
Our version is 2007 A SP:00 PL:49.
Thanks in Advance...Hello,
Perfect Notification
For Payment Terms for Business Partner----
IF (@transaction_type = 'A' Or @transaction_type = 'U') AND @object_type = '17'
BEGIN
Declare @GroupNum as Nvarchar(20)
Declare @OCRDGroupNum as Nvarchar(20)
Declare @PaymentTermCode as Nvarchar(20)
Declare @PaymentTermName as Nvarchar(20)
Set @PaymentTermCode = (Select GroupNum from OCRD where CardCode = (Select CardCode from ORDR where DocEntry =@list_of_cols_val_tab_del))
Set @PaymentTermName = (Select PymntGroup from OCTG where GroupNum = @PaymentTermCode )
Set @GroupNum = (select GroupNum from ORDR where DocEntry =@list_of_cols_val_tab_del)
Set @OCRDGroupNum =(Select GroupNum from OCRD where CardCode = (Select CardCode from ORDR where DocEntry =@list_of_cols_val_tab_del))
If @GroupNum != @OCRDGroupNum
begin
SET @error = 10
SET @error_message = N'Payment Terms Should be ' + ' ' + @PaymentTermName + ' ' +' For this Business Partner'
end
END
End----
It will Definatillly Help You.
Thanks
Manvendra Singh Niranjan -
Baseline Date for Due Date Calculation required for S/L indicators
Hello,
Iu2019m facing the following problem
Iu2019m trying to insert an invoice (using a customer master record) but the system blocks me because the field ZFBDT (Baseline Date for Due Date Calculation) is a Required entry.
The strange thing is that if I use a S/L indicators the field is mandatory, if not the date may be defaulted.
I checked in OB41 but there are non differences between Special PK and normal PK.
Any ideas?
Thanks in advance
AlbertoDear Alberto,
the field "Due On (BSEG-ZFBDT)" cannot be controlled with field status.
It is controlled by field attribute of screen painter (Tcd: SE51). If
you look at element attribute for "Due On" field, a flag for required
entry is activated. In this case, field status has no control over
the field.
As of release 3.1G, field BSEG-ZFBDT is hardcoded in most FI screens
to be mandatory and cannot be influenced by any field status
changes. This situation is only valid when posting with special G/L
indicator (ie PK 29/39).
SAP development team has determined that this is a critical field. The
reason behind this is that this special GL screen and the data entered
here are very important to many other programs. This data affects
liabilities and receivables where due date is necessary almost
everytime. Thus, we changed this field in this screen in order to
prevent problems in many other areas. The reason is explained further
in note 95079.
I hope this helps You.
mauri -
How to make a single payment for different open items with same due date
Hi,
I have created a payment method and selected "Payment per due day " option in payment method company code settings.
Even I have selected that option, Payment will not happen grouping for the items with same due date
for ex : I have two open items with one due date and another open item with another due date so when I am trying performing F110 system should make a single payment for the item with same due date and seperate payment for another item.
But system making single payment for all items
Could you please suggest anything how to make a seperate payment with due date.
Regards
VK GUPTAHi,
Please check Vendor Master data: FK02 ->company code data -> Payment transaction accounting: unflag 'individual payment'.
Make a test and let me know if it's okay.
regards -
I am having problems importing my I photo pics into new Photo programme. I am importing approx 11,000 pics that all seem fine in I photo but the import rejects around 7,000 of them with incorrect mete data. What can I do to import these?
I have the same problem.
Thread here: Import fails - "Unable to get metadata" -
Dear Gurus,
Is there any std report is available which calculates due date for payments considering payment terma maintained in the purchase order . It should calculate due date from the date of GRN.
Rgds,
SaurabhHi Saurabh,
Check the following reports -
S_ALR_87012078 - Due Date Analysis for Open Items
S_ALR_87012084 - Open Items - Vendor Due Date Forecast
Regards,
Mike -
FBL5N & S_ALR_87012168 - Due Date Analysis for Open Items
Hi,
As per the above mentioned i could find the that there is differene in the account balances in FBL5N report and due date analysis for customers. Where as FBL1N and the vendor due date analysis figure in the report are same.
Just want to know why is difference in customer related.
Require a immediate reply.....please help me
Thanks in advance.
jaiHi
I could not understand which report you compared with s_alr_87012172.
Have you tried matching FD10N and FBL5N. If not matching, then there could be problem with authorizations in FBL5N.
From report S_ALR_87012168, you can also drill down to view the line items. Hence if you drill down and list the line items, it will give you some clue.
Try whether if any parked documents are included in FBL5N.
Also ensure that in report S_ALR_87012168, Database is selected in Data sources.
Regards -
Drill down report for due date analysis for customer open items
Hi, in transaction FDI0 i am using report 0SAPDUEAN-01 Due Date Analysis for Open Items .The reason i am using this is that s_alr_87012178 caters for only 6 intervals. With this report , i get 8 intervals:
daily intervals Due Not Due Total OI
0 - 30 0,00 0,00 0,00
31 - 60 67.000,00- 0,00 67.000,00-
61 - 90 0,00 0,00 0,00
91 - 120 20.020,86 0,00 20.020,86
121 - 150 3.270,00 0,00 3.270,00
151 - 180 0,00 0,00 0,00
181 - 210 0,00 0,00 0,00
211 - 99999 0,00 0,00 0,00
Total open items 43.709,14- 0,00 43.709,14-
Is it possible to change the intervals through custo? i need intervals:
0 - 30
31 - 60
91-120
121-150
151-365
>365Hi AA
refer this link where in I have given the screen shots
http://img233.imageshack.us/g/86081486.jpg/
The 1st screen shot is COPY of the Std Form
The 2nd scren shot shows how to add new interval
Br, Ajay M -
Due date analysis for G/L account
Hy!
I need to make a report that makes due date analysis for G/L accounts similar to S_ALR_87012078 Due date analysis for open items
for Account payable.
Has any one experience with that and can help me with that?
Regards,
MarinaHi Marina,
its a bit surprising why you require due date analysis for GL accounts as GL accounts are used for realtime posting and no credit involved. Only AR and AP accounts contain credit, so they may be even over due and thus we require ageing or due date analysis.
If transaction is on a cash basis should be posted to GL not to Subledger. Since there is no due date system for GL posting due date is not possible which makes sense too.
Hope this gets a better clarity for you.
Regards
Bharat -
Due Date symbol for Spl GL Transactions
Hi Everybody,
Need one help regarding Down payment entries with Spl GL Indicators. We have created 3 Spl GL indicators (1 - local vendors / 2 - imports vendors / 3 - capital vendors).
When we are posting payment entries using these Spl GL indicators, for Spl GL indictor 1, Net Due Date symbol is not getting captured. It is blank. However, for Spl GL indicators 2 & 3, it is getting captured.
I have checked these Spl GL indicators for any data mismtach. There is no mismatch. All are having the same data. I need to have the Net Due Date symbol for Spl GL 1 also.
Can somebody help on this.
With Best Regards,
HemanthHi:
This field ins contained in standard dynpro:SAPMF05A 304 and hence it is not possible to display payment due date and other fields like payment terms in down payments with special GLs indicator, The reason being that the terms of payment not only control the due date but also the cash discount terms. Hence it is not feasible to display terms of payment/due date in Down payments. DP forms part of balance sheet and hence it is not system design to display payment terms with special GL indicator, Hope it will help you.
Regards -
Dynamic Date Calculation for Current Date - 1
I am trying to create a variant with a dynamic date calculation attribute.
I am following the instructions as they are posted to the web but I get an error message.
I want to get all data EQ to the current date -1
In the object for selection screen I enter a D for Selection Variable, for Name of Variable I enter an I to include specific values and the option EQ for current date +/- ??? days. Then I enter 1- for the number of days. I have tried to enter this many times and in many ways but it doesn't work. I keep getting this message "lower limit of interval is greater than upper limit"Hi,
Welcome to SDN.
Selection-screen has four values -
SIGN
OPTION
LOW
HIGH
Pass your date value in the option low for the screen.
Sign you have already pass as I and option as EQ.
Regard,
Amit
Reward all helpful replies.
Can you paste your code here.
Message was edited by:
Amit Khare -
Due date grid for FP04 transaction
Hi Folks,
I need a report layout showing the due date grid for all the open items. Using FP04, I created layouts with all the required fields, but I'm unable to see the grid for due days. Few screenshots of the layout I designed and the summarization fields I defined in our system.
As shown in the output screenshot above, it doesn't display the total grid horizontally for a given customer, instead it is showing rows individually for each grid (30, 60,etc.).
Please advise how this can be fixed to show all the grids for a given customer (30, 60, 90, 180, etc.) in a single row.
Thanks in advance.
Regards,
SantoshHi Amlan,
Thanks for your response.
Here is the layout I have defined.
I initially had few subtotals maintained, but I removed them later as it was not working.
Please advise.
Thanks,
Santosh. -
PR delivery date calculation for TAB orders
Hi All,
1) The PR which is created via TAB item in the sales order - the delivery date for such PRs is equal to the delivery date in the sales order. This is happening only for TAB orders without BOM explosion in the sales order.
2)In BOM exploded sales order - (meaning the parent item is entered in the sales order with item category TAP. ) -The sub components of this parent item is auto populate in the sales order. If any one of these sub components have item category TAB...then it creates a PR which has the delivery date equal to the "Planned delivery time" in the info record.
Can anybody please explain why the PR default delivery date is different in the two cases explained above. Both are TAB items...the only difference is one is a stand alone TAB item and the other is via BOM explosion.
Your help will be highly appreciated.
Thanks
AshokHi Sasy
Delivery date calculation for MRP generated PR will follow the below settings
1) Purchasing processing time in the Plant parameters in the customization and is calculated based on the Factory calendar days.
2) Planned delivery time maintained in PIR and is calculated based on Normal calendar days
3)GR Processing time Maintained in Material master record, calculated based on Factory calender.
If you add up in the following sequence then you will get the exact delivery date.
Purchasing Processing time + Plnd delivery time + GR processing time.
Hope it will solve your issue.
Thanks / Karthik
Maybe you are looking for
-
1) I have an Iphone 5 and want to organize all my contacts /emails on line vs on the phone, how can I do that? It seems somehow I have about 10 listings for one person - I think some came when I hit facebook to sync - which was a mistake I dont want
-
Cancelation of partial line items in the MBST is not opening the delivery
Hi Gurus, We are posting the GR with 503 mvt type with ref to delivery. In this process when some of the line items have to be returned, we are posting MBST against those line items. To cancel / reverse the same in delivery using VL09, system (does n
-
Creating Aging Report and Counting report
Hi Everyone! Greetings to all of you, I would like to know where can i find some resources or step by step insruction to create aging report and also counting reports (i.e No of PO created for a period). If any of you have any information related to
-
I downloaded the app from iTunes costing 99 cents and when I click on the icon on my ipad or iPhone it quickly opens and crashes..closes???? iPad, Phonebook cleanmaster crashes
-
Best practice to send report to disabled users
Few users are not on CRM yet. They are setup as deactivated users and user lookup on the Account is a look-up to their user record. They would like a to get an automated weekly email/report showing the activity (appointments, email, etc.) scheduled