Lockbox - IDOC

Hello,
The question is related to lockbox processing using IDOC (as opposed to BAI). The issue I am having is with interpretation o the document number that comes from lockbox IDOC. Challenge is that most of the time we wouldn't have customer's bank information on the customer master (don't ask me why, it is what it is) so we're going to have to rely on the document search for the most part. Now, when the bank file has SAP document number as reference it all works fine, the problems start when I use a reference document number in the file - then the system is unable to find the invoice to clear. I know that there are user exits that would let one manipulate the processing logic, but even w/o using them there should be a way (I am guessing in IDOC structure itself) to make system look for different fields in the document while searching for open item. Any thoughts would be appreciated.
Thanks,
K.

Hi, thanks for response, but I am not sure I really follow the solution:
First of all, the segment you're refering to is on a higher level then the actual invoice details, also we don't have information in the file from the bank as to what number is being transferred - reference number or invoice number (I don't think bank would even know, because it's totally dependant on what the customer put on their check). Also, what I am trying to achieve actually is that whatever number is transferred is to be used for search in several fields (e.g. first look in BELNR, then look in XBLNR etc.).
One more thing, the customizing you're referring to, I was under the impression that this customizing is for the electronic bank statement and lockbox had it's own piece in the IMG (quite small, only couple of steps). Are you saying that you, guys, are using the electronic bank statement functionality to process the lockbox file? Which transactions are you using to process the IDOC that came in: flbp and feba_lockbox or others?
Thanks,
K.

Similar Messages

  • PAYMENT MENTHOD FOR LOCKBOX

    Hi,
    I am setting up the lock box for my comp code.
    1. Payment method
    I have to define payment method for incoming check .
    But ..
    When i am click on incoming payment. system display this options.
    1. debit memo
    2. bill/ex
    3. bill/ ex pmt .req
    4. payment demand
    5. card payment
    no option for incoming check .. so what option that i have to use ..
    Thank you,
    PB Patel

    Hi,
    Thank you for the reply its really help me to get me to the next stage.. 
    I upload the file through FLB2 ..
    now when i m going in FLBP ... in order to post it .. i got  this error.
    Table T049B does not have an entry with key LOCKBOX IDOC
    Reason ..
    1 System is using the RFEBLB30 ..
    2 in which program is using format = idoc ... ..
    But . we r using BAI file format .. So In OBAY .. i define BAI ... not IDOC ..
    Que : how can i solve this error to run FLBP ..  
    Thank you,
    PB Patel

  • Lockbox MICR Code issue

    Hello experts,
    We use IDOC for processing lockbox payments. Customer master is having bank information Routing number as "071923226" and Bank Account number as "0940536".
    Lockbox IDOC has Routing number as "071923226" and Bank Account number as "0000000000940536". Lockbox processing program is not identifying customer using MICR/Bank data because of leading zeros. Is there a way to fix this issue without changing the IDOC because .
    Thanks
    Raghuram

    Solution is to add bank key and bank account number with and without leading zero's.
    Thanks
    Raghuram

  • 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

  • IDOC testing for Lockbox

    Hi Experts,
    Can someone send me the sample file of Lockbox data for testing IDOC processing (email). I do not know what to fill in these parameters in WE19 (Finsta01). I created one customer invoice and do have all the lockbox information.
    These are the parameters to fill for lockbox test in WE19
    EDIDC      0000000000000000
            E1IDKU1
            E1EDK03
            E1EDK02
            E1IDB02
            E1EDKA1
            E1IDPF1
            E1IDKU7
    Regards,
    Sim
    [email protected]

    Hello
    EDIDC 0000000000000000 is for the port partner number etc
    E1EDK03 contains the year month date and time
    E1IDLB1 is the lock box number which the bank sends
    E1IdBq2 is the bank routing number and the acocunt number
    and another line of E1IdBq2  is the customers bank details which are maintained in the customers master
    E1EDQ02 is the check number with which the payment is made
    E1IDQu5 is the amount on the check
    E1Idru5 is the invoice amount
    and E1EDR02 is the invoice number in SAP
    Assign points if helpfull

  • IDOCS for Lockbox

    Dear All,
    can anybody help me with any readables on creating idoc for lockbox and how it is used ?
    best regds
    Subha

    Hi Das,
    Sorry for missing of link. PFA the links for your easy reference.
    Lockbox Processing
    Lockbox Configuration
    Thanks & Regards,
    Lakshmi S

  • Open Item Clearing IDOC

    Hello,
    Does anyone know if there's an idoc that can clear open items as you would in a t-code like F-32?  I know of the LOCKBX FINSTA01 idoc, but we don't need the lockbox piece and just want to do a post with clearing.
    Appreciate the help,
    Kevin

    You can try to use REMADV (PEXR2002) idoc but it is a payment also. If it is just a clearing that you want to do, why don't you use F.13 ?
    Or create your own idoc, doing a call trasaction of F-32.

  • Payment Advcie - EDI 823 (Lockbox  - Incoming Payment)

    Hello,
    In process of testing EDI 823(Lockbox u2013 Incoming Payments) using testtool, Idocs are been successfully processing when an attempt is made to post the incoming customeru2019s payment for an open invoice (Basic type u2013 FINSTA01, Message type u2013 LOCKBX). Payment advice note is being generated for the successful processed Idocs.
    Then we ran a report RFAVIS40 in SE38 which basically selects the payments advices and then posts the clearing document. In the process when we are trying to execute the report for the generated payment advices u201CFor document type DZ, an entry is required in field referenceu201D this is the message we are getting.
    Manually I execute the same payment advice number using FBE2. When I enter the info in u2018Payment totalu2019 and u2018Payment doc.nou2019. at the Header level of FBE2 and then I run the report again, invoice documents are getting cleared.
    What config settings require to automate this functionality? OR Am I missing any mandatory field information at the time I process Idoc? OR System would work only in this manner?
    Please pass your comments.
    Thanks.

    Hi,
    Have never worked with EDI earlier so have some basic questions.
    We have an interface for incoming payments. The idea is that the incoming EDI IDOC interface would clear the open items in the customer account.
    Initially, have planned to use PEXR200/ REMADV, but realised that it is for creation of a payment advice. Can i use this to clear post and accounting doc or clear an open item in the customer account.
    Is there any other IDOC that i can use.
    thanks in advance

  • Need Help with AP Interface and Lockbox

    Been 2 years in SAP and new to US. My company is changing banks . check and ACH transfer to bank.
    I am facing many issues at the place. Really need to understand IDOCS, EDI What format banks accept.How should I go about it?
    All about AP interface. Config and technical design.
    ALso about Lockbox  - BDI, BDI2 formats, other  details config and design.
    Can someone please send me some good material on these two topics. I will really appreciate. My email is
    [email protected]
    Thanks in advance. Points will be awarded.

    Been 2 years in SAP and new to US. My company is changing banks . check and ACH transfer to bank.
    I am facing many issues at the place. Really need to understand IDOCS, EDI What format banks accept.How should I go about it?
    All about AP interface. Config and technical design.
    ALso about Lockbox  - BDI, BDI2 formats, other  details config and design.
    Can someone please send me some good material on these two topics. I will really appreciate. My email is
    [email protected]
    Thanks in advance. Points will be awarded.

  • Lockbox / Remittance Advice Configuration Error

    We are developing a solution to correct some issues posting EDI 820 (remittance advice) and EDI 823 (lockbox) transactions.  Our SAP implementation consultant apparently advised us to map both of these to FINSTA01 IDOCS, instead of using REMADV for the 820.  We would like to change this.  Is there any reason NOT to use REMADV?
    We are also trying to contact the original consultant to learn why it was done this way.  It doesn't make sense to us.
    What is the best practice?
    (We're on ECC 6.0 + AFS).

    We currently process customer payments via lockbox using the BAI format.  We do receive EDI 820 payment advices for some customers.  We would like to automate the payment posting using the EDI 820.  I would appreciate any guidance for the step by step setup required. 
    We are using SAP ECC 6.  We just applied service packs 6, 7, and 8. 
    We receive customer payments via lockbox (BAI) and some payments via wire (applied using F-28)
    We receive EDI 820 for a few customers
    I can provide more details as needed.

  • Lockbox BAI2 - EDI 820 Payment Advice

    Hello All,
    Thanks very much for your time.
    We currently have lockbox with BAI2 format file coming in from the bank for all our customers.
    As an enhancement, we want to implement lockbox payment advice to come directly from the customer through EDI 820 payment advice and will only receive the payment header (the 6 record) on the lockbox file from the bank.
    The small customers will still follow the current process - send their check and payment advice to the bank and the detail will be transmitted via the BAI2 lockbox file.
    I know this can be done - but have some questions regarding the timing of the files and the set up process.
    When the EDI 820 payment advice file comes in first, the system can be set up to wait for the header file from the bank to clear the customer account / open items. But if the lockbox file gets in the system before the EDI 820 payment advice file, the payment will get posted on account based on the MICR number without any customization process. Is there a process that has been successfully implemented to deal this scenario?
    Please let me know and thanks again for your help.
    AM

    Incoming payment advice or outgoing?  I don't have the details with me, but roughly, you will have to work with the ABAP and EDI people to convert the EDI into the relevant IDOCS (I think the IDOC type is PEXR2002 and msg type is PAYEXT). For automatic postings for incoming EDI/IDOC payment advices the FI consultant will then define the posting rules to the relevant G/L accounts (TCode OT83).
    Thanks,
    Frank

  • Missing Payment Advice - Lockbox

    I am using Lockbox processing to handle clearing of customer receipts. 
    Several times a week we incur a problem where a payment advice in NOT created (no information on the AVI* tables found).  Other than no advice being created everything regarding the IDOC and customer master data is correct.  I have two cases where this appears, 1) their are open items which should have been matched and cleared but were not, 2) the reciept is a downpayment/payment in advance situation (where no open items exist).
    Can you advise as to common problems as to why payment advices are not created?  As mentioned, payment advices work correctly 95% of the time, but on a weekly basis we have this issue.  Payment advice type is 01.
    Any input will be very helpful.  Many thanks and best regards, David C.

    HAVE ISSUES WITH LOCKBOX TOLERANCES. IT IS NOT ACCEPTING PAYMENTS WITHIN THE TOLERANCE RANGE, IN FACT ANY PAYMENT OTHER THAN EXACT ACOUNT IS NOT GETTING POSTED.
    I HAVE ASSIGNED TOLERANCES TO USERS, EMPLOYEES AND GL ACCOUNTS.
    I HAVE ALSO ASSIGNED BLANK REASON CODES, CUSTOMER SEEMS TO BE MATCHED CORRECTLY WITH MICR NUMBER,
    I REMOVED TOLERANCES FROM PAYMENT ADVICES, I THINK SYSTEM HAS BEEN ENABLED TO CREATE PAYMENT ADVICES, THIS IS A GREY ARE POSSIBLY.
    ANY HELP IS APPRECIATED AS I HAVE 9 DAYS TOWARDS SUPERANNUATION.
    BEN
    347 658 8293
    469 426 7966

  • Processing Credit Card refunds-not using SD, posting CC pymts thru Lockbox

    I have tried to search the forums, all of them, for this issue but have not been able to find a solution.  I have not specifically checked the OSS notes.  Here is our situation.  We use our proprietary system to do our credit card processing and then we import the sales information through an IDOC into SAP to create the customer open invoices.  Once we receive payment from our processor,  our system is configured to load the payments through the Lockbox programming.  The only issue we have with this is that we cannot load any refunds, credits,  that might have been issued to customers through lockbox. Right now, we have an LSMW set up but this is very time consuming for our IT department and we would like to see if there is a better solution with SAP.

    hello sir,
    i want to your help
    i was installed fresh windows 7 via cd rom and then after installed all software.
    and now after 1 day customer complained me that cd rom not read any cd and i m also check when i insurt cd so its not read and when i am double click on cd rom icon its eject so what i do for that please reply on my email address.
    [text removed for privacy]
    VIMAL

  • Lockbox error while posting customer payments

    Hello,
    I am testing the lockbox file upload and the system was able to locate the Customer number but while clearing customer, I am getting an error saying
    No payment advices were found
    Message no. F5664
    I am trying to edit payment advice and I am getting the error as below
    Payment advice 01 10000000 does not exist for account 110006 C850
    Message no. FA006
    Please let me know why this error is coming.
    Thank You.
    Edited by: Raghavaa on Dec 26, 2011 8:17 PM

    I have found the cause and solution to this problem.
    This error ”Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1” and other similar errors like “Fill all required fields SAPMF02D 0111 ADDR1_DATA-SORT1“ which occurrs during the IDOC posting when there are more than one sales area or company code occurs when the customer number range is set up for Internal numbering. This means, that the number gets generated only at the time of save and upon debugging the IDOC, we found out that after creating the customer and the first sales area/company code record, the segment E1KNA1M is cleared completely! This is the reason, it throws an error which points to a mandatory KNA1 field as missing. (Like NAME1, SORT1 etc.)
    This was resolved by splitting the IDOC into 2.
    The solution is to First post only the KNA1 segment and create the customer.
    In the second step, pass the IDOC with all other segments along with E1KNA1M, but pass only KUNNR in E1KNA1M and the rest of the fields in E1KNA1M as “/”:  you would have got the KUNNR after the first step.
    Important note: This requirement to split the IDOCs does not occur when the customer number is known upfront. (Meaning cases where the customer number is externally generated) I also tested this and created a customer with external numbering and I was able to post more than 1 sales area with the same IDOC. 
    I noticed multiple threads with the same issue, but none of it had a concrete answer. I hope this information will be useful for anyone facing similar problems.
    Cheers
    Venkat

  • Customer Bank Details creation in Lockbox using EDI

    Hi Experts,
    I am working on a Lockbox implementation project. Here we migrate the BAI2 based file processing to the IDOC (FINSTA01 ) based one.
    When we used BAI2, in the standard program RFEBLB20, there was a logic to create the customer bank details, if they are not present in the KNBK Table. I do not see any such logic in the IDOC file processing Function Module IDOC_INPUT_LOCKBX. Is this functionality missing and we need to do it manually?
    Any help on this would be greatly appreciated.
    Thanks,
    Ajith Cheruvally

    Thanks Nithin,
    I am aware of that configuration. And there is a corresponding subroutine in the BAI2 file processing program to create the BDC Session with the name that we mention there.
    However, I am unable to find any relevant code for creating the BDC session in the FINSTA IDOC's IDOC_INPUT_LOCKBX function module.
    No worries, I have implemented an exit with the required logic in that FM.
    Thanks,
    Ajith Cheruvally

Maybe you are looking for