Lawson LPA and S3 Applications Reference Guide

LPA and S3 Applications Reference Guide
Version 10.0.0.x
Published November 2011
Document Number LPAAPPSRG-10000-UW-01
Legal Notices
This content is for instructional or informational purposes only. This content may be changed or superseded
without notice, and is not part of any Lawson product, maintenance or services warranty.
Export Notice: Pursuant to your agreement with Lawson, you are required (at your own expense) to comply
with all laws, rules, regulations, and lawful orders of any governmental body that apply to you and the
products, services or information provided to you by Lawson. This obligation includes, without limitation,
compliance with the U.S. Foreign Corrupt Practices Act and all other applicable corrupt practices legislation
(which prohibits certain payments to governmental officials and political parties), export control regulations,
and regulations of international boycotts. Without limiting the foregoing, you may not use, distribute or export
the products, services or information provided to you by Lawson except as permitted by your agreement
with Lawson and any applicable laws, rules, regulations or orders. Non-compliance with any such law, rule,
regulation or order shall constitute a material breach of your agreement with Lawson.
Intellectual Property: All brand or product names mentioned herein are trademarks or registered trademarks
of Lawson, or the respective trademark owners. This documentation is the proprietary information of Lawson
protected internationally under copyright and related intellectual property laws. Lawson customers or
authorized Lawson business partners may use, copy, or transmit this document for their internal use only.
Any other use or transmission requires advance written approval of Lawson.
Modifications to this Document: Lawson does not authorize changes to this document and does not
warrant or provide maintenance for any modification, alteration or addition made to this document.
© Copyright 2011 Lawson Software. All rights reserved.
Contents
Chapter 1 Overview 7
What is a process?................................................................................................7
What are S3 triggers and services?.......................................................................7
Chapter 2 Install LPA Services for S3 Enterprise Applications 8

Install LPA Services for S3 Enterprise Applications...............................................8
Chapter 3 Application triggers and services for Human Capital

Management 9
Human Resources (HR)...............................................................10
Goal Approval......................................................................................................10
Employee Delete..................................................................................................11
Personnel (PA)..............................................................................12
Job Requisition Approval.....................................................................................12
Personnel Action Approval...................................................................................14
Chapter 4 Application triggers and services for Enterprise

Financial Management 17
Asset Management (AM)..............................................................18
Asset Addition......................................................................................................18
Asset Adjustment.................................................................................................18
Asset Disposal.....................................................................................................19
Asset Transfer......................................................................................................19
EAM Asset Addition.............................................................................................20
General Ledger (GL).....................................................................21

Cost Allocation.....................................................................................................21
FlexBudgeting Version Add..................................................................................21
FlexBudgeting Add...............................................................................................22
GL Level Reorganization......................................................................................23
Journal Entry Approval.........................................................................................23
Delete Accounting Unit........................................................................................25
GL Company Delete............................................................................................25
Project and Activity Accounting (AC).........................................26

Activity Addition Approval.....................................................................................26
Activity Delete......................................................................................................26
Activity Status Change.........................................................................................27
Activity Budget Change Order Request...............................................................27
Activity Budget Change Order Release...............................................................28
Grant Activity Budget Alert...................................................................................29
LPA and S3 Applications Reference Guide Contents 3

Activity Contract Complete...................................................................................31
Billing and Revenue Management (BR)......................................32

Activity Contract Complete...................................................................................32
Activity Billed........................................................................................................32
Activity Revenue Recognized...............................................................................33
Grant Management (GM)..............................................................34

Labor Distribution Approval..................................................................................34
Labor Cost Transfer Template Approval...............................................................35
Effort Certification ...............................................................................................36
Effort Variance .....................................................................................................37
Accounts Payable (AP)................................................................38

Invoice Approval...................................................................................................38
AP Cost Transfers Approval for General Ledger Transactions.............................40
AP Cost Transfers Approval for Activity Transactions...........................................41
AP Cost Transfers Approval for Grant Activity Transactions.................................41
General Vendor Maintenance...............................................................................42
EAM Supplier Add................................................................................................43
Accounts Receivable (AR)...........................................................44

Customer Add or Credit Limit Change.................................................................44
Customer Review Selection.................................................................................45
Payment Received with Orders on Credit Hold....................................................46
Transaction Transfer.............................................................................................47
Transaction Grouping...........................................................................................48
Disputed Invoice...................................................................................................48
Return to Maker Payment....................................................................................49
Add Cust Desc.....................................................................................................50
Upd Cust Desc.....................................................................................................50
Upd Customer......................................................................................................51
Employee Expense (EE)...............................................................52

Employee Advance Approval...............................................................................52
Employee Expense Approval...............................................................................54
Chapter 5 Application Triggers and Services for Supply Chain

Management 56
Billing (BL)....................................................................................57
Electronic Payment Authorization or Settlement Failed.......................................57
BL Price Override.................................................................................................58
Invoice Batch Release.........................................................................................58
Inventory Control (IC)...................................................................60

Bin Update...........................................................................................................60
Item Location Update...........................................................................................60
Item Update.........................................................................................................61
General Item Location Maintenance....................................................................61
EAM Item Issued to Work Order..........................................................................62
EAM Item Location Update..................................................................................63
4 Contents LPA and S3 Applications Reference Guide

Invoice Matching (MA)..................................................................64
Inspection Required.............................................................................................64
Reconciliation Invoice Message...........................................................................65
Requisition Item Received...................................................................................65
Purchase Order Cost Message............................................................................66
Purchase Order Overshipment Message Exists..................................................67
No Receipts in Match Pool...................................................................................68
Disapprove Recon Message................................................................................69
Invoice No Receipt...............................................................................................70
EAM PO Release to Work Order / PO Line Close...............................................70
Order Entry (OE)...........................................................................72

Customer Order Hold...........................................................................................72
Customer Order Line Hold...................................................................................73
Customer Order Canceled...................................................................................74
Customer Order Credit Check Fail.......................................................................75
Customer Order Released...................................................................................75
Customer Order Return Created..........................................................................76
Customer Quote...................................................................................................77
Electronic Payment Authorization or Settlement Failed.......................................78
Invoice Batch Release.........................................................................................79
OE Price Override................................................................................................80
Order Entry Backorder.........................................................................................80
WH Priority Override............................................................................................81
Purchase Order (PO)....................................................................83

Activity Budget Exceeded....................................................................................83
Inspection Required.............................................................................................84
Inspection Item Rejected.....................................................................................85
Purchase Order Overshipment Message Exists..................................................85
Purchase Order Overshipment Message Cleared...............................................86
Requisition Item Received...................................................................................87
PO Vendor Agreement Notify...............................................................................88
Subcontractor PO Approval.................................................................................88
EDI Purchase Order Acknowledgment................................................................89
EDI PO Acknowledgement Buyer Notification.....................................................91
PO Cost Discrepancy...........................................................................................91
P-Card Request...................................................................................................92
P-Card Charge Approval......................................................................................92
P-Card Charge Activation....................................................................................93
P-Card Charge Dispute........................................................................................94
P-Card Charge Rejected......................................................................................94
P-Card Charge Released.....................................................................................95
P-Card Rejection..................................................................................................96
PO Delivery Ticket Select.....................................................................................96
General PO Maintenance....................................................................................97
General PO Receipt.............................................................................................97
EAM PO Release to Work Order / PO Line Close...............................................98
Requisitions (RQ).......................................................................100
Rush Item...........................................................................................................100
Requisition Approval..........................................................................................101
Create Line Approval.........................................................................................102
Requisition Line Approval..................................................................................103
LPA and S3 Applications Reference Guide Contents 5

Requisition Line Approval GM............................................................................104
Warehouse (WH).........................................................................106
Warehouse Backorder........................................................................................106
WH Demand Cancellation..................................................................................107
WH Priority Override..........................................................................................108
WH Shipment Batch Creation............................................................................109
WH Shipment Creation......................................................................................110
Shipment Release..............................................................................................110
Shipment Backordered or Voided.......................................................................111
EAM Shipment Release.....................................................................................112
Production Order (WO)..............................................................114

Work Order Production......................................................................................114
Work Order Reverse..........................................................................................114
Work Order Sent Offsite.....................................................................................115
Work Order Allocation Override.........................................................................116
Chapter 6 Application Triggers and Services for EPM 117

Analytic Architect (IA)................................................................118
OLAP Database Notification..............................................................................118
6 Contents LPA and S3 Applications Reference Guide

Chapter 1
Overview
This reference guide provides information about the process triggers and services available in the Lawson
S3 Enterprise Applications for Lawson Process Automation. The following topics provide background
information for understanding how a triggers and services are used with Lawson Process Automation.
• "What is a process?" on page 7
• "What are S3 triggers and services?" on page 7
What is a process?
In Lawson Process Automation, a process moves work from defined activity to defined activity. A process
may transfer information or work from one user to the next until the work is completed. A process can also
perform work that does not involve users, such as take information from one Lawson form and add or change
the same information on another Lawson form automatically. For example, when a new employee is added
on the HR form Employee (HR11.1), that employee could also automatically (by means of a process) be
set up as a vendor for employee expenses.
Process files have the extension .lpd. The .lpd files are XML files in a proprietary format that the Lawson
Process Designer and Lawson Process Server can read.
What are S3 triggers and services?

NOTE You can use S3 triggers that are delivered with Lawson applications, or create your own. For more
information, see Lawson Process Automation Administration Guide .
A S3 trigger is COBOL code in a Lawson application that defines an event within the application that, when
it occurs, ultimately creates a work unit. A work unit is a data set that allows Lawson Process Automation
to start an associated process and track its execution. A trigger is activated as the by-product of a user
performing a business action in an application. For example, releasing a requisition or putting a customer
order on hold.
A service is a Lawson Process Automation entity that allows an application trigger to create a work unit
associated with the service. A service has specific requirements, such as an application code name that
corresponds to the service name and an initiating event. The services for triggers delivered with Lawson
application are available from Lawson Process Server and in Lawson Process Designer. All services are
delivered as disabled. You must enable them before they can be used in Lawson Process Automation. A
service can invoke one or more processes. Multiple processes can be processed at the same time.
LPA and S3 Applications Reference Guide Chapter 1 Overview 7

Chapter 2
Install LPA Services for S3 Enterprise

Applications
Install LPA Services for S3 Enterprise Applications

The LPA Services for S3 product holds the definition of each Service described in this document. Use the
following steps to install LPA Services for S3 product into your Lawsn Process Automation server.
STEPS To install LPA Services for S3

1. Download LPA Services for S3 from the Product Download Center.
2. Transfer the .jar file to your LPA server.
3. Extract the contents of the .jar file to a new temporary directory
jar –xvf lpaservices.jar
4. Run the installation program from the temporary directory. Use the data area created in Landmark
for LPA.
perl install.pl dataarea
Make sure that the services imported. You should see the S3 services listed when you log into
the LPA application.
8 Chapter 2 Install LPA Services for S3 Enterprise LPA and S3 Applications Reference Guide
Applications
Chapter 3
Application triggers and services for

Human Capital Management
This chapter provides detailed information about the services in the human resources applications.
• "Human Resources (HR)" on page 10
• "Personnel (PA)" on page 12
LPA and S3 Applications Reference Guide Chapter 3 Application triggers and services for 9
Human Resources (HR)
• "Goal Approval" on page 10
• "Employee Delete" on page 11
Goal Approval
The triggers create work units when a new employee objective is added by a manager or an employee, or
when an employee accepts an existing objective through the Goal View Self Service tasks.
Service Goal Approval
Service name Goal Approval
System Human Resources (HR)
Criteria Company
Work Category Supervisor

Data string = [company number][supervisor code]
Prerequisites Access to Goal View Manager/Employee Self

Service tasks
Initiating event • Manager defines an employee objective in the

MSS Goal View task where the Goal Status is
updated to Not Reviewed.
• Employee reviews and accepts an objective
defined by their manager where the Goal Status
is updated from Not Reviewed to Reviewed.
• Employee defines an objective in ESS Goal View
where the Goal Status is updated to Reviewed.
Resolution action Manager will either Approve or Reject an objective

record through their inbasket. The Goal Status on
HS08.2 is set to 2 (Mgr Approved) or back to 0 (Not
Reviewed) when the objective has not been
approved.
An email will be sent to an employee to notify him
or her that he/she will need to review and accept an
objective defined by the manager, or an email will
be sent to an employee with the objective’s Goal
Status after the Manager either approves or rejects
the objective record.
10 Chapter 3 Application triggers and services for LPA and S3 Applications Reference Guide
Variables EMP_SUPERVISOR
PGO_ACCEPTED
PGO_COMPANY
PGO_EMPLOYEE
WOR_WORK_ORDER_SUF
PGO_END_DATE
PGO_OBJECTIVE
PGO_PRIORITY
PGO_SEQ_NBR
PGO_START_DATE
PGO_TYPE
Special Considerations
User setup will require that a Supervisor work category is assigned to each user with the role MGR. The
values are the Company and Supervisor Code.
Employee Delete
This service creates a work unit when a S3 user successfully deletes an employee on Employee (HR11.1)
or PA115.
Service EmployeeDelete
Service name Employee Delete
System Human Resources (HR)
Criteria Company
Work Category None
Prerequisites
Initiating event Delete an employee on HR11.1 or PA115
Resolution action N/A
Variables EMP_COMPANY
EMP_EMPLOYEE
Related LPA Process

The following process file is delivered with S3 ION Connectors: XM_InactivateEmployee
Personnel (PA)
The following services are available in the Personnel (PA) application.
• "Job Requisition Approval" on page 12
• "Personnel Action Approval" on page 14
Job Requisition Approval

This trigger creates a work unit when a new job or position opening is entered on Requisition (PA42.1).
Service JobReq Approval
Service name Job Requisition Approval
System Personnel Administration (PA)
Criteria Company, Process Level, Department
Work Category Department

Data string = [process level][department]
Prerequisites Requisition (PA42.1) must have a requisition status

of WFINPROG. This WFINPROG status must be
typed exactly as shown. The description of the status
can be modified.
Initiating event Requesting a new job position on Requisition

