FlexProcess R6.0 Patch A release notes - Powered By Kayako SupportSuite

Sep 04 2010

Support Center » Knowledgebase » FlexProcess R6.0 Patch A release notes

	FlexProcess R6.0 Patch A release notes

Solution DEFECTS RESOLVED
Patches are additive within a release, and patch letters are assigned incrementally. i.e., a Patch B contains Patch A.

Below are the known defects in FlexProcess Version 6.0.00 that were reported and resolved in this Version 6.0.00 patch release:

Patch A:

NPS13221 (PROne01607) activity

When a value was keyed into the blank row's numeric field on the Activity Forms, the field value became incorrect.

For example, when a value 1 was entered into the Primary Quantity field, it was changed to 10.000000. Or the entered value 20 was changed to 200.000000. This problem occurred on all Activity Forms.

With this fix, the field value is accepted as entered.

(PROne03637) NewPurchasing

Before this fix, when two or more expected matching data related to the same Purchase Order were added to Vendor Invoice Line Items via FlexProcess API, FlexProcess aborts.

With this fix, the expected matching data are added correctly and FlexProcess will no longer abort.

NPS12224/NPS12692/NPS12894 (PROne03645) inventory

When creating activity forms, a timeout error might occur due to lock contention on inActyNumTblSeq table, which kept a sequence number for each activity numbering table.

With this fix, the sequence number update logic is improved and the timeout error will no longer occur when creating activity forms.

A new FlexProcess Manager option "\\Inventory\Activity Numbering Table\Generate Sequence Number on Alternate Session" enables you to choose the sequence number update logic. The default value of this option is "TRUE", which means the system uses the improved logic.

Note that if you choose "TRUE" for this option, it may cause lack of serial number on activity forms created in the same transaction. If you want to avoid this situation, choose "FALSE" for this option.

NPS13081 (PROne03649) COM

When a user executed Reservation, Shipping Activity, and Receiving Activity of a Transfer Order Delivery in a short period of time, sometimes the error "cannot be changed to state Reserved" occuerred in the Delayed Event Processor(DEP).

With this fix, DEP operates normally in the same situation.

(PROne03657) EventAutomation

"ORDER VALIDATED" event might be created on the Delayed Event Processor (DEP) in system event processing.

With this fix, "ORDER VALIDATED" event is no longer generated in DEP processing.

(PROne03661) schedule_maint

The unnecessarily validation of a target Schedule object was processed at updating of the Schedule Activity Form Line. Therefore, there was a negative performance impact at updating of the Schedule Activity Form.

With this fix, the performance of the Schedule Activity Form improved.

(PROne03662) NewPurchasing

Before this fix, when a Purchase Requisition Line Item with an unprocessed Delayed Event was deleted, errors occurred with the Delayed Event Processor(DEP).

With this fix, when a Requisition Line Item is removed, all Delayed events associated with the Requisition Line Item are deleted and the errors are prevented.

(PROne03663) NewPurchasing

Before this fix, when a Purchase Order Line Item with an unprocessed Delayed Event was deleted, errors occurred with the Delayed Event Processor(DEP).

With this fix, when a Purchase Order Line Item is removed, all Delayed events associated with the Purchase Order Line Item are deleted and the errors are prevented.

The problem also occured with a Purchase Order Receipt Line Item and it is corrected with this fix.

(PROne03664) NewPurchasing

Before this fix, when a Vendor Invoice Line Item with an unprocessed Delayed Event was deleted, errors occurred with the Delayed Event Processor(DEP).

With this fix, when a Invoice Line Item is removed, all Delayed events associated with the Invoice Line Item are deleted and the errors are prevented.

The problem also occured with a Match Line Item and it is corrected with this fix.

NPS13268 (PROne03671) NewPurchasing

Before this fix, when a Planning Purchasing Integrator Profile was deleted while it is still being referenced by a Planning Purchasing Integrator Run Results object, when the Planning Purchasing Integrator Run Results object is opened, an Assertion error message is displayed.

