Problem with Delivery IDOC staus 51

Hi all,
I have problem with Delivery IDOC.
An IDOC is sent from the logistics provider with reference to a manually created delivery, which creates another IDOC & another partial delivery.
The second IDOC created then confirms the partial delivery created by the first IDOC.
When IDOC try to confirm this delivery, it goes to status 51 with error " Delivery does not exist".
In some case IDOC was correctly processed & confirmed the delivery.
In some cases it went wrong.
Any ideas regarding this?

Hi Suneel,
It seems there is timing issue between the first IDoc and second IDoc.
When the first IDoc has not yet commit to DB then the second IDoc tries to process with reference to the first IDoc.
Is there any that can distinguish between 1st and 2nd IDocs?
In other word, can you post the second IDoc within minutes delay?
Just my two cents.
Regards,
Ferry Lianto

Similar Messages

Problems with multiple idocs in one file ( Inbound file )

HI,
Thanks in Advance for your suggestions.. Highly appreciated.
We have problems with multiple IDocs in one file.
We are using XIB ( Amtrix ) as Middleware to receive the files.
Curretenly When the file contains one IDoc then there is no problem. IDoc is created and everything is ok.
If file contains two IDocs ( for example two messages ORDERS and DELVERY ) then it is creating two IDocs but both IDocs contains ORDERS plus DELIVERY segements information. That is the problem. Some how SAP unable to differentiate the IDocs in the file.. But it knows that how many idocs are there in the file..because it is creating exact number of idocs.
We are using TRFC port ... Do I need to change it to File port..
When we have more than one idoc do we need set any parameter in the file ...

Thanks for the swift response. Always ideas are useful.
As of now , Middleware cannot split the file.
Thing is SAP is creating two Idocs with different message types. Problem is First IDoc contains ORDERS message type but also DELIVERY segments as well. Second IDoc with DELIVERY message tyoe but ORDERS segments as well... This is the problem... I think we are missing some field activation in file for EDIDC record.
As far as I know file port supports the number of IDocs in one file.. Hope TRFC port also supports that

Problems with posting iDocs from MDM in SAP R3

Hi,
I am an MDM consultant, with limited knowledge about SAP R3.
We send material master data from MDM, via PI to R3 using iDocs.
We are having problems with posting MATMAS, and it seems the problems are with updating already existing materials.
In BD87 we get the following warnings:
The field MARA-ERVOE is not ready for input and was therefore not initialized
The field MARA-ERVOL is not ready for input and was therefore not initialized
The field MARA-FERTH is not ready for input and was therefore not initialized
The field MARA-KZGVH is not ready for input and was therefore not initialized
The field MARA-XCHPF is not ready for input and was therefore not initialized
With the last message being:
No changes made
I have checked the MDM syndicator, and none of these idoc-fields are linked to the MDM repository.
So they are syndicated blank.
If we try to resend the material, it is again stopped and in BD87 I see the same messages.
Please help me understanding how to solve these issues.
Thanks,
Thomas

Hi,
Please refer the below threads which talks about the similar problem
http://scn.sap.com/thread/3180116
http://scn.sap.com/thread/1374222
Generally the basic view of the material to be created first. Then the sales, purchasing and other views to be created.
There are few fields in the other views which gets values from the basic data view.
Regards,
Antony

Problem with Inbound Idoc

Hi everybody.
I´ve got a problem with an inbound idoc. I've got a standard idoc INOTIF with an extension.
To receive this Idoc from external systema I´ve created a Z FM to process this idoc.
The problem is that when this idoc get to SAP the FM never is executed and the idoc appears with red flag and show me
the next error: No status record was passed to ALE by the application and the idoc is shown with the status 51.
¿¿How can I fix this??
Thanks a lot
Regards

hi
and also give the funtion type is function module in we57 and in BD51 give ur ZFM and give 1 in input.t field.
now you can see ur FM in WE42 under Identification field F4 value.
The FM which is created by you it should be in F4 help list fo field Identification in we42.
and give the Message type and Process code in we20 in inbound parameters.
i am sure this will work .
regards,
Kiran Jagana

Problems with sending IDocs into R/3 using BPM

Hi Vishnu,
as I have read the forum, you have experience with sending IDocs into R/3 from XI using the BPM.
Did you have problem, that this sending takes very long time?
My BPM splits the xml, sends IDoc into R/3 immediately, but the processing of the 2nd IDoc takes 6-10 minutes!
Do you have any idea, what could be wrong?
Thanx 4 answer, Peter

Vishnu, I was discussing this problem in another thread, but no helpful answer was sent, and I have read, that you have experience, so - just for explanation
Well,
yes, this situation is really strange.. New facts are:
when I send into XI XML, which is splitted in the BPM only into 1 IDoc, it is processed immediately. When I send there XML for 2 IDocs, the first is processed immediately, the 2nd starts immediately, but end of process is after 6-10 minutes, it depends... Then I tried to send there XML for 10 IDocs - and now attention please! 5 of them have been processed almost immediately, 5 of them after 8 minutes... The last test was with 16 items - 6 processed immediately, 10 after 10 minutes... And all these 10 minutes was my 4 processor XI box unavailable, with over 60% load... But finally the IDocs arrive!!
Any explanation???
This is really unbelievable situation!
Port name is SAPDEV, rfc destination DEVCLNT100
Actually, when I was creating the scenarion using the wizard and trying to add my communication channel(IDoc type) to receiver agreement, I got error - communication channel is not configured correctly, use another one. But somewhere I read, that I should create the receiver agreement manually. So I did.
To my BPM:
-receive MSG
-switch (but I'm testing only one branch now) - and the MSG message is always passed here, it's ok
-then I have transformation to MultiMSG (message with multiple DATA for multiple IDOCS)
-then comes the split mapping Multi2SingleMSG
-then ForEach Block with sending the Single MSG
this is the end of the BPM, and outside the BPM comes the mapping Single2IdocMSG and sending the IDoc into R/3
before I had the Single2Idoc mapping in the BPM, but thought, that this could be the bottleneck, so moved the mapping after the BPM... It didn't help...
So, what do you say?
Peter

Problem with HRMD_A06 idoc

Dear All,
I am using the IDOC HRMD_A06 for carrying out various operation on the available HR infotypes.Kindly go thru the below mentioned details for further insight of the problem
1.Scenario:
a.An interface to SAP HR system needs to be built
b.The interface will supply incremental master-data in
form of flat-files
c.An integration broker ,SAP XI will then convert the
flat-files to I-Docs and send I-Docs to SAP HR system
d.The I-Doc chosen for this purpose is HRMD_A.HRMD_A06
e.However this I-Doc is not supporting different
operations on incremental data like modify, delete etc
f.Further validations are also not being supported
g.Also segments for certain info-type records are missing
Example for Delete Operation mode:
Operation Delete: Delete existing infotype record
Expected Result: Only the particular info-type record, as supplied in the I-Doc should be deleted and not the entire personal number with all the info-types
Actual Result: The entire personal Number is deleted.
Is it that the Idoc behaves in this fashion or there is some other flag apart from OPERATION, which needs to be set.
Regards
Vinay

Hi Vinay,
Have you found a solution ?
Because I'm a similar problem by using IDoc HRMD_A06. I have not a segment E1P0021 when I delete the infotype 0021 on an employee. I have only its segment E1PITYP.
Regards
Mickael

Problems with sending IDOC via RFC from Unicode to NonUnic

Hello
I have following problem, sending an IDOC via RFC from Unicode to Non Unicode System. IDoc is not sent with error: codepage of receiver system cant determined. receiver destination was: Message no. B1999
I have tried different options in sm59, but it didnt help.
Any ideas? The recipient system is rather old, version 4.0

hey,
I had a similar experience. I was interfacing between 4.6 (RFC), PI and ECC 6.0 (ABAP Proxy). When data was passed from ECC to 4.6, RFC received them incorrectly. So i had to send trimmed strings from ECC and receive them as strings in RFC (esp for CURR and QUAN fields). Also the receiver communication channel in PI (between PI and RFC) had to be set as Non unicode. This helped a bit. But still I am getting 2 issues, truncation of values and some additional digits !! But the above changes resolved unwanted characters problem like "<" and "#". You can find a related post in my id. Hope this info helps..

Problem with mass IDoc for Material Master

Hi All,
Can anyone suggest a solution to work with mass IDocs for Material master?
We have DEBMDM and CREMDM as mass capable IDocs for Customer and Vendor. How do we get mass Material Master IDocs from R/3 in a single XML file?
Also the standard Material repository supplied with SAP MDM 5.5 SP3 doesn't have any XSD definition for MATMDM. Can anyone throw some light on this problem?
Regards
Pooja

Hello Pooja:
The standard way to do it is to generate a single file containing multiple idocs (And for the sake of performance, I suggest you stick to this technique).
In the case of material master, everything is straight forward. In the case of customer and vendor master, when data flows from R/3 to MDM no idoc conversion needs to be performed by XI.
However, for the case of customer and vendor master, when data flows from MDM to R/3, XI needs to separate the data in CREMDM to CREMAS and ADRMAS in order for R/3 to be able to process the idocs; as well as separate the data in DEBMDM to DEBMAS and ADRMAS.
The good thing is that you do not need to worry about all this mappings and conversions in XI. The only thing you need to do in XI is to import the standard business content for SAP MDM 5.5 into XI.
Hope this helps.
Regards,
Jorge.

Problems with sending IDOC in tRFC.

Hi All,
I am sending IDOC to websphere from SAP.
Problem is very weird. All the IDOCs have status 03, but some of them never reach webshpere.
I checked SM58 and there are some tRFC entries for the same.
Following is the error there:
Check SAP Connector log. Error in BO Handler.
I think problem is after the data has been sent to ALE layer.
Can anyone suggest what can be the issue? And how can this be resolved.
Regards
Anuj

Hi Anuj,
As it seems like from the error message there is some problem with the way BO handler is responding to request BOs .
The base class to initialize the connector has been set properly though.
Check the log in SM21 on this and it might give you the detailed information.
Also check if you are passing the large objects, which might require some additional config.
Hope these pointers help in solving the issue.
Cheerio,
Disha

Scheduling problem with delivery date in purch.req and requirement date

Dear all,
I have the problem, that the calculated delivery date in the purchase requisition does not correspond with the requiement date of the production or planned order.
I would like to use planned delivery times in the material master.
Example:
Planned delivery time: 20 days
Todays date 01.10
Case 1)
Requiement date of planned order 10.10
Case 2)
Requiement date of planned order 20.09
This situation can happen in our envirnoment, as the engineering process still continues after start of production. In this case I would like to have the following result:
Case 1)
Delivery date is 10.10 minus the goods receipt time
Case 2)
Delivery date is day of MRP or one or two days more
I made the setting that dates in the past are not allowed. This solves my first smal problem. I tried to set the scheduling margin key but these settings do not help me, as they are relevant for all materials. I need of course individual planned delivery dates per material.
So, I want to change the standart MRP procedure that in the case of the "wished requirement date" not the calculated date is beeing taken, but the "wished date". Usually you receive an exeption for this case and you would need t solve this manually. But this we dont want to do.
Can s.o. please help me? Thank you all very much, I really dont know what to do in this case.
With best regards,
Bjoern

The question cannot be answerd by SAP standart as I see. We will go through a workaround.

Problem with Custom idoc sending

Hi Experts,
We have created partner profile and port for receiver system, our idoc is Z (custom) idoc.
but the problem is here, when we are sending that idoc from R/3 system, it is in Yellow position with message number 30. How we can solve this problem.
Is there any other configuration required for Z (Custom) idoc.
Please help,
Regards,
Study SAP

hi check this...
http://www.****************/Tutorials/ALE/CustomIDOC/Create.htm
check the process followed or not if u miss any steps then it will give warning....that is not a problem..see one thing after creating the idoc u need to give the status back to the idoc_status. otherwise it will not show the green message 51...we have to do it if this is the custom idoc ...otherwise if it is a standard one there is nothing to do it will automatically catch the message back.

Problem with an IDOC, receiving empty fileds

Hi!
I'm trying to read an IDOC with a Real Time Service through a RFC Client. We have all configured and running, and the Data Flow is as simple as reading the IDOC and writing it to an XML template. The problem is that if I send 3 records, I get all the 3 records in the XML, but only the date fileds have data, all the remaining fields are empty.
We have tried some options but no one is working. Any help please, guys?
See you nad thank you very much
Luis C. Gamiño C.

Hi!
We are using that same example, MATMAS03, to do our configurations. After some testing we have found out that the fields with the type CHAR## are the only ones who are written to the XML file. These fields are originally numbers in the SAP tables, but they are converted to char for the IDOC. But all the remaining fields are empty, but we are sure they have data.
Do you have any more ideas, please?
See you nad thank you very much
Luis C. Gamiño C.

