Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Assign Enhancement to infotype 0379

Former Member
0 Kudos

Hello,

I need to add some new fields on the 'Additional Data' tab, which is subscreen 2020, for PA0379. I have followed the steps in the previous post, but the additional fields subscreen shows up for all the tabs. It is appreciated if someone can shad some light on what I have done wrong below.

1. Use PM01 and choose enhance IT to add new fields in CI include

2. Enter '2070' in include screen and click on create all

3. click on Assign enhancement then I see the following:

   MP037900 2000 ZP037900 2060

   MP037900 2010 ZP037900 2060

   MP037900 2020 ZP037900 2060

   MP037900 2030 ZP037900 2060

   MP037900 2040 ZP037900 2060

   MMP037900 2050 ZP037900 2060

   MP037900 2060 ZP037900 2060

   MP037900 3000 ZPP037900 2060

7 REPLIES 7

Former Member
0 Kudos

After adding the fields in ci_include then program ZP037900 and Screen 200 wiil automatically generated.

After click on assign enhancement then click on new entries.

Refer below screen shot.

0 Kudos

Hi,

Did the same way ...

If i deleted rest entries from table then additional fields not visible on subscreen...

and if i added the entry with screen number 2000 then additional fields subscreen shows up for all the tabs.

I want to show the additional fields only on third Tab subscreen not others...

0 Kudos

Hi,

You want new fields needs to be added in sub screen 2020. You need to add entry like previous post which is showed by me.

If you want your fields in third tab then u need to mention sub screen 2030 in place of 2020.

Then newly added fields will get in third tab only if you mention 2030 sub screen only.

0 Kudos

Additional fields at place 2 in below screen shot and for all tabs...my req is to add at place 1 in tab screen area....

0 Kudos

I checked every possibility to add field in place 1 which is mentioned by you. I think we need access for this requirement.

Actually the problem with this is generated screen 200 calling in 2000 screen only. For this refer below screen shot.

The

If this screen presented in 2030 then it will possible.

You need access key for this requirement.

former_member190103
Participant
0 Kudos

Hai Shilpi,

Parameters Explained

Here is a list of the fm's parameters and how they are used, obviously not all parameters will be used depending on what function you are performing i.e. insert, change, delet etc

infty - Infotype being updated

objectid - object id from infotype

number - Personnel number

validityend - validity end date

validitybegin - validity begin date

record - infotype record values to be updated, inserted etc (will be structure of infortyoe you are updating)

recordnumber - sequence nunber from infotype record you are updating

Operation - describes what operation is to be performed

COP = Copy

DEL = Delete

DIS = Display

EDQ = Lock/unlock

INS = Create

LIS9 = Delimit

MOD = Change

INSS = Create for Actions is not converted to Change

nocommit - commit yes('X') / no(' ')

dialog_mode - dialog mode or not, default is '0'  Example coding for MOD operation

Example coding for MOD operation

CONSTANTS: change TYPE pspar-actio VALUE 'MOD'.

      "This code is requred and locks the record ready for modification

      CALL FUNCTION 'HR_EMPLOYEE_ENQUEUE'

        EXPORTING

         number = p_pernr.

      "loop at p0071 into p_p0071.  "added to put code in context

      validitybegin = p_record-begda.

      validityend   = p_record-endda.

      p_record-endda = pn-begda - 1.

      CALL FUNCTION 'HR_INFOTYPE_OPERATION'

        EXPORTING

          infty         = '0071'

          subtype       = p_record-subty

          objectid      = P_record-objps

          number        = p_record-pernr     "employeenumber

          validityend   = validityend

          validitybegin = validitybegin

          record        = p_record

          recordnumber  = p_record-SEQNR

          operation     = change

          nocommit      = nocommit

          dialog_mode   = '0'

        IMPORTING

          return        = return_struct

          key           = personaldatakey

        EXCEPTIONS

          OTHERS        = 0.

       "endloop.

     "unlock record after modification

     CALL FUNCTION 'HR_EMPLOYEE_DEQUEUE'

       EXPORTING

        number = p_pernr.

Example coding for INS operation

CONSTANTS: insert TYPE pspar-actio VALUE 'INS'.

      "This code is requred and locks the record ready for modification

      CALL FUNCTION 'HR_EMPLOYEE_ENQUEUE'

        EXPORTING

         number = p_pernr.

 

      validitybegin = p_record-begda.

      validityend   = p_record-endda.

      p_record-pernr = p_pernr

      p_record-begda =  pn-begda.

      p_record-endda =  validityend.

      p_record-subty = p_SUBTY.  "subtype of new entry

      p_record-SCREF = p_SUBTY.  "subtype of new entry

      "plus populate any other fields you need to update

      CALL FUNCTION 'HR_INFOTYPE_OPERATION'

        EXPORTING

          infty         = '0071'

          subtype       = p_record-subty

          number        = p_record-pernr     "employeenumber

          validityend   = validityend

          validitybegin = validitybegin

          record        = p_record

          operation     = insert

          nocommit      = nocommit

          dialog_mode   = '0'

        IMPORTING

          return        = return_struct

          key           = personaldatakey

        EXCEPTIONS

          OTHERS        = 0.

     "unlock record after modification

     CALL FUNCTION 'HR_EMPLOYEE_DEQUEUE'

       EXPORTING

        number = p_pernr

INS operation example coding for infotype 0105

Also see BAPI_EMPLCOMM_CREATE for updating infotype 0105

  CALL FUNCTION 'HR_EMPLOYEE_ENQUEUE'

  EXPORTING

  number = p_pernr.

  p_record-subty = p_subtype. "subtype of new entry

  p_record-pernr = p_pernr.

  p_record-SEQNR = '000'.

  validityend = '99991231'.

  validitybegin = sy-datum.

  p_record-begda = sy-datum.

  p_record-endda = '99991231'.

  p_record-usrid = 'TESTUSR'.

  CALL FUNCTION 'HR_INFOTYPE_OPERATION'

  EXPORTING

  infty = '0105'

  subtype = p_record-subty

  objectid = P_record-objps

  number = p_record-pernr "employeenumber

  validityend = validityend

  validitybegin = validitybegin

  record = p_record

  operation = 'INS'

  nocommit = nocommit

  dialog_mode = '0'

  IMPORTING

  return = return_struct

  key = personaldatakey

  EXCEPTIONS

  OTHERS = 0.

  if sy-subrc eq 0.

* success

  endif.

  CALL FUNCTION 'HR_EMPLOYEE_DEQUEUE'

  EXPORTING

  number = p_pernr.

Cheers,

Sravan

0 Kudos

Hi Sravan,

For what purpose it is?