Inbound IDOC error :51 Passed with out Message Type to ALE Layer

Hi,
I am struct wtih the inbound IDOC scenario ..XI able to send IDOC but at ECC side it is in 51 red status and the error message is
"IDOC passed without Message type to ALE Layer"
Do I need to pass these segment values in Message Mapping? I didnt mapped any MESTYP,SNDPOR,SNDPRT and so on.. disabled these fields...
Could any one light on this issue?
Thanks
Rajeev

>
rajeev raj wrote:
> Hi,
>
> I am passing values in MM as below:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <ZPORDCR01>
> <IDOC BEGIN="Constant">
> <EDI_DC40 SEMENT="Constant">
> <TABNAM>Constant</TABNAM>
> <DIRECT>Constant</DIRECT>
> <IDOCTYP>ZOrders</IDOCTYP>
> <CIMTYP>Constant</CIMTYP>
> <MESTYP>Z_Orders</MESTYP>
> <SNDPOR>B0009</SNDPOR>
> <SNDPRT>LS</SNDPRT>
> <SNDPFC>LS</SNDPFC>
> <SNDPRN>PD_100</SNDPRN>
> <RCVPOR>DEV</RCVPOR>
> <RCVPRT>LS</RCVPRT>
> <RCVPRN>Dev10</RCVPRN>
> <REFINT>GB</REFINT>
> <REFGRP>MTI</REFGRP>
> <REFMES></REFMES>
> <ARCKEY>20090909</ARCKEY>
> </EDI_DC40>
> <E1PORDCR SEGMENT="Constant">
>
> I am forwarding these values in MM... IDOC is successfully reaching in ECC but with 51 error in red... Logical system, post and message types are avaliable in Control record of the IDOC which received wiht errors in ECC.
>
> Thnaks
> Rajeev
Fill the TABNAME as EDI_DC40 and Direct as 2 (represents the inbound direction) and resend the idoc and check
Rajesh

Similar Messages

File to file with out message mapping and using variable substitution

Hi,
Can any one send me a scenario where we can have file to file scenario with out message mapping and where i can use variable substitution.
As of now i am using integrate configurations where i cant use variable substitution as the message does not reflect in integration engine. I need to populate time stamp between <filename><timestamp>.txt.pgp
I am as of now using configuration scenario.
The time stamp always writes before the last file extension.
Let me know your thoughts?
Thanks,
Chandra.

Hi Chandra,
u can use the Variable substitution even without IR contents also(Mapping....).
in the receiver communication channel just specify the path u want to access for a value...
eg: filename payload:mt_name,1,records,1,name,1
and in th file name give it as %filename%.txt... or vt ever ur requirement
Babu

Want to add multiple idoc type with single message type.

Hi Gurus,
I have a problem. I want to add multiple idoc type with single message type in WE20.
How we can do this in WE20 or is there any other way to do that?
Please help me.
Thanks in advance.
Srimanta.

hi,
basically in partner profile i.e. in we20 , we add details to the receiver / sender port that we have created using we21.
so what exactly we do in that is that we first use the message type for those idocs that we have created.
now based on those message type we create a process code. now this is the reason why you cannot apply several message types with the same name in we20... as process code is unque for each message type.
so thats why you can only assign the same message name to several idocs in we82 and then in we20 define the process code for that message type.
it will solve your problem.
hope this will help you!!!
Thanks & regards,
punit raval.

Inbound IDOC error 51 Application Document not posted

Inbound IDOC error 51: Item: 002 Goods/Service number not entered So application document not posted.
Please help me out

hi
check whether service number is available in the idoc if not check the field mapping

Combine IDoc and RFC Respone in one Message Type

Hello,
I need to have the possibility to store the data of one IDoc and one RFC Response in one Message Type.
The structure should be something like this:
IDoc_AND_RFC_RESPONSE (root)
--item (0..onbounded)
ID (Attribute, type xsd:string)
IDOC (Elemtent, type IDOC <--unfortunately not possible in data type definition)
RFC_Response (Element, type RFC_Response <--unfortunately not possible in data type definition)
The goal is to merge 2 messages (idoc data and the data of a rfc response) into 1 message with logical connected items.
e.g.
IDOC (message 1)
--ID 01
IDOC_DATA_01
--ID 02
IDOC_DATA_02
RFC_Response (message 2)
--ID 01
RFC_DATA_0101
RFC_DATA_0102
--ID 02
RFC_DATA_0201
I need this data to be transformed into:
IDoc_AND_RFC_RESPONSE
--item
ID 01
IDOC
IDOC_DATA_01
RFC_RESPONSE
RFC_DATA_0101
RFC_DATA_0102
--item
ID 02
IDOC
IDOC_DATA_02
RFC_RESPONSE
RFC_DATA_0201
The problem ist NOT how to do the mapping, BUT how to define the data type of the target message.
The IDoc and the RFC have a very complex structure so manually building the structure is not possible.
Thanks for your help.

