0FC_BP_ITEMS delta functionality

Hi,
We are planning to implement datasource 0FC_BP_ITEMS for Open and clear items.
I just wanted to understand how this datasource delta functionality works.
SAP has mentioned how we can implement delta. The process is as below. But didnt mentioned how delta works here.
If you want to use the delta method, you first have to activate it in the Implementation Guide for Contract Accounts Receivable and Payable under Integration Business Intelligence Maintain Central Settings in the clients of the OLTP system.
Can some one help me in understanding how the delta works for this datasource i.e Delta enable field, delta logic and all
Thaks & Regards,
Anand

Hi,
Thanks for the reply.
In RSA2 i can find whether the datasource is Delta capable or not.
Yes, this datasource is delta capable. But i didnt find the field on which field the delta is ebnables and what is the logic it is using to extract data.
More over SAP mention as below while describing the Datasource 0FC_BP_ITEMS.
If you have a lot of data to initialize in the OLTP system, you can create several InfoPackages with disjointed selections on the field CPUDT to make the delta initialization parallel. The best way would be to start an InfoPackage with the selection of a particular period (for example, 1st of January of the current year until 31.12.9999), so that you can start the delta upload immediately afterwards for all business partner items that were or are created after the start date.
So can we understand the CPUDATE is delta field?? If it is so, what would be the logic in extracting the delta.
Please advice.
Thanks in Advance.
Regards,
Anand

Similar Messages

Function Module Extractor with Delta Functionality

Hi Friends,
I have to extract the entire data of CDPOS table in R/3 , as its a cluster table I am unable to build a view, I am planning to go for FM extraction, Could someone help me as how to build it with Delta Functionality.
I think I need to develop the Datasource, with Extract Structure,( Do I need to create a Structure in SE11) Please help me out .
Thanks,
Krish

Hi,
you can either use an existing structure or else create one on your own. (SE11).
The DeltaHandlig fairly easy.
When having finished the extractor (FunctionModule, Structur and DatasSource), go to the "generic Delta" button and select the relevant field.
The Generic Delta and its DeltaPointer is managed within the DeltaQueue (RSA7) and works more or less like a selection. Don't think too hard about it in your function module except taht you need to select by this field in your FM.
Did that come clear?
hth
Cheers
Sven

Delta Functionality

Hello,
Can someone please provide me the Basis Delta Functionality between SAP 4.7 to ECC 6.0 Upgarde.
Thanks in advance.
Br,
Naresh.

Naresh,
Since 4.7 - ECC 6.0 the platform change is very minimal as both of them base on enterprise core.
A lot of functionality gets additive which is new in ECC ( Data can be obtained from that link provided earlier). The level of detailing is also important - Printer screen gets changed a bit, services get active in some cases..cosmetic changes can be ignored ....
From authorizations side also it is minimalistic ...check the note 991377.
A bit of read on standard documentation will give u more info - so check that out as well.
Rgds,
Sri
Award points if found helpful

How does the Delta functionality works while updating Infocube from PA

Hi Gurus
How does the Delta functionality works when you send forecast to the Info cube from the Planning Area.
As I have weekly based planning, every week we have to update the forecast into the Cube. If I update every week into the Cube , then the values are going to append in the Info cube.
Shall I create ODS in between the Planning area and the Info cube .
(or)
Any other method ?
Please Suggest.

Hi Preetham,
Data Extraction from planning area to infocube usually its supports for full update only, when u r going to load the data from planning area to cube ,it deletes the previous data and u vil get the fresh data, this is the best method performance wise,
if u want to use the delta functionality u can go for planning area to Dso, Dso to cube, it vil supports the delta functionality, but it vil degrades the system performance,
regards
ravi

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 functionality between SAP 4.7 and ECC 6

Hi All,
Can anyone please provide me with any documents or links on delta functionality between SAP 4.7 and ECC 6.0 in MM/WM.
Any information would be helpful.
Regards
Prashant

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
check following
http://help.sap.com/bp_bblibrary/500/html/U40_EN_IN.htm
for more help check following
http://help.sap.com/bp_bblibrary/500/BBlibrary_start.htm
Go through the following link for the Delta functionality notes
http://solutionbrowser.erp.sap.fmpmedia.com/
Regards
Priyanka.P

