Importance of Due date ?

Hi Experts,
while we create the company code, what is the relevance of defining the due date range ?
regards,
Sanju

Hi
Due Date:
Date that detemines when the transaction documeneted becomes financially significant:
For Ex: in ur sales invocie u have to give the due date like when he has to pay the Amount for that Invoice as per ur terms & Condtions ( Net pay 30 - 60 - 90 days).
As per that date only the customer will pay to u and the cycle will close for that sales transaction.
same thing will follows while ur paying to ur vendor.
Giri

Similar Messages

Regarding new Reminder app in Mountain Lion: is there a away to sort reminders by due date in the same fashion you can in the iCloud version of Reminders?

Regarding new Reminder app in Mountain Lion: is there a way to sort reminders in due date order in the same fashion as you can in the iCloud version of Reminders?

So true! I have to agree: "It appears Reminders in 10.8 did not get a whole lot of thought put into it regarding how folks actually use reminders."
With Mountain Lion, Reminders no longer resembles a task-management (to-do) app in any way. I used to be able to limp along using it for my to-dos (although it never did accommodate this need well). This upgrade has made Reminders completely unusable for task management.
Once I got over my disappointment, I did some research and decided to try "Things." This application has all the functionality I've been wanting all along. It has a Mac version, an iPhone version, and an iPad version (among others)--and it keeps all devices synched via the Cloud (just not the iCloud ... but who needs the i ?). I wish I'd discovered it years ago. I'm glad now that Mountain Lion put Reminders over the edge; otherwise, I would not have made this discovery.
"Things" (oddly named though it is) comes close to the old Franklin planner software I used to love and haven't been able to find a substitute for. It can import items from Reminders, and it works with Siri. It's a joy to use, and it does everything I want it to do plus some things I never thought of and will use all the time. I downloaded the free trial version last night and within an hour paid for it with gratitude.

Fields on transaction S_ALR_87012168 -Due Date analysis for open Items

Hello Gurus
I am not able to find the technical name for report on fields due date 0-30,31-60 and so on because F1 does not work on those fields.
Do you know the fields name and SAP table?
Thanks in advance

Hello,
Please go to the FunctionPool SAPLKYRE and then click on the statement "INCLUDE lkyref20. " Subprograms for reading data". In the subprogram "LKYREF20" click on INCLUDE LKYREF2B . " READ_TABLES. Now in the Include LKYREF2B you can see the tables which are used for the output of the transaction S_ALR_87012168. I am not sure, how important it will be for you, but after a lot of R&D, I could get this information. You may let me know your findings.
Thanks and regards,
Suresh Jayanthi.

How to make net due date dependent on Payment Terms in credit memo FB75

Hi Experts,
In our system currently when we create credit memo using tcode FB75 system makes the invoive due immediately.
We wanted to make this net due date dependent on payment terms given by us. Please let me know how can I achieve this..
Please let me know if there is any user exit there or the configration path to achieve this...
Regards,
Vidya

Hi,
"vbdkr-zterm. is nothing but Payment terms
*   Fetching Payment term details
    SELECT SINGLE * FROM t052 INTO w_t052 WHERE zterm = vbdkr-zterm.
    IF sy-subrc = 0.
      CLEAR i_faede.
      MOVE-CORRESPONDING w_t052 TO i_faede.
      MOVE: w_t052-ztag1 TO i_faede-zbd1t,
      w_t052-ztag2 TO i_faede-zbd2t,
      w_t052-ztag3 TO i_faede-zbd3t.
      i_faede-bldat = BKPF-budat.                         "this is Importnat posting date
      i_faede-koart = 'D'.
*     Fetching Due date using Function Module
      CALL FUNCTION 'DETERMINE_DUE_DATE'
        EXPORTING
          i_faede                    = i_faede
        IMPORTING
          e_faede                    = e_faede
        EXCEPTIONS
          account_type_not_supported = 1
          OTHERS                     = 2.
      IF sy-subrc <> 0.
      ENDIF.
      w_invdate = e_faede-netdt.              "this field contains Net due date...
    ENDIF.
Prabhudas

Function Module to Calculate Due Date from Payment Terms?

I'm writing an aged debtor report as the SAP standard one isn't quite right for our requirements. Is there a function module that will calculate the payment due date if I give it the payment terms and the base line date?
I did a search in SE37 but couldn't see one which fitted my requirements (I was searching on CALCDUEDATE and variantions of).
Any suggestions welcome, thanks.
Gill

Hi,
Use the FM FI_TERMS_OF_PAYMENT_PROPOSE for calculating the Payment due date
call function 'FI_TERMS_OF_PAYMENT_PROPOSE'
exporting
    i_bldat         = gv_bldat
    i_budat         = gv_budat
    i_cpudt         = sy-datum
    i_zfbdt         = gv_zfbdt
    i_zterm         = gv_terms_paym
    i_bukrs         = gv_comp_code
