SAP ECC 6.0 extractor 0FI_GL_4 -extracting GL data in delta mode into MSSQL

Hi,
Currently we are having the following need. We have to build delta interface from SAP ECC into MSSQL for G/L data. If possible, we would like to use for this standard ECC extractor: 0FI_GL_4. As far as I know this extractor is dedicated for SAP BW, but can we apply it for MSSQL? Does anyone has any experience with similar task? Any help will be appreciated.
Regards,
Marek

Hi,
I'm using the data source 0SEM_BCS_10.
I have created my staging cube similar to my Totals cube (0BCS_C11).
I'm stuck in creating update rules for this staging cube, particularly with respect to the follwing feilds:
1) Posting level
Pls let me know how to update this.
Also, help me understand in general, how to write update rules to feilds which exist only in BCS.
2) F Yr of the first acquisition posted
3) Period in which first acq was posted
(Mapping for these will be constant values (actual dates) - correct me if wrong)
4) Mov Type
I guess we need to just map this with the transaction type in ECC.
Many Thanks,
Kumar

Similar Messages

How do I extract the data of Variant configuration into internal tables

Hi Experts,
How can I extract the data of variant configuration into an internal tables while preparing the report.
Thanks,
bsv.

Hi i´m not a "Expert.." but may I can help you:
CUCB_GET_VALUES_FROM_INSTANCE
Example:
Instance = MARA-CUOBF or
Instance = lips-cuobj
Result is the data of the Variant tables.
I need that for a simple report to evaluate customer & and his Variants......
Robert

Issue with extraction of data to Delta Queue

Hi All,
Background:- One LO Data source each from Application 8, 11 and 12 was active in LBWE. Update method was specified as Queued Delta. However this Data source was not utilized to pull any data to any of the Global BI Systems. These data sources did not exist in RSA7. There was a business requirement that these Data sources were to be enhanced, along with this other Data sources under these applications were also required to be enhanced. There were entries in LBWQ which used to get dumped out at regular interval by running the SAP Standard Collector jobs. Since no Delta was initialized for these extractors, no entries were passed on to RSA7.
Problem:- We did not clear the entries or took a downtime before sending transports and now the collector job is dumping saying the structures have changed, which is correct. I believe we wonu2019t require any data sitting in LBWQ as none of the extractors had any entry in RSA7. This problem is happening only in our Production system and we did not face this problem in any other system even though there were entries existing in LBWQ.
What is the solution to fix this? Is the only option now is to delete the Queue from LBWQ and then run the collector job or is there any other way and will that fix the problem?

Hi Victor,
As u said that u were not using the DS for Application 8,11 and 12.. in this case I believe that u dont have any data in BW as well(Historical data). As u have enhanced these data sources with the new requirement, I hope u must have changed the structures in BW side as well to load the data to the newly added fields.
So in ur case u need to replicate the DS in BW and then activate the Transfer structure for all of them.
And then flushout the LBWQ for all those 3 applications and then take the setup tables fill for the same (but this requires the down time in prod to make sure that u wont loose any records).
Before setup check SM13 whether u have any blocked entries for all these entries if so then u can delete them as well before taking the setup.
Once the setup is done then u can take Init without data transfer and then take repair full loads in BW for the targets.(Activate ur V3 once the init- without data transfer took place for the regular deltas) .
Thanks
Assign points if this helps

Loadind transaction data from SAP ECC 6.0 system failed

Hi!
I have SAP ECC 6.0 IDES system with the following clients:
100 DEV client
200 BI client of SAP 6.0
Now I would like to load the transaction data from InfoSources 0FI_AR_6 and 0FI_AR_4 from SAP ECC client 100.
The extraction process has been frozen in status "yellow" and after a while changed the status to "red" with the following information
Errors while sending packages from OLTP to BI
Diagnosis
No IDocs could be sent to BI using RFC.
System Response
There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
Further analysis:
Check the TRFC log.
You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Error handling:
If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source system.
The users BWREMOTE and ALEREMOTE seems to be ok and have the suitable authorization.
The tcode SM58 does not show any entries.
The tcode BD87 shows that the IDocs was sent (source system) and has been received on target system.
Question:
How can I solve my problem? Please give me some technical information (tcode, report).
Thank you very much!
regards

