EDI ALE Payment advice inbound

Hi Experts,
            Could any body help me how to do edi inbound report . The relation is between company vendors bank. When the bank giveing payments to the vendors the company has to receive conformations that should be updated in sap tables in bseg-sgtxt, bseg-xref1, bseg-xref2.
                                               I will give you maximum points.
                                                                                Satya.

Hi Satya
I think you are expecting payment advice to your company from bank.
For this you need create partner profile as BANK TYPE .
ANSI X12 txn is 820 - Payment Order/Remittance Advice
Please tell me is it ALE or EDI ?.
If it is EDI we are reciving the file from EDI Subsystem
It it is ALE means we are reciving the file from SAP R/3 only(genral practice).we can use ALE communication between SAP to NON-SAP systems also but when we are connecting to other company people will prefer EDI.
thanks

Similar Messages

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

Customer Inbound Payment Advice

Hello all,
What is the actual purpose of Payment Advices on the customers side (Inbound). Can somebody explain me how to post the customer payment advice in the SAP system? My assumption is below; please correct me where you see I am wrong
Customer sends the payment advice via email
1) Enter the payment advice manually by FBE1
2) Then goto F-28 and Enter and Clear the Customer open items against the Payment Advice. (We would received the EBS to reconcile Bank Account with the actual payment)
Can somebody provide me valuable input regarding my understanding and questions.
Thanks

Customer payment advices are created through two processes.These are independent processes.
1) lockbox processing - if the system did not find billing docs or payments do not match with billing doc, then system will create payment advice. Later AR clerks clears this payment advice by applying the payment to right customer & billing doc
2) in the second process, customer pays to your bank directly and payment details were sent by EDI to you. EDI creates payment advices. You can use FBE2 & RFAVIS40 to process payment advices. These transactions call FB05 to process customer payments.
thnx

Payment Advice FBE1

Hello,
What is the business purpose for the payment advice created using transaction FBE1?

Hi,
The payment advice number identifies a payment advice note together with the company code, the account type, and the account number.
The payment advice number can be assigned externally or internally and always begins with the payment advice type. The payment advice types are predefined and have the following meaning:
Payment advice type Meaning
01 Payment advice from lockbox
02 Payment advice from account statement
03 Payment advice from open item processing
04 Payment advice entered manually
05 Payment advice from credit memo display
06 Payment advice from customer (EDI)
07 Payment advice from reference number (DME)
08 Payment advice from correspondence
In the case of internal number assignment, the payment advice number is produced as follows:
aaddddddttttttuu,
whereby the following is the case:
Partial key Meaning
aa Payment advice type
dddddd Date of entry
tttttt Time of entry
uu Entered by (the first two letters)
Hope understood and assign points if you get through.
Thanks,
Vasu

Usage of inbound EDI payment advice

Hello experts,
I'm asked to implement an inbound payment advice / remittance advice via EDI using VDA 4907. I dived into the SAP help for this as well as into many discussions in this forum but I'm still unsure about the underlying concept as intended by SAP. My understanding is that the remittance advice closes the gap between a large single incoming payment and potentially many open items, thus clearing the open items and the payment.
Can someone please let me know if this understanding is correct?
How does this two-sided clearing process work?
Thanks in advance and best regards,
Christoph

Hi Abdul,
Currently I am working on EDI 820. I have really no clue how to configure this functionality.
I have done research but I couldn't manage to get enough material on this.
Since you have already worked on this using all your expertise I would appreciate if you could send some require material or info on the same.
Regards,
Victor

Automatic Clearing with Payment Advice via EDI

I am trying to automate the cash application process via the receipt of the customer inbound 820 (using message type REMADV, type PEXR2002). I can successfully post payment, clear open items, and set up deductions relating to a specific invoice, but I haven't been able to post deductions unrelated to an invoice. Our customers often take deductions not related to a specific invoice at the same time as remitting payment for invoices. Has anyone managed to post 'independent' deductions when posting a payment advice via EDI?
I also have one small problem selecting the customer open item for clearing. Our billing document number does not equal the financial accounting document number. We store our billing document number in the Assignment field, and this is the number the customer will reference when remitting payment. I have not been able to find a way to use the customer's reference number (e.g. Assignment field) to select the open item. Has anyone had any success using the Selection Rule assigned to the payer to select open items by something other than the accounting document number? Or is this functionality only available for manual processing of payment advices.
Any advice would be greatly appreciated!
Thank-you,
Shauna

Hi Kirti,
We are in the process of implementing incoming payments through EDI 820. However we are getting the below error when we generate the IDOC.
Formatting error in the field BKPF-WAERS ; see next message
    Message no. 00298
Diagnosis
    During batch input or when executing CALL TRANSACTION... USING a screen
    field was filled with an invalid input format.