Business Partner Items (0FC_BP_ITEMS) delta extraction help

Has anybody used 0FC_BP_ITEMS extractor? The documentation says that it supports delta, but it needs to be enabled.
I did enable delta extraction in IMG as SAP help site suggested. However, the documentation also says that before running delta, I need to update/initialize it in tcode FPOP. I go to that tcode, but I can hardly understand what to do in that tcode and there is no help or documentation I can find on how to initialize that delta extraction for 0FC_BP_ITEMS in OLTP system.
anybody came across any help document on FPOP tcode?
Thanks

Have you found a solution to the problems you were facing? is there any documentation you have regarding the BP Items extractor.

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 Add delta functionality to generic datasource

Hello all,
My requirement is to make a Generic Transactional Data source Extractor to Delta enabled.
The datasource doesnt contain either of the following delta enabling functionality
-> Date
->time stamp
->Numeric pointer.
Could anyone suggest idea how to add these in Generic Datasource so that it can be delta enabled
regards
Bala

Hi Bala,
Coding should be done checking th trasaction and the tables.
but i can provide outline .
add a field last changed on and write a code saying last changed on is equal to sy-datum.
i am not sure of the scenario where to write this code and after which line.you can take a decision.
check the link below
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c062a3a8-f44c-2c10-ccb8-9b88fbdcb008&overridelayout=true
Regards
Joga

Blog Clarification: Role of BI developer to get Deltas functional (part 1)

Hi,
I will appreciate some clarification on the following blog that I reviewed:
/people/swapna.gollakota/blog/2007/12/27/how-does-a-datasource-communicates-delta-with-bw
This blog seems to be suggesting that as a BI developer, you need to know the DELTA TYPEs for each datasource (selected in R3) and with that knowledge, you will be in a better position to choose Update types in ODS/DSO Overwrite or Addition, in the BW/BI environment.
At least that is what I came up with from the review.
1. For each datasource you activate as a BW developer in the BW environment, do you really need to go to R3 and study this datasource through the table RODELTAM to see the datasource type e.g. ABR, ABR1, etc and all the settings such as serialization =1 or 2?
2. I thought these datasouces, e.g. 2LIS_02_HDR are SAP delivered, ready to be used, isnu2019t it?
So, I understood that a decision will have to be made between ABR and ABR1 as the delta type.
i. whose responsibility is it to make such decisions?
ii. The R3 folks or the BW developer?
iii. What influences such decision making?
iv. In this table(RODELTAM), on R3, I saw several u201CXu201Ds under different columns, who sets these?
3. There were also discussions as to whether a datasource supports DSO/Cube or not?
Does this support the argument to study a datasource on R3 side in the table RODELTAM before using it?
Thanks

1. For each datasource you activate as a BW developer in the BW environment, do you really need to go to R3 and study this datasource through the table RODELTAM to see the datasource type e.g. ABR, ABR1, etc and all the settings such as serialization =1 or 2?
If you are a newbie and using it for the first time ofcourse you have to.But I would simply use RSA2 transaction than those tables.
2. I thought these datasouces, e.g. 2LIS_02_HDR are SAP delivered, ready to be used, isnu2019t it?
So, I understood that a decision will have to be made between ABR and ABR1 as the delta type.
i. whose responsibility is it to make such decisions?
ii. The R3 folks or the BW developer?
iii. What influences such decision making?
iv. In this table(RODELTAM), on R3, I saw several u201CXu201Ds under different columns, who sets these?
Ofcourse its BW developer who deals with BW related things.
iii. What influences such decision making?
Your datamodel.
3. There were also discussions as to whether a datasource supports DSO/Cube or not?
Does this support the argument to study a datasource on R3 side in the table RODELTAM before using it?
Datasource supports DSO/Cube, thats the whole point for determining the type of delta.
Hope this helps.

Delta functionality for LO datasource 2LIS_06_INV for enhanced Z fields

