EDI 823 - IDOC FINSTA01Mapping problem

While processing inbound IDOC for lockbox program i am able to create payment advice. but payment advice type is taking as '05'(Payment advice from Credit memo) it sholud be '06'(Payment advice for customer(EDI)) in AVIK table
i am not able to map this properly and suggestions please.
Regards
Muthappan

Hi Luis -
Another option to consider is <a href="http://help.sap.com/saphelp_nw04/helpdata/en/cf/406642ea59c753e10000000a1550b0/frameset.htm">Mapping Lookups</a>....   RFC based lookup in your case.   You can do this in your mapping to complete the target IDOC without bpm.
However, I will say I personally prefer avoiding the use of mapping lookups within the source or target system of the same scenario (since this seems a bit redundant), but sometimes it's unavoidable.  If you only have to do one or a few, it's acceptable...    a series of lookups, I'd start considering and weighing other options since this could be costly in terms of performance.
If possible, if the remaining data to complete the message is in the target system, I'd also consider trying to complete it once the message arrives there.  For the IDOC in ECC, have you found out if there's a preprocessing routine or exit that would give you a chance to complete the IDOC.  There's also what Krishna suggested of converting the target interface into an async proxy, within which you can also complete the data.  In either of these cases, there's custom application development to consider.
Regards,
Jin

Similar Messages

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

  • 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

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

  • 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

  • Seeburger EDI to IDoc

    Hi,
    The actual payload is not getting generated in the EDI to IDoc scenario.
    The acknowledgment is getting generated.
    What could be the possible error?

    Anu,
    is your mapping determined automatically or are you explicitly stating the mapping name in your
    module configuration?
    If you set mappingName to Auto BIC tries determine the correct mapping by looking at the
    the UNH segments, e.g. UNH1ORDERS:D:97A:AA'. If your mapping has been labeled
    differently in the Mapping Designer, for instance E2X_ORDERS_UN_D97A the system
    won't be able to find the mapping and therefore you won't get any payload.
    As I suggested before try using the parameter u2018logAttIDu2019 Value u2018ConverterLogu2019 in your
    module chain that will most likely tell you what the problem is.
    Sven
    Edited by: Sven Buttler on Jul 9, 2010 10:26 AM

  • 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

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

  • Conversion Agent -   (EDI - XI - IDOC)   -  Help

    Hi Experts,
    I am working on the scenario (EDI - XI - IDOC)  using Conversion Agent for Converting EDI data into XML.
    I am facing many problems in Real Time,  can any one who has already worked on the same scenario  send me complete scenario with screen shots,
    I need immediate help, really it is very urgent for me.
    Regards,
    Study SAP

    Hi Kishore,
    Thanks for your reply, We are using Standard IDOC Orders05 and EDI message ANSI X12 - Message Type 850 for Purchase Order.
    Posting EDI Data of Purchase Order in R/3 Sales Order as INBOUND Message.
    Using Conversion Agent Parser for the same and deployed this project at Integration Server in ServiceDB Directory.
    The Conversion Module CMTransformBean is also deployed at XI Server.
    When we are puting file at FTP Server, our XI System is not picking up file while using Conversion Agent Module,
    while it is picking up without conversion module successfully.
    Please help,
    Regards,
    Study SAP
    [email protected]

  • Regarding EDI----XI----IDOC

    Hi All,
    I have One Requirement here is that
    My Client's Customer will send EDI Formated Data (ANSI Type ) to Client. That Data has to be Posted into SAP R/3 Database. So here We are Using XI For that .
    Can Any One Explain me what could be the Scenario here And
    How to Handle this ANSI Data Format.
    Regards
    Babu

    Hi
    Scenario is EDI-XI-IDOC
    Data Will come in the Form of ANSI
    1) I Will Use IDOC Adapter in the Receiver End
    2) For Sender Side Which Adapter I Need to Use & How to do the Conversion From ANSI Format to XML ??????
    Can You Provide Any Real time Scenario Or Any thing Which meets this Requirement.
    I am Still in Confusion How this ANSI Data Will be Converted into XML Either it Can Happen in Seburger Adapter OR in XI Also
    Can You Expalin me How this Conversion in Detailed
    >>>>>>>>>>>>>>>>
    if you are getting the data in the format like ANSI then you have to first create the XML message with the help of the BIC mapper.
    the BIC mapper is basically used to convert the EDI message into the XML message. to convert the EDI message into XML message ypu have to create the mapping using the option createE2xmapping in the BIC mapper.
    the mapping that will be generated using the BIC mapper have to be deployed on the server.
    and in the adapter you have to used the same mapping name that you have deploy on the XI server in the module tab of the adapter.
    if you still face the problem please reply me back.
    Thanks
    Rinku

  • In EDI to IDOC or Idoc to EDI can we go for Dynamic recevier determination

    Hi all
       I am doing an EDI to IDOC scenario involving SEEBURGER( AS2) adapter .can we go for extended receiver determination
    Regars
    Saurabh

    Saurabh,
    You can not use Extended Receiver Determination coz AS2 connection is like point-to-point connection which requires AS2 id of both sender and receiver. Therefore you can not use the Extended receiver determination.
    Reagrds,
    Sarvesh

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

  • ALE, EDI and IDOCS

    Hi
    I am learning some stuff on ALE,EDI and IDOCS... are there any good sites which gives clear step by step procedure for the above.
    Thanks in Advance.
    Sudhi

    Hi Sudhi
    You can find details on SAP courses from your country's sap.com site. You can find links from http://www.sap.com/contactsap/countries/index.aspx .
    Also some Education Partners of SAP give courses. Some info about these will also be there...
    Regards...
    *--Serdar

Maybe you are looking for