Walk through your basis set up and check out
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0751ba5-b7a8-2b10-6d97-e91e85c0fafa
pts appreciated.

PowerPlant passive Oracle dblink to read data from SAP ECC?

Hello
We have a third party vendor named PowerPlant that is proposing to integrate with SAP ECC using a passive dblink to pull data into PowerPlant. This is proposed when SAP ECC is running on an Oracle database. Presumably this is a read-only connection to the SAP ECC Oracle database (at database level). Has anyone used this and/or have recommnedations for or against?
Thank you,
Harold

Hi Harold,
Technically it is possible but, check your Oracle license with the local SAP office. As far as I know that SAP is not permitted 3rd party connections to the database.
Best regards,
Orkun Gedik

Custom Extractor FM with Delta mode

I have looked a few blogs that dont seem to address the whole picture.
the online help looks to be wrong?
http://help.sap.com/saphelp_nw70/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/frameset.htm
Im trying to set up an FM to do generic extraction.
Declare Datasource in RSo2. With Generic delta... all looks BUT
RSa3 can call th FM.
Seems the ROOSOURCE entry was with type F2.
If I copied a "proper" generic delta with complex interface and not the simple interface,
the entry in roosurce looks wrong to me.
What is the normal way to maintain the data source so that generic extraction works and can be tested in RSa3.
I also found this blog:
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
again the issue of deltas is over looked.
The demo function is RSA3_GEN_GET_DATA
BUT when create a dat source with rso2, the function interface used to call teh function
matches function RSAX_BIW_GET_DATA_SIMPLE
and not RSA3_GEN_GET_DATA.
The helpd refers to delta mode, but the interfae does NOT have the upmode flag.
Am i missing something or is this a whole in the RSo2 process.
Custom FM based extractors CAN NOT be called with delta mode.
surely someone knows what the trick is here ?
Cheers
Phil.
Edited by: Phil Soady on Aug 25, 2009 7:00 AM

https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/67efb9bb-0601-0010-f7a2-b582e94bcf8a
No reference here either.
my conclusion that without using pseudo deltas, ie adding a field called delta mode, to the structure
and programming over the simple interface with a extra field
or
build a full F1 complex datasource definition tool,
there is no good standard solution.
Im still interested if anyone has a good approach to this.
regards
phil

Copying (or extracting) EXIF data...

In some of the other forums I participate in, they like to see the EXIF data from a particular photo, especially if one is requesting critique/suggestions.
I can display the EXIF data in PSE5, but I haven't found a way to easily extract the data for copy/paste into another place, within PSE5. Does anyone know of a way to do this? At times, I've taken screen shots and attached them to my posts, but this is kludgy, and in one site in particular, has a maximum of 3 postings per day, which is frequently taken up by the photos I'm posting.
I have located a rudimentary product, EXIF-Extract, and it 'seems' to work, but it's a Javascript app, seemingly written by a techie and in no way supported so I'm concerned about relying too heavily on it for the long run.
Thanks.
Chris

Don't think you can do this in PSE. I suspect there are number of tools
that can do this though (what do other posters to the forum do?).
So (assuming Windows OS)
Anyway, good old Irfanview will do this. Open an image.
Press 'I' to show the image properties, display the EXIF using the 'EXIF
info' button, and there is a handy 'copy to Clipboard ' button.
You can set up Ifanview as an external editor in Organiser, so you can
open it from a right click
Chris French

Extract BOM data from R/3 to BW

Hello BW Gurus,
what is the method of extracting BOM data from R/3 into BW.
Thanks in advance.
rgds,
TR PRADEEP

Hi Pradeep,
unfortunately you have to create something custom in order to manage BOM data in BW.
Doing that, consider that all your BOM data is available in R/3 tables STKO and STPO (Header and Item).
With the table MAST you can find also the link among the combination material/plant with every BOM codes.
At this point your might create a view (and then link it with your custom datasource) by using these tables (however you have to consider your specific needs).
Please keep in mind that you will extract all historical data of that BOM number. So, use the "Created date" to use the BOM data you are interested in.
By the way, access against these tables is not so feasible...try to search in your R/3 (I don't have the access now) a function module (search with BOM) that has as input parameters BOM Header, Alternative and others and gives back a table of the respective BOM items. You can create an InfoSet on the table STKO, enhance it with some code that calls the FM and writes the returned values in the Infoset (then use it to create your custom datasource !)
Hope it helps !
Bye,
Roberto

Master data extraction from SAP ECC

Hi All,
I am a newbie here and teaching myself SAP BI. I have looked through the forums regarding master data extraction from SAP ECC in all forums but could not answers for my question. Please help me out.
I want to extract customer attributes from SAP ECC. i have identified the standard data source 0customer_attr and replicated in SAP BI. I have created infopackage for full update. I validated the extractor checker(RSA3) and found 2 records for 0customer_attr.
When I run the info package, the info package remains in yellow state until it times out. Please let me know in case i am missing anything, Please let me know if there is any other process for master data extraction similar to transaction data extraction.

Hi All,
i did the below and afte clicking execute in the Simple job, it takes me back to the Monitor Infopackage screen.
From your info pack monitor --> menu environment-->job overview--> job in the source system--> prompts for source system(ECC) user id and password, enter them, you will get your job at SM37(ECC), select job and click on log details icon. there you can see details about your error. please share that error screen shot.
Please find the screenshots.
I did an Environment -->Check connection and found the below,

Extraction from SAP ECC to SAP BI

What are the steps for Extraction from SAP ECC to SAP BI? Thanks.

Hi,
we have two types of extractions 1) Application specific 2)cross application
under applicatin specific -->we have customer genenrated and business content extractions
under customer generated means LIS, CO-PA, FI-SL(i.e no ready made data source in business content so we have to generate datasource)
Business content means there is ready made business content datasource so we can use it
LIS,LO --> when ever we go for extracting logistics informatin
LO steps
http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
LO Cockpit (Use transaction LBWE)
/people/vikash.agrawal/blog/2006/12/18/one-stop-shop-for-all-your-lo-cockpit-needs
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/u/21406 [original link is broken] [original link is broken]
/people/sap.user72/blog/2005/09/05/sap-bw-and-business-content-datasources-in-pursuit-of-the-origins
To understand LO extraction go through these weblogs by Roberto
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
under cross Applicaion
Generic extraction-->table, view, infoset query, function module
Generic extractors are of 3 types:
1. Based on table/view
2. Based on Infoset Query
3. Based on Function module
GenericSteps
Log on sap R/3.
Step 1. create a table or view for generic extraction in se11.
Step 2. Goto t-code RSO2
Step 3. Here u have to decide whether to extract transaction data or master data attributes or texts.
Step 4. suppose if u have opted for transaction data,then give name in the column ex:ztd_m(data source name)
Step 5. select create button,this will take u to another screen.
Step 6. Here u have to decide from which application component u r extacting data.Ex: SD,MM,..
Step 7. in this screen u have to fill short disciption,medium,long( these r mandatory).
Step 8. then U have to Table name or view name which u have created in se11.
Step 9. I f u want to maintain generic delta then u can select generic delta in top left hand side corner.
Step 10. in next screen u have to give some field which is primary key.
step 11. here u to specify whether time stamp or cal day or numeric pointer depending on u r requirement.
step 12. then u have to specify whether new status for changed records or additive delta.
If u choose additive delta ,then u have to load data to infocube or ods object.
If u choose new status for changed records, then u to load data to ods object only.
Step 13. then save it.
Step 14. then logon to sap bw ,then replicate the data source then as usuall.
COPA
CO-PA--> for financial info
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/COPA/COPA.pdf
You can browse forum for more detailed info..
Regards,
B

SAP (ECC) extractor to transfer data into Non SAP System

Hi Experts,
Scenario : We had a requirement to decommission the existing SAP BW system and merge it into Non SAP BI system (say MSBI).
Existing BW system getting data from standard extractor and populating till cubes.
Now If this SAP BW system will be decommissioned and all the data needs to be moved to new Non SAP System BI.
What will be the approached for this smooth transfer.
Will SAP (ECC) std extractor will be used to move the data into non SAP BI system ? How ?
Any documentation and experience will be helpful.
Thank-You.
Regards,
VB

