Fetch PERNR with Future BEGDA

Hi Gurus,
My requirement is to fetch the PERNR using GET PERNR, but when i fetching the records for current date
Eg : PERNR BEGDA AEDTM

Hi ,
in your report program in the Attributes Tab provide the Logical Database as PNP and do the following
*& Tables declaration
TABLES: PERNR.
*& Infotypes declaration
INFOTYPES: 0001,                       " Org Assignment
           0002,                       " Personel Data
           0006,                       " Addresses
           0003 MODE A.                " Payroll status
*& START-OF-SELECTION EVENT
START-OF-SELECTION.
GET PERNR.
PROVIDE * FROM P0001
          * FROM P0002
          * FROM P0006
    BETWEEN PN-BEGDA AND PN-ENDDA.
IF P0001_VALID EQ 'X'.
      WRITE:
        / P0001-PERNR, P0001-BEGDA, P0001-ENDDA.
    ENDIF.
now when u run the report select the date as current date.
hope this help.... try out
best of luck!!
thanks
Ravi Aswani

Similar Messages

Purchase order error with future date

Hi,
Here one scenario like
We have created a sales order VA01-->Pur. Order ME21N with current date i.e., 05.09.2008. System able to post perfectly and post MIRO, cutomer invoice and finally released to accounting.
Now, same sales order VA01-->Pur. Order ME21N with future date i.e., 05.09.2009. System threws error message "Account requires an assignment to a cost object".
Here my question is, why system is asking this assignment if i gave future date(05.09.2009) and why system is not asking if i gave current date(05.09.2008) ? remaining all are same except date
Looking forward your comments/thoughts
thansk
anifi

Hi,
Thanks for your reply
regards
Edited by: Anifi on Sep 22, 2008 6:18 AM
Edited by: Anifi on Sep 29, 2008 2:05 PM

O4NM or O4TEN Create & Actualize a Ticket with future date

Hi,
I would like to create a ticket with future date; in the tab 'Movement Details'....'Start Date', 'End Date' & 'Posting Date'.
Example: Ticket to be created with the start & end date as 05/20/02008.
System throws error : Cannot actualize a ticket for a future date or time.
Please suggest.
Thanks
Parveen

Hi Sandil,
During the ticket creation, when I'm entering the 'Start Date' and 'End Date' with a future date eg 05/30/2008; getting the error.
The requirement is to create & actualize the ticket with dates 'Start Date', 'End Date' and the 'Posting Date' with future date.
FYI, there is a significant number of tickets that are booked using end of the month date in order to avoid several fees. We also have to do closing and reconsolidations end of the month. These activities create a significant stress to complete tasks before deadlines. Along with that, we also have to complete ticketing that we scheduled for end of the month. Therefore, resolving the issue of been able to ticket and actualize tickets ahead of time would substantially make processes and procedures easy when we are stretched for time which we don't have towards the end of the month.
Please suggest.
Thanks
Parveen

R11.0.3: An Invoice with future dated apyment data flow

