Documents

0000522902

Description
SAP Batch Job
Categories
Published
of 3
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Related Documents
Share
Transcript
  SAP Note   Header Data Symptom  You are using the background processing in the delivery monitor, however, no list of the selected deliveries is created in the spool. Other Terms  VL06, VL06O, VL06I, delivery monitor, SAPLV50Q, outbound delivery monitor, inbound delivery monitor Reason and Prerequisites  The delivery monitor executes certain follow-on functions - depending on the selected view - for the selected deliveries and does not generate any list if it is started in the background. Solution  This consulting note contains details and prerequisites for the use of the background processing in a summarized form in the delivery monitor. In addition to that, extensive information on the delivery monitor and especially the background processing is available to you in the SAP library. The note continues to refer to the new functions in the delivery monitor for Release 4.70. 1. Background processing up to Release 4.6C  Some components of the delivery monitor can be used usefully for the processing of large document quantities in the background. By means of this table, you see which transactions a list output makes possible and which ones a background processing makes possible. Lists contain all selected deliveries. On the other hand, the background processing does not generate any list, but rather it triggers a follow-on function for all selected documents. If you want to execute a processing in the background, then create a selection variant and plan this as a job. You can also do this from the selection screen. For this purpose, select the function on the menu bar <program> or the pushbutton provided for this. After completing the background processing, a list of all successful or incorrectly processed documents exists in the spool. 1.1. Outbound delivery   1.1.1. WS_MONITOR_OUTB_DEL_PICK - VL06P (for the picking)   522902 - VL06: Background processing   Version  4 Validity:  28.05.2003 - active Language  English Released On  28.05.2003 18:55:06 Release Status  Released for Customer Component  LE-SHP-DL-RM Reporting / Monitoring LE-SHP-DL Delivery Processing LE-SHP-DL-LA Inbound Delivery LE-SHP-GI Goods Issue LE-SHP-PI Picking Priority  Correction with medium priority Category  Consulting Background processingList outputOutbound delivery ..Picking VL06P .............X..Confirmation VL06C .............X..Loading VL06L  ........X ..Goods issue VL06G ..............X..Trans. Plan. VL06T  ........X ..Delivery list VL06F ..............X Inbound delivery ..Transportation planning  ........X ..Putaway VL06IP ..............X..Confirmation VL06IC ..............X..Goods receipt VL06IG ..............X..Delivery list VL06IF  ........X Other Components  The report allows you to create WM transfer orders. In the enhanced selection screen, it is possible via 'Control background processing' to select the option 'Transfer picking quantity'. Select field 'Activate position'. With that the system copies all items to the active worklist of the TO creation. The control parameters of this transaction correspond to the control parameters of Transaction LT03 here for the creation of transfer orders for delivery. 1.1.2. WS_MONITOR_OUTB_DEL_CONF - VL06C (for the confirmation)  With this transaction, you can confirm pick orders. Field 'Transfer picking quantity' is also used for doing this with report WS_MONITOR_OUTB_DEL_PICK. 1.1.3. WS_MONITOR_OUTB_DEL_GDSI - VL06G (for the goods issue)  This report is usable for the posting of the goods issue of all selected documents. The actual goods issue date is expected here as a default for the deliveries to be posted and not as a selection criterion. If it is initial, the current date is used. In the spool, you see the successful and incorrect documents by specifying the cause for a non-possible goods issue posting after the conducted background processing. You can schedule the goods issue directly as a job via the Easy Access menu: Logistics -> Logistics Execution -> Goods issue for the Outbound Delivery -> Goods Issue Posting -> Background processing scheduling or directly by calling Transaction VL23. 1.1.4. WS_MONITOR_OUTB_DEL_FREE - VL06F (Delivery list outbound deliveries)  With this report, it is possible for you to process delivering and picking messages. In order to be able to trigger the message processing in the background, it is necessary that you make the necessary entries for each case in selection screen 'Message default' for the fields 'Pick list' or 'Message type'. In the background processing, V2 and V4 messages are processed. If, however, both fields remain empty, then no messages can be found in the background either. Then, in the spool, it is simply noted that no messages were selected. The output of group messages in the background is not supported. In the spool, the report returns a list of the processed documents. 1.2. Inbound delivery   1.2.1. WS_MONITOR_INB_DEL_PICK - VL06IP (for the Putaway)  The report allows the creation of transfer orders for the Putaway. Then the background processing refers here to the quantity to be paged in in each case. 1.2.2. WS_MONITOR_INB_DEL_CONF - VL06IC (for the confirmation)  With this transaction, it is possible for you to process all selected inbound deliveries for the confirmation in the background. 1.2.3. WS_MONITOR_INB_DEL_GDRC - VL06IG (for the goods receipt)  With this report, the posting of the goods receipt of all selected documents is allowed. The actual goods receipt date is expected here as a default for the deliveries to be posted and not as a selection criterion. If it is initial, the current date is used. In the spool, you see the successful and incorrect documents under specification of the causes for a non-possible goods receipt posting after the conducted background processing . In case of activated Handling Unit Management, it is possible to post inbound deliveries with handling units for the goods receipt before the Putaway, provided that you permitted that with the warehouse number. For this reason, you must have already set the indicator XWBTA in table TVLR. In the Customizing, you can define this setting under the following path: Logistics - General -> Handling Unit Management -> Basics -> Delivery -> Define Sequence of Transfer Order - Goods Receipt . Decisive for this is the combination of the warehouse number and item category. The posting must occur on an HU managed storage location so that the sequence of goods receipt and Putaway can be swapped. Also consider Note 530632 in connection with this. 2. New functions of the delivery monitor for Release 4.70   2.1. Outbound delivery   2.1.1. WS_MONITOR_OUTB_DEL_UNCH - VL06U (for the check)  Two different R/3 systems which are linked within function Cross-system goods flow are prerequisites for these functions. Orders are sent from the orders system to the delivery system for each IDoc. There, unchecked outbound deliveries are created as consumers. A conversion of unchecked outbound deliveries into checked outbound deliveries can be achieved by means of a delivery monitor, both in the dialog and in the background. Then, in the background, a check of the deliveries is triggered. 2.1.2. WS_MONITOR_OUTB_DEL_DIST - VL06D (for the distribution)  These functions are only relevant for you if you are working with decentralized WMS and outbound deliveries are not distributed immediately to the decentral system (distribution status 'D') after their creation. With the aid of the background functions, it is possible to distribute all selected and restrained outbound deliveries to the decentral system via IDoc. In the spool, you see the successful and incorrect documents by specifying the causes for a non-    possible distribution after the conducted background processing. 2.2. Inbound delivery   2.2.1. WS_MONITOR_INB_DEL_DIST - VL06ID (for the distribution)  This function is only relevant for you if you are working with decentralized WMS and inbound deliveries are not distributed immediately to the decentral system (distribution status 'D') after their creation. With the aid of the background functions, it is possible for you to distribute all selected and restrained inbound deliveries to the decentral system via IDoc. In the spool, you see the successful and incorrect documents by specifying the causes for a non-possible distribution after the conducted background processing. Validity References This document refers to: SAP Notes   This document is referenced by: SAP Notes (1)  Software Component From Rel. To Rel. And Subsequent SAP_APPL 45B 45B   46A 46B   46C 46C   470 470   113048 Collective note on delivery monitor  113048 Collective note on delivery monitor  

Pil

Jul 23, 2017

The Outsider

Jul 23, 2017
Search
Similar documents
Tags
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks