E1EDP02 segment question in PEXR2002 idoc

Hello,
In PAYEXT idoc type, for Vendor payments, E1EDP02 segment is populating qualifier '009-Invoice number'. Is there a possibility to have a different Qualifier? If so, is it possible though any substitution since I do not want any enhancements.
Thank You.

Hi,
for sending IDocs to XI no adapter is necessary. It should be enough to reload the metadata in idx2:
http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm
Regards
Patrick

Similar Messages

Flat File IDOC - ECC, segment defn x in IDoc type y CIM type do not exist

Hi,
I'm working on idoc flat file > sap scenario. Everything seems to be working up until the point where I get an error message:
EDISDEF: Port EDIPORT segment defn E2FINBU000 in IDoc type FIDCCP01 CIM type do not exist
I've loaded the meta data, and the file structure is fine. I believe the issue is related to PI not having the idoc I'm interested in listed in WE30. How do I reference the standard IDOC type FIDCCP01? Ideas I've had are around SWCV or transport from another system, the first I'm not sure which SWCV, the later seems a bit of a bodge and I dont like the idea.
Thanks
James.

Hmm.. some light for the situation. Seems that the segments imported are:
E1FINBU     E2FINBU     31I
E1FINBU     E2FINBU001     40A
E1FINBU     E2FINBU002     40B
E1FINBU     E2FINBU003     45A
E1FINBU     E2FINBU004     45B
E1FINBU     E2FINBU005     46A
E1FINBU     E2FINBU006     46C
Which indeed does not have E2FINBU000, which the IDOC is most definitely trying to pass. I can only guess that the middleware producting this IDOC is flawed, and that standard SAP ALE will accept this as E2FINBU (It works into another SAP system without XI).
Guess I've answered my own question, but feel free to offer light for points
Thanks,
James.

Port &1 segment defn &2 in IDoc type &3 CIM type &4 do not exist

Hello,
I've a question. We would send an standard IDOC from the 4.6C System to our SAP Xi 3.0. I customized the XI with TA IDX1 and IDX2. If we trigger the IDOC to XI I get the follow error message back:
Port SAPQ73 segment defn E2EDL20002 in IDoc type DELVRY03 CIM type &4 do not exist.
The IDOC Vers. is 4.6. In another system with IDOC Vers. 6.20 isn't a problem. So I think its a problem of the IDOC Version, or? So I checked the forum about this topic but I didn't find anything. So, I hope you can help me. Kind Regards Stephan

Hello,
I have exactly the same issue... We're currently upgrading our SAP system 4.7 to ECC6.0. We're also upgraded the system to an unicode system.
Before those change, the interface between SAP and Xi worked well. Since the upgrade, those idocs don't pass any more and get the same error message than Stephan.
I've checked the authorization of the RFC user and he has SAP_ALL and SAP_NEW. Partner profile, RFC connection, port and distribution model didn't changed.
Do someone have an idea why this can appear ?
Thanks in advance.

PEXR2002 IDoc

Hi Experts,
Does anyone have any experience getting the PEXR2002 IDoc to work?
Its based on the PAYEXT message type.
This IDoc is to be sent to the bank, containing pay data.
Here are my following questions:
- How do we connect to the banks system?
- One IDoc per employee? Per payroll run? How does it usually go?
- How do we know if the destination system has have accepted it?
- Does most of it involve the typical general setup of IDocs? E.g. port definition, partner profiles, etc...
- Roughly how much work are we talking about for a typical setup (standard PEXR2002) ? 1week ? 3 weeks?
Thanks!

Hey,
Did you got the answers to your questions? I am in the similar situation. See if you can share that may help me in this problem.
Thanks,
Gagan Chodhry

PEXR2002 IDOC Need to pass certain data

Hi Gurus,
I need to pass certain data in the field FIIKONTO in the segment E1IDB02 in the IDOC generation for payments. We are using PEXR2002 format and are on ECC 5.0.
Is there any standard way or need to use any user exit only?
Cheers,
MCA

Hi,
Try using user exit function module FM--EXIT_SAPLIEDP_902 (INCLUDE ZXF08U06).
Here you can call a particular segment name and can then pass on your data to the field of that segment.
Regards,
Gaurav

How to add an feild to a segment to an existing idoc sturucture?

how to add an feild to a segment to an existing idoc sturucture?
please help me out with the step step by process...
thnaks and regards,
anu

Hi
use the WE31 Tcode to edit the segment
see the following steps
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Regards
Anji

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

Implementing EXIT_SAPLIEDP_002 for PEXR2002 Idoc

Hi Experts,
I am implementing user exit EXIT_SAPLIEDP_002 for PEXR2002 Idoc and PAYEXT message type.
My requirement is to update E1IDKU2-BUSGEO filed based on comparison between E1IDB02 BB u2013 FIIBLAND and E1IDB02 BB u2013 FIIBLAND .
If E1IDB02 BB u2013 FIIBLAND) = E1IDB02 BA u2013 FIIBLAND, populate u2018DOu2019 in E1IDKU2-BUSGEO filed.
If E1IDB02 BB u2013 FIIBLAND <> E1IDB02 BA u2013 FIIBLAND), populate u2018INu2019 in E1IDKU2-BUSGEO filed.
Can please suggest me how to approach on this.
Thanks in advance.
Regards,
Ram