제품 : FIN_AP
작성날짜 : 2003-11-18
R11.0.3: An Invoice with future dated apyment data flow
===============================================
PURPOSE
Future Dated Payment Term을 사용하는 Invoice의 Data Flow에 대해 살펴보도록 한다.
Explanation
accounting rule = accrual
.allowed future dated payment
1. Create a standard invoice (invoice amount: 2100, item amount: 2100, payment term : future dated payment)
And transfer it to GL.
* ap_invoice_distributions_all
accounting_date = 2003-11-11
accrual_posted_flag = Y
posted_flag = Y
* ap_trial_balance
accounting_date = 2003-11-11
distribution_amount = 2100
* 해당 data gl_interface table로 넘어감.
2. Posting these transferred journals in gl module
* 해당 data가 gl_interface table에서 삭제 된 후
* gl_je_lines
accounted_dr = 2100 charge
accounted_cr = 2100 liability
3. Create a payment against this invoice with mature date = 12-nov-2003 and then transfer it to gl
* ap_invoice_payments_all
accounting_date = 2003-11-11
accrual_posted_flag = 'N'
posted_flag = 'N'
future_pay_posted_flag = 'Y'
* ap_payment_distributions_all
line_type_lookup_code = 'CASH'
* ap_trial_balance
accounting_date = 2003-11-11
payment_amount = 2100
* ap_checks_all
status_lookup_code = 'NEGOTIABLE'
4. Posting these payment journals in gl module
* 해당 data가 gl_interface table에서 삭제 된 후
* gl_je_lines
accounted__cr : 2100 future pay
accounted_dr : 2100 liability
5. Clear this payment and then transfer to gl
Future dated payment 이고 Cash Management 를 사용하면 Cash Management 에서
Bank Reconcilation을 해주시면 됩니다.
Cash Management 를 사용하지 않으실 때는
"automatic clearing for future dated payment" 를 수행하여서 clear 를 해주어야 합니다.
이번 test case에서는 cash managemnt를 사용하지 않고 automatic clearing for
future dated payment 를 수행하여 clear 해주었습니다.
* ap_checks_all
status_lookup_code = 'CLEARED BUT UNACCOUNTED'
Cash Management를 사용하지 않기 때문에 status가 위와 같이 나타납니다.
Cash Management를 사용하면 option에 따라 status가 cleared나 reconciled로 변경 됩니다.
6. Transfer these cleared payment to gl and posting in gl
* 이 때에는 ap_trial_balance table에는 아무런 영향도 주지 않습니다.
* ap_invoice_payments_all
accrual_posted_flag = 'Y'
posted_flag = 'Y'
* gl_je_lines
accounted_dr= 2100 future pay
accounted_cr = 2100 cash
Example
Reference Documents
N/A

Rohini,
Thanks for your answer; I was out for few days and hence the delay.
What I am looking for is the complete usage model of the following ODS.
1> 0BBP_SC     we have figured it out
2> 0BBP_SCA    we have figured it out
3> 0BBP_DOC    we have figured it out
4> 0bbp_inv    we need help
     Looks like this can be populated from R3 using the following
Data Source    Info Source                    ODS Object
2LIS_02_ITM    2LIS_02_ITM                 0BBP_INV
2LIS_02_HDR    2LIS_02_HDR                0BBP_INV
5> 0BBP_DS     we need help
6> 0bbp_po     we need help
    The same combination is also used to populate the 0BBP_PO as well. We suspect that 0BBP_DS will then be populated from both 0BBP_INV and 0BBP_PO. At least that what we though after activating the BC and reading the sap help on BC for SRM.
We are doing a proof of concept and want to know all the ODS with data. We want to build an end to end (Shopping cart, approval, Doc flow, PO data with value, Invoice data with Value) and struggling to understand the model surrounding this three ODS ( 0bbp_inv, 0bbp_ds, 0bbp_po). Any help in this area will be appreciated.
Thanks
Arun

Error while trying to invoice the delivery doc with future date

Hi Gurus,
I am trying to create the Invoice document with future date with reference to delivery document,but the system is not allowing to do and its throwing the error message billing date is greater than current date not authorized.How to resolve this issue.
Thanks and Regards,
hari Challa.

Dear Hari
Curious to know why you are trying to maintain a future date in billing when you yourself very well know that it is WRONG. Logically, the invoice date should be either Actual GI Date from Delivery or the system date.
Coming to your question, in VTFL, for your item category if routine 11 is maintained for the field Data VBRK/VBRP, you cannot achieve what you want.
thanks
G. Lakshmipathi

COLLECTION ITERATOR PICKLER FETCH along with XMLSEQUENCEFROMXMLTYPE

