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.

Similar Messages

Error message B1 357-Status records with status 51 after status 53

Hi All,
somebody knows why is can be caused this message:
''Error message B1 357-Status records with status 51 after status 53''
Thanks and best regards
L

Dear Luis,
Please Check
Status records with status 51 after status 53
Best Regards,
Amit

Error in RFx with user-specified status profile

Hi experts,
I am having an issue in SRM 7.0 creating status profile for RFx.
When I try to create a new RFx, I get an error screen with message "Status profile ZCCP is not allowed for "Bidding Header""
In order to configure this, I went through the steps described in SAP Library:
1- Define user-specified status profiles in Customizing for Supplier Relationship Management under SRM Server->Cross-Industry Functions->Application Settings->User-Specified Status->Create Status Profile for User-Specified Status:
I created status profile ZCCP with the following data:
10     SUSP     Suspended     10     90     1     1
90     HABI     Abilities 10     90     1     1
and I assigned the status profile to object type "Bid Invitation Header (PS_BBP)"
2- Assign user-specified status profiles to procurement documents in Customizing for Supplier Relationship Management under SRM Server->Cross-Industry Functions->Application Settings->User-Specified Status->Assign User-Specified Status Profiles to Purchasing Documents
I created a new entry with:
BUS2200     H Header     0     ZCCP
3- Assign user-specified status profiles for each transaction type in Customizing for Supplier Relationship Management under SRM Server->Cross-Application Basic Settings->Define Transaction Types
I assigned the status profile ZCCP to all relevant operation types of obj. type BUS2200.
Does anyone know where this went wrong??
Thanks in advance!
Regards,
Joã

Hi joa
http://help.sap.com/saphelp_srm70/helpdata/EN/e8/70ff4187526430e10000000a1550b0/frameset.htm
You can use Status Management for records and documents. In Customizing, define the status values and the permitted sequence of these values. Users can then set these status values as attributes for records or documents.
The following Customizing steps need to be performed for Status Management:
·        Status value definition
To perform this step, choose IMG activity Customizing for Status Management -> Define Status For more information, see the online documentation for the IMG activity.
Status profile definition
To perform this step, choose IMG activity Customizing for Status Management -> Define Status Profile. For more information, see the online documentation for the IMG activity.
Status network definition
To perform this step, choose IMG activity Customizing for Status Management -> Define Status Network. For more information, see the online documentation for the IMG activity.
·         Assignment of a status profile to an element type
For element types whose elements you want to use Status Management for, assign an existing status profile to connection parameter STATE_PROFILE_ID. (The connection parameter is only offered for records and documents.)
Subsequently, users will be offered the attribute Status in the attribute maintenance dialog box whenever they edit the elements in question. Input help contains the status values that you have created.
If you want to use Status Management for the API, you require the following authorization objects: S_SRM_STAT, S_SRM_ST_P and S_SRM_ST_N.
br
muthu

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

Error while recording with fire fox (4.0) browser.

I am from ACS - MCSP QA Team,
I am getting the following error message , while recording with Fire Fox (4.0) Browser.
*"Cannot get a connection from the browser helper after 15 seconds. Do you want to*
*continue waiting for the browser to load?"*
Note: Before record , I Set the default browser as fire fox.
Could you please guide me regarding this?
For Screen shot please refer the below link,
http://imageshack.us/photo/my-images/847/osfirefox.png/
Edited by: 876356 on Aug 1, 2011 5:31 AM

Hi,
OATS 9.21 supports Firefox 3.5 and 3.6.
Cheers,
Jamie

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

Data Services IDOC Errors when working with a newl Basic Type

Hello,
Just wondering if anyone else has encountered an issue similar to the one I am dealing with. We are trying to create business partners in SAP CRM from Data Services via IDOC. We are not using the standard IDOC, but instead we are using a new IDOC type.
This IDOC type is generated by SAP CRM automatically through a transaction BDFG. This transaction creates a new basic type for an standard IDOC with the additional fields that we have added through the easy enhancement workbench (EEWB).
The issue that we are having is that when we import the IDOC type into data services and we look at the schema many fields and sub-structures of the IDOC are duplicated. This means that we receive hundreds of errors when we try to validate our data flow. I can delete the duplicated sub structures in my query transformation but then the query transformation and the output schema and the idoc input schema are no longer identical.
I have searched all over oss and different web forums for a solution but no one else it seems has even encountered this error. If anyone else has had a similar issue and can offer help it would be greatly appreciated.
Bill

Issue is resolved.
After importing the meta data for the IDOC into data services I then proceeded to edit out all of the duplicate structures and fields from the IDOC.
After making the IDOC structure in data services identical to the structure of the IDOC in SAP I then proceeded to test this IDOC and it executed successfully.

When Syncing with Desktop I get a error message "Record with Specified fffffeoa not found

I can sync with my desktop using my Playbook but will not sync with my 9700 bold and receive this error message.

You're most likely gonna have to backup, then erase your phone, as described here:
http://support.apple.com/kb/ht5014
If Orange has informed you your request has been processed, this should do the trick.

Error when recording with "What you hear" opt

