2014 Jan 29 11:34 AM
Dear Team,
Please help me/us on priority.
We have perfect connectivity from MDO (Master data Online) to backend ECC system. No changes to Configuration/profile/authorization/RFC.
Here is current senerio :
1)End User trying to create Vendor master data in ECC system via MDO
interface.
2)When vendor master is created via MDO interface; 4 IDOCs are created.
i) ADRMAS - Address master (successfully processed status) 53
ii) MDO_MT_VCP - Vendor Contact person (Successful processed status) 53
iii) ZMDO_MT_CIN - PAN card Details (Successfully Processed status) 53
iv) CREMAS - Vendor Master Creation (Unsuccessful processed status) 51
Please note that Despite CREMAS showing in failed status; Actually
Vendor master is successfully created in Backend ECC system. But in IDOC
processing we02 as mentioned first 3 IDOC's status in 53 while last one
IDOC status is 51.
This is quite confusing situation. I have attached Screenshot. No message is displayed other than I::000. What customer is shouting is that they not differentiate between successful and unsuccessful posting from IDOC status.
Regards,
Arthur Rodrigues
Dear Team,
Please help me/us on priority.
We have perfect connectivity from MDO (Master data Online) to backend ECC system. No changes to Configuration/profile/authorization/RFC.
Here is current senerio :
1)End User trying to create Vendor master data in ECC system via MDO
interface.
2)When vendor master is created via MDO interface; 4 IDOCs are created.
i) ADRMAS - Address master (successfully processed status) 53
ii) MDO_MT_VCP - Vendor Contact person (Successful processed status) 53
iii) ZMDO_MT_CIN - PAN card Details (Successfully Processed status) 53
iv) CREMAS - Vendor Master Creation (Unsuccessful processed status) 51
Please note that Despite CREMAS showing in failed status; Actually
Vendor master is successfully created in Backend ECC system. But in IDOC
processing we02 as mentioned first 3 IDOC's status in 53 while last one
IDOC status is 51.
This is quite confusing situation. I have attached Screenshot. No message is displayed other than I::000. What customer is shouting is that they not differentiate between successful and unsuccessful posting from IDOC status.
Regards,
Arthur Rodrigues
2014 Jan 29 1:31 PM
Hi ,
Can you check the we07 once. Check the report with RBDMA*
Regards,
Madhu.
2014 Jan 29 1:44 PM
Let me quote a reply from SAP for the same issue when loading customer masters:
"Idoc processing works with potentially many separate call transactions.As a result, there can be many data completely updated prior the idoc isset in status 51 .
A DEBMAS idoc have the general data segments like E1KNA1M.
It might have several company code data segments like E1KNB1M...
several sales area segments like E1KNVVM...
All these segments leads to separate batch input transaction to be run.
It can be XD02, followed by several XD01 (for creating a sales area of
a customer).
As a result, the processing of an idoc can finish with status 51 and
have some master data processed successfully."
2014 Jan 29 3:22 PM
Dear Jurgen,
Thanks for elaboration
I did found scn link related to my problem....
Only difference being My all IDOCs are processed successfully but IDOC status for CREMAS is 51. As Mr. Abhishek Biwal has mentioned screen shot; Same is showing in status record for CREMAS.
I am not sure how did he figured out about custom code. Cause in our case also we did not do any changes from basis side.
Regards,
Arthur
2014 Jan 29 10:29 PM
have you already tried to process the IDOC in foreground, e.g. in WE19?
or have you tried to re-process the failed IDOC?
It is extremely difficult to find the source of this error, for this one would need to know the whole IDOC with all its data, and how the vendor was before the IDOC got processed.
if it is a complete new creation, then it might be a little easier, because then you can mainly focus on the data in the IDOC, and how they are processed.
if the vendor already exist and you extend this vendor to new organizations then it is more difficult as you then potentially have a mix of creation and change.
one tipp: make sure that you have not 2 IDoc segments with the same data.e.g. several purchasing organisations and 2 of them are redundant.
2014 Jan 31 5:43 AM
Dear Jurgen,
It is completely new vendor master creation. Our MDO database has vendor details. End users login via MDO interface and go for new vendor creation. When they are done from their side; 4 IDOCs corresponding to Vendor details ( CREMAS, ADRMAS, Vendor contact person, bank/pan details) are processed. All are getting processed successfully (including CREMAS) ; but CREMAS status is 51 and others' 53. when checked for error message, there is this i::000 error message showing.
Problem is: customer has to go check in backend (XK03) if that vendor is created or not as successful and unsuccessful CREMAS IDOCs hold same status 51.
Regards,
Arthur
2014 Jan 31 5:47 AM
Also About Reprocessing IDOC, yes it goes successful. what end users do, instead of reprocessing IDOC, is that they once again select same vendor in MDO, Go for editing details, and do no changes and saves. Then CREMAS IDOC stands processed.
regards,
Arthur
2014 Jan 31 6:08 AM
you see, it is exact the behavior that I suspected. Without knowing the details of the IDOC (exact structure, segments and key fields of each segment) it is impossible to know the reason.
2014 Feb 13 1:11 PM
Dear Jurgen,
Sorry I am replying after so long. We asked SAP's help. they told they want IDOC for processing. To our/their dismay; It is Synchronous IDOC processing. so we can not provide any.
SAP's reply :
Could be that data are processed but late occurs an error and set status to 51 (cf explaination in note 1783582).
Root cause can be a modification, please check this.
At least LFBW segment for idoc 0000000006547246 seems not complete. Maybe can you check that also.
I will have to check it. Not sure where to start but will try.
Regards,
Arthur
2014 Feb 13 8:36 PM
We do not use the LFBW segment.
But you should be able to see the posted IDOCs in BD87.
Based on that you could create one yourself with WE19 in your test system.
2015 Jul 21 9:30 AM
Hi Arthur,
did you find a solution to this problem?
I am currently facing a similar issue - although instead of vendors I am trying to load customers.
I am using message type DEBMAS02 and for now I am only trying to create a single customer.
The customer is created and everything seems ok when looking at XD03 but the IDoc gets status 51 and no message - which means no indication of why the IDoc failed...
/Michael
2015 Jul 21 11:08 AM
Process the IDOC in foreground.
Go BD87 and find your failed IDoc.
Select the IDOC and choose from menu EDIT > Restrict and process.
On the next screen (is a selection screen for manual processing, usually already prefilled with the earlier selected number) you have to remove the flag from background processing at the bottom.
then you process the selection until you get to a screen with an individual IDOC number (screen called Status display) Here choose from menu Edit > process > in foreground (or foreground from error)
Then you should see at which screen and field SAP is when it fails.
2015 Jul 31 7:46 AM
Hey Michael,
Sorry I am replying late; If I recall correctly (as problem was with my last employer's client) the issue was with update of back account details of vendor. but We raised it to SAP; reproduced issue in quality system and asked them to check. But yes; issue was from 3rd party tool which used for MDM in our landscape.
Regards,
Arthur
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |