Modifying Cube/ODS data for few entries

Hi friends,
Is there any way to modify few record entries of couple of chars. in either
cube/ODS without actually distrubing the settings.
regards.

Hi Nasiroddin,
    Create a generic datasource based on ODS Active table. Create update rules from this ODS into this ODS only(Loop back).
    Pull data till PSA and edit manually(if records are less) or write some routines to change data accordingly and load except key figures(or map only required fields in overwrite mode).
    Push delta from this ODS to subsequent target, data will be corrected automatically.
Hope it Helps
Srini

Similar Messages

Extract Cube data for all entries of an internal table

Hi
I want to fetch the data from the cube for all entries of another internal table.
Scenario : Fetching the COMPANY_CODE and DATE into an internal table and for those company codes and Dates, I have to fetch the records of the Cube.,
I am using the Function Module : RSDRI_INFOPROV_READ
But not sure how to accommodate the multiple selections condition for this.
Selection Required:
                                *For all entries of it_cc
                                  where comp_code = it_cc-comp_code and
                                              date = it_cc-date.*
Please help me how to such multiple conditions and "for all entries" functionality for fetching the data from the cube.
Thanks.
Veera Karthik G

HI
You can try like this
LOOP AT lt_donotcall_old .
<ls_donotcall>-examination_date = sy-date.
<ls_donotcall>-examination_time = sy-time.
ENDLOOP.
append it_donotcall_old.
Reward all helpfull answers
Regards
Pavan

AP Aging report - key date for user entry

Hi All,
We have a requirement to calculate aging buckets like 0-30,31-60,61-90...etc.
I know the key date for this report is created on net due date in SAP standard report.
In standard SAP report , key date is always a system date(SY-DATUM).
What we need for this report is , we need to get all the invoices which are outstanding as of that date(the date which user enters).
If user enters today's date(08/28/07) , he should get all the invoices outstanding till that date in aging buckets and if user enters some date in the past like 07/26/07, he should get all the invoices outstanding as of that date.
Can someone Pls tell me if aging buckets are calculated based on a user entry ?
Regards,
Kumar

Hi Voodi,
Aging in the standard report is being calculated like below...
1.For open items
Posting date<key date
Item status = O
2.Posting date < keydate and clearing date > key date and net due date with offsets on keydate ( key date + 1 - keydate+30 --- for 1-30 days) like wise for all aging buckets.
in this scenarion , key date is always system date ie today's date.
But user wants to get all the invoices based on his user entry...
is this possible with the same standard key date variable or do we need implement any other logic???
Regards,
Kumar

Read data : for all entries

wht happens if v read data using FOR ALL ENTRIES in select statement

Hi Ankur,
You can only use FOR ALL ENTRIES IN ...WHERE ...in a SELECT statement.
SELECT ... FOR ALL ENTRIES IN itab WHERE cond returns the union of the solution sets of all SELECT statements that would result if you wrote a separate statement for each line of the internal table replacing the symbol itab-f with the corresponding value of component f in the WHERE condition.Duplicates are discarded from the result set. If the internal table itab does not contain any entries, the system treats the statement as though there were no WHERE cond condition, and selects all records (in the current client).
For Example:
SELECT *
FROM SCARR
INTO TABLE t_scarr.
LOOP AT t_SCARR INTO wa_scarr.
SELECT SINGLE *
    FROM sflight
    INTO wa_sflight
   WHERE carrid EQ wa_scarr-carrid.
APPEND wa_sflight TO t_sflight.
ENDLOOP.
Instead of the Above use below code:
SELECT *
FROM SCARR
INTO TABLE t_scarr.
SELECT *
FROM SFLIGHT
INTO TABLE t_sflight
   FOR ALL ENTRIES IN scARR
WHERE carrid EQ t_scarr.
this condition, return all entries of the sflight
Refer the Below Links for more Info:
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3a1f358411d1829f0000e829fbfe/content.htm
Regards,
Sunil

Migrate data for few infotypes

hello Experts,
I have a requirement. I am joining a client and client wants to transfer data for infotypes 0000, 0001,0002 and 1000 and 1001. I want to knw how do i go about it.correct and also please specify if i m technically wrong.
1. create a distrubution model with idoc hrmd_a. I want to knw where can i specify what infotypes i want to distribute.
2. create an ale connection between both the systems using SALE.
now do i need to activate the change pointers?
and how does the program run, i mean when wud be the idoc created and how will it be transferred to other system?
I knw my request is bit vague but any kind of help would be really appreciated>
thanks,
HM