(PA42.1).
Variables MAILTO
PJR_BUDJETED_FLAG
PJR_COMPANY
PJR_DATE_NEEDED
PJR_DEPARTMENT
PJR_DESCRIPTION
PJR_EXEMPT_EMP
PJR_JOB_CODE
PJR_LOCATION_CODE
PJR_POSITION_NBR
PJR_PROCESS_LEVEL
PJR_REPLACEMENT
PJR_REQUEST_BY
PJR_REQUEST_DATE
PJR_REQUISITION
PJR_SUPERVISOR
PJR_USER_LEVEL
Recommendation
The following status codes could be defined on Requisition Status (HR83.8):
• WFAPPROVE (Job Req Approved by Workflow)
• WFINPROG (Job Req Workflow in Progress)
• WFREJECT (Job Req Not Approved by Workflow)
Special considerations
• On Requisition (PA42.1), the following fields affect the routing of the Job Requisition Approval procedure:
Budgeted, Replacement, and Exempt.
• After a requisition goes into the approval process, any changes to the requisition cause the cancellation
of the existing process and require the generation of a new process.
• The ability to do email from the browser must be configured.
• The deletion of a requisition on Requisition (PA42.1) causes the cancellation of the existing process.
Possible process flow sequences
The Division Manager, Vice President, and Chief Financial Officer are notified that a job requisition needs
approval. The Exempt Recruiter or Non-Exempt Recruiter receives an e-mail notification when the job
requisition is approved.
1. The Division Manager receives notification that a job requisition needs approval. If the requisition
is for a replacement, the Division Manager can take action. Possible actions: Approve Staff
Replacement, Disapprove Staff Replacement, Suspend, and Hold.
2. If the Division Manager approves the replacement, an email notification is sent to a recruiter.
Depending on whether the position is exempt, either the Exempt Recruiter or the Non-exempt
Recruiter receives notification that the requisition is approved and hiring activities can begin.
3. Depending on whether the requisition was approved or rejected, the job requisition is updated
with the ID of the decision maker and a final status of WFApprove or WFREJECT via Requisition
(PA42.1).
- or-
1. The Division Manager receives notification that a job requisition needs approval. If the requisition
is for a staff addition or non-replacement position, the Division Manager can take action. Possible
actions: Approve Staff Addition, Disapprove Staff Addition, Suspend, and Hold.
2. If the Division Manager approves the staff addition requisition, and the position is budgeted, skip
to step 4. If the position is not budgeted, the Vice President receives notification that the job
requisition needs approval and takes appropriate action. Possible actions: Approve Staff Addition,
Disapprove Staff Addition, Suspend, and Hold.
3. If the Vice President approves the requisition, the Chief Financial Officer receives notification that
a job requisition needs approval and takes appropriate action. Possible actions: Approve Staff
Addition, Disapprove Staff Addition, Suspend, and Hold.
4. After the requisition is approved by all the required roles, an e-mail notification is sent to a recruiter.
Depending on whether the position is exempt, either the Exempt Recruiter or the Non-exempt
Recruiter receives notification that the requisition is approved and hiring activities can begin.
NOTE Taking the Disapprove Staff Addition action will change the requisition status to WFREJECT.
Personnel Action Approval

This trigger creates a work unit when a personnel action is entered on Individual Action (PA52.1), Hire an
Applicant (PA52.4), or Position and Job Action (PA52.5). It can also create a work unit when a salary change
is approved on Individual Action (PA52.1) and the employee has labor distribution templates with grants
subject to salary caps that need to be reviewed by a grant administrator.
Process information
If you are writing your own process against the Personnel Action Approval service, any action code that
is flagged as Workflow will create a work unit. The action code must be defined as the service and setup
as any other service. In other words, enabled, configured, and linked to a process file. When you define
the service for the action code, be sure to type the action code exactly as it appears on Action (PA50),
or the process will not be initiated.
Action Update (PA100) updates an action code flagged as Workflow only if one of these conditions
applies:
• The process has been completed.
• A record is displayed on Personnel Action Workflow Override (PA53.1) when an action is displayed
on the workflow (on Action (PA50.1)) and the Approval flag on the action is No. To approve the
action, set the Approval flag to Yes.
There are two ways for the Action to be approved and processed through Action Update (PA100).
The first is through the workflow when the action is approved. The second is when the approval is
done by and override done on Personnel Action Workflow Override (PA53.1) and will only be viewable
on the Individual Action (PA52.1), Hire an Applicant (PA52.4), or Position and Job Action (PA52.5).
An action must be approved to be updated by Action Update (PA100).
Service [use Action (PA50.1) action code value]
Service Name Personnel Action Approval (PA)
System Personnel Administration (PA)
Criteria Company, Process Level, Department
Work Category Supervisor
Data string = [company number][supervisor code]
Prerequisites Action codes must be defined on Action (PA50.1) as Workflow.
Initiating event Entry of personnel action on Individual Action (PA52.1).
Resolution action Update personnel action record in Personnel Action Workflow Override
(PA53.1) with a Yes in the Approval field for the record to be updated in
the system.
Variables Action
Action_Nbr
Action_Type
Company
Effect_Date
Employee
Mailsubject
New_Department
New_Employee_Status
New_Pay
New_Process_Level
New_Supervisor
Next_New_Super
Next_Old_Super
Old_Department
Old_Employee_Status
Old_Pay
Old_Process_Level
Old_Supervisor
Over_Budget
Percent_Changed
Reason_1
Reason_2
User setup will require that a Supervisor work category is assigned to each user with the role MGR. The
values are the Company and Supervisor Code.
Action Update (PA100) will not release any action flagged for Workflow where the Approval flag on the
action is No.
The Inbasket display is related to a salary change. You will need to make HTML programming changes
if you want the Inbasket to display different information.
The deletion of an action causes the cancellation of the existing process.
Possible process flow sequence
The next-level manager is notified that a given personnel action needs approval. You can create a
process flow for any action code.
Example for the Salary Change action code:
• The first-level manager is given the choice of approving or disapproving the increase on any
percentage change.
• If a change over a specified amount is approved, the next-level manager is notified and has the
ability to approve or disapprove the change. If no supervisor is found, then Compensation is notified
and can approve or disapprove the change.
• If a change is disapproved, the Compensation role will receive an e-mail with the subject Salary
Change Rejection.
• (capnotification) If a change is approved and the employee has labor distribution templates with
grants subject to salary caps, the grant administrator will receive an e-mail with the subject "Salary
Cap action required for employee."
Example for the Promotion action code:
• The first-level manager is given the choice of approving or disapproving the increase on any
percentage change.
• If a change over a specified amount is approved, the next-level manager is notified and has the
ability to approve or disapprove the change. If no supervisor is found then Compensation is notified
and can approve or disapprove the change.
• If a change is disapproved, the Compensation role will receive an e-mail with the subject Promotion
Rejection.
Chapter 4
Application triggers and services for

Enterprise Financial Management
This chapter provides detailed information about the services in the financials applications.
• "Asset Management (AM)" on page 18
• "General Ledger (GL)" on page 21
• "Project and Activity Accounting (AC)" on page 26
• "Billing and Revenue Management (BR)" on page 32
• "Grant Management (GM)" on page 34
• "Accounts Payable (AP)" on page 38
• "Accounts Receivable (AR)" on page 44
• "Employee Expense (EE)" on page 52
Asset Management (AM)
The following services are available in Asset Management (AM).
• "Asset Addition" on page 18
• "Asset Adjustment" on page 18
• "Asset Disposal" on page 19
• "Asset Transfer" on page 19
• "EAM Asset Addition" on page 20
Asset Addition
This trigger creates a work unit when a new asset is released into the system. Newly created assets can
be released into the system by Additions and Adjustments (AM20.2), Leased Asset Addition and Adjustment
(AM21.2), or Processing Release (AM170).
Service AssetAddition
Service name Asset Addition
System Asset Management (AM)
Criteria Company, Type, Subtype
Initiating event The releasing of a new asset into the system by

Additions and Adjustments (AM20.2), Leased Asset
Addition and Adjustment (AM21.2), or Processing
Release (AM170)
Variables ASSET
Asset Adjustment
This trigger creates a work unit when an asset adjustment is released into the system. Asset adjustments
can be released into the system by Additions and Adjustments (AM20.2), Leased Asset Addition and
Adjustment (AM21.2), or Processing Release (AM170).
Service AssetAdjustment
Service name Asset Adjustment
Initiating event The releasing of an asset adjustment into the system
by Additions and Adjustments (AM20.2), Leased
Asset Addition and Adjustment (AM21.2), or
Processing Release (AM170)
Variables ASSET
Asset Disposal
This trigger creates a work unit when an asset disposal is released into the system. Asset disposals can be
released into the system by using Disposals (AM40) or Asset Release (AM170).
Service AssetDisposal
Service name Asset Disposal
Initiating event The release of an asset disposal into the system by

Disposals (AM40) or Asset Release (AM170).
Variables ASSET
Asset Transfer
This trigger creates a work unit when an asset transfer is released into the system. Asset transfers can be
released into the system byTransfers (AM30) orAsset Release (AM170).
Service AssetTransfer
Service name Asset Transfer
Initiating event The releasing of an asset transfer into the system

by Transfers (AM30) orAsset Release (AM170).
Variables ASSET
EAM Asset Addition
When enabled, this trigger creates a work unit when a new EAM equipment item is released on Quick
Addition (AM20.1) or Additions and Adjustments (AM20.2).
Service EAM_AssetAddition
Service name EAM_Asset Addition
Work Category None
Prerequisites An EAM division must exist. On Division (AM08.1),

add a division of EAM. The value in the Division field
must be EAM.
Initiating event The releasing of a new asset into the system by

Additions and Adjustments (AM20.2), Leased Asset
Addition and Adjustment (AM21.2), or Processing
Release (AM170)
Variables ASI_DESCRIPTION
ASI_ITEM_NBR
ASI_MODEL_NUMBER
ASI_SERIAL_NUMBER
AST_ASSET AST_COMPANY
AST_DESCRIPTION
AST_STATUS
M3_STATUS
General Ledger (GL)
The following services are available in General Ledger (GL).
• "Cost Allocation" on page 21
• "FlexBudgeting Version Add" on page 21
• "FlexBudgeting Add" on page 22
• "GL Level Reorganization" on page 23
• "Journal Entry Approval" on page 23
• " Delete Accounting Unit" on page 25
• "GL Company Delete" on page 25
Cost Allocation
This trigger creates a work unit when Allocation Interface (CA190) is run for a company.
Service CostAllocation
Service name Cost Allocation
System General Ledger (GL)
Criteria Company
Work Category None
Prerequisites No prerequisites are required other than normal

allocation processing.
Initiating event Running Allocation Interface (CA190) for a company.
Variables MAILFROMUSER
MAILSUBJECT
MAILTOROLE

The Accounting owner is notified that Allocation Interface (CA190) was run for a company. (A Distribution
Group would have to be assigned to the job so the person with the task of Acct Supervisor could see the
report in his or her print manager.)
FlexBudgeting Version Add

This trigger creates a work unit when a new version of an existing budget is added by running Budget Version
(FB122).
Service FbBudgetVerAdd
Service name Flex Budgeting Version Add
Criteria Company, Fiscal Year, Budget Number
Work Category None

budget processing.
Initiating event Adding a new version of an existing budget by

running Budget Version (FB122).
MAILSUBJECT
MAILTOROLE

The Accounting Supervisor is notified when a new version of an existing budget is added.
FlexBudgeting Add
This trigger creates a work unit when a budget is added on Period Budget, Rate (FB20.1), Period Budget,
Amounts (FB20.6), or Period Budget, Units (FB20.7).
Service FbBudgetAdd
Service name Flex Budgeting Add
Criteria Company, Fiscal Year, Budget Number
Work Category None

budget processing.
Initiating event Adding a budget on Period Budget, Rate (FB20.1),

Period Budget, Amounts (FB20.6), or Period Budget,
Units (FB20.7).
MAILSUBJECT
MAILTOROLE
Possible flow sequence

The Accounting Supervisor is notified that a new budget was added.
GL Level Reorganization
This trigger creates a work unit when a level reorganization for a company is run on Level Reorganization
(GL120).
Service GlLevelReorg
Service name GL Level Reorg
Criteria Company
Work Category None

general ledger processing, which includes assigning
a Distribution Group to the job so the person with
the task of Acct Supervisor can see the report in his
or her print manager.
Initiating event Running a level reorganization for a company on

Level Reorganization (GL120).
MAILSUBJECT
MAILTOROLE

The Accounting Supervisor is notified that a level reorganization was run for a company.
Journal Entry Approval

This trigger creates a work unit when a journal entry is released on Journal Entry (GL40) or Journal Control
(GL45), when a recurring journal entry is journalized on Recurring Journal Control (GL75) or Recurring
Journal Interface (GL170), or when you run Batch Journal Control (GL146) under certain circumstances
(see "Initiating events for Batch " below.
Service JE Approval
Service name Journal Entry Approval
Criteria Company
Object GLCSET1
Work Category None
Prerequisites On Company (GL10), in the Options section of the

Journals page, the Workflow field must be set to Yes,
and the JE Approval Amount field must have a
defined amount. Any journal entry greater than the
defined amount initiates the service.
Initiating event Releasing a journal entry on Journal Entry (GL40)
or Journal Control (GL45).
Journalizing a recurring journal entry on Recurring
Journal Control (GL75) or Recurring Journal Interface
(GL170).
Running Batch Journal Control (GL146) under certain
circumstances. See "Initiating events for " below.
Variables ACCT_PERIOD
COMPANY
CONTROL_GROUP
FISCAL_YEAR
JE_AMT
JE_APPROVE_AMT
JE_SEQUENCE
JE_TYPE
SYSTEM
Initiating events for Batch Journal Control (GL146)

You can use Batch Journal Control (GL146) to create a work unit to approve journal entries for entries that
do not pass through the approval process when they are released or journalized. The table below illustrates
how to setup GL146 to initiate journal entry approval:
Action field System field (Main) Approve Flag field Systems fields (Approve)
(Approve)
JE Approve (A) Blank Yes Blank
JE Approve (A) Blank Yes Not Blank
JE Approve (A) Blank No Not Blank
• While the journal entry is in the approval process, it cannot be unreleased, maintained, or posted.
• If a journal entry is disapproved, it can be unreleased, maintained, deleted, or released again. It cannot,
however, be posted. Releasing a disapproved entry initiates the approval process again.
The Accounting Supervisor is notified that a general ledger journal entry needs approval based on a minimum
total debit or credit amount.
1. The Accounting Supervisor receives notification to review a journal entry and takes appropriate
action. Possible actions: Send to Controller, Disapprove, Suspend, and Hold.
2. Optional. If the Accounting Supervisor chooses Send to Controller, the Controller receives
notification to review the journal entry and takes appropriate action. Possible actions: Approve,
Disapprove, Suspend, and Hold.
3. The journal entry approval flag is appropriately updated via Journal Analysis (GL41.1).
4. If the Controller disapproves the journal entry, the Accounting Supervisor receives an e-mail
notification that the journal entry was rejected.
Delete Accounting Unit

This service creates a work unit when a S3 user successfully deletes an accounting unit on (GL20.1).
Service DelAcctUnit
Service name Delete Accounting Unit
System General Ledger Setup (IF)
Criteria Company, Accounting Unit
Work Category None
Prerequisites
Initiating event Delete an accounting unit on GL20.1
Variables GLN_COMPANY
GLN_ACCT_UNIT
Related LPA Process

The following process file is delivered with S3 ION Connectors: XM_InactivateAccountingUnit
GL Company Delete
This service creates a work unit when a S3 user successfully deletes a company on Company (GL10.1).
Service GLCompanyDelete
Service name GL Company Delete
System General Ledger Setup (IF)
Criteria Company
Work Category None
Prerequisites
Initiating event Delete a company on GL10.1
Variables GLS_COMPANY
GLS_NAME
Related LPA Process

The following process file is delivered with S3 ION Connectors: XM_InactivateCompany
Project and Activity Accounting (AC)
The following services are available in Project and Activity Accounting (AC).
• "Activity Addition Approval" on page 26
• "Activity Delete" on page 26
• "Activity Status Change" on page 27
• "Activity Budget Change Order Request" on page 27
• "Activity Budget Change Order Release" on page 28
• "Grant Activity Budget Alert" on page 29
• "Activity Contract Complete" on page 31
Activity Addition Approval

This trigger creates a work unit when an activity is added or changed on Activity (AC10).
Service ActAddApproval
Service name Activity Addition Approval
System Project Accounting (AC)
Criteria Activity Group
Work Category None
Prerequisites
Initiating event Adding an activity on Activity (AC10).
Resolution action None
Variables ACV_ACTIVITY
ACV_ACTIVITY_GRP
MAILFROMUSER
MAILSUBJECT
MAILTOROLE
Activity Delete
This service creates a work unit when a S3 user successfully deletes an activity on Activity (AC10).
Service ActAddApproval
Service name Activity Addition Approval
Criteria Activity Group
Work Category None
Prerequisites
Initiating event Delete an activity on AC10.1.
ACV_ACTIVITY_GRP
MAILFROMUSER
MAILSUBJECT
MAILTOROLE
Related LPA Process

The following process file is delivered with S3 ION Connectors: XM_InactivateActivity
Activity Status Change

This trigger creates a work unit when an activity status on is changed on Activity Status (AC12) or Mass
Activity Status Change (AC112).
Service ActStatusChg
Service name Activity Status Change
Criteria Status, Update
Work Category None
Prerequisites
Initiating event Changing an activity status on Activity (AC10),

Activity Status (AC12), or Mass Activity Status
Change (AC112).
ACV_ACTIVITY_GRP
MAILFROMUSER
MAILSUBJECT
MAILTOROLE
Activity Budget Change Order Request

This trigger creates a work unit when a budget change order is added on:
• Life Only Budget Change Order (AC21.1)
• Annual Budget Change Order (AC21.2)
• Period Budget Change Order (AC21.3)
• Activity Budget Change Orders by Activity (AC21.4)
Once a budget change order is added, it must be approved. When the change order is approved, it must
be released to update the existing budget.
Service ActBudChgReq
Service name AC Budget Change Order Request
Criteria Activity Group, Activity, Budget Number
Work Category None
Prerequisites None
Initiating event Adding a budget change order on:

• Activity Budget Change Orders by Activity
(AC21.4)
Variables CHO_ACTIVITY
CHO_ACTIVITY_GRP
CHO_BUDGET_NBR
CHO_CHG_ORDER_NBR
MAILFROMUSER
MAILSUBJECT
MAILTO
Activity Budget Change Order Release

This trigger creates a work unit when an activity budget change order is approved or released on Change
Order Approval (AC22). After a change order is added, it must be approved before it can be released.
Releasing a change order updates the existing activity budget with the change.
Service ActBudChgReleas
Service name AC Budget Change Order Release
Criteria Activity Group, Activity, Budget Number
Work Category None
Prerequisites To approved a change order, the change order must

have been added on anly of the following forms:
• Activity Budget Change Orders by Activity
(AC21.4)
To release a change order, the change order must
have been approved on Change Order Approval
(AC22).
Initiating event Approving an activity budget change order on

Change Order Approval (AC22) generates a work
unit that contains a message indicating the change
order has been approved.
Releasing an activity budget change order on
Change Order Approval (AC22) generates a work
unit that contains a message indicating the change
order has been released.
Variables CHO_ACTIVITY
CHO_ACTIVITY_GRP
CHO_BUDGET_NBR
CHO_CHG_ORDER_NBR
MAILFROMUSER
MAILSUBJECT
MAILTOROLE
Grant Activity Budget Alert

This trigger creates a work unit when a report line is over budget tolerance when Activity Commitment
Summary (AC295) is run. The work unit creates an email notification to alert the principal investigator (PI)
that the grant activity is over budget tolerance.
IMPORTANT This trigger is available only when the Grant Management (GM) application is used.
Service ActBudgetAlert
Service name Grant Activity Budget Alert
Criteria Activity Group, HR Company, PI (Principal

Investigator)
Work Category None
Prerequisites ProcessFlow field on AC295 set to Yes.
Initiating event A work unit is created for any line on the Activity
Commitment Summary report where value in the
Over/Under Tolerance column is Over.
NOTE Activity actual amounts and commitments are

dynamic. The work unit is triggered if the report line
was over tolerance when the report was run. The
actual and commitment amounts may change
between the time the work unit was created and the
time other inquiries or reports are used to analyze
the overage.
(For more information, see Initiating Event,

Continued, below.)
Variables ACCT_CATEGORY
ACCT_CATEGORY_DESC
ACTIVITY
ACTIVITY_DESC
ACTIVITY_GROUP
ACTIVITY_GROUP_DESC
ACTUAL
BUDGETED
BUDGET_NUMBER
COMMITMENT
PERIOD
REPORT_DATE
REPORT_TIME
TO_DATE_OPTION
VARIANCE
VARIANCE_PERCENT
YEAR
Initiating Event, Continued

The following formula determines if Over appears in the column:
(Actual+Commitment) — Budget = Variance Amount
(Variance Amount/Budget) * 100 = Variance %
If Variance % > AC295 Tolerance parameter, then Over
AC295 parameters for Activity Level Type and Account Category Detail determine which lines appear on
the report, and that determines if a work unit is created.
• Activity Level Type allows you to present summary activities, posting activities, or both. Both is not
recommended since it will create duplicate work units.
• Account Category Detail determines if the report prints by activity and account category, or if account
category information is consolidated into one line by activity. This determines the level at which the
budget tolerance formula and the resulting work units. For example, to generate a work unit for a given
line item within a grant that is over budget, the Account Category Detail field should be set to Yes. To
generate a work unit only if the entire grant activity is over budget, set the field to No.
Activity Contract Complete

This trigger creates a work unit when the percent complete is calculated on Activity Percentage of Completion
(AC65) or Percent Complete Calculation (AC165), and a percent complete of 100% or more is obtained.
The formula for calculating percent complete is (Activity Costs/Activity Budget).
Service ActContrCmplete
Service name Activity Contract Cmplete
Criteria Activity, Budget Type, Date
Work Category None
Prerequisites Define activity budgets and post activity costs.
Initiating event Calculating 100% or greater percent complete on

Activity Percentage of Completion (AC65) or Percent
Complete Calculation (AC165).
MAILSUBJECT
MAILTOROLE
Billing and Revenue Management (BR)
The following service is available in the Billing and Revenue Management (BR) application.
• "Activity Contract Complete" on page 32
• "Activity Billed" on page 32
• "Activity Revenue Recognized" on page 33
Activity Contract Complete

This trigger creates a work unit when the percent complete is calculated on Contract Percent Complete
(BR65.1), Percent Complete by Activity (BR65.2), or Percent Complete Calculation (BR165), and a percent
complete of 100% or greater is obtained.You can calculate percent complete on contracts with any revenue
recognition method; however, contracts using the Completed Contract Method B revenue recognition must
be 100% complete in order to recognize revenue.
Service ActContrCmplete
Service name Activity Contract Cmplete
System Billing and Revenue Management (BR)
Criteria Activity, Budget Type, Date
Work Category None
Prerequisites Define a contract, define activity budgets, and post

activity costs.
Initiating event Calculating 100% or greater percent complete on

Contract Percent Complete (BR65.1), Percent
Complete by Activity (BR65.2), or Percent Complete
Calculation (BR165).
MAILSUBJECT
MAILTOROLE
Activity Billed
The Activity Billed service creates a work unit that can be used to notify the Activity Supervisor that Invoice
Calculation (BR120) has been run in Update mode.
Service ActBilled
Service name Activities Have Been Billed (AC)
Criteria Update
Category None
Prerequisites None
Initiating event Run Invoice Calculation (BR120) with the Update

option set to Y.
MAILSUBJECT
MAILTOROLE
Activity Revenue Recognized

The Activity Revenue Recognized service creates a work unit that can be used to notify the Activity Supervisor
that Revenue Recognition (BR130) has been run in Update mode.
Service ActRevRecog
Service name Revenue Has Been Recog'd (AC)
Criteria Activity, Acct Category, Update
Category None
Prerequisites None
Initiating event Run Revenue Recognition (BR130) with the Update

option set to Y.
MAILSUBJECT
MAILTOROLE
Grant Management (GM)
The following services are available in the Grant Management (GM) application.
IMPORTANT Grant Management-based triggers exist in other system codes, see:

• "Grant Activity Budget Alert" on page 29
• "AP Cost Transfers Approval for Grant Activity Transactions" on page 41
• "Requisition Line Approval GM" on page 104
• "Labor Distribution Approval" on page 34
• "Labor Cost Transfer Template Approval" on page 35
• "Effort Certification " on page 36
• "Effort Variance " on page 37
Labor Distribution Approval

The service for labor distribution approval is triggered when a labor distribution template line is released on
Labor Distribution Template Entry (GM10.2) or during Labor Distribution Mass Status Change (GM115).
Labor distribution template lines are typically approved by the principal investigator (PI) associated with a
grant activity, or the PI’s designee. Labor distribution template lines must have an approved status to be
eligible for Salary Encumbrance Processing (GM110) or labor distribution processing during Payroll Close
(PR197) or Non-Lawson Payroll Transaction Import (GM500).
The PI is associated with the activity in the labor distribution template line. If no PI exists for the activity, the
PI for its parent activity is used. Distribution lines that do not contain an activity will not have a PI associated
with them. In this case, the Process Definition should contain a line for a blank PI. The flow should contain
a DME call that filters on general ledger company and accounting unit for approval routing.
Service Lab Dist Appr
Service name Labor Distribution Approval
System Grant Management (GM)
Criteria HR Company, PI (Principal Investigator)
Work Category Company/PI

Data string = [HR company][employee ID]
Prerequisites Define a labor distribution template on Labor

Distribution Template Entry (GM10.2).
Initiating event Releasing a labor distribution template line on Labor

Distribution Template Entry (GM10.2) or Labor
Distribution Mass Status Change (GM115).
Variables GMA_ACCOUNT
GMA_ACCT_CATEGORY
GMA_ACCT_UNIT
GMA_ACTIVITY
GMA_COMPANY
GMA_EFFECT_DATE
GMA_EMPLOYEE
GMA_GML_OBJ_ID
GMA_HR_COMPANY
GMA_JOB_CODE
GMA_OBJ_ID
GMA_PAY_CODE
GMA_POSITION
GMA_SEQUENCE_NBR
GMA_SUB_ACCOUNT
Labor Cost Transfer Template Approval

This trigger creates a work unit when a labor cost transfer template line is released on Labor Cost Transfer
Template Entry (GM12.2) or Labor Distribution Mass Status Change (GM115).
Cost transfer template lines are typically approved by the principal investigator (PI) associated with a grant
activity or the PI's designee. All lines in a labor cost transfer template must be approved to be eligible for
Labor Cost Transfer Processing (GM170) or Non-Lawson Payroll Cost Transfer Processing (GM171).
The PI is associated with the activity in the labor cost transfer template line. If no PI exists for the activity,
the PI for its parent activity is used. Distribution lines that do not contain an activity will not have a PI
associated with them. In this case, Process Definition should contain a line for a blank PI. The flow should
contain a DME call that filters on general ledger company and accounting unit for approval routing.
Service LabTransferAppr
Service name Labor Cost Transfer Approval
Criteria HR Company, PI (Principal Investigator)

Prerequisites Define a labor cost transfer template on Labor Cost

Transfer Template Entry (GM12.2).
Initiating event Releasing a labor cost transfer template line on

Labor Cost Transfer Template Entry (GM12.2) or
Labor Distribution Mass Status Change (GM115).
Variables GMH_ACCOUNT
GMH_ACCT_CATEGORY
GMH_ACCT_UNIT
GMH_ACTIVITY
GMH_COMPANY
GMH_EMPLOYEE
GMH_END_DATE
GMH_GMI_OBJ_ID
GMH_GMI_SEQ_NBR
GMH_HR_COMPANY
GMH_JOB_CODE
GMH_PAY_CODE
GMH_POSITION
GMH_SEQUENCE_NBR
GMH_START_DATE
GMH_SUB_ACCOUNT
Effort Certification
This trigger creates a work unit that can be used to notify the primary certifier that effort data exists that
requires certification.
Service Effort Cert
Service name Effort Certification
Criteria HR Company, Primary Certifier, Secondary Certifier
Work Category HR Company

Certifier
Prerequisites
Initiating event Running Effort Calculation and Certification Report

(GM165) with the Report Option field set to Calculate
or Recalculate.
Running Effort Exception Report (GM265) will also
create a work unit if there are effort records with a
status of "Calculated".
Variables EFH_BEGIN_DATE
EFH_EMPLOYEE
EFH_END_DATE
EFH_HR_COMPANY
EFH_SEQUENCE_NBR
Effort Variance
This trigger creates a work unit that can be used to notify the primary certifier about variances between
actual effort and planned effort percentages or actual effort and salary percentages.
Service Effort Variance
Service name Effort Variance
Criteria HR Company, Primary Certifier. Secondary Certifier
Work Category Company

Certifier
Prerequisites
Initiating event Running Effort Variance Report (GM465) and

variances exist above the tolerance specified on the
report parameters
Variables EFX_ACCT_UNIT
EFX_ACTIVITY
EFX_ACTL_EFRT_PCT
EFX_BEGIN_DATE
EFX_CALC_PAY_PCT
EFX_COMPANY
EFX_EMPLOYEE
EFX_END_DATE
EFX_HR_COMPANY
EFX_LINE_NBR
EFX_PLAN_PCT
EFX_SEQUENCE_NBR
Accounts Payable (AP)
The following services are available in the Accounts Payable (AP) application.
• "Invoice Approval" on page 38
• "AP Cost Transfers Approval for General Ledger Transactions" on page 40
• "AP Cost Transfers Approval for Activity Transactions" on page 41
• "AP Cost Transfers Approval for Grant Activity Transactions" on page 41
• "General Vendor Maintenance" on page 42
• "EAM Supplier Add" on page 43
Invoice Approval
This trigger creates a work unit when an invoice for payment is released. For example, on Batch Control
(AP25), Invoice Release (AP26), Batch Release (AP125), Mass Invoice Release (AP126), Reconciliation
Queue (MA60), Review Invoice Message (MA66), Auto Matching (MA126), Invoice Interface (MA540),
Invoice Line Detail - Purchase Order (MA43), Basic Invoice (AP20).
Service Inv Approval
Service name Invoice Approval
System Accounts Payable (AP)
Criteria Company, Process Level
Object Key APISET1
Work Category Authority Code

Data string = [authority code]
Prerequisites On Basic Invoice (AP20), values must be entered in

the Authority Code and Voucher fields. The Workflow
field on the Options page of Company (AP00.4) must
be set to Yes. In addition, approval must be defined
on Company Approval (AP00.6) or Vendor Approval
(AP10.7). Company Approval (AP00.6) can be
accessed on Company (AP00.4), and Vendor
Approval (AP10.7) can be accessed on Vendor
(AP10.1).
Initiating event Releasing an invoice for payment on Batch Control

(AP25), Invoice Release (AP26), Batch Release
(AP125), Mass Invoice Release (AP126),
Reconciliation Queue (MA60), Review Invoice
Message (MA66), Auto Matching (MA126), Invoice
Interface (MA540), Invoice Line Detail - Purchase
Order (MA43), Basic Invoice (AP20).
Resolution action AGS call to set the approval field on AP32.1.
Variables API_AUTH_CODE
API_CANCEL_SEQ
API_COMPANY
API_INVOICE
API_INVOICE_TYPE
API_OUT_BAL_FLAG
API_SUFFIX
API_VENDOR
• Approving or disapproving an invoice using the Employee Advance Approval, Employee Expense
Approval, or Invoice Approval service updates the invoice status in the Accounts Payable system. If
approved, the invoice is available for payment selection on Cash Requirements (AP150). If disapproved,
the invoice is available for cancellation or adjustment.
• A company defined as Invoice Approval or Batch Releasing on Company (AP00.4) can initiate the
Employee Advance Approval, Employee Expense Approval, and Invoice Approval services.
• Approval can be established for Company, Company and Process Level, or Company and Vendor Level.
• On Company (AP00.4), if the Release Out of Balance field is set to Yes, the Workflow field must be set
to Yes, also.
• The Release Out of Balance field allows only those invoices with a variance between the invoice amount
and the distribution amount to be released. The invoice amount and payment amount must be in balance.
• When the Release Out of Balance field is set to Yes, all invoices that are out of balance, regardless of
the amount, initiate the Invoice Approval service.
• The approval amount defined for a company refers to the total invoice amount, and not to individual
detail lines.
• The invoice cannot be maintained on Invoice Maintenance (AP30) during the approval process, with
the exception of the following fields: Separate Payment, Pay Immediately, Enclosure, and Invoice Group.
• Run Invoice Payment Approval Edit (AP236) to list all invoices that are released but not approved.
• In the AGS call to set the approval field on AP32.1, be sure the WF-CANCEL-OVERRIDE field is set to
YES (WF-CANCEL-OVERRIDE=Y).
• If an invoice is approved directly on Workflow Approval Maintenance (AP32.1), the ProcessFlow work
unit for the invoice is cancelled.
The Accounts Payable Coder, Accounts Payable Supervisor, and Vice President are notified that an invoice
is ready to be paid and released for payment.
1. If the invoice is out of balance, the Accounts Payable Coder receives notification and takes the
appropriate action. Possible actions are: Balanced, InvCancelled, Suspend, and Hold.
2. If the invoice is greater than a predetermined dollar amount, the Vice President receives notification
to approve the invoice. Possible actions for the Vice President are: Approve, Reject, Suspend, or
Hold.
– or –
If the invoice is less than a predetermined dollar amount, the Accounts Payable Supervisor receives
notification to approve the invoice. Possible actions for the Accounts Payable Supervisor are:
Approve, Reject, Send to VP, Suspend, or Hold.
3. Optional. If the Accounts Payable Supervisor sends the invoice to the Vice President, the Vice
President receives notification to approve the invoice. Possible actions for the Vice President are:
Approve, Reject, Suspend, or Hold.
4. The invoice is updated via Workflow Approval Maintenance (AP32.1).
5. If the Accounts Payable Supervisor or Vice President rejects the invoice, the Accounts Payable
Coder receives an e-mail notification that the invoice was disapproved.
AP Cost Transfers Approval for General Ledger Transactions

NOTE This service, ApGlApproval, is one of three distribution adjustment services you can enable
(ApGlApproval for GL-only distributions, ApGrantActivity for distributions for grant activities, or
ApNonGrantActvy for distributions for non-grant activities).
When you release a cost transfer distribution in Accounts Payable, this service creates a work unit to approve
cost transfer distributions.
Service ApGlApproval
Service name AP Cost Transfer Approval for GL Transactions
Criteria Company, Acct Unit
Object APDSET1
Work Category
Prerequisites The Distribution Adjustments field on the Workflow

page of Company (AP00.4) must be set to Yes.
Initiating event Adjustments (Add, Change, Delete, or Reverse) or

comments entered on Distribution Adjustments
(AP30.2).
Resolution action AGS call to set the Approval field on Distribution

Approval (AP36.2).
Variables APD_API_OBJ_ID
APD_DIST_SEQ_NBR
API_COMPANY
API_INVOICE
API_SUFFIX
API_VENDOR
AP Cost Transfers Approval for Activity Transactions
NOTE This service, ApNonGrantActvy, is one of three distribution adjustment services you can enable
When you release a cost transfer distribution for an activity in Accounts Payable, this service creates a work
unit to approve cost transfer distributions.
Service ApNonGrantActvy
Service name AP Cost Transfer Approval for Activity Transactions
Criteria Company, Activity, Acct Unit
Object APDSET1
Work Category


(AP30.2).

Approval (AP36.2).
APD_DIST_SEQ_NBR
API_COMPANY
API_INVOICE
API_SUFFIX
API_VENDOR
AP Cost Transfers Approval for Grant Activity Transactions

NOTE This service, ApGrantActivity, is one of three distribution adjustment services you can enable
When you release a cost transfer distribution for a grant activity in Accounts Payable, this service creates
a work unit to approve cost transfer distributions.
IMPORTANT This service is for Grant Management (GM) users only. To approve non-GM activities, use
the ApNonGrantActvy service.
Service ApGrantActivity
Service name AP Cost Transfer Approval for Grant Activity
Transactions
Criteria Company, Activity, Acct Unit
Object APDSET1



(AP30.2).

Approval (AP36.2).
APD_DIST_SEQ_NBR
API_COMPANY
API_INVOICE
API_SUFFIX
API_VENDOR
General Vendor Maintenance

This service creates a work unit when a S3 user successfully adds or updates a vendor (on Vendor (AP10.1))
that is assigned a vendor class that is set with the EAM Vendor Flag field = Yes.
This service also creates a work unit when a S3 user successfully deletes a vendor (on Vendor (AP10.1)).
Service Gen_Supplier
Service name General Vendor Maintenance
Criteria Vendor Group, Vendor Class
Initiating event A vendor has been added or changed on AP10.1

and the vendor is assigned the EAM vendor class
(defined on Vendor Class (AP00.3) with EAM Vendor
Flag set to Yes on it).
A vendor has been deleted on AP10.1.
Variables NOTE All fields in the APVENMAST file.
Related LPA Process

The following process files are delivered with S3 ION Connectors: ION_SyncSupplierPartyMaster,
XM_InactivateVendor
EAM Supplier Add

When enabled, this trigger creates a work unit when an EAM vendor is added on Vendor (AP10.1).
Service EAM_Supplier
Service name EAM_Supplier
Criteria Vendor Group, Vendor Class, Vendor
Work Category None
Prerequisites A Vendor Class must exist (AP00.3) with EAM

Vendor Flag set to Yes
Initiating event A vendor added on Vendor (AP10.1) with a Vendor

Class that has the EAM Vendor Flag set to Yes on
it
Variables VENDOR
VENDOR_GROUP
VEN_CLASS
VEN_NAME
VEN_STATUS
Accounts Receivable (AR)
The following services are available in the Accounts Receivable (AR) application.
• "Customer Add or Credit Limit Change" on page 44
• "Customer Review Selection" on page 45
• "Payment Received with Orders on Credit Hold" on page 46
• "Transaction Transfer" on page 47
• "Transaction Grouping" on page 48
• "Disputed Invoice" on page 48
• "Return to Maker Payment" on page 49
• "Add Cust Desc" on page 50
• "Upd Cust Desc" on page 50

• "Upd Customer" on page 51
Customer Add or Credit Limit Change

This trigger creates a work unit when a customer is added or a customer credit limit is changed on Customer
(AR10) or the customer add or change API ARCA70PD is used. (This API is used to add or change customer
records using an interface to a third-party system.)
Service Cst Add Crd Lmt
Service name Customer Add Credit Limit Chg
System Accounts Receivable (AR)
Criteria Company
Object Key ACMSET1
Work Category Credit_Analyst

Data string = [credit analyst code]

accounts receivable processing, which includes a
non-existent customer for adding a customer, or an
existing customer for changing a credit limit.
Initiating event Adding a customer or changing a customer credit

limit on Customer (AR10) or using the customer add
or change API ARCA70PD. This API is used to add
or change customer records using an interface to a
third-party system.
Variables ACM_COMPANY
ACM_CREDIT_ANLYST
ACM_CREDIT_LIM
ACM_CUSTOMER
ACM_NAME
ACM_PRIOR_CREDIT_LIM
MAILFROMUSER
MAILSUBJECT
MAILTO
OPERATOR_CODE

The Credit Analyst is notified that a company-level customer was added or a company-level credit limit was
changed. Possible actions: Done, Hold, and Suspend.
Customer Review Selection

This trigger creates a work unit when the Customer Review Selection (AR170) selection process designates
the customer for credit analyst review.
Service Customer Review
Service name Customer Review Selection
Criteria Company
Object Key SELSET1

Data string = [credit analyst]
Prerequisites A customer must be in an eligible customer review

state.
Initiating event The Customer Review Selection (AR170) selection

process designates the customer for credit analyst
review.
ACM_CREDIT_ANLYST
ACM_CREDIT_LIM
ACM_CUSTOMER
ACM_NAME
MAILFROMUSER
MAILSUBJECT
OPERATOR_CODE

The Credit Analyst is notified that one or more customers have been selected by Customer Review Selection
(AR170) and are pending review.
Payment Received with Orders on Credit Hold

This trigger creates a work unit when an order for payment is received on Cash Batch (AR20), Cash MICR
Assignment (AR21), Cash Batch Release (AR24), Entry and Application (AR30), EFT Payment Creation
(AR115), Cash Batch Release Report (AR124), Lock Box Interface (AR570), Payment1 Interface (AR575),
or Payment Interface (AR580).
Service Pmt RelOrd Hold
Service name Pmt Rec w/ Order on Hold
Criteria Company
Object Key ACMSET1

Prerequisites A customer must have orders on hold with a payment

in an unreleased status.
Initiating event Releasing an order for payment on Cash Batch

(AR20), Cash MICR Assignment (AR21), Cash Batch
Release (AR24), Entry and Application (AR30), EFT
Payment Creation (AR115), Cash Batch Release
Report (AR124), Lock Box Interface (AR570),
Payment1 Interface (AR575), or Payment Interface
(AR580).
ACM_CREDIT_ANLYST
ACM_CREDIT_LIM
ACM_CUSTOMER
ACM_NAME
ACM_PRIOR_CREDIT_LIMIT
MAILFROMUSER
MAILSUBJECT
OPERATOR_CODE

The Credit Analyst is notified that a payment was received for a customer that has orders on credit hold.
Transaction Transfer
This trigger creates a work unit when Transfer (AR29) is used to initiate the transaction transfer process.
Service Trans Transfer
Service name Transaction Transfer
Criteria Company
Object Key ACMSET1


transaction transfer processing.
Initiating event Transfer (AR29) is used to initiate the transaction

transfer process.
ACM_CREDIT_ANLYST
ACM_CREDIT_LIM
ACM_CUSTOMER
ACM_NAME
MAILFROMUSER
MAILSUBJECT
OPERATOR_CODE
The credit analyst is notified that a transaction (payment, credit memo, invoice, or debit memo) has been
transferred from one customer to another.
Transaction Grouping
This trigger creates a work unit when one or more invoices, debit memos, or credit memos have been
grouped into a new debit or credit memo record using Transaction Obligation Grouping (AR44).
Service Trans Grouping
Service name Transaction Grouping
Object Key ARHSET1
Criteria Company
Work Category
Prerequisites A customer must have one or more of the following

items open: invoices, debit memos, or credit memos.
Initiating event The transaction grouping process
Variables

The Credit Analyst is notified that one or more invoices, debit memos, or credit memos have been grouped
into a new debit or credit memo record.
Disputed Invoice
This trigger creates a work unit when a disputed invoice or credit memo in created on Disputes (AR45.1).
Service Disp Inv
Service name Disputed Invoice
Criteria Company
Object Key ACMSET1

Prerequisites No prerequisites are required other than the

existence of a disputed invoice or credit memo.
Initiating event Creating a disputed invoice or credit memo on

Disputes (AR45.1).
ACM_CREDIT_ANLYST
ACM_CREDIT_LIM
ACM_CUSTOMER
ACM_NAME
MAILFROMUSER
MAILSUBJECT
OPERATOR_CODE

The Credit Analyst is notified that a customer invoice or debit memo is in a dispute status.
Return to Maker Payment

This trigger creates a work unit when Returned Payment (AR82) is released to create a return-to-maker
payment request.
Service RTM Payment
Service name Return to Maker Payment
Criteria Company
Object Key ACMSET1


return-to-maker payment request processing, which
includes adding a return-to-maker payment.
Initiating event Releasing Returned Payment (AR82) to create a

return-to-maker payment request.
ACM_CREDIT_ANLYST
ACM_CREDIT_LIM
ACM_CUSTOMER
ACM_NAME
MAILFROMUSER
MAILSUBJECT
OPERATOR_CODE

The Credit Analyst is notified of a customer return-to-maker payment.
Add Cust Desc

This trigger creates a work unit when a group level customer is added on Customer (AR10).
Service Add Cust Desc (WF05)
Service name Add Cust Desc
Criteria Company (WF05)
Category None
Work Categories None
Prerequisites Customer defaults are set up
Initiating event Adding a Group-level customer
Resolution action
Variables None

A notification email of adding a Group-level customer record is initiated.
The AR09 form and the required keys for inquiry are provided for inquiry, and review of the customer
attributes.
Upd Cust Desc

This trigger creates a work unit when a group level customer is updated on Customer (AR10).
Service Upd Cust Desc
Service name Upd Cust Desc
Criteria Company
Category None
Prerequisites Group-level customer exists
Initiating event Changing a Group-level customer
Resolution action
Variables None

A notification email of changing a Group-level customer record is initiated.
The AR09 form and the required keys for inquiry are provided for inquiry, and review of the customer
attributes.
Upd Customer
This trigger creates a work unit when a company level customer is updated on Customer (AR10).
Service Upd Customer
Service name Upd Customer
Criteria Company
Category None
Prerequisites Company-level customer exists
Initiating event Changing a Company-level customer
Resolution action
Variables None

The customer’s credit analyst is notified via email of a change made to a company-level customer record.
The AR10 form and the required keys for inquiry are provided for the credit analyst to inquire on the customer,
and review the customer attributes.
Employee Expense (EE)
The following services are available in the Employee Expense (EE) application.
• "Employee Advance Approval" on page 52
• "Employee Expense Approval" on page 54
Employee Advance Approval

This trigger creates a work unit when an employee advance for payment is released on Advance Release
(EE35.1) or Mass Employee Release (EE135).
Service EmpAdv Approval
Service name Employee Advance Approval
System Employee Expense (EE)
Object EEASET1

Prerequisites The Workflow field on the Options page of Company

(AP00.4) must be set to Yes. In addition, approval
must be defined on Company Approval (AP00.6) or
Vendor Approval (AP10.7).
TIP Company Approval (AP00.6) can be accessed

on Company (AP00.4), and
Vendor Approval (AP10.7) can be accessed on
Vendor (AP10.1).
Initiating event Releasing an employee advance for payment on

Advance Release (EE35.1) or Mass Employee
Release (EE135).
Resolution action AGS call to set the approval field on AP32.1.
API_CANCEL_SEQ
API_COMPANY
API_INVOICE
API_INVOICE_TYPE
API_OPERATOR
API_OUT_BAL_FLAG
API_PROC_LEVEL
API_SUFFIX
API_TRAN_INV_AMT
API_VENDOR
to Yes, also.
detail lines.
The Department Manager and Vice President are notified that an employee advance needs approval.
1. The Department Manager receives notification that an employee advance needs approval. The
Department Manager takes appropriate action. Possible actions: Approve, Reject, Suspend, and
Hold.
2. If the advance is higher than a predetermined dollar amount, the Vice President receives notification
that an employee advance needs approval. The Vice President takes appropriate action. Possible
actions: Approve, Reject, Suspend, and Hold.
3. The advance request is updated via Workflow Approval Maintenance (AP32.1).
4. If the Department Manager or Vice President rejects the advance, the requester receives an e-mail
notification that the advance request was rejected.
Employee Expense Approval

This trigger creates a work unit when an employee expense for payment is released on Advance Release
(EE35.1) or Mass Employee Release (EE135).
Service EmpExp Approval
Service name Employee Expense Approval
System Employee Expense (EE)
Object EXPSET1

Prerequisites The Workflow field on the Options page of Company

(AP00.4) must be set to Yes. In addition, approval
must be defined on Company Approval (AP00.6) or
Vendor Approval (AP10.7). Company Approval
(AP00.6) can be accessed on Company (AP00.4),
and Vendor Approval (AP10.7) can be accessed on
Vendor (AP10.1).
Initiating event Releasing an employee expense for payment on

Advance Release (EE35.1) or Mass Employee
Release (EE135).
Resolution action AGS call to set the approval field on AP32.1
API_CANCEL_SEQ
API_COMPANY
API_INVOICE
API_INVOICE_TYPE
API_OPERATOR
API_OUT_BAL_FLAG
API_PROC_LEVEL
API_SUFFIX
API_TRAN_INV_AMT
API_VENDOR
to Yes, also.
detail lines.
The Department Manager, Vice President, and Auditor are notified that an employee expense needs approval.
1. The Department Manager receives notification that an employee expense needs approval. The
Department Manager takes appropriate action. Possible actions: Approve, Reject, Send to Vice
President, Suspend, and Hold.
2. Optional. If the Department Manager sends the request to the Vice President, the Vice President
receives notification that the expense needs approval. The Vice President takes appropriate
action. Possible actions: Approve, Reject, Suspend, and Hold.
3. If the Department Manager and, when necessary, the Vice President approve the request, the
Auditor receives notification that the expense needs approval. The Auditor takes appropriate
action. Possible actions: Approve, Reject, Suspend, and Hold.
4. The expense request is updated via Workflow Approval Maintenance (AP32.1).
5. If the Department Manager, Vice President, or Auditor rejects the expense, the requester receives
an e-mail notification that the expense request was rejected.
Chapter 5
Application Triggers and Services for

Supply Chain Management
This chapter provides detailed information about the services in the supply chain management applications.
• "Billing (BL)" on page 57
• "Inventory Control (IC)" on page 60
• "Invoice Matching (MA)" on page 64
• "Order Entry (OE)" on page 72
• "Purchase Order (PO)" on page 83
• "Requisitions (RQ)" on page 100
• "Warehouse (WH)" on page 106
• "Production Order (WO)" on page 114
56 Chapter 5 Application Triggers and Services for LPA and S3 Applications Reference Guide
Billing (BL)
The following services are available in the Billing (BL) application.
• "Electronic Payment Authorization or Settlement Failed" on page 57
• "BL Price Override" on page 58
• "Invoice Batch Release" on page 58
Electronic Payment Authorization or Settlement Failed

This service notifies the Order Processing Manager that a customer order has failed the authorization or
settlement process for electronic payments.
Service EP AuthStl Fail
Service name EP Auth or Settlement Failed
System Order Entry (OE)

Billing (BL)
Criteria Company, Customer
Work Category Order Proc Mgr
Prerequisites No prerequisites are required.
Initiating event Item Speed Entry (OE10), Batch Order Release

(OE110), Invoice Inquiry (BL20), Batch Control
(BL29), Invoice Batch Release (BL120), or Billing
Interface (BL520) try to authorize or settle an
electronic payment, but fail.
Variables EPT_COMPANY
EPT_CUSTOMER
EPT_EP_ACCOUNT
EPT_EP_TYPE
EPT_ERROR_CODE
EPT_INVC_NUMBER
EPT_INVC_PREFIX
EPT_ORDER_NBR
EPT_TRANS_ID
EPT_TRANS_TTL_BASE
EPT_FAIL_AUTH_HOLD
EPT_FAIL_STTL_HOLD
LPA and S3 Applications Reference Guide Chapter 5 Application Triggers and Services for 57
BL Price Override
This service notifies the Order Processing Manager that the calculated price for an order line has been
overridden by a user.
Service BL Price Overrd
Service name BL Price Override
System Billing (BL)
Criteria Company, Process Level, Customer
Initiating event A Change line action in the line price field on Invoice
Entry (BL20.1).
Variables OEI_BATCH_NBR
OEI_CURRENCY_CODE
OEI_CUSTOMER
OEI_PROCESS_LEVEL
OIL_COMPANY
OIL_ENTERED_PRICE
OIL_INVC_NUMBER
OIL_INVC_PREFIX
OIL_ITEM
OIL_LINE_NBR
OIL_LOCATION
OIL_QUANTITY
Invoice Batch Release

This service notifies the Order Processing Manager that an invoice batch has been released.
Service Inv Batch Rel
Service name Invoice Batch Release
System Billing (BL)

Order Entry (OE)
Criteria Company, Batch Nbr
Initiating event A release action on Invoice Entry (BL20), Batch
Control (BL29), Invoice Batch Release (BL120),
Billing Interface (BL520), or Daily Shipment Journal
(OE129).
Variables OIH_BATCH_NBR
OIH_COMPANY
OIH_DTL_QUANTITY
OIH_INV_SOURCE
STATUS_DESC
Inventory Control (IC)
The following services are available in Inventory Control (IC).
• "Bin Update" on page 60
• "Item Location Update" on page 60
• "Item Update" on page 61
• "General Item Location Maintenance" on page 61
• "EAM Item Issued to Work Order" on page 62
• "EAM Item Location Update" on page 63
Bin Update
This trigger creates a work unit when a bin is added or deleted on Bins (IC15).
Service ICBinUpdate
Service name Bin Update
System Inventory Control (IC)
Criteria Company, Location
Initiating event A bin has been added or deleted.
Variables ACTION
COMPANY
LOCATION
BIN
Item Location Update

This trigger creates a work unit when an item location is added or changed on Item Formats (IC10), Item
Location (IC12), or Item Location Load (IC821), or deleted on Item Location (IC12).
Service ItemLocUpdate
Service name Item Location Update
Initiating event An item location has been added, changed, or

deleted.
Variables ACTION
COMPANY
LOCATION
ITEM
Item Update
This trigger creates a work unit when an item is added or changed on Item Formats (IC10), Item Master
(IC11), imported on Item Master Load (IC811), or deleted on Item Master (IC11).
This trigger also creates a work unit when an item is created by Vendor Agreements (PO25), Bid Load to
Contract or Catalog (PO150), or Vendor Price Agreement Import (PO536).
Service ItemUpdate
Service name Item Update
Criteria Item Group
Initiating event An item has been added, changed, or deleted.
Variables ACTION
COMPANY
LOCATION
General Item Location Maintenance

This service creates a work unit when a S3 user successfully adds or updates an item to inventory location
(on Inventory Location (IC12.1)) that is set as an EAM location.
Service Gen_ItemLoc
Service name General Item Location Maintenance
Initiating event An item has been added or changed on IC12.1 and

the location is set as an EAM Location on Location
(IC02.1).
Variables NOTE All fields in the ITEMMAST and ITEMLOC

files.
Related LPA Process
The following process file is delivered with S3 ION Connectors: ION_SyncItemMaster
EAM Item Issued to Work Order

This trigger creates a work unit when an EAM item is issued on Issues (IC21) or Adjustments (IC24).
Service EAM_ ItemIssue
Service name EAM_ ItemIssue
Prerequisites An EAM Location must exist (IC02) with EAM

Location Type = 1 EAM Location.
Initiating event An item is released on Issues (IC21) with a Location

= EAM location and a work number in the EAM Work
Number field.
Variables ACTION
ICT_ITEM
ICT_COMPANY
ICT_COMPONENT_SEQ
ICT_DOCUMENT
ICT_DOC_TYPE
ICT_EAM_OPER_NBR
ICT_EAM_SEQ_NBR
ICT_EAM_WO_NBR
ICT_LINE_NBR
ICT_LOCATION
ICT_SHIPMENT_NBR
ICT_STOCK_QUANTITY
ICT_STOCK_UNIT_COST
ICT_STOCK_UOM
ICT_SYSTEM_CD
ICT_TRANS_DATE
M3_STATUS
SIGN
EAM Item Location Update
This trigger creates a work unit when an EAM item location is added on Item Location (IC12).
Service EAM_ItemLocUpd
Service name EAM_ItemLocUpd

Initiating event An EAM item is added on Item Location (IC12) with

the Location = EAM Location.
Variables ACTION
ITE_ACTIVE_STATUS
ITE_DESCRIPTION
ITE_DESCRIPTION2
ITE_ITEM_GROUP
ITE_STOCK_UOM
ITL_COMPANY
ITL_ITEM
ITL_LOCATION
M3_STATUS
Invoice Matching (MA)
The following services are available in the Invoice Matching (MA) application.
• "Inspection Required" on page 64
• "Reconciliation Invoice Message" on page 65
• "Requisition Item Received" on page 65
• "Purchase Order Cost Message" on page 66
• "Purchase Order Overshipment Message Exists" on page 67
• "No Receipts in Match Pool" on page 68
• "Disapprove Recon Message" on page 69
• "Invoice No Receipt" on page 70
• "EAM PO Release to Work Order / PO Line Close" on page 70
Inspection Required
This trigger creates a work unit when the purchase order receivings are released on PO Receiving (PO30),
Receiving Approval and Release (PO35) or Receipt Interface (MA531).
Service Inspection Req
Service name Inspection Required
System Purchase Order (PO)
Work Category None

purchase order processing, which includes setting
the Inspection Required flag on PO Line Options
(PO20.3) or PO Receiving (PO30.1).
Initiating event Releasing the purchase order receivings on PO

Receiving (PO30), Receiving Approval and Release
(PO35), or Receipt Interface (MA531).
Resolution action Notification
Variables MAILSUBJECT
MAILTOROLE
PRL_COMPANY
PRL_REC_NUMBER

The Receiving Inspector is notified that a shipment needs inspection.
Reconciliation Invoice Message
This trigger creates a work unit when a match has been attempted from the Reconciliation Queue (MA60)
and there are differences between the invoice and the receipt.
Service Recon Invmsg
Service name Reconciliation Invoice Message
System Invoice Matching (MA)
Criteria Company, Auth Code
Work Category None
Valid agents Mail, SMTP
Object APISET1
Prerequisites Set the for Reconciliation Match fields on Company

(MA01.1), Messaging page.
Initiating event Attempting a match from the Reconciliation Queue

(MA60) and there are differences between the
invoice and the receipt.
Resolution action The message is resolved on Invoice Message -

Details (MA66.2). Access MA66.2 to respond to the
Reconciliation Invoice Message. If the message
response is Approve or Chargeback, the Inv
Approval work unit for the Invoice Approval service
is created.
Variables API_CANCEL_SEQ
API_COMPANY
API_INVOICE
API_SUFFIX
API_VENDOR
Requisition Item Received

This trigger creates a work unit each time a requested line item is received on PO Receiving (PO30),
Receiving Approval and Release (PO35), or Receipt Interface (MA531).
Service Req Item Rec
Service name Requisition Item Received
Criteria Company, Location, Requester
Object Key REQSET2
Work Category None
requisition and purchase order processing.
Initiating event Receiving a requested item on PO Receiving (PO30),

Receiving Approval and Release (PO35), or Receipt
Interface (MA531).
Variables MAILNOFOLDER
MAILSUBJECT
PRL_LOCATION
PRL_ITEM
PRL_ORIG_REC_QTY
PLS_SOURCE_DOC_N
PLS_SOURCE_DOC
RQH_REQUESTER
• If several items for the same requester are received and released at the same time, an e-mail notification
is sent to the requester for each of the received items.
• If there are multiple requisition lines on a purchase order line, the service is not initiated.
• All requestors need to be defined as ProcessFlow users.
The requester is notified that the requisition was received through an email with the subject "Requested
item has been received." The Message button contains requester, requisition number, item, received quantity
and unit of measure, and location information.
Purchase Order Cost Message

This service creates a work unit that notifies the buyer when a purchase order cost message has been
created out of the invoice add process.
Service POCostMsg
Service name Purchase Order Cost Message
Work Category
Prerequisites On Company (MA01.1), Messaging page, the PO

Cost and Workflow fields must be set to Yes.
Initiating event A match invoice is entered and the invoice unit cost
and the PO unit cost are not the same. Match
invoices are entered on the Invoice Line Detail
(MA43) forms and Invoice Interface (MA540).
Resolution action The message is resolved on Purchase Order Cost
Review Message (MA66.3). Access MA66.3 to
respond to the PO Cost Message.
If you are using the Accept action on MA66.3, the
invoice will not complete match via Auto Matching
(MA126). You will need to processed the invoice via
Detail Level Match (MA60.3). Once the select and
match via MA60.3 is complete, the Inv Approval work
unit for the Invoice Approval service is created.
If you are using the Adjust action on MA66.3 to adjust
the invoice cost, the invoice will match via Auto
Matching (MA126) (assuming there are no further
discrepancies) and the Inv Approval work unit for the
Invoice Approval service is created. (You could also
use MA60.3 to match. The Inv Approval work unit
would be created.)
NOTE If you are also using the Reconciliation Invoice

Message service, and the match creates a
reconciliation invoice message, then the Inv Approval
work unit for the Invoice Approval service is NOT
created. Instead, the Recon Invmsg work unit for the
Reconciliation Invoice Message services only is
created. When the reconciliation message is
responded to on Invoice Message - Details (MA66.2),
then the Inv Approval work unit for the Invoice
Approval service is created. If the match does not
create a reconciliation invoice message, the Invoice
Approval service is triggered as stated above.
Variables API_CANCEL_SEQ
API_COMPANY
API_INVOICE
API_SUFFIX
API_VENDOR
API_PO_NUMBER
API_AUTH_CODE
Purchase Order Overshipment Message Exists

This trigger creates a work unit when a buyer message is created by reporting excess goods on PO Receiving
(PO30) or Receipt Interface (MA531).
Service PO Overshipment
Service name PO Overshipment Message Exists
Criteria Company
Object Key BUYSET1
Work Category Buyer Code

Data string = [buyer code]
Prerequisites Messaging must be set on the PO Company Setup

(PO01.1) (on the Receiving page, the Disable
Overshipment Message field must be set to No).
Initiating event Creating a buyer message by reporting excess goods

on PO Receiving (PO30) or Receipt Interface
(MA531).
MAILTO
POM_COMPANY
POM_DOC_NBR_NUM
POM_LINE_NBR
POM_REC_NUMBER

The Buyer is notified that more goods were received than were ordered.
No Receipts in Match Pool

This trigger creates a work unit when attempting a match on Invoice Line Detail-PO (MA43), Auto Matching
(MA126), Invoice Interface (MA540), Receipt Interface (MA531), ERS Invoice Creation, or Invoice Entry
(AP20) when there are no corresponding receipts in the same match pool, and the invoice date or discount
date is within the number of “No Receipt” days.
Service NoRcptInPool
Service name No Receipts in Match Pool
Criteria Company, Process Level, Vendor
Category Authority Code

Object APOBJ2
Prerequisites Set flag for No Receipt field under Additional

Workflow Options on Company (MA01.1), Messaging
tab.
Initiating event Attempting a match on Invoice Line Detail - PO
(MA43), Auto Matching (MA126), Invoice Interface
(MA540), Receipt Interface (MA531), ERS Invoice
Creation, or Invoice Entry (AP20) when there are no
corresponding receipts in the same match pool.
Resolution action
Possible flow sequence The Accounts Payable Clerk is notified when there
are no corresponding receipts in the same match
pool and the invoice date or discount date is within
the number of “No Receipt” days.
API_CANCEL_SEQ
API_COMPANY
API_INVOICE
API_INVOICE_TYPE
API_OPERATOR
API_OUT_BAL_FLAG
API_PROC_LEVEL
API_SUFFIX
API_TRAN_INV_AMT
API_VENDOR
Disapprove Recon Message

This trigger creates a work unit that notifies a person or a group that a reconciliation message has been
disapproved and that some action needs to be taken.
Service MsgDisapprove
Service name Disapprove Recon Msg
System Matching (MA)
Criteria Company
Object MAGSET1
Prequisites An invoice is created on AP20, and a reconciliation

message is created during matching.
Initiating event The Auth Code/Buyer disapproves a reconciliation

message on MA66.
Variables MAG_CANCEL_SEQ
MAG_COMPANY
MAG_INVOICE
MAG_MAD_SEQ_NBR
MAG_SEQ_NBR
MAG_SUFFIX
MAG_VENDOR
Invoice No Receipt
This trigger creates a work unit when an invoice exists and is ready to match, but there is either no receipt,
or the invoice quantity is greater than the receipt quantity.
Service InvNoReceipt
Service name Invoice No Receipt
System Matching (MA)
Prerequisites An invoice is entered on Basic Invoice (AP20.1).
EAM PO Release to Work Order / PO Line Close

This trigger creates a work unit when an EAM purchase order is released on Purchase Order Entry (PO20),
Authorization, Release (PO22), Purchase Order Worksheet (PO23), or Purchase Order Interface from
Lawson Applications (PO100) or when an EAM purchase order is closed on PO Receiving (PO30), Receiving
Adjustment (PO33), or invoice matching Reconciliation Queue (MA60).
Service EAM_PORelease
Service name EAM_PORelease
System Purchase Order (PO), Invoice Matching (MA)

An EAM Vendor Class must exist (AP00.3) with EAM
Vendor Flag = Yes.
The Purchase Order has a value in the EAM Work
Order field.
Initiating event A purchase order is released or closed and it has an

EAM ship to location, a value in the EAM Work Order
number field, and EAM Vendor class.
Variables ACTION
M3_STATUS
PLI_COMPANY
PLI_EAM_OPER_NBR
PLI_EAM_SEQ_NBR
PLI_EAM_WO_NBR
PLI_ITEM
PLI_LINE_NBR
PLI_PO_CODE
PLI_PO_NUMBER
PLI_PO_RELEASE
PLI_STOCK_QUANTITY
PLI_STOCK_UNIT_COST
PLI_STOCK_UOM
Order Entry (OE)
The following services are available in the Order Entry (OE) application.
• "Customer Order Hold" on page 72
• "Customer Order Line Hold" on page 73
• "Customer Order Canceled" on page 74
• "Customer Order Credit Check Fail" on page 75
• "Customer Order Released" on page 75
• "Customer Order Return Created" on page 76
• "Customer Quote" on page 77
• "Electronic Payment Authorization or Settlement Failed" on page 78
• "Invoice Batch Release" on page 79

• "OE Price Override" on page 80
• "Order Entry Backorder" on page 80
• "WH Priority Override" on page 81
Customer Order Hold

This trigger creates a work unit when a customer order is placed on hold on Item Speed Entry (OE10).
Service Cstord Hold
Service name Customer Order Hold
Work Category None
Prerequisites No prerequisites are required other than normal order

entry processing, which includes the existence of a
customer order.
Initiating event Placing a customer order on hold on Item Speed

Entry (OE10).
Variables COR_BILL_NAME
COR_COMPANY
COR_CUSTOMER
COR_ENTERED_DISC
COR_FRT_CHG_CURR
COR_HOLD_CODE
COR_INV_GDS_CURR
COR_MISC_TTL_CURR
COR_NI_GDS_CURR
COR_ORDER_DATE
COR_ORDER_TYPE
COR_ORD_DISC_CURR
COR_SHIP_TO
COR_SHIP_TO_NAME
COR_STATUS
HDD_DESCRIPTION
MAILFROMUSER
MAILSUBJECT
MAILTOROLE
OEC_NAME
OTP_DESCRIPTION

The Order Processing Manager is notified that a customer order was placed on hold.
Customer Order Line Hold

This service notifies the Order Processing Manager that an order line has been put on hold.
Service Cstord Ln Hold
Service name Customer Order Line Hold
Initiating event A hold code is manually added to a released order

line using the Item Entry forms (OE10), or the system
applies a hold cold to an order line.
Variables COL_COMPANY
COL_CUSTOMER
COL_CUST_SHIP_TO
COL_HOLD_CODE
COL_ITEM
COL_LINE_NBR
COL_ORDER_NBR
COL_INV_LOCATION
COL_OPR_CODE
COL_PROCESS_LEVEL
Customer Order Canceled

This trigger creates a work unit when a customer order is canceled on Item Speed Entry (OE10).
Service Cstord Canceled
Service name Customer Order Canceled


customer order.
Initiating event Canceling a customer order on Item Speed Entry

(OE10).
Variables COR_COMPANY
COR_CUSTOMER
COR_OPEN_ORD_AMT
COR_ORDER_NBR
MAILTOUSER

The Order Processing Manager is notified that a customer order was canceled.
Customer Order Credit Check Fail
This trigger creates a work unit when a credit check fails in the credit check process.
Service Credit Chk Fail
Service name Customer Order Credit Check Fail

Data string = [credit analyst code]

non-Cash on Delivery order with the order amount
greater than the single order limit.
Initiating event Failing a credit check in the credit check process.

Credit checks occur when an order is released on
Item Speed Entry (OE10) or Batch Order Release
(OE110), when a released order is changed on Item
Speed Entry (OE10), and when the pick list is run
on Pick List Print (WH130).
Variables COR_COMPANY
COR_CUSTOMER
COR_OPEN_ORD_AMT
COR_ORDER_NBR
MAILTOUSER
Possible process flow sequences

The Credit Analyst or Credit Supervisor is notified that the credit check for a customer order failed, and the
order is on hold. For example:
1. The Credit Supervisor receives notification to review the order and takes appropriate action.
Possible actions are Approve and Reject.
2. The customer order is updated on Item Speed Entry (OE10).
Customer Order Released

This trigger creates a work unit when a customer order is released on Item Speed Entry (OE10) or Batch
Order Release (OE110).
Service Cstord Released
Service name Customer Order Released
Work Category None

customer order.
Initiating event Releasing a customer order on Item Speed Entry

(OE10) or Batch Order Release (OE110).
COR_COMPANY
COR_CUSTOMER
COR_ENTERED_DISC
COR_FRT_CHG_CURR
COR_INV_GDS_CURR
COR_MISC_TTL_CURR
COR_NI_GDS_CURR
COR_ORDER_DATE
COR_ORDER_NBR
COR_ORDER_TYPE
COR_ORD_DISC_CURR
COR_SHIP_TO
COR_SHIP_TO_NAME
MAILFROMUSER
MAILSUBJECT
MAILTOROLE
OEC_NAME
OTP_DESCRIPTION

The Order Processing Manager is notified that a customer order was released.
Customer Order Return Created

This service notifies the Order Processing Manager that a return authorization number was created.
Service Cstord Return
Service name Customer Order Return Created
Criteria Company, Process Level, Location
Prerequisites No prerequisites required.
Initiating event A release form action on the Return (OE30) forms.
Variables RTN_AUTH_NO
RTN_COMPANY
RTN_CUSTOMER
RTN_INVC_NUMBER
RTN_INVC_PREFIX
RTN_LOCATION
RTN_PROCESS_LEVEL
Customer Quote
This trigger creates a work unit when a customer quote is added on Item Speed Entry (OE10).
Service Cstord Quote
Service name Customer Quote
Work Category None

customer order.
Initiating event Adding a customer quote on Item Speed Entry

(OE10).
COR_COMPANY
COR_CUSTOMER
COR_ENTERED_DISC
COR_FRT_CHG_CURR
COR_INV_GDS_CURR
COR_MISC_TTL_CURR
COR_NI_GDS_CURR
COR_ORDER_DATE
COR_ORDER_NBR
COR_ORDER_TYPE
COR_ORD_DISC_CURR
COR_SHIP_TO
COR_SHIP_TO_NAME
MAILFROMUSER
MAILSUBJECT
MAILTOROLE
OEC_NAME
OTP_DESCRIPTION

The Order Processing Manager is notified that a customer quote was created.
Electronic Payment Authorization or Settlement Failed

This service notifies the Order Processing Manager that a customer order has failed the authorization or
settlement process for electronic payments.
Service EP AuthStl Fail
Service name EP Auth or Settlement Failed

Billing (BL)
Criteria Company, Customer
Initiating event Item Speed Entry (OE10), Batch Order Release
(OE110), Invoice Inquiry (BL20), Batch Control
(BL29), Invoice Batch Release (BL120), or Billing
Interface (BL520) try to authorize or settle an
electronic payment, but fail.
Variables EPT_COMPANY
EPT_CUSTOMER
EPT_EP_ACCOUNT
EPT_EP_TYPE
EPT_ERROR_CODE
EPT_INVC_NUMBER
EPT_INVC_PREFIX
EPT_ORDER_NBR
EPT_TRANS_ID
EPT_TRANS_TTL_BASE
EPT_FAIL_AUTH_HOLD
EPT_FAIL_STTL_HOLD
Invoice Batch Release

This service notifies the Order Processing Manager that an invoice batch has been released.
Service Inv Batch Rel
Service name Invoice Batch Release
System Billing (BL)

Order Entry (OE)
Criteria Company, Batch Nbr
Initiating event A release action on Invoice Entry (BL20), Batch

Control (BL29), Invoice Batch Release (BL120),
Billing Interface (BL520), or Daily Shipment Journal
(OE129).
Variables OIH_BATCH_NBR
OIH_COMPANY
OIH_DTL_QUANTITY
OIH_INV_SOURCE
STATUS_DESC
OE Price Override
This service notifies the Order Processing Manager that the calculated price for an order line has been
overridden by a user.
Service OE Price Overrd
Service name OE Price Override
Initiating event A Change line action in the line price field on the
Item Entry (OE10) forms.
Variables COL_COMPANY
COL_CUSTOMER
COL_ENTERED_PRICE
COL_ITEM
COL_LINE_NBR
COL_ORDER_NBR
COL_ORDER_QTY
COL_CHG_OPR
COL_CURRENCY_CODE
COL_INV_LOCATION
COL_OPR_CODE
COL_PROCESS_LEVEL
Order Entry Backorder

This service notifies the Order Processing Manager that a customer order has failed to allocate completely.
Service OE Backord Line
Service name Order Entry Backorder
Prerequisites The billing company must be set up for online

allocation.
Initiating event Item Entry forms (OE10) tried to allocate goods to

an order line but failed.
Variables COMPANY
PROCESS_LEVEL
CUSTOMER_NUMBER
ORDER_NUMBER
ORDER_LINE_NUMBER
ITEM
LOCATION
BACKORDER_QTY
BILL_TO
SHIP_TO
ORDER_DATE
EXPECTED_SHIP_DATE
REQUESTED_DATE
ORDER_STATUS
KIT_FLAG
WH Priority Override
This service notifies the Order Processing Manager that the allocation priority for warehouse demand has
been changed.
Service WH Prior Overid
Service name WH Priority Override

Warehouse (WH)
Object Key WDMSET1
Initiating event A change form action on the Item Entry (OE10) forms
or the Allocation (WH20) forms to alter the allocation
priority of an order line.
Variables COR_OPR_CODE
COR_SHIP_TO_NAME
OEC_NAME
REQ_REQUESTER
WDM_CUSTOMER
WDM_ALLOC_PRI
WDM_COMPANY
WDM_COMPONENT_SEQ
WDM_DESTINATION
WDM_DOC_NBR
WDM_DOC_NBR_NUM
WDM_ITEM
WDM_ITEM_DESC
WDM_LINE_NBR
WDM_LOCATION
WDM_QUANTITY
WDM_STATUS
WDM_SYSTEM_CD
Purchase Order (PO)
The following services are available in the Purchase Order (PO) application.
• "Activity Budget Exceeded" on page 83
• "Inspection Required" on page 84
• "Inspection Item Rejected" on page 85
• "Purchase Order Overshipment Message Exists" on page 85
• "Purchase Order Overshipment Message Cleared" on page 86
• "Requisition Item Received" on page 87
• "PO Vendor Agreement Notify" on page 88
• "Subcontractor PO Approval" on page 88
• "EDI Purchase Order Acknowledgment" on page 89

• "EDI PO Acknowledgement Buyer Notification" on page 91
• "PO Cost Discrepancy" on page 91
• "P-Card Request" on page 92
• "P-Card Charge Approval" on page 92
• "P-Card Charge Activation" on page 93
• "P-Card Charge Dispute" on page 94
• "P-Card Charge Rejected" on page 94
• "P-Card Charge Released" on page 95
• "P-Card Rejection" on page 96
• "PO Delivery Ticket Select" on page 96
• "General PO Maintenance" on page 97
• "General PO Receipt" on page 97
• "EAM PO Release to Work Order / PO Line Close" on page 98
Activity Budget Exceeded

This trigger creates a work unit when a requisition or purchase order is created with an activity assigned
that exceeds the budget limit on Purchase Order (PO20).
Service ActBudgetExc
Service name Activity Budget Exceeded
System Purchase Order (PO)/Requisition (RQ)
Work Category None

purchase order or requisition processing.
Initiating event Creating a requisition or purchase order with an

activity assigned that exceeds the budget limit on
Purchase Order (PO20).
MMD_ACCT_CATEGORY
MMD_ACTIVITY
MMD_DIST_COMPANY
PLI_COMPANY
PLI_LINE_NBR
PLI_PO_CODE
PLI_PO_NUMBER
PLI_PO_RELEASE

The Activity owner is notified when the assignment of an activity to a requisition line or purchase order line
causes a potential over-budget situation.
Inspection Required
This trigger creates a work unit when the purchase order receivings are released on PO Receiving (PO30),
Receiving Approval and Release (PO35) or Receipt Interface (MA531).
Service Inspection Req
Service name Inspection Required
Work Category None

the Inspection Required flag on PO Line Options
(PO20.3) or PO Receiving (PO30.1).
Initiating event Releasing the purchase order receivings on PO

Receiving (PO30), Receiving Approval and Release
(PO35), or Receipt Interface (MA531).
MAILTOROLE
PRL_COMPANY
PRL_REC_NUMBER

The Receiving Inspector is notified that a shipment needs inspection.
Inspection Item Rejected

This trigger creates a work unit when an item on Inspection Accept or Reject (PO34.1) is rejected.
Service Inspection Rej
Service name Inspection Item Rejected
Work Category None

the Inspection Required flag on Item Location
(IC12.1), PO Line Options (PO20.3), or PO Receiving
(PO30.1).
Initiating event Rejecting an item on Inspection Accept or Reject

(PO34.1).
MAILSUBJECT
MAILTO
PRL_COMPANY
PRL_LINE_NBR
PRL_REC_NUMBER

The Buyer is notified that a received item was rejected.
Purchase Order Overshipment Message Exists

This trigger creates a work unit when a buyer message is created by reporting excess goods on PO Receiving
(PO30) or Receipt Interface (MA531).
Service PO Overshipment
Service name PO Overshipment Message Exists
Criteria Company
Object Key BUYSET1

Data string = [buyer code]
Prerequisites Messaging must be set on the PO Company Setup

(PO01.1) (on the Receiving page, the Disable
Overshipment Message field must be set to No).
Initiating event Creating a buyer message by reporting excess goods

on PO Receiving (PO30) or Receipt Interface
(MA531).
MAILTO
POM_COMPANY
POM_DOC_NBR_NUM
POM_LINE_NBR
POM_REC_NUMBER

The Buyer is notified that more goods were received than were ordered.
Purchase Order Overshipment Message Cleared

This trigger creates a work unit when a buyer message is released on Buyer Message - Receiving (PO52)
Service Overship Clrd
Service name PO Overshipment Message Clrd
Work Category None

purchase order processing.
Initiating event Releasing a buyer message on Buyer Message -

Receiving (PO52).
Special considerations If more than one buyer message exists, all messages
must be released.
MAILTO
PRL_COMPANY
PRL_REC_NUMBER

The receiving clerk is notified that the Buyer approved an overshipment.
Requisition Item Received

This trigger creates a work unit each time a requested line item is received on PO Receiving (PO30),
Receiving Approval and Release (PO35), or Receipt Interface (MA531).
Service Req Item Rec
Service name Requisition Item Received
Criteria Company, Location, Requester
Object Key REQSET2
Work Category None

requisition and purchase order processing.
Initiating event Receiving a requested item on PO Receiving (PO30),

Receiving Approval and Release (PO35), or Receipt
Interface (MA531).
MAILSUBJECT
PRL_LOCATION
PRL_ITEM
PRL_ORIG_REC_QTY
PLS_SOURCE_DOC_N
PLS_SOURCE_DOC
RQH_REQUESTER
• If several items for the same requester are received and released at the same time, an e-mail notification
is sent to the requester for each of the received items.
• If there are multiple requisition lines on a purchase order line, the service is not initiated.
• All requestors need to be defined as ProcessFlow users.
The requester is notified that the requisition was received through an email with the subject "Requested
item has been received." The Message button contains requester, requisition number, item, received quantity
and unit of measure, and location information.
PO Vendor Agreement Notify

This trigger creates a work unit when a PO is released in Purchase Order Entry (PO20.1), PO Interface from
Lawson (PO100), PO Worksheet (PO23), or PO Interface from Non-Lawson (PO520).
Service PO Agrmt Max
Service name Vendor Agreement Notification
Criteria Procurement Group, Vendor Agreement Reference
Object PVHSET1
Work Category Procurement Grp
Prerequisites An agreement must be set up. On the agreement,

there must be an Admin, a notification percent, and
a lifetime maximum amount. (Setup the Admin on
Contacts (PO07)). The admin's e-mail address is
required.)
Initiating event Releasing a PO in Purchase Order Entry (PO20.1),

