IDOC PEXR2003 vs PEXR2002

How do i know which IDOC basic type i should be using for message type PAYEXT? What are the different basic types available for outbound payment document to be sent to the bank

Hi,
I never recommended PEXR2003. I simply mentioned that 2003 includes all segments of 2002 + newly added segments.
Now, it depends on business which it'd like to go for. We''ve implemented PEXR2002, which satisfies all our need.
Thanks,
Nirav

Similar Messages

F110S - debugging - Idoc basic type PEXR2002

Hi,
i'm trying to debug F110S and its not stopping in FEDI0003 routines. am i missing something.
i have to populate bank details in this Idoc (basic type pexr2002 and message type PAYEXT)
please let me know.
Thanks.
Edited by: vij k on Aug 5, 2009 9:51 PM

figured it out. Thanks.

Populating bank details in Idoc basic type PEXR2002 message type PAYEXT

Hi,
I need to populate the bank details in E1IDBO2 I2. however, this segment appears on the idoc if i use RVND free form payment and release it.
This is not happening if i use FB60. i couldn't see the E1IDBO2 I2 segment at all.
Is there any setting in config to make this segment appear on the Idoc.
Any thoughts on this.
Thanks.

figured it out. Thanks.

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

Idoc to file problem with DynamicConfiguration

HI SAP Guru's
I have a iDoc to File scenario and the output file requirement is bit tricky.
output file should be xx_Region_iDoc Number_YYYYMMDDHHMMSS
I been through couple of blogs but non of them mentioned about the iDoc all of them showed the about the FileName in FileAdapter.
I believe it is only possibly via Dynamic configuration.
I need to extract E1EDKA1/LAND1, DOCNUM from Source IDoc Structure and then concat it with Date and generate the output file name.
I cannot even get the iDoc Number i.e. DOCNUM via Dynamic Configuration.
I was trying this method but it didn't work.
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/IDoc","DOCNUM");
String ourSourceFileName = conf.get(key);
return ourSourceFileName;
Can somebody please let me know how to achieve this and how?