Hi All,
We have Oracle database 10.2.0.4 on solaris 10.
I found some xml queries which are consuming CPU and memory highly, below is the execution plan for one of this xml sql.
PLAN_TABLE_OUTPUT
SQL_ID gzsfqp1mkfk8t, child number 0
SELECT B.PACKET_ID FROM CM_PACKET_ALT_KEY B, CM_ALT_KEY_TYPE C, TABLE (XMLSEQUENCE (EXTRACT (:B1 ,
'/AlternateKeys/AlternateKey'))) T WHERE B.ALT_KEY_TYPE_ID = C.ALT_KEY_TYPE_ID AND C.ALT_KEY_TYPE_NAME = EXTRACTVALUE
(VALUE (T), '/AlternateKey/@keyType') AND B.ALT_KEY_VALUE = EXTRACTVALUE (VALUE (T), '/AlternateKey') AND NVL
(B.CHILD_BROKER_CODE, '6209870F57C254D6E04400306E4A78B0') = NVL (EXTRACTVALUE (VALUE (T), '/AlternateKey/@broker'),
'6209870F57C254D6E04400306E4A78B0')
Plan hash value: 855909818
PLAN_TABLE_OUTPUT
| Id | Operation                           | Name                   | Rows | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
|   0 | SELECT STATEMENT                    |                        |       |       | 16864 (100)|          |       |       |
|* 1 | HASH JOIN                          |                        |    45 | 3240 | 16864   (2)| 00:03:23 |       |       |
|   2 |   TABLE ACCESS FULL                 | CM_ALT_KEY_TYPE        |     5 |   130 |     6   (0)| 00:00:01 |       |       |
|* 3 |   HASH JOIN                         |                        |   227 | 10442 | 16858   (2)| 00:03:23 |       |       |
|   4 |    COLLECTION ITERATOR PICKLER FETCH| XMLSEQUENCEFROMXMLTYPE |       |       |            |          |       |       |
|   5 |    PARTITION HASH ALL               |                        |    10M|   447M| 16758   (2)| 00:03:22 |     1 |    16 |
|   6 |     TABLE ACCESS FULL               | CM_PACKET_ALT_KEY      |    10M|   447M| 16758   (2)| 00:03:22 |     1 |    16 |
PLAN_TABLE_OUTPUT
Predicate Information (identified by operation id):
   1 - access("B"."ALT_KEY_TYPE_ID"="C"."ALT_KEY_TYPE_ID" AND
              "C"."ALT_KEY_TYPE_NAME"=SYS_OP_C2C(EXTRACTVALUE(VALUE(KOKBF$),'/AlternateKey/@keyType')))
   3 - access("B"."ALT_KEY_VALUE"=EXTRACTVALUE(VALUE(KOKBF$),'/AlternateKey') AND
              NVL("B"."CHILD_BROKER_CODE",'6209870F57C254D6E04400306E4A78B0')=NVL(EXTRACTVALUE(VALUE(KOKBF$),'/AlternateKey/@broker'
              ),'6209870F57C254D6E04400306E4A78B0'))Seems due to