PO Interface from Lawson (PO100), PO Worksheet
(PO23), or PO Interface from Non-Lawson (PO520).
MAILSUBJECT
MAILTO
PVH_PROCURE_GROUP
PVH_VEN_AGRMT_REF

The user is notified when the amount ordered on the agreement divided by the agreement maximum amount
equals or exceeds the percent entered in the Notification Percent field under the Header Defaults and Amts
tab on Vendor Agreement (PO25.1).
Subcontractor PO Approval
When a subcontractor purchase order is released, this service creates a work unit to approve purchase
orders for grant subcontractors.
IMPORTANT The subcontractor PO approval service is for Grant Management (GM) users only.
Service PO Approved
Service name Subcontractor PO Approval
Criteria Company, PI
Work Category PI-CONCATENATED
Prerequisites The vendor must be set up as a subcontractor in

Grant Management.
The PO must contain activities, and the activities
must be associated to a PI (Principal Investigator).
The PO must be set up as a subcontractor PO.
Initiating event Releasing a purchase order on Purchase Order

(PO20).
Resolution action AGS call to set the Approval field on Direct Approval
(PO24.1).
Variables PCR_COMPANY
PCR_PO_CODE
PCR_PO_NUMBER
PCR_PO_RELEASE
PCR_PURCH_FR_LOC
PCR_VENDOR
EDI Purchase Order Acknowledgment