With this fix, an Assertion does not occur, and the Planning Purchasing Results Object can be opened. When the profile is deleted, "---------" is shown as the profile description.

This problem also occured with the Purchase Order Generator Run Results and it is corrected with this fix.

(PROne03673) inventory

When the "RESERVE DELIVERY" action creates an automatically reservation for a COM Order on the Delayed Event Processor(DEP), a memory leak was detected.

With this fix, the action creates the automatically reservation correctly and memory leak is not detected.

NPS13110 (PROne03676) COM

When the delivery's UM for pricing was set to "Specified", the Invoice was created based on the original ordered quantity in the Pricing UM not based on the actual shipped quantity.

With this fix, the invoice is created for the actual shipped quantity in the Pricing UM.

NPS13139 (PROne03686) inventory

Prior to this fix, when a user specified a Carrier on the Outbound Shipment Transportation Details tab, the CarrierObjectID column was not set in the inOutboundShipm database table.

After this fix, the CarrierObjectID is correctly set during the validation and is stored in the inOutboundShipm database table when the specified Carrier is valid.

NPS13086 (PROne03696) Financials

There was some case that undoing Apply action to Balance Forward Statement was prevented by two checks.

One of the checks was about a series of applied Balance Forward Statement. And it reported an error message

Only actions on the latest balance forward statement-payable in a series of statement can be undone. fg:950099
The other was about the order of Source Document Actions related to each Source Document. And it reported an error message

Actions must be undone in the reverse order from which they were done. Check both Source Documents for actions that were done subsequent to the one you are attempting to undo. fg:21366

With this fix, check logic about the series of applied Balance Forward Statement was changed to consider the order (time) of apply actions. This change allows the apply actions from/to Balance Forward Statement to be undone by reverse order.

NPS13148 (PROne03707) inventory

FlexProcess was terminated abnormally when trying to Prefill an Outbound Shipment from an Expected Shipment which no longer exists. This could occur when the Expected Shipment was deleted due to the Order cancel after the Expected Shipment was added to the Outbound Shipment.

With this fix, FlexProcess is not terminated in this situation. Instead, FlexProcesss issues an message informing the user that the Expected Shipment no longer exists.

NPS11736/NPS13060 (PROne03716) FinancialsPlus

Before this fix, error occured when Source Document Mass Action was launched from Note Adjust Template by the following procedures.

Choose target Source Documents
Specify "Change to status"
Run Source Document Mass Action

Now you can run Source Document Mass Action correctly by the above procedures.

NPS11429/NPS13060 (PROne03720) FinancialsPlus

Before this fix, error occured when Source Document Mass Action was launched from Note Adjust Template with specifying the action date which was later than the due date.

Now you can run Source Document Mass Action correctly in the above case with specifying '1' in the parameter: AllowActionDateAfterDueDate of Custom Tool Plus.

NPS13060 (PROne03723) FinancialsPlus

Before this fix, error occured when Source Document Mass Action was launched from Note Adjust Template with specifying the action date which was earlier than the document date.

Now you can run Source Document Mass Action correctly in the above case with specifying '1' in the parameter: AllowActionDateBeforeDocDate of Custom Tool Plus.

NPS13119 (PROne03726) Costing

FlexProcess was sometime terminated abnormally when adding Production Model in Cost Pegging Inquiry.

With this fix, FlexProcess is not terminated in the situation.

(PROne03727) planning

The Planning run was not correctly matching characteristics for supply and demand. When a demand contains a characteristic with a defined value, only supply with the same characteristic value should be used to satisfy the demand. However, before this fix, an existing supply which contains a characteristic with a null value was being used to satisfy the demand.

With this fix, as long as the supply contains a compatible value for each characteristic defined on the demand, the supply can be used to satisfy the demand. When the value of the characteristic on a demand is null, then the Planning run will use supply, regardless of the characteristic value to satisfy the demand, which is the same behavior prior to this fix.

