Duplicate IDOC created for basic type PEXR2002

Hi,
We are using PEXR2002 idoc for some document postings in FI. For a segment EIEDP02, when trying to write a BELNR field value which exceeds its size of CHAR 35. Its creating a duplicate segment with same key value. Because of this, the idoc not getting created and ends up in error.
Could you please anyone help me in this regard?
Thanks and Regards,
Vimala P

Hi,
In our process, the EIEDP02-BELNR value is actually filled with document text field value which is of length more than 35. What is happening right now is, if the length of document text having more than 35 characters and then with first 35 character of BELNR value one segment is created. And it again create one more segment EIEDP02 with BELNR value having the rest of the fields value(>35 characters). Thus creates duplicate segments which results in IDOC creation failure
Thanks and Regards,
Vimala P

Similar Messages

1 request Idocs created for message type MATMAS

Hi Experts
I have done necessary config.
I have attempted BD10 and BD11.
I have got message that "1 request Idocs created for message type MATMAS"
But iam unable to find the material in target system.
Please suggest what need to be done.
regards
ramSiva

Marias,
And in PI, after having changed the password (why not), have you unlock this user account ? in SU01 of PI, you have a lock button.
if you did it, and changed also the password, as explained, you have perhaps another (or several) program like a RFC destination which uses another password, and so after some exchanges... with a bad/old password, you have your message "too many...", and then the user is again locked...
If you change the password in PI, you should change it in all application which uses this user. I hope you have not the same user from ECC to PI, than from a third-party to PI...
that's why: the use of such technical users have to be referenced in a doc. By this way, if password has to modifiy, we know where we have to update it (mainly in different RFC destination).
Mickael
Edited by: Mickael Huchet on Dec 5, 2011 5:33 PM

IDOC Exit for Basic Type PORDCR101

I had extended the idoc type PORDCR101( Create Purchase Order ) and added the new segment under E1BPMEPOITEM .
Now i want to find the exit which will help me in populating the added segment fields when the IDOC is posted .
Any sort of help is appreciated .
Regards,
Praveen.

Hello,
The message PORDCR will use FM IDOC_INPUT_PORDCR and further processing is done using a BAPI: BAPI_PO_CREATE.
Enhancement SAPLMEWP deals with the Exits related to the BAPI.
Hope the above point helps you.
Best Regards, Murugesh AS

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.

Error :- No authorization for basic types (activity 01)

Hi Experts,
While trying something at the BW server i suddenly got the below error
I am getting the error when i am accessing the T-CODE RSA1.
Error :- You have no authorization for basic types (activity 01)
I checked the ids of my colleagues all are getting the same messages...
Regards,
RG

Hi,
1. Check in SU53 tcode
2. You are having RSECADMIN/PFCG tcode access?? If yes you can give authorisation for the same.
3. You dont have S_RS_ADMWB - authorisation
4. for your user id give this above authorisation
5. If you are unable to do the same, ask your basis team to give you the authorisation
refer this link- 1.http://help.sap.com/saphelp_nw70ehp1/helpdata/en/f3/291542e4b4df2ce10000000a1550b0/frameset.htm
2.http://help.sap.com/saphelp_nw70ehp1/helpdata/en/a4/1be541f321c717e10000000a155106/frameset.htm
Edited by: Asish Sahu on Apr 28, 2009 10:34 AM

Error :- No authorization for basic types

Hi Experts,
While trying something at the BW server i suddenly got the below error
I am getting the error when i am accessing the T-CODE RSA1.
Error :- You have no authorization for basic types (activity 01)
I checked the ids of my colleagues all are getting the same messages...
Regards,
RG

Hi,
analyze the missing authorization with transaction SU53 immediately when the error appeared.
Ask your system/authorization administrator to grant you the missing authorization.
Regards
Rainer

Accessing RSA1 issueYou have no authorization for basic types (activity 01)

We are experiencing the following issue with RSA1
While accessing this it comes back with error
You have no authorization for basic types (activity 01)
This was working before and no authorizations got changed. Appreciate your feedback.

Hi,
This is realted to authorizaion problem. please contact your basis team.
Assign points if it helps.
Cheers,
Malli.

Duplicate outbound Idoc created for outbound delivery

