AFS Outbound Delivery

Outbound delivery is the process of delivering goods to the customer. In this process, the stock is moved
out of one's premises into the customer's warehouse. Outbound delivery supports all shipping activities,
including picking, packing, transportation, and goods issue. During the outbound delivery process,
shipping-planning information is recorded, status of shipping activities is monitored, and data
accumulated during shipping processing is documented. When the outbound delivery is created, the
shipping activities, such as picking or delivery scheduling, are initiated, and data that is generated during
shipping processing is included in the delivery.
In AFS, Deliveries can be created only with reference to a preceding document. One more important
point to be noted is that in AFS delivery it is very important that an Allocation Run ( ARun) has been
carried out before creating delivery. Allocation will provide the batch information which is picked by AFS
delivery. Batches cannot be entered during delivery creation.
For processing deliveries with AFS materials, AFS-specific tab pages are available (AFS item overview and
AFS picking). Similar to the structure of the sales documents, item details at grid value level can also be
displayed in the shipping documents. The following data can be checked:
Stock/ requirements category
Delivery group
Schedule line group
Process flow:
1. Create Sales Order and Save
2. Execute ARun and carry out allocation
3. Create Outbound Delivery and Save
4. Carry out Picking and Post Goods Issue.
In AFS, the Sales orders contain schedule lines with reference to the SKU's maintained for the material.
The allocation is also carried out with respect to the SKU's. However when it comes to delivery, the item
of the Sales Order is created as the main item and the schedule lines are created as the Batch Split
items. All AFS materials should therefore by default be Batch Split.
An AFS delivery looks like the following, with the main item being 10 and the subitem being the row
with item number starting from 900001


The AFS information is there in the tab AFS data.

Picking has to be carried out at the sub item level.

Once the picking is done, Post Goods Issue can be carried out.

Database tables:
LIKP SD Document: Delivery Header Data
LIPS
SD document: Delivery: Item data
MCHB
Batch Stocks
J_3ABDBS
AFS Requirement - Stock assignment
J_3ABDSI
AFS ORDER (Sizes)

Logic:
Allocation Run is mandatory for Delivery creation in AFS. The allocation tables are read and the delivery
sub items are created accordingly.
After PGI, the J_3ABDSI and J_3ABDBS entries are deleted.
Technical
1. Building Batch Split items (Include : MJ3AVFDL_BATCH_SPLIT )
The allocation tables (J_3ABDBS) are read using the below mentioned function module


For each entry of J_3ABDBS which has an F status (Fixed)

The FORM batch_split_item is called.


Call Stack :
SAPMJ3AV FORM BATCH_SPLIT
SAPMJ3AV FORM J_3A_BATCH_ASSIGN
SAPFV50P FORM LIPS_BEARBEITEN
SAPFV50C FORM LIPS_KOPIEREN
SAPFV50C FORM VORLAGE_KOPIEREN
SAPMV50A FORM AUFTRAG_REFERIEREN
SAPMV50A MODULE (PAI) AUFTRAG_REFERIEREN

2. Save the Delivery (Include : MJ3AVFDL_SAVE_DOCUMENT)
BDBS save is called here

Deletion of allocation is taken care of in this routine.

Stock information is updated here


Schedule lines status is saved here


Call Stack :
SAPMJ3AV FORM J_3A_SAVE_DOCUMENT
SAPMV50A FORM BELEG_SICHERN_POST
SAPMV50A FORM BELEG_SICHERN_01
SAPMV50A FORM BELEG_SICHERN


3. Post Goods Issue (PGI)

SAPLMBWL FUNCTION MB_CREATE_GOODS_MOVEMENT
SAPFV50W FORM WA_MATERIALBELEG_ERZEUGEN
SAPFV50W FORM WARENAUSGANG_BUCHEN
SAPMV50A FORM FCODE_WABU
SAPLV00F FORM FCODE_BEARBEITEN
SAPLV00F FUNCTION SCREEN_SEQUENCE_CONTROL
SAPMV50A FORM FCODE_BEARBEITEN
SAPMV50A MODULE (PAI) FCODE_BEARBEITEN



General Information
To Copy the picked quantity as the Delivery quantity, use this menu item.



The VAS data in the document can be seen




Delivering different sales order together with the current delivery is not supported