Delta in 4.7 to ECC 6.0

Hi Guru,
Can anyone please provide me with the list of delta functionalities between 4.7 and ECC 6.0 in MM/WM module.
Thanks in advance.
Regards
Prashant

I have no idea how often questions like this have been answered here but I try to help you though.
Read the Release notes
http://service.sap.com/releasenotes
Read the deltas for ERP 2004/ECC 5.0 and ERP 6.0
Use the solution browser:
http://solutionbrowser.erp.sap.fmpmedia.com/
Markus

Similar Messages

What is delta between 4.6b to ECC 6.00

Hi
what is delta between 4.6b to ECC 6.0 in MM module ?
Could anyone help me out with some scenario's please?
Thankyou

http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financials, Human Capital Management, Sales....
Select module like MM, PP, SD, QM.....
Click on Search
Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
Hope this helps you.

Delta functionality in SAP-MM ECC 6.0

Hi Guys,
Please list the delta functionalities in ECC 6.0 of SAP-MM compared to 4.7 version.
Thanks,
Pallu Tillu

Hello
Following are the basic differences as far as MM Module is concerned;
Pickup list - Batch where-used list display in transaction MB56
u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
Usability enhancements for transaction MIGO for the posting of goods movements
u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
u2022 User changes the default values in the menu path "Settings -> Default Values."
u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
Goods receipt
Goods issue
Transfer posting
Remove from storage
u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
New report : display list of invoice documents (MIR5)
u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
u2022 In the output list, the report shows both posted and held invoices.
u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
Requirement prioritizations in materials management
u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
Mass maintenance of outline agreements
The following two transactions available:
u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
Commitment plan for purchase contracts
u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
u2022 This commitment plan itself can have any number of items.
u2022 User can define a value and a validity date for each commitment plan item.
u2022 This enables user to pre plan different values for different periods of time.
u2022 The software generates an earmarked fund document for a defined commitment plan item.
u2022 This earmarked funds document can in turn contain several different items with different account assignments.
u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
u2022 Account assignment to a different account assignment object is then no longer allowed.
Availability check in "Enjoy purchase order and requisition"
u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
u2022 Two settings are possible with availability check:
Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
Delivery proposal - Full confirmation
External services: putting service items in the purchase order on hold (changed)
User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
Customizing transactions OX18 replaced by view
The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
Goods receipt: new movement types in inventory management
The following new movement types are available in inventory management:
107: Goods receipt to valuated goods receipt blocked stock
109: Goods receipt from valuated goods receipt blocked stock
Prepayment of invoices
This functionality is characterized as follows:
u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
u2022 When the software posts invoices, it continues to execute the standard checks.
u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
Purchasing accounting information to the former SAP Business Information Warehouse
u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
u2022 Functionality for report RMMR1MRS is enhanced.
u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
u2022 To do so, set the relevant indicator on the initial screen of the report.
Parking service items
It is now possible to put service orders without errors or with commitment errors on hold.
Report MB5B : Stock on Posting Date
u2022 This Report is available with "Non-Hierarchy" display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
u2022 This functionality is not available in Release 4.7.
Stock Transfer Between Storage Locations
u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
u2022 As a result of which user can input issuing storage location with supplying plant.
u2022 Facility of using different delivery types for different issuing storage locations is available.
u2022 Shipping Point data can also be determined based on the issuing storage location.
If u want to know more go through the following links
http://solutionbrowser.erp.sap.fmpmedia.com/
http://help.sap.com/saphelperp2005vp/helpdata/en/43/6880cbb88f297ee10000000a422035/frameset.htm_
https://wiki.sdn.sap.com/wiki/display/ERP6/ERP2005+Upgrade

How to activate delta download for BP from ECC to CRM

Hi,
i have completed BP initial download from ECC 6.0 to CRM 5.0.
i dont know how to activate the Delta download?.
Plz anyone tell me the procedure.
regards
geetha.g

