Structure of basic type PEXR2001 - PEXR2002

Hello,
I am sorry for my english.
I search informations about the structure of PEXR2001 and PEXR2002.
I have found links for others types IDoc like CREMAS02 : https://websmp109.sap-ag.de/~sapidb/011000358700002529571998/cremas02_d.htm
or MATMAS03 : https://websmp102.sap-ag.de/~sapidb/011000358700002529571998/matmas03_d.htm
I want know if there are a link for see the structure of PEXR2001 and PEXR2002.
I have already test : https://websmp109.sap-ag.de/~sapidb/011000358700002529571998/pexr2001_d.htm
but this don't work.
Thx,

Hi,
I up my post.
I have to make a mapping from PEXR2002 (PAYEXT) to SCT ( European format for credit transfer ).
I obtained a description of PEXR2002 with all segment that contain but without explications.
I search restrictions of this format (segment mandatory, field use or not), signification of segments and if it is possible to have a sample of PERX2002.
NB : I have not SAP software.
Thx,

Similar Messages

Structure of basic type

Hi Friends,
How i can know the Structure of basic type of the following idocs: DEBMAS05, CREMAS05, MATMAS05, ARTMAS and INVOIC02. Any documents or link would be more helpful.
Any help will be appreciated. Thank you all.

This you can find the IDOC Interfaces (Debmas, Cremas, etc) for Business Partner:
http://help.sap.com/saphelp_mdm300/helpdata/en/06/c5567cff4370448bc381ab39739199/frameset.htm

Reg. IDOC Segement E1IDB02 in IDOC basic type PEXR2001

Hi All,
This probelm is with the idoc segment definition release.
The IDOC segement defintion E2IDB02002 is not in release status.
Could you please let me know how to change the segment Status to Release.
Regards
Anil Kumar K

Hi Anil,
You can set and reset the release status in transaction WE30 (if I remember it right). You can switch (when at the SAP Menu tree) to the IDoc Menu by transaction WEDI. You will see the relevant transactions under the menu point "development".
Gunter

Fill IDOC segment, E1IDBW1. For PEXR2002 Basic Type

Hello Team.
We send the IDOC for the Basic Type PEXR2002, Message Type PAYEXT.
This IDOC doesn't fill the Segment E1IDBW1 (IDoc header - special instructions (INP) )
I'm review some notes(1164524) and said to fill this segment it's neccesarie config the IHC.
But doesn't have this functionality.
It's possible fill the segment E1IDBW1 in a user exit or any other enhacement at creation idoc moment?
My idea is used the FM
CALL FUNCTION 'GET_SEGMENT_POS_FOR_INSERT'
    EXPORTING
      I_BASIS_TYPE            = ch_edidc-idoctp
      I_EXT_TYPE              = ch_edidc-cimtyp
      I_SEGMENT_TYPE          = 'E1IDBW1'
    IMPORTING
      E_INDEX                 = li_tabix
    TABLES
      IT_EDIDD                = t_edidd
    EXCEPTIONS
      BASIS_TYPE_NOT_FOUND    = 1
      EXTENSION_NOT_FOUND     = 2
      EXTENSION_ERROR         = 3
      INVALID_IDOC_DEFINITION = 4
      IDOC_ERROR              = 5
      INVALID_SEGMENT_TYPE    = 6
      INVALID_START_INDEX     = 7
      NO_MORE_POSITION        = 8
      TOO_MANY_SEGMENTS       = 9
      OTHERS                  = 10.
To Fill 2 constants in this segment.
Do you have any other idea?
Thanks
Edited by: David Lezama Gonzalez on Sep 1, 2011 2:51 PM