1.COLLECTION ITERATOR PICKLER FETCH along with XMLSEQUENCEFROMXMLTYPE which i think is due to usage of table( XMLSEQUENCE() )
2.Conversion taking place according to SYS_OP_C2C function as shown in Predicate Information.
3.Table is not using xmltype datatype to store XML
4.Wilcards have been used (/AlternateKey/@keyType)
Could anyone please help me in tuning this query as i know very less about XML DB
Including one more sql which also use to consume huge CPU and memory, these tables are also not hving any column with xmltype datatype.
SELECT /*+ INDEX(e) */ XMLAGG(XMLELEMENT ( "TaggingCategory", XMLATTRIBUTES (G.TAG_CATEGORY_CODE AS
"categoryType"), XMLELEMENT ("TaggingValue", XMLATTRIBUTES (C.IS_PRIMARY AS "primary", H.ORIGIN_CODE AS
"origin"), XMLAGG (XMLCONCAT (XMLELEMENT ("Value", XMLATTRIBUTES (F.TAG_LIST_CODE AS "listType"),
E.TAG_VALUE), CASE WHEN LEVEL = 1 THEN :B4 ELSE NULL END))) )) FROM TABLE (CAST (:B1 AS
T_TAG_MAP_HIERARCHY_TAB)) A, TABLE (CAST (:B2 AS T_ENUM_TAG_TAB)) C, REM_TAG_VALUE E, REM_TAG_LIST F,
REM_TAG_CATEGORY G, CM_ORIGIN H WHERE E.TAG_VALUE_ID = C.TAG_VALUE_ID AND F.TAG_LIST_ID = E.TAG_LIST_ID
AND G.TAGGING_CATEGORY_ID = F.TAGGING_CATEGORY_ID AND H.ORIGIN_ID = C.ORIGIN_ID AND C.ENUM_TAG_ID =
A.MAPPED_ENUM_TAG_ID GROUP BY G.TAG_CATEGORY_CODE, C.IS_PRIMARY, H.ORIGIN_CODE START WITH
A.MAPPED_ENUM_TAG_ID = HEXTORAW (:B3 ) CONNECT BY PRIOR A.MAPPED_ENUM_TAG_ID = A.ENUM_TAG_ID
Plan hash value: 2393257319
| Id | Operation                                    | Name             | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                             |                  |       |       | 16455 (100)|          |
|   1 | SORT AGGREGATE                              |                  |     1 |   185 | 16455   (1)| 00:03:18 |
|   2 |   SORT GROUP BY                              |                  |     1 |   185 | 16455   (1)| 00:03:18 |
|* 3 |    CONNECT BY WITH FILTERING                 |                  |       |       |            |          |
|* 4 |     FILTER                                   |                  |       |       |            |          |
|   5 |      COUNT                                   |                  |       |       |            |          |
|* 6 |       HASH JOIN                              |                  |   667K|   117M| 16413   (1)| 00:03:17 |
|   7 |        COLLECTION ITERATOR PICKLER FETCH     |                  |       |       |            |          |
|* 8 |        HASH JOIN                             |                  | 8168 | 1459K| 16384   (1)| 00:03:17 |
|   9 |         TABLE ACCESS FULL                    | REM_TAG_CATEGORY |    25 |   950 |     5   (0)| 00:00:01 |
|* 10 |         HASH JOIN                            |                  | 8168 | 1156K| 16378   (1)| 00:03:17 |
| 11 |          TABLE ACCESS FULL                   | REM_TAG_LIST     |   117 | 7137 |     5   (0)| 00:00:01 |
| 12 |          NESTED LOOPS                        |                  | 8168 |   670K| 16373   (1)| 00:03:17 |
| 13 |           MERGE JOIN                         |                  | 8168 |   215K|    27   (4)| 00:00:01 |
| 14 |            TABLE ACCESS BY INDEX ROWID       | CM_ORIGIN        |     2 |    50 |     2   (0)| 00:00:01 |
| 15 |             INDEX FULL SCAN                  | PK_CM_ORIGIN     |     2 |       |     1   (0)| 00:00:01 |
|* 16 |            SORT JOIN                         |                  | 8168 | 16336 |    25   (4)| 00:00:01 |
| 17 |             COLLECTION ITERATOR PICKLER FETCH|                  |       |       |            |          |
| 18 |           TABLE ACCESS BY INDEX ROWID        | REM_TAG_VALUE    |     1 |    57 |     2   (0)| 00:00:01 |
|* 19 |            INDEX UNIQUE SCAN                 | PK_REM_TAG_VALUE |     1 |       |     1   (0)| 00:00:01 |
|* 20 |     HASH JOIN                                |                  |       |       |            |          |
| 21 |      CONNECT BY PUMP                         |                  |       |       |            |          |
| 22 |      COUNT                                   |                  |       |       |            |          |
|* 23 |       HASH JOIN                              |                  |   667K|   117M| 16413   (1)| 00:03:17 |
| 24 |        COLLECTION ITERATOR PICKLER FETCH     |                  |       |       |            |          |
|* 25 |        HASH JOIN                             |                  | 8168 | 1459K| 16384   (1)| 00:03:17 |
| 26 |         TABLE ACCESS FULL                    | REM_TAG_CATEGORY |    25 |   950 |     5   (0)| 00:00:01 |
|* 27 |         HASH JOIN                            |                  | 8168 | 1156K| 16378   (1)| 00:03:17 |
| 28 |          TABLE ACCESS FULL                   | REM_TAG_LIST     |   117 | 7137 |     5   (0)| 00:00:01 |
| 29 |          NESTED LOOPS                        |                  | 8168 |   670K| 16373   (1)| 00:03:17 |
| 30 |           MERGE JOIN                         |                  | 8168 |   215K|    27   (4)| 00:00:01 |
| 31 |            TABLE ACCESS BY INDEX ROWID       | CM_ORIGIN        |     2 |    50 |     2   (0)| 00:00:01 |
| 32 |             INDEX FULL SCAN                  | PK_CM_ORIGIN     |     2 |       |     1   (0)| 00:00:01 |
|* 33 |            SORT JOIN                         |                  | 8168 | 16336 |    25   (4)| 00:00:01 |
| 34 |             COLLECTION ITERATOR PICKLER FETCH|                  |       |       |            |          |
| 35 |           TABLE ACCESS BY INDEX ROWID        | REM_TAG_VALUE    |     1 |    57 |     2   (0)| 00:00:01 |
|* 36 |            INDEX UNIQUE SCAN                 | PK_REM_TAG_VALUE |     1 |       |     1   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   3 - access(SYS_OP_ATG(VALUE(KOKBF$),1,2,2)=PRIOR NULL)
   4 - filter(SYS_OP_ATG(VALUE(KOKBF$),2,3,2)=HEXTORAW(:B3))
   6 - access(SYS_OP_ATG(VALUE(KOKBF$),1,2,2)=SYS_OP_ATG(VALUE(KOKBF$),2,3,2))
   8 - access("G"."TAGGING_CATEGORY_ID"="F"."TAGGING_CATEGORY_ID")
