Skip to Content
author's profile photo Former Member
Former Member

How to use ldb PNPCE with FM u0091HR_INFOTYPE_OPERATIONu0092

Hi all,

I’m creating a report with LDB PNPCE, this report has to create/modify infotypes of an ID person. I’m trying to use de FM ‘HR_INFOTYPE_OPERATION’, but it’s not working… A DUMP is generated, with this description:

An exception that could not be caught occurred.CX_HRPA_VIOLATED_PRECONDITION

I think that the problem is due to logical database PNPCE, because if I use PNP, it’s working… Does anybody know anything about using the FM ‘HR_INFOTYPE_OPERATION’ with the LDB PNPCE?

Thanks!!

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Jan 08, 2008 at 01:38 PM

    It might be due to the way your passing values to the function call.. HR_INFOTYPE_OPERATION as such has nothing to do with the LDB.. PNP/PNPCE is of no relevance.. PL paste your code..

    ~Suresh

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 08, 2008 at 01:52 PM

    This piece of code it's working with ldb PNP

    CALL FUNCTION 'ENQUEUE_EPPRELE'

    EXPORTING

    • MODE_PREL = 'E'

    • MANDT = SY-MANDT

    pernr = wa_p9961-pernr

    infty = '9961'

    • SUBTY =

    • OBJPS =

    • SPRPS =

    endda = wa_p9961-endda "'99991231'

    begda = wa_p9961-begda "'20071201'

    • SEQNR =

    • X_PERNR = ' '

    • X_INFTY = ' '

    • X_SUBTY = ' '

    • X_OBJPS = ' '

    • X_SPRPS = ' '

    • X_ENDDA = ' '

    • X_BEGDA = ' '

    • X_SEQNR = ' '

    • _SCOPE = '2'

    • _WAIT = ' '

    • _COLLECT = ' '

    EXCEPTIONS

    foreign_lock = 1

    system_failure = 2

    OTHERS = 3

    .

    CALL FUNCTION 'HR_INFOTYPE_OPERATION'

    EXPORTING

    infty = '9961'

    number = wa_p9961-pernr

    subtype = wa_p9961-subty

    • OBJECTID =

    • lockindicator = 'X'

    validityend = wa_p9961-endda

    validitybegin = wa_p9961-begda

    • recordnumber = lwa_pa9961-seqnr

    record = wa_p9961

    operation = 'INS'

    tclas = 'A'

    dialog_mode = '0'

    • nocommit = ' '

    • VIEW_IDENTIFIER =

    • SECONDARY_RECORD =

    IMPORTING

    return = l_return

    • KEY =

    .

    CALL FUNCTION 'DEQUEUE_EPPRELE'

    EXPORTING

    • MODE_PREL = 'E'

    • MANDT = SY-MANDT

    pernr = wa_p9961-pernr

    infty = '9961'

    • SUBTY =

    • OBJPS =

    • SPRPS =

    endda = wa_p9961-endda "'99991231'

    begda = wa_p9961-begda "'20071201'

    • SEQNR =

    • X_PERNR = ' '

    • X_INFTY = ' '

    • X_SUBTY = ' '

    • X_OBJPS = ' '

    • X_SPRPS = ' '

    • X_ENDDA = ' '

    • X_BEGDA = ' '

    • X_SEQNR = ' '

    • _SCOPE = '3'

    • _SYNCHRON = ' '

    • _COLLECT = ' '

    .

    But if I use ldb PNPCE instead PNP, with the events:

    GET person.

    GET group.

    GET peras.

    ths dump is generated...

    Thank u!!

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Marta,

      In our system we haven't implemented CE, so i am not able to debug/test since i m not getting the dump :).

      Try to debug and check why the context has set twice (are you using any other FM or Class methods before calling HR_INFOTYPE_OPERATION whcih is setting the context ?) , also i noticed you are updating custom infotype '9961', check whether same dump is coming when you update for standard infotype's ?

      Regards,

      Shrinivas

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.