EarlWalker
Member
AIS is Oracle's favourite child at the moment an will continue to be enhanced going forward.
The separate integrations team here (who know nothing about JDE) are looking for a REST API to create Sales Orders (and purchase orders and work orders...)
My understanding is very limited - no hands on experience with either. Spent hours on the internet and on the Oracle site but 99% of of the examples are all about getting address book info. No meat and potatoes.
So ... this is what I think. Is it right?
AIS Forms Service
AIS Forms service which would require them (i.e. the integrations team) to understand P4210 a little bit to know how a user would use it and also get the object ID's. They would then need to craft a single JSON document to make the REST API call which will, 0) name the W4210A form, 1) populate the header fields 2) populate the grid fields for one or more rows 3) then press the OK button. i.e. the JSON document would contain the actions, field mappings and sales order data.
Orchestrator
They would send in JSON document with the sales order data only.
Using P4210 and Orchestrator Studio, we (JDE team) would record/create a orchestration which will map the JSON data to the P4210 header/grid fields. When the orchestration runs, it would open the from, populate the header/grid fields, click the ok button.
How do you create multiple grid rows????? Can multi-line Sales Orders be created using a orchestration? (maybe in future releases???)
Differences - (from the Integrations Team POV)
I'm guessing one of the benefits of the Orchestrator is that you can build in extra steps and decision making. E.g. They only have the LongAddressNumber so Orch1 fetches AN8 and SearchType from P01012. If SearchType = 'C'ustomer then run Orch2 with AN8 to create the Sales Order. The flow and decision logic stays withing JDE.
Doing the same thing done using AIS Forms/data service would require 2 separate service calls and some logic inbetween to link them together. The flow and decision logic to create a SO based on SearchType would be outside of JDE.
3pl Products
EveREST2jde address the issue that there is no JDE REST API for calling individual bsfn's.
Modus/Mulesoft is something similar (I think???).
Both would require the Integrations team to understand JDE a bit more and maybe for some JDE objects to be specifically created to encapsulate the business logic?
Please discuss!!!!!!!
The separate integrations team here (who know nothing about JDE) are looking for a REST API to create Sales Orders (and purchase orders and work orders...)
My understanding is very limited - no hands on experience with either. Spent hours on the internet and on the Oracle site but 99% of of the examples are all about getting address book info. No meat and potatoes.
So ... this is what I think. Is it right?
AIS Forms Service
AIS Forms service which would require them (i.e. the integrations team) to understand P4210 a little bit to know how a user would use it and also get the object ID's. They would then need to craft a single JSON document to make the REST API call which will, 0) name the W4210A form, 1) populate the header fields 2) populate the grid fields for one or more rows 3) then press the OK button. i.e. the JSON document would contain the actions, field mappings and sales order data.
Orchestrator
They would send in JSON document with the sales order data only.
Using P4210 and Orchestrator Studio, we (JDE team) would record/create a orchestration which will map the JSON data to the P4210 header/grid fields. When the orchestration runs, it would open the from, populate the header/grid fields, click the ok button.
How do you create multiple grid rows????? Can multi-line Sales Orders be created using a orchestration? (maybe in future releases???)
Differences - (from the Integrations Team POV)
I'm guessing one of the benefits of the Orchestrator is that you can build in extra steps and decision making. E.g. They only have the LongAddressNumber so Orch1 fetches AN8 and SearchType from P01012. If SearchType = 'C'ustomer then run Orch2 with AN8 to create the Sales Order. The flow and decision logic stays withing JDE.
Doing the same thing done using AIS Forms/data service would require 2 separate service calls and some logic inbetween to link them together. The flow and decision logic to create a SO based on SearchType would be outside of JDE.
3pl Products
EveREST2jde address the issue that there is no JDE REST API for calling individual bsfn's.
Modus/Mulesoft is something similar (I think???).
Both would require the Integrations team to understand JDE a bit more and maybe for some JDE objects to be specifically created to encapsulate the business logic?
Please discuss!!!!!!!