Map companies, branches and items across the link, and know what the pair carries — transcript

Play this as a presentation — one slide per step, with the same narration. Every word of every step is on this page.

This presentation is for you if your tenant and a partner’s tenant are connected and you now have to make the link say something useful: which company and branch is which, and which of your items the partner may pair with theirs. In about nine minutes you will map a company and branch, open items to the partner and pair them, learn what the pair does and does not carry, and end a link knowing exactly what stays behind.

Step 1 — Map your company and branch to the partner’s

After this step a company and branch pairing exists on both sides. A mapping says: this company and branch of mine, and this customer or supplier record I keep for the partner, correspond to that company and branch of theirs. GadgetSphere Distribution maps its company and branch GSD-KV-01, plus its customer record for the dealer, to the dealer’s company and main branch. Either side may create one, only while the connection reads connected; each customer or supplier record maps once per partner tenant. The partner’s companies and branches are read live from its tenant, so the lists slow with every connection you hold. Nothing checks that the company and branch you save exist on either side; a wrong branch is accepted, so check every part before saving and read it back afterwards. Setting a mapping inactive stops nothing; it stays listed as before. To end one, delete it; the server removes the other side’s copy in the same call.

Reference: T2T Admin — Mapping companies and branches

Step 2 — Create the mapping from the side that will maintain it

After this step you will know which side should own each mapping. When you save a mapping, the server writes a copy into the partner’s tenant, and the copy is not a mirror. It records the partner’s own company and branch, and your customer record as the other party, and nothing else: not which of your companies it points back to, and not the partner’s own record for you. So on the partner’s side, the view that pairs companies shows a blank against your branches where the pairing should be, and the view that lists only mapped pairs leaves it out. The side that created the mapping is the side that sees it whole. Agree with the partner, before anyone clicks, which side creates and looks after each mapping, and write that agreement down with the connection’s name, because nothing in the mapping itself will tell a newcomer.

Reference: T2T Admin — Mapping companies and branches

Step 3 — Open items to the partner, as the host

After this step the dealer can see the items you chose and no others. Item sharing is two steps, and the host takes the first. Open the item in Doc Item Maintenance, then its T2T Item Mapping tab, T2T meaning tenant to tenant, and the Guest Tenant Permission Listing; the tab is there unless your application settings hide it, and its tenant list is empty until a connection exists. Add a permission for the dealer’s tenant against that item. Do this for GadgetSphere Distribution’s ultraportable laptop range and nothing else, and the dealer’s search of your catalogue returns only those. A permission can be granted only while the dealer is connected. To take an item back, delete the permission from the same listing; nothing else withdraws it, and any pair the dealer already made stays until someone deletes it.

Reference: T2T Admin — Sharing items

Step 4 — Pair the items, as the guest

After this step the two item codes are paired on both sides. The guest takes the second step. On the dealer’s tenant, open the dealer’s own item, its T2T Item Mapping tab, then Host Tenant. Choose GadgetSphere Distribution from the tenant list, search the host’s items by name or code, and the search offers only what the host has permitted to you. Save, and the pair is written on both sides: the guest’s row pointing at the host’s item, the host’s row pointing back. The rules are strict. Without a permission the pair is refused. An item can be in only one pair per connection in each direction, so a second dealer code against the same host item is refused. And pairing works only while the host is connected. The host sees every pair on its Guest Tenant Item Mapping sub-tab and may change or delete one, but only the guest can create it.

Reference: T2T Admin — Sharing items

Step 5 — Reconcile the item masters yourself, before and after

After this step you will know which part of item mapping is your job. The pair records that two codes mean the same thing; it holds the two item references, the partner tenant, which side is which, its own status and stamps, and nothing about the item. It copies no description, unit, price or tax code, and a later edit on either side is not carried across; no item update reads the pair. So before pairing, someone at each business compares the two items and agrees they are the same thing in the same unit; a laptop sold by the unit on one side and by the carton on the other is a wrong pair the software accepts. After pairing, check on the host’s side: the Guest Tenant Item Mapping sub-tab lists the dealer’s item code and name against yours, where a wrong pair is caught. When either side retires a code, delete the pair; nothing does it for you.

Reference: T2T Admin — Lifecycle and effects

Step 6 — Add the partner’s users to an external team, knowing what is not established

After this step you will know what an external team is and what nobody has yet told you about it. An external team is a team in your own tenant, tied to the partner’s, whose members you choose from the partner’s user list; you can create one only while the partner is connected, you become its owner when you create it, and it can be linked to a role. Creating, changing or deleting the team and adding or removing a member is written to the audit trail; the role link is not. What a member of that team can then reach in your tenant is stated on none of our pages, and this series does not claim it. So ask BigLedger what the team grants and add nobody until you have the answer in writing; and treat membership like any other access, with a named owner on your side and a review when the partner’s staff change.

Reference: T2T Admin — External teams

Step 7 — Disconnect, and know what stays behind

After this step you can end a link without surprises. Either side can end it: the guest by answering disconnect, the host by changing the connection’s status, and both records move together. What stays behind: every company mapping and item pair remains on both sides, and every item permission on the host’s, because disconnecting revokes nothing and deletes nothing. What stops: no new mapping, permission or pair can be made and no pair can be changed while the connection is not connected. What you can still do: the host can delete a permission and either side can delete a pair; a company mapping can be read but not changed or deleted until you reconnect. Nothing tells the partner, so tell them yourself, and agree before you disconnect whether permissions and pairs should be deleted first, permission then pair. Reconnecting is the guest’s move, and only while the host still approves it.

Reference: T2T Admin — Connecting the two sides

How the steps fit together

    flowchart TD
  s1["Step 1 — Map your company and branch to the partner's"]
  s2["Step 2 — Create the mapping from the side that will maintain it"]
  s3["Step 3 — Open items to the partner, as the host"]
  s4["Step 4 — Pair the items, as the guest"]
  s5["Step 5 — Reconcile the item masters yourself, before and after"]
  s6["Step 6 — Add the partner's users to an external team, knowing what is not established"]
  s7["Step 7 — Disconnect, and know what stays behind"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  s6 --> s7
  

Check yourself

Three to five questions on what you just heard. Every correct answer links to the page that makes it correct, so you can check the source, not just the mark.

Back to the series · Play this as a presentation