IDOC Type PEXR2002: Txn F110

Hi Idoc Gurus,
I have to trigger the IDOC PEXR2002 type for payment run transaction F110.
I know there is this program RFFOEDI1 which does this job.
My questions are :
1) Do I have to create a Outbound Processing type ? Or it is not required as the program already does the job ?
2) Are all relevant data populated by that program ?
3) If I have to populate the Z-extensions of the IDOC type PEXR2002, then which is the user-exit I should use ?
Any hints will be greatly appreciated.
Regards,
Sandip.

Check the links -
https://forums.sdn.sap.com/click.jspa?searchID=2815420&messageID=3492865
Outbound PEXR2002
Regards,
Amit

Similar Messages

Include segment in Control record of idoc type PEXR2002 and PAYEXT

Gurus
This is business scenario. We are using four different flavours of payment methods. when exectuing F110 for each payment method,Program RFFOEDI1 generates IDOC. This IDOC are send to EDI team who then sends that as EDI820 to bank.
The payment method used are populated in Detail record field of IDOC . But EDI team wants that to be in Control record of IDOC .
We are using PEXR2002 and message type is PAYEXT . this is an outbound IDOC .
Is it possible to add segement in control record for each payment method?.
Thanks for your time and consideration
Auroar

It may depend on how the IDoc is created.
From a file.
Sent via a Remote Call.
You would then need to code it for this Message type only.
I would take a copy of the standard Function and change that. You would have greater control then.
Why is the partner number wrong anyway. Can you not just create another partner profile(s).
Message was edited by:
Martin Shinks

Implementation of IDOC types FINSTA01 and PEXR2002

Hi All,
I want to implement the 2 IDOC types PEXR2002 and FINSTA01 using EDI.The requirement is like I have to generate both the inbound and outbound processing for both the IDOC types using EDI.
I have the following queries :
1)What are the basic fields that are required for both the inbound and outbound processing(like file format)
2)How the inbound and outbound processing will be triggered like how can I send the file from SAP to EDI or how can I get the file from EDI to SAP and how to uplaod the record into SAP is there any SAP standard transactions or any standard reports or do I have to configure in the SPRO etc.
3)What are the settings that I have to configure?
Please help me out and your help will be appreciated.
Thanks and Regards,
Ramesh.

Hello Ramesh,
The answers to your questions are a few chapters in some books, meaning its quite large.
But in short.
1. the minimum fields are what is required by that particular transaction in SAP for inbound and for outbound you gotta check with the receiving party what they need.
example , if you are posting a PO in SAP, then what are the mandatory fields, thats the minimum.
With every idoc , incoming, there are a few ways to post, most common is via function modules.
Lets say you know a partner which will communicate via EDI, you have to maintain a partner profile in WE20.
There you define the incoming and outgoing messages.
Every message has, idoc type.
Transactions WE42 and WE43 are where you define a process code for attaching the message type/idoc type to a Funtion module.
Also there is config for setting up output types, see transaction NACE.
This is a process with lots of parameters.
You would be better off getting a book which explains it all in a proper order.

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.

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.

IDoc type could not be determined for the IDoc in F110

Dear All,
The below mentioned error is encountered by us in F110.We have check all the setiing and not able to find the solution for this error.
Now our heads has gone for a toss....can anyone kindly suggest what and where we have missed out.
The system is not creating the IDOC file.....
IDoc type could not be determined for the IDoc
Message no. B1090
Diagnosis
The IDoc passed to the ALE layer could not be processed. The specifications passed in the control record were not correct.
The basic IDoc type (field EDIDC-IDOCTP on the outbound side or EDI_DC-IDOCTYP on the inbound side)has not been specified for this IDoc.
The attempt to read the basic IDoc type from table EDIDO also failed. No table entry was found for IDoc type from field DOCTYP.
Procedure
Possible error sources:
- The calling program did not provide values for the fields specified above correctly. Make a note of the transaction in which this error occurred and consult your ALE administrator.
- The IDoc type is not known in your system and must be maintained.
Kindly do the needful.
Regards

If you want to create IDocs from the proposal run, outbound parameters (we20) with the 'Test' flag are required in addition.
see OSS note 504230 : Message EUPEXR forms the logical unit around the individual payment messages (PAYEXT IDocs). The E1IDRD1 segments contain the IDoc numbers of the payment messages in field DOCNUM. Segment E1IDRS1 contains check sums (total of all amounts, account numbers, bank numbers, number of payment messages). This information is provided for the EDI subsystem. Set up EUPEXR In Transaction WE20 for the partner profile for the house bank, create the outbound parameters for message type EUPEXR with IDoc type IDCREF01. If you want to create IDocs from the proposal run, outbound parameters with the 'Test' flag are required in addition.

IDoc type could not be determined for the IDoc

