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.

Similar Messages

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.

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

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

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

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 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 810 Inbound - Vendor Invoice

Hi
What is the Message type, Basic type, Process code and Function module for Inbound Vendor Invoice (EDI 810 Inbound) ?
Thanks
Maruthi

Hi
I am working on the Invoice receipt thru EDI-IDoc from Vendors (EDI-810 INBOUND). I am getting certain errors.
Error 1:
Customer , Vendor XXXXXXX not known
Message no. FD110
Error 2:
G/L Account XXXXXXX can only be posted internally.
Message no. F5562
I have tried to trigger IDocs using basic types INVOIC01 and INVOIC02. But all in vain.
Please rush your answer,
Cheers
Maruthi

EDI 810 Inbound

Hi,
i am trying to post an Inbound Idoc through message type:INVOIC.I have configured every thing and now able to post the Idoc by using WE19,Now i have file in application server with naming format OH_810_xxxxxxx.EDI. I am using the existing FILE port and have given the application server path in INDOUND FILE tab and the FM:EDI_PATH_CREATE_CLIENT_DOCNUM.
the issue is now the file is not picking....how to automate it like when ever the file comes in application server the idoc should be trigered.

Hi
I am working on the Invoice receipt thru EDI-IDoc from Vendors (EDI-810 INBOUND). I am getting certain errors.
Error 1:
Customer , Vendor XXXXXXX not known
Message no. FD110
Error 2:
G/L Account XXXXXXX can only be posted internally.
Message no. F5562
I have tried to trigger IDocs using basic types INVOIC01 and INVOIC02. But all in vain.
Please rush your answer,
Cheers
Maruthi

EDI idoc inbound statuses

We're running SAP in a different partition from EDI (TrustedLink) on an iSeries. I'm getting inbound documents just fine, but no inbound statuses. I see that the status documents make it over to the SAP partition but they're not visible in WE05 - so all of my successful outbound 850s are at at status of 18 & that's it. I've looked at authorities etc but am still missing something. Thanks in advance if anyone can point me in the right direction. Susan

try this
enter tcode we21,
Go to system , click on status
Then you can see the programe name , Double click on programe name, you can see ABAP editior screen.
Then you can see go to tan and click on object directry Tab.
You can see package for which object is created.
Now use tocde Smod, select F4 for enchancement , in package you can enter SED.
You can get follwing user exit
Exit name Short text
SIDOC001 Customer function for module pool EDI1
SIDOC002 CA-EDI: Exits in Function Group EDI6 (Partner Profile)
Technically all EDI-IDOC inbound and outbound programs are wirtten as FUCNTION MODUELS.In the every fucntion moudle you can find large number of user-exits.For outbound idoc after filling every segment you have a user exit like CALL CUSTOMER FUNCITON '001'.You can find by using the keyword search CALL CUSTOMER FUNCITON in that funciton module.
In inbound also you can find after every segment you can find user-exit.
For funciton module search you can search in se37 by using idoc type,For example ORDERS01 search in se37 by using *ORDERS8.
regards,
sapsd

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

EDI 823 inbound lockbox

Similar Messages

Maybe you are looking for