Hi Geetha
Synchronization download allows you to synchronize inconsistent datasets on various databases. This can be controlled in time slots or can be triggered manually.
1. Creating a Request
Choose Middleware -->Data Exchange --> Synchronization --> Define Requests.
To define a new data request, choose Display --> Change and New Entries.
Enter data for the request.
In object name enter CUSTOMER_MAIN
2. Starting the Request
Choose Middleware --> Data Exchange -->Synchronization --> Synchronize Objects.
A selection screen appears. Enter the objects to be synchronized or use F4 input help to select objects. Choose Execute to start synchronizing the data.
3. Monitoring Request
Choose Middleware --> Data exchange --> Synchronization --> Monitor requests
Enter an object name or a range of object names. Use the input help or of you want to display all the objects, do not enter an object name at all. Choose Execute.
Further help is available on http://help.sap.com/saphelp_crm50/helpdata/en/c7/95fc381478ab6fe10000000a11402f/frameset.htm
Hope this would help.
Regards,
Rekha Dadwal
<b>You gain a point for every point that you reward. So reward helpful answers generously</b>

Delta Functions 4.6C and ECC^

Hi,
Does anybody have documentations on Delta functionality from 4.6C to ECC6? Especially what configurations are changed since we are planning to use ECC6 but by copying 4.6C configurations. After that we activate new GL. We need to know whether this will work.
Thanks
Edited by: Harry Soehendro Rameli on Jan 30, 2009 4:19 AM

Hello Harry,
Below would be the reply to your questions.
Regarding the delat functionality between 4.6C and ECC 6.0 please use the link http://solutionbrowser.erp.sap.fmpmedia.com/ . This is a beautiful self expanatory link and u can get all the delta functionalities module wise.
(ii) Regarding New GL- As per SAP product roadmap, customers who are upgrading from earlier version to mySAP ERP are not mandatorily expected to use the NEW GL. The classic GL Total table"GLT0" remains active even after the upgrade. It is the choice of customer whether they would like to continue with classic GL or would like to move on to New GL. If theyy want to move to New GL, it needs to be activated through the TCode- FAGL_Activation. In such cases the total table of clssic GL is replaced by new table"FAGLFLEXT" of new GL.
Hope this helps you. Let me know if you need anyother information.
Rgds
Manish

Delta relaease Vehicle management system ECC 6

Hi all,
where can I search delta relase for VMS ECC 6?
Thanks,
Andrea.

Hi ,
Automotive is an addon that SAP is providing , in earlier for
getting this functionality we were ask to to install this
addon separately , but now with ERP release we only need to
activate these addon in transaction SFW5.
Like all other addons automotive also provides so many additional
functionalities like warranty claim processing (WTY ),
Just in time (JIT) , vehicle managment ( VMS) , Self billing (SBI)
etc
Please go through the following link in help.sap.com for knowing
more about the automotive funtionalites
http://help.sap.com/saphelp_dimp50/helpdata/EN/71
/c16736de7ef76de10000009b38f839/frameset.htm
Regards
V V

Delta in ECC 6.0 -US Payroll?

Hi
Would like to know if you have experienced the Delta functionality in US Payroll (ECC 6.0 vs 4.6B)?
Was not able to find delta in solution browser.
Thanks

Solution Browser

Scenarion of Delta Load problem in COPA Extraction

Please get me the solution for this particular scenario.
Let us suppose that i created the datasource some 1 year back and running the deltas successfully since then.
Let us number the requests from 1,2,3... and so on since 1st jan 2009. And let us suppose each request loads
some 1000 records everyday from ECC to BI.
Now on 10th august some change was made to ECC( such as change in the User Exit ) that caused the mismatch in number of data records ( loading only 950 records ) since the change was made on 10th August. But I identified the problem on 17th august with request number 160. Let us say those request numbers are 153(10th),154(11th),155(12th),156(13th),157(14th),158(15th),159(16th),160(17th). I fixed the program in ECC on 17th and further the requests from request number 160(17th) are fetching the correct number of data records. Now I need to delete the data in BI for request numbers 153 till 159 since they are not reconciling the data of ECC with BI. Now we reload the deltas for such requests from ECC to BI. So how do I reload the deltas now in this scenario since ECC system keeps track of the last delta ie.. on 17th august(Req no 160). But how do I Load the deltas from req number 153 to 159 from ECC to BI.
One proposed solution to this problem was setting the timestamp of COPA to 10th august. But it is not advised to set the timestamp for COPA datasources using the KEB5 transaction in a production system.
Now in this scenario how do I load the request numbers 153 to 159 from ECC to Bi to fetch the correct data records for that period. Please propose a solution for this problem ASAP. U can also call me back whenever u need.
Thanks in advance