Hi,
at following link there is a step by step guide for Idoc distribution HR.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEHR/CABFAALEHR_ALE_QS.pdf
There are also a few other useful pdfs for ALE/IDoc at:
http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
In the distribution model you have to create filters. There you could specify which infotype you want to distribute.
Call report RHALEINI to create initial Idocs.
Regards
Bernd

APD Process for Cube - ODS data transfer.

hi,
Two data sources (cube and ODS) are feeding another ODS. I want to delete the data in Data target (ODS)belongs to that particular infosource for every data load if it comes from the same infosource without using process chain or events. (I want the similar option found in cube). I also want to write some complex functionality (ABAP CODE) in start routine of update rules.
Bhanu suggested me to use APD Process. Can any one (including BHANU) explain me in detail about APD Process. Please also give me navigations.
Regards,
Avneet

Hi Avneet,
You can read details about the APD here:
http://help.sap.com/saphelp_nw04/helpdata/en/49/7e960481916448b20134d471d36a6b/content.htm
Basically you can get to the APD from transaction RSANWB. Start creating a new process using a query as the source of data. You can provide a transactional ODS as a data target and you also have the opportunity of changing the data using predefined functions, or also ABAP code before loading into the ODS.
Hope this helps...

Custom Date for Birthdate entry

I got issued a project that requires me to take a pre-exsisting professional Scholarship form and make it into a PDF. I've been able to make the form fields with no problem but I'm running into a few issues with the Date format. This form requires the Applicant to type out their Birthdate and Social Security #, however, the higher ups don't like the default method Acrobat uses.
Problem #1: Because some of our Applicants are Elderly and/or are not very computer literate, I want there to be "some" flexibility to them typing out their birthdate. IE, MDDYY, MMDDYY, MDDYYYY, MMDDYYYY will Validate through a script that turns it into the company standard format of MM/DD/YYYY. I have a very basic bit of Custom Keystroke script that I found and edited slightly. Its not pretty though.
var a = event.value;
if(a.length==5){var b = util.scand("mddyy",a);event.value = util.printd("mm/dd/yyyy",b)}
if(a.length==6){var b = util.scand("mmddyy",a);event.value = util.printd("mm/dd/yyyy",b)}
if(a.length==7){var b = util.scand("mddyyyy",a);event.value = util.printd("mm/dd/yyyy",b)}
if(a.length==8){var b = util.scand("mmddyyyy",a);event.value = util.printd("mm/dd/yyyy",b)};
This does what I want it to do, sort of, but deviating outside of this script results in undesired results. IE typing 02/13/71 will get 02/13/71 not 02/13/1971. Then there's a potential problem of the century. Typing 021327 will get 02/13/2027 not 1927.
Can anyone lead me in the right direction of where to close the flexibilty off at giving an Audio Alert when any other keystroke besides 0-9 and / is entered while maintaning the Validity of the above format of MM/DD/YYYY?
(I realize this is pretty much nitpicking, but the higher ups say jump and I have to say How High and I'm not at the skill level yet to achieve the desired results.)
Problem #2: In the same form, the Applicants SSN needs to be entered but the default format under Properties > Format > Special is requiring the full 9 digits. However, we have more than a few people who have "less" than 9 digits. Given that the higher ups want to give some flexibilty to Elderly and non-computer literate on the SSN field as well, I've been asked to correct this problem. Now, I've been steered in the direction of Leading Zeros script and AutoTab features, but to be honest, most of this is beyond my understanding in how to achive it. I understand the concept of leading 0's in the util.printd feature of the 999-99-9999 format, however, any attempt to do this stuff leads in undesired results. Please help if you can.
Thanks in Advance,
Dean

Thank you for replying Gkaiseril, not really sure what you're talking about with RegExp, hidden Fields and the like. As I stated above, my skills with acrobat are limited and my knowledge of Java script is less than that. Could you give examples or write out examples of what you're talking about? I plan to learn more on Java, scripting and getting better at Acrobat, but for the mean time, I just need the scripting of how to get the Date field to do what I want it to do.
As for the SSN, I'm aware of the 9 digit limit, this is why I'm wanting the script to fill in less-than-9-digit SSN's with leading Zeros. We have had examples of the past of our clients and applicants with Exm 001-34-5678 not entering their 0's first and it confuses them as why their paperwork was'nt accepted or returned invalid. Plus, our OCR system doesn't like the SSN field if its entered incorrectly. This is why I was directed to look at leading 0's and something about a decimal point ...
I haven't looked into the util.printd yet, in fact I know absolutely nothing about it except from what you told me. No idea where to look for the things I want to accomplish.

How to lock the data for few periods in the Input Layout

Dear All,
I have an input enabled layout wherein I will display the data based on a period range.( For ex, 01.2007 to 12.2007).
Now, based on the current period I should disable the input readiness for the periods less than my current period.
In my ex, if my current period is 06.2007, the input readiness should be disabled for the periods 01.2007 to 05.2007 .
How can I achive this?
Regards,
Srini.

Hi Srinivas.
You can use user variable exit for the disabled one (the period one); based on the current period..
You can read regarding it in here:
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
Hopefully it can help you a lot.
Regards,
Niel
thanks for the points you choose to assign.

Highlight the column in the ALV grid only for few entries!

Hi all,
I am using the FM "REUSE_ALV_GRID_DISPLAY" to dsplay the o/p of my report in ALV grid.
Now i need to highlight 1 particluar column for only some entries(row) based on the value of the column which is to be highlighted.
Can anyone tell me the steps to do so??

Please make search thru this form you can find lot of threads
For example
https://forums.sdn.sap.com/search.jspa?threadID=&q=alvANDcellANDcolor+&objID=f50&dateRange=all&numResults=15
a®

Modify Classification data for IL02

Hi,
I want to modify the classification data for Functional location.
Is there any function modules available to change. I know the functional module for Material classification, but Functional location its not working.
SO pls tell me the function modules or any other method is available.
I was unable to do to in BDC.
regards
Rajesh V

Hi,
CALL FUNCTION 'BAPI_OBJCL_CHANGE'
EXPORTING
    objectkeynew    = lv_funcloc
    objecttablenew = 'IFLOT'
    classnumnew     = lv_class
    classtypenew    = '010'
TABLES
    allocvaluesnum = li_numc
    allocvalueschar = li_char
    allocvaluescurr = li_curr
    return              = li_return.
if not li_return[] is initial.
read table li_return into lwa_return with key TYPE = 'E'.
if sy-subrc ne 0.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
endif.
endif.
Fill the new characteristic values into table parameters li_numc, li_char, li_curr depending on the data type (field ATFOR) of the characteristic value.
Inside the FM it uses BAPI_OBJCL_GETDETAIL to get the old characteristic values and make comparision with table parameters li_numc, li_char, li_curr and updates the characteristic data for the functional location and class.
Regards,
Dwaraka.S
Edited by: Dwarakanath Sankarayogi on Jan 29, 2009 10:49 AM

Any tool to upload data to Fast entry (pa42) infotype

Hi all,
is there any tool like LSMW to upload data for Fast entry actions infotype?
Regards,

Hi dear Kavitha,
U can use S-CAT and BDC for that.
BDC u can record at transaction code SHDB.
Make a template for the same and uplaod.
(ABAPer Help is required fopr BDC though its a small task if u understand the same)

Missing Data Target in Infopackage for Update ODS Data in Data Target Cube

Hello & Best Wishes for the New Year to all of you,
I have 3 ODS (1 on Full Update and 2 with Delta Updates). All these 3 ODS update data to a single CUBE. In my development system this works correctly. Data load from PSA to ODS to Cube.
Now I transported this to my QA and Production System. In QA and Production System, I am able to load data upto all the 3 ODS and ACTIVATE Data in all these 3 ODS.
When I am trying for "Update ODS Data in Data Target" to load data from ODS to Cube in QA /PD, the system created Infopackage (ODS to CUBE), doesnot get the Data Target details. (Initial Upload / Full Upload). The Data Target Tab is Blank (expected Cube details).
I have tried to transport again after deleting the update rules.
Can you suggest what could be the problem ?
regards - Rajesh Sarin

Thanks Dinesh,
I have the ODS to CUBE Update Rules ACTIVE in the QA and PD system. Still the problem exists only in QA and PD. In DV the ODS to CUBE Data Target is available in the Infopackage and loading the data correctly to Cube.
Listing all the trials I have done :
1) Originally transported with all the Collected Objects. Inspite of having Active Update Rules, Data Target Cube was missing in QA and PD.
2) After this problem, I again transported only the Update Rules through the Transport Connection, still the problem didnot get solved in QA and PD.
3) Again, I sent a transport to delete the Update Rules which deleted the ODS to CUBE update rules in (DV), QA, PD. After that I sent another request to CREATE the ODS To CUBE UPDATE Rules in (DV), QA and PD. Still the Data Target is missing, inspite of having Active Update Rules in QA and PD.
In DV the ODS to CUBE Data Target is available and loading the data correctly to Cube, even now.
4) I have also tried "Generate Export Data Source" for the 3 ODS in QA and PD. Still it doesnot help.
Can you please suggest ?
regards - Rajesh Sarin

