Perceptive Voucher Build Connector for PeopleSoft ... · PDF file© ....

Perceptive Voucher BuildConnector for PeopleSoftInstallation GuideVersion: 2.1.xDate: Wednesday, August 17, 2016

© 2016 Lexmark. All rights reserved.Lexmark is a trademark of Lexmark International Inc., registered in the U.S. and/or other countries. All othertrademarks are the property of their respective owners. No part of this publication may be reproduced, stored, ortransmitted in any form without the prior written permission of Lexmark.

Perceptive Voucher Build Connector for PeopleSoft Installation Guide 2.1.x

3

Table of Contents

Perceptive Voucher Build Connector for PeopleSoft 6

Releases 6

Overview 6

About the Voucher Build Connector process 6

Technical Specifications 7

Internet Browser 7

Operating Systems 7

Software 7

Licenses 7

Installation 8

Related Information 8

Preparing for the Installation 8

Overview 8

Tasks 8

Determine Required Document Types 8

Analyze ExistingWorkflows 9

Validate Voucher BuildWeb Service 9

Validate Connectivity 10

Install the Voucher Build Connector 10

Overview 10

Downloading Install Files 10

Licensing the Connector 10

Installing the Connector 10

Create the PeopleSoft Response Channel 10

Overview 11

Create the Response Channel 11

Action Configuration 12



4

PeopleSoft Voucher Build Configuration 18

Overview 18

Publish Voucher BuildWeb Service 18

Verify Service Operation Settings 18

Verify Queue Settings 19

Configure EIP ResponseMessage 19

Enable EIP Messages 20

Configure Voucher Build Connector 21

Enable Extended Voucher Build Messages 21

Create the Store Invoice Channel Mapping 21

Overview 21

Create a Channel 22

Create Channel Mapping 23

eForm Field 23

Literal Values 23

In header fields 23

In XML rowsets 24

Document Field or Custom Property 24

Repeating Elements Using Rowsets 24

Nested Repeating Elements Using Rowsets 25

Sample Configuration 26


Configure Perceptive Content Workflow 26

Overview 27

SampleWorkflow 28

Workflow Queue Details 29

Design Considerations 30

Multiple Integration Queues 30

Staging Timeout 30


5

Perceptive Connect Channel Mapping Cookbook 30

Overview 30

Get Document fromWorkflow Item 30

Get eForm Content from Document 31


PeopleSoft Voucher Build Connector release notes 32

2.1.0 32

F12472 32

2.0.2 32

2.0.0 32

1.0.0 32


6

Perceptive Voucher Build Connector for PeopleSoftReleases

Overview of Release Notes

OverviewThe Perceptive Voucher Build Connector for PeopleSoft is an extension to Perceptive Content, also calledImageNow. It allows Perceptive Content to export accounts payable (AP) invoices entered in a PerceptiveContent eForm, such as the AP Invoice eForm, to PeopleSoft.

This solution streamlines the AP invoicing process. You can expect the following benefits when using theVoucher Build Connector for PeopleSoft.

l Streamline the collection of complete invoices.

l Reduce themanual effort of updating invoices in PeopleSoft.

l Allow staff to complete their review and evaluation processes more quickly.

l Make faster andmore informed decisions, improving invoice processing quality.

About the Voucher Build Connector processWhen a document enters the configured workflow in Perceptive Content, a web services notifies PeopleSoftAP Voucher Build. PeopleSoft receives the data, creates a voucher, and after running the voucher buildprocess, notifies Perceptive Content workflow. Finally, Content routes the document to a workflow queuethat indicates the final state.

The Voucher Build Connector runs on Perceptive Connect Runtime. The runtime service provides anindependent messaging and data exchange between Perceptive Content and PeopleSoft.


7

Voucher Build Overview Flow Diagram

Technical Specifications

Internet Browserl Chrome, latest version

Operating Systemsl Runs on all operating systems that Perceptive Connect Runtime supports.

Softwarel ImageNow Client and Server, version 6.7 or Perceptive Content Client and Server, version 7.0

l Perceptive AP Invoice eForm or a custom eForm compatible with your version of ImageNow orPerceptive Content

l Perceptive Connect Runtime, version 1.4 or higher

l Perceptive Content Connector, version 1.0 or higher

l PeopleTools, version 8.49.18 or higher

l PeopleSoft Financials, version 8.8 or higher

LicensesThe Voucher Build Connector for PeopleSoft requires the following licenses.


8

l ImageNow AP Connector for PeopleSoft

InstallationTo install the connector and create an integration between Perceptive Connect and PeopleSoft, complete thefollowing tasks, in order.

l Prepare for Installation

l Install the Voucher Build Connector

l Create the PeopleSoft Response Channel

l PeopleSoft Voucher Build Configuration

l Configure Perceptive Content Workflow

l Create the Store Invoice Channel Mapping

Related Informationl Perceptive Connect Runtime Installation and SetupGuide

l PeopleSoft Web-Service Supplemental Guide

Preparing for the InstallationPerceptive Voucher Build Connector for PeopleSoft

OverviewInstallation of thePerceptive Voucher Build Connector for PeopleSoft is an involved process. The connectorrequires close interaction with your accounts payable process in both Perceptive Content and PeopleSoft.Perform the following tasks before proceeding with installation and configuration.

