Infotype 0008-End date issue

Hi
Whenever my client wants to delete a wage type in infotype 0008 ( Basic pay ), they are not getting the end date 31/12/9999 , they are getting the current month as the end date ( For example if we delete a wage type on 01/06/2009 , the end date should be 31/12/9999 ,but here we are getting 30/06/2009 )
Thanks in Advance .

IT008 is haveing TC 1
say
if the salary of an employee is 10,000
he joined in the month of jan 2009
It0008
Begda 01.01.2009 endda 31.12.9999 because his salary will not changed on monthly basis right unles and untill if he has any increment or promotion for this we have to run the Actions
so kidnly check if thee is any master data problem or TC problem for IT008 in V_T582A
if it gets changed in the march
the record shd be delimited for the month of FEB
01.03.2009 31.12.9999
0101.2009 28.02.2009

Similar Messages

Infotype 0008 Wage type Issue(Urgent)

Hi all,
An hiring action was run for a new employee and subsequent information was input in PA30.Along with other information wage-type was filled in Infotype 0008.
Problem: When we check the corresponding transparent table PA0008 we are unable to find wage type or amount entry there. But when we retrieve the same in PA30 we get all the information along with wage-type and amount.
Can someone please tell as to where the data is getting retrieved from if it is not saved in PA0008.
Thanks and Regards,
Ribhu

Hi ALL
Thanks for your response.
but the problem isn't solved. The client says that this WT is not a proportionate value instead amount should be payed for the hours the employees works.
In table T510 i find the amount as 2.00 DKK which appears in the infotype 0008 amount field.
Kindly advice

Infotype 0008 wage-type issue.

Hi all,
An hiring action was run for a new employee and subsequent information was input in PA30.Along with other information wage-type was filled in Infotype 0008.
Problem: When we check the corresponding transparent table PA0008 we are unable to find wage type or amount entry there. But when we retrieve the same in PA30 we get all the information along with wage-type and amount.
Can someone please tell as to where the data is getting retrieved from if it is not saved in PA0008.
Thanks and Regards,
Ribhu

Hi Ribhu,
You have to retrieve data through the Reports only because data of IT8 is stored in the infotype only and we cannot check the data from the database table .
It is suggested to get the Report or use standard report.
Manoj Shakya.
Technical-Fuctional Consultant
SAP-HR
******(Useful answers should be rewarded)

Infotype 0008 master data with no salary and no wage types.

I am an abapper so I apologise whole heartedly in advance for what may be a silly question.
I want to use infotype 0008 only to hold master data values. The only fields I want filled are:
Pay Scale Type,
Pay Scale Area,
Pay Scale Group,
Pay Scale Level,
Capacity utilization level.
Is it possible to configure infotype 0008 just to enter these values and nothing else. I don't any values in Annual Salary, Wage types, etc.

Dear Gemini,
You can hide some of the fields if you donu2019t want to display or you can make them Output fields (table name T588M, and select the module pool, MP000800).
Thanks
Haji

How to retrive data from infotype 0008 &0021 and dispaly as alv output

hi all,
i have to read data from infotype 0008 and infotype 0021 and display as alv grid..
can any one help me..
<removed by moderator>
regards,
viswanath
Moderator message: please search for information and try yourself before posting here.
Edited by: Thomas Zloch on Jan 12, 2012

Hello Sourabh,
If I am not wrong, there are two parts two your query...
a) Data or Content Retrieval
b) Displaying Retrieved content
Here is my feedback
a) The Content can be Retrieved using the FM ARCHIV_GET_TABLE.
Pass the Archive Object, SAP Object and the SAP Object ID and based on the Connection table entries (TOA*), the underlying Content Repository (T-code OAC0) is determined and a request for synchronous retrieval is made to the Content Server.
b) Display of Retrieved content is normally done through dedicated viewers (Ex: Livelink Viewer) or front-end applications (Excel, Word) based on the Protocol (OAA3/OAA4) specified in the Content Reository Configuration. Hence, to my knowledge, you cannot display the content directly in the Smartform.
With Regards
Vijay Gajavalli

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

Change infotypes end date when delete leaving action for employee

Hello,
I created new infotype and when employee leaves its end date is changed for leaving date.
When leaving action is deleted ther is some least of infotypes that user can sign so the end date of selected infotypes will be changed to 31.12.9999. How can i add my infotipe to this list?
Thank you,
Paulina

Hi,
Maintain IT 0041 where in that table maintain employee start date of hiring and leaving date of employee bze in IT 0000 the dates will change as per action lets say if employee hire that date will be in IT 0000 action and if employee gets promotion date or leaving date that will store in IT 0000 by delimiting other actions
So maintain IT 0041 where you can pull dates from there if you maintain
End date will always be 31.12.9999 so check action start date you will get in sequence
Thanks
Edited by: Vibinsap on Mar 9, 2012 7:12 AM

Short dump while changing the end date of infotype 0167 through PA30