Not able to modify the data for infotype 0008 using FM

Hi All ,
I have got a requirement for updating the infotype 0008 data using FM : HR_MAINTAIN_MASTER_DATA.
While trying to modify the wagetypes data which is of blank ..unable to upload the amount for that partcular field ..
For this am herewith the link of o/p :
http://i55.tinypic.com/28jfw2c.jpg for this am also posting the code...
Please suggest me furthur in what way i can upload..
      SELECT * FROM pa0008 INTO TABLE itab_pa0008
FOR ALL ENTRIES IN itab
    WHERE pernr = wa_data-pernr
    AND begda = wa_data-begda_out
    AND endda = wa_data-endda_out.
    DESCRIBE TABLE itab_pa0008 LINES lin.
    IF lin EQ 0.
      c_action = 'INS'.
    ELSE.
      c_action = 'MOD'.
    ENDIF.
    LOOP AT itab INTO wa_itab WHERE pernr = wa_data-pernr.
      CLEAR: wa_bapireturn, wa_bapireturn1, wa_hr_return.
      REFRESH: it_pprop[],it_modified_keys[].
      it_pprop-infty = '0008'.
      it_pprop-fname = 'P0008-TRFAR'.                 "1
      it_pprop-fval = wa_itab-trfar.
      APPEND it_pprop.
      CLEAR it_pprop.
      it_pprop-infty = '0008'.
      it_pprop-fname = 'P0008-TRFGB'.                 "2
      it_pprop-fval = wa_itab-trfgb.
      APPEND it_pprop.
      CLEAR it_pprop.
      it_pprop-infty = '0008'.
      it_pprop-fname = 'P0008-TRFGR'.                  "3
      it_pprop-fval = wa_itab-trfgr.
      APPEND it_pprop.
      CLEAR it_pprop.
      it_pprop-infty = '0008'.
      it_pprop-fname = 'P0008-TRFST'.                  "4
      it_pprop-fval = wa_itab-trfst.
      APPEND it_pprop.
      CLEAR it_pprop.
      flag = flag + 1.