T-code CMOD
enter project = FFEDI001
click on enhancement Assignment radio button
Click on Display
Then click on the "components" button
Then click on EXIT_SAPLIEDP_002 button.
SAP will edit the function.
Include code on ZXF08U04.
Hope this helps,
Mirko.

Segment definition in an IDOC type

Hi,
What does Maximum number and Minimum number stand for in an segment definition within an IDOC type? I think there are two options.
1. the occurence number of the segment type in an IDOC type defintion
2. the occurence number of the segment data of a special IDOC
1 or 2. Please suggest ... It will better if there is any example for me to understand it. Thanks.
Regards

Option 2 is correct from my observation.

Populating a segment in the target idoc based on dif

Hi
We have E1MARCM, E1MBEWM and ZE1MARCM (constum segment) in the material IDOC and we map the idoc to similar idoc which has same sement in the target idoc material idoc.
ZE1MARCM segment is the custom segment and is the subsegment of E1MARCM. while populating the target idoc segment, we are taking the values from E1MBEWM segment and populting in ZE1MARCM, but the problem is as ZE1MARCM doesnt get populated unless E1MARCM gets populated in the source, So, we need to manually populate E1MARCM in the target message with some default valaues incase we dont have E1MARCM coming in the source. Just would like to know what is the effort in the XI side. Is it a good design to implement this in XI or should we change the ABAP in the ERP side to always populate the E1MARCM on the source idoc which is a standard idoc.

we need to manually populate E1MARCM in the target message with some default valaues incase we dont have E1MARCM coming in the source.
Use mapWithDefault std function or ifelse function in PI. It solves your issue.
Is it a good design to implement this in XI or should we change the ABAP in the ERP side to always populate the E1MARCM on the source idoc which is a standard idoc.
It anyways dont take much effort in doing so in XI. If you can do so in ABAP, even that would be fine.
Regards,
Swetha

ALE Configuration for PEXR2002 IDoc and PAYEXT message type sending to XI

Hi all,
I need ALE Configuration for PEXR2002(Basic Type) IDoc , it's message type PAYEXT.
I don't know ALE Configuration for sending data from SAP IDS to SAP XI.????
I need ALE Configuration doc/pdf??
Please give me some guidline for this..
Regards,
Umesh

Umesh,
I was wondering if you have had any luck creating the configuration for PEXR2002 Idoc, PAYEXT message types, and sending the result set to XI.
I need to perform the same task within our R3 environment using the FTP protocol in XI to send the file to the Bank to be processed.
Any help or direction would be great.
Thanks,
Dave

Question related to IDOCs

Hello,
I have a question related to IDOC processing.
Lets assume that I process the following IDOCs collectively in the transaction BD87: -
1) 100
2) 140
3) 150
Simultaneously, another user using the same user ID as myself, processes the following IDOCs: -
1) 110
2) 120
3) 130
Is it possible to determine which IDOCs were processed collectively together? I mean is there some sort of an IDOC attribute which would be the same for IDOCs 100, 140 and 150 and for IDOCs 110, 120 and 130?
I hope that my question is clear. Please try and answer it as quickly as possible.
Best regards,
Divyaman Singh Rawat

Simultaneously, another user using the same user ID
I dont think SAP has any such provision. May be you can track by UserID but in your case that too is same.

EDISDEF:Port sid segment defn Z2Q0015000 in idoc type... CIM

Hi Experts,
I am getting the error "EDISDEF:Port <sid> segment defn Z2Q0015000 in idoc type..YHRMD. CIM"
in sm58 of sender sap system. I thought it would be the metadata issue and tried to search the segment 'Z2Q0015000' but unable to find any thing in sender sap.
Even i have tried in idx2. in xi
Please help !!
Regards,
Suresh.

Hi Michal,
Many thanks for your input. The issue is coz the metadata in IDX2 is not updated. The sender system was trying to post the data from the segment which XI doesnt have.
I just tracked the segment from we60 based on the error message and checked the idoc structure in IDX2.Then imported the idoc into IDX2 from sender sap.
once again thanks a lot !!
Regards,
Suresh.

Question about inbound PEXR2002 IDOC

Hi,
How would you handle multiple deductions (2 different deductions with different reason codes) for the same invoice? What are the segments that are going to be used for this purpose?
Thanks,
Nile.

Hi ,
check this link...it gives more info
file to idoc scenario
sekhar

PEXR2002 IDOC inbound question

Hi,
How would you handle multiple deductions (2 different deductions with different reason codes) for the same invoice? What are the segments that are going to be used for this purpose?
Thanks,
Nile.

Hi Nile,
Did you resolve the multiple deduction issue, I am facing the same problem, please let me know if you have already resolved this one.

E1EDP02 segment question in PEXR2002 idoc

Similar Messages

Maybe you are looking for