Generic Datasource--plz confirm

Hi gurus,
i have created a generic datasource but unfortunately i don't have any number, date field which i can use as delta field...so as per the document on SDN which says that by using Business Transaction Events we can get the delta capability
but i am not able to find any BTE for production orders which i can use for delta...so can somebody help on this like how ...enable the delta capability as well as plz help to find BTE so that i can use it.
thanks and regards
Neel
Message was edited by: Neel Kamal
Message was edited by: Neel Kamal
Message was edited by: Neel Kamal

Hi Neel
Pseudo delta is not generic delta. What I had advised is you can create pseudo delta if you are not able to find date field for generic delta mechanism.
1.Add both date fields to generic datasource alongwith all other fields.
2.You have to assign this datasource to infosource in BW and map the transfer rules.
3. Create 2 infopackages for this -one for CREATED ON - will load new records created yesterday & other for CHANGED ON - will load changed records yesterday.
4. schedule both these infopackages to load daily.
Also want to re-iterate the fact that this approach is not recommended over creating a delta enabled generic datasource. But in abscence of date field for generic delta mechanism.
Hope this helps
Regards
Pradip

Similar Messages

Business scenarios on SD and MM modules for generic datasources and enhance

Hi,
Can anybody send some documents on SD and MM module on generic datasource and on enhancements.Pl send it to my MailID:[email protected]
Thanks,
Chinna

