A Single Mistake Can Cost You $$$$$

IDOC, Mike Salvo, RBDMIDOC, SAP

Posted by ccampbell on July 9, 2009 · Leave a Comment

While working with a client on developing EDI-856 transactions with one of their trading partners, an error occurred that cost my client thousands of dollars in charge back fines.

In their SAP environment they produce a single DESADV IDoc per order/purchase order.  This could amount to several hundred DESADV IDocs being generated.  The initial development was a 1 to 1 translation in that each DESADV IDoc that was produced would be translated into a single EDI-856 document.

Because of a single data error, due to department procedures not being followed in the warehouse in the closing of orders, the bad data element resulted and was repeated throughout all of the DESADV IDocs that were generated.  Translation of the IDocs was successful because this error was not conceived at the point of map development.  The hundreds of translated documents were sent to the trading partner and subsequently resulted in failed documents.

Because the trading partner generated a charge back for each document sent, my client was billed thousands of dollars in charge back fines.  This simple example shows how a single error repeated in each document can turn out to be a very costly problem.

I hope to show you in the next few postings how to bundle the IDocs together to:

• Bundle and reduce the number of IDocs being translated
• Reduce the number of EDI documents being sent to the trading partner
• Minimize the charge back cost, should and error occur

Changing SAP IDOCs Status In Mass / Mass Deletion Of IDOCs

Posted by Tim Yates on Wednesday, October 7, 2009 · Leave a Comment

Mass Change of SAP IDOC Status

From time to time it becomes necessary to change the status of SAP IDOCs in SAP. The most common scenario is the requirement to mark SAP IDOCs for deletion. There is no good way to mass mark IDOCs for deletion via the standard IDOC processing transaction BD87. However there is a program that will let you change status.

RC1_IDOC_SET_STATUS

CAUTION: This program should be used with great care and consideration. Improper use of this program can result in data consistency issues. Make sure you know what you are deleting, why you are deleting it, and what is required to correctly update you system after deleting.

Example: Marking IDOCs for Deletion In Mass

It is pretty typical for support users to set the deletion flag on IDOCs that have been incorrectly created and have errored. When there are a small number of IDOCs this is possible via transaction BD87.

An inbound IDOC in error will have the status 51, when it is marked for deletion it has a status of 68.

A view of the IDOCs to be deleted in WE05.

To mass delete IDOCs run the following program via SE38: RC1_IDOC_SET_STATUS via the SAP Transaction: SE38

There are only a few parameters on the selection screen for this program. It is most important that you correctly restrict the IDOCs you select with this program. The program automatically defaults to marking inbound IDOCs in error for deletion.

To mass select IDOCs to be marked for deletion select:

There are many options for selecting and restricting the IDOCs to Mass process. Select by single value or range. Restrict by single value or range.

The allows you to upload a list of IDOCs from a text file.

The allows you to apply a list from your clipboard.

Execute the program

Check the status of the 3 IDOCs in WE05

Example: Changing IDOCs Status To Repost

It is also possible to use this program to reset an IDOC so that it can be reprocessed.

With the following selection we are going to reset the IDOCs with status 68 marked for deletion back to status 64 to try and reprocess them.

Execute the program

As you can see, program RC1_IDOC_SET_STATUS is very helpful, but please be careful when you use it!

About Tim:

Tim has over 20 years industry experience, with 15 years concentrated on SAP and related technologies. He has broad industry exposure working with companies such as Siemens Automotive, Mercury Marine, SAP America, Eli Lilly & Company, and Verizon. Tim’s deep understanding of SAP and the industry comes from a very hands on approach. His concentration in SAP has been in systems architecture and integration, helping companies develop their infrastructure and controls to successfully integrate SAP into their existing IT landscape.

Notes in MM-PUR

List of most important notes in MM-PUR

MM-PUR

30316 Problems with fields that are not ready for input in purch.



MM-PUR-GF-ACC

496082 FAQ: Account assignment in purchasing

627072 ME21N: incorrect account assignment on cost center

551863 ME21N: Accnt assignment not derived for required entry field



MM-PUR-GF-ADR

498153 FAQ: Addresses in the purchasing

821981 Change in Vendor Address in PO updates Vendor Master address

422641 ME21N, ME22N:



MM-PUR-GF-ARC

456129 FAQ: Archiving in purchasing

401318 Archiving: Additional information

335800 SARA: Deletion indicator not set, but why?



MM-PUR-GF-REL

365604 FAQ: Release strategies in purchasing

493900 FAQ: Release Strategy

86900 Transport of Release strategies (OMGQ,OMGS)



MM-PUR-GF-ARL

499625 FAQ: Optical archiving in purchasing

732278 Display of Originals does not work for archived documents

ABAP Development Workbench Basics

SAP_Siemens -

SAP-MASS-CHANGE-by-Mohamed-Hasan-RifaieM

SAP MASS CHANGE by Mohamed Hasan RifaieM -

SAP MASS CHANGE By M. Mohamed Hasan Rifaie

SAP MASS CHANGE by Mohamed Hasan RifaieM

Dr. Edward de Bono - Edward de Bono Foundation UK