This document describes the process the link creation between vendor and Company, Purchasing Order, Plant, Partner and PI1 system.
This procedure specifies the role of Vendor Master Data and the systems involved (PF1_020, WP1_400 and PI1_020).
| Requesters | The requester is responsible for sending these requests to D&A Team mailbox ptp-data.analysis@solvaysbs.freshdesk.com or via Vendor Workflow Request. |
Data Operations Team | D&A Team is responsible for receiving the request from the requesters and update vendors MD accordingly. Before proceed with the request, the person who do so must perform all the necessary checks in order to avoid duplicate vendors set up on the system. It is under Data Team responsibility to check whether all the required information to set up a vendor account was provided. Once the request is completely processed, Data Team has to inform the requester of the completion of the request. |
The link between a vendor and a company code is performed without approval.
The transaction used is XK02 or FK02.
NOTE: When extending a vendor at accounting level, we take as reference the values by the following order:
Reconciliation Account
The reconciliation account in G/L accounting is the account which is updated parallel to the sub ledger account for normal postings (for example, invoice or payment).
Indicates the layout rule for the Allocation field in the document line item.
This field contains the account number of the master record for the head office account.
You specify this account number only for branch accounts (examples: ZD15, ZA15). Items that you post using the branch account number are automatically posted to the head office account.
The link of a branch to a company code foresee the link of the same company to the headoffice vendor.
In cash management, customers and vendors are allocated to planning groups by means of an entry made in the master record.
The code release group classifies the vendor.
The personnel number is the only feature within a client which is unique to an employee (PF1 and WP1). You have to enter a personnel number before you can display and maintain an employee's master data and time data.
Payment Terms
Key for defining payment terms composed of cash discount percentages and payment periods. These field is specific linked to the Financial Accounting.

![]() |
|
|---|
Field | Standard Vendors | Miscellaneous Vendors | ||
|---|---|---|---|---|
| PF1 | WP1 | PF1 | WP1 | |
Reconciliation Account | 2300000000 | 40100100 | 2489101000 | 40100100 |
Sort Key | 009 | 001 | 009 | 001 |
Cash management group | A1 (Domestic) or A2 (Foreign) | - | A7 (Domestic) or A2 (Foreign) | - |
Release group | ZZZZ | - | Z003 | - |
Payment Terms | - | Y009 | - | Y009 |
Check Double Invoices | yes | yes | yes | yes |
Payment Method | 1 (same) or 3 (different country) | V (domestic transfer outside SEPA - 6068, 7781 and 7531) Z (SEPA payment method, domestic or European payment in EUR) T (International non - SEPA payment) | 1 (same) or 3 (different country) | Z |
| House Bank | FACT | - | FACT | - |
| Withholding Tax | - | FR - FR; D2; HO; Liable IT - IT; I3; 40; Liable | - | - |
SYSTEM: PF1_020 / WP1_400
Enter transaction MK01
Fill in vendor number and purchasing org.:

IMPORTANT:
When extending a vendor at purchasing level, we take as reference the values by the following order:
| Note |
|---|
|
SYSTEM: PI1
Enter transaction XK01
Fill in vendor number and CICC company code 0231:

| PI1 | |
|---|---|
| Recon. Account | 2300000000 |
| Sort Key | 009 |
| Minority Indic | - |
| Cash mgmnt group | - |
| Release Group | - |
| Payt Terms | - |
| Chk double inv. | yes |
| Payment method | =6 |
| House Bank | - |
| Clrk´s internet | - |
| WH Tax Country | - |
Enter transaction FK02
Fill in vendor number with a flag on Correspondence and enter:

The email address provided should be added to field Clrk's internet

IMPORTANT:
Is possible to add more than one email address, they should be separated by a blank space.
Once the changes have been made click on 
This kind of vendors are mostly used to send POs and are normally requested by POC Team, in order to be added to Main Vendor at Purchasing Org. Level.
An OA vendor is an exact copy of the main vendor, but with a different email address (some times could be possible to have the need to create an OA with the same email address for contract purposes)
Open two SAP sessions, in the first one enter transaction XK02 with the main vendor and in the other enter transaction XK01.
Enter the correct account group (all options can be found by pressing F4, sorted by country and type of vendor), the account group should be for the same country as the main vendor but should mention Address

Copy all info and add the new email address.
Don't forget to transfer the vendor to the respective SAP System (PF1/WP1) and add OA in Search Term 2 
Afterwards the OA should be added to the Main Vendor at Purchasing org. Level (always provided by the requester)
In transaction MK02 (PF1/WP1) flag option Partner Functions and add update the OA with the new number:

Once the changes have been made click on 
This kind of vendors are used for Selfbilling purposes and are normally requested by Selfbilling Team or directly by the locals.
An F9 vendor is an exact copy of the main vendor, but with a different email address.
Open two SAP sessions, in the first one enter transaction XK02 with the main vendor and in the other enter transaction XK01.
Enter the correct account group (all options can be found by pressing F4, sorted by country and type of vendor), the account group selected should be for the same country as the main vendor but should mention Address

Copy all info and add the new email address.
Don't forget to transfer the vendor to the respective SAP System (PF1/WP1)
Afterwards the request should be transferred to Materials Team in order to check the contracts and they will them transfer the Ticket to PTP AP Fileupload in order to set this new vendor for Selfbilling.
Enter transaction BD14
Enter transaction BD87

Don't add any info and execute

Click on the arrow of the yellow sign, than click on the message type that you have used in BD14 (don't open, just click once) and execute
The information should be sent to the target system (PF1 / WP1 / PI1)
Go to the target system and do the BD87 again directly on PF1 or WP1 (we don't have access to do it in PI1)
The information should now be available in production.