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

Similar Messages

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.

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

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 ?

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.

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

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

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.

IDOC to EDI file scenario and EDI file to IDOC scenario without Seeburger

Hi All,
IDOC (Invoice) to EDI file scenario without Seeburger
Pls let me know if anybody have blogs for the same
EDI file to IDOC (Orders) scenario without Seeburger
Pls let me know if anybody have blogs for the same
Regards

Hi Rachit,
>>Can anybody send me blogs to convert IDoc structure to EDI or EDI to IDoc structure using Conversion Agent or using JAVA Mappings.
Using conversion Agent there is no coding, If you have a conversion agent insatlled in your landscape you will have better understanding..
Also java code for IDoc to EDI have some problems:
1. The EDI format differs based on requirement so there will always be a customized code for it.. Like we have IDco to EDIFACT and ANSX12...
2. Because most of these codes are propriety materials I doubt whether anyone be sharing the complete code here in SDN. Better to have a java consultant at your end and put him with your requirement.. From the reply in above threads you should be clear that what you are looking for can be done from java coding..
All the best
Regards
Suraj

EDI file to IDOC using Business connector 4.6

Hi Gurus,
We have a requirement of converting the EDI file to IDOC using Business connector 4.6 (943 & 944 ) one Inbound and other is outbound ..
Can any one of you share the document on developing the scensrio ... we have searched couldnt get the same.
Thanks in advance .
Ramamurthy

Hi Raj,
Thanks for the reply , Yes currently we also having the project using PI as rightly said we are using the seeburger and then converting the EDI format to XML and then mapped in IR to the IDOC .
also using Item field conversion we developed some projects , similarly we have developed using modules too .
Since the Business connector is new to us we didnt able to catch hold on where to import the Java program that we write in the Business connector ... from Jothi reply understood the server side configuration.
In case of BC where is that we need to implement the java code if you can share some thing on this would be good .
Could you please share on how to transform and then implement the code in the BC ....
Thanks,
Ramamurthy

EDI, ALE and IDOC

Hi All,
I am a Junior ABAP developer. I am new to EDI, ALE and IDOC's. Could someone help me out how to start with this and the necessary material required to go through!!
Thanks in advance!!

HI Penchanta ,
Go through this links for additional information.
1.http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
2.http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
3.http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
4.http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
5.http://www.sapgenie.com/sapedi/index.htm
Regards.
Note: Reward if useful
Also check this link from SDN
(1) /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
(2) /people/kevin.wilson2/blog/2006/11/13/ale-scenario-development-guide
(3)http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
(4) idoc
(5)http://help.sap.com/saphelp_erp2005vp/helpdata/en/78/2178a651ce11d189570000e829fbbd/frameset.htm--
--This is for Message Control. See the Left Pane in this web page to get the ALE implementation for BAPI's also.
(6)/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment - Converson Rules Guidelines

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.

IDOC FINSTA01 information

HI All,
Could anybody provide some information on the mapping of data from BAI2 format to idoc FINSTA01. I checked the program FF_5 which accepts a text file (comma separated) as input to update data in SAP (direct insert into FEBKO), but we need to map this data to idoc FINSTA01's segements. I checked the documentation in WE60 but was not much of help.
Thanks and Regards,
Sachin

Hi,
Check this link
[IDOC Statistics|http://www.sapmaterial.com/IDOC_statistics_we07.html]
[Handle Acknowledgement of IDOC|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe]
Name of the table is EDIDC ---> Control record.
Regards
Narin Nandivada

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

EDI 823 to iDoc FINSTA01

Similar Messages

Maybe you are looking for