(PROne03730) planning

When UM Conversion was not processed successfully, the following error message was generated as the result of Planning Run.

-Case 1:

RDNAME::The From UM () of the quantity field cannot be converted to the To UM () of the quantity field. pp : 480026
This occurred when a Reference Density Conversion factor did not exist in the database, when converting a Volume type UM to a Weight type for a Density Resource, and vice versa.
-Case 2: cases except for the above-mentioned

::The From UM (UM Name) of the quantity field cannot be converted to the To UM (UM Name) of the quantity field. pp : 480026
("RDNAME" is the abbreviation of "Reference Density Name".)
In the 2 cases above, the Resource and UM which caused the error could not be identified with this message.

With this fix, the name of Resource and UM is included in the error message. And "RDNAME" is changed to "Reference Density Conversion", because it is difficult to be understood.

-New message for Case 1

Reference Density Conversion::The From UM (UM Name) of the quantity field cannot be converted to the To UM (UM Name) of the quantity field. pp : 480026
-New message for Case 2

Site Name:Resource Name::The From UM (UM Name) of the quantity field cannot be converted to the To UM (UM Name) of the quantity field. pp : 480026
(PROne03734) EventAutomation

Before this fix, even though a Delayed Event was registered on the Purchase Requisition, Purchase Order or Vendor Invoice object, the Delayed Action defined in the FlexProcess Automation Designer (FAD) object was not executed.

With this fix, the Delayed Action defined in the FAD object is executed correctly.

NPS13069 (PROne03754) Financials

Before this fix, the following phenomena occured with the journal entry made by apply or discount apply action via FlexProcess Automation API.

Phenomenon 1:
When the user changed the currency conversion type and changed the currency, the currency conversion rate different from the case when an action was executed in UI was used.

Phenomenon 2:
When "Journal entry" -> "convert currency" menu was selected, the currency conversion rate in the currency conversion dialog box was displayed with empty.

With this enhancement, the new key is added to Financials in FlexProcess Manager.

Key FillInCurrConvType
Location \\Financials\FillInCurrConvType
Type Boolean. Specify whether to enable this fix.
TRUE - enable.
FALSE - disable.

Default FALSE

By setting up TRUE to this key, this problem will be fixed as follows.

Phenomenon 1:
The same currency conversion rate as the one executed in UI will be used.

Phenomenon 2:
The currency conversion rate will be displayed.

NPS13162 (PROne03761) COM

When a user operated the following steps on FlexProcess client, the Delayed Event Processor(DEP) sometimes encountered Errors.

Create and save a Debit Order or a Credit Order.
re-Open the Order and change Unit Price or some item in a Delivery.
Save and Close the Order.
re-Open the Order and set status of the Delivery to Cancel.
Save and Close the Order.

With this fix, DEP no longer encounters the error in the same situation.

NPS13190 (PROne03763) Financials

When payment generator was launched and the table configuration was changed on Payment Generator Window, the values in "Creator Description", "Creator Description2", "Payee Description" and "Payee Description2" columns became blank.

With this fix, Payment Generator displays correct values in the columns after the table configuration was changed.

NPS13130 (PROne03765) COM

Previously, when selecting a Sales Catalog Item from a user-defined query linked to the dynamic cabinet as a default query, an extra filter dialog appeared on the Order Line Item Level Service Window.

With this fix, the display of the extra filter dialog is suppressed.

NPS13192 (PROne03768) NewPurchasing

Before this fix, when a Vendor Resource entry on the objects tab for the Workspace did not exist, and New button on page 4 of the Logistics tab of Resource dialog was clicked, the following message was displayed and FlexProcess aborts:

A null pointer was found where one should never exist. f2 : 90262

With this fix, the tool for the object which is not defined as available in the Workspace are disabled to launch. This fix is administered to the objects below.