This trigger creates a work unit when Transmitted PO Acknowledgment (PO122) is run.
Service EDIPOAckNotify
Service name EDI PO Acknowledgment
Criteria Company, Buyer
Work Category None
Prerequisites No prerequisites are required other than normal EDI

setup and purchase order processing.
Initiating event Running Transmitted PO Acknowledgment (PO122).
COR_CUSTOMER
COR_OPR_CODE
COR_ORDER_DATE
COR_ORDER_NBR
COR_ORDER_TYPE
COR_SHIP_NAME
COR_SHIP_TO
MAILFROMUSER
MAILSUBJECT
MAILTO
MAILTOUSER
OEC_NAME
OTP_DESCRIPTION
SHIP_LINE_ACTION
WHA_COMPANY
WHA_LINE_NBR
WHA_QUANTITY
WHA_SHIPMENT_NBR
WHA_STATUS
WHL_DESCRIPTION
WHL_ITEM

Buyers are notified when acknowledgments are processed against their purchase orders and a separate
copy is created of the discrepancy report for each buyer within a company. The copy contains only the
acknowledgments for that buyer and company.
• The report distribution parameters can be set up to distribute the report to either the buyers or the buyers'
printers. All reports must be distributed in the same manner.
• If there is inaccurate data in the Company or Buyer fields, or if a buyer is not set up in the Workflow
system, the PO EDI Coordinator receives an e-mail notification. The notification directs the coordinator
to review the full discrepancy report and informs the coordinator that a buyer copy was not distributed.
Setup requirement: For this flow sequence to work properly, a Distribution Group should be assigned
to the job so the person with the task of PO EDI Coord can see the report in his or her Print Manager.
For information on setting up EDI acknowledgments, including running Transmitted PO Acknowledgment
(PO122), see the Lawson EDI Standard and EDI Professional for Supply Chain Management User
Guide.
EDI PO Acknowledgement Buyer Notification
This trigger creates a work unit when an invoice is added on Invoice Detail Line-PO (MA43.1), Invoice Entry
(AP20), or Invoice Interface (MA540) and there is a PO cost discrepancy.
Service BuyerNotify
Service name TransmitPOAck
Criteria Company, Buyer Code
Work Category None
Type E-mail
Prerequisites None other than normal EDI setup and purchase

