This chapter includes these topics:
This chapter provides detailed information about the business interfaces that are available for the Procurement Voucher business object.
This table lists all of the available interface components:
| Interface Type | Available Interfaces |
|---|---|
| Business Services | The VoucherMatchManager published business service (JP43B000) manages these web service operations: |
| Batch Import Programs | This list includes the batch import programs for the Procurement Voucher business object:
|
|
Note: You can find additional technical information about each type of business interface component. For additional descriptions of the information available, and instructions for finding this information, see Chapter 5, "Accessing Additional Information for Business Interface Components." |
This section describes the available business services associated with the VoucherMatchManager published business service (JP43B000), which is part of the Procurement Voucher business object. The business services include:
| Operation | Description |
|---|---|
| processVoucherMatch (J43B0010) | Use this operation to add voucher match records for logged vouchers and both two-way and three-way voucher match within the JD Edwards EnterpriseOne Procurement system. This operation also supports additional charge information lines for a voucher along with purchase order lines being vouchered. |
| processsVoucherMatchV2 (J43B0010) | Use this operation to add voucher match records for logged vouchers and both two-way and three-way voucher match within the JD Edwards EnterpriseOne Procurement system. This operation also supports additional charge information lines for a voucher along with purchase order lines being vouchered. Additionally, this version includes global location number (GLN). |
| processVoucherMatchV3 (J43B0010) | Use this operation to override the tax during voucher match within the JD Edwards EnterpriseOne Procurement system. The taxOverride must be set to Y for retaining the overridden tax on voucher. Otherwise the system will calculate tax based on tax information on purchase order. |
| processVoucherMatchV4 (J43B0010) | Use this operation to override the tax explanation code and tax rate area for purchase order detail lines during voucher match within the JD Edwards EnterpriseOne Procurement system. This way, the accounts payable system can account for any change in the tax rate area and tax explanation code from the time the purchase order was created to the time it is vouchered. The taxes can also be accrued at the time of voucher match. |
| processVoucherMatchV5 (J43B0010) | Use this operation to choose and voucher partially received lines from a purchase order as part of the Voucher Match Manager web service during voucher match within the JD Edwards EnterpriseOne Procurement system. This helps in creating vouchers quickly and accurately for partially received lines on a purchase order. |
To access Javadoc for the VoucherMatchManager web service and its related operations, review these Javadoc packages:
JP43B000 (VoucherMatchManager)
J43B0010 (processVoucherMatch)
J43B0010 (processVoucherMatchV2)
J43B0010 (processVoucherMatchV3)
J43B0010 (processVoucherMatchV4)
J43B0010 (processVoucherMatchV5)
Before you use the Voucher Match Manager web service, or any of the related operations, you must install and set up the JD Edwards EnterpriseOne Procurement and JD Edwards EnterpriseOne Accounts Payable systems.
This section provides an overview of the processVoucherMatch web service operation, lists prerequisites, and discusses how to set processing options for Purchase Order XPI (P43XPI).
The processVoucherMatch operation is an inbound transaction operation that enables consumers to process voucher match information within the JD Edwards EnterpriseOne system. The consumer can add voucher match records to the JD Edwards EnterpriseOne Procurement system for logged vouchers and both two-way and three-way voucher match. This operation also supports additional charge lines for purchase order detail lines on a voucher.
If the operation completes successfully, the system returns a confirmation message to the consumer. This message contains voucher match data. The system also returns to the consumer any error messages that the operation encounters during processing.
The processVoucherMatch operation processes a voucher match in the JD Edwards EnterpriseOne system. The first call of the XPIInboundVoucherMatch business function (B4302300) checks for record reservation. If the business function finds that any record is reserved, the system stores the error in the Message List and returns from flow.
For an additional charge line, the XPIInboundVoucherMatch business function passes tax information into the taxRateArea, taxExplanationCode, additionalChargeQty, amount, lineTaxableCode, description1, lineTaxAmount, and expenseAcctNumber fields.
The system uses the following processing logic to handle tax for additional charge lines:
Pass the following information to the VM Edit Line if the operation passes a non-zero value to the lineTaxAmount field:
Set the lineTaxableCode to Y.
Use the taxRateArea and taxExplanationCode if the operation passes these values.
Use the values from the first PO Detail record fetched for the passed in PO header information if either the taxRateArea or the taxExplanationCode value passed in is blank.
Use the values from the supplier purchasing information's default tax values if either the taxRateArea or the taxExplanationCode value passed in is blank.
Pass the following information to the VM Edit Line if the operation passes a non-empty and non N value for the lineTaxableCode field:
Use the values the operation passes in for the taxRateArea and taxExplanationCode fields.
Use the values from the first PO Detail record fetched for the passed in PO header information if either the taxRateArea or the taxExplanationCode value passed in is blank.
Use the values from the supplier purchasing information's default tax values if either the taxRateArea or the taxExplanationCode value passed in is blank.
Do not pass in the tax information to the VM Edit Line function if the integration passes in N or blank lineTaxableCode value.
The system uses the expense account number if the B4302300 business function passes it into the system. If the expense account number is not passed in then the system uses the default account number from the P43XPI processing options.
Before using the processVoucherMatch operation, you must:
Set the Voucher Type processing option on the Voucher Match tab of the P43XPI program.
|
Note: It is recommended that you set the Voucher Type processing option to 1. This processing option setting enables the operation to process matched and logged vouchers. |
Set the 2. Voucher Match Processing Option Version (P4314) processing option on the Versions tab of the P43XPI program.
Set the 2. Expense Account for Additional Charges processing option on the Voucher Match tab of the P43XPI program for additional charges.
Set the processing options for the version of P4314 called by the P43XPI program.
Set the 8. Orders Per Voucher processing option on the Process tab of the P4314 program to 1.
Set the 1. Order Line Entry processing option on the New Order Line tab of the P4314 program to 2 for additional charges.
Set the 2. Line Type processing option on the New Order Line tab of the P4314 program to J for additional charges.
Set the 3. Last Status Code processing option on the New Order Line tab of the P4314 program to 400 for additional charges.
Set the 3. AP Master Business Function Processing Option Version for Logged Vouchers (P0400047) processing option on the Versions tab of the P43XI program.
Set the processing options for the version of P0400047 called by the P43XPI program.
|
Note: If logged vouchers are enabled in the Voucher Type processing option on the Voucher Match tab of the P43XPI program, then you must set the 1. Voucher Logging processing option on the Logging tab of the P0400047 program. |
This section discusses the functionality that the processVoucherMatch operation supports.
|
Note: If functionality is not explicitly documented as supported functionality, it is to be understood that the functionality is not supported by the integration solution. |
The consumer can add voucher match records to the JD Edwards EnterpriseOne Procurement system. The operation supports both two-way and three-way voucher match. The consumer can also create a logged voucher. The operation processes only one line for the logged voucher.
The processVoucherMatch operation does not support the following functionality:
Change voucher
Delete voucher
Reverse voucher
Voucher redistribution
Recost vouchers
Before you use this operation, you can set business service properties to define how the system processes voucher match data. If you do not set these business service properties, the system uses default values for each constant. This table includes information about the business service properties used by the processVoucherMatch operation:
| Group | Key | Description | Default Value |
|---|---|---|---|
| J43B0010 | J43B0010_P43XPI_VERSION | Use this business service property to specify which version of the Purchase Order XPI program (P43XPI) the operation uses. | ZJDE0001 |
| J43B0010 | J43B0010_BYPASS_BSFN_WARNINGS | Use this business service property to specify whether the system converts warning messages to errors during processing. | 1
Note: The system does not treat warnings as errors so the system keeps processing. |
| J43B0010 | J43B0010_PREFIX_1 | Use this business service property to specify the prefix value the operation uses for error messages when JD Edwards EnterpriseOne processes detail lines. | VoucherMatchRecordSentin |
| J43B0010 | J43B0010_PREFIX_2 | Use this business service property to specify the prefix value the operation uses for error messages when JD Edwards EnterpriseOne processes additional charges. | VoucherMatchAdditionalRecordSentin |
The processVoucherMatch web service operation calls the XPIInboundVoucherMatch business function (B4302300) which calls the Purchase Order XPI program (P43XPI). You must set the processing options for the P43XPI program, which provides the input for the voucher type. You must set the Voucher Type processing option on the Voucher Match tab.
See Section 83.2.4, "Setting Processing Options for Purchase Order XPI (P43XPI).".
The following table includes information that can help determine whether the processVoucherMatch operation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If a business service exception is not thrown, then the operation completed successfully and the system returns a confirmation message to the consumer.
The return message includes all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system. At a minimum, the system returns non-zero values for these fields:
|
| If I encounter errors while processing a transaction, do I need to reverse the transaction? | This operation uses standard transaction processing. Therefore, if you encounter errors during processing, the system does not update any information in the JD Edwards EnterpriseOne system. No manual update is necessary. |
| Does this operation use record reservation? | This operation calls the XPIInboundVoucherMatch business function (B4302300). This function reserves records in the JD Edwards EnterpriseOne system when the operation adds voucher match records for both two-way and three-way voucher match. |
Processing options enable you to specify the default processing for programs and reports.
For programs, you can specify options such as the default values for specific transactions, whether fields appear on a form, and the version of the program that you want to run.
Specify a value from UDC 40/AT that indicates the last step in the processing cycle that this order line has successfully completed.
Specify a value from UDC 40/AT that indicates the next step in the order flow of the line type.
Specify a value from UDC 40/AT that indicates the next step in the order flow of the line type.
Specify a value from UDC 40/AT that indicates the next step in the order flow of the line type.
Specify a value from UDC 40/AT indicates the next step in the order flow of the line type.
Specify the version that the system uses when you enter a purchase order.
Specify the version that the system uses when you match an invoice to a purchase order line or receipt line. If the Voucher Match processing option, which is located on the Voucher Match tab, is set to 1 or 2, the system validates the version that you specify.
Specify the version that the system uses when you log a voucher for an invoice. If the Voucher Match processing option, which is located on the Voucher Match tab, is set to blank or 1, the system validates the version that you specify to ensure that the voucher logging process is active.
Specify a value from UDC 40/AT that indicates the next step in the order flow of the line type.
Specify whether the system advances the shipment status of the line or order. Values are:
Blank: Do not advance to Shipped Status.
1: Advance to shipped status (no receipt).
Specify whether the system creates a logged voucher or matched voucher. Values are:
Blank: The system always creates a logged voucher.
1: If the invoice includes specific purchase order information, the system creates a matched voucher. If the invoice does not include specific purchase order information, the system creates a logged voucher.
2: The system always creates a matched voucher.
Specify the account that the system uses to expense the additional charges that are specified on the invoice. You set up the account format in the General Accounting Constants program (P0000), using one of the following formats for account numbers:
Structured account (business unit.object.subsidiary)
25-digit unstructured number
25-digit unstructured number
8-digit short account ID number
Speed code
Review the information in the processVoucherMatch section of this chapter before using the processVoucherMatchV2 web service operation. All of the information in the processVoucherMatch section also applies to the processVoucherMatchV2 operation.
The processVoucherMatchV2 operation is a version of the processPurchaseVoucherMatch web service operation. This web service operation is used to add voucher match records for logged vouchers along with GLNs. This version executes the processPurchaseOrder (J43B0010) web service operation.
Review the information in the processVoucherMatch section of this chapter before using the processVoucherMatchV3 web service operation. All of the information in the processVoucherMatch section also applies to the processVoucherMatchV3 operation.
The processVoucherMatchV3 operation is a version of the processPurchaseVoucherMatch web service operation. This web service operation is used to override tax. The taxOverride field under the Financial Detail section must be set to Y for retaining the overridden tax on voucher. Otherwise, the system will calculate tax based on the tax information on the purchase order. This version executes the processPurchaseOrder (J43B0010) web service operation.
Review the information in the processVoucherMatch section of this chapter before using the processVoucherMatchV4 web service operation. All of the information in the processVoucherMatch section also applies to the processVoucherMatchV4 operation.
The processVoucherMatchV4 operation is a version of the processPurchaseVoucherMatch web service operation. This web service operation is used to override the tax explanation code and tax rate area for purchase order detail lines during voucher match. This way, the accounts payable system can account for any change in the tax rate area and tax explanation code from the time the purchase order was created to the time it is vouchered. The taxes can also be accrued at the time of voucher match. By providing this capability, the Voucher Match Manager web service works similar to the standard voucher program P4314 for tax rate area override. When the amountTax field in the Financial Detail has a value, the lineTaxableCode is set to Y by default. When the detail tax amount is zero, the lineTaxableCode value is considered for voucher match. This version executes the processPurchaseOrder (J43B0010) web service operation.
Review the information in the processVoucherMatch section of this chapter before using the processVoucherMatchV5 web service operation. All of the information in the processVoucherMatch section also applies to the processVoucherMatchV5 operation.
The processVoucherMatchV5 operation is a version of the processPurchaseVoucherMatch web service operation. This web service operation provides the ability to choose and voucher partially received lines from a purchase order as part of the Voucher Match Manager web service. This helps in creating vouchers quickly and accurately for partially received lines on a purchase order. By providing this capability, the Voucher Match Manager Web Service will work similar to the standard voucher program P4314. When the receiptLineNumber field in the Detail has a valid value greater than zero, the Voucher Match Manager searches for a purchase order receipt record to create a three-way Voucher Match. When the receiptLineNumber is blank it is not considered as input value; purchase order or receipt record for Voucher Match are selected based on the other input values provided. Invalid value in the receiptLineNumber results in error. This version executes the processPurchaseOrder (J43B0010) web service operation.
You use batch import programs to import data from an external software system into the JD Edwards EnterpriseOne system, where it can then be processed by EnterpriseOne programs.
This table lists and describes the available batch import programs that are associated with the Procurement Voucher business object: