An IDoc without a message type was passed to the ALE layer

I am fairly new to IDOC processing and I am getting the following message? Any ideas what I might be able to do to resolve this?
Many thanks
Dannyboy
P.S. Points rewarded for helpful answers!

Hi Dan,
Have you setup the partner profile (WE20) for your given message type?
Also for testing purposes, please use WE19 (IDoc test tool) to generate the IDoc.
Let me know if you need extra help.
Regards,
Ferry Lianto

Similar Messages

Inbound Idoc for own Message type

Dear All,
I have created a message type for outbound and sent data to the Java System.But when distributing in BD64 inbound parameters are not getting created.
For inbound idoc if i am creating a new message type,How i can get data from external server and commit it in database.
We have to write any program as we do for outbound?
Another issue outbound idoc is in waiting status i have to process it in BD87.How i can sent it immediately and in partner profile, distributing in module view BD64 i have given Transfer IDoc Immediately.
PLZ reply ASAP.
Thanks & Regards,
Arun.

Dear rhea,
I want to receive the IDOC data for message type WPUUMS from a java server. Currently i am working on sample values for segments
E1WPU01
E1WPU02
E1WPU03
E1WPU04
E1WPU05
E1WXX01
I am facing problems in passing the correct values .
Its throwing a error message status 51.(Application document not posted) IDoc not fully processed.
can you help me with some dummy data for all the fields in the above segments.
reply ASAP
regards
arun

IDOC question on Message type and Basic Type - Partner Profile

Hi all,
I am wonder if I can post any IDoc question in this right forum/module. If not please direct me to the right forum/module. I am a newbie in IDOC setup.
My question is about the setup of Partner Profile creation (WE20).
When creating a new partner, for example with partner type LI, I notice there is outbound parameter and inbound parameter.
Questions:
1 u2013 It makes sense to have only one message type record appear in EITHER one of these two tables. I notice that some partner in my system has message type record exist on both the inbound and outbound parameters table, why system allows? What is the business rational?
2 u2013 May I have a list of standard SAPu2019s Message Type object of its usage description, and its allowable Basic Type (ie. IDOC TYPE). Basically a website to describe their (i.e. Message type and its Basic Type) business usage.
Thanks.
tuff

Tuff,
Below are my thoughts,
There is a partner sing partner type LI. This partner in the WE20, has one record (i.e. with Message Type ORDERS) exist in the Outbound Parameter table. This partner also has 4 records (i.w. with Message Type DESADV, INVOIC, MBGMCR, and ORDRSP) exist in the Inbound Parameter table. So my question is what is the business rational behind this kind of setup. Because I am confuse when come to create a partner profile, whether I need to create a message type in Inbound Parameter table or Outbound Parameter table, or I need both.
OK, so looking at the above example, you have an orders message type(This is for creating an order) in the outbound, this means that you are sending out an IDOC(purchase order for ex) to this partner, so that this partner can create an SO in his system and fulfill your order.
Now you also, mention that you have other four Message types for the same partner on the inbound, now let us look at the above scenario, you have asked your partner to fulfill the order, i guess you would like to get a confirmation from him/her if the order was created or not in his/her system and how and when is he/she going to fulfill your order requirement. This he/she does by sending an response to your order - ORDRSP.
And when the partner is ready to ship your order to you, he/she sends out a Advance Shipping Notice - ASN via the IDOC of message type DESADV.
Finally and most importantly , he/she will send you the invoice - INVOIC for the order.
In general, you interact with your partner via Business Docs - Order, Delivery, ASN, Invoice etc, so whatever document come from your partner - ORDRSP, INVOIC etc will be on the inbound profile of the partner. Whatever docs that you send ORDERS, ORDCHG etc etc will be on the outbound profile of the partner.
2 - Bascially I would like a reference in any website that allow me to choose which message type is best use for my partner profile, so that I don't have to reinvent.
Well, there is no choice of choosing/best message type for a given requirement - So for sending an Invoice the message type is INVOIC, ORDERS - For order creation, ORDCHG for order change etc. However the IDOC type, is some thing that you can choose, for Ex: ORDERS01 - ORDERS05, these are the IDOC types that are available, so if you are interacting with a partner who are running an old version of SAP and their system has only upto ORDERS02 in their version of SAP then you would use ORDERS02.
Regards,
Chen

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

How to enable IDOC serialization at message type level

Hi,
I am trying to enable IDOC serialization at message type and i am unable to achieve the desired results.
SETTINGS DONE:
I have done the settings required under SALE trsanaction
ALE IMG (transaction SALE)
   Model and Implement Business Processes
      Configure Master Data Distribution
          Set-Up Data for Sending and Receiving Serialization
              Serialization by Message Type
I have done the settings in both the receiving system and the sending system.
PROBLEM:
I am trying to send the Material classification first and then followed by Material class and then try to send the material itself to the other system. Since the serialization is enabled in the system, i was expecting that there should not be any errors.
But since the material classification IDOC is posted first it throws an error saying the Material Class does not exists. Since the serialization is enabled in the system i was expecting that the system would ensure that it post the Matrial class first and then post the material classification. I mean it would post in the order in which i have defined in the serialization.
Settings at Partner Profile.
    - I have set the trigger in background for all the message types except the SERDAT message type which is set trigger immediately.
