Extend Input Interface and REST API Support to Work Area Activities
The WFM Work Area Activities (WAA) view is used to create system, VAS, and manual activities. The WMS Screens child view of WAA is used to map system activities to WMS Screens. In 24C, we have enhanced WFM to upload or post WAA data and the mapped WMS Screens via input interface and REST API. The functionality of the configuration migration action button on the WAA view has also been enhanced to include the mapped WMS screens for system activities in the exported config file.
CONFIGURATION MIGRATION ACTION BUTTON ON WORK AREA ACTIVITY
The Configuration Migration action button on Work Area Activity is used to export/import system, VAS and manual activities. This functionality has been enhanced to include the mapped WMS screens for system activities.
IMPORTANT NOTE: For system activities to be imported successfully in the destination environment, the relevant WMS screens should exist in the screens view prior to importing Work Area Activity data.
INPUT INTERFACE FOR WORK AREA ACTIVITY
A new option “Work Area Activity” has been introduced in the Input interface screen (InputInterfaceView) that can be used to upload warehouse activities into WFM. Refer WFM Input Interface Format Spec for a list of fields in the Work Area Activity interface file. Work Area Activity interface files must be prefixed with "WAA"
INPUT INTERFACE FOR WMS SCREENS
A new option “WAA Screen XREF” has been introduced in the Input interface screen (InputInterfaceView) that can be used to upload WMS Screens that need to be mapped to system activities. Refer WFM Input Interface Format Spec for a list of fields in the WAA Screen XREF interface file. WAA Screen XREF files must be prefixed with "WSX".
REST API SUPPORT FOR WORK AREA ACTIVITY AND WMS SCREENS
Now, the external system can communicate and post the Work Area Activity and WAA Screen XREF data directly to WFM via following REST APIs:
WORK AREA ACTIVITY SCREEN API
POST ..lgfapi/v10/entity/work_area_activity
The post request consists following request body:
| Name | Required | Type | Description |
|---|---|---|---|
|
facility_id |
X |
Integer |
Facility ID |
| code |
X |
String |
Work Area Activity Code |
| name |
X |
String |
Work Area Activity Name |
|
work_area_activity_type_id |
X |
Integer |
WFM Internal ID of WAA Type |
|
work_area_id |
X |
Integer |
WFM Internal ID of the Work Area |
Request body example
<request>
<fields>
<facility_id>648</facility_id>
<code>IBACT01</code>
<name>Inbound Receiving Activity</name>
<work_area_activity_type_id>0</work_area_activity_type_id>
<work_area_id>18</work_area_id>
</fields>
</request>
WORK AREA ACTIVITY SCREEN XREF API
POST ..lgfapi/v10/entity/waa_screen_xref
The post consists following request body:
| Name | Required | Type | Description |
|---|---|---|---|
|
work_area_activity_id |
X |
Integer |
WFM Internal ID of Work Area Activity |
|
module_instance_id |
X |
Integer |
WFM Internal ID of the WMS Screen |
Request body example
{
"fields": {
"work_area_activity_id": 12,
"module_instance_id": 18
}
}
GET SUPPORT FOR ADDITIONAL STAGE ENTITIES
We’ve also extended GET API support to the following WFM entities:
- STAGE_DAILY_VAS_TRACK
- STAGE_WORK_AREA_ACTIVITY
- STAGE_WAA_SCREEN_XREF
Steps to Enable
Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.