SPl G/L posting Due on Date field should mandatory field .

Hi ,
while posting special G/l code 'G', (Advances from vendor with posting Key-29 ) I need  Due on Field as Mondatory field, (Baseline date for due date calculation
Date to which the periods for the cash discount deadline and the due date for net payment refer. This is the case for line items in open item accounts.) it is giving other Spl G/l code except this code, it is in suppress mode. anybody can help me how get this field as reqd.( I have given same field status group and same reconciliation account also, for which I am getting it is a mondatory field eventhough it is not showing)
Regards,
SYReddy.

1) use validation :  OB28
2) tcode OB41
A.

Similar Messages

  • :Due On" date field missing while posting with Spl GL indicator for vendor

    Hello,
    I am facing a problen while posting a n entry with spl GL indicator in fb01, the issue is Due On date field is missing in the screen.
    I am posting an spl GL transaction for a vendor thro FB01 and after entering the posting key 39, vendor code and spl Gl indicator in line item and in next screen, the "Due ON" date field is not appearing.
    Both vendor recon account and spl GL alternative account use same field status group and  checked the field status group , the due date, payments terms are made optional.
    The strange thing is, when I use the same vendor with Spl GL indicator "A" , the Due ON field is missing in next screen, and when I use spl indicator " B" , for same vendor, Due On date field is appearing.
    Is there any specfic field status setting for DUE ON date field for Spl GL indicator wise? or please help me how to bring due on date field in the screen when posting spl GL transaction?
    Please help me on this.
    Regards
    Surya

    Hello Surya,
    To make field baseline date for payment (BSEG-ZFBDT) ready for input for
    posting the down payment, the following Customizing setting is
    necessary:
    Financial Accounting -> Accounts Receivable and Accounts Payable ->
    Business Transactions -> Outgoing Payments -> Automatic Outgoing Payment
    -> Payment Method/Bank Selection -> Configure payment program -> All
    company codes -> double-click on corresponding company code -> under
    Customer -> 'Sp. G/L transactions to be paid' the letter A should be
    entered.
    The field "Due On (BSEG-ZFBDT)" cannot be controlled with field status.
    It is contolled 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.
    545944    FAQ, down payment, tax code, baseline date
    above Field is controlled through SE51 only.
    Tcode : SE51
    Program (screen)     SAPMF05A
    Screen number        304
    Eliment list  press display.
    special attributes.
    BSEG-ZFBDT - Required.
    Other options are below.
         The attribute "Input" can have the following values:
         o    Not possible
             The input/output field cannot be supplied with an input - that
             the screen element can only be used for outputs.
         o   Possible
             The input/output field can be supplied with an input at runtime
             the remainder of the transaction, an input is not required.
         o   Recommended (Optional Field)
             The input/output field should be supplied with an input at runt
             The system, of course, does not check immediately whether there
             been an input. During the remainder of the transaction, however
             input is necessary.
             To mark this kind of target field, the input template starts wi
             special character that is represented in the Screen Painter by
             question mark ('?'). The question mark will be suppressed only
             the field is in a table control or a step loop.
             You use the "target field", for example, if inputs cover severa
             screens and only at a later stage are subject to a common check
    o   Required Field
        The input/output field must be supplied with an input at runtime.
        The system checks this property immediately, and very definitely
        when the event is processed  (PROCESS AFTER INPUT).
        So that such a required field is marked accordingly, its input
        template must begin with a special character that is represented in
        the Screen Painter by a question mark ('?'). The question mark is
        suppressed only if the field is in a table control or a step loop.
    I hope above information will resolve your issue.
    Kind Regards,
    Fernando Evangelista

  • Posting / Due / Document date trouble

    Hi there,
    i have a little bit trouble with the dates. I already read a sheet about dates in SAP, but there are some misunderstandings. Here is the scenario, in which i have problems :
    I book a incoming payment ( Posting date : 15.11.2008 | due date : 02.11.2008 | document date : 15.11.2008)
    You find the payment in the general ledger with the correct dates. Now i find out, that i made some mistakes and i have to cancel the incoming payment. I cancel the incoming payment and i find a wrong due date in the in the general ledger (not 02.11.2008 -> 15.11.2008). Cause of booking date and cancel date is the same time, the systems do not ask for the date.
    I do not understand the correct meaning of posting, due and document for incoming and outgoing payments.
    I book the incoming payments by means of the bank statements. In my opinion the posting date is the time i book the incoming payment, the valuta date is the due date and the document date is the bank statement date. But i think i am wrong with my opinion, cause of my experience with the cancellation.
    Pleas give me an advise, the general ledger is going wrong.
    Thanks and regards

    Hi Gordon,
    hi community,
    as your mentioned i was trying your last comment :
    Depending on the date you receive the payment, you could use this date for all Posting / Due / Document date. Just keep the consistency for your date. Which ever you like, do not confuse yourself.
    I changed the posting / document date of incoming payments to the date of receiving the payment. E.g.
    Invoice date is 22.12.2008, Incoming Payment 13.01.2009, and today i got the bank statement and book it into SAP.
    If i do so posting date = incoming payment date, the system warns "There is a document of this type with a later posting date". I was already searching the forum about this message and i am not sure if it is ok to ignore this message.
    Thanks Steffen

  • Confusion about posting, due, doc date

    Hello there,
    I am very confused by dates used in SBO documents, could anyone please explain for me?
    For example,
    We receive an invoice from supplier, which is dated on 1st Oct. And then we input it into SAP on 5th Oct.
    Based on the payment term, say 30 days, we should pay it by the 4th of Nov (1st Oct +30 days).
    So ...
    Which is posting date, due date and document date?
    As I believe, posting date is 05/10 (as we posted it), due date is 04/11 (when the invoice is due), document date is 01/10 (as the date is on the document).   Is that wrong?
    If I am right, then
    why is that most of reports don't show "document date" but only posting date and due date, such as BP balance, bank reconciliation.
    Another example is Cash discount defination, it uses "Days After Posting Date" to calculate discount ...
    Hopefully, I am not wrong ...
    Edited by: Y on Oct 17, 2008 5:36 PM
    Edited by: Y on Oct 17, 2008 5:36 PM

    Hi Y,
    here are some perinent excerpts from the EES:
    Posting Date:
    Date that determines in which u2018Posting Periodu2019 a document or journal entry is added to the database.
    Due Date:
    Date that determines when the transaction documented becomes financially significant.
    Document Date:
    Date that indicates when the shipment of goods takes place.
    Example:
    Our company sells fruit.
    1.) We receive an order & take an apple out of our warehouse to ship to our customer. This date is the  u2018Document Dateu2019.
    2.) Our customer receives the apple & now accepts liability for the payment. This is the u2018Posting Dateu2019.
    3.) We send the customer an invoice where we specify the date when payment for the apple is expected. This is the u2018Due Dateu2019.
    I would recommend you speak with the partner, all this info is freely available to all partners.
    All the best,
    kerstin

  • Recuring posting problem with dates

    Dear experts
    I would like to ask you how to deal with strange problem within recuring posting document
    For recusring document I have set up for Run date 15, but when document was posted due to date was 5th not 15th. 5th is the same as posting date.
    can you tell me what can causing this?
    thanks a lot
    KR
    Peter

    Hi,
    The question is a bit unclear whether the recurring posting was created on 5th or 15th or you want that the date of the recurring posting could be changed.
    You can refer to Note No. : 1114120 and check whether this is what you are looking for.
    Kind Regards,
    Jitin
    SAP Business One Forum Team

  • In F-51 transaction was not posted,& due date field for advance payment VEN

    1.  In F-51 transaction was not posted. 
    In the above T-code I want to tranfer Invoice amount (RE) to special GL debit retention money payable the following error was throwing,
    Balancing Field "Profit Center" in the line item 001 not filled.
    2. For advance payments for vendors due date field is not appearing in document entry screen.  How   can I see due date field in document entry screen.
      In OB41 I changed the field status for posting key 29 in payment transations I made due date field required, but it is not appearing due date field in document entry screen, while posting transaction.
    Please advise on this.
    Regards

    Hi thru f-51 u cannot post the transaction here u can enter first line item and select process open item and post it and the base line date is already entered in invoice document based on that one the advance amount is adjusted u con't enter that base line date at the time of advance payment and also the payment terms are maintained in vendor master based on that on also due date is calculated i hope it will be helpful.

  • Due date field in F-48

    HI
    I need to get the due date field to appear on both the debit as well as credit sides of a posting in F-48 vendor down payment.
    Right now for example if i do the following transaction:
    Credit bank account    Rs 10,000     Due date:01/01/2009
    Debit  Vendor account Rs 10,000     Due date: no field seen
    I tried making the field required in field status for posting key 29 but it did not cause the field to appear in debit side.
    Could anyone advise me on how to cause this field to appear in the second line item?
    thanks
    Roshan

    Hi
    The field is not appearing on the vendor side. It is marked as optional by default in both 026 as well as 067 in our settings. but still only appears for the bank side.
    I should clarify that what i am looking for is to have the due date field appear on both the debit as well as the credit side of the transaction,
    In other words the user should have to enter it when he fills out initial screen of F-48 and then again enter it in the 2nd line item screen.

  • Billing report with due date field

    Dear Friends,
    Can you please tell the logic of Billing report with due date field.
    Input.  billing document no, date range, sales organisation
    Output : billing document no, sales organisation, Amount. Due date.
    If any clarification required, Please let me know.
    Thanks in advance
    Ranjan

    Is it VF05 is suffiant for your purpose?
    use further selection criteria tab.
    Amit.

  • Payment terms and Due date field gets emptied after residual clearing

    Hi
    There is advance of Rs.50000 in Vendor ledger and Invoice of Rs.200000 (with payment term - G019)
    I cleared these two line items (residual clearing). One new line item got created of Rs.150000. When i saw that line item, i saw that there payment term field and due date field got emptied. My requirement is that the original payment term entered in initial invoice document (of Rs.200000) should automatically get populated in new line item of Rs.150000.
    How to fulfill this requirement?

    Thanks for the prompt reply.
    I wanted to ask one more thing. Same way when i do partial clearing (not residual), is it possible to populate the invoice's due date in advance line item. One link is that my invoice reference gets populated advance line item. So i want due date (not payment term) also to get populated in advance line item.
    Please help.
    Edited by: Deepak Agrawal on Jul 29, 2011 11:43 AM

  • Making Posting date field Mandatory in DP91 screen

    Hi All,
    Is it possible to make the posting date field mandatory in the DP91 screen.
    Currently if the posting date is not specified, system will always consider the current date as posting date and picks the appropriate actual line items.  
    Is its possible to make the posting date field Mandatory through standard way or if not through exit.Pl suggest
    Regards
    SB

    Hi All,
    By Mistake I have typed wrongly.The requirement is
    In DP91 screen the current date is populated in posting date to field by default. But the user want it should be empty and they will key in the date.The reason behind is if they will always raise the Billing request for the previous month and by mistake if they executed DP91 for current date it will be an issue.
    Regards
    sb

  • Due date field.

    hi gurus!
    i want to knw due date field for invoice.
    regards,
    Rahul

    may be it may help u
    bsik-zfbdt, " Base Line Date
    bsik-zbd1t, " Due date1
    bsik-zbd2t, " Due Date2
    bsik-zbd3t,

  • Query not returning rows in 'result' tab due to invalid date field (bug?)

    It seems that in the results display, if there is a date field with out of bounds data then the query is stopped and only the results up to that record are displayed. When running the same query as a script, all of records are returned. The offending date in the table was '-10100-00-00 0-1:0-1:0-1.0'. Don't ask how it got there... I really have no idea.
    Has anyone else noticed this? Could it relate to the NLS format? Would it be possible to just display this value as null in the 'results' tab instead? Or wrap any invalid data as such and return nothing in the field but still show the record?

    Hello,
    It seems that you had resolved the issue which caused by premission.
    You can post the solution in a new reply and mark it as answer.
    Regards,
    Fanny Liu
    If you have any feedback on our support, please click here. 
    Fanny Liu
    TechNet Community Support

  • GRN Document Date / Posting Date Field Mandatory or Freeze

    Dear All,
    We have four Company Codes with single Chart of Accounts. we required to make GRN Document Date / Posting Date Field Mandatory or freeze on current date for only one Company Code. Can it be possible through Standard Configuration?
    Regards,
    Majid Khan

    what exactly we say Document Date & Posting Date
    Just type in google difference between document date and posting date  and execute.  You will find lot of threads discussed on this topic.  Please dont post any query without searching the forum or google.
    G. Lakshmipathi

  • Need to Programmatically Set IRR Filter on Date Field Due to APEX 4.1 Bug

    There may be another work around but, here is the problem that we are encountering...
    We have a huge table that is partitioned on a DATE field and an IRR that reports on this table. By default, we want to show the most recent 3 days of data. There is a built-in filter for "is in the last 3 Days." Sounds Great! Unfortunately APEX generates the code using TIMESTAMP rather than DATE functions. As a result of this, the query does not perform partition pruning and, as a consequence, it is doing a full table scan which takes forever. Note the use of the "LOCALTIMESTAMP" function in the query that is generated by APEX for this filter:
    SELECT   "BUSINESS_DATE",
             COUNT ( * ) OVER () AS apxws_row_cnt
      FROM   (SELECT   *
                FROM   (SELECT   *
                          FROM   position_delta_his p) r
               WHERE   ("BUSINESS_DATE" BETWEEN *LOCALTIMESTAMP*
                                                - NUMTOYMINTERVAL (:APXWS_EXPR_1,
                                                                   'year')
                                            AND  *LOCALTIMESTAMP*)) r
    WHERE   ROWNUM <= TO_NUMBER (:APXWS_MAX_ROW_CNT)If, instead, APEX used the SYSDATE function, as the underlying column is a DATE, this returns instantly, after partition pruning.
    SELECT   "BUSINESS_DATE",
             COUNT ( * ) OVER () AS apxws_row_cnt
      FROM   (SELECT   *
                FROM   (SELECT   *
                          FROM   position_delta_his p) r
               WHERE   ("BUSINESS_DATE" BETWEEN *SYSDATE*
                                                - NUMTOYMINTERVAL (:APXWS_EXPR_1,
                                                                   'year')
                                            AND  *SYSDATE*)) r
    WHERE   ROWNUM <= TO_NUMBER (:APXWS_MAX_ROW_CNT)
    The bug is that APEX should base the underlying function on the data type of the filtered column.
    As a work around, if we create a filter where BUSINESS_DATE >= '4/13/2012' (three business days ago), again, this returns instantaneously. The issue is that we can only set this filter by using the APEX GUI. We need to be able to:
    1. Determine the date for 3 business days ago
    2. Set this as the default filter.
    I tried creating a BEFORE HEADER PL/SQL page process but, it does not appear to be having any effect. Here is that code:
    DECLARE
        ldt_Filter DATE;
        CURSOR lcsr_GetMaxBusinessDate IS
            SELECT Max(BUSINESS_DATE)
            FROM POSITION_DELTA_HIS;
        DAYS_AGO CONSTANT NUMBER := 3;       
    BEGIN
        APEX_UTIL.IR_CLEAR( :APP_PAGE_ID );
        OPEN lcsr_GetMaxBusinessDate;
        FETCH lcsr_GetMaxBusinessDate INTO ldt_Filter;
        CLOSE lcsr_GetMaxBusinessDate;
        ldt_Filter := ( Trunc( ldt_Filter ) - 3 );
        APEX_UTIL.IR_FILTER( p_page_id       => :APP_PAGE_ID,
                             p_report_column => 'BUSINESS_DATE',
                             p_operator_abbr =>'GTE',
                             p_filter_value  => TO_CHAR( ldt_Filter, 'YYYYMMDDHH24MISS' ) );
    END;Can anyone tell me:
    1. How to set this filter programmatically (also needs to be displayed on the page so the user can see the current filter...as if it were created via the GUI) ***OR***
    2. Some other work around for this issue..
    Thanks,
    -Joe

    Actually, now that I look further, I don't think it is going to work to simply set the filter programmatically. The end user can still click the column heading where they are only given the choice of the LOCALTIMESTAMP based filters. If they pick one, the page is going to be out to lunch for them.
    We really need some other fix. We really need a way to actually address the underlying issue.
    -Joe

  • IDoc posted in R/3 but data for Date field has not generated.

    Hi Experts
    This is JDBC to IDoc scenarion.
    Source: MS SQL Server
    Date Data Type: smalldatetime
    Date field Format: yyyy-MM-dd hh:mm:ss --> example: 2009-11-13 00:00:00
    XI Mapping: Source Date --> Transformation --> Target Date
    Transformation: yyyy-MM-dd hh:mm:ss to yyyyMMdd
    Target: R/3 System
    Date Data Type:  ERDAT from VBAK table - Date on Which Record Was Created
    Date field Format: Date field (YYYYMMDD) stored as char(8)
    Check points:
    1. Mapping is working fine in XI and transformation is done with the test data: 2009-11-13 00:00:00  --> to ---> 20091113
    2. In SXMB_MONI the data is processed from the source and the IDoc XML data is generated. In the IDoc XML data the date field is containing the value <DATE>20091113</DATE>
    3. But when I tried to open the IDoc(SE05) in R/3 the date field is empty and no data is generated.
    Request you to let me know why the error is happening.
    Regards
    Ram

    Hi Ram,
    First try to test the same IDOC generated in ECC Box by populating date field value using WE19 and test .
    Or
    Instead of passing date value from SQL Server, Just give a try with  Current Date function in Mapping and test in ECC system.
    then we can think on further analysis.
    Regards,
    Vijay

Maybe you are looking for