This covers the SAP – Readsoft transactions related to Web Cycle Routing for FI Documents (coded invoices) and MM Documents (PO invoices).
This applies to Technology Solutions GBU working with SBS Latvia.
These tables are used by all zones. Please make sure you are only adding, modifying or deleting entries related to the Technology Solutions GBU.
This transaction controls the routing of the FI Coding web cycle based on the value populated on the Site field of a cockpit document.
This table does not require any recurring maintenance (i.e. daily, weekly, monthly etc.). It will only have to be updated, if a new coder is taking over responsibility for a Site/GBU.
Request will come from the GBU, Plant manager or Controller. They will provide the name, phone number and email address of the user and which site code they will now be handling.
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.
To add an entry, click on the 
button. The following fields must be populated:
Click the save button 
when completed.
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.
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.
This transaction controls the routing of the FI Validation Web Cycle by Company Code, Site and Vendor (optional).
There can be up to three different approvers for each Company code and Site. Note that the approvers are defined in the relation of invoice amount.
Approver 1 up to Superior Limit 1
Approver 2 up to Superior Limit 2
Approver 4 over Superior Limit 2
In cases when two approvers are required for the same site and same invoice limit a PO should be created instead.
This table is only updated, if the approvers for a GBU/Site have changed or a new Site has to be added to the table.
We can also receive requests from Accounts Payable, to add an approver for a specific site and vendor code.
Note! There always has to be at least one entry for each Site code in this table. Even if the approver is defined for a cost center, an entry for Company Code and Site has to be made in this table to catch any FI request that comes in referencing a cost center not defined on table ZWFA05O.
If asked to add a new approver for a specific vendor code or change an existing one, an approval needs to be arranged from the default approver of the site (site controller). Persons involved need to be informed as well.
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.
When you access transaction ZUFA05N it automatically places you in CHANGE mode.
To add an entry, click on the 
button. Populate the following fields:
Click the save button 
when completed.
To update the table use the Position option to locate the correct entry.
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.
Transaction ZWFA05O controls the routing of the FI Validation Web Cycle by Company Code, Site and Cost Center.
There can be up to three different approvers for each Company code and Site. Note that the approvers are defined in the relation of invoice amount.
Approver 1 up to Superior Limit 1
Approver 2 up to Superior Limit 2
Approver 4 over Superior Limit 2
This table is only updated if the approvers for a GBU/Site/Cost Center have changed or a new Site has to be added to the table (and there are approvers defined at the cost center level). (Note: if there is no approver defined at the cost center level then this table does not need to be updated, only ZWFA05N)
Only the GBU can submit a request for a change or provide a list of approvers for a new Site code. They will send their request to James Weaver, who will provide the GBU/Site and vendor if applicable.
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.
When you access transaction ZWFA05O it automatically places you in CHANGE mode
To add an entry, click on the 
button. Populate the following fields:
Click the save button 
when completed.
To update the table use the Position option to locate the correct entry.
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:
These values are entered for every new site code that is created. If this table is not populated, the FI Validation web cycle flow will not work for the new Site code.
Only Mark Dahlinger (or his comparable level) can authorize the change in these values.
Front Office will advise the DMO team when there is a new site code. They will provide both: the Company Code and the Site code.
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.
When you access transaction ZWFA05C it automatically places you in CHANGE mode
To add an entry, click on the 
button. Populate the following fields:
Click the 
when complete.
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.
This table does not require any recurring maintenance (i.e. 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 DMO 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 DMO team receives a request:
For a new plant/site:
Deleting a plant/site:
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:
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 (i.e. daily, weekly, monthly etc.). It will only need to be updated if the Raw Material Operations Specialist changes.
Procurement Team lead for Front Office will advise DMO team, if there is a change in who the Raw Material Operations Specialist is. They will provide the information required to create a new Web Cycle ID for this person.
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.
When you access transaction ZUFA05K it automatically places you in CHANGE mode.
To update, navigate to the required company code, and change all entries to the Web Cycle ID of the new Raw Material Operations Specialist.
To add an entry, click on the 
button. Populate the following fields:
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.
This table does not require any recurring maintenance (i.e. daily, weekly, monthly etc.). It will only need to be updated if the Controller for the site changes.
The GBU, plant manager or Front Office will advise the DMO 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, 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.
When you access transaction ZUFA05G it automatically places you in CHANGE mode.
To update, navigate to the requested company code, and change the entry to the Web Cycle ID of the new Controller.
To add an entry, click on the 
button. Populate the following fields:
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 (i.e. daily, weekly, monthly etc.). It will only need to be updated if the Procurer/LPR changes.
The GBU, plant manager or Front Office will advise the DMO 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, 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.
When you access transaction ZUFA05I it automatically places you in CHANGE mode.
To update, navigate to the company code requested, and change the entry to the Web Cycle ID of the new Procurer/LPR.
To add an entry, click on the 
button. Populate the following fields: