Hello,
We have updated from IFS 24.R1 to 25.R1 and as many times before we face multiple changes in API’s and Views.
Im just interested if there is any recommendation how to work with this? If this still is the recommended way and we still want to improve our processes, I dont really now how we should keep being evergreen. Standard lobbys are of course good but never satisfies my colleagues.
For example we have created a lobby based on view purchase_receipt_stat_uiv. And if we look at removed fields from this view there is a lot. Some of them are used in our lobbys that now of course stopped to work and there are pretty much job to recreate it and find usable values from other views.
Regards,
Johan Magnusson
Removed fields in mentioned view
| v1 |
| ACTIVITY_SEQ |
| BUY_UNIT_MEAS |
| CONTRACT |
| DESCRIPTION |
| LINE_NO |
| MAX_DAYS_EARLY |
| MAX_DAYS_LATE |
| OBJID |
| OBJKEY |
| OBJVERSION |
| ORDER_LINE_OBJSTATE |
| ORDER_NO |
| PART_NO |
| PLANNED_DELIVERY_DATE |
| PROJECT_ID |
| PROMISED_DELIVERY_DATE |
| PURCHASE_SITE |
| QTY_ARRIVED |
| QTY_INVOICE |
| QTY_REJECTED |
| QTY_RETURN_CREDIT |
| QTY_RETURN_REWORK |
| REAL_ARRIVAL_DATE |
| REAL_DELIVERY_DATE |
| RECEIPT_NO |
| RELEASE_NO |
| RENTAL_DB |
| SCRAPPED_FOR_CREDIT_QTY |
| SCRAPPED_NO_CREDIT_QTY |
| VENDOR_NAME |
| VENDOR_NO |
| -- Added attributes -- |
| MANUFACTURER_ID |
| SOURCE_REF_TYPE_DB |
|
|