Hi,
Basically the segment E1IDBW1 will always be filled via user exit.
If you work with the IHC (In-House-Cash) application you have to fill
the E1IDBW1 segment as described in note 626577.
If you don't work in an IHC environment the following conditions must
be fulfilled:
1. The payment program has to fill certain fields (e. g. REGUH-DTAWS,
REGUH-DTWS1 - REGUH-DTWS4).
2. If this is fulfilled the payment data (REGUH, REGUP tables) will
be filled. The instruction keys will be moved to IDOC segment
E1IDKU3.
3. In user exit EXIT_SAPLIEDP_002 you can take over the instruction
keys from segment E1IDKU3 into E1IDBW1.
You may also read note 496663, this note explains about user exit
EXIT_SAPLIEDP_002 to populate this field in the idoc.
Also, you can check the note:
580321 - RFFOEDI1: BTE process 00002441 (Change IDoc)
REgards,
Cristiano

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.

Reg : The functionality of WMMBID02 Basic type in SAP.

Hi All,
Can anyone give me the functionality of WMMBID02 Basic type in SAP. Mean, not the structure of the Idocs i am talking about. But to which Module of SAP is it related to and what kind of inventory data it carries? what the significance of this data. which table get updated when this idocs gets posted successfully.
And also that, From table /GLB/RGTTPLANHED, we can get the trip status. So wat exactly this trip status indicates?... can anyone explain this in detail?

The message typer for this is WMMBXY and its used for Goods movement between storage location. This would internally calls MB01 transaction and related to MM module.

How to populate custom fields in SAP standard Basic type DELFOR01(E1EDK09)

I've a requirement to include and populate 2 custom fields in SAP standard basic type DELFOR01 and Segment E1EDK09 (it is at hierarchy level 1 ) .
The requirement looks very simple but for this, as per my knowledge, I have to create a new Basic type with the copy of segment E1EDK09 and attach it to outbound process code and write my own function module to populate the segments.
It seems ok but the there are some existing codes in the user-exits for the SAP standard function module.These codes will not get triggered.(Or I've copy the user-exits code in my FM)
Can we do it any other way to handle this kind of situation?
Thanks in advance for your suggestions and help.

Hi Phani,
You have done it correctly. ECC additional data to be moved to EWM, 1. you need to enhance the CIF for master data/ bapi to populate the data in the custom field in EWM. 2. Make your your are not enhancing only one structure. You need to do it in the CI includes so that the field is available in all the related tables/structures.
3. The BAPI/FM which updated these tables will take care automatically to update the custom field data if the field is correctly added in all the tables.
4. If the custom fields are added correctly and still the data is not getting saved , then need to check the mapping of the custom field and bepi extension.
Let me know if this helps.

Unable to extend the basic type "SALESORDER_CREATEFROMDAT202"

HI
when iam trying to extend the IDOC basic type "SALESORDER_CREATEFROMDAT202" iam getting an error message "Action is not possiable for generated IDOC types"
To my understanding SALESORDER_CREATEFROMDAT202 is a bapi.So, I guess we can not extend these type of IDOC directly.
Can any one can help me how to copy the BAPI interface and extend it....
or any other solution for this......
can any one can help me reg this.....

I will answer my question!
This is the proble of version we are useing!
the extenction is possiable in sap 4.6 version.
but it is not possiable in ecc6.
So follow the steps i have done
created a new basic type "ZSALESORDER_CREATEFROMDAT202"
where icopy the basic type "SALESORDER_CREATEFROMDAT202" to it
Then i extened the IDOC "ZSALESORDER_CREATEFROMDAT202"
and added the new segments.
FInally while assiging the basic type to extended IDOC given basic type as "SALESORDER_CREATEFROMDAT202"
And assigned to the message type "SALESORDER_CREATEFROMDAT2" to it
then we can use this Structure with
Message type: SALESORDER_CREATEFROMDAT2
Basic type: SALESORDER_CREATEFROMDAT202
Extended:SALESORDER_CREATEFROMDAT202EX
for data picking u can code in the followin function modules:
Function Module for Outbound ALE
ALE_SALESORDER_CREATEFROMDAT2
Function Module for Inbound ALE
IDOC_INPUT_SALESORDER_CREATEFR
There is another method also for this:
create a bapi fm with all the requirements and go to swo1 tc create an object with method as BAPI FM created.then go to TC bdbg and create a bapi ale interface.this will automatically generates the inbound and outbound FM's .Then the idoc will be generated with the added segments...

EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

Hi,
I'm trying to various infotype 2001,2002,2006 ecc to another SAP system via ALE and since they are not part of message type "HRMD_A" I have created the extension ZHRMD_A06. I've already created the new segments(we31) and put these segments (with names Z1P2001, Z1P2002 ecc ecc) into the extension(we30). And I've assigned the extension to the message and basic type (we82).
The new segment are processed correctly in the idoc creation via transaction PFAL, but via transaction BD21 i meet the abend message : B1 070 - Internal Error : program....command... for argument Z1P2001 (for example)
In other words, BD21 do not process the custom segment but the PFAL yes...how it is possible?
I've activate the change pointer in every customizing table intersting.
Many thanks in advance for any reply
Achille

unfortunately, the standard do not provide the infotypes for the HR-TM (Time Management), that
are between the structures i must send in the other system sap.
Ok, I have never delt with Time data in HRMD_A. Probably this is the case then
Ok,now i've checked the filter in BD64 and the tables BDCP2, CDHDR and CDPOS but it seems
all correct!!
By checking Filters I mean that confirm if you have added Time Infotypes there (just
making sure). If data is appearing in BDCP2 that means there is no problem in Change
pointer creation, Just ruling out possibility.
Try with an user exit it's a good idea, but why in the PFAL the idoc (with the custom segments)
is created without problems and in the BD21 no??? This is very strange
1) Well BD21 uses the Function module (TBDME for HRMD_A) which read change pointers and
create IDOCs. So now if you have extended Segment you have to add your population code
here somewhere.
2) PFAL is Push program, my assimption here is you have wriiten some piece of code to
populate Additinal segments data here? Otherwise IDOC will not be populated
automatically.
Let me know what you think.

