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 ???.
Unit of measurement (@IAG_WAS3.U_Lium):
Contains the unit of measurement out of the partner sales order / ERP.
Item stock (@IAG_WAS3.U_Onhand):
Contains the available item stock. It is determined through the item stock of the shipping warehouse (defined in partner sales order / ERP) minus the goods issue position of other goods issues which have the status “released”, but no delivery note has been created yet.
Storage location (@IAG_WAS3.U_Lgoart):
Contains the storage location defined in partner sales order / ERP. The feature Documents deducts the quantity from this storage location.
Item ID (@IAG_WAS3.U_Itemcode):
Contains the item number out of the partner sales order.
Item description (@IAG_WAS3.U_Itemname):
Contains the item description out of the partner sales order.
Batches (@IG_WAS3.U_Chanr):
Contains the amount of batches which have been designated to this position. The sum of the designated amount is in brackets.
Foreign item code (@IAD_WAS3.U_Fsn):
Contains the customer item number (foreign item code (FIC)) out of the partner sales order.
Customer factory (@IAG_WAS3.U_Wrk):
Contains the customer’s factory out of the partner sales order.
Unloading point (@IAG_WAS3.U_Abl):
Contains the customer’s unloading point out of the partner sales order.
Order number (@IAG_WAS3.U_Abs):
Contains the order number out of the partner sales order.
Change index (@IAG_WAS3.U_Aix):
Contains the change index out of the partner sales order.
Partner order No. (@IAG_WAS3.U_Docnum):
Contains the partner sales order number out of the partner sales order if the goods issue position was created because of a partner sales order. If the goods issue position is created because of a individual order position, the sales order number is saved.
Row (@IAG_WAS3.U_Visorder):
Contains the position number of the individual order position out of B1. If the origin is a partner sales order, this field stays empty.
Packaging definition variant (@IA_WAS3.U_Pmdvar):
Contains the PM (packaging material) variant, with which the goods issue position was packed up. With creation of the position, the PM variant is pulled out of the partner sales order. It can also be changed subsequently. If the variant is manipulated through the PM definition, the PM definition is pulled out of the partner sales order.
Net weight (@IAG_WAS3.U_Netgwt):
Contains the net weight (only the material weight) of the goods issue position. This field is filled through the feature Weight calculation.
Gross weight (@IAG_WAS3.U_Brtgwt):
Contains the gross weight (tare plus PM weight) of the goods issue position. This field is filled through the feature Weight calculation.
Number of positions (@IAG_WAS3.U_Anzps):
Contains the quantity of the outer packages. If there are packages with the M or G flag (mostly quantity of pallets), it then represents the quantity of these packages. If there are only packages with the S flag, the respective amount is saved. This field is filled through the feature Weight calculation.
Division quantity (@IAG_WAS3.U_Etlmng):
Contains the division quantity of the division which is to be satisfied out of the partner sales order. If the goods issue position is created out of the shipping proposal, the call quantity is pulled out of the shipping proposal. If the goods issue position is created manually, the call quantity is pulled from the selected allocation out of the partner sales order.
Division date (@IAG_WAS3.U_Etldat):
Contains the date of the selected division out of the partner sales order. If the goods issue position is created out of the shipping proposal, the call date is pulled out of the shipping proposal. If the goods issue position is created manually, the call date is pulled from the selected allocation out of the partner sales order.
Division time (@IAG_WAS3.U_Etlzet):
Contains the time of the selected division out of the partner sales order. If the goods issue position is created out of the shipping proposal, the call time is pulled out of the shipping proposal. If the goods issue position is created manually, the call time is pulled from the selected allocation out of the partner sales order.
Overdraft quantity (@IAG_WAS3.U_Etldis):
Contains the yet to be delivered quantity (plannable quantity) of the selected division out of the partner sales order. If the goods issue position is created out of the shipping proposal, the yet to be delivered quantity is pulled out of the shipping proposal. If the goods issue position is created manually, the yet to be delivered quantity is pulled from the selected allocation out of the partner sales order.
Customer reference number (@IAG_WAS3.U_Refnrk):
Contains the reference number of the selected division out of the partner sales order. If the goods issue position is created out of the shipping proposal, the reference number is pulled out of the shipping proposal. If the goods issue position is created manually, the reference number is pulled from the selected allocation out of the partner sales order.
Chassis number (@IAG_WAS3.U_Frgnr):
Contains the chassis number of the selected division out of the partner sales order. If the goods issue position is created out of the shipping proposal, the chassi number is pulled out of the shipping proposal. If the goods issue position is created manually, the chassis number is pulled from the selected allocation out of the partner sales order.
Kanban (@IAG_WAS3.U_Kanban):
Contains the Kanban number of the selected division out of the partner sales order. If the goods issue position is created out of the shipping proposal, the Kanban number is pulled out of the shipping proposal. If the goods issue position is created manually, the Kanban number is pulled from the selected allocation out of the partner sales order.
PUS-Number (@IAG_WAS3.U_Pusnr):
Contains the PUS-Number (Pick Up Sheet number / generally used by GM) of the selected division out of the partner sales order. If the goods issue position is created out of the shipping proposal, the PUS-number is pulled out of the shipping proposal. If the goods issue position is created manually, the PUS-number is pulled from the selected allocation out of the partner sales order.
Material handling code (@IAG_WAS3.U_Mhdcod):
Contains the material handling code of the selected division out of the partner sales order. If the goods issue position is created out of the shipping proposal, the material handling code is pulled out of the shipping proposal. If the goods issue position is created manually, the material handling code is pulled from the selected allocation out of the partner sales order.
Production No. (@IAG_WAS3U_Prodnr):
Contains the production number of the selected division out of the partner sales order. If the goods issue position is created out of the shipping proposal, the production number is pulled out of the shipping proposal. If the goods issue position is created manually, the production number is pulled from the selected allocation out of the partner sales order.
Special specification (@IAG_WAS3.U_Sspfkt):
Contains the special specification of the selected division out of the partner sales order. If the goods issue position is created out of the shipping proposal, the special specification is pulled out of the shipping proposal. If the goods issue position is created manually, the special specification is pulled from the selected allocation out of the partner sales order.
Type/Model (@IAG_WAS3.U_Typbm):
Contains the type/model of the selected division out of the partner sales order. If the goods issue position is created out of the shipping proposal, the type/model is pulled out of the shipping proposal. If the goods issue position is created manually, the special specification is pulled from the selected allocation out of the partner sales order.
Point of consumption (@IAG_WAS3.U_Verbrs):
Contains the point of consumption out of the partner sales order / general.
Usage key (@IAG_WAS3.U_vrwkey):
Contains the usage key out of the partner sales order / general.
Shipping address (@IAG_WAS3.U_Ladr):
Contains the address-ID of the shipping address out of the partner sales order / shipping.
Payment address (@IAG_WAS3.U_Radr):
Contains the address-ID of the shipping address out of the partner sales order / shipping.
Storage location customer (@IAG_WAS3.U_Lgokd):
Contains the customer’s storage location out of the partner sales order / ERP.
Country of origin (@IAG_WAS3.U_Urslnd):
Contains the country of origin out of the partner sales order / general.
Storage location item transfer (@IAG_WAS3.U_Lgoartu):
Contains the storage location of the ESP (external service provider) where the item is transferred to, out of the partner sales order / ERP.
Storage location packaging (@IAG_WAS3U_lgopm):
Contains the storage location of the packaging material out of the partner sales order / shipping.
Storage location packaging transfer (@IAG_WAS3.U_Lgopmu):
Contains the storage location where the packaging material is booked to via EDI. Comes out of the partner sales order / ERP.
Invoice ID (@IAG_WAS3.U_Rngid):
Contains the invoice number out of B1. This information is saved with the feature documents.
Price per unit ATM (@IAG_WAS3.U_Repatm):
Contains the price per unit out of the partner sales order / ERP.
Price per unit (@IAG_WAS3.U_Rep):
Contains the price per unit of the goods issue position, determined through the B1 price determination logic. This price is saved via the feature approval.
INV net amount (@IAG_WAS3.U_Rnetbtr):
Contains the invoice net amount of the goods issue position. This value is determined via the feature approval.
INV VAT amount (@IAG_WAS3.U_Rmwstb):
Contains the VAT amount of the goods issue position. This value is determined via the feature approval.
INV gross amount (@IAG_WAS3.U_Rbrtbtr):
Contains the gross amount of the goods issue position. This value is determined via the feature approval.
Invoice series (@IAG_WAS3.U_Rngkrs):
Contains the number range with which the invoice is created via the feature documents.
Credit No. (@IAG_WAS3.U_Gutnr):
Contains the credit note number which is saved through the feature history position procedure.
Credit unit price (@IAG_WAS3.U_Gep):
Contains the unit price of the credit note which is saved through the feature history position procedure.
Credit net amount (@IAG_WAS3.U_Gnetbtr):
Contains the net amount, transmitted through the credit note and saved through the feature history position procedure.
Credit VAT amount (@IAG_WAS3.U_Gmwstb):
Contains the VAT amount of the credit note which is saved through the feature history position procedure.
Credit gross amount (@IAG_WAS3.U_Grbrtbtr):
Contains the gross amount of the credit note which is saved through the feature history position procedure.
Delivery schedule EDI No. (@IAG_WAS3.U_Labdnr):
Contains the delivery schedule number of the selected allocation out of the partner sales order.
JIT EDI No. (@IAG_WAS3.U_Fabdnr):
Contains the JIT delivery schedule number of the selected allocation out of the partner sales order.
JIS EDI no. (@IAG_WAS3.U_Pabdnr):
Contains the JIS delivery schedule number of the selected allocation out of the partner sales order.
DNT-EDI-No (@IAG_WAS3.U_Lstdnr):
Contains the delivery note transport data EDI number. This number is created with the feature DNT-EDI.
INV-EDI-No (@IAG_WAS3.U_Rngdnr):
Contains the invoice EDI number. This number is created with the feature INV-EDI.
CN-EDI-No (@IAG_WAS3.U_Gutdnr):
Contains the EDI number the credit note was transmitted with. It is saved through the feature history position procedure.
Project (@IAG_WAS3.U_Project):
Contains the project out of the partner sales order.
Cost Center 1 (@IAG_WAS3.U_Prccd1):
Contains the 1st cost center out of the partner sales order / Cost acct..
Cost Center 2 (@IAG_WAS3.U_Prccd2):
Contains the 2nd cost center out of the partner sales order / Cost acct..
Cost Center 3 (@IAG_WAS3.U_Prccd3):
Contains the 3rd cost center out of the partner sales order / Cost acct..
Cost Center 4 (@IAG_WAS3.U_Prccd4):
Contains the 4th cost center out of the partner sales order / Cost acct..
Cost Center 5 (@IAG_WAS3.U_Prccd5):
Contains the 5th cost center out of the partner sales order / Cost acct..
Annotations (@IAG_WAS3.U_Bemerk):
Contains the annotation out of the partner sales order / Annotation.
Origin (@IAG_WAS3.U_Origin):
Contains a origin flag – whether the requirement comes from a normal requirement or a time slice. The following characteristics are possible:
| Value | Meaning | Description |
|---|---|---|
| N | normal | The requirement comes from a normal allocation |
| M | manual | Goods issue position comes from a manual creation |
| T | Timeslice | The requirement comes from an allocation which belongs to a time slice |
| P | JIS | The requirement comes from a JIS delivery schedule |
Expected RCQ (@IAG_WAS3.U_Erwefz):
Contains the expected RCQ (cumulated quantity received) which is reached through the reception of goods at the customer’s.
Creation user (@IAG_WAS3.U_Anlusr):
Contains the user who created the goods issue position.
Creation date (@IAG_WAS3.U_Anldat):
Contains the creation date of the goods issue position.
Creation time (@IAG_WAS3.U_Anlzet):
Contains the goods issue position’s creation time.
Update user (@IAG_WAS3.U_Updusr):
Contains the user who was the last to update the goods issue position.
Update date (@IAG_WAS3.U_Upddat):
Contains the date where the goods issue position was last updated.
Update time (@IAG_WAS3.U_Updzet):
Contains the time when the goods issue position was last updated.
Post your comment on this topic.