*****************************************************************************************************5
      BREAK-POINT.
      IF NOT wa_itab-lga1 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA01'.
        it_pprop-fval = wa_itab-lga1.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet1.
      ENDIF.
      IF NOT wa_itab-bet1 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET01'.
        it_pprop-fval = wa_itab-bet1.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************6
     IF NOT wa_itab-lga2 IS INITIAL.
       it_pprop-infty = '0008'.
       it_pprop-fname = 'P0008-LGA02'.
       it_pprop-fval = wa_itab-lga2.
       APPEND it_pprop.
       CLEAR it_pprop.
       bet1 = wa_itab-bet2.
     ENDIF.
      IF NOT wa_itab-bet2 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET02'.
        it_pprop-fval = wa_itab-bet2.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************7
      IF NOT wa_itab-lga3 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA03'.
        it_pprop-fval = wa_itab-lga3.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet2.
      ENDIF.
      IF NOT wa_itab-bet3 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET03'.
        it_pprop-fval = wa_itab-bet3.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************8
      IF NOT wa_itab-lga4 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA04'.
        it_pprop-fval = wa_itab-lga4.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet2.
      ENDIF.
      IF NOT wa_itab-bet4 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET04'.
        it_pprop-fval = wa_itab-bet4.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************9
      IF NOT wa_itab-lga5 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA05'.
        it_pprop-fval = wa_itab-lga5.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet2.
      ENDIF.
      IF NOT wa_itab-bet5 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET05'.
        it_pprop-fval = wa_itab-bet5.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************10
      IF NOT wa_itab-lga6 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA06'.
        it_pprop-fval = wa_itab-lga6.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet2.
      ENDIF.
      IF NOT wa_itab-bet6 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET06'.
        it_pprop-fval = wa_itab-bet6.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************11
      IF NOT wa_itab-lga7 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA07'.
        it_pprop-fval = wa_itab-lga7.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet2.
      ENDIF.
      IF NOT wa_itab-bet7 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET07'.
        it_pprop-fval = wa_itab-bet7.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************12
      IF NOT wa_itab-lga8 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA08'.
        it_pprop-fval = wa_itab-lga8.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet2.
      ENDIF.
      IF NOT wa_itab-bet8 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET08'.
        it_pprop-fval = wa_itab-bet8.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************13
      IF NOT wa_itab-lga9 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA09'.
        it_pprop-fval = wa_itab-lga9.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet2.
      ENDIF.
      IF NOT wa_itab-bet9 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET09'.
        it_pprop-fval = wa_itab-bet9.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************14
      IF NOT wa_itab-lga10 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-LGA010'.
        it_pprop-fval = wa_itab-lga10.
        APPEND it_pprop.
        CLEAR it_pprop.
        bet1 = wa_itab-bet2.
      ENDIF.
      IF NOT wa_itab-bet10 IS INITIAL.
        it_pprop-infty = '0008'.
        it_pprop-fname = 'P0008-BET010'.
        it_pprop-fval = wa_itab-bet10.
        APPEND it_pprop.
        CLEAR it_pprop.
      ENDIF.