Add IT0006 custom fields for segment definition E1P0006 basic type HRMD_A06

Hello! I am am trying to determine how to bring in our custom fields from IT0006 into our IDOC's for message type HRMD_A basic type HRMD_A06 without performing a custom SAP modification. I was able to create a new segement definition called Z1P0006 and replace the SAP standard E1P0006 IDOC segment defintion in table T777D for infotyp 0006 to Z1P0006. However, I receive a message that I must not maintain this IDOC segment manually and instead you must maintain infotypes and their individual elements by using the transactions for processing infotypes: PPCI or PM01 (Infotype copy transaction for personnel administration).
Does anyone know of a way to bring in the new custom infotype fields from i.e. reimport the table structure for IT0006 into the segment definition without a custom SAP modificaiton? I would really appreciate any help on this topic!
Thanks!
Holly

unfortunately, the standard do not provide the infotypes for the HR-TM (Time Management), that
are between the structures i must send in the other system sap.
Ok, I have never delt with Time data in HRMD_A. Probably this is the case then
Ok,now i've checked the filter in BD64 and the tables BDCP2, CDHDR and CDPOS but it seems
all correct!!
By checking Filters I mean that confirm if you have added Time Infotypes there (just
making sure). If data is appearing in BDCP2 that means there is no problem in Change
pointer creation, Just ruling out possibility.
Try with an user exit it's a good idea, but why in the PFAL the idoc (with the custom segments)
is created without problems and in the BD21 no??? This is very strange
1) Well BD21 uses the Function module (TBDME for HRMD_A) which read change pointers and
create IDOCs. So now if you have extended Segment you have to add your population code
here somewhere.
2) PFAL is Push program, my assimption here is you have wriiten some piece of code to
populate Additinal segments data here? Otherwise IDOC will not be populated
automatically.
Let me know what you think.

Idoc basic type PEXR2003

Hi all,
can any one take me the structure of Idoc Basic type PEXR2003.
WE60 ==> Basic Type checked ==> enter PEXR2003 ==> F9 key
Thanks in advance
Ragerds
Mercuryx

Up,
No ideas??????

Nhi guru's cross apps what is basic type,idoc type , message type