Any idea what i am missing? Any suggestions on what needs to be done to ensure that the idoc is posted in serialization?
Edited by: Workflow learner on Jun 4, 2008 1:21 PM

Hi,
Create a custom transaction for PO Print & make the necessary changes as per your requirement In the custom program which you attach to the custom transaction you can put a validation to display the price based on user ID or some other parameters.
Thanks & Regards,

Outbound delivery with Inbound IDOC DELVRY06 with Message type SHPCON

Hi Friends
I am trying to pack outbound delivery with Inbound IDOC DELVRY06 with Message type SHPCON.
But IDOC has error Specification of destination HU missing.
Could you please help us to resolve the issue to Pack the outbound delivery with the IDOC.
Thanks
SR

HI Ian Kehoe
Sorry for delay in reply
Thanks you very much
I solved that problem .
Could you please advice test data for IDOC DELVRY06 packing hierarchy (multi level packing) to pack SAP outbound delivery.
Thanks
Ravi

Idoc generation for message types

Hi All,
regarding IDOC generation....
how do we activate the message type so that every time the application data which is created or changed or deleted generates the idoc and send it to other system. If iam not using Chnage pointers technique then i would not be activating the message type in BD50. In such case ie if the message type is not present in BD50 list and if change pointers is not used to transfer that message type . How do we genrate the idoc for such message types.
Thanks
Avinash

Hi,
For ur scenario u need to go for change pointers method only.U have other options like distributing master data and transactional data..But i don't think anything otherthan change pointers is useful.
Regards,
Nagaraj

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

Error message: file was skipped because the old remote file could not be deleted.. Later it will up

Error message: file was skipped because the old remote file could not be deleted.. Later it will upload after i try a few more times. Not at my size quota for website (I have lots of room) , have toggled Passive FTP ...keeps happening. Is there a way to fix this? Thanks! I am using DW CS5 on Windows 7 platform. This does not happen when I upload otherwise on my computer - only when using DW.
It also only happens with the html files - it does not happen with my jpeg files

Do you have notes in your site? DW's local and remote site synching might be off. Try clearing your cache.
http://forums.adobe.com/thread/494811
Nancy O.

Purchase Order Outbound Idoc issue. Message Type ORDER

Hi Experts,
I am having issue with outbound IDoc generated from Purchase Order.(Message Type ORDER and Basic Type ORDERS05)
Issue is when i create PO idoc Segment E1EDP01 and field ACTION populates as 001 this works fine.
Now when made any changes to the purchase order.* PO trigers one more EDI - Idoc. but the ACTION field is stil as 002.*
Could any tell me how to fix this.
Cheers...Gopinath.

Hi,
Thank you.
I have found the issue and fixed.
Below three setting was missing same has been done in Partner Profile now ok.
Message type u2013 ORDCHG, Processing Code u2013 ME11 and Change flag On.
Cheers..Gopinath
Edited by: Gopinath A.R on Oct 8, 2009 3:14 PM

How to send IDOC with extended message type MATMAS

Hi Experts,
I am looking for a solution to send open PR & open PO related data for diffrent materials through as IDCO in XML file.
Scenario is i have to show a report in a 3rd party system for open PR & open PR that too will come after selection some materials. That means select a materials & it will show all the open PO & related data in a report.
The rough idea for the solution i got is I can save the data in XML file in the system. For this i have to send IDOC. but the problem is there is no message type for PR. IF i am not wrong i can extend the MATMAS05 for a segment that will have PR related info.
Now what to do with that how to send the IDOC do i need to create another report to send IDOC or i can send the extended one through BD10. I tried it but it shows error message "0 communication idoc sent" so I dont no y such error is coming i think i am not filling the extended idoc. But again my QUestion is how to do that.
Can i use BAPI also for such work, if then how it can be helpful.
If anyone have any other solution Please help me out of this.
Regards,
Nik

Hi Mahesh,
Thanks for your reply.
My requirement is bit different. i have to send Open PR data for diffrent materials. In a 3rd party application user will search for few materials which will generate a report that will show the PR related data for those material.
That means for few selected materials there will be few PR's which may be open, i have to show those in my report.
Eg: material A, B. are in PR 00001 & material B, C in PR 00002.
After selecting materials A to C report will show
Material                 PR No                   Item No                Quantity
A                           00001                    10                             1
B                           00001                     20                            3
B                           00002                     10                            3
C                           00002                      10                           1
Same thing i have to do for open PO & open Sales order also.
Can u please help me to provide the solution how can i proceed for it. U have given the Message type & a bapi how it will help in my issue?
I got a suggesion from someone that extend message type matmas for PR, PO, SD related data & send the idoc. but i am confused how to pass that much data ina single IDOC.
Regards,
Nik

IDOC: Process order: Message type LOIPRO