Problem With Uploading IDOC Metadata using IDX2

Hi Experts,
While i am uploading IDoc metadata using IDX2 it is showing
"I::000" information.
Anybody please help me why i am getting this problem?

Hi Bhuvan,
Basicall this problem arises when user Id being used in the SM59 to trigger the IDoc's from the R3 system , i,e , the XI user id being used in SM59 of R3 does not have the authorizations to post the Idoc.
Note : 837595 describes the authorizations needed to post and Idoc. Make sure that the user id has the authorizations in this note.
Activate the authorization check in transaction ST01.
And also it may be due to insufficient roles for the user which ur using in RFC connection to SAP system.
Check with the port in IDX1 whether u have configured corectly.
Check this link
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
PAGE - 11
Regards,
Vinod.

Problem with inbound idoc processing.

hi
I am creating release orders through idocs with the help of a custom program.
After posting the release orders, i need to take the RO number created by the posting from EKPO table, which is required for further processing within the same program. An error is coming saying that no RO exists for the specified criteria. May be the idocs are not getting updated.
Appreciate any suggestion for the above problem.

Hi,
Have you used
COMMIT after creating the RO..
That might be the reason i Think .
Use
Commit and wait.
Hope that helps.
Regards,
Tanveer.
Please maek helpful answers

Problem with processing idoc cond_a04

Hi all,
I m using idoc message COND_A04 to populate and create condition and scale entries for Agreements (MEB1). However, i am getting the following error:
"Results of pricing with condition type ZI01 can not be changed"
where ZI01 is a condition type i've defined.
I m not sure if anyone has encounter and got this problem resolved.
I've populate values to the following segments:
E1KONH-KNUMA_BO (agreement number)
E1KONH-KNUMH
E1KOMG-KSCHL (condition type)
E1KOMG-KOLIF (prior vendor)
E1KOMG-EKORG (purchasing org)
E1KONP-BOMAT
E1KONP-KBETR
E1KONH-DATAB
E1KONH-DATBI
E1KOMG-KVEWE (filled with value 'E')
E1KOMG-KOTABNR (condition table number)
E1KOMG-KAPPL (filled with value 'M')
Thereafter i tested the idoc posting using WE19 and got the error above.
Are there any fields in the segment i missed out?
Or could there be other cause?
Cheers,

There could be numerous reasons for the IDoc failure because the message that you are getting is too generic. Btw, Is this the only message you get, check if there are more than 1 status 51 in your IDoc to get some more information.
Also see the longtext of the message by double clicking on the status message, probably you will get a more comprehensive reason for the failure.
If nothing of the above helps, try to see the message number and class and see where it is used in the posting program and put a break point at the spot where this message is triggered.
regards,
Advait

Problem with Delivery IDOC staus 51

Similar Messages

Maybe you are looking for