Title: Enterpriseone 8.9 OCM Mappings for Business Functions Invalid

Title: EnterpriseOne 8.9 OCM Mappings for Business Functions Invalid

Abstract: There is a known issue with EnterpriseOne 8.9 business function mappings. This document describes the issue and a resolution to clean up the invalid mappings and create appropriate mappings for the environments.

EnterpriseOne 8.9 OCM Mappings for Business Functions Invalid

Business function OCM mappings for upgrades or installs of EnterpriseOne 8.9 are incorrectly created during the planner validation step and therefore can cause multiple application issue since certain functions can not be mapped to the server for standard environments.

There are approximately 400 business functions mapped incorrectly to the server that should not have any mapping. The default mapping for business functions is set to run locally for standard environment names. The incorrect OCM mappings created by the default EnterpriseOne 8.9 OCM creation can cause incorrect behavior and failures from business functions while running applications from a standard environment. JAS environments are not affected by this issue.

SAR# 7125594 has been entered and will be released in the next planner ESU for EnterpriseOne 8.9. This SAR will fix the problem for any new installs, upgrades, or for any new environments created after the SAR has been installed. Existing environments however will require the manual fix below. The resolution below does not require the planner ESU containing SAR #7125594 so all of these instructions can be completed without an updated ESU.

Table of Contents
1. Resolution
2. Default Results for R986140
3. Known Issues Caused by Invalid OCM Mappings
4. Considerations

1. Resolution

The resolution provided is highly recommended for all clients to test in their development and prototype environments prior to implementing any changes in production. A backup should be made of the F986101 table prior to any changes being done on the system. If your environment has a large number of custom mappings then please remember to retain these records or recreate the custom OCMs at the end of the process. This process is intended to be run only against standard environments and will not be needed for JAS environments.

Please follow these steps to resolve the issue with invalid OCM mappings.

1. Log into the deployment server in the DEP9 environment.
2. Launch the OCM application from the fastpath.
3. Choose the System - B9 and find all records for your environment where the object type is equal to 'BSFN'. In this step you should also filter by the appropriate non-JAS environment (i.e. DV9, PY9,...) and you can also filter on user or *PUBLIC. You can select using shift-click to select all records in the grid after going to the bottom record in the list. If you want you can exclude any custom OCM mappings you don't want removed at this time. Business functions with a function location of 3 will get a server mapping by default in the next steps.
4. Delete all records selected. The deletion of the records is needed since the UBE run is step 5 will recreate the appropriate mappings. The DEFAULT record will not be removed and should be active and pointing to LOCAL.
5. Now run BV (Batch Versions) from the fastpath and enter the R986140 and hit find.
6. Copy the XJDE0001 Version to a custom version name.
7. Change the PO Options to the following for this new custom version (run in proof mode first to see the list of affected OCM mappings for functions).

Option 1. 1 (1 for Final Mode or 0 for Proof Mode)
Option 2. Servername - Logic (The servername datasource for the proper server name for the mapping)
Option 3. DV9 (this value will allow you to run for each environment -- change this to the proper names for each of your environments)
Option 4. System - B9 (this value is the default location for the OCM mapping table)

1. Change the Data Selection for BC Location so that the right operand is equal to 3 only (the default is 2,3). This step is critical since the default data selection will cause the process to create thousands of invalid mappings if the value of 2 is left in place.
2. Override the location through batch versions to run this UBE locally.
3. Once this report is run in final mode please check to make sure the mappings are correct and any custom mappings are recreated or retained if they were not deleted in step #4.
4. Repeat these steps for each environment. It is also required that you clean up OCM mappings locally on the deployment server by running the same steps while logged into JDEPLAN and changing Processing Option 4 in step #7 to point to the OneWorld Planner - B9 database.

Note: Changes to OCMs will require that any fat client or Citrix server be restarted to cache the new OCM table information created by this process. Application and Logic servers do not require a restart.

2. Default Results of R986140

The new OCM mappings by default should map the following objects to the ServerName - Logic datasource after using the resolution above. Exceptions to this and considerations are detailed below.