10 - access("F"."TAG_LIST_ID"="E"."TAG_LIST_ID")
16 - access("H"."ORIGIN_ID"=SYS_OP_ATG(VALUE(KOKBF$),3,4,2))
       filter("H"."ORIGIN_ID"=SYS_OP_ATG(VALUE(KOKBF$),3,4,2))
19 - access("E"."TAG_VALUE_ID"=SYS_OP_ATG(VALUE(KOKBF$),7,8,2))
20 - access(SYS_OP_ATG(VALUE(KOKBF$),1,2,2)=PRIOR NULL)
23 - access(SYS_OP_ATG(VALUE(KOKBF$),1,2,2)=SYS_OP_ATG(VALUE(KOKBF$),2,3,2))
25 - access("G"."TAGGING_CATEGORY_ID"="F"."TAGGING_CATEGORY_ID")
27 - access("F"."TAG_LIST_ID"="E"."TAG_LIST_ID")
33 - access("H"."ORIGIN_ID"=SYS_OP_ATG(VALUE(KOKBF$),3,4,2))
       filter("H"."ORIGIN_ID"=SYS_OP_ATG(VALUE(KOKBF$),3,4,2))
36 - access("E"."TAG_VALUE_ID"=SYS_OP_ATG(VALUE(KOKBF$),7,8,2))-Yasser
Edited by: YasserRACDBA on Feb 24, 2010 8:30 PM
Added one more sql..

Looking at the second query, it too has a lot of bind variables... Can you find out the types and values of each BIND. Also, I'm suspcious about the use of XMLCONCAT.. Can you found out why the developer is using it..
SELECT /*+ INDEX(e) */ XMLAGG
                            XMLELEMENT
                               "TaggingCategory",
                               XMLATTRIBUTES (G.TAG_CATEGORY_CODE AS "categoryType"),
                               XMLELEMENT
                                 "TaggingValue",
                                 XMLATTRIBUTES (C.IS_PRIMARY AS "primary", H.ORIGIN_CODE AS "origin"),
                                 XMLAGG
                                    XMLCONCAT
                                      XMLELEMENT
                                        "Value",
                                        XMLATTRIBUTES (F.TAG_LIST_CODE AS "listType"),
                                        E.TAG_VALUE
                                      CASE WHEN LEVEL = 1
                                          THEN :B4
                                          ELSE NULL
                                      END
FROM TABLE (CAST (:B1 AS T_TAG_MAP_HIERARCHY_TAB)) A,
      TABLE (CAST (:B2 AS T_ENUM_TAG_TAB)) C,
      REM_TAG_VALUE E,
      REM_TAG_LIST F,
      REM_TAG_CATEGORY G,
      CM_ORIGIN H