Price Sheet
Comment
Purchase Order
Purchase Requisition
Inventory Inquiry
Available to Promise Inquiry
Receiving Activity Form
Shipping Activity Form
Expected Receipt Inquiry
Expected Shipment Inquiry
Planning ATP
Planning Action Board
Vendor Invoice
NPS13130 (PROne03775) COM

Previously, when selecting a Sales Catalog Item from a user-defined query linked to the dynamic cabinet as a default query, an extra filter dialog appeared on the Order Line Item pane.

With this fix, the display of the extra filter dialog is suppressed.

NPS13143 (PROne03776) COM

When a user set OS_Closed(17) to OrderStatus Property by using FlexProcess Automation API IPROTEANOrderSummary, FlexProcess did not execute Order Close Process.

With this fix, FlexProcess executes the Order Close Process in this situation.

NPS13143 (PROne03777) COM

When a user set OS_Closed(17) to LineStatus property by using FlexProcess Automation API IPROTEANOrderLineItem, FlexProcess allowed to set OS_Closed to the Property without any checks.

With this fix, FlexProcess prevents IPROTEANOrderLineItem.LineStatus property from being set to OS_Closed when any deliveries of the Order Line Item has the status other than OS_Canceled or OS_Closed.

(PROne03781) NewPurchasing

Before this fix, when a Purchase Requisition Line Item details dialog was displayed, even though the Purchase Order Line Item related to the Purchase Requisition Line Item exists, the Purchase Order Line Item menu was unavailable.

With this fix, when a Purchase Order Line Item related to the Purchase Requisition Line Item exists, the menu is available.

(PROne03782) COM

Before this fix, when the Price Sheet used for purchasing was opened for view, the Base Price Amount and UM in the Basic Tab are editable. Furthermore, when quantity breaks were set in the Quantity Breaks tab and the Base Price UM is modified and "Yes" was answered to the following message, FlexProcess aborted.

::Changing the base price unit of measure will affect the unit of measure on the Quantity Breaks tab. Would you like to clear your current quantity breaks? co:1550005

With this fix, when the Price Sheet used for purchasing is opened for view, the Base Price Amount and UM in the Basic Tab cannot be edited and FlexProcess will no longer abort.

NPS13203 (PROne03784) inventory

This problem was found where the value of Staging Location and Staging Classification were not displayed in the result list of Expected Receipt Inquiry, even though they were set to be displayed.

With this fix, they are displayed when specified.

(PROne03785) inventory

This problem was found where the value of Staging Classification was not displayed in the result list of Expected Shipment Inquiry, even though they were set to be displayed.

With this fix, it is displayed when specified.

(PROne03788) NewPurchasing

Before this fix, when trying to create 10,000 or more Line Items in one Purchase Order, FlexProcess aborted.

With this fix, when trying to create 10,000 or more Line Items in one Purchase Order, the following message is displayed and FlexProcess no longer aborts.

This value is out of range. f2:91928
This problem also occurs with Purchase Requisition, Vendor Invoice, and has been corrected with this fix.

(PROne03793) FinancialsPlus

Before this enhancement, source documents with complete status were not processed in the Cash Receipt Application.

With this enhancement, the new key is added to parameters of FlexProcess Custom Tool Plus for the Cash Receipt Application.

New key: UseCompleteDoc
Specify whether source documents with complete status are processed.
0 - Do not process source documents with complete status.(default)
1 - Process source documents with complete status.

By setting up 1 to this key, source documents with complete status will be processed.

NPS13209 (PROne03798) foundation

When a user deleted Value List Value on the Value List that was used and referenced by the other object and saved the Value List, FlexProcess aborted.

With this fix, when the Value List Value cannot be deleted, FlexProcess displays an errer message and no longer aborts.

NPS13204 (PROne03804) FinancialsPlus

Before this fix, when entering a Natural account of a Journal Entry Plus by Windows Server 2003 SP1, an error occurred.

Now when entering a Natural account of a Journal Entry Plus by Windows Server 2003 SP1, an error will not occur.

