---
schema_version: "1"
id: fa12ff5a9a8ecc8e056594f1f3f485441823a2816a7782235a9a6dc0a1f8b94a
title: Accelerator Setup Guide
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/manufacturing/latest/mfg-setup-guide.md
canonical_url: https://docs.mulesoft.com/manufacturing/latest/mfg-setup-guide
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 05a836ad871a9f7950227d949158befdfe1f0d7ce42481b008eda1ad461cb22a
description: MuleSoft Documentation Site
release: "1.4"
latest: true
---
---
product: Manufacturing
version: 1.4
is-latest-version: true
---

# Accelerator Setup Guide

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

This page provides guidance on configuring the various systems and products required to implement
the use cases provided by this solution.

## Salesforce Manufacturing Cloud

The following provides guidance on the custom fields that need to be created for the customer,
product, and sales order sync use cases in order to function end-to-end.

## Custom Fields

The following fields must be created in the corresponding objects.

<table><colgroup><col> <col> <col> <col> <col> <col> <col></colgroup><thead><tr><th>Salesforce Object</th><th>Field Name</th><th>Data Type</th><th>Length</th><th>Unique</th><th>ExternalId</th><th>Description</th></tr></thead><tbody><tr><td><p>Account</p></td><td><p>Global_Customer_Id__c</p></td><td><p>Text</p></td><td><p>36</p></td><td><p>Y</p></td><td><p>Y</p></td><td></td></tr><tr><td><p>Order</p></td><td><p>Global_SalesOrder_Id__c</p></td><td><p>Text</p></td><td><p>36</p></td><td><p>Y</p></td><td><p>Y</p></td><td></td></tr><tr><td><p>Order</p></td><td><p>Total_Tax__c</p></td><td><p>Currency</p></td><td><p>10,2</p></td><td><p>Y</p></td><td><p>Y</p></td><td></td></tr><tr><td><p>Order</p></td><td><p>OrderTotalAmount__c</p></td><td><p>Formula (Currency)</p></td><td><p>10,2</p></td><td><p>Y</p></td><td><p>Y</p></td><td><p>Order Total Amount is sum of Shipping<em>c, Total_Tax</em>c, and TotalAmount</p></td></tr><tr><td><p>Product2</p></td><td><p>Global_Product_Id__c</p></td><td><p>Text</p></td><td><p>36</p></td><td><p>Y</p></td><td><p>Y</p></td><td></td></tr></tbody></table>

## Anypoint MQ Configuration

The Anypoint-MQ-Queues-Exchanges Postman collection in the
[MFG Common Resources project](https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-common-resources-src/)
will pre-create all MQ destinations required by the accelerator components.

The collection requires the dev environment template to be imported into your Postman workspace and
assigned proper values first. The following MQ destinations will be created upon successful
execution.

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Queue Name</th><th>Bound to Exchange</th><th>Dead Letter Queue Name</th></tr></thead><tbody><tr><td><p>mfg-customer-update-queue</p></td><td><p>accelerator-customer-update-exchange</p></td><td><p>mfg-customer-update-queue-dlq</p></td></tr><tr><td><p>mfg-product-update-queue</p></td><td><p>accelerator-product-update-exchange</p></td><td><p>mfg-product-update-queue-dlq</p></td></tr><tr><td><p>mfg-order-update-queue</p></td><td><p>accelerator-order-update-exchange</p></td><td><p>mfg-order-update-queue-dlq</p></td></tr><tr><td><p>mfg-rebatepayout-create-queue</p></td><td><p>mfg-rebatepayout-create-exchange</p></td><td><p>mfg-rebatepayout-create-dl-queue</p></td></tr></tbody></table>

## Configurations in S/4HANA

Below are all the configuration arrangements that are required for this use case:

<table><colgroup><col> <col></colgroup><thead><tr><th>Communication Arrangement</th><th>Service Name</th></tr></thead><tbody><tr><td><p>SAP_COM_0008</p></td><td><p>Business Partner - Replicate from SAP S/4HANA Cloud to Client</p></td></tr><tr><td><p>SAP_COM_0009</p></td><td><p>Product Catalog - Replicate from SAP S/4HANA Cloud to Client</p></td></tr><tr><td><p>SAP_COM_0287</p></td><td><p>Sales Order Bulk Replication Integration</p></td></tr></tbody></table>

## Configure Communication Arrangement

For communication arrangement SAP\_COM\_0287 to replicate the sales orders pricing elements, the
following configuration is required.

1.  Enter the **Communication arrangement** app to edit or create the arrangement.

2.  At outbound services sections, complete with the following:

![SAP S/4HANA communication arrangement configuration for SAP\_COM\_0287](/mulesoft/current/en-us/manufacturing/latest/_images/mfg-saphana-setup-1.png)

## Custom Fields

Create the following fields in the corresponding objects for the use case:

<table><colgroup><col> <col> <col> <col> <col> <col></colgroup><thead><tr><th>Salesforce Object</th><th>Field Name</th><th>Data Type</th><th>Length</th><th>Unique</th><th>ExternalId</th></tr></thead><tbody><tr><td><p>BusinessPartner</p></td><td><p>YY1_SME_MPARTYROLEID_M_bus</p></td><td><p>Text</p></td><td><p>40</p></td><td><p>Y</p></td><td><p>Y</p></td></tr><tr><td><p>SalesOrder</p></td><td><p>YY1_SME_MORDERID_MFG_SDH</p></td><td><p>Text</p></td><td><p>40</p></td><td><p>Y</p></td><td><p>Y</p></td></tr><tr><td><p>Product</p></td><td><p>YY1_SME_UnvProductId_M_PRD</p></td><td><p>Text</p></td><td><p>40</p></td><td><p>Y</p></td><td><p>Y</p></td></tr></tbody></table>