WHERE E.TAG_VALUE_ID = C.TAG_VALUE_ID
AND F.TAG_LIST_ID = E.TAG_LIST_ID
AND G.TAGGING_CATEGORY_ID = F.TAGGING_CATEGORY_ID
AND H.ORIGIN_ID = C.ORIGIN_ID
AND C.ENUM_TAG_ID = A.MAPPED_ENUM_TAG_ID
GROUP BY G.TAG_CATEGORY_CODE, C.IS_PRIMARY, H.ORIGIN_CODE
      START WITH A.MAPPED_ENUM_TAG_ID = HEXTORAW (:B3 )
      CONNECT BY PRIOR A.MAPPED_ENUM_TAG_ID = A.ENUM_TAG_IDEdited by: mdrake on Feb 24, 2010 8:11 AM

Unable to fetch Data with apps_query_role

Hi Guru,
There is some issue on fetching data with my database account i have apps_query_role i can fect the data from devlopemnet instance.
which checked in devlopemnt instance:
select * from all_directories
I am getting data
When doing same thing in prod i am getting no row selected. Please help here.

Hi,
it would be hard to guess the things.. Try to check the session_privs from your current session with prod,
Try to check privs granted on directories to specific to your account or not.
- Pavan Kumar N

Cannot reverse document with future posting date

Hi,
When I tried to reverse a document with future posting date, system gives error F5362 Posting date must not be smaller than XX.XX.XXXX (x = future posting date).
Is it possible to do this in SAP?

Hello,
You need to use reversal reason configured accordingly.
Configure the reversal reason for your purpose:
IMG => Financial Accounting => Business Transactions => Adjustment Posting / Reversal / Define Reasons for Reversal
Make SURE that you have ticked Alt.Pos.dt (Alternative Posting Date) check box.
Save it.
Now use this reversal reason for your posting and give a fugure date.
Make sure that the future posting period is opened but NOT closed.
Please also read F1 on alternative posting date check box:
Indicator: Alternative posting date allowed
Indicator as to whether you are allowed to specify an alternative posting date for the relevant reversal reason.
Use
When you use the reversal reason, the system checks that reversal is not carried out using an alternative posting date and therefore possibly in a later posting period or in a later fiscal year.
Examples
If you want to use negative postings during reversal but only if the reversal is posted in the same period, you can define two reversal reasons:
1st reason: No alternative date allowed, generate negative posting
2nd reason: Alternative date allowed, do not generate negative posting
Regards,
Ravi

Issue While Terminating a Service Contract with future date

Hi CRM Gurus,
We are in Oracle EBusiness Suite version R12 (12.1.3) and implementing service contracts for a client.
Please help us with the following issue that we are facing while terminating a service contract line with future date (end of the month).
Example :
A Contract 123 with 10 months of duration (Start Date:01-JUL-2013 and End Date: 30-APR-2014) has a service line 1.0 with unit price as $50 for a period of 10 months .The billing schedule is set for 10 months with each month for $50.
The create main billing is run for the month of Jul 2013 and Aug 2013 and is sent to AR.Now we want to terminate the contract line with 30-Sep-2013 as termination date without any credit back to the customer so that we want to charge for month of Sep as well for $50.
When we give 30-Sep-2013 as termination date and terminate the line, the billing schedule refreshes with $50 for Jul1-Jul 31 and $50 for Aug1-Aug31 and $48.39 for Sep1-Sep 29 instead of 30-Sep which is the termination date that we see on the line.
The requirement is that we want to have the billing for $50 even for the month of Sep,but the system only calculates for $48.39(which is 1 day minus) for the month of Sep. When we give Oct 1 as termination date ,then we get the schedule dates and amounts correctly i.e. 01-Sep to 30-Sep for $50.
How do we achieve to bill for $50 when we put 30-Sep-2013 as termination date ? I see that the regular termination process does not consider timestamp while providing the termination date.
Is this a bug or is there a patch for this or is there a workaround for this other than providing 01-Oct as termination date ?Please help.
Regards,
Sandeep Gorla

Update the Ar Interface Table with value 50$ for that record, before the Invoice gets created.

