Scribd
Upload
124 views4 pages

Handling Open Data Extraction Errors

SAP Note 1083709 addresses an error encountered when importing support packages in SAP Business Warehouse, specifically related to open data extraction orders. It outlines the necessary steps to process these orders to prevent data loss during the import, including creating a report and executing various transactions. The note also provides troubleshooting guidance for specific error messages and emphasizes the importance of performing these actions during system downtime.

Uploaded by

Mitchel Neyra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
124 views4 pages

Handling Open Data Extraction Errors

SAP Note 1083709 addresses an error encountered when importing support packages in SAP Business Warehouse, specifically related to open data extraction orders. It outlines the necessary steps to process these orders to prevent data loss during the import, including creating a report and executing various transactions. The note also provides troubleshooting guidance for specific error messages and emphasizes the importance of performing these actions during system downtime.

Uploaded by

Mitchel Neyra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

SAP Note

1083709 - Error when importing support packages


Component: BW-BCT-LO-LIS (SAP Business Warehouse > BW only - Business Content and Extractors > BW
only - Logistics - General > BW only - Logistics Information System), Version: 8, Released On: 24.04.2023

Symptom
When you use transaction SPAM to import a Support Package or transaction SAINT for an
installation, the system issues the following error message in the CHECK_REQUIREMENTS phase.
Open data extraction orders
You notice that there are still open data extraction orders in the system. You want to
process these before the start of the object import because changes to the ABAP Dictionary
structures could lead to data extraction orders not being able to be read after the import
and their processing terminating. For more details about this problem, see Note 328181.
Go to the Customizing cockpit for data extraction and start the processing of all open
extraction orders.

Other Terms
CHECK_REQUIREMENTS, 328181, SPAM, SAINT, LBWE, LBWQ, LBWG, SMQ1, SM13

Reason and Prerequisites


Importing Support Packages may cause changes to the structures of the logistics data
extraction. To prevent data being lost by the changes, you must first process all the 'data
stores' (tables, queues, updates) that provide logistics data for the extraction.
This note should help you to diagnose the steps you need to carry out.

Solution
Call transaction SE38 and create a new report with the name RMCEXCHK. Delete the lines that
are automatically generated here, including the REPORT statement.

Maintain the following text symbols for the report:

001 Check for unprocessed logistics extraction data

002 No open V3 updating requests found.

003 Open V3 updating requests found!

004 No queue entries for logistics extraction found.

005 Unprocessed queue entries for logistics extraction found!

006 No data in setup tables for logistics extraction found.

007 Check found data in setup tables for logistics extraction!

008 No data in buffer MC12_PUFFER found.

009 Check found data in buffer MC12_PUFFER!

Then implement the attached source code.

The report gives you an overview of the steps that you still need to carry out for the
logistics data extraction.
Note that this processing must take place during system downtime because otherwise the
different objects will be immediately filled with data again.

Here are some detailed descriptions of how you should proceed for the individual error
messages:
MCEX 140 "Struct. from appl. &1 due to open V3 proc. not changed -> Long text": This
means that logistics extraction data still exists in the update. Procedure:
Normally, there should only be V3 update entries for application 03.
Call transaction LBWE in all productive clients of the system.
For application 03, choose the "Job Control" link in the "Update" column.
Plan a job with the start date "Immediate".
If the system still issues message MCEX 140 after you have carried out all these steps and
all scheduled jobs have run and you have executed check report RMCEXCHK again, this may be
due to inconsistencies in the update tables. In this case, remove the inconsistencies as
described in Note 67014.
MCEX 151 "Entries for application &1 still exist in the extraction queue ->": This means
that logistics extraction data still exists in the MCEXnn outbound queues (nn =
application number). Procedure:
Call transaction SMQ1 and select using the following parameters:

Client *

Queue Name MCEX*

Queue Destination *

Waiting Queues Only

Create a list with the listed clients and application numbers.


Call transaction LBWE in all listed clients.
For each of the applications listed under the respective clients, choose the "Job
Control" link in the "Update" column.
Plan a job with the start date "Immediate".
If the system still issues message MCEX 151 after you have carried out all these steps and
all scheduled jobs have run and you have executed the check report RMCEXCHK again, this may
be due to blocking queue entries.
Note 835466 describes various options for dealing with blocked queues that have an
application-specific cause.
MCEX 141 "Struct. from appl. &1 cannot be changed due to setup table -> Long text": The
system issues this message if data for the logistics extraction still exists in the
setup tables. Procedure:
Make a note of the application numbers displayed.
Call transaction LBWG for each application and delete the contents of the respective
setup tables. This deletion should affect all clients. (for 2LIS_02_SRV : SE14 -
> MC02M_0SRVSETUP. SAP Note 2003744)
MCEX 149 "Entries still exist in system &1 in the table MC12_PUFFER ->": This means that
logistics extraction data still exists in the table MC12_PUFFER of at least one client.
Procedure:
Call transaction LBWE in all productive clients of the system.
For application 12, choose the "Job Control" link in the "Update" column.
Schedule a job with the start date "Immediate".

To reduce the downtime required, we recommend that you execute check report RMCEXCHK during
the normal production time (shortly before downtime) and that you process the messages
accordingly.
This reduces the data volume that has to be processed during the downtime. In addition, you
can find any problems early on.