As stated in a previous post...
How you choose to do this can be summed up by the question: Does the target for this data have cumulative or non-cumulative Key Figures?
If you are doing an overwrite to the Key Figures, you could just execute a Full Repair InfoPackage that extracts the data for the days that you found inconsistencies instead of attempting to change the timestamp in KEB5 on the source ECC environment.
However, if you're target has cumulative Key Figures you're left with very few options (a couple of them are time-consuming):
1) Changing the timestamp in KEB5, if your plug-in is PI 2003.1 or older. Newer versions of the plug-in do not allow the changing of the timestamp as was pointed out by Ferruccio earlier.
2) Deleting the keys in the target InfoProvider for those records that you extract in a Full Repair extract.
3) Delete all data in BW for COPA and start from the beginning. This may be your best bet for cleaning up the issues in this scenario.

GI quantity Delta issue with 2LIS_02_SCL

Hi Friends !
We are facing delta issue in the BI Prod. Hence to look into the issue, performed few steps in Test environment to check whether delta is performing or not. Mentioned below are the steps which are carried :
1. BW Setup
a. Deletion of queues for Purchasing data in ECC
b. Data collection of purchasing documents for March 1 u2013 March 31 in ECC
c. Deletion of source system initialization in BW
d. Loaded collected data into SAP as delta initialization
Result - OK
2. ECC data entry
a. Created PO #5052422, intracompany STO from DDP1 to USC1
i. 1 line item (qty 5) with two schedule lines (qty 2 & 3)
3. First delta run
a. BW brings over 2 schedule lines for PO #5052422
Result - OK
4. ECC data entry
a. Created PO #5052423, intercompany from DDP1 (USC1) to IRP3 (BV11)
i. 1 line item (qty 5) with two schedule lines (qty 2 & 3)
5. Second delta run
a. BW brings over 2 schedule lines for PO #5052423
Result - OK
6. ECC data entry
a. Posted partial delivery for schedule line 1 of PO #5052422 with a quantity of 1
7. Third delta run
a. no records brought over (change to GI quantity should trigger delta)
Result - FAIL
8. ECC data entry
a. Posted partial delivery for remainder of schedule line 1 of PO #5052422 with and a partial delivery for schedule line 2 with a quantity of 1
9. Fourth delta run
a. no records brought over (change to GI quantity should trigger delta)
Result - FAIL
10. ECC data entry
a. Modified delivery date of both schedule lines of PO #5052422
11. Fifth delta run
a. Both schedule lines of PO #5052422 brought over with updated delivery dates and goods issue quantities
Result - OK
12. ECC data entry
a. Modified delivery date of both schedule lines of PO #5052423
13. Fifth delta run
a. Both schedule lines of PO #5052423 brought over with updated delivery dates
Result - OK
Ques :
1) When modified, GI quantity is not triggering delta. Please advise.
2) 2LIS_02_SCL extractor is build on which delta field.
3) How delta works & behaves with 2LIS_02_SCL extractor?
With Regards
Rekha

Good afternoon Rehka,
I believe that it is correct that the GL change you mention will not trigger a delta on the BW side. This functionality appears to be missing.
If you check in LBWE you will see that the EVENTS for 02: Purchasing -> MC02M_0SCL include the following:
MA: Purchase order
MB: Goods receipt
MC: Invoice receipt
MD: Scheduling agreement
The event associated with a Goods Issue is ML and not included in the list of events for this structure. This is the standard behavior.
I checked and I was unable to find a datastructure that does handle event ML. From what I see the only way to do this is through a custom datasource.
Kind Regards,
Des

Delta data load for huge table in Data Services XI R3

Hi,
We have a project requirement of pulling delta data once in a week from table which has around 44 million records but it doesn't have any last modified column.
In such case we have to use table comparison transform, but it will be very time consuming.
Please provide some suggestions to meet this requirement.
The source of DS job is a snapshot(the source table is in a remote database).
Thanks!

Because SAP Business Objects Data Services XI 3.x doesn't have any built-in delta-enablement mechanism with R3/ECC, the only possibility right now is to do a table compare. Given that this is only a weekly activity, while maybe time-consuming, it may be sufficient.
In the future, you may want to consider activating the related SAP BW standard content DataSource(s) to extract into Data Services prior to loading to the target repositories. This may provide delta-enablement for the data that you're extracting.

Error in COPA Delta

Hi,
While I was trying to change the Timestamp of a COPA Delta load to a previous load in transaction KEB5, I got the following Error Message:
"Master Record for Datasource 1_CO_PA800IDEA_AC is defined for generic delta Read
Timestamp could not be set"
What might be the possible reason for such a Error Message. Could anybody help me in this regard ???