Hi Experts,
We have enhanced standard data source 2LIS_06_INV by appending some Z fields. When we are doing full load values are getting populated for the entire Z field but when we are running delta request, values for some Z fields are not getting populated.I have put the code to extract the value for Z fields in user exit under include ZXRSAU01.
If any one have faced this isuue , Please help me out .

Ur error is a very common error
need not panic
this can be solved
check whether all the v3 jobs are maintained properly or not
check whether the datasource is in active status or not
Pls assign me full points if answer satisfied to you
Regards ,
Subash Balakrishnan

EasyDMS 7 Delta Functionality

Hi,
I've been going through the changes in EasyDMS 7 and was wondering if anybody could point me to any documentation which provides more details.
I've gone through a presenation which lists the following enhancements (I have only mentioned the ones I need more info on). Would anybody know more specific details on this.
1. Support for latest MS Application including Office 2007 - office 2007 works fine in EasyDMS 6.0 as well. What other enhancemens does 7.0 offer.
2. Increase in scope for object link search - EasyDMS 7.0 and note 1171060 list the following. These were also available in 6.0. Any new object link searches available in 7.0 which were not previously available in 6.0?
DRAW Document
MARA Material
KNA1 Customer
LFA1 Vendor Master General Text
EQUI Equipment
IFLOT Functional Location
EKPO Purchase Order Item
EBAN Purchase Requist Item
PRPS WBS Element for Work Breadown Structure
3. ACL improvements, specifically traceability of changes to ACL's - how do I see this info?
Thanks,
Lashan
P.S: I couldn't get digital signature working on 7.0 (no issues in 6.0). If anybody has any ideas appreciate if you could post a solution in thread EasyDMS 7 - Digital signature error "you must make a digital signature...."

Read "Readme.txt' for details.
Few features new in 7.0 are.
- Microsoft Windows Vista 32 and 64 bit support.
- Improved Automatic Check-In/Check-Out functionality.(better handling with Excle and txt files and more featues like baloon notification)
- Several files with the same name in the same folder can be viewed, edited, or synchronized.(Very helpful offiline feature)
- SAP Product Lifecycle Management (SAP PLM) 7.0 process integration: You can create, edit, and delete documents in SAP PLM 7.0 using SAP Easy Document Management 7.0.
- support SAP PLM 7.0 authorization concept.(ACC)
- Supports SAP Standard installation. (Better installation and uipgrade similar to SAP GUI)
- Several registry entries can be centrally maintained to control the behavior of the application.(Centrally controlled registry- Better deployment control and user control as reg keys can be controlled from HKLM )
- With SAP ERP 6.0 Enhancement Package 4, you can track changes made to an ACL.

Delta functionality Release.

Where can I find a functioanlity comparison between CRM 5.0 and release 7.0. I cannot find it in the CRM Wiki.

Hello,
You can get it in SAP Service Market place.
The main difference between CRM 5.0 and 7.0 is that, 5.0 uses SAP GUI and in 7.0, you can have Web UI.
Best Regards,
Shanthala Kudva.

Issue with Delta in Function Module

Hi Team,
I have an issue with delta in Genric extraction using function module.Full load is working fine and i have taken post_date as delta field.plz chk the code if any delta related statements are missing.
FUNCTION ZRSAX_BIW_MANGEMENT_RAT .
""Local interface:
*" IMPORTING
*"     VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR
*"     VALUE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
*"     VALUE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
*"     VALUE(I_INITFLAG) TYPE SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
*"     VALUE(I_READ_ONLY) TYPE SRSC_S_IF_SIMPLE-READONLY OPTIONAL
*" TABLES
*"      I_T_SELECT TYPE SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL
*"      I_T_FIELDS TYPE SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL
*"      E_T_DATA STRUCTURE ZQMBW_FUJ_MANAGEMENT OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
Example: DataSource for table MANAGEMENT RATING
TABLES: ZQMBW_MANAGEMENT.
Auxiliary Selection criteria structure
DATA: L_S_SELECT TYPE SRSC_S_SELECT.
Maximum number of lines for DB table
STATICS: S_S_IF TYPE SRSC_S_IF_SIMPLE,
counter
          S_COUNTER_DATAPAKID LIKE SY-TABIX,
