Infotype Z in the portal ESS

Question

Good Nigth.
I have the following issue.
In the company in where i am, there is very much Infotype Z created and enhancement to Infotype Standard. They want that some of this infotype and Some fields that were add in the infotype standard can be update through of the portal.
Someone can help me , that I should do.?
Kind Regards.

Answer 1

Hi,
As per your Query ...
It can be possible ..
For if you are all ready displaying the fields on the portal .. then following solution will help you .
In back end you need to create RFC by using T-code se37.
For example I want to update some fields in Info type  from Z info type.
My Z info type is ( 9500 ) and other Standard info type is 0001 ( Org Assignment).
On the portal you are displaying fields from Z ( 9500 ) info type u2026
Then for updating data in the infotype 0001.
1.     Go to Tcode se37 .. Give RFC name u201C Z9500_CHANGEu201D in attribute give processing type Remote-enabled Module , give short text ect. In Importing Parameter give .
I_9500     TYPE     PA9500                               HR Master Record: Infotype 9500
Only give importing parameter donu2019t give others like exporting , changing ect.
And it source code give following coding.
FUNCTION Z9500_CHANGE.
""Local Interface:
*"  IMPORTING
*"     VALUE(I_9500) TYPE  PA9500 OPTIONAL
                         data definition                             *
  DATA: WA_9500  TYPE PA9500,
        WAP_9500 TYPE P9500,
        WA_0077  TYPE PA0077,
        WAP_0077 TYPE P0077,
        WA_RETURN TYPE BAPIRETURN1,
        WA_KEY TYPE BAPIPAKEY.
  DATA: V_USER TYPE SY-UNAME.
  CONSTANTS: C_9500 TYPE INFTY VALUE '9500',
            C_MOD TYPE ACTIO VALUE 'MOD'.
             C_MOD TYPE ACTIO VALUE 'INS'.
  MOVE-CORRESPONDING I_9500 TO WAP_9500.
  WAP_9500-INFTY = C_9500.
  WAP_9500-ENDDA = '99991231'.
  WAP_9500-BEGDA = SY-DATUM.
LOCK THE EMPLOYEE
  CALL FUNCTION 'HR_EMPLOYEE_ENQUEUE'
    EXPORTING
      NUMBER       = WAP_9500-PERNR
    IMPORTING
      RETURN       = WA_RETURN
      LOCKING_USER = V_USER.
  CHECK WA_RETURN IS INITIAL.
Update the dependednt infotype
  SELECT SINGLE *
     FROM PA0077
     INTO WA_0077
     WHERE PERNR =  I_9500-PERNR AND
                    ENDDA >= SY-DATUM AND
                    BEGDA <= SY-DATUM.
  MOVE-CORRESPONDING WA_0077 TO WAP_0077.
  WAP_0077-INFTY = '0077'.
  WAP_0077-ENDDA = '99991231'.
  WAP_0077-BEGDA = SY-DATUM.
  IF WAP_0077-RACKY NE I_9500-RACKY.
    MOVE I_9500-RACKY TO WAP_0077-RACKY.
    CALL FUNCTION 'HR_INFOTYPE_OPERATION'
      EXPORTING
        INFTY         = '0077'
        NUMBER        = WAP_9500-PERNR
        VALIDITYEND   = '99991231'
        VALIDITYBEGIN = SY-DATUM
        RECORD        = WAP_0077
        OPERATION     = C_MOD
        DIALOG_MODE   = '0'
      IMPORTING
        RETURN        = WA_RETURN
        KEY           = WA_KEY.
  ENDIF.
Update the Infotype
  CALL FUNCTION 'HR_INFOTYPE_OPERATION'
    EXPORTING
      INFTY         = C_9500
      NUMBER        = WAP_9500-PERNR
     VALIDITYEND   = WA_9500-ENDDA
     VALIDITYBEGIN = WA_9500-BEGDA
      VALIDITYEND   = '99991231'
      VALIDITYBEGIN = SY-DATUM
      RECORD        = WAP_9500
      OPERATION     = C_MOD
      DIALOG_MODE = '0'
    IMPORTING
      RETURN        = WA_RETURN
      KEY           = WA_KEY.
UNLOCK THE EMPLOYEE
  CALL FUNCTION 'HR_EMPLOYEE_DEQUEUE'
    EXPORTING
      NUMBER = WAP_9500-PERNR
    IMPORTING
      RETURN = WA_RETURN.
*e_return-message = 'Dequeued'.
ENDFUNCTION.
Here I shown the way how to update infotype from portal data u2026..Please do as per your requirement Logic will be same ..in your case table will otheres u2026if you do it  with the ABAP consultant its is just half hour work
Cheers,
Vivek