Please get me the solution for this particular scenario.
Let us suppose that i created the datasource some 1 year back and running the deltas successfully since then.
Let us number the requests from 1,2,3... and so on since 1st jan 2009. And let us suppose each request loads
some 1000 records everyday from ECC to BI.
Now on 10th august some change was made to ECC( such as change in the User Exit ) that caused the mismatch in number of data records ( loading only 950 records ) since the change was made on 10th August. But I identified the problem on 17th august with request number 160. Let us say those request numbers are 153(10th),154(11th),155(12th),156(13th),157(14th),158(15th),159(16th),160(17th). I fixed the program in ECC on 17th and further the requests from request number 160(17th) are fetching the correct number of data records. Now I need to delete the data in BI for request numbers 153 till 159 since they are not reconciling the data of ECC with BI. Now we reload the deltas for such requests from ECC to BI. So how do I reload the deltas now in this scenario since ECC system keeps track of the last delta ie.. on 17th august(Req no 160). But how do I Load the deltas from req number 153 to 159 from ECC to BI.
One proposed solution to this problem was setting the timestamp of COPA to 10th august. But it is not advised to set the timestamp for COPA datasources using the KEB5 transaction in a production system.
Now in this scenario how do I load the request numbers 153 to 159 from ECC to Bi to fetch the correct data records for that period. Please propose a solution for this problem ASAP. U can also call me back whenever u need.
Thanks in advance

No.of transferred records do not match with delta records in RSA7

Hi,
The full update was failing since a number of days in 0vendor because of error in the source system. So I did an initialize with data transfer and corrected the PSA data and updated it using scheduler in the infoobject. In this case the number of transferred records was 24300 and added records was 0.Next I executed the delta infopackage and was expecting 0 records,since there were 0 records in rsa7. But I got 16000 records.Can you explain me why this happened?
Regards,
Shalaka

Hi Shalaka,
In which version of SAP you are working?
You might want to have a look at the table BDCP2 which is a different table that handles the delta mechanism for the change pointers.
You can reset the processing status using the program RSA1BDCP ex with following entries.
Now, coming to your issue - to verify the initial loads I am listing some basic checks(step by step).
You can give it a try in Dev/QAS if you have any restrictions in Prod.
1. Check and verify if the RSA7 delta queue is present.
2. In BW system, delete the INITIALIZATION request from infopackage - This should delete the delta queue from RSA7 in ECC system. (I am not 100% sure about this so try this once)
3. Re-initialize the datasource from BW system and note the no. of incoming records in BW. This should match with LFA1 entries.
4. Check the delta queue in RSA7 - There should be a new delta queue created
5. Start the Delta load - The should not be any records coming in to BW
6. Check the entries in table BDCP2 and its process indicator.
7. Create a new vendor from XK01 and check the entry again in BDCP2 table.
8. Run the delta again in BW and this time delta should have the newly created vendor.
Also be aware that since its a master data datasource and deals with change pointers you will not see any entries in RSA7.
A possible reason I could think of you getting 16000 records in delta is because you might have initialize the datasource is past and then started the FULL loads. So the deltas actually started accumulated in BDCP2 with processing status as BLANK and then when you triggered delta again back now all the historical deltas are processed.
This apply with BDCPV too if you are on older version of SAP.
Did you tried running delta's multiple times - you should not face any delta records when the processing status of change pointers is set to 'Processed' i.e. 'X'.
PS: You can find the message type for 0VENDOR_ATTR in ROOSGEN table. This will be useful in looking at table BDCP2.
Please let me know if there are any questions.
Thanks
Amit

Delta DATA SOURCE not at all visible in RSA7

hi ,i have installed ecc6 and bi on two different servers ,and the connection is also established ,but coming to ecc,i have activated the data source which is generic data source,and i have initiated delta and generic delta is successfully created but the problem is the data source is not showing in RSA7,i have tried in so many ways like i have tried for logistic data also but,RSA7 not showing any data sources,from my side i am able to initiate delta successfully ,,but RSA7 IN ecc not working,no data source is listed in RSA7,,,please help me ,any settings i need to do in RSA7 to visible data source in RSA7.,,,,,please help me
Moderator message: not directly related to ABAP development.
Edited by: Thomas Zloch on Nov 22, 2011 10:16 AM