Hi all,
I am getting short dump while changing the end date of infotype 0167(Health Plans) through Tcode PA30.
dump descript is as below
An exception occurred that was not caught.
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_HRPA_VIOLATED_POSTCOND
Date and Time          11.03.2010 07:06:26
What happened?
    The exception 'CX_HRPA_VIOLATED_POSTCONDITION' was raised, but it was not
     caught anywhere along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
     'CL_HRPA_SAPUP50R_ADAPTER======CP' has to be
    terminated.
thanks
shahid

Search OSS Notes for that.

Why the delivery date is the same date as 'transptn plan date" & loading date' & ' good issue' & GR end date'

Hi Experts,
why the delivery date is the same date as ‘transptn plan date” & loading date’ & ‘ good issue’ & GR end date’.
in shipping tab i can see Planned Deliv. Time 170 Days ... wat could be the reason.
Many Thanks:
Raj Kashyap

Hi Jurgen,,
Thanks for quick reply!!
But i didnot find any things like that .. what could be the customizing .. and we are using GATP from APO side.
\Raj Kashyap

Org.Assignment Infotype start date and End date is getting wrong.

Hi, When i create a new employee in PA40, in Org. Assignment infotype start date and end date is getting wrong. for eg. When i create an employee on 01.04.2014. In org. assignment infotype its getting like this. 01.01.2014 to 31.03.9999 and 01.04.9999 to 31.12.9999 Two date entries are creating by default.

Hi
Check in the Table - T588Z : Dynamic Actions ,is there any custom routines causing the defaulting dates functionality.
Thanks,
Sreeram

Infotype 0008 reecord creation in a BAdI - Issue

I am implementing the method 'CALC_SAL_ADJUSTMENT' of the BAdI definition 'HRECM00_ACTIVATION'. As per the requirement, I have to copy the record in the importing parameter IT0008_OLD, make some modifications to the record and then pass it on to the exporting parameter IT0008. Simultaneously, a new infotype 0008 record has also to be created based on the data in the new record IT0008. I tried using the FM 'BAPI_BASICPAY_CREATESUCCESSOR', since this will also delimit the previous record.
**Create a new Infotype 0008 record, delimiting the previous record
CALL FUNCTION 'BAPI_BASICPAY_CREATESUCCESSOR'
EXPORTING
employeenumber = pernr
subtype = it0008_old-subty
validitybegin = effdt
validityend = c_endda
payscaletype = it0008_old-trfar
payscalearea = it0008_old-trfgb
payscalegroup = it0008_old-trfgr
payscalelevel = it0008_old-trfst
nextincrease = it0008_old-stvor
localallowlevel = it0008_old-orzst
partnership = it0008_old-partn
currency = it0008_old-waers
comparisonpayscltype = it0008_old-vglta
comparisonpaysclarea = it0008_old-vglgb
comparisonpaysclgrp = it0008_old-vglgr
comparisonpayscllvl = it0008_old-vglst
compnextincrease = it0008_old-vglsv
capacityutillevel = it0008_old-bsgrd
hoursworkedperperiod = it0008_old-divgv
annualsalary = v_annsal
casegroupcatalog = it0008_old-falgk
casegroup = it0008_old-falgr
currencyannualsalary = it0008_old-ancur
reason = it0008_old-preas
nocommit = space
IMPORTING
return = wa_return
employeenumber = v_empno
subtype = v_subty
objectid = v_objectid
lockindicator = v_lockind
validitybegin = v_valbegin
validityend = v_valend
recordnumber = v_recordno
TABLES
wagetypes = it_bwagetype.
However, it is raising an exception 'cx_hrpa_violated_precondition', which is not caught and hence a run-time error.
I tried using the above function module in a report program and it worked fine.
Can anybody please let me know, whether it is possible to create an infotype 0008 record inside the above BAdI implementation? and if yes, where am I going wrong?
Thanks in advance.
Sujit.

put the BAPI call as a BACKGROUND TASK & try it..
~Suresh

Problem in changing end date of PA-Infotype using HR_INFOTYPE_OPERATIONS .

Hi All,
I am trying to change the end date of an active record in an infotype using HR_INFOTYPE_OPERATIONS FM. But am getting an error, 'Infotype does not exist'.
I am using operation as 'MOD' and passing appropriate parameters as required.
it would be great if someone can help me out to understand, why could that error be coming?

Hi Santosh,
With this FM you cannot change the enddate as enddate is a key field and used to determine the exact record in the database.
Why don't you use PA30 to change end date of an infotype record?
Or else delete the row first w. HR_INFOTYPE_OPERATION DEL and insert it again with INS operation and new end date.
Regards,
Dilek
Edited by: Dilek Ersoz Adak on Jan 8, 2010 7:54 AM

Start Date,End Date prompt issue