*******************************************************************************************************15
   it_pprop-infty = '0008'.
   it_pprop-fname = 'P0008-LGA11'.
   it_pprop-fval = wa_itab-lga11.
   APPEND it_pprop.
   CLEAR it_pprop.
   bet1 = wa_itab-bet2.
   it_pprop-infty = '0008'.
   it_pprop-fname = 'P0008-BET11'.
   it_pprop-fval = wa_itab-bet11.
   APPEND it_pprop.
   CLEAR it_pprop.
********************************************************************************************************16
   it_pprop-infty = '0008'.
   it_pprop-fname = 'P0008-LGA12'.
   it_pprop-fval = wa_itab-lga12.
   APPEND it_pprop.
   CLEAR it_pprop.
   bet1 = wa_itab-bet2.
   it_pprop-infty = '0008'.
   it_pprop-fname = 'P0008-BET12'.
   it_pprop-fval = wa_itab-bet12.
   APPEND it_pprop.
   CLEAR it_pprop.
********************************************************************************************************17
   it_pprop-infty = '0008'.
   it_pprop-fname = 'P0008-LGA13'.
   it_pprop-fval = wa_itab-lga13.
   APPEND it_pprop.
   CLEAR it_pprop.
   bet1 = wa_itab-bet2.
   it_pprop-infty = '0008'.
   it_pprop-fname = 'P0008-BET13'.
   it_pprop-fval = wa_itab-bet13.
   APPEND it_pprop.
   CLEAR it_pprop.
********************************************************************************************************18
   it_pprop-infty = '0008'.
   it_pprop-fname = 'P0008-LGA14'.
   it_pprop-fval = wa_itab-lga14.
   APPEND it_pprop.
   CLEAR it_pprop.
   bet1 = wa_itab-bet2.
   it_pprop-infty = '0008'.
   it_pprop-fname = 'P0008-BET14'.
   it_pprop-fval = wa_itab-bet14.
   APPEND it_pprop.
   CLEAR it_pprop.
