How to debug extraction a datasource in ecc starting execution in bw ?

HI gurus,
how to debug extraction a datasource in ecc starting execution in bw ?
Thanks.

Hi,
In your issue i thick data source trace in BW is not possible but RFC is the main criteria here if it is correct data will comes to the bw automatically when ever info package triggers.
If you need to check the data source data in trace mode and it is not coming properly, then we need to check from RSA3 by executing with debug mode check box option.
Still need any clarification let me know.
Thanks & Regards,
Srinu.Rapolu

Similar Messages

How to debug LAE function modules in ECC

Hi,
I've been trying to debug sequence of FMs called by LAE during asset creation in ECC. The asset is created for every service contract created in SAP CRM and then replicated to ECC system. While debugging the flow from CRM, I could debug upto ECC and then put external breakpoing in LAE FMs mentioned above but those FMs were not hit.
LAFA_ASSETS_CREATE_ON_LEASE
LAFA_ASSETS_CREATE
LAFA_ASSET_CREATE
LAFA_ASSETS_RETIRED_GET
Could anybody help me debugging these FMs?
Regards,
Ravi

Hi Ravi,
this process works asynchonous. This means from CRM some entries are stored in LAE_CRM* tables with function module FILA_BUS_TRANSACTION_RECEVIE. A triggered function picks up the entreis and process them. This function runs through your mentioned function modules.
In a test system, you can call transaction FILATEST and copy the contract sent from CRM and using the simulation or execution function. This will bring you to these function modules.
Kind regards,
Steve
Edited by: Steve Trester on Mar 1, 2011 8:13 AM

How to debug a function module using in the generic datasource?

Hi all,
We have created a generic data source using function modulle and have been extracting the data for a single customer it contains single records but it has pulled out more than 10,000 records. how to debug the function module used in the data source.
since we schedule for extraction in bi and back ground job gets triggered in ecc for extraction,
i know in se37 we can select the function module name and then debug but still need to check while the bacground job is trigered through bi.
Thanks

Yes you can debug the Function Module.
Open the function module in SE37 and put a break point in the code where you want to check from, then come to RSA3 and give the datasource name and check the Debug check box on this screen, once you click on the start button it will take you the place where you have placed the break point in the FM, by pressing F5 you can see the flow of the FM.
Let me know whether this solves your issue.

How to debug mapping function module during delta extraction?

Hi experts,
Somehow our delta is not working properly, and i would like to debug our mapping function module. How can i debug it during a delta extraction?
Some info:
Our source system is CRM and our extractor is extracting one order document (contracts in this case). I know that when we modify a contract, a bdoc is generated and then passed throught the mapping function then the extracted data to the delta queue. I just need to debug when the bdoc is being mapped to see what's wrong with the extracted data.
Thanks in advance,
Van

Hi,
Since you are using a Function Module for the Extraction. Edit the Function Module and give "BREAK-POINT" before the loop command. Check and activate the Function Module.
Now Extract the datasource using RSA3. Now you can debug it. After checking remove the "BREAK-POINT" from the function module. Also Check and activate the same.
Regards
Jayaram M

Changes are not updated from ECC to CRM How to debug

Hi,
QCs 1140049726 and 1140047459 were updated in P20 system to remove the WBS. This was done per normal P20 process and instructions. P20 system correctly reflects that QCs have no WBS value and the contracts are BOX - all is correct in P20.
CSP still shows these QCs as having a WBS assigned to them. This is incorrect. It has been over 24 hours since the P20 QCs were changed to reflect no WBS, but CSP still has not been replicated with the correct data.
How to proceed with it. How to debug from ECC to CRM.
Prem.

Hello Prem,
Could you please have a look at SAP note 656823?
This note contains debug tips for btx data transfer. Please check point 6 which talks about the delta download.
Hope this could be helpful.
Best regards,
Maggie

How to debug a failed shopping cart transfer to ECC in classic mode