order processing
Initiating event PO EDI Acknowledgment Report (PO122)
Variables Company
Buyer Code
Buyer E-mail
PO Cost Discrepancy
This trigger creates a work unit when an invoice is added on Invoice Detail Line-PO (MA43.1), Invoice Entry
(AP20), or Invoice Interface (MA540) and there is a PO cost discrepancy.
Service PO Discrepancy
Service name PO Cost Discrepancy

Type E-mail
Objects ATRSET1
Roles None
Prerequisites Set flag for PO Cost field on Company (MA01.1)

, Messaging tab.
Initiating event Adding an invoice on Invoice Detail Line-PO

(MA43.1),Invoice Entry (AP20), or Invoice Interface
(MA540), and the invoice detail unit costs do not
match PO line costs.
API_CANCEL_SEQ
API_COMPANY
API_INVOICE
API_INVOICE_TYPE
API_OPERATOR
API_OUT_BAL_FLAG
API_PROC_LEVEL
API_SUFFIX
API_TRAN_INV_AMT
API_VENDOR
P-Card Request
This trigger notifies the purchasing card administrator that a purchasing card has been requested.
Service P-Card Request
Service name P-Card Request
System Purchase Order
Criteria Program
Work Category P-Card Admin
Prerequisites None
Initiating event New card request released.
Variables PROGRAM
REQUEST_ID
USER_ID
CARDHOLDER_NAME
EMAIL
PROXY_EMAIL
P-Card Charge Approval

