cancel
Showing results for 
Search instead for 
Did you mean: 

Would I use Dynamic Actions for this?

Former Member
0 Kudos

As part of my hiring action, I would like to trigger an email to the Org's chief once the employee record is created. Is this done via Dynamic Actions? If so, can someone give me a step-by-step on how to set that up?

Thanks!

Accepted Solutions (0)

Answers (3)

Answers (3)

JohnWick
Active Participant
0 Kudos

Hi you can use code like this in table T588Z

Infotype

|0000 | | |06|101|P|P0000-MASSN='E9'| check Action Type

|0000 | | |06|102|P|P0000-MASSG='02'| check Reason for Action

|0000 | | |06|103|P|PSPAR-PERSG='4' | check Employee group

|0000 | | |06|104|W|PSPAR-PERSG='6' | check employee subgroup

|0000 | | |04|105|M|M0001 | call a feature

With this feature M0001 I think you can make it

M0001 Parameter Settings for Mail on Change to Infotype Record

Object

Feature

Task

This feature enables you to control who is sent a mail, the text sent,

and the processing type used.

Use

The feature can be used for all master data infotypes for both employees

and applicants.

Note

Decision field TCLAS enables you to control whether processing is

carried out only for employees (TCLAS=A) or only for applicants

(TCLAS=B).

Procedure

The return matrix of the feature has the following form: XXXXX ZZZZZ

XXXXX Mail attribute

o IDTXT - Name of a standard text. The first line is used as a title,

therefore you should formulate the mail after the second

line

of the standard text. The above variable is entered. You can

only activate the infotype fields that trigger a mail.

o RECV1 - Recipient 1 is the administrator for HR master data from the

Organizational Assignment infotype (0001) who is responsible

for the employee on today's date.

For applicants this is the personnel officer.

The user name contained in T526 is converted into an office

name. This conversion takes place for RECV2 and RECV3.

o RECV2 - Recipient 2 is the payroll administrator taken from

the Organizational Assignment infotype (0001) who is

responsible for the employee on today's date.

This field is not supported for applicants.

o RECV3 - Recipient 3 is for the Time Management administrator taken

from the Organizational Assignment infotype (0001) who is

responsible for the employee on today's date.

This field is not supported for applicants.

o SUBTY - You want the employee whose data is changed to receive an

e-mail

Here you specify which subtype is to be used to read the

employee's infotype 0105 record, that is, in which subtype

you

store the employee's mail name. The employee only

receives a mail if SUBTY is filled.

o OUTBX - The mail should be in the sender's outbox.

o DISTR - Distribution list that is stored in the general folders

in SAP-Office (Transaction SO04).

o NAME1 - If the infotype that triggers the mail is not the

Organizational Assignment infotype (0001), then the feature

specified is read.

You can define distribution lists and recipients in

this feature. The standard SAP system contains the

feature RCIEV, which can be used as an example.

o NAME2 - If the infotype that triggers the mail is the

Organizational Assignment infotype (0001),

then the feature specified will be read

using the new data contained in infotype 0001. New data

means data contained in an infotype record for infotype

0001 that has been changed after the mail was sent. You

can define a distribution list and a recipient in this

feature.

The standard SAP system contains the feature RCNEW,

which can be used as an example.

o NAME3 - If the infotype that triggers the mail is the

Organizational Assignment infotype (0001),

then the feature specified here, will be

read using the old data contained in the infotype. Old

data means data prior to changing the infotype record that

triggered a mail to be sent. You can define distribution

lists and recipients in the feature. The standard SAP

system contains feature RCOLD, which can be used as an

example.

You can give a mail a process. The recipient of the mail can start the

transaction specified from the mail:

o TCODE - Transaction code

o PAINF - Infotype

o PASUB - Subtype

o PABEG - Begin date

o PAEND - End date

o PAFCD - Function code (OKcode)

ZZZZZ 30-character value that is entered in the field.

o XXXXX = IDTXT: ZZZZZ is a standard text from SAPScript with the text

ID PAMA (Transaction SO10)

o XXXXX = RECV1, RECV2, RECV3: ZZZZZ=X is the appropriate

administrator who is to receive the mail

o XXXXX = SUBTY: ZZZZZ is 4-digit subtype for the infotype 0105

o XXXXX = OUTBX: ZZZZZ=X the mail is put in the sender's outbox

o XXXXX = TCODE: ZZZZZ=PA30, PA20, PB30 or PB20

o XXXXX = PAINF: ZZZZZ is the 4-digit number of an infotype

o XXXXX = PASUB: ZZZZZ is the 4-digit number of a subtype

o XXXXX = PABEG, PAEND: ZZZZZ= either an 8-digit date in the format

YYYYMMDD, e.g. ZZZZZ=19950630 for "30.06.1995", or enter the name of

a variable in inverted commas, e.g. ZZZZZ='P0001-ENDDA'. The

following exist: P0001-BEGDA, P0001-ENDDA, P0002-BEGDA, P0002-ENDDA,

Pnnnn-BEGDA, Pnnnn-ENDDA, nnnn is the number of the infotype that

triggers the mail to be sent.

o XXXXX = PAFCD: ZZZZZ=COP Copy, ZZZZZ=DEL Delete, ZZZZZ=DIS

Display, ZZZZZ=EDQ Lock/Unlock, ZZZZZ=INS Create, ZZZZZ=MOD Change

By using the operation NEXTR, you will jump into the feature's

subsequent line. The last line of an action is closed with commas (not

NEXTR).

Former Member
0 Kudos

HI alli,

This is related to Workflow , so , try to look into workflow concepts then you will come to know the solution.

Regards,

Narendra.

Former Member
0 Kudos

Hai...

pls check the std actions which already exists in T588Z table... kindly go through the doc.. if u stil face any issues.. pls post here