try running an ethernet cable from your Mac to the AX. this should enable AU to see it.
once configured, you can disconnect the ethernet cable.
JGG

Issue with delta queue initialization

Hello
I am having a problem with an initialization of the delta queue for a certain extractor. The initialization was successfull, and I can see the extractor in the delta queue maintenance (RSA7) in ECC, but when users are posting transactions in ECC, they are not coming into RSA7.
The extractor is 0CO_OM_WBS_6, so its not standard LO cockpit where we have V3 (background) jobs which have to be triggered.
One more thing, the record which was posted was backdated, ie the date is sometime in the past. But I think the delta queue still picks the records. Can i know how the delta queue funtions based on the time stamp?
Please advise.

Here is the OOS note fro FI Datasources.
OSS 485958:
Symptom
The FI line item delta DataSources can identify new and changed data only to the day because the source tables only contain the CPU date and not the time as time characteristic for the change.
This results in a safety interval of at least one day.
This can cause problems if the batch processing of the period-end closing is still running on the day following the period-end closing and all data of the closed period is to be extracted into BW on this day.
Example:
The fiscal year of the company ends on December 31, 2002.
On January 01, 2003, all data of the closed fiscal year is to be extracted into BW.In this case, the FI line item delta DataSources only extract the data with a safety interval of at least one day.
This is the data that was posted with a CPU date up to December 31, 2002.
However, the batch programs for closing the 2002 fiscal year are still running on January 01, 2003.
The postings created by these programs with a January 01 date for the 2002 fiscal year can therefore only be extracted with delta extraction on January 02, 2003. However, extraction should already be possible on January 01, 2003.
Other terms
FI line item delta DataSources
0FI_AP_4; 0FI_AR_4; 0FI_GL_4
Reason and Prerequisites
This problem is caused by the program design.
Solution
The functions are enhanced as of PI 2002.1, standard version.
Due to a customized setting, it is now possible for the FI line item extractors to read the data up to the current date during the delta runs.
During the next delta run, the data is then read again from the day when the previous extraction was called, up to the current day of the call for the new extraction.This means that the delta extraction of the data always occurs with time intervals overlapping by one day.
The delta calculation by the ODS objects ensures that the repeatedly extracted data does not cause duplicate values in the InfoCube.
Activate the new functions as follows:
1. PI 2001.1 or PI 2001.2:
Implement the new functions with the correction instructions in this note.As of PI 2002.1, these changes are already implemented in the standard version.
1. Start a test run for an FI line item DataSource via transaction RSA3.
2. Two new parameters are now available in the BWOM_SETTINGS table.
3. Parameter BWFIOVERLA (Default _)
Set this parameter to "X" using transaction SE16, to activate the new function of overlapping time intervals.
Caution
The new function also uses a safety interval of one day to determine the To value of the selection, if the time limit set by BWFITIMBOR is not reached.This means that only data up to the day before the extraction was called is selected, if the extraction starts before 02:00:00 (default for BWFITIMBOR).
Correction: Parameter BWFITIMBOR (Format HH:MM:SS, default 020000)
The default value for this parameter is 02:00:00.Do not change this value.
If this time limit is not reached, only data up to the previous day (with BWFIOVERLA = 'X') or the day before this day (with BWFIOVERLA = ' ') is selected.
This logic prevents records with a CPU date of the previous day being contained in the posting when the extraction is executed.
Check any OSS notes for your data source.

Middleware - initial and delta downloads

Hi Experts,
I am working on the middleware configuration. The requirement is to have an initial download of business partners from ECC 6 to CRM, then to have delta loads from CRM to ECC 6.
From what i've read, with initial downloads, for example, from ECC 6 to CRM, delta downloads of the same objects are automatically triggered in the background.
What i want to know is:
- How do i stop the automatic delta loads of business partners from ECC 6 to CRM?
- How do i then trigger the delta loads for the business partners from CRM to ECC 6?
Thanks in advance.
Rgds,
Keitumetse

Initally you do settings in PIDE in ECC what partners do you want to replicate from ECC to CRM and CRM to ECC ,once you do an initial load of customer master from ECC to CRM , the delta gets active automatically, if you want to stop the delta changes from CRM to ECC go to R3AC4 object class BUPA as inactive.

Delta in 4.7 to ECC 6.0

Similar Messages

Maybe you are looking for