This trigger notifies the purchasing card administrator that a charge was approved by the cardholder.
Service ChargeApproved
Service name P-Card Charge Approval
Criteria Program, Card Number
Work Category P-Card Admin
Prerequisites None
Initiating event Line change action with new status=A.
Variables ADMIN_EMAIL
AMOUNT
CARD_NUMBER
CHARGE_TYPE
COMPANY
DATE
MERCHANT
PO_NUMBER
PROGRAM
REASON_CD
STATEMENT
TRANSACTION_ID
USER_NAME
P-Card Charge Activation

This trigger notifies the purchasing cardholder that his or her card has been activated.
Service P-Card Activate
Service name P-Card Activation
Criteria Program
Work Category Buyer, Requester
Prerequisites None
Initiating event Card status changed from Approved to Activated.
Variables PROGRAM
REQUEST_ID
USER_ID
CARDHOLDER_NAME
EMAIL
PROXY_EMAIL
P-Card Charge Dispute

This trigger notifies the user that a Change action was performed and a line status changed to "Disputed."
Service ChargeDispute
Service name P-Card Charge Dispute
Criteria Program
Prerequisites None
Initiating event Card status changed from Unapproved to Rejected.
Variables COMPANY
EMAIL
ITEM_CHARGE
MERCHANT
PCARD_NBR
PO_NUMBER
PROGRAM
REASON_CODE
STATEMENT
TRAN_DATE
TXN_NBR
USER NAME
P-Card Charge Rejected

This trigger notifies the purchasing card holder that a charge was rejected by the administrator.
Service ChargeRejected
Service name P-Card Charge Rejected
Criteria Program, Card Number
Work Category P-Card Cardholder
Prerequisites None
Initiating event Line change action with new status=Rejected.
Variables COMPANY
EMAIL
ITEM_CHARGE
MERCHANT
PCARD_NBR
PO_NUMBER
PROGRAM
REASON_CODE
STATEMENT
TRAN_DATE
TXN_NBR
USER NAME
P-Card Charge Released

This trigger notifies the cardholder via email that procurement card charges have been released and are
ready for approval by the cardholder. Only one email is created for all the credit card's charges.
Service ChargeReleased
Service name P-Card Charge Released
Criteria Program, Pcard number
Work Category None
Prerequisites Procurement card setup is complete
Initiating event When charge records are set to "released" status

on P-Card Invoice and Release (PD130), and the
credit card program is set up for manual approvals.
Variables PXD-PROGRAM
PXD-INVOICE
PXD-PCARD-NBR
PXD-INVOICE-DATE
P-Card Rejection
This trigger notifies the purchasing cardholder that his or her card has been rejected.
Service P-Card Reject
Service name P-Card Rejection
Criteria Program
Prerequisites None
Initiating event Card status changed from Unapproved to Rejected.
Variables PROGRAM
REQUEST_ID
USER_ID
CARDHOLDER_NAME
EMAIL
PROXY_EMAIL
PO Delivery Ticket Select

This trigger creates a work unit for each receipt line when a purchase order is received and delivered.
Service PODelivery
Service name PO Delivery Ticket Select
Criteria Company, Origin Code, Rqsrc Machine
Initiating event Delivery / Putaway ticket printed via PO30 or PO134
Variables PRL_COMPANY
PRL_REC_NUMBER
PRL_LINE_NBR
PRL_ENT_UNIT_CST
PRL_STOCK_QTY
PRL_STOCK_UOM
General PO Maintenance
This service creates a work unit when a user or the system creates or updates a purchase order (via Purchase
Order Interface From Lawson Applications (PO100) or Purchase Order Worksheet (PO23)) and the purchase
order is released on PO Entry (PO20), Authorization, Release (PO22), Purchase Order Worksheet (PO23),
or Purchase Order Interface From Lawson Applications (PO100).
Service Gen_PurchaseOrd
Service name General PO Maintenance
Criteria Company, Location, Buyer
Initiating event A PO is created or updated on PO100 or PO23 and

released on PO100, PO20, PO22, or PO23.
Variables NOTE All fields in the PURCHORDER and POLINE

files.
Related LPA Process

The following process file is delivered with S3 ION Connectors: ION_SyncPurchaseOrder
General PO Receipt
This service creates a work unit when a S3 user releases or updates a purchase order receipt on PO
Receiving (PO30).
Service Gen_POReceive
Service name General PO Receipt
Criteria Company
Initiating event A PO receipt is created or updated on PO30.
Variables NOTE All fields in the PORECEIVE and PORECLINE
files.
Related LPA Process

The following process file is delivered with S3 ION Connectors: ION_SyncReceiveDelivery
EAM PO Release to Work Order / PO Line Close

This trigger creates a work unit when an EAM purchase order is released on Purchase Order Entry (PO20),
Authorization, Release (PO22), Purchase Order Worksheet (PO23), or Purchase Order Interface from
Lawson Applications (PO100) or when an EAM purchase order is closed on PO Receiving (PO30), Receiving
Adjustment (PO33), or invoice matching Reconciliation Queue (MA60).
Service EAM_PORelease
Service name EAM_PORelease
System Purchase Order (PO), Invoice Matching (MA)

An EAM Vendor Class must exist (AP00.3) with EAM
Vendor Flag = Yes.
The Purchase Order has a value in the EAM Work
Order field.
Initiating event A purchase order is released or closed and it has an

EAM ship to location, a value in the EAM Work Order
number field, and EAM Vendor class.
Variables ACTION
M3_STATUS
PLI_COMPANY
PLI_EAM_OPER_NBR
PLI_EAM_SEQ_NBR
PLI_EAM_WO_NBR
PLI_ITEM
PLI_LINE_NBR
PLI_PO_CODE
PLI_PO_NUMBER
PLI_PO_RELEASE
PLI_STOCK_QUANTITY
PLI_STOCK_UNIT_COST
PLI_STOCK_UOM
Requisitions (RQ)
The following services are available in the Requisitions (RQ) application.
• "Rush Item" on page 100
• "Requisition Approval" on page 101
• "Create Line Approval" on page 102
• "Requisition Line Approval" on page 103
• "Requisition Line Approval GM" on page 104
Rush Item
This trigger creates a work unit when rush processing is requested on RequisitionRequisition (RQ10).
Service Rush Item
Service name Rush Item
System Requisitions (RQ)
Criteria Company, Location, Buyer
Prerequisites The following conditions must exist to allow rush

processing:
• There is a buyer on the Requisition.
• The requisition is released and approved.
• The line priority is 1 (one).
• The Create PO flag is set to Yes.
Initiating event Requesting rush processing on

RequisitionRequisition (RQ10).
Variables BUYER_EMAIL_ADDRESS
RLN_BUYER
RLN_COMPANY
RLN_DESCRIPTION
RLN_ENTERED_UOM
RLN_ITEM
RLN_LINE_NBR
RLN_PURCH_FR_LOC
RLN_QUANTITY
RLN_REQ_DEL_DATE
RLN_REQ_NUMBER
RLN_VENDOR

The Buyer or the Purchasing Manager is notified that a request needs rush processing.
Requisition Approval
This trigger creates a work unit when a requisition is released.
Service Req Approval
Service name Requisition Approval
Object Key REQSET2, RLNSET1,RQHSET1
Work Category Req Loc

Data string = [requisition location]
Prerequisites None required other than normal requisition

processing.
Initiating event Releasing a requisition.
Resolution action Creates new work units.
Variables REQ_NAME
RQH_ALLOC_PRI
RQH_QUOTE_FL
RQH_APPROVAL_VAL
RQH_BUYER_CODE
RQH_COMPANY
RQH_I_TOTAL
RQH_N_TOTAL
RQH_PO_USER_FLD_3
RQH_REQUESTER
RQH_REQ_LOCATION
RQH_REQ_NUMBER
RQH_X_S_TOTAL
Email must be configured in the browser to allow the Reject or Unrelease actions to be taken.
NOTE This action can still be taken but no email will be received if there is not an email address configured
for the user.
Create Line Approval