Hello,
I am using SRM 5 in classic mode, connected to ECC 6.0.
I have an error message in the administrator monitor that tells me a transfer a shopping cart to ECC has failed.
"Shopping cart 1000000123: Error creating the follow-on document"
(Message is BBP_PU 367)
This is located in the "local errors" section of the administrator monitor.
The follow on doucment will be a PO in ECC.
This message does not tell me the cause of the problem therefore I need to retrnsmit the cart and debug to find the error message that is being returned from ECC.
I have browsed the forum and there are various answers about debugging but but have not found exact instructions on how to debug, and it is now always clear on whether the instructions apply to classic or extended classic.
I have seen reference to the method in note 539978 that creates test data with FBGENDAT for the ECC BAPI. However this method does not seem suitable for a production system because it will interfere with all shopping carts being transferred while the shoppign cart with the problem is being debugged.
Therefore I would like to debug in SRM just for the shoppign cart with the problem.
Hopefully this thread will become the defintiive poitn of reference for debuggin a classic shopping cart transfer to ECC in SRM 5.
I propose to use function module BBP_PD_SC_TRANSFER to transfer the shopping cart again by entering the shopping cart GUID.
Question 1) Can this error message be returned by checks in SRM before the BAPI is called in ECC? If so, where do I place a breakpoint to find the error determined by the checks in SRM?
Question 2) If the system is getting as far as calling the BAPI in ECC, is it possbile to find the error message passed back from ECC by this approach, given that the actual transfer is carried out by the spooler?
Question 3) If this approach is valid, in which method/function module do I need to place a breakpoint, at which statement is the error message passed back to SRM from ECC?
Your help would be appreciated,
Reagrds

Hi Paul,
a small correction to Dishas comment:
The class CL_BBP_BS_ADAPTER_PO_CRT_470_1 is used for the backend release 4.7, so it is not relevant for you. Instead of this, you have to take the CL_BBP_BS_ADAPTER_PO_CRT_ERP10 and method CREATE_DOCUMENT. This is the last step, before the SRM calls the backend system.
From the alert "local errors" I suppose, that there is an error in the SRM customizing (in case the error message comes from the backend system, you get the message into the "Backend Application error").
Typical customizing error, when e.g. the number range of the purchase REQUISITION is not correctly customized (in case the prerequisits for a PO are not fulfilled, the system tried to create a purchase requisition). See the note 1173815 regarding this problem.
Back to your questions:
The activating of the FBGENDAT was a good idea, but I would give here two hints:
- I case of production system you can use only the "Mode B".
- Activate the FBGENDAT only for a short term:
-- at first set the breakpoint in the method CREATE_DOCUMENT (as above described)
-- execute the BBP_PD_SC_TRANSFER
-- you will be stopped at the breakpoint.
-- Now you can activate the FBGENDAT in the backend
-- go on with F8 in the debugger in the SRM system
-- >>> test data will be filled in the backend system (BAPI_PO_CREATE1)
-- deactivate the FBGENDAT
You can do this in one min. and the worst what can happen is that you have 2-3 test data in the BAPI_PO_CREATE1 additionally to the erronous SC.
Question 1) Can this error message be returned by checks in SRM before the BAPI is called in ECC? If so, where do I place a breakpoint to find the error determined by the checks in SRM?
- Maybe... Places for setting breakpoints
-- FM "BBP_PD_MSG_ADD"
-- System command "RAISE"
-- FM "META_BAPI_DISPATCH" (typical problem, see above, and also the note 1173815)
Question 2) If the system is getting as far as calling the BAPI in ECC, is it possible to find the error message passed back from ECC by this approach, given that the actual transfer is carried out by the spooler?
- Yes, you can find the message in the:
-- Test data of the BAPI_PO_CREATE1, if you have activated the FBGENDAT
-- In the method CREATE_DOCUMENT if you "comes back" from the RFC call from the backend
Question 3) If this approach is valid, in which method/function module do I need to place a breakpoint, at which statement is the error message passed back to SRM from ECC?
- see above, CL_BBP_BS_ADAPTER_PO_CRT_ERP10 method CREATE_DOCUMENT
Kind regards,
Peter

How the data extraction happens from HR datasources from R/3 to BW system.

Hello All
How the data extraction happens from HR datasources from R/3 to BW system.Incase of delta records ( for CATS datasources ) ,Is there any flow like LO .
Incase of Full and delta loads how does the data will be taken from R/3 to BW,DO we need to fill setup tables ?
Searched forum but couldnt able to find the relevant one.
Thankyou
Shankar