Hi,
thank you for your hints.
- How can I define one interface with 2 message types? I work with XI 3.0.
- Manually manipulatiing the xsd files is what I wanted to avoid (besides that, there is no possibility to get the rfc as xsd, only wsdl). Besides that, I tried to extract the IDoc xsd and imported it as message type, but there is an error message telling me "Schema to be handled does not contain a definition of type <Data Type Name>", whereas <Data Type Name> is the name I give to the Data Type. I tried the name of the IDoc Type here. Importing the xsd as external definition would work, but that would still not solve the problem as I cannot use the message in my data type definition.
Maybe I should specify the scenario a bit better:
I have an R3 System sending an IDoc.
The Idoc contains multiple items.
The data in the IDoc is NOT sufficient (and due to warranty reasons and company guidelines, it is not possible to add all the needed data to the IDoc).
Therefore, the IDoc is passed to an Business Process, where an RFC is invoked (input are the item IDs of the IDoc).
So afterwar the rfc call, I have all neccessary data per item in 2 messages, the IDoc and the RFC response.
Now I need to merge the data per item into one message.
This one message than is splitted into the several items and every item has to be sent separately. So I need a possibility to unite the IDoc with the rfc response.
Any hint?
Thanks a lot!

Variable initialized with wrong message type

Hi,
I have a BPEL process variableA of Message type A as defined in the partnerlink WSDL file. This variable get initialized during operation A from the partnerlink. The WSDL has another message type B defined for another operation B.
During runtime when operation A is called variable A gets initialized with message type A, however when operation B is invoked with mesage type B variableA gets initialized again with the content of message type B even though it's defined to be of message type A. Below are the snippets from the WSDL and BPEL process file
WSDL file ..
<message name="MessageTypeA">
<part name="payload" element="mpx:MessageARequest"/>
</message>
<message name="MessageTypeB">
<part name="payload" element="mpx:MessageBRequest"/>
</message>
<portType name="MutilPort">
<operation name="A">
<input message="tns:MessageTypeA"/>
</operation>
<operation name="BA">
<input message="tns:MessageTypeB"/>
</operation>
</portType>
Process BPEL file
<variable name="VariableA"
messageType="tns1:MessageTypeA"/>
<variable name="VariableB"
messageType="tns1:MessageTypeB"/>
<pick name="Pick_2" createInstance="yes">
<onMessage portType="tns1:MutilPort" operation="square"
variable="VariableA" partnerLink="Multiplex">
<sequence name="Sequence_1">
<assign name="Assign_2">
<copy>
<from variable="VariableA" part="payload"
query="/ns1:MessageARequest/ns1:Operand1"/>
<to variable="ResponseVariable" part="payload"
query="/ns1:AllOpProcessResponse/ns1:Result1"/>
</copy>
</assign>
</sequence>
</onMessage>
<onMessage portType="tns1:MutilPort" operation="addition"
variable="VariableB" partnerLink="Multiplex">
<sequence name="Sequence_2">
<assign name="Assign_1">
<copy>
<from variable="VariableB" part="payload"
query="/ns1:MessageBRequest/ns1:Operand5"/>
<to variable="ResponseVariable" part="payload"
query="/ns1:AllOpProcessResponse/ns1:Result1"/>
</copy>
</assign>
</sequence>
</onMessage>
</pick>
Please can anyone shed some light on why and how this can happen and where is it going wrong.
Thanks,
Shishir

Looks like the destination which is used by your EG has default settings,
particulary the RedeliveryLimit param. If it is set to -1 (default setting)
WL will try to redeliver the message forever in case of any error. Just set
it to something else. You can also specify an ErrorDestination and hadle
error messages specifically in it.
Denis.
<Gunjan Shukla> wrote in message news:[email protected]..
Hi,
We are using WLI 8.1, in one of our applications I have a message broker
channel configured to listen to rawdata type messages. A jms event
generator is configured to publish messages, which are sent to a jms
topic, on this channel.
We have no control over type of messages sent by client applications, when
some client application sends an ObjectMessage instead of BytesMessage,
following error is thrown
####<Jun 1, 2006 10:47:14 AM GMT-07:00> <Error> <WLW> <P931467> <cgServer>
<ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<anonymous>>
<BEA1-004324CB0C4F26C12C0A> <000000> <Cannot publish non-BytesMessage to
channel of type RAWDATA>
####<Jun 1, 2006 10:47:14 AM GMT-07:00> <Error> <WLI-Core> <P931467>
<cgServer> <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'>
<<anonymous>> <BEA1-004324CB0C4F26C12C0A> <BEA-489048> <Not a
BytesMessage>
server keeps throwing this exception and fills the logs and ultimately
server needs to be re-started.
Can somebody point me to whether its possible to catch these exceptions in
a process?
Or alternatively is it possible to somehow ignore the messages with
mismatched message type?
Any ideas are greatly appreciated.
Thanks and regards,
Gunjan

