E1: 42W:- Fetch From Cache B4277716 Failed (078N)- After Line Is Partially Released (Doc ID 1901000.1)

Last updated on NOVEMBER 17, 2015

Applies to:

JD Edwards EnterpriseOne Fulfillment Management - Version 9.1 to 9.1 [Release 9.1]
Information in this document applies to any platform.

Symptoms

9.1
Fulfillment Workbench (P4277701)

When a partial release is done with Fulfillment Release (R4277703) causing the Sales Detail Line to split, a split line is not created in the Sales Detail Tag File (F49211). This causes the Fulfillment Workbench (P4277701) to fail with a Fetch from Cache B4277716 failed (078N) error because the SQL statement is unable to join records from F4201, F49211, and F4211 because the F49211 record was not created. This only occurs if the  Transportation Module (SY49) is turned off in EnterpriseOne System Control (P99410).

STEPS
-----------------------
1. In EnterpriseOne System Control (P99410) Transportation Module (SY49) is turned off.
2. Create a new item with no inventory. Set Inventory Cost Level to 2 (Item/Branch Only).
3. Create a non-blank primary location on the item branch record.
4. Enter a Fulfillment Management order with a quantity of 800.  
5. Verify the order in Fulfillment Workbench.
6. Adjust inventory to fulfill 191 EA.
7. Run Auto Fulfillment (R4277701). Order quantity is partially fulfilled.
8. Run Fulfillment Release (R4277703). Verify the partial quantity is released.
9. Verify in Customer Service Inquiry (P4210) that Release Fulfillment split the lines.
10. Check Sales Detail Tag File (F49211). The split line WAS NOT added to the tag file.
11. Adjust another 100 units in inventory.
12. Enter Fulfillment Workbench to edit the split order line.
13. Fetch from Cache B4277716 failed (078N) error is displayed.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Not able to manually fulfill order lines that remain as a result of a partial release. This is a big issue for kits which are required to be manually fulfilled and released. This issue will delay the client go-live which is scheduled for 7/14/14.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms