New posts

Reply to thread

Message: <blockquote data-quote="Dana BY" data-source="post: 198258" data-attributes="member: 48828">Hey guys,I have a question.Currently we are working on moving HR/Payroll activities out of JDE into third party application, but Finance will still stay in JDE; so we will need to send Journal Entries to be send back to JDE E1, and because of that we are looking into integration options we currently have. Option 1: Journal entry batch processing - for HR software to generated flat file to be sent to JDE, JDE report will populate data into F0911Z1 table; report R09110Z to process data into F0911 table; and journal entries to be posted using R09801 - all of those reports to be put on scheduler with output info to be sent to Payroll Accountant by email. Concerns: connection is not live, dependable on scheduler, in case of errors some time can be lost due to time lag etcOption 2: API. Now, here I have concern, probably because I don't understand API process correctly due to lack of knowledge. As far as i understand API works this way: JSON with request details are sent to JDE, Orchestrator calls application which is responsible for this particular task. So, In case of Journal Entry, JDE Orchestrator calls P0911 and enter data from JSON into applications one by one - am I right? Like it mimics manual entry or robotic (UiPath) entry. Here is what I am concerned about. I know Z1 process and I know we can perform proper data validation on report level, I am comfortable with Z1 process knowing it can process big batches with up to several hundred lines of several document types (in case of Payroll there are 3 doc types at least - T1, T2, T3) while I am not sure how it will be processed via API.Question: do you have any experience in API JDE Journal entry? have you any experience when large batches with several different document types are processed via API? What is your opinion which approach is more suitable in this case? Thank youJDE E1 9.2</blockquote>

Verification