BREAK-POINT.
      CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
        EXPORTING
          number = wa_itab-pernr
        IMPORTING
          return = wa_bapireturn1.
      BREAK-POINT.
     IF c_action = 'INS'.
       CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
         EXPORTING
           pernr           = wa_itab-pernr
           actio           = 'INS'
         tclas           = 'A'
           begda           = wa_data-begda_out             "'20110401'
           endda           = wa_data-endda_out             "'99991231'
           dialog_mode     = '2'
         luw_mode        = '1'
         IMPORTING
           return          = wa_bapireturn
           return1         = wa_bapireturn1
           hr_return       = wa_hr_return
         TABLES
           proposed_values = it_pprop
           modified_keys   = it_modified_keys.
       IF NOT wa_bapireturn IS INITIAL.
         WRITE : / wa_bapireturn.
         CLEAR : wa_itab , wa_bapireturn.
       ENDIF.
     ELSEIF c_action = 'MOD'.
        CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
          EXPORTING
         infty         = '0008'
            pernr           = wa_itab-pernr
            actio           = 'MOD'
            begda           = wa_data-begda_out             "'20110401'
            endda           = wa_data-endda_out             "'99991231'
      record        = p_record
         recordnumber = wa_itab-SEQNR
         operation     = change
         nocommit      = nocommit
            dialog_mode     = '0'
         IMPORTING
            return          = wa_bapireturn
            return1         = wa_bapireturn1
            hr_return       = wa_hr_return
          TABLES
            proposed_values = it_pprop
            modified_keys   = it_modified_keys.
        IF NOT wa_bapireturn IS INITIAL.
          WRITE : / wa_bapireturn.
          CLEAR : wa_itab , wa_bapireturn.
        ENDIF.
     ENDIF.
      CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
        EXPORTING
          number = wa_itab-pernr
        IMPORTING
          return = wa_bapireturn1.
    ENDLOOP.
ENDLOOP.

Here is a sampe, and the logic you are using for wages goes in the internal table for wages (you already have the enqueue & dequeue so you don't have to worry about that, so you only have to add the BAPI_TRANSACTION_COMMIT):
CALL FUNCTION 'BAPI_BASICPAY_CHANGE'
EXPORTING
    employeenumber             = pa0008-pernr
    subtype                    = pa0008-subty
    objectid                   = pa0008-objps
    lockindicator              = pa0008-sprps
    validitybegin              = pa0008-begda
    validityend                = pa0008-endda
    recordnumber               = pa0008-seqnr
    payscaletype               = pa0008-trfar
    payscalearea               = pa0008-trfgb
    payscalegroup              = pa0008-trfgr
    payscalelevel              = pa0008-trfst
*   NEXTINCREASE               =
*   LOCALALLOWLEVEL            =
*   PARTNERSHIP                =
*   CURRENCY                   =
*   COMPARISONPAYSCLTYPE       =
*   COMPARISONPAYSCLAREA       =
*   COMPARISONPAYSCLGRP        =
*   COMPARISONPAYSCLLVL        =
*   COMPNEXTINCREASE           =
*   CAPACITYUTILLEVEL          =
*   HOURSWORKEDPERPERIOD       =
*   ANNUALSALARY               =
*   CASEGROUPCATALOG           =
*   CASEGROUP                  =
*   CURRENCYANNUALSALARY       =
*   REASON                     =
*   NOCOMMIT                   =
* importing
*   return                     =
TABLES
   wagetypes                  = wages.
Regards,
Ryan Crosby

Delta load from ODS to cube failed - Data mismatch

Hi all
We have a scenario where the data flow is like
R/3 table - >dataSrc -- > pSA - >InfoSrc -> ODS ->Cube.
The cube has an additional field called "monthly version"
and since it is a history cube , it is supposed to hold data
snapshots of the all data in current cube for each month .
We are facing the problem that the Data for the current month
is there in the history ODS but not in the cube . In the ODS ->Manage->requests
tab i can see only 1 red request that too with 0 recs.
However ,In the cube -> manage-> reconstruction tab , i can see 2 Red request
with the current month date. Could these red requests be the reason for
data mismatch in ODS and cube .
Please guide as to how can i solve this problem .
thanks all
annie

Hi
Thanks for the reply.
Load to Cube is Delta and goes daily .
Load to ODS is a full on daily basis .
Can you help me how to sort this issue . I have to work directly in production env . so has to be safe and full proof .
Thanks
annie

Funds management cube getting data from 4 ods, data not seen in cube

Hello all,
I am working on funds management cubes (0PU_C02 and 0PU_C03). These two cubes get data from like 7 or 8 ODS. Can someone tell me which are the ODS which feed to respective cubes. I have the mappings done but i am getting very confused.
In the ods 0PU_O44 there is RLDNR for Ledger and I can see that data in ODS but when i run load to cube I dont see the ledger data (its direct mapping there are no routines or rules).
Is there any sequence with wihic we have to load the data?
Thanks
Message was edited by: Raj M

Hi Raj,
I was going thru the forums who has knowledge in Public sector when i came accross ur forum.Can i get your email id..i have some questions to ask regarding student administration.
thanks.

Modifying Cube/ODS data for few entries

Similar Messages

Maybe you are looking for