Hi VB,
First you need to identify that your MSBI system support BCI(business content integration) method. For example Informatica support BCI and provide RFC plugins to integrate with SAP. If your MSBI support BCI method then you can use standard dataextractors to extract data in new BI system. You will also need to plan the reporting model and how the extracted data will be feeded in your BI datamodel/reporting side. You may use some transformation reference from your existing SAP BI system.
Thanks
Amit

Extracting delta's with ODP-data source 0MATERIAL_ATTR from SAP ECC

We are using ODP-replication to extract data from SAP ECC to a MS SQL-database by SAP BusinessObjects Data Services.
For extracting Material-data we use the standard data source 0MATERIAL_ATTR in SAP ECC.
This data source delivers a full load with all Materials in it.
In the properties of this data source (tab attributes) we saw that this data source is Delta_Extractor_Capable.
Therefore we set the extraction mode from 'Query' to CDC (= Change Data Capable) and did a new initial load to get all Materials again.
After changing a Material in ECC, we did a delta-load, but unfortunately we received ZERO records.
Is there anyone with experience on extracting delta's with data source 0MATERIAL_ATTR or another standard masterdata data source in ECC?
Thank you for your reaction in advance,
Best regards,
Jan-Hendrik

Hi,
You can check the delta records in RSA3 see teh article. in https://wiki.sdn.sap.com/wiki/display/profile/Surendra+Reddy
Checking the Data using Extractor Checker (RSA3) in ECC Delta Repeat Delta etc...
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/80f4c455-1dc2-2c10-f187-d264838f21b5&overridelayout=true
Data Flow from LBWQ/SMQ1 to RSA7 in ECC and Delta Extraction in BI
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/d-f/data%20flow%20from%20lbwq_smq1%20to%20rsa7%20in%20ecc%20and%20delta%20extraction%20in%20bi.pdf
Delete the Queue in LBWQ/RSA7 and then freshly load Init and Check the Delta.
Once you load the Init then if there are no new records then it won't get any data. so 0 records
Check in SM37 in ECC why the job is terminated. See in ST22 also.
Thanks
Reddy

Extracting Values of a Field from a Database Table in SAP ECC System

Hi,
I downloaded Extracting Values of a Field from a Database Table in SAP ECC System Using MII 12.0
senario from sdn. I'm trying to do that senario in MII 12.05. But I have problem with section 6 in page 7 (you can supply senario from sdn)
"6- Under the loop of Repeater, use action u2018Rowu2019 to append just the string part of the WA which will display only values for field u2018Batchu2019"
I did not find WA elemen in Output element of Repeater_0
How can I create WA element?
Thanks.

Cemil,
Set up a SAP JCo Interface action block. Use the RFC name RFC_READ_TABLE.
In the link editor map the table to "MARA", set RowCount to something small (20 is good sample size) and create an xml transaction property named FIELDS and copy the following into it:
<?xml version="1.0" encoding="UTF-8"?><FIELDS>
      <item>
        <FIELDNAME>MATNR</FIELDNAME>
        <OFFSET/>
        <LENGTH/>
        <TYPE/>
        <FIELDTEXT/>
      </item>
      <item>
        <FIELDNAME>MTART</FIELDNAME>
        <OFFSET/>
        <LENGTH/>
        <TYPE/>
        <FIELDTEXT/>
      </item>
      <item>
        <FIELDNAME>BSTME</FIELDNAME>
        <OFFSET/>
        <LENGTH/>
        <TYPE/>
        <FIELDTEXT/>
      </item>
      <item>
        <FIELDNAME>XCHPF</FIELDNAME>
        <OFFSET/>
        <LENGTH/>
        <TYPE/>
        <FIELDTEXT/>
      </item>
      <item>
        <FIELDNAME>DATAB</FIELDNAME>
        <OFFSET/>
        <LENGTH/>
        <TYPE/>
        <FIELDTEXT/>
      </item>
    </FIELDS>
