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

Similar Messages

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

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

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

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

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

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

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

Attaching a document along with payment advice during F110

Hi All,
when i run F110 all payments with payment mode 'T'(telegraphic) are mailed to the respective vendors and all payments with mode 'K'(Credit) are displayed in the spool(SP01).
Now the requirement is that the contract of the vendor(contract document is attached in the vendor master-FK02) should also me mailed along with the payment advice.
I created a Z-program(copied from RFFOEDI1) which downloads this contract document from vendor master onto the desktop and then uploads this and sends it to the customer.
However when i do this the mail request for the contract document is being generated(as can be seen in the send requests list (t-code SOSG) and the mail also gets triggered when i process it in SCOT), but no mail request is being generated for the payment advice .
Also no spool for payment advices with payment mode 'K' is generated in SP01.
Any help is appreciated and will be rewared generously.
Thanks in advance.
Najam
I am attaching the part of code i have inserted -
REPORT RFFOEDI1.
INCLUDE ZDWNLD_ATTA.
   F110ID-LAUFD   = ZW_LAUFD.
   F110ID-LAUFI   = ZW_LAUFI.
   F110ID-OBJKT   = KON_PARAM.
PERFORM F_MAIL_CONTRACT.
INSERT T012D-EDIPN INTO HEADER.
AT SELECTION-SCREEN ON PAR_WFOR.
IF PAR_WFOR NE SPACE.
    SET CURSOR FIELD 'PAR_WFOR'.
    CALL FUNCTION 'FORM_CHECK'
      EXPORTING
        I_PZFOR = PAR_WFOR.
ENDIF.
FORM F_MAIL_CONTRACT .
   F110ID-LAUFD   = ZW_LAUFD.
   F110ID-LAUFI   = ZW_LAUFI.
   F110ID-OBJKT   = KON_PARAM.
IMPORT SLKTAB FROM DATABASE RFDT(FB) ID F110ID.
READ TABLE SLKTAB INDEX 1.
IF SY-SUBRC = 0.
    W_LIFNR = SLKTAB-VONKT.
ENDIF.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
    INPUT         = W_LIFNR
IMPORTING
   OUTPUT        = W_LIFNR .
*Get vendor Email Address
SELECT SINGLE * FROM LFA1 WHERE LIFNR = W_LIFNR.
IF SY-SUBRC = 0.
SELECT SINGLE * FROM ADR6 WHERE ADDRNUMBER = LFA1-ADRNR.
ENDIF.
W_RECIPIENT = ADR6-SMTP_ADDR.
PERFORM DOWNLOAD_ATT USING W_LIFNR.
PERFORM UPLOAD_ATT_SEND_MAIL USING W_RECIPIENT LTP_FILENAME .
ENDFORM.                    " F_MAIL_CONTRACT
FORM DOWNLOAD_ATT USING    P_W_LIFNR.
SO_INSTI = P_W_LIFNR.
SELECT * FROM SRGBTBREL INTO TABLE TA_SRGBTBREL
WHERE INSTID_A = SO_INSTI
    AND TYPEID_A = SO_TYPID
    AND CATID_A = SO_CATID.
IF SY-SUBRC EQ 0.
   SORT TA_SRGBTBREL BY INSTID_A TYPEID_A CATID_A.
   DELETE ADJACENT DUPLICATES FROM TA_SRGBTBREL
     COMPARING INSTID_A TYPEID_A CATID_A.
   LOOP AT TA_SRGBTBREL INTO WA_SRGBTBREL.
     PERFORM PROCESS_ATTACHMENTS
     USING WA_SRGBTBREL-INSTID_A
            WA_SRGBTBREL-TYPEID_A
            WA_SRGBTBREL-CATID_A.
   ENDLOOP.
ENDIF.
ENDFORM.                    " download_att
FORM UPLOAD_ATT_SEND_MAIL USING    P_W_RECIPIENT
                                    P_LTP_FILENAME.
RECEIVER = P_W_RECIPIENT.
PERFORM ML_CUSTOMIZE USING 'Tst' 'Contract'.
PERFORM ML_ADDRECP USING RECEIVER 'U'.
PERFORM UPL.
PERFORM DOCONV TABLES I_ITAB OBJBIN.
PERFORM ML_PREPARE USING 'X' EXTENSION NAME.
PERFORM ML_DOSEND.
FORM ML_CUSTOMIZE USING    OBJNAME
                            OBJDESC.