I am trying to Post the payment run through the transaction F110.
In the payment run log i get the following message:
"IDoc type could not be determined for the IDoc"
But in fact the IDoc is generated and it is displayed in We05.
I have configured the Message type PAYEXT-PEXR2002 and EUPEXR-IDCREF01 both for the partner.
Has anybody Idea about why this error is coming and how i can resolve this?
This is important because in Payment run log, they need to know the IDoc number generated for that run, else it may become difficult for user to identify which IDoc was created for a particular payment run.
Would appreciate if anyone can please help on the same.
Thanks & Regards,
Narayanan

Hi,
If you are paying the payment through F110, if the payment exceeds the limit what you are spefied in available amounts in FI12 screen. First Please check this screen.
still if you are having any problem
Check in the below path:
IMG- Financial Accounting (New) - Accounts Receivable and Accounts Payable - Business Transactions - Release for Payment - 1. Create Workflow Variant for Release for Payment
2. Assign Release Approval Procedure for Release for Payment
3. Define Users with Authorization to Payment Release
Thanks
Chandra

IDOC Types and their equivalent messages in EDIFACT and ANSI X12

Hi all, since I only have a list of messages in EDIFACT and ANSI X12 for release 4.6 B, I need to update the list from 6.0 version, but I don't have online support system to get it (OSS), it's note 104606 in OSS.
Can somebody give me a link to the full new updated list? Will surely give points with your helpful answers
Regards,

Hi,
Please check these perhaps they may help.
Mapping ANSI X12 to SAP Message Type and IDoc Type:
204 Motor carrier shipment information
The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
214 Transportation carrier shipment status message
The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
304 Shipping instructions
The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
810 Invoice or billing document (also 880), EDI - Inbound INVOIC posting configuration
The logical message is INVOIC, the IDoc type INVOIC01.
812 Credit and debit advice
The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
820 Payment order and credit advice
For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
823 Lockbox
The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
830 Delivery schedule (LAB)
The logical message is DELINS (from the EDI standard ODETTE) or DELFOR, the IDoc type is DELFOR01.
832 Price catalog (also 879, 888, 889)
The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
834 Benefit enrollment and maintenance
The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
840 Request
The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
843 Quotation
The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04. Outbound processing is supported.
850 Purchase order or order (also 875)
The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
852 Stock and sale data
The logical message is PROACT, the IDoc type PROACT01.
855 Ordering or order response (also 865)
The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
856 Transport and shipping notification (ASN - Advanced Ship Notification)
For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
For delivery in the SAP application, the logical message is DESADV, the IDoc types are DESADV01 (expires) or DELVRY01 and DELVRY02.
860 Ordering or order modification (also 876)
The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
861 Credit advice (ERS - Evaluated Receipt Settlement)
The logical message is GSVERF, the IDoc type GSVERF01.
862 delivery schedule (FAB)
The logical message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDoc type is DELFOR01.
864 Text message
The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
940 Shipping order and stock order
The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
945 Shipping confirmation and stock confirmation
The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
997 Functional Acknowledgment
This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
"22" Shipping OK, acknowledgment has yet to come
"16" Functional Acknowledgment positive
"17" Functional Acknowledgment negative
The status values "14" and "15" are available for the Interchange Acknowledgment accordingly.
Regards,
Ferry Lianto

Message types and idoc types

hi,
     i need the list of message types and idoc types for edi.
      can any one of u pls send it.

Hi,
Check the OSS notes 104606.
The following list maps the logical messages and IDoc types to the corresponding ANSI X12 transaction sets.That is, the logical message can be copied to the transaction sets named.
204 Motor carrier shipment information
           The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
214 Transportation carrier shipment status message
           The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
304 Shipping instructions
           The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
810 Invoice or billing document (also 880)
           The logical message is INVOIC, the IDoc type INVOIC01.
812 Credit and debit advice
           The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
820 Payment order and credit advice
           For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
           For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
823 Lockbox
           The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
830 Delivery schedule (LAB)
           The logic message is DELINS (from the EDI standard ODETTE) or DELFOR the IDOC type DELFOR01.
832 Price catalog (also 879, 888, 889)
           The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
834 Benefit enrollment and maintenance
           The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
840 Request
           The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
843 Quotation
           The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04.Outbound processing is supported.
850 Purchase order or order (also 875)
           The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
852 Stock and sale data
           The logical message is PROACT, the IDoc type PROACT01.
855 Order confirmation (also 865)
           The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
856 Transport and shipping notification (ASN - Advanced Ship Notification)
           For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
           For the delivery in the SAP application, the logic message is DESADV, the IDoc types DESADV01 (to be discontinued), DELVRY01 and DELVRY02.
860 Ordering modification (also 876)
           The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
861 Credit advice (ERS - Evaluated Receipt Settlement)
           The logical message is GSVERF, the IDoc type GSVERF01.
