Lockbox with EDI 823

Here is the process we follow:
We get EDi823 from the Bank. we create the I-doc FINSTA01 which creates the data in the Payment advice. The customer pays by 2 fields- Actual Invoice number and reference which is a sales order number.
What are the settings we require in the Selection rule or FLBP to check for both the fields? we created a new selection field with Document number and Reference field and attached it to the customer master but that is not working and FLBP is putting everything "on Account".
Any Suggestions.

Hi Nitin
When you create the selection rule, you can prioritize the fields. In your case, document number should be first and then the reference.
Also, in the config for selection rule, the system gives the options for external selection filed and the selection field. So, you need to take a look at the payment advice and confirm that the document number is getting populated in the BELNR field of the payment advice and the order number is actually getting populated in XBLNR.
If you EDI 823 is mapped to populate the above values in some other fields in the payment advice, your config should reflect the same. Otherwise the system would not match the open items.

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

  • EDI 823 inbound lockbox

    Hello all,
    I am using idoc_input_lockbox fm to process finsta01 idocs generated based on EDI 823 format. I am having a custom field in AVIK, payment advice header table which needs to be populated with the 3 fields from the idoc concatenated. Is EXIT_SAPLIEDP_202 right place to do this?  I am moving the fields I need from the corresponding segments into the custom field of AVIK and updating idoc_avik parameter with this.

    No Response.

  • EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

    Hi All,
    We are facing some issues regarding EDI 821 and EDI 823 file mappings.
    We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
    EDI 823 - Lock Box
    Basic IDOC type - FINSTA01
    Message type - FINSTA
    Process Code  - FINS
    The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
    EDI 821 -
    Basic IDOC type - PEXR2002
    Message type - PAYEXT OR REMADV
    Process Code  - PEXC OR REMA
    We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
    We are trying different combinations but nothing is working so far.
    I need the following things to proceed furthur.
    1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
    2)If those are not correct, can you please let me know the correct entries
    3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then  I can re check it.
    4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
    thanks in advance for all your help.
    Please let me know if my question is not clear.
    Thanks,
    Ramesh.

    Hi Ramesh,
    I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
    First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
    Are you can give me the exact error and i can help you as well.
    Thanks,
    Mahesh.

  • Mapping Issue for EDI 823 from XI to R/3

    Hi All,
    We are receiving an EDI 823 from XI to R/3 and the XML file looks like this as below.
    - <FINSTA01>
    - <IDOC BEGIN="1">
    - <EDI_DC40 SEGMENT="1">
      <MANDT>110</MANDT>
      <DOCNUM>0000000000000000</DOCNUM>
      <DIRECT>1</DIRECT>
      <IDOCTYP>FINSTA01</IDOCTYP>
      <MESTYP>LOCKBX</MESTYP>
      <STD>X</STD>
      <STDVRS>003040</STDVRS>
      <STDMES>823</STDMES>
      <SNDPOR>EXTD_BALE</SNDPOR>
      <SNDPRT>B</SNDPRT>
      <SNDPRN>1000000015</SNDPRN>
      <SNDSAD>1000000015</SNDSAD>
      <RCVPOR>SAPYRD</RCVPOR>
      <RCVPRT>LS</RCVPRT>
      <RCVPRN>YRDCLNT110</RCVPRN>
      </EDI_DC40>
    Now the problem is the incoming IDOC ends up with errors.
    Recipient Information
    Port : <empty>
    Partner No: YRDCLNT110
    Partn Type: LS
    Sender Information
    Port: SAPYXD
    Partner No: EXTD_BALE
    Partn Type: LS
    Whereas there exists no partner no. in R/3 by the name EXTD_BALE. The interesting part is EXTD_BALE is a IDoc Adapter Port No in XI.
    Please provide inputs on these.
    Regards,
    Karthik

    Hi, any feedback in this one ?

  • 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

  • EDI 823 to iDoc FINSTA01

    I am trying to map EDI 823 file to iDoc FINSTA01.
    I mapped as much as I know, but I am getting following errors when I test it:
    - External transaction is missing for determining the posting rule
    - Bank statement date is incorrect: 00000000
    Anyone seem these errors?
    Anyone know what I need to fix to get rid of these errors?
    Any help can be really appreciated.
    Thank you,
    John

    Hi,
      Can you give the procedure to configure EDI 823 and the bare minimim segments with fields that are required to be filled if you have solved the issue you got earlier.
    Thanks & regards,
    raj

  • EDI 823 (Inbound) - Field Mapping

    Hello,
    I need to configure Incoming IDOC EDI 823 for Lockbox.
    Basic type: FINSTA01
    Message Type: FINSTA
    Processing code: FINS
    Function Module: IDOC_INPUT_FINSTA
    By giving the Basic type u2013 FINSTA01 and executed in the test tool, I am getting the list of all the segments related to this Idoc type.
    I request please let me know how I can map the field segments by taking minimum segments and what qualifiers should I input to process the idoc.
    Thanks for your co-operation.

    No Response.

  • Getting error while creating Business Action with EDI EDIFACT 837 document.

    Hi,
    When I am trying to create a business action with EDI 837 &lsquo;.ecs&rsquo; file, I am getting a error. It is not creating the business action. Even it is not displaying any error details.
    Please help me in resolving this issue as it's very urgent.
    Thanks in advance.

    Hi Jyotirmoy,
    What error you are getting exactly while creating the business action? Did you try to create business action for any other protocol? If not, then please try to create business action for any other protocol and check whether you are getting the same error over there also.
    Regards,
    Anuj

  • Mapping error for EDI 823 from XI to R/3

    Hi All,
    We are receiving an EDI 823 from XI to R/3 and the XML file looks like this as below.
    Partner No: YRDCLNT110
    Partn Type: LS
    Sender Information
    Port: SAPYXD
    Partner No: EXTD_BALE
    Partn Type: LS
    Whereas there exists no partner no. in R/3 by the name EXTD_BALE. The interesting part is EXTD_BALE is a IDoc Adapter Port No in XI.
    Please provide inputs on these.
    Regards,
    Karthik

    Hi Karthik,
         Have u configure a R/3 port in IDX1 of XI. This port has the RFC destination pointing to R/3. It will be used by XI to get into R/3.
    Regards,
    Akshay

  • How to link Partner function with EDI ?

    Hi all,
    While sending PO thourgh EDI i am getting some error message...Partner function is not assigned with EDI..this message is not coming with ALE.
    Can any body help me to "How to link Partner function with EDI "?
    Thanks in advance.
    ankush

    Hi Ankush,
    Perhaps unintentionally, you are not rewarding points for correct answers, instead of clicking on the radio button"AWARD POINTS", you are clicking  "SOLVED BY OWN".
    and no points are being given from your side.
    Please award points if you find the answers helpful.
    Now also you can award points first, unassign by clicking again and then assign to whomsoever you think deserves.
    Regards,
    Sachendra Singh

  • How to work with EDI 810

    Hi Guys,
    Iam new ABAP and i have to work on EDI in which iam going to use 810,850,855,856.
    Iam not able to connect to EDI and even i don't know how to use the above numbers.
    Canany body help me and provide me the step by step process of how to use this 810,850,855,856 in EDI or else please provide me the link from i can get the steps.
    My in Trouble with EDI please any boby can help me. I will be very thankful to them.
    Regards
    Venkata

    Rajesh,
    These are just another method of representing the business documents.
    Its called as ANSI X12 format.
    810 - Customer invoice
    850 - PO create sales order
    855 - PO acknowledgement
    856 - Advance shipment notice
    Check the below links,
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/dc/6b7c9f43d711d1893e0000e8323c4f/frameset.htm
    i hope this will help you.
    Reward points if its help full.
    -Prsna

  • Inbound EDI 823

    Hi Guys,
    I'm working on EDI 823 inbound file to SAP. Appreciate if u have any document for mapping EDI 823 (IDOC FINSTA01) to SAP.
    u can mail me at [email protected]
    really appreciate it....

    Hi Rams,
      We really need it. can you send it please.
    Thanks & Regards,
    Raj

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

Maybe you are looking for