cursor
          S_CURSOR TYPE CURSOR.
RANGES: POST_DATE FOR ZMMTVEND_RATING-POST_DATE,
          VENDOR FOR ZMMTVEND_RATING-VENDOR.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF I_INITFLAG = SBIWA_C_FLAG_ON.
Initialization: check input parameters
                buffer input parameters
                prepare data selection
Check DataSource validity
    CASE I_DSOURCE.
      WHEN 'ZQMMANAGEMENT_DS'.
      WHEN OTHERS.
        IF 1 = 2. MESSAGE E009(R3). ENDIF.
this is a typical log call. Please write every error message like this
        LOG_WRITE 'E'                  "message type
                  'R3'                 "message class
                  '009'                "message number
                  I_DSOURCE   "message variable 1
                  ' '.                 "message variable 2
        RAISE ERROR_PASSED_TO_MESS_HANDLER.
    ENDCASE.
    APPEND LINES OF I_T_SELECT TO S_S_IF-T_SELECT.
Fill parameter buffer for data extraction calls
    S_S_IF-REQUNR    = I_REQUNR.
    S_S_IF-DSOURCE = I_DSOURCE.
    S_S_IF-MAXSIZE   = I_MAXSIZE.
Fill field list table for an optimized select statement
(in case that there is no 1:1 relation between InfoSource fields
and database table fields this may be far from beeing trivial)
    APPEND LINES OF I_T_FIELDS TO S_S_IF-T_FIELDS.
ELSE.                 "Initialization mode or data extraction ?
    IF S_COUNTER_DATAPAKID = 0.
Fill range tables BW will only pass down simple selection criteria
of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
      LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'VENDOR'.
        MOVE-CORRESPONDING L_S_SELECT TO VENDOR.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
          EXPORTING
            INPUT = VENDOR-LOW
          IMPORTING
            OUTPUT = VENDOR-LOW.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
          EXPORTING
            INPUT = VENDOR-HIGH
          IMPORTING
            OUTPUT = VENDOR-HIGH.
        APPEND VENDOR.
      ENDLOOP.
      LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'POST_DATE'.
        MOVE-CORRESPONDING L_S_SELECT TO POST_DATE.
        CONCATENATE L_S_SELECT-LOW6(4) L_S_SELECT-LOW3(2) L_S_SELECT-LOW+0(2) INTO POST_DATE-LOW.
        CONCATENATE L_S_SELECT-HIGH6(4) L_S_SELECT-HIGH3(2) L_S_SELECT-HIGH+0(2) INTO POST_DATE-HIGH.
        APPEND POST_DATE.
      ENDLOOP.
**Get Management rating details
      OPEN CURSOR WITH HOLD S_CURSOR FOR
      SELECT VENDOR POST_DATE OVERALL_MNGT_RAT OVERALL_DEV_RAT FROM ZMMTVEND_RATING WHERE VENDOR IN VENDOR AND POST_DATE IN POST_DATE .
    ENDIF.
Fetch records into interface table.
    FETCH NEXT CURSOR S_CURSOR
               APPENDING CORRESPONDING FIELDS
               OF TABLE E_T_DATA
               PACKAGE SIZE S_S_IF-MAXSIZE.
    S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
    IF SY-SUBRC <> 0.
      CLOSE CURSOR S_CURSOR.
      RAISE NO_MORE_DATA.
    ENDIF.
ENDIF.              "Initialization mode or data extraction ?
ENDFUNCTION.

Hi
Check URLs:
How to populate the ranges using FM for the SELECTs
Re: Generic Delta Function Module

Generic Delta extraction by Function module issue