Attributes
Key Value
Other Basis Components > Upgrade - general > Upgrade Add-On Components (BC-UPG-ADDON)
Components

Other Basis Components > Upgrade - general > Online Corr. Support (Tools:Supp.-Pack., Addon Install/Upgr) (BC-
Components UPG-OCS)

Software Components
Software Component From To

SAP_APPL 600 600

SAP_APPL 602 602

SAP_APPL 603 603

SAP_APPL 604 604

SAP_APPL 605 605

SAP_APPL 606 606

SAP_APPL 616 616

SAP_APPL 617 617

PI 2004_1_46C 2004_1_500

Correction Instructions
Software Component Number of Correction Instructions

SAP_APPL 1

PI 1

Support Package
Software Component Version Support Package

PI 2004_1_46C SAPKIPZI4F

PI 2004_1_470 SAPKIPZI5F

PI 2004_1_500 SAPKIPZI6H

SAP_APPL 600 SAPKH60011

SAP_APPL 602 SAPKH60201

This document refers to


SAP Note/KBA Component Title

1597645 BW-BCT-LO-LIS

1285994 BW-BCT-LO-LIS LBWG/appl. 04: Not all setup tables are deleted

1137564 GRC-SAC Open Data Extraction Request errors with GRC RTA/Plug-ins

1081287 BW-BCT-LO-LIS Data extraction orders are blocking the upgrade process

835466 BW-BCT Using the repair mode of the hash solution

640066 BW-BCT-LO-LIS Upgrade: Return code 6 with XPRA RMCSBWXP_COM

328181 BW-BCT-LO-LIS Changes to extract structures in the Customizing Cockpit

67014 BC-CST-UP Reorganizing update requests

This document is referenced by


SAP Component Title
Note/KBA
3334069 How to check logistic setup tables in the CHECK_REQUIREMENTS phase when using SPAM to
import a Support Package or SAINT for an installation

2387875 BW-BCT-LO-LIS Short dump MESSAGE_TYPE_X in SAPLMCEX - error MCEX194

1597645 BC-UPG-TLS- Check of SPs for relevance for logistics extraction


TLA

1137564 GRC-SAC Open Data Extraction Request errors with GRC RTA/Plug-ins

328181 BW-BCT-LO-LIS Changes to extract structures in the Customizing Cockpit

835466 BW-BCT Using the repair mode of the hash solution

67014 BC-CST-UP Reorganizing update requests

1285994 BW-BCT-LO-LIS LBWG/appl. 04: Not all setup tables are deleted

1081287 BW-BCT-LO-LIS Data extraction orders are blocking the upgrade process

941112 XX-PART- KVsprint 4.600: Installation/Upgrade


KVSPRINT

640066 BW-BCT-LO-LIS Upgrade: Return code 6 with XPRA RMCSBWXP_COM

Common questions

Powered by AI

Inconsistencies in update tables can lead to failure in processing data extraction orders even after executing required tasks. Such inconsistencies may result in persistent error messages like MCEX 140, indicating that logistics extraction data remains unresolved. To address these, inconsistencies must be removed as described in Note 67014, ensuring smooth continuation of the import process .

Executing the check report RMCEXCHK before system downtime is important because it identifies pending logistics extraction data and processes it, reducing the data volume that needs to be handled during the limited downtime period. This proactive approach also allows early detection of potential issues, minimizing disruptions during the actual import .

Immediate job scheduling for handling extraction queue entries, as recommended for issues like MCEX 151, ensures that data blockages are promptly addressed. This rapid response minimizes disruptions by quickly clearing queue backlogs, aiding ongoing data processes and maintaining system performance during data extraction tasks .

Unprocessed logistics data in buffer MC12_PUFFER can lead to errors during Support Package imports due to existing data preventing orderly updates and potential loss of critical data. To mitigate this, scheduling immediate jobs using LBWE in productive clients is necessary to clear the buffer, allowing for a clean import process .

Data existing in setup tables prevents changes to logistics extraction application structures, triggering error messages like MCEX 141. The presence of such data suggests unresolved logistics extraction processes that must be addressed by deleting setup table contents using transaction LBWG for each relevant application, allowing structural updates .

Transaction LBWG is used to manage SAP logistics extraction data by facilitating the deletion of contents within setup tables linked to specific applications. This is necessary when error messages like MCEX 141 arise, indicating unresolved data in setup tables that hinder structural changes in the system .

To create and use the report RMCEXCHK, a new report must be generated in transaction SE38 without default code. Specific text symbols are defined, and the provided code is implemented. This report then assesses pending logistics data processes across tables, queues, and buffers, guiding the user through resolving the detected issues before continuing with Support Package imports .

Processing open data extraction orders before importing a Support Package is crucial because changes to the ABAP Dictionary structures during the import could prevent data extraction orders from being read, leading to their processing being terminated. Therefore, it is necessary to clear these orders to avoid potential data loss and inconsistencies .

Blocked queue entries during logistics data extraction should be managed by following the procedure outlined in Note 835466, which recommends options such as using repair modes specific to application-caused blocks. This involves scheduling jobs immediately to clear blockages and using tools like transaction LBWE to manage the identified application queues .

SAP Note 835466 is applicable where blocked queues result from application-specific causes during data extraction processes. It guides problem resolution by describing repair modes for unblocking these queues, ensuring that extraction backlogs are cleared and structural updates can proceed without disruptions .

You might also like