Transfer Entry RRAR Merge Process Report overview
Function acronym: WTERM
The Transfer Entry RRAR Merge Process Report (WT RRAR Merge) is the last step necessary in the replenishment cycle. This process converts your accepted warehouse transfer items into Transfer Entry transactions.
These criteria must be met before each warehouse transfer can be merged:
- If either the Default Line Acceptance to No or Default Line Acceptance to Yes option in SA Administrator Options-Documents-Transfer Orders- Replenishment is selected, blank acceptance is assumed as a No and transfer lines are not created.
- Each line item accepted to be merged must have an order quantity greater than zero. If the quantity ordered is zero, an exception is printed on the Exception Report and the report is not merged.
- The product must be active. If a product is not set up in Product Warehouse Product Setup or the product is inactive in Product Setup, the product is not copied to the warehouse transfer that is created. An exception is included on the Exception Report, but the merge still occurs and the WT RRAR header and line items are deleted if no partial lines exist.
Consider these items before you merge warehouse transfers:
- The maximum number of lines a WT RRAR can have is 9,999. However, 999 lines are allowable on a warehouse transfer. You are alerted when items still exist for the report number and that you must re-generate the WT RRAR Merge to include the remaining line items. These alerts continue until all line items are accounted for.
- If the Print Surplus not Taken on the RRAR Merge Report option in SA Administrator Options-Document-Transfer Orders-Replenishment is selected, any surplus that was not accepted is included on the report. If the option is not selected, surplus is not included on the report.
- If the product is surplus, a warehouse transfer is created if it has been accepted. The Reference field displays Surplus - WT RRAR Merge.
- Addons from the ship from warehouse are included in the line cost if the Include Addons option in SA Administrator Options-Products-Costs is selected.
For each line item added to the warehouse transfer created during WT RRAR Merge, the Approve Type is designated as shown in this table.
| SA Operator Setup Approval Warehouse | Product Warehouse Description Setup Ship From Whse Approve WT | Transfer Entry Approve Flag | Transfer Entry Approve Enterable | New Transfer's Stage |
|---|---|---|---|---|
| "*" or Ship From/Co# | Approve/Requested/ ARP Approved | Yes | Yes | Ordered |
| Not Ship From/Co # | Approve or ARP Approved (ARP is followed) | Yes | No | Ordered |
| Not Ship From/Co # | Requested or ARP Approved (ARP not followed) | Requested | No | Requested |
| Blank | Approve or ARP Approved (ARP is followed) | Yes | No | Ordered |
| Blank |
Requested or ARP Approved (ARP not followed) |
Requested | No | Requested |
ARP represents Authorized Replenishment Path.
For each line item added to a warehouse transfer created during Transfer Entry RRAR Merge Process Report, the Approve Type is set to Requested if the Product Warehouse Description Setup Approve WT field is set to R for the ship from warehouse or if none of the above conditions apply for the Approve Type Yes condition.
When a warehouse transfer is created, Product Warehouse Product Setup-Costs is updated for the products.
These conditions also apply:
- If it is a push transfer (ship to warehouse’s Product Warehouse Product Setup Push option is selected), the SA Administrator Options-Documents-Transfer Orders-Replenishment Push Stock On Hand to Zero, Safety, or Order Point option is used to determine the appropriate level for the Net Available.
- When the Transfer Entry RRAR Merge Process Report is run, ties to existing orders that have been subsequently back ordered are made to the back order rather than the original order.
- During Transfer Entry RRAR Merge Process Report, for each acceptance line item that is a special/nonstock product or component and the Accept type is Yes, the associated sales order or warehouse transfer is updated. The warehouse transfer number is cross-referenced with the respective order or transfer.
- If the line item was created from a nonstock/special sales order, build-on-demand kit component, or transfer, the order type, order number, line number, and sequence number (for a build-on-demand kit) is stored on the OE/WT line item. If the cost on a nonstock line is overridden in Transfer RRAR Acceptance, the cost is updated during WT RRAR Merge and is carried to the OE/WT order. If the unit is also changed, the cost is not carried back to the OE/WT until the transfer is received. Errors are incluced on the Exception Report if the product was changed, a line is missing, or the non-stock status has changed.
Auto merging
You can automatically merge WT RRARs for receiving warehouses during Transfer Entry RRAR Merge Process Report. Select Auto Merge in Product Warehouse Description Setup and WT RRAR reports generated for that warehouse as the receiving warehouse are created when the Merge option is Yes in Transfer Demand Center Entry.
When the Auto Merge option is selected for a warehouse, reports that are eligible for merging in Transfer Entry Recommended Replenishment Action Report will have the Ready to Merge flag set to Yes. This ensures they are picked up by the Transer Entry RRAR Merge Process Report without user intervention to manually set the Merge option. Other criteria for this automatic merge process include:
- There must be at least one line on the WT RRAR with the Accept Type option set to Yes. This option indicates there is stock to ship on the transfer. This is dependent on the setting for the Default Line Acceptance option in SA Administrator Options-Documents-Transfer Order-Replenishment.
- You must set up a @mrgwtrr merge stored report for the Transfer Entry RRAR Merge Process Report. This is used by the report to create the records used during the merge process.
If a WT RRAR is set to auto-merge, it is not included in the Transfer Entry Recommended Replenishment Action Report output. The transfer lines are accepted and ready to merge, so there is no need to include them on the report.
If there is a lag between the creation of the Transfer Entry Recommended
Replenishment Action Report and when you run Transfer Entry
RRAR Merge Process Report, you can view the report in
Transfer Demand Center Entry. The message RRAR is
Flagged As An Auto Merge RRAR (8050) is displayed if you try to access
the report.
Stored reports
If you are printing warehouse transfers when the Transfer Entry RRAR Merge Process Report is generated, you may want to use the options in Transfer Entry Print Warehouse Transfer. A stored report corresponding to the print function can be established with the default options to be used when the Automatic Print function or direct printing is initiated. Use a standard, consistent stored report naming convention. The following format is recommended: "@ + function + warehouse". For example, @wtmain would represent the stored report to print pick tickets for the main warehouse. If a stored report cannot be found, the current defaults are used.
For example, these defaults are set for Transfer Entry Print Warehouse Transfer:
Stored report name: @wtmain. Use only alphabetic characters and numbers in your stored report name. The use of punctuation marks and special characters (with the exception of @) causes the stored report function to fail.
Ship From Warehouse: global warehouse. The Print Transfer for Shipping Whse option in WT RRAR Merge always overrides the stored report Ship From Whse option so you have the most current information.
Enter a List of WTs: Yes
Print Orders thru Requested Ship Date: **/**/**
Days to Allow Forward: 0
Print Rush Transfers Only: No
Print Changes Only: Yes
Print Order: W
Back orders
If the Create Back Orders at Ordering Stage option in SA Administrator Options-Documents-Transfer Orders-Processing is selected, back orders are created or adjusted when you press Enter. The transfers are created before the Exception Report is run.