> For the complete documentation index, see [llms.txt](https://docs.greytrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.greytrix.com/gumu-salesforce-integration/sagex3/transaction/sales-order.md). # Address Creation and Promotion To promote an Address the Account should be promoted or linked to Sage X3. 1. Creating the Shipping/Billing Address while promoting the Account is mandatory. 2. Once completed with promoting the Account, then it gets automatically promoted to Sage X3. As shown in the below image B01 and S01 are the promoted Addresses.

3. Click the "**New Address**" button, to add an additional Shipping/Billing Address for the Account.

4. Choose the Address Type (Shipping or Billing) from the dropdown menu, ensuring that you change the Address Code to avoid duplication. Complete all the necessary details. In the image above, multiple Shipping and Billing Addresses have been created as examples.

### **Address Details**

Field	Description
Address Code	For easy identification, the Address code should always be unique (two addresses for the Account cannot have same Address Code)
Is Default Ship-To-Address?	Do you want this to be the Default Address in Salesforce and Sage
Address Type	Is the new Address created a Billing or Shipping address
Address Name	Same as the Address Code, Address Name should also be unique

5. To view/edit the promoted shipping address click on the pencil icon under the Action panel to edit (bottom left).

6. After making the updates, let's review the changes in Sage X3 to gain a clearer understanding of the real-time adjustments.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.greytrix.com/gumu-salesforce-integration/sagex3/transaction/sales-order.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.