My Oracle Support Banner

E1: 42: Change To Category Code During SO Entry (P4210) Is Not Saved (Doc ID 1962493.1)

Last updated on FEBRUARY 04, 2019

Applies to:

JD Edwards EnterpriseOne Sales Order Entry - Version 9.1 to 9.1 [Release 9.1]
Information in this document applies to any platform.

Symptoms

Sales Order Entry (P4210)

When attempting to change Sales Category Code 1 (SRP1) on a previously saved sales order, the changed value is not saved. This only occurs if there are no records populated in the Company Constants Tag Table (F0010T). If even one record for a different company other than the order company is populated in the Company Constants Tag Table (F0010T), the change is saved,

The issue can be reproduced at will with the following steps:

  1. Verify Company Constants Tag Table (F0010T) has no records populated.
  2. Populate the value BIK in the Sales Category Code 1 (SRP1) field on an item branch record.
  3. Create a Sales Order for the Item and Branch Plant.
  4. Verify the value BIK is defaulted in the Sales Category Code 1 (SRP1) field on the sales detail line.
  5. Save the order.
  6. Reinquire and enter Sales Detail Revisions.
  7. On SOE Additional Info 1 change the value from BIK to ACC in the Sales Category Code 1 (SRP1) field and click OK.
  8. Save the order with the new value.
  9. Look at the Sales Detail (F4211) record and notice the value is still BIK in the Sales Category Code 1 (SRP1) field.
  10. Now add a record in the Company Constants Tag Table (F0010T) has no records populated.
  11. Repeat the test above. The change is saved.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.