Interface from S3 to LTM to GHR

This is an interesting question. Why are you creating the position in S3 rather than in TM? Generally, TM is the system of record for Jobs, Positions, Supervisors, and Employees and the LTMS3_xxxxxx Pflows interface them to S3. I'd think interfacing from S3 to LTM would be troublesome in the long term (i.e. after initial load)

To answer your question, I strongly suggest you NOT update the POSITION table directly. The import program does lots of error checking to be sure all the prerequisites exist. For one thing, generally the JOB record has to exist first as do HROrganization, HROrganizationUnit, Location, Pay Grade, Pay Schedule, etc. I'd be very concerned to do a direct update.

We used POSITIONIMPORT to do our initial TM data load. I haven't used POSITIONIMPORTLITE, but this may be your only option if you already have the PositionID created in S3 - unless you are going to map the TM position to the S3 position.

POSITIONIMPORTLITE:
- Go to Data Menu>>GenericInterface>>Business Classes>>PositionImportLite
- Add or confirm records exist
- Select a record and do Action>>Create or Action>>Update
- OR do Action>>Process All Positions (this will prompt you for a batch number to process)

POSITIONIMPORT:
- Go To Data Menu>>hr>>Business Classes>>PositionImport)
- Add or confirm records exist
- Select a record and do Action>>Create
- OR do Action>>Create All Positions (this will prompt you for a batch number to process)

I hope this is helpful.

Kelly

Now that I think about it, I suppose if you are using S3 as your system of record, you'd need to do this. My guess is that the two flows are there because new records have to be created with POSITIONIMPORT and existing records need to be updated with POSITIONIMPORTLITE. That is just a guess, but since the POSITIONIMPORT table doesn't include PositionID that's all I can figure.

Interestingly, I don't find the flow that uses "POSITIONIMPORT" on our system - what is the flow name that updates this table? I think POSITIONIMPORT is really intended to be used for data conversion and initial load of new positions into TM in batch.

Anyway...good luck!

Kelly

We are reversing that.  We are using GHR and LTM but our system of record is S3.  That’s why I’m a little confused as to how to get the new position into the position table.  

While I continue to find the solution I will heed your advice about updating the Position table directly.

Thank you.
Dave.

I believe you're correct. I think the POSITIONIMPORT is intended to be used for data conversion and initial load.

I have two flows.  POSITIONIMPORT and POSITIONIMPORTLITE.  Neither are touching the POSITION table so there must be something I'm missing.

Thank you.
Dave.

Huh. What version of TM are you running? On our systems (v3.4.2 and v10.x) the only flow I see is HRMPositionImport, which populates the TM POSITIONIMPORTLITE table from the S3 HRLTMPOS table. Is there a chance someone modified the delivered flow and/or added a new custom flow?

They wouldn't touch the Position table - the idea is to load the data into the staging tables, and then run the add/update process from the staging table. That load process can be manually triggered from the table, as I mentioned, or it can be set up as a scheduled job. In any case, there are two steps - loading the staging table, and then running the update process.

We are on v10.x.  The flow is called HRMPositionImport which populates the TM POSITIONIMPORTLITE table from the S3 HRLTMPOS table just as you said.

Can you tell me a little about the add/update process you run from the staging table?  What’s it called?

 
Thank you.
Dave.

For POSITIONIMPORTLITE:
- Go to Data Menu>>GenericInterface>>Business Classes>>PositionImportLite
- Add or confirm records exist
- Select a record and do Action>>Create or Action>>Update (this will process a single record)
- OR do Action>>Process All Positions (this will prompt you for a batch number to process)

That's the part I was missing.  Thank you very much!

Dave Lis