importing
    e_zbd1t         = gv_zbd1t
    e_zbd1p         = gv_zbd1p
    e_zbd2t         = gv_zbd2t
    e_zbd3t         = gv_zbd3t.
Regards,
Dwaraka.S

Wrong due date on vendor invoices

Hi SAP Gurus,
I am facing one issue in due date calculation for Vendor open item.
I have maintained terms of payment in vendor master data in which invoice due date should be 30 days after invoice generation. But this terms of payment is not picked automatically in vendor invoices (it is blank) and system is considering all the open items for payment during Automatic Payment Program.
Need your help to understand why system is not picking terms of payment automatically in vendor invoices when it is already there in vendor master data.
Many thanks for all your help.
Regards,
SATVIR SINGH

Hi,
In invoice is posted through MIRO then terms of payment applied in purchase organization segment of vendor master data has top priority over one which is entered in company code segment.
For items posted directly in FI terms of payment in company code segment is considered.
Moreover if some one edits default terms of payment at the time of invoice then terms of payment entered at the time or payment will be updated in vendor invoice or line items.
If no term s of payment is entered in vendor line item then invoice is due immediately on the base line date of invoice.
Also check document change log in tcode FB04 to ensure terms of payment is not edited after document is posted.
Next payment date you enter while secluding the payment run is important thing to consider for payment to consider in current payment run.
Thanks!
Raju

Change in payment due date

My bill has always been due on the first of the month. You are now changing my due date to the 27th of the month. So for the month of June, I will have made two payments to you, one on the 1st and one on the 27th. Then my payment will be due on 27 July and every month until the end of the year. I will have made 13 payments to you in this year. Next year, I assume that my bill will be due on the 27th of every month, so I will pay the bill 12 times. Why am I paying you 13 times this year and twice in one month?

ATT send me a text last week and again today:
Starting in June 2015, AT&T will standardize the number of days wireless and Digital Life customers have to pay their bill. As a result, a due date earlier or later than usual may appear on your wireless and/or Digital Life bill.
Due Date Change
If you receive a message on your bill, text message, or email directing you to this page, your due date will change. Otherwise, your payment date will be the same.
Important Note
No changes to monthly charges - A change to your payment due date only affects the amount of time you have to pay your bill. You will have about three weeks after the close of your billing cycle to make a payment. The change to your due date does not affect your billing cycle or billed charges.

Error in invoice due date

Hi all,
i need to fetch invoice due date data(FAEDT) using the FM 'DETERMINE_DUE_DATE'.i passed ZFBDT(base line date) and ZTERM(payment terms) and fetching the invoice due date.
DATA : ZFBDT TYPE DATS,
       ZTERM TYPE BSAK-ZTERM,
       FAEDT TYPE DATS.
CALL FUNCTION 'DETERMINE_DUE_DATE'
    EXPORTING
      I_FAEDE                          = ZFBDT
     I_GL_FAEDE                       = ZTERM
     IMPORTING
     E_FAEDE                          = FAEDT
EXCEPTIONS
ACCOUNT_TYPE_NOT_SUPPORTED       = 1
OTHERS                           = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
but iam getting error as zterm is not there in the parameters.can you please guide me how to fetch invoice due date.thank you.

Yes Lakshmipathi,The Pricing type in Copy control is G and I also tried to replicate this Issue in our Quality system but I am getting the Netvalue copied from Sales order and no pricing error .
Only thing odd I see on our Production System is that I am seeing this Message
Unit of measure VPRS is not defined within the delivery or UoM group
Message no. O3136
We are in 4.7 IS-Oil System,would like to know the relevannce of this message with the Pricing error in Invoice.
Thanks and Regards
Mohammed Roshan

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

To find cash discount due date for invoice

Hi,
is there any fuction module to get cash discount due date using Payment term Zterm, Ztag:1Days from Baseline Date for Payment and Ztag2:Days from Baseline Date for Payment from T052 table.
Regards,
santosh

check the below fuction module.
CALL FUNCTION 'DETERMINE_DUE_DATE'
EXPORTING
    I_FAEDE                          = faede
IMPORTING
   E_FAEDE                          = faede
EXCEPTIONS
   ACCOUNT_TYPE_NOT_SUPPORTED       = 1
   OTHERS                           = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
you can pass the zterm and Days from Baseline Date for Payment from T052 table to correspoinding fields of faede structure .
Thanks and Regards,
pavankumar

Special G/L indicator and due date

Dear all,
In FB01 when I post on customer account with special GL indicator, in the next screen the "due date" field is mandatory.
I would like to fill this field automatically. I tried via substitution, but it doesn't seem to work with "due date".
Do you have any suggestions please?
Many thanks,
Becky

