Background
Mobile Action communicates 100% via API's to M3. Where the functionality we required to build does not have a standard API or there were missing functionality in the standard API we would build a user defined API in CMS010=>CMS015.
We do not use EXPORTMI nor do we use MDBREADMI.
Guiding principle: if we can retrieve the required data by calling an additional API for example MMS200MI_GetItmBasic we would do that instead of creating a user defined API to avoid the unnecessary overhead this causes in implementation and support.
Note: For Cloud Edition customers the custom views and API's can be exported in CMS010 and CMS015 and imported to the environment. If the import fails the log will tell us what sorting order is missing or wrong etc and there will always be some adjusting there. Our API reference ENV is ComActivity's : MT_TRN_790
This is a list of currently used Custom API's
| Info brows cat (CMS010) | Description | Master table | API_Trans (CMS015) | View (CRS020) | Sort order (CRS022) | Index used: (CRS021) | MA Function | Comments |
| MFTRND_Z01 | MA: Find report no by package | MFTRND | LstMFTRND_Z01 | STD01-00 | 1 | 00 | Unpicking | |
| MHDISH_Z01 | MA: Find DPOL via DLIX | MHDISH | LstMHDISH_Z01 | Z01_01 | 99 | 00 | Pick&Pack | To enable IssueMoveModeByDispatchPolicy |
| MHDISH_Z02 | MA: Find DLIX via RIDN | MHDISH | LstMHDISH_Z02 | CUS99-01 | 99 | U1 | Unpicking | |
| MIATTR_Z01 | MA:Get Attr value by Attribute No & ID | MIATTR | LstMIATTR_Z01 | STD01-00 | 1 | 00 | StockMove | Custom putaway logic based on no of Balance ID and attributes |
| MITALO_Z01 | MA: List MITALO (Pick by Item) | MITALO | LstMITALO_Z01 | CUS99-01 | 99 | U1 | Pick by Item | |
| MITALO_Z02 | MA: List Waves in MITALO (Pick WBy Zone) | MITALO | LstMITALO_Z02 | CUS99-01 | 99 | U2 | Wave picking | |
| MITBAL_Z01 | MA: Custom API - SL after Thaw | MITBAL | LstMITBAL_Z01 | Z01_01 | 1 | 00 | Stock Move | Auto Reclassification upon move based on X days configurable. https://globalomnichannel.atlassian.net/browse/WA2-568 |
| MITLOC_Z01 | MA: Lists bal ID by priority date | MITLOC | LstMITLOC_Z01 | CUS99-01 | 99 | U3 | Pick&Pack | To be used when adding pick path to Softallocated picks (replace MM002/G loc with the best one from MITLOC) https://globalomnichannel.atlassian.net/browse/WA2-1073 |
| MITPCE_Z01 | MA: Find locs by Zone and ABC Frequency | MITPCE | LstMITPCE_Z01 | STD99-01 | 99 | U1 | Stock Move | Custom putaway logic based on no of Balance ID and attributes |
| MPAGRH_Z01 | MA: List all valid agr by sup and prio | MPAGRH_Z01 | LstMPAGRH_Z01 | CUS99-01 | 99 | U1 | Bin management - Link docket to sample | |
| MPTRNS_Z01 | MA: By docket (ORPA2) | MPTRNS | LstMPTRNS_Z01 | CUS-99 | 99 | U1 | Bin management - Link docket to sample | |
| MPTRNS_Z02 | MA: List package in ORPISS<90 | MPTRNS | LstMPTRNS_Z02 | CUS99-01 | 99 | U2 | Prt docs by tote | This is so we can re use the same package on and on again. as long as only one of them is in active picking status. |
| https://globalomnichannel.atlassian.net/browse/WA2-1150 | ||||||||
| MPTRNS_Z03 | MA: By External tracking no | MPTRNS | LstMPTRNS_Z03 | CUS99-01 | 99 | U9 | Bin Management Find bin by external track no | |
| ZWAMITBIL30 | MA: Browse on MITBIL | MITBIL | Lst_ZWAMITBIL30 | STD05-00 | 5 | 30 | Pick face replenishment | |
| ZWWAWHUT01 | MA: Whs Utilisation | MITPCE | Lst_ZWWAWHUT01 | ZWWAWHUT01 | 90 | 30 | Whs utilisation screen | Needs some improvement |
| MWOHED_Z99 | MA: Find PRNO via MO number | MWOHED | LstMWOHED_Z99 | STD14-00 | 14 | 14 | Adhoc labelPrint MO label | This could possibly be replaced by MWSLWMMI_LstMOHead or LstMOHead2 |
| MWOMAT_Z01 | MA: List Materials Direct API | MWOMAT | LstMWOMAT_Z01 | CUS99-01 | 99 | U2 | MO Issue List Materials Direct | |
MWOMAT_Z01 | MA: List Materials Direct API | MWOMAT | LstMWOMAT_Z02 | CUS99-01 | 98 | U3 | MO Issue List Materials Direct (List all MO's) | |
| MITLOC_Z02 | CUS99-01 | 99 | U5 | PickByItem | Summarise the stock by item and WHS whe ALOC=1 and STAS=2 (so excluded non allocable stock like in Pack and Dock) is used to calculate available stock for picking. |
Instruction on how to export and import user defined API's in Cloud Edition.
Note: this may work in the on-prem version too depending on how the API is built etc. but we have found that manual copy paste is probably a less time consuming option if on prem.
- CRS021 - Create Sorting options: If the API has a user defined sort order it needs to be exported first (or keyed manually. Tip if it is already used by other consultant application try to see which one is easiest to change. Probably easiest to key the whole thing manually if change is needed. (or manipulate the XML to use a different sort oder
- Export configuration
- Download configuration and store
- Upload configuration
- Import configuration
- CMS010 - Option 26 Export configuration
- Administration Tools, Business Engine Files
- Find the exported XML and DOWNLOAD on a server location/sharepoint
- ComActivity\Mobile Action - Documents\General\WA2.0\MT_CE_Exported_Configurations
- UPLOAD: Administration Tools, Business Engine Files
- Note: If same tennant the Down and upload can be skipped
- Import: Administration Tools, Business Engine Configuration Data
- Find the log under Administration Tools, Business Engine Files and add missing sorting orders etc.
- CMS015 repeat the above steps
Details
Export configuration (In CRS021, CMS010, CMS015)
Business Engine Files: Download data (if not on same tennant)
Upload data in the target environment:
Import configuration data: Business EngineConfiguration Data:
Unsure of the need of Division here
If it fails:
Back to Business Engine Files:
download to be able to view...
log will tell what is missing (the key is to add in the Sorting orders first)
fix it and try again