The meaning of [Quick Check] is that in a column (such as "Customer Number"), you will appear by point-speed check button (this button in the IFS application, F8: list of values ..) will appear. A new window, there is all customer information inside;
For example: To customize an export statistics, the rough fields are as follows: Manual number, .. Order number, customs order number, ... factory area (Contract), sales number (Catalog Number) ......... Where: Contract originated in the Contract in the Site table (the main key of the Site table is contract); CatalogNo is derived from the CatalogNo in the Salespart table (the primary key of the SalesPart table is CatalogNo Contract); ==> The quick investigation of the factory is very simple. The quick investment of the sales material is implemented; 1) ROSE modeling, the model is as follows: The model in the corresponding bag and Others
The model in the package Emcie remembers archived into emcie.mdl; emcie.cat; others.cat
2) IFS's Design adds Emcie.PRJ, associated with the Emcie.mdl that has just been generated; only modifies the corresponding fields of the source table in Model Properties; as follows: Come and modify the Model Properties in Emcie, Storage (Oracle) ), Business logic (PL / SQL); the corresponding operation process will be omitted here; remember that the timely archive will generate an Emcie.cre, ExportsDetail.API, an ExportsDetail.apy script file; 3) post modification of the script file; about .cre file Just delete Storage (& Normal), it is estimated that there is setting, do not generate this statement, I didn't find it; open the exportsdetail.apy script file; find this statement: comment on column & view..conTract is' Flags = kmiu- ^ DataType = String (5) ^ prompt = contract ^ ref = Site ^ '; => "=" The' K 'of the back is the main key value, and if the RER = Site is the maintenance of the content area, Find information in the Site table; because the primary key of the Site table is a Contract, so there is nothing to modify, then see another statement:
Comment on column & view..catalog_no is 'Flags = a-iu- ^ Datatype = String (25) ^ prompt = catalog no ^ ref = salespart ^'; please pay attention to here, but the primary key of the Salespart table is CatalogNo Contract; so modify ==>: comment on column & view..catalog_no is 'Flags = a-iU- ^ DataType = String (25) ^ prompt = catalog no ^ ref = Salespart (contract) ^'; look for APY files All Catalog_no will find this (there should be two): Elsif (Name_ = 'catalog_no') Then newRec_.catalog_no: = value_; if (value_ is not null) Then sales_part_api.exist (newrec_.catalog_no); = => (newRec_.catalog_no, newrec_.contract) End if >> Usually you don't modify, you can't change it in the import script, how to pass the specific parameters, you can see how the process is written; for example above, You can see Sales_PART_API.EXIST;
4) Start importing scripts: CRE, API, APY; must be in turn; 5) Start customerization APL, App, Apt; Run Results1: Run Result2; http://blog.9cbs.net/images/blog_9cbs_net/ Foreveryday007 / 26389 / O_2004082705.JPG