Hi,
MM Process flow:
The typical procurement cycle for a service or material consists of the following phases:
1. Determination of Requirements
Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.
2. Source Determination
The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.
3. Vendor Selection and Comparison of Quotations
The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.
4. Purchase Order Processing
The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.
5. Purchase Order Follow-Up
The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.
6. Goods Receiving and Inventory Management
Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and underdeliveries of ordered goods.
7. Invoice Verification
The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.
Common Tables used by SAP MM:
Below are few important Common Tables used in Materials Management Modules:
EINA Purchasing Info Record- General Data
EINE Purchasing Info Record- Purchasing Organization Data
MAKT Material Descriptions
MARA General Material Data
MARC Plant Data for Material
MARD Storage Location Data for Material
MAST Material to BOM Link
MBEW Material Valuation
MKPF Header- Material Document
MSEG Document Segment- Material
MVER Material Consumption
MVKE Sales Data for materials
RKPF Document Header- Reservation
T023 Mat. groups
T024 Purchasing Groups
T156 Movement Type
T157H Help Texts for Movement Types
MOFF Lists what views have not been created
A501 Plant/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History per Purchasing Document
EKET Scheduling Agreement Schedule Lines
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPO Purchasing Document Item
IKPF Header- Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor Master (General section)
LFB1 Vendor Master (Company Code)
NRIV Number range intervals
RESB Reservation/dependent requirements
T161T Texts for Purchasing Document Types
Transaction Codes:
RFQ to Vendor - ME41
Raising Quotation - ME47
Comparison of Price - ME49
Creation of PO - ME21N
Goods Receipt - MIGO
Invoice (Bill PAssing) - MIRO
Goods Issue - MB1A
Physical Inventory - MI01( Create doc)
MI04 (Enter Count)
MI07 (Post)
Also please check this links.
http://www.sapgenie.com/sapfunc/mm.htm
http://www.sap-basis-abap.com/sapmm.htm
SD Process Flow:
The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customers telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.
Transaction Codes:
Inquiry - VA11/VA12/VA13
Quotation - VA21/VA22/VA23
Sales Order - VA01/VA02/VA03
Delivery - VL01N/VL02N/VL03N
Billing/Invoicing - VF01/VF02/VF03
Also please check this links.
http://www.sapgenie.com/sapfunc/sd.htm
http://www.sap-basis-abap.com/sapsd.htm
http://www.sapgenie.com/abap/tables_sd.htm
Production Planning:
For example, consider a pump manufacturing plant, based on the customer requirement, planning is done for future months ( we plan for a qty on particular
date). Pump is an assembly - were main component would be manufactured in the plant and others would be procured. As PP, we are concerned only in the inhouse
manufacturing but the final assembly (considering BOM) can be done only if the procured components are available. MRP helps in planning the shortage, on
particular date based on the planned date. Work center (ex. lathe) place the components are machined/assembled (were the operation is done). Sequence of
operation is routing (lead time scheduling data is got from routing). In the MRP Run,basic or lead time scheduling (need to know when to start/finish date)
is done. On creation of the production order, system checks for which BOM and routing to be picked up (if there are many routings or BOM for that particular
finished product). Availabilty checks for material,PRT and capacity needs to be done. on release of the order, confirmation of the order can be done (on
completion of the order or after manufacturing the quantities). GI and GR have to be done.PP flow ends here
step 1: creation of master data (Material master,BOM,Work center,Routing)
step 2: Planning - can be done by Planned independent requirement (MD61), Independent requirement (MD81).
we plan for a quantity, on which date (it would be finish date).
step 3: MD04 -stock/requirement lsit (plan made can be viewed in MD04)
step 4: MRP run - MD02, PIR is converted into Planned order
step 5:Planned order to be converted production order - CO40, CO41
step 6: production order to be released - CA02
step 7: confirm the production order (order confirmation-CO15 (after which GI and GR is done)
assign pts if helpful...

Error while transporting Generic Datasource in R/3

Hi All,
I have created a generic datasource(R/3) on a view. As it was in $TMP, I have assigned the datasource, ZABCD, and the view, ZVIEW to a devlopment package and also to a transport request. I released the Transport request and when I tried to import it into Q, it throwed me an error with below messages:
Extract structure ZOX**** is not active
The extract structure ZOX**** of the DataSource ZABCD is invalid
Errors occurred during post-handling RSA2_DSOURCE_AFTER_IMPORT for OSOA L
The errors affect the following components:
BC-BW (SAP Business Information Warehouse Extractors)
The extract structure ZOX**** is the structure used by the datsource. I forgot to assign that to the earlier TR and I think the error is because the structure is missing in the TR. Am I correct?
How should I deal with it now? DO I need to create a new TR with this structure alone as the earlier TR is already released?
Thanks,
RPK.

As you comment it is possible error was not include the structure in earlier TR.
You can create, in se09 or se10, an empty TR. In these transactions you have a buttoun with a box drawed. Set focus on your new empty TR and push button.
Add object from TR transported with error and the missed structure.

Generic DataSource using InfoSet on BI 7.0

Hi gurus,
I need to extract data from a InfoCube through a generic DataSource. I have created an InfoSet Query based on this InfoCube and I have noticed this kind of InfoSet is not the same that is used by Tcode RSO2.
Does anybody know if there is any way to get this vai generic DataSource?
I need to get data from Infocube because de Delta Control must be the package number.
Thanks in advance,
Silvio Messias.
P.S.: The version of my environment is 7.0.

Hi Ashok,
Into the Tcode RSO2 (Generic DataSource) I have the option to collect data from an InfoSet. This InfoSet must be created through Tcode SQ02, right?
I woult like to get data from a Infoset Query based on InfoCube, created through RSA1 on BI 7.0.
Is there any way to do it?
Thanks for your help,
Silvio Messias.

Can someone plz confirm me that how i can change or update the security questions related to my apple id? as i have been never put them since i create my apple id but now due to some security reasons its asking me again and again the answers. i am unable

can someone plz confirm me that how i can change or update the security questions related to my apple id? as i have been never put them since i create my apple id but now due to some security reasons its asking me again and again the answers. i am unable to go through the process. thanks.

Some Solutions for Resetting Forgotten Security Questions: Apple Support Communities

Generic datasource creation in IS-HTCM

Gurus
Has anyone worked with IS-HTCM on CRM? and creating of reports with HTCM as source system?
We want to create a few generic Datasources ....BWA1 is one option and RSO2 is the other...But can the BWA1 concept of CRM be tried in HTCM as well? or do we have to resort to RSO2?
Thanks in advance
Regards
Prakash

Hi Prakash,
for generic datasources the transaction will be rso2 in all systems.
Siggi

Generic datasource by function module to fetch data from multiple tables?

I'm writing a function module to fetch price, for generic datasource.
At first, extract test is OK. But InfoPackage never stop when loading data to PSA in BW.
And I find the example codes:
     OPEN CURSOR WITH HOLD S_CURSOR FOR
      SELECT (S_S_IF-T_FIELDS) FROM SFLIGHT
                               WHERE CARRID IN L_R_CARRID AND
                                     CONNID IN L_R_CONNID.
    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.
There using Cursor to fetch data package by package, and raise exception NO_MORE_DATA to stop the loading process.
Now I fetch data from multiple tables, I don't think I can use Cursor.
Then How can I handle this?
Thanks a lot.

Thanks
IF IT_999[] IS INITIAL.
    SELECT A~KNUMH A~MATNR A~KSCHL VKORG VTWEG A~DATBI A~DATAB KBETR KMEIN KPEIN C~MTART APPENDING CORRESPONDING FIELDS OF
      TABLE TP_DATA
        FROM A999 AS A
          INNER JOIN KONP AS B
              ON A~KNUMH = B~KNUMH
          INNER JOIN MARA AS C
             ON A~MATNR = C~MATNR
*          FOR ALL ENTRIES IN IT_999
                WHERE
*      A~KNUMH = IT_999-KNUMH AND
       ( ( A~KSCHL = 'ZPRC' AND VKORG = 'Z000' AND VTWEG = 'Z1' ) OR
                      ( A~KSCHL = 'ZPRD' AND VKORG = 'A000' AND VTWEG = 'Y3' ) ) AND
*                      A~DATBI >= SY-DATUM AND
                      LOEVM_KO = ''.
    SELECT A~KNUMH A~MATNR A~KSCHL VKORG VTWEG A~DATBI A~DATAB KBETR AS KHETR KMEIN KPEIN C~MTART APPENDING CORRESPONDING FIELDS OF
      TABLE TP_DATA
        FROM A999 AS A
          INNER JOIN KONP AS B
              ON A~KNUMH = B~KNUMH
          INNER JOIN MARA AS C
             ON A~MATNR = C~MATNR
*          FOR ALL ENTRIES IN IT_999
                WHERE
*      A~KNUMH = IT_999-KNUMH AND
      A~KSCHL = 'ZPR3' AND A~VKORG = 'I000' AND
*                      DATBI >= SY-DATUM AND
                      LOEVM_KO = ''.
ENDIF.
IF IT_997[] IS INITIAL.
    SELECT A~KNUMH A~MATNR A~KSCHL VTWEG A~DATBI A~DATAB KBETR AS KHETR KMEIN KPEIN C~MTART APPENDING CORRESPONDING FIELDS OF
      TABLE TP_DATA
        FROM A997 AS A
          INNER JOIN KONP AS B
              ON A~KNUMH = B~KNUMH
          INNER JOIN MARA AS C
             ON A~MATNR = C~MATNR
*          FOR ALL ENTRIES IN IT_997
                WHERE
*      A~KNUMH = IT_997-KNUMH      AND
      A~KSCHL = 'ZPRA' AND VTWEG = 'Y1' AND
*                      DATBI >= SY-DATUM AND
                  LOEVM_KO = ''.
ENDIF.
IF IT_996[] IS INITIAL.
    SELECT A~KNUMH A~MATNR A~KSCHL A~DATBI A~DATAB KBETR AS KHETR KMEIN KPEIN C~MTART APPENDING CORRESPONDING FIELDS OF
       TABLE TP_DATA
         FROM A996 AS A
           INNER JOIN KONP AS B
               ON A~KNUMH = B~KNUMH
           INNER JOIN MARA AS C
              ON A~MATNR = C~MATNR
*          FOR ALL ENTRIES IN IT_996
                WHERE
*      A~KNUMH = IT_996-KNUMH AND
      A~KSCHL = 'ZPRB' AND
*                       DATBI >= SY-DATUM AND
      LOEVM_KO = ''.
ENDIF.
SELECT   MATNR     "u7269u6599u53F7u7801
           MEINH     "u4ED3u50A8u5355u4F4Du7684u5907u7528u8BA1u91CFu5355u4F4D
           UMREZ     "u57FAu672Cu8BA1u91CFu5355u4F4Du8F6Cu6362u5206u5B50
           UMREN     "u8F6Cu6362u4E3Au57FAu672Cu8BA1u91CFu5355u4F4Du7684u5206u6BCD
      FROM MARM
      INTO CORRESPONDING FIELDS OF TABLE IT_MARM
       FOR ALL ENTRIES IN TP_DATA
     WHERE MATNR = TP_DATA-MATNR AND MEINH = TP_DATA-KMEIN.
LOOP AT TP_DATA.
    IF TP_DATA-KPEIN NE 0.
      TP_DATA-KBETR = TP_DATA-KBETR / TP_DATA-KPEIN.
      TP_DATA-KHETR = TP_DATA-KHETR / TP_DATA-KPEIN.
    ENDIF.
    IF TP_DATA-KSCHL = 'ZPRA'.
*       TP_DATA-MEINH = 'ZI'.
*      TP_DATA-KSCHL = 'B4'.
      IF TP_DATA-KMEIN = 'ZI'.
        TP_DATA-KBETR = TP_DATA-KHETR / '1.17'.
      ELSE.
        READ TABLE IT_MARM INTO WA_MARM1 WITH KEY MATNR = TP_DATA-MATNR MEINH = TP_DATA-KMEIN.
*           READ TABLE IT_MARM INTO WA_MARM2 WITH KEY MATNR = TP_DATA-MATNR MEINH = 'CT'.
        TP_DATA-KHETR = TP_DATA-KHETR * WA_MARM1-UMREN / WA_MARM1-UMREZ.
*           * WA_MARM2-UMREZ / WA_MARM2-UMREN.
        TP_DATA-KBETR = TP_DATA-KHETR / '1.17'.
      ENDIF.
    ELSEIF TP_DATA-KSCHL = 'ZPRB'.
*      TP_DATA-KSCHL = 'L0'.
*       TP_DATA-MEINH = 'ZI'.
      IF TP_DATA-KMEIN = 'ZI'.
        TP_DATA-KBETR = TP_DATA-KHETR / '1.17'.
      ELSE.
        READ TABLE IT_MARM INTO WA_MARM1 WITH KEY MATNR = TP_DATA-MATNR MEINH = TP_DATA-KMEIN.
*           READ TABLE IT_MARM INTO WA_MARM2 WITH KEY MATNR = TP_DATA-MATNR MEINH = 'BAG'.
        TP_DATA-KHETR = TP_DATA-KHETR * WA_MARM1-UMREN / WA_MARM1-UMREZ.
*           * WA_MARM2-UMREZ / WA_MARM2-UMREN.
        TP_DATA-KBETR = TP_DATA-KHETR / '1.17'.
      ENDIF.
    ELSEIF TP_DATA-KSCHL = 'ZPRC' OR TP_DATA-KSCHL = 'ZPRD'.
*       TP_DATA-MEINH = 'ZI'.
      IF TP_DATA-KMEIN = 'ZI'.
        TP_DATA-KHETR = TP_DATA-KBETR * '1.17'.
      ELSE.
        READ TABLE IT_MARM INTO WA_MARM1 WITH KEY MATNR = TP_DATA-MATNR MEINH = TP_DATA-KMEIN.
*           READ TABLE IT_MARM INTO WA_MARM2 WITH KEY MATNR = TP_DATA-MATNR MEINH = 'WZI'.
        TP_DATA-KBETR = TP_DATA-KBETR * WA_MARM1-UMREN / WA_MARM1-UMREZ.
*           * WA_MARM2-UMREZ / WA_MARM2-UMREN.
        TP_DATA-KHETR = TP_DATA-KBETR * '1.17'.
      ENDIF.
    ELSEIF TP_DATA-KSCHL = 'ZPR3'.
*      TP_DATA-KSCHL = 'B2'.
      IF TP_DATA-KMEIN = 'ZI'.
        TP_DATA-KBETR = TP_DATA-KHETR / '1.17'.
      ELSE.
        READ TABLE IT_MARM INTO WA_MARM1 WITH KEY MATNR = TP_DATA-MATNR MEINH = TP_DATA-KMEIN.
*           READ TABLE IT_MARM INTO WA_MARM2 WITH KEY MATNR = TP_DATA-MATNR MEINH = 'BAG'.
        TP_DATA-KHETR = TP_DATA-KHETR * WA_MARM1-UMREN / WA_MARM1-UMREZ.
*           * WA_MARM2-UMREZ / WA_MARM2-UMREN.
        TP_DATA-KBETR = TP_DATA-KHETR / '1.17'.
      ENDIF.
    ENDIF.
    TP_DATA-MEINH = '01'.
    MODIFY TP_DATA.
E_T_DATA-MATNR =   TP_DATA-MATNR.
E_T_DATA-KSCHL =   TP_DATA-KSCHL.
E_T_DATA-KHETR =   TP_DATA-KHETR.
E_T_DATA-KBETR =   TP_DATA-KBETR.
E_T_DATA-KMEIN =   TP_DATA-KMEIN.
E_T_DATA-DATAB =   TP_DATA-DATAB.
E_T_DATA-DATBI =   TP_DATA-DATBI.
APPEND E_T_DATA.
    CLEAR WA_MARM1.
    CLEAR WA_MARM2.
ENDLOOP.
Edited by: Shen Peng on Oct 20, 2010 10:09 AM

Problem in creating a generic datasource with infoset

Dear Expert,
I have to create a generic datasource with infoset. I linked the infoset with a test program below. In the program, I have one selection option, which is s_order. After creating an infoset and a datasource, this selection option 'SELECT_S_ORDER' is added to my extract structure. However, after try filtering with this SELECT_S_ORDER, it doesn't filter data at all. Why? I want to filter data with my s_order.
REPORT ZBI_DS_TEST.
tables: vbak.
* DATA
field-symbols: <vbak> type vbak.
data:   t_vbak      type table of vbak,
            w_vbak     type vbak,
            t_vbak2    type table of vbak,
            w_vbak2    type vbak.
* SELECT-OPTIONS
selection-screen begin of block b1 with frame title text-001.
    select-options: s_order   for vbak-vbeln.
selection-screen end of block b1.
    start-of-selection.
* <Query_head>
   perform sub_select_data.
   loop at t_vbak into w_vbak2.
     move-corresponding w_vbak2 to vbak.
* <Query_body>
   endloop.
*&      Form sub_select_data
*      Select data
FORM sub_select_data .
    select *
    into    table t_vbak
    from   vbak
    where vtweg = 'IP'.
ENDFORM.                    " sub_select_data

What do you mean by linking program with infoset?
Do you get the field in your RSA3 Tcode?

Delta issue on a Generic Datasource

Hi
   I had a Generic Datasource on a Z table.
   The Z table had a Date field on which Delta is based.The Postings are performed manually.
How to solve the delta issue in the below scenario.
Ex; A user made a manual posting with a date 09AUG2010 today and delta is extracted to BW.
    But tommorow a used made another posting with a date 14JULY2010....
Currently that record is not being extracted....how can i resolve this
Thanks

Hi,
Once the data source is created you will extract the data till that date and as the delta is set it will fetch the newly updated records .But i dont think one can post with the back dates in R/3 side.
If i'm not wrong if you are asking regarding record got missed out them wht need to be done?
Then do the repair full request and pull the missed delta records and it wont effect the delta settings.
Regards
KP

Invalid Extract Structure error while creating "Generic DataSource" on a view...

Dear All,
I have created a view on following tables MARA, AFKO and MSEG. The Table/Join condition is as follow:
AFKO--AUFNR = MSEG--AUFNR
AFKO--PLNBEZ = MARA--MATNR
I have included all the fields from MSEG and other all fields from MARA and AFKO. The view is created successfully and contents/records are also being fetched/displayed from this view.
See screen shot as well:
But when I go to RSO2 to create a "Generic DataSource" on this view. I get a series of warning messages and then error message "Invalid Extract Structure" and therefore I'm unable to create my DataSource on this view. See below screen shots of warning and error messages.
Other warning messages are as follow:
Field GAMNG with reference field MEINS: Reference table MARA is replaced by ZOXPRD0150
Field PLSVB with reference field PLNME: Reference table PLKO is replaced by ZOXPRD0150
Field PLSVN with reference field PLNME: Reference table PLKO is replaced by ZOXPRD0150
Field LODIV with reference field MEINS: Reference table MARA is replaced by ZOXPRD0150
Following is the screen shot of error message:
1. How can I get rid of this error message and be able to create my "Generic DataSource" on top of this "View"?
2. What should I do to resolve the above warning and error messages?
I will appreciate your reply.
Many thanks!
Tariq Ashraf

Hi Vipul,
as you can find in CKIS table, the reference feild for value feild "WERTN" is missing.
As per the table the reference feild is HWAER. This should have been used in place of FWAER.
Try mentioning this in your view and this should work.
Also I am a little enthusiastic to know, what are you trying to get from the datasource.
If you are trying to get the cost estimate of multi level BOM, not (just one child level), then this approach may not work.
There is a BAPI that gives such itemization split. Just FYI, in case you are looking for multi level explosion.
"BAPI_COSTESTIMATE_ITEMIZATION".
Hope this helps.
Naveen.A

Error while creating Generic Datasource

Hi,
I try to create generic datasource using function module in RSO2, it is giving the following errors and the datasource is not creating.
"Units field WAERK for field TOT_REV of DataSource ZIPO_TRANSCATION is hidden Message no. R8147"
"Units field WAERK for field EXP_REV of DataSource ZIPO_TRANSCATION is hidden Message no. R8147"
TOT_REV and EXP_REV fileds datatype is CURR.
Fuction Module is working fine. Please give me any inputs, it is very urgent.
Best Regards,
SGK.

hi,
let WAERS field be present in your structure defn
In the Currency/Quantity fields tab of your extract structure give the refernce of the same structure and same field
Regards,
Sampat

Generic Datasource on table IMRG in R/3- delta on timestamp is it ok ?

Hi
I am creating Generic datasource based on table IMRG in R/3, This has stoppages related data. which we need in BI report. There is a field for Time-stamp in the table, i have checked values in table IMRG, but in R/3 it shows no data for the time-stamp.
Now i want to create delta basis for this generic datasource based on table, so shall i create delta based on time-stamp or date field.
If I create delta based on time-stamp will it create problem in delta extraction subsequently? Please share your experience in such a cases.

There is a field for Time-stamp in the table, i have checked values in table IMRG, but in R/3 it shows no data for the time-stamp.
Delta specific field should be something which defines changes in your table, not something which is blank always.Based on the change in this delta specific field only delta will be pulled.Having it blank will never pull you delta.
Hope this helps.

Error when activating an R/3 generic datasource in BW

Hi
I've created a generic datasource in R/3 4.6C system using a table view over R/3 standard Project System tables with joins. This datasource has been activated. I then replicated this generic datasource in BI7 datawarehousing environment. The replication went ok and I could see the R/3 generic datasource in RSA1. When I tried to activate this datasource I received this error message:
Error when activating DataSource ZPROJECT_ATTR Message no. RSO404
I didnt have similar problem with the other generic datasources.
I'm currently working on Netweaver 2004s BI support pack 10 environment.
Please let me know how to fix this problem.
Many thanks,
Anthony

Hi Anthony,
Do go through the note's detailed text and do listen to this advice from an old man. Do read the section below in the note and do assign some points to this geezer "lying" on his deathbed.
Quote from the note (this one rhymes..yaa):
Source system = R/3 Release 4.0B ff (all subsequent releases including 4.7 and so on)
= BW Datamart 2.0B, 2.1C, 3.0B, 3.10, 3.50, 7.00 ff
= CRM release 2.0, 3.0, 4.0 ff
unquote...
Cheers
Neeraj

Problem while transporting generic datasource to test box

Hi Gurus,
I am trying to transport Generic datasource from SCM Dev to SCM Test box. Datasource is created with custom table in SCM.
It is throwing me RC8.
Start of the after-import method RS_ISMP_AFTER_IMPORT for object type(s) ISMP (Activation Mode)
DataSource ZGATPUPLOAD does not exist in source system TA6CLNT010 of version A
Mapping between data source ZGATPUPLOAD and source system TA6CLNT010 is inconsistent
DataSource ZGATPUPLOAD does not exist in source system TA6CLNT010 of version A
Field /BIC/ZCSHIPTO will not be delivered from DataSource ZGATPUPLOAD in source system TA6CLNT010
Field CALWEEK will not be delivered from DataSource ZGATPUPLOAD in source system TA6CLNT010
Field FIXPEGQTY will not be delivered from DataSource ZGATPUPLOAD in source system TA6CLNT010
Field LOC will not be delivered from DataSource ZGATPUPLOAD in source system TA6CLNT010
Field MATNR will not be delivered from DataSource ZGATPUPLOAD in source system TA6CLNT010
Field PROD_ALLOC_OBJEC will not be delivered from DataSource ZGATPUPLOAD in source system TA6CLNT010
Field SALESORG will not be delivered from DataSource ZGATPUPLOAD in source system TA6CLNT010
Field SALES_DIST will not be delivered from DataSource ZGATPUPLOAD in source system TA6CLNT010
Field SIMID will not be delivered from DataSource ZGATPUPLOAD in source system TA6CLNT010
Field USER_MOD_QTY will not be delivered from DataSource ZGATPUPLOAD in source system TA6CLNT010
Start of the after-import method RS_ISTS_AFTER_IMPORT for object type(s) ISTS (Activation Mode)
Reference to transfer structure ZGATPUPLOAD_CA not available. No activation possible.
Please give me suggestions....

Are you still looking ans on it?

Error while extracting data from Generic datasource

Hello Gurus,
I have encountered an error "Errors in source system" with status red while extracting data from generic datasource into DSO.
I have done below things:-
1. Checked the jobs in source system, the job is successfully completed
2. The generic datasource is active and supporting delta with calender day in source system.
3. No TRfc error and no idocs stucked.
4. No short dumps in source system.
5. The delta queue(RSA7) is showing 0 with status as green.
6. Replicated the datasource On BW side and also activated the transfer rules by RS_TRANSU_ACTIVATE_ALL
The problem has not yet solved. Could you guys please suggest me what might be the reason for this error......
Thanks,
Sonu

Hello,
I have used the generic delta using calender day.
Safety upper limit : - 1
Safety lowerr limit : - 0
I have made the entries in va01 transaction, but the delta queus is not getting updated which should show 1.
Do Generic extraction require any job to transfer data from Database table to delta queue.
We are not able to get the delta records on BW side. Please suggest.
Please suggest.
Thanks,
Sonu

Generic Datasource--plz confirm

Similar Messages

Maybe you are looking for