Creating deliveries by Background Job

Here are a few tips on creating outbound delivery documents via a background job:

1)       The Easy Access menu path:

  1. SAP menuàLogisticsàLogistics ExecutionàOutbound ProcessàGoods Issue for Outbound DeliveryàOutbound DeliveryàCreateàCollective Processing of Documents Due for Deliveryà
  2. VL10 – User-Specific Delivery Scenario
  3. VL10A – Sales Orders
  4. VL10C – Sales Order Items
  5. VL10E – Sales Order Schedule Lines
  6. VL10B – Purchase Orders
  7. VL10D – Purchase Order Items
  8. VL10F – Purchase Order Item Schedule Line
  9. VL10G – Sales Orders and Purchase Orders
  10. VL10H – Sales Orders and Purchase Orders (Items)
  11. VL10I – Sales Orders and Purchase Orders (Schedule Lines)
  12. VL10U – Cross-System Deliveries
  13. VL10BATCH – Plan Background Processing

2)       One can simply execute a transaction code as above and then fill the values of the selection screen and tabs, after which one may SAVE the variant.

3)       Transaction VL10BATCH is useful to show all variants. One can also use this transaction to select a variant and execute the job immediately or schedule the job.

4)       Alternatively one may use the batch Job Wizard (I am not going to share on how to use the job wizard as this is pretty basic via transaction code SM36.) to create a background job and schedule it. Use your created variant with program RVV50R10C.

 

Some Tips:

A)      It makes sense to create an express shipping point for which you can schedule a delivery creation background job in a much faster schedule to the normal delivery creation schedule.

B)      Be careful to schedule your jobs with care. For example you want your delivery creation job to be completed before you process any picking jobs and shipment related jobs. (Likewise you want your billing jobs to run after your shipment related jobs are completed.)

C)      It is not uncommon for the delivery creation jobs to hold sales docs and or materials in a shared or exclusive lock. This is not a problem. It just means you have to wait for the locks to be released, which in most instances should be split seconds. But knowing this happens your target should be to have more delivery due list jobs running with smaller run times than a single huge list which could lock itself at times.

D)      In the “User Role” Tab is a setting for Delivery Profile which has a field called “Repeat Blocked” This will set how many times the system will try access a document which is blocked.

E)      You can also enter a default delivery scenario and a default list profile for each user, that is called up from the menu or via transaction VL10. Set the user parameters LE_VL10_SZENARIO and LE_VL10_PROFIL. (You can see the values for the scenario on the “User Role” Tab.)

 

Leave a Reply