System Response
    Processing was terminated.
Procedure
    The screen field has the technical name BKPF-WAERS . The cause of the
    error is described in the following message.
    Correct the appropriate BDC data."
We tried to debug and but we got below
In the 1st screen, the currency/ rate field comes up as blank. The value u2018USDu2019 was entered manually by me.
The Amount comes as blank as well u2013 hence the transaction shows an warning message that the line will be ignored because of the 0 amount
Lastly the following screen shows up and stops with the error message.
"Different Currencies in payment advice and document header /USD.
Any help is highly appreciated.
Thanks in advance
Krishna

Payment Advice EDI - Reason Codes

HI All,
At the time of configure the Payment Advise through EDI, Is it Reason Codes configuration is Mandatory.
Ex :
Case 1 :
SAP - Customer Invoice : @ 1000
Customer Account Dr - 1000
To Sales Revenue       - 1000
Incoming Payment Received file from EDI Transfer : @ 1000
Bank Main Account Dr - 1000
Customer Account or   - 1000
Case 2
SAP - Customer Invoice : @ 1000
Customer Account Dr - 1000
To Sales Revenue       - 1000
Incoming Payment Received file from EDI Transfer : @ 900
Will it accounting entry generate or will it stop due to the Partial Incoming Amount.
In this case Reason Codes will work. So Where can we insert the reason codes to capture the differential amount between the Invoice & EDI Incoming receipt
Regards
Raj

Hi Satya
I think you are expecting payment advice to your company from bank.
For this you need create partner profile as BANK TYPE .
ANSI X12 txn is 820 - Payment Order/Remittance Advice
Please tell me is it ALE or EDI ?.
If it is EDI we are reciving the file from EDI Subsystem
It it is ALE means we are reciving the file from SAP R/3 only(genral practice).we can use ALE communication between SAP to NON-SAP systems also but when we are connecting to other company people will prefer EDI.
thanks

Check Payment advice through EDI

Hi,
I need a solution to send the payment advice to bank through EDI.
For that i created partner profiles for vendor and bank. I activated EDI in vendor master also.
And i attached EDI accompaying sheet also to the FBZP t code.
for this we created a new payment method and testing. it is working.
our client is asking: He want to send the payment advice for the payment method 'C' - Check to his bank through EDI. What we have to do for this.
For this if we give C in payment method in F110 we have to use payment method program only not EDI program.
Please guide me
sateesh kumar

Hi Sateesh,
Generally payment advices are directly sent to Vendor, but sometimes clients will sent the payment details and payment advice to the bank.
In your case, if u want to select the Payment Method C, then if u give RFFOEDI1 program for EDI setting, then u cant print your cheques locally.
One Alternative is that use Payment Medium Workbench (PMW) in that check management option is present, try with that.
I am not sure how far it is going to be successful.
Regards
srikanth

EDI Vendor outbound payment advice, idoc do not contain RE in the header

Hi,
I am facing a critical issue on EDI vendor outbound payment advice idoc. Actually the IDOCs which i created do not contain the RE in the header record. This mandatory qualifier is located just before the SAP ID. The IDOCs which i created got error out and not translate.
Example - LIRE0001000922
Can anybody tell me that how can we get this RE mentioned in the above idoc no. I want this RE to be come when the idoc is created.
Point will be awarded.

Hi Rajesh,
If everything is maintianed, i think the problem is with the file that your are uploading. Please check the file.
And also check whether the data record is maintained. For Field Name "PARTNER_Q" youa have to assign the :QualPart" RE (biil-to-party) in the data record.
Check these things and i hope it solves your problem.
And you can contact me at [email protected]
Thanks
~Rajesh

EDI Payment Advice by email

Hello,
I have setup the BTE 2040 as oss notes 836169. "Register it for the event 2040 in transaction FIBF, under the process modules of a customer without country or application indicator."
Then I run payment program RFFOD__S to generate IDocs for EDI payment. I expect RFFOD__S to call the z function module in the FIBF config and send email, but it was never been called. The Idocs are created.
What's missing for me? we are in version ECC60. I even tried to debug but for some reason the function module was not called ever.
Please help.

Hi G Krishna Kishore
can u give me more details on how u are using BTE to generate emails for Payment advice from F110.
We would like to send our payment advices as an email to our vendors from F110
Thanks
Dave

EDI 820 Outbound Payment advice EUPEXR

When I am trying to generate an EDI through payment run F110, it correctly generates one for Message type PAYEXT and Idoc Basic type PEXR2002. However, in addition to that it is generating one for Message type EUPEXR and Idoc Basic type IDCREF01.
What is the purpose of this EUPEXR and why is it generating even though I havent set it up in the Outbound parameters of the Partner profile?
Thanks!