Hi Rodrigo,
I have done the UDF with 3 inputs and mapped it with header of Target side and now would like to know about the setting in File Adapter.
1. Could tell me what do I need to write in "File Name Scheme" , I am using *.xml , is it right?
2. I also check the Use Adapter Specific Message Attributes,
Fail if Adapter-Specific Message Attributes Missing
FileName
Could you please tell me is there anything else I need to do because I have been through couple of blogs and all of them mentioned about File but not about the IDoc.
DynamicConfigurationKey key = DynamicConfigurationKey.create(u201Chttp://sap.com/xi/XI/System/Fileu201D,u201CFileNameu201D);
Except you who mentioned this
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/IDoc",fileName);
I am bit confused about the FileName because there is no FileName in IDoc;
I found these information in IDoc Dynamic Configuration
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:DynamicConfiguration xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPOR">SAPDGE</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRN">DGE008</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRT">LS</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPOR">A000000012</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRN">CITIPHMX</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRT">B</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="MESTYP">PAYEXT</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="IDOCTYP">PEXR2002</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="CIMTYP">ZPEXR2002</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/Message/30" name="CALLER_CODEPAGE">4102</SAP:Record>
</SAP:DynamicConfiguration>
Please comment.

Configuring IDOC to file Scenario in PI 7

Hello All,
I am doing an IDOC to file scenario, all the configuration is done. When i trigger the outbound IDOC, I can see in SXMB_MONI the sender component, sender Namespace, sender interface and reciever component are coming up correctly as configured.
1. But the reciever namespace and Reciever Interface are having the same values as the sender namespace and sender interface interface respectively. I am sure they have to be as per the config in ID.
2. Also on further going into the error message
SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code
SAP:AdditionalText>No standard agreement found for , DEV400, ANZ, BC_RECV_PAYM_ORD, urn:sap-com:document:sap:idoc:messages, PAYEXT.PEXR2002</SAP:AdditionalText>
Can anyone please suggest , what is it that I am doing wrong.
---Prashanth

Hi,
Please delete the Receiver determination and try creating again. refresh cache.
Can you please have a look at the sap notes if of any use .. i think its a different case altogether , but pls have a look.
SAP Notes 1278244- https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1278244
SAP Note 1284103 -https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1284103
Regards,
Srinivas

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.

Danish FIK (FI card) outgoing payment by Idocs

Hello dear Sap FICO colleagues
Danish affiliate wants to use FIK payment for vendors, it is a local payment in DKK. The main point is that this kind of payment is based on a code as follow : +71< 000000000000000+00000000< . First part is for the vendor's identification and the second one for the invoice number.
The main problem is that we are using idocs (basic type PEXR2002- message type PAYEXT) to communicate with the bank and the bank is requiring to populate some fields ( as BELNR (used currently for invoice number) or FIIKONTO (used currently for vendor's bank details) with Card number or Creditor ID.
I don't want to change the content of these fields because they are already used for Vendor's bank transfert.
In that case how can I manage for a same Idoc segment several different values ?
Is there some function module or BTE which i can activate ?
I will be very thanksful for your answers, because i am totally blocked.

Hello SAP Gurus, any clues for me ???

Setup for F110 IDoc

Hi All,
I need to understand the basic steps required to generate PEXR2002 IDocs from the payment run (transaction F110)?
I'm quite confused about how to setup the bank partner and assocated EDI config to generate these IDocs and link them to the payment run program.
Thanks for you help.
- Suresh

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

Segment E1IDBW1 is missing for the inbound idoc type PAYEXT

Hello,
the above segment is missing in the inbound idoc - basic type pexr2002.
I have checked in TC-we30 and its available there.
but still the idoc is getting generated without this segment.
can someone suggest.
thanks
Arun

Hi All,
I have a similar query to that of Penny. We are able to get the standard IDOC to generate with segment E1IDBW1. It contains the standard fields INPWEEMP, INPWTXT1, INPWTXT2. However, we have a requirement to manipulate the standard contents of these fields. We wanted to use user exit EXIT_SAPLIEDP_002 to do this.
I have maintained user exit EXIT_SAPLIEDP_002 but when we enter this on creation of the IDOC the segment E1IDBW1 does not seem to be available in table EDIDD_TABLE for manipulation. Can you advise please if (1) you were able to get E1IDBW1 available to edit in exit EXIT_SAPLIEDP_002 and (2) were you able to manipulate the contents of INPWTXT1, INPWTXT2 etc?
We have done the following steps:
- BTE 2441 is available on our release
- house bank has been setup as an In House Cash Center which allows E1IDBW1 to be generated
- entry has been maintained in table FEDICUS with Message Type = PAYEXT, BasicType = PEXR2002, Extension = Blank, Seg Type = E1IDBW1
- code maintained in ZXF08U04
The system enters ZXF08U04 but E1IDBW1 is not available there for manipulation.
Can you advise what we might be missing please?
Thanks and regards
Mike

IDoc File Port Exit

Hi all,
I'm using a File Port to download an IDoc of type PEXR2002.
AFTER the IDoc is downloaded, I want the system to instantly run some custom code.
Is anyone familiar with an user/customer exit for this?
Does anyone know any exits for file ports? I know the exits for PEXR2002 but not sure if they are relevant.
Kevin

Does the file have to physically exist when you run the custom code? If it doesn't, and you want SAP to trigger some code, then you can write a function module to do what you need and hook it into the ports outbound file function code. The function called there is usually to name the file uniquely, such as EDI_PATH_CREATE_CLIENT_DOCNUM. However, you could write a function module that calls this, then executes your own code. If you want to take a chance, you could use that function module to raise a workflow event for a task with a one minute delay, then execute the code in a function module.
On the other hand, if you need the file to exist, I think that you need the operating system to inform you of the creation of the file, in a similar way to the XI file adapter. In that case, you could have an OS process trigger a remote RFC call into the R/3 system which executes the code that you need.
As we say in english: there's more than one way to skin a cat...
BR,
Tony.

IS-U and IDoc creation

Hello everybody,
I need that the IS-U payment run creates a PAYEXT or DIRDEB Idoc with BaseType PEXR2002 ( I need this for in-house cash).
Anybody here who knows how to do this?
Thx
Thorsten

Thersten,
I understand that after you send the IDoc info to SAP-Inhouse Cash, the entry/entries wud/cud be
DR: Subsidiary Bank
CR : Inhouse Cash Center
(OR) &
DR: Inhouse Cash Center
CR : House Bank
Another combination can be
DR: Subsidiary Bank
CR : Inhouse Cash Center
(OR) &
DR: Inhouse Cash Center
CR : Clearing Partner.
So while sending the IDocs to SAP Inhouse bank, you need to consider above entries & design the program accordingly.
But do remember that FYP1 entries usually wud be:
DR: Bank Clearing Account
CR: Contract Account
Below URL may be helpful to you
https://help.sap.com/saphelp_erp60_sp/helpdata/en/20/8ad8fa96494f16a8db9110234c855b/frameset.htm
Hope this helps
Rgds
Rajendra

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

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

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

IDOC PEXR2003 vs PEXR2002

Similar Messages

Maybe you are looking for