When a requisition is released, this trigger creates a work unit that will call one of two requisition line level
approval services – one for Grant Management, one for non-Grant Management users.
Before you start You must enable ALL THREE line approval services (RQCreateLnApprv, then
ReqLineApproval and ReqLineApprvGM) in order for requisition line approvals to work.
Service RQCreateLnApprv
Service name Create Line Approval
Prerequisites None required other than normal requisition

processing.
Resolution action AGS call to set the Approval field on Direct Line
Approval (RQ13.2).
Variables APPROVAL_VAL
REQ_NAME
RQH_ALLOC_PRI
RQH_APPROVAL_VAL
RQH_COMPANY
RQH_REQUESTER
RQH_REQ_LOCATION
RQH_REQ_NUMBER
Requisition Line Approval

When a requisition is released, the Create Line Approval service creates a work unit that will call one of two
requisition line level approval services – one for Grant Management users, one for non-Grant Management
users. If you do not use Grant Management, this is the service that will be called. This service creates a
work unit to approve requisitions at the line level.
Service ReqLineApproval
Service name Requisition Line Approval
Prerequisites The create line approval (RQCreateLnApprv) and

line approval for GM (ReqLineApprvGM) services
must be enabled.
Approval (RQ13.2).
Variables MMD_ACCOUNT
MMD_ACCT_CATEGORY
MMD_ACCT_UNIT
MMD_ACTIVITY
MMD_SUB_ACCT
RLN_ALLOC_PRI
RLN_APPROVAL_VAL
RLN_COMPANY
RLN_ITEM
RLN_ITEM_TYPE
RLN_LINE_NBR
RLN_REQ_LOCATION
RLN_REQ_NUMBER
Requisition Line Approval GM

When a requisition is released, the Create Line Approval service creates a work unit that will call one of two
requisition line level approval services – one for Grant Management users, one for non-Grant Management
users. If you use Grant Management, this is the service that will be called. This service creates a work unit
to approve requisitions at the line level.
Service ReqLineApprvGM
Service name Requisition Line Approval GM
Criteria Company, PI
Work Category PI-CONCATENATED
Prerequisites The create line approval (RQCreateLnApprv) and

line approval (ReqLineApproval) services must be
enabled.
Approval (RQ13.2).
Variables MMD_ACCOUNT
MMD_ACCT_CATEGORY
MMD_ACCT_UNIT
MMD_ACTIVITY
MMD_SUB_ACCT
RLN_ALLOC_PRI
RLN_APPROVAL_VAL
RLN_COMPANY
RLN_ITEM
RLN_ITEM_TYPE
RLN_LINE_NBR
RLN_REQ_LOCATION
RLN_REQ_NUMBER
Warehouse (WH)
The following services are available in the Warehouse (WH) application.
• "Warehouse Backorder" on page 106
• "WH Demand Cancellation" on page 107
• "WH Priority Override" on page 108
• "WH Shipment Batch Creation" on page 109
• "WH Shipment Creation" on page 110
• "Shipment Release" on page 110
• "Shipment Backordered or Voided" on page 111
• "EAM Shipment Release" on page 112
Warehouse Backorder
This service notifies the Order Processing Manager that a customer order line has been backordered.
Service WH Backord Line
Service name Warehouse Backorder
System Warehouse (WH)
Prerequisites None
Initiating event Inventoried Allocation (WH20) or Batch Allocation

(WH110) created a backorder for a customer order.
Variables COMPANY
PROCESS_LEVEL
CUSTOMER_NUMBER
ORDER_NUMBER
ORDER_LINE_NUMBER
ITEM
LOCATION
BACKORDER_QTY
BILL_TO
SHIP_TO
ORDER_DATE
EXPECTED_SHIP_DATE
REQUESTED_DATE
ORDER_STATUS
KIT_FLAG
WH Demand Cancellation
This service notifies the Order Processing Manager that a requisition demand has been cancelled.
Service WH Demand Canc
Service name WH Demand Cancel
Criteria Company, Location, Item
Object Key WDMSET1
Initiating event A Cancel line action or Cancel All form action is

completed on Cancellation by Item (WH25.1) or
Cancellation by Document (WH25.2).
Variables QUANTITY CANCELLED
WDM_BACKORD_QTY
WDM_COMPANY
WDM_DOC_NBR
WDM_ITEM
WDM_LINE_NBR
WDM_LOCATION
WDM_QUANTITY
WDM_REQ_COMPANY
WDM_REQ_LOCATION
WDM_SYSTEM_CD
WH Priority Override
This service notifies the Order Processing Manager that the allocation priority for warehouse demand has
been changed.
Service WH Prior Overid
Service name WH Priority Override

Warehouse (WH)
Object Key WDMSET1
Initiating event A change form action on the Item Entry (OE10) forms
or the Allocation (WH20) forms to alter the allocation
priority of an order line.
Variables COR_OPR_CODE
COR_SHIP_TO_NAME
OEC_NAME
REQ_REQUESTER
WDM_CUSTOMER
WDM_ALLOC_PRI
WDM_COMPANY
WDM_COMPONENT_SEQ
WDM_DESTINATION
WDM_DOC_NBR
WDM_DOC_NBR_NUM
WDM_ITEM
WDM_ITEM_DESC
WDM_LINE_NBR
WDM_LOCATION
WDM_QUANTITY
WDM_STATUS
WDM_SYSTEM_CD
WH Shipment Batch Creation

This service notifies the Warehouse Manager that a shipment batch has been successfully created.
Service WH ShipmentBtch
Service name WH Shipment Batch Creation
Object key WHBSET1
Work Category Warehouse Mgr
Prerequisites None
Initiating event A shipment batch was created on Pick List Print

(WH130)
Variables COMPANY
LOCATION
BATCH NUMBER
WH Shipment Creation
This service notifies the Warehouse Manager that a new shipment is ready for processing.
Service WH Shipment
Service name WH Shipment Creation
Object key WHSSET1
Work Category Warehouse Mgr
Prerequisites None
Initiating event A shipment was created
Variables COMPANY
LOCATION
SYSTEM CD
DOC NBR
LINE NBR
ITEM
DESTINATION
ROUTE
STOP
CARRIER
CUST SHIP TO
REQ LOCATION
REQ COMPANY
Shipment Release
This service notifies the Order Processing Manager that a shipment has been released.
Service Shpmt Release
Service name WH Shipment Release
Object Key WHSSET1
Initiating event A shipment is released with the release form action

on the Shipping (WH32) forms or a batch is
submitted on Shipment Release (WH190).
Variables COR_CUSTOMER
COR_SHIP_TO_NAME
WHS_BATCH_NBR
WHS_COMPANY
WHS_CUST_SHIP_TO
WHS_DOC_NBR
WHS_LOCATION
WHS_REQ_LOCATION
WHS_SHIPMENT_NBR
WHS_SYSTEM_CD
Shipment Backordered or Voided

This trigger creates a work unit when a shipment line is backordered or voided in the Warehouse feedback
processes on Picking Feedback by Shipment (WH30), Packing Feedback by Shipment (WH31), or Shipping
Feedback by Shipment (WH32).
Service Shpmt BkordVoid
Service name Shpmnt Bckordrd or Voided
Work Category None
Object Key WHLSET1

warehouse processing, which includes the existence
of a customer order.
Initiating event Back ordering or voiding a shipment line in the

Warehouse feedback processes on Picking
Feedback by Shipment (WH30), Packing Feedback
by Shipment (WH31), or Shipping Feedback by
Shipment (WH32).
COR_CUSTOMER
COR_OPR_CODE
COR_ORDER_DATE
COR_ORDER_NBR
COR_ORDER_TYPE
COR_SHIP_TO
COR_SHIP_TO_NAME
MAILFROMUSER
MAILSUBJECT
MAILTO
OEC_NAME
OTP_DESCRIPTION
SHIP_LINE_ACTION
WHA_COMPANY
WHA_LINE_NBR
WHA_QUANTITY
WHA_SHIPMENT_NBR
WHA_STATUS
WHL_DESCRIPTION
WHL_ITEM

The user who added the order is notified that an item was back ordered or voided.
EAM Shipment Release

This trigger creates a work unit when an EAM item is issued on Shipping Feedback By Document (WH32).
Service EAM_WHShip
Service name EAM_WHShip

Initiating event A shipment is released on Shipping Feedback By

Document (WH32) with a Location = EAM location
and a work number in the EAM Work Number field
Variables ACTION
ICT_ITEM
ICT_COMPANY
ICT_COMPONENT_SEQ
ICT_DOCUMENT
ICT_DOC_TYPE
ICT_EAM_OPER_NBR
ICT_EAM_SEQ_NBR
ICT_EAM_WO_NBR
ICT_LINE_NBR
ICT_LOCATION
ICT_SHIPMENT_NBR
ICT_STOCK_QUANTITY
ICT_STOCK_UNIT_COST
ICT_STOCK_UOM
ICT_SYSTEM_CD
ICT_TRANS_DATE
M3_STATUS
SIGN
Production Order (WO)
The following services are available in Production Order (WO).
• "Work Order Production" on page 114
• "Work Order Reverse" on page 114
• "Work Order Sent Offsite" on page 115
• "Work Order Allocation Override" on page 116
Work Order Production

This trigger creates a work unit when a work order is placed in the In Production status on Production
Schedule (WO20) or Work Order (WO30).
Service WO Production
Service name Work Order Production
System Production Order (WO)
Work Category Company Location
Prerequisites No prerequisites are required other than normal work

order processing, which includes the existence of a
work order with allocated components in an exploded
status.
Initiating event Placing a work order in the In Production status on

Production Schedule (WO20) or Work Order (WO30).
Variables WOR_COMPANY
WOR_LOCATION
WOR_WORK_ORDER
WOR_WORK_ORDER_SUF

The Line Supervisor is notified that a work order was put in production.
Work Order Reverse

This service notifies the Order Processing Manager that a work order has been reversed.
Service WO Reverse
Service name Work Order Reverse
Initiating event A reverse action on Reverse Work Order (WO45.1).
WOR_LOCATION
WOR_REVERSED_BY_WO
WOR_WORK_ORDER
WOR_WORK_ORDER_SUF
Work Order Sent Offsite

This trigger creates a work unit when a work order is sent offsite on Send Offsite (WO35).
Service WO Send Offsite
Service name Work Order Sent Offsite
Work Category Company Location

Data string = [company][work order location]
Prerequisites No prerequisites are required other than normal work

order processing, which includes the existence of a
work order in the In Production status and Inventory
Control setup for an offsite component.
Initiating event Sending a work order offsite on Send Offsite (WO35).
WOR_LOCATION
WOR_OFFSITE_DATE
WOR_WORK_ORDER
WOR_WORK_ORDER_SUF

The Line Supervisor is notified that a work order has been sent offsite.
Work Order Allocation Override
This service notifies the Order Processing Manager that a work order was placed into production without
allocating all components.
Service WO Alloc Ovrrd
Service name Work Order Allocation Override
Prerequisites On Location (IC02.1), Work Order page, the Allow

Unallocated In-Production field must be set to “No
—but override allowed” (O) or “In prod unrestricted
by alloc” (N).
Initiating event Not enough components to meet demand. An in

production action on Work Order (WO30.1), and a
Yes to the resulting override option.
Variables WOI_PLAN_QTY
WOR_COMPANY
WOR_LOCATION
WOR_WORK_ORDER
WOR_WORK_ORDER_SUF
Chapter 6
Application Triggers and Services for EPM
This chapter provides detailed information about the services in the Enterprise Performance Management
(EPM) applications.
• "Analytic Architect (IA)" on page 118
LPA and S3 Applications Reference Guide Chapter 6 Application Triggers and Services for EPM 117
Analytic Architect (IA)
The following services are available in the Analytic Architect (IA) application.
• "OLAP Database Notification" on page 118
OLAP Database Notification

This trigger creates a work unit when an Essbase error is received when running Data Mart Load (IA120).
The OLAP Database Notification service notifies the OLAP Supervisor when an Essbase error occurs during
the running of Data Mart Load (IA120).
Service OLAPCubeNotify
Service name OLAP Cube Notification
System Information Architecture (IA)
Criteria Application, Database
Work Category None
Prerequisites Normal OLAP processing, which includes:

Assigning a Distribution Group to the job so the
person with the task of OLAP Supervisor can see
the report in his or her print manager.
Initiating event Receiving an Essbase error when running Data Mart

Load (IA120).
MAILSUBJECT
MAILTOROLE

The OLAP Supervisor is notified when an Essbase error occurs during the running of Data Mart Load (IA120).
118 Chapter 6 Application Triggers and Services for EPM LPA and S3 Applications Reference Guide

Lawson LPA and S3 Applications Reference Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lawson LPA and S3 Applications Reference Guide

Uploaded by

Copyright:

Available Formats

LPA and S3 Applications Reference Guide

Chapter 2 Install LPA Services for S3 Enterprise Applications 8

Chapter 3 Application triggers and services for Human Capital

Chapter 4 Application triggers and services for Enterprise

General Ledger (GL).....................................................................21

Project and Activity Accounting (AC).........................................26

LPA and S3 Applications Reference Guide Contents 3

Billing and Revenue Management (BR)......................................32

Grant Management (GM)..............................................................34

Accounts Payable (AP)................................................................38

Accounts Receivable (AR)...........................................................44

Employee Expense (EE)...............................................................52

Chapter 5 Application Triggers and Services for Supply Chain

Inventory Control (IC)...................................................................60

4 Contents LPA and S3 Applications Reference Guide

Order Entry (OE)...........................................................................72

Purchase Order (PO)....................................................................83

LPA and S3 Applications Reference Guide Contents 5

Production Order (WO)..............................................................114

Chapter 6 Application Triggers and Services for EPM 117

6 Contents LPA and S3 Applications Reference Guide

• "What is a process?" on page 7

• "What are S3 triggers and services?" on page 7

What are S3 triggers and services?

LPA and S3 Applications Reference Guide Chapter 1 Overview 7

Install LPA Services for S3 Enterprise

Install LPA Services for S3 Enterprise Applications

STEPS To install LPA Services for S3

Application triggers and services for

• "Human Resources (HR)" on page 10

• "Personnel (PA)" on page 12

• "Employee Delete" on page 11

Service Goal Approval

Service name Goal Approval

System Human Resources (HR)

Work Category Supervisor

Prerequisites Access to Goal View Manager/Employee Self

Initiating event • Manager defines an employee objective in the

Resolution action Manager will either Approve or Reject an objective

Service name Employee Delete

System Human Resources (HR)

Work Category None

Initiating event Delete an employee on HR11.1 or PA115

Resolution action N/A

Related LPA Process

• "Job Requisition Approval" on page 12

• "Personnel Action Approval" on page 14

Job Requisition Approval

Service JobReq Approval

Service name Job Requisition Approval

System Personnel Administration (PA)

Criteria Company, Process Level, Department

Work Category Department

Prerequisites Requisition (PA42.1) must have a requisition status

Initiating event Requesting a new job position on Requisition

Resolution action N/A

Personnel Action Approval

Application triggers and services for

• "Asset Management (AM)" on page 18

• "General Ledger (GL)" on page 21

• "Project and Activity Accounting (AC)" on page 26

• "Billing and Revenue Management (BR)" on page 32

• "Grant Management (GM)" on page 34

• "Accounts Payable (AP)" on page 38