Contents
Contents .......................................................................................................................................... 1
Outgoing messages From People Soft to TCD Server................................................................... 2
Message Monitor ........................................................................................................................ 4
Incoming Messages From TCD Server to People soft Server: ....................................................... 5
Configure Appserver for Publish and Subscribe. .......................................................................... 6
Node Definition : ............................................................................................................................ 6
Local Node.................................................................................................................................. 6
External Node, TCD Servers ...................................................................................................... 7
Transactions ................................................................................................................................ 8
Gateway for People soft system:................................................................................................. 9
Publish Rules ................................................................................................................................ 10
Batch Publish ............................................................................................................................ 10
Inbound File .............................................................................................................................. 12
Inbound File Publish ................................................................................................................. 13
Trouble Shooting .......................................................................................................................... 14
Frequently asked questions ........................................................................................................... 17
1
Url for Psoft pages:
Userid and Password :
Navigation mentioned as xxxx Æ xxxÆ xxx Æ
Messages and Subscription Pcode are delivered Inactive. Make sure they are activated using Application
Designer.
Message Channels are delivered Pause. Make sure they are changed to Run in Message Monitor Page.
Outgoing messages From People Soft to TCD Server
Messages
Channel
2
Setup objects of Interest
Setup HRMS --> Product Related --> Time and Labor
1. Configure Task--> Where Taskgroup/Taskprofile are defined. Don’t Forget to check on Send
to TCD on Task profile page
2. Time Reporting Æ Trc Programs and TRC’s. Don’t Forget to check on Send to TCD on TRC
page
3. Time Collection Device: Page where the TCD Environment can be configured, like defining
what Messages should be sent, TCDattributes, TCD Grouping, etc.,. Send Set up to TCD
Initiate the
4. Process to publish to TCD Servers on run control page publish can be initiated to all the
nodes or by selecting the Specific node of yours
5. Enroll Time Reporter Data: Where TCD Group can be assigned to Time Reporters.
3
Message Monitor
People Tools --> Integration Broker --> Monitor Messages
Page will show the messages published FROM People soft or to People soft with other details
Overview: Page gives an overview of how many messages were published from Psoft or to Psoft
Message Instance: Page gives info about what Messages are published (to and From People soft) with
Time etc.,
Pub Contract: Page gives info about Messages Published from People soft Local node (PSFT_HR) to
other People soft node or to External node specifying the Local node, message name, published to which
message with date time stamp and Status and a link to Detail of message. If you click on the detail of
message you can have further details.
Sub Contract: Messages, which are published, to People soft node will be listed here.
Channel Status: List the entire channels that are in people soft system. Make sure Channel status is
running. If they are not click on Run Push button, Run Push button and Pause are mutually exclusive.
Æ For all out bound messages
(Time_Device_XXXX) from People soft to external node.
Æ For Incoming message of Elapsed and Punch
time message.
If click Details link on Pub contract and Sub Contract, will open a browser where further details can be
found out. Message Properties has Resubmit button, which can be chosen in case of any Errors.
Message Error will give what is the error. XML Schema Viewer will show XML Schema.
4
Incoming Messages From TCD Server to People soft Server:
Messages
Channel
Incoming messages will trigger TL_ST_LOADER Appengine Process, which will insert rows into
Reported Tables. TL_ST_LOADER will also kick of Validation process for the validations set defined on
TL Installation page.
Check the incoming messages in the Message monitor For Elapased_time and Punched time
TCD Error Queue
Setup HRMS Æ System Administrator Æ Analyze Time and Labor Æ Review TCD Errors
Check any errors for the Publishing Node you are using.
If no errors found for the node then you can see the time in reporting pages
Manager Self service Æ Time Management Æ Record Time Æ Report Time
Will display the list of Employees find the Employee using Find feature on the Grid. Select Weekly
Elapsed for Elapsed Message or Weekly Punch for Punch Page from the top of the page and then click
on Name, which will open with current date as start of the week. You can change the Week begin date
and hit Refresh Date.
5
Configure Asperser for Publish and Subscribe.
Make sure asperser is configured for pub/sub. See Appserver configuration for more details.
Node Definition :
People Tools --> Integration Broker --> Node Definition
Local Node
Couple of important settings
Node info Page: For you local node makes sure you have following setting
Connectors Page: Local node always uses PSFTTARGET for 8.4x tool set
Other very important Transactions are
If using flat file architecture make sure that Time_DEVICE_XXXX messages have both out sync and in
sync specified and ACTIVE. Flat file are generated by local Node for each Flat File TCD Server. Location
of Out put is defined on TL Installation Page /TL General Settings Page.
6
External Node, TCD Servers
Node info Page: For you TCD node make sure you have following setting. TCD Nodes are required only
for XML Messaging.
Connectors Page: Local node always uses PSF81TARGET from 8.4x tool set to a TCD Server which are
still using 8.1x type or XML Messaging. Don’t forget to specify target URL that is TCD Server Gateway
Typically if using IIS Web server it will end with [Link]. TCD Vendor should have the details
For Kronos it is typically like: [Link] where 000 is IP Address
For Time Link it is typically like: [Link] where xxxxx is their server address
might be like //server
For Kaba Benzing typically like [Link]
Connectors Page: Local node always uses HTTPTARGET from 8.4x tool set to a TCD Server which l
using 8.4x type or XML Messaging. Don’t forget to specify the Properties as listed below
Ping Node
7
On Message monitor Æ Node status page. Ping Local node and also the External node by selecting
Nodes.
Transactions
Don’t forget to specify the outbound transactions and inbound transactions. Routing type should be
Implicit.
8
Gateway for People soft system:
People Tools --> Integration Broker --> Gateway Definitions
A typical Gateway for People soft. Refer to people books for more information
Gateway: [Link]
Gateway to be specified by the External Nodes on their system
Gateway URL for 8.4 External to 8.8 HRMS: [Link]
Gateway URL for 8.1/8.3 External to 8.8 HRMS:
[Link]
9
Publish Rules
Batch Publish
Enterprise Components Æ Integration Definition Æ Batch Publish Rules
Activate the Batch Publish rules
TL_OUTTCD App engine process uses Batch Publish rules to publish the messages to TCD Servers.
Activate the rules, which you will be used for TCD Interface.
TL_OUTTCD appengine triggers Messages to be published
Note: Don’t change any of the setting other than to make active if you using delivered process.
10
11
Inbound File
Activate the Inbound File rules
Enterprise Components Æ Integration Definition Æ Inbound File Rules
Activate inbound file rule if using Flat file integration. If using XML Integration there is no need to
Inbound File: Change the location to location of flat files. The name of the file should be still
ELAPSED_TIME*.csv. Change only c:\temp to the appropriate location.
Location: c:\temp\ELAPSED_TIME*.csv
Status = Active
No need to change other fields.
12
Inbound File Publish
If using Flat File Integration. Process to Read the Flat file is initiated from this component.
Enterprise Components Æ Integration Definition Æ Initiate Process Æ Inbound File Publish
Make Sure there is Request ID populated.
Process Frequency: Should be either Once or Always. Use Once if running the process with Run control
ID only once. Other wise Use Always if using same Run control Id repeatedly.
Once the file is processed, the file will be archived and placed in the location specified on TL Installation
page
13
Trouble Shooting
1. Outgoing Messages from People soft to TCD Server: TL_OUTTCD is successful: No
messages generated
Check If messages are active in Application designer
Check If Channels are in Run Mode in Message Monitor
Check If Transactions are specified on the External Nodes
Check If Batch Publish is activated
Check If Node and Transactions Routing Type is specified as Explicit instead of Implicit
2. In Coming messages from TCD Server to Psoft Server
Receiving an error “<?xml version="1.0"
?><reply><operations><exception><title>Publish Subscribe Message
Exception</title><defaultmsg>[Link]:
</defaultmsg><msgset>94</msgset><msgid>1</msgid><parameters
count="1"><parm>[Link]:
</parm></parameters></exception></operations></reply> <?xml version="1.0"
?><reply><operations><exception><title>Publish Subscribe Message
Exception</title><defaultmsg>[Link]:
</defaultmsg><msgset>94</msgset><msgid>1</msgid><parameters
count="1"><parm>[Link]:
</parm></parameters></exception></operations></reply>”
This mean Transaction is not specified for that TCD Server node
3. 8.1 and 8.3 are working but once upgraded to 8.8 Nothing is working
Make sure Nodes are defined
Make sure Transactions are specified on External Nodes for XML
Make sure Transactions are specified on Local node for in async and out async if using Flat
file integration
Make sure TCD Server should upgraded to use 8.4 too set Xml messaging else Change the
connector Id as discussed above in Node configuration
4. Ping does not work from People Soft Server to TCD server
Make sure using appropriate target connector as discussed in Node configuration
5. To Purge the message details
DELETE FROM PSAPMSGPUBHDR;
DELETE FROM PSAPMSGPUBDATA;
DELETE FROM PSAPMSGPUBCON;
DELETE FROM PSAPMSGSUBCON;
DELETE FROM PSAPMSGPUBCERR;
DELETE FROM PSAPMSGPUBERR;
DELETE FROM PSAPMSGSUBCERR;
DELETE FROM PSAPMSGPUBCERRP;
DELETE FROM PSAPMSGPUBERRP;
DELETE FROM PSAPMSGSUBCERRP;
DELETE FROM PSAPMSGARCHPC;
DELETE FROM PSAPMSGARCHPD;
DELETE FROM PSAPMSGARCHPH;
DELETE FROM PSAPMSGARCHSC;
14
6. Flat file not created for out bound messages, but messages generated in message monitor
Makes sure Outbound/Inbound transaction is specified on Local node
Make sure Subscription people code is active on all the Messages. Which can be done in
App designer by right click on subscription pcode
Make sure you are looking at the appropriate location, which is specified on TL Installation
page(TL General setting)
Make sure TL_OUTTCD has not given any errors in Process monitor
Make sure your Appserver and process scheduler has read and write access to the file
location.
7. Flat file is not empty after inbound file publish process is run
Make sure File location is properly specified on Inbound file rule
Make sure inbound file rule is active
Make sure Inbound file Process run control has Process Frequency = Always or Once as
needed.
Make sure you are following comma delimiter for each column
Make sure Inbound file rule is active
Make sure the file name is ELPASED_TIME*.CSV or PUNCHED_TIME*.CSV
8. Messages transaction are not same as in Flat file
Make sure each row in flat file has carriage return in the sense each transaction should be a
new line in simple sense each line by hitting your return/key.
15
9.0 Large message
When Message size exceeds than specified on People Tools options pages. Message is split into multiple
messages. For Full sync there would be one header followed by multiple Data messages and then one
Trailer. In the example shown below 3687 is header followed by Data 3688/3689/3690/3691 and then
finally trailer 3692.
10.0 Receiving Header and Footer only
Messages are active but probably TCD Type set up is not appropriate, or no data to publish Task
elements and or time reporting elements or schedules …
11.0 Differences between 8sp/8.3 Vs 8.8.
8sp1 and 8.3 application are on tools 8.1x
8.8 Application is on 8.4x tool set
12.0 Message log and Error log can be found in
Msg Log : [Link]
Error Log : [Link]
16
Frequently asked questions
What parser can be used : MSXML parser/Microsoft's XML DOM
User Id and Password: Userid/Passwords can be enforced if the external can enforce.
Response to the ping from TCD Server
<?xml version="1.0" ?>
<reply>
<operations namespace="External Gateway Servlet"
interface
="[Link]
onGatewayHandler">
<invoke opnum="1" member="invokeHandler">
<return type="number">0</return>
</invoke>
</operations>
</reply>
When you ping the Psoft Node you got a response back with a return code of
0 (Zero), that indicates the ping is successful.
Page 8 of Integration doc for 8.1x tools /8.3 explains the return code. I
believe Psoft will respond back to your gateway defined in our system
Please let us know if you need more clarification.
Do all the downloads have the TCD ID? For example there are 50 terminals
(Time Collection Device IDs) and if an employee is valid for all 50 TCDs,
will there be 50 records sent for the same employee? The TCD ID seems to be
in every type of transaction, does that mean all data is pertinent for only
that TCD ID? If all data is valid for all TCDs, does that mean we have 50
times the data we would have in the scenario that has 50 TCDs in the system?
Even the total hours for an employee seem to be for each TCD, although they
should be the same no matter which TCD they are displayed on.
Ans: Yes, each TCD will get employee population and other information.
The documentation indicates that the compression (using the deflate
algorithm) and base64 encoding should be done only for the data section.
There are some uncompressed ASCII examples in the documentation. I am
assuming those are only for illustration purposes and that it is mandatory
to base64 encode and compress the data section (and conversely uncompress
and decode when we receive it). Regarding the header and trailer messages,
when we POST to Peoplesoft you mentioned that we do not need to send the
header since it is considered incremental. Do we need to send a trailer? Is
the trailer message same as the header except for msg_seq_flg is set to T
instead of H? Since there can be multiple transactions in the message, it
can get to be fairly big (especially if communication was down for some
reason). Is there a size limit on the XML file that we can send?
Ans: Yes, Compression is mandatory. No need to send header and trailer while posting to PeopleSoft.
Yes the only difference between header and trailer is H and T. There is no size limit. Size of message is
configurable on people soft side, if the size is more people soft will break into multiple messages.
17
Example Full sync Empl_Full_SYNC from people soft, if a message size exceeded than the specified,
message is broken in to multiple messages in these scenario the TCD server will receive header followed
by multiple data messages and then a trailer.
What is the Operator ID (char 8) in the Punched and Elapsed transactions?
How to validate this information?
Ans : Oprid : can be left blank or it is up to implementation site if they want to populate with the Id of the
person who is punching.
Why is the Supervisor ID 20 characters in the Punch and Elapsed
Transactions even though it is only 11 characters when loaded into the
system? Is this a different field?
Ans: I am pretty sure Supervisor Id is 20 characters in all the messages. Could you please point me to the
message, which has length of 11?
What is the meaning of [+/-hhmm] in the date time format mentioned in
Appendix F. is this the offset from GMT? Is this an optional component? Are
All the date time fields provided in the local time of the time collection
device?
So if it is 4:10 pm local time in the Eastern Time Zone (which is GMT - 5
Right now), when a punch occurred on 2/4/02, will the date time be
2002-02-04T16:10:00.000000-0500 ? Can we leave out the -0500 at the end?
Ans : Yes it is needed and should take care day light saving also here is an example of the format from
Process mode doc: The date time format for XML is CCYY-MM-DDTHH:MM:[Link][+/-hhmm]. For
example, 1999-09-14T16:47:56.793000-0700.
How do we validate (or is there no validation) for the Billable Indicator
and Pay Rate Override fields on the Elapsed transaction?
Ans: No Validation is necessary, Please refer to 8.0TL_TCD_Vendor_Interface_PMD.doc page 49 and
also 51.
I don't seem to have the format headers files for the
TASK_PROFILE_FULLSYNC and EMPL_ATT_SYNC (incremental) transactions. Can you
Send them to me?
Ans: Empl Att sync will not have header and trailer as it is considered as incremental message, this is the
only message which is incremental TCD's receive all other messages are Full Synch which will have
header, data and trailer.
Time Collection Device Groups are mentioned in some places in the
Documentation. Do we get these groups in any transaction or are these
Internal to Peoplesoft?
Ands : TCD Groups is a group of TCD's internal to People soft.
10) In the Elapsed Interface, there is a Date Under Report field. Is this?
The same as the date of the punch?
Ans: Date under report is date of Punch with no time
Regarding enforcing the schedules: The way I understand the data, there
Is a timestamp (punch date and time) for each punch type for each employee?
18
There is also a sequence number but the comment says that it is used only
when the schedule spans multiple days. For the following scenario, how would
we enforce the schedule with a restriction profile of say 10 minutes early
and 10 minutes late for each type of punch?
Let us say the schedule for an employee is:
Punch Type Punch DateTime
I 8 am
B 10 am
M 1 pm
T 3 pm (Not sure how we enforce a schedule for transfer
since there is no restriction profile)
O 5 pm
Let us say the employee has the following punches:
I 8 am
B 10 am
I 10:30 am (Back In from the break)
M 1 pm
I 2 pm (Back In from the meal)
T 3 pm (No restriction profile values, so how to
validate this?)
O 5 pm
How do we validate the Back In from break (since schedule does not tell us
how long the break is supposed to be)?
How do we validate the Back In from meal (since schedule does not tell us
how long the meal is supposed to be)?
If there is no validation for the above mentioned cases, do we keep track of
the last transaction for the employee and enforce the validation for In only
if it is after a previous Out?
Ans : Restriction profiles : I think customers should have their schedules with punches in the format of
how each user punches. In your example Break in 10:30 which is missing in schedules, I expect
Schedules should have the Punch other wise Supervisor Id will work for any punch. If customers want to
live with supervisor Id we should be OK, if they don't want supervisor over rides then their schedule
should be similar to their punching pattern. In general if there is no restriction profile for a punch then we
should let it go as the user might not want to validate a punch back to your example we might let it go. I
don't know how much flexible your server is.
19