Then link the Transaction.FIELDS to SAP_JCo_Interface_0.Request{/RFC_READ_TABLE/TABLES/FIELDS}. You may run into problems with two other fields and optionally they can be removed (set link type to remove xml). I usually remove them initially for testing. The two fields are:
SAP_JCo_Interface_0.Request{/RFC_READ_TABLE/INPUT/NO_DATA}
SAP_JCo_Interface_0.Request{/RFC_READ_TABLE/INPUT/DELIMITER} (or you can set this to something like a semicolon,";" or tilda,"~". I find it easier to caclulate position by length, but that is my own idiosyncrasy.)
Once you get this one working, we can explore how to do filtering on the dataset. Your output should be something like this:
<?xml version="1.0" encoding="utf-8"?>
<RFC_READ_TABLE>
<INPUT>
    <DELIMITER />
    <NO_DATA />
    <QUERY_TABLE>MARA</QUERY_TABLE>
    <ROWCOUNT>20</ROWCOUNT>
    <ROWSKIPS>0</ROWSKIPS>
</INPUT>
<TABLES>
    <DATA>
      <item>
        <WA>000000000000000023ROH 00000000</WA>
      </item>
      <item>
        <WA>000000000000000038HALB 00000000</WA>
      </item>
      <item>
        <WA>000000000000000043HAWA 00000000</WA>
      </item>
      <item>
        <WA>000000000000000058HIBE 00000000</WA>
      </item>
      <item>
        <WA>000000000000000059HIBE 00000000</WA>
      </item>
      <item>
        <WA>000000000000000068FHMI 00000000</WA>
      </item>
      <item>
        <WA>000000000000000078DIEN 00000000</WA>
      </item>
      <item>
        <WA>000000000000000088FERT 00000000</WA>
      </item>
      <item>
        <WA>000000000000000089FERT 00000000</WA>
      </item>
      <item>
        <WA>000000000000000098HALB 00000000</WA>
      </item>
      <item>
        <WA>000000000000000170NLAG 00000000</WA>
      </item>
      <item>
        <WA>000000000000000178NLAG 00000000</WA>
      </item>
      <item>
        <WA>000000000000000188NLAG 00000000</WA>
      </item>
      <item>
        <WA>000000000000000288HALB 00000000</WA>
      </item>
      <item>
        <WA>000000000000000358HAWA 00000000</WA>
      </item>
      <item>
        <WA>000000000000000359HAWA 00000000</WA>
      </item>
      <item>
        <WA>000000000000000521HAWA 00000000</WA>
      </item>
      <item>
        <WA>000000000000000578FERT 00000000</WA>
      </item>
      <item>
        <WA>000000000000000597HAWA 00000000</WA>
      </item>
      <item>
        <WA>000000000000000598VERP 00000000</WA>
      </item>
    </DATA>
    <FIELDS>
      <item>
        <FIELDNAME>MATNR</FIELDNAME>
        <OFFSET>000000</OFFSET>
        <LENGTH>000018</LENGTH>
        <TYPE>C</TYPE>
        <FIELDTEXT>Material Number</FIELDTEXT>
      </item>
      <item>
        <FIELDNAME>MTART</FIELDNAME>
        <OFFSET>000018</OFFSET>
        <LENGTH>000004</LENGTH>
        <TYPE>C</TYPE>
        <FIELDTEXT>Material Type</FIELDTEXT>
      </item>
      <item>
        <FIELDNAME>BSTME</FIELDNAME>
        <OFFSET>000022</OFFSET>
        <LENGTH>000003</LENGTH>
        <TYPE>C</TYPE>
        <FIELDTEXT>Purchase Order Unit of Measure</FIELDTEXT>
      </item>
      <item>
        <FIELDNAME>XCHPF</FIELDNAME>
        <OFFSET>000025</OFFSET>
        <LENGTH>000001</LENGTH>
        <TYPE>C</TYPE>
        <FIELDTEXT>Batch management requirement indicator</FIELDTEXT>
      </item>
      <item>
        <FIELDNAME>DATAB</FIELDNAME>
        <OFFSET>000026</OFFSET>
        <LENGTH>000008</LENGTH>
        <TYPE>D</TYPE>
        <FIELDTEXT>Valid-From Date</FIELDTEXT>
      </item>
    </FIELDS>
    <OPTIONS />
