Before you arrange AFAS setup

Identify your AFAS environment and whether you use a production or test environment. Check who administers AFAS for your organisation. If a partner maintains an existing connection, include that partner in the setup discussion.

Decide which stock, sales, supplier or purchasing information you need. This is your requested scope, not a list of automatically included flows.

Steps to arrange AFAS setup

  1. Contact Optiply Support and request AFAS setup guidance.
  2. Identify the environment and explain whether this is a new or existing connection.
  3. Describe the data you need and name your existing connection owner, if you have one.
  4. Ask Support to confirm the connection route, responsible setup owner and applicable field-mapping instructions.
  5. Ask the setup owner which authentication method and AFAS permissions your connection needs.
  6. Follow the confirmed instructions with your AFAS administrator.
  7. Share any requested access details only through the secure method agreed with the setup owner.
  8. Agree the first checks for the selected data before using it for purchasing decisions.

Fields in your AFAS setup request

  • Environment: the AFAS environment concerned, including production or test.
  • Connection state: new setup, an existing connection, or a change to a partner-maintained connection.
  • Setup owner: the person or team responsible for the connection and its configuration.
  • Required data: the entities and direction you want the setup owner to confirm.
  • Verification checks: the records and values you will compare after setup.

Keep passwords, tokens and other access values out of your initial request.

What you see when AFAS setup coordination worked

You know who owns setup, which environment it concerns and where to obtain the applicable connection and mapping instructions. A Support request alone does not create or verify a connection.

Limits of arranging AFAS setup

Agree availability, partner involvement, subscription, price and synchronization timing with Support. Do not choose a partner or create credentials from the system name alone.

AFAS supports different authentication routes. Ask your setup owner to select the appropriate route before changing an existing app connector. AFAS's app connector guidance explains its access controls.

If AFAS setup coordination did not work

If the connection route or mapping remains unclear, return to Support with the unresolved question. Keep an existing working configuration unchanged until its owner confirms the next action.