@MDSHIFT issue with future years

We have a complex calc on a dynamic member using @MDSHIFT. It works perfectly if we arepointing to past years; but if we point to future year(s), it fails without any error.
The calc itself validates fine.
Are there any exceptions for using @MDSHIFT with future years?(we do have forecast data for the future years too)
Example from our calc script:
((@MDSHIFT("Adjust Stat Forecast"->"Forecast"->"Jan",1,"Year",)
Edited by: 784749 on Mar 10, 2011 1:57 PM

Hi,
What do you try to shift? For example: Data from Next Year to current Year?
You may need to check what member you fix on in the calc, the problem could be because the fix is not correct or the
desitination is not correct.

Got the email from Apple Aperture compatible with future versions of iOS? (Mac OS?)

Got the email from Apple about Aperture this morning. They had a huge omission: are they going to keep Aperture compatible with future iOS? If not, I want, at a minimum, a refund for what I paid for the app.

They had a huge omission: are they going to keep Aperture compatible with future iOS?
There will be no further development of Aperture. That much should be clear from the announcement, that Aperture will no longer be sold at the AppStore. You are lucky - you used the last chance to buy the best photos app ever Apple created. The new Photos is not intended to be used by professional photographers like Aperture was. And you will be able to use and enjoy it as long as you keep a compatible operating system on your Mac.

Fetching pernr from workitem

HI All,
I am working on workflow for approval /rejection of leave requests. Can someone tell me if there is any BAPI/function module or DB table from where i can fetch the personnel number (pernr) from the workitem id in my function module?
Regards
Partha
Edited by: Partha Kar on Apr 6, 2010 6:03 PM

Check below code snippet, Actually Iam not clear whose pernr you are trying to get whether the Intiiators or the approvers, if it is intiiators the you can use the below code snippet,
DATA:
           lv_wiid   TYPE sww_wiid,
           lt_cont   TYPE STANDARD TABLE OF swr_cont,
           ls_cont TYPE swr_cont,
           lv_pernr TYPE pernr_d,
           lv_initiator TYPE sysid.
CALL FUNCTION 'SAP_WAPI_READ_CONTAINER'
EXPORTING
    workitem_id      = lv_wiid
TABLES
    simple_container = lt_cont.
READ TABLE lt_cont INTO ls_cont WITH KEY element = '_WF_INITIATOR'.
IF sy-subrc IS INITIAL.
lv_initiator = ls_cont-value.
CALL FUNCTION 'RP_GET_PERNR_FROM_USERID'
    EXPORTING
      begda     = sy-datum
      endda     = sy-datum
      usrid       = lv_initiator
      usrty       = '0001'
    IMPORTING
      usr_pernr = lv_pernr
    EXCEPTIONS
      retcd     = 1
      OTHERS    = 2.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDIF.
If at all you are looking for approvers pernr then you need to change read table statement by replacing the key from WIINITIATOR to WIACTUAL_AGENT.

Fetching Data with dates

Hi Experts,
I am having this scenario.
PERNR          BEGDA          ENDDA
000001          01.01.2006     13.01.2007
000001          14.01.2007     31.12.9999
000002          14.01.1982     12.11.2006
000002          13.11.2006     31.01.2007
000002          01.02.2007     31.12.9999
This is the scenario my requirement is like that if I will enter PERNR = 1 then it will display 14.01.2007 record. And if I will enter PERNR = 2 then it will display 13.11.2006.
Regards,
Rajneesh Gupta

i don know why u r such awkward requirements.but instead of going for simple HR,u shud go for ABAP-Hr and then write ur code.use LDB PNP.
and use Get pernr event and then move ur concerned data to ur output internal table.
Get pernr event will fetch all the Infotype records for the concerned pernr and then u can have particular one in ur iutput table as per ur requirement.
demo code for using LDBs -
tables: pernr.
infotypes: 0021.
*eject
*& Constants                                                           *
constants: c_1(1)       type c               value '1' .
data: begin of t_output occurs 0,
       num_dep(2) type n,
       pernr like pernr-pernr.
data: end of t_output.
data: count type i.
*eject
*& Initialization                                                      *
Initialization.
Initialize Selection-Screen values
perform init_selction_screen.
Start-of-selection.
get pernr.
clear t_output.
Read Infotype 0021
rp-provide-from-last p0021 space pn-begda pn-endda.
check pnp-sw-found eq c_1.
Gather all the required information related to the emp
describe table p0021 lines count.
move: pernr-pernr to t_output-pernr,
        count to t_output-num_dep.
append t_output.
Clear count.
*eject
*& End-of Selection                                                    *
end-of-selection.
perform print_report.
*eject
*&      Form print_report
*Description:
FORM print_report .
Print the report
loop at t_output.
skip 1.
at sum
write: 2 t_output-pernr,
         15 t_output-num_dep.
endloop.
ENDFORM.                    " print_report

My rMBP won't fetch emails with the mail app on it's own?

I have a hotmail and yahoo account synced with the mail app but anytime i get an email, i have to manually fetch to be able to see them. All other notifications such as facebook and twitter fetch automatically and on sync time-wise. Does anyone know why i would be having this problem with mail?

From the Mail menu bar, select
Mail ▹ Preferences ▹ Accounts ▹ Advanced
and check the box marked
Include when automatically checking for new messages
Repeat for each account.

HR - Daily Snapshot Issues with Future Dated Changes

The w_employee_daily_snp_f_1 table has timing issues. The effective end date on all per_all_assignments_f, per_all_people_f, etc always shows the time at midnight. For example: 08/14/2009 12:00:00 AM. When this person has a new assignment, for one day only, the extract does not pick up this person. See example below:
Employee 123 has a supervisor change and the new supervisor is effective on 6/15/2009
Emp Eff Start Date Eff End Date Supervisor
123 01/01/2009 12:00:00 AM 06/14/2009 12:00:00 AM 888
123 06/15/2009 12:00:00 AM 12/31/4712 12:00:00 AM 555
When the ETL runs on the night of 6/14/09 at 7:35:42 PM, this record does not get picked up because according to the apps.per_all_assignments_f table on the day of 6/14/09 this person does not have an active assignment. There is one day when the person (according to the system) does not have a supervisor. The next night, on 6/15/09 10:34:18 PM the record reappears and does so every night until the assignment record is again end dated. This only occurs for future dated HR changes.
This is a big problem because if the future dated change is for a supervisor, not only does the supervisor not appear in the daily snapshot, but either does any of his/her subordinates. Has anyone else run into this problem? How did you solve it? Did you customize all the HR mappings?

Have posted an updated version of the MST to my webspace here:
http://homepage.ntlworld.com/minkus/shockwave/shockwave115606mst2.zip
This new version fixes the following issues (changes to this version in bold):
MsiInstaller repair & errors on first run as non-admin (removes 'AppData' directory entries)
DCOM errors once Shockwave is installed (adds double quotes to the beginnning of LocalServer32 value)
Incorrect TypeLib paths in the registry (fixed to use built-in [SystemFolder] property)
Default CLSID description value missing (set to 'Shockwave ActiveX Control', as per the executable installer)
Incorrect Shockwave 10 paths in the registry (fixed to use built-in [SystemFolder] property)
Misspelt 'OptionalComponets' registry key (renamed to 'OptionalComponents')
Missing .dcr, .dir, .dxr Content Type registry values (included in the executable installer)
Fixed incorrect AppID registry key (set to use installer's [VERSION] variable)
Removed 'Launch SWDNLD.exe' shortcut created in Programs subfolder (people don't want this - see here)
I have tested this on my network and it all seems to work fine. Unfortunately my original plan to use the executable installer didn't work out as it does not include the Shockwave 10 compatibility components described here and here, so it looks like I'll have to keep this MST file up to date with the latest versions until Adobe fix the problems themselves...
If you want to see the changes that I have made, load up Adobe's 11.5.6.606 MSI file in Orca, then use Transform / Apply Transform to apply the MST, and look for the entries in green.
Please post any feedback to this thread, and I will try to respond if I can help!
Chris Hill

Fetch PERNR with Future BEGDA

Similar Messages

Maybe you are looking for