1. Objective and Scope
1.1 Objective of this Procedure
This LOP covers the SAP – Readsoft transactions related to Web Cycle Routing for MM Documents (PO invoices)
1.2 Scope
This LOP applies to Solvay USA Inc & Solvay Canada Inc in the NA that work with Solvay SBS.
2. Definitions
This table is used by all zones. Please make sure you are only adding, modifying or deleting entries related to the North American Zone (6283, 7424, 7651)
3. Main part
3.1 Transaction ZWFA05H – List of generic mail
This transaction controls the routing of NOGR and Quantity Discrpancy web cycles to the Plant Generic Web cycle accounts for Raw Material (3014), Packaging(3010) and Industrial Supply (3012) POs.
This table does not require any recurring maintenance (ie. daily, weekly, monthly, etc). It will only have to be updated if a new Site/Plant is set up in WP1 or a Site/Plant is being removed from WP1. This is rare.
Since these are the Generic Web Cycle Accounts for the plants/sites, there would only be requests to set up new sites or delete existing ones. Front Office should notify D&A team of a new site, providing new email address and company number/site code etc. if applicable. If it is a request for a deletion then Front office will provide the company number and site code of the existing location and reason for its removal.
When D&A team receives a request:
For a new plant/site – D&A team will create a new generic web cycle ID via transaction /COCKPIT/WUM and link it to the email address provided by FO. After the new ID is set up then they can add the entries for the new site/plant in table ZWFA05H for each Purchase Org: 3009, 3010, 3011, 3012, 3013, 3014, 3015, 3016. After the table has been updated they will advise FO that request has been completed and the New Generic Web Cycle account and initial password.
Deleting a plant/site – After D&A has received the request from FO, they must contact AP's team leader and request that the web cycle account be checked for any outstanding web cycles. If there are, then redirect them to the new WC id that will be handling them. Once completed, the AP Team Lead will advise D&A and they can delete the web cycle id, who will go into transaction ZWFA05H and remove all entries for that site/plant. After the entries have been removed, then D&A team will delete the generic web cycle id(s) via transaction /COCKPIT/WUM. Notify FO when deletion is completed.
3.2 Transaction ZWFA05K – Key procurer
This transaction controls the routing of Price Discrepancy web cycles for Raw Material (3014) and Packaging(3010) to the Raw Material Operations Specialist.
This table does not require any recurring maintenance (ie. daily, weekly, monthly, etc). If will only need to be updated if the Raw Material Operations Specialist changes.
Procurement Team lead for FO will advise D&A team if there is a change in who the Raw Material Operations Specialist is. They will provide the name, phone number and email address of the new person incase D&A needs to set up the user with a Web Cycle id.
When the request from the Procurement FO Team Lead is received, D&A team will check to see if the user has a web cycle id. IF not, they will create a new id via transaction /COCKPIT/WUM and then update table ZWFA05K with the new web cycle id and confirm back to the requester when the task has been completed.
3.3 Transaction ZWFA05G – List of default recipient (Controller)
For General Expense (3009), Industrial Service (3015) and Transportation Logistics (3016) POs, if the requisitioner name listed on the PO is not linked to an active web cycle ID, the system will route the web cycle to the Controller for that site.
This table does not require any recurring maintenance (ie. daily, weekly, monthly, etc). If will only need to be updated if the Controller for the site changes.
The GBU, plant manager or Front Office will advise the D&A team if there is a new Controller for a site/plant. They will provide the Site ID, Name, Phone number and email address and who they are replacing.
When the request is received, D&A team will check to see if the user has a web cycle id. IF not, they will create a new id via transaction /COCKPIT/WUM and then update table ZWFA05G with the new web cycle id and confirm back to the requester when the task has been completed.
3.4 Transaction ZWFA05I – List of procurer
This transaction controls the routing of Invalid PO web cycles based on the site code populated on the cockpit document.
This table does not require any recurring maintenance (ie. daily, weekly, monthly, etc). If will only need to be updated if the Procurer/LPR changes.
The GBU, plant manager or Front Office will advise the D&A team if there is a new Procurer/LPR for a site/plant. They will provide the Site ID, Name, Phone number and email address and who they are replacing.
When the request is received, D&A team will check to see if the user has a web cycle id. IF not, they will create a new id via transaction /COCKPIT/WUM and then update table ZWFA05I with the new web cycle id and confirm back to the requester when the task has been completed.




