All the material numbers and delivery notes for a goods issue are lodged in the tab “positions”. A goods issue always refers to one customer.
The goods issue position can be managed via the following structures:
- Position data
- Context menu
Position data
Delivery note number (@IAG_WAS3.U_Lsnr):
Contains the delivery note number of the goods issue position. While adding, this number is generated automatically. The delivery note number is a reserved number and already exists before a B1 delivery note. There is a distinct number range which is managed in the ATM configuration. The delivery note numbers are divided in two groups: normal delivery notes (with invoice creation) and ESP (external service provider) delivery notes (these delivery notes are closed in B1, without creating an invoice).
DN pos (@IAG_WAS3.U_Lsponr):
Contains the delivery note position number. It is almost always “1”. That means every delivery note has only one position. There is one exception at the moment: At Porsche AG one delivery note is assigned per conclusion of the purchase order number, that implies several positions can exist per delivery note.
Shipment status (@IAG_WAS3.U_Vvssts):
Contains the status of the goods issue position. The following characteristics are possible:
Wert | Bedeutung | Beschreibung |
---|---|---|
01 | created | The goods issue head is created. |
02 | recorded | The goods issue position (at least one) is created. |
03 | weighted | The feature weight calculation was conducted. |
04 | released | The feature approval was conducted. |
05 | GIS printed | The feature shipping papers was conducted. |
06 | Order created | The feature documents was conducted and only one sales order was created. |
07 | Delivery note created | The feature documents was conducted and one sales order and one delivery note were created. |
08 | Invoice created | The feature documents was conducted and one sales order, one delivery note and one invoice were created. |
09 | Goods entry created | The feature documents was conducted during a ESP (external service provider) delivery and a sales order, delivery note and the goods entry were created on the ESP storage. |
10 | Package booked | The feature Packaging booking was conducted successfully. |
11 | DNT sent | The feature DNT-EDI was conducted and DNTs (delivery note transport data) were also sent out (a output file is created). |
12 | INV sent | The feature INV-EDI was conducted and the INV (invoice) was also sent out (a output file is created). |
13 | CRN received nOK | A credit note was received for the goods issue, but there is a deviation in the invoice amounts. This status can be set only if the customer is in the credit note procedure. |
14 | CRN received OK | A credit note was received for the goods issue, and the invoice amounts concur. This status can be set only if the customer is in the credit note procedure. |
15 | DNT created | The feature DNT-EDI was conducted but the DNTs were not sent out. This status allows one to start the feature “DNT-EDI” once again. |
16 | INV erstellt | The feature INV-EDI was conducted but the INV was not sent out. This status allows one to start the feature “INV-EDI” once again. |
20 | closed |
Delivery note date (@IAG_WAS3.U_Lsdat):
Contains the delivery note date. During the creation of the position, the date is equalled with the cargo transfer date.
Delivery note quantity (@IAG_WAS3.U_Lsmng):
Contains the delivery note quantity. If the goods issue position was created through a shipping proposal, the delivery note quantitiy is inherited from this shipping proposal. If the goods issue position is created manually, the value of the field is to be deleted. The “TAB” key opens then another window including the possibility to pick an allocation out of the respective partner sales order. The creation of a goods issue position out of an allocation of a partner sales order is important, because other data (call date, call quantity, quantitiy to be delivered) is taken over from the allocation as well. These fields are necessary for a ???.
Post your comment on this topic.