F-28 Incoming payment - Field VALUT

Hello,
I'd like to understand if the field VALUT in transaction F-28 has to be alwayes populated and which are the difference in the document generated if I populate this field or not.
Thanks a lot
Cheers,
Emanuela

This field will be mandatory/optional based on the bank GL account field status group.
Value date is the actual date when the amount realized in the bank account, and this field is mandatory for bank and bank sub accounts.
It may be differ from posting/document date.
Rgds
Murali. N

Similar Messages

  • Incoming Payments Repeatitive Area Printing

    Hi All
    I need to know how to print in the repeatitive area in incoming payments.....
    I need to print paid invoices and the customer name in the report.
    Please help.....

    Bongani,
    The Customer Name appears on the top and can also be added anywhere else in the report. 
    Add a database field:
    Table: Incoming Payment:
    Field: Customer Name
    The list of invoices cannot be added to the repetitive area.   The system template prints the list of invoice in the End of Report section using System Variable 130 (In the 2005A Receipt template this field is FIELD_340)
    Suda

  • Dimension 1 Cost centre field is not able to edit in Incoming payment for Down payment Request

    Hi Exports,
    I am facing an issue on selecting Cost centres in Incoming payment screen.
    Issue: While I am booking the payment entry for Down payment request, I am not able to select first Dimension cost centre in Incoming payment rows for down payment request document, the Second dimension is able to select and update. the field is in non-editable mode (only on specific document row)
    Setup:
    1. Two Dimension are enabled
    2. In Separate Columns - Both Cost Centres are in separate column
    The above issue is only for Down payment request, for other documents (Invoice) I am able to select and update cost centre
    Please find below snap shot for reference
    Kindly check and let me know the solution
    Regards,
    Kiran

    Hi Gordon,
    Thanks for your reply.
    Yes agree, The Down Payment request is not a financial document but the Cost centres are able to select in Down payment request rows, no issue at all in this case.
    In Incoming payment screen it is necessary to select Cost centres because it has financial implication using down payment request with related to currency difference or Bank charges (both are Expense accounts) and DR assignment is mandatory in this case.
    And you have to notice one thing in above issue, I am able to select second dimension cost centre and it is allowing to edit and update the cost centre on respective row. Only issue is specific cell (dimension 1 cost centre) is not able to edit.
    Even I am not able to process payment entry without selection of Cost Centre on first dimension, the system is blocking and displaying the error message "DR Assignment is mandatory on Dimension 1 for specific account"
    Looks like bug, please clarify
    SBO version: 9.0 PL 11
    Regards,
    Kiran

  • Location field in Incoming Payment

    Hi All,
    My client requirement is that they want to have Location in the Incoming payment window but in that its not possible to get that. I can map that through UDF but this does not solve my problem as through UDF i can give it for storing the information as far as reporting i concerned i cant get it. So please help me out. Thanks is advance.
    With best regards,
    Murtuza Ahmed.

    Hi
    Can you please explain what does location field mean and where it is defined . Location is usually used in Item master data as UDF to work as a bin location .I don't think so your client want to see where item is located in incoming payment.
    If you can define Location,probably can help to find your solution .
    Thank you
    Bishal

  • Incoming Payment Check No. field not editable directly

    SBO 2007A, PL 42
    Banking >> Incoming Payments >> Payment Means
    When I am entering an incoming check from a customer, on the Payment Means window, I can't click in the Check No. field and enter data, but if I tab over it to it from the amount field, I can.
    Is this by design or a bug? What's the point of it?

    Hi Cindy
    It works fine on mine .Is that you are having problem when you enter incoming payment at first time or when you are trying to edit .
    It is working fine on mine .I can put check number .
    What patch level you are in ? which SBO version
    Thank you
    Bishal

  • XLR - Incoming Payment - Open Balance field not found

    I'm trying to build an aged debtors report in XLR and the last piece I need is the Open Balance (ORCT.OpneBal) on an Incoming Payment that was made on account. I've not been able to find this field in XLR. Does anyone know if its available from inside XLR, and if so, what its called?
    Thanks
    Edu

    There is no Open balance available in XLR.  To get aged debtors report, you can use invoice and credit note field.  Payment is only part of formula.  I don't think it holds enough information to create this kind of report.
    Thanks,
    Gordon

  • Reference field in selection parameter in incoming payments.

    hi kings
    i want to add the tab for reference field in slection parameter in incoming payment after open items selection.
    Present selection prameters are document no, business are, due days, document date,INR gross amount, cash discount,cash. So i want to add one more parameter for reference doc number .
    How can i add this field to existing fields. How can edit the layout.
    thanks
    ram

    Hi saravan
    did u mean by Accounting opitions button. This field is only there in three right side of the screen.
    I am using 5.0 version it includes the tabs are Overview button,distribute  diff.,charge of diff., Editing opitions,Cash discount due,create distribute case.
    But configuration was not there in F-28.
    plse let me the process and there is why to resolve the problem through the editing opitions.
    regards
    ram

  • How to add incoming payment lock field (EZASP or INC_PAY_LOCK) in CA of MDT

    I want to add the field of incoming payment lock  in the master data template contract_account.
    i tried the following configuration(Tcode =EPDTYPE)
    Type Name       EZASP_OLD_KK
    Table Name      FKKVKP1
    Field Name      EZASP
    Counter         888
    Table Name      FKKVKP
    Field Name      EZASP
    and another option configuration:
    Type Name       EZASP_OLD_KK
    Table Name      FKKVKP1
    Field Name      EZASP
    Counter         888
    Table Name      DFKKLOCKS
    Field Name      LOCKR
    but nothing is right( can not save to database)
    please any experts can explain it?

    session #1 doing
    MMR_XWALK
    SET
    PAY_ADJUSTMENT_END_DT = :PAY_ADJUSTMENT_END_DT,
    UPDATOR_ID = :UPDATOR_ID,
    UPDATE_DT = SYSDATE,
    PAYMENT_PERIOD_DT=TO_NUMBER(200502)
    WHERE
    HIC_NUM= :HIC_NUM AND
    SEQUENCE_NUM = :SEQUENCE_NUM AND
    PAY_ADJUSTMENT_START_DT= :PAY_ADJUSTMENT_START_DT_XWALK AND
    ACTIVE_IND = 'A'session #2
    UPDATE
    FDS.CMS_MMR_XWALK
    SET
    PAY_ADJUSTMENT_END_DT = TO_DATE( :PAY_ADJUSTMENT_END_DT,'YYYY-MM-DD'),
    UPDATOR_ID = :UPDATOR_ID,
    UPDATE_DT = SYSDATE,
    PAYMENT_PERIOD_DT=TO_NUMBER(200503)
    WHERE
    HIC_NUM= :HIC_NUM AND
    SEQUENCE_NUM = :SEQUENCE_NUM AND
    PAY_ADJUSTMENT_START_DT=TO_DATE( :PAY_ADJUSTMENT_START_DT_XWALK,'YYYY-MM-DD') AND
    ACTIVE_IND = 'A'Slightly different UPDATE statements means 2 different procedures hitting same table
    Notice different PAYMENT_PERIOD_DT between sessions
    Are any triggers involved?
    This is application problem; not Oracle problem

  • DueDate field in the Incoming payments

    I need know the Incoming payments paid with the respective duedates..
    for this, i use this SQL statement:
    SELECT
    T1.DocNum ,
    T2.Serial ,
    T1.CardCode ,
    T1.Cardname ,
    T6.GroupName,
    T4.SlpName ,
    T3.CityS ,
    T0.SumApplied,
    T1.DocDate ,
    FROM  [dbo].[RCT2] T0
    LEFT OUTER  JOIN [dbo].[ORCT]  T1  ON  T1.DocNum = T0.DocNum
    LEFT OUTER JOIN [dbo].[OINV] T2  ON  T2.DocEntry = T0.DocEntry
    LEFT OUTER JOIN  INV12 T3  ON T3.DocEntry=T2.DocEntry
    LEFT OUTER JOIN  OSLP T4 ON T4.SlpCode=T2.SlpCode
    LEFT OUTER JOIN  OCRD T5 ON T5.CardCode=T2.CardCode
    LEFT OUTER JOIN  OCRG T6 ON T6.GroupCode=T5.GroupCode
    WHERE T1.CardCode='[%0]'
    How can i add the duedate field from INV6 table, without duplicate records in this select?There is any other duedate field
    in another table that corresponds the INV6 table(duedate)?
    Thanks
    Edited by: Philip Eller on May 20, 2008 9:25 AM
    Edited by: Philip Eller on Jun 3, 2008 8:37 AM*
    Edited by: Philip Eller on Jun 17, 2008 9:30 AM**

    The value date in the INV6.. (AR Invoice>Accounting tab>Instalments)...
    The date of the expiration in the Invoice's DUE DATE. (DocDueDate) can be different of the date of Instalments.
    I can divide the total of the Invoice with different dates(DueDate).
    Each one generates a incomming payments
    I need a query that shows this field...
    basically...
    SELECT
    T1.DocNum ,
    T2.Serial ,
    T1.CardCod,
    T1.Cardname ,
    T0.SumApplied ,
    FROM  [dbo].[RCT2] T0
    LEFT OUTER  JOIN [dbo].[ORCT]  T1  ON  T1.DocNum = T0.DocNum
    LEFT OUTER JOIN [dbo].[OINV] T2  ON  T2.DocEntry = T0.DocEntry
    WHERE T1.CardCode='[%0]'
    and add the the DueDate (Instalments)

  • Which field, table for Document No in Incoming Payment

    Need to retrieve all posted Incoming payments with matched Invoice Number, Credit Memo Number (checks, cash, credit card or wire transfer payment means).  I will use this result to compare the Invoice /CM to pay com.
    Can someone provide the query?  Thanks.

    Try this one:
    SELECT T1.CardCode Customer, T1.CardName 'Customer Name', Case T0.InvType WHEN '13' THEN 'INVOICE' WHEN '14' THEN 'CR Memo' END AS 'TYPE', T0.DocEntry AS 'Invoice/CR#', T1.DocCurr AS 'BY',Case WHEN T1.DocCurr = '$' THEN T0.SumApplied ELSE T0.AppliedFC END AS 'Paid Amount', CASE WHEN T1.CashSum > 0 THEN 'Cash' WHEN T1.CreditSum > 0 THEN 'CC' WHEN T1.TrsfrSum > 0 THEN 'WIRE' ELSE 'Check' END AS 'Method', T1.DocNum AS 'RC#', T1.DocDate AS 'Posted' 
    FROM dbo.ORCT T1   INNER JOIN dbo.RCT2 T0 ON T1.DocNum = T0.DocNum  WHERE Month(T1.DocDate) = Month(GetDate()) AND Year(T1.DocDate) = Year(GetDate()) AND T1.JrnlMemo != 'Cancelled' AND T1.NoDocSumSy > 0.02
    Thanks,
    Gordon

  • Incoming Payment Clearing F-28: Cash Dicount Field to be inactive

    Hi Experts,
    Can anyone share on how can we make Cash Dicount Fiedd to inactive automatically in F-28 (Incoming Payment) when the payment is made after due date.
    Appreciate your responde on this regard.
    Regards,
    Ravi

    Hi Saulo,
    Thanks for ur reply.
    I had alreay done the config in OBXL and OBBE. Only thing I wanted to know is while posting Incoming Payment by F-28, how to use this reason code.
    Ur reply was a gr8 help for me.
    Regards,
    Pradnya

  • BAPI on Post Incoming Payment (F-28) Enquiry

    Hi all,
    I try to look for BAPI on F-28 and I had search for many info. However, I found that 1 thread saying that we can have 'BAPI_ACC_GL_POSTING_POST' to do.
    Refer to this site:
    bapi is used to 'post incoming payments (t-code F-28)'
    However, I found that the BAPI is used for transaction FB50. Generally, I use the F-28 to post incoming payment for AR. So I am not so sure that the BAPI can work.
    Besides that, I found another thread claim that no BAPI for the F-28. Refer to this site:
    https://www.sdn.sap.com/irj/sdn/profile?userid=677412
    As my research, I cant find the appropriate BAPI. Please give me some idea on how the BAPI work, and any correct BAPI can be used? Frankly, I a bit confused now.
    Thanks and regards.
    Cheers,
    Isaac

    Kindly go through this. I thjink it will clear you.
    Pattern in which function modules are called
    The function module fi_document_process is called 4 times and finally document_post is called once which updates the tables.
    Step 1. Call FI_DOCUMENT_PROCESS
    Import Parameters
    I_GJAHR     LIKE     TRWCA- YEAR
    I_PROCESS     LIKE     TRWPR-PROCESS
    I_EVENT     LIKE     TRWPR-EVENT
    Tables
    T_BKPF          LIKE     BKPF
    T_BSEG          LIKE     BSEG
    T_BSEGZ     LIKE     BSEGZ
    T_ACCIT_EXT     LIKE     ACCIT_EXTENSION   
    Values to populate import parameters
          i_gjahr                 = '2007'     “Fiscal year from the screen
          i_process              = 'BELEG'    “Constant, can be hard coded
          i_event                  = 'CRBSEGZ'   “Constant, can be hard coded
                  xbkpf-bukrs '1000'.            “ Company code from the screen
                  xbkpf-belnr '$1'.              “ constant , can be hard coded
                  xbkpf-gjahr '2007'.             “ Fiscal Year , from the screen
                  xbkpf-blart 'DZ'.              “ Can be obtained from the invoice document
                  xbkpf-bldat '20070116'.      “ Document Date, from the screen
                  xbkpf-budat ’20070118'.      “ Posting Date , from the screen
                  xbkpf-monat '01'.                  “ constant , can be hard coded
                  xbkpf-wwert '20070118'.       “ posting Date
                  xbkpf-usnam 'SAPUSER'.       “ user name
                  xbkpf-tcode 'FBZ1'.               “ Constant, can be hard coded
                  xbkpf-waers 'EUR'.                 “ currency, from the screen
                  xbkpf-glvor 'RFBU'.                “ constant can be hard coded
                  xbkpf-awtyp 'BKPF'.                “ constant, can be hard coded
                  xbkpf-fikrs ’1000'.              “ customer account number, from the screen
                  xbkpf-hwaer 'EUR'.              “ Currency, from the screen
                  xbkpf-awsys 'ECCCLNT800'.    „can be hard coded
    xbseg Record 1
          xbseg-bukrs  '1000'.           “ Company code from the screen
          xbseg-belnr  '$1'  .           “ constant , can be hard coded
          xbseg-gjahr  '2007'.            „ Fiscal Year, from the screen
          xbseg-buzei  ’001'.             “ constant , can be hard coded
          xbseg-bschl  '40'.          “ constant , can be hard coded
          xbseg-koart  'S'.          “ constant , can be hard coded
          xbseg-shkzg  'S'  .           “ constant , can be hard coded
          xbseg-dmbtr  '10'.           „ Amount, from the screen
          xbseg-wrbtr  '10'.           „ Amount, from the screen
          xbseg-pswbt  ’10'.           „ Amount, from the screen
          xbseg-pswsl  'EUR'.           „ Currency, from the screen
          xbseg-valut  ’20070118'.        “ Posting date, from the screen
          xbseg-altkt  '0000110100'.
          xbseg-vorgn  'RFBU'.      “ constant , can be hard coded
          xbseg-fdlev  'B9'.           “ constant , can be hard coded
          xbseg-fdwbt  '10'.            „ Amount, from the screen
          xbseg-fdtag  '20070118'.        “ Posting date, from the screen
          xbseg-kokrs  ’1000'.             “ Customer account
          xbseg-xkres  'X'.           “ constant , can be hard coded
          xbseg-xopvw  'X'.            “ constant , can be hard coded
          xbseg-hkont  '0000110009'. “ Bank Account number
          xbseg-xbilk  'X'.           “ constant , can be hard coded
          xbseg-fipos  '9620'.            “ constant , can be hard coded
          xbseg-lokkt  '0000110009'.  “ Bank Account number
    xbseg Record 2.
            bseg-bukrs '1000'.      “ Company code from the screen
          bseg-belnr. '$1'      “ constant , can be hard coded
          bseg-gjahr. '2007'     “ Fiscal year from the screen
          bseg-augbl. '*'     “ constant , can be hard coded
          bseg-buzei'002'.      “ constant , can be hard coded
          bseg-bschl. '15'     “ constant , can be hard coded
          bseg-koart. 'D'     “ constant , can be hard coded
          bseg-shkzg. 'H'     “ constant , can be hard coded
          bseg-dmbtr. '10'      “Amount, from the screen
          bseg-wrbtr. '10'     “Amount, from the screen
          bseg-pswbt. '10'     “Amount, from the screen
          bseg-pswsl. 'EUR'     “ currency, from the screen
          bseg-altkt. '0000120100'
          bseg-vorgn. 'RFBU'     “ constant , can be hard coded
          bseg-kokrs. '1000'      “ Customer account number
          bseg-xkres. 'X'     “ constant , can be hard coded
          bseg-xopvw. 'X'     “ constant , can be hard coded
          bseg-hkont. '0000140000'
          bseg-xbilk. 'X'     “ constant , can be hard coded
          bseg-fipos. '9620'     “ constant , can be hard coded
          bseg-lokkt. '0000140000'
          bseg-nebtr. '10'      “ Amount, from the screen
          bseg-xauto. 'X'     “ constant , can be hard coded
          bseg-xzahl. 'X'     “ constant , can be hard coded
          bseg-saknr. '0000140000'
          bseg-zfbdt. '20070116'” Invoice document date
          bseg-hwmet. 'A'     “ constant , can be hard coded
          bseg-kkber. '1000'     “ Customer account number
          bseg-agzei. '1'     “ constant , can be hard coded
    Step 2. Call FI_DOCUMENT_PROCESS
    Import Parameters
    I_GJAHR     LIKE     TRWCA- YEAR
    I_PROCESS     LIKE     TRWPR-PROCESS
    I_EVENT     LIKE     TRWPR-EVENT
    Tables
    T_BKPF          LIKE     BKPF
    T_BSEG          LIKE     BSEG
    T_BSEGZ     LIKE     BSEGZ
    T_AUSZ3     LIKE     AUSZ_CLR
    T_AUSZ4     LIKE     AUSZ_CLR_ASGMT
    T_ACCIT_EXT     LIKE     ACCIT_EXTENSION   
    Values to  populate import parameters
          i_gjahr                 = '2007'     “Fiscal year from the screen
          i_process              = 'BELEG'    “Constant, can be hard coded
          i_event                  = 'CLOSE'   “Constant, can be hard coded
    Table xausz3.
              ausz3-agzei. '1'       “Constant, can be hard coded
           ausz3-waers. 'EUR'     „ Currency from the screen
           ausz3-bukrs. '1000'     „ Company Code
           ausz3-belnr. '1800000076' „ Document number from the screen
           ausz3-gjahr. '2007'        „ Fiscal Year
           ausz3-buzei. '001'          
           ausz3-shkzg. 'S'          “Constant, can be hard coded
           ausz3-dmbtr. '10'         “ Amount, from the screen
           ausz3-wrbtr. '10'          “ Amount, from the screen
           ausz3-koart. 'D'             “Constant, can be hard coded
    Step 3. Call FI_DOCUMENT_PROCESS
    Import Parameters
    I_GJAHR     LIKE     TRWCA- YEAR
    I_PROCESS     LIKE     TRWPR-PROCESS
    I_EVENT     LIKE     TRWPR-EVENT
    Tables
    T_BKPF          LIKE     BKPF
    T_BSEG          LIKE     BSEG
    T_BSEGZ     LIKE     BSEGZ
    T_AUSZ3     LIKE     AUSZ_CLR
    T_AUSZ4     LIKE     AUSZ_CLR_ASGMT
    T_ACCIT_EXT     LIKE     ACCIT_EXTENSION   
    Values to populate import parameters
          i_gjahr                 = '2007'          “Fiscal year from the screen
          i_process              = 'BELEG'         “Constant, can be hard coded
          i_event                  = 'PROJECT'        “Constant, can be hard coded
       I_AUGLV           = 'EINGZAHL' “Constant, can be hard coded
    Step 4. Call POST_DOCUMENT
    Import Parameters
    I_BKDF     LIKE     BKDF
    I_UF05A     LIKE     UF05A
    I_GENER     LIKE     T020-GENER
    I_AUGLV     LIKE     T041A-AUGLV
    Tables
    T_AUSZ1     LIKE     AUSZ1
    T_AUSZ2     LIKE     AUSZ2
    T_AUSZ3     LIKE     AUSZ_CLR
    T_AUSZ4     LIKE     AUSZ_CLR_ASGMT
    T_BKP1          LIKE     BKP1
    T_BKPF          LIKE     BKPF
    T_BSEC          LIKE     BSEC
    T_BSED          LIKE     BSED
    T_BSEG          LIKE     BSEG
    T_BSET          LIKE     BSET
    T_BSEU          LIKE     BSEU
    Values to populate import parameters
    Table xausz1
        xausz1-belnr. '1800000076'    „ Document number from the screen
        xausz1-bukrs. '1000'            „ Company code from the screen
        xausz1-gjahr. '2007'            „ Fiscal year from the screen     
        xausz1-buzei. '001'            “ Constant , can be hard coded
    Table xausz2
            ausz2-bukrs. '1000'            „ Company code from the screen
            ausz2-aktio. 'A'               “ Constant , can be hard coded
            ausz2-augbl. '1400000054'     „ Posted document number..from the function NUMBER_GET_NEXT(Dynamically generated unique number)
            ausz2-augdt. '20070118'          „ Posting Date from the screen
            ausz2-auggj. '2007'          „ Fiscal Year from the screen
    Table xbkpf
    First record of the internal table zbkpf has to be modified with the dynamically generated document number.
    Xbkpf-belnr.  ‘1400000054’
    Table xbkp1
    xbkp1-currj     '2007'   “ Fiscal year, from the screen
    Table xbseg
    Following fields in the table xbseg has to be modified before passing to this function module.
    Record 1
       TO wa_bseg1-belnr. '1400000054' “ Dynamically generated number
       TO wa_bseg1-zuonr. '20070116'   “ Document Date from the screen
    Record 2
       bseg1-belnr. '1400000054' „ Dynamically generated number
       bseg1-augdt. '20070118'   „ Posting date from the screen
       bseg1-augcp. '20070118'   „ Posting date from the screen
       bseg1-augbl. '1400000054'  „ Dynamically generated number
    bseg1-zuonr. '14000000542007' „ Concatenating dynamically generated number                                   and fiscal year
       bseg1-kunnr. '1000'        “ Customer number from the screen
    Table Xbseu
    Record 1
    bseu-waers     'EUR'     “ Currency from the screen
    Record 2
    bseu-waers.      'EUR'           “ Currency from the screen
    bseu-xzver.       'X'            “ Constant Hard coded
    Step 5. Call FI_DOCUMENT_PROCESS
    Import parameters
    I_GJAHR     LIKE     TRWCA-TOYEAR
    I_PROCESS     LIKE     TRWPR-PROCESS
    I_EVENT     LIKE     TRWPR-EVENT
    I_AWTYP     LIKE     ACCHD-AWTYP
    I_AWREF     LIKE     ACCHD-AWREF
    I_AWORG     LIKE     ACCHD-AWORG
    I_AWSYS     LIKE     ACCHD-AWSYS
    Tables
    T_BKPF     LIKE     BKPF
    Values to populate import parameters
      i_gjahr           = '2007'     “ Fiscal Year from the screen
      i_process         = 'BELEG'     “ Constant      
      i_event           = 'POST'     “ Constant
      i_awtyp           = 'BKPF'     “ Constant
      i_awref           = '1400000054'”Dynamically generated posting doc number
      i_aworg           = '10002007'     “ Concatenate comp code and Fiscal Year
      i_awsys           = 'ECCCLNT800'” Constant.

  • Incoming payment by F-28: Reason code error while posting

    Hello everyone,
    I want to post Incoing Payment using F-28 net of TDS. I want the separate GL account to be picked up automatically for the difference when I enter the Reason Code 003.
    I did the following customization for the same.
    1. Financial Accounting> Accounts Receivable and Accounts Payable> Business Transactions>Incoimng Payments> Incoming Payments Global Settings>Overpayment/Underpayment> Define Reason Codes:- Here I selected the Indicator 'C' for reason code 003 which is for "Indicator: Charge off difference via separate account". The reason code 003 is for TDS Netted
    2. Below the Define Reason Code node, I selected the node 'Define Accounts for Payment Differences' . Selected the key ' Rules' and selected the checkbox 'Reason Code'. Then clicked on 'Accounts' and enetered the desired GL account against the reason code '003'.
    After doing the above customization I posted the Incoming payment using T code F-28. I entered the difference in the field 'Difference Posting'. Then entered reason code '003' which is for 'TDS netted' in the field 'Reason Code'. Now, I am getting the follwoing error.
    Reason codes with automatic charge-off are not permitted here
    Message no. F5605
    Diagnosis
    The reason code entered is designed to ensure that the payment difference amount is posted to an account specially set up for this purpose.  Postings of this nature usually require additional specifications (e.g. tax code, business area). If the difference stems from a single open item, the necessary specifications can be taken from that item. In the case that led to this error message, however, the difference does not stem soley from one item, which means that this method cannot be used.
    System Response
    The reason code entered is not accepted.
    Procedure
    You can either select a different reason code, which would create a new open item for the customer or vendor OR write off the difference using the function Charge off diff.. This function either takes you into a pre-configured account assignment model or into the document overview. From here you can enter the required difference postings.
    How can I proceed ahead?
    Thanks and Regards,
    Pradnya

    Hi Saulo,
    Thanks for ur reply.
    I had alreay done the config in OBXL and OBBE. Only thing I wanted to know is while posting Incoming Payment by F-28, how to use this reason code.
    Ur reply was a gr8 help for me.
    Regards,
    Pradnya

  • Clearing issue Incoming payment due to Cash discount ( customers)

    Hello,
    During processing automatic incoming payments the system don't clear the customer open item in case the customer has taken a cash discount.
    The clearing should be done automatically in the posting area 2 but now the the user needs to do manual interventions in the FEBAN in order to clear the customer
    We checked the payment terms and verified the discount taken by the customer and they are ok
    After investigation we guess that the original SD invoice don't send the Discount amount and Discount base amount to FI, because  we saw that those fields are empty in the FI document (RV),
    Also in Billing the Cash discount base field in empty...
    When i tried to create a manual customer invoice those fields are well filled in and the system clears the customer open item perfectly !
    Any one an idea how to fix it ?

    Hello,
    Thanks for your feedback but the issue is not solved.
    Is there difference in clearing behaviour in case the open item posting is orginated from  a SD invoice ( Billing) because as stated before, when I make a FI sales invoice (FB60) the system perfectly accepts the cash discount and post and clears in postingarea 2
    Also when I consult the open item position (FBL5N) the cash discount amount field is empty which is not the case when I post an FB60 invoice
    Summarized
    We are usiing the automatic bank statement program ( FEBC), during posting the system post perfectly posting area 1 (FEBP) but fails the post postingarea 2 ( the system makes a payment advice) the message the system generates ' Difference to large for clearing F5263'
    Many thanks for help

  • Billing Doc. No in Incoming payment.

    Dear Gurus,
                 I made a sales document in SD module say "12345" and the billing doc. no as "123" for customer "xyz" for amount "1000".
    I receive payment via- T.code f-28 for this customer for exact amount. My query is when I check the ledger in FBL5N for this customer it is not showing billing doc. no"123" for the incoming payment (doc.type "ZP" ),however it is showing billing doc. for sd document . Kindly guide . Also is there any way to view customer ledger via billing document no. For ex. how much payment due?Please guide

    Payment document can be posted based on the accounting document.
    If you want you can maintain invoice number in reference field, also there is one option to make reference field mandatory.
    In OBA7 activate reference document number as mandatory for the document type DZ. So, while doing the transaction in F-28, value should be mandatory to this field.
    If maintain invoice value in reference field, then you can do sorting and totaling based on the reference field in FBL5N.
    there are no standard reports to check the outstanding amount based on the invoice number.
    Rgds
    Murali. N

Maybe you are looking for