Hi there fellow Creative Fans,
I see that a similar thread already exists for this topic, however it does not seem to be resolved yet...and, my situation is a bit different. I run a pretty standard setup (Intel P4 .6 Ghz, 52 MB RAM, Windows XP Pro SP2) and of course a Sound Blaster Audigy 2. I have been running this setup for approxiamately 5 months now with no changes whatsoever (hardware/software). I have been making extensi've use of the "What you hear" functionality in the Creative Media Go Player. Two nights ago, I wanted to record sound from a DVD and I got this message "The recording process was aborted".
As stated before, I have not added or removed hardware, installed service packs or any new software for that matter. I have reinstalled all the drivers and software, checked and re-checked settings. I have downloaded the latest drivers from Creative's site...all in vain.
Can anyone please help. If acker25 is reading this: "Have you resolved your problem yet?"
Regards
Steyn

Problem resolved. Follow Creatives FAQ advice on uninstalling the Soundblaster device drivers...it's on this web site. Follow all the steps, but include deleting "Creative" out of the registry. This worked for me. I can not guarantee this on any other users machines. I'm assuming that the drivers get's damaged.
Good luck.

Idocs status records!!!

Hi,
We have a requirement in which the status records need to be added in the inbound Idoc.
In the present scenario, Idoc status records are being created like : status 52 Inbound delivery/deliveries are created(no's are 000001 to 000005). This is current scenario.
Requirement is like :
we need to have the number of status records depends on Inbound deliveries created.
For ex : If two inbound deliveries gets created in an Inbound Idoc, then In Idoc status records should be like :
Status 52 Inbound delivery created ( no 0000001 to 0000001)
Status 52 Inbound delivery created ( no 0000002 to 0000002)
Status 52 Inbound delivery created ( no 0000003 to 0000003).
and so on.......
Please let us know how can we acheive the above scenario?
Thanks in advance.
Ramesh.

The inputs to the IDoc processing function are:
*"*"Local interface:
*" IMPORTING
*"     REFERENCE(INPUT_METHOD) TYPE BDWFAP_PAR-INPUTMETHD
*"     REFERENCE(MASS_PROCESSING) TYPE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*"     VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      *IDOC_STATUS STRUCTURE BDIDOCSTAT*
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*"      WRONG_FUNCTION_CALLED
The status records are returned from the processing function via the parameter IDOC_STATUS which is an internal table so you can append multiple entries to it.
The only restriction is that all records must have the same status code (ex. all must be 51 is there is an error, or all must be 53 if there are no errors). An IDoc processing function executes as a single DB transaction so it is all or nothing.
~Ian

Error while updating the status record of IDOC in SAP

Hi All,
I am facing this problem. I have done outbound processing and IDOC was sent successfully from SAP to EDI system and it was processed in EDI and now EDI system wants to send the status back to SAP with a status message and the status number that we are using is '24' and we have mapped all the fields in the status table EDIDS and made sure that EDI system sends all those and I think Counter field can not be determined by EDI system so EDI system used the counter '1' since it can not determine how many counters are already there in SAP and unless we pass the value to this counter field we were getting the error. After passing all the values the status of the IDOC is updated with the status '00' instead of '24' and we do not know why it is happened and I would like to know how SAP converts the status record that is received from the EDI system.
Please let me know how the status record will be translated into SAP from EDI system and I ahve followed basically EDIDS structure and the IDOC status is updating in SAP but with wrong status number and the alignemnt also missing in SAP fields like if I give some text in the EDI it is splitting and storing in 2 fields.
Please help me in this and I think I have explained the problem in a detail manner.
Thanks,
Ramesh.

Hi Naresh,
Thanks for the reply and my question is since EDI system is able to send the status back to SAP from EDI system and only problem is it is updatinf the status wrong and I have checked the EDIDS table also and the entry is creating with another counter and please confirm me that it is because of EDI does not support the status record update so that I can confirm to the client that there is nothing wrong in the way SAP functions and EDI system can not update the status code in the SAP.
Thanks,
Ramesh.

Application failed to return status record to ALE layer after Idoc procesed

Hi,
I am loading a full load to Product category (hierarchies) through process chain.
One of the load failed with the following error. The Idoc has status 51 in BW.
Can some suggest me the process for correcting this.
Thanks
No status record was passed to ALE by the application
Message no. B1358
Diagnosis
The application failed to return a status record to the ALE layer after the IDoc was processed.
This is due to an error in the application function module which processed the inbound IDoc.
Procedure
If you wrote the application function module yourself, you need to change the program.
If the function module in question is a standard application function module, you should consult SAP.

Hi
If this is standard code then you will have to write code to populate the status message in exit. But in case of custom code, the above mentioned solution is best (if coding logic is correct). I have given this solution to many queries and all worked.
Thanks
Anuraag

Error in idoc of basic type artmas05 - status 51 with Message no. MG537

Hi all,
I tried to upload the material master table through idoc creation of basic type artmas05. But when i'm trying to do that i'm getting status 51 with Message no. MG537. then I analysed the application log which displays the following
*The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required
field; it does not contain an entry
*The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry
*The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
*You have not fully maintained the tax classifications
*The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
But i hv given values for all the above fields in their respective segments.So can any1 suggest me how to proceed further.
It would be helpful if someone could tel me the required fields in idoc to upload material master table through idoc.
Thanks in advance,
Revathi.

Hi,
Anybody please tell me the reason for the following error, despite giving all the field values mentioned there. The same error occurs even if I run the BAPI (which the ARTMAS iDoc uses) directly by passing values.
The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required field; it does not contain an entry
The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry
The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
Regards,
Gowri.S

Status record 65 error in ale service

HI Experts,
               I have an issue when I tried to send a cost center idoc from one system to another. The company code for the record is 0093 in the sender system; however when the idoc gets created, in the idoc the value of the company code becomes SAH001. I dont know why this happens.
This is the record to in the corresponing table table- which is to be sent from sender to Receiver. The company code ie company code field value is 0093 .
The RFC/LS connections have been done and checked. I am able to send the cost center group data correctly. While sending the cost center I am encountering the following error:-
For an example
Content of created Idoc in sender
Company code field |   SAH001
The company code info is now SAH001. I wonder why ?
So when we send the idoc to recceiver, we get the same company code and I get an error that company code doesnt exist.
Content of idoc in receiver
Company code field |   SAH001
I want to display 0093.
Please tel me what is error and how to rectify?
Thanks & regards
Mathi

hI,
Testing inbound idoc :
Once you configured everything then goto WE19 Transaction :
Give message type or idoc type and execute .
now here you need to fill the Mandatory data in each segment,once you done then
idoc->edit control record -> here you need to fill sender and receiver details.
now you should get green color ,if you get red color then config issue.
now click on start inbound -> now you will get idoc number.
if you want to debug then click on inbound function module -> enter FM -> select call in debug mode and enter.
now cursor will go debug mode
http://www.photographybykevin.net/sap/idoc_overview.pdf
Testing Outbound idoc :
Once you done all configuration ..
Let me say example like invoice ,you need to send invoice from SAP R/3 to other system.
create invoice at VF01 -> Here customer should configure in Parter profile ,once you create invoice ,it creates the idoc.
debugging Outbound IDOC :
keep the break point in form routine above as i said
Create invoice or invoice list
when you maintain output type in invoice or invoice list -
Now click on Further data ->select peridoc scheduling-> back and save it.
Run RSNAST00 Program
Output application : V3
Object key : Invoice or invoice list number
Output type : RD00 or LR00
Medium = 6(EDI) ,A (ALE)
when you execute the program and it will goto debugging.
See the below status codes :
See table TEDS1 for all status codes via SE16 in SAP. Outbound ALE Status Codes
Successful Transmission:
03 - Successful outbound transmission
12 - Dispatch OK
IDoc being processed:
01 - IDoc created
30 - IDoc ready for dispatch (ALE service) (Program RSEOUT00 needs to be executed)
ALE Error Messages:
02 - Error passing data to port
04 - Error within control information on EDI subsystem
05 - Error during translation
25 - Processing despite syntax errors (outbound)
29 - Error in ALE service
32 - Resubmit edited intermediate document (DO NOT USE)
Syntax Error Messages:
26 - Error during syntax check of IDoc (outbound) Inbound ALE Status Codes
IDoc Processed Successfully:
50 - IDoc added
53 - Successful posting
IDoc ready for processing:
64 - IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.
Errors in IDoc Processing:
51 - Error - application document not posted
56 - IDoc with errors added (You should never see this error code)
60 - Error during syntax check of IDoc (inbound)
61 - Processing despite syntax error (inbound)
63 - Error passing IDoc to application
65 - Error in ALE service - indicates partner profiles are incorrect
69 - IDoc was edited
Regards,
Nagaraj

Outbound IDoc Error: Status Code 37 'Sender Port' is invalid

Hi
I have an Error when the Outbound IDoc is triggered.
It shows that 'Sender Port in Control Record is invalid'.
Status Code: 37.
I know that there are some issues with the Sender Port Definition.
Please help me out to solve this problem using some checkpoints at each and every step.
Reward Points Assured.
Regards,
Baburaj

Hi Baburaj Manickam
Good
Follow this simple procedure
1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
- Create File Port (WE21) for outbound file.
- Maintain Distribution Model (BD64) for sender ->receiver system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s).
_ Then you can FTP the file(s) to receiver system.
2) Upload the flat file as an IDOC on the inbound sytem
which is Client2(RECIEVER).
- Create File Port (WE21) for inbound file.
- Maintain Distribution Model (BD64) for receiver -> sender system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RSEINB00 to upload IDoc MATMAS file(s).
INBOUND IDOC PROCESSING:
Firstly attach your idoc to a process code.
In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
2. Set Function Modules as Inbound: - Transaction BD51
3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
4. Create process codes : Transaction WE42, and link the z-function module.
5. Create partner profile: transaction WE20 and attach the message type and process code.
6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
Try the Trasaction WE19 for testing your inbound and outbound IDOCs
Good Luck and Reward me for the same
Thanks
Ashok.N

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

Similar Messages

Maybe you are looking for