FINSTA01+ LOCKBOX

Hi All,
I have one doubt regarding how many times the particular segemnt repeated .
I am reading some data from EDIDC table and thern calling the FM ''IDOC_READ_COMPLETELY'
     loop at i_EDIDC
        call function module to collect the idoc information.
CALL FUNCTION 'IDOC_READ_COMPLETELY'
  EXPORTING
    document_number                = itab-docnum
IMPORTING
   idoc_control                   = edidc
TABLES
   int_edids                      = i_edids
   int_edidd                      = i_edidd
EXCEPTIONS
   document_not_exist             = 1
   document_number_invalid        = 2
   OTHERS                         = 3
Loop at DATA Record to fill segment
  LOOP AT  i_edidd ASSIGNING <fs_edidd>.
    CASE <fs_edidd>-segnam .
      WHEN 'E1IDLB1' .           "  C_E1IDLB1 Make consatatn SAU
        <fs_e1idlb1> = <fs_edidd>-sdata .
        APPEND <fs_e1idlb1> TO i_e1idlb1.
        CLEAR <fs_e1edpa1>.
      WHEN 'E1EDPA1'.
         <fs_e1edpa1> = <fs_edidd>-sdata.
         APPEND <fs_e1edpa1> TO i_e1edpa1.
         CLEAR <fs_e1edpa1>.
      WHEN 'E1IDPU5'.
        <fs_e1idpu5> = <fs_edidd>-sdata.
        APPEND <fs_e1idpu5> TO i_e1idpu5.
        CLEAR <fs_e1edpa1>.
    ENDCASE.                       "  case <fs_edidd>-segnam .
  ENDLOOP.                        "  LOOP AT i_edidd
ENDLOOP.
Here My Question is How many times the Segment E1IDLB1' & E1EDPA1' can be repeated for a single IDOC Num in I_EDIDC. I am sure segemnt 'E1IDPU5' will repeated multiple times for a single idoc num .But dont know abt other two segments.
I have to process some other function based on the value in the segments.
How can we create test data in WE19.
How can any one know that for a particular IDOC type a segment can be repated or not for a single IDOC Num.
Thanks a lot in Advance.
Best answer are always rewarded with points.
Regards
Saurabh T

Go To Tranction WE60, and give FINSTA01 and check your segments.
E1lDLB1>1 times(Check Min/Max>number of segment you can repeat)
E1EDPA1-->2 times.
E1IDLB1                  % ( IDoc: Lockbox Data/Account                       
                               Segment definition E2IDLB1 Released from Release 40A 
                               Optional min./max. 0000000001/0000000001             
E1EDPA1                        % ( IDoc: Doc.item partner information                 
                               Segment definition E2EDPA1003 Released from Release 45A
                               Optional min./max. 0000000001/0000000002
Thanks,
Narayan

Similar Messages

  • 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

  • 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

  • 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.

  • 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

  • EDI 823 for Lockbox

    Hi,
    We are trying to implement Lockbox functionality using EDI(FINSTA01 IDOC Type / Lockbx message type).
    Where can I find what information will be available in which data segment of the FINSTA01 type?
    I went to we60 and there is no detailed information available there.
    When we used BAI2, there were lot of materials available online describing what record is for what purpose.
    Could anyone guide me in understanding the Segment details?
    Thanks,
    Ajith Cheruvally 

    No Response.

  • Inbound IDOC FINSTA01 status Change

    Hi,
    Actually we are posting in bound idco for lockbox using Idoc Finsta01,Depending on the header and item amount ,ie if both are not equal  need to post the idoc with 64  status with custome message.
    Any User Exit ?
    Thanks,
    Madhu

    Hi,
    Please check these user exits for IDOC_INPUT_LOCKBX.
    EXIT_SAPLIEDP_201 (for Settlement Handling)
    EXIT_SAPLIEDP_202 (for Segment Processing)
    EXIT_SAPLIEDP_203 (for Changes to Payment Advice)
    Again, you need to fill up structure parameter FIMSG with your custom message and raise an exception.
    Regards,
    Ferry Lianto
    Please reward points if  helpful.

  • Did anyone know how to update status for Idoc Finsta01

    Hi ,
    Did anybody did updating idoc status and message for idoc type FINSTA01.
    In Lockbox idoc_input_lockbx.
    If any BADI avilibale fr this to update.
    Thanks,
    Madhu

    Option 1:
    See SAP Help as below you will get the idea-
    Certain IDoc statuses are classified as archivable in the standard system, while others are not. You can display or change this classification.
    The current status of an IDoc must be archivable before the IDoc can be archived.
    Procedure
    Choose SAP Menu -> Tools -> Business Communications -> IDoc Basis -> Control -> Status -> Maintain Status Value.
    To change entries, choose .
    Select the required status. By double-clicking you can call a detail screen, in which you can display or change the archivability.
    By using or you can display or change all statuses one after another.
    Option2: I think it might be possible using generate status file for the outbound IDOC and then change the status in the file further process it. But I am not sure, I just had a look at the Xns in WEDI and made this story
    Thanks,
    Naren

  • 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

  • Sort, sum & preprocess in FINSTA01 IDOC

    HI,
    I have an issue in lockbox processing.
    When data is received from bank into SAP, FINSTA01 idoc gets created in SAPThis idoc contains check details and invoice reference details. There is a preprocessor which sorts and sums invoice references. But, I observed that invoices are not getting sorted and summed in idocs.
    Please help me out to find out the reason why this preprocessor is not working as expected.
    Thanks & Regards,
    Bharath Kumar

  • Oracle EDI - Bank Statement Interface, Payment file to Bank and AR Auto Lockbox

    Hello,
    There is a need from the client to do setups for EDI - this is needed for Bank Statement Import from the Bank, sending Bank Payment file and also getting the Lockbox details. How is this done? What are the steps? What are the setup steps? Thanks,
    Arun

    Hello,
    There is a need from the client to do setups for EDI - this is needed for Bank Statement Import from the Bank, sending Bank Payment file and also getting the Lockbox details. How is this done? What are the steps? What are the setup steps? Thanks,
    Arun

  • Clearing of customer open items in FLB2 (Lockbox)

    Hi Gurus,
    What is the correct process of lockbox in case when we recieve partial payment or out of 10 invoices one is partially paid. What will system do.
    Thanks

    Hi
    Just run FEBP as a nightjob after the Finsta have been imported, and create one variant per company code. I works perfect for us.
    If you provide me with you email, I can send you a dump screen of our variants.
    Best regards
    Pernille

  • Issue with printing lockbox report

    Hi,
    My lockbox report after processing file is giving the total amount and check amount correctly but when I print the same report, the figures don't match with the correct report figures for check amount and advice total.
    Please help....
    Thanks,
    Sheel
    Edited by: Sheel Ahuja on May 19, 2010 11:11 PM

    Hello,
    Please, open a message for SAP on the OSS Marketplace. There are some notes for this type of issue, but they are currently in pilot release.
    So, open a message describing the issue and providing a reproducible example in your system.
    REgards,
    REnan

  • One lockbox for multiple company codes

    Is it possible to have one lockbox for multiple company codes?

    No, I don't think so. Lockbox is 1:1 for a Company Code.
    You configure Lockbox for a Company Code.
    You can use one of the 2 available Lockbox user exits (not sure which) to write a piece of code that searches invoices against the customer posted to different company codes. You will have to have the intercompany setups.
    You may find an OSS notes for intercompany clearing.
    Hope this helps!

  • One lockbox for multiple company code

    Hi Guru's.
    Currently we have one company code to many lockbox configured, process
    is working fine.
    We are in process of merging two companies.
    We have a scenario were we have one Lockbox shared between multiple
    company code, when we process the lockbox file lockbox process will
    clear one company code Invoice and other Invoice for different company
    code are unprocessed.
    We have looked in to user exit EXIT_RFEBLB20_001 and EXIT_RFEBLB20_002,
    was not much of help.
    Regards,
    KJ

    I had this scenario few years back in a company and we used exit RFEBLB20_002. We used logic to find the invoicing company code from the BSID table using the document number from lockbox file, then change the default lockbox company code to invoicing company code. Unfortunately this scenario will work only if you use unique document number ranges for each company codes which is not the case for most companies.
    Edited by: PaulKr on Sep 26, 2011 9:08 PM

Maybe you are looking for