Hi
I would like to know here no other way to download LOIPRO idocs as soon as the process order or production order are created/changed.
Currently i'm using program rcclord and rccltran to create idocs. The problem I see here is that during every execution ALL orders, disregarding of the status (i.e. closed orders as well), will be exported.
G.
Message was edited by: Giovanni Baumann

Hi Baumann,
You can use the BADI WORKORDER_UPDATE
I am using this for releasing Process Orders. I hope this will help you..
*Appending the Selection Screen fields.
*Process Order
s_rspar-selname = c_selnam1.
s_rspar-kind    = c_kind.
s_rspar-sign    = c_sign.
s_rspar-option = c_option.
s_rspar-low     = im_ord_header-aufnr.
APPEND s_rspar TO t_rspar_tab.
*Material Number
s_rspar-selname = c_selnam2.
s_rspar-kind    = c_kind.
s_rspar-sign    = c_sign.
s_rspar-option = c_option.
s_rspar-low     = im_ord_header-matnr.
APPEND s_rspar TO t_rspar_tab.
*Planning plant
s_rspar-selname = c_selnam3.
s_rspar-kind    = c_kind.
s_rspar-sign    = c_sign.
s_rspar-option = c_option.
s_rspar-low     = im_ord_header-werks.
APPEND s_rspar TO t_rspar_tab.
*Order category
s_rspar-selname = c_selnam4.
s_rspar-kind    = c_kindp.
s_rspar-low     = im_ord_header-autyp.
APPEND s_rspar TO t_rspar_tab.
*MRP controller
s_rspar-selname = c_selnam5.
s_rspar-kind    = c_kind.
s_rspar-sign    = c_sign.
s_rspar-option = c_option.
s_rspar-low     = im_ord_header-dispo.
APPEND s_rspar TO t_rspar_tab.
*Logical System
SELECT SINGLE rcvprn INTO v_opt_sys FROM edp13 "#EC *
   WHERE rcvprt = c_rcvtype AND mestyp = c_messageid.
s_rspar-selname = c_selnam6.
s_rspar-kind    = c_kindp.
s_rspar-low     = v_opt_sys.
APPEND s_rspar TO t_rspar_tab.
*Message Type
s_rspar-selname = c_selnam7.
s_rspar-kind    = c_kindp.
s_rspar-low     = c_mesageid.
APPEND s_rspar TO t_rspar_tab.
*This statement will submit the programme RCCLORD using the table RSPARMS
*which holds the fields to be filled in the selection screen for RCCLORD and return
SUBMIT rcclord USING SELECTION-SCREEN 1000
                 WITH SELECTION-TABLE t_rspar_tab
                 AND RETURN.
Cheers
Prasad

IDoc transfer error - Message Type Conversion

Hi,
While trying to transfer an IDocs from a 46C system, i get the following STATUS message in transaction BD87
Message type RPM_TIME could not be converted
Message no. EA 694
Diagnosis
Conversion entry between long and short names missing.
System Response
IDoc cannot be processed without this entry.
Procedure
Create an appropriate entry for logical message RPM_TIME.
Could you anyone let me know the reason as to why it occurs.
Regards,
Roshith

The problem is the FM for that action is trying to use a material movement to make the transfer. You can't use standard material movements to transfer into QI once you have activated any of the materials inspection types.
What inspection lot is generated by your current action box? I'm guessing an 89. I can't remember.
Have an ABAP'er trace the FM and determine how it is doing the stock transfer. If it is using a 322 it won't work with QM active. You will have to have you ABAP'er modify it to use a 311 or 411 which will then use the 08 inspection type. I suggest you use a copy of 411 or 311 for this.
Craig

ALE - Status 52 Idocs for HRMD_A message type

HRMD_A Idocs in target system are not completely posted, turning into status '52'. Most of the times the infotype 1001 idoc with relations ship P->S arrives before the idoc which has the actual objects(P, S) causing 'Relationship imposible because the object does not exist". We use program RBDAPP01 for inbound processing of Idoc which should take care of Serialization based on the time stamp of idoc creation in source system.
Change pointors for Message type HRMD_A are processed using program RBDMIDOC in source system.
It is unlikely that relationship P->S is created without object P being created in the source system. So the change pointors should create the idocs in the same sequence. But it is not happening.
Any help on this appreciated.

Hi Santosh,
If you haven't found by now the .... here is the Solution:
First change the size of table T77S0 check out note 305688
Then process the IDOCS again - check out note 363187
Regards
Luis

To seperate PAYEXT outbound IDoc according to message type

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 .
I want to know whether Message code given for PAYEXT and how to link that with Payment Method?
Is it possible to add segement in control record and to map that to each payment method?
Your reply would highly help me to slove out the problem
Thanks
Auroar

Hi Auro,
You use use EDI_DC-SNDSAD field, currently this field is used no where.
If you not sure where to see double control record and click address info tab
you can use either field receiver or sender.
For testing use WE19 transaction and pass your paymethod to following field
and then inform to EDI Mapper that your sending paymethod in this field.
For them this field is very easy to grab.
Let me know if you any concern.
Thanks,
Narayan

An IDoc without a message type was passed to the ALE layer

Similar Messages

Maybe you are looking for