Hi Shankar.
HR Datasources do not have setup tables . Though before implementation, certain customizations should be done and the delta loads have dependency on other data sources. Also you must have implemented Support Package SAPKH46C32, or have made the relevant corrections in SAP Note 509592.
Follow this link for details on customization and dependencies for all CATS datasources.
http://help.sap.com/saphelp_nw70/helpdata/en/86/1f5f3c0fdea575e10000000a114084/frameset.htm
Regards,
Swati

PI-ECC connection (IDOC scenario), how to debug? (External BP)

Hello everybody,
In PI -> ECC IDOC scenario I have encountered a debugging problem
Delivery IDOC is being sent from PI to ECC.
It is processed with IDOC_INPUT_DELVRY FModule.
The question is how to debug this communication?
I try to set external breakpoint in IDOC_INPUT_DELVRY with the user I can see in IDOC processing log
(IDOC Status details -> 'Logging' tab -> 'Message from' section -> 'User name').
This user is used to serve communication with PI.
User is set as dialog and has debugging rights
When I trigger communication from PI - IDOC is sent but debugger does not popup
Is my debugging approach incorrect?
I would appreciate every comment on this.
Kind Regards,
P.

Pothana Yadav
Thanks a lot for reply!
What do you mean by checking at Master_Idoc level?
I am setting a BreakPoint in IDOC_INPUT_DELVRY FModule at the very beginning. Also tried to set BP insidy my BAdi method (which is for sure being call during communication).
Or maybe you know some other way how to debug such IDOC communication triggered from PI into ECC?
I know I could use 'endless loop / sm50' trick but then I need to transport source code, which in case of Production is not feasible.
Regards,
P.

How to extract retail datasources please describe clearely

how to extract retail datasources please describe clearely

Dear,
http://help.sap.com/saphelp_nw04/helpdata/en/39/e531c93747da4a8806612212b013b4/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/8e/65f438c842cc2be10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/86/39d6386e24f90ae10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/35/e58282fe8711d3b49f006094b9301e/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/73/d26594107711d4af1e080009d2232d/content.htm
Also check in:
www.service.sap.com/bi -->>solution detail -->>Industry Portfolios -->> Sap Retail
Thanks

How to debug Delta records..urgent

Hi All,
I loaded some records with delta mode.
In rsa3, I select delta mode D, and clk Excute button, But It is saying "Error During Execution".
A. What is the reason Can any one explain?
B. How to Debug my delta records?
Pls explain Urgent.
Thanks & Regards,
Lakshmi.K.

Hi,
in case of simulation of update mode D you also have to provide the name of your target system. Then check the box debug mode. After clicking the execution button you are in the coding right before the extraction fm gets called. Jump into in by pressing F5 ....
But first of all you need to make sure that your datasource provides a delta (this may cause the 'error during execution').
regards
Siggi

How to handle the Timestamp datasource while migration

Hi All
" I tried searching the forum,but didnt get the relevant one,hence posting this question".
While migration from 4.7 to ECC in R/3 system,
how to handle the Timestamp datasources( especially FI like COPA and other ) while extarcting the data from source to BW during source system migration.Since we need to empty the delta queue and should make sure that there are no delta records exists in delta queue.
Like for sales datasources using LO,we will be executing the V3 jobs for execting the LUW's from LBWQ to RSA7? In the same way is there any particular way for this also.
Anyone whi knows abt this pls share your views
Regards
Shankar

