Example Request Payloads
This section provides the example request payloads that must be sent from KanbanBOX to trigger the recipe. Using the payload information provided here, you can test the recipe for readiness in Oracle Integration.
Example: Purchase Requisition Payload
Here’s an example payload to trigger the Oracle KanbanBOX ERP PurchaseOrder Create integration flow of the recipe.
{
"kanbanbox_params": {
"batch_cards": [{
"part_unit_of_measurement": "Ea",
"kanban_quantity": "1",
"required_date": "2022-02-28",
"customer_number": "K Store",
"last_status_change_date": "2022-02-28",
"type_of_kanban": "purchase",
"business_unit": "US5 Business Unit",
"requestor": "User, KanbanBox",
"buyer": "Lans, Nash",
"deliver_to_location": "Chicago 501",
"kanban_status_name": "released",
"organization": "501",
"part_number": "G2A4009",
"customer_name": "K Store",
"supplier_name": "Allied Supplies",
"ekanban_string": "R3GDA9C",
"supplier_number": "300000230281607"
}]
}}Definition: Purchase Requisition Payload
The following table describes the attributes in the Purchase Requisition payload.
| Attribute Name | Description |
|---|---|
| part_unit_of_measurement | The unit of measurement that is used to specify the part quantity in Oracle Fusion Cloud Procurement. |
| required_date | The required date for the part as entered in a purchase requisition. This field accepts the current date or a future date. |
| customer_number | This is mapped to the sub-inventory name in Oracle Fusion Cloud Procurement for the purpose of integration. |
| customer_name | This is mapped to the sub-inventory name in Oracle Fusion Cloud Procurement for the purpose of integration. |
| last_status_change_date | The field that provides information about the last-updated status change date. The field is not used or mapped in the recipe. |
| type_of_kanban | The attribute value purchase indicates that a purchase requisition needs to be created. The field is not used or mapped in the recipe.
|
| business_unit | The business-unit name from where the purchase requisition is created in Oracle Fusion Cloud Procurement. |
| requestor | The user owning the requisition in Oracle Fusion Cloud Procurement. The field is not used or mapped in the recipe. |
| buyer | The person managing the purchase requisition in Oracle Fusion Cloud Procurement. |
| deliver_to_location | The location to deliver the goods in Oracle Fusion Cloud Procurement. |
| kanban_status_name | The status of the card from the Kanban system. For example, Released. The field is not used or mapped in the recipe.
|
| organization | The code for the organization where goods are delivered. |
| part_number | The item number in Oracle Fusion Cloud Procurement. |
| supplier_name | The name of the supplier in Oracle Fusion Cloud Procurement. The field is not used or mapped in the recipe. |
| ekanban_string | The unique card-identifier generated and sent from KanbanBox. |
| supplier_number | The unique identifier representing the supplier in Oracle Fusion Cloud Procurement. The field is not used or mapped in the recipe. |
Example: Work Order Payload
Here’s an example payload to trigger the Oracle KanbanBOX ERP WorkOrder Create integration flow of the recipe.
{
"kanbanbox_params": {
"batch_cards": [{
"part_unit_of_measurement": "Ea",
"kanban_quantity": "40",
"required_date": "2022-02-26",
"customer_number": "K Store",
"last_status_change_date": "2022-02-26",
"type_of_kanban": "production",
"kanban_status_name": "released",
"organization": "501",
"part_number": "G2A4008",
"customer_name": "K Store",
"supplier_name": "Allied Supplies",
"ekanban_string": "PTA7RT59",
"supplier_number": "300000230281607"
}]
}}
Definition: Work Order Payload
The following table describes the attributes in the Work Order payload.
| Attribute Name | Description |
|---|---|
| part_unit_of_measurement | The unit of measurement that is used to specify the part quantity in Oracle Fusion Cloud Manufacturing. The field is not used or mapped in the recipe. |
| kanban_quantity | The number of quantities placed to create the work order against the item pre-configured in Oracle Fusion Cloud Manufacturing. |
| required_date | The required date for the part as entered in a work order. This field accepts the current date or a future date. |
| last_status_change_date | The field that provides information about the last-updated status change date. The field is not used or mapped in the recipe. |
| type_of_kanban | The attribute value production indicates that a work order needs to be created.
|
| kanban_status_name | The status of the card from the Kanban system. For example, Released. The field is not used or mapped in the recipe.
|
| Organization | The code for the organization where goods are delivered. |
| part_number | The item number in Oracle Fusion Cloud Manufacturing. |
| customer_name | This is mapped to the sub-inventory name in Oracle Fusion Cloud Manufacturing for the purpose of integration. The field is not used or mapped in the recipe. |
| supplier_name | The name of the supplier in Oracle Fusion Cloud Manufacturing. The field is not used or mapped in the recipe. |
| ekanban_string | The unique card-identifier generated and sent from KanbanBOX. |
| supplier_number | The unique identifier representing the supplier in Oracle Fusion Cloud Manufacturing. The field is not used or mapped in the recipe. |
| customer_number | This is mapped to the sub-inventory name in Oracle Fusion Cloud Manufacturing for the purpose of integration. |