Hello,
Please note that the due date field is as per standard design as per the SAP note 95079.
Field BSEG-ZFBDT is hardcoded in most FI screens to be mandatory and cannot be influenced by any field status changes. This situation only valid when posting with special G/L indicator (downpayment).
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.
Could you try the following :
- Change in SE51 the requirement condition (field attribute). However, this would be deemed as a modification to the standard
system. You may be responsible for any negative consequences once decided to make such modification.
- You can also try Use a substitution rule (like: if special GL = A and user = ... and account = ... and.... then BSEG-ZFBDT = today). I am surprised to know that this doesn't work for you. Are you getting any error message while subsititution is triggered?
Thanks for your cooperation and understanding.
Best regards,
Suresh Jayanthi.

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,
Hemanth

Hi:
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

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
Alberto

Dear 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

Batch management - due dates

hi
my location is Chile ..
I would comment as follows:
Within what is the batch management in SAP Business One, specifically when it is done out of a product, you can view the lots available and implement a self-selection button.
This button takes lots available SAP considering the order given, and that follows an alphabetical or numerical order. Companies usually look at the batch management to keep track of due dates for a product, so it would be very important to give an order to the self-selection of lots based on this variable.
Currently to fix this, you define a code of covering a lot Loig based on product expiration date so that they can be downloaded from the inventory then consider this criterion.
Greetings,
Paul Ponce

You have two separate issues here.
The first issue here is activating batch management for a material of which there is inventory. This is not easy. There are many threads out there on this. Here's two of them.
wants to activate batch management for a material which already had a Stock
http://www.sapfans.com/forums/viewtopic.php?t=289203
Basically you have to remove your inventory of the material from the system via a material movement like 562, activate batch management, then bring the material back like via a 561 movement type. You can reload the inventory using 561 directly into the batches you want to create from your exisiting inventory or as SAP suggested, load it as a single batch, then use standard stock movements to transfer the inventory into the actual batches.
Once you do that, you must update the batch records with the proper expiration dates, (MSC2N) for your exisitng inventory.
As far as reinspection, there are many threads on setting that up. Here are some to get you started.
http://help.sap.com/saphelp_470/helpdata/en/be/00bbcfca5311d2961800a0c930e04c/content.htm
http://help.sap.com/saphelp_46c/helpdata/ru/6d/bb16f840f311d4b2f20050da4ceab0/content.htm
recurring inspection
Deadline Monitoring: QA07
FF

Subroutine in sapscript for net due date

Hi,
This is the first time I am creating a subroutine for sapscript and I could not get it to work. I need to calculate the net due date using the baseline date plus cash discount days. But the form is just printing out 0000000. I am just trying to extract one due date here but I will have to get it for all line items then sort descending to get the latest one. Can anyone help me to see the gap why this is not working?
In the sapscript I have the following:
DEFINE &BASEDATE& = &REGUP-ZFBDT&
DEFINE &PAYTERMS& = &REGUP-ZBD1T&
PERFORM NET_DUE_DATE IN PROGRAM Z_SAPSCRIPT_FUNCTIONS
USING &BASEDATE&
USING &PAYTERMS&
CHANGING &DUEDATE&
ENDPERFORM
In program Z_SAPSCRIPT_FUNCTIONS
Thanks in advance!
Cholen

Hi Raju!
I am really getting close! I did the conversion for all variables, however for VBLNR, it does not work. It gives leading zeroes but the value starts with a 'P' before the zeroes and the numeric value. I tried to remove that from the where clause and my select finally got something. However the output on the form is in the internal format. I suppose I should use CONVERT_DATE_TO_EXTERNAL which I tried doing after out_tab-value = lv_netduedate which is the variable I am passing to the form.
Raju Shrestha wrote:
Hi Cholen,
I believe your lv_laufd is a 10 character field in format MM/DD/YYY or DD/MM/YYYY. You should move that data to a 8 character variable (say lv_date) in YYYYDDMM format.
Please try this conversion
    CALL FUNCTION 'CONVERT_DATE_TO_INTERNAL'
      EXPORTING
        date_external            = lv_laufd
      IMPORTING
        date_internal            = lv_date
      EXCEPTIONS
        date_external_is_invalid = 1
        OTHERS                   = 2.
Check in debug, you should get lv_date in YYYYMMDD. Now use lv_date in your WHERE clause.
If you still do not get data after lv_date eq YYYYMMDD, check your LIFNR and KUNNR. They should be 10 charaters with leading zeroes if not 10 .
If needed use the conversion for lv_lifnr and lv_kunnr.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
      EXPORTING
        date_external            = lv_lifnr
      IMPORTING
        date_internal            = lv_lifnr.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
      EXPORTING
        date_external            = lv_kunnr
      IMPORTING
        date_internal            = lv_kunnr.
Cheers,
Raju.

Importance of Due date ?

Similar Messages

Maybe you are looking for