* These two functions automatically get a server mappings however it is recommended that the mappings be deactivated or removed. Please see the considerations section below for more detail.

3. Known Issues Caused by Invalid OCM Mappings

The incorrect OCM mappings created by the default EnterpriseOne 8.9 OCM creation can cause incorrect behavior and failures from business functions while running applications from a standard environment. JAS environments are not affected by this issue. Some of the identified issues caused by the incorrect OCM mappings are the following:

• The following functions fail for UBE's run locally that write to the WorkCenter. The UBE will show a memory violation in the PDF:
  B0100011 Error Message Processor to PPAT System
  B0100025 Initialize PPAT Error Message API
  
• The following functions fail for interactive applications. The user will receive a pop-up stating 'Commit Failed or was Cancelled':
  B03B0011 Invoice Entry Master Business Function
  B03B0012 F03B14 Apply Receipt to Invoice
  B03B0138 F03B13 Maintain Receipt Header
  B03B0149 F03B14 Maintain Receipt Detail
  B0400047 Voucher Entry Master Business Function
  B0900049 Journal Entry
  
• If not all of the Commissions Business Functions are mapped to the same location as Sales Order Entry Master Business Functions (B4200310 & B4200311), then commission information will not get populated during Sales Orders Entry (P4210). The resolution above will remove any incorrect mappings with these functions and set them all to use the default local business function mapping for the environment.
  All of the Commissions Business Functions listed below should be mapped to the the same location as Sales Order Entry Master Business Functions (B4200310 & B4200311):
  B4205090
  B4202160
  B4202170
  B4202180
  B4200050
  
• In EnterpriseOne 8.9, if the business functions related to advanced pricing are not mapped to the same location as the Sales Order Entry Master Business Functions (B4200310 & B4200311), then errors are returned for some advanced pricing processes.

First, when running Basket/Order Level Reprice (R42750) two errors are returned:

1. Open Cursor for Cache F42IU12 Failed (error id: 078M)
2. Fetch from Cache Failed (error id: 078N)

Second, when using Volume Upsell an error stating that the "Volume Upsell Does Not Exist" is displayed in the Sales Order Entry (P4210) when an Upsell does exist. To address these issues, all of the pricing business functions listed below must to be mapped to the same location as Sales Order Entry Master Business Functions (B4200310 & B4200311). The resolution above will remove any incorrect mappings with these functions and set them all to use the default local business function mapping for the environment :

B4500541
B4500542
B4501300

Example jde.log for the entering journal entries shows the following if OCMs are incorrect:
2496/176 Tue Mar 23 15:05:44.757 jdb_exet.c6509
JDB9901232 - Canceling transaction because: TC017 JDEK_SendCallRequest: transaction cancelled on server
2496/176 Tue Mar 23 15:05:44.967 jdb_exet.c6119
JDB9900849 - Failed to commit user
2496/176 Tue Mar 23 15:05:44.967 DLG_MSGB.CPP170
Commit Failed or was Canceled. Transaction not committed

4. Considerations

1. The following functions were found to have server mappings due to their coded business function location of 3 for server only. These functions however can be used both locally and on the server so it is recommended that the OCM mappings created for these functions be deactivated or deleted. Several applications call this function through the local ER if running from a fat client environment.
   
2. B4301490 and B4301710
   
3. The process above does not create OCM mappings for the server for Vertex business functions. This is a manual step and may be required if your environments are utilizing any of the Vertex products.
   The following functions should be manually mapped to run on the server for the environments updated by the resolution process above. If you are running Vertex locally then these functions do not require any mapping changes.
   
4. Vertex for Sales and Use
   X00TAX.c
   B7300002
   B7300004
   B7300012
   B0000182
   B0000183
   
5. Vertex for Payroll
   R07200
   B0700058
   B0701520
   B0701490
   B0700030
   B0700022
   B0700059
   N0701900

This document will be updated with additional considerations where manual mappings are required as they are found.

Bottom of Form