 |
Purchasing / Goods Receipt
Using the Goods Receipt for Purchase Order transaction makes sense if the SAP installation includes the Purchasing component of the MM (Materials Management) module, which handles purchases of goods from vendors. The Purchase Order in the SAP system includes information such as the vendor and the quantities and types of goods purchased. When a delivery arrives, the recipient should verify the contents of the delivery against the original Purchase Order document. Using the Goods Receipt for Purchase Order transaction allows the SAP system to update the purchase order history, valuate the goods receipt, and verify vendor invoices.
|
SAP TRANSACTIONS
|
|
MB01-101 / MIGO-101 – Goods Receipt for Purchase Order
|
The pre-configured Goods Receipt for Purchase Order transaction in the NLINK ADC to SAP Solution prompts the user for the Purchase Order number and / or a material or batch number, usually scanned off the delivery documentation or packaging. The NLINK ADC to SAP Solution then returns the matching line item information for verification of quantity and receiving location. Finally, the NLINK ADC to SAP Solution posts the goods movement using Movement Type 101 (Receipt to Warehouse/Stores) to the SAP system and notifies the user of the success of the transaction.
|
|
MB1C-501 – Goods Receipt without Purchase Order
|
The pre-configured Goods Receipt without Purchase Order transaction in the NLINK ADC to SAP Solution prompts the user for the material number, usually scanned off the delivery documentation or packaging. The NLINK ADC to SAP Solution then returns the material information for verification and prompts for the quantity and receiving location. Finally, the NLINK ADC to SAP Solution posts the goods movement using Movement Type 501 (Receipt without Purchase Order into Warehouse) to the SAP system and notifies the user of the success of the transaction.
|
Transfer Posting
SAP uses a Stock Transfer or a Transfer Posting to physically or logically move goods around internally, or to combine / reassign materials or material stock. Technically, the term Stock Transfer refers to a physical goods movement, while Transfer Posting refers to a logical goods movement. In practice, most people do not adhere to the distinction between the terms and use them interchangeably. The SAP system takes care of creating material and accounting documents as necessary, depending on the Movement Type and provided data.
|
SAP TRANSACTIONS
|
|
MB1B-301 – Transfer Posting Plant to Plant
|
The pre-configured Transfer Posting Plant to Plant transaction in the NLINK ADC to SAP Solution uses the Movement Type 301 (One-Step Transfer Posting Plant to Plant). It prompts the user for the issuing Plant, Storage Location and a material number or batch number. The NLINK ADC to SAP Solution then returns the existing inventory information for verification and prompts for the receiving Plant, Storage Location and quantity to move. Finally, the NLINK ADC to SAP Solution posts the goods movement to the SAP system and notifies the user of the success of the transaction.
|
|
MB1B-309 – Transfer Posting Material to Material
|
The pre-configured Transfer Posting Material to Material transaction in the NLINK ADC to SAP Solution uses the Movement Type 309 (Material to Material Transfer). It prompts the user for the issuing and receiving Material, source and destination Plant and Storage Location. The NLINK ADC to SAP Solution posts the goods movement to the SAP system and notifies the user of the success of the transaction.
|
|
MB1B-311 – Transfer Posting Storage Location to Storage Location
|
The pre-configured Transfer Posting Storage Location to Storage Location transaction in the NLINK ADC to SAP Solution uses the Movement Type 311 (One-Step Transfer Posting Storage Location to Storage Location). It prompts the user for the issuing Storage Location and a material number or batch number. The NLINK ADC to SAP Solution then returns the existing inventory information for verification and prompts for the receiving Storage Location and quantity to move. Finally, the NLINK ADC to SAP Solution posts the goods movement to the SAP system and notifies the user of the success of the transaction.
|
|
LT01 – Create Transfer Orders bin to bin
|
The pre-configured Create TO for Bin to Bin Transfer transaction in the NLINK ADC to SAP Solution prompts the user for the Warehouse, Movement code, Plant, Storage Location and Batch or Material Number, usually scanned off documentation or packaging. The NLINK ADC to SAP Solution then prompts the user for the source and destination storage type, section and bin. Finally, the NLINK ADC to SAP Solution creates a Transfer Order (TO) in the SAP system and notifies the user of the success of the transaction.
|
|
LT12 – Picking for Transfer Orders
|
The pre-configured Transfer Order (Picking) Confirmation transaction in the NLINK ADC to SAP Solution prompts the user for the Warehouse and Transfer Order (TO) number, usually scanned off documentation or packaging. The NLINK ADC to SAP Solution returns all matching and open (unconfirmed or partially confirmed) TO lines. Each TO line is shown one at a time. The user can navigate between TO lines using the << and >> buttons. The user marks all desired lines by checking the CONFIRM box for each line. Finally, the NLINK ADC to SAP Solution posts a confirmation containing all selected lines to the SAP system and notifies the user of the success of the transaction.
|
|
LT12 – Putaway for Transfer Orders
|
The pre-configured Transfer Order (Putaway) Confirmation transaction in the NLINK ADC to SAP Solution prompts the user for the Warehouse and Transfer Order (TO) number, usually scanned off documentation or packaging. The NLINK ADC to SAP Solution returns all matching and open (unconfirmed or partially confirmed) TO lines. Each TO line is shown one at a time. The user can navigate between TO lines using the << and >> buttons. The user marks all desired lines by checking the CONFIRM box for each line. Finally, the NLINK ADC to SAP Solution posts a confirmation containing all selected lines to the SAP system and notifies the user of the success of the transaction.
|
Physical Inventory
Companies take Physical Inventories to reconcile the book quantities and values with the actual on-hand quantities and values of their stored goods. In SAP, you can use periodic, continuous, cycle counting or sampling procedures to generate the Physical Inventory documents, which indicate the materials and locations to count. The following Physical Inventory transactions are currently available:
|
SAP TRANSACTIONS
|
|
MI04 – Physical Inventory Count
|
The pre-configured Physical Inventory Count transaction in the NLINK ADC to SAP Solution prompts for the Physical Inventory Document number. The NLINK ADC to SAP Solution then returns the storage location and material number for verification and prompts for the counted quantity. Finally, the NLINK ADC to SAP Solution posts the inventory count to the SAP system and notifies the user of the success of the transaction.
|
|
MI05 – Physical Inventory Recount
|
The pre-configured Physical Inventory Recount transaction in the NLINK ADC to SAP Solution prompts for the Physical Inventory Document number. The NLINK ADC to SAP Solution then returns the document count data for verification and prompts for the new count quantity. Finally, the NLINK ADC to SAP Solution posts the inventory count to the SAP system and notifies the user of the success of the transaction.
|
|
MI04/MI05 Combo
|
The pre-configured Physical Inventory Count / Recount combo transaction in the NLINK ADC to SAP Solution prompts for the Material number. The NLINK ADC to SAP Solution then returns the current active physical inventory document data, and prompts for the count quantity. If the item has been counted, the count quantity will also be displayed for verification. When the user posts the count quantity, the NLINK ADC to SAP Solution automatically checks to determine of the post should be a count (MI04) or a recount (MI05) posting.
|
|
MI09 – Physical Inventory Count without Reference
|
The pre-configured Physical Inventory Count without Reference transaction in the NLINK ADC to SAP Solution prompts for the storage location and material number. The NLINK ADC to SAP Solution then returns the material information for verification and prompts for the counted quantity. Finally, the NLINK ADC to SAP Solution creates the Physical Inventory document in the SAP system along with the inventory count and notifies the user of the success of the transaction.
|
Plant Maintenance / Maintenance Orders
If the SAP installation includes the Plant Maintenance (PM) component, which handles planning and tracking of goods used for maintenance of technical objects (assets), then using the Goods Issue for Work Order transactions may make sense.
|
SAP TRANSACTIONS
|
|
MB1A-261 – Goods Issue to Work Order
|
The pre-configured Goods Issue to Work Order transaction in the NLINK ADC to SAP Solution prompts the user for the Work Order number, usually scanned off the order documentation. The NLINK ADC to SAP Solution then returns the matching line item information for verification of quantity and issuing location. The user can navigate between items using the << and >> buttons. Finally, the NLINK ADC to SAP Solution posts the goods movement using Movement Type 261 to the SAP system and notifies the user of the success of the transaction. Option to link goods issue to Asset Serial Number is also available.
|
|
MB1A-921 – Goods Issue to Service Order
|
The pre-configured Goods Issue to Service Order transaction in the NLINK ADC to SAP Solution prompts the user for the Service Order number, usually scanned off a order documentation. The NLINK ADC to SAP Solution retrieves all matching and open reservation items associated with the service order. Each reservation item is shown one at a time. The user can navigate between items using the << and >> buttons. When the user posts an issue against a particular item, the NLINK ADC to SAP Solution will post the goods movement using Movement Type 921 to the SAP system and notifies the user of the success of the transaction.
|
|
MB1A-262 – Goods Issue Reversal
|
The pre-configured Goods Issue Reversal to Work Order transaction in the NLINK ADC to SAP Solution prompts the user for the Work Order number, usually scanned off the order documentation or packaging. The NLINK ADC to SAP Solution then returns the matching line item information for verification. The user can navigate between items using the << and >> buttons. Finally, the NLINK ADC to SAP Solution posts the goods movement using Movement Type 262. to the SAP system and notifies the user of the success of the transaction. Option to link goods issue reversal to Asset Serial Number is also available.
|
Production / Manufacturing Orders
If the SAP installation includes the Production Order component of the PP (Production Planning) module, which handles planning and tracking of goods used for in-house production of materials, then using the Goods Receipt for Production Order and Goods Issue to Production Order transactions may make sense. The Production Order in the SAP system includes information such as the material being produced, the quantities and types of goods needed to produce the material, and the destination of the finished material. The Goods Issue transaction tracks consumption of the goods needed to produce another material, while the Goods Receipt acknowledges the new material created as a result of completing the Production Order.
|
SAP TRANSACTIONS
|
|
MB1A-261 – Goods Issue to Production Order
|
The pre-configured Goods Issue to Production Order transaction in the NLINK ADC to SAP Solution prompts the user for the Production Order number and a material or batch number, usually scanned off the production documentation or packaging. The NLINK ADC to SAP Solution then returns the matching line item information for verification of quantity and issuing location. Finally, the NLINK ADC to SAP Solution posts the goods movement using Movement Type 261 (Consumption for Order from Warehouse) to the SAP system and notifies the user of the success of the transaction.
|
|
MB31-101 – Goods Receipt for Production Order
|
The pre-configured Goods Receipt for Production Order transaction in the NLINK ADC to SAP Solution prompts the user for the Production Order number and / or a material or batch number, usually scanned off the delivery documentation or packaging. The NLINK ADC to SAP Solution then returns the matching line item information for verification of quantity and receiving location. Finally, the NLINK ADC to SAP Solution posts the goods movement using Movement Type 101 (Receipt to Warehouse/Stores) to the SAP system and notifies the user of the success of the transaction.
|
|
CO11N – Production Order Confirmation for Time Tickets
|
The pre-configured Production Order Confirmation for Time Tickets in the NLINK ADC to SAP Solution prompts the user for the Production Order number and a specific operation, usually scanned off the order documentation or packaging. The NLINK ADC to SAP Solution then returns the matching line item information for verification, and prompts users for quantity to be confirmed. Finally, the NLINK ADC to SAP Solution posts the confirmation to the SAP system and notifies the user of the success of the transaction. The option to combo this transaction with MB1A-261 or MB31-101 exists if necessary.
|
|
CO15 – Production Order Confirmation on Header Level
|
The pre-configured Production Order Confirmation on Header Level in the NLINK ADC to SAP Solution prompts the user for the Production Order number, usually scanned off the order documentation or packaging. The NLINK ADC to SAP Solution then returns the matching order item information for verification, and prompts users for quantity to be confirmed. Finally, the NLINK ADC to SAP Solution posts the confirmation to the SAP system and notifies the user of the success of the transaction.
|
Outbound Delivery
In SAP, an Outbound Delivery is a composition of the goods that is provided for shipping. The Outbound Delivery is the basis for the Advanced Shipping Notification (ASN) and Delivery Note that are sent to the product recipient. Outbound Deliveries can be applied to Sales Orders, Purchase Orders, or Stock Transport Orders. When you create an outbound delivery, you initiate shipping activities such as picking and transportation scheduling.
|
SAP TRANSACTIONS
|
|
VL01N – Create Outbound Delivery for Sales Order
|
The pre-configured Create Outbound Delivery for Sales Order transaction in the NLINK ADC to SAP Solution prompts the user for the Sales Order number and a material availability date (defaulted to the current date, but editable). The NLINK ADC to SAP Solution verifies that an active outbound delivery document does not exist, then returns the matching line item information for verification. Finally, the NLINK ADC to SAP Solution posts the request to the SAP system and notifies the user of the success of the transaction. The option to combine this with the VL02N Transaction is also available.
|
|
VL01N – Create Outbound Delivery for Stock Transport Order
|
The pre-configured Create Outbound Delivery for Stock Transport Order transaction in the NLINK ADC to SAP Solution prompts the user for the Stock Transport Order number. The NLINK ADC to SAP Solution verifies that an active outbound delivery document does not exist, then returns the matching line item information for verification. Finally, the NLINK ADC to SAP Solution posts the request to the SAP system and notifies the user of the success of the transaction. The option to combine this with the VL02N Transaction is also available.
|
|
VL02N – Outbound Delivery Confirmation
|
The pre-configured Outbound Delivery Confirmation transaction in the NLINK ADC to SAP Solution prompts the user for the Outbound Delivery Document number OR the Sales Order / Stock Transport Order Number. The NLINK ADC to SAP Solution verifies that an active outbound delivery document exists, then returns the matching line item information for verification. After user enters the delivery quantity, the NLINK ADC to SAP Solution posts the request to the SAP system and notifies the user of the success of the transaction.
|
Stock Inquiries
Inventory stock inquiries are sometimes necessary to reduce the likelihood for Goods Movement Errors. The following Stock inventory inquiry transactions are available:
|
SAP TRANSACTIONS
|
|
MMBE – Plant Stock per Material
|
The pre-configured Plant Stock per Material transaction in the NLINK ADC to SAP Solution prompts the user for the material number. The NLINK ADC to SAP Solution then returns the inventory for the material in SAP, and displaying the results on the screen. Users have the option to filter the results displayed by plant, storage location, Batch, and/or non-zero values.
|
|
LS24 – Bin Stock per Material
|
The pre-configured Bin Stock per Material transaction in the NLINK ADC to SAP Solution prompts the user for the Warehouse, Plant and Batch or Material Number, usually scanned off documentation or packaging. When the user selects the QUERY button, the NLINK ADC to SAP Solution returns all matching Warehouse Quants. Each Quant is shown one at a time. The user can navigate between Quants using the << and >> buttons. This is a reporting only transaction and does not include any posting to SAP.
|
SAP Fixed Assets
Many organizations face a significant challenge to track the location, quantity, condition, maintenance and depreciation status of their fixed assets. By tracking fixed assets using bar code tags for easy and accurate reading, companies can periodically take inventory with a mobile barcode reader and then produce a variety of reports. As a result, companies reduce expenses through loss prevention and improved equipment maintenance. They reduce new and unnecessary equipment purchases, and they can more accurately calculate taxes based on depreciation schedules. In general, Fixed Assets need to be created, edited, moved, verified and (ultimately) retired.
|
SAP TRANSACTIONS
|
|
Download Fixed Asset Inventory List
|
The pre-configured Download Fixed Asset Inventory List transaction in the NLINK ADC to SAP Solution for Fixed Assets prompts the user for a Plant Code, Location and/or Room. The NLINK ADC to SAP Solution for Fixed Assets then retrieves a list of inventoried Fixed Assets that fit the entered criteria. It stores this list in the local database, and all further processing validates against this data, until such time as the user retrieves a new list.
|
|
Scan Fixed Asset
|
The pre-configured Scan Fixed transaction in the NLINK ADC to SAP Solution for Fixed Assets prompts the user for an Asset number and, if necessary an Asset Sub-number. The NLINK ADC to SAP Solution for Fixed Assets then searches for this Asset in the previously downloaded Fixed Asset Inventory List. If it finds the Asset, it displays the matching information (description, last count date, quantity, etc.) and allows the user to make changes. If it does not find the Asset, it prompts the user to create a new Asset.
|
|
Reconcile Fixed Asset Scans
|
The pre-configured Reconcile Fixed Asset Scans transaction in the NLINK ADC to SAP Solution for Fixed Assets walks the user through posting each scanned Asset back to SAP. Each post will be a Change (AS02) or Create (AS01) as appropriate, based on the actions the user took during the Scan Fixed Asset interface. The user does not have to reconcile all outstanding transactions in one sitting, but will not be able to perform and new Scans, or do Retires or Receipts until the Reconciliation is either completed (by going through all the pending Posts) or abandoned (by downloading a fresh Fixed Asset Inventory List).
|
|
Receive Fixed Asset: Goods Receipt for Purchase Order (MB01-101)
|
The pre-configured Receive Fixed Asset transaction in the NLINK ADC to SAP Solution for Fixed Assets prompts the user for the Purchase Order number, usually scanned off the delivery documentation or packaging. The NLINK ADC to SAP Solution for Fixed Assets then returns the line item(s) containing Fixed Assets. If there are multiple line items, the user may move back and forth between the lines to select the correct Fixed Asset entry. Once the desired line item is location, the user verifies the receiving details. Finally, the NLINK ADC to SAP Solution for Fixed Assets posts the goods movement using Movement Type 101 (Receipt to Warehouse/Stores) to the SAP system and notifies the user of the success of the transaction.
|
|
Retire Fixed Asset (ABAON)
|
The pre-configured Retire Fixed Asset transaction in the NLINK ADC to SAP Solution prompts the user for an Asset number and, if necessary an Asset Subnumber. The NLINK ADC to SAP Solution for Fixed Assets then searches for this Asset in the previously downloaded Fixed Asset Inventory List. If it finds the Asset, it displays the matching description and allows the user to enter posting dates and revenue value for retirement. Finally the NLINK ADC to SAP Solution for Fixed Assets posts the retirement using Asset Sale without Customer to the SAP system and notifies the user of the success of the transaction.
|
VIDEO PRESENTATIONS
There`s really only so much information you can absorb by reading about an enterprise software product like the NLINK ADC to SAP Solution. At some point you need to see the software in action and that`s what the NLINK ADC to SAP Solution Video Presentations are all about.
REQUEST AN NLINK ADC TO SAP DEMO
If you have already seen the Video Presentations and would like to learn more by scheduling a WebEx demonstration of the NLINK ADC to SAP Solution, please click here.
TECHNICAL INFORMATION
For more technical and product information regarding the NLINK ADC to SAP Solution please contact .
SALES AND PRICING INFORMATION
For sales and pricing information regarding the NLINK ADC to SAP Solution please contact .
|