Hello Experts,
Please help !!!
I have problem for delta extraction by Function module. For the full load, I wrote function module based on RSAX_BIW_GET_DATA_SIMPLE. It works fine.
But I would like to have the delta load enabled. Therefore, I modified the datasource, add a delta specific field u2018ztimestampu2019, which type is calendar day.
Then I create a function module based on template u2018RSAX_BIW_GET_DATAu2019, as this support the upload mode. But when I test this datasource in RSA3, no matter itu2019s full load or initial delta load, it always send me an error, u201CErrors occurred during the extractionu201D.
I had some debug, and found that there is no value for i_isource when my function module is called. Therefore it raised the exception.
But I do not have the chance to debug my code for the delta logic, can somebody help to check?
I also check the entries in ROOSOURCE,
For my datasource ZTRNREC_FM_DELTA, The DELTA value is u2018AIEu2019, and extraction method is u2018F2u2019, should I change them to DELTA= u2018Du2019 and extraction method to u2018F1u2019? Where to change?
FUNCTION ZRSAX_TRAININGREC_DELTA.
""Local Interface:
*" IMPORTING
*"     VALUE(I_REQUNR) TYPE SBIWA_S_INTERFACE-REQUNR
*"     VALUE(I_ISOURCE) TYPE SBIWA_S_INTERFACE-ISOURCE OPTIONAL
*"     VALUE(I_MAXSIZE) TYPE SBIWA_S_INTERFACE-MAXSIZE OPTIONAL
*"     VALUE(I_INITFLAG) TYPE SBIWA_S_INTERFACE-INITFLAG OPTIONAL
*"     VALUE(I_UPDMODE) TYPE SBIWA_S_INTERFACE-UPDMODE OPTIONAL
*"     VALUE(I_DATAPAKID) TYPE SBIWA_S_INTERFACE-DATAPAKID OPTIONAL
*"     VALUE(I_PRIVATE_MODE) OPTIONAL
*"     VALUE(I_CALLMODE) LIKE ROARCHD200-CALLMODE OPTIONAL
*"     VALUE(I_REMOTE_CALL) TYPE SBIWA_FLAG DEFAULT SBIWA_C_FLAG_OFF
*" TABLES
*"      I_T_SELECT TYPE SBIWA_T_SELECT OPTIONAL
*"      I_T_FIELDS TYPE SBIWA_T_FIELDS OPTIONAL
*"      E_T_DATA STRUCTURE ZTRN_REC_TIME OPTIONAL
*"      E_T_SOURCE_STRUCTURE_NAME OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
The input parameter I_DATAPAKID is not supported yet !
Example: InfoSource containing TADIR objects
Auxiliary Selection criteria structure
DATA: l_s_select TYPE sbiwa_s_select.
Maximum number of lines for DB table
STATICS: l_maxsize TYPE sbiwa_s_interface-maxsize,
          S_S_IF TYPE SRSC_S_IF_SIMPLE,
          S_COUNTER_DATAPAKID LIKE SY-TABIX.
Parameter I_PRIVATE_MODE:
Some applications might want to use this function module for other
purposes as well (e.g. data supply for OLTP reporting tools). If the
processing logic has to be different in this case, use the optional
parameter I_PRIVATE_MODE (not supplied by BIW !) to distinguish
between BIW calls (I_PRIVATE_MODE = SPACE) and other calls
(I_PRIVATE_MODE = X).
If the message handling has to be different as well, define Your own
messaging macro which interprets parameter I_PRIVATE_MODE. When
called by BIW, it should use the LOG_WRITE macro, otherwise do what
You want.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF i_initflag = sbiwa_c_flag_on.
Initialization: check input parameters
                buffer input parameters
                prepare data selection
The input parameter I_DATAPAKID is not supported yet !
Invalid second initialization call -> error exit
    IF NOT g_flag_interface_initialized IS INITIAL.
      IF 1 = 2. MESSAGE e008(r3). ENDIF.
      log_write 'E'                    "message type
                'R3'                   "message class
                '008'                  "message number
                ' '                    "message variable 1
                ' '.                   "message variable 2
      RAISE error_passed_to_mess_handler.
    ENDIF.
Check InfoSource validity
    CASE i_isource.
      WHEN 'ZTRNREC_FM_DELTA'.
      WHEN OTHERS.
        IF 1 = 2. MESSAGE e009(r3). ENDIF.
        log_write 'E'                  "message type
                  'R3'                 "message class
                  '009'                "message number
                  i_isource            "message variable 1
                  ' '.                 "message variable 2
        RAISE error_passed_to_mess_handler.
    ENDCASE.
