REMADV / PEXR2002 mapping

Hi,
Does anyone have an example of mapping remittance advice for customers from a bank? It is not coming from the customer.
Customer number is not included (E1EDKA1 partner function 'AG'), only INV number and check # with amount.
I'm having problems with:
"Company code could not be determined for intermediate document..." and
"Customer/vendor could not be determined for intermediate document..."
I've been thru SAP note 63485 to configure the E1IDB02 segment. Still no luck.
Also stepped thru the function module IDOC_INPUT_REMADV_CTR - company code lookup keeps failing in a function called: GET_BANK_ACCOUNT because the Bank's swift code is not equal to the bank number:
IF BNKA-BANKL <> I_BANKL AND BNKA-SWIFT <> I_BANKL.
DELETE X012K.
ENDIF.
Does not make sense?
Thanks,
Craig

Hi Craig,
Please check these mapping for:
<a href="http://www.erpgenie.com/sapgenie/docs/sapedi/remadvin.xls">REMADV Inbound</a>
<a href="http://www.erpgenie.com/sapgenie/docs/sapedi/remadvou.xls">REMADV Outbound</a>.
Regards,
Ferry Lianto

Similar Messages

How to specify alternate G/L account in PEXR2002 REMADV inbound IDoc

Hi,
I am trying to post a Remittance Advice REMADV PEXR2002 IDoc into SAP. For a given item from the EDI 820, i need to create two line items in the payment advice. E.g. the invoice amount for an item is 1000. The payment is 700. And i need to post 300 to the rebate account.
For the first line item, I need to pass in the payment from the customer. This part works fine.
However, for the second line, I also need to post a credit to a G/L account. But I am not able find where to pass in the alternate account information and the account type in the IDoc.
In FBE1, I can create the payment advice manually with the two line items. For the second line item, i specify the Account type as S for G/L account and pass in the alternate account number.
I have already coded some of the user exit EXIT_SAPLIEDP_101 for IDOC_INPUT_REMADV processing for the IDoc where i am doing a lookup of the accounting document from the invoice number. This part works fine. But i can't find a way to pass in the G/L account information.
Any help is appreciated.
Jay

I figured this out. In the user exit EXIT_SAPLIEDP_101, fill in the AVIP_OUT structure. This has the fields for the alternate account information and the account type - and all of the fields shown in FBE1.
Jay

Remittance Advice to Vendor through EDI, message REMADV

Hi Guru
I want to send a remittance advice to vendor only through EDI after running payment run. But standard SAP requires configuration for Vendor and as well as House Bank and generates two Idocs one for bank(Message type PAYEXT-PEXR2002) and one for Vendor(Message type REMADV-PEXR2002).
The requirement is only to send the remittance advice to vendor but not to the bank is any way that i can stop generating idoc to bank.
THANKS & REGARDS
Pavan
Edited by: Pavanks on Sep 14, 2009 10:28 AM
Edited by: Pavanks on Sep 14, 2009 10:29 AM

hi Pavan,
you want to do the open item clearing without the banking file throught auto payment run, do you? can you try to use other payment method , like check.
thansk

Open Item Clearing IDOC

Hello,
Does anyone know if there's an idoc that can clear open items as you would in a t-code like F-32? I know of the LOCKBX FINSTA01 idoc, but we don't need the lockbox piece and just want to do a post with clearing.
Appreciate the help,
Kevin

You can try to use REMADV (PEXR2002) idoc but it is a payment also. If it is just a clearing that you want to do, why don't you use F.13 ?
Or create your own idoc, doing a call trasaction of F-32.

Interface test in PI 7.1

Hi Experts
I am working on a Proxy to SOAP (Syncronous) scenario, I am testing this scenario by creating the Claim at ECC, and the data comes into PI and it goes out to the external vendor
But I want to change the Request Message from Proxy to my own test message (Provided by the Vendor) and send it to the same web service
How can I test the scenario from End to End (at least from PI to Web service call), where should I need to give the test data to complete the testing
Please let me know
Thanks
PR

Well is according your receiver determination
SenderParty , Serder Service
ReceiverParty " your BPM" and the service.
the interface =(e.g REMADV.PEXR2002) and the namespace.
User and Password.
And paste the your XML Payload

Idoc2File- WE20 Configuration Details

Hi,
The scenario is IDoc to File , Please suggest below details for Outbound IDOCs
   IDOC --- REMADV.PEXR2002
   IDOC --- MBGMCR.MBGMCR03
*We20 --> Outbound Parameters --> Message Control*
Application -         ???
Message Type-    ???
Process Code -     ???
Thanks,

