VAS Activity Data

The Daily VAS Track API allows you to create one or more VAS activity data records in WFM.

URL

POST ..lgfapi/v10/entity/daily_vas_track/

Fields

Name	Required	Type	Description
facility_id	X	Integer	Facility ID
work_area_id	X	Integer	WFM Internal ID of the Work Area
work_area_activity_id	X	Integer	WFM Internal ID of the VAS Activity (Work Area Activity of Type ‘VAS’)
cal_date	X	date	Date in DDMMYYYY format
team_id	O	integer	WFM Internal ID of the team; If this is populated, cw_user_id should not be sent (**Refer Note below)
cw_user_id	O	integer	WFM Internal ID of the user; If this is populated, team_id should not be sent (**Refer Note below)
qty	X	integer	Qty of items handled
uom_id	X	integer	WFM Internal ID of the UOM
Sku_line_group_id	X	integer	WFM Internal ID of the SKU Line Group

Note: To indicate empty values for team_id or cw_user_id, the following conventions should be used:

• In JSON, omit the tag completely or send a value of null.
• In XML, omit the tag completely or send empty tags.

Request Body Example (JSON)

Instance Create

{
    "fields": {       
 "facility_id": 648,         
 "work_area_id”: 516,        
 "work_area_activity_id": 476,        
 "cal_date": "2024-02-15",       
 "team_id": null,     
 "cw_user_id" :10754,
 "qty": 150,         
 "uom_id": 2,      
 "sku_line_group_id": 42
    }
}

Bulk Create

{
    "options": {
        "commit_frequency": 2
    },
    "fields": [
{       
 "facility_id": 648,         
 "work_area_id”: 516,        
 "work_area_activity_id": 553,        
 "cal_date": "2024-02-13",       
 "team_id": "",       
 "cw_user_id”: "33423391",  
 "qty": 120,         
 "uom_id": 1,      
 "sku_line_group_id": 162
 },
 {       
 "facility_id": 648,         
 "work_area_id”: 516,        
 "work_area_activity_id": 553,        
 "cal_date": "2024-02-13",       
 "team_id": 180,       
 "cw_user_id”: "",  
 "qty": 100,         
 "uom_id": 1,      
 "sku_line_group_id": 162
 }
    ]
} 

Request Body Example (XML)

Instance Create

<request>
    <fields> 
        <facility_id>648</facility_id>
        <work_area_id>1056</work_area_id>
        <work_area_activity_id>893</work_area_activity_id>
        <cal_date>2024-03-08</cal_date>
        <team_id>181</team_id>
        <cw_user_id></cw_user_id>
        <qty>15</qty>
        <uom_id>2</uom_id>
        <sku_line_group_id>42</sku_line_group_id>               
    </fields>

Bulk Create

<request>
    <fields>
    <list-item>  
        <facility_id>648</facility_id>
        <work_area_id>1056</work_area_id>
        <work_area_activity_id>476</work_area_activity_id>
        <cal_date>2024-02-13</cal_date>
        <team_id>440</team_id>
        <cw_user_id></cw_user_id>
        <qty>35</qty>
        <uom_id>1</uom_id>
        <sku_line_group_id>2</sku_line_group_id>        
    </list-item>
    <list-item>  
        <facility_id>648</facility_id>
        <work_area_id>516</work_area_id>
        <work_area_activity_id>478</work_area_activity_id>
        <cal_date>2024-02-13</cal_date>
        <team_id></team_id>
        <cw_user_id>787</cw_user_id>
        <qty>350</qty>
        <uom_id>3</uom_id>
        <sku_line_group_id>249</sku_line_group_id>        
    </list-item>
    </fields>
    <options>
        <commit_frequency>2</commit_frequency>
     </options>  
</request>

Note: If the options parameter "commit_frequency" is not provided in the payload, the behavior defaults to same behavior as commit_frequency = 0, which is a all or nothing functionality. In other words, either all records are processed (if successful) or none of the records are processed even if 1 record fails validations.