EKES sapnote_0000544896

18.02.2013 Page 1 of 2 SAP Note 544896 - Inbound delivery does not exist in transaction MD04 Note Language: English Version: 7 Validity: Valid Since 20.07.2011 Summary Symptom In the stock/requirements list (transaction MD04), there is an inbound delivery that cannot be accessed using the inbound delivery processing transactions (VL32, VL33, and so on). Alternatively, the inbound delivery may exist but the corresponding delivery item does not exist. Other terms Material planning Reason and Prerequisites The origin of the inbound delivery is unclear. There are no goods movements for the inbound delivery. Alternatively: It is unclear where the deleted (?) delivery items are. No goods movement was posted for them. Solution Download the correction report ZDELEKES from the correction instructions and execute the report. If the inbound delivery exists but individual delivery items do not exist, you must delete the following four lines from the correction report: SELECT SINGLE * FROM LIKP INTO WA_LIKP WHERE VBELN = T_EKES-VBELN. CHECK SY-SUBRC NE 0. SELECT SINGLE * FROM VBUK INTO WA_VBUK WHERE VBELN = T_EKES-VBELN. CHECK SY-SUBRC NE 0. If the inbound delivery was archived but entries still exist in the purchase order history (table EKBE), you can use the report variant ZDELEKES2 contained in the correction instructions. Header Data Release Status: Released for Customer Released on: 20.07.2011 14:15:51 Master Language: German Priority: Correction with medium priority Category: Program error Primary Component: MM-PUR-GF-CON Confirmation Control/Shipping Notification Secondary Components: PP-MRP Material Requirements Planning LE-SHP-DL Delivery Processing LE-SHP-DL-LA Inbound Delivery Valid Releases

Upload
murthy-magapu
Category

Documents
view
110
download
2

Embed Size (px):

description

SAP NOTE FOR EKES TABLE ENTRY CORRECTIONS. IMPLEMENT

Transcript of EKES sapnote_0000544896

18.02.2013 Page 1 of 2

SAP Note 544896 - Inbound delivery does not exist intransaction MD04

Note Language: English Version: 7 Validity: Valid Since 20.07.2011

Summary

SymptomIn the stock/requirements list (transaction MD04), there is an inbounddelivery that cannot be accessed using the inbound delivery processingtransactions (VL32, VL33, and so on).Alternatively, the inbound delivery may exist but the correspondingdelivery item does not exist.

Other termsMaterial planning

Reason and PrerequisitesThe origin of the inbound delivery is unclear.There are no goods movements for the inbound delivery.

Alternatively: It is unclear where the deleted (?) delivery items are. Nogoods movement was posted for them.

SolutionDownload the correction report ZDELEKES from the correction instructionsand execute the report.

If the inbound delivery exists but individual delivery items do not exist,you must delete the following four lines from the correction report: SELECT SINGLE * FROM LIKP INTO WA_LIKP WHERE VBELN = T_EKES-VBELN. CHECK SY-SUBRC NE 0. SELECT SINGLE * FROM VBUK INTO WA_VBUK WHERE VBELN = T_EKES-VBELN. CHECK SY-SUBRC NE 0.

If the inbound delivery was archived but entries still exist in thepurchase order history (table EKBE), you can use the report variantZDELEKES2 contained in the correction instructions.

Header Data

Release Status: Released for CustomerReleased on: 20.07.2011 14:15:51Master Language: GermanPriority: Correction with medium priorityCategory: Program errorPrimary Component: MM-PUR-GF-CON Confirmation Control/ShippingNotification

Secondary Components:PP-MRP Material Requirements Planning

LE-SHP-DL Delivery Processing

LE-SHP-DL-LA Inbound Delivery

Valid Releases