Have you checked this thread in SDN?
PEXR 2002, Stopping generation of EUPEXR inbound message type.
This is automatically generated by SAP, and deals with the eletronic signature details usually accompanying an electronic payment instruction set. The thread gives a way to prevent output of the IDoc (not preventing generation through!).
The Building Block documentation for In-House Cash clearly states:
When you create PAYEXT, EUPEXR is created automatically. Recommendation: Create a port to which EUPEXR can be sent, if you do not need this Idoc type in SAP In-House Cash. You can delete this file defined for the port at specific intervals.
Rgds
Gulshan

EDI 820 Incoming payment advice config

Hi,
what is the functionality of EDI 820 incoming payment advice in SAP. Can any one explain me the process involved involved and related config.
Thanks,
Santosh

Hi Santosh,
Can you please share your experiences in working with 820 for processing incoming customer payments.
Thanks

EDI820 currency and amount- blank in Payment advice.(Basic type PEXR2002)

Hi All,
We are in the process of implementing EDI 820 for customer payments.
When the IDOC is generated, a payment advice is created but it has blank values in amount & currency fields, due to which we get an error "Formatting error in the field BKPF-WAERS ; see next message"
I had maintained currency & amount values in segment E1IDKU5 through WE19, but I am not sure why the payment advice generated has blank values.
Can anyone please let me know what could be the reason.
Thanks in advance.
Krishna

Have you checked this thread in SDN?
PEXR 2002, Stopping generation of EUPEXR inbound message type.
This is automatically generated by SAP, and deals with the eletronic signature details usually accompanying an electronic payment instruction set. The thread gives a way to prevent output of the IDoc (not preventing generation through!).
The Building Block documentation for In-House Cash clearly states:
When you create PAYEXT, EUPEXR is created automatically. Recommendation: Create a port to which EUPEXR can be sent, if you do not need this Idoc type in SAP In-House Cash. You can delete this file defined for the port at specific intervals.
Rgds
Gulshan

SAP ABAP and EDI/ALE/IDOC

Hi gurus,
I am an ABAP consultant and I am trying to learn EDI/ALE and Idoc, but I am not sure where to start with and what all do I need to cover in it. So can you please tell me how to proceed and what all is reqd. to know about EDI/ALE and Idoc for an ABAP guy and it will be great if you can also send me some documentation .
Thanks,
Rajeev !!!

Please check this online document for ALE and IDoc.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
EDI
Electronic Data Interchange
Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
Refer
http://www.erpgenie.com/sapedi/index.htm
http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp
http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/
http://www.erpgenie.com/sapedi/index.htm
http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd
EDI is nothing but Electronic data interchange. SAP will support EDI through Intermediate documents (IDOCS).
EDI (Electronic Document interchange) - EDI is the electronic exchange of business documents between the computer systems of business partners, using a standard format over a communication network.
EDI is also called paperless exchange.
Advantages:
Reduced Data entry errors
Reduced processing time
Availabilty of data in electonic form
Reduced paperwork
Reduced Cost
Reduced inventories and better planning
Standard means of communications
Better business process
EDI has two process
1. Outbound process
2. Inbound process
OP:
1.Application document is created.
2.IDOC is generated
3.IDoc is transferred from SAP to Operating system layer
4.Idoc is converted into EDI standards
5.Edi document is transmitted to the business partner
6.The Edi Subsystem report status to SAP
IP:
1.EDI transmission received
2.EDI document is converted into an IDOC
3.IDOC is transferred to the SAP layer
4.The application document is created
5.The application document can be viewed.
EDI FLOW :
Here is some thing which helps you and here the purchase order is taken as example too..
Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.
What parts of the business cycle can be supported by EDI?
Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.
How does EDI get started?
EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.
What is the flow of EDI?
The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.

Is there a way for EDI 820 (remittance advice) to identify proforma invoice

Hi,
We have certain customers who pay by proforma invoices. These customers send remittances through EDI 820 which we create as payment advice in SAP. When the cash comes in, the payment advice is not being applied since the document number has the proforma invoice and in FI, the proforma invoice is not stored anywhere.
Proforma invoice in our case is a consolidated billing document that is not passed onto FI. Any thoughts to have the payment advice apply when the cash comes in even though the customer pays by proforma?

Hi,
We have certain customers who pay by proforma invoices. These customers send remittances through EDI 820 which we create as payment advice in SAP. When the cash comes in, the payment advice is not being applied since the document number has the proforma invoice and in FI, the proforma invoice is not stored anywhere.
Proforma invoice in our case is a consolidated billing document that is not passed onto FI. Any thoughts to have the payment advice apply when the cash comes in even though the customer pays by proforma?

EDI ALE Payment advice inbound

Similar Messages

Maybe you are looking for