Check for supported update mode
    CASE i_updmode.
      WHEN 'F'.
      WHEN 'D'.
      WHEN 'R'.
      WHEN OTHERS.
        IF 1 = 2. MESSAGE e011(r3). ENDIF.
        log_write 'E'                  "message type
                  'R3'                 "message class
                  '011'                "message number
                  i_updmode            "message variable 1
                  ' '.                 "message variable 2
        RAISE error_passed_to_mess_handler.
    ENDCASE.
Check for obligatory selection criteria
    APPEND LINES OF i_t_select TO g_t_select.
Fill parameter buffer for data extraction calls
    g_s_interface-requnr    = i_requnr.
    g_s_interface-isource   = i_isource.
    g_s_interface-maxsize   = i_maxsize.
    g_s_interface-initflag = i_initflag.
    g_s_interface-updmode   = i_updmode.
    g_s_interface-datapakid = i_datapakid.
    g_flag_interface_initialized = sbiwa_c_flag_on.
Fill field list table for an optimized select statement
(in case that there is no 1:1 relation between InfoSource fields
and database table fields this may be far from beeing trivial)
    APPEND LINES OF i_t_fields TO g_t_segfields.
ELSE.                 "Initialization mode or data extraction ?
Data transfer: First Call      OPEN CURSOR + FETCH
               Following Calls FETCH only
LOOP AT G_T_SELECT INTO L_S_SELECT
        WHERE FIELDNM = 'ZTIMESTAMP'.
ENDLOOP.
      IF G_COUNTER_DATAPAKID = 0.
        IF L_S_SELECT-LOW = '' AND L_S_SELECT-HIGH = ''.
        OPEN CURSOR WITH HOLD G_CURSOR FOR
            SELECT (g_t_fields)
            FROM ZTRN_REC_TIME.
        ELSE.
          OPEN CURSOR WITH HOLD G_CURSOR FOR
            SELECT (g_t_fields)
            FROM ZTRN_REC_TIME
            WHERE ZTIMESTAMP >= L_S_SELECT-LOW
              AND ZTIMESTAMP <= L_S_SELECT-HIGH.
        ENDIF.
      ENDIF.
FETCH NEXT CURSOR G_CURSOR
               APPENDING CORRESPONDING FIELDS
               OF TABLE E_T_DATA
               PACKAGE SIZE S_S_IF-MAXSIZE.
    IF SY-SUBRC <> 0.
      CLOSE CURSOR G_CURSOR.
      RAISE NO_MORE_DATA.
    ENDIF.
    S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
ENDIF.
ENDFUNCTION.
I found some similar issue in this forum by link
Generic Extractor Delta Function Module code, but still I could not get clear answer.
Can you please help me:
1)     why there is no value for i_source , how to fix it?
2)     For the delta logic for ztimestemp, is it correct?
3)     Need I modify the entries in ROOSOURCE ?
Thanks a lot !!!

Hello Andre,
        Thanks a lot for your help. I did some change , but still does not work. Could you please help check.
Now the source code are the following, It's based on the RSAX_BIW_GET_DATA_SIMPLE, as you confirm that this also supply the update mode (full, initial delta, delta).
FUNCTION RSAX_BIW_GET_DATA_TRAININGREC1.
""Local Interface:
*" IMPORTING
*"     VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR
*"     VALUE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
*"     VALUE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
*"     VALUE(I_INITFLAG) TYPE SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
*"     VALUE(I_READ_ONLY) TYPE SRSC_S_IF_SIMPLE-READONLY OPTIONAL
*"     VALUE(I_REMOTE_CALL) TYPE SBIWA_FLAG DEFAULT SBIWA_C_FLAG_OFF
*" TABLES
*"      I_T_SELECT TYPE SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL
*"      I_T_FIELDS TYPE SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL
*"      E_T_DATA STRUCTURE ZTRN_REC_TIME OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
Auxiliary Selection criteria structure
DATA: L_S_SELECT TYPE SRSC_S_SELECT.
Maximum number of lines for DB table
STATICS: S_S_IF TYPE SRSC_S_IF_SIMPLE,
counter
          S_COUNTER_DATAPAKID LIKE SY-TABIX,