</TABLES>
</RFC_READ_TABLE>
Add a repeater sourced on:
SAP_JCo_Interface_0.Response{/RFC_READ_TABLE/TABLES/DATA/item}
Link your repeater output to a tracer with this:
Repeater_0.Output{/item/WA}
What you will see in each tracer message is a single line of data with all the fields contents concatenated together. You can look up what each field in the string represents by the length of the field as returned in the Response segment of the RFC_READ_TABLE rfc. Then you can parse out the data you are interested in.
Give this a try and let me know how you succeeded.
By the way, I could not find the scenario you referred to. Can you post a link?
Regards,
Mike
Edited by: Michael Appleby on Jan 12, 2009 5:16 PM

SAP ECC 6.0 - Using BAPIs for C# to extract data out

I have had a client recommend a strategy of extracting data usin C# (Visual Studio 2005) to extract data from SAP ECC using BAPIs.
We do have an existing methodology in place using flat files to extract data to non SAP systems
We have purchase XI which we intend to implement next year.
I basically wanted to keep things tidy and continue with the flat file interface strategy just to keep things simple going forward to XI.
THen there is also the security piece, the developer has had to slowly build a profile / roles that alows him to come in thru visual studio to access these BAPIs
I am looking for anyone who has had experience with this and what your experiences are. As well, what are the SAP best practicies concerning this strategy
Thank YOU ALL who will reply

I think that SAP's strategy toward exposing BAPI is leaning toward leveraging their AS-JAVA stack. With the AS-JAVA Enterprise Services and standard delivered web content, SAP is already exposing many existing BAPI/Business Functionality outside of the ABAP world. However, that's not saying that traditional flat files have no place in the future. Matter of fact, I don't see flat/delimited files going away any time soon.
It all really comes down to what you are doing, you may even end up with a landscape that's a mix of files/RFCs. Here inhouse, we leverage file based transfers for large data sets such as SAP BI OHS extracts, and daily R/3 FI extracts. Why file? because it's simple, easy to control, and you can see the data being transferred. A file can be "hold in my hands" if you will, at best there's just a few characters in-flight.
As for RFCs, any type of RFCs in fact (Anything from sap .net connector to AS-JAVA ESOA Based ES), are basically designed for transactional data. Here, you are looking at things that are high in transactional count but small in individual size. Your client's call using C#, it all really depends on how you are doing it. MOST IMPORTANTLY: Make sure you are using a proven, standarized, and SAP supported way, PERIOD. NEVER EVER go into production with a "hack".
For the high-transactional-count-small-individual transactions, we leverage BizTalk Server (BTS) here. I'll be frank, we are not using BTS because we wrote it. We are using BTS because it just works better for us, in our environment. BTS now support SAP 2.0 connector (registered program ID) and SAP 3.0 (WCF based, direct SAP RFC call, supported by Microsoft AND SAP). We are leveraging these adapters and BTS (as distribution and transformation) in our environment more and more.
So, long story short: Determine the transaction type, multiple solutions is ok, make sure the solution is supported!

Lo-Extraction Job Failed in SAP ECC 6.0

Hello,
My Lo-extraction job failed yesterday because of this I'm unable to extract the delta data from SAP ECC 6.0 to BI. When I extract the Delta data from 2LIS_11_VAITM to BI there is no data because of Job failed in SAP ECC 6.0.
How to get the data back to 2LIS_11_VAITM data source?
Thanks

Error log display as follows
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLMCEX" or "LMCEXU14"
"MCEX_UPDATE_11"
Actually I add ZZ fields to structure if that is the case do i need to delete the data from MCEX11 ?
I delete the data from setup tables but i did not delete the LUW entries?
When do we delete the LUW entries?
If the structure changes do I need to cancel the old job and re-schedule job?
Thanks

SAP ECC 6.0 extractor 0FI_GL_4 -extracting GL data in delta mode into MSSQL

Similar Messages

Maybe you are looking for