Hello Shankar.
Before the upgrade (import of a queue), all extraction queues and open
update orders in all clients must be processed. The content of the setup
tables must be deleted. To avoid problems during the upgrade or to
correct them, carry out the following steps:
1. Call transaction SMQ1 and check whether all queues in all clients
(client = '', queue name 'MCEX') have been processed. To process the
queues, start the collective run report for each application in the
displayed clients. If you no longer need the data in the BW system,
deactivate the relevant extraction queues and DataSource in the LO
cockpit (transaction LBWE) and delete the queue entries in transaction
SMQ1.
2. If you use the V3 update that is not serialized (usually only for
application 03): Start collective run report RMBWV303. Then check the
update orders in transaction SM13. If there are incorrect update orders
in transaction SM13, correct the orders and then start the collective
run report again. If you no longer require the update orders, you can
delete them. There may be inconsistencies between tables VBMOD and
VBHDR. For further information about this, see Notes 652310 and 67014.
3. Before the upgrade, delete the contents of the setup tables. Execute
report RMCEX_SETUP_ENTRIES to find out which setup tables still contain
entries. You can use transaction LBWG to delete the contents of the
setup tables for all clients.
Unfortunately the check that the system carries out during the upgrade
or when you import a Support Package does not display all affected
applications. Therefore, Note 1083709 provides a check report that you
can use to determine all affected applications and tables or queues.
More detailed information please check these following notes:
1083709-Error when you import Support Packages
1081287-Data extraction orders block the upgrade process
I hope I can be helpful.
Thanks,
Walter Oliveira.

0PM_CATIND & 0PM_PLANIND where is text datasource in ecc,0PM_OPER install

dear friend,
I have 0PM_CATIND - Maint.Orders Category Indicator and 0PM_PLANIND - Maint.Orders Planning Indicator in BI, where to find its text datasource in ECC, i havent found in ECC rsa5, is such text datasource required to create?
2) I have 0PM_OPER - Operation Number for PM is new master Infoobject in PM where Maintanance order is compound,
I have install it but it installed only with infoobject not any attribute or trasferrule or updaterule, Is it required to do manually mapped with any datasource? or required to copy its attribute from other master infoobject attribute?
if anybody have workerd already on this Info object.
Thanks
Dushyant.

could you explain how help.sap was of help? and also, what is the name of the extracter is RSA5 that you linked them to?
thanks for you help. i am having the same issue.

How can I extract maetrial condition (ME13)

Hi,
I need to extract data from transaction ME13, this transaction has any entries for validity periods of price and tax .
Anybody konws how can I extract all validity periods of this conditions?
Thanks,
Cesar G. Batista

The Master Data Attribute DataSource 0INFO_REC_ATTR may have most of what you require for Purchasing Info Record header data from R3/ECC table EINA. It definitely provides the validity period (EINA-LIFAB and EINA-LIFBI). Tax can be different for each Info Record, Plant, Purchasing Org combination (R3/ECC table EINE). In the end, you may have to create a generic DataSource for the EINE data.
Also take a look at 2LIS_02_S012 too.

Unable to extract the data from ECC 6.0 to PSA

Hello,
I'm trying to extract the data from ECC 6.0 data source name as 2LIS_11_VAHDR into BI 7.0
When i try to load Full Load into PSA , I'm getting following error message
Error Message: "DataSource 2LIS_11_VAHDR must be activated"
Actually the data source already active , I look at the datasource using T-code LBWE it is active.
In BI on datasource(2LIS_11_VAHDR) when i right click selected "Manage" system is giving throughing below error message
"Invalid DataStore object name /BIC/B0000043: Reason: No valid entry in table RSTS"
If anybody faced this error message please advise what i'm doing wrong?
Advance thanks

ECC 6.0 side
Delete the setup tables
Fill the data into setup tables
Schedule the job
I can see the data using RSA3 (2LIS_11_VAHDR) 1000 records
BI7.0(Service Pack 15)
Replicate the datasource in Production in Backgroud
Migrate Datasource 3.5 to 7.0 in Development
I did't migrate 3.5 to 7.0 in Production it's not allowing
When i try to schedule the InfoPakage it's giving error message "Data Source is not active"
I'm sure this problem relate to Data Source 3.5 to 7.0 convertion problem in production. In Development there is no problem because manually i convert the datasource 3.5 to 7.0
Thanks

How To: Debug missing Drivers in MDT

