Modification to setup instructions, version 7.5.2
Fulfillment setup requires multiple Oracle user ID's to be set up, one as the fulfillment house database owners, and one for each fulfillment house customer. In the following write up, FFMASTER is the fulfillment house database owner, and FFCUSTOMER is the fulfillment house customer. In reality, the oracle user ID's are user-defined.
1. Create a new Oracle user to hold the fulfillment house customer. The customer number in the master fulfillment house database must be the same as the Oracle user for the customer.
* For example, if the customer number in the master fulfillment house database is CUST01, the customer Oracle user ID must also be CUST01.
* You can use the makends.sql script to create your customer Oracle user. More commonly, a skeleton user will be set up at each fulfillment company site, and this skeleton user will be exported and then imported to the new Oracle user.
2. Both the fulfillment house database master and each fulfillment house customer must have the same codes in use for the financial enterprise, manufacturing enterprise and plant. The records are different for each Oracle user, so the descriptions can be different, but the code must be the same across all NDS instances.
* For example, if FFMASTER had the following set up:
Financial enterprise 100 - Master Company
Manufacturing enterprise 100 - Master Company
Manufacturing plant 10 - Master Plant
* Then FFCUSTOMER would have this set up:
Financial enterprise 100 - Customer Company
Manufacturing enterprise 100 - Customer Company
Manufacturing plant 10 - Customer Plant
3. As FFMASTER, run ff_grants.sql creates grants for the tables
4. As FFCUSTOMER, run ff_cust.sql destroys tables for the customer instance
5. As FFMASTER, run program SPUM, System Authorization Maintenance, and set up access for the FFCUSTOMER user.
6. The security system and menu system exist only in the fulfillment house database master instance (FFMASTER). As FFMASTER, run program MUSC, User Security Maintenance.
7. Set up an application log in for FFCUSTOMER, so that FFCUSTOMER can access the menu system.
8. As FFCUSTOMER, run program MUIW, Windows Menu File Uploads, and import the following:
* nf_ctl - System Control Definitions
* nf_rcl - Report Classes
* nf_org - Organization definitions
* nf_fsh - Drill Down Definitions
* nf_fsk - Drill Down Target Keys
* nf_aut - Audit Tables
* nf_auk - Audit Keys
* nf_aud - Audit Columns
* nf_mda - Renumber Metadata
* nf_mdk - Renumber Headers
* nf_glint - GL Posting Parameters
9. As FFMASTER, run program UTCM, Fulfillment Context Maintenance, and enter the FFMASTER and FFCUSTOMER in the Project Schema fields. Set the pop-list to the appropriate setting.
10. From the menu, press the [Password] button. Enter the FFCUSTOMER log in.
11. Run the following programs to set up the company names for the fulfillment customer user (FFCUSTOMER).
* MUOM, Menu Organization Code Maintenance
* GMEM, Enterprise Maintenance
* ILUM, Manufacturing Enterprise Maintenance
* ILPM, Plant Code Maintenance
* SPAP, System Parameters/Accounting Parameters
12. From the menu, press the [Password] button. Enter the FFCUSTOMER log in. Make sure the changes to the company name have been saved.
13. Complete initial system setup, including system tables and the general ledger, and complete the basic steps for customer setup.
14. Go to program CMMM, Customer Master Maintenance. Enter a customer number here for the fulfillment house customer (FFCUSTOMER with the SAME customer number as is used for the customer in the fulfillment house database master (FFMASTER).
* If the customer number in the fulfillment house database master is CUST01, you must create a customer in fulfillment house customer instance numbered CUST01. This customer record should contain the same information as the CUST01 customer record in the fulfillment house database master.
* This is to prevent Oracle errors in Project Tracking.
15. From the menu, press the [Password] button. Enter the FFMASTER log in.
16. Run program FFSCI, Push Common Inventory to Customers. This will copy all existing items with the Common Item flag set to on from the fulfillment house database master to the fulfillment house customers.
17. In program ICMM, Inventory Master Maintenance, enter any other common inventory. Items that are defined as common inventory have the Common Item flag set to on.
* When the Common Item flag is set to on for an inventory item, the inventory information is copied to all fulfillment house customer instances.
* Common items cannot be lot or serial controlled.
* Common items can only be created and maintained at the fulfillment house database master instance (FFMASTER).
* If a common item is converted back to a private item (Common Item flag set to off), the item copies in the fulfillment house customer instances (FFCUSTOMER) will not be deleted.
* You can set up common items to only be common for a specific fulfillment customer. In program ICMM, Inventory Master Maintenance, when setting the Common Item flag to on, also enter the fulfillment customer number in the Cust field. The inventory information will only be copied to that fulfillment customer database instance. Only that fulfillment customer database instance will remain synchronized with the FFMASTER for that common item.
* For more information about common item inventory transactions, see the Fulfillment Periodic Tasks.
18. In program GPTM, Posting Template Maintenance, set up general ledger templates for common items.
* In the fulfillment house database master instance (FFMASTER), set up templates for transactions for common items to post to the general ledger.
* In the fulfillment house customer instances (FFCUSTOMER), set up templates that suppress transactions for common items from posting to the general ledger.
Use program UTCM, Fulfillment Context Maintenance, to view the database tables that are shared for fulfillment databases. Shared tables are owned by the fulfillment house database master.
1. Run ndsidrop for the client.
2. Drop the grants from the master for the client.
To drop the grants you can create a special drop grant script by using the ff_grants.sql and for each grant, modifying from:
grant all on table to &&the_customer;
to
revoke all on table from &&the_customer;
3. Run UTCM, Fulfillment Context Maintenance, and remove the client's schema.