Two idocs are created for one output message type

hi all,
we are communicating our sap idocs to external system using ALE.It is working smoothly.
Our problem raises here,
.idocs are creating at the time of output type attachment for purchase orders.But rarely,two idocs are creating for one message type.It means two idocs are created for same Purchase order.It makes complications for the external system.
anyone can help me pls?
thnks in advance..........

thanks jurgen for ur reply,
jurgen, the second idoc is not an "ORDCHG",It is the replica of first idoc.This one has also "ORDERS" message type.The only difference between these idocs are the time.It means the difference between the time field segments of these idocs have only three(3)seconds difference.We think that its from the system error.If it is not from the system error pls give me the explanation.
thanks in advance.......

Regarding Message Type in ALE

hi guys,
i was involved in Master data distribution using Message Types MATMAS, DEBMAS and CREMAS but never created a customer specific Message Type that is why, i just want to know in what cases do we have to create our own message type's using we31, we30 and we81 and we82.
can any one out here help me out by sharing giving some real time scenario's in what cases do we exactly have to create our own message type.
thanks
Pavan

Hi Pavan,
There is no hard and fast rule that you use standard or custom message types...
SAP has provided messages for almost all scenarios. If you don't have enough fields in standard messgae type, you can enhance it to accumulate your requirement.
But if the organization has completetly custom defined system (involving many Z-tables) , we create custom message types...
As far as my knowledge, we should try to go ahead with standard message types by suppressing unnecessary segments and enhancing existing segments just to avoid Z-objects.
Regards,
Audy

Tcode to send custom data using custom message type in ALE

I have ceated custom message type and i want to send data to say system B.I wanted to know Tcode to send custom data using custom message type in ALE.
for example:
material data...message type = matmas....tcode = BD10.
like this.
i hope you have got my question.
plz guide me?
regards
mallikarjun mangalore

Hi,
Sending data through ALE is not a single-step process. Take a look at http://www.sapgenie.com/ale/. The paper at http://www.sapgenie.com/sapgenie/docs/ale_whitepaper.doc is a wonderful resource for the ALE process.
Regards

INVOICE EDI Inbound IDOC error

Hi,
We have implemented Support pack SAP_APPL SAPKH47027. And now we get
the Following error in IDOC inbound processing message type INVOIC during intercompany billing to post vendor invoices.
Error message: 'Field BSEG-BSCHL (1) (is not an input field)'.
I find that this is due to the OSS note: 960639 that has come along
with this Support pack.
Also SAP has mentioned a corection note to this problem. OSS note:
1032469.
But this Note 1032469 is not clear.
It is mentioned that..
"You explicitly enter the tax amounts in the IDoc
You can enter the tax information either at item level in
segment E1EDP04 or in header segment E1EDK04."
Is SAP suggesting to enter the TAx amounts (E1EDP04-MWSBT)?
And shud the coding be done during the Inbound processing function
module:
IDOC_INPUT_INVOIC_FI or during the outbound processing RSNASTED
(EDI_PROCESSING). We use SAP standard functionality.
Can anybody please explain what SAP has suggested to do techincally.
Regards,
Midhun.

Hi,
I checked both OSS note 960639 & 1032469. I neither find anything in first note ( 960639 ) which could cause this probem nor in the second note ( 1032469 ) which solve this problem. The only way to check is by doing what note 1032469 is saying.
One more thing you can do is debug the code, put the break-pointe message statement and findout where this error message is coming. Then you can check the code to find out the reason for this.
Can you also check if you are getting the same message when you try to enter same data directly in SAP using FB01 or whatever the relavent transaction is.
Regards,
RS

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

PO Rejection - ORDSP Idoc Errors in ECC with different process codes