862 Delivery schedule (FAB)
           The logic message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDOC type DELFOR01.
864 Text message
           The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
940 Shipping order and stock order
           The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
945 Shipping confirmation and stock confirmation
           The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
997 Functional acknowledgment
           This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
           "22" Shipping OK, acknowledgment has yet to come
           "16" Functional acknowledgment positive
           "17" Functional acknowledgment negative
           The status values "14" and "15" are available for the Interchange Acknowledgment accordingly. Source code corrections
Cheers
VJ

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 types in SAP ECC

Hi Gurus,
1) 3rd party->PI->SAPECC
We have a requirement that the tenant refunds coming from 3rd party system should be sent to SAP ECC system.
To send this messgae to SAP ECC, is there any separate idoc format for this tenant refunds.
Should I use any FICO or any other standard module to post these files to SAP ECC.
2)SAPECC->PI->3rd party
Also is there any IDOC type for the direct debit details and customer payments or should i run the F110 transaction to execute the customer payments and to send the paymnet files to PI.
Coould you please advise.
Thanks,
Jay.

If you have fair understanding about ECC then you can easily identify which IDoc to use or any extension required for existing IDoc.
otherwise better to talk with ABAP/Functional team they will help you.

IDOC type to send OPEN ITEMS per INVOICE to external system?

Dear EDI Experts,
we want to send OPEN ITEMS of a customer per document via EDI to an XML file.
We checked on idoc type CRESTA01 but this idoc type provides "only" the total OPEN ITEMS of a customer but NOT e.g the invoice document numbers.
Is there any way to generate an IDOC or XML file with the invoice numbers and its OPEN ITEM amounts?
We want to transfer that data to an HH device in order to show customer which invoices yet to be paid.
Any idea?
Many, many thanks
Regards
JW

Hello,
many thanks for the quick answer to my question.
We want ONE credit idoc per one customer showing all OPEN ITEMS with the document number.
That info is sent to the Handheld in order to provide customer exact info which invoice he has not paid yet.
We do not need ONE idoc per ONE document.
But it seems no standard idoc provides such info and we have to call a FM to provide that info to a Z-Segement of CRESTA01. Is that correct?
Port definition XML in we21 for idoc type is understood.
Thanks a lot
Regards
JW

PO and SO IDoc Type

Hi,
I understand that the IDoc type ORDERS05 can be used for Sales Order as well as Purchase Order. My requirement is to receive Order IDoc and create the sales order and send the PO details to a partner. Please let me know whether I can use the IDoc ORDERS05 for both these cases.
Also I found that IDoc type PORDCR04 is available for PO. Can we use this IDoc type for sending Purchase order details.
Thanks
N

Hello Nanditha,
Yes you can do that.
Also go to WE60 and put in PORDCR04 and downloadd to your PC if needed.
Then search if all the fields you need are in that Idoc type.
There are no rules as to which Idoc type you have to use, but you should try your best to stick to SAP recommended one's.
Hope this helps.

How can I design a BPM with mulitiple IDOC types as sender

Hi Experts,
I am using PI 7.1
I have a senario that I have to design a BPM in such a way that I will get different IDOC types as sender while the receive step has to trigger the the respective IDOC types at run time.
For example: when matmas is the IDOC the BPM instance have to trigger only the respective Abstract interface at runtime.
In my senario I have 5 IDOC TYPES which should pick the related one using a single Abstract Interface in the same design( one BPM ).
Is this possible. Please suggest me how can I do this if possible.
Regards
Shankar.

Hi,
you could work with multiple receive steps that triggering the process.
Similar to the example pattern in SAP Basis BpmPatternSerializeMultipleTrigger
http://help.sap.com/saphelp_nw04/helpdata/en/77/0737133012b24b9d0a12c6df2b1054/frameset.htm
In the fork step you could set the number of required branches to 1 that means only one receiving IDoc is required to leave the fork step.
Regards
Patrick

Error while creating an outbound idoc using idoc type delvry02

hi,
i getting the following error while creating an outbound idoc(outbound shipping notification) using message type " DESADV" and IDOC TYPE " DELVRY02"
ERROR:
" SPECIFY EITHER ADDRESS NO OR ADDRESS HANDLE"
MESSAGE NO: AM053
Help would be appreciated.
regards
leo

The message is kind of self-explanatory. It seems that some address (delivery address ?) is required but is missing from the IDoc. If it's a syntax error, then the segment with error will appear in red in WE05 transaction.
It is also possible that you have filled some field that you should have left blank and now SAP is trying to find an address based on that field.
Check your IDoc contents. It's really hard to tell from the distance since the requirements and configuration could be very different in different systems. Sometimes the OSS note search by message ID and number is also helpful.

IDOC Type PEXR2002: Txn F110

Similar Messages

Maybe you are looking for