The definitive post on missing drivers in MDT (most comprehensive list I've done so far)…
Please to NOT post questions from this thread, instead create a new thread.
How to debug Network Driver Problems
One of the earliest hurdles an MDT administrator will come across is the management of device drivers, specifically networking drivers. With most other drivers, like Audio, printer, and video drivers, a quick call to Windows Update or install over the network
will resolve the Installation. However unless the Network (and storage) Drivers are installed into Windows from the start, it will be much more difficult to install the rest of the system.
This post should help you get started if you find a machine that did not install a device driver properly, and you want to know how to find and import the correct drivers.
Installing network drivers in the
full OS
Step 1 - Try network connection again
It's possible that you might get a DHCP error from MDT, but when you try again later to connect the Deployment Share it works! This may be caused by a slow or malfunctioning DHCP server in your network. Re-check your DHCP servers, ensure that PortFast is enabled
on your routers. If all else fails get your network administrators to document the DHCP delay. A long delay in modern networks is unnecessary.
Step 2 - Verify connectivity
You may not have a driver problem but a network problem. Check the physical connection on the computer (Network installs on MDT *REQUIRE* a wired network connection, no Wi-Fi). Open a web browser. Check the IP Address (ipconfig.exe /all). Ping the Deployment
Server, manually connect to the Deployment Share. IF you can't connect to the Deployment Share, neither can MDT.
Step 3 - Find the Correct Driver Package
Before you load the driver into MDT, first verify that you have the correct driver. There are scenarios where you may *think* you have the correct driver, but the driver will never run because the package is designed for a different OS/SKU/Platform/whatever.
Install the driver package by:
  ○ Open the Device Manager (devmgmt.msc).
  ○ Find the network device in the list (ensure this is the wired device, not the wireless device)
  ○ Right click on "Properties" and click on the "Details" tab.
  ○ From the "Details" tab, select the property "Hardware Ids" select all the values, and copy to the clipboard, it would be a good idea to save for later. Should look something like:
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA&REV_04
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA
      PCI\VEN_8086&DEV_1502&CC_020000
      PCI\VEN_8086&DEV_1502&CC_0200
  ○ From the "Driver" tab, click on "Update Driver…", click on "Browse my computer for driver software" locate the driver package on the local machine or USB Drive, and install the package.
  ○ You should get a confirmation that the driver package was installed.
  ○ IF you do not get confirmation, MDT driver installation may not work.
Windows will install the driver starting with the *.inf install package, and will typically include a *.sys (binary) and a *.cat (digital Signature). If the driver package has been re-packaged into a *.cab, *.zip, or other compressed *.exe file, the
package must be extracted first. This is a hard requirement for any driver used by MDT and/or SCCM. All driver packages that are signed by Microsoft (WHQL) will be installed from the *.inf file, and you should only use devices that have the Microsoft WHQL
Logo as a sign of quality.
If you need a help on where to find driver packages for your devices, the 3 largest Computer OEM manufacturers supply drivers grouped by Make and Model that are easily imported into MDT and SCCM. See:
http://deploymentbunny.com/2014/07/08/back-to-basicwhere-to-find-drivers-for-servers-and-clients/
Step 4 - Load driver into MDT
If you have more than 20 driver packages, or if you anticipate you will have more than 20 drivers, you should start grouping your drivers in sub-folders for organization. One popular method is to group by Computer Make and Model. Ensure that you are using the
correct Driver Selection Profile in your task sequence. If you are unsure, disable any selection profile(s) to ensure the driver is installed correctly.
Step 5 - Run the full MDT installation
During installation MDT will perform the following:
  ○ Run the PNPEnum.exe utility and capture output to PnPEnum.xml. The VEN_Xxxx and DEV_Yyyy from the "HardwareIDs" property above must be present in this list. Otherwise we won't have a match.
  ○ Search through the %DeployRoot%\control\drivers.xml file looking for a match for the HardwareID. MDT may filter the search based on the folder search type.
  ○ MDT will copy each matching driver to the local c:\drivers directory using the xcopy.exe command. You can search (grep) for the string "xcopy" in the ZTIDrivers.log file, that will get you list of all driver packages matched by MDT.
  ○ MDT will allow the machine to boot into the NEW OS, and Driver Installation will begin in the OS. IF there are multiple drivers found and copied locally, the Windows (not MDT) will determine the best one. The c:\windows\inf\SetupAPI.*.log files
will detail which drivers copied locally were installed (or *not* installed).
Installing Network Drivers in
WinPE
Step 6 - Try the network connection again
(See above
Step 7 - Verify Connectivity from within WinPE
Verifying network connectivity will be a bit more difficult in WinPE, since we have a limited User Interface, so all investigation must be done in the debugging mode (Press F8) cmd.exe
  ○ Try connecting to the Deployment Share:
  c:\> net use * \\MDT\DeploymentShare$ /u:UserDomain\UserName *
  ○ Try pinging the Deployment Server:
  c:\> Ping.exe MDT.Corp.contoso.com
  ○ Verify that you have an IP address ( ipconfig /all ) If you have an AutoConfiguration address - Driver OK - WinPE can't reach the DHCP server. If you have "Media Disconnected" - Driver OK - Physical adapter not plugged to network. If
no devices are listed - Driver bad - Driver not installed.
  ○ Check the x:\windows\system32\WpeInit.log - This log will show the network driver (if found) being installed.
Step 8 - Verify driver packages are getting included into WinPE
Firstly, verify the correct driver package from within the full OS above. By default MDT will import *all* Storage and Networking drivers into your WinPE image. However it is possible to change the subset of files copied via "Selection Profile" or
other method. Cross check your WinPE Driver Settings.
  ○ From within the MDT console, right click on the root of your Deployment Share and select properties.
  ○ Click on the "Windows PE" tab, and the "Drivers and Patches" sub tab for both x86 and x64.
  ○ Your Network Drivers package must be in the "Selection Profile" if enabled.
Finally verify that the correct Network Driver package is being copied to WinPE. If necessary this may include setting up a debugger to watch the MDT Provider build the WinPE Image from scratch. My preference is to use the SysInternals
http://live.sysinternals.com/Dbgview.exe tool.
  ○ Open up the MDT console.
  ○ Download and run the DbgView.exe tool.
  ○ Update the deployment share in question.
  ○ The DbgView tool should show what drivers were copied to each WinPE Image.
Other
Whenever you add a driver into the MDT console, you must update the deployment share for that drivers to be added to your WinPE Image. If you are unsure, select "Completely regenerate the boot images." to ensure the drivers is imported. Additionally,
you must copy the updated LitetouchPE_x??.wim and *.iso files to the other consumers of the WinPE image like WDS/PXE and or any USB offline media.
Note that some Broadcom NetXtreme class of drivers have a multi-function driver architecture that may have difficulty loading in WinPE. Ensure that you load the "RIS" class of drivers from Broadcom in your MDT environment.
Note that by default MDT does *NOT* support the installation of Windows over Wireless network devices (Wi-Fi). The MDT installation sources must either be available through wired networking, or offline (USB Flash) media.
This post does not discuss origination of drivers within MDT ( Chaos vs. Total Control ), that is a different topic.
http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
Further Help
If you are still having problems with drivers in via MDT, ask the experts in the MDT Technet Forum:
Include a short description of the problem. Including the Make/Mode if necessary.
Include the HardwareIDs from the Device Manager (Devmgmt.msc) into the post (from above).
Copy your known good driver package (step 3 above) to OneDrive.
Copy the following log files to a public site like OneDrive and include the link:
  ○ PnpEnum.xml (from Client)
  ○ Bdd.log (From Client) - or at least the ZTIDrivers.log file.
  ○ c:\windows\inf\SetupAPI.*.log (from client)
  ○ %DeployRoot%\control\Driver*.xml
  ○ %DeployRoot%\control\SelectionProfile*.xml
  ○ %DeployRoot%\control\settings.xml (if problems in WinPE)
  ○ x:\windows\System32\WpeInit.log (if problems in WinPE)
  ○ If the MDT server is not including your driver package in WinPE include the DBGView log.
This post is by Keith Garner - Keith was a developer on the MDT team where he developed the ZTIDrivers.wsf script, he also worked for the Windows Hardware Quality Labs as a technical PM on Driver Quality, and developed samples for the
Microsoft Device Driver Kit (DDK) specifically around the area of Device Driver installation in the OS (Windows NT 5.0, 2000 and Windows XP). (So yes, I know drivers :^).
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

OK. I have redone the drivers for WinPE which has reduced the image size by about 200MB. Unfortunately the problem persists.
Is there anyway to turn on some sort of boot logging so I can see what driver it is failing on?
I am also still seeing the weird behavior of it working over PXE but blue screens when booting from USB. Can anyone explain that?
JJ

How to debug extraction a datasource in ecc starting execution in bw ?

Similar Messages

Maybe you are looking for