Lockbox Processing of Discounts

Hi All,
We have purchased a new business and their payments terms to not fit in with standard SAP (their discounts go six levels).  So, they use a speadsheet and handle it manually.  We want to be able to process this with our normal lockbox processing.  We would like to make the modification at the time discounts are determined.  I have not be able to find where this occurs in the lockbox process.  Any ideas?
Regards,
Greg

Hello-
Make sure the configuration the partially applied box is unchecked under Define Control Parameters. 
If so, does your client understand the definition of Residual versus Partially applied?
Partial Payment
Leaves original invoice intact (full amount)
Credits the Customer account for the payment amount
No items are cleared
Residual Payment
Clears the original invoice
Creates a new line item for the remaining amount
The new line item has a new document date and baseline date

Similar Messages

  • Modify Payment Terms for Lockbox Processing

    All,
    For our batch lockbox processing (RFEBLB00), I need change the payment terms information.  The percentage varies for up to 8 months. So, I need to alter the percentage discount and number of days. BTE 00001100 looks like a perfect fit, but it does not seem to be executed.  I have looked at OSS Note 494777 and the BAdI and SMOD don't seem to address this. Any ideas?
    Regards,
    Greg

    Hi,
    Payment terms is stored in customer master-> sales area data.
    u wud need to find an exit or modify std F4 to display data wrt order type..
    check with functional guy if it can be done thru config.
    Regards,
    Amit

  • Lockbox issue for discount amount and incorrect reference

    Hi All,
    While doing Lockbox processing through FLB2, for certain payment advices discount was not recorded and it was posted directly by the system in price difference(maintained in Reason Code). Also, system did not prompted an error message for the invoice paid with incorrect reference and not even processing to On Account.
    In total of discount amount and invoice amount paid with incorrect reference posted to GL Account maintained in one of the Reason codes automatically. 
    Where could be the error in configuration point of view to check, please advice with your expertise.
    Thanks,
    Likhit

    hi ,
    can you pl help me in sending the lockbox config and test file & testing process as my client needs lockbox set up?
    i would be thankful to you if could help me inthis regard.
    mail: [email protected]
    regds,
    raman

  • Need SAP not to clear off the payment in LockBox processing

    HI,
    In the case of the lockbox processing, we want that the system doews not clear off the invoice in case there is payment difference.
    We want to take dicision on those payments manually.
    Regards,
    MCA

    Hi,
    You need to define the tolerances in OBA3 and OBXL.
    Then the system will not clear off the invoices, instead it will post the ament on account, which you need to then post process.
    Regards,
    Gaurav

  • SAP Lockbox Processing (EDI 823) via FINSTA01 IDoc

    I am trying to implement lockbox processing in SAP using the FINSTA01 IDoc. I have not found any documentation regarding the data mapping. Does anybody have experience with this? If so, I could really use a sample data mapping document.
    Any help would be appreciated.

    Hi,
    Sorry,
    Three times the same URL  has copied,
    Click to the URL and check :
    http://help.sap.com/saphelp_erp2005/helpdata/en/57/f1fc3768b56d00e10000009b38f842/frameset.htm
    1) Importing Lockbox Data
    2) Postprocess Lockbox Data
    This might help you,
    http://ifr.sap.com/catalog/query.asp?namespace=urn:sap-com:ifr:FI:470&type=idoc&name=FINSTA01
    Regards
    Agasthuri Doss

  • LOCKBOX PROCESS 시 42440 RECEIPT HAS INVALID APPLICATIONS ERROR 가 발생했을 경우

    제품 : FIN_AR
    작성날짜 : 2005-10-24
    LOCKBOX PROCESS 시 42440 RECEIPT HAS INVALID APPLICATIONS ERROR 가 발생했을 경우
    ========================================================================
    PURPOSE
    Lockbox process 시 42440 Error 에 대처한다.
    Problem Description
    LockBox Interface table 에 데이타를 load 후 lockbox process 실행 시 report output 에 error: 42440 Receipt has invalid applications error 가 발생 한것을 발견하였다.
    Workaround
    Maintenance Transmission Screen 을 Open하여 해당 lockbox process 를 조회 하고 Application Button을 눌러 Invoice Filed 를 Clear 한 후 다시 해당 Process 를 수행한다.
    Solution Description
    아래 내용을 참조 하여 patch를 apply 한다.
    11.0 arlval.lpc 110.12 or higher
    11.5 arlval.lpc 115.7 or higher
    11.0 1999278 patchset 11.0.AR.I
    11i 1999278 patchset 11i.AR.H
    2004333 Standalone
    문제의 원인은 lockbox validation program 수행 시 error 가 발생하였는데 그 error 의 원인 데이타를 고치고 다시 lockbox validation program 을 수행 하였을 경우 이전의 invoice 데이타를 clear 하지 않아 발생 하는 것으로 판단 된다.
    Reference Documents
    Note. 219854.1 - Oracle Receivables Lockbox Troubleshooting Guide

    Hi,
    Can youplease let me know what is the exact error message you are encountering. May be the output/log file message will throw some additional information on this. please paste this here.
    Thanks and Regards,
    Raj..

  • Lockbox processing - customer invoice

    Hi Gurus,
    i have a query on Lockbox processing of an invoice created using F-22 tcode.
    How will we tell the system that this particular invoice ( or say particular customer ) is going to pay this amount to a lockbox maintained in the system?
    I have maintained the configuration for Lockbox using tcodes OB10 ( define lockbox accounts for house banks ), OBAY( define control parameters ), OBAX( Define posting data) .
    i have a sample BAI2 file to be uploaded for the lockbox processing using tcode FLB2.
    regards,
    ficoguy.

    when you send the invoice to the customer, you have to inform your customer the lockbox to which he needs to send the payment.
    As you have already informed him lockbox details, along with his payment to the lockbox he will generally forward the invoice details and checks to the lockbox.
    in the lockbox file, you will see the bank details and invoice number.

  • Lockbox process- end user tasks

    Hi experts!
    Could please someone answer my following question
    once the whole lockbox configuration is done, what will be the tasks that need to be performed by the end user daily? ( after done with the cofniguration settings , and checking out with the bank about the timings they send the lokcbox file daily , we schedule in such a way that the lockbox program will run daily at some particular time, right? so once done with all these , what will be the end user need to do daily? what entries should he has to perform?and then does he has to perform the post processing e.t.c
    <b>so to cutshort my question - what tasks should an end user has to perform in the lockbox process once it goes live.</b>
    Points will be rewarded.
    Thanks

    Hi,
    After configured the lockbox in banking,
    The checks the bank sends to you are entered as credits by the bank, and the information entered is sent to the payee using File Transfer.
    Under certain circumstances, the bank transmits a data carrier to the payee several times a day; the carrier bears the important check information.
    From this data carrier, postings are then generated for accounts receivable and G/L accounting, User has to use Tcode: FLB2 - Importing the file, FLBP - To post and FLBP_Lockbox -- To reprocess.
    End user documentation needs to be prepared on these tcodes and process.
    **if useful assign the points.
    Regards,
    Prashanth

  • Error occurred in Lockbox Processing.....

    Hello All,
    While running Lockbox import program in Receivables: Interfaces > Lockbox Its ending with Error.
    I herewith submitting the Source file, Data File and Error Logout put file.
    Please look into error and guide me to clear this error.
    Source File:
    -- Type 2 - Lockbox Header
    INTO TABLE AR_PAYMENTS_INTERFACE
    WHEN RECORD_TYPE = '2'
    ( STATUS CONSTANT 'AR_PLB_NEW_RECORD'
    ,RECORD_TYPE POSITION(01:01) CHAR
    ,DESTINATION_ACCOUNT POSITION(02:11) CHAR
    ,ORIGINATION POSITION(12:21) CHAR
    ,LOCKBOX_NUMBER POSITION(22:27) CHAR
    -- Type 6 - Payment record
    INTO TABLE AR_PAYMENTS_INTERFACE
    WHEN RECORD_TYPE = '6'
    ( STATUS CONSTANT 'AR_PLB_NEW_RECORD'
    ,RECORD_TYPE POSITION(01:01) CHAR
    ,LOCKBOX_NUMBER POSITION(02:05) CHAR
    ,BATCH_NAME POSITION(06:08) CHAR
    ,ITEM_NUMBER POSITION(09:11) CHAR
    ,REMITTANCE_AMOUNT POSITION(12:21) DECIMAL external
    ,TRANSIT_ROUTING_NUMBER POSITION(22:30) CHAR
    ,ACCOUNT POSITION(31:44) CHAR
    ,CHECK_NUMBER POSITION(45:54) CHAR
    ,DEPOSIT_DATE POSITION(55:60) DATE 'YYMMDD' NULLIF DEPOSIT_DATE=BLANKS
    -- Type 4 - Overflow
    INTO TABLE AR_PAYMENTS_INTERFACE
    WHEN RECORD_TYPE = '4'
    ( STATUS CONSTANT 'AR_PLB_NEW_RECORD'
    ,RECORD_TYPE POSITION(01:01) CHAR
    ,LOCKBOX_NUMBER POSITION(02:05) CHAR
    ,BATCH_NAME POSITION(06:08) CHAR
    ,ITEM_NUMBER POSITION(09:11) CHAR
    ,OVERFLOW_SEQUENCE POSITION(12:14) CHAR
    ,OVERFLOW_INDICATOR POSITION(15:15) CHAR
    ,INVOICE1 POSITION(16:30) CHAR
    ,CUSTOMER_NUMBER POSITION(34:41) CHAR
    ,AMOUNT_APPLIED1 POSITION(42:51) DECIMAL external
    "DECODE(:AMOUNT_APPLIED1,0,NULL,:AMOUNT_APPLIED1)"
    Data File:
    2GOVT_MGBSS10123456789L820
    6LB01MGB0010001723187 L150 110401
    4LB01MGB100100109100701 00300001023134857
    4LB01MGB100100209100702 00300001023179809
    4LB01MGB100100309100703 00300001023179809
    4LB01MGB100100409100704 00300001023179809
    4LB01MGB100100509100705 00300001023149841
    4LB01MGB100100609100706 00300001023179809
    4LB01MGB100100709100707 00300001023179809
    4LB01MGB100100809100708 00300001023179809
    4LB01MGB100100909100801 00300001023179809
    4LB01MGB100101009100802 00300001023179809
    Log output:
    ARLPLB module: Process Lockboxes
    Current system time is 24-APR-2012 11:40:51
    Starting ARLPLB
    Input parameters:
    Y
    Test15
    Y
    /muthulb/mgbmuthu/LB.txt
    arplbox
    1000
    Y
    N
    2011/05/01 00:00:00
    A
    N
    Y
    N
    120
    L
    Argv value for ignore invalid: |
    Argv value for report format: |A|
    Argv value for complete batches only: |N|
    Argv value for alt name search: |N|
    Argv value for ussgl trx code: |
    Argv value for org id: |120|
    Ignore Invalid Txn Num: |
    Scoring model Id is NULL
    Lockbox id is NULL.
    Inserted ar_transmissions record
    Control file: /d10/appltop/apps/apps_st/appl/ar/12.0.0/bin/arplbox.ctl
    Bad file: /d10/appltop/inst/apps/SOLDEV_mgbr12/logs/appl/conc/log/b539553.bad
    Log file: /d10/appltop/inst/apps/SOLDEV_mgbr12/logs/appl/conc/log/l539553.log
    Discard file: /d10/appltop/inst/apps/SOLDEV_mgbr12/logs/appl/conc/log/d539553.dis
    Username:SQL*Loader-350: Syntax error at line 3.
    Illegal combination of non-alphanumeric characters
    ^
    SQL*Loader: Release 10.1.0.5.0 - Production on Tue Apr 24 11:40:51 2012
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    0
    AR-ARLPLB: fdpldr returned FALSE.
    AR-ARLPLB: Error in main.
    AR-ARLPLB: 0 ORA-01403: no data found
    Start of log messages from FND_FILE
    End of log messages from FND_FILE
    Executing request completion options...
    Finished executing request completion options.
    AR-ARLPLB: Error in main.
    Thanks and Regards,
    Muthu

    Hi;
    Please check below which could be helpful for your issue:
    AR-ARLPLB: 0 ORA-01403: no data foundTroubleshooting Known Issues In Lockbox [ID 1366298.1]
    Oracle Receivables Lockbox: Known Issues and Patches [ID 1358497.1]
    Receipts Workbench Error: Listing of ORA Errors [ID 1364345.1]
    Regard
    Helios

  • Special GL Items Clearing while Lockbox Processing

    Hi Friends,
    Is it possible that while lockbox payment is processed in SAP for customer it also takes into account the special GL items for that customer while clearing the open items.
    Example :
    Customer has two open items of 1000 each
    First Item is Standard/Normal Open Item
    Second Item is Special GL Transaction
    Now if the payment is received for the special GL Item, lockbox should be able to clear the same based on refernce.
    Thanks

    Hi Mohit,
    If you want to use any other value under Invoice number field as processing parameter, then you have to make sure that details are being maintained in lockbox file as well.
    For example, if you want to use 2 (Reference document number) and you believe that sales order no. is being maintained as Reference no. in SAP, then make sure that sales order no. is also coming in lockbox file, only then FLB2 will be successful. You can use standard lockbox user exit as well, if required.
    Regards,
    Gaurav

  • BAI2 Lockbox statement. for Discount component

    Hi,
    In BAI2 Lockbox ( I am new to this) I have no issue to get the amount matched to Customer Open Item.\
    How the discount amount for early payment by customer is repressented in BAI2 ? With minus sign or discount is represented by some code no ?
    Thanks,
    Chitra.

    Hi Orlando,
    what was your solution to this problem?  I'm also facing the same problem.
    Regards,
    Andrew

  • Lockbox  processing

    Hi,
    Bank has missed putting the check amount total in payment advice. Not sure how to process check.
    Can anyone help me
    thanks

    Hi Ravana,
    Please check this link and go to <b>Postprocess Lockbox Data</b> link.
    http://help.sap.com/saphelp_erp2005/helpdata/en/57/f1fc3768b56d00e10000009b38f842/frameset.htm
    Hope this will help.
    Regards,
    Ferry Lianto

  • Lockbox Process, Configuration, Lockbox File format

    Hi everybody,
    I need a help on lockbox documents. Pls send.
    Regards,
    JC

    hi
    Lockbox is a process provided by a bank where the customer remits his payment to a PO Box at your bank, the bank deposits the check in your account and enters the remittance data from the customer. Then the bank sends the data to you electronically for you to import and apply in SAP-AR.
    The structure that the bank uses is usually one of two formats. BAI will provide you the customer information and the check amount but no invoice remittance data. Usually cheaper and works well for a business where customers are paying only one invoice at a time.
    BAI-2 offers remittance data but the bank charges more for the service because they have to enter more info.
    Look at structures FLB** to see the transfer data. 
    When the bank sends the customer payment data you use Treasury function FLB2 to import and then process the payments. This process attempts to determine where to apply the payment and will post directly against an invoice, an account to a customer or if it can't even determine the customer it posts into a clearing account (configured) to be resolved.
    Purpose
    Lockbox is a service offered by American banks in which banks collect and process customer payments to reduce processing time. The system can handle both lockbox file formats offered by banks, namely, BAI and BAI2.
    Process Flow
    A company can create accounts called ‘lockbox’ accounts at its bank (or banks) that act as payment collection accounts for customer payments.  The company then informs their customers that all open item payments for their accounts must be submitted to one of the established bank lockbox accounts.  The bank collects these payments along with the customers’ remittance information that indicates what open items the customer payments intend to clear.  Data entry clerks at the bank manually enter the information into an electronic file for transmission to the company to which the lockbox account belongs. These files are typically transferred nightly to the various lockbox owners (companies).  The files adhere to one of two standard banking industry transmission formats (BAI and BAI2), both of which are supported in the system.
    BAI and BAI2 formats differ in their level of information detail.  BAI does not separate out the incoming check line items by invoice subtotal reference.  Conversely, BAI2 splits the check total into separate invoice references and associated payment amounts. As a result, your ‘hit rate’ percentage of payment-invoice matching from each transmission is likely to be higher when using BAI2 rather than BAI formats.
    for furthur notes
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/4e/888d24ccb811d3bffd0000e8a4a484/frameset.htm
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/57/f1fc3768b56d00e10000009b38f842/frameset.htm
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/7a/af0eba9ffa11d295d900a0c9426c73/frameset.htm
    http://help.sap.com/search/search_overview.jsp
    nagesh

  • Remove leading zeros for invoice lists to allow auto lockbox processing

    I have a change request for the following document at my job. but i am very new into it and do not know how to start and what to do exactly? can anyone please help me what to do in this matter.
    SAP auto posting process for lockbox checks was created to post cash with minimal manual intervention.
    Transaction FLB2 is used to import a lockbox file from Bank of America containing customer payment detail to auto match and clear invoices in the AR subledger. The auto post program tries to match an invoice number from the Reference field to the invoice # in the lockbox file which does not have any leading zeroes. In order to allow this match to happen a user exit was developed to remove any leading zeros from the Reference field in the invoices It works fine for regular invoices but not for the invoice lists u2013 invoice numbers in the 76xxxxxx range. The leading zeros are not removed there, so these invoices fall out of the auto posting process. It has been expressed that we need to improve our automated check posting hit rate for better efficiencies, and to do so we need to have these invoice list invoices fixed in the same way as the regular invoices are.
    please advise
    Vishal

    can anybody please answer it?

  • Lockbox processing : Partial payments

    Hi,
    We are using Lockbox with BAI2 file formats.
    Here we have made configurations for disabling partial payments.
    (uncheck the checkbox)
    But still, for some random cases, partial payments are happening.
    Is there any other settings that has to be done or any SAP NOTE
    to avoid this?
    Kindly pour in your valuable inputs.
    Thanks in advance.
    Regards
    Megha

    Hi Megha,
    You can restrict and implement your functionality by developing an User Exit. Ask Abaper to look into the standard program
    Thanks
    Rajanikanth

Maybe you are looking for