This defect was due to changes made to the MFC method (COleSafeArray::CreateOneDim()) in Windows Server 2003 SP1. We have also fixed the following FlexProcess Automation APIs which use this method.

CTaxRulePluss::qryTaxRules()
CTaxRulePluss::qryTaxCategories()
CCustomToolPluss::GetCustomToolPlusNameList()
CFiscalEdgeUtil::GetReferencesFromJE()

(PROne03807) NewPurchasing

Before this fix, when a Purchase Order was listed on the "Require view access to see in cabinets" table on the Security tab of FlexProcess System Tailoring, if a Purchase Order was created and a Purchase Order Line Item is newly entered, the following error message is displayed:

XXX::YYY::View rights are required to XXX in order to enter it in this field. Your workspace does not have view rights to this object. f2:91115

With this fix, the error message will no longer be displayed and a Vendor Resource can be set correctly.

NPS13230 (PROne03809) resource

This problem was found where the User UM field was displayed when the value was input for the Characteristic which did not have the Default User UM on the second page in Custom tab of Resource object.

With this fix, User UM field is not displayed.

NPS13063 (PROne03813) Financials

When "Load Results" button was clicked on Unrealized Currency Gain/Loss tool, always single Source Document row was loaded in the results table regardless of field settings.

After this fix, all expected Source Document data is loaded in the results table.

NPS13232 (PROne03819) COM

When a user closed a customer order with a canceled Line and a completed Line, the Delayed Event Processor(DEP) encountered an error.

DEP no longer encounters the error in the same situation.

NPS13222 (PROne03821) COM

When a user set a substitute resource on a Reserved Order Delivery, the Delayed Event Processor(DEP) encountered an error.

DEP no longer encounters the error in the same situation.

NPS13214 (PROne03823) COM

In case the UM for Order and the UM for Invoice were different, the Open Amount was incorrect because the calculation of the charge which was added to the order delivery was incorrect.

With this fix, both the charge added to the order delivery and the Open Amount of the order delivery are calculated correctly in the same situation.

(PROne03826) activity

This problem was found where the input value could not be reflected to the numeric field of a blank row when the numeric field of entry assist bar(EAB) had a default value.

With this fix, the input value can be reflected.

(PROne03828) COM

Before this fix, Trading Partner comments could not be added via FlexProcess API. Using the FlexProcess API, a CommentReferenceSubordinate object could be retrieved using the Add method of the TradingPartnerComments managing object. However, since the CommentReference property of the CommentReferenceSubordinate object is readonly, there is no way to set the value of the added object to a particular comment. When the CommentReference value of a CommentReferenceSubordinate object is not set, the object is always deleted by FlexProcess during the save process.

After this fix, the Add method of the TradingPartnerComments managing object will now take a CommentReference object as a parameter. By passing a CommentReference object to the Add method, a CommentSubordinate will be created with the CommentReference set. Also, the XmlDataAdapter will now be able to create a Trading Partner object with comments using XML.

Please note that all applications that are currently calling the TradingPartnerComments.Add() method will have to be changed so that the Add method takes a CommentReference object as a parameter.

(PROne03830) dotnet

Before this fix, Financial, Logistics, and Production defaults of the User Object could not be retrieved, or set using the XmlDataProvider.

With this fix, defaults that are shown on the Financials, Logicstics, and Production tabs of the FlexProcess User object UI can be retrieved and set using the XmlDataProvider.

NPS13250 (PROne03835) planning

The following error occured when the Planning Run was executed using the Planning Run Profile on which one or more level codes of "Pause after Level Codes" were selected.

Error ::The extract database cannot be created. pp : 480009

Error ::An inconsistency was detected during the allocation of an array of objects of type bcStringi18n. The compiler believes the all pp : 480068
This problem dud not occur when "Pause after All Level Codes" or "Do not Pause" was selected on the Planning Run Profile.

With this fix, the Planning Run and the function of "Pause after Level Codes" is executed without the errors.

Article Details

Article ID:

Created On:

May 11 2007 11:02 PM