CLEAR DOCDATA.
REFRESH OBJPACK.
CLEAR OBJPACK.
REFRESH OBJHEAD.
REFRESH OBJTXT.
CLEAR OBJTXT.
REFRESH OBJBIN.
CLEAR OBJBIN.
REFRESH OBJHEX.
CLEAR OBJHEX.
REFRESH RECLIST.
CLEAR RECLIST.
REFRESH LISTOBJECT.
CLEAR LISTOBJECT.
CLEAR TAB_LINES.
CLEAR DOC_SIZE.
CLEAR ATT_TYPE.
DOCDATA-OBJ_NAME = OBJNAME.
DOCDATA-OBJ_DESCR = OBJDESC.
ENDFORM.                    " ml_customize
FORM ML_ADDRECP USING   PRECEIVER PREC_TYPE.
CLEAR RECLIST.
RECLIST-RECEIVER = PRECEIVER.
RECLIST-REC_TYPE = PREC_TYPE.
APPEND RECLIST.
ENDFORM.                    " ml_addrecp
FORM UPL .
FILE_NAME = LTP_FILENAME.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
FILENAME = FILE_NAME
FILETYPE = 'BIN'
TABLES
DATA_TAB = I_ITAB
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
NO_AUTHORITY = 6
UNKNOWN_ERROR = 7
BAD_DATA_FORMAT = 8
HEADER_NOT_ALLOWED = 9
SEPARATOR_NOT_ALLOWED = 10
HEADER_TOO_LONG = 11
UNKNOWN_DP_ERROR = 12
ACCESS_DENIED = 13
DP_OUT_OF_MEMORY = 14
DISK_FULL = 15
DP_TIMEOUT = 16
OTHERS = 17.
PATH = FILE_NAME.
CALL FUNCTION 'PC_SPLIT_COMPLETE_FILENAME'
EXPORTING
COMPLETE_FILENAME = PATH
IMPORTING
EXTENSION = EXTENSION
NAME = NAME
EXCEPTIONS
INVALID_DRIVE = 1
INVALID_EXTENSION = 2
INVALID_NAME = 3
INVALID_PATH = 4
OTHERS = 5.
ENDFORM.                    " upl
FORM DOCONV TABLES MYPDF STRUCTURE TLINE
                   OUTBIN STRUCTURE SOLISTI1.
DATA : POS TYPE I.
DATA : LEN TYPE I.
LOOP AT MYPDF.
POS = 255 - LEN.
IF POS > 134. "length of pdf_table
POS = 134.
ENDIF.
OUTBIN+LEN = MYPDF(POS).
LEN = LEN + POS.
IF LEN = 255. "length of out (contents_bin)
APPEND OUTBIN.
CLEAR: OUTBIN, LEN.
IF POS < 134.
OUTBIN = MYPDF+POS.
LEN = 134 - POS.
ENDIF.
ENDIF.
ENDLOOP.
IF LEN > 0.
APPEND OUTBIN.
ENDIF.
ENDFORM.                    " doconv
*&      Form ml_prepare
      text
FORM ML_PREPARE USING BYPASSMEMORY WHATATT_TYPE WHATNAME.
IF BYPASSMEMORY = ''.
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
LISTOBJECT = LISTOBJECT
EXCEPTIONS
OTHERS = 1.
IF SY-SUBRC EQ 0.
MESSAGE ID '61' TYPE 'E' NUMBER '731'
WITH 'LIST_FROM_MEMORY'.
ENDIF.
CALL FUNCTION 'TABLE_COMPRESS'
TABLES
IN = LISTOBJECT
OUT = OBJBIN
EXCEPTIONS
OTHERS = 1
IF SY-SUBRC EQ 0.
MESSAGE ID '61' TYPE 'E' NUMBER '731'
WITH 'TABLE_COMPRESS'.
ENDIF.
ENDIF.
*Packing Info For Text Data
DESCRIBE TABLE OBJTXT LINES TAB_LINES.
READ TABLE OBJTXT INDEX TAB_LINES.
DOCDATA-DOC_SIZE = ( TAB_LINES - 1 ) * 255 + STRLEN( OBJTXT ).
CLEAR OBJPACK-TRANSF_BIN.
OBJPACK-HEAD_START = 1.
OBJPACK-HEAD_NUM = 0.
OBJPACK-BODY_START = 1.
OBJPACK-BODY_NUM = TAB_LINES.
OBJPACK-DOC_TYPE = 'TXT'.
APPEND OBJPACK.
*Packing Info Attachment
ATT_TYPE = WHATATT_TYPE..
DESCRIBE TABLE OBJBIN LINES TAB_LINES.
READ TABLE OBJBIN INDEX TAB_LINES.
OBJPACK-DOC_SIZE = ( TAB_LINES - 1 ) * 255 + STRLEN( OBJBIN ).
OBJPACK-TRANSF_BIN = 'X'.
OBJPACK-HEAD_START = 1.
OBJPACK-HEAD_NUM = 0.
OBJPACK-BODY_START = 1.
OBJPACK-BODY_NUM = TAB_LINES.
OBJPACK-DOC_TYPE = ATT_TYPE.
OBJPACK-OBJ_NAME = 'ATTACHMENT'.
OBJPACK-OBJ_DESCR = WHATNAME.
APPEND OBJPACK.
ENDFORM.                    " ml_prepare
*&      Form ml_dosend
      text