Hi,
Below T-codes can help you find information:
Check Transaction NACE to see what applicatios you can use for different objects.
Check transaction WE42 for all inbound process codes
Check transaction WE41 for all outbound process code.
Check transaction WE64 for inboud / outbound message types and related process codes.
Not sure if any standard process codes are avaialable for the mentioned outbound idocs.
Post you question in other forum like MM / SD .

Mapping from PEXR2002 iDoc to EDI 820

We are planning to use XI to map from the payment advice (PEXR2002) iDoc to EDI 820.
We have 2 options: (1) Use XI and an EDI adapter (e.g. Seeburger); or (2) Use XI's own mapping functionality.
If you have done iDoc to EDI mapping with either of the above 2 options, please briefly advise about your experiences and how much efforts it took to develop the mapping.
Thank-you
Bac Quan

Hi Bac,
Although it is possible to create an EDI message in an XI mapping (or XSLT), this is not very nice. The use of an EDI adapter (iWay or SeeBurger) is strongly recommended.
The other way around (rom EDI to XML) is hardly feasiable without an EDI adapter. Although I haven't worked the SeeBurger adapter, it looks quite nice.
Kind regards, Guy Crets

Mapping fields for REMADV EDI process

Does anybody know the fields we would need to map in our idoc that would allow us to have reference key 1, reference key 2, and the text field populated with data in the payment advice after running our bd87 for our REMADV edi process? Currently we have the other fields necessary filled in to get most data to our payment advice, but our users are asking that these 3 fields are updated as well from our idoc.

Hi Tony,
- The part that is painfully slow is when you need to
map the fields of the aggregated attribute to the DB
fields. It takes 30 seconds to open a drop-down box
for the DB field selection. Sometimes freezes
altogether (or maybe I was not patient enough)This is definitely not good and I haven't seen this problem before. It would be great if we could fix this before the final 10.1.3 release. Could you send me your project at [email protected] ? I shouldn't need the class files, just all of the workbench xml files. You can just send the 9.0.4.5 project if that is easier.
One additional thought. When I was recreating my
project in 9.0.4.5 it complained untill I have
included all of the jar files into my project
classpath. 10.1.3 was less demanding in that respect.
Could it me that those unresolved references were
slowing the mapping?What exactly do you mean by it complaining? Do you mean that it wouldn't let you generate deployment xml? In 10.1.3 there is no longer a requirement to have class files on the classpath when generating deployment xml. You will only need them to import or refresh classes.
Karen Moore

IDOC PEXR2002/REMADV : On Account Posting

Has anyone encountered an error " Difference amount is to big for clearing.........." when processing the IDOC which has a invoice number which the system is not able to find?
The payment advice is created but the FI document is not created and the error "Difference amount is to big for clearing........" is displayed. However if I manually via FB05 enter the payment advice the system creates on account posting.
Any comment is appreicated.
Thanks

Hi,
The system is saying difference in dr and cr line items, thats why it is not clearing.
See same amount you are entering or see any advance payment document or any withholding tax document or see any differency in currencies also.
Regards,
Hari

EDI 820 mapping into SAP

Hi
Can any one give me the step-by-step approach in mapping the EDI 820 (both Inbound steps and Outbound steps) into SAP standard functionality ?
Thanks
Maruthi Ram

