Page History

...

Sponsored by:
Integral Business Solutions (http://www.go-integral.com)
Hotwax Media, Inc (http://www.hotwaxmedia.com)
Antwebsystems Co,.Ltd (http://www.antwebsystems.com)

Table of Contents

1. Purpose and Goal of This Document
2. Data To Gather for Setup
3. General Terms and Information
   1. OFBiz "Manager" Applications
   2. Other OFBiz Terms
4. Business Setup Process
   1. General Company Setup
      1. Company Contact Information
   2. Facility (Warehouse) Setup
   3. WebSite Setup
   4. Store Setup
      1. Store Settings
      2. Store Role Settings
      3. Promotional Settings
      4. Catalog Settings
      5. Web Site Settings
      6. Sales Tax Settings
      7. Store Shipping Settings
         1. UPS Online Rate Estimates
         2. UPS XPCI Integration
         3. USPS Online Rate Estimates
      8. Store Payment Settings
         1. Payment Processor Details
         2. PayPal Payment Setup
         3. CyberSource Payment Setup
         4. Giftcards
      9. e-mail Settings
      10. Survey Settings
      11. General Settings Override
   5. Catalog, Category, Product Setup
      1. Catalog Setup
      2. Category Setup
      3. Product Setup
         1. Add Content to the New Product
         2. Add Prices to the Product
5. Accounting Organization and Setup Process

Purpose and Goal of This Document

Anchor
purpAndGoal purpAndGoal

...

Manager applications which will be referenced in this document include the:
"Catalog Manager" accessed at:

http://localhost:8080/catalog/control/main

"Party Manager" accessed at:

http://localhost:8080/partymgr/control/main

More technical web based tools, or tools for the OFBiz framework are available in the "Web Tools" application: http://localhost:8080/webtools/control/main

...

This is configured using various properties in the file:

${ofbiz install dir}/applications/product/config/shipment.properties

1. UPS XPCI Access License Number
   1. o shipment.ups.access.license.number
   2. o Example: TEST262223144CAT
   3. o This license number is used for both the UPS shipment estimate online service and the UPS XPCI shipping interface services (described below)
2. Shipper Default Pickup Type
   1. shipment.ups.shipper.pickup.type
   2. Example: 06
   3. Valid options:
      1. 01 - Daily Pickup
      2. 03 - Customer Counter
      3. 06 - One Time Pickup
      4. 07 - On Call Air Pickup
      5. 11 - Suggested Retail Rates (UPS Store)
      6. 19 - Letter Center
      7. 20 - Air Service Center
   4. Choose the option that represents your relationship with UPS. This affects the estimated rate you will get back since UPS varies their prices based on how you get your packages to them.
3. Estimate split into packages
   1. shipment.ups.max.estimate.weight
   2. Example: "90" meaning 90 pounds
   3. This number is used as the max weight per package when the total weight is > than this weight the weights are split into packages not exceeding max.

...

This is configured using various properties in the file:

${ofbiz install dir}/applications/product/config/shipment.properties

1. UPS Shipper Number
   1. shipment.ups.shipper.number
   2. Example: 486915
2. UPS Bill Shipper Account Number
   1. shipment.ups.bill.shipper.account.number
   2. Example: 486915
3. UPS XPCI Access License Number
   1. shipment.ups.access.license.number
   2. Example: TEST262223144CAT
4. UPS XPCI Access User ID
   1. shipment.ups.access.user.id
5. UPS XPCI Access Password
   1. shipment.ups.access.password
6. Setting to save files needed for UPS certification
   1. shipment.ups.save.certification.info=true
   2. shipment.ups.save.certification.path=/ofbiz/work/ofbiz/upscert
   3. This option is used to create the artifacts the UPS needs to certify client implementation. It is generally required for each customer to go through this process and for UPS to verify the results. Once this is done the shipment.ups.save.certification.info property should be set to false. For more information on this process, see the UPS XPCI documentation and additional information in the UpsServices.java file.

...

This is configured using various properties in the file:

${ofbiz install dir}/applications/product/config/shipment.properties

1. USPS Connection URL & timeout in seconds
   1. shipment.usps.connect.url
   2. Example: http://localhost/facility/ShippingAPI.dll
   3. shipment.usps.connect.timeout
   4. Example: 60
2. USPS Credentials
   1. shipment.usps.access.userid
   2. shipment.usps.access.password
3. Estimate split into packages
   1. shipment.usps.max.estimate.weight
   2. Example: 70

...

While the payment services and high level settings are configured in the Store section of the Catalog Manager the detailed configuration for the various payment processing services are configured in the file:

${ofbiz install dir}/applications/accounting/config/payment.properties

1. There are many comments in this file and sections for each of the major payment processing services.
2. If you are using any credit card payment processor, be sure to check and if necessary change the properties near the beginning of the payment.properties file that follow the pattern: "payment.general.reauth.*.days".

...

See the end-user documentation space for details on how to set these things up and what they mean. Also see this for more advanced options for Products, Categories, and so on.

Accounting data organization and Setup (field/entitynames in brackets[])

Anchor
accountingSetup accountingSetup

General principles

1. The general ledger of ofbiz consists out of a list of 'ledger buckets = glAccounts' with a non meaningfull ID: glAccountId and a meaningfull code accountCode and a meaningfull name accountName Initially, in the demo data, the account id and code are the same. When reorganizations are required these codes can be easily renamed without changing the glAccountId.
2. The buckets are in a hierachy where totals of the lower levels are added together and be shown at the higher levels, therefore every ledger bucket has a parent parentGlAccountId; with one exeption if the glaccount is a toplevel glAccount/bucket.
3. Every glAccount has a account type id glAccountTypeId with a organization dependent second default glAccountId GlAccountTypeDefault.glAccountId to be able for the system to create the double booking. (Currently the system will do that always to "ACCOUNTS_RECEIVABLE" default glAccountTypeId for sales invoices).
4. Transactions are created for several reasons like posting of invoices or payments, inventory movements and workeffort costs.
5. GlAccount class is used for categorization and reporting.

General Setup (accounting -> global GlSettings)

1. Company data and internal organizations
   demo file at: /applications/accounting/data/DemoOrganizationData.xml
2. All glAccounts are predefined GlAccount and can be viewed on the globalGlSettings->chartOfAccounts screen.
   demo file at /applications/accounting/data/DemoGeneralChartOfAccounts.xml
3. Load the Sales/purchase InvoiceItemType table and default glAccountId general setup for all organizations.
   demo file at /applications/accounting/data/DemoGlSetupData.xml

Organizational Setup (accounting -> organizational settings -> setup).

1. The predefined glAccounts are assigned to an organization GlAccountOrganization on screen chartOfAccounts (this file can only be loaded and not changed)
   demo file at /applications/accounting/data/DemoGlSetupData.xml
2. if required override the invoiceItem type type assignement for a particular organization at the glAccountDefaults->SalesInvoice/PurchaseInvoice
3. Enter/load the payment TYPE GlType Mapping file PaymentGlAccountTypeMap at
   glAccountDefaults->PaymentTypeGlMapping
4. Enter/load the payment METHOD GlType Mapping file PaymentMethodTypeGlAccount at
   glAccountDefaults->PaymentMethodTypeGlMapping

Creating ledger transactions.

1. Sales invoice
2. Purchase invoice
3. Incoming payment
4. Outgoing payment
5. Inventary adjustment
6. Workeffort costs