2 Resolved Issues

This section contains a list of the customer-reported bugs that were fixed in this release.

Customer Service

Bug ID Description

17120

Contact Center Order Entry now requires authority to Order Inquiry/Maintenance (OIOM) as well as and Order Entry (OEOM) and Contact Center Order Entry (CCOE) in order to see all information on the customer information page.

32960132

Corrected the calculation to determine whether a drop ship order line is a future order, when the order was created through the order API or in Modern View Order Entry.

31408294

Corrected the calculation of the amount to refund when a tax override was applied to an order before a return took place.

32219152

Corrected Contact Center in Modern View to prevent releasing an order from AU (Broker Order Under Review) hold.

32321822

Corrected the generation of shipment confirmation emails to prevent a situation in which some emails were generated twice.

32680789

Corrected the ORCE Organization Descriptor (L50) SCV to store the descriptor in the entered case.

32581520

Corrected the calculation of discount percentage in order entry when the discount percentage was added to the order header and then the order line was added.

32710649

Corrected the recalculation of tax when a post-shipment discount is applied in Modern View.

32745376

Corrected the formatting of the recipient name at the customer tab in Modern View.

Customer Engagement Integration

Bug ID Description

32567615

Corrected starting the RLTCSUP (Customer Upload to Customer Engagement) job to start successfully when scheduled or run on demand.

Fulfillment

Bug ID Description

32540183

Corrected calculation of arrival date plus lead days (reservation lead days and vendor item lead days) to determine whether to generate a drop ship pick or purchase order for a drop ship item.

Related issues resolved:

  • Orders were not flagged correctly as future orders based on the above calculation, regardless of whether the order was created through order entry (OEOM), the order API, or Modern View.

  • The FUTURE periodic function (FLR0246) did not consider vendor lead days when determining whether an item on an order was now eligible to be reserved.

Imports and Exports

Bug ID Description

32558523

Corrected an error that occurred during the Marketing Download Extract periodic function (MDEXTR).

32376525

Corrected generation of the RTLog file to prevent creating duplicate records.

32376586

Corrected update to the RTLog file for processing a negative additional charge. For these transactions, the Transaction Type in the THEAD record was blank, and it is now set to RETURN. Also, the Item Status in the TITEM record was blank, and it is now set to R.

32382479

Corrected RTLOG file generation to include an invoice that was created when you added an additional charge to a closed order, with the No Inventory Return flag set to Y.

32573808

Corrected the Marketing Download Extract to include cancellations of partial line quantities.

32616021

Corrected the calculation of the quantity returned in the Marketing Download Extract.

32619216

Corrected the Marketing Download Extract to include shipment activity for partial shipments, as well as ship-alone items.

32638970

Corrected an issue with the Marketing Download Extract that caused the quantity ordered to sometimes be incorrect.

Order Broker Integration

Bug ID Description

14900

Changed shipping_agent passed to Order Broker in the status update request message for a fulfilled or intransit update to be the ship via code rather than the description.

18147

Corrected a situation in which Order Management System was sending an additional intransit status update for the fulfilling order for a ship-for-pickup order when the customer picked up the order at the pickup location. This issue occurred when Use OROB for Fulfillment Assignment (M31) was selected and Use OROB for Ship for Pickup Fulfillment Assignment (M34) was set to ALWAYS. In this case, a duplicate order shipment detail record was being created.

To fix this issue, the status of the Order Broker record associated with the retail pickup order now changes to completed (X) immediately when the merchandise is in transit to the pickup location, and the duplicate status update message isn't sent. However, the correct status of intransit is always sent to Order Broker.

Note:

Since the status changes to completed immediately, you can no longer use the Display Order Broker History screen to track when the Order Broker status changes to intransit, intransit polled, received, or fulfilled for a ship-for-pickup order when the Use OROB for Ship for Pickup Fulfillment Assignment (M34) system control value is set to NEVER, or a retail pickup order.

32381050

Changed the BROKER_ORD job to check status less frequently. To enhance performance, the job now checks to see whether it needs to end or to continue processing each time it has processed requests for all eligible companies and the Outbound Delay Time has passed.

32472644, 32472709, 32769851

Corrected a situation in which Order Management System did not send a rejected status update to Order Broker when an item on a fulfilling delivery order was sold out. This situation occurred when the Use OROB for Fulfillment Assignment (M31) system control value was selected, and when:

  • There was also another item on the originating order that was available, or

  • The line number in Order Broker is not 1 if, for example, Order Broker assigned the first order line to a store location for fulfillment.

32539445

Corrected the BROKER periodic function to prevent it from unnecessarily starting the CCAUTH_BTH job, related to batch authorization.

Note:

The CCAUTH_BTH job is no longer used as part of Order Broker processing, and does not need to be scheduled to start and stop each day. The related periodic functions to start and stop this job are AUTHSTR and AUTHEND.

32583887

Corrected Order Broker processing, as well as the PREORDER periodic function, to create an Order Broker record for a held order if the Send Held Orders to OROB (M18) system control value is selected.

Payment Processing

Bug ID Description

31137678

Corrected a situation in which the system reauthorized a canceled order through the external payment service.

31906595

Corrected the Payment Method Details window in Contact Center to display all payment method details, regardless of whether they were for the same amount and on the same date.

32134416

Corrected submission of multiple authorizations for a single deposit transaction when using the External Payment Service to include the correct authorization code and transaction ID from Authorization History for each.

32223591

Corrected net exchange billing to take place correctly for orders exchanged in Contact Center.

32355233

Corrected generation of drop ship pick slips and submission of brokered backorders to Order Broker when the Authorization Number for Authorizations Under 1.00 (I08) system control value is populated and there is an authorization less than 1.00.

32491482

Corrected External Payment Service authorization to handle a REJECT or ERROR response by putting the order on AT hold and setting the authorization to declined when:

  • The reason code passed is not defined as an authorization response code, or

  • The reason code passed is defined as an authorization response code but also has a hold code defined, or

  • No reason code is passed.

Additionally, if no reason code is passed, a response code of SU is defaulted.

32501790

Corrected Contact Center order entry to clear the hold applied to the order when the credit card entered during online authorization was declined, enabling the system to generate an authorization request for the replacement card entered.

32555113

Corrected the External Payment Service to prevent a situation in which data in requests could have been incorrect.

32618802

Corrected authorization for a pre-order when a payment method has been deactivated and a new payment method added.

32622423

Enhanced CyberSource processing in cases when the service is unavailable, including better identification of reasons for service unavailability and capturing the causes of any failures in the APP log.

32636838

Corrected pick slip generation to prevent orders with valid, unexpired authorizations from going on hold due to an error related to their expiration dates.

Performance

Bug ID Description

32607782

Enhanced performance of the BILL_ASYNC job.

System Management

Bug ID Description

31960998

Corrected the Customer Engagement Sales Feed periodic function (RLTSLSF) to prevent it from logging unnecessary errors.

32200805

Re-added the yearly clear periodic function (YEARCLR or CLR_YR, MSR0577) to the delivered periodic functions.

32039209

Corrected the format of the Update Time and Transaction Time displayed at the Work with Job Monitor (WJMO) screen.

32259516

Corrected the REAUTH_JOB to prevent a situation in which multiple instances of the job could run at the same time. The job now submits an active procedure and is now one of the jobs monitored and corrected, if needed, by the JOBCLN periodic function.

32415562

Corrected issue that prevented successfully activating or deactivating a job at the Scheduled Jobs screen.

32639673

Corrected creation of system control values in the delivered companies (49 and 51).

Taxation

Bug ID Description

31630872

Corrected the Distribute Tax request to Vertex to include the freight override amount, if any, in the ExtendedPrice tag.

User Interface

Bug ID Description

30646501

Corrected accessibility issues at the Customer Information step of Contact Center Order Entry.

30808543

Corrected accessibility issues at the Manage Held Orders page in Modern View.

31619073

Corrected searching by customer email address in Streamlined Order Inquiry (DORI) to be case-insensitive, so that customers are found based on the email address entered, regardless of case.

31820324

Corrected the first Execute Periodic Process screen to prevent a Java exception error if you entered an invalid time.

32078879

Clarified the error message displayed in order entry (OEOM) when there was an error related to Vertex because the required files were not found. The error that is now displayed indicates: Error calling Tax Interface, check configuration. See Vertex Setup in the online help for more information.

32108268

Corrected item class information displayed for a customer in order entry (OEOM).

32518932

Corrected Work with Accounting Period (WACP) to enable deleting an accounting period without data.

32593409

Corrected the sequence in which jobs are listed at the Job Management screen.