## Custom CDS View

- Name: YY1\_JournalEntryItem\_Info

- Representative Key: AccountingDocument

- Scenario: External API

- Data Source: I\_JournalEntryItem

- Elements:

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Alias</th><th>Path</th><th>Type</th><th>Key</th></tr></thead><tbody><tr><td><p>SourceLedger</p></td><td><p>I_JournalEntryItem.SourceLedger</p></td><td><p>CHAR (2)</p></td><td><p>Yes</p></td></tr><tr><td><p>CompanyCode</p></td><td><p>I_JournalEntryItem.CompanyCode</p></td><td><p>CHAR (4)</p></td><td><p>Yes</p></td></tr><tr><td><p>FiscalYear</p></td><td><p>I_JournalEntryItem.FiscalYear</p></td><td><p>NUMC (4)</p></td><td><p>Yes</p></td></tr><tr><td><p>AccountingDocument</p></td><td><p>I_JournalEntryItem.AccountingDocument</p></td><td><p>CHAR (10)</p></td><td><p>Yes</p></td></tr><tr><td><p>LedgerGLLineItem</p></td><td><p>I_JournalEntryItem.LedgerGLLineItem</p></td><td><p>CHAR(6)</p></td><td><p>Yes</p></td></tr><tr><td><p>Ledger</p></td><td><p>I_JournalEntryItem.Ledger</p></td><td><p>CHAR(2)</p></td><td><p>Yes</p></td></tr><tr><td><p>AccountingDocumentType</p></td><td><p>I_JournalEntryItem.AccountingDocumentType</p></td><td><p>CHAR(2)</p></td><td><p>No</p></td></tr><tr><td><p>Customer</p></td><td><p>I_JournalEntryItem.Customer</p></td><td><p>CHAR(10)</p></td><td><p>No</p></td></tr><tr><td><p>YY1_SME_ExtPaymID_MFG_JEI</p></td><td><p>I_JournalEntryItem.YY1_SME_ExtPaymID_MFG_JEI</p></td><td><p>CHAR(20)</p></td><td><p>No</p></td></tr><tr><td><p>CreationDate</p></td><td><p>I_JournalEntryItem._JournalEntry.AccountingDocumentCreationDate</p></td><td><p>DATS (8)</p></td><td><p>No</p></td></tr><tr><td><p>LastChangeDate</p></td><td><p>I_JournalEntryItem._JournalEntry.LastChangeDate</p></td><td><p>DATS (8)</p></td><td><p>No</p></td></tr><tr><td><p>IsReversed</p></td><td><p>I_JournalEntryItem._JournalEntry.IsReversed</p></td><td><p>CHAR(1)</p></td><td><p>No</p></td></tr><tr><td><p>ReversalReason</p></td><td><p>I_JournalEntryItem._JournalEntry.ReversalReason</p></td><td><p>CHAR(2)</p></td><td><p>No</p></td></tr><tr><td><p>ReverseDocument</p></td><td><p>I_JournalEntryItem._JournalEntry.ReverseDocument</p></td><td><p>CHAR(10)</p></td><td><p>No</p></td></tr><tr><td><p>ClearingDate</p></td><td><p>I_JournalEntryItem.ClearingDate</p></td><td><p>DATS (8)</p></td><td><p>No</p></td></tr><tr><td><p>ClearingAccountingDocument</p></td><td><p>I_JournalEntryItem.ClearingAccountingDocument</p></td><td><p>CHAR(10)</p></td><td><p>No</p></td></tr><tr><td><p>ClearingDocumentLastChangeDate</p></td><td><p>I_JournalEntryItem._ClearingAccountingDocument.LastChangeDate</p></td><td><p>DATS (8)</p></td><td><p>No</p></td></tr><tr><td><p>ClearingDocumentCreationDate</p></td><td><p>I_JournalEntryItem._ClearingAccountingDocument.AccountingDocumentCreationDate</p></td><td><p>DATS (8)</p></td><td><p>No</p></td></tr><tr><td><p>ClearingDocumentCreationTime</p></td><td><p>I_JournalEntryItem._ClearingAccountingDocument.CreationTime</p></td><td><p>TIMS (6)</p></td><td><p>No</p></td></tr><tr><td><p>AmountInCompanyCodeCurrency</p></td><td><p>I_JournalEntryItem._ClearingAccountingDocument._OperationalAcctgDocItem.AmountInCompanyCodeCurrency</p></td><td><p>CURR (23,2)</p></td><td><p>No</p></td></tr><tr><td><p>AmountInTransactionCurrency</p></td><td><p>I_JournalEntryItem._ClearingAccountingDocument._OperationalAcctgDocItem.AmountInTransactionCurrency</p></td><td><p>CURR (23,2)</p></td><td><p>No</p></td></tr><tr><td><p>TransactionCurrency</p></td><td><p>I_JournalEntryItem._ClearingAccountingDocument._OperationalAcctgDocItem.TransactionCurrency</p></td><td><p>CUKY (5)</p></td><td><p>No</p></td></tr><tr><td><p>CompanyCodeCurrency</p></td><td><p>I_JournalEntryItem._ClearingAccountingDocument._OperationalAcctgDocItem.CompanyCodeCurrency</p></td><td><p>CUKY (5)</p></td><td><p>No</p></td></tr></tbody></table>

A custom communication scenario has to be created adding this CDS view as an inbound service. Once
published, create a communication arrangement using that custom communication scenario. That
arrangement will have the service URL to retrieve the Journal Entry Item information.

## See Also

- [Prerequisites](https://docs.mulesoft.com/manufacturing/latest/prerequisites)

- [MuleSoft Accelerator for Manufacturing](https://docs.mulesoft.com/manufacturing/latest/)