About Generic Delta!
I create a Z-table and use RSO2 to create a datasource,and create the general delta by using the calendar day.but when I use the Delta function twice,the error message is like this "Error occurred in the data selection " "The data in the delta queue for DataSource ZZZZTA are inconsistent. The structure that was used to put the data in the queue, can no longer be
reconstructed."
Anybody has confront this problem?
by the way,I found that the initial and delta will be duplicate,my data is this:
bukrs belnr bldat
1000 1000000001 2005.07.25
1000 1000000002 2005.07.26
1000 1000000003 2005.07.27
1000 1000000004 2005.07.28
1000 1000000005 2005.07.28
the initial on 2005.07.27,result is:
1000 1000000001 2005.07.25
1000 1000000002 2005.07.26
1000 1000000003 2005.07.27
then delta data is:
1000 1000000003 2005.07.27
so the initial and delta duplicated,right?
Very helpful answer.
But can you explain the difference among:
Time Stamp,Calendar day,Numerical Pointer
If I use Time Stamp,while Use BLDAT as field name above the radio button,can I do the Test the same day?You mean that there will be no data,but in my test,it's a ERROR,the error message is the one listed above.please look into it and doing some analysis.
Message was edited by: Chunhui Zhu
Message was edited by: Chunhui Zhu
Similar Messages
-
Doubt about generic delta using function module.
Hi,
I have the following scenario.
I have to create a generic data source having delta using funcation module.
The full load works fine, but the delta load not.
I don't know, if always the field that was specified as a delta, must be part of the cursor in this case AFRU~LAEDA
This is my cursor:
OPEN CURSOR WITH HOLD S_CURSOR FOR
SELECT AFIHAUFNR AFIHADDAT AFIHIPHAS AFIHILART AFIH~AKKNZ
AFIHPLKNZ AFIHILOAN AFIHIWERK AS ZPLANPLANT AFIHEQUNR
ILOA~TPLNR
AFKOGSTRP AFKOGLTRP AFKOGSTRS AFKOGLTRS AFKOGSTRI AFKOGETRI AFKO~FTRMI
AUFKAEDAT AUFKERDAT AUFKWERKS AUFKKOSTL AUFKKOKRS AUFKSOWRK AUFK~OBJNR
AUFKAUART AUFKVAPLZ
CRHD~ARBPL
TKA01~WAERS AS ZCOSTP_ML_UM
FROM AFIH
INNER JOIN AFKO ON AFIHAUFNR = AFKOAUFNR
LEFT OUTER JOIN ILOA ON ILOAILOAN = AFIHILOAN
INNER JOIN AUFK ON AFIHAUFNR = AUFKAUFNR
INNER JOIN TKA01 ON AUFKKOKRS = TKA01KOKRS
LEFT OUTER JOIN CRHD ON CRHDOBJID = AFIHGEWRK
WHERE AFIH~AUFNR in L_R_AUFNR
AND AFIH~EQUNR in L_R_EQUNR
GROUP BY AFIHAUFNR AFIHADDAT AFIHIPHAS AFIHILART AFIHAKKNZ AFIHPLKNZ AFIH~ILOAN
AFIHIWERK AFIHEQUNR
ILOA~TPLNR
AFKOGSTRP AFKOGLTRP AFKOGSTRS AFKOGLTRS AFKOGSTRI AFKOGETRI AFKO~FTRMI
AUFKAEDAT AUFKERDAT AUFKWERKS AUFKKOSTL AUFKKOKRS AUFKSOWRK
AUFKOBJNR AUFKAUART AUFK~VAPLZ
CRHD~ARBPL
TKA01~WAERS.
For each aufnr I must go to the afru table and totalize the real work (IWNW) and real duration (IDAUR) when AFRUSTZHL > 0 and totalize too when AFRUSTZHL = 0 but with sign to negative.
This is my external query, i need that the field AFRU~LAEDA must be taken as delta field:
SELECT AFRUERSDA AFRULAEDA AFRUSTZHL SUM( AFRUISMNW ) AS ZTRA_REAL AFRUISMNE AS ISMNE SUM( AFRUIDAUR ) AS ZDURAC_REAL AFRU~IDAUE AS IDAUE
INTO CORRESPONDING FIELDS OF TABLE WT_AFRU_OM
FROM AFRU
WHERE AUFNR = WT_ZCUROM-AUFNR
AND AFRU~STZHL = 0
GROUP BY AFRUERSDA AFRULAEDA AFRUSTZHL AFRUAUFNR AFRUISMNE AFRUIDAUE AFRUISMNW AFRUIDAUR
order by AFRUERSDA AFRULAEDA AFRUSTZHL AFRUIDAUE AFRU~ISMNE.
IF sy-subrc = 0.
CLEAR WT_AFRU_OM2.
REFRESH WT_AFRU_OM2.
SELECT AFRUERSDA AFRULAEDA AFRUSTZHL SUM( AFRUISMNW ) AS ZTRA_REAL AFRUISMNE AS ISMNE SUM( AFRUIDAUR ) AS ZDURAC_REAL AFRU~IDAUE AS IDAUE
INTO CORRESPONDING FIELDS OF TABLE WT_AFRU_OM2
FROM AFRU
WHERE AUFNR = WT_ZCUROM-AUFNR
AND AFRU~STZHL > 0
GROUP BY AFRUERSDA AFRULAEDA AFRUSTZHL AFRUAUFNR AFRUISMNE AFRUIDAUE AFRUISMNW AFRUIDAUR
order by AFRUERSDA AFRULAEDA AFRUSTZHL AFRUIDAUE AFRU~ISMNE.
IF sy-subrc = 0.
LOOP AT WT_AFRU_OM2.
WT_AFRU_OM2-ZTRA_REAL = WT_AFRU_OM2-ZTRA_REAL * -1.
WT_AFRU_OM2-ZDURAC_REAL = WT_AFRU_OM2-ZDURAC_REAL * -1.
APPEND WT_AFRU_OM2 TO WT_AFRU_OM.
ENDLOOP.
ENDIF.
LOOP AT WT_AFRU_OM.
"fjro incluir el clear y el move
CLEAR WT_DATOS_OM.
MOVE-CORRESPONDING W_DATOS_BASE to WT_DATOS_OM.
MOVE-CORRESPONDING WT_AFRU_OM TO WT_DATOS_OM.
APPEND WT_DATOS_OM.
APPEND WT_DATOS_OM TO WT_ESTFIN_OM.
ENDLOOP.
ENDIF.
It's possible set the delta field in a external query of the cursor.
Best Regards
Ramon Sanchez
Edited by: RAMON SANCHEZ on Aug 20, 2010 2:46 PMHi Sri,
here some coding, I hope this helps!
first, get the delta-field
LOOP AT s_s_if-t_select INTO l_s_select.
CASE l_s_select-fieldnm.
WHEN 'ZDATE'.
MOVE-CORRESPONDING l_s_select TO r_date.
IF r_date-high IS INITIAL OR r_date-high = space.
r_date-high = '9991231'.
ENDIF.
APPEND r_date.
ENDCASE.
ENDLOOP.
Cursor öffnen
OPEN CURSOR WITH HOLD s_cursor FOR
SELECT * FROM
WHERE ....
AND erdat in r_date
AND aedat IN r_date.
FETCH NEXT CURSOR s_cursor INTO CORRESPONDING FIELDS OF table e_t_data package size s_s_if-maxsize.
regards
Siggi
PS: Note that this coding only works for a very straight forward extraction.
Message was edited by: Siegfried Szameitat -
How to deal with delete record in generic delta of generic datasource
Hi,
Anyone can give me suggestion about the delete record in generic delta of generic data. I need extract data with a generic datasource and hope deleted record in datasource also can be "delete" in next delta extraction. I do a test with generic delta. It seem that the delete record can not be updated in ODS. but updated record can be updated in next delta extraction.
How dose BW generic delta deal with the deleted record with generic delta mechanisim? Or how can I use generic delta mechanisim to realize that BW "delete" the deleted record of source system in ODS with delta extraction?
Thanks in advance!
BillyDelete is not supported in delta mechanism of generic delta extractor. You will need to add a workaround for that.
- Capture the deleted records somewhere (maybe enhance the txn deleting the record so the key is written to a Z table). Take these records to BW and manipulate the recordmode to affect deletion of corresponding record from ODS.
- If your generic delta is based on FM, and if the 'delete' is captured in change document tables, add the logic to check change document tables whether any records are deleted, and if yes, send those to BW with appropriate recordmode to achieve deletion. -
Hi experts
i have problem in loading generic delta , Generic delta have three parameters
1.Time Stamp
2.Numeric pointer
3.Calender day
and also upperlimit and lower limit
can any one explain me about this parameters and how it works in generic delta
Thanks in in advancehi,
Yes we have these 3 delta types.
timestamp is used when the requiement of data load is depends on time ie hourly based.
0calday is is used when the requiement of data load is depends on date ie daily based.
Numeric pointer is uesed if u want to load delta based on some fields like sales order,material order.
Lower limit and upper limit used for not to miss the records.
regards,
kundan -
hello guys
I have some doubts when it comes Generic Extraction of Master Data from a source system(say SAP R3) with possible deltas...
1.I heard from my friend,that while working with Master Data Generic Extraction (involving deltas),we generally do FULL LOADS....itsnot a common practise to do initialisation and then delta update as in the case of Transaction Data...Is that true?
I know that it varies from case to case,but generally speaking,how often do we do these FULL LOADS?
2.Suppose,if I say,I will go the unusual way and choose to do Master Data Deltas exactly like we do with Transaction Data deltas(first initialisation with data transfer then delta updates now and then)....how do we choose if its time stamp or numeric pointer incase of Master Data fields....
suppose,I want to set characteristic 'Location' as delta-field,what do I choose out of numeric pointer,calendar day and time stamp?and why should I choose it?
how about incase of Characteristic 'Customer Phone number'?
Thanks fr ur time
SHi ,
In generic delta you can choose only one field as delta option ie whatever changes happens for a record thar field shold get updated only then you will get delta for those records.
Choosing numeric pointer for text fields like location wont help for you. May be phone number you can try as numeric pointer if it is purely a number series which uses new numbers always.
If you are choosing these fields whenever there in chamge in this fields you will get delta. No other change in the same record will be captured
Thanks,
Arun -
Hi Gurus,
Good Day to all. I just like to inquire some details for creating generic datasource with delta enabled. I have created a view table with fields from EKBE table, and created generic datasource that reads the view table I have created from EKBE, now it needs delta process with CPUDT as delta specific field name, seeing the data type of CPUDT, it is DATS with 8 length.
I would like to assure if what will be use as marker of delta, timestamp utc, timestamp local, calendar day and numeric pointer?
And if I use one of the above, what settings that needs to be use for the safety interval upper and lower limit?
Thank you for your inputs and really appreciate it.Hi,
use the CALDAY as a generic delta pointer.
i would like to recommend as: Safety Interval for Upper Limit as 1 and Safety Interval for lower Limit as ZERO
i think your are using the DSO as a staging layer no worry about duplicates.
Thanks,
Phani. -
Dear Expert
I have a z Table consisting fields like company code , change date, etc.
I have created a generic delta using change date as delta field.
A program loads data to this table.
Lets say I loaded all data for company code 1000 and there are other company code data I also need to load but have not done so.
I replicate the datasource to BI 7.
I have read guides on Generic delta and need clarification on its mechanism in more detail.
========
1. Do we need to Initialize Delta for Generic Delta?
2. If my infopackage used for the init is change date of yesterday, what happens when some days later, I load company code data 2000 into the z table and these data has change dates earlier than the init date?
3. Does init work like this : lets say the data selection in the infopackage used for the init is :
company code = 1000
change date = yesterday.
the 1st delta infopackage will be based on the change date of yesterday and the upper and lower limit?
4. What if I subsequently load other company code data into the z table? How can these be loaded as delta by the existing delta? Or must there be another init? can this be done?
5. Technically, if delta is loaded today, and 2 days later, I insert manually into z table a record having the same change date as the 1st delta change date. How does the delta mechanism know about this? I seek clarification that this record will not be known by the delta and will not be picked up and loaded by the next delta infopackage because the change date is incremental and will never pick up and old change date and delta is based on change date selection.
Hope you can enlighten me on the above doubts .
Best regards
PascalHi Pascal,
1. Do we need to Initialize Delta for Generic Delta?
Yes, you need to do init to capture the delta records.for this while designing you have to select Delta check box in data source maintenance screen.
2. If my infopackage used for the init is change date of yesterday, what happens when some days later, I load company code data 2000 into the z table and these data has change dates earlier than the init date?
The change date will be populated in Z table based on system, when you change any record today you won't get yesterday date.anyways in your question as change date is less than last delta run date it won't pick that records.
3. Does init work like this : lets say the data selection in the infopackage used for the init is :
company code = 1000
change date = yesterday.
the 1st delta infopackage will be based on the change date of yesterday and the upper and lower limit?
The best practice is run the init with out any selections, unless when you have requirement that you need to create multiple init's on same data source.
no need to give date selections in info package(already your delta is working on change date).If you need data for a particular company code, give company code other even do not give company code as selection.It will pick all the new or changed data from last delta run.
4. What if I subsequently load other company code data into the z table? How can these be loaded as delta by the existing delta? Or must there be another init? can this be done?
Do not give company code as selection in your delta info package.same delta IP will pick the data for all company codes.
5. Technically, if delta is loaded today, and 2 days later, I insert manually into z table a record having the same change date as the 1st delta change date. How does the delta mechanism know about this? I seek clarification that this record will not be known by the delta and will not be picked up and loaded by the next delta infopackage because the change date is incremental and will never pick up and old change date and delta is based on change date selection.
As i already told we cannot give change date manually, when you save a record this will be populated by system in the table.
Delta settings for generic data source will be maintained in table ROOSGENDLM (here we will have last delta run time stamp on this data source).When you run delta next time, it will pick the data which was stored after delta time stamp.
Regards,
Venkatesh. -
What are the disadvantages of generic delta extraction
Hi all,
what are the disadvantages of generic delta extraction.
how function module generic extraction works.
Thanks,
Madhu.hi madhu,
Pls refer ths,To learn more about Generic Extraction pls read BW350 book.
Gereric Extraction can be done in 3 ways.
If you go to transaction RSO2 in R/3 side, provide tech name for data source and click create.
you will get the 3 options.
1)From a DB Table
2)From a DB View
3)From Functional module/ Infoset Query
in first option you can directly give a standard or custom build talbe name. in second option you can select the necessary fields from more than one talbe(eiter standard or custom). In third option you will create a function module or Query to extract data. When creating function modules you can use standard function modules as a template e.g. RSAX_BIW_GET_DATA_SIMPLE.
see weblog : /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
If you want to enable delta for generic extractor you choose the option delta and provide necessary settings.
Generic extraction is when your extraction is not satisfied by either BC or LIS/LO. It can be using a view / query/table/FM
Here the changed records can be isentified by :
1. Based on the date of creation or last change ( Delta based on 0Calday)
2. Based on the record number ( Numeric Pointer )
3. Based on time of change ( Timestamp)
real time examples would be
1. Master Record creation like customer ID creation
2. Timesheets in SAP PS
3. Invoive details / Sales Order Details.
Pls check this web logs for clear Idea.
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
Have a look at these threads too.
Tables
Transfer Structure
The steps for creating extractor using Function Module.
1. Create new Function group (if you have already not done so) in Se80
2. Copy Function module "RSAX_BIW_GET_DATA_SIMPLE" with suitable name.
3. Change the code that populate data.
Following table may give you the guideline for parameters.
Parameter Description
I_REQUNR (import) BW provides this request identifier. It is a system-generated identifier in the form REQU_XXXXXX. BW uses this same identifier in all function module calls that relate to a single load.
I_DSOURCE (import) The name of the generic extractor
I_MAXSIZE (import) The maximum number of records that BW expects to be in each data packet
I_INITFLAG (import) A Boolean flag that indicates if this is the initialization (first) call to the function module
I_READ_ONLY (import) A test flag not needed in most extraction scenarios
I_T_SELECT (table) This table holds any selections from the BW InfoPackage. The function module should examine these selections and only return data that matches the selections.
I_T_FIELD (table) This table holds the fields that BW requests
E_T_DATA (table) The function module fills this table with data records. These records then return to BW as data packets. This table has the same structure as the extract structure defined in the generic DataSource.
NO_MORE_DATA (exception) The function module raises this exception when no more data is available
ERROR_PASSED_TO_MESS_HANDLER (exception) The function module raises this exception if an error occurred during the extraction. It alerts BW to check for error logs.
Change following code to put the selection fields
Select ranges
RANGES: L_R_CARRID FOR SFLIGHT-CARRID,
L_R_CONNID FOR SFLIGHT-CONNID.
Change following to populate data
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.
Some more links:
Re: functionmodule
Re: FM for G. extractor
with hopes
Raja Singh -
Regd Safety Interval Lower Limit for Generic Delta
Hi All,
Safety Interval Upper Limit =1 for a Generic Delta would get Delta based on yesterday's BW data.
What would Safety Interval Lower Limit would do for a Generic Delta .
Your inputs please
SreeHi,
just a short example:
you run a init today --> 20070525 (internal date format).
for the next delta tomorrow the system takes the last extraction date - 1 day so 20070524 for data selection and will store 20070526 as last extraction date and so on.
This is to make sure that you will get all additional records extracted which were changed or created on each extraction date, but after last extraction. OK, you will get some records twice, but therefore you normally post the data to a ods via overwrite mode and this will take care about the 'real' delta while doing the further posting to the cube.
Hope this helps
kind regards
Siggi -
Safety Intervals for Generic Delta
Hello Gurus,
I want to know about safety upper limit and lower limit for generic delta.
I have gone through the previous threads related to this topic and i am not able to understand completely.
can anybody explains me this in detail with example in terms with Calday, Timestamp & Numeric pointer.
Thanks in advance.There is very good example was exist on wiki.
please search and help yourself.
Use Google search by using search term " wiki generic delta".
You will get what you need. -
Hi All,
I have a requirement to develop generic DELTA extractors. have extensively created generic ectractors using function module RSAX_BIW_GET_DATA_SIMPLE.
Can you please let me know how to create generic delta extractors with Steps.
Also How the tabel ROOSGENDLM us used in generic extractors..
Point will be assigned to useful answers..
Regards,
BillHi Bill,
check this out: Generic Extraction via Function Module
You do not have to take care about that table, the service api will do that for your, you only need to take care about the information (delta date, timestamp or pointer) passed to the fm by the api and design your coding related to that information.
regards
Siggi -
Hi,
Has anyone used the function module to create a generic delta queue to work for extracting data from tables CDHDR and CDPOS when using the UDATE as the change date? I was able to find an alternate solution to extracting the data from these tables, but the solution is not approved, and it is suggested to use the function module and use a changed date to create the generic delta queue from RSO2.
Please advise.
Thank youHi Siggi,
Thank you for your insight on this. Well, UDATE is the changed date in the table CDHDR, and I am wondering if that should be used to provide to the RSO2 setup and set the interval to 1 day. I am extracting this UDATE to my extract structure.
Here is what I have in the FM and I am loading right now. I provided the date range to the 'Data Selection' tab for a complete year, which should only be 100K records but it is now extracting up to 17M records and still going. I am not sure if I should stop the load because it seems that it is loading the complete table CDHDR which is 80M.
Here is my code form my FM:
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 = 'UDATE'.
MOVE-CORRESPONDING L_S_SELECT TO L_R_UDATE.
APPEND L_R_UDATE.
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.
OPEN CURSOR WITH HOLD S_CURSOR FOR
SELECT (S_S_IF-T_FIELDS) FROM CDHDR
WHERE UDATE IN L_R_UDATE
AND OBJECTCLAS ='ORDERBUCH'.
SELECT OBJECTID CHANGENR USERNAME UDATE UTIME OBJECTCLAS TCODE
FROM CDHDR
WHERE UDATE IN L_R_UDATE
AND OBJECTCLAS ='ORDERBUCH'.
I have the other SELECT commented out because I was getting an error dump on the R3 side saying "One of the field names in the SELECT clause was not recognized.", referring to statement "OPEN CURSOR WITH HOLD S_CURSOR FOR", so I am using the other SELECT that is not commented out.
I think I am following what you are referring to about the SELECT but not quite completely. What would you suggest to rewrite for the UDATE issue to process both the Full and Delta data?
Thank you -
In Generic Delta By selecting 0CALDAY?
hello all
In generic delta,if v select <b>0calday</b> as a delta type,after selecting this delta type v need to select a field for this delta type,should v need to select <b>Time field</b> only(like Creation date,Last date of creation or something like) or <b>other than Time field</b> like select Matnr,Ername or something like this?
Pl let me know that?
regards
baljiMy pleasure!!
The following document should be very helpful for you.. i lik this paper very much..
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
hope it helps..
regards,
Hari -
Generic delta with function module
Hi Gurus,
Is it possible to create a generic DataSource with delta support using function module following the queue delta mechanism (u can get some function moduel in MCEX function group, and check the outbound delta queue before and after update in transaction smq1.
I can store the delta data using qRFC and collective update mechanism. but I don't know how to create a generic data with delta and how to attach a rfc destination (& logical system) to the data source. The Source system information is stored in the table "ROOSGEN". Is there any configuration setting required to do the same.
Regards,
JugalJugal,
What I understand you to be asking is if it is possible to create a generic delta extractor which uses the delta queue. If this indeed is your question the answer is yes.
First you need to create your data source so it is visible via tx RSA5 and need to make sure that the delta type (ie ABR, AIM)is set appropriately for the datasource.
The issue however is determining from where you will associate your delta hook (when will you write to the queue)? I have in the past utilized BTE's, Business Transaction Events to write information out to the delta queue, you can see a list of available BTE's in your system via tx FINF.
Once you find a place to write your deltas from you call the below FM with the appropriate datasource.
RSC1_TRFC_QUEUE_WRITE.
Once you have done this the standard BW extractor for deltas will pull the information from the delta queue. But from what I understand you just want to know how to associate the data with the delta and that is the FM listed above.
Hope this helps,
Cheers,
Scott
> Hi Gurus,
>
> Is it possible to create a generic DataSource with
> delta support using function module following the
> queue delta mechanism (u can get some function moduel
> in MCEX function group, and check the outbound delta
> queue before and after update in transaction smq1.
> I can store the delta data using qRFC and collective
> update mechanism. but I don't know how to create a
> generic data with delta and how to attach a rfc
> destination (& logical system) to the data source.
> The Source system information is stored in the table
> "ROOSGEN". Is there any configuration setting
> required to do the same.
>
> Regards,
> Jugal -
Problem in getting Generic Delta records to BW
Hi BW Gurus,
I have got one issues with which I have been struggling a lot for several days . i.e
I am extracting data from R/3 using Generic Extractor (View) from CATSCO and CATSDB. At the time of delta, I tried using Personal No with Time Stamp giving Upper limit as 1800 seconds. I executed Infopackage in BW immediately. But it didn't work out. So plz guide me how I can get Delta Records to BW. Or should I do any necessary factors apart from these in Generic Delta Screen (RSO2).
It is very urgent.
I will be thankful for solving this issue.Hey I am "Intros" again,,
I am sorry man for giving the wrong T-code mistakenly in my last reply..
To solve the proble...the whole process is same what I told u before..
But... you got to go to T-Code : BD87 , then execute the IDocs manually to bring them in to BW
identify your IDocs which are missing in Monitor screen, then goto BD87 and select those IDocs and click execute... )you can search the IDoc's based on selection conditions)
I hope this will help u...
cheers man..
---Intros
Maybe you are looking for
-
May i know how to set the image .jpg or gif into the label ? how to get the time in this format::Monday 12th Jan 2004 thanks
-
Multi insert on table with checkbox list
Hi all, I've a problem perhaps it's a small one but I need to do an insert on a table with with the use of a checkbox, however the checkbox retrieves multiple values. Which I've tried to insert with a loop in the pl/sql block. How exactly can I do th
-
Create Service Contract using BAPI_SLSTRANSACT_CREATEMULTI
Hi, In my requirement, I have to create a Service Contract from flat file by using BAPI - BAPI_SLSTRANSACT_CREATEMULTI and data which are comming from flat files are, <b>Serial number, Sold-to party, Ship-to party, Installation date, Contract start d
-
Missing javai.dll with jdk1.3, 4.5.1, sp13
Now that Java 2 JDK1.3.0 with hotspot is supported for 4.5.1 (http://www.weblogic.com/platforms/index.html#winnt), I thought I would give it a try. I am using Weblogic 4.5.1 with SP13, and NT 4.0. When I start the server I get the following dialog bo
-
Photoshop & Lightroom matching
1)When I view the same raw file with both Lightroom 2 & Photoshop CS3 the PS version is darker with a slight colour shift. All metadata synchronised & ACR 4.5 2) When I export a photo (from LR)as TIFF (with profile) this same photo viewed on both PS