Hi Gurus,
We use decentralised whse system for goods movement.
For couple of outbound deliveries there are double idocs created (messge type SHP_OBDLV_SAVE_REPLICA).
I have no idea how the duplication taken plcae. Any body come accross this kind of issue .
Please help to reslove the issue .
Thanks in advance

Hi,
There is nothing in message control tab for outbound parameter(we20) and even there are multiple changes in delivery.
What we do is as soon as the delivery is created . Z trnx is executed which changes the dec whse status A(Relevent ) to B (distribution) simulteneously outbound Idoc is created and delivery details send to whse.
Normally there will be one outbound idoc per delivery , but in this case there are 2 (duplicate)

How to find IDOC Function Module for Basic Type:ORDERS05

Hi,
What is the Transaction Code to locate the Function Module linked to the IDOC Basic Type & IDOC Message Type?
Appreciate Your Help.
Thanks,
Kannan.

Hi Seshu,
Thanks for your reply. While creating a Custom IDOC, How do I link the IDOC Function Module and Basic Type. Appreciate Your Help.
Thanks,
Kannan.

IDOC reduction for MSG type MATMAS

HI all,
i have a requirement where clients need only some standard segments and some particulars staructure.We are using MATMAS as a message type and MATMAS05 as a basic type.Basically it leads us for IDOC reduction. Can someone pls help me out for getting this requirement.
Rgds,
Raghav
Edited by: raghav on Jun 9, 2009 12:28 PM

Hi,
Launch the BD53 transaction (IDoc Reduction Maintenance: Initial Screen). In the Reduced message type field, type the value ZVISTAPM_REDUCED, then press the Create button. In the popup window which appears, type in the Message type reference field the value MATMAS.
Validate.
In the next popup window, type a short description for the new reduced message type.
Validate.
In the following window, select the segments and the fields needed for the new reduced message type.
Save.
KR Jaideep,

Idoc processing - determine Basic Type in Program

Hi Forums,
I would like to determine the Basic type that is being processed by at the time of my Idoc creation.
the function module I am using is being called by shipping document as well as delivery documents.
I would like my code only to be executed when it is a basic type of DELVRY05

Hi,
1) Goto Tcode - we57:
Assign function module to IDoc type
Module: Function module
Basic type:
Message type:
Direction: 2 (inbound)
This will differentiate between Shipping and Delivery.
2) Creating Inbound process code - we42
For Outbound Process Code -- WE41.
For further plz refer following link.
https://wiki.sdn.sap.com/wiki/display/ABAP/ALE%2CIDOC
Thanks and Regards,
ShreeMohan

Logical Message for Basic Type SHIPMENT_CHANGE01

Hi,
I want to use the basic type SHIPMENT_CHANGE01 in order to update a shipment (status, date, hour, and specifics elements) but I can't find wich Logical Message I have to use.
Could you help me please ?
Thank you
Alex

Thank you Shiva.
And do you know which Logical Message I have to use please ?
There is the SHIPMENT_CREATEFROMDATA for shipment creation but for the modification, I can't find anyone. Maybe SHPMNT (Shipping outbound) ? or SHIPPL (Inbound planned shipments) ?
Thanks again.
Alex

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.

EDI820 currency and amount- blank in Payment advice.(Basic type PEXR2002)

Hi All,
We are in the process of implementing EDI 820 for customer payments.
When the IDOC is generated, a payment advice is created but it has blank values in amount & currency fields, due to which we get an error "Formatting error in the field BKPF-WAERS ; see next message"
I had maintained currency & amount values in segment E1IDKU5 through WE19, but I am not sure why the payment advice generated has blank values.
Can anyone please let me know what could be the reason.
Thanks in advance.
Krishna

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

Problem LSMW + IDOC method for message type : MATMAS

hi friends,
I am using LSMW + IDOC method Message : MATMAS , idoc type : MATMAS03 .Setting every thing are fine. Finally Material is not created with error "message have been issued number : <idoc number>".
data : material, industry type, material type, description, Basic unit of mesure.
Please help me.
Balaji.T.

Hi,
I have nothing found regarding your issue. But maybe a look at SAP note 638058 will give you a hint.
Regards,
Klaus

Duplicate IDOC created for basic type PEXR2002

Similar Messages

Maybe you are looking for