Hi All,
We were testing the Scenario where the Supplier rejects a PO line item as part of the PO Collaboration. On rejecting the PO in SNC, it trigerred an ROC XML with AcceptanceStatusCode == RE. The same was passed on from XML to Idoc in the IDoc segment E1EDP01, field ACTION = "003".
However, such ORDSP Idocs was failing on the ECC side during Inbound processing with the following errors:
1. Acknowledgment for PO item 4400000XXX 00010 contains quantity variance: Message no. ME794
2. Price unit 0 from IDoc differs from unit of purchase order 1: Message no. ME729
3. Order price unit differs from unit EA from purchase order: Message no. ME728
4. Order units differ : Message no. ME791
5. Material number differs from that of ordered material : Message no. ME790
Note : We dont get these errors for a normal confirmation. It happens only with Rejection.
The deletion indciator could not be set in the ECC PO line item even after manually correcting the above errors in the Idoc and posting it.
Then based on this SDN Post: [PO rejection in SNC does not update the items in MM with ORDRSP;, we changed the WE20 settings. i.e., for ORDSP Idoc changed the Process code from ORDR to ORDR_SUS. After this change, the the above errors were eliminated and the the rejection data was also updated on the ECC PO by setting a deletion indicator. But we are having the following issues:
1. Though both the confirmation & rejection data are getting transferred successfully, the Idocs remain in status 52 (Application document not fully posted).
2. The message in the status record is "Rejection of PO item 4400000XXX 00010 with reason: Message no. ME749
3. Came across these 2 related SAP Notes:
a. #1087422 : But this is not applicable as the note states that this error will occur only if we delete the PO line item before hand in ECC.
b. # 66192 : This note suggets a custom solution. But actually all the info from the ORDSP Idoc are getting processed successfully (Rejection & Confirmation send in the same Idoc). Only the status of the Idoc (Status = 52) is concerning us.
Looking forward for inputs / suggetions from those who have used the Rejection functionality in SNC without custom development.
Regards,
Bharath

Hi Bharath
Rejections is handled like that only, can you please check whether note 1529579 is helpful
It is standard behavior, as it expects other segments to fill, but never the less the PO will be updated properly, its only problem
with the status of the idoc....nothing wrong in the data updation. The above note should be handy.
Regards
Vinod

Inbund IDOC error: Status records with status 51 after status 53

Hi all,
I'm looking to resolve an issue related to posting an inbound IDOC. when I process inbound IDOC created from report prg I'm getting a status message: "Status records with status 51 after 53" .
Functionality: I'm creating an IDOC from flat file and processing it to post Customer master data into SAP. During this process creation of IDOC is successful but when I'm changing the existing data record (customer master data) IDOC is throwing this error.
Changing data: For changing existing data I'm passing KUNNR field and overwriting the remaining data. Even though the idoc status is 51 the changed data is getting posted in to SAP. Here my concern is to see IDOC status as 53.
Regards,
Ganesh.
Edited by: Ganesh Sunkara on Aug 1, 2009 3:45 AM

Hi all,
I solved this issue by myself. There is an error in the user exit code.
regards,
Ganesh.

Custom inbound Idoc error handling/ Workflow

Dear Experts,
I have a requirement where in I created a custom inbound idoc, but now i need to handle the errors in the workflow and notify the users thru workflow on an error.
Can some one please provide me a step by step guide on how to create a organizational unit, position and assign users to the position... and any other steps that need to be configured to notify the user on the error.
I'm pretty new to all these organizational uints and workflow related stuff. Any step by step would really be helpful.
Thanks for your time.
-Amit.
Moderator message: sorry, these forums cannot replace proper training, if there is step by step guides out there, then please use the search functions.
Edited by: Thomas Zloch on Oct 31, 2010 11:50 AM

Vittal,
1. If your requirement is for a SAP Standard Basic Message type and a Z extension: Then you simply have to find out the 'Standard Task' associated with basic type. You shouldn't worry about extensions. The standard task will be triggered at input error.
2. If your requirement is for a Z basic type i.e. you have created a customer IDOC for a custom processing: There are many dependencies on how you can achieve this. Firstly, you need to know how you're are processing this Z_IDOC. Are you using a standard FM or custom workflow or custom FM? There should be some triggering event within the processing of this Z_IDOC which will raise a certain flag when the error you want to capture happens (or when there is a generic error). You can configure this event in binding objects to trigger a workflow task. If you take a look at any standard tasks, you'll get an idea how the triggering event happens.
Once the workflow task (you can use custom task or use a standard task i.e. by triggering a standard event within the IDOC processing program) is triggered, you can either send it to SAP inbox, e-mail, trigger another processing etc. This is altogether another story.
So bottomline: For custom IDOC processing, you need to trigger an event when error happens. This can be a custom event or a standard event. This event should be linked to a task (custom/standard - check in SWETYPV). Bind all of these in PFTC. Once the task is triggered, you can do whatever you want to do with it.

Scheduling agreement inbound idoc error.

Hi Experts,
I am creating an Scheduling Agreement with DELFOR02 inbound idoc, while creation the Scheduling Agreement system is giving error regarding Scheduling Agreement not found. In fact I have create the Scheduling agreement by T-code VA31. And I check the table VLPKM, there are relevant record stored.
Then I maintain the view V_T663A to not check everything when inbound idoc recevie. and tried agan in t-code BD87. the system give me another message Make an entry in all required fields.
How can I handle these error messages?
Thanks..
Regards....

Does any one has ideas for that?
Thanks.

Inbound IDOC error :51 Passed with out Message Type to ALE Layer

Similar Messages

Maybe you are looking for