Hello Maruthi
[http://edi.stylusstudio.com/msg013304.htm]
Hi Jeff-
It is a message type PAYEXT (REMADV), the i-Docs are PEXR2001 and
PEXR2002.
Best Regards,
Mike Kelly
----- Original Message -----
From: "Jeff Garwick" < To: < < < Sent: Wednesday, 16 February, 2005 05:04 PM
Subject: [EDI-L] SAP transaction set / EDI 820
What is the SAP transaction set that supports an inbound EDI 820
payment/remittance advice?
Thank you,
Jeff Garwick
Bourns, Inc.
Please use this input as starter for your own detailed search and let us know if you have found an appropriate solution.
Regards
Uwe

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.

Vendor Payment Advice - idoc PEXR2002

Dear guru,
My customer would like to receive a payment advice from the bank regarding the vendor payments done.
It means that after processing the F110 and sent the payments to the bank, we will receive an acknowledgement idoc from the bank in order to inform us that all payments have been correctly processed.
I have seen that the idoc PEXR2002 can be used as "payment advice" with message type REMADV for instance. But all the cases that i have seen concerned customer payment advices sent directly by them.
Is anyone know if it is possible to use this idoc in order to retrieve the payment information for vendor and not customer?
If yes, where can we retrieve those information in SAP? Besides the table AVIK/AVIP, can we check the payment advice integration somewhere else (reports, financial document)? because in our case we just want to retrieve the confirmation of payments but there wont be clearing between payment/vendor invoice because it will have been already done at F110 processing.
I hope this is clear enough.
Thanks a lot for you help
Guillaume

Hi Afzal,
For sending Payment advice by E-Mail, "You need to copy SAMPLE_PROCESS_00002040 and adjust it to write code as per your requirement. This BTE runs for each payment advice note to be sent and in the module, it is mentioned 1=print, 2 = Fax and I=mail, so you can set your priority, that if an E-Mail address is maintained in the vendor master, send mail or if no E-mail address is maintained send Fax, and if both are not possible shoot a Print.
From Configuration side, you need to maintain the Z copy of SAMPLE_PROCESS_00002040 in FIBF transaction under the Process module of a customer without country or application indicator.
SAP Note 836169 - Consulting: Payment advice notes by email or fax.
Regards,
SAPFICO

Java mapping or UDF required for a requirement!!!

I am doing idoc to file scenario and stuck with the mapping in the following case. I think an UDF or JAVA mapping will do the bill. can some one help me in this regard please.
IDoc message type, IDoc basic type, IDoc extension
PAYEXT.PEXR2002.ZEXR2002.
<u><b>conditions:</b></u>
IF E1IDB02 BA-FIIKWAER = CNY
      then MID(E1EDKA1 BE-NAME1,12,11)
IF E1IDB02 BA-FIIKWAER <> CNY and LEN(E1EDKA1 BE-NAME1)<=35
     then MID(E1EDKA1 BE-STRAS,1,35)
IF E1IDB02 BA-FIIKWAER <> CNY and LEN(E1EDKA1 BE-NAME1)>35
     then MID(E1EDKA1 BE-NAME1,36,35)
This will be mapped to "Info Line 1" field in file.
Thanks,
Kiran

Hi Mr.Kiran,
here is the code
pass the following fields to Context UDF
1.E1IDB02-FIIKWAER
2.E1EDKA1-NAME1
3.E1EDKA1-STRAS
for(int k = 0;k<FIIKWAER.length;k++)
     if(FIIKWEAR[k].equalsIgnoreCase("CNY"))
        result.addValue(NAME1[k].substring(11,12));
     else if(!(FIIKWEAR[k].equalsIgnoreCase("CNY"))&&(NAME1[k].length() <= 35))
       result.addValue(STRAS[k].substring(1,35));
     else if(!(FIIKWEAR[k].equalsIgnoreCase("CNY"))&&(NAME1[k].length() > 35))
      result.addValue(NAME1[k].substring(35,36));

PAYMENT IDOC PEXR2002, Authorization, setup procedures.

Dear Members,
Can somebody throw some light on how to learn the following requirements:
1) Creation of Outgoing Payment Idoc in PEXR2002 format. (Also would like to know what are the different types of payment run)
2) How to setup or trigger the Authorization procedure, before the above created payment instruction is released?
3) How to setup the collection (bundling) of the above idocs into a single file (Multiple Idocs in a single file)?
Thanks in anticipation,
Best Regards
NG.

1. Coincidentally I am also working on the setup for F110 IDoc.
Basically I want the breif steps for set up of IDoc process for check payments.
2. Please also confirm whether message type is REMADV and IDoc type is PEXR2002 for check payments.
Kindly help me.
Thanks & regards,
Suraj

How to map idoc segment field E1IDB02-FIIKONTO with BSEG-ESRNR.

Hi,
I have searched for lot of threads in the forum , and also i tried myself but i am not able to map this fields segment with my logic, so please anyone kindly contribute in mapping idoc segment field with the logic given below:
idoc type :PAYEXT outbound idoc.
message type: PEXR2002
This is my logic: i need to populate the ISR number(BSEG-ESRNR ) in idoc segment field( E1IDB02-FIIKONTO)
DATA : str1 TYPE string,
      len1 TYPE i,
      len2 TYPE i,
      str2 TYPE string,
      str3 TYPE string.
str1 = '01-1234-4'. ---> BSEG-ESRNR "ISR Subscriber Number
REPLACE FIRST OCCURRENCE OF '-' IN str1 WITH '_'.
REPLACE ALL OCCURRENCES OF '-' IN str1 WITH space.
CONDENSE str1.
len1 = STRLEN( str1 ).
IF len1 LT '9'.
len2 = '9' - len1.
CASE len2.
   WHEN '1'.
     REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '00'.
   WHEN '2'.
     REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '000'.
   WHEN '3'.
     REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '0000'.
   WHEN '4'.
     REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '000000'.
   WHEN OTHERS.
ENDCASE.
ELSEIF len1 EQ '9'.
REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '0'.
ELSEIF len1 GT '9'.
REPLACE ALL OCCURRENCES OF '_' IN str1 WITH space.
CONDENSE str1.
ENDIF.
Thanks in Advance.

Resolved.

REMADV / PEXR2002 mapping

Similar Messages

Maybe you are looking for