This chapter includes these topics:
Section 34.1, "Additional Financial Management Solutions Interface Component Overview"
Section 34.2, "FinancialComplianceManager Business Services"
This chapter provides detailed information about the business interface components available for the Financial Management Solutions (FMS) product suite, that are not associated with other business interfaces.
This table lists all of the additional interface components:
|
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." |
The FinancialComplianceManager web service (JP000040) manages the processing of compliance-related web service operations. This table includes a description of the financial compliance web service operations:
To access Javadoc for the Financial Compliance Manager web service and its related operations, review these Javadoc packages:
JP000040 (FinancialComplianceManager)
J0000041 (getAPProcessingOptions)
J0000042 (getWriteOffProcessingOptions)
J0000043 (getAgingCompanyConstants)
J0000044 (getCustomerCreditLimits)
J0000045 (getGeneralConstants)
J0000046 (getJournalGeneralConstants)
J0000047 (getPolicyEditRules)
J0000048 (getPurchasingToleranceRules)
J0000049 (getSecurityWorkbench)
The getAPProcessingOptions web service operation is a business function query operation that enables consumers to retrieve and review the processing option values for these programs in the JD Edwards EnterpriseOne system:
Recycle Recurring Vouchers (R048101)
Purchase Order Receipts (P4312)
You can retrieve processing options for selected versions, or for all versions. If the operation encounters errors while processing, those errors are returned to the consumer.
This table includes information that can help determine whether the getAPProcessingOptions operation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If the operation completes successfully, the system returns all processing option values for the specified programs and versions.
The records that are returned to the consumer include 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. |
| If I encounter errors while process a transaction, do I need to reverse the transaction? | This is a query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and try your query again. If the operation does not return any records, verify that a version matching your query exist in the JD Edwards EnterpriseOne database. |
| Does this operation use record reservation? | No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing. |
The getWriteOffProcessingOptions web service operation is a business function query operation that enables consumers to retrieve and review the processing options for these JD Edwards EnterpriseOne Accounts Receivable programs:
Standard Receipts Entry (P03B102)
Draft Entry (P03B602)
Speed Receipts Entry (P03B0001)
Invoice Selection Match (R03B50A)
Known Invoice Match With Amount (R03B50D)
Known Invoice Match Without Amount (R03B50E)
You can retrieve processing options for selected versions, or for all versions. If the operation encounters errors while processing, those errors are returned to the consumer.
This table includes information that can help determine whether the getWriteOffProcessingOptions operation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If the operation completes successfully, the system returns the processing option values for the selected programs and versions.
The records that are returned to the consumer include 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. |
| If I encounter errors while process a transaction, do I need to reverse the transaction? | This is a query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and try your query again. If the operation does not return any records, verify that a version matching your query exist in the JD Edwards EnterpriseOne database. |
| Does this operation use record reservation? | No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing. |
Before you use this operation, you should have an understanding of the Accounts Receivable system, with specific knowledge of drafts and receipts processing.
See "Setting Up Accounts Receivable Drafts", "Setting Up Automatic Receipts Processing", "Processing Manual Receipts", and "Processing Accounts Receivable Drafts" in the JD Edwards EnterpriseOne Applications Accounts Receivable Implementation Guide.
The getAgingCompanyConstants web service operation is a database query operation that enables consumers to retrieve and review company constant records from the Company Constants table (F0010) in the JD Edwards EnterpriseOne system. The operation returns zero to many records, based on the selection criteria that the consumer passes in, and on the maximum number of rows to return, as defined in the business service properties.
If the consumer does not pass in selection criteria for the fromCompany and toCompany fields, the operation uses these default values when processing the query:
fromCompany: 00000
toCompany: 99999
This operation returns to the consumer all errors and warnings encountered during processing.
Before you use this operation, you can set business service properties to specify how the system retrieves data from the JD Edwards EnterpriseOne database. This table includes information about the business service properties that the getAgingCompanyConstants operation uses:
| Group | Key | Description | Default Value |
|---|---|---|---|
| J0000043 | J0000043_QUERY_MAX_ROWS | Use this business service property to specify the maximum number of records the operation returns for a query. | 100 |
|
Note: It is recommended that you configure and use this business service property, and that you send in selection criteria when performing a query. If you leave this property blank, or set it to 0 (zero), the system does not limit the number or records to return. Therefore, sending in a blank query when this property is not set to limit the number of records returned could cause significant performance issues. |
This table includes information that can help determine whether the getAgingCompanyConstants operation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If the operation completes successfully, the system displays company constant records matching the selection criteria. If no records match the selection criteria, the operation returns a response message with an empty array.
The records that are returned to the consumer include 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. |
| If I encounter errors while process a transaction, do I need to reverse the transaction? | This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database. |
| Does this operation use record reservation? | No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing. |
The getCustomerCreditLimits web service operation is a database query operation that enables consumers to retrieve and review accounts receivable information, such as credit limits, for selected customers in the JD Edwards EnterpriseOne system. The operation retrieves information from the Customer Master by Line of Business table (F03012).
If the operation encounters errors, processing stops and all errors are returned to the consumer.
Before you use this operation, you can set business service properties to specify how the system getCustomerCreditLimits operation retrieves data. This table includes information about the business service properties that the getCustomerCreditLimits operation uses:
| Group | Key | Description | Default Value |
|---|---|---|---|
| J0000044 | J0000044_MAX_ROWS | Use this business service property to specify the maximum number of records that the operation can return for a query. | 100 |
|
Note: It is recommended that you configure and use this business service property, and that you send in selection criteria when performing a query. If you leave this property blank, or set it to 0 (zero), the system does not limit the number or records to return. Therefore, sending in a blank query when this property is not set to limit the number of records returned could cause significant performance issues. |
This table includes information that can help determine whether the getCustomerCreditLimits operation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If the operation completes successfully, the system displays accounts receivable records for the specified customers.
The records that are returned to the consumer include 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. |
| If I encounter errors while process a transaction, do I need to reverse the transaction? | This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database. |
| Does this operation use record reservation? | No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing. |
Before you use this operation, verify that credit and collection information for your customers exists in the JD Edwards EnterpriseOne Accounts Receivable system.
See "Setting Up Customer Master Information", and "Setting Up Credit and Collections Management" in the JD Edwards EnterpriseOne Applications Accounts Receivable Implementation Guide.
The getGeneralConstants web service operation is a database query operation that enables consumers to retrieve and review general constants from the General Constants table (F0009) in the JD Edwards EnterpriseOne system. The constant that this operation displays determines how the system handles duplicate invoice numbers.
If the operation encounters errors, processing stops and the errors are returned to the consumer.
|
Note: The F0009 contains only one record. Therefore, this operation will not return multiple records. |
This table includes information that can help determine whether the getGeneralConstants operation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If the operation completes successfully, the record that exists in the F0009 table is returned to the consumer.
This record 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 a non-zero value for the duplicateInvoiceNumberEdit field. |
| If I encounter errors while process a transaction, do I need to reverse the transaction? | This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and try your query again. If the operation does not return any records, verify that a record matching your query exist in the JD Edwards EnterpriseOne database. |
| Does this operation use record reservation? | No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing. |
The getJournalGeneralConstants web service operation is a database query operation that enables consumers to retrieve and review general constants from the General Constants table (F0009) in the JD Edwards EnterpriseOne system. This operation returns constants that determine how the system processes journal entry information. For example, you can use this operation to review whether batch control or management approval is required, whether postings or invalid accounts are allowed, and whether the system processes intercompany settlements or multicurrency transactions.
If the operation encounters errors, processing stops and the errors are returned to the consumer.
|
Note: The F0009 contains only one record. Therefore, this operation will not return multiple records. |
This table includes information that can help determine whether the getJournalGeneralConstants operation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If the operation completes successfully, the record that exists in the F0009 table is returned to the consumer.
This record 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 process a transaction, do I need to reverse the transaction? | This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and try your query again. If the operation does not return any records, verify that a record matching your query exist in the JD Edwards EnterpriseOne database. |
| Does this operation use record reservation? | No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing. |
The getPolicyEditRules web service operation is a database query operation that enables consumers to retrieve and review policy edit rule information from the JD Edwards EnterpriseOne Expense Management system. The operation retrieves information from the Policy Edit Rules table (F09E108).
If the operation encounters errors, processing stops and the errors are returned to the consumer.
Before you use this operation, you can set business service properties to specify how the system retrieves data from the JD Edwards EnterpriseOne database. This table includes information about the business service properties that the getPolicyEditRules operation uses:
| Group | Key | Description | Default Value |
|---|---|---|---|
| J0000047 | J0000047_MAX_ROWS | Use this operation to specify the maximum number of records that the system returns for a query. | 100 |
This table includes information that can help determine whether the getPolicyEditRulesoperation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If the operation completes successfully, policy edit rule records are returned to the consumer.
The records that are returned to the consumer include 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. |
| If I encounter errors while process a transaction, do I need to reverse the transaction? | This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service properties and try your query again. If the operation does not return any records, verify that a record matching your query exist in the JD Edwards EnterpriseOne database. |
| Does this operation use record reservation? | No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing. |
The getPurchasingToleranceRules web service operation is a database query operation that enables consumers to retrieve and review tolerance rules from the JD Edwards EnterpriseOne Procurement system. The operation retrieves data from the Purchasing Tolerance Rules table (F4322).
If the operation encounters errors, processing stops and the errors are returned to the consumer.
Before you use this operation, you can set business service properties to specify how the system retrieves data from the JD Edwards EnterpriseOne database. This table includes information about the business service properties that the getPurchasingToleranceRules operation uses:
| Group | Key | Description | Default Value |
|---|---|---|---|
| J0000048 | J0000048_MAX_ROWS | Use this operation to specify the maximum number of records that the system returns for a query. | 100 |
This table includes information that can help determine whether the getPurchasingToleranceRules operation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If the processing completes successfully, the operation returns zero to many records, based on the query.
The records that are returned to the consumer include 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. |
| If I encounter errors while process a transaction, do I need to reverse the transaction? | This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service properties and try your query again. If the operation does not return any records, verify that a record matching your query exist in the JD Edwards EnterpriseOne database. |
| Does this operation use record reservation? | No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing. |
The getSecurityWorkbench web service operation is a database query operation that enables consumers to retrieve and review security workbench records from the JD Edwards EnterpriseOne system. The operation retrieves data from the Security Workbench table (F00950).
The operation returns security records for these JD Edwards EnterpriseOne programs:
Manual Payments (P0413M)
Work With Payment Groups (P04571)
Create Payment Groups (R04570)
Speed Status Change (P0411S)
Multi Company Voucher (P041016)
Multiple Voucher (P041017)
Standard Voucher (P0411)
Speed Voucher (P0411SV)
Supplier Master (P04012)
If the operation encounters errors, processing stops and the errors are returned to the consumer.
Before you use this operation, you can set business service properties to specify how the system retrieves data from the JD Edwards EnterpriseOne database. This table includes information about the business service properties that the getSecurityWorkbenchoperation uses:
| Group | Key | Description | Default Value |
|---|---|---|---|
| J0000049 | J0000049_MAX_ROWS | Use this operation to specify the maximum number of records that the system returns for a query. | 0: Return All Rows |
|
Note: The maximum number of rows that this operation can return is minimal. Leaving this option set to zero does not cause performance issues. |
This table includes information that can help determine whether the getSecurityWorkbenchoperation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If the processing completes successfully, the operation returns zero to many records, based on the query.
The records that are returned to the consumer include 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. |
| If I encounter errors while process a transaction, do I need to reverse the transaction? | This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service properties and try your query again. If the operation does not return any records, verify that a record matching your query exist in the JD Edwards EnterpriseOne database. |
| Does this operation use record reservation? | No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing. |
The FinancialManager web service (JP090000) manages the processing of financial-related web service operations. This table includes a description of the financial web service operations:
To access Javadoc for the Financial Compliance Manager web service and its related operations, review these Javadoc packages:
JP090000 (FinancialManager)
J0900001 (getGLAccount)
J0900002 (insertBatchJournalEntry)
The getGLAccount operation is a database query operation that enables consumers to retrieve and review general ledger account records from the Account Master table (F0901) in the JD Edwards EnterpriseOne General Accounting system. If the operation encounters errors during processing, the operation does not complete and the errors are returned to the consumer.
This table includes information that can help determine whether the getGLAccount operation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If the operation completes successfully, the system returns records that match the query, if they exist. If the operation ends in error, the consumer receives an error message.
The records that are returned to the consumer include 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. |
| If I encounter errors while process a transaction, do I need to reverse the transaction? | This is a query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and try your query again. If the operation does not return any records, verify that a version matching your query exist in the JD Edwards EnterpriseOne database. |
| Does this operation use record reservation? | No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing. |
The insertBatchJournalEntry operation is a database insert operation that enables consumers to add journal entry records to the Journal Entry Transactions - Batch table (F0911Z1). The F0911Z1 is a temporary table in the JD Edwards EnterpriseOne General Accounting system. After records have been added to this table, consumers can use JD Edwards EnterpriseOne programs to update and process the journal entries that have been added to the temporary table.
This table includes information that can help determine whether the insertBatchJournalEntry operation is functioning correctly:
| Question | Answer |
|---|---|
| How can I tell if the operation completes successfully? | If the operation completes successfully, the system inserts records into the table. |
| If I encounter errors while process a transaction, do I need to reverse the transaction? | If the service does not complete successfully, no records are inserted into the table. You must reprocess the action to insert the records. |
| Does this operation use record reservation? | No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing. |