HCM - JDE1 (MOSC)

MOSC Banner

SOX issue: need to lock down a .txt file?

edited Jun 15, 2010 2:02AM in HCM - JDE1 (MOSC) 2 commentsAnswered
Our internal SOX audtiors have raised an issue with the .txt file we create out of JDE and send to the bank for our ACH direct deposits. (They have raised the same issue with our AP ACH file as well.) Is there a way to lock down a .txt file so the person submitting it to the bank cannot change any data  in it?

And if not, how does your company get around this SOX issue?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

E1 HCM Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center