Cancel Order Getting Async BSFN Error For Few Users (P4210)

Purpose of Document

This document is part of an advisor - to see other documents related to Sales, please use the links provided below:

JD Edwards EnterpriseOne Sales Advisor > JD Edwards EnterpriseOne Sales Troubleshooting Advisor > Note 1110095.1



The audience for this note is someone with developer level knowledge.

Cancellation of existing Sales Order issues Commit Fail error when,

UserTableColFromToAddChangeDeleteView
UserA F4211 NXTR 500 509 N N N N
UserA F4211 NXTR 510 999 Y Y Y Y


And Order Activity Rules are defined as below for SO and SQ type orders:

Order
Type
Line
Type
Last
Status
DescriptionNext
Status
SQ S 500 Enter Quote Order 505
SQ S 505 Ready to Create SO 510
SQ S ...    

 

Order
Type
Line
Type
Last
Status
DescriptionNext
Status
SO S 510 Enter Sales Order           540
SO S 540 ...  


All the setting appears to be valid as Next Status is 560 to be moved to next status is 999 but ASYNCHRONOUS BUSINESS FUNCTION ERROR against Business Function F4211FSEndDoc is issued and jde.log leave message as below:

1952/2160 WRK:TESTFBA_050DC240_P4210 Wed May 26 01:26:37.896050 Jdb_exef.c826
JDB9900900 - Inclusive Row Level Security Violation: UserA attempted an UPDATE on column SDNXTR in table F4211

1952/2160 WRK:TESTFBA_050DC240_P4210 Wed May 26 01:26:37.896052 Jdb_exet.c8094
JDB9901232 - Canceling transaction because: TC031 UpdateTable: security violation

What is problem and how to overcome this error?

Error is caused by Row Security in updating SQ order line. As Bug 12498818 - "Re-Open Blanket Order in case of the quantity releases decreased" indicates, the SQ quantity has to be replenished in canceling Sales Order which is derived from Sales Quote.

Since cancellation has to update quantity and status (F4211.NXTR) for SQ into 505 it ends in error as 505 wasn't included in the security.

Note:


To overcome this error correct Row Security settings by allowing NXTR = 505

UserTableColFromToAddChangeDeleteView
UserA F4211 NXTR 505 999 Y Y Y Y


or do not set inclusive row security for column Change.

Disclaimer: Oracle is not responsible for transaction failure which is caused by incorrect Row Security settings.

To discuss information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the JDE1 Distribution Community.

To look at upcoming or archived Advisor Webcasts please see Advisor Webcast Details (Doc ID 548764.1) if your topic is not currently scheduled please suggest it.