Why idoc status 62

The views expressed in this email are not necessarily the views of Vision Express. Vision Express operates an Information Technology Usage Policy and reserves the right to monitor both internal and external e-mails within the limits prescribed by legislation.

By reading this notice you will have deemed to have consented to the monitoring of your e-mail and to Vision Express holding personal data for monitoring purposes. This email message has been swept by MIMEsweeper for the presence of known computer viruses.

Have you tried processing each IDoc in turn through WE19? Could you please tell me what function module you are using to post idoc. I can see a time issue in updating the idoc tables.

What causes this Idoc status? We receive orders from a trading partner but all of their Idocs sit in status 64 until the file is manually processed. When the Idoc is manually processed, a pop-up screen wants a selection of the sold-to partner.

We have multiple sold-to partners set up for this customer. Also, sometimes when I have an unusually large amount of idocs processing through, they will go to status 64 and I have to use the BD87 function. If the idoc is at status 64 that means the initial import and save of the idoc on the database was successful, which means that there were no structural defects in the idoc and there was a partner profile that exactly matched the incoming partner customer number and logical message type idoc.

If they stayed at 64, as Chris indicated, the partner profile was set to Collect idocs rather than Process immediately.

This is generally automated through a variant and a scheduled job. The Orders are then posted via BDC session, which mimics in background the manual creation of an order.

The question I would ask about your problem is what is the partner type of the partner in the idoc? Is it a sold-to partner or a ship-to, bill-to or some other partner type that may be linked to multiple sold-tos in table KNVP?

As of this week we are experiencing the same issue. Over the weekend we had an SAP shutdown in order to upgrade our disk system. Any ideas? First check the partner profile. Is it set to Trigger by background program or Trigger immediately?

Please respond to sap-interfaces Gr oups. Embedded image moved to file: pic Posted by ruther Sr. No Account? Sign up. By signing in, you agree to our Terms of Use and Privacy Policy. Already have an account? Sign in.

By signing up, you agree to our Terms of Use and Privacy Policy. Enter the email address associated with your account. We'll send a magic link to your inbox.

Email Address. All Sign in options. Enter a Email Address. Choose your interests Get the latest news, expert insights and market research, sent straight to your inbox. Newsletter Topics Select minimum 1 topic. Enterprise Software. Afterwards, check the workflow Customizing in transaction SWU3. So I changed the user, it fixed the problem. These blogs are timeless! An analysis well done is always a helpful document for the community. Skip to Content. Tuncay Karaca. June 22, 3 minute read.

If this happened you will see a trace in the system log ST Alert Moderator. Alerting is not available for unauthorized users. Assigned Tags. Similar Blog Posts. Related Questions. You must be Logged on to comment or reply to a post. Kumud Singh. Regards, Kumud. Like 0 Share.