appse ai Academy: Partner Training Basics

How to Configure SAP B1:

• Create the company DB, pick chart of accounts/localization, set currency/tax/numbering rules upfront.

• Create scoped user roles/authorizations; for integrations (like appse ai), use a dedicated service account, not an admin login.

• Configure BP groups, item groups, warehouses, multi-currency, and document numbering series before go-live.

• Enable Service Layer (port 50000) or DI API, confirm the integration user's license type allows API access.

How to Configure Shopify

• Set store name, currency, timezone, and units under Settings → General; configure legal pages (refund/privacy/ToS) and shipping zones/rates.

• Set up product types, collections (manual/smart), variants, and inventory tracking; enable multi-location inventory if you have multiple warehouses.

• Enable Shopify Payments (or a third-party gateway), configure tax settings (automatic or manual by region), and customize checkout fields/branding.

• Install a private/custom app (Settings → Apps → Develop apps) to generate an Admin API access token with scoped permissions — this is the piece relevant if you're prepping for an APPSeCONNECT integration (order sync, inventory sync, fulfillment).

How to Configure ZOHO CRM

• Configure company details, fiscal year, currency, and Users/Roles under Setup → Users & Control → Security; assign profiles (Standard/CRM/Zia) per user.

• Customize Leads/Deals/Contacts/Accounts modules — layouts, custom fields, deal stages, and lead scoring rules under Setup → Customization.

• Set up Workflow Rules, Blueprints (process enforcement), and assignment rules for lead routing under Setup → Automation.

• Go to Setup → Developer Space → APIs & SDKs to generate an OAuth client ID/secret (Server-based apps) with scoped permissions (e.g., ZohoCRM.modules.ALL) — this is what an APPSeCONNECT/iPaaS integration needs for token-based access to leads/deals/contacts sync.

Customer Sync from Shopify to SAP B1

• Generate a Shopify Admin API access token (via a custom app with read_customers/write_customers scope) and a SAP B1 Service Layer login (dedicated integration user, not admin) — both configured in the connector's connection settings.

• Map Shopify Customer fields (first/last name, email, phone, default address, tags) to SAP B1 Business Partner fields (CardCode, CardName, GroupCode, Address, Contact Person) — decide the CardCode generation rule (auto numbered vs. Shopify customer ID based) upfront.

• Set matching logic to avoid duplicate BPs — usually email or phone as the unique key — and define whether it's create only, update only, or upsert; also decide sync direction/trigger (webhook on new/updated customer vs. scheduled polling).

• Pre configure default BP Group, Payment Terms, Price List, and Territory in SAP B1 for auto created customers, since Shopify doesn't carry this ERP specific data — the integration needs fallback/default values or a mapping table.

• Set up a review/failure queue for records that fail validation (bad tax ID, missing required B1 field), test with a batch of real orders, then enable the live sync.

Partner Account and Contact Sync

• Map source Account/Customer fields (name, tax ID, billing/shipping address, price list, terms) to target Business Partner fields (CardCode, CardName, GroupCode, Address); decide the CardCode generation rule (auto numbered vs. source ID based).

• Sync Contacts as child records under their parent Account/BP — map name, email, phone, job title, and mark one as primary; ensure the integration preserves the Account-Contact parent-child relationship, not flat unrelated records.

• Use email or tax ID/registration number as the unique key to avoid duplicate Accounts and Contacts across systems; define create only, update only, or upsert behavior per entity.

• Set trigger (webhook vs. scheduled polling) and field level ownership — e.g., ERP owns credit limit/payment terms, CRM/source owns marketing preferences — to prevent overwrite conflicts on shared fields.

Automating New Shopify Orders into SAP B1 Sales Orders

• Configure Shopify Admin API access token (read_orders/read_customers scope) or webhook subscription for orders/create, and a SAP B1 Service Layer integration user with permissions on Sales Orders and Business Partners.

• Map Shopify order header (order number, date, currency, shipping/billing address) to SAP B1 Sales Order fields (CardCode, DocDate, DocCurrency, Address); resolve or auto-create the Business Partner first if the customer doesn't already exist in B1 (link back to the Customer/Contact sync flow).

• Map Shopify line items (SKU, quantity, price, discounts, tax) to B1 Sales Order rows (ItemCode, Quantity, Price, DiscountPercent, TaxCode); handle SKU mismatches (Shopify variant SKU vs B1 ItemCode) with a lookup/mapping table, and decide how to treat out-of-stock or unmapped SKUs.

• Use webhook (near real-time) or scheduled polling as the trigger; map Shopify shipping line to a B1 freight/service line, and reconcile Shopify's tax-inclusive pricing with B1's tax code logic (common mismatch point).

• Decide whether to write the B1 DocNum back to Shopify (order tag/note) for traceability, set up a failure queue for orders that fail validation (missing item, invalid BP, tax mismatch), and test with real order variants (partial refunds, cancellations, multi-currency) before go-live.

Inventory Sync Back to Shopify and Error Checks via Email/Outlook

• On SAP B1 goods receipt, transfer, or inventory count, push updated on-hand quantity (per warehouse/location if Shopify has multi-location inventory enabled) back to the mapped Shopify variant via the Admin API inventoryLevels endpoint or connector-native inventory sync.

• Match B1 ItemCode to Shopify variant SKU/ID via the same lookup table used for order sync; apply a safety buffer or reserve threshold if B1 on-hand includes committed-but-unshipped stock, so Shopify doesn't oversell.

• Decide near-real-time (webhook/event on B1 stock change) vs. scheduled polling (e.g. every 5–15 min); since B1 owns true inventory, treat it as the single source of truth and always overwrite Shopify — never let Shopify-side manual edits persist.

• Configure the connector's failure queue to trigger an Outlook/SMTP alert (via Microsoft Graph API or SMTP relay) on sync failures — missing SKU mapping, negative stock, API rate-limit/auth errors — routed to a shared mailbox, with a daily digest summary and immediate alert for critical failures (e.g. auth token expiry).