cursor
          S_CURSOR TYPE CURSOR.
Select ranges
RANGES:
        L_R_ZTIMESTAMP FOR ZTRN_REC_TIME-ZTIMESTAMP.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF I_INITFLAG = SBIWA_C_FLAG_ON.
Initialization: check input parameters
                buffer input parameters
                prepare data selection
Check DataSource validity
    CASE I_DSOURCE.
      WHEN 'ZTRNREC_FM'.
      WHEN OTHERS.
        IF 1 = 2. MESSAGE E009(R3). ENDIF.
this is a typical log call. Please write every error message like this
        LOG_WRITE 'E'                  "message type
                  'R3'                 "message class
                  '009'                "message number
                  I_DSOURCE   "message variable 1
                  ' '.                 "message variable 2
        RAISE ERROR_PASSED_TO_MESS_HANDLER.
    ENDCASE.
    APPEND LINES OF I_T_SELECT TO S_S_IF-T_SELECT.
Fill parameter buffer for data extraction calls
    S_S_IF-REQUNR    = I_REQUNR.
    S_S_IF-DSOURCE = I_DSOURCE.
    S_S_IF-MAXSIZE   = I_MAXSIZE.
Fill field list table for an optimized select statement
(in case that there is no 1:1 relation between InfoSource fields
and database table fields this may be far from beeing trivial)
    APPEND LINES OF I_T_FIELDS TO S_S_IF-T_FIELDS.
ELSE.                 "Initialization mode or data extraction ?
Data transfer: First Call      OPEN CURSOR + FETCH
               Following Calls FETCH only
First data package -> OPEN CURSOR
    IF S_COUNTER_DATAPAKID = 0.
      LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'ZTIMESTAMP'.
      MOVE-CORRESPONDING L_S_SELECT TO L_R_ZTIMESTAMP.
      APPEND L_R_ZTIMESTAMP.
      ENDLOOP.
Determine number of database records to be read per FETCH statement
from input parameter I_MAXSIZE. If there is a one to one relation
between DataSource table lines and database entries, this is trivial.
In other cases, it may be impossible and some estimated value has to
be determined.
     IF L_S_SELECT-LOW = '' AND L_S_SELECT-HIGH = ''.
        OPEN CURSOR WITH HOLD S_CURSOR FOR
        SELECT (S_S_IF-T_FIELDS)
        FROM ZTRN_REC_TIME.
        ELSE.
        OPEN CURSOR WITH HOLD G_CURSOR FOR
        SELECT (S_S_IF-T_FIELDS)
        FROM ZTRN_REC_TIME
        WHERE ZTIMESTAMP >= L_S_SELECT-LOW
        AND ZTIMESTAMP <= L_S_SELECT-HIGH.
     ENDIF.
    ENDIF.                             "First data package ?
Fetch records into interface table.
named E_T_'Name of extract structure'.
    FETCH NEXT CURSOR S_CURSOR
               APPENDING CORRESPONDING FIELDS
               OF TABLE E_T_DATA
               PACKAGE SIZE S_S_IF-MAXSIZE.
    IF SY-SUBRC <> 0.
      CLOSE CURSOR S_CURSOR.
      RAISE NO_MORE_DATA.
    ENDIF.
    S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
ENDIF.              "Initialization mode or data extraction ?
ENDFUNCTION.
I think it already includes the important statements you suggested.
I test this FM in RSA3, for the Full load mode, it works fine. Also if I checked the debug mode in execution , it will stop in the code and let me debug.
But when I choose other mode, like 'initializion of the delta transfer' or simulation of initial delta, I always get error 'error occurs during the extraction' .. even I choose debug mode, but it could not enter the code for debug..
Till now I did not see any parameter or value for the upload mode..
Another questions is that, in RSO2, I define Ztimestamp as my delta field.. But , can I add other field as selection condition in the datasource definition, and has its range table in this function module ?
Should I change the entries in ROOSOURCE for this datasource ??
Please let me know your feedback, do you have some concret example for generic delta extraction ?
Thanks a lot !

0FC_BP_ITEMS delta functionality

Similar Messages

Maybe you are looking for