nhi guru's cross apps what is basic type,idoc type , message type plz help me i am larning how to work on idocs using ale explain me like realtime environment

Hi,
Hi,
i got this data from sdn .plz go thru might be helpful
IDOC is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
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
For creating a IDOC u need to Create a segment type in WE31.The internal table in which we store the data to be passed to the IDOc thos fielda are defined in fieldname and data element.Save and release the segment.
Create IDOC type in WE30. Give min and max types. Mark it as mandatory.
Create Message type in WE81.Assign it to a change request and save it.
Link this message type with IDOC type in WE82.
Then start your coding and pass the details of Data and control records.
Just have a look at these links:
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
Creation of IDOC:
idoc creation
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=creation%20of%20idoc&cat=sdn_all&start=11
ALE/ IDOChttp://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
i think this will helps u
<b>reward is usefull</b>

BASIC TYPE VS MESSAGE TYPE

Hi all,
Can i know wats the difference between Basic type and Message type??
wat s the use of having both this types????

hi
Message Type:
A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterises the data sent across systems and relates to the structure of the data called an IDOC type.
Diff. with IDOC type
An IDoc type specifies the structure of the data.
A message type specifies the meaning of the data
Diff. b/w IDOC type and IDOC
An IDoc type is the definition of a specific data structure.
An IDoc is an actual instance of data based on an IDoc type. Therefore, there can be many IDocs created from a single IDoc type.
Every idoc type will have Message Type.
It mean Idoc will be recognised By message type.
For ex : MATMAS03 is idoc type, and its message type MATAMS.
There are different message type for every master data. suppose for vendor master CREMAS is the message type, for customer mast DEBMAS like these there many message type for other type of master data.
To recognise the particular idoc, we use message types.
We82 is the TCode where IDoC type is attached to Mesage tYpe.
Refer to this related thread
difference between message type and idoc type
Check 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://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Regards
Anji

Data Services IDOC Errors when working with a newl Basic Type

Hello,
Just wondering if anyone else has encountered an issue similar to the one I am dealing with. We are trying to create business partners in SAP CRM from Data Services via IDOC. We are not using the standard IDOC, but instead we are using a new IDOC type.
This IDOC type is generated by SAP CRM automatically through a transaction BDFG. This transaction creates a new basic type for an standard IDOC with the additional fields that we have added through the easy enhancement workbench (EEWB).
The issue that we are having is that when we import the IDOC type into data services and we look at the schema many fields and sub-structures of the IDOC are duplicated. This means that we receive hundreds of errors when we try to validate our data flow. I can delete the duplicated sub structures in my query transformation but then the query transformation and the output schema and the idoc input schema are no longer identical.
I have searched all over oss and different web forums for a solution but no one else it seems has even encountered this error. If anyone else has had a similar issue and can offer help it would be greatly appreciated.
Bill

Issue is resolved.
After importing the meta data for the IDOC into data services I then proceeded to edit out all of the duplicate structures and fields from the IDOC.
After making the IDOC structure in data services identical to the structure of the IDOC in SAP I then proceeded to test this IDOC and it executed successfully.

Extending basic type SDPIID01

Hi,
I have to extend basic type SDPIID01 and add custom segments, After adding those segments I need to update records in those custom fields that would get stored in the databse table using Idoc.Pls suggest the complete steps and the any enhancement or exits that I need to implement to update the values in the database.Also pls suggest the logic that needs to be written inside that enhancement, exit or BADI.
Thanks in advance
Anand

Hi go to we30
Give one zidoc type name and create with radio button extension.
Choose create newlinked basic type , give ur basic type as SDPIID01
Then enter description and say ok.
and save .
Now Clk on the segment under which u want to add ur zsegment wether u want to add on hraedr level or item level.
and click on craete .
Enter a segment name , minimum1 maximum u can gv as per u like 10 , 99 etc.and ok.
It will take u to the segment structure , where u have to add the zfields.
For detail u can go through some documents or helps.
Regards

Structure of basic type PEXR2001 - PEXR2002

Similar Messages

Maybe you are looking for