| Table of Contents |
|---|
1 Objective and Scope
1.1 Objective of this Procedure
This covers the SAP – Readsoft transactions related to Web Cycle Routing for FI Documents (coded invoices) and MM Documents (PO invoices).
1.2 Scope
This applies to Technology Solutions GBU working with SBS Latvia.
2 Definitions
These tables are used by all zones. Please make sure you are only adding, modifying or deleting entries related to the Technology Solutions GBU.
3 Main part
3.1 Transaction ZWFA05P – List of coder
This transaction controls the routing of the FI Coding web cycle based on the value populated on the Site field of a cockpit document.
...
When the request is received, DMO 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 ZWFA05P with the new Web Cycle ID and confirm back to the requester when the task has been completed.
3.1.1 Steps for ZWFA05P – List of coder
To add an entry, click on the 
button. The following fields must be populated:
...
To update the table use the Position option to locate the correct entry. Transaction ZWFA05P already places user in the change mode, thus you can immediately proceed with the changes.
3.2 Transaction ZWFA05N – list of approvers for EU
NOTE! Please ignore the title of this transaction it is not for EU only, back in 2009 it was developed at the request of EU. This table is actually used by ALL Zones.
...
When the request is received, DMO team will check to see if the user(s) have a Web Cycle ID. If not, they will create a new ID(s) via transaction /COCKPIT/WUM and then update table ZWFA05N with the new Web Cycle ID(s) and confirm back to the persons involved when the task has been completed.
3.2.1 Steps for ZWFA05N – list of approvers for EU
When you access transaction ZUFA05N it automatically places you in CHANGE mode.
...
To update the table use the Position option to locate the correct entry.
3.3 Transaction ZWFA05O – List of approvers for US
Note! Please ignore the title of this transaction, it is not for US only, back in 2008 it was developed at the request of US. This table is actually used by ALL Zones.
...
When the request from the GBU received, DMO team will check to see if the user(s) has a Web Cycle ID. If not, they will create a new ID(s) via transaction /COCKPIT/WUM and then update table ZWFA05O with the new Web Cycle ID(s) and confirm back to Front Office when the task has been completed.
3.3.1 Steps for ZWFA05O – List of approvers for US
When you access transaction ZWFA05O it automatically places you in CHANGE mode
...
To update the table use the Position option to locate the correct entry.
3.4 Transaction ZWFA05C – Limit amounts by company
This transaction controls the default approver of the Web Cycle based on the company code, site and invoice amount. The amount breakdown for NA is as follows:
...
When the request is received, DMO team will add a new entry to transaction ZWFA05C for the new site code and inform the requester when completed.
3.4.1 Steps for ZWFA05C – Limit amounts by company
When you access transaction ZWFA05C it automatically places you in CHANGE mode
...
Click the 
when complete.
3.5 Transaction ZWFA05H – List of generic mail
This transaction controls the routing of NOGR and Quantity Discrepancy Web Cycles to the Plant Generic Web cycle accounts (common mailbox) for Raw Material, Packaging and Industrial Supply POs based on purchasing organization and plant.
...
- After DMO team has received the request from Front Office, they must contact AP’s team leader and ask them to check, if the Web Cycle ID has any outstanding Web Cycles. If there are, they should be re-directed to the new ID that will be handling them. Once completed, the AP Team Lead will advise DMO.
- DMO team will remove all entries for the specific plant/site in the ZWFA05H transaction.
- After the entries have been removed DMO team will delete the generic Web Cycle ID(s) via transaction /COCKPIT/WUM.
- DMO team will notify the Front Office when completed.
3.5.1 Steps for ZWFA05H – List of generic mail
To add an entry, click on the 
New Entries button. You need to make an entry for each Purchase Org.
...
To remove entries, highlight the lines you want to remove and press the delete button:
3.6 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.
...
When the request from the Procurement FO Team Lead is received DMO team will create new Web Cycle ID for the Raw Material Operations Specialist via transaction /COCKPIT/WUM, in case it does not already exist. Then they will update table ZWFA05K with the Web Cycle ID and confirm back to the requester when the task has been completed.
3.6.1 Steps for ZWFA05K – Key procurer
When you access transaction ZUFA05K it automatically places you in CHANGE mode.
...
- CoCd: company code;
- Site;
- POrg: you need to make an entry for Purchasing Org. 3010 & 3014 only.
- Generic User: Web Cycle ID of the Raw Material Operations Specialist.
3.7 Transaction ZWFA05G – List of default recipient (Controller)
Default Site Controller for General Expense (3009), Industrial Service (3015) and Transportation Logistics (3016) POs. He will receive the Web Cycle in cases, if the requisitioners name listed on the PO is not linked to an active Web Cycle ID.
...
When the request is received, DMO 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 Web Cycle ID and confirm back to the requester when the task has been completed.
3.7.1 Steps for ZWFA05G – List of default recipient (Controller)
When you access transaction ZUFA05G it automatically places you in CHANGE mode.
...
- CoCd: Company code;
- Site;
- Default Recipient: Web Cycle ID of the Controller
3.8 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.
...
When the request is received, DMO 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 Web Cycle ID and confirm back to the requester when the task has been completed.
3.8.1 Steps for ZWFA05I – List of procurer
When you access transaction ZUFA05I it automatically places you in CHANGE mode.
...