Hi
I have a problem for prompts related to start Date and End Date selection i.e
Start Date                   End Date
01-Jan-2007                 31-Jan-2007
01-Jul-2008                  31-Jul-2008
The issue is if the user select the Start Date from a list of values(prompt) the End Date LOV's should appear only from its related Start Date i.e
If Start Date is selected as 01-Apr-2007 then End Date LOV's should start only from 30-Apr-2007
and the End Date LOV's should be seen only for the next 12 months i.e only till 31-Mar-2008
Please suggest me how I can resolve this prompt issue

hi there,,
you can not do that at the prompt form
coz every prompt is independent from the other.
good luck
Amr

Infotype for Employee begin date and end date

Hi Friends,
Could any one tell me the infotype and fields for getting employee joining date and end date.
Regards,
Susmita.

Infotype 41 (Date Specifications) should have all dates.
Infotype 2...i.e. PA0002 BEGDA & ENDDA may not have actual start and end date depending on how your company maintains it.
In Infotype 41 (table PA0041)...get either BEGDA & ENDDA or get correct date based on qualifier DAR01-DAR12.
Thanks,
Pushpinder Randhawa

Week End Date calculates dates in table issues

Greetings All,
I'm working on a LiveCycle Designer ES4 document that has a Week Ending Date MM-DD-YYYY (which need to always be a Saturday) selected in a subform.
I need this Week End Date to then calculate and display the selected Saturday and the previous days in a seperate subform with a table. The days need to display in seperate columns below the header.
This is what I have so far:
TopmostSubform.Page1.Requestor.WeekEndDate::exit - (FormCalc, client)
var endDate = Date2Num($,"MM-DD-YYYY")
var dayOfWeek = Num2Date(endDate, "E")
if (dayOfWeek <> 7) then
   xfa.host.messageBox("Ending date must be a Saturday")
   $ = null
   xfa.host.setFocus("$")
endif
Page1.#subform[1].InputTable.Row1[0].Date7 = Num2Date(endDate - 0, "DD")
Page1.#subform[1].InputTable.Row1[0].Date6 = Num2Date(endDate - 1, "DD")
Page1.#subform[1].InputTable.Row1[0].Date5 = Num2Date(endDate - 2, "DD")
Page1.#subform[1].InputTable.Row1[0].Date4 = Num2Date(endDate - 3, "DD")
Page1.#subform[1].InputTable.Row1[0].Date3 = Num2Date(endDate - 4, "DD")
Page1.#subform[1].InputTable.Row1[0].Date2 = Num2Date(endDate - 5, "DD")
Page1.#subform[1].InputTable.Row1[0].Date1 = Num2Date(endDate - 6, "DD")
However I keep getting an error on the WeekEndDate when selecting a Saturday.
Does anyone have any idea what I'm doing wrong?
Thank you for any help!
-Michelle

Well, I never got an answer from the forum here, but to help out others - here is what I did:
This was all done in FormCalc.
The object WeekEndDate Date/Time Field has a set pattern date{MM/DD/YYYY} in the Object Field Pattern in LiveCycle.
BUT, the Scripting required the pattern to be YYYY-MM-DD
Why? I have no flipping clue. It won't work any other way for me.
Also this item requires a Saturday Date to be chosen. Days of the week are designated by numbers (Sunday = 1, Monday = 2, etc.)
The line <>7 means that if the day is not Saturday (7) then the error message "Ending date must be a Saturday" will appear.
This is the Exit event Script:
TopmostSubform.Page1.Requestor.WeekEndDate::exit- (FormCalc, client)
var endDate = Date2Num($,"YYYY-MM-DD")
var dayOfWeek = Num2Date(endDate, "E")
if (dayOfWeek <> 7) then
     xfa.host.messageBox("Ending date must be a Saturday")
     $ = null
     xfa.host.setFocus("$")
endif
The individual Date cells are set to a Date/Time Field with no pattern set in the Object Field Pattern in LiveCycle.
The coding below designates a MM/DD pattern.
Each individual field has it's own scripting, with the appropriate minus calculation - #
This is the Calculate script for the Sunday cell:
TopmostSubform.Page1.#subform[1].InputTable.Row1[0].Date1::calculate - (FormCalc, client)
var dateNum = date2num(TopmostSubform.Page1.Requestor.WeekEndDate.formattedValue,"MM/DD/YYYY") - 6
$.rawValue = num2date(dateNum,"MM/DD")
And the Saturday cell, that needed to display the Saturday End Date has the following Script, with NO minus number:
TopmostSubform.Page1.#subform[1].InputTable.Row1[0].Date7::calculate - (FormCalc, client)
var dateNum = date2num(TopmostSubform.Page1.Requestor.WeekEndDate.formattedValue,"MM/DD/YYYY")
$.rawValue = num2date(dateNum,"MM/DD")
Why did I include this all here?
Because this whole project has been gawd-awful, and hopefully these insights can help another struggle forms designer understand the FormCalc scripting used.
-M

Infotype 0008-End date issue

Similar Messages

Maybe you are looking for