--> p1        text
<-- p2        text
FORM ML_DOSEND .
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
EXPORTING
DOCUMENT_DATA = DOCDATA
PUT_IN_OUTBOX = 'X'
COMMIT_WORK = 'X' "used from rel. 6.10
TABLES
PACKING_LIST = OBJPACK
OBJECT_HEADER = OBJHEAD
CONTENTS_BIN = OBJBIN
CONTENTS_TXT = OBJTXT
RECEIVERS = RECLIST
EXCEPTIONS
TOO_MANY_RECEIVERS = 1
DOCUMENT_NOT_SENT = 2
DOCUMENT_TYPE_NOT_EXIST = 3
OPERATION_NO_AUTHORIZATION = 4
PARAMETER_ERROR = 5
X_ERROR = 6
ENQUEUE_ERROR = 7
OTHERS = 8
*IF SY-SUBRC EQ 0.
*MESSAGE ID 'SO' TYPE 'S' NUMBER '023'
*WITH DOCDATA-OBJ_NAME.
*ENDIF.
ENDFORM.                    " ml_dosend

Hi,
As far as I remember there are no direct ways in SAP do to that.
One suggestion. Create a custom program to send emails and save it with a variant in DME (the last Tab in F110). This is the same place where you maintain the details for sending out the EDI information.
Once you are done with F110, you can carry out the print functionality to execute the program to send out emails with the payment advice.
hope this helps.
Regards

Payment advice note to vendors thru e mail

Guys,
After executing F110, system generates the payment advices.I updated the master reocrd of vendor with a test email id , system is sending payment advices to this mail id,as its our internal server mail id.But when I update vendor record with some other external mail address, the system displays the msg.below.and cannot send thru mail.Please suggest.
XS826 Cannot process message, no route from to
F0387 Advice note for pymt 5000 2000000405 will be printed; dispatch via e-mail not poss.
Regards
Shaun

Hi shaun,
Payment advice is transfer to the external sytem. It means we need conectivity between 2 systems. I need to configure EDI settings. You need to contact the ABAPer and Basis consultant for your configuration.
Regards
Odaiah Pelley

Idoc for customer payment advice

Hi all,
We receive Idoc for payment advice from customer. Can some body tell me how can I read this information to match the invoice.I mean how can I map Idoc field to SAP internal tables.
How do I know which Idoc field will hit which SAP table & which table.
So please guide me about Idoc mapping & finding appropriate field for inbound idocs.
Edited by: Nik Wallace on Aug 5, 2008 8:04 AM

Hello,
Customer of vendor payment advice is the advice informing the customer that the amount has been paid against which invoices.
You need to configure the payment advice in FBZP or give them as part of variant in F110.
When you run the automatic payment program, based on the FBZP settings, a payment advice gets triggered.
You are able to see your payment advice in SP02. To generate payment advice correctly, please make sure your settings in Variant (F110) are correct. Any invalid entries will result in NO generation of payment advice.
Hope this is useful to you.
Regards,
Ravi

Clearing Payment Advices

Hi
In SAP when we are creating a credit memo it allows you to assign this credit to a debit.
Once its assigned it created a payment advice with this credit and debit information.
I know how to clear this manually. I use FB05 and enter the payment advice info and its cleared.
But is there any way I can automate the process.
This is not an incoming EDI 820 or any payment. This is just a payment advice created by a credit and debit entry.
Can I use the program RFAVIS40 to clear these? If so how should I define the posting rules.
Thanks

Hi,
You can do it via OB74 and F.13
Rest (uncleared) can be processed via program RFAVIS40.
Regards,
Gaurav

Usage of inbound EDI payment advice

Similar Messages

Maybe you are looking for