Tasksl [x] [Determine the required Perceptive Content document types](#determine-required-document-types).

l [x] [Analyze your existing AP workflows in Perceptive Connect](#analyze-existing-workflows).

l [x] [Validate PeopleSoft Voucher BuildWeb-Service](#validate-voucher-build-web-service).

l [x] [Validate connectivity between Perceptive Connect and PeopleSoft](#validate-connectivity).

Determine Required Document TypesThe process to export data to PeopleSoft will generally differ between types of invoices. For example,PeopleSoft has different required fields for PO versus non-PO Inovices. As such, each invoice type willrequire a dedicated Integration queue (ASQ) in the workflow.

https://docs.lexmark.com/PC!/en_US/1.3/Runtime/Print/Perceptive_Connect_Runtime_Installation_Guide_1.3.x.pdf


9

It is generally prefered that all workflow steps upstream and downstream from the export to PeopleSoft beshared. In this case, a possible solution is to use a document type (PO Invoice versus Non-PO Invoice) tocreate a routing rule just before the export to step as indicated by the diagram below.

Document Type Routing Rule Flow

Analyze ExistingWorkflowsThe Voucher Build Connector leverages Integration queues (ASQ) to trigger the export process in PerceptiveConnect. It will be necessary to determine the correct point in the workflow to trigger the export and handle theresponse.

It is important to note that the Voucher Build in PeopleSoft runs as a batch process. The export step inworkflow will therefore require a queue to hold documents, staged in PeopleSoft, waiting for the batch processto execute. The response from the PeopleSoft Voucher Build Message will be sent periodically, as configuredin PeopleSoft.

Validate Voucher BuildWeb ServiceThe Voucher Build Connector uses PeopleSoft's built-in, Voucher Build web service to upload invoices. Youmust ensure that the web service is installed, available, and has the proper permissions to populate theVoucher Build staging tables. A SOAP tool like Soap UI is a great way to validate the web service isfunctioning correctly.

http://www.soapui.org/


10

Validate ConnectivityThe Voucher Build Connector (running in Perceptive Connect) will require connectivity to the targetPeopleSoft environment. Youmust ensure that firewalls and network permissions allow themachine runningPerceptive Connect to communicate with the PeopleSoft. The connector uses the URL and ports outlined inyour PeopleSoft instance's Voucher BuildWSDL.

Install the Voucher Build ConnectorPerceptive Voucher Build Connector for PeopleSoft

OverviewThePerceptive Voucher Build Connector is runs insides of Perceptive Connect Runtime (PCR). Itfurther utilizes thePerceptive Content Connector (PCC) for communication withPerceptive Content(ImageNow). Before proceeding, you need to ensure bothPCR andPCC are installed and configuredcorrectly.

Downloading Install Files1. Go to the Perceptive Software website and log in to the Customer Portal.

2. In the Product Downloads page, search for thePerceptive Voucher Build Connector for PeopleSoftfile.

3. Download the file to a temporary directory on your computer.

Licensing the ConnectorTheVoucher Build Connector is subject to a license that most be installed on thePerceptive Contentserver prior to execution. The license required for theVoucher Build Connector is the ImageNow APConnector for PeopleSoft.

The licensing process consists of the folowing steps: * Generate a system finger print for your PerceptiveContent server. * Contact your Percetpive Software representative with the fingerprint to obtain your license. *Install the license on yourPerceptive Content server.

Please see the Perceptive Content (ImageNow) documentation for more details.

Installing the ConnectorTo install theVoucher Build ConnectorUse the Perceptive Connect Runtime's Bundle installer page. SeeInstall a Connector in the Perceptive Connect Runtime Install Guide for more information. Back to Top

Create the PeopleSoft Response ChannelPerceptive Voucher Build Connector for PeopleSoft

http://docs.perceptivesoftware.com/Portal/Customer/Help/Product_Documentation.htm#Products/en/ImageNow.htm


11

OverviewThe PeopleSoft Voucher Build executes as a scheduled batch. ThePeopleSoftVoucherStoreActon simplypopulates staging tables in the PeopleSoft database. The data is not processed until the batch processexecutes. At that time, PeopleSoft sends a response with the invoice status (success, failure or recycle).

TheVoucher Build Connector handles this response by creating a channel inPerceptive ConnectRuntime. The channel is customizeable for each solution, but will likely will leverage the followingcomponents. * Trigger: TheWebXmlTrigger is used to expose an http endpoint that can receive the XMLmessage (text/plain) response from PeopleSoft. *Action: TheRoute By Status Action is used to route theinvoice document to the correct destination queue based upon the status communicated in the XMLmessage. *DocumentSearchReader: TheDocument Search Reader takes the invoice values from thePeopleSoft response XML and performs a search inPerceptive Content to locate thematching invoice.

Create the Response ChannelThe channel defines themapping between the XML response from PeopleSoft and resulting actions withinPerceptive Content. Complete the following steps to define this mapping.

1. In thePerceptive Connect Runtime Web Console, underPerceptive Connect, click Create aChannel.

2. InSelect a trigger, select theWebXmlTrigger.

3. InUnique Instance Name, type a short name to uniquely describe the channel.

l NOTE: The instance name needs to be URL compliant.

l For example, PeopleSoftInvoiceResponse or Invoice-Response-Endpoint.

4. InSelect an action, select theRoute By Status Action.

5. InConfigure Input Mapping, complete the steps defined in the Action Configuration section tocomplete themapping.

6. Click Next.

7. InConfigure output mapping, complete the steps defined in the Output Configuration section tocomplete themapping.

8. Click Save Channel > OK.

Following the steps above will create a listener at the following URL. This URLwill be used in the PeopleSoftConfiguration when configuring theEIP Response Message.

http://[Perceptive Connect Server]:[port]/rs/webXml/[Unique Instance Name]

http://www.faqs.org/rfcs/rfc1738.html


12

Action ConfigurationThe action configuration can be customized for solution's needs. Generally, the process will involve four maincomponents:

1. Read required values from the PeopleSoft response XML.

2. Search for thematching document inPerceptive Content.

3. Set the desired document keys and custom properties for thematching document.

4. Route thematching document to the proper status queue (Success, Failure, Recycle).

Selecting theRoute By Status Action yields the following default action configuration that you are requiredto customize. A complete sample following the example below can be found here.

<c:parameter><c:name>statusValue</c:name><c:none/>

</c:parameter><c:parameter>

<c:name>documentId</c:name></c:parameter><c:parameter>

<c:name>fallbackQueueName</c:name><c:none/>


<c:name>originQueueName</c:name><c:none/>


<c:name>destQueueName0</c:name><c:none/>


<c:name>compareValue0</c:name><c:none/>







</c:parameter>


13

<c:parameter><c:name>compareValue2</c:name><c:none/>









</c:parameter>

First, you need to add a parameter to reference PeopleSoft XML response provided by theWebXmlTrigger.Hence forth, the XML data can be accessed using the WebXMLData parameter.

<c:parameter><c:name>WebXMLData</c:name><c:trigger>XML Document</c:trigger>

</c:parameter>

Next, you need to populate the originQueueName to indicate the staging queue where the document will belocated when the PeopleSoft response is recieved. See the workflow configuration for more information on thestaging queue.

<c:parameter><c:name>originQueueName</c:name><c:literal>AP Invoice Export Stage</c:literal>

</c:parameter>

Next, the statusValue should be populated with the PeopleSoft status XML value used to conditionallyroute the document to the proper status queue. In the example below, the status value will be pulled from the//*/MsgData/Transaction/VCHR_EIP_OUT/ENTRY_STATUS element of the XML.

<c:parameter><c:name>statusValue</c:name><c:xmlSource>

<c:reference>WebXMLData</c:reference><c:xpath>//*/MsgData/Transaction/VCHR_EIP_OUT/ENTRY_STATUS</c:xpath>

</c:xmlSource></c:parameter>


14

NOTE: The configuration above uses theXML Reader provided with thePerceptive Connect Runtime(PCR). Please see thePerceptive Connect Runtime Installation Guide for more information.

Next, you need to customize the status / destination queues combinations to handle the various statusexpected from PeopleSoft. The compareValue[index] values will bematched against the statusValuefrom above. When amatch is found the document will be routed to thematching workflow queue indicated bydestQueueName[index].

NOTE: The expected status values from PeopleSoft would be as follows. * 'F' - Failure * 'R' - Recycle * 'S' -Success

<c:parameter><c:name>compareValue1</c:name><c:literal>F</c:literal>


<c:name>destQueueName1</c:name><c:literal>AP Invoice Export Fail</c:literal>

</c:parameter>

NOTE:Only five conditional sets are currently supported by configuration.

If statusValue is not found amongst the compareValue[index] parameters, the action will attempt toroute to the queue defined in the fallbackQueueName parameter. Please see the fallback queue paremterexample below. If the fallback is not defined, the document will not be routed and will remain in the stagingqueue.

<c:parameter><c:name>fallbackQueueName</c:name><c:literal>AP Invoice Export Fail</c:literal>

</c:parameter>

Lastly, use theObject Search Reader to discover the documentId parameter of the action. PeopleSoft hasno concept of thePerceptive Content document ID. A search is therefore required to discover the documentID using the XML data provided by the PeopleSoft response.

In the example below, theObject Search Readerwill search for a document with the following criteria. *Business Unit in Field1 * Vendor ID in a custom property named 'Vendor ID' * Invoice ID in a custom propertynamed 'Invoice ID'

For predictable results, the combination of the view and search critera should yield in a single, uniquedocument result.

https://docs.perceptivesoftware.com/PC!/en_US/1.0/Runtime/Print/Perceptive_Connect_Runtime_Installation_Guide_1.0.x.pdf


15

<c:parameter><c:name>SearchFieldBusinessUnit</c:name><c:xmlSource>

<c:reference>WebXMLData</c:reference><c:xpath>//*/MsgData/Transaction/VCHR_EIP_OUT/BUSINESS_UNIT</c:xpath>

</c:xmlSource></c:parameter><c:parameter>

<c:name>SearchFieldVendorId</c:name><c:xmlSource>

<c:reference>WebXMLData</c:reference><c:xpath>//*/MsgData/Transaction/VCHR_EIP_OUT/VENDOR_ID</c:xpath>


<c:name>SearchFieldInvoiceId</c:name><c:xmlSource>

<c:reference>WebXMLData</c:reference><c:xpath>//*/MsgData/Transaction/VCHR_EIP_OUT/INVOICE_ID</c:xpath>


<c:name>documentIdList</c:name><in:objectSearch>

<in:viewType>DOCUMENT</in:viewType><in:viewName>pre-defined-doc-view</in:viewName><in:viewColumnID>8</in:viewColumnID><in:maxWaitTime>0</in:maxWaitTime><in:searchTerm>

<in:joinOperation>AND</in:joinOperation><in:operatorType>EQUALS</in:operatorType><in:parameterType>FIELD1</in:parameterType><in:propertyName/><in:searchValueRef>SearchFieldBusinessUnit</in:searchValueRef>

</in:searchTerm><in:searchTerm>

<in:joinOperation>AND</in:joinOperation><in:operatorType>EQUALS</in:operatorType><in:parameterType>Custom_property</in:parameterType><in:propertyName>Vendor ID</in:propertyName>/><in:searchValueRef>SearchFieldVendorId</in:searchValueRef>

</in:searchTerm><in:searchTerm>

<in:joinOperation>AND</in:joinOperation><in:operatorType>EQUALS</in:operatorType><in:parameterType>Custom_property</in:parameterType><in:propertyName>Invoice ID</in:propertyName>/><in:searchValueRef>SearchFieldInvoiceId</in:searchValueRef>

</in:searchTerm>


16

</in:objectSearch></c:parameter><c:parameter>

<c:name>documentId</c:name><c:listItem>

<c:listRef>documentIdList</c:listRef><c:index>0</c:index>

</c:listItem></c:parameter>

TheObject Search Reader returns its results in list. The first (and only) list itemmust be retrieved using theList Item Reader. The documentation for the List Item Reader can be found here.

TheObject Search Reader can alsomatch parameters such as keys and custom properties from a literal(constant) paramter using the following example.

<c:parameter><c:name>VendorId</c:name><c:literal>abc123</c:literal>


<c:name>documentId</c:name><in:searchTerm>

<in:joinOperation>AND</in:joinOperation><in:operatorType>EQUALS</in:operatorType><in:parameterType>FIELD1</in:parameterType><in:propertyName/><in:searchValueRef>VendorId</in:searchValueRef>

</in:searchTerm></c:parameter>

The documentation for theObject Search Reader can be found here.

This is also a convenient place to add parameters that will be used in the output configuration later. Allparameters declared in the action configuration will also be available in the output configuration.

<c:parameter><c:name>VoucherId</c:name><c:xmlSource>

<c:reference>WebXMLData</c:reference><c:xpath>//*/MsgData/Transaction/VCHR_EIP_OUT/VOUCHER_ID</c:xpath>


<c:name>enteredDate</c:name><c:xmlSource>

<c:reference>WebXMLData</c:reference><c:xpath>//*/MsgData/Transaction/VCHR_EIP_OUT/ENTERED_DT</c:xpath>

</c:xmlSource>

http://pswgithub.rds.lexmark.com/integrated-products/connect/blob/master/docs/install_guide/appendix_d.html#list-item-reader

http://pswgithub.rds.lexmark.com/integrated-products/content-connector/blob/master/docs/appendix_c.html#object-search-reader


17

</c:parameter>```

[Back to top](#)## Output Configuration ##The example below illustrates the default output configuration for the**Route By Status Action**. The `resultStatus` parameter indicates thestatus that was matched by the status action (blank if no match). The`wasRouted` parameter indicates if the document was routed using a booleanvalue.To use the output parameters, simply replace the `<c:noTarget/>` with a**Perceptive Connect** writer appropriate for your need. Please see the[Perceptive Content Runtime Installation Guide](https://docs.lexmark.com/PC!/en_US/1.0/Runtime/Print/Perceptive_Connect_Runtime_Installation_Guide_1.0.x.pdf) or [Perceptive Content ConnectorInstallation Help](https://docs.lexmark.com/PCC/1.0.x_en_US/Install/PCC_Install.htm) for more details.

These values are provided for convienence, but in most cases, will not berequired. The recommended workflow outlined in the [workflow configuration](workflow-config.html) uses a timeout on the staging queue to handle caseswhere the PeopleSoft response is not recieved. If the action fails to matchthe status, the timeout rule will move the document to timeout queue.**NOTE:** You are required to delete the two, auto-generated parameters ifnot used by your implementation. An error will occur if the parametersremain unconfigured.The output configuration can be used to set the values of any **PerceptiveContent** keys or custom properties required by the implementation. In[action configuration](#action-configuration), you had the option of addingparameters to conveniently read values from the PeopleSoft response XML.Those parameters are now available to you in the action configuration.

```

NOTE: The configuration above leverages theObject Property Writer provided with thePerceptiveContent Connector. Please see thePerceptive Content Connector Installation Help for moreinformation.

NOTE:Date values from PeopleSoft (YYYY-MM-DD) are not compatible with dates stored inPerceptiveContent as a date type custom property (MM/DD/YYYY). TheDate Format Reader delivered withPerceptive Connect can be used to reformat dates. See thePerceptive Connect documentation here formore details.

Related Informationl Perceptive Content Runtime Installation Guide

l Perceptive Content Connector Installation Guide

https://docs.lexmark.com/PCC/1.0.x_en_US/Install/PCC_Install.htm

https://docs.lexmark.com/PC!/en_US/1.3/Runtime/Print/Perceptive_Connect_Runtime_Installation_Guide_1.3.x.pdf


http://twrobowebd00.ad.rds.lexmark.com/PCC/en_US/0.14.x/Perceptive_Content_Connector_Installation_Guide_0.14.x.pdf


18

PeopleSoft Voucher Build ConfigurationPerceptive Voucher Build Connector for PeopleSoft

OverviewThePerceptive Voucher Build Connector leverages the Voucher Build web service supplied byPeopleSoft.

Before continuing, verify PeopleSoft Integration Broker is correctly configured. For more information on how toconfigure the Integration Broker, refer to your PeopleSoft documentation.

Publish Voucher BuildWeb ServiceIn PeopleSoft EnterpriseWeb Application, you need to publish a web service that the Voucher Buildconnector users to communicate with PeopleSoft. Perform the following steps to publish a web service.

1. In the left pane, underMenu, click PeopleTools and then click Integration Broker.

2. In the right pane, underWeb Services, click Provide Web Service to open theProvide Web ServiceWizard.

3. On theSelect Services page, perform the following substeps:

4. UnderSearch Criteria, in theService Name box, typeAP_VOUCHER_BUILD.

5. Click Search.

6. UnderSearch Results, select AP_VOUCHER_BUILD.

7. Click Next.

8. On theSelect Services Operations page, perform the following substeps:

9. Verify Use Service Alias in WSDL is not selected.

10. Click Next.

11. On theView WSDL page, verify theService is AP_VOUCHER_BUILD, and then click Next.

12. On theSpecify Publishing Options page, verifyWSDL Repository is selected, and then click Finish.

13. Note the generatedWSDL URL for use during the Voucher Build Connector Configuration.

Verify Service Operation SettingsPerform the following steps to verify service operations are correctly configured and active:

1. In the left pane, underMenu, click PeopleTools and then click Integration Broker > Integration Setup> Service Operations.

2. On theService Operations page, perform the following substeps:


19

3. UnderSearch Criteria, in theService Operation box, typeAP_VOUCHER_BUILD_ADD, and thenclick Search.

4. UnderSearch Results, click AP_VOUCHER_BUILD_ADD.

5. On theGeneral tab, perform the following substeps:

6. UnderDefault Service Operation Version, verify Active is selected.

7. UnderRouting Status, verify Any-to-Local is set toExists.

8. On theHandlers tab, underHandlers, verify theRQSTHNDLR handler is set toActive.

9. On theRouting tab, perform the following substeps:

10. Verify Sender Node is set to ~Any~.

11. Verify Direction is set to Inbound.

12. Verify Status is set toActive.

13. Click Save if youmade any changes.

Verify Queue SettingsPerform the following steps to verify queue settings:

1. In the left pane, underMenu, click PeopleTools and then click Integration Broker > Integration Setup> Queues.

2. On theQueues page, perform the following substeps:

3. UnderSearch Criteria, in theQueue Name begins with box, typeVOUCHER, and then click Search.

4. UnderSearch Results, click VOUCHER.

5. On theQueue Definitions page, verify theQueue Status is set toRun.


Configure EIP ResponseMessageThe Voucher Build Response EIP message is amessage sent from PeopleSoft, after the voucher buildprocess, that informs Voucher Build connector that PeopleSoft has successfully processed the invoicedocument. The Voucher Build connector will use this information to update invoice documents in ImageNowor Perceptive Content with PeopleSoft statuses and the voucher ID. Perform the following steps to configurethis message.

1. In the left pane, underMenu, click PeopleTools and then click IntegrationBroker> Integration Setup**> Service Operations.

2. On theService Operations page, perform the following substeps:

3. UnderSearch Criteria, in theService Operation box, typeAP_VCHR_MESSAGE_OUT, and thenclick Search.


20

4. UnderSearch Results, click AP_VCHR_MESSAGE_OUT.

5. On theGeneral tab, underDefault Service Operation Version, verify Active is selected.

6. On theRouting tab, verify Status is set toActive, and then, underName, click AP_VCHR_MESSAGE_OUT.

7. On theConnector Properties tab, perform the following substeps;

8. In theGateway ID box, configure the appropriate gateway ID.

9. In theConnector ID box, typeHTTPTARGET.

10. Configure thePRIMARYURL value to point to theVoucher Build Connector response channelendpoint.

l See the response channel configuration to determine the URL for your configuration.

l For example, http://[Perceptive Connect Server]:[port]/rs/webXml/[UniqueInstance Name]

11. Click Save.

12. In the left pane, underMenu, click PeopleTools and then click Integration Broker > Integration Setup> Queues.

13. On theQueue page, perform the following substeps:

14. UnderSearch Criteria, in theQueue Name begins with box, typeAP_VCHR_OUT, and then clickSearch.

15. UnderSearch Results, click AP_VCHR_OUT.

16. On theQueue Definitions page, verify Queue Status is set toRun.


Enable EIPMessagesEnabling EIP messages for the Voucher Build process allows PeopleSoft to sendmessages about processedVoucher information to subscribed applications such as theVoucher Build Connector.

1. In the left pane, underMenu, click Accounts Payable > Batch Processes > Vouchers > VouchersBuild.

2. On theVoucher Build Request page, locate an appropriateRun Control or create a new one.

3. On theVoucher Build tab, under Interfaces, select XML Invoice from theVoucher Build Interfacelist, and verify Publish Voucher Messages is selected.


5. If necessary, set up a run schedule. For more information, refer to your PeopleSoft documentation.


21

Configure Voucher Build ConnectorTo configure theVoucher Build Connector, perform the following steps:

1. In thePerceptive Connect Runtime Web Console, underPerceptive Connect click ViewConfiguration.

2. UnderPeopleSoft Voucher Build, click theEdit button for thePeopleSoft Voucher StoreConfiguration.

3. In thePeopleSoft Voucher WSDL URL, enter location of the PeopleSoft voucherWSDL as a URL. Forexample: http://[server-name]/PSIGW/PeopleSoftServiceListeningConnector/AP_VOUCHER_BUILD.1.wsdl

4. Check the Legacy PeopleTools box if your version of PeopleTools is prior to 8.49.18

5. Check the Log Message to enable logging of the outboundMessage to PeopleSoft during the VoucherBuild Action. The Perceptive Connect Runtime logs will contain the XMLmessage

6. Check theSimulate Voucher Buildmessage to prevent the connector from actually sending theVoucher Build Message to PeopleSoft. This is helpful during initial configuraiton

7. Click Save.

Enable Extended Voucher Build MessagesBy Default, theVoucher Build Connector sends the Voucher Header message with GL and Distributionlines. To enable Extendedmessage types of Bank, Intermediary Bank, Miscellaneous Charges, Vendor andPayment information youmust configure thePeopleSoft xtended Voucher Build Store Action

1. In thePerceptive Connect Runtime Web Console, underPerceptive Connect click ViewConfiguration.

2. UnderPeopleSoft Voucher Build, click theEdit button for thePeopleSoft Extended VoucherStore Action.

3. Checkbox all the Sub-Messages you wish tomap

4. Click Save.

Create the Store Invoice Channel MappingPerceptive Voucher Build Connector for PeopleSoft

OverviewAfter installing theVoucher Build Connector, youmust create channels thePerceptive Connect Runtimeto trigger the export the invoice into PeopleSoft.


22

A channel consists of a trigger, an action and a configuration binding the two together. TheVoucher BuildConnector provides thePeopleSoftVoucherStoreActon andPeopleSoftExtendedVoucherStoreActionto perform export to PeopleSoft.

In general, Voucher Build channels will consist of the following components: * Trigger: Integration ASQTrigger * Action: PeopleSoftVoucherStoreAction * Configuration: Mapping between Invoice eForm XML andPeopleSoft web service parameters.

* NOTE: The **PeopleSoftExtendedVoucherStoreAction** will only be availableif you [Enable Extended Voucher Build Messages](peoplesoft-config.html#enable-extended-voucher-build-messages)

If you are exportingmultiple invoice types (PO and Non-PO for example), you will need to have a channel foreach invoice type. Each channel will correspond to an Integration (ASQ) queue in yourWorkflow withinPerceptive Content.

Create a ChannelA channel defines themapping between the Invoice eForm data stored inPerceptive Content and the invoiceweb service into PeopleSoft. Complete the following steps to define this mapping.

1. In thePerceptive Connect Runtime Web Console, underPerceptive Connect, click Create aChannel.

2. InSelect a trigger, select the Integration ASQ Trigger.

3. InWorkflow Queue ID, type the queue ID of the Integration Queue (ASQ)where invoice documentswill be routed. For example: 321YY9C_0000RCLP800001W.

l NOTE: To find the queue ID, open theWorkflow Designer, right-click the desired queue, clickProperties. The ID is listed underDetails.

4. InSelect an action, select thePeopleSoftVoucherStoreAction orPeopleSoftExtendedVoucherStoreAction.

5. InConfigure Input Mapping, complete the steps defined in theMapData from an eForm section tocompolete themapping.

6. Click Next.

7. UnderConfigure output mapping, accept the default value.

8. Click Save Channel > OK.


23

Create Channel MappingTheVoucher Build Connectormaps data from anPerceptive Content eForm, such as the ImageNow APInvoice eForm, into the Voucher Build web service in PeopleSoft. Tomaximize configurability, any eFormfield can bemapped into any web service parameter. Therefore, custom eForms can use theVoucher BuildConnector to export to PeopleSoft.

l Refer to the data definition file for the eForm on yourPerceptive Content server. The eForm datadefinitions can be found in the server installation directory at [drive:]/inserver6/form/data_definition.

l TheVoucher Build Connector uses XPath to extract values from an eForm to populate the webservice request. You need to be familiar with this language before proceeding.

l Refer to the Perceptive Connect Runtime Installation and SetupGuide and the Perceptive ContentConnector Installation Guide for additional information on XML parameter mapping.

l Reasonable Default values for unmapped parameters are used. Refer to the PeopleSoft Web ServiceSupplemental Guide for information about parameters available in the PeopleSoft web service.

The following sections outline commonways tomap data from an invoice eForm to Voucher Build webservice parameters. * eForm Field * Literal Value * Document Field or Custom Property * Repeating ElementsUsing Rowsets * Nested Repeating Elements Using Rowsets

eForm Field<c:parameter>

<c:name>INVOICE_DT</c:name><c:xmlSource>

<c:reference>InvoiceXmlDoc</c:reference><c:xpath>/Invoice/InvoiceDate</c:xpath>


NOTE:InvoiceXmlDoc is defined outside the scope of this example. See the Channel Mapping Cookbookfor more details.

Literal ValuesLiteral (static) values can be used in themapping configuration

In header fields

<c:parameter><c:name>VOUCHER_ID</c:name><c:literal>NEXT</c:literal>

</c:parameter>

http://www.w3.org/TR/xpath/





24

In XML rowsets

Use the xpath values: string("[value]") and number(0) for XML rowset mappings:

<c:parameter><c:name>VOUCHER_ID</c:name><c:xmlSource>

<c:context>POLineItem</c:context><c:xpath>string("NEXT")</c:xpath>


Document Field or Custom Property<c:parameter>

<c:name>INVOICE_DT</c:name><in:objectPropertyReader>

<in:name>DRAWER</in:name><in:objectIdRef>DocId</in:objectIdRef><in:objectType>document</in:objectType><in:propertyType>key</in:propertyType>

</in:objectPropertyReader></c:parameter>

NOTE:DocId is defined outside the scope of this example. See the Channel Mapping Cookbook for moredetails.

Repeating Elements Using RowsetsThe <c:rowset> items for thePeopleSoftVoucherBuildStoreAction represent a collection of repeatingparameters required by the Voucher Build web service. For example, an invoice can havemultiple line items.Generally, an <c:xmlRowSource> will be used as illustrated in the following example.

<c:rowset><c:name>LINE</c:name><c:xmlRowSource>

<c:reference>InvoiceXmlDoc</c:reference><c:id>GLLineItem</c:id><c:xpath>/Invoice/GLLineItems/GLLineItem</c:xpath>

</c:xmlRowSource><c:mapping>

<c:parameter><c:name>MERCHANDISE_AMT</c:name><c:xmlSource>

<c:context>GLLineItem</c:context><c:xpath>GLExtAmount</c:xpath>


25

<c:name>BUSINESS_UNIT</c:name><c:xmlSource>

<c:reference>InvoiceXmlDoc</c:reference><c:xpath>GLUnit</c:xpath>

</c:xmlSource></c:parameter>...

</c:mapping></c:rowset>

NOTE: * The parameters contained by the <c:rowset> can reference the <c:xmlRowSource> using the<c:context> tag as illustrated above in theMERCHANDISE_AMT parameter. * The parameter containedby the <c:rowset> can reference the source XML document as InvoiceXmlDoc using the<c:reference> tag as illustrated above in theBUSINESS_UNIT parameter.

Nested Repeating Elements Using RowsetsA <c:rowset> can also be nested within other <c:rowset> items. For example, the PeopleSoft VoucherBuild web service allows multiple distributions (DIST) for multiple line items (LINE) in a given invoice. Nestedrowsets can be configured using themethods outlined in following example.

<c:rowset><c:name>LINE</c:name><c:xmlRowSource>

<c:reference>InvoiceXmlDoc</c:reference><c:id>GLLineItem</c:id><c:xpath>/Invoice/GLLineItems/GLLineItem</c:xpath>


...<c:rowset>

<c:name>DIST</c:name><c:xmlRowSource>

<c:reference>GLLineItem</c:reference><c:id>SubItem</c:id><c:xpath>.</c:xpath>


<c:parameter>

<c:name>BUSINESS_UNIT_CHILD</c:name><c:xmlSource>

<c:context>SubItem</c:context><c:xpath>GLUnit</c:xpath>

26

<c:parameter>

<c:name>BUSINESS_UNIT_GRANDCHILD</c:name><c:xmlSource>

<c:context>GLLineItem</c:context><c:xpath>BusinessUnit</c:xpath>


<c:parameter>

<c:name>BUSINESS_UNIT_HEADER</c:name><c:xmlSource>

<c:reference>InvoiceXmlDoc</c:reference><c:xpath>BusinessUnit</c:xpath>

</c:xmlSource></c:parameter>...

</c:mapping></c:rowset>...

</c:mapping></c:rowset>

NOTES: * The nested <c:rowset> item forDIST references the parent rowset using the <c:reference>tag. * Nested parameters can reference the parent <c:rowset> using the <c:context> tag as illustratedby theBUSINESS_UNIT_CHILD parameter. * Nested parameters can reference the grandparent<c:rowset> using the <c:context> tag as illustrated by theBUSINESS_UNIT_GRANDCHILDparameter. * Nested parameters can reference the source XML document (InvoiceXmlDoc) using the<c:reference> tag as illustrated by theBUSINESS_UNIT_HEADER parameter.

Sample Configurationl PO Invoice for the Perceptive AP eForm

l Non-PO Invoice for the Perceptive AP eForm

Related Informationl PeopleSoft Web Service Supplemental Guide

l Perceptive Connect Runtime Installation and SetupGuide


l Perceptive Connect Channel Mapping Cookbook

Configure Perceptive Content WorkflowPerceptive Voucher Build Connector for PeopleSoft


27

OverviewThe Perceptive Voucher Build Connector uses workflow Integration queues (ASQ) to trigger the export toPeopleSoft. Using your plan established in the install preparation, make the required changes to your existingworkflow process.


28

SampleWorkflow

Workflow Process Sample Screenshot


29

WorkflowQueue Details

QueueName

QueueType

Purpose Notes

APInvoiceExport -Filter

System Routes documents toappropriate Integration queue.

A routing rule should route documents to eitherPO Invoice Export orNon-PO Invoice Exportbased upon document type.

POInvoiceExport

Integration Executes channel in PerceptiveConnect for uploading POInvoices data to PeopleSoft.

Non-POInvoiceExport

Integration Executes channel in PerceptiveConnect for uploading Non-POInvoices data to PeopleSoft.

InvoiceExport -Stage

System Holding queue for documentsstaged in PeopleSoft waitingfor Voucher Build batch toexecute.

Documents will automatically move from thisqueue when batch executes in PeopleSoft. Atimeout should be configured as a fail-safemoving documents to Invoice Export -Timeout.

InvoiceExport -Recycle

System Terminal queue for documentsthat were successfully process,but require additionalprocessing in PeopleSoft toresolve issues

The connector will route recycled documents tothis queue from Invoice Export - Stage.

InvoiceExport -Success

System Terminal queue for documentsthat PeopleSoft Voucher Buildhas successfully processedfrom staging tables.

The connector will route successful documentsto this queue from Invoice Export - Stage.

InvoiceExport -Failure

System Terminal queue for documentsthat failed to export.

InvoiceExport -Timeout

System Terminal queue for documentsthat timeout while in staging.

PeopleSoft can, in certain cases, fail to stageor process stages invoices without notifying theconnector.

30

Design Considerations

Multiple Integration QueuesThe Voucher Build Connector requires a different Integration queue for each invoice, export type. Commontypes of invoices PO Invoices, Non-PO Invoices, and Credit Memos. Each of these invoice types will requirea distinct Integration queue in order to handle the each types unique parameters sent to the PeopleSoft webservice.

It is advisable to create a routing schemewhere the Integration queues sit behind a system queue configuredwith a routing rule. Routing based upon document type would be a common rule to employ.

Staging TimeoutThe PeopleSoft Voucher Build is a batch system. The Voucher Build Connector attempts to stage data inPeopleSoft. If staging fails, PeopleSoft does not always inform the connector. It is advisable to create aqueue timeout to move documents to an appropriate failed state when PeopleSoft fails to respond with astatus.

Perceptive Connect Channel Mapping CookbookPerceptive Voucher Build Connector for PeopleSoft

OverviewThePerceptive Voucher Build Connector leverages the Perceptive Connect Runtime (PCR) and thePerceptive Content Connector (PCC). Creating the channel linking an Integration queue (ASQ) with thePeopleSoftVoucherBuildStoreAction requires the composition of an XML channel configuration.

The following reference document outlines some patterns generally found in the channel configuration. Moreinformation about Perceptive Connect Triggers, Actions, Readers andWriters can be found in the installationguides. See the Related Information section for links to this content.

Get Document from Workflow ItemTypically, an Integration queue will trigger thePeopleSoftVoucherBuildStoreAction using the IntegrationASQ Trigger. The Integration ASQ Triggerwill supply theWorkflow Item Id of the triggering item. ThisDocument Id can then be found using a theWorklow Item Reader.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><c:inputs xmlns:c="http://www.perceptivesoftware.com/pif/mapping"xmlns:ns2="http://www.perceptivesoftware.com/pie/mapping/sample"xmlns:in="http://www.perceptivesoftware.com/pif/imagenow">

<c:parameter>

31

<c:name>DocId</c:name><in:workflowItem>

<in:reference>WFId</in:reference><in:objectType>WORKFLOW</in:objectType><in:objectField>OBJECT_ID</in:objectField>

</in:workflowItem></c:parameter>

<c:parameter>

<c:name>WFId</c:name><c:trigger>WorkflowItemId</c:trigger>

</c:parameter>...

</c:inputs>

Get eForm Content from DocumentThe content of an eForm associated with a document can be obtained using the Form Reader as illustratedby the following example.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><c:inputs xmlns:c="http://www.perceptivesoftware.com/pif/mapping"xmlns:ns2="http://www.perceptivesoftware.com/pie/mapping/sample"xmlns:in="http://www.perceptivesoftware.com/pif/imagenow">

<c:parameter>

<c:name>InvoiceXmlDoc</c:name><in:eFormSource>

<in:reference>DocId</in:reference><in:name>AP Invoice</in:name><in:type>DOCUMENT</in:type>

</in:eFormSource></c:parameter><c:parameter>

<c:name>DocId</c:name><in:workflowItem>

<in:reference>WFId</in:reference><in:objectType>WORKFLOW</in:objectType><in:objectField>OBJECT_ID</in:objectField>

</in:workflowItem></c:parameter>

<c:parameter>

<c:name>WFId</c:name><c:trigger>WorkflowItemId</c:trigger>

</c:parameter>


32

...</c:inputs>

Related Informationl Perceptive Connect Runtime Installation and SetupGuide


PeopleSoft Voucher Build Connector release notes2.1.0

F12472l Added Support for ExtendedMessage types in the PeopleSoft Voucher Build Message

l Added Support for logging PeopleSoft Voucher Build Message

l Added Support for simulating the outbound call to PeopleSoft for testing the Voucher Build Message

l Fixed an issue that caused the PeopleSoft Voucher Build Store Action to fail during and upgrade from2.0.0 to 2.0.2

l Changed the default values for parameters in the PeopleSoft Voucher Build Messagesl All Number type parameters default to null and are not included in themessage unless mapped. SeethePeopleSoft Voucher Build Supplimental Guide for details

l Unmapped Date type parameters are still defaulted to theCurrent Date but can now bemapped tonull

<c:parameter><c:name>ENTERED_DT</c:name><c:null/>

</c:parameter>

2.0.2Issue #27 Default dates now default to the current date instead of the date Perceptive Connect Runtime wasstarted Issue #26 Support for multiple Transactions in PeopleSoft Voucher Responsemessage Issue #25Legacy support for PeopleTools serialization defect in PeopleTools 8.48.17 and below

2.0.0Support for Perceptive Connect Runtime

1.0.0Initial release based in depricated Perceptive Integration Framework webapp



Perceptive Voucher Build Connector for PeopleSoft ... · PDF file© ....

Documents

Transcript of Perceptive Voucher Build Connector for PeopleSoft ... · PDF file© ....